Professional Documents
Culture Documents
ANSYS LS-DYNA MAPDL 14.5 L08 Postprocessing PDF
ANSYS LS-DYNA MAPDL 14.5 L08 Postprocessing PDF
Postprocessing
14.5 Release
ANSYS LS-DYNA
in Mechanical APDL
© 2012 ANSYS, Inc. February 5, 2013 1 Release 14.5
Objectives
• This lecture concerns Postprocessing. Both the POST1 and POST26 ANSYS
postprocessors are illustrated. Accessing LS-DYNA ASCII results file data
is also covered. Since the LS-PREPOST postprocessor from LSTC is
unsupported by ANSYS, Inc., it is only discussed in the workshop
accompanying this lecture.
• Topics:
A. POST1 Overview
B. RSYS Capabilities in POST1
C. Failed Elements in POST1
D.Animation in POST1
E. POST26 Overview
F. EDREAD Command in POST26
G.Postprocessing Workshop
• In contrast, the POST26 Time History Postprocessor is used to view a small subset
of the model (limited by the EDHIST command) much more often via the contents
of the binary Jobname.HIS file. The frequency at which data is written to this
history file is based on the EDHTIME command setting. The Time History
Postprocessor will be discussed in more detail, later.
• To get results closer to the surface, more layers should be used through
the thickness of the shell. The NIP real constant determines how many
integration points exist through the shell thickness, but the EDINT
command determines which of these layers data is saved for.
© 2012 ANSYS, Inc. February 5, 2013 5 Release 14.5
... POST1 Overview
• Another peculiarity is in how stress and strain data is saved. For a five
layer shell in which data is saved for each layer (NIP=5 and EDINT=5),
the stress data is available for all five layers, but LS-DYNA only writes
out strain data for the top and bottom layers. Therefore, LAYER=2
represents the second layer for stress, but the fifth layer (in this case)
for strain. Layers are counted from the bottom surface of the shell.
• Shell stresses can be rotated into another coordinate system using RSYS, except for
composite shells (KEYOPT(3) = 1). The data saved on some of the LS-DYNA ASCII
files (e.g., the elout file) can be presented in a different coordinate system than
discussed above.
• Local coordinate systems defined with the EDLCS command must be redefined
with the LOCAL command in order to be interpreted by RSYS. Elements that do
not support RSYS should be unselected before issuing the RSYS command to avoid
POST1 error messages. Finally, the RSYS command is not applicable to POST26.
PUNCH
BLANK
DIE
• Note: The ANDATA.MAC macro is unusable for all but the most simple
models. Until this problem is corrected, you will need to use
interpolation (via ANTIME.MAC) to animate your models.
• When reading most of these files, additional information is required. For example,
the SPCFORC file requires the specification of a node number for which the reaction
force data is desired.
• For the desired ASCII output data to be available, several things must
be done before the solution is initiated:
– The output file needs to be requested ( EDOUT, SPCFORC )
– The appropriate restraint, etc. needs to exist ( D, 1, ALL, 0.0 )
– The entity must belong to a history file component ( EDHIST, NODE_1 )