Anytime you add nonphysical mass to increase the timestep in a dynamicanalysis, you affect the results (think of
F=m*a). Sometimes the effect is insignificant and in those cases adding nonphysical mass is justifiable. Examples of such cases may include the addition of mass to just a few small elements in a noncritical area or quasi-static simulations where the velocity is low and the kinetic energy is very small relative to the peak internal energy. In the end, it’s up to the judgement of the analyst to gage the affect of mass scaling. You may have to reduce or eliminate mass scaling in a second run to gage the sensitivity of the results to the amount of mass added.
One can employ mass scaling in a selective manner by artificially increasing material density of the parts you want to mass-scale. This manual form of mass scaling is done independently of the automatic mass scaling invoked with
DT2MS is input as a negative value, mass is added only to those elements whose timestep would otherwise be less than
|DT2MS|. By adding mass to these elements, their timestep becomes equal to
|DT2MS|. An infinite number of combinations of
DT2MS will give the same product, i.e., timestep but the added mass will be different for each of those combinations. The trend is that the bigger
|DT2MS| (and the smaller
TSSFAC*|DT2MS|=const), the greater the added mass. In return, stability may improve as
TSSFAC is reduced (just as in non-mass-scaled solutions). If stability is a problem with the default
TSSFAC of 0.9, try 0.8 or 0.7. If you reduce
TSSFAC, you can increase
|DT2MS| proportionally so that their product, and hence timestep, is unchanged.
MATSUMfiles. These files will allow you to plot added mass vs. time for the complete model and for individual parts, respectively. To produce fringe plots of added mass in parts comprised of shell elements (
*DATABASE_EXTENT_BINARY. You can then fringe the added mass (per element) using LS-POST by choosing Fcomp > Misc > time step size. (Here, the label “time step size” is really the element added mass.)
*CONTROL_TIMESTEPis as follows:
Negative: Mass is added to only those elements whose timestep would otherwise be less than
TSSF*abs(DT2MS). When mass scaling is appropriate, I recommend this method.
Positive: Mass is added or taken away from elements so that the timestep of every element is the same. My opinion is there is no advantage to using this method over the negative
DT2MS method and I find it harder to rationalize.
*CONTROL_TIMESTEP controls whether mass is added only once during initialization (
MS1ST=1) or anytime as necessary to maintain the desired timestep specified via
You can use
*CONTROL_TERMINATION to stop the calculation aftera certain amount of mass has been added (active for automatic mass scaling only).
The mass-scaling parameter in
DT) affects only the spotwelds. If no mass-scaling is invoked in
DT2MS=0.) AND the timestep is controlled by the deformable spotwelds,
DT can be used to add inertia to the spotwelds during intialization in order to increase the timestep to a value of
DT is nonzero, mass added to spotweld beams is reported to
MATSUM momentum and KE does NOT factor in added mass to def. spotwelds.
GLSTAT DOES factor in added mass to total KE.
d3hspis bogus when
DT2MSis neg. and
*MAT_SPOTWELD = 0, the following are correct: “added spotweld mass” in
d3hsp“added mass” and “percentage increase” in
d3hspAFTER the first time step “added mass” in
*MAT_SPOTWELDis NOT INCLUDED in “added mass” given in
DT2MSis neg. and
*MAT_SPOTWELDis nonzero. This can be quite misleading. User must check for “added spotweld mass” in
d3hsp. Recommended: Do not invoke both mass-scaling criteria. Neg.
DT=0(case 1 above) is preferred.
DTis nonzero and
DT2MS=0, the initial timestep will NOT consider added spotweld mass but the time step will increase by 10% each cycle until the correct timestep (considering added spotweld mass) is achieved.
matsumcontain no “added mass” line item.
*CONTROL_TIMESTEP. Selective mass-scaling can be turned on using the
*CONTROL_TIMESTEPand could apply either to all the parts of the model (set to 1) or do just a few parts (<0 with abs(IMSCL) = part set list) which is recommended as the selective mass-scaling is both memory and CPU intensive.
m*a=Ftakes some CPU time. The system is solved iteratively.