Professional Documents
Culture Documents
Optistruct 130 Reference Guide
Optistruct 130 Reference Guide
In addition, the following countries have resellers for Altair Engineering: Colombia, Czech Republic, Ecuador, Israel, Russia,
Netherlands, Turkey, Poland, Singapore, Vietnam, Indonesia
Official offices with resellers: Canada, China, France, Germany, India, Malaysia, Italy, Japan, Korea, Spain, Taiwan, United
Kingdom, USA
In addition to HyperWorks® trademarks noted above, Display Manager™, Simulation Manager™, Compute Manager™, PBS™,
PBSWorks™, PBS GridWorks®, PBS Professional®, PBS Analytics™, PBS Desktop™, PBS Portal™, PBS Application Services™,
e-BioChem™, e-Compute™ and e-Render™ are trademarks of ALTAIR ENGINEERING INC.
Altair trademarks are protected under U.S. and international laws and treaties. Copyright© 1994-2014. Additionally, Altair software
is protected under patent #6,859,792 and other patents pending. All other marks are the property of their respective owners.
ALTAIR ENGINEERING INC. Proprietary and Confidential. Contains Trade Secret Information. Not for use or disclosure outside of
ALTAIR and its licensed clients. Information contained inHyperWorks® shall not be decompiled, disassembled, or “unlocked”,
reverse translated, reverse engineered, or publicly displayed or publicly performed in any manner. Usage of the software is only as
explicitly permitted in the end user software license agreement.
Reference Guide
........................................................................................................................................... 1
Input Data
............................................................................................................................................... 2
The Bulk Data Input File
................................................................................................................................... 3
Guidelines for I/O Options and Subcase Information Entries
................................................................................................................................... 7
Guidelines for Bulk Data Entries
................................................................................................................................... 9
Solution Sequences - Data Selectors (Table)
................................................................................................................................... 14
Summary of Defaults for I/O Options
................................................................................................................................... 15
I/O Options Section
................................................................................................................................... 22
Subcase Information Section
................................................................................................................................... 233
Bulk...................................................................................................................................
Data Section 318
Element Quality Check
................................................................................................................................... 2160
Material Property Check
................................................................................................................................... 2189
Output Data
............................................................................................................................................... 2197
List of Files Created by OptiStruct (Alphabetical)
................................................................................................................................... 2200
Results Output by OptiStruct
................................................................................................................................... 2346
Legacy Data
............................................................................................................................................... 2378
Previous (OS3.5) Input Format
................................................................................................................................... 2379
Setting Up Decks in OptiStruct 5.0 with OptiStruct 3.5 Objectives and
Constraints
................................................................................................................................... 2384
Previously Supported Input
................................................................................................................................... 2388
The Subcase Information Section contains information for specific subcases. It identifies
which loads and boundary conditions are to be used in a subcase. It can control output type
and frequency, and may contain objective and constraint information for optimization
problems. For more information on solution sequences, see the table included on the Solution
Sequences page of the online help.
The Bulk Data Section contains all finite element data for the finite element model, such as
grids, elements, properties, materials, loads and boundary conditions, and coordinates
systems. For optimization, it contains the design variables, responses, and constraint
definitions. The bulk data section begins with the BEGIN BULK statement.
One-File Setup
In a one-file setup, all three data sections are included in one file. The bulk data section
must be the last section. It is recommended that the extension .fem be used for this file.
Multi-File Setup
A multi-file setup is facilitated through the use of INCLUDE statements. This option enables
you to include information from other files without cutting and pasting. INCLUDE statements
may be placed in any section of the one or two-file setup, but must include information
appropriate to the section.
The following example shows how an additional subcase can be added to the Subcase
Information section.
$ Subcase 2
Subcase 1 SPC = 1
SPC = 1 Load = 3
Load = 2
$
INCLUDE sub2.inc
$
BEGIN BULK
$
The solver reads all files and positions the lines of the included file at the location of the
INCLUDE statement in the input.fem file. An echo of the input.fem file as read by
OptiStruct would be:
$
Subcase 1
SPC = 1
Load = 2
$
Subcase 2
SPC = 1
Load = 3
$
BEGIN BULK
$
The two-file setup separates the control data (I/O Options section and Subcase Information
section) from the model data (Bulk Data section). If the input file does not contain a BEGIN
BULK statement, the solver attempts to read the model data from another file:
If the INFILE card is present in the I/O Options section, the argument given on this
card is the name of the file that contains the model data.
If the INFILE card is not present in the I/O Options section, and the input file does not
have the extension .fem, the name of the file containing the model data will be
constructed from the input file by replacing the extension with .fem.
The two-file setup allows you to perform runs using multiple control data files and a single
model file and vice versa. It is recommended that the .parm extension be used for control
data files and the .fem extension be used for model data files.
An input file and referenced included files can be optionally compressed using gzip
compression. A compressed file has to have the extension .gz appended to the file name.
Valid example file names are: input.fem.gz, input.gz, and input.dat.gz. Compressed files
can be mixed with plain ASCII files. The INCLUDE card does not have to be modified when a
file is compressed. For example, if the card INCLUDE infile.dat were present, the reader
would search for infile.dat and continue on to search for the compressed file,
infile.dat.gz, if not found. Other input files (such as RESTART, ASSIGN) cannot be
compressed.
The following guidelines apply to all entries in the I/O Options and Subcase Information
sections:
All input cards are limited to 80 characters per line; all characters after the 80th are
skipped. SYSSETTING,CARDLENGTH may be used to change the number of characters
allowed in each line.
Cards which require a file name (OUTFILE, RESTART, INCLUDE, LOADLIB, TMPDIR,
EIGVNAME, ASSIGN) can contain up to 200 characters in a single line. Alternatively,
the file name may be continued in several lines if it is enclosed in quotes (" or ‘). When
combining continuation lines, all trailing and leading blanks in each line are omitted.
Other blanks, including all blanks between the quote and file name, are considered as
part of the file name.
File names can contain an absolute or relative path. Forward slash (/) or back slash
(\) characters can be used to separate parts of a path name. Absolute paths are
discouraged since they prevent moving files from one location to another, and may
cause unexpected failures, as in PBS or a similar batch environment.
Windows style file names, starting with the drive letter (for example: D:/users/mbg/
workarea), can be used on UNIX/Linux only when environment variable(s)
DOS_DRIVE_# are defined. Content of the respective environment variable replaces
the first two letters (‘D:’) in the file name, and the expanded file name must fit within
200 characters. Alternatively, the DOS_DRIVE_# option can be specified in the config
file. UNC format (//server/path/filename) is not accepted.
Each line of data contains up to ten fields in free format. Entries in the free format are
separated by any number of characters from the following set:
(blank)
, (comma)
File names and titles (TITLE, SUBTITLE, LABEL) are exceptions to this rule.
P2G / K2GG / M2GG / B2GG entries allow more than ten fields per line (up to
CARDLENGTH limit).
GROUNDCHECK / WEIGHTCHECK / EIGVRETRIEVE / XYPLOT allow more than ten fields
per line and are the only entries which allow continuation.
Dollar signs, $, in any column denote comments. All characters after the dollar sign
until the end of the line are ignored. A dollar sign can be a part of a file name or title,
but the full title or file name must be enclosed in quotes (" or ‘) in such cases.
Lines which begin with two slashes, //, or a pound symbol, #, are read as comment
lines. Blank lines are also assumed to be comment lines.
Examples
is equivalent to:
INCLUDE "path//split into multiple / lines/filename.txt "
Note that several spaces, the space at the end in particular, which are valid parts of this
name, may cause unexpected results.
The following guidelines apply to all entries in the bulk data section:
Data may contain 80 characters per line at most. All characters after the 80th are
ignored. The only exception is for the INCLUDE data entry. SYSSETTING,CARDLENGTH
can be used to change the number of characters allowed in each line.
Each line of data contains up to nine fields in one of the three accepted formats:
Fixed Format
Each field consists of 16 characters; two consecutive lines form nine fields, similar to
other formats (shown below). Large field format is recognized by the first character
after the keyword, or by the first character in each continuation line, which must be
‘*’. The second line (‘half line’), if present, must also contain ‘*’ in the first column.
The first and last field in each half line is eight characters long. The last field on each
first half-line and the first field on each second half-line are ignored.
The following examples show the same card in fixed and large field formats:
Free Format
Fields are separated by commas; blank characters surrounding commas are not
significant. Two consecutive commas define empty (blank) fields. If a comma is
present in a line of data, it is assumed to be free format data. Continuation lines for
free format start with a blank, '+' or '*'.
If there is a comma within the first 10 characters in a line, the line is assumed to be in
free format; otherwise, if there is an '*' immediately after the card name or a
continuation line starts with '*', then the line is accepted as large field fixed format.
All other lines are read in as fixed format.
Use of fixed format limits the range of integer data (-9,999,999 .. 99,999,999) and the
accuracy of floating point numbers, but does not influence the internal storage of data
– in particular all floating point numbers are always read and stored with full precision
(64-bit REAL*8).
Bulk data is always limited to 9 fields per line. Content of 10th field and the first field
of each continuation line are silently skipped when fixed format is used (other codes
can use these fields for special purposes, such as to mark matching continuation lines).
Extensions of free format (which may allow more than 9 fields in a line) are not
accepted. An error message is issued when a free format card contains more than 9
fields. This error can be disabled (changed to non-fatal warning) through the use of
SYSSETING,SKIP10FIELD.
Dollar signs, $, in any column denote comments. All characters after the dollar sign
until the end of the line are ignored. Dollar signs can only appear in quoted files
names.
Lines which begin with two slashes, //, or a pound symbol, #, are read as comment
lines. Blank lines are also assumed to be comment lines.
The full keyword of each bulk data entry must be given starting from the first column.
Abbreviated keywords are not allowed.
The format of most bulk data entries is similar to that for Nastran. Not all entry
options are supported by OptiStruct. Consult the list of fields and options supported.
Continuation entries must follow the parent entries. If the first character of any entry
is either a blank, a ‘+’, or an ‘*’, it is treated as a continuation of the previous entry.
If the entire line is blank, it is treated as a comment line.
An ENDDATA entry or end-of-file denotes end of data. Lines after the ENDDATA entry
are ignored.
All Bulk Data entries must appear after the BEGIN BULK statement in the input data.
The content of the tenth field in each card, and that of the first field in each
continuation card, is disregarded.
Each entry can be placed anywhere within the field. For example, blanks preceding
and following an entry are ignored, except the keyword entry, which must be left
justified in its field.
0.1
.1
+.1
-0.1
1e5
1e+5
1+5
1.0E-5
.1d-5
.00001-05
Character entries longer than eight characters are silently truncated in large field and
free field formats, with the exception of file names on the INCLUDE entry (see
documentation for INCLUDE entry) and the “LABEL’ field on DESVAR, DRESP1, DRESP2,
DRESP3, and DTABLE entries (allows up to 16 characters).
Continuation lines do not have to be in the same format as the parent entries. It is
allowed to mix lines in different formats within a single bulk data card.
Invisible tab characters are equivalent to the number of spaces needed to advance to
the nearest tab stop. Tab stops are placed at the beginning of each eight-character
field. Use the SYSSETTINGS,TABSTOPS option to change this value, for example, to
tab stops at 4-character fields.
Replication is a limited data generation capability which may be used for GRID data
only.
Duplication of fields from the preceding GRID entry is accomplished by coding the
symbol =.
Duplication of all trailing fields from the preceding entry is accomplished by coding
the symbol ==.
Only the fields for ID, CP, X, Y, Z, and CD can be incremented. The PS data
cannot be incremented.
Entered entries:
GRID,101,17,1.0,10.5,,17,3456
GRID,*1,=,*(0.2),==
GRID,*100,,=,=,*10.0,==
GRID,20,17,==
Generated entries:
Key:
O Optional Data Selector. All optional data selectors can be set equal to zero in order to
override inheritance from default settings (data selectors appearing before the first
subcase).
E Either one of the selectors marked E are required, both are optional.
Data selector may be defined above the first subcase, in which case it is used in any
subcase where it is allowed (as long as it has not been defined specifically).
** METHOD(Fluid) and SDAMPING(Fluid) are allowed when the model does not contain fluid
parts, but a warning is issued in such cases.
‡ Direct Frequency and Transient solutions only allow reference of FREQ, FREQ1 and
FREQ2. Modal Frequency and Transient solutions also allow reference of FREQ3, FREQ4
and FREQ5.
Run Controls
TMPDIR ./ or .\ error
Analysis Output
AUTOSPC NO YES
PRETBOLT NO YES
Optimization Output
HISOUT 15 15
RESULTS FL FL
SENSOUT FL FL
DMIGNAME AX AX
Optimization
FE Analysis
Description
The @HyperForm statement indicates an input file for one-step stamping simulation written
from HyperForm.
Format
@HyperForm
Comments
1. Must be present as the first line of the input file to allow the one-step stamping related
bulk data entries to be accepted as input.
Description
The ACCELERATION command can be used in the I/O Options or Subcase Information sections
to request acceleration vector output for all subcases or individual subcases respectively.
Format
ACCELERATION(sorting,format,form,rotations,random,peakoutput) = option
sorting <SORT1, SORT2> This argument only applies to the PUNCH format
(.pch file) or the OUTPUT2 format (.op2 file) output
Default = blank for normal modes, frequency response, and
transient subcases. It will be ignored without
warning if used elsewhere.
format <HM, H3D, HG, OPTI, HM: Results are output in HyperMesh
PUNCH, OP2, PLOT, binary format (.res file).
blank>
H3D: Results are output in Hyper3D
Default = blank format (.h3d file).
option <YES, ALL, NO, YES, ALL, blank: Acceleration is output for all
NONE, SID> nodes.
1. When the ACCELERATION command is not present, acceleration results are not output.
2. Acceleration output is only available for frequency response and transient analysis
solution sequences.
3. The form argument is only applicable for frequency response analysis. It is ignored for
other analysis types.
4. The forms BOTH and COMPLEX do not apply to the .frf output files.
5. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information
on the results available and their respective formats.
6. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
7. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as
it does not allow different frequencies for different formats.
8. In general, HyperView does not recognize the SORT2 format for results from the .op2 file.
When results are output only in SORT2 format (<Result Keyword> (SORT2, OUTPUT2, …
.)), the results are written by OptiStruct into the .op2 file in SORT2 format, but when
the .op2 file is imported into HyperView, the results in SORT2 format are not recognized.
Therefore, the SORT1 option is recommended for results output in OUTPUT2 format and
SORT2 option is recommended for results output in PUNCH format.
9. Results in binary format (.h3d or .op2) are always output in PHASE/MAG form, regardless
of the options specified in the FORM field. The corresponding post-processors
(HyperView/HyperGraph) can easily convert the PHASE/MAG format to the required
formats. Results in ASCII formats are output in the specified/requested FORM.
10. The abbreviations ACCE and ACCEL are interchangeable with ACCELERATION.
11. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The ASSIGN command can be used in the I/O Options section to identify external files and
their contents.
Format
AKUSMOD filename N/A Identifies an external file from which to read the
AKUSMOD fluid-structure coupling matrix.
See comment 1.
EXCINP SUBCASE ID filename Identifies an external file from which to read the
modal participation factors calculated by AVL/
EXCITE for both transient and FRF residual runs.
H3DDMIG matrixname filename Identifies an external nodal flexh3d file from which to
read DMIG matrices. Provides a prefix (matrixname)
for the matrices contained therein, and the path to
and the name of the flexh3d file. All of the matrices
in the h3d file are used in the analysis by default. If
only some of the matrices are to be used, then use
the K2GG, M2GG, K42GG, and B2GG data to specify
which matrices are to be used. The unreferenced
matrices will not be used in this case.
H3DCDS matrixname filename Identifies an external file from which to read complex
dynamic matrices for a CDS residual run. Provides a
prefix (matrixname) for the matrices contained
therein and the path to and the name of the
filename_CDS.h3d file. All of the matrices in the
filename_CDS.h3d file are used in the analysis.
H3DMBD Flex Body ID filename Identifies an external nodal flexh3d file which
contains the analysis recovery information for
displacements, velocities, accelerations, stresses
and strains. Provides a Flex Body ID for the
information therein, and the path to and the name
of the flexh3d file.
MBDINP SUBCASE ID filename Identifies an external file from which to read the
modal participation factors calculated by
MotionSolve for transient analysis.
See comment 1.
UPDATE filename N/A Identifies an external file from which to read the
updated cards after an optimization run.
GRID
CONM2
Examples
Comments
1. For geometric nonlinear subcases, two types of modification commands are available in
the external file defined with ASSIGN,STARTER/ENGINE: insert and replace.
insert
Syntax: /INSERT,LINENUM
Content to be inserted
/ENDINS
Usage: Uses content between keywords /REPLACE and /ENDREP to replace the
content in the intermediate RADIOSS Block deck between line numbers
LINENUM1 and LINENUM2.
Content as replacement
/ENDREP
2. The SEINTPNT subcase information entry can only be used to convert interior super
element grid points in .h3d files referenced by ASSIGN, H3DDMIG.
Limitations:
Each subcase can only be defined with a maximum of one ASSIGN,STARTER entry and
one ASSIGN,ENGINE entry.
In the external file, the line numbers (LINENUM after /INSERT, and LINENUM1 after /
REPLACE) should be input in increasing order.
For subcases in the same load sequence (defined by CNTNLSUB), ASSIGN,STARTER
settings should be identical.
Description
The AUTOSPC command requests that stiffness singularities and near singularities be
constrained automatically with single point constraints.
Format
Argument Description
(Default)
PUNCH Creates a PUNCH file with SPC data for each AUTOSPC DOF
for each SUBCASE. The SPC SID is the SUBCASE ID.
NOPUNCH Do not create a PUNCH file with SPC data for each
AUTOSPC DOF for each SUBCASE.
(Default)
Comments
Description
The CDSMETH command can be used in component dynamic synthesis method for generating
component dynamic matrices at each loading frequency.
Format
CDSMETH = CDSID
Example
CDSMETH = 10
Default = NONE
Comments
2. The subcase must be a modal frequency response subcase, except it does not require a
DLOAD card for load specification.
Description
The CHECK command can be used in the I/O Options section to request that only a model
check be performed.
Format
CHECK
Comments
2. If this keyword is present, only the subroutines which read in the input files are executed.
A report that provides information on errors in the model and the memory and disk space
requirements is given.
3. Useful for large runs since the amount of memory and time required to perform this
function is very small.
Description
The CMDE command can be used above the first SUBCASE or within a SUBCASE definition to
request component modal synthesis damping energy output for all subcases or individual
subcases respectively.
Format
CMDE(format_list,THRESH=thresh,RTHRESH=rthresh,TOP=topn,MODES=mset,TYPE=type)
= option
mset <ALL, SID, TOTAL> ALL: Modal energy is output for all
modes.
Default = ALL
SID: If a set ID is given, modal energy
is output only for modes listed in
that set.
option <YES, ALL, NO, YES, ALL, blank: Modal energy is output.
NONE>
Default = ALL
NO, NONE: Modal energy is not output.
Comments
1. When the CMDE command is not present, component modal synthesis damping energy is
not output.
2. Component modal synthesis damping energy output is only available for frequency
response analysis (both direct and modal methods). It is intended for use when external
CMS superelements are used.
3. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information
on which results are available in which formats.
4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
5. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous version of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as
it does not allow different frequencies for different formats.
Description
The CMKE command can be used above the first SUBCASE or within a SUBCASE definition to
request component modal synthesis kinetic energy output for all subcases or individual
subcases respectively.
Format
CMKE(format_list,THRESH=thresh,RTHRESH=rthresh,TOP=topn,MODES=mset,TYPE=type)
= option
mset <ALL, SID, TOTAL> ALL: Modal energy is output for all
modes.
Default = ALL
SID: If a set ID is given, modal energy
is output only for modes listed in
that set.
option <YES, ALL, NO, YES, ALL, blank: Modal energy is output.
NONE>
Comments
1. When the CMKE command is not present, component modal synthesis kinetic energy is not
output.
2. Component modal synthesis kinetic energy output is only available for frequency response
analysis (both direct and modal methods). It is intended for use when external CMS
superelements are used.
3. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information
on which results are available in which formats.
4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
5. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous version of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as
it does not allow different frequencies for different formats.
Description
The CMSE command can be used above the first SUBCASE or within a SUBCASE definition to
request component modal synthesis strain energy output for all subcases or individual
subcases respectively.
Format
CMSE(format_list,THRESH=thresh,RTHRESH=rthresh,TOP=topn,MODES=mset,TYPE=type)
= option
Comments
1. When the CMSE command is not present, component modal synthesis strain energy is not
output.
2. Component modal synthesis strain energy output is only available for frequency response
analysis (both direct and modal methods). It is intended for use when external CMS
superelements are used.
3. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information
on which results are available in which formats.
4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
Description
The CONTF entry can be used in the I/O Options or Subcase Information sections to request
contact results output for all nonlinear analysis subcases or individual nonlinear analysis
subcases respectively.
Format
CONTF (format, type) = option
Default = blank
OPTI: The total contact force results are
output to the .cntf file.
Default = ALL
FORCE: Contact force results are output.
option <YES, ALL, YES, ALL, Contact results are output for all grid
Comments
1. The CONTF entry is only applicable in nonlinear analysis subcases that are identified by the
presence of an NLPARM subcase entry. The specific detailed result types displayed differ
slightly between NLSTAT and geometrically nonlinear subcases.
2. Most of the contact results are real numbers and are self-explanatory. Some results that
may require clarification are listed below:
Open/Closed status is represented by 0.0 for Open and 1.0 for Closed. On graphical
display, intermediate values may appear due to transition from open to closed across
individual elements,
Slip/Stick Status is represented by 0.0 for Open, 1.0 for Slip and 2.0 for Stick. On
graphical display, intermediate values may appear due to transition of status across
individual elements,
Sliding Distance represents total sliding distance accumulated while the surfaces are in
contact. This may be different than just the difference in displacements between the
starting and final position.
3. The calculation of contact results on both sides of contact interface involves projections
and mappings. Therefore, a perfect match of results between two sides cannot be
expected, especially on mismatched meshes. Also, the resolution of different types of
results (pressure versus gap opening) differs according to their respective FEA
interpolation order. Therefore, such results may appear locally inconsistent, especially on
second order meshes and mismatched mesh densities. (Usually pressure and traction will
appear smoother than gap opening or penetration.)
4. Only formats that have been activated by an OUTPUT or FORMAT statement are valid for
use on this entry.
5. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for further
information.
6. Multiple instances of this entry are allowed; if the instances conflict, the last instance
dominates.
Description
The CSTRAIN command can be used in the I/O Options or Subcase Information sections to
request ply strain output for elements referencing PCOMP or PCOMPG properties for all
subcases or individual subcases respectively.
Format
CSTRAIN (format_list,type,extras_list) = option
type <ALL, PRINC> ALL, blank: All strain results are output.
Default = ALL
PRINC: Only principal strain results are
output.
option <YES, ALL, NO, YES, ALL, blank: Results are output for all elements.
NONE, SID, PSID>
Comments
1. When the CSTRAIN command is not present, ply strain results are not output.
2. This output is not currently available for the frequency response or transient solution
sequences.
3. The STRAIN I/O option controls the output of strain results for the homogenized
composite material.
5. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
6. The SOUT field on the PCOMP or PCOMPG bulk data entry must be set to YES to activate
strain results calculation for the corresponding ply.
7. For plies defined on a PCOMPG bulk data entry, the results are grouped by GPLYID.
8. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
9. The mechanical and thermal contributions to strain may be requested in addition to the
total strain.
10. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The CSTRESS command can be used in the I/O Options or Subcase Information sections to
request ply stress and failure index output for elements referencing PCOMP or PCOMPG
properties for all subcases or individual subcases respectively.
Format
CSTRESS (format_list,type) = option
type <ALL, PRINC, FI> ALL, blank: All stress results are output.
Default = ALL
PRINC: Only principal stress results are
output.
Option <YES, ALL, NO, YES, ALL, Results are output for all
NONE, SID, PSID> blank: elements.
Default = YES
NO, NONE: Results are not output.
Comments
1. When the CSTRESS command is not present, ply stress and failure index results are not
output.
2. This output is not currently available for the frequency response or transient solution
sequences.
3. The STRESS I/O option controls the output of stress results for the homogenized
composite material.
4. Multiple formats are allowed on the same entry, these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands, for which the result is available. See Results Output for information
on which results are available in which formats.
5. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
6. The SOUT field on the PCOMP or PCOMPG bulk data entry must be set to YES to activate
stress results calculation for the corresponding ply. For Failure Indices to be calculated,
the FT and SB fields on PCOMP or PCOMPG bulk data and stress (or strain) allowables on
the referenced materials need to be defined.
7. For plies defined on a PCOMPG bulk data entry, the results are grouped by GPLYID.
8. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
9. Failure Index results are not available in the .pch and .op2 files.
10. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
Description
The DAMAGE command can be used in the I/O Options or Subcase Information sections to
request fatigue damage results output for all fatigue subcases or individual fatigue subcases
respectively.
Format
DAMAGE (format, type) = option
format <H3D, OPTI, H3D: Results are output in Hyper3D format (.h3d
blank> file).
Default = blank
OPTI: Results are output in OptiStruct results
format (.fat file).
type <SUB, LOAD, SUB: Only the total damage from the fatigue
EVENT, ALL> subcase is output.
Default = SUB
LOAD: Damage contribution from each static
subcase and total damage from the fatigue
subcases are output.
option <YES, ALL, NO, YES, ALL, Results are output for all elements.
NONE, SID> blank:
Default = ALL
NO, NONE: Results are not output.
Comments
1. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output by OptiStruct for
information on which results are available in which formats.
2. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
Description
The DENSITY command can be used in the I/O Options section to request density output for a
topology optimization.
Format
DENSITY (format_list,type) = option
Default = DES
DES, blank: Results are only output in the
design history simulations.
Default = YES
NO, NONE: Results are not output.
Comments
1. When the DENSITY command is not present, density results are output.
3. Outputting the density results in all simulations allows analysis results to be plotted on
the density iso-surface in HyperView.
4. The frequency of this output is controlled by the DESIGN keyword on an OUTPUT definition
or, if no OUTPUT definition exists with the DESIGN keyword, by the DENSRES I/O option.
5. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information
on which results are available in which formats.
6. Density results are reported as element strain energy in the .op2 file.
7. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
Description
The DESGLB command can be used in the I/O Options section, before the first subcase
statement, to select a constraint set that is not subcase dependent.
Format
DESGLB = integer
integer < SID > SID: Set identification of a DCONSTR or DCONADD bulk
data entry.
No default
Comments
1. The constrained response referenced by the DESGLB constraint selection must not be
subcase dependent.
2. Only one DESGLB entry can be defined in the I/O options section for the entire model.
Description
The DESHIS command can be used in the I/O Options section to control the creation of the
optimization history file .hgdata.
Format
DESHIS = option
option <YES, ALL, NO> YES, ALL, blank: .hgdata file is created.
Default = YES
NO: .hgdata is not created.
Comments
1. When the DESHIS command is not present, the .hgdata file is created.
Description
The DGLOBAL command can be used in the I/O Options section to activate the Global Search
Option (GSO).
Format
DGLOBAL = n
No default
Comments
1. This command must reference a DGLOBAL bulk data entry to run GSO.
Description
The DISPLACEMENT command can be used in the I/O Options or Subcase Information sections
to request displacement vector output for all subcases or individual subcases respectively.
Format
DISPLACEMENT (sorting,format,form,rotations,random,peakoutput,modal,complex
eigenvalue analysis) = option
sorting <SORT1, SORT2> This argument only applies to the PUNCH format (.pch
file) or the OUTPUT2 format (.op2 file) output for
Default = blank normal modes, frequency response, and transient
subcases. It will be ignored without warning if used
elsewhere.
format <HM, H3D, OPTI, HM: Results are output in HyperMesh results
PUNCH,OP2, format (.res file).
PATRAN, HG,
APATRAN, PLOT, H3D: Results are output in Hyper3D format
blank> (.h3d file).
random <PSDF, RMS> PSDF: Requests PSD and RMS results from
random response analysis to be output.
No default
Only valid for the H3D format. The
"RMS over Frequencies" output is at
the end of the Random results.
option <YES, ALL, NO, YES, ALL, blank: Displacement is output for all grids.
NONE, SID>
Comments
1. When DISPLACEMENT command is not present, displacement is output for all grids for all
subcases, except for frequency response subcases.
2. The form argument is only applicable for frequency response analysis. It is ignored for
other analysis types.
3. The forms BOTH and COMPLEX do not apply to the .frf output files.
4. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information
on which results are available in which formats.
5. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
6. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous version of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
8. For normal modes output, if there is USET U6 data the static residual displacement
vectors associated with the USET U6, DOF are also output to the PUNCH, H3D, and
OUTPUT2 files.
10. Results in binary format (.h3d or .op2) are always output in PHASE/MAG form, regardless
of the options specified in the FORM field. The corresponding post-processors
(HyperView/HyperGraph) can easily convert the PHASE/MAG format to the required
formats. Results in ASCII formats are output in the specified/requested FORM.
12. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The DMIGNAME command can be used in the I/O Options section to define the name given to
the reduced matrices written to an external data file.
Format
DMIGNAME = mtxname
Comments
4. See Direct Matrix Approach in the User's Guide for more detailed usage information.
Description
The DSA command can be used in the I/O Options section to request Design Sensitivity
Analysis results in a frequency response analysis.
Format
DSA (TYPE, PEAKOUT, PROPERTY) = SID
Examples
DSA(DISP,PROPERTY)=12
DSA(VELO,PEAKOUT)=45
DSA(ACCE,PEAKOUT,SCALE)=23
Default = DISP
PEAKOUT Default = blank If PEAKOUT is present inside the parentheses of the DSA
entry, the filtered frequencies from the PEAKOUT card
will be considered for DSA results.
Comments
1. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates. If this entry is defined above the first subcase then it is applied to all
subcases. If it is defined within a specific subcase then it is applied to that subcase only.
2. If the input deck doesn't contain any optimization data (apart from DESVAR’s), then a
MASS objective function is automatically created along with responses and constraints
corresponding to the DSA request. If the input deck contains a valid optimization setup,
then it's augmented with the DSA request.
3. In the H3D file, the "SCALE" value is only printed when the PROPERTY argument is not
present within the parentheses of the DSA entry. The sensitivities are pre-scaled when
the PROPERTY argument is present in the DSA entry, so the scaling factor is not required
in the H3D file.
4. OUTPUT, H3DSENS can be used to include (or exclude) user-defined responses in the DSA
output. The table below lists the sensitivities that are output for each option.
5. Design variables and their corresponding design properties must be defined in the input
deck if sensitivity output is requested through the DSA entry.
Description
The ECHO command can be used in the I/O Options section causing the output of the
interpreted forms of subcase information and bulk data entries to the .out file.
The ECHOON command can be used in the I/O Options, Subcase Information, or Bulk Data
sections causing the (verbatim) output of any subsequent I/O options, subcase information,
or bulk data entries to the .out file until an ECHOOFF command is encountered.
The ECHOOFF command can be used in the I/O Options, Subcase Information, or Bulk Data
sections suppressing the output of any subsequent I/O options, subcase information, or bulk
data entries to the .out file until and ECHOON command is encountered.
Format
ECHO = option1
ECHOON = option2
ECHOOFF
Example
ECHO = SORT(EIGR,EIGRL,ASET1,SPOINT,PARAM,SPC1,SPCADD,MPCADD,
DLOAD,RLOAD2,DAREA,DPHASE,FREQ1,TABLED1,TABDMP1)
Comments
2. The interpreted echo always includes SUBCASE cards (solution related), but not output
control cards.
3. The cards are organized within groups, for example, optimization cards appear after model
definition cards, and most cards are sorted by their numerical IDs.
4. The interpreted echo may contain some cards that are automatically generated or
converted during reading (for example, a CQUADR card shows as CQUAD4, or a CMASS1 card
shows as a CMASS3 when only scalar points are referenced). Unreferenced cards may not
show in the printout. PARAM,DOPTRM,OSDIAG will not be shown.
5. ECHO will be produced from internal representation of each card, thus it will be
equivalent, but not identical to the input:
For most of the optional fields, the blank from input will be printed in ECHO as default
value.
Fields which are not recognized or not used by OptiStruct are left blank.
Some values which would generate warning on the input will be printed after
adjustment.
Optional continuation cards may be printed even if they did not appear in the input.
DMIG cards are usually very large and are not shown in the interpreted echo. Adding the
card:
OSDIAG,167,1
anywhere in the control section will force full printout of DMIG cards if the interpreted
echo is requested.
7. {cardname} contains the list of all cards which are to be included in the interpreted echo
(or excluded, if EXCEPT keyword is present). This list may contain ELEM, MAT, or PROP
keywords, which is equivalent to listing all valid element, material, or property names,
respectively.
8. Multiple ECHO cards are allowed; all parameters of these cards are accumulated in the
order in which they are input. EXCEPT may appear anywhere (for example, before or after
{cardname} list) and may be repeated on multiple cards.
9. ECHOON / ECHOOFF cards may appear in any section of the input deck.
10. All comment cards, empty cards, and characters after the $ character on any card will
not be printed in any ECHO format.
11. The .echo file generated when 'ECHO = PUNCH' is defined represents a copy of the input
deck in a form suitable to use for another solution which, when used with the same
Subcase Information and I/O Options entries, should generate identical results (round off
error may be noticeable if the original input deck uses large field format). However, in
some cases, the ECHO may require manual editing before being acceptable as input for
OptiStruct. In particular, some optimization cards may be printed with information already
modified internally, and they will be not correct. Also some cards with a negative ID may
be printed in ECHO; those cards are automatically generated internally to OptiStruct, and
should simply be deleted.
Description
The EDE command can be used in the I/O Options or Subcase Information sections to request
element energy loss per cycle and element energy loss per cycle density output for all
subcases or individual subcases respectively.
Format
EDE (format_list, type, dmig) = option
option <YES, ALL, NO, YES, ALL, Element damping energy and damping
NONE, SID> blank: energy density are output for all
elements.
Default = ALL
NO, NONE: Element damping energy and damping
energy density are not output.
Comments
1. When an EDE command is not present, element damping energy and damping energy
density is not output.
2. Initial thermal strain is included in the calculation of element energy loss per cycle and
element energy loss per cycle density.
3. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
5. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
7. There are three ways to calculate the Element Damping Energy in Frequency Response
Analysis. They are listed as follows:
Average
Amplitude
Peak
Where,
E = Elemental Energy
8. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The EIGVNAME command can be used in the I/O Options section to define the prefix to be
used for external eigenvalue data files (.eigv).
Format
EIGVNAME = prefix
Argument Description
prefix The prefix to be used for the saving and retrieval of external eigenvalue
data files.
Comments
1. When an EIGVNAME command is not present, the OUTFILE prefix definition is used. If
OUTFILE is not defined, the prefix of the input file is used.
4. The total length of information on this card is limited to 200 characters (including the card
name and spaces between arguments). This data can be on a single line or span multiple
continuation lines. See Guidelines for I/O Options and Subcase Information Entries for an
example showing how to enter long file names on multiple lines.
5. Prefixes specified on the EIGVNAME card can be arbitrary file prefixes with optional paths
appropriate to the operating system (Windows or UNIX). They may be enclosed in quotes
(double or single quotes can be used), and either forward slash (/) or back slash (\)
characters can be used to separate parts of the path name.
When the argument contains an absolute path of the file (if it starts with "/" on UNIX
or a drive letter, such as "D:", on Windows, for example), OptiStruct creates .eigv
files at the given location.
Description
The EKE command can be used in the I/O Options or Subcase Information sections to request
kinetic energy and kinetic energy density output for all subcases or individual subcases
respectively.
Format
EKE (format_list, type, dmig, peakoutput) = option
see Comment 7
PEAK: In frequency response analysis the
peak energy is output. This is the sum
of AVERAGE and AMPLITUDE.
option <YES, ALL, NO, YES, ALL, Element kinetic energy and kinetic
NONE, SID> blank: energy density are output for all
elements.
Default = ALL
NO, NONE: Element kinetic energy and kinetic
energy density are not output.
Comments
1. When an EKE command is not present, element kinetic energy and kinetic energy density
is not output.
2. Initial thermal strain is included in the calculation of kinetic energy and kinetic energy
density.
3. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information
on which results are available in which formats.
4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
5. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
7. There are three ways to calculate the Element Kinetic Energy in Frequency Response
Analysis. They are listed as follows:
Average
Amplitude
Peak
Where,
E = Element Energy
8. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The ENERGY command can be used in the I/O Options or Subcase Information sections to
request energy output for all geometric nonlinear analysis subcases or individual geometric
nonlinear analysis subcases respectively.
Format
ENERGY (format, type) = option
type
<ALL, ENERG, ALL: All energy results are output.
HOURG>
Default = ALL ENERG: All energy results without hourglass
energy are output.
option
<YES, ALL, NO, YES, ALL, Energy results are output for all
NONE, SID, blank: elements.
PSID>
Default = ALL NO, NONE: Energy results are not output.
Comments
1. ENERGY is only applicable for geometric nonlinear analysis subcases which are defined by
an ANALYSIS = NLGEOM, IMPDYN or EXPDYN subcase entry. It is ignored for all other
subcases.
2. Only formats that have been activated by an OUTPUT or FORMAT statement are valid for
use on this card.
3. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
Description
The ERP command can be used in the I/O Options or Subcase Information sections to request
equivalent radiated power output for all subcases or individual subcases, respectively.
Format
ERP (format_list, grid) = option
format <H3D, PUNCH, H3D: Results are output in Hyper3D format (.h3d
blank> file).
Default = blank
PUNCH: Results are output in Nastran punch results
format (.pch file).
option <YES, ALL, NO, YES, ALL, Equivalent radiated power is output for all
NONE> blank: panels.
Default = ALL
NO, NONE: Equivalent radiated power is not output.
Comments
1. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information
on which results are available in which formats.
3. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous version of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as
it does not allow different frequencies for different formats.
4. In addition to the ERP values, the following results are output to the .pch file: total ERP
over the loading frequencies, fraction of the total ERP at each loading frequency, and ERP
expressed in decibels ERBdB = 10 * log 10 (ERP) at each loading frequency.
5. The ERP is calculated as half the normal velocity squared of each grid multiplied by the
associated area of each grid on the panel. The parameters for the speed of sound
(ERPC), fluid density (ERPRHO), and radiation loss factor (ERPRLF) are used in the
calculation of ERP using the formula below.
6. The calculation of ERP in decibels (dB) is performed using the PARAM data RHOCP and
ERPREFDB in the equation below. ERPREFDB is the reference value in dB and RHOCP is the
scale factor:
7. At least one of the bulk data entries ERPPNL or PANELG (TYPE=ERP) needs to be
specified, if the ERP Output Request is used.
Description
The ESE command can be used in the I/O Options or Subcase Information sections to request
strain energy and strain energy density output for all subcases or individual subcases
respectively.
Format
ESE (format_list, type, dmig, peakoutput) = option
option <YES, ALL, NO, YES, ALL, Element strain energy and strain
NONE, SID> blank: energy density are output for all
elements.
Default = ALL
NO, NONE: Element strain energy and strain
energy density are not output.
Comments
1. When an ESE command is not present, element strain energy and strain energy density is
not output.
2. Initial thermal strain is included in the calculation of strain energy and strain energy
density.
3. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
5. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
7. There are three ways to calculate the Element Strain Energy in Frequency Response
Analysis. They are listed as follows:
Average
Amplitude
Peak
Where,
E = Elemental Energy
8. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The FLUX command can be used in the I/O Options or Subcase Information sections to
request temperature gradient and flux output for all steady-state heat transfer analysis
subcases, transient heat transfer analysis subcases or individual heat transfer analysis
subcases, respectively.
Format
FLUX (format_list) = option
format <PUNCH, OP2, PUNCH: Results are output in Nastran punch results
H3D, PLOT, format (.pch file).
blank>
OP2: Results are output in Nastran output2 format
Default = blank (.op2 file) (see comment 5).
option <YES, ALL, NO, YES, ALL, Flux results are output for all valid elements.
NONE, SID> blank:
Default = ALL
NO, NONE: Flux results are not output.
1. When the FLUX command is not present, flux results are not output.
2. Flux output is only available for steady-state heat transfer analysis and transient heat
transfer analysis solution sequences.
3. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
the results available and their respective formats.
4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
5. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The FORCE command can be used in the I/O Options or Subcase Information sections to
request element force output for all subcases or individual subcases respectively.
Format
FORCE (sorting, format_list, form, type, location, random, peakoutput, modal)
= option
type <TENSOR, DIRECT> TENSOR: Force results are output for all
solution sequences in which force
Default = TENSOR
results are supported. The Tensor
location <CENTER, CUBIC, CENTER: Element forces for shell and solid
SGAGE, CORNER, elements are output at the
BILIN> element center only.
Default = CENTER
CUBIC: Element forces for shell elements
are output at the element center
and grid points using the strain
gage approach with cubic bending
correction.
option <YES, ALL, NO, YES, ALL, Element force is output for all
NONE, SID> blank: valid elements.
Default = ALL
NO, NONE: Force is not output.
Comments
1. When neither FORCE nor ELFORCE commands are present, force is not output.
2. FORCE results are available for ELAS (CELAS1, CELAS2, CELAS3, CELAS4), ROD (CROD),
BAR (CBAR, CBEAM), BUSH (CBUSH), PLATE (CQUAD, CTRIA), GAP (CGAP), FASTENER
(CFAST)*, VISCOUS DAMPER (CVISC), SCALAR DAMPER (CDAMP1, CDAMP2, CDAMP3,
CDAMP4) and WELD (CWELD) elements.
* CFAST elements or their corresponding force results are available for post-processing in
HyperView only if the .fem file is loaded as a model (procedure used in comment 9).
3. The form argument is only applicable for frequency response analysis. It is ignored in
other instances.
4. The forms BOTH and COMPLEX do not apply to the .frf output files.
6. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
7. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
8. In general, HyperView does not recognize the SORT2 format for results from the .op2 file.
When results are output only in SORT2 format (<Result Keyword> (SORT2, OUTPUT2, …
.)), the results are written by OptiStruct into the .op2 file in SORT2 format, but when
the .op2 file is imported into HyperView, the results in SORT2 format are not recognized.
Therefore, the SORT1 option is recommended for results output in OUTPUT2 format and
SORT2 option is recommended for results output in PUNCH format.
9. Vector and Tensor plots of some element force results (weld, beam/bar and gap
elements) are available for post-processing in HyperView only if the .fem file is loaded in
the Load Model field and the results file is loaded in the Load Results field (below is an
example illustration of the HyperView Load model and results: panel).
Make sure that the Advanced option is selected from the Result Math Template: menu.
10. For shell elements force results are given as force/unit length.
11. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The FORMAT command can be used in the I/O Options section to indicate the format in which
results are to be output.
Format
FORMAT = option
option <ASCII, OS, OPTI, OPTI, OS, ASCII: OptiStruct ASCII results
HM, HYPER, BOTH, files are output.
H3D, FLX, NASTRAN,
PUNCH, PATRAN, HM, HYPER: The HyperMesh binary
APATRAN, O2, results file (.res file) is
OUT2, OP2, PLOT, output.
NONE>
BOTH: Same as defining both HM
Default = FLX and OPTI.
Comments
3. It is recommended to use the OUTPUT command instead of the FORMAT command since it is
more flexible and allows different frequencies of output for different formats during an
optimization.
4. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The FOS command can be used in the I/O Options or Subcase Information sections to request
fatigue factor of safety output for all fatigue subcases or individual fatigue subcases.
Format
format <H3D,OPTI, blank> H3D: Results are output in Hyper3D format (.h3d
file).
Default = blank
OPTI: Results are output in OptiStruct results format
(.fat file).
Comments
1. When a FOS command is not present, fatigue FOS results are not output.
2. Multiple formats are allowed on the same entry; these should separated by a comma. If
no format is specified, then this output control applies to all formats defined by OUTPUT
or FORMAT commands, for which the result is available. See Results Output by OptiStruct
for information on which results are available, in which formats.
3. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
Description
The GPFORCE command can be used in the I/O Options or Subcase Information sections to
request grid point force balance output for all subcases or individual subcases respectively.
Format
GPFORCE (format_list, elem, form, peakoutput, modal) = option
format <H3D, OPTI, H3D: Results are output in Hyper3D format (.h3d
PUNCH, OP2, file).
PLOT, blank>
OPTI: Results are output in OptiStruct results
Default = blank format (.gpf file).
elem <ELEM, NOELEM: GPFORCE results in the H3D output file will
(H3D only) NOELEM> not include element contributions. However,
the TOTAL value for each GRID includes the
Default = element contributions.
NOELEM
ELEM: GPFORCE results in the H3D output file
includes element contributions.
form <REAL, IMAG, REAL, IMAG: Provides rectangular format (real and
PHASE> imaginary) of complex output.
option <YES, ALL, NO, YES, ALL, Grid point force balance is output for all
NONE, SID> blank: elements.
Default = ALL
NO, NONE: Grid point force balance is not output.
Comments
1. When a GPFORCE command is not present, grid point force balance is not output.
4. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
5. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
6. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
7. GPFORCE in .op2 output can only be post-processed with the Free Body Diagram (FBD)
tools in HyperMesh.
8. GPFORCE in .h3d output is specifically added for the load transfer path analysis with
NVDirector. It is only available for linear static, frequency response, and acoustic
analyses.
9. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The GPKE command can be used in the I/O Options or Subcase Information sections to
request grid point kinetic energy output for normal modes subcases.
Format
format <PUNCH, blank> PUNCH: Results are output in Nastran punch results
format (.pch file).
Default = blank
option <YES, ALL, NO, YES, ALL, blank: GPKE results are output for all elements.
NONE, SID>
NO, NONE: GPKEs results are not output.
Default = ALL
Comments
1. Grid point kinetic energy is written in % of the total kinetic energy of all grids in the
structure. Therefore, GPKE results for each grid are the same regardless of the requested
option (ALL, YES, or SID).
2. Note that if the coupled mass matrix is used (PARAM,COUPMASS,YES), then the results at
each GRID are influenced by all GRID connected to that GRID. Using a diagonal mass
matrix formulation (PARAM,COUPMASS,NO) provides more meaningful results.
3. For large problems solved using EIGRA, run times increase if GPKE=ALL or a coupled mass
matrix (PARAM,COUPMASS,YES) is specified, as the entire eigenvector for each mode
must be calculated and stored.
Description
The GPSTRESS command can be used in the I/O Options or Subcase Information sections to
request grid point stresses output for all subcases or individual subcases respectively.
Format
GPSTRESS (format_list, averaging, type) = option
option <YES, ALL, NO, YES, ALL, blank: Grid point stresses output
NONE, SID> for all elements.
Comments
1. When a GPSTRESS command is not present, grid point stresses are not output.
3. Grid point stresses are not available for elements which form part of a topology design
space. When an analysis only run is performed, grid point stresses are available for all
solid elements. When PARAM, REANAL is used, grid point stress contributions are only
calculated for fully dense elements.
4. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
6. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
7. Grid point stresses are output for the entire model and for each individual PSOLID
component. This allows grid point stresses to be accurately obtained at the interface of
two components referencing different material definitions.
8. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The HISOUT command can be used in the I/O Options section to control the amount of data
printed to the .hgdata file.
Format
HISOUT = option
option <Integer <32> HISOUT value is equal to the sum of the desired options:
Example:
If you wanted design variables and all DRESP2 responses,
you would enter:
HISOUT = 9
Comments
Description
The HYBDAMP command can be used in the I/O Options section to request modal damping as a
function of the natural frequency of the model in Dynamic Analysis.
Format
HYBDAMP = option
option < SID > SID: Set identification of HYBDAMP in bulk data entry.
No default
Comments
1. HYBDAMP can be set at the global level in the I/O Options section. It can exist only once
in the I/O Options section.
Description
The INCLUDE command can be used in the I/O Options, Subcase Information, or Bulk Data
sections to indicate that the contents of another file are to be inserted into the input file at
the exact location of the include command.
Format
INCLUDE option
option <filename> filename: the path to and the name of the file to be
included.
No default
Comments
1. INCLUDE commands may be placed at any location in the input file, but must include
information appropriate to that location.
2. Names specified on the INCLUDE card can be arbitrary file names with optional paths
appropriate to the operating system (Windows or UNIX). They may be enclosed in quotes
(double or single quotes can be used), and either forward slash (/) or back slash (\)
characters can be used to separate parts of the path name.
The following rules are used to locate a file referenced on the INCLUDE card:
When the argument contains the absolute path of the file (if it starts with "/" on UNIX
or a drive letter, such as "D:", on Windows, for example), the file at the given location
is used.
When only the file prefix is given (without the path), the file has to be located in the
same directory as the file containing the INCLUDE command.
Description
The LIFE command can be used in the I/O Options or Subcase Information sections to
request output of fatigue life results for all fatigue subcases or individual fatigue subcases
respectively.
Format
LIFE (format_list) = option
format <H3D, OPTI, blank> H3D: Results are output in Hyper3D format (.h3d
file).
Default = blank
OPTI: Results are output in OptiStruct results
format (.fat file).
option <YES, ALL, NO, YES, ALL, Results are output for all elements.
NONE, SID> blank:
Default = ALL
NO, NONE: Results are not output.
Comments
1. When a LIFE command is not present, fatigue life results are not output.
2. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output by OptiStruct for
information on which results are available in which formats.
3. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
Description
The LOADLIB entry can be used in the I/O Options section to define the external libraries and
external files to be loaded into OptiStruct. External functions can be implemented within
dynamic libraries (.dll) under Windows, shared libraries (.so) under Linux, by using
HyperMath (.hml) on Windows and Linux, and external files by using Microsoft Excel (.xls or
.xlsx) on Windows.
Format
LOADLIB = type, group, path
path <Path including file The path to the external shared or dynamic
name and extension> library to be loaded.
No default
Comments
1. Absolute paths (those starting with a drive letter or a slash) will be used as they are
defined on the LOADLIB card. Relative library or file paths will be appended to the path
corresponding to the input deck's location.
2. The total length of information on this card is limited to 200 characters (including the card
name and spaces between arguments). This data can be on a single line or span multiple
continuation lines. See Guidelines for I/O Options and Subcase Information Entries for an
example showing how to enter long file names on multiple lines.
Description
The MBFORCE command can be used in the I/O Options section to request force output for a
set of joints and/or force elements from multi-body dynamics subcases.
Format
MBFORCE = option
option <YES, ALL, NO, YES, ALL, blank: Force is output for all joints and
NONE, SID> force elements.
Comments
1. When MBFORCE is not present, force results for joints and force elements are not output.
2. The force results for selected joints and force elements are output to the .mrf file.
Description
The MECHCHECK command can be used in the I/O options section to perform a massless
mechanism check on the model.
Format
MECHCHECK
Comments
1. Running the normal mode analysis by adding MECHCHECK helps detect the massless
mechanism where the massless mechanism shows up as rigid body modes.
2. A massless mechanism occurs due to degrees of freedom that do not possess both
stiffness and mass. To find such degrees of freedom, a small amount of mass is added to
the mass matrix so that the massless mechanism shows up as a rigid body mode (the
stiffness matrix K is still zero but the mass matrix M becomes non-zero) in normal modes
analysis. This is the reason why you have to set the lower bound on the EIGRL bulk data
entry to blank or zero when MECHCHECK is used.
3. The analysis results with this card cannot be used since the model is changed internally.
It can only be used to find the massless mechanism. The message “RESULTS FROM THIS
SOLVER RUN ARE INACCURATE AS IT IS IN MECHCHECK MODE” is also displayed in the .out
file when MECHCHECK is included in the I/O Options section of the solver deck.
4. MECHCHECK results (in the .out file) include a list of rigid body modes in the following
format:
ANALYSIS RESULTS:
------------------
ITERATION #
Rigid Modes in Eigenvalue Loadcase: #
-----------------------------------------------------
Mode Grid No. Type x-comp y-comp z-comp
-----------------------------------------------------
1 ## Tran ## ### ###
2 ## Rotn ## ### ###
… …. … etc … … …
-----------------------------------------------------
Description
The MODALDE command can be used above the first SUBCASE or within a SUBCASE definition
to request modal damping energy (the energy loss per cycle) output for all subcases or
individual subcases respectively. Note that this modal damping energy only includes the
energy contribution from viscous dampers. Structural damping and modal damping are not
included.
Format
MODALDE(format_list,THRESH=thresh,RTHRESH=rthresh,TOP=topn,MODES=mset,TYPE=typ
e) = option
format <H3D, blank> H3D: Results are output in Hyper3D format (.h3d
file).
Default = blank
blank: Results are output in all active formats for
which the result is available.
topn <Integer> Specifies that only the top N values should be output.
No default
mset <ALL, SID, ALL: Modal energy is output for all modes.
TOTAL>
SID: If a set ID is given, modal energy is output
Default = ALL
only for modes listed in that set.
option <YES, ALL, NO, YES, ALL, Modal energy is output for all modes.
NONE> blank:
Default = ALL
NO, NONE: Modal energy is not output.
Comments
1. When MODALDE command is not present, modal damping energy is not output.
2. Modal damping energy output is only available for modal frequency response analysis.
3. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
5. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
6. Note that this modal damping energy only includes the energy contribution from viscous
dampers. Structural damping and modal damping are not included.
Description
The MODALKE command can be used above the first SUBCASE or within a SUBCASE definition
to request modal kinetic energy output for all subcases or individual subcases respectively.
Format
MODALKE(format_list,THRESH=thresh,RTHRESH=rthresh,TOP=topn,MODES=mset,TYPE=typ
e) = option
format <H3D, blank> H3D: Results are output in Hyper3D format (.h3d
file).
Default = blank
blank: Results are output in all active formats for
which the result is available.
topn <Integer> Specifies that only the top N values should be output.
No default
mset <ALL, SID, ALL: Modal energy is output for all modes.
TOTAL>
SID: If a set ID is given, modal energy is output
Default = ALL
only for modes listed in that set.
Comments
1. When MODALKE command is not present, modal kinetic energy is not output.
2. Modal kinetic energy output is only available for modal frequency response analysis.
3. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
5. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
Description
The MODALSE command can be used above the first SUBCASE or within a SUBCASE definition
to request modal strain energy output for all subcases or individual subcases respectively.
Format
MODALSE(format_list,THRESH=thresh,RTHRESH=rthresh,TOP=topn,MODES=mset,TYPE=typ
e) = option
format <H3D, blank> H3D: Results are output in Hyper3D format (.h3d
file).
Default = blank
blank: Results are output in all active formats for
which the result is available.
topn <Integer> Specifies that only the top N values should be output.
No default
mset <ALL, SID, ALL: Modal energy is output for all modes.
TOTAL>
SID: If a set ID is given, modal energy is output
Default = ALL
only for modes listed in that set.
Default = ALL
NO, NONE: Modal energy is not output.
Comments
1. When MODALSE command is not present, modal strain energy is not output.
2. Modal strain energy output is only available for modal frequency response analysis.
3. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
5. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous version of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
Description
The MODEL command can be used in the I/O Options section to request output of only a
subset of the model and related results for H3D and OUTPUT results files as well as for CMS
superelements.
Format
NONE: No elements.
gridset <SID, ALL, SID: SID of a SET. A set of grids to be added to the
NONE> subset associated with the preceding elset field.
rigidset <RIGID/ALL, RIGID/ All rigid elements and their associated GRID will be
NORIGID/NONE, ALL: output.
SID>
Default
(analysis run)
=RIGID/ALL
Default (CMS SE
NORIGID/ No rigid elements will be output.
creation) = NONE:
NORIGID/NONE
Comments
1. For CMS superelements output in h3d format, only the ASET DOF are output when the
MODEL data is not present. When the MODEL data is present, the .h3d file contains the
ASET DOF and what is specified on the MODEL data.
2. In addition to the results output, the MODEL data controls the portion of the model that is
written to the .op2 and .h3d files.
Description
The MPCFORCE command can be used in the I/O Options or Subcase Information sections to
request multi-point force of constraint vector is output for all subcases or individual subcases
respectively.
Format
MPCFORCE (sorting, format, form_list, peakoutput, modal) = option
sorting <SORT1, SORT2> This argument only applies to the PUNCH format (.pch file) or
the OUTPUT2 format (.op2 file) output for normal modes,
Default = blank frequency response, and transient subcases. It will be
ignored without warning if used elsewhere.
format <OPTI, PUNCH, OPTI: Results are output in OptiStruct results format
OP2, PLOT, (.mpcf file).
blank>
PUNCH: Results are output in Nastran punch results
Default = blank format (.pch file).
form <REAL, IMAG, REAL, Provides rectangular format (real and imaginary)
PHASE> IMAG: of complex output.
Default = REAL
PHASE: Provides polar format (phase and magnitude) of
complex output.
option <YES, ALL, NO, YES, ALL, Multi-point force of constraint vector is output
NONE, SID> blank: for all grids.
Default = ALL
NO, NONE: Multi-point force of constraint vector is not
output.
Comments
1. When an MPCFORCE command is not present, multi-point force of constraint vector is not
output.
2. Multiple formats area allowed on the same entry; these should be comma separated. If
no format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
4. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were use; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
5. In general, HyperView does not recognize the SORT2 format for results from the .op2 file.
When results are output only in SORT2 format (<Result Keyword> (SORT2, OUTPUT2, …
.)), the results are written by OptiStruct into the .op2 file in SORT2 format, but when
the .op2 file is imported into HyperView, the results in SORT2 format are not recognized.
Therefore, the SORT1 option is recommended for results output in OUTPUT2 format and
SORT2 option is recommended for results output in PUNCH format.
6. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The MSGLMT command can be used in the I/O Options section to limit the number of ERROR,
WARNING and INFORMATION messages output, or to elevate a WARNING or INFORMATION
message to an ERROR.
Format
MSGLMT, mode
Examples
MSGLMT (WARNING) = 1000
MSGLMT (101) = 50
See comments 1
and 2 for
mode
<STRICT, STRICT: All messages are printed according to
UNREF, BRIEF> MSGLMT.
Comments
1. By default, the limit for most individual ERROR and WARNING/INFORMATION messages is
10.
2. The default limit for the total number of ERROR messages is 10,000 and for the total
number of WARNING/INFORMATION messages is 1,000.
Note:
1. If the Message ID belongs to an
error, the specified error and multiple
occurrences of the same error will
not be printed in the output file.
However, this will not allow the
solver to continue after error
suppression. This can sometimes
generate an output file which states
that an error occurred without any
information regarding the nature of
the error, since it was suppressed.
2. Suppressed ERROR/WARNING
messages still count toward
respective limits and are reported in
the job summary.
5. Multiple instances of MSGLMT may occur. If any instances conflict, then the last instance
will be honored.
For Example:
MSGLMT, 1692, <Integer> or MSGLMT (1692) =<integer>, prints the first <integer>
number of duplicate GRID ID’s:
MSGLMT, 1692, OFF or MSGLMT (1692) =OFF, prints all duplicate GRID ID’s:
Description
The NLRESTART command can be used in the I/O Options section to indicate the current
nonlinear solution sequence is to be restarted from a specified nonlinear subcase.
Format
NLRESTART = n
Argument Description
Comments
2. Only one NLRESTART entry can be defined, and it must be above the first subcase.
Description
The OFREQUENCY command can be used in the I/O Options or Subcase Information sections to
request a set of frequencies for output requests for all subcases or individual subcases
respectively.
Format
OFREQUENCY = option
Default = ALL
SID: If a set ID is given, output is only for
frequencies listed in that set.
Comments
2. The SET definition referenced by the OFREQUENCY card must be a real value set.
3. The number of solutions selected will always be equal to the number of quantities in the
selected set. The closest values will be used.
Description
The OLOAD command can be used in the I/O Options or Subcase Information sections to
request the form of applied load vector output for all subcases or individual subcases
respectively.
Format
OLOAD (format_list,type) = option
option <NONE, NO, YES, ALL, YES, ALL, Load data is output for all
SID> blank: nodes.
Default = ALL
NO, NONE: Loads are not output.
Comments
2. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
3. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
4. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
5. The SPARSE output type is only available when the OPTI output format is used.
6. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The OMODES command can be used in the I/O Options or Subcase Information sections to
request a set of modes for output requests for all subcases or for individual subcases,
respectively. This command is applicable for normal modes and linear buckling solution
sequences only.
Format
OMODES = option
option <ALL, SID> ALL, blank: Output is calculated for all modes.
Default = ALL
SID: If a set ID is given, output is calculated for
only modes listed in that set.
Comments
2. The SET definition referenced by the OMODES card must be an integer value set.
3. This output control is not available for frequency response subcases; OFREQUENCY should
be used instead.
4. If both the OMODES and OFREQUENCY requests appear, the OMODES request takes
precedence.
Description
The OTIME command can be used in the I/O Options or Subcase Information sections to
request a set of times for output requests for transient analysis for all subcases or individual
subcases respectively.
Format
OTIME = option
option < ALL, SID > ALL, blank: Output is at all times.
Default = ALL
SID: If a set ID is given, output is only at times in
that set.
Comments
1. When an OTIME command is not present the output for all times will be computed.
2. This command is particularly useful for requesting a subset of the output (for example,
stresses at only peak times, and so on).
\
Description
The OUTFILE command is used in the I/O Options section to define the prefix for the results
files output.
Format
OUTFILE = option
option <file prefix> file prefix: The path to and file prefix used for
the results files output.
Default = passed
in from the
command line.
Comments
1. Prefixes specified on the OUTFILE card can be arbitrary file prefixes with optional paths
appropriate to the operating system (Windows or UNIX). They may be enclosed in quotes
(double or single quotes can be used), and either forward slash (/) or back slash (\)
characters can be used to separate parts of the path name.
When the argument contains an absolute path of the file (if it starts with "/" on UNIX
or a drive letter, such as "D:", on Windows, for example), output files are created at
the given location.
When only the file prefix is given (without the path), output files will be created in the
current directory, meaning the directory from which the solver has been executed, and
not in the directory where the input file is located.
When the argument contains a relative path (../filename or sub/filename, for
example), output is created in a directory relative to where the solver is executed and
NOT relative to the directory where the input file is located.
2. The total length of information on this card is limited to 200 characters (including the card
name and spaces between arguments). This data can be on a single line or span multiple
continuation lines. See Guidelines for I/O Options and Subcase Information Entries for an
example showing how to enter long file names on multiple lines.
Description
The OUTPUT command can be used in the I/O Options section to control the format of results
output and the creation of certain results files.
Format
OUTPUT, keyword, frequency, option1, option2
NONE: No output
Note that if there is no result OUTPUT defined, then default result output is both HM and
H3D. If any result OUTPUT commands exist, then there is no default OUTPUT type.
DMIGALL: recovery is
activated for all grids/
elements
DMIGSET: recovery is
activated for grids/elements
in the SET defined on the
corresponding output request
(default)
(Applicable to
optimization
runs only).
DMIGALL: recovery is
activated for all grids/
elements
DMIGSET: recovery is
activated for grids/elements
in the SET defined on the
corresponding output request
(default)
DMIGALL: recovery is
activated for all grids/
elements
DMIGSET: recovery is
activated for grids/elements
in the SET defined on the
corresponding output request
(default)
DMIGALL: recovery is
activated for all grids/
elements
DMIGSET: recovery is
activated for grids/elements
in the SET defined on the
corresponding output request
(default)
Optimization Outputs
Default
frequenc Affected
Keyword Description Options Details
y files
LOCAL: Grid
definitions are
output to the
.grid file,
referencing local
coordinate
systems as
defined by the
CP field on the
GRID definitions.
Default =
ADVFREE
3. Ignore
<IGNORE>-
OUT: Updated
design variable
values are output
to the .out file.
BOTH: Updated
design variable
values are output
to both the .out
file and the
.desvar file.
NONE: Updated
design variable
values are not
output.
BOTH: Updated
property
definitions and
non-design
properties are
output to both
the .out file and
the .prop file.
NONE: Updated
property
definitions are
not output.
Default
Keyword Description Affected files Options Details
frequenc
y
See comment
17.
See comment
3.
See comments
2 and 3.
See comments
2 and 3.
free-sizing NOSTRESS
sensitivity.
See comment
6.
center of
gravity of the
item.
Default
Keyword Description frequenc Affected files Options Details
y
Comments
1. Frequency does not apply for any of the keywords where a dash (-) is given as the
default frequency in the keywords table above.
3. HGFREQ, HGTRANS, and HGMBD will only use output requests where a Set ID is specified.
For example, if DISPLACEMENT = ALL or DISPLACEMENT(HG) = ALL is given, displacement
information will not be present in the presentation, whereas if DISPLACEMENT = 1 or
DISPLACEMENT(HG) = 1 is given, displacement information will be present in the
presentation for the constituent nodes of Set 1.
If NOSTRESS or blank: results are printed, but stress, strain, and force responses are
ignored.
If ALL or STRESS: results are printed, including stress, strain, and force responses.
The integer value given is equal to the sum of the desired options:
1: Design Variable.
For example: If you want Design Variables and all DRESP2 responses, you would use 9.
6. The DVGRID option creates shape variable definitions for displacement or eigenvector
results of linear static, normal modes, or liner buckling analyses. These shape variable
definitions can then be used in subsequent optimizations. This process facilitates the use
of "natural" shape functions.
7. For the keywords HM, H3D, HV, ASCII, OPTI, OS, NASTRAN, PUNCH, OP2, OUT2,
OUTPUT2, PATRAN and APATRAN, the information provided by the OUTPUT I/O option
entry takes precedence over information provided on the older FORMAT and RESULTS I/O
option entries.
8. OUTPUT entries are read sequentially; therefore, where multiple OUTPUT entries exist with
the same keyword, the last instance is used.
10. OUTPUT,DESIGN takes precedence over the information provided on the older DENSRES I/O
option entry. OUTPUT,DESIGN will write design results, at the frequency defined, to all
active output formats (HM, H3D, or OPTI), regardless of the frequency chosen for that
output format. By default, HM is the only active output format.
11. When CMSMETH is used, or when a full multi-body dynamics run is performed, the CMS
stress modes can be written to OP2 format. This only happens when OUTPUT,OP2 (or
FORMAT,OP2) is defined. One file for each is generated. Stresses are written for shells
and solids, while forces are written for bars/beams and welds. Each mode is written as a
static load case with ID equal to the mode index. This output is compatible with FEMFAT
by MAGNA.
12. The MODEL/NOMODEL option for OUTPUT, OP2 may be overridden by the PARAM, OGEOM
bulk data entry.
13. The FSTHICK keyword generates a file with the .fsthick extension. The file contains
bulk data entries for elements (CQUAD4, CQUAD8, CTRIA3, and CTRIA6) contained in free-
size design spaces. The element definitions have the optimized thickness defined as
nodal thicknesses (Ti) for each element.
For frequency response analyses, plots are generated for the real part, the imaginary part
and the magnitude of the participation factors. Magnitude plot is visible by default, while
real and imaginary plots are hidden by default.
15. The H3D output from optimization runs consists of a number of files. The BYSUB/BYITER
option allows switching between two modes of H3D output. There is a no default option
(BYSUB/BYITER) for analysis runs.
BYSUB (This is the default option for optimization runs) outputs one _des.h3d file for
the animation of the optimization history. The frequency of the optimization results in
this file is defined by OUTPUT, DESIGN (Default = ALL). In addition, an _si.h3d file for
each subcase i is written that contains the history of the analysis results for each
subcase. Frequency determines the analysis result output frequency. Optimization
results can be written to the subcase files using DENSITY, SHAPE, or THICKNESS output
requests.
(Using OUTPUT, H3D, or BYSUB for analysis runs (without optimization) will output the
same files as above (except for the _des.h3d file), however no design results or
analysis history will be available within the files).
(Using OUTPUT, H3D, or BYITER for analysis runs (without optimization) will output
only one .h3d file since there are no multiple iterations).
16. Results for interior points of external superelements will be output by default to HM, H3D,
PUNCH, and OP2 files.
17. If GPSTRESS output is requested in addition to OUTPUT, ADAMSMNF, then nodal stress
results for solid elements will be written to the .mnf file.
Bundles: This specifies the number of ply bundles to be generated per fiber orientation.
Method: Ply bundle thicknesses are determined based on the method defined.
The advanced algorithm is available for 2, 4 and 8 ply bundles. It takes into account the
thickness distribution when generating the ply bundles, which results in a more accurate
representation of the original free-sized thickness profile.
Ply bundle thickness can also be multiples of the manufacturable ply thickness.
Ignore: Elements may be ignored in a given ply orientation when their thickness is less
than 5% of the maximum thickness. This option is inactive by default.
19. H3DSENS, USER indicates that the user-defined responses should be included in the DSA
output. NOUSER indicates that user-defined responses should not be included. In both
cases, responses defined through the DSA output request are included in the DSA output.
Description
The PFGRID command can be used in the I/O Options section to request output of acoustic
grid participation factors for all frequency response subcases. The output will be in the .h3d
file.
Format
PFGRID (GRIDS=setg, GRIDF=setfl, FREQUENCY=setf, NULL=ipower, RPCUTOFF=rval,
RPDBACUT=rpdba, CONTOUR=YES/NO,PEAKOUT) = setdof/PEAKOUT
Examples
PFGRID(FREQUENCY=391)=12
PFGRID(PEAKOUT)=23
PFGRID(PEAKOUT)=PEAKOUT
setg <ALL, NONE, ALL: Output acoustic grid participation for all structural grid
SID> points at the fluid-structure interface.
Default = NONE NONE: Do not output acoustic grid participation for any
structural grid points.
setfl <ALL, NONE, ALL: Output acoustic grid participation for all fluid grid points
SID> at the fluid-structure interface.
Default = NONE NONE: Do not output acoustic grid participation for any fluid
grid points.
setf <ALL, SID> ALL: Participation factors are processed for all excitation
frequencies.
Default = ALL
SID: Participation factors are only processed for a set of
excitation frequencies. SID refers to the ID of a SET of
type FREQ.
rpdba <Non- RPDBACUT is the decibel pressure cutoff value for fluid
Negative responses, and is similar to RPCUTOFF. It will take precedence
REAL> over RPCUTOFF for fluid responses. A weighting is applied to
RPDBACUT values at the excitation frequency. The grid
Default = 0.0
participation will be calculated when the magnitude of the
response is about the cutoff value. See comment 4 for decibel
calculations and reference pressure settings.
CONTOUR (YES/NO) If CONTOUR is specified as YES, the area projected value for the
fluid grid participation is output. Otherwise, the output of fluid
Default = YES grid participation would be the actual complex value.
PEAKOUT If PEAKOUT is present as an option inside the parenthesis of the PFGRID data,
then the filtered frequencies from the PEAKOUT data will be considered for output
of grid participation.
setdof/ <SID/ Degrees of freedom for which the grid participation factors are
PEAKOUT PEAKOUT> to be processed. SID refers to the ID of a SET of type GRID.
If “PEAKOUT” is specified instead of SID, the output will be
considered at the filtered frequencies corresponding to the
degree of freedom in the PEAKOUT card in the bulk section.
Comments
2. Acoustic grid participation factors are available in a coupled frequency response analysis
(both in direct and modal frequency response).
Description
The PFMODE command can be used in the I/O Options section to request output of modal
participation factors for all modal frequency response subcases.
Format
PFMODE (type, FLUIDMP=fmp, STRUCTMP=smp, PANELMP=setp, FREQUENCY=setf,
FILTER=fratio, NULL=ipower, RPCUTOFF=rval, RPDBACUT=rpdba, MTYPE=otype,
CMSSET=seset, RTYPE=rtype, outfile, PEAKOUT) = setdof/PEAKOUT
Examples
PFMODE(FLUID,STRUCTMP=30,FREQUENCY=391,PANELMP=ALL)=393
PFMODE(STRUCTURE,H3D)=23
PFMODE(FLUID,H3D,PEAKOUT)=11
PFMODE(STRUCTURE,H3D,PEAKOUT)=PEAKOUT
PFMODE(FLUID,PUNCH)=31
setp <ALL, NONE> ALL: Output structural modal participation for each
panel specified in the PANEL data.
Default = NONE
NONE: Do not output panel modal participation.
setf <ALL, SID> ALL: Participation factors are processed for all
excitation frequencies.
Default = ALL
SID: Participation factors are only processed for a set
of excitation frequencies. SID refers to the ID of
a SET of type FREQ.
rpdba <Non-Negative RPDBACUT is the decibel pressure cutoff value for fluid
REAL> responses, and is similar to RPCUTOFF. It will take precedence
over RPCUTOFF for fluid responses. A weighting is applied to
Default = 0.0 RPDBACUT values at the excitation frequency. The modal
participation will be calculated when the magnitude of the
response is about the cutoff value. See comment 9 for decibel
calculations and reference pressure settings.
otype <ALL, SYSTEM, For SYSTEM, the output related to PFMODE will correspond to
CMS> the whole model. Component modal participation will not be
output by default. However, when using ALL or CMS, the
Default = component modal participation will be output. For the CMS
SYSTEM
option, there will not be system modal participation. Component
modal participation can also be calculated for internal grids in
the superelement.
seset <ALL, SID> Component modal participation of all the H3D superelements will
be output by default. However, you can specify a specific set
Default = ALL of superelement names for output.
rtype <DISP, VELO, The Structural modal participation will be output for
ACCE> Displacement, Velocity or Acceleration respectively based on
Default = DISP the specified option (DISP, VELO, ACCE).
outfile <PUNCH, H3D> Modal participation can be exported either into the H3D file or
PUNCH file. Because of the large volume of data, it is
Default = H3D
recommended to export the modal participation data into a H3D
file.
PEAKOUT If PEAKOUT is present inside the bracket of the PFMODE option, the filtered
frequencies from the PEAKOUT card will be considered for the output of modal
participation.
Comments
1. The output of both the PFMODE and PFPANEL must be either to an H3D file or to a PUNCH
file. Both PFPANEL and PFMODE must have the same output option.
2. The modal participation output is sorted in descending order by magnitude of the modal
participation in the PUNCH file output.
3. PFMODE(FLUID,..) and PFMODE(STRUCTURE,…) can coexist in the input data, but only
one PFMODE(FLUID) and one PFMODE(STRUCTURE) are allowed in a single SUBCASE.
7. The filter is applied to the magnitude of the modal participation factors. Only modal
participation factors that pass the filter are output.
9. The dB value is calculated using 20 * log10 (P/P0), where P0 is the reference pressure.
The reference pressure is dependent on the units specified on the UNITS input data. If
the units are SI, the value is set as 2.0E-5 Pa. If they are CGS, it is set as 2.0E-4 barye.
If they are MPa, it is set as 2.0E-11 MPa. If they are BG or EE, then it is set as 4.17E-7
lbf/ft 2. If no UNITS data is present, the default value is 2.0E-11 MPa.
10. Legacy format for the export of modal participation to H3D or PUNCH files: PFMODE (type,
OUTPUT=outfile)=setdof/PEAKOUT is also supported.
11. If you wish to output modal participation factors for interior points of a superelement (in a
CMS model), the SEINTPNT entry can be used in the subcase information section to
convert the interior points of interest to exterior points. After conversion, these points
can now be referenced by the <SID/PEAKOUT> option for the sedof/PEAKOUT argument.
Description
The PFPANEL command can be used in the I/O Options section to request output of acoustic
panel participation factors for all frequency response subcases.
Format
Examples
PFPANEL(PANEL=ALL,FREQUENCY=45)=12
PFPANEL(H3D, PEAKOUT)=56
PFPANEL(H3D, PEAKOUT)=PEAKOUT
PFPANEL(PUNCH)=32
setp <ALL, NONE> ALL: Output acoustic panel participation for all panels.
Default = NONE
NONE: Do not output acoustic panel participation.
setf <ALL, SID> ALL: Participation factors are processed for all excitation
frequencies.
Default = ALL
SID: Participation factors are only processed for a set of
excitation frequencies. SID refers to the ID of a SET
of type FREQ.
outfile <PUNCH, H3D> Panel participation can be exported either into a H3D file or a
PUNCH file. Because of the large volume of data, it is
Default = H3D recommended to export the panel participation data into a H3D
file.
PEAKOUT If PEAKOUT is present as an option inside the parentheses of the PFPANEL data,
then the filtered frequencies from the PEAKOUT data will be considered for output
of panel participation.
Comments
1. Output is to the H3D or PUNCH files only. The output of both PFMODE and PFPANEL must
be either to an H3D file or to a PUNCH file. Both PFPANEL and PFMODE must have the same
output option.
2. Acoustic panel participation factors are available in a coupled frequency response analysis
(both in direct and modal frequency response).
4. Legacy format for the export of acoustic panel participation to H3D or PUNCH files:
PFPANEL (OUTPUT=outfile)=setdof/PEAKOUT is also supported.
Description
The PFPATH command can be used in the I/O Options section for transfer path analysis for a
response at the connection points.
Format
PFPATH = SID
Comments
Description
The POWERFLOW command can be used in the I/O Options section to request output of the
power flow field.
Format
POWERFLOW (format,peakoutput) = option
format <H3D> H3D: Results are output in Hyper3D format (.h3d file).
Default = H3D
option <YES, ALL, NO, YES, ALL, Power flow field is output for all elements.
NONE, SID> blank:
Default = ALL
NO, NONE: Power flow field is not output.
Comments
2. The power flow field indicates the magnitude and direction of vibrational energy which
travels in dynamically loaded structures. It helps with identifying the energy transmission
paths as well as the vibration sources and energy sinks. Structural intensity, defined as
the power flow per unit area, is also available.
3. The references used in the calculation of the power flow field are listed in the References
section of the User’s Guide.
Description
Description
The PRETBOLT command can be used in the I/O Options or Subcase Information sections to
request output of pretension force/adjustment values in the pretension bolts for all
pretensioning and pretensioned subcases.
Format
PRETBOLT (format) = option
Example
PRETBOLT = NO
PRETBOLT (OPTI)
PRETBOLT
Comments
1. When a PRETBOLT command is not present, pretension force/adjustment values are not
output.
2. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
Description
The PROPERTY command can be used in the I/O Options section to request the output of the
property definitions used in the final iteration of an optimization.
Format
PROPERTY = option
option <FILE, OUT, FILE or blank: Updated property definitions are output
BOTH, NONE> to the .prop file.
Comments
1. When a PROPERTY command is not present the updated property definitions will not be
output.
RADSND - References RADSND Bulk Data to specify sound generation panels and microphone
field points
Description
The RADSND command can be used in the I/O Options or Subcase Information sections to
request radiated sound output for all subcases or individual subcases respectively.
Format
RADSND = option
No default
Comments
1. Multiple instances of this card are allowed. If the instances are conflicting, the last
instance will be considered.
Description
The RCROSS command can be used in the I/O Options section to request computation and
output of cross-power spectral density functions for random response analysis.
Format
RCROSS(format_list,form,type, randid=RANDPS_ID) = option
format <PUNCH, PUNCH: Results are output in Nastran punch results format
blank> (.pch file).
Default =
blank: Results are output in all active formats for which the
blank
result is available.
Comments
1. The RCROSS I/O option must be used in conjunction with the RANDOM subcase information
entry.
3. Multiple RCROSS bulk data entries must be defined when each RCROSS subcase
information entry references different randid.
For example:
rcross(PUNCH, PHASE, PSDF, randid=210020)=451
rcross(PUNCH, PHASE, PSDF, randid=210050)=452
rcross(PUNCH, PHASE, PSDF, randid=210070)=453
rcross(PUNCH, PHASE, PSDF, randid=210090)=454
4. randid=<RANDPS_ID> must be specified within the RCROSS I/O options entry when
multiple RANDOM subcase information entries are present.
Description
The REQUEST command can be used in the I/O Options or Subcase Information sections to
select a multi-body request definition to be used in a multi-body problem.
Format
REQUEST = option
Comments
2. This subcase information entry is only valid when it appears in a multi-body subcase.
3. If the SID referenced by the REQUEST subcase information entry matches with the SID
defined for an MBREQ bulk data entry, the information on this entry alone is selected.
However, if no MBREQ bulk data entry has the referenced SID defined, any of the multi-
body motion entries: MBREQE or MBREQM which have this SID will be selected.
4. If present above the first subcase, it is applied to each multi-body dynamics subcase
without a REQUEST entry.
Description
The RESPRINT command can be used in the I/O Options section to force all unretained
responses of a certain type to be printed to the output file, provided they are referenced
either as an objective or a constraint. This also applies to manufacturing constraints for
composites.
Format
RESPRINT = option
Comments
1. When a RESPRINT command is not present, only retained responses will be output.
For example:
RESPRINT = STRESS, DISP
will force all stress and displacement responses referenced as either an objective or
constraint to be output.
Description
The RESTART command can be used in the I/O Options section to indicate that the current
optimization is to be restarted from the final iteration of a previous optimization.
Format
RESTART = option
option <File prefix> File prefix: The prefix of the .sh file to be
used as the starting iteration
Default = prefix of .fem for the restart.
file
Comments
1. To restart an optimization, you will need information about the final iteration of a previous
optimization run. This information is contained in the .sh file.
2. The purpose of the restart functionality is for restarting with unconverged optimization
runs or optimization runs that were terminated before completion (due to a power outage,
and so on). Only limited changes are allowed to be made to the model data. Refer to
the User's Guide section Restarting OptiStruct.
4. Output files from a restart run are appended with the extension _rst#, where # is a 3
digit number indicating the starting iteration for the restart run. For example,
filename_rst030.out is the .out file created when restarting filename.fem from
iteration 30.
5. The total length of information on this card is limited to 200 characters (including the card
name and spaces between arguments). This data can be on a single line or span multiple
continuation lines. See Guidelines for I/O Options and Subcase Information Entries for an
example showing how to enter long file names on multiple lines.
Description
The RESULTS command can be used in the I/O Options or Subcase Information sections to
determine the frequency of output of analysis results for all subcases or for individual
subcases respectively.
Format
RESULTS = frequency
frequency <FIRST, LAST, FL, FIRST: Output analysis results for the first
ALL, NONE, N> iteration only.
Comments
1. When a RESULTS command is not present, analysis results are output for formats that are
activated by the FORMAT command for both the first and last iterations.
2. The information on this card pertains to all analysis output formats that are not
specifically described by an OUTPUT command.
Description
The SACCELERATION command can be used in the I/O Options or Subcase Information sections
to request the form and type of modal participation accelerations output for all subcases or
individual subcases respectively.
Format
SACCELERATION (sorting,format_list,form,peakoutput) = option
sorting <SORT1, SORT2> This argument only applies to the PUNCH format
(.pch file) or the OUTPUT2 format (.op2 file) output
Default = blank for normal modes, frequency response, and
transient subcases. It will be ignored without
warning if used elsewhere.
option <YES, ALL, NO, YES, ALL, blank: Results are output.
NONE>
Comments
1. When the SACCELERATION command is not present, modal participation accelerations are
not output.
2. The SACCELERATION command is only valid for modal frequency response and modal
transient solution sequences.
3. The OFREQUENCY and OTIME I/O Options may be used to control the amount of output.
4. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
6. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
7. In general, HyperView does not recognize the SORT2 format for results from the .op2 file.
When results are output only in SORT2 format (<Result Keyword> (SORT2, OUTPUT2, …
.)), the results are written by OptiStruct into the .op2 file in SORT2 format, but when
the .op2 file is imported into HyperView, the results in SORT2 format are not recognized.
Therefore, the SORT1 option is recommended for results output in OUTPUT2 format and
SORT2 option is recommended for results output in PUNCH format.
9. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The SCREEN command can be used in the I/O Options section to control the output of model,
analysis, and optimization information to the UNIX or DOS shell.
Format
SCREEN = option
option <OUT, LOG, OUT, blank: The .out file is echoed to the screen.
NONE>
LOG: A log of the optimization process is echoed
Default = NONE
to the screen.
Comments
2. If the option LOG is chosen, the value of the objective function and the maximum
constraint violation at every iteration, as well as indication of satisfied convergence
ratios, are echoed to the screen.
Description
The SDISPLACEMENT command can be used in the I/O Options or Subcase Information sections
to request the form and type of modal participation displacements output for all subcases or
individual subcases respectively.
Format
SDISPLACEMENT (sorting,format_list,form,peakoutput) = option
sorting <SORT1, SORT2> This argument only applies to the PUNCH format (.pch
file) or the OUTPUT2 format (.op2 file) output for normal
Default = blank modes, frequency response, and transient subcases. It
will be ignored without warning if used elsewhere.
form <REAL, IMAG, REAL, IMAG: Provides rectangular format (real and
PHASE> imaginary) of complex output.
Default = REAL
PHASE: Provides polar format (magnitude and
phase) of complex output. Phase
output is in degrees.
Comments
1. When the SDISPLACEMENT command is not present, modal participation displacements are
not output.
2. The SDISPLACEMENT command is only valid for modal frequency response and modal
transient solution sequences.
3. The OFREQUENCY and OTIME I/O options may be used to control the amount of output.
4. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
5. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
6. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous version of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
9. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The SENSITIVITY command can be used in the I/O Options section to request the output of
the responses and sensitivities for size and shape design variables to a Microsoft Excel
spreadsheet.
Format
SENSITIVITY = option
option <YES, NO, ALL, NONE, NO, NONE: The results and sensitivities are not
STRESS, NOSTRESS> output.
Comments
4. For more details on the output format, go to the #.slk file page in the output section of
the Reference Guide.
5. Additional sensitivity output requests for topology, free-sizing and gauge design variables
can be made through OUTPUT,H3DTOPOL and OUTPUT,H3DGAUGE (in H3D format), and
OUTPUT,ASCSENS (ASCII format).
Description
The SENSOUT command can be used in the I/O Options section to control the frequency of
output of responses and sensitivities for size and shape design variables to a Microsoft Excel
spreadsheet.
Format
SENSOUT = frequency
frequency <FIRST, LAST, FIRST: The results and sensitivities are output for the
FL, ALL, N> first iteration only.
Default = FL LAST: The results and sensitivities are output for the
final iteration only.
Comments
Description
The SHAPE command can be used in the I/O Options section to request altered shape output
for a shape optimization.
Format
SHAPE (format_list,type) = option
format <HM, H3D, blank> HM: Results are output in HyperMesh results
format (.res file).
Default = blank
H3D: Results are output in Hyper3D format
(.h3d file).
Default = DES
DES, Results are only output in the design
blank: history simulations.
Default = YES
NO, NONE: Results are not output.
Comments
1. When the SHAPE command is not present, shape results are output.
2. Shape results are only available for shape, topography, and free-shape optimizations.
4. The frequency of this output is controlled by the DESIGN keyword on an OUTPUT definition
or, if no OUTPUT definition exists with the DESIGN keyword, by the DENSRES I/O option.
5. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
6. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
Description
The SINTENS command can be used in the I/O Options section to request Sound Intensity
output for all frequency response subcases. The SINTENS command can be used in the I/O
Options or Subcase Information sections to request Sound Intensity output for all subcases or
individual subcases respectively.
Format
SINTENS(type) = option
type <PANEL, NOPANEL> PANEL, Sound Intensity is output for both panels
blank: and microphone locations.
Default = PANEL
Comments
1. When the SINTENS command is present, Sound Intensity is output for all RADSND panel
grids and all microphone grids for all frequency response subcases. (If type=NOPANEL is
specified, sound intensity results are output only for microphone locations).
2. Sound Intensity results (via SINTENS) are output to the .h3d file.
Description
The SPCFORCE command can be used in the I/O Options or Subcase Information sections to
request single-point force of constraint vector output for all subcases or individual subcases
respectively.
Format
SPCFORCE (sorting,format_list,form,type,peakoutput) = option
sorting <SORT1, SORT2> This argument only applies to the PUNCH format (.pch
file) or the OUTPUT2 format (.op2 file) output for
Default = blank normal modes, frequency response, and transient
subcases. It will be ignored without warning if used
elsewhere.
format <HM, H3D, OPTI, HM: Results are output in HyperMesh results
PUNCH, OP2, format (.res file).
PLOT, blank>
H3D: Results are output in Hyper3D format (.h3d
Default = blank file).
option <YES, ALL, NO, YES, ALL, Single-point force of constraint is output
NONE, SID> blank: for all nodes.
Default = ALL
NO, NONE: Single-point force of constraint is not
output.
Comments
1. When an SPCFORCE command is not present, single-point force of constraint vector is not
output.
2. Single-point force of constraint values are highly dependent on mesh density and type of
elements used.
3. For modal frequency analysis, residual forces are zero only in modal space. Therefore,
the single-point force of constraint vector may not be accurate unless all modes are used
in the modal solution. When all possible modes in the model space are used, the modal
frequency analysis solution should match the direct frequency analysis solution.
4. When single-point force of constraint is calculated, the reaction force summary, the load
summary, and the strain energy residuals for the affected subcases are written to the
.out file.
5. The form argument is only applicable for frequency response analysis. It is ignored in
other instances.
6. The forms BOTH and COMPLEX do not apply to the .frf output files.
7. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
8. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
9. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
11. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The SPL command can be used in the I/O Options or Subcase Information sections to request
Sound Pressure output for all subcases or individual subcases respectively. SPL can only be
requested for frequency response subcases.
Format
SPL = option
Comments
1. When the SPL command is present, Sound Pressure is output for all microphone grids for
all frequency response subcases.
2. Sound Pressure results (via SPL) are output to the .h3d file.
Description
The SPOWER command can be used in the I/O Options or Subcase Information sections to
request Sound Power output for all subcases or individual subcases respectively. SPOWER can
only be requested for frequency response subcases.
Format
SPOWER(type) = option
type <PANEL, NOPANEL> PANEL, Sound Power is output for both panels
blank: and microphone locations.
Default = PANEL
option <ALL> ALL, Sound Power is output for all panel grids
blank: and all grids defined as microphone
Default = ALL locations on the RADSND bulk data. In
addition, the total Sound Power for each
Panel and all the microphone locations is
output.
Note:
Comments
1. When the SPOWER command is present, Sound Power is output for all RADSND panel grids
and all microphone grids for all frequency response subcases. (If type=NOPANEL is
specified, sound power results are output only for microphone locations).
2. Sound power is always output for microphone locations regardless of the specified type
(PANEL/NOPANEL).
3. Sound Power results (via SPOWER) are output to the .h3d file.
Description
The STRAIN command can be used in the I/O Options or Subcase Information sections to
request strain output for all subcases or individual subcases respectively.
Format
STRAIN
(sorting,format_list,form,type,location,extras_list,random,peakoutput,modal) =
option
sorting <SORT1, SORT2> This argument only applies to the PUNCH format (.pch
file) or the OUTPUT2 format (.op2 file) output for
Default = blank normal modes, frequency response, and transient
subcases. It will be ignored without warning if used
elsewhere.
type <VON, PRINC, VON: Only von Mises strain results are
MAXS, SHEAR, output.
ALL, TENSOR,
DIRECT> PRINC, MAXS, von Mises and maximum principal
SHEAR: strain results are output.
Default = ALL
random <PSDF, RMS> PSDF: Requests PSD and RMS results from
random response analysis to be
No default output for solid and shell elements
only (See comment 13).
option <YES, ALL, NO, YES, ALL, blank: Results are output for all elements.
NONE, SID,
PSID>
NO, NONE: Results are not output.
Default = ALL
Comments
2. HyperView can internally derive strain results from the strain tensor when the options
TENSOR or ALL are used. If the option DIRECT is used, it will display the strain results
that were directly computed.
3. The von Mises and Principal stresses are not available for frequency response analysis.
4. For elements that reference PCOMP and PCOMPG properties, the STRAIN I/O option controls
only strain results for the homogenized composite. The CSTRAIN I/O option must be used
to obtain ply strain results.
5. The form argument is only applicable for frequency response analysis. It is ignored in
other instances.
6. The forms BOTH and COMPLEX do not apply to the .frf output files.
7. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
8. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
9. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
10. The mechanical and thermal contributions to strain may be requested in addition to the
total strain.
13. PSDF and RMS von Mises strain results based on the Segalman Method are also written to
the .h3d file for Random Response Analysis (only available in the H3D format).
15. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The STRESS command can be used in the I/O Options or Subcase Information sections to
request stress output for all subcases or individual subcases respectively.
Format
STRESS (sorting,format_list,form,type,location,random,peakoutput,modal) =
option
type <VON, PRINC, MAXS, SHEAR, VON: Only von Mises stress
ALL, TENSOR, DIRECT> results are output (HM,
OPTI, and H3D only).
Default = ALL, TENSOR
PRINC, MAXS, von Mises and maximum
SHEAR: principal stress results are
output (HM and H3D only).
option <YES, ALL, NO, NONE, SID, YES, ALL, blank: Stress results are output
PSID> for all elements.
Comments
1. When a STRESS command is not present, stress results are output for all elements for all
linear static analysis, nonlinear quasi-static gap analysis, and inertia relief analysis
subcases.
2. HyperView can internally derive STRESS results from the stress tensor when the options
TENSOR or ALL are used. If the option DIRECT is used, it will display the stress result that
were directly computed.
3. For elements that reference PCOMP or PCOMPG properties, the STRESS I/O option controls
only stress results for the homogenized composite. The CSTRESS I/O option must be used
to obtain ply stress and failure index results.
4. The Von Mises and Principal stresses are not available for frequency response analyses.
5. The form argument is only applicable for frequency response analysis. It is ignored in
other instances.
6. The forms BOTH and COMPLEX do not apply to the .frf output files.
7. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
8. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
9. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
10. For normal modes analysis output, if there is USET U6 data, the stresses for each residual
displacement vector associated with the USET U6 DOF are also output to the H3D, PUNCH,
and OUTPUT2 files.
11. For modal frequency response and transient analysis, the stress vectors associated with
the residual vectors are written to the .op2 and .pch files after the modal stress vectors
if the keyword MODAL is used.
12. In general, HyperView does not recognize the SORT2 format for results from the .op2 file.
When results are output only in SORT2 format (<Result Keyword> (SORT2, OUTPUT2, …
.)), the results are written by OptiStruct into the .op2 file in SORT2 format, but when
the .op2 file is imported into HyperView, the results in SORT2 format are not recognized.
Therefore, the SORT1 option is recommended for results output in OUTPUT2 format and
SORT2 option is recommended for results output in PUNCH format.
15. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The SUBTITLE command can be used in the I/O Options or Subcase Information sections to
define the subtitle for all subcases or for individual subcases respectively.
Format
SUBTITLE = name
Argument Description
No default
Comments
Description
The SVELOCITY command can be used in the I/O Options or Subcase Information sections to
request the form and type of modal participation velocities output for all subcases or individual
subcases respectively.
Format
SVELOCITY (sorting,format_list,form,peakoutput) = option
sorting <SORT1, SORT2> This argument only applies to the PUNCH format
(.pch file) or the OUTPUT2 format (.op2 file)
Default = blank output for normal modes, frequency response, and
transient subcases. It will be ignored without
warning if used elsewhere.
Comments
1. When the SVELOCITY command is not present, modal participation velocities are not
output.
2. The SVELOCITY command is only valid for modal frequency response and modal transient
solution sequences.
3. The OFREQUENCY and OTIME I/O Options may be used to control the amount of output.
4. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
6. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
7. In general, HyperView does not recognize the SORT2 format for results from the .op2 file.
When results are output only in SORT2 format (<Result Keyword> (SORT2, OUTPUT2, …
.)), the results are written by OptiStruct into the .op2 file in SORT2 format, but when
the .op2 file is imported into HyperView, the results in SORT2 format are not recognized.
Therefore, the SORT1 option is recommended for results output in OUTPUT2 format and
SORT2 option is recommended for results output in PUNCH format.
9. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The SYSSETTING command can be used in the I/O Options section to alter system settings.
Any setting defined here may be over-ridden by command line arguments (see Run Options for
OptiStruct). Most of these options can also be specified in one of the config files (see
OptiStruct Configuration File).
Format
SYSSETTING(setting=option_list,setting=option_list,…)
Examples
SYSSETTING(RAMDISK=100)
SYSSETTING(SCRFMODE=buffered,stripe)
SYSSETTING(SPSYNTAX=mixed,RAMDISK=100,SCRFMODE=buffered,stripe,OS_RAM=1234)
BARPROP <STRICT, MIXED> STRICT: The CBAR and CBEAM beam element
connections cannot reference the PBEAM beam
Default = STRICT
property entries, respectively.
BUFFSIZE BUFFSIZE = 16832 The maximum size in 8 byte words of the records of
data written to the .op2 file. Use -1 to turn off
buffering.
H3DVTAG <YES, NO> Appends the version of the H3D format used, onto
the .h3d file output by OptiStruct.
Default = NO
So the results file would then be
{filename}.h3d11 or {filename}.h3d12.
OS_RAM <RAM in Mbytes> Memory limit in Mb. The solver will attempt to run
at least the minimum core solution regardless of
Default = 1Gbyte the memory limit. See Memory Limititations in the
User’s Guide for details.
PLOTELID <UNIQUE, ALLOWFIX> Controls the numbering scheme of the PLOTEL ID.
SAVEFILE SAVEFILE = OUT SAVEFILE controls the behavior of the solver when
an output file with the same name already exists
when the program starts.
SPSYNTAX <STRICT, CHECK, Controls how strict the checks are in the reader for
MIXED> mixing GRIDs and SPOINTs.
SYNTAX <ALLOWINT, STRICT> Controls how strict the syntax checker in the
reader is.
Default = ALLOWINT
ALLOWINT is the default setting for OptiStruct, and
converts integer values to real values whenever
real values are expected. In those instances,
where the form of the input (Integer or Real)
indicates the nature of the input (for example,
when reading vector entries (X,Y,Z) with alternate
form (GID, , )), a negative integer value in the first
field, or a non-blank value in the second or third
field indicates the (X,Y,Z) format and all fields are
Defaults = quiet and verbose More output including old and new
strict values.
USERAM <RAM in Mbytes> Memory limit in Mb. The solver will use more than
the minimum memory required up to this limit, but
only if it improves the speed of the solution. See
Memory Limitations in the User’s Guide for details.
Comments
1. The number of fields in this card is not limited to 10, but it is limited by the current line
length (default 80).
2. Continuation lines are not allowed, multiple SYSSETTING cards are allowed.
3. The settings CPU and NPROC are interchangeable, and can also be specified on the
command line.
4. Each option except SCRFMODE must have exactly one argument. SCRFMODE arguments
should be comma separated.
d) STRIPE requires multiple TMPDIR cards and has effect only for out-of-core or minimum-
core solutions.
e) Most modern operating systems (Linux in particular) use excess available RAM for the
buffering of disk i/o. The SCRFMODE command will have effect only for jobs which
exceed the capabilities of this buffer.
f) When AMSES is used on Windows, BASIC mode is enforced during AMSES calculations.
g) The –scrfmode option can be specified on the command line (see Run Options for
OptiStruct) – this overrides any information specified in the input file.
8. The SAVEFILE option tries to preserve only files in the start directory, that is, this option
has no effect when the input file is specified with a path, or the OUTFILE option defines a
different location for all output files. Unless SAVEFILE,NONE is specified, standard .out
and .stat files are always renumbered, even if they are created in different folder. All
files are renumbered at program start – .out file is preserved first, and then the same
NNN is used for all files found in the current folder. Only files with default names are
preserved (that is those starting with the same root as outfile). Note that this option
may sometimes cause the solver to fail if it renames the file which is intended for the
input.
9. Multiple SAVEFILE cards overwrite each other (the last one is in effect). Multiple
SAVEFILE,ext cards can be used (up to 5 extensions can be defined), but using of any of
the standard options (NONE/ALL/OUT) empties the list of previously defined extensions.
Description
The TCURVE command can be used in the I/O Options section to define the plot title for
XYPLOT output from a random response analysis.
Format
TCURVE = title
Argument Description
Comments
2. A TCURVE definition applies to all plots defined after TCURVE until another definition of
TCURVE occurs.
Example:
XTITLE = X-A
YTITLE = Y-A
XYPLOT (first plot definition)
YTITLE = Y-B
TCURVE = C-A
XYPLOT (second plot definition)
would assign X-A, Y-A and the default plot title to the first plot, then X-A, Y-B and C-A
to the second plot.
Description
The THERMAL command can be used in the I/O Options or Subcase Information sections to
request temperature output for all heat transfer analysis subcases or individual heat transfer
analysis subcases respectively.
Format
THERMAL (format_list) = option
option <YES, ALL, YES, ALL, Thermal results are output at all grid points
NO, NONE, blank: for which temperature results are available.
SID>
Comments
1. When the THERMAL command is not present, thermal results are not output.
3. The PUNCH output produces TEMP bulk data entries, and the SID on the entries will be the
subcase number (=1 if no SUBCASES are specified).
4. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
the results available and their respective formats.
5. Temperature output via the THERMAL output request is available for both linear steady
state heat transfer and linear transient heat transfer analyses.
6. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
7. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The THICKNESS command can be used in the I/O Options section to request thickness output
for elements referencing a PSHELL or PCOMP property in:
Size/Free-size optimization
Analysis runs
Topology optimization
Format
THICKNESS (format_list, comp) = option
option <YES, ALL, NO, NONE> YES, ALL, blank: Thickness results are output
Default = YES
NO, NONE: Thickness results are not output.
Comments
1. When the THICKNESS command is not present, thickness results are output. THICKNESS
results for analysis runs, however, are not output by default and will be output only if
the THICKNESS data entry is present in the solver deck.
2. Thickness results are available for analysis runs, size/free-size optimization, and topology
optimization only.
3. When thickness results are output to the .h3d file, percentage thickness change is also
output.
4. Outputting the density results in all simulations allows analysis results to be plotted on
the density iso-surface in HyperView.
5. The frequency of this output is controlled by the DESIGN keyword on an OUTPUT definition
or, if no OUTPUT definition exists with the DESIGN keyword, by the DENSRES I/O option.
6. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
7. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
Description
The THIN command can be used in the I/O Options or Subcase Information sections to
request thinning and thickness output for all geometric nonlinear analysis subcases or
individual geometric nonlinear analysis subcases respectively.
Format
THIN (format, type) = option
option <YES, ALL, NO, NONE, YES, ALL, blank: Thinning/thickness are output for
SID, PSID> all elements.
Comments
1. THIN is only applicable for geometric nonlinear analysis subcases which are defined by an
ANALYSIS = NLGEOM subcase entry.
2. Only formats that have been activated by an OUTPUT or FORMAT statement are valid for
use on this card.
3. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
Description
The TITLE command can be used in the I/O Options section to define the title for the
OptiStruct job.
Format
TITLE = name
Argument Description
No default
Comments
Description
The TMPDIR command is used in the I/O Options section to choose the directory in which the
scratch files are to be written.
Format
TMPDIR = <options> path
path <directory path> The path to the directory where scratch files are to be
written.
Default = ./
Examples
Local Drive
Network Drive
1. Map the network drive (drive on a remote machine) to a drive (Y:\) on your computer.
2. Use the path to your preferred scratch directory on the mapped network drive as the
“path” argument for TMPDIR.
Local Drive
TMPDIR = -FILESIZE=13 /Dir1/Dir2/.../DirN/Scratch
Comments
1. The total length of information on this card is limited to 200 characters (including the card
name and spaces between arguments). This data can be on a single line or span multiple
continuation lines. See Guidelines for I/O Options and Subcase Information Entries for an
example showing how to enter long file names on multiple lines.
2. Multiple TMPDIR cards are allowed (up to five entries). Scratch files will be allocated in all
directories depending on the options defined (see comments 3 through 8).
3. Before opening any scratch file during the solution process, the solver checks the
available free space on all TMPDIRs and allocates that file on the directory which has most
free space. This algorithm tends to spread disk usage between different directories, but
does not guarantee full usage of each TMPDIR area.
4. The main scratch file used during a linear solver process (that is solution of linear system
or eigen problem) can be split between multiple TMPDIRs (see SCRFMODE).
5. When TMPDIR is marked as SLOW, it is used only after other TMPDIRs are filled up.
Selecting directories for TMPDIR on disk drives shared across the network (that is on
different computers or on centralized file servers) is not recommended, and should be
avoided if possible. Some scratch files (especially for out-of-core and minimum-core
mode) are heavily used, and accessing them across the network will dramatically increase
wall clock time for the solution. The main purpose of the TMPDIR command is to avoid
this delay when work areas (home directories) are allocated on a central server, as is
customary at many large organizations. All scratch files are stored in the specified
directories. The scratch files are automatically removed at the end of the analysis unless
there is a system error or core dump (in which case, the scratch file may need to be
cleaned up manually).
6. See the SCRFMODE setting on the SYSSETTING I/O option for an additional way to use
multiple TMPDIR cards for large jobs.
7. The –tmpdir option can be specified on the command line (see Run Options for
OptiStruct); this overrides any information specified in the input file.
8. The filesize option is needed in rare cases when there is a file size limit imposed by
operating system. This limit is large enough for all practical problems in most cases. The
following cases are known to have a file size limit of 2GB:
Description
The TTERM command can be used in a geometric nonlinear subcase to define the termination
time.
Format
TTERM = value
Argument Description
Comments
1. TTERM is only allowed in geometric nonlinear subcases which are defined by an ANALYSIS
= NLGEOM, IMPDYN, or EXPDYN subcase entry.
Description
The UNITS command can be used in the I/O Options section to define a system of units for
the model.
Format
UNITS = system
MPA: Mega
Length: millimeter = mm
Mass: tonne = tonne
Time: second = s
Temperature: Kelvin = K
Pressure - MPa
Pressure = Ibf/ft 2
Comments
1. Only one instance of this card is supported. If multiple instances are defined, the last
occurrence will be used.
Description
The VELOCITY command can be used in the I/O Options or Subcase Information sections to
request velocity vector output for all subcases or individual subcases respectively.
Format
VELOCITY(sorting,format,form,rotations,random,peakoutput) = option
sorting <SORT1, SORT2> This argument only applies to the PUNCH format
(.pch file) or the OUTPUT2 format (.op2 file)
Default = blank output for normal modes, frequency response, and
transient subcases. It will be ignored without
warning if used elsewhere.
option <YES, ALL, NO, YES, ALL, blank: Velocity is output for all nodes.
NONE, SID>
Comments
1. When the VELOCITY command is not present, velocity vector is not output.
2. Velocity output is available for frequency response and transient analysis solution
sequences.
3. The form argument is only applicable for frequency response analysis. It is ignored for
other analysis types.
4. The forms BOTH and COMPLEX do not apply to the .frf output files.
5. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
6. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.
7. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.
8. In general, HyperView does not recognize the SORT2 format for results from the .op2 file.
When results are output only in SORT2 format (<Result Keyword> (SORT2, OUTPUT2, …
.)), the results are written by OptiStruct into the .op2 file in SORT2 format, but when
the .op2 file is imported into HyperView, the results in SORT2 format are not recognized.
Therefore, the SORT1 option is recommended for results output in OUTPUT2 format and
SORT2 option is recommended for results output in PUNCH format.
9. Results in binary format (.h3d or .op2) are always output in PHASE/MAG form, regardless
of the options specified in the FORM field. The corresponding post-processors
(HyperView/HyperGraph) can easily convert the PHASE/MAG format to the required
formats. Results in ASCII formats are output in the specified/requested FORM.
11. format=OUTPUT2 can also be used to request results to be output in the Nastran output2
format (.op2 file).
Description
The XTITLE command can be used in the I/O Options section to define the x-axis label for
XYPUNCH or XYPLOT output from a random response analysis.
Format
XTITLE = title
Argument Description
Default = blank
Comments
2. An XTITLE definition applies to all plots defined after XTITLE until another definition of
XTITLE occurs.
Example:
XTITLE = X-A
YTITLE = Y-A
XYPLOT (first plot definition)
YTITLE = Y-B
TCURVE = C-A
XYPLOT (second plot definition)
would assign X-A, Y-A and the default plot title to the first plot, then X-A, Y-B, and C-A
to the second plot.
Description
The XYPEAK, XYPLOT, and XYPUNCH commands can be used in the I/O Options section to
request output from a random response analysis. The XYPUNCH command can also be used
with the RESPONSE plot-type to request .pch file output from a frequency response analysis.
Format
operation, curve-type, plot-type / entity ID(item code) list
ACCE, FORCE,
VELO: Requests output for velocity.
STRESS,
STRAIN>
ACCE: Requests output for acceleration.
No default
FORCE: Requests output for force.
plot-type <PSDF, AUTO, PSDF: Requests power spectral density function for
RESPONSE> random response analysis. (see comment 5)
No default
AUTO: Requests autocorrelation for random response
analysis.
entity ID (item List of grid or GRID: Each entry consists of a GRID or SPOINT ID
code) list element, followed by a component of motion (T1, T2, T3,
component R1, R2, or R3) in parentheses. In the components
pairs. of motion, T signifies translation and R signifies
rotation while the numbers indicate the
The list must translational direction or rotational axis.
come after a
slash "/". For frequency response analyses, the
Each entry in components of motion are T1RM, T2RM, T3RM,
the list is T1IP, T2IP, T3IP, R1RM, R2RM, R3RM, R1IP, R2IP,
comma and R3IP, where RM signifies Real or Magnitude
separated. and IP signifies Imaginary or Phase. The type of
the response depends on a preceding output
No default request.
Examples
Comments
1. Unlike other output requests, XYPEAK, XYPLOT, and XYPUNCH may be combined on a single
line (as shown in the example above).
2. If the XYPEAK, XYPLOT, or XYPUNCH commands are not supplied, then no random response
results will be output.
3. If the XYPEAK, XYPLOT, or XYPUNCH commands are supplied, but with an incomplete
definition, an error termination will occur.
5. Multiple RANDOM subcase information entries with non-unique ID’s are allowed in a single
model. Therefore, if the plot-type field is set to PSDF, then the RANDOM ID will be added
to the XYPUNCH headers in the corresponding result sections of the .pch file when
multiple RANDOM entries are present in the same deck. If only one RANDOM entry is
present, the RANDOM ID is not printed.
Description
The YTITLE command can be used in the I/O Options section to define the y-axis label for
XYPUNCH or XYPLOT output from a random response analysis.
Format
YTITLE = title
Argument Description
Default = blank
Comments
2. A YTITLE definition applies to all plots defined after YTITLE until another definition of
YTITLE occurs.
Example:
XTITLE = X-A
YTITLE = Y-A
XYPLOT (first plot definition)
YTITLE = Y-B
TCURVE = C-A
XYPLOT (second plot definition)
would assign X-A, Y-A and the default plot title to the first plot, then X-A, Y-B, and C-A
to the second plot.
Description
The A2GG command can be used in the Subcase Information section to select a direct input
fluid-structure coupling matrix.
Format
A2GG = name
Argument Description
name Name of a fluid-structure coupling matrix that is input in the bulk data
section using the DMIG card.
Comments
1. DMIG matrices will not be used unless selected in the Subcase Information section.
3. The selected fluid-structure coupling matrix is always added to the computed coupling
matrix.
4. The referenced DMIG entry must be a square matrix (field 4 must be 1), where GJ
corresponds to fluid points, CJ = 0, Gi corresponds to structural points, Ci corresponds to
DOF, and Ai corresponds to the area values.
5. Multiple instances of A2GG are not allowed, and will result in an error termination.
Description
The ANALYSIS command can be used in the I/O Options section to request that only a finite
element analysis be performed (optimization input is ignored). It may also be used in the I/O
Options or Subcase Information sections to identify the solution sequence for all subcases or
for individual subcases, respectively.
Format
ANALYSIS = option
option <ONLY, OPTSKIP, The first two options ONLY and OPTSKIP refer to the run
STATICS, NLSTAT, control functionality of the ANALYSIS command:
MODES, MCEIG,
BUCK, DFREQ, ONLY: Performs finite element analysis run only.
MFREQ, DTRAN, Optimization inputs are checked but
MTRAN, DFOUR, ignored.
MFOUR, HEAT,
NLHEAT, MBD, OPTSKIP:
Performs finite element analysis run only.
NLGEOM, IMPDYN,
Optimization inputs are ignored.
EXPDYN, FATIGUE>
Comments
4. When ANALYSIS=ONLY or ANALYSIS=OPTSKIP are used, all properties and grids referenced
by size and shape variables will be set at the values on the associated property and GRID
data.
Description
The B2GG command can be used in the Subcase Information section to select a direct input
viscous damping matrix.
Format
B2GG = name
Argument Description
name Name of a damping matrix that is input in the bulk data section using the
DMIG card.
Comments
2. This matrix is handled like the damper elements CDAMPi and CVISC.
3. Terms are added to the viscous damping matrix before any constraints are applied.
4. The matrix must be symmetric, that is field 4 on the referenced DMIG entry must contain
the integer 6.
5. When multiple instances of this card occur, the referenced DMIG entries are combined.
This behavior differs from that of Nastran, which only recognizes the last instance of this
card in the same situation.
Description
The CMETHOD command can be used in the Subcase Information section to select the method
for complex eigenvalue extraction.
Format
CMETHOD = option
option < SID > SID: Set identification of an EIGC bulk data entry.
No default
Comments
3. If present above the first subcase, it is applied to all complex eigenvalue subcases.
Description
The CMSMETH command can be used in the Subcase Information section to request that only a
component mode synthesis solution be performed and to select a component mode synthesis
method definition to be used.
Format
CMSMETH = option
No default
Comments
1. All subcases must have the same MPC reference; in which case it runs the component
mode synthesis (flexible-body preparation) solution sequence using the CMSMETH reference
and the common MPC reference.
Description
The CNTNLSUB command can be used in the Subcase Information section to continue a
nonlinear solution from a preceding nonlinear subcase, and thus create complex loading
sequences.
Format
CNTNLSUB = option
option <Yes, No, Yes: This nonlinear subcase continues the nonlinear
SID> solution from the nonlinear subcase immediately
preceding.
Default = Yes
"Preceding" refers to the sequence of subcases
in the deck, not the subcase numbering. If
CNTNLSUB,YES is used within a subcase, then
the preceding subcase must be nonlinear
subcase of the same type. If CNTNLSUB,YES is
used above the first subcase, then all the
consecutive nonlinear subcases of the same
type will continue each other (however, other
types of subcases interspersed between
nonlinear ones will “break” the continuation
sequence).
Nonlinear subcases may only be continued from other nonlinear subcases of the same
analysis type. that is, geometric linear subcases (ANALYSIS=NLSTAT) may only be
continued from other geometric linear subcases, and geometric nonlinear subcases
(ANALYSIS=NLGEOM, IMPDYN or EXPDYN) may only be continued from other geometric
nonlinear subcases.
3. If CNTNLSUB = option is present above the first subcase, it is applied to all nonlinear
subcases. (CNTNLSUB = SID is only allowed within a subcase).
Description
The DEFORM command can be used in the Subcase Information section to select an element
deformation set.
Format
DEFORM = option
option < SID > SID: Set identification of a DEFORM bulk data entry.
Comments
2. If present above the first subcase, it is applied to all linear static, linear buckling, and
nonlinear quasi-static (Gap/Contact) subcases.
Description
The DESOBJ command is used in the Subcase Information section to select a single response
definition as the objective function of an optimization, or to select system response definitions
when the objective function is the least squares sum of these definitions. The DESOBJ
command also indicates if this response is to be minimized or maximized.
Format
DESOBJ (type) = integer, PROB
2. For global DRESP1 responses (responses which are not subcase dependent) or DRESP2 or
DRESP3 responses containing either DRESP1L/DRESP2L data or global DRESP1 responses,
the DESOBJ data must be above the first SUBCASE statement.
3. If the DESOBJ data references responses that are subcase specific, then the DESOBJ
statement must be within the appropriate subcase definition and the subcase must be of
the appropriate type.
4. If the DSYSID entry is referenced by a DESOBJ subcase entry, a least squares objective
function is used in the optimization. The objective function is the sum of the squared,
weighted, normalized differences between the target responses and those calculated by
the finite element analysis.
5. DSYSID entries must have unique identification numbers with respect to DRESP1, DRESP2,
and DRESP3 entries.
6. DRESP1, DRESP2, and DRESP3 entries referenced by the DSYSID entry can define only a
single response per subcase when the DESOBJ formulation is used.
7. Time dependent responses should not be referenced by the DESOBJ entry. The minmax
formulation should be used for optimization problems that have time-dependent responses
as the objective functions. The minmax formulation can be selected using the MINMAX or
MAXMIN subcase information entry.
8. The MAXP, MINP, and PROB options can be input during a Reliability-based Design
Optimization run. MINP and MAXP are not supported if random design variables or random
parameters are not defined in the model.
Description
The DESSUB command can be used in the Subcase Information section, within a subcase
definition, to select a constraint set that is subcase dependent.
Format
DESSUB = integer
Comments
1. The constrained response referenced by the DESSUB constraint selection must be subcase
dependent.
Description
The DESVAR command can be used in the Subcase Information section to select a set of
design variables for use in an optimization run.
Format
DESVAR = option
option <ALL, SID > ALL: All design variables in the input data, as defined
by DESVAR bulk data entries, are used in the
Default = ALL optimization.
Comments
1. Only one DESVAR command may appear in the Subcase Information section and should
appear before the first SUBCASE statement.
2. The DESVAR command is optional. If it is absent, all DESVAR bulk data entries will be
used.
3. DESVAR bulk data entries that are not selected by this command are frozen at their initial
values (that is same as setting XINIT=XLB=XUB) and all referenced properties will still be
governed by the DESVAR settings.
Description
The DLOAD command can be used in the Subcase Information section to select a dynamic load
to be applied in a transient or frequency response problem.
Format
DLOAD = option
option < SID > SID: Set identification of a DLOAD, TLOAD1, TLOAD2,
RLOAD1, RLOAD2, ACSRCE, or CAALOAD bulk data
No default entry.
Comments
Description
The EIGVRETRIEVE command can be used in the Subcase Information section to retrieve
eigenvalue and eigenvector results of a normal modes analysis from an external data file
(.eigv).
Format
EIGVRETRIEVE = integer1, integer2, integer3, ...
Comments
2. When multiple integer arguments are provided, eigenvalues are retrieved from multiple
external data files and combined.
3. If EIGVRETRIEVE is not present, eigenvalue and eigenvector results are not retrieved from
external data files and a normal modes analysis is performed for the modal frequency
response or modal transient response analysis subcase.
Description
The EIGVSAVE command can be used in the Subcase Information section to output eigenvalue
and eigenvector results of a normal modes analysis to an external data file (.eigv).
Format
EIGVSAVE = integer
Comments
2. If EIGVSAVE is not present, eigenvalue and eigenvector results do not get exported to an
external data file.
Description
The ESLTIME command can be used in the Subcase Information section to select particular
time steps for geometric nonlinear response ESLM optimization or Multi-body Dynamics ESLM
optimization.
Format
ESLTIME = option
Comments
1. Only one ESLTIME entry can be present for each subcase. It can only be used in
subcases that contain an ANALYSIS = NLGEOM, IMPDYN, EXPDYN or MBD entry.
2. If the SID referenced by the ESLTIME subcase information entry matches with the SID
defined for an ESLTADD bulk data entry, then the information on this entry alone is
selected. However, if an ESLTADD bulk data entry does not exists with the referenced
SID, then any ESLTIME bulk data entries that have this SID will be selected.
Description
The EXCLUDE command can be used in the Subcase Information section to select a set of
elements to be excluded from a linear buckling analysis.
Format
EXCLUDE = option
No default
Comments
1. The element set is defined using the SET bulk data entry.
2. This subcase information entry is only valid when it appears in a buckling subcase.
3. The excluded elements are only removed from the geometric stiffness matrix, resulting in
a buckling analysis with elastic boundary conditions. This means that the excluded
elements may still be showing movement in the buckling mode.
4. Extreme caution is advised when using the EXCLUDE command. In general, excluding any
region from buckling analysis can, and usually will, result in a higher, overestimated critical
load calculation, which then may produce false overconfidence in a structure’s load
bearing capacity. The excluded region will have no effect on the calculated critical load
only if the excluded modes are geometrically separated from, or orthogonal to, the actual
critical buckling mode.
Description
The FATDEF command can be used in the Subcase Information section to select a FATDEF bulk
data entry that will define the elements, and their associated fatigue properties, to be
considered for fatigue analysis.
Format
FATDEF = option
Option < SID > SID: Set identification of a FATDEF bulk data entry.
No default
Comments
1. FATDEF bulk data entries will not be used unless selected in the Subcase Information
section.
2. If present above the first subcase, it is applied to all fatigue analysis subcases.
Description
The FATPARM command can be used in the Subcase Information section to select a FATPARM
bulk data entry that will define the parameters to be used for a fatigue analysis.
Format
FATPARM = option
Option < SID > SID: Set identification of a FATPARM bulk data entry.
No default
Comments
1. FATPARM bulk data entries will not be used unless selected in the Subcase Information
section.
2. If present above the first subcase, it is applied to all fatigue analysis subcases.
Description
The FATSEQ command can be used in the Subcase Information section to indicate that a
subcase is a fatigue analysis subcase and to select a FATSEQ bulk data entry that will define
the loading sequence for the fatigue analysis.
Format
FATSEQ = option
Option < SID > SID: Set identification of a FATSEQ bulk data entry.
No default
Comments
Description
The FREQUENCY command can be used in the Subcase Information section to select the set of
forcing frequencies to be solved in a frequency response problem.
Format
FREQUENCY = option
option < SID > SID: Set identification of FREQ, FREQ1, FREQ2, FREQ3,
FREQ4, and FREQ5 bulk data entries.
No default
Comments
1. A frequency set selection is required for transient response by the Fourier transform
method when TSTEP (FOURIER) is used. The Fourier transform will be performed at the
frequencies specified.
2. All FREQi data with the same set identification number will be used.
3. If present above the first subcase, it is applied to each frequency response or transient
subcase without a FREQUENCY command.
Description
The GLOBSUB entry can be used in the Subcase Information section to select a subcase that
references the global structure for local-global analysis. A set of grid points in the local
structure that defines the transfer zone can also be specified.
Format
GLOBSUB, SUBID, SID
SUBID <integer > 0> Specifies the identification number of the subcase that
contains the global structure definition (via SUBMODEL).
SID <integer > 0> Specifies the set of grid points in the local structure
that defines the transfer zone. The displacements from
the global structure are interpolated and applied to this
set of grid points.
Comments
1. The transfer zone should contain only 3-dimensional elements in both the local and global
structures. Second order elements (for example, CHEXA20) are allowed. There is no
further restriction on element types elsewhere in the structure.
2. The transfer zone may represent single or multiple cuts (sections) through the structure.
Multiple cuts should be separated from each other, that is, they should not exist closer
than the element size of the global model.
3. The GLOBSUB entry should always reference the subcase ID of a global subcase that is
defined above its corresponding local subcase.
Description
The GROUNDCHECK command can be used in the Subcase Information section to perform a
grounding check analysis on the stiffness matrix to expose unintentional constraints by moving
the model rigidly.
Format
GROUNDCHECK(print,GRID=gid,THRESH=thresh) = option
print < PRINT, NOPRINT > PRINT: Write output to the .out file.
Default = PRINT
NOPRINT: Do not write output to the .out file.
grid < GID > Grid Point ID: Reference grid point for the
Default = geometric calculation of the rigid body motion.
center of the
structure.
Comments
3. Any MPC that will be violated due to rigid body modes is reported. An equivalent energy
magnitude is also calculated between MPC violation and the strain energy. The
equivalent energy from MPC violation is added to the strain energy when performing the
grounding check.
Description
The IC command may be used in the Subcase Information section to select initial conditions
for transient and explicit analysis.
Format
IC = option
Example
IC = 10
option < SID > SID: Set identification number of TEMP, TEMPD, TIC,
TICA bulk data entries.
No default
Comments
1. TIC and TICA entries will not be used (therefore, no initial conditions) unless selected in
the Subcase Information section.
Description
The INVEL command can be used in the Subcase Information section to select a multi-body
initial velocity set to be applied in a multi-body problem.
Format
INVEL = option
option < SID > SID: Set identification if INVELB or INVELJ bulk data
entries.
No default
Comments
2. This subcase information entry is only valid when it appears in a multi-body subcase.
Description
The K2GG command can be used in the Subcase Information section to select a direct input
stiffness matrix.
Format
K2GG = name
Argument Description
name Name of a stiffness matrix that is input in the bulk data section using
the DMIG card or name list, with or without factors.
Example
K2GG=KAAX
K2GG=1.25*KAAX,1.5*KBBX
Comments
1. DMIG matrices will not be used unless selected in the Subcase Information section.
3. The matrix must be symmetric, that is field 4 on the referenced DMIG entry must contain
the integer 6.
4. When multiple instances of this card occur, the referenced DMIG entries are combined.
This behavior differs from that of Nastran, which only recognizes the last instance of this
card in the same situation.
5. The entries in the name list are separated by comma or blank. With factors, each entry
consists of a factor followed by a star and a name. The factors are real numbers.
Description
The K2PP command can be used in the Subcase Information section to select a direct input
stiffness matrix, which is not included in normal modes.
Format
K2PP = name
Argument Description
name Name of a stiffness matrix that is input in the bulk data section using
the DMIG card.
Comments
1. DMIG matrices will not be used unless selected in the Subcase Information section.
3. K2PP matrices are used only in dynamic response problems. They are not used in normal
modes.
4. When multiple instances of this card occur, the referenced DMIG entries are combined.
This behavior differs from that of Nastran, which only recognizes the last instance of this
card in the same situation.
Description
The K42GG command can be used in the Subcase Information section to select a direct input
structural element damping matrix.
Format
K42GG = name
Argument Description
name Name of a damping matrix that is input in the bulk data section using the
DMIG card.
Comments
2. This matrix is handled like the contributions from the structural element damping
coefficients GE on MATi, PBUSH, and PELAS.
3. Terms are added to the damping matrix before any constraints are applied.
4. The matrix must be symmetric, that is field 4 on the referenced DMIG entry must contain
the integer 6.
5. When multiple instances of this card occur, the referenced DMIG entries are combined.
This behavior differs from that of Nastran, which only recognizes the last instance of this
card in the same situation.
Description
The LABEL command can be used in the Subcase Information section to provide a subcase
with a label.
Format
LABEL = name
Argument Description
Comments
Description
The LOAD command can be used in the Subcase Information section to select a static load set
to be applied in linear static solutions.
Format
LOAD = option
option < SID > SID: Set identification of a LOAD bulk data entry or,
if no LOAD bulk data entry exists with this SID,
No default the set identification of FORCE, FORCE1,
MOMENT, MOMENT1, PLOAD, PLOAD1, PLOAD2,
PLOAD4, GRAV, RFORCE, and SPCD, bulk data
entries.
Comments
2. A METHOD entry cannot be present in the same subcase definition as a LOAD entry.
3. If the SID referenced by the LOAD subcase information entry matches with the SID
defined for a LOAD bulk data entry, the information on this entry alone is selected.
However, if no LOAD bulk data entry has the referenced SID defined, any of the static
load entries: FORCE, FORCE1, MOMENT, MOMENT1, PLOAD, PLOAD1, PLOAD2, PLOAD4,
GRAV, RFORCE, and SPCD, which have this SID will be selected.
4. In versions of OptiStruct prior to 8.0, thermal loads were selected in the Subcase
Information section using the LOAD data selector. In version 8.0, the TEMPERATURE data
selector was added to perform this function. It is possible to revert to the old behavior
mode by setting the LOADTEMP option to SHAREID in the OptiStruct Configuration File.
Description
The M2GG command can be used in the Subcase Information section to select a direct input
mass matrix.
Format
M2GG = name
Argument Description
name Name of a mass matrix that is input in the bulk data section using the
DMIG card.
Comments
1. DMIG matrices will not be used unless selected in the Subcase Information section.
3. The matrix must be symmetric, that is field 4 on the referenced DMIG entry must contain
the integer 6.
4. By default, mass contribution of the external mass matrix (M2GG) is considered for the
generation of gravity and centrifugal loads.
5. When multiple instances of this card occur, the referenced DMIG entries are combined.
This behavior differs from that of Nastran, which only recognizes the last instance of this
card in the same situation.
Description
The MBSIM command can be used in the Subcase Information section to select a multi-body
simulation definition to be applied in a multi-body problem.
Format
MBSIM = option
option < SID > SID: Set identification of MBSEQ, MBSIM, or MBLIN bulk
data entries.
No default
Comments
2. This subcase information entry is only valid when it appears in a multi-body subcase.
3. MBSIM can be used to select only one bulk data entry. MBSEQ, MBSIM, and MBLIN must
have unique IDs.
Description
The METHOD command can be used in the Subcase Information section to select a method for
real eigenvalue extraction.
Format
METHOD (type) = option
type <STRUCTURE, The referenced EIGRL or EIGRA bulk data entry is applied
FLUID> to the structural (STRUCTURE) or fluid (FLUID) portion of
the model.
Default =
Structure
option < SID > SID: Set identification of an EIGRL or EIGRA bulk data
entry.
No default
Comments
1. Only one METHOD entry of each type can be defined for each subcase.
2. A METHOD entry cannot be present in the same subcase definition as a LOAD entry.
3. A METHOD entry is required for normal modes, linear buckling, modal frequency response,
and modal transient response solution sequences.
4. If present above the first subcase, it is used in all subsequent subcases which can accept
a METHOD entry. However, this does not apply to subcases which already contain their
own METHOD entry.
5. AMSES can be used for the fluid (FLUID) part of the model. METHOD(FLUID) can reference
an EIGRA bulk data entry.
Description
The MFLUID command can be used in the Subcase Information section to select the
parameters and damp elements and activate the calculation of virtual fluid mass.
Format
MFLUID = option
option < SID > SID: Set identification number of one or more MFLUID
bulk data entries.
No default
Comments
2. MFLUID may be requested for a normal modes, complex eigenvalue, frequency response,
or transient response analysis.
Description
The MINMAX or MAXMIN commands can be used in the Subcase Information section to select
normalized response or system identification definitions as the objective function for a
"Minmax" or "Maxmin" optimization.
Format
MINMAX = integer
MAXMIN = integer
Comments
1. Multiple MINMAX entries are allowed and multiple MAXMIN entries are allowed, but a MAXMIN
entry cannot appear in the same input file as a MINMAX entry.
2. The multiple MINMAX or MAXMIN entries define the same optimization problem.
3. Refer to the Optimization Problem page of the User's Guide for more information on
"Minmax" optimization.
4. If the DSYSID entry is referenced by a MINMAX or a MAXMIN subcase entry, the beta
method is applied in the optimization as follows:
Description
The MLOAD command can be used in the Subcase Information section to select a multi-body
load set to be applied in a multi-body problem.
Format
MLOAD = option
option < SID > SID: Set identification of GRAV, MBFRC, MBFRCC,
MBFRCE, MBMNT, MBMNTC, MBMNTE, MBSFRC,
No default MBSFRCC, MBSFRCE, MBSMNT, MBSMNTC,
MBSMNTE, and MLOAD bulk data entries.
Comments
2. This subcase information entry is only valid when it appears in a multi-body subcase.
3. If the SID referenced by the MLOAD subcase information entry matches with the SID
defined for an MLOAD bulk data entry, the information on this entry alone is selected.
However, if no MLOAD bulk data entry has the referenced SID defined, any of the multi-
body load entries: GRAV, MBFRC, MBFCC, MBFRCE, MBMNT, MBMNTC, MBMNTE, MBSFRC,
MBSFRCC, MBSFRCE, MBSMNT, MBSMNTC, or MBSMNTE which have this SID will be
selected.
Description
The MODESELECT command can be used in the I/O Options or the Subcase Information section
to select a subset of computed modes in modal dynamic analysis subcases.
Format
MODESELECT (type) = n
Alternate Format 1
MODESELECT (type, LMODES = lm)
Alternate Format 2
MODESELECT (type, LMODENM = lom, HMODENM = him)
Alternate Format 3
MODESELECT (type, LFREQ = lof, HFREQ = hif, UNCONSET = m)
(Integer > 0)
LMODENM lom Specifies the lower bound of the mode number range for
selecting modes (See comment 3).
(Integer > 0)
HMODENM him Specifies the upper bound of the mode number range for
selecting modes (See comment 3).
(Integer > lom
> 0)
LFREQ lof Specifies the lower bound of the frequency range for
selecting modes (See comment 4).
(Real > 0.0)
HFREQ hif Specifies the upper bound of the frequency range for
selecting modes (See comment 4).
(Real > lof >
0.0)
UNCONSET UNCONSET This flag indicates that the following fields specify a single
mode or a set of modes for unconditional inclusion or
exclusion.
Comments
1. The MODESELECT I/O Options entry is only supported in modal frequency response, modal
transient and complex eignenvalue analyses. It is not supported in Response Spectrum
Analysis.
2. Multiple MODESELECT entries are allowed in a model. MODESELECT entries can be specified
above the first subcase or within each subcase.
LMODENM HMODENM
Defaults specified 1.0E+7
1 specified
4. If LFREQ is specified without HFREQ, a default value of 1.0E+30 is assumed for HFREQ. If
HFREQ is specified without LFREQ, a default value of 0.0 is assumed for LFREQ.
LFREQ HFREQ
Defaults specified 1.0E+30
0.0 specified
5. When the MODESELECT Case Control command is used in conjunction with the parameter
LFREQ, the MODESELECT Case Control takes precedence.
6. If the use of MODESELECT results in all or none of the computed modes for use, you are
informed with a message.
a) an “S” next to the mode number, if the mode is eliminated by MODESELECT in one
subcase and PARAM, LFREQ or PARAM, HFREQ in another subcase, or
Description
The MODEWEIGHT command can be used in the Subcase Information section to define a
multiplier for computed eigenvalues that are to be used in the calculation of the "weighted
reciprocal eigenvalue" and "combined compliance index" optimization responses.
Format
MODEWEIGHT (mode) = weight
Argument Description
weight The multiplier to be used for the corresponding mode in the calculation of
"weighted reciprocal eigenvalue" or "combined compliance index."
Comments
2. Modes for which there is no MODEWEIGHT definition are not included in the calculation of
the "weighted reciprocal eigenvalue" and "combined compliance index" optimization
responses.
3. Refer to the Responses page of the User's Guide for more information on "weighted
reciprocal eigenvalue" and "combined compliance index" optimization response
calculations.
5. If there is no MODEWEIGHT defined, but a DRESP1 with RTYPE = WCOMP exists, the
following default is applied:
MODEWEIGHT (7) = 1.0 if no SPC is defined for the subcase, EIGRL does not define a V1
> 0.0, and it is solving for more than 6 modes or all modes below an upper bound.
6. This entry is represented as an optimization response in HyperMesh.
Description
The MODTRAK command can be used in the Subcase Information section to control mode
tracking.
Format
MODTRAK = option
Default = OFF
OFF: Mode tracking is not active.
Comments
4. Negative integers or 0 are not accepted as option and will result in an error termination.
Description
The MOTION command can be used in the Subcase Information section to select a multi-body
motion set to be applied in a multi-body problem.
Format
MOTION = option
option < SID > SID: Set identification of MOTION, MOTNG, MOTNGC,
MOTNGE, MOTNJ, MOTNJC, and MOTNJE bulk data
No default entries.
Comments
2. This subcase information entry is only valid when it appears in a multi-body subcase.
3. If the SID referenced by the MOTION subcase information entry matches with the SID
defined for a MOTION bulk data entry, the information on this entry alone is selected.
However, if no MOTION bulk data entry has the referenced SID defined, any of the multi-
body motion entries: MOTNG, MOTNGC, MOTNGE, MOTNJ, MOTHJC, or MOTIONJE which have
this SID will be selected.
Description
The MPC command can be used in the Subcase Information section to select a multi-point
constraint set.
Format
MPC = option
option < SID > SID: Set identification of a MPCADD bulk data entry or, if
no MPCADD bulk data entry exists with this SID, the
No default set identification of an MPC bulk data entry.
Comments
2. If the SID referenced by the MPC subcase information entry matches with the SID defined
for a MPCADD bulk data entry, then the information on this entry alone is selected.
However, if no MPCADD bulk data entry has the referenced SID defined, then any MPC bulk
data entries that have this SID defined will be selected.
3. If present above the first subcase, it is the default for each subcase without an MPC
command, with the exception of linear buckling analysis subcases. Linear buckling
analysis subcases inherit the MPC information from the referenced static subcase.
4. MPC may be set to 0 to override the default in subcases where no MPC is required.
Description
The NLOAD command can be used in the Subcase Information section to select a time
dependent load to be applied in geometric nonlinear analysis problem.
Format
NLOAD = option
option < SID > SID: Set identification of an NLOAD or NLOAD1 bulk data
entry.
No default
Comments
1. NLOAD can only be used in subcases that contain an ANALYSIS = NLGEOM entry.
Description
The NLPARM command can be used in the Subcase Information section to activate nonlinear
solution methods for this subcase and to select the parameters used for nonlinear quasi-static
analysis and geometric nonlinear implicit analysis.
Format
NLPARM = option
option < SID > SID: Set identification of an NLPARM bulk data entry.
No default
Comments
1. NLPARM bulk data entries will not be used unless selected in the Subcase Information
section.
2. If present above the first subcase, it is applied to all linear static subcases. Nonlinear
quasi-static analysis subcases, by their definition, will already have an NLPARM reference
which is used.
Description
The NONLINEAR command can be used in the Subcase Information section to select a
nonlinear dynamic load set for direct transient analyses.
Format
NONLINEAR = option
option < SID > SID: Set identification of NOLIN1, NOLIN2, NOLIN3,
NOLIN4 or NLRGAP bulk data entries.
No default
Comments
Description
The NORM command can be used in the Subcase Information section to define a normalization
factor used in the computation of the "combined compliance index" optimization response.
Format
NORM = option
Argument Description
Comments
1. Refer to the Responses page of the User's Guide for more information on the "combined
compliance index" optimization response calculation.
Description
The NSM command can be used in the Subcase Information section to select a non-structural
mass set for mass generation. The selector command must appear before the first SUBCASE
statement.
Format
NSM = option
option < SID > SID: Set identification number of a NSMADD bulk data
entry or, if no NSMADD bulk data entry exists with
No default this SID, the set identification of NSM, NSM1,
NSML and NSML1 bulk data entries.
Comments
1. Only one NSM subcase information entry can be present in the model.
2. This subcase information entry must appear before the first SUBCASE statement.
Description
The P2G command is used before the first subcase to select a direct input load matrix.
Format
P2G = name
Examples
P2G = PAX
Argument Description
name Name of a load matrix that is input in the bulk data section using the
DMIG card.
Comments
1. Terms are added to the load matrix before any constraints are applied.
2. The DMIG matrix must be rectangular (columnar), that is field 4 on the referenced DMIG
entry must contain the integer 9.
3. A scale factor may be applied to this input using the CP2 parameter (See PARAM bulk data
entry).
4. By default, gravity and centrifugal loads are not generated based on the external mass
matrix (M2GG). In this case, gravity and centrifugal loads should be included in generating
the reduced loads in the DMIG.
5. When multiple instances of this card occur, the referenced DMIG entries are combined.
This behavior differs from that of Nastran, which only recognizes the last instance of this
card in the same situation.
7. If the DMIG data referenced by the P2G statement has multiple load columns, then they
are applied in order in the linear and nonlinear static structural analysis subcases. If
there are more static subcases than columns, then only the subcases up to the number
of columns will get loads. If there are more columns than static subcases, then the
number of columns used with be the number of static subcases. For example, if the DMIG
has two columns and there are three static subcases, only the first two subcases will get
8. For more control, to add a single DMIG load to one of multiple static subcases, use
P2GSUB.
Description
The P2GSUB command is used in a specific subcase to select a direct input load matrix.
Format
Examples
P2GSUB = PAX
P2GSUB = PAY(2)
P2GSUB = 2.5*PAZ(3)
Argument Description
<Real>
Default = 1.0
name Name of a load matrix that is input in the bulk data section using the
DMIG card.
Default = 1
Comments
1. Terms are added to the load matrix before any constraints are applied.
2. The DMIG matrix must be rectangular (columnar), that is field 4 on the referenced DMIG
entry must contain the integer 9.
3. A scale factor may be applied to this input using the CP2 parameter (see PARAM bulk data
entry).
4. By default, gravity and centrifugal loads are not generated based on the external mass
matrix (M2GG). In this case, gravity and centrifugal loads should be included in generating
the reduced loads in the DMIG.
Description
The PEAKOUT command can be used in the Subcase Information section to select the criteria
for automatic identification of loading frequencies at which result peaks occur. Other result
output may then be requested at these “peak” loading frequencies. This data selector is for
frequency response solution sequences only.
Format
PEAKOUT = option
option < SID > SID: Set identification of a PEAKOUT bulk data entry.
No default
Comments
2. If present above the first subcase, it is applied to all subcases which can accept it but do
not contain a PEAKOUT card.
3. Other result output may be obtained at the peak loading frequencies by using the PEAK
keyword in the option field. Currently, support is only available for PFMODE, PFPANEL,
and PFGRID.
Description
The PRETENSION command can be used in the Subcase Information section to select and
activate a pretensioning bolt load.
Format
PRETENSION = option
option < PSID > Pretensioning load set identification of a PTADD bulk
data entry or, if no PTADD bulk data entry exists with
this PSID, the set identification of PTFORCE, PTFORC1,
PTADJST and PTADJS1 bulk data entry.
Comments
3. The rules for sequencing pretensioning subcases on the same pretension section are as
follows:
Description
Selects the RANDPS and RANDT1 bulk data entries to be used in random analysis.
Format
RANDOM = n
Example
RANDOM = 177
Comments
1. This command must select RANDPS bulk data entries in order to perform random analysis.
3. This data can be placed anywhere in the Subcase Information section. It is not SUBCASE
specific.
Description
The REPGLB command can be used in the Subcase Information section, before the first
subcase statement, to select a report set that is not subcase dependent.
Format
REPGLB = integer
integer < DRID > DRID: Set identification of a DREPORT or DREPADD bulk
data entry.
No default
Comments
1. The response referenced by the REPGLB selection must not be subcase dependent.
Description
The REPSUB command can be used in the Subcase Information section, within a subcase
definition, to select a report set that is subcase dependent.
Format
REPSUB = integer
integer < DRID > DRID: Set identification of a DREPORT or DREPADD bulk
data entry.
No default
Comments
Description
The RESVEC command can be used in the Subcase Information section to control the
calculation of residual vectors.
Format
RESVEC(type, damping) = option
See comments
NO: Residual vectors are not calculated.
for default.
Comments
1. RESVEC can be requested for normal modes, modal complex eigenvalue analysis, modal
frequency response, and modal transient response analysis subcases.
2. If the RESVEC does not exist in a subcase (and is not defined above the first subcase),
then the default is YES for modal frequency response and transient response analysis
subcases, and the default is NO for all other applicable subcases. If a RESVEC card exists
without the YES/NO option, the default is YES.
4. For normal modes analysis, the unit load method (type=UNITLOD) is applied to the
degrees-of-freedom defined by USET and USET1 U6 entities. If the Lanczos eigensolver is
used then RESVEC=YES must be present. If the AMSES or AMLS eigensolver is used, then
the USET and USET1 U6 residual vectors will always be calculated (even if RESVEC=NO is
specified).
5. Even though DAMPLOD and NODAMP may be defined inside each subcase, the setting from
the last RESVEC data will be used for all of the modal complex eigenvalue analysis, modal
frequency response, and modal transient subcases in the model.
6. Residual vectors from USET and USET1 U6 data are only available for modal complex
eigenvalue analysis when AMSES or AMLS is used to calculate the normal modes. They
are not created if Lanczos is used.
7. For modal frequency response and modal transient analysis, the USET and USET1 U6
residual vectors will always be calculated if the AMSES or AMLS eigensolver is used, and
they will never be calculated if the Lanczos eigensolver is used. The RESVEC command
has no effect on the USET and USET1 U6 residual vector creation for modal frequency
response and modal transient analysis.
RGYRO – This data entry can be used in the subcase information section to activate
gyroscopic effects in Rotor dynamics
Description
Identifies a RGYRO bulk data entry that contains information required to implement Rotor
dynamics in Modal Complex Eigenvalue Analysis and/or Modal Frequency Response Analysis.
Format
RGYRO = option
Example
RGYRO = 3
RGYRO = NO
(Integer)
Comments
1. Multiple RGYRO subcase information entries are allowed in different subcases, however,
only one RGYRO subcase entry can exist within each subcase.
Description
The RSPEC command can be used in the Subcase Information section to reference combination
rules, excitation degrees of freedom, and input spectra for use in response spectrum analysis.
Format
RSPEC = option
option < SID > SID: Set identification of an RSPEC bulk data entry.
No default
Comments
2. Refer to the Response Spectrum Analysis section of the User’s Guide for more details.
Description
The RWALL command can be used in the Subcase Information section to select rigid walls for
geometric nonlinear analysis.
Format
RWALL = option
option < SID > SID: Set identification of an RWALADD bulk data entry
or, if no RWALADD bulk data entry exists with this
No default SID, the set identification of RWALL bulk data
entries.
Comments
1. Only one RWALL entry can be present for each subcase. It can only be used in subcases
that contain an ANALYSIS = NLGEOM entry.
2. If the SID referenced by the RWALL subcase information entry matches with the SID
defined for an RWALADD bulk data entry, then the information on this entry alone is
selected. However, if no RWALADD bulk data entry has the referenced SID defined, then
any XHSIT bulk data entries that have this SID defined will be selected.
Description
The SDAMPING command can be used in the Subcase Information section to apply modal
damping as a function of natural frequency in modal solutions.
Format
SDAMPING (type) = option
type < STRUCTURE, FLUID > The referenced bulk data entry is applied to the
Default = STRUCTURE structural (STRUCTURE) or fluid (FLUID) portion of
the model.
option < SID > SID: Set identification of a TABDMP1 bulk data
entry.
No default
Comments
1. SDAMPING can only be used in modal transient, modal frequency response and modal
complex eigenvalue analyses; and must reference a TABDMP1 bulk data entry.
2. Only one SDAMPING entry of each type can be defined for each subcase.
4. If present above the first subcase, it is applied to each modal frequency or modal
transient subcase without an SDAMPING entry.
The TYPE field in the TABDMP1 bulk data entry should be set to CRIT. This TABDMP1 bulk
data entry is referenced by the SDAMPING subcase information entry.
Set the damping value (field gi) in the TABDMP1 bulk data entry equal to half of the
value of PARAM, G (that is set the constant value to C/C0).
Description
The SEINTPNT command can be used in the Subcase Information section to select a set of
interior DOF of super elements to be converted to exterior DOF.
Format
SEINTPNT = option
Example
SEINTPNT = 100
BEGIN BULK
SET,100,GRIDC,
+,10643,T1,10643,T2,10643,T3
option <SID> SID refers to the ID of a bulk card SET of type GRIDC.
No default
Comments
1. SEINTPNT can be used when CMS super elements in .h3d files are present in residual runs.
After the conversion, these DOF are part of the analysis DOF and can be used as
connection points, load DOF, response DOF during optimization.
3. GRID point information for interior grids (that are to be converted to exterior grids) should
be included in the GRID bulk data entry, which in turn should be included in the solver
deck if SEINTPNT is used.
Description
The SOLVTYP command can be used in the Subcase Information section to select the solver
for linear and nonlinear static subcases, nonlinear geometric implicit static subcase
(ANALYSIS=NLGEOM), and nonlinear geometric implicit dynamic subcase (ANALYSIS=IMPDYN).
Format
SOLVTYP = option
option < SID > SID: Set identification of an SOLVTYP bulk data entry.
Comments
1. Only one SOLVTYP entry can be defined for each linear and nonlinear static subcases or
nonlinear geometric implicit subcase.
2. If present above the first subcase, it is applied to all compatible linear and nonlinear
static subcases and nonlinear geometric implicit subcases. For more details on subcase
type and solver compatibility, refer to the SOLVTYP bulk data entry.
6. The performance of the iterative solver depends on the conditioning of the stiffness
matrix. For compact solid models, the iterative solver may perform considerably better
than the direct solver in terms of memory usage and elapsed times for a single linear
Description
The SPC command can be used in the Subcase Information section to select a single-point
constraint set.
Format
SPC = option
option < SID > SID: Set identification of an SPCADD bulk data entry or,
if no SPCADD bulk data entry exists with this SID,
No default the set identification of SPC or SPC1 bulk data
entries.
Comments
2. If the SID referenced by the SPC subcase information entry matches with the SID defined
for an SPCADD bulk data entry, then the information on this entry alone is selected.
However, if no SPCADD bulk data entry has the referenced SID defined, then any SPC or
SPC1 bulk data entries that have this SID defined will be selected.
3. If present above the first subcase, it is the default for each subcase without an SPC
command, with the exception of linear buckling analysis subcases. Linear buckling
analysis subcases inherit the SPC information from the referenced static subcase.
4. SPC may be set to 0 to override the default in subcases where no SPC is required.
5. SPC must be present for linear static solutions. The SID may be set to 0 to run linear
static solutions with no constraints.
Description
The STATSUB command can be used in the Subcase Information section to select a static
solution subcase.
Format
STATSUB(type) = option
Comments
2. A linear buckling solution cannot be performed on a linear static subcase that uses inertia
relief.
3. STATSUB(PRELOAD) is supported for linear static, normal modes, and direct frequency
response solution sequences.
4. STATSUB(PRETENS) is supported for linear and nonlinear static subcases. Other subcase
types can use STATSUB(PRELOAD), which refers to a pretension subcase, in order to
incorporate the effect of pretensioning on natural frequencies, dynamic solutions, and so
5. STATSUB(PRETENS) can only reference a subcase that precedes the current subcase in
the input deck.
Description
The SUBCASE command can be used in the Subcase Information section to indicate the start
of a new subcase definition.
Format
SUBCASE = integer
Argument Description
Comments
1. Each subcase must be declared with a separate SUBCASE header and a unique SID.
Description
Format
SUBCOM = n
Example
SUBCOM = 125
Argument Description
(Integer > 2)
Comments
4. If the referenced subcases contain thermal loads or element deformations, you must
define the temperature field in the SUBCOM with a TEMP(LOAD) command or the element
deformations with a DEFORM command.
Description
The SUBMODEL entry can be used in the Subcase Information section to select a submodel as
a set of elements. Subcase entries specific to the selected element set can be used to solve
the submodel without affecting the rest of the structure.
Format
SUBMODEL, SID, SID_r
SID <integer>0> Specifies the SID of a SET of elements that defines the
submodel.
Comments
1. A SUBMODEL entry can only be defined within a subcase and cannot be specified above
the first subcase.
2. The SUBMODEL entry does not automatically apply the specific attributes (loads,
constraints and so on) to the defined submodel. It is your responsibility to specify
corresponding attributes that apply exclusively to the subcase-specific model defined via
SUBMODEL.
Description
Gives the coefficients for forming a linear combination of the previous static subcases.
Format
Example
SUBSEQ=1.0, -1.0, 0.0, 2.0
Argument Description
(Real)
Comments
Description
The SUPORT1 command can be used in the Subcase Information section to select the fictitious
support set to be applied to the model.
Format
SUPORT1 = option
option < SID > SID: Set identification of a SUPORT1 bulk data entry.
No default
Comments
1. SUPORT1 entries will not be used unless selected in the Subcase Information section by
the SUPORT1 command.
Description
Selects the temperature set to be used in either material property calculations or thermal
loading.
Format
TEMPERATURE (type) = option
Examples
TEMPERATURE(LOAD)=15
TEMP(MATERIAL)=7
TEMPERATURE=7
option < SID > SID: Set identification number of TEMP or TEMPD
bulk data entries.
No default
4. The total load applied will be the sum of external (LOAD command), thermal (TEMP(LOAD)
command) and constrained displacement (SPC command) loads.
5. Static and thermal loads should have unique set identification numbers.
where, A(T0 ) is the thermal expansion coefficient defined on the MATi bulk data entries, T
is the load temperature defined with TEMPERATURE(LOAD), and T0 is the initial temperature
which is defined in one of the following ways:
Description
The TSTEP command can be used in the Subcase Information section to select integration for
transient analysis.
Format
TSTEP (type) = option
Example
TSTEP = 731
TSTEP (FOURIER) = 755
option < SID > SID: Set identification number of a TSTEP bulk
data entry.
No default
Comments
2. A TSTEP entry can also be used to execute a transient thermal analysis (only for
type=TIME or Default).
Description
The TSTEPNL command can be used in the Subcase Information section to select integration
and other parameters for nonlinear implicit dynamics analysis.
Format
TSTEPNL = option
Example
TSTEPNL = 731
Comments
Description
The TSTRU command can be used in the Subcase Information section to assign a temperature
set identification number to the resulting nodal temperatures of a steady-state heat transfer
analysis or the last time step of a transient heat transfer analysis.
Format
TSTRU = option
option < SID > SID: This is a temperature set identification number.
It may be referenced from a static analysis
Default = Subcase ID subcase, in which case the resulting nodal
temperatures of a steady-state heat transfer
analysis or the last time step of a transient
heat transfer analysis are considered as applied
loads for the static analysis.
Comments
2. If TSTRU does not explicitly appear in a heat transfer subcase, then the Subcase ID is
used as the default.
3. A temperature set from a heat transfer analysis will override any temperature set defined
by the bulk data entries TEMP or TEMPD.
Description
The WEIGHT command can be used in the Subcase Information section to define a weighting
factor (multiplier) for the compliances of individual linear static solution subcases, which are
used in the calculation of the "weighted compliance" and "combined compliance index"
optimization responses.
Format
WEIGHT = value
Argument Description
value The multiplier to be used for the compliance of this subcase in the
calculation of "weighted compliance" or "combined compliance index."
Comments
1. Refer to the Responses page of the User's Guide for more information on "weighted
compliance" and "combined compliance index" optimization response calculations.
3. If a WEIGHT is not defined in any subcase, but a DRESP1 with RTYPE = WCOMP or COMB
exists, all static subcases are assigned a WEIGHT of 1.0 by default.
Description
The XHIST command can be used in the Subcase Information section to select time history
output for geometric nonlinear analysis.
Format
XHIST = option
option < SID > SID: Set identification of an XHISTADD bulk data entry
or, if no XHISTADD bulk data entry exists with this
No default SID, the set identification of XHIST bulk data
entries.
Comments
1. Only one XHIST entry can be present for each subcase. It can only be used in subcases
that contain an ANALYSIS = NLGEOM entry.
2. If the SID referenced by the XHIST subcase information entry matches with the SID
defined for an XHISTADD bulk data entry, then the information on this entry alone is
selected. However, if no XHISTADD bulk data entry has the referenced SID defined, then
any XHSIT bulk data entries that have this SID defined will be selected.
Description
The XSTEP command can be used in the Subcase Information section to activate the explicit
solution method for this subcase and to select the parameters used for explicit analysis.
Format
XSTEP = option
option < SID > SID: Set identification of an XSTEP bulk data entry.
No default
Comments
1. XSTEP bulk data entries will not be used unless selected in the Subcase Information
section.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
AC C LR AID GID FC UT
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
AC C LR 100 34 100.0
Field Contents
(Integer > 0)
(Integer > 0)
(Real > 0)
Comments
4. The recommended value for FCUT is 1650 Hz (1.65 ms-1) to obtain a class 1000 SAE
filtering.
6. Note that if the coordinates are moving, the integrals of X, Y, and Z raw accelerations
projected to the output coordinate system are not the same as the velocities projected
to the output coordinate system, as described in XHIST. Computation of these integrals
in a post-processor allows retrieving the accelerations projected to the output coordinate
system without aliasing problems. Integration and differentiation are acting like another
filter on top of the 4-pole Butterworth.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
INFOR Defines whether grids or elements identified by FSET and SSET are to be
used to define the fluid-structure interface.
DSKNEPS Secondary fluid skin growth tolerance (See comments 4 and 5).
SRCHUNIT Search units. ABS for absolute model units or REL for relative model units
based on element size.
MAXSGRID The maximum number of structural grids that can be interfaced with one fluid
element face.
Comments
1. ACMODL card is optional in the deck. If provided, only one ACMODL card is allowed.
2. For INTER=IDENT, the interface would be calculated based on a grid to grid match
between fluid and structural parts. For INTER=IDENT, INFOR must be GRID or blank. Each
grid specified on the FSET/SSET must be able to find a matching interface grid. If either
FSET or SSET is not provided, a searching algorithm would find the grids on the skin of
the surface.
3. For INTER=DIFF, if FSET/SSET is provided, the skin of the surface would be based on the
set. If either FSET or SSET is not provided, a searching algorithm would find the skin of
the surface. The searching algorithm for this case is based on the normal distance from
the fluid face. When INTER=DIFF, a grid to grid match is no longer a requirement.
INTOL represents a normal direction into the fluid for the case when the fluid protrudes
past the structural interface. It is defined as INTOL x L, where L is the smallest edge
of the fluid element surface.
5. The value required in the secondary fluid skin growth tolerance (DSKNEPS) field must
always be greater than the value of the fluid growth tolerance (SKNEPS).
If the required value of DSKNEPS is less than SKNEPS, then an ERROR message will be
output and the run will be terminated.
If the DSKNEPS field is left blank, a default value equal to 1.5 * SKNEPS is assigned to
it.
6. This card is represented as a control card in HyperMesh.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
directly defines the value of that will be used for all degrees-of-freedom
that are excited by this dynamic load entry.
Comments
1.
where,
2. Dynamic load sets must be selected in the I/O Options or Subcase Information sections
with the command DLOAD = SID.
3. SID must be unique with respect to other dynamic load sets, that is ACSRCE, DLOAD,
RLOAD1, RLOAD2, TLOAD1, and TLOAD2 entries.
4. The referenced EXCITEID, DELAY and DPHASE entries must specify fluid points only.
5. If either DELAY or DPHASE are blank or zero, the corresponding or will be zero.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ASET G1 C1 G2 C2 G3 C3 G4 C4
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
Ci Component numbers.
(Integer zero or blank for scalar points, or up to 6 unique digits (0 < integer
< 6) may be placed in the field with no embedded blanks for grid points.
The components refer to the coordinate system referenced by the grid
points.)
Comments
1. Refer to the User's Guide section on The Direct Matrix Approach for more information on
the use of this card.
2. A fatal error will be issued if the input contains ASET or ASET1, but PARAM, EXTOUT is
not given.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ASET1 C G1 G2 G3 G4 G5 G6 G7
G8 G9 G10 -etc.-
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ASET1 123 34 88 4 12 19 7 70
1234 65
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ASET1 C G1 "THRU" G2
C Component number.
(Integer zero or blank for scalar points, or up to 6 unique digits (0 < integer
< 6) may be placed in the field with no embedded blanks for grid points. The
components refer to the coordinate system referenced by the grid points.)
Comments
1. If the alternate format is used, all points in the sequence G1 through G2 are not required
to exist, but there must be at least one boundary degree-of-freedom for the model, or a
fatal error will result. Any grids implied in the THRU that do not exist will collectively
produce a warning message, but will otherwise be ignored.
2. Refer to the User's Guide section on The Direct Matrix Approach for more information on
the use of this card.
3. A fatal error will be issued if the input contains ASET or ASET1, but PARAM, EXTOUT is
not given.
4. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
MIXED, it is allowed that when grid lists are provided for a given component, that the grid
references be either scalar points (SPOINT) or structural grid points (GRID) when the
component is 0, 1 or blank; interpreting all of these as 0 for scalar points and as 1 for
structural grids. When SPSYNTAX is set to STRICT it is required for grid/component pairs
(G#/C#) that the component be 0 or blank when the grid references are to scalar points
(SPOINT), and that the component be > 1 when the grid references are to structural grid
points (GRID). When the component is greater than 1, the grid references must always
be a structural grid (GRID).
The BEAD bulk data entry will no longer be supported for the definition of topography
optimization. All definitions must be provided using the DTPG bulk data entry. HyperMesh will
continue to read BEAD entries, but will convert them into DTPG entries.
Information regarding the BEAD entry can be found in the Previously Supported Input section
of the Reference Guide.
Description
The BEGIN bulk data entry indicates the beginning of data that is used to describe a specific
entity (or entities) for inclusion in a model. The BEGIN entry is used in conjunction with the
END entry to define the data required for a specific entity.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
TYPE Specifies the entity type that will be defined by the BEGIN data entry (see
Comment 2).
(HYPRBEAM or FEMODEL)
NAME This field specifies the name of the entity that is defined by the BEGIN entry
(see Comment 2).
(Character String)
1. The BEGIN and END bulk data entries are used in conjunction to define an entity within
the full model.
2. TYPE = HYPRBEAM:
Data required for the definition of an arbitrary beam section will be specified between the
BEGIN and END data entries.
TYPE = FEMODEL:
In a model containing multiple parts, the parts are included within the full model specifying
part data between the BEGIN and END bulk data entries (the INCLUDE entry can also be
used for part data referencing). The name of the included part should be specified in the
NAME field.
3. The INCLUDE entry, similar to almost any other bulk data entry, is allowed between BEGIN
and END entries. However, BEGIN and END should exist in the same file.
4. Models are often defined in separate files, and the block (BEGIN – END) contains only
INCLUDE entries. It is possible to duplicate a single part by including the same file(s) in
different BEGIN-END blocks.
5. There can be multiple sections of arbitrary beam data; one for each beam section.
6. An example set of data for the definition of an arbitrary beam section is as follows:
BEGIN,HYPRBEAM,SQUARE
$
GRIDS,1,0.0,0.0
GRIDS,2,1.0,0.0
GRIDS,3,1.0,1.0
GRIDS,4,0.0,1.0
$
CSEC2,10,100,1,2
CSEC2,20,100,2,3
CSEC2,30,100,3,4
CSEC2,40,100,4,1
$
PSEC,100,1000,0.1
$
END,HYPRBEAM
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
MU Coefficient of friction.
No default (Real)
Comments
1. This entry is only valid with an @HyperForm statement in the first line of the input file.
Description
Defines quad or tria faces that are in turn used to define a barrier to limit the total
deformation for free-shape design regions.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
BMFAC E BMID G1 G2 G3 G4
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
BMID Barrier mesh identification number. Referenced from a DSHAPE bulk data
entry.
G# Grid point identification number of connection points. G1, G2, and G3 are
required to define tria faces, G4 is required to define quad faces.
Comments
1. Grid points used in the definition of BMFACE entries cannot be used to define structural
elements.
Description
Defines the degrees-of-freedom to be fixed during DMIG generation using CMSMETH card.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
Comments
2. ASET, BNDFIX and BNDFREE; all three are not allowed in the same deck.
3. If BNDFREE and ASET are present, the DOFs associated with ASET would be in BNDFIX;
except the DOF assigned to BNDFREE.
4. If BNDFIX and ASET are present, the DOFs associated with ASET would be in BNDFREE;
except the DOF assigned to BNDFIX.
Description
Defines the fixed (B-set) degrees-of-freedom to be fixed during DMIG generation using
CMSMETH card.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
C Component numbers.
No default (Integer > 0 or blank). Zero or blank for SPOINT and any unique
combination of integers 1 through 6 for grid points with no embedded
blanks.
3. If BNDFREE/BNDFRE1 and ASET/ASET1 are present, the DOFs associated with ASET will be
in the B-set; except the DOF assigned to BNDFREE which will be in the C-set.
4. If BNDFIX/BNDFIX1 and ASET/ASET1 are present, the DOFs associated with ASET would
be in C-set; except the DOF assigned to BNDFIX which will be in the B-set.
5. Multiple “thru” sequences can be used on a single card, and can span across continuation
lines.
6. If the "thru" comment is used, G1 and G2 must exist, but the grid points between G1 and
G2 are not required to exist.
Description
Defines the free (C-set) degrees-of-freedom to be fixed during DMIG generation using
CMSMETH card.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
C Component numbers.
No default (Integer > 0 or blank). Zero or blank for SPOINT and any unique
combination of integers 1 through 6 for grid points with no embedded blanks.
3. If BNDFREE/BNDFRE1 and ASET/ASET1 are present, the DOFs associated with ASET will be
in the B-set; except the DOF assigned to BNDFREE which will be in the C-set.
4. If BNDFIX/BNDFIX1 and ASET/ASET1 are present, the DOFs associated with ASET would
be in C-set; except the DOF assigned to BNDFIX which will be in the B-set. Any number of
continuations may appear.
5. Multiple “thru” sequences can be used on a single card, and can span across continuation
lines.
6. If the "thru" comment is used, G1 and G2 must exist, but the grid points between G1 and
G2 are not required to exist.
Description
Defines the degrees-of-freedom to be fixed during DMIG generation using CMSMETH card.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
Comments
2. ASET, BNDFIX and BNDFREE are not allowed in the same deck.
3. If BNDFREE and ASET are present, the DOFs associated with ASET would be in BNDFIX;
except the DOF assigned to BNDFREE.
4. If BNDFIX and ASET are present, the DOFs associated with ASET would be in BNDFREE;
except the DOF assigned to BNDFIX.
Description
Description
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C AABSF 71 4 1 10 5
Field Contents
$
$$--------------------------------------------------------------
$$ HYPERMESH TAGS
$$--------------------------------------------------------------
$$BEGIN TAGS
$$END TAGS
PARAM,AUTOSPC,YES
PARAM,POST,-1
$$
$$ DESVARG Data
$$
$$
$$ GRID Data
$$
GRID 9 0.492 0.0 -1.72-15 -1
GRID 10 0.246 0.0 -8.59-16 -1
GRID 11 0.0 0.0 0.0 -1
GRID 12 -0.246 0.0 8.589-16 -1
GRID 13 -0.492 0.0 1.718-15 -1
GRID 14 -0.492 0.246 1.718-15 -1
GRID 15 -0.492 0.492 1.718-15 -1
GRID 16 -0.246 0.492 8.589-16 -1
GRID 17 0.0 0.492 0.0 -1
GRID 18 0.246 0.492 -8.59-16 -1
GRID 19 0.492 0.492 -1.72-15 -1
GRID 20 0.492 0.246 -1.72-15 -1
GRID 21 0.0 0.246 0.0 -1
GRID 22 -0.246 0.246 8.589-16 -1
GRID 23 0.246 0.246 -8.59-16 -1
GRID 24 0.492 -0.246 -1.72-15 -1
GRID 25 0.492 -0.492 -1.72-15 -1
GRID 26 0.246 -0.492 -8.59-16 -1
GRID 27 0.0 -0.492 0.0 -1
GRID 28 -0.246 -0.492 8.589-16 -1
GRID 29 -0.492 -0.492 1.718-15 -1
GRID 30 -0.492 -0.246 1.718-15 -1
GRID 31 0.0 -0.246 0.0 -1
GRID 32 0.246 -0.246 -8.59-16 -1
GRID 33 -0.246 -0.246 8.589-16 -1
GRID 34 0.246 5.049-29-.300073 -1
GRID 35 -5.99-130.0 -.300073 -1
GRID 36 -5.62-130.246 -.300073 -1
GRID 37 0.246 0.246 -.300073 -1
GRID 38 0.246 2.524-29-.600146 -1
GRID 39 -1.2-12 0.0 -.600146 -1
GRID 40 -1.12-120.246 -.600146 -1
GRID 41 0.246 0.246 -.600146 -1
GRID 42 0.246 2.919-29-0.90022 -1
GRID 43 -1.79-120.0 -.900219 -1
GRID 44 -1.68-120.246 -.900219 -1
GRID 45 0.246 0.246 -0.90022 -1
GRID 46 0.246 3.787-29-1.20029 -1
GRID 47 -2.39-120.0 -1.20029 -1
GRID 48 -2.24-120.246 -1.20029 -1
GRID 49 0.246 0.246 -1.20029 -1
GRID 50 0.246 4.733-29-1.50037 -1
GRID 51 -3.0-12 0.0 -1.50037 -1
GRID 52 -2.81-120.246 -1.50037 -1
GRID 53 0.246 0.246 -1.50037 -1
GRID 54 0.246 5.364-29-1.80044 -1
GRID 55 -3.6-12 0.0 -1.80044 -1
GRID 56 -3.37-120.246 -1.80044 -1
GRID 57 0.246 0.246 -1.80044 -1
GRID 58 0.246 6.311-29-2.10051 -1
GRID 59 -4.2-12 0.0 -2.10051 -1
GRID 60 -3.93-120.246 -2.10051 -1
GRID 61 0.246 0.246 -2.10051 -1
GRID 62 0.246 7.258-29-2.40059 -1
$
$$
$$ PSHELL Data
$$
$
$
$
$
$
$
$
$HMNAME PROP 1"tube" 4
$HWCOLOR PROP 1 52
PSHELL 1 20.1 2 2 0.0
$$
$$ PSOLID Data
$$
$HMNAME PROP 2"Air" 5
$HWCOLOR PROP 2 4
PSOLID 2 1 PFLUID
$$
$$ MAT1 Data
$$
$HMNAME MAT 2"alum" "MAT1"
$HWCOLOR MAT 2 3
MAT1 21.0+7 0.3 0.000254
$$
$$ MAT10 Data
$HMNAME MAT 1"Air" "MAT10"
$HWCOLOR MAT 1 3
MAT10 1 1.21-7 13000.0
$$
$$------------------------------------------------------------------------------$
$$ HyperMesh Commands for loadcollectors name and color information $
$$------------------------------------------------------------------------------$
$HMNAME LOADCOL 2"spc"
$HWCOLOR LOADCOL 2 6
$$
$HMNAME LOADCOL 8"Force"
$HWCOLOR LOADCOL 8 7
$$
$HMNAME LOADCOL 12"SPC"
$HWCOLOR LOADCOL 12 5
$$
$$
$$ FREQi cards
$$
$HMNAME LOADCOL 3"Freq"
$HWCOLOR LOADCOL 3 6
$FREQ1 3 0.0 5.0 600
FREQ 3480.
ALTDOCTAG "0mjpRI@DXd^3_0ASnbi`;l;q6A23R@9_67hgW8R?OiZ]
Eq:PeN``A;WXh3ITgJeq5NZRd5jSHQK3X@:`a12;n4qD_I^RYMo"
ADI0.1.0 2011-02-11T20:16:20 0of1 OSQA
ENDDOCTAG
1. Element identification numbers should be unique with respect to all other element
identification numbers.
3. The CAABSF element must connect entirely to fluid points on the fluid-structure
boundary.
Description
The CAALOAD bulk data entry defines the CFD pressure that is transferred to the structural
side for frequency response analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
CAAID Identification number of the H3D file (loadID) specified by ASSIGN,H3DCAA (See
comments 1 and 2).
SRFID Identification number of a SURF bulk data entry that defines the surface where
CFD pressure is applicable (See comment 1).
Comments
1. The surface GRIDs associated with the CFD pressure must be fluid grids. The pressures
from CFD analysis at each loading frequency are stored in an H3D file. This H3D file can be
referenced using the ASSIGN I/O Options Entry (ASSIGN, H3DCAA, loadID, and filename).
2. The pressure from the fluid grids will be transferred to structural grids for frequency
response analysis.
3. CAALOAD can be chosen as a dynamic load in the I/O Options or Subcase Information
sections with the command DLOAD = SID.
4. The SID field in this CAALOAD entry must be unique with respect to other dynamic load
sets (ACSRCE, DLOAD, RLOAD1, RLOAD2, TLOAD1, and TLOAD2 entries).
Description
The CBAR bulk data entry defines a simple beam element (BAR) of the structural model.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C BAR 2 39 7 3 13
513
Field Contents
No default (Real)
PA,PB Pin flags for bar ends A and B, respectively. Used to remove
connections between the grid point and selected degrees-of-
freedom of the bar. The degrees-of-freedom are defined in the
element’s coordinate system. The bar must have stiffness
associated with the PA and PB degrees-of-freedom to be released
by the pin flags. For example, if PA=4 is specified, the PBAR entry
must have a value for J, the torsion stiffness.
Fig 2: Moments and Internal Forces in the x-y Plane (for a C BAR element)
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
4. If X1/G0 is a positive integer and X2 and X3 are blank, then G0 is used to orient the
element, otherwise X1, X2, X3 is used.
5. The OFFT character string specifies how the offset and orientation vector components
are computed. By default, the offset vectors are specified in the Global (local
displacement) coordinate system of each grid A and B, and the orientation vector is
specified in the Global coordinate system of grid A. Using the codes below, the offset
vector can be specified in the element coordinate system and the orientation vector can
be specified in the basic coordinate system. The valid character strings and their
meanings are shown below:
The element system x-axis is defined from GA to GB. The orientation vector and the
element system x-axis are then used to define the z and y axes of the element system.
A vector is formed from the cross product of a vector going from Grid A to Grid B and the
orientation vector to create the element coordinate z-direction.
6. Offset vectors are treated like rigid elements. The length of the offset vectors is not
affected by thermal loads.
Description
The CBEAM bulk data entry defines a beam element (BEAM) of the structural model.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C BEAM 2 39 7 3 13
513 3.0
Field Contents
PA, PB Pin flags for beam ends A and B respectively. Used to remove
connections between the grid point and selected degrees-of-freedom
of the beam. The degrees-of-freedom are defined in the element’s
coordinate system and the pin flags are applied at the offset ends of
the beam. The beam must have stiffness associated with the PA and
PB degrees-of-freedom to be released by the pin flags. For example,
if PA=4, the PBEAM entry must have a non-zero value for J, the
torsion stiffness.
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2. If X1/G0 is a positive integer and X2 and X3 are blank, then G0 is used to orient the
element, otherwise X1, X2, X3 is used.
3. G0 GA or GB.
The element system x-axis is defined from GA to GB. The orientation vector and the
element system x-axis are then used to define the z and y axes of the element system.
A vector is formed from the cross product of a vector going from Grid A to Grid B and the
orientation vector to create the element coordinate z-direction.
6. Offset vectors are treated like rigid elements. The length of the offset vectors is not
affected by thermal loads.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
S OC ID S1 S2 S3
Example 1
Spring-damper element defined with default orientation and location; default orientation is
only valid when only K1, and/or K4 are defined on referenced PBUSH.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C BUSH 2 6 8 1
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C BUSH 19 7 1 2 4
0.3
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C BUSH 41 9 1 2 5
Field Contents
(Real)
Default = -1 (Integer > -1; -1 indicates that the offset is along GA-GB)
(Real)
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
C BUSH element
2. CID > 0 overrides GO and Xi. Then the element x-axis is along T1, the element y-axis is
along T2, and the element z-axis is along T3 of the CID coordinate system. If the CID
refers to a cylindrical coordinate system or a spherical coordinate system, the grid GA is
used to locate the system. If for cylindrical or spherical coordinate, GA falls on the z-axis
used to define them, it is recommended that another CID be selected to define the
element x-axis.
3.
specified, the line AB is the element x-axis and the orientation vector lies in the x-y
plane (similar to the CBEAM element).
4.
specified, the line AB is the element x-axis. This option is valid only when K1 or K4 or
both on the PBUSH entry are specified (but K2, K3, K5, and K6 are not specified). If K2,
K3, K5, or K6 are specified, the solver will terminate with an error.
7. A CBUSH element, referencing a PBUSH property with a single stiffness term, is equivalent
to a CELAS1 or CELAS2 element, only when the elements have zero length. A non-zero
length CBUSH assumes rigid body connections from the connection points, GA and GB, to
the spring-damper location, as defined either by S or the OCID and Si fields.
F = K(UGB - UGA )
Therefore, the sign of the force will depend on the grids GA and GB. If the grids are
switched, then the element force will be reversed.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C BUSH1D 2 6 8 1
Field Contents
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2.
axis. In geometric nonlinear analysis, the element axis (line GA to GB) follows the
deformation of grids GA and GB.
4. If CID > 0, the x-axis of CID is the element axis. In geometric nonlinear analysis,
depending on the referenced system being movable or fixed, the axis of the element will
move or not move with the axes of the system, respectively. Geometric nonlinear
analysis is selected by an ANALYSIS = NLGEOM, IMPDYN or EXPDYN subcase entry.
7. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on CBUSH1D entries in the model. A fully qualified reference
(“PartName.number”) is similar to the format of a numeric reference. “PartName” is the
name of the part that contains the referenced local entry (part names are defined on the
BEGIN bulk data entry in the model). “number” is the identification number of a referenced
local entry in the part “PartName”. See Parts and Instances in the User’s Guide for
detailed information on the use of fully qualified references.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C DAMP1 2 10 0 26 3
Field Contents
2. Scalar points may be used for G1 and/or G2, (with corresponding C1 and/or C2 of zero or
blank). If only scalar points and/or grounded terminals are involved, it is more efficient to
use the CDAMP3 entry.
3. Element identification numbers must be unique with respect to all other element
identification numbers.
4. The two connection points (G1, C1) and (G2, C2) must be distinct.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.
6. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C DAMP2 EID B G1 C1 G2 C2
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C DAMP2 2 3.12 12 2
Field Contents
No default (Real)
2. Scalar points may be used for G1 and/or G2, (with a corresponding C1 and/or C2 of zero
or blank). If only scalar points and/or grounded terminals are involved, it is more efficient
to use the CDAMP4 entry.
3. Element identification numbers must be unique with respect to all other element
identification numbers.
4. This single entry completely defines the element since no material or geometric properties
are required.
5. The two connection points (G1, C1) and (G2, C2) must be distinct.
6. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C DAMP3 16 978 24 36
Field Contents
Comments
1. S1 or S2, but not both, may be blank or zero, indicating a constrained coordinate.
2. Element identification numbers should be unique with respect to all other element
identification numbers.
4. A scalar point specified on this entry need not be defined on an SPOINT entry.
Description
Defines a scalar damper element that is connected only to scalar points and is without
reference to a material or property entry.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C DAMP4 EID B S1 S2
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C DAMP4 16 -2.6 4 9
Field Contents
No default (Real)
1. S1 or S2, but not both, may be blank or zero, indicating a constrained coordinate.
2. Element identification numbers should be unique with respect to all other element
identification numbers.
3. This single entry completely defines the element since no material or geometric properties
are required.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.
Description
The CDSMETH command can be used in the component dynamic synthesis method for
generating component dynamic matrices at each loading frequency.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Default = NONE
SVDNP BME:
Dynamic Stiffness Matrix is calculated by block matrix
elimination (Comment 6).
OSET <INTEGER> Grid set for interior grids. The responses corresponding
to interior grids may be recovered in the residual run
Default = BLANK
(Comment 5).
GP_RC <YES, NO> Grid participation recovery control. If YES, the fluid-
structural interface connection matrix is calculated and
Default = NO stored as a part of the CMS super element. This is only
valid, if CMSOUT is specified.
Comments
1. The responses available for recovery, and the attachment points available for connection
in the residual structure, must be specified on a BNDFRE1, BNDFREE, CSET or CSET1 data
entry for a modal frequency response analysis in which CDSMETH has been specified.
2. Frequencies available for recovery must be specified, using the FREQ or FREQ# (# ranges
from 1 to 5) data entries, in the modal frequency response analysis in which CDSMETH
has been specified.
3. A MODEL card may be used for additional response output for the optional CMS
superelement output.
4. Reasonable speedup may be achieved by reducing the number of ASET points in the
residual run when CDSMETH is used.
6. Performance may be an issue with the Block Matrix Elimination (BME) method for large
models. The BME option for the GTYPE field is only recommended for small models or when
other methods fail to work.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ELAS1 2 6 8 1
Field Contents
2. Scalar points may be used for G1 and/or G2 (with a corresponding C1 and/or C2 of zero or
blank). If only scalar points and/or grounded terminals are involved, it is more efficient to
use the CELAS3 entry.
3. Element identification numbers must be unique with respect to all other element
identification numbers.
4. The two connection points (G1, C1) and (G2, C2) must be distinct.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.
6. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).
7. A CBUSH element, referencing a PBUSH property with a single stiffness term, is equivalent
to a CELAS1 or CELAS2 element, only when the elements have zero length. A non-zero
length CBUSH assumes rigid body connections from the connection points, GA and GB, to
the spring-damper location, as defined either by S or the OCID and Si fields.
Description
Defines a scalar spring element of the structural model without reference to a property entry.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ELAS2 EID K G1 C1 G2 C2 GE S
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ELAS2 28 6.2+3 19 4
Field Contents
K Spring stiffness.
No default (Real)
S Stress coefficient.
Comments
2. Scalar points may be used for G1 and/or G2 (with a corresponding C1 and/or C2 of zero or
blank). If only scalar points and/or grounded terminals are involved, it is more efficient to
use the CELAS4 entry.
3. Element identification numbers must be unique with respect to all other element
identification numbers.
4. This single entry completely defines the element since no material or geometric properties
are required.
5. The two connection points (G1, C1) and (G2, C2) must be distinct.
6. To obtain the damping coefficient GE, multiply the critical damping ratio, C/C0, by 2.
8. A scalar point specified on this entry need not be defined on an SPOINT entry.
9. The element force of a spring is calculated from the equation: F = k * (u1 – u2)
Where, k is the stiffness coefficient for the scalar element and u1 is the displacement of
the first degree-of-freedom listed on the CELAS entry. Element stresses are calculated
from the equation: s = S * F, where, S is the stress coefficient as defined above.
10. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).
11. A CBUSH element, referencing a PBUSH property with a single stiffness term, is equivalent
to a CELAS1 or CELAS2 element, only when the elements have zero length. A non-zero
length CBUSH assumes rigid body connections from the connection points, GA and GB, to
the spring-damper location, as defined either by S or the OCID and Si fields.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ELAS3 19 2 14 15
Field Contents
Comments
2. Element identification numbers should be unique with respect to all other element
identification numbers.
Description
Defines a scalar spring element that is connected only to scalar points without reference to a
property entry.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ELAS4 EID K S1 S2 GE S
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ELAS4 42 6.2-3 2
Field Contents
No default (Real)
S Stress coefficient
Comments
1. S1 or S2, but not both, may be blank or zero indicating a constrained coordinate.
2. Element identification numbers should be unique with respect to all other element
identification numbers.
3. This single entry completely defines the element since no material or geometric properties
are required.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.
6. The element force of a spring is calculated from the equation: F = k * (u1 – u2)
Where, k is the stiffness coefficient for the scalar element and u1 is the displacement of
the first degree-of-freedom listed on the CELAS entry. Element stresses are calculated
from the equation: s = S * F, where, S is the stress coefficient as defined above.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
XS YS ZS
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C FAST 22 1 PROP 2 3
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default
SHIDA, SHIDB Element identification numbers of shells defining fastener ends A and
B, respectively. Required when CTYPE = ELEM.
(Integer > 0)
(Integer > 0)
XS, YS, ZS Coordinates of point that defines the location of the fastener in the
basic coordinate system. It is an alternative way of specifying the
location of GS.
(Real)
Comments
1. CFAST defines a flexible connection between two shell surface patches. An internally-
generated CBUSH element will be created automatically for a CFAST, and the end points
of this bushing will be connected to the grids of corresponding shell elements. Then the
2. A CFAST element connects Shell A and Shell B. An internal CBUSH is generated for the
CFAST and supported by fictitious auxiliary points. Auxiliary points, in turn, are
constrained by corresponding shell grids. (To have a clear view, only one of these kind of
constraint relationships is shown with dotted lines).
3. The end points of the internally-generated CBUSH element are defined from GS, GA, and
GB (not all are required). If GA or GB is not specified, they are generated from the normal
projection of GS onto the surface patches. If GA and GB (or, GA only) are (is) specified,
they take precedence over GS in defining the respective end points (If only GA is
specified, then GA is used as a normal projection point (similar to GS) to generate GB on
Shell B). Also, their locations will be corrected so that they lie on surface patch A and B,
respectively. If neither GS nor GA is specified, then (XS, YS, and ZS), in the basic
coordinate system, must be specified. The length of the connector is the distance
between projected points GA and GB.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Examples
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
X1, X2, Components of the orientation vector, from GA, in the displacement
X3 coordinate system at GA.
G0 Alternate method to supply orientation vector, using grid point G0. Direction
of orientation vector is from GA to G0.
Alternatively: FLIP – reverses the direction of the gap axis (See comment
5).
Comments
1. For linear subcases, the CGAP element will produce a linear stiffness matrix which remains
linear with the initial stiffness. The stiffness used depends on the value for the initial gap
opening (U0 field in the PGAP entry).
2. The gap element coordinate system is defined by one of the following methods:
Prescribed CID: If the coordinate system CID is specified, the element coordinate
system is established using that coordinate system. In this case, the element x-axis is
in the coordinate system’s 1-direction, and the y-axis is in the coordinate system’s 2-
direction (for rectangular coordinate systems; the 1-direction is the x-direction and
the 2-direction is the y-direction). The orientation vector will be ignored in this case.
CID field blank: If the CID field is blank and the grid points GA and GB are not
coincident (distance from GA to GB > 10-4), then the line GA-GB is the element x-axis
and the orientation vector lies in the x-y plane (as with the CBEAM element).
FLIP option: the x-axis of the gap coordinate system is reversed with respect to the
default orientation described above. This option is useful when meshes of bodies A
and B overlap, rather than have a gap between them (See comment 5).
For gaps with coincident nodes (the distance between GA and GB < 1.0e-4), the gap
coordinate system must be specified.
3. In typical applications, leaving the CID field blank is appropriate when the nodes GA and
GB obstacle are initially separated. If the meshes of bodies A and B overlap, then a
coordinate system CID should be specified or the FLIP option should be used as discussed
below.
5. The FLIP option in the CID field is useful when meshes of bodies A and B overlap, rather
than have a gap between them. In such cases, the defaults gap axis vector GA-GB
would be opposite to the overall direction from body A to body B and therefore would
produce a "gluing" effect, rather than a resolution of the contact condition. The FLIP
option reverses the default gap direction so that the gap axis correctly points from the
bulk of body A towards body B in such cases. The effect of FLIP is equivalent to defining
a coordinate system with axis 1 pointing in direction GB-GA, rather then GA-GB.
Aside from setting the FLIP option to correctly resolve the cases with initial penetration,
U0 on the PGAP card needs to be properly set to a negative value, or an AUTO option
needs to be used in the U0 field.
Alternatively, FLIP can be used to define a simple cable element. If such an arrangement
is used, then it should be noted that:
a) F0 corresponds to a pair of forces acting on the ends of the cable (pointing inwards),
while U0 corresponds to pre-existing “slack” or extra length in the cable.
b) Gap “open” status corresponds to the cable being “shortened”, while “closed” gap
status corresponds to the cable being “elongated.”
c) Positive gap force reported in the results corresponds to the cable being in tension
(note that the force also includes the effect of F0).
7. If neither coordinate system nor orientation vector are specified, the orientation vector is
defined automatically as a vector aligned with the axis of the basic coordinate system
that makes the largest angle with the gap direction (gap x-axis).
8. Initial gap openings are specified on the PGAP entry and not derived from the separation
distance between GA and GB.
9. Forces, which are requested with the FORCE card in the I/O Options or Subcase
Information sections, are output in the element coordinate system. F x is positive for
compression.
10. For more information on using nonlinear gaps, refer to the Nonlinear Quasi-Static Analysis
section of the User's Guide.
11. Heat transfer properties can be defined for Gap elements using the PGAPHT bulk data
entry.
Description
Defines a node-to-obstacle gap element. The obstacle may be an element face or a patch of
nodes.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
257
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TYP Character string indicating the type of obstacle on the B end of CGAPG
(opposing node GA):
X1, X2, X3 Components of the orientation vector, from GA, in the displacement
coordinate system at GA.
PUSHOUT – for obstacles defined as solid elements using ELIDB, gap axis is
automatically defined so as to create “pushout” force that prevents GA
GB# Grid identification number of the grid surface patch on the B (obstacle)
end of the CGAPG element. GB1 to GB3 are required.
G4 For solid element ELIDB: identification number of the TETRA grid point
located at the corner, not on the face being loaded. This is used for
TETRA elements only. It is required data if G1 has been specified.
1. CGAPG defines a contact element between a point and an obstacle. The obstacle may be
defined as a patch of nodes or as an element face. See figure below:
2. The gap element coordinate system is defined via one of the following methods:
Prescribed CID: if the coordinate system CID is specified, the element coordinate
system is established using that coordinate system. In this case, the element x-axis is
in the coordinate system’s 1-direction, and the y-axis is in the coordinate system’s 2-
direction (for rectangular coordinate systems; the 1-direction is the x-direction and
the 2-direction is the y-direction). The orientation vector will be ignored in this case.
CID field blank: if the CID field is blank and the grid point GA does not lie on the
element face or node patch (distance from GA to the surface > 10-4), then the x-axis
is defined along the shortest distance from GA to the element face or node patch. The
orientation of gap x-axis points from GA towards the patch or element face (see figure
above). The orientation vector defines the x-y plane of the gap coordinate system
(similarly as for the CGAP element).
If the grid point GA lies on the element face or node patch (distance from GA to the
surface < 10-4), then CID must be prescribed.
FLIP option: the x-axis of the gap coordinate system is reversed with respect to the
default orientation described above. This option is useful when meshes of bodies A
and B overlap rather than have a gap between them (See comment 5).
PUSHOUT option: the x-axis of the gap coordinate system is oriented so as to prevent
GA from entering interior of body B. This is only available for obstacles defined as 3D
solid elements with ELIDB.
In cases when GA does not have a direct normal projection onto the obstacle B, and
the "shortest distance" projection is used (GAPGPRJ set to SHORT on the GAPPRM
card), the pushout force is oriented along the shortest distance line, yet with the
orientation aligned with the normal vector.
Note that for faces on solid elements, the default normal is pointing inwards, so that it
is the PUSHREVN option that will prevent penetration (PUSHOUT is a more
straightforward option to use on solid faces).
3. In typical applications, leaving the CID field blank is appropriate when the node GA and
the obstacle are initially separated; that is, there is a gap between respective bodies A
and B (see figure above). If the meshes of bodies A and B overlap, then a coordinate
system CID should be specified (See comment 4). Alternatively, and usually more
intuitively, one of the FLIP, PUSHOUT, PUSHNORM, or PUSHREVN options may be used.
4. When prescribing the gap coordinate system CID, it is essential to assure that the
resulting gap x-axis points in the general direction from body A (the one associated with
node GA) towards body B (the one associated with element ELIDB or patch GB#). This
assures that the gap element will act to prevent the contact/overlap of these bodies. An
incorrect orientation of the x-axis will result in the gap element being ineffective or can
even act to "glue" the bodies together rather than prevent their overlap. The solver
checks for such misalignment and prints respective error and warning messages. For more
information, see the GAPPRM bulk data card.
5. The FLIP option in the CID field is useful when the meshes of bodies A and B overlap
rather than have a gap between them. In such cases, the default gap axis vector would
be opposite to the overall direction from body A to body B, and therefore would produce a
"gluing" effect rather than a resolution of the contact condition. The FLIP option reverses
the default gap direction so that the gap axis correctly points from the bulk of body A
towards body B in such cases.
Aside from setting the FLIP option or prescribing CID to correctly resolve the cases with
initial penetration, U0 on the PGAP card needs to be properly set to a negative value or
an AUTO option needs to be used in the U0 field.
6. If neither coordinate system CID nor orientation vector is specified, the orientation vector
is defined automatically as a vector aligned with the axis of the basic coordinate system
that makes the largest angle with the gap direction (gap x-axis).
7. GB# are required when TYP is QUAD or TRIA. At least 3, and at most 8, grid IDs may be
specified for GB#. Triangular and quadrilateral element definition sequences apply for the
order of GB# (see below). Missing mid-side nodes are allowed.
8. If ELIDB represents a solid element and G1, G3/G4 fields are blank, then the element face
closest to the grid GA is selected as the respective obstacle face.
Note that if the meshes are overlapping (such as in the case of initial penetration), this
option should not be used, and the contact face should be explicitly prescribed.
Otherwise, the face closest to GA may be an internal face within the solid body, rather
than the outside surface of body B.
9. G1 and G3 are ignored for shell elements (TRIA3, QUAD4, TRIA6 and QUAD8).
10. For triangular faces of PENTA elements, G1 is an identification number of a corner grid
point that is on the face being loaded and the G3 or G4 field is left blank. For faces of
TETRA elements, G1 is an identification number of a corner grid point that is on the face
being loaded and G4 is an identification number of the corner grid point that is not on the
face being loaded. Since a TETRA has only four corner points, this point, G4, is unique
and different for each of the four faces of a TETRA element.
11. For the quadrilateral face of the PYRA element, G1 is an identification number of a corner
grid point on the face and the G3 or G4 field is left blank. For the triangular faces, G1 and
G3 must specify the grids on the edge of the face that borders the quadrilateral face and
the grids must be ordered so that they define an inward normal using the right hand rule.
12. The element coordinate system does not rotate as a result of deformation.
13. Initial gap openings are specified on the PGAP entry and not derived from the separation
distance between GA and GB, unless the AUTO option is used on the PGAP card.
14. Gap forces, which are requested with the FORCE card in the I/O Options or Subcase
Information sections, are output in the gap element coordinate system. F x is positive for
compression.
15. For linear subcases, the CGAPG element will produce a linear stiffness matrix which
remains linear with the initial stiffness. The stiffness used depends on the value for the
initial gap opening (U0 field in the PGAP entry).
16. For more information on using nonlinear gaps, refer to the Nonlinear Quasi-Static Analysis
section of the User's Guide.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C GASK6 71 4 3 4 5 6 7 8
Field Contents
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
3. If the user-prescribed node numbering on the bottom and top faces is reversed as
compared to the sequence shown above, then the nodes are renumbered to produce
right-handed orientation of numbering. This is accomplished by swapping nodes G1 with
G3 and G4 with G6. In such cases, the element local coordinate system will be built on
the renumbered node sequence.
4. The element coordinate system for the CGASK6 element is defined below.
The local 3-direction (the gasket material thickness direction in default) is defined as the
simple average of the unit normal directions on the top and bottom surfaces of the
element. After the local 3-direction is defined, a local 1-2 plane is generated accordingly.
Then, the local 1-direction and 2-direction are defined as follows: Project the basic x-axis
onto the local 1-2 plane, and set it to be the default local 1-direction. If the basic x-axis
is within 0.1° difference as the local 3-direction, project the basic z-axis onto the local 1-
2 plane and set it to be the local 1-direction. The local 2-direction is determined then.
5. The gasket material coordinate system is the same as the element coordinate system in
default and can be defined as a prescribed system through PGASK entry.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
G7 G8
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C GASK8 71 4 3 4 5 6 7 8
9 10
Field Contents
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2. Grid points G1, …, G4 must be given in consecutive order at the bottom face of the
gasket element. G5, …, G8 must be on the top face with G5 opposite G1, G6 opposite G2,
and so on.
3. If the user-prescribed node numbering on the bottom and top faces is reversed as
compared to the sequence shown above, then the nodes are renumbered to produce
right-handed orientation of numbering. This is accomplished by swapping nodes G1 with
G3 and G5 with G7. In such cases, the element local coordinate system will be built on
the renumbered node sequence.
4. The element coordinate system for the CGASK8 element is defined below.
The local 3-direction (the gasket material thickness direction in default) is defined as the
simple average of the unit normal directions on the top and bottom surfaces of the
element. After the local 3-direction is defined, a local 1-2 plane is generated accordingly.
Then, the local 1-direction and 2-direction are defined as follows: Project the basic x-axis
onto the local 1-2 plane, and set it to be the default local 1-direction. If the basic x-axis
is within 0.1° difference as the local 3-direction, project the basic z-axis onto the local 1-
2 plane and set it to be the local 1-direction. The local 2-direction is determined then.
5. The gasket material coordinate system is the same as the element coordinate system in
default and can be defined as a prescribed system through PGASK entry.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C GASK12 71 4 3 4 5 6 7 8
9 10 11 12 13 14
Field Contents
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2. Corner grid points G1, …, G3 must be given in consecutive order at the bottom face of the
gasket element. Corner grid points G4, …, G6 must be on the top face with G4 opposite
G1, G5 opposite G2, and so on.
Edge grid points G7, …, G9 must be given in consecutive order at the bottom face of the
gasket element. Edge grid points G10, …, G12 must be on the top face with G10 opposite
G7, G11 opposite G8, and so on.
3. If the user-prescribed node numbering on the bottom and top faces is reversed as
compared to the sequence shown above, then the nodes are renumbered to produce
right-handed orientation of numbering. This is accomplished by swapping nodes G1 with
G3 and G4 with G6. In such cases, the element local coordinate system will be built on
the renumbered node sequence.
4. The element coordinate system for the CGASK12 element is defined below.
The local 3-direction (the gasket material thickness direction in default) is defined as the
simple average of the unit normal directions on the top and bottom surfaces of the
element. After the local 3-direction is defined, a local 1-2 plane is generated accordingly.
Then, the local 1-direction and 2-direction are defined as follows: Project the basic x-axis
onto the local 1-2 plane, and set it to be the default local 1-direction. If the basic x-axis
is within 0.1° difference as the local 3-direction, project the basic z-axis onto the local 1-
2 plane and set it to be the local 1-direction. The local 2-direction is determined then.
5. The gasket material coordinate system is the same as the element coordinate system in
default and can be defined as a prescribed system through PGASK entry.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
G15 G16
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C GASK16 71 4 3 4 5 6 7 8
9 10 11 12 13 14 15 16
17 18
Field Contents
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2. Corner grid points G1, …, G4 must be given in consecutive order at the bottom face of the
gasket element. Corner grid points G5, …, G8 must be on the top face with G5 opposite
G1, G6 opposite G2, and so on.
Edge grid points G9, …, G12 must be given in consecutive order at the bottom face of the
gasket element. Edge grid points G13, …, G16 must be on the top face with G13 opposite
G9, G14 opposite G10, and so on.
3. If the user-prescribed node numbering on the bottom and top faces is reversed as
compared to the sequence shown above, then the nodes are renumbered to produce
right-handed orientation of numbering. This is accomplished by swapping nodes G1 with
G3 and G5 with G7. In such cases, the element local coordinate system will be built on
the renumbered node sequence.
4. The element coordinate system for the CGASK16 element is defined below.
The local 3-direction (the gasket material thickness direction in default) is defined as the
simple average of the unit normal directions on the top and bottom surfaces of the
element. After the local 3-direction is defined, a local 1-2 plane is generated accordingly.
Then, the local 1-direction and 2-direction are defined as follows: Project the basic x-axis
onto the local 1-2 plane, and set it to be the default local 1-direction. If the basic x-axis
is within 0.1° difference as the local 3-direction, project the basic z-axis onto the local 1-
2 plane and set it to be the local 1-direction. The local 2-direction is determined then.
5. The gasket material coordinate system is the same as the element coordinate system in
default and can be defined as a prescribed system through PGASK entry.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C HAC AB 71 4 3 4 5 6 7 8
9 10
Field Contents
$$------------------------------------------------------------------------------$
$$ $
$$ NASTRAN Input Deck Generated by HyperMesh Version : 8.0SR1 $
$$ Generated using HyperMesh-Nastran Template Version : 8.0sr1
$$ $
$$ Template: general $
$$ $
$$------------------------------------------------------------------------------$
$$------------------------------------------------------------------------------$
$$ Executive Control Cards $
$$------------------------------------------------------------------------------$
SOL 111
CEND
$$------------------------------------------------------------------------------$
$$ Case Control Cards $
$$------------------------------------------------------------------------------$
SET 1 = 1734
DISPLACEMENT = 1
$
$HMNAME LOADSTEP 1"Load2"
SUBCASE 1
LABEL= Load2
SPC = 4
FREQUENCY = 5
DLOAD = 2
$$------------------------------------------------------------------------------$
$$ Bulk Data Cards $
$$------------------------------------------------------------------------------$
BEGIN BULK
ALTDOCTAG "HqTD_ARNMI\S\pMpN13G;5oANN]l[enE7fmSbTJro20LOpNriZFOQfUk]
_`5hfS5ATf6pT7RXMjA3e@k_r^K?GP;?OeEbD0"
ADI0.1.0 2011-05-13T19:57:45 0of1 OSQA
ENDDOCTAG
Comments
1. Element identification numbers should be unique with respect to all other element
identification numbers.
2. Grid points G1 through G4 must be given in consecutive order about one quadrilateral
face. G5 through G8 must be on the opposite face with G5 opposite G1, G6 opposite G2,
and so on.
3. The edge points, G9 to G20 are optional. All or none of them may exist. The corner grid
points cannot be deleted. The edge points should be in the middle third of the edges.
5. The face consisting of grid points G1 through G4 and G9 through G12 is assumed to be in
contact with the structure.
6. The mass is lumped to the face formed by grid points G5 through G8 and G17 through G20
and defined to be in contact with the fluid. The opposite face has no mass contribution
due to the absorber element. Also, the face in contact with the fluid has only
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
Comments
2. EID2 identifies the heat conduction element associated with this surface element.
1D 2D 3D
CBAR CQUAD4 CHEXA
CBEAM CQUAD8 CPENTA
CONROD CTRIA3 CPYRA
CROD CTIRA6 CTETRA
C onduction elements for heat transfer analysis
3. All conduction elements that are to have a boundary condition applied must be individually
identified with the application of a surface element entry CHBDYE.
Sides are numbered consecutively according to the order of the grid point numbers on the
3D element entry. The sides of 3D elements are either quadrilaterals or triangles. For
each element type, the side numbers are shown here:
2D elements have one side of type AREA (this is Side 1) and 3 or 4 sides of type LINE.
AREA type: Side 1 is that given by the right hand rule on the shell’s gird points.
LINE type: The second side (first line) is from grid point 1 to grid point 2, and the
remaining lines are numbered consecutively. The thickness of the line is that of the shell,
and the normal to the line is outward from the shell in the plane of the shell. Note that
midside nodes are ignored in the specification.
1D elements have one linear side (Side 1) with geometry that is the same as that of the
element and two POINT type sides, corresponding to the two points bounding the linear
element (first grid point side 2; second grid point side 3).
Boundary conditions (QBDY1) are applied to CHBDYE through reference of the EID.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C HEXA 71 4 3 4 5 6 7 8
9 10
Field Contents
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2. Grid points G1,…,G4 must be given in consecutive order about one quadrilateral face.
G5,…,G8 must be on the opposite face with G5 opposite G1, G6 opposite G2, and so on.
The edge points, G9 through G20, are optional. If any of the edge points are present,
they all must be used. The second continuation must not be present for the 8-noded
version of this element.
It is recommended that the edge points be placed near the middle of the edge.
C HEXA definition
3. If the user-prescribed node numbering on the bottom and top faces is reversed as
compared to the sequence shown above, then the nodes are renumbered to produce
right-handed orientation of numbering. This is accomplished by swapping nodes G1 with
G3 and G5 with G7. For 20-noded CHEXA, appropriate changes to mid-side node
numbering are also performed. In such cases, the element coordinate system will be built
on the renumbered node sequence.
4. Stresses are output in the material coordinate system. The material coordinate system is
defined on the referenced PSOLID entry. It may be defined as the basic coordinate
system (CORDM = 0), a defined system (CORDM = Integer > 0), or the element coordinate
system (CORDM = -1).
5. The element coordinate system for the CHEXA element is defined as follows:
R Joins the centroids of the faces described by the grid points G4, G1, G5, G8
and the grid points G3, G2, G6, G7.
S Joins the centroids of the faces described by the grid points G1, G2, G6, G5
and the grid points G4, G3, G7, G8
T Joins the centroids of the faces described by the grid points G1, G2, G3, G4
and the grid pints G5, G6, G7, G8.
The origin of the element coordinate system is at the intersection of these three vectors.
If the vectors do not all intersect at one point, then the average location of the
intersection points is used.
The element x-axis is the cross product of the element y-axis and the element z-axis.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C MASS1 45 4 653 2
Field Contents
2. Scalar points may be used for G1 and/or G2, (with a corresponding C1 and/or C2 of zero
or blank). If only scalar points and/or grounded terminals are involved, it is more efficient
to use the CMASS3 entry.
3. Element identification numbers should be unique with respect to all other element
identification numbers.
4. The two connection points (G1, C1) and (G2, C2) must not be coincident. Except in
unusual circumstances, one of them will be a grounded terminal with blank entries for Gi
and Ci.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.
6. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C MASS2 EID M G1 C1 G2 C2
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C MASS2 2 1.1 56 3
Field Contents
No default (Real)
2. Scalar points may be used for G1 and/or G2, (with a corresponding C1 and/or C2 of zero
or blank). If only scalar points and/or grounded terminals are involved, it is more efficient
to use the CMASS4 entry.
3. Element identification numbers should be unique with respect to all other element
identification numbers.
4. This single entry completely defines the element since no material or geometric properties
are required.
5. The two connection points (G1, C1) and (G2, C2) must be distinct. Except in unusual
circumstances, one of them will be a grounded terminal with blank entries for Gi and Ci.
6. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C MASS3 13 42 62
Field Contents
Comments
1. S1 or S2, but not both, may be blank or zero, indicating a constrained coordinate.
2. Element identification numbers should be unique with respect to all other element
identification numbers.
4. A scalar point specified on this entry need not be defined on an SPOINT entry.
Description
Defines a scalar mass element that is connected only to scalar points, without reference to a
property entry.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C MASS4 EID M S1 S2
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C MASS4 23 14.92 23
Field Contents
No default (Real)
Comments
1. S1 or S2, but not both, may be blank or zero, indicating a constrained coordinate. This is
the usual case.
4. A scalar point specified on this entry need not be defined on an SPOINT entry.
5. This single entry completely defines the element since no material or geometric properties
are required.
Description
Defines a beam element for multi-body dynamics solution sequence without reference to a
property entry.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
A I1 I2 J K1 K2
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
(Real)
(Integer > 0)
(Real)
J Torsional constant.
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2. The X-axis of the beam is always along the line connecting G1 and G2. The Z-axis of the
beam is determined based on the X-axis and the Y-axis provided by G3/X1, Y1, and Z1.
The beam coordinates must be aligned with the principal axes of the cross-section.
4. The transverse shear stiffness in planes 1 and 2 are (K1)AG and (K2)AG, respectively. If
a value of 0.0 is used for K1 and K2, the transverse shear flexibilities are set to 0.0 (K1
and K2 are interpreted as infinite).
Description
Defines a beam element for multi-body dynamic solution sequence without reference to a
property entry based on markers.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
A I1 I2 J K1 K2
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
(Integer > 0)
(Integer > 0)
(Real)
(Real)
J Torsional constant.
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2. The X-axis of the markers M1 and M2 should always be along the axis of the beam.
The beam coordinates must be aligned with the principal axes of the cross-section.
4. The transverse shear stiffness in planes 1 and 2 are (K1)AG and (K2)AG, respectively. If
a value of 0.0 is used for K1 and K2, the transverse shear flexibilities are set to 0.0 (K1
and K2 are interpreted as infinite).
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
"K" K1 K2 K3 K4 K5 K6
"B" B1 B2 B3 B4 B5 B6
"P" P1 P2 P3 P4 P5 P6
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
P 0 0 0 0 0 0
Field Contents
(Integer > 0)
(Integer > 0)
(Integer > 0)
(Integer > 0)
(Real)
K Stiffness specifier.
B Damping specifier.
P Preload specifier.
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
"P" P1 P2 P3 P4 P5 P6
KINT BINT
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
B 1 1 1 1 1 1
P 0 0 0 0 0 0
Field Contents
(Integer > 0)
(Integer > 0)
(Integer > 0)
(Integer > 0)
K Stiffness specifier.
B Damping specifier.
P Preload specifier.
Default = AKIMA
Default = AKIMA
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
CMBUSHE – Nonlinear Bushing Element for MBD using Expression Defined in MBVAR
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
"P" P1 P2 P3 P4 P5 P6
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
B 1 1 1 1 1 1
P 0 0 0 0 0 0
Field Contents
(Integer > 0)
(Integer > 0)
(Integer > 0)
(Integer > 0)
(Real)
K Stiffness specifier.
B Damping specifier.
P Preload specifier.
1. Element identification numbers must be unique with respect to all other element
identification numbers.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C MBUSHM EID M1 M2
"K" K1 K2 K3 K4 K5 K6
"B" B1 B2 B3 B4 B5 B6
"P" P1 P2 P3 P4 P5 P6
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C MBUSHM 1 12 13
P 0 0 0 0 0 0
Field Contents
(Integer > 0)
(Integer > 0)
(Integer > 0)
K Stiffness specifier.
(Real)
(Real)
B Damping specifier.
(Real)
(Real)
P Preload specifier.
(Real)
(Real)
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
"P" P1 P2 P3 P4 P5 P6
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
B 1 1 1 1 1 1
P 0 0 0 0 0 0
Field Contents
(Integer > 0)
(Integer > 0)
(Integer > 0)
(Integer > 0)
(Real)
K Stiffness specifier.
B Damping specifier.
P Preload specifier.
1. Element identification numbers must be unique with respect to all other element
identification numbers.
Description
CMSMETH defines the CMS method, frequency upper limit, number of modes, and starting
SPOINT ID to be used in a component mode synthesis solution. The eigenvalue solver is also
specified. In addition, preload as well as loads for reduction and residual vector generation
can be defined. Also, an ASCII file containing CELAS4 and CDAMP3 element data and/or their
corresponding design variable definitions can be generated for DMIG to allow the use of the
component modes in optimization runs.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
UB_FREQ Upper bound frequency for the eigenvalue analysis for the structural part.
If 0.0 or blank, no upper bound is used. See comments 3 and 4.
SPID The starting SPOINT ID to be used in DMIG matrix output for the
structural eigenmodes.
SOLVER The eigenvalue solver. Either blank or LAN for Lanzos. AMSES for
AMSES.
SHFSCL For vibration analysis, it is the estimate of the frequency of the first
flexible mode. See comment 12.
UB_FREQ_F Upper bound frequency for the eigenvalue analysis for the fluid part. If
0.0 or blank, no upper bound is used. See comments 3 and 4.
SPID_F The starting SPOINT ID to be used in DMIG matrix output for the fluid
eigenmodes.
If any boundary degrees of freedom are fixed and GPRC is set to YES, the
program will be terminated with an error.
PRELOAD PRELOAD flag indicates that a preload will be used in the CMS analysis
LOADSET LOADSET flag indicates that static load sets will be used in CMS analysis.
USETYPE RESVEC/REDLOAD/BOTH defines the use type for the load sets
RESVEC – the load set is used for generating residual vectors to improve
the modal space
LSIDi The load set IDs for generating residual vectors and/or reduced loads.
Default = S
DMIGDV DMIGDV flag indicates that an ASCII file containing CELAS4 and CDAMP3
element data and/or their corresponding design variable definitions is
generated for DMIG (see comment 13).
OUTOPT OUTOPT defines how design variable definitions are written for DMIG.
(see comments 13 to 17) If OUTOPT is:
1 – Only CELAS4 and CDAMP3 element data and PDAMP properties (if
any) are written. Design variable definitions are not written.
2 – All data from Option-1 and design variable definitions are written
(Default, see comment 14).
3 – All data from Option-2 and constraint (f1<f2) creation data are
written (see comment 15).
NMODE NMODE defines the number of design variables for ∆K/∆GE and ∆B in
CELAS4 and CDAMP3 (see comment 18).
If NMODE is not specified (the NMODE field is blank) then as many design
variables as the total number of modes are written.
Default: DVKUPFAC=0.1
DVGEUP Upper bound of ∆GE. This applies to all the design variables for ∆GE. If
DVGEUP is not specified (DVGEUP field is blank) then it is set to 2*DVBUP
by default (See comment 16).
Default: DVGEUP=2*DVBUP
DVBUP Upper bound of ∆B. This applies to all the design variables for ∆B. If
DVBUP is not specified (DVBUP field is blank) then it is set to 0.4 by
Default: DVBUP=0.4
Comments
1. This definition will be ignored unless referenced in the I/O Options section by a CMSMETH
run control.
2. Several methods are available for Component Mode Synthesis, these are: CB, CC, CBN,
GM and GUYAN (see descriptions below).
The first two methods (CB and CC) are used for generating flexible bodies for use with
multi-body dynamics analysis software, such as Altair’s MotionSolve.
The remaining methods (CBN, GM and GUYAN) are used primarily to generate external
superelements (stored in DMIG format) for use in subsequent finite element analyses.
CB – Craig-Bampton formulation
CC – Craig-Chang formulation
GUYAN is the same as CBN without including structural eigenmodes; when GUYAN is used,
UB_FREQ & NMODES are ignored.
3. UB_FREQ, NMODES, UB_FREQ_F and NMODES_F cannot all be blank. Additionally, when
structural elements are present in the model, UB_FREQ and NMODES cannot both be
blank, and when fluid elements are present in the model, UB_FREQ_F and NMODES_F
cannot both be blank.
4. When UB_FREQ = 0.0 and NMODES = 0, this is a special case where no structural
eigenmodes will be included in CMS mode generation. If both UB_FREQ and NMODES are
specified, lowest NMODES below UB_FREQ will be accepted as structural SPOINTs.
Similarly things are applied to fluid part.
5. If PARAM, EXTOUT, DMIGPCH (or DMGBIN) is defined when using the CB method, then a
DMIG matrix corresponding to the reduced stiffness and mass matrices will be output.
The stiffness and mass corresponding to the eigenmodes will be assigned to the
generated SPOINTs.
6. The SPOINT IDs of the structure and fluid should have distinct IDs. Any fluid SPOINT ID
cannot be in between structural SPOINT IDs.
7. When PARAM,EXTOUT is used to output DMIG matrices, then it is possible to disable the
8. The nodal flexh3d file output from the CBN method can be used as the DMIG input (using
ASSIGN,H3DDMIG). In this way, the model set output in flexh3d file will be recovered as
the interior points of the DMIG matrix in the residual structure run. The displacements of
these interior points will be included in the output.
9. AMPFFACT is used to increase the accuracy of the eigenvalue and eigenvectors at the
expense of slightly longer run times. It is recommended to use higher values of
AMPFFACT for solid structures like engine blocks and suspension components. If
AMPFFACT is not specified by you and the model contains a large number of solid
elements, then the value of AMPFFACT is automatically reset to 10.
10. The mass properties of the super element (Mass, Center of Gravity, and Moments of
Inertia) are written to the H3D file. In the residual run, these mass properties are
included in the mass properties of the structure printed in the .out file.
11. The USETYPE field should always be set to BOTH or blank for flexible body generation
(METHOD=CB or CC, see comment 2).
13. If you define the DMIGDV optional continuation card, a text file (ASCII)
filename_dmig_dv.inc is created after the run. You can include this file in the original
input deck to study how changes in the eigenvalues/damping of superelements affect the
performance of the residual structure.
14. In addition to the data included in option 1, the ASCII file now also contains design
variable definitions. These design variables can control available eigenvalues, structural
damping, and viscous damping of the superelement. You can set up an optimization
problem by including this file in the original input deck.
15. In addition to the data included in option 2, the ASCII file now includes data required for
the creation of constraints. These constraints ensure that the eigenvalue of the nth
mode is less than the eigenvalue of the (n+1)th mode during optimization.
16. The lower bound of ∆K, ∆B and ∆GE is set such that K, B and GE are always greater than
or equal to zero.
17. The DMIGDV continuation line works only for METHOD = GM (General Modal formulation) in
field 3 of CMSMETH (See comment 2).
18. Where, ∆K, ∆GE and ∆B represent increments/decrements to the eigenvalues (K), damping
coefficients (GE) and scalar damping values (B) respectively. You are required to include
the .h3d file containing the values of K, GE and B using ASSIGN, H3DDMIG.
19. For further information on creating flex bodies for third party software, refer to Coupling
OptiStruct with Third Party Software in the User’s Guide.
Description
Defines a spring damper element without reference to a property entry for multi-body solution
sequence.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
K Stiffness value.
(Integer > 0)
(Integer > 0)
B Damping value.
PF Preload force.
TYPE Type
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2. The spring damper force is along the line segment connecting the grids G1 and G2.
(a) For a translational spring, OptiStruct calculates the length between the two grid
points (G1, G2) of the spring damper for the value of L.
Description
Defines a spring damper element without reference to a property entry for multi-body solution
sequence.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
AKIMA 1
Field Contents
(Integer > 0)
(Integer > 0)
(Integer > 0)
PF Preload force.
TYPE Type.
Default = AKIMA
Default = AKIMA
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2. The spring damper force is along the line segment connecting the grids, G1 and G2.
CMSPDPE – Nonlinear Multi-body Spring Damper Element using Expression defined in MBVAR
Description
Defines a spring damper element without reference to a property entry for multi-body solution
sequence.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
(Integer > 0)
PF Preload force.
TYPE Type.
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2. The spring damper force is along the line segment connecting the grids G1 and G2.
Description
Defines a spring damper element without reference to a property entry for multi-body solution
sequence based on marker.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
K Stiffness value.
(Integer > 0)
(Integer > 0)
B Damping value.
PF Preload force.
TYPE Type.
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2. The spring damper force is along the line segment connecting the marker M1 and M2.
Description
Defines a spring damper element without reference to a property entry for multi-body solution
sequence.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
(Integer > 0)
PF Preload force.
TYPE Type.
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2. The spring damper force is along the line segment connecting the grids G1 and G2.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
4.8 28.6
28.6 28.6
Field Contents
(Integer > 0)
(Integer > 0)
(Integer > 0)
(Real)
Comments
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ONM2 EID G C ID M X1 X2 X3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ONM2 2 15 49.7
Field Contents
M Mass value.
No default (Real)
X1, X2, X3 Offset distance from the grid point to the center of gravity of the mass
in the coordinate system defined by CID, unless CID = -1, in which case
X1, X2, and X3 are the coordinates (not offsets) of the center of gravity
of the mass in the basic coordinate system.
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
3. The form of the inertia matrix about its c.g. is taken as:
where M =
4. If CID = -1, then the offsets are computed internally as the difference between the grid
point location and X1, X2, and X3. The grid points may be defined in a local coordinate
system, in which case the values of must be in a coordinate system that parallels the
basic coordinate system.
5. If CID > 0, then X1, X2, and X3 are defined by a local Cartesian system, even if CID
references a spherical or cylindrical coordinate system.
Description
The CONNECT bulk data entry can be used to define equivalence for all degrees of freedom of
grid points of two different parts within a specified tolerance. The tolerance is defined as the
maximum distance between two grid points within which equivalence is allowed. Two formats
can be used to either select all grid points or a few grid points for equivalence.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Alternate Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Alternate Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
name_a Name of a part selected for equivalencing. Part “name_a” is the reference
part. All grid points in part “name_a” are considered during the search; if
OptiStruct finds grid points in part “name_b” within the specified maximum
distance (tol), then such grid point pairs are equivalent.
(Character String)
name_b Name of a part selected for equivalencing. All grid points in part “name_a” are
considered during the search; if OptiStruct finds grid points in part “name_b”
within the specified maximum distance (tol), then such grid point pairs are
equivalent.
(Character String)
tol Specifies the numeric value defining the maximum distance between two grid
points to allow equivalence. All grid points in part “name_a” are considered
during the search; if OptiStruct finds grid points in part “name_b” within the
specified maximum distance (tol), then such grid point pairs are equivalent.
GRID GRID flag indicating that a list of grid point ID’s is to follow. These grid point
locations are used to define locations to search for matching nodes.
GID# Identification numbers of grid points that define locations at which a search
for matching nodes is conducted. GID# do not need to belong to either part
“name_a” or part “name_b”.
(Integer > 0)
Comments
1. Parts can be connected in two different ways, using the CONNECT entry or by using rigid
elements. The RELOC and INSTNCE entries can be used to position the part appropriately
within the full model and the CONNECT entry or rigid elements can be used to connect the
requisite number of grid points of one part to the other.
2. In an alternate form, grid point ID’s can be specified anywhere in the model, it is not
mandatory for a grid point ID to belong to a part. Equivalencing takes place between any
matching grids in both parts if they coincide with the location of any grid in the list.
3. Searches defined by this entry are performed after all parts are located at their final
positions.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ONROD 2 16 17 4 269
Field Contents
(Integer > 0)
(Integer > 0)
(Real)
J Torsional constant.
(Real)
(Real)
(Real)
Comments
1. For structural problems, MID may reference only a MAT1 material entry. For heat transfer
problems, MID may reference only a MAT4 material entry.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ONTAC C TID PID/ SSID MSID MORIENT SRC HDI ADJUST C LEARANC E
T TYPE/ S
MU1
DISC RET
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ONTAC T 5 SLIDE 7 8
N25
Field Contents
(Integer > 0)
(Integer > 0)
(Integer > 0)
(Integer > 0)
MORIENT Orientation of contact “pushout” force from master surface. This only
applies to masters that consist of shell elements or patches of grids.
Masters defined on solid elements always push outwards irrespective of
this flag.
NORM – Contact force is oriented along the vector normal to the master
surface.
SRCHDIS Search distance criterion for creating contact condition. When specified,
only slave nodes that are within SRCHDIS distance from master surface
will have contact condition checked.
Default = twice the average edge length on the master surface. For
FREEZE contact, half the average edge length. (Real > 0 or blank)
ADJUST Adjustment of slave nodes onto the master surface at the start of a
simulation.
Default = NO.
NO – no adjustment.
AUTO – A real value equal to 5% of the average edge length on the
master surface is internally assigned as the depth criterion (see comment
10).
Real > 0.0 – value of the depth criterion which defines the zone in
which a search is conducted for slave nodes (for which contact elements
have been created). These slave nodes (with created contact elements)
are then adjusted onto the master surface. The assigned depth criterion
is used to define the searching zone in the pushout direction (see
comment 10).
Integer > 0 – identification number of a SET entry with TYPE = “GRID”.
Only the nodes on the slave entity which also belong to this SET will be
selected for adjustment.
Note: See comment 10 for more information.
CLEARANCE Prescribed initial gap opening between master and slave, irrespective of
the actual distance between the nodes (see comment 11).
2. The slave entity (SSID) always consists of grid nodes. It may be specified as:
DISCRET = N2S is recommended if the slave entity is a set of grids (nodes) or a set of
solid elements.
5. Prescribing TYPE=FREEZE enforces zero relative motion on the contact surface – the
contact gap opening remains fixed at the original value and the sliding distance is forced
to be zero. Also, rotations at the slave node are matched to the rotations of the master
patch. The FREEZE condition applies to all respective contact elements, no matter
whether open or closed.
6. Prescribing MU1 directly on the CONTACT card allows for simplified specification of
frictional contacts. Note that this implies MU2=MU1, unless MU2 is specified explicitly on
the CONTPRM card. Also note that the value of MU1 prescribed on the CONTACT card
must be less than 1.0 – to specify higher values of static coefficient of friction, PCONT
card must be used.
If FRIC is not explicitly defined on the PCONTX/PCNTX# entries, the MU1 value on the
CONTACT or PCONT entry is used for FRIC in the /INTER entries for Geometric Nonlinear
Analysis. Otherwise, FRIC on PCONTX/PCNTX# overwrites the MU1 value on CONTACT/
PCONT.
7. MORIENT defines the master pushout direction, which is the direction of contact force
that master surface exerts on slave nodes.
It is important to note that, in most practical applications, leaving this field blank will
provide correct resolution of contact, irrespective of the orientation of surface normals.
Only in cases of master surfaces defined as shells or patches of grids, and combined with
initial pre-penetration, is MORIENT needed.
By default, MORIENT is ignored for solid elements – it applies only to master surfaces that
consist of shell elements or patches of grids. (Master surfaces defined as faces of solid
elements always push outwards, irrespective of the surface normals, or whether the
contact gap is initially open or closed. See comment 7 for additional options).
a) In default behavior (OPENGAP), the pushout direction is defined using the assumption
that the gap between slave and master is initially open, and the contact condition
should prevent their contact (gap “padding” GPAD from the PCONT card is ignored in
defining the pushout direction – this direction is based strictly on the positions of
master and slave nodes).
c) With the NORM option, the pushout force is oriented along the normal vector to the
master surface. (Note that the surface normal may be reversed relative to the default
normal to a shell element if a FLIP flag is present on the master SURF definition. This
behavior corresponds to that of the reverse normals checkbox on the contactsurfs
panel in HyperMesh). In cases when the slave node does not have a direct normal
projection onto the master surface, and the "shortest distance" projection is used
(GAPGPRJ set to SHORT on the GAPPRM card), the pushout force is oriented along the
shortest distance line, yet with the orientation aligned with the normal vector.
8. By default, MORIENT does not apply to masters that are defined on solid elements – such
masters always push outwards. This can be changed by choosing
CONTPRM,CORIENT,ONALL which extends the meaning of MORIENT to all contact
surfaces. In which case, it should be noted that the default normal is pointing inwards
unless a FLIP flag appears on the master SURF definition for surfaces on solid elements,
making the surface normal point outwards. (When creating contact surfaces in
HyperMesh, this behavior corresponds to that of the reverse normals checkbox on the
contactsurfs panel).
9. Presently one CONTACT element is created for each slave node. This assures reasonably
efficient numerical computations without creating an excessive number of contact
elements. However, this may require special handling in some cases, such as when a
master surface wraps around the slave set. In such cases, switching the role of slave
and master may be recommended. Alternatively, multiple CONTACT interfaces can be
Figure 6: Special case - Master surface wraps around a slave node set
10. The adjustment of slave nodes doesn’t create any strain in the model. If DISCRET=N2S is
selected, it is treated as a change in the initial model geometry. If DISCRET=S2S is
selected, it is treated as a change in the initial contact opening/penetration.
If a node on the slave entity lies outside the projection zone of the master surface, it will
always be skipped during adjustment since no contact element has been constructed for
it.
Contact interface padding will be accounted for during the nodal adjustment. If the
MORIENT field is “OPENGAP” or “OVERLAP” while the GPAD field in the referred PCONT
entry is “NONE” or zero, the nodal adjustment will be skipped, since for “OPENGAP” or
“OVERLAP” there is no way to decide the master pushout direction if slave nodes are
adjusted to be exactly on the master face.
If different contact interfaces involve the same nodes, nodal adjustment definitions are
processed sequentially in the order of identification numbers of the contact interfaces.
Care must be taken to avoid conflicts between the nodal adjustments; otherwise, contact
element errors or lack of compliance may occur.
Depth Criterion
The depth criterion (A non-negative real value for ADJUST) is used to define the searching
zone for adjustment, as shown in Figure 7. This searching zone is created in the pushout
direction up to a distance equal to the value of the ADJUST field. The slave nodes within
the searching zone (with defined contact elements) are then considered for adjustment
based on the rules specified within this comment (Comment 10).
c) If the ADJUST field is set to an integer value (the identification number of a grid SET
entry), the nodes shared by the slave entity and the grid SET will be checked for
contact creation, that is, SRCHDIS will be ignored for these nodes, and then adjusted if
a projection is found. The nodes belonging to the grid SET but not to the slave entity
will be simply ignored.
11. Using CLEARANCE overrides the default contact behavior of calculating initial gap opening
from the actual distance between Slave and Master. CLEARANCE is now equal to the
distance that Slave and Master have to move towards each other in order to close the
contact. Negative value of CLEARANCE indicates that the bodies have initial pre-
penetration.
Note:
1. CLEARANCE cannot be used in conjunction with PID of PCONT entry. In such a case,
clearance must be specified on the PCONT entry.
2. The CLEARANCE field value on the CONTACT entry will be ignored for
ANALYSIS=NLGEOM subcases
12. CONTACT models an interface between a master surface and a set of slave grid points. A
grid point can be at the same time as a slave and a master node. Each slave grid point
can impact each master segment; except if it is connected to the impacted master
segment. A grid point can impact on more than one segment. A grid point can impact on
the two sides, on the edges, and on the corners of each segment. The contact uses a
fast search algorithm without limitations.
The main limitations of this interface follow: a) the time step in an explicit analysis is
reduced in case of high impact speed or contacts with small gap; b) the contact may not
work properly if used with a rigid body at high impact speed or rigid body with small gap;
c) the contact does not solve edge to edge contact.
13. Additional control can be applied to the CONTACT definition in geometric nonlinear
subcases through CONTPRM and PCONTX. These definitions are ignored in all other
subcases. A geometric nonlinear subcase is one that has an ANALYSIS = NLGEOM entry
in the subcase definition.
14. The slave entity (SSID) always consists of grid nodes. It may be specified as:
18. Thermal-structural analysis problems involving contact are fully coupled since contact
status changes thermal conductivity. Refer to Contact-based Thermal Analysis in the
User’s Guide for more information.
Description
Defines the default properties of all contacts and sets parameters that affect all contacts.
The default values set here can be overridden by values explicitly specified on PCONT,
PCONTX, and CONTACT cards.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PARAM5 VALUE5
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
Name Values
GPAD “Padding” of master or slave objects to account for additional layers, such
as shell thickness, and so on. This value is subtracted from contact gap
opening as calculated from location of nodes. See comment 1.
CONTGAP Create a bulk data file that contains internally created node-to-surface
contact elements represented as CGAPG elements. The file name is:
filename_root.contgap.fem. See comment 6.
CORIENT Indicates whether the master orientation field MORIENT on the CONTACT
card applies to all surfaces or if it excludes solid elements.
Name Values
(Real > 0)
(Real > 0)
Default = 0 (Integer = 0, …, 2)
0 - No deletion.
1 - When all of the elements (shells, solids) associated to one segment are
deleted, the segment is removed from the master side of the interface.
Additionally, non-connected nodes are removed from the slave side of the
interface.
2 - When a shell or a solid element is deleted, the corresponding segment
is removed from the master side of the interface. Additionally, non-
connected nodes are removed from the slave side of the interface.
0 - No action.
1 - Deactivation of stiffness on nodes.
2 - Deactivation of stiffness on elements.
3 - Change slave node coordinates to avoid small initial penetrations.
4 - Change master node coordinates to avoid small initial penetrations.
5 - Gap is variable with time but initial gap is slightly de-penetrated as
follows:
CORIENT Indicates whether the master orientation field MORIENT on the CONTACT
card applies to all surfaces, or if it excludes solid elements.
NO - No filter is used.
SIMP - Simple numerical filter.
PER - Standard -3dB filter with filtering period.
CUTF - Standard -3dB filter with cutting frequency.
FFAC
IGNORE Flag to ignore slave nodes if no master segment is found for TIE contact
(See comment 18).
Default = 1 (Integer = 0, 1, 2)
Default = 0 (Integer = 0, 1)
IEDGE Flag for edge generation from slave and master surfaces.
NO – No edge generation.
FANG Feature angle for edge generation in degrees (Only with IEDGE = FEAT).
CONST - Gap is constant and equal to GAP (See comments 11 and 12).
Default = 0 (Integer = 0, …, 5)
(Real > 0)
1. The initial gap opening is calculated automatically based on the relative location of slave
and master nodes (in the original, undeformed mesh). To account for additional material
layers covering master or slave objects (such as half of shell thickness), the GPAD entry
can be used. GPAD option THICK automatically accounts for shell thickness on both sides
of the contact interface (this also includes the effects of shell element offset ZOFFS or
composite offset Z0).
2. Option STIFF=AUTO determines the value of normal stiffness for each contact element
using the stiffness of surrounding elements. Additional options SOFT and HARD create
respectively softer or harder penalties. SOFT can be used in cases of convergence
difficulties and HARD can be used if undesirable penetration is detected in the solution.
7. The CONTACT capability in NLSTAT solution is designed to correctly resolve initial pre-
penetration, such as happens in press fit, and so on. This usually works reliably with
correct identification of Master and Slave surfaces. However, in some cases users create
contact surfaces by property for convenience, which results in contact surfaces
enveloping the entire solid bodies. Also, sometimes the Slave and Master receive the
same ID, which is known as self-contact (and is not a recommended practice, in spite of
the convenience factor). In such cases, it is possible to encounter false self-
penetrations, as illustrated below:
Apart from correctly identifying potential Slave and Master sets, a possible remedy to
avoid such situations is to make sure that SRCHDIS is smaller than minimum thickness of
the solid bodies which are enveloped by self-contacting surfaces.
Note that SFPRPEN affects only surfaces that actually have self-penetration, as in a case
where the Slave Node and Master Face belong to the same contact set or surface. On
properly defined, disjoint Slave and Master surfaces, the initial pre-penetrations will be
resolved irrespective of this parameter.
8. Effective in Release 12.0, two models of friction are available in nonlinear analysis:
This latter model typically shows better performance in solution of frictional problems
thanks to more stable handling of transitions from stick to slip. Key differences between
the two available models are illustrated in the figure below (F 1 and F 2 represent two
different values of normal force F x ):
Model (a), based on fixed stiffness KT, is relatively simple, yet has certain drawback in
modeling nonlinear friction. Namely, in Coulomb friction the frictional resistance depends
upon normal force. Using fixed KT will predict different range of stick/slip boundary for
different normal forces, and thus may qualify the same configuration as stick or slip,
depending on normal force.
Model (b), based on Elastic Slip Distance, provides unique identification of stick or slip
and generally performs better in solution of problems with friction. This model does
require prescribing elastic slip distance FRICESL – for contact interfaces this value is
determined automatically as 0.5% of typical element size on all Master contact
surfaces.
The model (b), which is currently the default, is recommended for solution of nonlinear
problems with friction. For backwards compatibility, the model based on fixed KT can be
activated by prescribing FRICESL=0 on PCONT or CONTPRM card.
9.
and/or the slave segment stiffness Ks.
The master stiffness is computed from Km = STFAC * B * S * S/V for solids, Km = 0.5 *
STFAC * E * t for shells as well as when the master segment is shared by a shell and
solid.
The slave stiffness is an equivalent nodal stiffness computed as Ks = STFAC * B * V-3 for
solids, Ks = 0.5 * STFAC * E * t for shells.
In these equations, B is the Bulk Modulus, S is the segment area, E is the modulus of
elasticity, t is shell thickness, and V is the volume of a solid. There is no limitation to the
value of stiffness factor (but a value larger than 1.0 can reduce the initial time step).
ISTF > 1, the interface stiffness is then K = max (STMIN, min (STMAX, K1)) with
10. In an implicit analysis, the contact stiffness plays a very important role in convergence.
ISTF = 4 (which takes the minimum of master and slave stiffness’s for contact) is
recommended. This is because the penalty contact force will be balanced with the
internal force of the deformable impacted part. That means the stiffness near the
effective stiffness one will converge easier than a higher one.
For small initial gaps in implicit analysis, the convergence will be more stable if a GAP is
defined that is larger than the initial gap.
In implicit analysis, sometimes a stiffness with scaling factor reduction (for example:
STFAC = 0.01) or reduction in impacted thickness (if rigid one) might reduce unbalanced
forces and improve convergence, particularly in shell structures under bending where the
effective stiffness is much lower than membrane stiffness; but it should be noted that too
low of a value could also lead to divergence.
11. The default for the constant gap (IGAP = CONST) is the minimum of
with:
gs = 0 if the slave node is not connected to any element or is only connected to solid or
spring elements.
gs = t/2, t - largest thickness of the shell elements connected to the slave node.
If the slave node is connected to multiple shells and/or beams or trusses, the largest
computed slave gap is used.
13. INACTI = 3, 4 are only recommended for small initial penetrations and should be used with
caution because:
14.
the tangential friction forces are smoothed using a filter:
F T = α * F'T + (1 - α) * F'T -1
where,
F T - Tangential force
α - filtering coefficient
For IFRIC is not COUL, the friction coefficient is set by a function ( = (p, V)), where p is
the pressure of the normal force on the master segment and V is the tangential velocity
of the slave node.
= Fric + C1 * p + C2 * V + C3 * p * V + C4 * p2 + C5 * V2
The static friction coefficient C1 and the dynamic friction coefficient C2 must be lower
than the maximum friction C3 (C1 < C3 ) and C2 < C3 ).
The minimum friction coefficient C4 , must be lower than the static friction coefficient
C1 and the dynamic friction coefficient C2 (C4 < C1 and C4 < C2 ).
F adh = F Told + ∆F T
∆F T = K * VT * dt
17. For nonlinear implicit contact with friction, the stiffness formulation (IFORM = STIFF) is
recommended.
18. If IGNORE = 1 or 2, the slave nodes without a master segment found during the searching
are deleted from the interface.
If IGNORE = 1 and SRCHDIS is blank, then the default value of the distance for searching
closest master segment is the average size of the master segments.
If IGNORE = 2 and SRCHDIS is blank, then the distance for searching closest master
segment is computed as follows for each slave node:
d1 = 0.6 * (T s + T m)
d2 = 0.05 * T md
SRCHDIS = max(d1, d2 )
where,
T s is the thickness of the element connected to the slave node, for solids T s = 0.0
T m is the thickness of master segment, for solids T m = Element volume / Segment area
CONTX11 – Edge to Edge or Line to Line Contact Interface Definition for Geometric Nonlinear
Analysis
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ONTX11 5 10 7 8
Field Contents
(Integer > 0)
(Integer > 0)
(Integer > 0)
(Integer > 0)
1. CONTX11 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
2. The property of CONTX11(PID) only can be defined by PCONT and its extended card
PCNTX11.
3. CONTX11 defines contact interface type 11, it describes the edge to edge or line to line
interface. This interface simulates impact between lines, a line can be a beam or truss
element or a shell edge or spring elements. The interface properties are:
Description
Defines a free convection boundary condition for heat transfer analysis through connection to
a surface element (CHBDYE card).
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
Comments
q = H * (T - TAMB)
Where, H is the free convection heat transfer coefficient specified on a MAT4 card
referred by a PCONV card, T is the grid temperature, and TAMB is the ambient
temperature.
Description
This entry defines a cylindrical coordinate system using three grid points. The first point is
the origin, the second lies on the Z-axis, and the third lies in the X-Z plane (see Figure 1).
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ORD1C C ID G1 G2 G3 C ID G1 G2 G3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ORD1C 3 16 32 19
Field Contents
(Integer > 0)
G1, G2, G3 Grid point identification numbers of points used to uniquely define the
cylindrical coordinate system (see Figure 1).
Comments
2. A duplicate identification number is allowed if the CID and GID are identical and the
coordinates are within the value set by PARAM, DUPTOL (see Guidelines for Bulk Data
Entries for further information).
3. The three points G1, G2, G3 must be non-collinear. Non-collinearity is checked by the
geometry processor.
4. The location of a grid point (P in Figure 1) in this cylindrical coordinate system is given by
(R, θ, and Z) where, θ is measured in degrees.
5. The displacement coordinate directions at P are dependent on the location of P (ur, uθ,
and uz) as shown in Figure 1. The displacements in all three of these directions at the
grid point are specified in units of length.
In OptiStruct, the cylindrical and spherical coordinate systems are internally resolved to
entity-position-dependent (example: GRID) rectangular systems. Therefore, when a grid
point is located in a cylindrical system, OptiStruct constructs a rectangular system at
that location for the grid point. The R-direction corresponds to the X-axis, the Z-axis is
the same, and the θ axis is tangential to the X (or R) axis. Now the various degrees of
freedom can be resolved (vis-à-vis constraints) similar to a general rectangular system.
Care must be taken to observe that the internally generated rectangular systems are
dependent on the grid point location in the cylindrical system. So they may be different
for different grid point locations within the same cylindrical system.
Description
This entry defines a rectangular coordinate system using three grid points. The first point is
the origin, the second lies on the Z-axis, and the third lies on the X-Z plane (see Figure 1).
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ORD1R C ID G1 G2 G3 C ID G1 G2 G3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ORD1R 3 16 32 19
Field Contents
(Integer > 0)
G1, G2, G3 Grid point identification numbers of points used to uniquely define the
rectangular coordinate system (see Figure 1).
Comments
2. A duplicate identification number is allowed if the CID and GID are identical and the
coordinates are within the value set by PARAM, DUPTOL (see Guidelines for Bulk Data
Entries for further information).
3. The three points G1, G2, and G3 must be non-collinear. Non-collinearity is checked by
the geometry processor.
4. The location of a grid point (P in Figure 1) in this rectangular coordinate system is given
by (X, Y, and Z).
5. The displacement coordinate directions at P are (Ux , Uv , and Uz) as shown in Figure 1.
Description
This entry defines a spherical coordinate system using three grid points. The first point is the
origin, the second lies on the polar (Z) axis, and the third lies in the X-Z plane (see Figure 1).
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ORD1S C ID G1 G2 G3 C ID G1 G2 G3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ORD1S 3 16 32 19
Field Contents
(Integer > 0)
Comments
2. A duplicate identification number is allowed if the CID and GID are identical and the
coordinates are within the value set by PARAM, DUPTOL (see Guidelines for Bulk Data
Entries for further information).
3. The three points G1, G2, and G3 must be non-collinear. Non-collinearity is checked by
the geometry processor.
4. The location of a grid point (P in Figure 1) in this spherical coordinate system is given by
(R, θ, and ). Where, θ and are measured in degrees.
5. The displacement coordinate directions at P are dependent on the location of P (ur, uθ,
and u ) as shown in Figure 1. The displacements in all three of these directions at the
grid point are specified in units of length.
6. Points on the polar axis may not have their displacement directions defined in this
coordinate system due to ambiguity. In this case, the defining rectangular system is
used.
Description
This entry defines a cylindrical coordinate system using three grid points specified with
respect to a reference coordinate system. The coordinates of the three non-collinear grid
points are used to uniquely define the coordinate system. The first point defines the origin.
The second point defines the direction of the Z-axis. The third lies in the X-Z plane (see
Figure 1).
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ORD2C C ID RID A1 A2 A3 B1 B2 B3
C1 C2 C3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Real)
Figure 1: Defining a C ylindrical C oordinate System (C ID) using points A, B and C with reference to another
coordinate system (RID).
Comments
1. The three points (A1, A2, A3), (B1, B2, B3), (C1, C2, C3) must be unique and non-
collinear. Non-collinearity is checked by the geometry processor.
3. A duplicate identification number is allowed if the CID and GID are identical and the
coordinates are within the value set by PARAM, DUPTOL (see Guidelines for Bulk Data
Entries for further information).
4. The location of a grid point (P in Figure 1) in this cylindrical coordinate system is given by
(R, θ, and Z). Where, θ is measured in degrees.
5. The displacement coordinate directions at P are dependent on the location of P (Ur, Uθ,
and Uz) as shown in Figure 1. The displacements in these three directions at the grid
point are specified in units of length.
6. Points on the Z-axis should not have their displacement directions defined in this
coordinate system due to ambiguity.
7. The reference coordinate system (RID) should be independently defined or left blank. If
blank (or 0), the reference coordinate system is the default basic coordinate system. In
such cases, A, B and C are defined with respect to the basic coordinate system.
Description
The entry defines a rectangular coordinate system by using three grid points. The coordinates
of the three non-collinear grid points are used to uniquely define the coordinate system. The
first point defines the origin. The second defines the direction of the Z-axis. The third point
defines a vector, which, with the Z-axis, defines the X-Z plane (see Figure 1).
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ORD2R C ID RID A1 A2 A3 B1 B2 B3
C1 C2 C3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Real)
Figure 1: Defining a Rectangular C oordinate System (C ID) using points A, B and C with reference to another
coordinate system (RID).
Comments
1. The three points (A1, A2, and A3), (B1, B2, and B3), and (C1, C2, and C3) must be
unique and non-collinear. Non-collinearity is checked by the geometry processor.
3. A duplicate identification number is allowed if the CID and GID are identical and the
coordinates are within the value set by PARAM, DUPTOL (see Guidelines for Bulk Data
Entries for further information).
4. The location of a grid point (P in Figure 1) in this rectangular coordinate system is given
by (X, Y, and Z).
5. The displacement coordinate directions at P are (Ux , Uv , and Uz) as shown in Figure 1.
Description
This entry defines a spherical coordinate system three grid points. The coordinates of the
three non-collinear grid points are used to uniquely define the coordinate system. The first
point defines the origin. The second point defines the direction of the Z-axis. The third lies in
the X-Z plane (see Figure 1).
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ORD2S C ID RID A1 A2 A3 B1 B2 B3
C1 C2 C3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
B1,B2,B3 RID is blank or 0, then the reference coordinate system is the default
C1,C2,C3 basic coordinate system.
(Real)
Figure 1: Defining a Spherical C oordinate System (C ID) using grid points A, B and C .
Comments
1. The three points (A1, A2, and A3), (B1, B2, and B3), and (C1, C2, and C3) must be
unique and non-collinear. Non-collinearity is checked by the geometry processor.
3. A duplicate identification number is allowed if the CID and GID are identical and the
coordinates are within the value set by PARAM, DUPTOL (see Guidelines for Bulk Data
Entries for further information).
4. The location of a grid point (P in Figure 1) in this spherical coordinate system is given by
(R, θ, and ). Where, θ and are measured in degrees.
5. The displacement coordinate directions at P are (ur, uθ, and u ) as shown in Figure 1.
The displacements in all three of these directions at the grid point are specified in units of
length.
7. The reference coordinate system (RID) should be independently defined or left blank. If
blank (or 0), the reference coordinate system is the default basic coordinate system. In
such cases, A, B and C are defined with respect to the basic coordinate system.
Description
The entry defines a rectangular coordinate system using three grid points. The first point is
the origin, the second lies on the X-axis, and the third lies on the X-Y plane (see Figure 1).
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ORD3R C ID G1 G2 G3 C ID G1 G2 G3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ORD3R 3 16 32 19
Field Contents
(Integer > 0)
G1, G2, G3 Grid point identification numbers of points used to uniquely define the
rectangular coordinate system (see Figure 1).
Comments
2. A duplicate identification number is allowed if the CID and GID are identical and the
coordinates are within the value set by PARAM, DUPTOL. Refer to Guidelines for Bulk Data
Entries.
3. The three points G1, G2, and G3 must be non-collinear. Non-collinearity is checked by
the geometry processor.
4. The location of a grid point (P in Figure 1) in this rectangular coordinate system is given
by (X, Y, and Z).
5. The displacement coordinate directions at P are (Ux , Uv , and Uz) as shown in Figure 1.
Description
This entry defines a rectangular coordinate system using three grid points specified with
respect to the basic coordinate system. The coordinates of the three non-collinear grid points
are used to uniquely define the coordinate system. The first point is the origin, the second lies
on the X-axis, and the third lies on the X-Y plane (see Figure 1).
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ORD4R C ID A1 A2 A3 B1 B2 B3
C1 C2 C3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
Comments
2. A duplicate identification number is allowed if the CID and GID are identical and the
coordinates are within the value set by PARAM, DUPTOL (see Guidelines for Bulk Data
Entries for further information).
3. The three points (A1, A2, and A3), (B1, B2, and B3), and (C1, C2, and C3) must be
unique and non-collinear. Non-collinearity is checked by the geometry processor.
4. The location of a grid point (P in Figure 1) in this rectangular coordinate system is given
by (X, Y, and Z).
5. The displacement coordinate directions at P are (Ux , Uv , and Uz) as shown in Figure 1.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
TYPEi Type.
3. The type is optional if the Joint is revolute or translation. But if the joint is cylindrical,
the type should be set to TRA to denote that the translational motion is coupled or ROT
to specify that the rotational motion is coupled.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
G15
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
1. Element ID numbers must be unique with respect to all other element ID numbers.
2. The topology of the diagram must be preserved, that is, G1, G2, and G3 define a
triangular face, G1-G4, G2-G5, and G3-G6 each form one edge.
The edge points, G7-G15, are optional. If any of the edge points are present, they all
must be used. The second and third continuation is not needed for the six node version
of this element.
It is recommended that the edge points be placed near the middle of the edge.
C PENTA definition
3. If the user-prescribed node numbering on the bottom and top faces is reversed as
compared to the sequence shown above, then the nodes are renumbered to produce
right-handed orientation of numbering. This is accomplished by swapping nodes G1 with
G3 and G4 with G6. For 15-noded CPENTA, appropriate changes to mid-side node
numbering are also performed. In such cases, the element coordinate system will be built
on the renumbered node sequence.
4. Stresses are output in the material coordinate system. The material coordinate system is
defined on the referenced PSOLID entry. It may be defined as the basic coordinate
system (CORDM = 0), a defined system (CORDM = Integer > 0), or the element coordinate
system (CORDM = -1).
5. The element coordinate system for the CPENTA element is defined as follows:
The origin of the element coordinate system is located at the mid-point of a straight line
from G1 to G4.
The element z-axis corresponds to the average of the vector connecting the centroid of
triangular face G1-G2-G3 to the centroid of the triangular face G4-G5-G6 and the normal
vector of the mid-plane (the plane on which the mid-points of the straight lines G1-G4,
G2-G5, and G3-G6 lie). The positive sense of the z-axis is toward the triangular face G4-
G5-G6.
The element y-axis is perpendicular to the element z-axis and lies on the plane created by
the element z-axis and the line connecting the origin and the mid-point of a straight line
from G3 to G6. The positive sense of the y-axis is toward the straight line from G3 to G6.
The element x-axis is the cross product of the element y-axis and the element z-axis.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C PYRA 71 4 3 4 5 6 7
Field Contents
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2. Grid points G1,…,G4 must be given in consecutive order about the quadrilateral face.
The edge points, G6 through G13, are optional. If any of the edge points are present,
they all must be used. The continuation must not be present for the 5-noded version of
this element.
It is recommended that the edge points be placed near the middle of the edge.
C PYRA definition
3. Stresses are output in the material coordinate system. The material coordinate system is
defined on the referenced PSOLID entry. It may be defined as the basic coordinate
system (CORDM = 0), a defined system (CORDM = Integer > 0), or the element coordinate
system (CORDM = -1).
4. The element coordinate system for the CPYRA element is defined as follows:
The origin of the element coordinate system is located at the intersection of the vectors
R and S.
The element x-axis is the cross product of the element y-axis and the element z-axis.
Description
Defines a quadrilateral plate element (QUAD4) of the structural model. This element uses a 6
degree-of-freedom per node formulation.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
T1 T2 T3 T4
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
ZOFFS Offset from the plane defined by element grid points to the shell
reference plane. See comment 10. Overrides the ZOFFS specified on
the PSHELL entry.
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2. Grid points G1 through G4 must be ordered consecutively around the perimeter of the
element.
5. For H3D and OUTPUT2 output formats, stresses and strains are always output in the
elemental system.
6. For HM, PUNCH and OPTI output formats, stresses and strains are output by default in
the material coordinate system. PARAM, OMID can be set to NO to output results in the
elemental system. For elements with blank Theta/MCID, THETA = 0.0 is assumed, and
the material coordinate system is aligned with side G1-G2 of the shell element. For
elements with prescribed THETA, the material x-axis is rotated from side G1-G2 by angle
THETA. For elements with prescribed MCID, the material system is constructed by
projecting the prescribed MCID onto the plane of the element.
7. If any of the Ti fields are blank, the thickness specified on the PSHELL data will be used
for that node’s thickness. If 0.0 is specified for Ti, then the thickness at that node is
zero.
8. If the property referenced by PID is selected as a region for free-size or size optimization,
then any Ti values defined here are ignored. If you input Ti for elements in the design
space for Topology or Free-Size optimization, the run will error out.
10. The shell reference plane can be offset from the plane defined by element nodes by
means of ZOFFS. In this case all other information, such as material matrices or fiber
locations for the calculation of stresses, is given relative to the offset reference plane.
Similarly, shell results, such as shell element forces, are output on the offset reference
plane.
1. Real:
2. Surface:
This format allows you to select either “Top” or “Bottom” option to specify the offset
value.
Top:
The top surface of the shell element and the plane defined by the element nodes are
coincident.
This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
property entry referenced by this element. (The sign of the ZOFFS value would depend on
the direction of the offset relative to the positive z-axis of the element coordinate
Bottom:
The bottom surface of the shell element and the plane defined by the element nodes are
coincident.
This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
property entry referenced by this element. (The sign of the ZOFFS value would depend on
the direction of the offset relative to the positive z-axis of the element coordinate
system, as defined in the Real section). See Figure 2.
Note that when ZOFFS is used, both MID1 and MID2 must be specified on the PSHELL
entry referenced by this element (otherwise, singular matrices would result).
Offset is applied to all element matrices (stiffness, mass, and geometric stiffness), and to
respective element loads (such as gravity). Hence, ZOFFS can be used in all types of
analysis and optimization. Note, however, that for first order shell elements (CQUAD4 and
CTRIA3), the offset operation does not correct for secondary effects, such as change of
shell area when offset is applied on curved surfaces. Hence, the value of ZOFFS should
be kept within a reasonable percentage (10% - 15%) of the local radius of curvature.
Automatic offset control is available in composite free-size and sizing optimization where
the specified offset values are automatically updated based on thickness changes.
Moreover, while offset is correctly applied in geometric stiffness matrix and hence can be
used in linear buckling analysis, caution is advised in interpreting the results. Without
offset, a typical simple structure will bifurcate and loose stability “instantly” at the critical
Hence, the structure with offset can reach excessive deformation before the limit load is
reached. Note that the above illustrations apply to linear buckling – in a fully nonlinear
limit load simulation, additional instability points may be present on the load path.
11. PHFSHL properties are only valid with an @HYPERFORM statement in the first line of the
input file.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
G7 G8 T1 T2 T3 T4 Theta ZOFFS
or
MC ID
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
Ti Thickness of the element at the corner grid points G1 through G4. The
thickness of the element with Ti specified will be constant and equal to
an average of T1, T2, T3 and T4.
ZOFFS Offset from the surface of grid points to the element reference plane.
See comment 7. Overrides the ZOFFS specified on the PSHELL entry.
Comments
1. Element identification numbers should be unique with respect to all other element IDs.
If MCID is used in place of THETA, then the local material x-direction (Xmaterial) is
obtained at any point in the element by projection of the x-axis of the prescribed MCID
coordinate system onto the surface of the element at this point. The local z-direction is
aligned with the normal to the surface and the material y-direction (Y material) is
constructed accordingly to produce right-handed local material system X-Y-Zmaterial.
5. T1, T2, T3, and T4 are optional. If they are not supplied, then the element thickness will
be set equal to the value of T on the PSHELL entry. If 0.0 is specified for Ti, then the
thickness at that node is zero. If Ti’s are supplied, PID cannot reference PCOMP or
PCOMPP data. If the property referenced by PID is selected as a region for Size
optimization, then any Ti values defined here are ignored. If you input Ti for elements in
the design space for Topology or Free-Size optimization, the run will error out.
6. It is required that the midside grid points be located within the middle third of the edge;
that is the interval (0.25, 0.75) excluding the quarter points 0.25 and 0.75. If the edge
point is located at the quarter point, the program may fail with an error or the calculated
stresses will be meaningless.
7. The shell reference plane can be offset from the plane defined by element nodes by
means of ZOFFS. In this case all other information, such as material matrices or fiber
locations for the calculation of stresses, is given relative to the offset reference plane.
Similarly, shell results, such as shell element forces, are output on the offset reference
plane.
1. Real:
This format allows you to select either “Top” or “Bottom” option to specify the offset
value.
Top:
The top surface of the shell element and the plane defined by the element nodes are
coincident.
This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
property entry referenced by this element. (The sign of the ZOFFS value would depend on
the direction of the offset relative to the positive z-axis of the element coordinate
system, as defined in the Real section). See Figure 1.
Bottom:
The bottom surface of the shell element and the plane defined by the element nodes are
coincident.
This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
property entry referenced by this element. (The sign of the ZOFFS value would depend on
the direction of the offset relative to the positive z-axis of the element coordinate
system, as defined in the Real section). See Figure 2.
Note that when ZOFFS is used, both MID1 and MID2 must be specified on the PSHELL
entry referenced by this element (otherwise, singular matrices would result).
However, while offset is correctly applied in geometric stiffness matrix and hence can be
used in linear buckling analysis, caution is advised in interpreting the results. Without
offset, a typical simple structure will bifurcate and loose stability “instantly” at the critical
load. With offset, though, the loss of stability is gradual and asymptotically reaches a
limit load, as shown below in figure (b):
Hence, the structure with offset can reach excessive deformation before the limit load is
reached. Note that the above illustrations apply to linear buckling – in a fully nonlinear
limit load simulation, additional instability points may be present on the load path.
8. Stresses and strains are output in the local coordinate system identified by and
above.
9. Size optimization of the property referenced by PID is not possible if Ti values are defined
here. If the property referenced by PID is selected as a region for free-size optimization,
then any Ti values defined here are ignored.
10. These 2nd order shell elements do not have normal rotational degrees-of-freedom (often
referred to as "drilling stiffness"). No mass is associated with these degrees-of-freedom.
If unconstrained, massless mechanisms may occur. It is therefore advisable to use
PARAM,AUTOSPC,YES when working with these elements.
Description
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ROD 12 13 21 23
Field Contents
(Integer > 0)
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
GS GE
Examples
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
7 8
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C SEAM 22 3 ELEM 11 12 21 22
7 8
Alternate Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C SEAM 22 3 ELEM 11 12 21 22
Field Contents
CTYPE Character string indicating how the connection is defined. Either format
connects up to 3 x 3 quadrilateral shell elements per patch (possibly more
for triangular elements).
IDAS, Used to define the two connecting patches or the start parts of patch A
IDBS and patch B.
GS Identification number of a grid point which defines the start location of the
connector.
GE Identification number of a grid point which defines the end location of the
connector.
XS, YS, Coordinates of point that defines the start location (GS) of the seam weld
ZS in the basic coordinate system.
(Real)
XE, YE, Coordinates of point that defines the end location (GE) of the seam weld in
ZE the basic coordinate system.
(Real)
1. CSEAM defines a flexible connection between two surface patches. With all of the
information provided, a fictitious 8-node CHEXA will be generated internally for a CSEAM,
and the eight corner nodes are all constrained by the grids of corresponding shell
elements. Then the element stiffness of this fictitious CHEXA will be transferred to the
corresponding shell grids. The CSEAM element itself does not hold any independent DOF.
See the figure below:
A CSEAM element connects Shell A and Shell B. A fictitious hexa is generated for the
CSEAM, and the corner nodes of the hexa are all constrained by corresponding shell grids.
To have a clear view, only one of this kind of constraint relationship is shown with dotted
lines.
2. In the SMLN entry, a name can be given for the CSEAM element. If one CSEAM's GS or
GE is common to the GS or GE of the other CSEAM and they have the same SMLN, the
two CSEAM elements are regarded as neighbors. For two neighboring CSEAM elements,
the faces of the internally generated CHEXAs will be adjusted to form a single common
face.
A seam line does not have a branch with the same SMLN,
3. The distance between GS and GE is the length of the element. The width of the seam
weld is defined in the PSEAM card as W. It is measured perpendicular to the length and
lies in the plane of Shell A or B.
Since the geometry for finding the correct projection could be various and complicated,
many geometry related checks will be implemented in the following procedure. The
default projection algorithm and checking rules can be modified to some extent via
changing the default value defined in the SWLDPRM card.
To build the connectivity, at first, project GS on Shell A and B; the projection points are
denoted as SA and SB respectively. This is also true for GE, and the projection points are
denoted as EA and EB. SA, SB, EA and EB are also called piercing points. Meanwhile, the
shell elements supporting these piercing points are denoted as EIDSA, EIDSB, EIDEA and
EIDEB.
Take SA as an example. For ELEM type, the program will try to project GS on the user
specified element; if the piercing point falls inside the element, the program will accept it
and move to find the next piercing point. If the piercing point falls outside the element
but within the tolerance defined by PROJTOL in the SWLDPRM card, the program will still
accept it. Otherwise, an error will be issued for this CSEAM element, and the program
continues to process other CSEAM elements. For PSHELL type, the case could be much
more complicated. First, a bunch of shell elements which are the closest ones to GS and
have the user-specified shell property will be selected as candidates. Then project GS on
each of the candidates. If the piercing point falls inside one of the candidates, the
program will accept it and move to find the next one. After looping all the candidates, if
there is no appropriate one to support the piercing point, the tolerance defined by
PROJTOL will be used and all candidates will be searched again. At last, if still no element
is found to support the piercing point, an error will be issued for this CSEAM, and the
program continues to process other CSEAM elements. In this way, all the four piercing
points and elements supporting them are found, or an error is issued.
If GMCHK > 0 (be defined in the SWLDPRM card), various geometry checks will be
implemented at specific steps.
If GMCHK > 0 and GSPROJ > 0.0 (be defined in the SWLDPRM card), the program will
check the angle between the normal vectors of EIDSA and EIDSB, and the angle between
the normal vectors of EIDEA and EIDEB. If the angle is larger than GSPROJ, an error will
be issued for this CSEAM. If GSTOL > 0.0 (be defined in the SWLDPRM card) and one of
the lengths of GS-SA, GS-SB, GE-EA and GE-EB is larger than GSTOL, an error will be
issued. Besides these basic checks, a group of cutout and span checks will be performed
if GMCHK>0.
After the four piercing points are found, the auxiliary points will then need to be located
with the definition of the seam width. Take SA as an example, with the coordinates of
the piercing point, the supporting element EIDSA and the seam weld width W, you can
define the following vector n × GS-GE where n is the normal vector of EIDSA. Through
SA, two points SA1 ' and SA2 ' can be defined along this vector and |SA1 '-SA2 '| = W. SA1 '
and SA2 ' are called the preliminary auxiliary points. For a curved or folded shell patch, the
preliminary points may not lie on the shell surface. Therefore, a second projection is
needed to find the final auxiliary points. Take SA1 ' as an example. First, a group of
candidate elements needs to be collected. They are composed of shell elements
surrounding EIDSA. SA1 ' will be projected on each of the candidates to find the best one
to support the projection point. If no element with the user specified shell property is
found with/without tolerance, elements with different shell property will be supplemented
to the candidate list. After projecting all the eight preliminary auxiliary points on the shell
When collecting candidate shell elements which will be used to support the auxiliary
points, the angle between the normal vector of the shell element and the thickness
direction of the fictitious CHEXA will be checked. If the angle is larger than GSPORJ, this
shell element will not be considered as a candidate. If EIDSA, EIDSB, EIDEA or EIDEB fails
the check, a warning message will be issued. For curved or folded shell surface, shell
elements on it have more chances to be eliminated from the candidate list, thus may
possibly induce the failure of locating all auxiliary points. One remedy to this problem is to
increase the value of GSPORJ to include more shell elements into the candidate list.
Various projection points generated in building the connectivity for a CSEAM element.
5. When building the connectivity for CSEAM, if not all eight auxiliary points can be found
and GSMOVE > 0, GS or/and GE will be moved by W/2 and re-projected to avoid the
failure. This often happens near the mesh boundary.
6. For PSHELL type CSEAM, when the GS or GE is close to a folded or curved part of a shell
surface, the program has more chances to fail in locating the correct element to support
the piercing points because of multiple possible choices. In this case, using ELEM type to
directly specify the elements for projection would be a wise alternative.
7. Check whether the CSEAM spans a cutout or spans more than three shell elements on
each shell surface when GMCHK > 0.
If EIDSA = EIDEA, the seam lies on the same element on this surface. This case is
accepted.
EIDEA and they share at least one common grid, it is necessary to do some
checks.
(In the following check, an element called EIDMA is used to assist the check. EIDMA is
located on the same shell surface where EIDSA and EIDEA are located. It shares one of
the common grids shared by EIDSA and EIDEA. EIDMA could be multiple.)
a)If EIDSA and EIDEA share only one common grid but no EIDMA is found, then this case
is rejected.
b)If EIDSA and EIDEA share only one common grid and at least one EIDMA is found, the
number of free edges will be counted. The following cases are considered.
If there are three or more free edges (bold lines), this case is rejected.
Angle check.
If there are two free edges, the angle (α) between the free edges will be calculated. If
the angle is larger than CNRAGLI (be defined in the SWLDPRM card), this case is
accepted. If the angle is smaller than CNRAGLI, then you project the mid-point M to
EIDSA, EIDEA and EIDMA, if the projection point falls inside, this case is still accepted. Or
it will be rejected.
Angle check.
Projection check. M is the middle point of the two free edges' ends.
Compare the angle (α) with CNRAGLO even EIDSA and EIDEA share an edge. If the angle
is larger than CNRAGLI, this case is accepted. If the angle is smaller than CNRAGLI, then
you project the mid-point M to EIDSA and EIDEA, if the projection point falls inside, this
case is still accepted. Or it will be rejected.
elements around them and check how these elements are connected with EIDSA and
EIDEA.
(In the following check, EIDMA is re-defined as an element which shares at least one grid
respectively with EIDSA and EIDEA)
a) If there is no EIDMA, this means the CSEAM element spans more than three elements
in the current shell surface, and this case is rejected.
b) If there are three EIDMA which share edges with both EIDSA and EIDEA, this case is
accepted.
Two different cases when there are two EIDMA who share edges with both EIDSA and
EIDEA.
d) If there is only one EIDMA which shares edges with both EIDSA and EIDEA. The check
presented in the following figure needs to be implemented.
Point M is the average of the two piercing points, that is SA and EA. If the projection
from point M on EIDMA falls inside this element, this case is accepted, or it will be
rejected.
e) If there is only one EIDMA which shares one edge with EIDSA and shares a corner with
EIDEA (or shares one corner with EIDSA and shares one edge with EIDEA), the same
check implemented for the last case will be adopted.
g) If there are two EIDMA and each of them shares an edge with EIDSA or EIDEA and
shares a corner with EIDEA or EIDSA, this case is accepted.
h) If there is only EIDMA which shares only corners but no edge with EIDSA or EIDEA, this
case is rejected.
These two cases are rejected. For the one on the right, although there is no cutout on
the surface, but EIDMA is not fully constrained (only two corners are constrained) by the
CSEAM. Therefore, this case is still rejected.
All the cutout/span checks introduced here still cannot cover 100% cases, but they can
spot most of the bad cases that will lead to unreal modeling of the seam weld. Thus, it is
recommended to turn on the cutout/span check (GMCHK > 0) to exam the seam weld
model in the first round. After all possible problems are resolved, then start the final run.
8. Check whether the CSEAM spans a corner on each shell surface when GMCHK > 0.
9. Diagnostic print outs, checkout runs and non-default setting of search and projection
parameters are requested on the SWLDPRM bulk data entry.
10. It is possible to visualize the fictitious CHEXA via setting SHOWAUX = 1 in the SWLDPRM
card. To have the fictitious CHEXA and corresponding results output into the H3D file,
one also needs to set SHOWAUX = 1.
11. It is recommended to start with default settings and turn on the full geometry check by
setting GMCHK=1 or 2. With the full geometry check, most of the unexpected cases
which may possibly induce unreasonable projections can be spotted. If the switch for
outputting diagnostic info, that is PRTSW, is turned on, the connectivity detail of each
CSEAM element will be printed in the .out file. Also, a summary of various geometry data
will be printed after all CSEAM elements are gone through by the program. They will be
very useful for debugging the seam weld model.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C SEC 2 71 4 3 4
Field Contents
Comments
1. Element identification numbers within a section definition must be unique with respect to
all other element identification numbers within the same section definition.
2. This entry is only valid when it appears between the BEGIN and END statements.
Description
Defines a 1st order three-noded element used in the definition of arbitrary beam cross-
sections.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C SEC 3 10 100 3 4 5
Field Contents
Comments
1. Element identification numbers within a section definition must be unique with respect to
all other element identification numbers within the same section definition.
2. This entry is only valid when it appears between the BEGIN and END statements.
Description
Defines a 1st order four-noded element used in the definition of arbitrary beam cross-sections.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C SEC 4 10 100 3 4 5 6
Field Contents
Comments
1. Element identification numbers within a section definition must be unique with respect to
all other element identification numbers within the same section definition.
2. This entry is only valid when it appears between the BEGIN and END statements.
Description
Defines a planar, 2nd order, six-noded element used in the definition of arbitrary beam cross-
sections.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C SEC 6 10 100 3 4 5 6 7 8
Field Contents
Comments
1. Element identification numbers within a section definition must be unique with respect to
all other element identification numbers within the same section definition.
3. This entry is only valid when it appears between the BEGIN and END statements.
Description
Defines a planar 2nd order eight-noded element used in the definition of arbitrary beam cross-
sections.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
G7 G8
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C SEC 8 10 100 3 4 5 6 13 14
15 16
Field Contents
1. Element identification numbers within a section definition must be unique with respect to
all other element identification numbers within the same section definition.
3. This entry is only valid when it appears between the BEGIN and END statements.
Description
Description
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
Comments
1. Element identification numbers should be unique with respect to all other element
identification numbers.
C SHEAR definition
Description
Defines an axisymmetric triangular cross-section ring element for use in linear analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Theta
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C TAXI 111 2 31 74 75 32 51 52
15.0
Field Contents
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2. All the grid points must be located in the x-z plane of the basic coordinate system with x
= r > 0, and ordered consecutively starting at a corner grid point and proceeding around
the perimeter in either direction.
Corner grid points G1, G3 and G5 must be present. The edge points G2, G4 and G6 are
optional. If any of the edge points are present, they all must be used.
C TAXI definition
4. If the PAXI entry referenced in field 3 references a MAT3 entry, material properties and
stresses are always given in the (xm, zm) coordinate system shown in the figure above.
5. A concentrated load (for example, the load specified on a FORCE entry) at a grid Gi of this
element denotes that applied onto the circumference with radius of Gi. For example, in
order to apply a load of 200N/m on the circumference at Gi which is located at a radius of
0.4m, the magnitude of the load specified on the static load entry must be:
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
G7 G8 G9 G10
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C TETRA 112 2 3 15 14 4
Field Contents
Comments
1. Element ID numbers must be unique with respect to all other element ID numbers.
The edge points G5 to G10 are optional. All or none of the edge points can be specified.
It is recommended that the edge points be located within the middle third of the edge.
C TETRA definition
3. If the user-prescribed node numbering on the bottom face is reversed as compared to the
sequence shown above, then the nodes are renumbered to produce right-handed
orientation of numbering. This is accomplished by swapping node G2 with G3. For 10-
noded CTETRA, appropriate changes to mid-side node numbering are also performed. In
such cases, the element coordinate system will be built on the renumbered node
sequence.
4. Stresses are output in the material coordinate system. The material coordinate system is
defined on the referenced PSOLID entry. It may be defined as the basic coordinate
system (CORDM = 0), a defined system (CORDM = Integer > 0), or the element coordinate
system (CORDM = -1).
5. The element coordinate system for the CTETRA element is defined as follows:
The element x-axis is the cross product of the element y-axis and the element z-axis.
Description
Defines a triangular plate element (TRIA3) of the structural model. This element uses a 6
degree-of-freedom per node formulation.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
T1 T2 T3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
ZOFFS Offset from the plane defined by element grid points to the shell reference
plane. See comment 8. Overrides the ZOFFS specified on the PSHELL
entry.
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2. The x-axis of the element coordinate system is aligned with side 1-2 of the shell element.
3. For H3D and OUTPUT2 output formats, stresses and strains are always output in the
elemental system.
4. For HM, PUNCH, and OPTI output formats, stresses and strains are output by default in
the material coordinate system. PARAM,OMID can be set to NO to output results in the
elemental system. For elements with blank Theta/MCID, the material coordinate system is
aligned with elemental coordinate system. For elements with prescribed THETA, the
material x-axis is rotated from side G1-G2 by angle THETA. For elements with prescribed
MCID, the material system is constructed by projecting the prescribed MCID onto the
plane of the element.
5. If any of the Ti fields are blank, the thickness specified on the PSHELL data will be used
for that node’s thickness. If 0.0 is specified for Ti, then the thickness at that node is
zero.
6. If the property referenced by PID is selected as a region for free-size or size optimization,
then any Ti values defined here are ignored. If you input Ti for elements in the design
space for Topology or Free-Size optimization, the run will error out.
8. The shell reference plane can be offset from the plane defined by element nodes by
means of ZOFFS. In this case all other information, such as material matrices or fiber
locations for the calculation of stresses, is given relative to the offset reference plane.
Similarly, shell results, such as shell element forces, are output on the offset reference
plane.
1. Real:
This format allows you to select either “Top” or “Bottom” option to specify the offset
value.
Top:
The top surface of the shell element and the plane defined by the element nodes are
coincident.
This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
property entry referenced by this element. (The sign of the ZOFFS value would depend on
the direction of the offset relative to the positive z-axis of the element coordinate
system, as defined in the Real section). See Figure 1.
Bottom:
The bottom surface of the shell element and the plane defined by the element nodes are
coincident.
This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
property entry referenced by this element. (The sign of the ZOFFS value would depend on
the direction of the offset relative to the positive z-axis of the element coordinate
system, as defined in the Real section). See Figure 2.
Note that when ZOFFS is used, both MID1 and MID2 must be specified on the PSHELL
entry referenced by this element (otherwise, singular matrices would result).
Moreover, while offset is correctly applied in geometric stiffness matrix and hence can be
used in linear buckling analysis, caution is advised in interpreting the results. Without
offset, a typical simple structure will bifurcate and loose stability “instantly” at the critical
load. With offset, though, the loss of stability is gradual and asymptotically reaches a
limit load, as shown below in figure (b):
Hence, the structure with offset can reach excessive deformation before the limit load is
reached. Note that the above illustrations apply to linear buckling – in a fully nonlinear
limit load simulation, additional instability points may be present on the load path.
9. PHFSHL properties are only valid with an @HYPERFORM statement in the first line of the
input file.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
THETA ZOFFS T1 T2 T3
or
MC ID
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C TRIA6 302 3 31 33 71 32 51 52
Field Contents
ZOFFS Offset from the surface of grid points to the element reference plane;
see Comment 7. Overrides the ZOFFS specified on the PSHELL entry.
Comments
1. Element identification numbers should be unique with respect to all other element IDs.
If MCID is used in place of THETA, then the local material x-direction (Xmaterial) is
obtained at any point in the element by projection of the x-axis of the prescribed MCID
coordinate system onto the surface of the element at this point. The local z-direction is
aligned with the normal to the surface and the material y-direction (Y material) is
constructed accordingly to produce right-handed local material system X-Y-Zmaterial.
6. It is required that the midside grid points be located within the middle third of the edge.
That is the interval (0.25, 0.75) excluding the quarter points 0.25 and 0.75. If the edge
point is located at the quarter point, the program may fail with an error or the calculated
stresses will be meaningless.
7. The shell reference plane can be offset from the plane defined by element nodes by
means of ZOFFS. In this case all other information, such as material matrices or fiber
locations for the calculation of stresses, is given relative to the offset reference plane.
Similarly, shell results, such as shell element forces, are output on the offset reference
plane.
1. Real:
2. Surface:
This format allows you to select either “Top” or “Bottom” option to specify the offset
value.
The top surface of the shell element and the plane defined by the element nodes are
coincident.
This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
property entry referenced by this element. (The sign of the ZOFFS value would depend on
the direction of the offset relative to the positive z-axis of the element coordinate
system, as defined in the Real section). See Figure 1.
Bottom:
The bottom surface of the shell element and the plane defined by the element nodes are
coincident.
This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
property entry referenced by this element. (The sign of the ZOFFS value would depend on
the direction of the offset relative to the positive z-axis of the element coordinate
system, as defined in the Real section). See Figure 2.
Note that when ZOFFS is used, both MID1 and MID2 must be specified on the PSHELL
entry referenced by this element (otherwise, singular matrices would result).
Offset is applied to all element matrices (stiffness, mass and geometric stiffness) and to
respective element loads (such as gravity). Hence, ZOFFS can be used in all types of
analysis and optimization. Automatic offset control is available in composite free-size and
sizing optimization where the specified offset values are automatically updated based on
thickness changes.
Hence, the structure with offset can reach excessive deformation before the limit load is
reached. Note that the above illustrations apply to linear buckling – in a fully nonlinear
limit load simulation, additional instability points may be present on the load path.
8. Stresses and strains are output in the local coordinate system identified by and
above.
9. Size optimization of the property referenced by PID is not possible if Ti values are defined
here. If the property referenced by PID is selected as a region for free-size optimization,
then any Ti values defined here are ignored.
10. These 2nd order shell elements do not have normal rotational degrees-of-freedom (often
referred to as "drilling stiffness"). No mass is associated with these degrees-of-freedom.
If unconstrained, massless mechanisms may occur. It is therefore advisable to use
PARAM,AUTOSPC,YES when working with these elements.
Description
Description
Defines an axisymmetric triangular cross-section ring element for use in linear analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Theta
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
15.0
Field Contents
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
2. All the grid points must be located in the x-z plane of the basic coordinate system with x
= r > 0, and ordered consecutively starting at a corner grid point and proceeding around
the perimeter in either direction.
Corner grid points G1, G3 and G5 must be present. The edge points G2, G4 and G6 are
optional. If any of the edge points are present, they all must be used.
C TRIAX6 definition
4. If MID is defined on a MAT3 entry, material properties and stresses are always given in
the (xm, zm) coordinate system shown in the figure above.
5. A concentrated load (for example, the load specified on a FORCE entry) at a grid Gi of this
element denotes that applied onto the circumference with radius of Gi. For example, in
order to apply a load of 200N/m on the circumference at Gi which is located at a radius of
0.4m, the magnitude of the load specified on the static load entry must be:
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C TUBE 12 13 21 23
Field Contents
(Integer > 0)
Comments
1. Element identification numbers must be unique with respect to all other element
identification numbers.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C VISC 2 64 12 63
Field Contents
Comments
1.
2. Element identification numbers must be unique with respect to all other element
identification numbers.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
55 56 21 22
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
15 16
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
The alternative formats of CWELD listed below are useful in cases when the weld diameter
extends beyond a single shell element. These options connect up to 3x3 shell elements per
patch (possibly more for triangular elements) on each side of weld element.
Format (Alternate)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PIDA/ PIDB/
SHIDA SHIDB
XS YS ZS
Example 1 (Alternate)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C WELD 10 20 PARTPAT
33 34
Example 2 (Alternate)
1034 2035
Field Contents
GA# Grid identification numbers of the first surface patch. GA1 to GA3 are
required (See comment 6).
SHIDA, SHIDB Element identification numbers of shells defining weld ends A and B,
respectively. Required for ELPAT.
XS, YS, ZS Coordinates of point that defines the location of the weld in the basic
coordinate system. It is an alternate way of specifying the location
of GS. Available with PARTPAT/ELPAT options only.
Real
Comments
1. CWELD defines a flexible connection between two surface patches, between a point and
a surface patch, or between two shell vertex grid points. See figure below:
3. If TYP is GRIDID, either a point to patch (GS to GA#) or a patch to patch (GA# to GB#)
connection is defined. For the patch to patch connection, GA# describes the first
surface patch and GB# describes the second surface patch.
4. The input of the piercing points GA and GB is optional when TYP is GRIDID and ELEMID. If
GA or GB are not specified, they are generated from the normal projection of GS onto the
surface patches. If GA and/or GB are specified, they take precedence over GS in defining
the respective end points. Also, their locations will be corrected so that they lie on
surface patch A and B, respectively. If GS is not specified, both GA and GB are required.
The length of the connector is the distance from GA to GB.
5. SPTYP defines the type of surface patches to be connected. SPTYP is required when TYP
is GRIDID to identify quadrilateral or triangular patches. Allowable combinations are:
SPTYP Description
6. GA# are required when TYP is GRIDID. At least 3, and at most 8, grid IDs may be
specified for GA#. Triangular and quadrilateral element definition sequences apply for the
order of GA# and GB#, see below. Missing mid-side nodes are allowed.
8. When TYP is ALIGN, a point to point connection is defined. GA and GB are required. GA
and GB are not required when TYP is GRIDID or ELEMID.
9. Forces and moments are output in the element coordinate system (shown in comment 10
below).
The element x-axis points from GA to GB. The element y-axis lies on the plane created by
the element x-axis and the smallest component of the element x-axis is the basic
coordinate system, and is orthogonal to the element x-axis. The element z-axis is the
cross-product of the element x-axis and the element y-axis.
10. The output format of the forces and moments, including the sign convention, is identical
to the CBAR element.
11. Diagnostic print outs, checkout runs and non-default setting of search and projection
parameters are requested on the SWLDPRM bulk data entry. It is recommended to start
with default settings.
12. The formats PARTPAT and ELPAT connect shell element patches on side A and B. The
patches are identified by specifying SHIDA and SHIDB (for ELPAT connection) and by
specifying property IDs PIDA and PIDB for PARTPAT connection (wherein SHIDA and SHIDB
are found by appropriate search of best projections of GS (or GA) onto the surfaces A
and B, respectivel)y. The piercing points GA and GB are found by appropriate projections
onto SHIDA and SHIDB. Then the axis GA-GB is used to define four pairs of auxiliary
points GAHi, GBHi, i=1,4 that are located on patches A and B, respectively. The cross-
section area of the resulting hexahedral is equivalent to the area of the weld. The weld
stiffness matrix is first built using the auxiliary points and then constrained to supporting
shell nodes using respective shape functions.
Description
Defines scale (area) factors for dynamic loads. DAREA is used in conjunction with RLOAD1,
RLOAD2, TLOAD1, and TLOAD2 entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DAREA SID P1 C1 A1 P2 C2 A2
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Real)
2. Refer to RLOAD1, RLOAD2, TLOAD1, or TLOAD2 entries for the formula that define the
scale factor A#.
4. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
+ EID7 …
Field Contents
EID# Entity identification numbers. List of entities of type ETYPE for which this
DCOMP card is defined.
LAMTHK LAMTHK flag indicating that laminate thickness constraints are applied.
LTEXC Exclusion flag indicates that certain plies are excluded from the LAMTHK
constraint. The following options are supported:
PLYTHK PLYTHK flag indicating that ply thickness constraints are applied. Multiple
PLYTHK constraints are allowed.
PTGRP Ply orientation in degrees, ply sets or ply IDs, to which the PLYTHK
constraint is applied, depending on the PTOPT selection.
PTOPT Ply selection options for the PLYTHK constraint. Plies can be selected based
on the following:
PTEXC Exclusion flag indicates that certain plies are excluded from the PLYTHK
constraint. The following options are supported:
PLYPCT PLYPCT flag indicating that ply thickness percentage constraints are applied.
Multiple PLYPCT constraints are allowed.
PPGRP Ply orientation in degrees, ply sets or ply IDs, to which the PLYPCT
constraint is applied, depending on the PPOPT selection.
Default = blank (Real > 0.0, < 1.0 and > PPMIN)
PPOPT Ply selection options for the PLYPCT constraint. Plies can be selected based
on the following:
PPEXC Exclusion flag indicates that certain plies are excluded from the PLYPCT
constraint. The following options are supported:
BGRP1 First ply orientation in degrees, ply sets or ply IDs, to which the BALANCE
constraint is applied, depending on the BOPT selection.
BGRP2 Second ply orientation in degrees, ply sets or ply IDs, to which the BALANCE
constraint is applied, depending on the BOPT selection.
BOPT Ply selection options for the BALANCE constraint. Plies can be selected
based on the following:
CGRP Ply orientation in degrees, ply sets or ply IDs, to which the CONST constraint
is applied, depending on the COPT selection.
COPT Ply selection options for the CONST constraint. Plies can be selected based
on the following:
PLYDRP Indicates that ply drop-off constraints are applied. Multiple PLYDRP
constraints are allowed.
PDGRIP Ply orientation in degrees, ply sets or ply IDs, to which the PLYDRP
constraint is applied, depending on the PDOPT selection.
PDTYP Specifies the type of the drop-off constraint as: TOTDRP (see comment 5).
PDOPT Ply selection options for the PLYDRP constraint. Plies can be selected based
on the following:
PDEXC Exclusion flag indicates certain plies are excluded from the PLYDRP
constraint. The following options are supported:
Comments
1. The following manufacturing constraints are available for ply-based composite sizing
optimization:
Lower and upper bounds on the total thickness of the laminate (LAMTHK)
Lower and upper bounds on the thickness of a given orientation (PLYTHK)
Lower and upper bounds on the thickness percentage of a given orientation (PLYPCT)
Manufacturable ply thickness (PLYMAN)
Linking between the thicknesses of two given orientations (BALANCE)
Constant (non-designable) thickness of a given orientation (CONST)
LAMTHK, PLYTHK and PLYPCT can be applied locally to sets of elements. There can be
elements that do not belong to any set.
2. These constraints are automatically created after performing free-sizing optimization
when the OUTPUT,FSTOSZ control card is activated.
3. For a more detailed description and an example, refer to the User’s Guide section,
Optimization of Composite Structures.
4. Older versions of the DCOMP card (OptiStruct version 11.0 and prior) are supported and
handled appropriately.
5. The option for selecting the type of drop-off constraints for PDTYP is defined for a set of
plies, as shown in the figure below:
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DC ONADD DC ID DC 1 DC 2 DC 3 DC 4 DC 5 DC 6 DC 7
DC 8 etc.
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DC ONADD 101 10 20 30
Field Contents
(Integer > 0)
(Integer > 0)
Comments
3. All DCID must be unique with respect to all Dci (DCONSTR IDs).
Description
Defines design constraint upper and lower bounds where response is defined by DRESP1,
DRESP2, and DRESP3 cards.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Associated Cards
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
Comments
1. The DCONSTR DCID is selected in the Subcase Information section by the DESSUB or
DESGLB cards and/or referenced by the DCONADD card.
2. For any DCID, the associated RID can be referenced only once.
3. If LBOUND or UBOUND are blank, no constraint will be generated for the bound.
4. Constraint bounds of zero should be avoided. Unnecessary bounds should be left blank.
For example, lower bounds on von Mises stress should be blank, not zero. If a bound of
zero is input, the bound will be changed to 1.0E-7 for lower bounds and –1.0E-7 for upper
bounds. This will remove numerical difficulties and cause the constraints to be ignored
unless the response is actually very near zero.
5. LFREQ, UFREQ apply only to response types related to a frequency response subcase
(DRESPi, RTYPE = FRDISP, FRVELO, FRACCL, FRSTRS, FRSTRN, FRFORC, and FRERP). The
constraint bounds LBOUND and UBOUND are applied only if the loading frequency falls
between LFREQ and UFREQ. If ATTB of DRESP1 specifies a frequency value, LFREQ and
UFREQ are ignored.
6. LTID, UTID identify a loading frequency dependent tabular input using TABLEDi. They are
applied analogous to LFREQ, UFREQ detailed in comment 5.
Description
This bulk data entry can be used to define real, discrete design variable values for discrete
variable optimization or to define relative rotor spin rates in rotor dynamics.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Alternate Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
The continuation entry formats (shown below) may be used more than once, and in any order.
They may also be used with either format above.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
1.5 20
Field Contents
(Integer > 0)
(Real)
Comments
2. Trailing fields on a DDVAL record can be left blank if the next record is of type DVALi
"THRU" DVALj "BY" INC. Also, fields 7 though 9 must be blank when the type DVALi "THRU"
DVALj "BY" INC is used in fields 2 through 6. Fields 8 through 9 must be blank when the
type DVALi "THRU" DVALj "BY" INC is used in fields 3 through 7 for the first record.
Embedded blanks are not permitted in other cases.
4. The format DVALi "THRU" DVALj "BY" INC defines a list of discrete values, for example,
DVALi, DVALi+INC, DVALi+2.0*INC, …, DVALj. The last discrete DVALj is always included,
even if the range is not evenly divisible by INC.
Description
Defines enforced axial deformation for one-dimensional elements for use in statics problems.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Real)
Comments
1. Only CBAR, CBEAM, CROD, CONROD, and CTUBE elements are valid.
Since most elements in an FEA model are not free to expand, the specified extension
value may not be achieved because elastic compression of the element will partially or
completely offset the effect of the prescribed strain. To precisely enforce a prescribed
increase in length, MPC equations are more appropriate. Alternatively, giving the DEFORM
element a very high axial stiffness can approximate such conditions.
Description
Defines the time delay term in the equations of the dynamic loading function. DELAY is
used in conjunction with RLOAD1, RLOAD2, TLOAD1, and TLOAD2 entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DELAY SID P1 C1 T1 P2 C2 T2
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Real)
1. One or two dynamic load time delays may be defined on a single entry.
2. SID must also be specified on a RLOAD1, RLOAD2, TLOAD1, or TLOAD2 entry. See those
entry descriptions for the formulae that define the manner in which the time delay term,
, is used.
4. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
…; …; EQNn-1; EQNn
Example 1
z = -y*1.3E-2
Example 2
Field Contents
(Integer > 0)
Comments
2. Each equation card is specified in a fixed format, without the limitation of data field
boundaries. Equations are located in columns 17-72 on the first card, and in columns 9-
72 on each continuation card. There is no limit on the total length of any equation.
4. Free field format is allowed, but only the same number of characters as in the fixed format
(56 on the first line and 64 on the continuation lines) and will be accepted. Characters
after the 72nd column will not be accepted. Excess characters are silently disregarded,
which may result in DEQATN error or in a valid expression different from that intended. On
the continuation card in free format, the comma must be present within the first 8
columns; otherwise, the card will be interpreted in a fixed field format.
5. Blank characters in the equation have no effect, even within a constant, variable or
function name. Lower and upper case letters are equivalent.
6. There must be only one variable at the left-hand side of each equation in any equation
card. The variable of the first equation must be followed by an argument list in the
following format:
v1(x1,x2,…,xn) = expression(x1,x2,…,xn);
v2 = expression(x1,x2,…,xn,v1);
vi = expression(x1,x2,…,xn,v1,v2,…,vi-1);
vn = expression(x1,x2,…,xn,v1,v2,…,vn-1);
where, vi is the variable of equation i. (x1, x2, …, xn) is the argument list for variable v1.
(v1,v2,…,vi-1) is the variable list which corresponds to the result of equation 1 through
equation i-1.
Only the value of the last expression is returned to the bulk data card referencing EQUID
(DRESP2).
7. Constants can be specified in a format of either integer or floating point. A floating point
number can be in a format of either normal decimal-point format ("3.90") or scientific
notation ("-2.0E-3"), which means -2x10-3.
acos(x) arccosine
asin(x) arcsine
atan(x) arctangent
cos(x) cosine
exp(x) exponential
pi(x) multiples of
sin(x) sine
Two-argument functions
+ binary + x+y
- binary - x-y
* multiplication, x*y
/ division x/y
** power x**y
+ unary + +1.0
- unary - -1.0
Expression Result
2**-3 0.128
1 / 2 +3 3.5
2*3-4 2.0
-2**3**2 -512.0
2 + -5 -3.0
2 * -5 -10.0
2 - -5 7.0
2/3/4 0.16666666…
2/(3/4) 2.6666666…
10. Functions can be defined in a layered format, for example, min(sin(x1), x2). There is no
limit on the number of layers.
11. The DEQATN entry is referenced by DRESP2 and/or DVPREL2 bulk data cards.
DRESP2 card, the variable identified by DVIDi, LABj, NRk, Gr and DPIP correspond to
variable arguments listed in the left-hand side of the first equation of a DEQATN card
identified by EQUID. The variable arguments x1 through xN (where N = n + m + p + q + s)
are assigned in the order DVID1, DVID2, …, DVIDn, LAB1, LAB2, …, LABm, NR1,NR2, …,
NRp, G1, …, Gq, DPIP1,…,DPIPS. In a DVPREL2 card, the variables identified by DVIDi and
LABj correspond to variable arguments listed in the left-hand side of the first equation of
a DEQATN card identified by EQUID. The variable arguments x1 through xN (where N = n
+ m) are assigned in the order DVID1, DVID2, …, DVIDn, LAB1, LAB2, …, LABm.
Only the computed value of the last expression (vn) is used by DRESP2 and/or DVPREL2
entry.
Variable names longer than 8 characters are truncated, which may create an error in
equation if two names are identical after such truncation.
All trigonometric arguments are in radians.
Only alphanumeric characters may be used in variable names (that is do not use
underscores, monetary symbols, punctuation symbols, mathematical operators, letters
from non-English alphabet, and so on).
Mathematical function names (such as those listed in comment 7 above) should not be
used as variable names.
The following functions are not accepted:
DB()
DBA()
INVDB()
INVDBA()
Possible Errors
An informative error message with the DEQATN ID will be displayed if the parsing of the
equation fails. However, in certain cases, the following generic message will be provided:
Error 1690: This equation could not be parsed. See the DEQATN entry in the
OptiStruct manual.
This error message means that it was not possible to clearly identify the reason for the failure.
If this happens, check for the following possible causes, and contact ossupport@altair.com:
The length of the equation exceeds the 72 character per line limitation.
The last character of the equation is an operator.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
+ RAND ITYPE P1 P2 P3
+ RANP ITYPE P1 P2 P3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Character)
(Real)
(Real)
RAND flag indicating that the random design variable distribution parameters
for Reliability-based Design Optimization (RBDO).
(Character string)
RANP flag indicating that the random parameter distribution parameters for
Reliability-based Design Optimization (RBDO).
Comments
1. Only the initial value of the move limits can be set. Move limits are automatically
adjusted to enhance iterative stability and convergence speed.
2. LABEL must begin with an alphabetical character, and cannot have embedded blanks.
3. If the design variable is discrete (Integer > 0 in DDVAL field), and if either XLB and/or XUB
bounds are wider than those given by the discrete list of values on the corresponding
DDVAL entry, XLB and/or XUB will be replaced by the minimum and maximum discrete
values.
Description
Defines an override for design variable settings.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
ID Identification Number.
INIT Overrides the initial value setting for affected design variables. See
comment 1.
SET Defines the design variables that are affected by this DESVARG entry. Can
either be the keyword ALL or the SID of a SET of type DESVAR.
Comments
1. If any of INIT, LB or UB are left blank, then no override is applied to the corresponding
field on affected DESVARs.
Likewise if INIT is defined as UB, then for all affected DESVAR entries the initial value is
set to the upper bound setting.
If, INIT is defined as ANALYSIS, then for all affected DESVAR entries the initialization is
accomplished based on the corresponding analysis properties.
When a Design Variable is associated with multiple properties that have different
values.
When a Design Variable is associated with a property through DVPREL2
When a Design Variable is associated with a property through DVPREL1 with multiple
design variables.
When one of the three limitations occurs, a warning is issued and the Design Variable is
initialized based on the DESVAR card.
3. Multiple DESVARGs are allowed (DESVARGs are processed in the order of input).
4. If the bounds are invalid after DESVARG is applied, then an error will occur.
Description
Defines input parameters required for the Global Search Option (GSO).
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
+ … …
Field Contents
NPOINT Number of starting points for each group of design variables. See
comment 1.
NPOINT# Number of starting points for the current group of design variables.
SPMETH# Method used to generate the starting points for the current group of
design variables.
1. Design variables are automatically organized in groups, and design variables within a given
group are assigned the same relative starting points, such as their lower or upper bound.
With the AUTO option, OptiStruct determines NGROUP and NPOINT so as to generate a
reasonable and manageable number of starting points. Note that for small optimization
problems, each design variable might be assigned its own group. By default, the number
of groups is equal to the number of independent design variables with an upper limit of 10.
For larger optimization problems, design variables are grouped together in order to
consolidate the potential starting points.
2. With the EXTREME option, the lower and upper bounds are included in the list of starting
points; whereas with the OFFSET option, the lower and upper bounds are not considered
as starting points. In both cases, the starting points are distributed evenly.
3. In situations where finer control is required, design variables can be grouped manually by
creating DESVAR SETs. NPOINT# and SPMETH# can also be defined for individual groups.
If those parameters are not defined for a specific group, they inherit their value from the
generic NPOINT and SPMETH parameters.
4. The unique design tolerance DESTOL provides the threshold under which two designs are
considered identical. It is measured as the average of the relative differences between
the design variables at the last iteration. If such identical designs are found, the best
occurrence is preserved and other results are discarded. Up to NOUTDES unique designs
are saved in subdirectories named <filename_#s_#u>, where #s is the starting point and
#u is the rank of the unique design.
5. The global search option stops searching for optimal designs when any of the following
criteria has been met:
7. The DGLOBAL bulk data entry is referenced by the DGLOBAL command in the I/O section
of the input data.
Description
Defines a link between a DIM# field on a PBARL or PBEAML property and either the thickness
on a PSEC definition or the y or z coordinate on a GRIDS definition; it is used in the definition
of arbitrary beam cross-sections.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Alternate Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DIM 1 T 10
Field Contents
COORD Coordinate.
No default (Y or Z)
Comments
2. This entry is only valid when it appears between the BEGIN and END statements.
Description
The DLINK bulk data entry defines a link between one design variable and one or more other
design variables.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
IDV3 C3 etc.
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
15 -3.0
Field Contents
(Integer > 0)
(Integer > 0)
C0 Constant.
(Integer > 0)
(Real)
Comments
This capability allows physical and non-physical design variables to be related such as
shell thickness and interpolating functions.
2. Independent IDVi’s can occur on the same DLINK entry only once.
Description
Defines a link of one design variable to one or more other design variables defined by a
DEQATN card. The equation inputs come from the referenced DESVAR values and the
constants defined on the DTABLE card.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
LABL8 etc.
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DESVAR 5 6
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Character)
No default (Character)
1. The main application for this entity is to link shape design variables with each other
through equations. DVPREL2 should be used for linking sizing design variables with each
other through equations.
2. The following functions can be used instead of an EQUID. If FUNC is used, the DEQATN
entry is no longer needed. The functions are applied to all arguments on the DLINK2
regardless of their type.
Description
Defines a dynamic loading condition for frequency response problems as a linear combination
of load sets defined via RLOAD1 and RLOAD2 entries, or for transient problems as a linear
combination of load sets defined via TLOAD1 and TLOAD2 entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DLOAD SID S S1 L1 S2 L2 S3 L3
S4 L4 … … … … … …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
-2.0 201
Field Contents
S Scale factor.
No default (Real)
S# Scale factors.
No default (Real)
Comments
1. Dynamic load sets must be selected in the I/O Options or Subcase Information sections
with DLOAD=SID. (See I/O Options and Subcase Information DLOAD entry).
4. SID must be unique from all RLOAD1 and RLOAD2 or TLOAD1 and TLOAD2 entries.
5. A DLOAD entry may not reference a set identification number defined by another DLOAD
entry.
6. RLOAD1 and RLOAD2 loads and TLOAD1 and TLOAD2 loads may be combined only through
the use of the DLOAD entry.
Description
Defines direct input matrices related to grid points. The matrix is defined by a single header
entry and one or more column entries. A column entry is required for each column with non-
zero elements.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DMIG NAME GJ CJ G1 C1 A1
G2 C2 A2 G3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DMIG STIF 0 9 1 0 2
120 4 2.5+10
123 4 4.1+8
NCOL Number of columns in a rectangular matrix. Must be used when IFO = 9. Not
used when IFO = 6.
No default (Real)
1. Matrices may be selected for all solution sequences by the structural matrices before
constraints are applied.
2. The header entry containing IFO is required. Each no-null column is started with a GJ, CJ
pair. The entries for each row of that column follow. Only non-zero terms need be
entered. The terms may be input in arbitrary order. A GJ, CJ pair may be entered more
than once, but input of an element of the matrix more than once will produce a fatal
message.
4. A given off-diagonal element may be input either below or above the diagonal. While
upper and lower triangle terms may be mixed, a fatal message will be issued if an element
is input both below and above the diagonal.
6. The recommended format for rectangular matrices requires the use of NCOL and IFO = 9.
The number of columns in the matrix is NCOL. (The number of rows in all DMIG matrices is
always g-set size). The GJ term is used for the column index. The CJ term is ignored.
7. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).
8. The DMIG matrices can be multiplied by real numbers and combined when referenced by
the K2GG, M2GG, K42GG, K2PP, B2GG, and A2GG data.
9. The DMIG matrices can be multiplied by real numbers as they are assembled into the
global matrices using the PARAM data C2K, CP2, CB2, and CM2 for K2GG, K2PP, B2GG, and
M2GG data respectively.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ORIGIN A1 A2 A3
Field Contents
No default (1 to 6 characters)
SHFGID All Grid identification numbers in the superelement are shifted by the
specified value. If this field is left blank, then a shift does not occur (see
comment 2).
SHFSPID All SPOINT identification numbers in the superelement are shifted by the
specified value. If this field is left blank, then a shift does not occur (see
comment 2).
SHFSPID_F All Fluid SPOINT identification numbers in the superelement are shifted by the
specified value. If this field is left blank, then a shift does not occur (see
comment 2).
SHFCID All Coordinate System identification numbers in the superelement are shifted
by the specified value. If this field is left blank, then a shift does not occur
(see comment 2).
SHFEID All Element identification numbers in the superelement are shifted by the
specified value. If this field is left blank, then a shift does not occur (see
comment 2).
SHFRID All Rigid Element identification numbers in the superelement are shifted by
the specified value. If this field is left blank, then a shift does not occur (see
comment 2).
METHOD Identification number of EIGRL card. Hybrid damping would be applied on the
superelements for the modes referred by EIGRL card. If blank, then applied
damping on all the modes.
KDAMP If KDAMP is set to -1, viscous modal damping is entered into the complex
stiffness matrix as structural damping instead of viscous damping.
Default = 1 (Integer)
METHOD_F Identification number of EIGRL card. Hybrid damping would be applied on the
fluid part of superelement for the modes referred by the EIGRL card. If
blank, then modal damping is applied damping to all the fluid modes.
SDAMP_F Identification number of TABDMP1 entry for fluid modal damping of the
superelement.
KDAMP_F If KDAMP_F is set to -1, viscous modal damping is entered into the complex
stiffness matrix as structural damping instead of viscous damping.
Default = 1 (Integer)
RELOC Keyword indicating that matching grid point ID pairs in the residual structure
and superelement are to follow (see comment 1).
PA1, PA2, ID’s of three non-collinear grid points in the residual structure.
PA3
PB1, PB2, ID’s of three non-collinear grid points in the superelement that will be
PB3 matched to corresponding grid points in the residual structure (defined by
PA1, PA2 and PA3).
Comments
1. The RELOC entry and its related fields define three matching grid point pairs on the
residual structure and the superelement. The superelement defined using ASSIGN,
H3DDMIG is relocated (translated and rotated, as required) such that the three non-
Figure 1: Matching three grids on the superelement with grids on the residual structure
Description
Defines a response and its reference values for a minmax (maxmin) optimization problem.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Associated Cards
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
Comments
1. The same DOID can be used for multiple DOBJREF entries. If only one DOID is used, only
one MINMAX=DOID entry is needed in the Subcase Information section.
2. The use of reference values allows users to set up general minmax problems involving
different responses with different magnitudes. For these problems, the objective can be
defined as:
Or, alternatively:
where, Wk are response values, and rk are corresponding reference values, which can
take different values depending on whether the response is positive or negative.
3. Typically, the target value or constraint value of a response can be used as its reference
value. So, instead of the traditional optimization problem where there is a single objective
and multiple constraints, the problem may be formulated as a minmax (maxmin)
optimization, where all the responses which were previously constrained are defined as
objectives and their bounds are used as reference values. This works toward pushing the
maximum ratio of response versus bound value as low as possible, thus increasing the
safety of the structure.
4. LOWFQ and HIGHFQ apply only to response types related to a frequency response
subcase (DRESPi, RTYPE = FRDISP, FRVELO, FRACCL, FRSTRS, FRSTRN, FRFORC, FRPRES
and FRERP). The reference values NEGREF and POSREF are applied only if the loading
frequency falls between LOWFQ and HIGHFQ. If ATTB of DRESP1 specifies a frequency
value, LOWFQ and HIGHFQ are ignored.
5. LID and UID identify a loading frequency dependent tabular input using TABLEDi. They are
applied analogous to LOWFQ, HIGHFQ detailed in comment 4.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Real or Integer)
The available parameters and their values are listed below (click the parameter name for
detailed parameter descriptions).
DELSHP The initial fractional move limit for Real > 0.0
topography/shape design variables Default = 0.2
(fractional difference between the
upper and lower bounds).
ESLSTOL Controls the tolerance for screening 0.0 < Real < 1.0
out time steps in the design of multi- Default = 0.3
body dynamic systems.
MATINIT Defines the initial material fraction. Real between 0.0 and 1.0
TMINPLY Defines the minimum ply thickness 0.0 < Real < min(Ti)
allowed for all plies of PCOMP’s
selected by DSIZE or DTPL design
variable definitions.
Comments
1. Some of the parameters may also be defined as separate entities in the I/O section of the
deck, using the previous (OS3.5) input format. Only one definition is allowed.
APPROX < FULL or Approximation type switch for stress/strain responses for
REDUCED > shells, composites and 1D elements.
Default =
FULL When REDUCED is chosen, some stress/strain responses will
use the constant force approximation. This method has the
benefit of reducing the memory requirement for large
optimization problems (many stress/strain responses for
many size design variables). Another benefit is the reduction
in runtime if the bottleneck occurs due to sensitivity
analysis. You are encouraged to try the REDUCED option for
the large size optimization model, and, if the FULL option
results in the error 832 (Optimization problem is too big to be
solved by OptiStruct).
DELSHP Real > 0.0 Initial fractional move limit for topography/shape design
Default = 0.2 variables. Defined as the fractional difference between
the upper and lower bounds.
DELSIZ Real > 0 Initial fractional move limit for size design variables.
Default = 0.5
Only the initial value of the move limits can be set.
Move limits are automatically adjusted to enhance
iterative stability and convergence speed.
DELTOP Real > 0 Initial fractional move limit for topology and free-size
Default = 0.5 design variables.
DISCRETE Real > 0.0 Discreteness parameter. Influences the tendency for
elements in a topology optimization to converge to a
Defaults material density of 0 or 1. Higher values decrease the
1.0 – general number of elements that remain between 0 and 1.
default.
Note: Recommended bounds are 0.0 and 2.0 for shells,
2.0 - for solid or 3.0 for solids.
dominant
structures with
member size
control and no
manufacturing
constraints.
ESLMAX Integer > 0 Maximum number of outer design loops in the design
Default = 30 of multi-body dynamics systems, and for nonlinear
optimization using the equivalent static load
method.
ESLSOPT < 0, 1 > Controls the time step screen strategy in the design
Default = 1 of multi-body dynamics systems.
ESLSTOL 0.0 < Real < 1.0 Controls the tolerance for screening out time steps
Default = 0.3 in the design of multi-body dynamic systems. Valid
only when DOPTPRM, ESLSOPT is 1.
MATINIT Real between This parameter declares the initial material fraction. For
0.0 and 1.0 topology optimization runs with mass as the objective,
default is 0.9. For runs with constrained mass, the
default is reset to the constraint value. If mass is not
the objective function and is not constrained, the
default is 0.6.
MINDENS Real > 0.0 Minimum element material density. Sets a lower limit
Default = 0.01 on the amount of material that can be assigned to any
design element. Extremely low values for this
parameter can result in an ill-conditioned stiffness
matrix.
MINDIM Real > 0.0 Specifies the minimum diameter of members formed
Default = no in a topology optimization. This command is used to
minimum member eliminate small members.
size control
MMCHECK Integer = 0,1 The use of this parameter, in conjunction with MINDIM,
Default = 0 will ensure a checkerboard-free solution, although with
the undesired side effect of achieving a solution that
involves a large number of semi-dense elements, similar
to the result of using CHECKER=1. Therefore, use this
parameter only when it is necessary.
NESLEXPD Integer > 0 This parameter specifies the number of time steps
Default = 20 retained for optimization from each EXPDYN subcase.
At each time step, one ESL (equivalent static load) is
generated.
NESLIMPD Integer > 0 This parameter specifies the number of time steps
Default = 20 retained for optimization from each IMPDYN subcase.
At each time step, one ESL (equivalent static load) is
generated.
NESLNLGM Integer > 0 This parameter specifies the number of time steps
Default = 1 retained for optimization from each NLGEOM subcase.
At each time step, one ESL (equivalent static load) is
generated.
Note:
Note:
TMINPLY 0.0 < Real < min(Ti) Defines the minimum ply thickness allowed for all
plies of PCOMPs selected by DSIZE or DTPL design
variable definitions. Should be smaller than the
minimum of all relevant Ti on the selected PCOMPs.
Check its compatibility with volume constraint if
applied. Note also that for volume fraction
calculation, TMINPLY is not treated as none design
volume in the same way as T0 for regular PSHELLs.
Description
Defines the phase lead term in the equation of the dynamic loading function. DPHASE is
used in conjunction with RLOAD1 and RLOAD2 entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Real)
1. One or two dynamic load phase lead terms may be defined on a single entry.
2. SID must be referenced on a RLOAD1 or RLOAD2 entry for the formulae that define how
the phase lead is used.
4. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).
Description
Defines the draping data for plies used in ply-based composite definition.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DRAPE ID
...
Field Contents
DID# Entity number. Must refer to an element (for ELEM) or SET (for
SET) bulk data entry. Must be blank for ALL.
T# Thinning factor.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DR8 etc.
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DREPAD 101 10 20 30
D
Field Contents
(Integer > 0)
(Integer > 0)
Comments
3. All DRID must be unique with respect to all DRi (DREPORT IDs).
Description
The DREPORT card is used in the bulk data section to report responses, defined by DRESP1,
DRESP2 and DRESP3 cards, to the output file, which are not constrained or used as the
objective function, as defined by the optimization problem.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Associated Cards
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
(Real or blank)
(Real or blank)
(Integer or blank)
(Integer or blank)
Comments
1. The DREPORT DRID is selected in the Subcase Information section by the REPSUB or
REPGLB cards and/or referenced by the DREPADD card.
2. For any DRID, the associated RID can be referenced only once.
3. If NL=1, only the lowest response in the range [LALLOW, UALLOW] (if specified) is
reported. If NU=1, only the highest response in the range [LALLOW, UALLOW] (if
specified) is reported.
Description
A response, or set of responses, that are the result of a design analysis iteration. These
responses can be used as a design objective or as design constraints.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ATT2 … … … … … … …
EID8 … … …
EXTN RANDID
Examples
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
or
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
4 7
Field Contents
ID Response identification number. Each DRESP1 card must have a unique ID.
No default (Character)
RTYPE Type of response that is defined – mass, volume, freq, disp, stress, etc.
No default (See Responses and attributes for DRESP1 card for full list of
response types)
PTYPE If a property response, then PTYPE is the property type, for example,
PSHELL. It is used in conjunction with ATT1 to identify the unique
property. If an element response, then PTYPE = ELEM. It is used in
conjunction with ATTi to identify the element IDs. For material responses,
PTYPE is MAT and ATTi are material IDs. For grid responses, PTYPE is blank
and ATTi are grid IDs. (See Responses and attributes for DRESP1 card for
further information).
ATTi PID, MID, EID, MBREQM ID, MBREQE ID, PFBODY ID or Grid ID as referenced
by PTYPE and RTYPE. (See Responses and attributes for DRESP1 card for
further information).
EXCL EXCL flag indicating that IDs of elements excluded from the response
follow.
EXTN EXTN flag indicating that extended attribute definition follows. RANDID is
currently supported as an extended attribute definition and is the RANDPS
ID to which the response applies. See comments 30 and 31.
Comments
2. Responses of the same RTYPE with the same region identifier are grouped together into
the same region. If the region identifier is blank, elements identified by an ATTi field
(when PTYPE = ELEM) are grouped together into the same region, but for properties or
materials, each property or material identified by an ATTi field will form its own region.
Refer to the User's Guide section Constraint Screening for a more detailed explanation.
3. DRESP1 entries must have unique identification numbers with respect to DRESP2 and
DRESP3 entries.
5. The total displacement can be requested using ATTA=7; the total rotation using ATTA=8.
6. PTYPE = PCOMP, PCOMPG can be selected for RTYPE = STRESS or RTYPE = STRAIN, in
which case homogenized stresses or strains are used. RTYPE = CSTRESS or RTYPE =
CSTRAIN should be used instead for composite responses.
7. Stresses are element stresses. For CBAR, CBEAM, stresses are normal (axial) stresses for
the element.
8. VOLFRAC and MASSFRAC can only be applied to topology design domains. OptiStruct will
terminate with an error if this is not the case.
9. MASS, MASSFRAC, COG and INERTIA responses are not available for PBUSH, PDAMP,
PELAS, PGAP, PVISC, and PWELD.
10. VOLUME and VOLFRAC responses are not available for CONM2, PDAMP, PELAS, PGAP,
PMASS, and PVISC.
11. The VOLUME of a single CWELD element is 1.0. The response then is the number of
welds.
12. WCOMP, WFREQ, COMB require the definition of WEIGHT and/or MODEWEIGHT subcase
commands. If WEIGHT or MODEWEIGHT are not defined, the following defaults apply:
WCOMP WEIGHT in static subcases WEIGHT = 1.0 for all static subcases.
WFREQ MODEWEIGHT in normal modes MODEWEIGHT (1) = 1.0 in most cases for
subcase topology optimization.
COMB WEIGHT in static subcases WEIGHT = 1.0 for all static subcases.
13. CSTRESS, CSTRAIN, and CFAILURE are only available for PCOMP, PCOMPG.
ATTB = # refers to a ply on a PCOMP.
Example: DRESP1, 12, PLY23, CSTRESS, PCOMP, SMAP, 23, 43.
ATTB = G# refers to a global ply on a PCOMPG.
Example: DRESP1, 12, GLOBAL11, CFAILURE, PCOMPG, HILL, G11, 17.
ATTB must be blank for PLY response type.
15. Composite Stress/Strain item codes S1Z and S2Z for Shear-1Z and Shear-2Z are for
CSTRESS only, these are not available for CSTRAIN.
16. Lower bound constraints are not allowed on von Mises stress.
18. Responses that do not exist are ignored, and a warning is issued.
19. EXCL only applies to RTYPE = STRESS, STRAIN, FORCE, CSTRESS, CSTRAIN, CFAILURE,
FRSTRS, FRSTRN, and FRFORC response types.
20. For RTYPE = MASS, MASSFRAC, VOLUME, VOLFRAC, COG, INERTIA, BEADFRAC, and
COMP; ATTi can only be blank if PTYPE is also blank. ATTi blank means that all relevant
entities are included. They all belong to the same region for constraint screening.
21. For RTYPE=STRESS, STRAIN, FORCE, FRSTRS, FRSTRN, FRFORC, CSTRESS, CSTRAIN, and
CFAILURE; ATTi can only be blank if PTYPE is a property type (not allowed when PTYPE is
"ELEM"). ATTi blank means that all entities of the defined PTYPE are selected.
22. For RTYPE = MASS, MASSFRAC, MBMASS, VOLUME, VOLFRAC, COG, MBCOG, INERTIA,
MBINER, COMP, and BEADFRAC; ATTB = COMB results in the creation of a single response
for the combination of all ATTi entities.
23. For RTYPE=MASS, MBMASS, VOLUME, MBCOG, MBINER, COMP, MASSFRAC, and VOLFRAC;
ATTB=SUM is the same as ATTB=COMB.
24. For RTYPE = FRDISP, FRVELO, FRACCL, FRSTRS, FRSTRN, FRFORC, FRERP, PSDDISP,
PSDVELO, PSDACCL, and PSDPRES the following functions can be applied through the
character input on ATTB. The formulas are applied across all loading frequencies. The
use of MAX can be very inefficient computationally and it is better to leave ATTB blank
and let constraint screening take care of it.
25. For RTYPE = INERTIA, the Moment of Inertia is with reference to the center of gravity.
The Moment of Inertia of the whole model is referred to the center of gravity of the whole
model. The Moment of Inertia of each property or material is referred to the center of
gravity of that property or material.
26. For acoustic optimization, pressure responses are defined using RTYPE=FRPRES; however,
it is acceptable to define a pressure response on a fluid grid as RTYPE=FRDISP with ATTA
as one of M-TX, R-TX or I-TX, internally it will be converted to FRPRES (with M-TX/R-TX/
I-TX interpreted as M-PRES/R-PRES/I-PRES). Likewise, RTYPE=PSDDISP or RMSDISP are
accepted in place of PSDPRES or RMSPRES, respectively.
27. For RTYPE = MBDIS, MBVEL, MBACC, or MBFRC, the PTYPE must be MBREQM. These four
response types must be defined using MARKERs, and requested by MBREQM. For RTYPE =
MBEXPR, the PTYPE must be MBREQE. The response must be requested by MBREQE. For
28. MBREQE referenced in DRESP1 must have single expression although MBREQE allows up to
6 expressions for analysis output.
29. MBD system level responses must be scalar quantities. Thus, THE ATTB field must have
one of the following - MAX, MIN, MAXABS, or MINABS so that time dependent vectors can
be converted to scalar quantities.
30. Legacy data with RANDPS ID defined on the PTYPE or ATTB entry is also supported.
31. A blank field for RANDID on the EXTN extended attributes entry indicates that all RANDPS
cards in the input file will be used.
32. “Cluster Size” represents the number of elements around the specified element whose
stress contributions are included in the calculation of the individual element’s stress
contribution. The contributions of the elements in the cluster are weighted based on their
distance to the center of the cluster (Available for Shell and Solid elements). Weighting
element stress contributions using “Cluster Size” is generally useful in models with stress
gradients or stress concentrations in the design space. If the stress distribution within
the selected element cluster is uniform, there may not be any significant difference in the
stress response. A separate result type “Element Stress Cluster” is available in the
_s#.h3d file and stress results based on element cluster response(s) can be viewed in
HyperView by selecting Element Stresses Cluster in the Result type: drop-down menu.
Response
RTYPE PTYPE ATTA ATTB ATTi EXTN
s
Static CSTRES "PCOMP", Composite ALL, Ply No. PID, EID, Ply -
stress in a S "PCOMPG" Stress item or ‘G#**** ID,
composite , "PLY", code (Default = 1) or blank***
or blank*****
lay-up or "ELEM"
Static CSTRAI "PCOMP", Composite ALL, Ply No. PID, EID, Ply -
strain in a N "PCOMPG" Strain item or ‘G#**** ID,
composite , "PLY", code (Default = 1) or blank***
or blank*****
lay-up or "ELEM"
Static CFAILU "PCOMP", Composite ALL, Ply No. PID, EID, Ply -
failure in a RE "PCOMPG" Failure item or ‘G#**** ID,
composite , "PLY", code (Default = 1) or blank***
or blank*****
lay-up or "ELEM"
Frequency Value.
PSD PSDVEL - PSD/RMS item (Blank, Real > GRID ID RANDPS
velocity O code 0.0 or Character) ID
PSD stress PSDSTR PTYPE PSD/RMS item Frequency PID, EID RANDPS
S or code Value or blank*** ID
PSD strain PSDSTR PTYPE PSD/RMS item Frequency PID, EID RANDPS
N or code Value or blank*** ID
"ELEM" (Blank, Real >
0.0 or
Character)
Static WCOMP - - - - -
compliance
weighted
across all
subcases
Frequency WFREQ - - - - -
weighted
across
reciprocal
eigenvalue
s
Combined COMB - - - - -
static
compliance
and
frequency
index
(Combined
Complianc
e Index)
SPC Component ID
SPCFOR - - Grid ID -
Forces CE (1-6) –
(Reaction Degrees of
forces/ Freedom
moments)
* ATTi can only be blank when PTYPE is also blank, and means that all relevant
entities will be included. See comment 20 on the DRESP1 page.
** ATTB = COMB – Response represents a single response for the combination of all
*** ATTi can only be blank when a property type is defined in the PTYPE field (not
allowed for "ELEM"), and means that all entities of the defined property type will
be selected. See comment 21 on the DRESP1 page.
**** ATTB = G# – # is the number of the global ply defined on a PCOMPG. See
comment 13 on the DRESP1 page.
***** ATTB must be Blank for PLY response type. See comment 13 on the DRESP1
page.
****** ATTB = Cluster Size represents the number of elements in a cluster for which
Stress Constraints need to be defined. See comment 32 on the DRESP1 page.
CELAS Stress/Strain S 2
End A SA 2
End B SB 2
Normal X SXX 6
Normal Y SYY 14
Normal Z SZZ 20
Shear XY SXY 7
Shear YZ SYZ 15
Shear XZ SXZ 21
Normal X 2 SX2 11
Normal Y 1 SY1 4
Normal Y 2 SY2 12
Shear XY 1 SXY1 5
Shear XY 2 SXY2 13
*OptiStruct provides partial support for Nastran item codes. Since Nastran response items
are not fully compatible with those used in OptiStruct, it is recommended that the OptiStruct
ASCII item codes be used.
**For Bar elements that reference PBARL, PBEAML, it is recommended that the special stress
item codes listed under Stress Item Codes for Bar Elements using PBARL, PBEAML Properties be
used. Stress/strain items listed here for CBAR, CBEAM elements using PBAR, PBEAM, PBARL, or
PBEAML properties include only normal stress/strain.
Evaluation Stresses
S1N
S2N
S3N
S4N
S5S S5V
S6S S6V
S7S S7V
Evaluation Stresses
S5S S5V
S6S S6V
S7S S7V
S8S S8V
S9S S9V
S10S S10V
S11S S11V
S12S S12V
Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.
S5S S5V
S6S S6V
S7S S7V
S8S S8V
S9S S9V
S10S S10V
S11S S11V
S12S S12V
Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.
Evaluation Stresses
S1N
S2N
S3N
S4N
S5S S5V
S6S S6V
S7S S7V
S8S S8V
S9S S9V
Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
Evaluation Stresses
S1N
S2N
S3N
S4N
S5S S5V
S6S S6V
S7S S7V
S8S S8V
S9S S9V
Evaluation Stresses
S1N
S2N
S3N
S4N
S5S S5V
S6S S6V
S7S S7V
S8S S8V
S9S S9V
Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.
Evaluation Stresses
S1N S1V
S2N S2V
S3N S3V
S4N S4V
S5S S5V
S6S S6V
S8S S8V
Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.
H element type
Evaluation Stresses
S1N
S2N
S3N
S4N
S6S S6V
S7S S7V
S8S S8V
S9S S9V
Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.
Evaluation Stresses
S1N
S2N
S3N
S4N
S6S S6V
S7S S7V
S8S S8V
S9S S9V
S10S S10V
S11S S11V
S12S S12V
S13S S13V
S14S S14V
S15S S15V
Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.
I element type
Evaluation Stresses
S1N
S2N
S3N
S4N
S5S S5V
S6S S6V
S7S S7V
S8S S8V
S9S S9V
I1 element type
Evaluation Stresses
S1N
S2N
S3N
S4N
S5S S5V
S6S S6V
S7S S7V
S8S S8V
S9S S9V
Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.
L element type
Evaluation Stresses
S1N
S2N
S3N
S4N
S5S S5V
S6S S6V
S7S S7V
S8S S8V
Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.
Evaluation Stresses
S1N S1S
S2N S2S
S3N S3S
S4N S4S
S5V
The location of point 5 will be determined by varying the from 0 to 360 degrees to find
the maximum von Mises stress.
Evaluation Stresses
S1N
S2N
S3N
S4N
S5S S5V
S6S S6V
S7S S7V
Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.
T1 element type
Evaluation Stresses
S1N
S2N
S3N
S4N
S5S S5V
S6S S6V
S7S S7V
Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.
T2 element type
Evaluation Stresses
S1N
S2N
S3N
S4N
S5S S5V
S6S S6V
S7S S7V
Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.
Evaluation Stresses
S1N S1S
S2N S2S
S3N S3S
S4N S4S
S5V
The location of point 5 will be determined by varying the from 0 to 360 degrees to find
the maximum von Mises stress.
Z element type
Evaluation Stresses
S1N
S2N
S3N
S4N
S5S S5V
S6S S6V
S7S S7V
S8S S8V
S9S S9V
Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
Imaginary I-F 3
Magnitude M-F 2
Phase P-F 3
Imaginary I-FA 3
Magnitude M-FA 2
Phase P-FA 3
Imaginary I-FA 3
Magnitude M-FA 2
Phase P-FA 3
Imaginary I-FB 5
Magnitude M-FB 4
Phase P-FB 5
Imaginary I-FA 3
Phase P-FA 3
Imaginary I-FB
Magnitude M-FB
Phase P-FB
Magnitude M-MA1 2
Phase P-MA1 10
Magnitude M-MA2 3
Phase P-MA2 11
Magnitude M-MB1 4
Phase P-MB1 12
Magnitude M-MB2 5
Phase P-MB2 13
Magnitude M-SA1 6
Phase P-SA1 14
Magnitude M-SA2 7
Phase P-SA2 15
Imaginary I-FA 16
Magnitude M-FA 8
Phase P-FA 16
Imaginary I-TA 17
Magnitude M-TA 9
Phase P-TA 17
Magnitude M-SB1
Phase P-SB1
Phase P-SB2
Imaginary I-FB
Magnitude M-FB
Phase P-FB
Imaginary I-TB
Magnitude M-TB
Phase P-TB
Imaginary I-FX 8
Magnitude M-FX 2
Phase P-FX 8
Imaginary I-FY 9
Magnitude M-FY 3
Phase P-FY 9
Imaginary I-FZ 10
Magnitude M-FZ 4
Phase P-FZ 10
Imaginary I-MX 11
Magnitude M-MX 5
Phase P-MX 11
Imaginary I-MY 12
Magnitude M-MY 6
Phase P-MY 12
Imaginary I-MZ 13
Magnitude M-MZ 7
Phase P-MZ 13
Imaginary I-F41 10
Magnitude M-F41 2
Phase P-F41 10
Imaginary I-F21 11
Magnitude M-F21 3
Phase R-F21 11
Imaginary I-F12 12
Phase P-F12 12
Imaginary I-F32 13
Magnitude M-F32 5
Phase P-F32 13
Imaginary I-F23 14
Magnitude M-F23 6
Phase P-F23 14
Imaginary I-F43 15
Magnitude M-F43 7
Phase P-F43 15
Imaginary I-F34 16
Magnitude M-F34 8
Phase P-F34 16
Imaginary I-F14 17
Magnitude M-F14 9
Phase P-F14 17
Magnitude M-KF1 18
Phase P-KF1 26
Imaginary I-SH12 27
Magnitude M-SH12 19
Phase P-SH12 27
Imaginary I-KF2 28
Magnitude M-KF2 20
Phase P-KF2 28
Magnitude M-NX 2
Phase P-NX 10
Imaginary I-NY 11
Magnitude M-NY 3
Phase P-NY 11
Magnitude M-NXY 4
Imaginary I-MX 13
Magnitude M-MX 5
Phase P-MX 13
Imaginary I-MY 14
Magnitude M-MY 6
Phase P-MY 14
Magnitude M-MXY 7
Phase P-MXY 15
Magnitude M-SXZ 8
Phase P-SXZ 16
Magnitude M-SYZ 9
Phase P-SYZ 17
*OptiStruct provides partial support for Nastran item codes. Since Nastran response items
are not fully compatible with those used in OptiStruct, it is recommended that the OptiStruct
ASCII item codes be used.
Imaginary I-S 3
Magnitude M-S 2
Phase P-S 3
Imaginary I-SAB
Magnitude M-SAB
Phase P-SAB
Imaginary I-SA 3
Magnitude M-SA 2
Phase P-SA 3
Imaginary I-SB
Magnitude M-SB
Phase P-SB
Magnitude M-SALL
Phase P-SALL
Imaginary I-SAC 7
Magnitude M-SAC 2
Phase P-SAC 7
Imaginary I-SAD 8
Magnitude M-SAD 3
Phase P-SAD 8
Imaginary I-SAE 9
Magnitude M-SAE 4
Phase P-SAE 9
Imaginary I-SAF 10
Magnitude M-SAF 5
Phase P-SAF 10
Imaginary I-SBC 16
Magnitude M-SBC 12
Phase P-SBC 16
Imaginary I-SBD 17
Magnitude M-SBD 13
Phase P-SBD 17
Imaginary I-SBE 18
Magnitude M-SBE 14
Phase P-SBE 18
Imaginary I-SBF 19
Magnitude M-SBF 15
Phase P-SBF 19
Magnitude M-SAMAX
Phase P-SAMAX
Magnitude M-SBMAX
Phase P-SBMAX
Magnitude M-SALL
Phase P-SALL
Imaginary I-SAC 8
Magnitude M-SAC 4
Phase P-SAC 8
Imaginary I-SAD 9
Magnitude M-SAD 5
Phase P-SAD 9
Imaginary I-SAE 10
Magnitude M-SAE 6
Phase P-SAE 10
Imaginary I-SAF 11
Magnitude M-SAF 7
Phase P-SAF 11
Magnitude M-SAMAX
Phase P-SAMAX
Magnitude M-SBMAX
Phase P-SBMAX
Imaginary I-SHMAX 3
Magnitude M-SHMAX 2
Phase P-SHMAX 3
Imaginary I-SHAVG 5
Magnitude M-SHAVG 4
Phase P-SHAVG 5
Magnitude M-SXX 6
Phase P-SXX 12
Imaginary I-SYY 13
Magnitude M-SYY 7
Phase P-SYY 13
Imaginary I-SZZ 14
Magnitude M-SZZ 8
Phase P-SZZ 14
Imaginary I-SXY 15
Magnitude M-SXY 9
Phase P-SXY 15
Imaginary I-SYZ 16
Magnitude M-SYZ 10
Phase P-SYZ 16
Imaginary I-SXZ 17
Magnitude M-SXZ 11
Phase P-SXZ 17
Magnitude M-SXB
Phase P-SXB
Imaginary I-SX1 4
Magnitude M-SX1 3
Phase P-SX1 4
Imaginary I-SX2 11
Magnitude M-SX2 10
Phase P-SX2 11
Magnitude M-SYB
Phase P-SYB
Imaginary I-SY1 6
Magnitude M-SY1 5
Phase P-SY1 6
Imaginary I-SY2 13
Magnitude M-SY2 12
Phase P-SY2 13
Magnitude M-SXYB
Phase P-SXYB
Imaginary I-SXY1 8
Magnitude M-SXY1 7
Phase P-SXY1 8
Imaginary I-SXY2 15
Magnitude M-SXY2 14
Phase P-SXY2 15
* OptiStruct provides partial support for Nastran item codes. Since Nastran response items
are not fully compatible with those used in OptiStruct, it is recommended that the OptiStruct
ASCII item codes be used.
Imaginary I-TX 7
Magnitude M-TX 1
Phase P-TX 7
Imaginary I-TY 8
Magnitude M-TY 2
Phase P-TY 8
Imaginary I-TZ 9
Magnitude M-TZ 3
Phase P-TZ 9
Imaginary I-RX 10
Magnitude M-RX 4
Phase P-RX 10
Imaginary I-RY 11
Magnitude M-RY 5
Phase P-RY 11
Imaginary I-RZ 12
Magnitude M-RZ 6
Phase P-RZ 12
Imaginary I-NORM -
Magnitude M-NORM -
Phase P-NORM -
*OptiStruct provides partial support for Nastran item codes. Since Nastran response items
are not fully compatible with those used in OptiStruct, it is recommended that the OptiStruct
ASCII item codes be used.
Imaginary I-PRES 7
Magnitude M-PRES 1
Phase P-PRES 7
*OptiStruct provides partial support for Nastran item codes. Since Nastran response items
are not fully compatible with those used in OptiStruct, it is recommended that the OptiStruct
ASCII item codes be used.
Center of Gravity
x-coordinate X
y-coordinate Y
z-coordinate Z
Moments of Inertia
lxx XX
lyy YY
lzz ZZ
lxy XY
lxz XZ
lyz YZ
CELAS Force F 2
Force End B FB -
Torque End A TA 9
Torque End B TB -
Torque End A TA 9
Torque End B TB 99
CBUSH Force-X FX 2
Force-Y FY 3
Force-Z FZ 4
Moment-X MX 5
Moment-Y MY 6
Moment-Z MZ 7
Bending Moment X MX 5
Bending Moment Y MY 6
Force 2 to 1 F21 3
Force 1 to 2 F12 4
Force 3 to 2 F32 5
Force 2 to 3 F23 6
Force 4 to 3 F43 7
Force 3 to 4 F34 8
Force 1 to 4 F14 9
*OptiStruct provides partial support for Nastran item codes. Since Nastran response items
Hill HILL
Hoffman HOFF
Tsai-Wu TSAI
Normal - 1 S1 3
Normal - 2 S2 4
Shear - 12 S12 5
Shear - 1Z S1Z 6
Shear - 2Z S2Z 7
* OptiStruct provides partial support for Nastran item codes. Since Nastran response
items are not fully compatible with those used in OptiStruct, it is recommended to use
the OptiStruct ASCII item codes.
Normal - 1 S1 3
Normal - 2 S2 4
Shear - 12 S12 5
* OptiStruct provides partial support for Nastran item codes. Since Nastran response
items are not fully compatible with those used in OptiStruct, it is recommended to use
the OptiStruct ASCII item codes.
Normal - 1 TS1 -
Normal - 2 TS2 -
Shear - 12 TS12 -
* OptiStruct provides partial support for Nastran item codes. Since Nastran response
items are not fully compatible with those used in OptiStruct, it is recommended to use
the OptiStruct ASCII item codes.
Normal - 1 MS1 -
Normal - 2 MS2 -
Shear - 12 MS12 -
* OptiStruct provides partial support for Nastran item codes. Since Nastran response
items are not fully compatible with those used in OptiStruct, it is recommended to use
the OptiStruct ASCII item codes.
Translational X TX
Translational Y TY
Translational Z TZ
Rotational X RX
Rotational Y RY
Rotational Z RZ
Translational TXYZ
resultant
Translational X TX
Translational Y TY
Translational Z TZ
Rotational X RX
Rotational Y RY
Rotational Z RZ
Translational TXYZ
resultant
Rotational RXYZ
resultant
Translational X FX
Translational Y FY
Translational Z FZ
Rotational X MX
Rotational Y MY
Rotational Z MZ
Translational FXYZ
resultant
Rotational MXYZ
resultant
Translation X TX 1
Translation Y TY 2
Translation Z TZ 3
Rotation X RX 4
Rotation Y RY 5
Rotation Z RZ 6
*OptiStruct provides partial support for Nastran item codes. Since Nastran response items
are not fully compatible with those used in OptiStruct, it is recommended that the OptiStruct
ASCII item codes be used.
Pressure PRES
Normal X SXX
Normal Y SYY
Normal Z SZZ
Shear XY SXY
Shear YZ SYZ
Shear XZ SXZ
Normal X 1 SX1
Normal X 2 SX2
Normal Y 1 SY1
Normal Y 2 SY2
Shear XY 1 SXY1
Shear XY 2 SXY2
Description
When a desired response is not directly available from OptiStruct, it may be calculated using
DRESP2. This response can be a functional combination of any set of responses resulting from
the design analysis iteration. Responses defined in this manner can be used as design
objectives or constraints. The DRESP2 card identifies the equation to use for the response
relationship and the input values to evaluate the response function.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 1
Define a response labeled FUNC1 that references equation #999, where DESVAR #11 is the
first variable, the DTABLE entry PI is the second variable, DRESP1 #1 is the third variable,
the Y location of grid #11 is the forth variable and the DVPREL1 #22 is the fifth variable.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DESVAR 11
DTABLE PI
DRESP1 1
DGRID 11 2
DVPREL1 22
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DRESP2 3 AVDIS 7 2
DRESP1 9 2
Associated Cards
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Character)
No default (Character)
MODEL User-defined model names defined on the ASSIGN, MMO entry (see
NAME# comment 15).
VARTYPE# Indicates the type of variables to follow. Can be one of: DESVAR,
DTABLE, DGRID, DGRIDB, DRESP1, DRESP1L, DRESP2, DRESP2L, DVPREL1,
DVPREL2, DVCREL1, DVCREL2, DVMREL1, DVMREL2, DVMBRL1, or
DVMBRL2 (see comments 5, 13 and 16).
No default (Character)
comment 13).
Comments
1. DRESP2 entries are referenced from the subcase through one of DESOBJ, DESSUB, or
DESGBL.
2. DRESP2 entries must have unique identification numbers with respect to DRESP1 and
DRESP3 entries.
3. DRESP1L, DRESP2L define a response defined with a DRESP1 or DRESP2, respectively, and
a SUBCASE. The SUBCASE number 0 should be used for global responses.
4. Responses with the same region identifier are grouped together into the same region. If
the region identifier is blank, then a separate region is formed for each DRESP2 definition.
The RTYPE EQUA on the DSCREEN definition refers to DRESP2 responses. It is important
to ensure that responses with the same region identifier reference similar equations. For
further information, refer to Constraint Screening in the User's Guide.
5. Any number of VARTYPE# continuation lines can be defined. The order in which the
VARTYPE# continuation lines are listed on the DRESP2 card is not prescribed. The same
VARTYPE# can be repeated any number of times, in any position, on the card. However,
the order in which the VARTYPE# continuation lines are listed will affect the solution as
the values are passed to the equation (or function) in the listed sequence.
6. The entries on the DRESP2 cards are assigned to the variable on the DEQATN card in the
order that they occur. For example 2 above x1 is the displacement response defined by
the DRESP1 card with ID=9 and x2 is the displacement response defined by the DRESP1
card with ID=2.
7. DRESPi and DRESPiL cards cannot be mixed on the same DRESP2 definition.
8. If DRESP1L, DRESP2L are used for a constrained DRESP2, DESGLB must be used to identify
the DRESP2.
9. If DRESP1L, DRESP2L are used in a DRESP2 objective function, then the DESOBJ that
references the DRESP2 must be defined before the first Subcase.
10. If the DRESP2 data is referenced by DESOBJ data, the DESOBJ data must be above the
first SUBCASE if:
The DESOBJ data must be in the correct SUBCASE if the DRESP2 contains subcase
dependent DRESP1 responses.
12. DRESP2 cannot reference itself directly or recursively, but multiple levels of referencing
are allowed.
13. The DGRID and DGRIDB VARTYPE’s can be used to select grid point locations as variables
to be passed to the specified equation or function. The grid point locations are specified
as a list of Grid point ID/Component pairs where every second value is a component. The
Grid point ID’s are unique grid point identification numbers (ID) and Components are the
grid point locations X1, X2, and X3 fields on the GRID bulk data entry.
Examples:
DGRIDB:
The VARTYPE DGRIDB can be used to select grid point locations in the basic coordinate
system. The basic coordinate system is the default rectangular coordinate system in
OptiStruct.
DGRID:
The VARTYPE DGRID can be used to select the grid point locations in the local coordinate
system of each grid point. This local coordinate system may be specified by the CP field
of the GRID bulk data entry for a particular grid point of interest. All local (or user defined)
coordinate systems are directly or indirectly based on the default basic coordinate
system.
14. The following functions can be used instead of an EQID. If FUNC is used, the DEQATN
entry is no longer needed. The functions are applied to all arguments on the DRESP2
regardless of their type.
15. Multiple RID-Model Name pairs can be specified on a single DRESPM continuation line.
These responses can be used similar to responses defined via the VARTYPE# -ID# entries.
ASSIGN, MMO can be used to identify the filename of the model and the user-defined
Model Name that contains the referenced response definition.
16. An inconsistent number of responses can be referenced via multiple DRESP#L VARTYPE’s.
The following requirements should be met for such entries:
2. DRESP# entries listed on other DRESP#L VARTYPE’s should reference the same number
of responses.
3. If requirement (1) above is not met, then the number of responses referenced by all
the DRESP# entries (listed on all the DRESP#L VARTYPE’s) should be equal.
Example
Allowed
Not Allowed
DRESP1 1 R1 STRESS ELEM SVM1 1
2
DRESP1 2 R2 STRESS PSHELL SVM2 1
DRESP2 3 MNA 1
+ DRESP1L 4 0
+ DRESP1L 1 2
+ DRESP1L 2 2
DRESP1 4 vol VOLUME
DEQATN 1 f(a,b,c)=a+b+c
Description
When a desired response is not available from OptiStruct, either directly or via equations, it
may be calculated through external user-supplied functions implemented in shared/dynamic
libraries or external files (see External Reponses). The DRESP3 card identifies the external
function to be called and defines the parameters to be transferred to that function.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
...
ID8
C ELLIN C I1 C I2 C I3 ... C In
C ELLOUT CO
SENSOPT METHOD
C ELLIN C I1 thru C In
EIGV2 LID2 G2 C2
USRDATA STRNG
...
Field Contents
No default (Character)
No default (Character)
No default (Character)
MODEL User-defined model names defined on the ASSIGN, MMO entry (see
NAME# comment 21).
RESP RESP identifier that defines the response to be returned by the external
function.
MAXRESP MAXRESP identifier that defines the number of responses available in the
external function.
VARTYPE# Indicates the type of variables to follow. Can be one of: DESVAR,
DTABLE, DGRID, DGRIDB, DEIGV, DRESP1, DRESP1L, DRESP2, DRESP2L,
DVPREL1, DVPREL2, DVCREL1, DVCREL2, DVMREL1, DVMREL2, DVMBRL1,
DVMBRL2, USRDATA or SLAVE (see comment 18).
No default (Character)
CELLIN CELLIN flag indicates that a list of Microsoft Excel worksheet cell
references are to follow, that define response input values (see comments
19 and 20).
CI# A list of Microsoft Excel worksheet cell references that define response
input values (see comments 19 and 20).
No default (Alphanumeric)
CELLOUT CELLIN flag indicates that a Microsoft Excel Worksheet cell reference is to
follow that defines the response output value (see comments 19 and 20).
No default (Alphanumeric)
NONE (or blank): Sensitivities are not provided. Full evaluations are
performed at every step of the approximation process.
Gi Grid IDs.
Ci Component IDs.
No default (1, 2, 3, 4, 5, or 6)
Comments
1. DRESP3 entries are referenced from the subcases through one of DESOBJ, DESSUB, or
DESGBL.
2. DRESP3 entries must have unique identification numbers with respect to DRESP2 and
DRESP1 entries.
3. DRESP1L, DRESP2L define a response defined with a DRESP1 or DRESP2, respectively, and
a SUBCASE. The SUBCASE number 0 should be used for global responses.
4. Responses with the same region identifier are grouped together into the same region. If
the region identifier is blank, then a separate region is formed for each DRESP3 definition.
The RTYPE EXTERNAL on the DSCREEN definition refers to DRESP3 responses. It is
important to ensure that responses with the same region identifier reference similar
external responses. For further information, refer to Constraint Screening in the User's
Guide.
5. Any number of VARTYPE# continuation lines can be defined. The order in which the
VARTYPE# continuation lines are listed on the DRESP2 card is not prescribed. The same
VARTYPE# can be repeated any number of times, in any position, on the card.
6. The entries on the DRESP3 card are assigned to the parameters passed to the external
function in the order that they occur.
8. If DRESP1L, DRESP2L is used for a constrained DRESP3, DESGLB must be used to identify
the DRESP3.
10. If the DRESP3 data is referenced by DESOBJ data, the DESOBJ data must be above the
first SUBCASE if:
The DESOBJ data must be in the correct static or eigenvalue SUBCASE if the DRESP3
contains static or eigenvalue DRESP1 responses.
11. DRESP1 of RTYPE = WCOMB, WFREQ, and COMP cannot be referenced by DRESP3 data.
13. The RESP field may be used to request a specific response from the external function,
while MAXRESP defines the maximum number of responses available in that function.
External functions can be implemented to compute any number of responses and to return
any subset of these responses. This approach has two main benefits:
There is no need to write a specific external function for each response that you want
computed. One general function may be written instead. In many cases, this allows
for easier code maintenance and better code reusability.
OptiStruct will automatically group responses which point to the same external
function, and which use the same set of input data. The external function will only be
called once for that group of responses, which may save computational time in the
library.
14. The SLAVE continuation line indicates that the input data (DESVAR, and so on) for the
current DRESP3 card is identical to the input data of the master DRESP3 card. There
cannot be any other continuation line when SLAVE is used.
This simplifies the DRESP3 definition and reduces potential errors when modifying input
decks, either via the HyperMesh interface or manually. Also, as explained above,
OptiStruct will group responses that share the same input data.
15. The data in the STRNG field is character string based. It provides a convenient way to
pass constants to the external response server routines. The maximum number of
characters allowed in 32000.
16. The eigenvector values provided on the DEIGV continuation are normalized against the
mass matrix. No sensitivities are calculated for these values.
17. Performance of the sensitivity evaluation method is problem dependent, and selection of a
method depends on the number of arguments and the cost of each evaluation. The
default method works best for most problems. However, if the approximation module is
observed to be very slow with the default, AUTO or USER can be tried.
18. The DGRID and DGRIDB VARTYPE’s can be used to select grid point locations as variables
Examples:
DGRIDB:
The VARTYPE DGRIDB can be used to select grid point locations in the basic coordinate
system. The basic coordinate system is the default rectangular coordinate system in
OptiStruct.
DGRID:
The VARTYPE DGRID can be used to select the grid point locations in the local coordinate
system of each grid point. This local coordinate system may be specified by the CP field
of the GRID Bulk Data Entry for a particular grid point of interest. All local (or user
defined) coordinate systems are directly or indirectly based on the default basic
coordinate system.
19. An external Microsoft Excel workbook can be referenced on the GROUP field via the
LOADLIB I/O Options Entry.
20. Multiple CELLIN continuation lines can be specified; each CI# entry on the CELLIN
continuation lines corresponds to responses (ID#) defined on the VARTYPE# continuation
lines. See External Responses in the User’s Guide for further information.
21. Multiple RID-Model Name pairs can be specified on a single DRESPM continuation line.
These responses can be used similar to responses defined via the VARTYPE# -ID# entries.
ASSIGN, MMO can be used to identify the filename of the model and the user-defined
Model Name that contains the referenced response definition.
Description
Defines design constraint screening data. Refer to Constraint Screening in the User's Guide
section.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Alternate Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Associated Cards
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
THOLD Normalized threshold value – constraint will not be retained during the
current iteration if its normalized value is below THOLD.
MAXC Maximum number of constraints to be retained for each region definition and
each load case.
When this is activated, the screening algorithm will seek to retain the least
number of responses that are necessary for stable convergence.
LEVEL The automatic constraint screening has levels 1 through 5, with 1 being the
least aggressive (more responses retained) and 5 being the most aggressive
(less responses retained). Level 3 is the default.
Comments
1. RTYPE may be any of the RTYPEs allowed on the DRESP1 entry, or EQUA or EXTERNAL or
AUTO.
2. RTYPE EQUA refers to DRESP2 definitions. If DRESP2 definitions are given the same region
identifier, they should reference similar equations.
3. RTYPE EXTERNAL refers to DRESP3 definitions. If DRESP3 definitions are given the same
region identifier, they should reference similar equations.
4. F is the normalized constraint. If F> THOLD, then the constraint will be retained. F is
calculated with respect to the upper and lower bounds of the constraint as follows:
6. When no DSCREEN definitions are present in the input data, automatic constraint
screening is active for all responses. The presence of any DSCREEN definition disables
the automatic screening for all response types.
7. With automatic screening, the upper bound on the EIGRL card for buckling analysis will be
adjusted in order to calculate only the necessary buckling eigenvalues (responses) that
are potentially retained in the optimization.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DSHAPE ID
GID7 GID8 … …
DRAFT
EXTR EC ID XE YE ZE
… …
… …
BMESH BMID
DTYPE Specifies the direction type for the free-shape variation (Comment 1).
MVFACTOR Initial limit on the movement factor of the design grids. The unit of
MVFACTOR is the average mesh size of meshes adjacent to grids defined
after GRID.
Only the initial value of this limit can be set. The values in subsequent
optimization iterations are automatically adjusted to enhance to enhance
iterative stability and convergence speed; however, they will never be
greater than the initial limit.
Default = 10 (Integer)
No default
No default
Default = 1 (1 or 2)
NTRANS Number of design grid layers in the transition zone to non-design area,
where additional treatment will be applied to produce smooth transition
(Comment 4).
GRID GRID flag indicating that a list of grid IDs is to follow. These grids are
design variables for the free-shape optimization.
GMETH Flag indicating that a list of grids is to be defined by a list of grid IDs or a
single SET reference.
GID# Grid identification numbers. List of grids for which this DSHAPE card is
defined.
GSETID Grid SET identification number. A grid set containing design grids for free-
shape optimization.
PATRN PATRN flag indicating that variable pattern grouping is active. Indicates
that information about the pattern group will follow.
Default = 0 (0 or 10)
AID/XA, YA, ZA Variable pattern grouping anchor point. These fields define a point that
determines how grids are grouped into variables (See comment 3). The X,
Y, and Z values are in the global coordinate system. You may put a grid
ID in the AID/XA field to define the anchor point.
FID/VXF, VYF, Direction of first vector for variable pattern grouping. These fields define
VZF an xyz vector which determines how grids are grouped into variables
(Comment 3). The X, Y, and Z values are in the global coordinate system.
If FID is defined, it defines a vector pointing from grid AID or point (XA,
YA, and ZA) to grid FID.
If VXF, VYF, VZF are defined, it defines a vector pointing from point (XA,
YA, and ZA) to point (XA+VXF,YA+VYF,ZA+VZF). (XA, YA, and ZA) are
coordinates of the anchor point defined by AID or XA, YA, and ZA.
If all fields are blank and the PATYP field is not blank or zero, OptiStruct
gives an error.
No default
DRAW DRAW flag indicating that casting constraints are being applied. Indicates
that draw direction information is to follow. Only valid for design grids on
solid elements.
DAID/XDA, YDA, Draw direction anchor point. These fields define the anchor point for draw
ZDA direction of the casting. The point may be defined by entering a grid ID in
the DAID field or by entering X, Y, and Z coordinates in the XDA, YDA, and
ZDA fields, these coordinates will be in the basic coordinate system.
DFID/XDF, YDF, Direction of vector for draw direction definition. These fields define a
ZDF point. The vector goes from the anchor point to this point. The point
may be defined by entering a grid ID in the DFID field or by entering X, Y,
and Z coordinates in the XDF, YDF, and ZDF fields, these coordinates will
be in the basic coordinate system.
SDCON# SDCON# flag indicating that side constraints are being applied.
SDCID# The ID of a coordinate system which the following XL#, XU#, YL#, YU#,
ZL#, or ZU# components are resolved in.
XL#, XU#, YL#, Side constraints defined by lower and upper bounds of coordinates, which
YU#, ZL#, ZU# restrict the moving space of the design grids. Any of the six fields could
be blank, which means the corresponding coordinate is not constrained.
EXTR EXTR flag indicating that extrusion constraints are being applied.
Indicates that extrusion information is to follow. Only valid for design
grids on solid elements.
For Free-Shape 9.0, only consider two simple extrusion paths: Line and
Circle.
XE, YE, ZE When ECID is a rectangular system ID, X, Y, and Z are components of a
vector under system EID, which define the extrusion path.
GRIDCON GRIDCON flag indicating that a list of grids with associated constraints are
to follow.
Note: Grids within the smoothing zone (defined by NSMOOTH) will move
during Free-shape optimization to avoid mesh distortion without
changing the shape of the model. Users can also constrain the
movement of these grids by GRIDCON even if they are not defined
after GRID.
GCMETH Flag indicating that a list of grids is to be defined by a list of grid IDs or a
single SET reference.
GCSETID# Grid SET identification numbers. IDs of certain grid SETs which are
constrained to move in a predefined manner.
GDID# IDs of certain grids which are constrained to move in a predefined manner.
No default (Integer > 0, ID must also be present in the list following the
GRID flag)
CTYPE# Specifies the type of constraint applied to the grid GDID# (Comment 2).
X#, Y#, Z# X, Y, and Z components of a vector, which either defines the direction in
which the grid GDID# is constrained to move, or the normal of a plane on
which the grid GDID# is constrained to remain.
BMID The BMFACE ID which defines a list of QUADs and/or TRIAs which define a
barrier that the design surface will not penetrate during shape
optimization.
Comments
For a more detailed description, refer to Free-shape Optimization in the User’s Guide.
b) DIR – grid is forced to move along the vector defined by the following fields.
c) NORM – grid is forced to remain on a plane for which the following fields define the
normal direction.
For a more detailed description, refer to Free-shape Optimization in the User’s Guide.
3. For a single plane of symmetry (TYP = 10), the plane is defined normal to the first vector
and is located at the anchor node.
4. The NTRANS option allows you to achieve a smooth transition between design and non-
design regions. This additional smoothness, however, comes with an inherent cost of a
reduction in design flexibility. NTRANS improves design smoothness across the transition
zone between design and non-design regions at the expense of design flexibility.
For detailed information illustrating the working mechanism of NTRANS, refer to Defining
Free-shape Design Regions in the User’s Guide.
5. The draft angle can be specified in degrees via the DRAFT field, as illustrated in the figure
below. Geometric constraints (GRIDCON and SDCON) may not be satisfied when the draft
angle is activated:
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
+ EID7 …
+ C ANG7 …
+ VANG7 …
Field Contents
EID# Entity identification numbers. List of entities of type ETYPE for which this
DSHUFFLE card is defined.
MAXSUCC MAXSUCC flag indicating that the "maximum number of successive plies"
constraint is applied. Multiple MAXSUCC constraints are allowed (see
Comment 1).
VSUCC Allowable percentage violation for the MAXSUCC constraint. 0.0 indicates
that this constraint cannot be violated.
PAIR PAIR flag indicating that a pairing constraint is applied (see Comment 2).
PANGLE1 First ply orientation, in degrees, to which the PAIR constraint is applied.
PANGLE2 Second ply orientation, in degrees, to which the PAIR constraint is applied.
POPT Pairing option. SAME indicates that the stacking sequence should remain
the same for consecutive pairs. REVERSE indicates that the stacking
sequence should be reversed for alternate pairs.
CORE CORE flag indicating that a ply sequence for the core layer is defined.
Only one CORE sequence is allowed (see Comment 3).
No default (Real)
COVER COVER flag indicating that a ply sequence for the cover layer is defined.
Only one COVER sequence is allowed (see Comment 3).
No default (Real)
RANGE Indicates that starting and ending ply identification numbers are defined in
the following fields to specify the range of plies to be shuffled. OptiStruct
will only shuffle plies between PIDSTA and PIDEND. Multiple DSHUFFLE
entries can be created to define different ply ranges.
PIDSTA The ply identification number (starting ply) that defines the first ply in the
range to be shuffled.
PIDEND The ply identification number (ending ply) that defines the last ply in the
range to be shuffled.
Comments
1. The MAXSUCC constraint indicates that the stacking sequence should contain no sections
with more than a given number of successive plies with the same orientation. In the case
of symmetrical laminates, this constraint accounts for the mirrored successive plies on
both sides of the symmetry plane. In the image below, (a) shows invalid and valid
sequences for a non-symmetrical stack, and (b) shows invalid and valid sequences for a
symmetrical stack, both for MAXSUCC=3.
3. The CORE and COVER constraints specify stacking sequences for the core and cover
layers respectively. Plies are listed from the bottom surface upward, in respect to the
element’s normal direction. In the example below, the sequence for the core is (0°, 0°,
90°, 90°) while the sequence for the cover is defined as (90°, 90°, 0°, 0°).
Note that, for non-symmetrical laminates, COVER actually corresponds to the bottom
cover, whereas CORE corresponds to the upper cover. At this point, it is not possible to
create an actual core for non-symmetrical stacks.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PID7 … … … … … …
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
THIC K T0 T1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
STRESS UBOUND
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MEMBSIZ MINDIM
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
UC YC SID/XS YS ZS
Optional continuation lines for "Master" definition for pattern repetition constraint:
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MASTER
C AID/
C OORD C ID YC A ZC A C FID/XC F YC F ZC F
XC A
C SID/
YC S ZC S C TID/XC T YC T ZC T
XC S
Optional continuation lines for "Slave" definition for pattern repetition constraint:
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SLAVE DSIZE_ID SX SY SZ
C SID/
YC S ZC S C TID/XC T YC T ZC T
XC S
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Alternate continuation line for zone based free-sizing definition (Alternate Format):
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
T0 Minimum thickness.
T1 Maximum thickness.
STRESS STRESS flag indicating that von Mises stress constraints are
active and that an upper bound value for the stress is to follow.
See comment 4.
MEMBSIZ MEMBSIZ flag indicating that member size control is active for
the properties listed. Indicates that MINDIM is to follow.
LTEXC Exclusion flag indicating that certain plies are excluded from the
LAMTHK constraint. The following options are supported:
PTGRP Ply orientation in degrees, ply sets or ply IDs, to which the
PLYTHK constraint is applied, depending on the PTOPT
selection.
PTOPT Ply selection options for the PLYTHK constraint. Plies can be
selected based on the following:
PTEXC Exclusion flag indicating that certain plies are excluded from the
PLYTHK constraint. The following options are supported:
PPGRP Ply orientation in degrees, ply sets or ply IDs, to which the
PLYPCT constraint is applied, depending on the PPOPT selection.
Default = blank (Real > 0.0, < 1.0 and > PPMIN)
PPOPT Ply selection options for the PLYPCT constraint. Plies can be
selected based on the following:
PPEXC Exclusion flag indicating that certain plies are excluded from the
PLYPCT constraint. The following options are supported:
PMGRP Ply orientation in degrees, ply sets or ply IDs, to which the
PLYMAN constraint is applied, depending on the PMOPT
selection.
PMOPT Ply selection options for the PLYMAN constraint. Plies can be
selected based on the following:
PMEXC Exclusion flag indicating that certain plies are excluded from the
PLYMAN constraint. The following options are supported:
BGRP1 First ply orientation in degrees, ply sets or ply IDs, to which the
BALANCE constraint is applied, depending on the BOPT
selection.
BGRP2 Second ply orientation in degrees, ply sets or ply IDs, to which
the BALANCE constraint is applied, depending on the BOPT
selection.
BOPT Ply selection options for the BALANCE constraint. Plies can be
selected based on the following:
CGRP Ply orientation in degrees, ply sets or ply IDs, to which the
CONST constraint is applied, depending on the COPT selection.
COPT Ply selection options for the CONST constraint. Plies can be
selected based on the following:
PDGRP Ply orientation in degrees, ply sets or ply IDs, to which the
PLYDRP constraint is applied, depending on the PDOPT selection.
PLYSLP (Default)
PLYDRP
TOTSLP
TOTDRP
PDOPT Ply selection options for the PLYDRP constraint. Plies can be
selected based on the following:
PDEXC Exclusion flag indicates that certain plies are excluded from the
PLYDRP constraint. The following options are supported:
PDX, PDY, PDZ Used to specify the drop-off direction when DIRECT is input in
the PDDEF field. See comment 12.
PATRN PATRN flag indicating that pattern grouping is active for the
properties listed. Indicates that information for pattern
grouping is to follow.
AID/XA, YA, ZA Anchor point for pattern grouping. The point may be defined by
entering a grid ID in the AID field or by entering X, Y, and Z
coordinates in the XA, YA, and ZA fields. These coordinates will
be in the basic coordinate system. See comment 1.
FID/XF, YF, ZF First point for pattern grouping. The point may be defined by
entering a grid ID in the FID field or by entering X, Y, and Z
coordinates in the XF, YF, and ZF fields. These coordinates will
be in the basic coordinate system. See comment 1.
SID/XS, YS, ZS Second point for pattern grouping. The point may be defined by
entering a grid ID in the SID field or by entering X, Y, and Z
coordinates in the XS, YS, and ZS fields. These coordinates will
be in the basic coordinate system. See comment 1.
MASTER MASTER flag indicating that this design variable may be used as
a master pattern for pattern repetition. See comment 2.
SLAVE SLAVE flag indicating that this design variable is slave to the
master pattern definition referenced by the following DSIZE_ID
entry. See comment 2.
CAID/XCA, YCA, ZCA Anchor point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CAID field or
by entering X, Y, and Z coordinates in the XCA, YCA, and ZCA
fields. These coordinates will be in the basic coordinate
system. See comment 2.
CFID/XCF, YCF, ZCF First point for pattern repetition coordinate system. The point
may be defined by entering a grid ID in the CFID field or by
entering X, Y, and Z coordinates in the XCF, YCF, and ZCF
fields. These coordinates will be in the basic coordinate
system. See comment 2.
CSID/XCS, YCS, ZCS Second point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CSID field or
by entering X, Y, and Z coordinates in the XCS, YCS, and ZCS
fields. These coordinates will be in the basic coordinate
system. See comment 2.
CTID/XCT, YCT, ZCT Third point for pattern repetition coordinate system. The point
may be defined by entering a grid ID in the CTID field or by
entering X, Y, and Z coordinates in the XCT, YCT, and ZCT
fields. These coordinates will be in the basic coordinate
system. See comment 2.
FATIGUE FATIGUE flag indicating that fatigue constraints are active and
their definition is to follow.
No default (Real)
Comments
1. There are currently five pattern grouping options for free-size optimization:
This type of pattern grouping requires that the anchor point and the first point be defined.
A vector from the anchor point to the first point is normal to the plane of symmetry.
This type of pattern grouping requires that the anchor point, first point, and second point
be defined. A vector from the anchor point to the first point is normal to the first plane of
symmetry. The second point is projected normally onto the first plane of symmetry. A
vector from the anchor point to this projected point is normal to the second plane of
symmetry.
This type of pattern grouping requires that the anchor point, first point, and second point
be defined. A vector from the anchor point to the first point is normal to the first plane of
symmetry. The second point is projected normally onto the first plane of symmetry. A
vector from the anchor point to this projected point is normal to the second plane of
symmetry. The third plane of symmetry is orthogonal to both the first and second planes
of symmetry, passing through the anchor point.
This type of pattern grouping requires that the anchor point, first point, and number of
cyclical repetitions be defined. A vector from the anchor point to the first point defines
the axis of symmetry.
This type of pattern grouping requires that the anchor point, first point, second point,
and number of cyclical repetitions be defined. A vector from the anchor point to the first
For a more detailed description, refer to the Pattern Grouping for Free-Size Optimization
page contained within the User’s Guide section Manufacturability for Free-Size
Optimization.
2. Pattern repetition allows similar regions of the design domain to be linked together so as
to produce similar topological layouts. This is facilitated through the definition of "Master"
and "Slave" regions. A DSIZE card may only contain one MASTER or SLAVE flag. For both
"Master" and "Slave" regions, a pattern repetition coordinate system is required and is
described following the COORD flag. In order to facilitate reflection, the coordinate
system may be a left-handed or right-handed Cartesian system. The coordinate system
may be defined in one of two ways, listed here in order of precedence:
Four points are defined and these are utilized as follows to define the coordinate
system (this is the only way to define a left-handed system):
- A vector from the anchor point to the first point defines the x-axis.
- The second point lies on the x-y plane, indicating the positive sense of the y-axis.
A rectangular coordinate system and an anchor point are defined. If only an anchor
point is defined, it is assumed that the basic coordinate system is to be used.
Multiple "Slaves" may reference the same "Master."
Scale factors may be defined for "Slave" regions, allowing the "Master" layout to be
adjusted.
For a more detailed description, refer to the Pattern Repetition for Free-Size Optimization
contained within the User’s Guide section Manufacturability for Free-Size Optimization.
3. It is recommended that a MINDIM value be chosen which allows for the formation of
members that are at least three elements thick. When pattern grouping constraints are
active, a MINDIM value of three times the average element edge length is enforced, and
user-defined values (which are smaller than this value) will be replaced by this value.
4. Von Mises stress constraints may be defined for topology and free-size optimization
through the STRESS optional continuation line on the DTPL or the DSIZE card. There are
a number of restrictions with this constraint:
The definition of stress constraints is limited to a single von Mises permissible stress.
The phenomenon of singular topology is pronounced when different materials with
different permissible stresses exist in a structure. Singular topology refers to the
problem associated with the conditional nature of stress constraints that is the stress
constraint of an element disappears when the element vanishes. This creates another
problem in that a huge number of reduced problems exist with solutions that cannot
usually be found by a gradient-based optimizer in the full design space.
Stress constraints for a partial domain of the structure are not allowed because they
often create an ill-posed optimization problem since elimination of the partial domain
would remove all stress constraints. Consequently, the stress constraint applies to the
The capability has built-in intelligence to filter out artificial stress concentrations
around point loads and point boundary conditions. Stress concentrations due to
boundary geometry are also filtered to some extent as they can be improved more
effectively with local shape optimization.
Due to the large number of elements with active stress constraints, no element stress
report is given in the table of retained constraints in the .out file. The iterative
history of the stress state of the model can be viewed in HyperView or HyperMesh.
Lower and upper bounds on the total thickness of the laminate (LAMTHK).
Lower and upper bounds on the thickness of a given orientation (PLYTHK).
Lower and upper bounds on the thickness percentage of a given orientation (PLYPCT).
Linking between the thicknesses of two given orientations (BALANCE).
Constant (non-designable) thickness of a given orientation (CONST).
LAMTHK, PLYTHK, PLYPCT, and PLYMAN can be applied locally to sets of elements.
There can be elements that do not belong to any set.
For a more detailed description and an example, refer to Optimization of Composite
Structures in the User’s Guide.
6. PLYMAN has no influence on the free-size phase, but this information will be translated
into the TMANUF entry on the PLY card for the sizing phase.
8. The core is designable by default. It can be made non-designable through the CONST
manufacturing constraint. To facilitate this, the keyword CORE can be used instead of a
ply ID when BYPLY is activated.
9. The core is excluded from the LAMTHK, PLYTHK, PLYPCT and PLYMAN manufacturing
constraints by default.
10. Legacy data field PTMAN (for manufacturable ply thickness) defined on the PLYTHK and
PLYPCT entries is supported. However, it is now recommended to define the
manufacturable ply thickness in the PMMAN field through the PLYMAN continuation line as
this offers more control.
11. The options for selecting the type of drop-off constraints for PDTYP are defined for a set
of plies, as shown in the figures below:
PLYSLP
TOTSLP
TOTDRP
Assuming that the plies are stacked as shown above, you have the following definitions:
Field Value
PDX, PDY, PDZ PDX, PDY and PDZ are real numbers.
Description
Defines responses and their target values for a system identification problem.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
+ RID2 SID2 T2 W2
+ ...
+ RIDn SIDn Tn Wn
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
+ 5 5 0.05
Associated Cards
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(Integer > 0)
No default (Character)
(Integer > 0)
Ti Target value.
No default (Real)
Wi Weighting factor.
Comments
1. If the DSYSID entry is referenced by a DESOBJ subcase entry, a least squares objective
function is used in the optimization. The objective function is the sum of the squared,
weighted, normalized differences between the target responses and those calculated by
the finite element analysis:
If the DSYSID entry is referenced by a MINMAX or MAXMIN subcase entry, the beta
method is applied in the optimization as follows:
2. DSYSID entries must have unique identification numbers with respect to DRESP1, DRESP2,
and DRESP3 entries.
4. In order to use DSCREEN to control the number of retained responses when performing a
system identification, RTYPE=EQUA needs to be used on the DSCREEN entry.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Character)
(Real)
Comments
1. If a DTABLE entry has a pair of blank fields, they are ignored. If there are other
constants after the blank fields, they are read in.
2. If fields are full of zeros, the constant label is "0", and the value is 0.0.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TID3 DAMP3 … … … … … …
… …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
4 0.04
Field Contents
No default (A, V, D)
No default (Real)
Comments
2. The TID#, DAMP# pairs list the TABLED1 entry, which defines a line of the spectrum and
the damping value assigned to it. The damping value is in the units of fraction of critical
damping.
3. Refer to Response Spectrum Analysis in the User’s Guide for more details.
Description
Defines units for multi-body, component mode synthesis (flexible-body preparation), and
geometric nonlinear solution sequences.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DTI UNITS 1 KG N M S
Field Contents
Default = KG (KG, LBM, SLUG, GRAM, OZM, KLBM, MGG, SLINCH, UG, NG,
USTON, or MG)
Default = N (N, LBF, KGF, OZF, DYNE, KN, KLBF, MN, UN, or NN)
Default = MM (MM, KM, M, CM, MI, FT, IN, UM, NM, ANG, YD, MIL, or
UIN)
kg kilogram
lbm pound-mass
slug slug
gram gram
ozm ounce-mass
mgg megagram
slinch 12 slugs
ug Microgram
ng Nanogram
uston US ton
mg Milligram
n newton
lbf pounds-force
kgf kilograms-force
ozf ounce-force
dyne dyne
kn kilonewton
mn Millinewton
nn Nanonewton
km kilometer
m meter
cm centimeter
mm millimeter
mi mile
ft foot
in inch
um Micrometer
nm Nanometer
ang Angstrom
yd Yard
mil Milli-inch
uin Micro-inch
s seconds
h hours
min minutes
ms milliseconds
us Microsecond
d day
5. PARAM, WTMASS is ignored for the multi-body and component mode synthesis (flexible-
body preparation) solution sequences. Unit data for these solution sequences is supplied
on the DTI,UNITS bulk data entry.
6. This DTI, UNITS data entry is the same as the UNITS entry.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PID7 … … … … … …
PATRN2 UC YC SID/XS YS ZS
BOUNDS LB UB INIT
Optional continuation lines for "Master" definition for pattern repetition constraint:
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MASTER
C SID/ YC S ZC S C TID/ YC T ZC T
XC S XC T
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SLAVE DTPL_ID SX SY SZ
C SID/ YC S ZC S C TID/ YC T ZC T
XC S XC T
Example 1
This example defines a topography design variable which allows for swages to be created in
components referencing the PSHELL properties 1, 9, and 23. The swages will have a
minimum width of 3 units, a draw angle of 600, and a maximum height of 5 units. The draw
direction will be in the element’s normal direction, but the swages may grow in either the
positive or negative direction. The swages should be grouped such that they form a
cyclical pattern of 1200 intervals about the z-axis, through the point (0,25,0), and they
also should be symmetrical about the xy plane.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DTPG 1 PSHELL 1 9 23
Example 2
This example defines a topography design variable that references the shape variables
defined by the DVGRIDs with ID 1. The swages will have a minimum width of 5 units and a
draw angle of 750. The height and draw direction of the swages is defined by the DVGRID
cards. Also ensure that the swages can only grow in the positive direction as defined by
the DVGRID cards.
DTPG 1 DVGRID 1
Field Contents
If TYPE is DVGRID, then this entry is the Design Variable Number for a
set of DVGRIDs. Only one DVID may be given.
MW Bead minimum width. This parameter controls the width of the beads
in the model [recommended value between 1.5 and 2.5 times the
average element width]. See comment 1.
ANG Draw angle in degrees. This parameter controls the angle of the
sides of the beads (recommended value between 60 and 75 degrees).
See comment 1.
HGT Draw height. This parameter sets the maximum height of the beads
to be drawn. This field is only valid if TYPE is PSHELL or PCOMP.
norm/XD,YD,ZD Draw direction. If norm/XD field is ‘norm’, the shape variables will be
created in the normal directions of the elements. If all the fields are
real, the shape variable will be created in the direction specified by
the xyz vector defined by the three fields. The X, Y, and Z values
are in the global coordinate system. This field is only valid if TYPE is
PSHELL or PCOMP.
SKIP Boundary skip. This parameter tells OptiStruct to leave certain nodes
out of the design domain. If ‘none’, all nodes attached to elements
whose PIDs are specified will be a part of the shape variables. If ‘bc’
or ‘spc’, any nodes which have SPC or SPC1 declarations are omitted
from the design domain. If ‘load’, any nodes which have FORCE,
FORCE1, MOMENT, MOMENT1, or SPCD declarations are omitted from
the design domain. If ‘both’, nodes with either ‘spc’ or ‘load’
declarations are omitted from the design domain. This field is only
valid if TYPE is PSHELL or PCOMP.
AID/XA,YA,ZA Variable grouping pattern anchor point. These fields define a point
that determines how grids are grouped into variables. See comment
3. The X, Y, and Z values are in the global coordinate system. You
may put a grid ID in the AID/XA field to define the anchor point.
FID/XF,YF,ZF Direction of first vector for variable pattern grouping. These fields
define an xyz vector which determines how grids are grouped into
variables (See comment 3). The X, Y, and Z values are in the global
coordinate system. You may put a grid ID in the FID/XF field to
define the first vector. This vector goes from the anchor point to
this grid. If all fields are blank and the TYP field is not blank or zero,
OptiStruct gives an error.
No default
No default
BOUNDS BOUNDS flag indicating that information on upper and lower limits and
the initial value for grid movement are to follow.
INIT The initial value of the variables controlling grid movement. This sets
the initial value on grid movement equal to INIT*HGT.
where:
MASTER MASTER flag indicating that this design variable may be used as a
master pattern for pattern repetition.
COORD COORD flag indicating information regarding the coordinate system for
pattern repetition is to follow. This is required if either MASTER or
SLAVE flags are present.
CAID/XCA, Anchor point for pattern repetition coordinate system. The point
YCA, ZCA may be defined by entering a grid ID in the CAID field or by entering
X, Y, and Z coordinates in the XCA, YCA, and ZCA fields. These
coordinates will be in the basic coordinate system. See comment 6.
CFID/XCF, YCF, First point for pattern repetition coordinate system. The point may
ZCF be defined by entering a grid ID in the CFID field or by entering X, Y,
CSID/XCS, Second point for pattern repetition coordinate system. The point
YCS, ZCS may be defined by entering a grid ID in the CSID field or by entering
X, Y, and Z coordinates in the XCS, YCS, and ZCS fields. These
coordinates will be in the basic coordinate system. See comment 6.
CTID/XCT, Third point for pattern repetition coordinate system. The point may
YCT, ZCT be defined by entering a grid ID in the CTID field or by entering X, Y,
and Z coordinates in the XCT, YCT, and ZCT fields. These
coordinates will be in the basic coordinate system. See comment 6.
SLAVE SLAVE flag indicating that this design variable is slaved to the master
pattern definition referenced by the following DTPL_ID entry. See
comment 6.
Comments
1. The bead minimum width and draw angles are used to determine the geometry of the
shape variables. The figure below shows a cross-section of a single shape variable fully
extended normal to the plane of the design elements. The top of the bead is flat across
the circular area with a diameter equal to the minimum bead width parameter. The sides
of the bead taper down at an angle equal to the draw angle parameter.
2. The buffer zone is a parameter that controls how the interfaces between design and non-
design elements are treated. If active, OptiStruct will place the shape variables far
enough away from the non-design elements so that the proper bead widths and draw
angles are maintained. If inactive, the boundary between the beads and non-design
elements will have an abrupt transition. Any nodes that were skipped due to the
boundary skip parameter (field 10) will also have a buffer zone created around them.
Transitions between design and non-design elements with and without buffer zone
3. Symmetry of topography optimization can be enforced across one, two, or three planes.
Defining symmetry planes for symmetric model and loading conditions is recommended
because automatic variable generation may not be symmetric if it is not enforced. A
symmetric mesh is not necessary, OptiStruct will create variables that are very close to
identical across the plane(s) of symmetry. If the mesh is larger on one side of the
plane(s) of symmetry than the other, OptiStruct will reflect variables created on the
‘positive’ side of the plane(s) of symmetry to the other side(s) but will not create
variables on the ‘negative’ side(s) of the plane(s) of symmetry that do not overlap with
the positive side. The positive side of the plane(s) of symmetry is the one in which the
first vector, second vector, and cross product thereof are pointing toward.
4. Variable pattern grouping may be defined for a DTPG card. OptiStruct will generate shape
variables based on the type of pattern selected in field 20. For variable grouping pattern
types 1 through 14, only the first vector and anchor node need to be defined. For
variable pattern grouping types 20 or higher, the first and second vectors need to be
defined as well as the anchor node. If a grid is used to define the first vector, the normal
vector will begin at the anchor point and extend towards the given grid (see below).
Grids or xyz data may be used for either the first vector, second vector, or anchor point
and can be a mixture, (that is the anchor point may be determined by a grid and the first
vector determined by xyz data or vice-versa).
One very useful feature for topography optimization in OptiStruct is the automatic
generation of shape variables in simple patterns. In many cases, due to manufacturing
constraints or the risk of elements being collapsed upon them during shape optimization, it
The second vector is calculated by taking the grid point or vector defined in fields 22, 23,
and 24 and projecting it onto plane 1. If a grid point was used to define the second
vector, the second vector is a vector running from the anchor node to the projected grid
point. If a vector was used to define the second vector, the base of the projected
vector is placed at the anchor point. The second vector is normal to plane 2 (see
below).
6. Pattern repetition allows similar regions of the design domain to be linked together so as
Four points are defined and these are utilized as follows to the define the coordinate
system (this is the only way to define a left-handed system):
- A vector from the anchor point to the first point defines the x-axis.
- The second point lies on the x-y plane, indicating the positive sense of the y-axis.
- The third point indicates the positive sense of the z-axis.
A rectangular coordinate system and an anchor point are defined. If only an anchor
point is defined, it is assumed that the basic coordinate system is to be used.
Multiple "Slaves" may reference the same "Master."
Scale factors may be defined for "Slave" regions, allowing the "Master" layout to be
adjusted.
For a more detailed description, refer to the Pattern Repetition page contained within the
User's Guide section Manufacturability for Topography Optimization.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PID7 … … … … … …
… …
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TMIN T0
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
STRESS UBOUND
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MESH MTYP
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
OPID8 … … … … … …
NOHOLE
STAMP TSTAMP
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
EXTR ETYP
EP1_ID8 … … … … … …
… …
EP2_ID8 … … … … … …
… …
Optional continuation lines for "Master" definition for pattern repetition constraint:
MASTER
C SID/ YC S ZC S C TID/ YC T ZC T
XC S XC T
Optional continuation lines for "Slave" definition for pattern repetition constraint:
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SLAVE DTPL_ID SX SY SZ
C SID/ YC S ZC S C TID/ YC T ZC T
XC S XC T
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
UC YC SID/XS YS ZS
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MAT MATOPT
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 1
Define a topology design variable that allows the thickness of components referencing the
PSHELL properties 7, 8, and 17 to vary between 1.0 and 5.0 (the thickness defined on
PSHELL definitions with PID 7, 8, and 17 is 5.0). The optimized design should contain
members whose width is no less than 60.0 units.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DTPL 1 PSHELL 7 8 17
MEMBSIZ 60.0
TMIN 1.0
Example 2
Define a topology design variable for components referencing the PSOLID properties 4, 5,
and 6. The optimized design should contain members whose diameter is no less than 60.0
units. The final design will be manufactured using a casting process, where the draw
direction lies along the x-axis. The components referencing PSOLID properties 10, 11, and
12 are non-designable, but will form part of the same casting as the designable
components.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DTPL 1 PSOLID 4 5 6
MEMBSIZ 60.0
Field Contents
PTYPE Property type for which DTPL card is defined, PBAR, PBARL,
PBEAM, PBEAML, PBUSH, PROD, PWELD, PSHELL, PCOMP, or
PSOLID.
TMIN TMIN flag indicating that minimum thickness value will follow.
Only valid when PTYPE = PSHELL.
MTYP Indicates that the mesh conforms to certain rules for which
the optimizer is tuned. Currently, only the ALIGN option is
available. ALIGN indicates that when manufacturing
constraints are active, the mesh is aligned with the draw
direction or extrusion path. See comment 4.
SINGLE indicates that a single die will be used, the die being
withdrawn in the given draw direction.
DAID/XDA, YDA, ZDA Draw direction anchor point. These fields define the anchor
point for draw direction of the casting. The point may be
defined by entering a grid ID in the DAID field or by entering
X, Y, and Z coordinates in the XDA, YDA, and ZDA fields,
these coordinates will be in the basic coordinate system.
DFID/XDF, YDF, ZDF Direction of vector for draw direction definition. These fields
define a point. The vector goes from the anchor point to
this point. The point may be defined by entering a grid ID in
the DFID field or by entering X, Y, and Z coordinates in the
XDF, YDF, and ZDF fields, these coordinates will be in the
basic coordinate system.
OBST OBST flag indicating that a list of PIDs will follow which are
non-designable, but their interaction with designable parts
needs to be considered with regard to the defined draw
direction. OBST stands for obstacle.
EPATH1 EPATH1 flag indicating that a list of grid IDs will follow to
define the primary extrusion path.
EPATH2 EPATH2 flag indicating that a list of grid IDs will follow to
define the secondary extrusion path. This is only required
when ETYP has been set to TWIST.
MASTER MASTER flag indicating that this design variable may be used
as a master pattern for pattern repetition. See comment 7.
CAID/XCA, YCA, ZCA Anchor point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CAID field
or by entering X, Y, and Z coordinates in the XCA, YCA, and
ZCA fields. These coordinates will be in the basic coordinate
system. See comment 7.
CFID/XCF, YCF, ZCF First point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CFID field
or by entering X, Y, and Z coordinates in the XCF, YCF, and
ZCF fields. These coordinates will be in the basic coordinate
system. See comment 7.
CSID/XCS, YCS, ZCS Second point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CSID field
CTID/XCT, YCT, ZCT Third point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CTID field
or by entering X, Y, and Z coordinates in the XCT, YCT, and
ZCT fields. These coordinates will be in the basic coordinate
system. See comment 7.
CAID/XCA, YCA, ZCA Anchor point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CAID field
or by entering X, Y, and Z coordinates in the XCA, YCA, and
ZCA fields. These coordinates will be in the basic coordinate
system. See comment 7.
CFID/XCF, YCF, ZCF First point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CFID field
or by entering X, Y, and Z coordinates in the XCF, YCF, and
CSID/XCS, YCS, ZCS Second point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CSID field
or by entering X, Y, and Z coordinates in the XCS, YCS, and
ZCS fields. These coordinates will be in the basic coordinate
system. See comment 7.
CTID/XCT, YCT, ZCT Third point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CTID field
or by entering X, Y, and Z coordinates in the XCT, YCT, and
ZCT fields. These coordinates will be in the basic coordinate
system. See comment 7.
PATRN PATRN flag indicating that pattern grouping is active for the
properties listed. Indicates that information for pattern
grouping is to follow.
AID/XA, YA, ZA Anchor point for pattern grouping. The point may be defined
by entering a grid ID in the AID field or by entering X, Y, and
Z coordinates in the XA, YA, and ZA fields. These
coordinates will be in the basic coordinate system. See
comment 10.
FID/XF, YF, ZF First point for pattern grouping. The point may be defined
by entering a grid ID in the FID field or by entering X, Y, and
Z coordinates in the XF, YF, and ZF fields. These
coordinates will be in the basic coordinate system. See
comment 10.
SID/XS, YS, ZS Second point for pattern grouping. The point may be
defined by entering a grid ID in the SID field or by entering
X, Y, and Z coordinates in the XS, YS, and ZS fields. These
coordinates will be in the basic coordinate system. See
comment 10.
Default = PLY
No default (Real)
LEVELSET LEVELSET flag indicating that the Level Set method (for
topology optimization) is activated and the definitions of the
required parameters follow.
HOLEINST Defines the method used to insert holes into the design.
NONE/ADAPT/ALIGN/TOPDER
DEFAULT = ADAPT
Comments
1. Von Mises stress constraints may be defined for topology and free-size optimization
through the STRESS optional continuation line on the DTPL or the DSIZE card. There are
a number of restrictions with this constraint:
The definition of stress constraints is limited to a single von Mises permissible stress.
The phenomenon of singular topology is pronounced when different materials with
If MINDIM is defined, but no other manufacturing constraint exists, MINDIM will not be
reset to the recommended lower bound value for PTYPE = PSHELL or PSOLID, if the
defined value is less than the recommended value. For PTYPE = PCOMP, MINDIM will be
reset in the absence of manufacturing constraints.
3. MAXDIM should at least be twice the value of MINDIM. If the input value of MAXDIM is
too small, OptiStruct automatically resets the value and an INFORMATION message is
printed.
MAXDIM implies the application of a MINGAP constraint of the same value as MAXDIM, as
well. Therefore, for MINGAP to be effective, it should be greater than MAXDIM.
It is important to pay attention to volume fraction as the achievable volume is below 50%
when MAXDIM is defined, and further decreases as MINGAP increases.
4. MTYP "ALIGN" may be used in conjunction with draw direction or extrusion manufacturing
constraints to indicate that a mesh is aligned with a draw direction or extrusion path.
Mesh 1 is "aligned" for draw direction 1 in the example shown, but not for draw direction
2.
MTYP "ALIGN" may also be used in conjunction with manufacturing constraints (minimum
member, maximum member, pattern grouping, and pattern repetition) other than draw
direction and extrusion, and Mesh 1 is considered "aligned" for those manufacturing
constraints, too.
In both cases, this will enable OptiStruct to use a smaller minimum member size and
smaller maximum member sizes. The default minimum member size is three times the
average element edge length; with an "aligned" mesh, the default size can be two times
the average element edge length.
5. The stamping constraint is available for only one sheet, which is defined by the
combination of STAMP and DTYP as SINGLE.
STAMP and NOHOLE can be a good combination as this helps to produce a continuous/
spread shell structure.
Note that attention should be paid to the compatibility between thickness and target
volume.
Four points are defined and these are utilized as follows to define the coordinate
system (this is the only way to define a left-handed system):
- A vector from the anchor point to the first point defines the x-axis.
- The second point lies on the x-y plane, indicating the positive sense of the y-axis.
- The third point indicates the positive sense of the z-axis.
A rectangular coordinate system and an anchor point are defined. If only an anchor
point is defined, it is assumed that the basic coordinate system is to be used.
Multiple "Slaves" may reference the same "Master."
Scale factors may be defined for "Slave" regions, allowing the "Master" layout to be
adjusted.
For a more detailed description, refer to the Pattern Repetition page contained within the
User's Guide section Manufacturability for Topology Optimization.
8. Pattern grouping is applicable for PCOMP, PSHELL, and PSOLID components only.
9. For historic reasons, the SYMM flag may be used in place of the PATRN flag.
This type of pattern grouping requires the anchor point and first point to be defined. A
vector from the anchor point to the first point is normal to the plane of symmetry.
This type of pattern grouping requires the anchor point, first point, and second point to
be defined. A vector from the anchor point to the first point is normal to the first plane
of symmetry. The second point is projected normally onto the first plane of symmetry. A
vector from the anchor point to this projected point is normal to the second plane of
symmetry.
This type of pattern grouping requires the anchor point, first point, and second point to
be defined. A vector from the anchor point to the first point is normal to the first plane
of symmetry. The second point is projected normally onto the first plane of symmetry. A
vector from the anchor point to this projected point is normal to the second plane of
symmetry. The third plane of symmetry is orthogonal to both the first and second planes
of symmetry, passing through the anchor point.
Uniform (TYP = 9)
This type of pattern grouping does not require any additional input.
This type of pattern grouping requires the anchor point, first point, and number of cyclical
repetitions to be defined. A vector from the anchor point to the first point defines the
axis of symmetry.
This type of pattern grouping requires the anchor point, first point, second point, and
number of cyclical repetitions to be defined. A vector from the anchor point to the first
point defines the axis of symmetry. The anchor point, first point, and second point all lay
on a plane of symmetry. A plane of symmetry lies at the center of each cyclical
repetition.
For a more detailed description, refer to the Pattern Grouping page contained within the
User's Guide section Manufacturability for Topology Optimization.
11. The level set method can merge existing holes but cannot nucleate new holes in the
design domain. Therefore, creating an initial design with holes is necessary, especially for
2D design problems (For 3D design problems, new holes can be “tunneled” when two
surfaces merged).
12. By default, OptiStruct will automatically create a Cheese-Like initial design with holes
adaptively distributed over the design domain, as shown in Figure 2. The default hole
radius is 4.0 times the average mesh size.
Figure 2: A C heese-Like Initial design generated with (left) the default setting, and (right) double hole
radius.
13. Changing the value of HOLERAD can result in different initial designs. Figure 2 (Right)
shows an initial design filled with holes possessing a doubled hole radius when compared
to Figure 2 (Left). If the you wish to create an initial design with evenly distributed and
well aligned holes (this may be preferable for regular design domains), HOLEINST can be
set to ALIGN. The number of holes in each direction can be further specified by using
NHOLESX, NHOLESY and NHOLESZ as shown in Figure 3.
14. Currently, level set supports both SINGLE and SPLIT draw direction constraints. When
multiple DTPL cards are involved, the draw directions need to be the same. The
information needed for draw direction constraint is read from the DTPL cards and thus no
extra settings are required.
Description
Linearly relates a design variable to an analysis model element property using the equation:
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Character)
EPNAME/FID Element property name, such as "K" or “ZOFFS" (as in the documentation
of the element bulk data entries), or field number on an element bulk
data entry.
Comments
DVCREL2 – Relates Design Variables to Analysis Model Element Properties via Relationship
Defined by User-supplied Equation
Description
Relates design variables to an analysis model element property using a relationship defined by
a DEQATN card. The equation inputs come from the referenced DESVAR values and constants
defined on a DTABLE card.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
LABL8 etc.
Field Contents
No default (Character)
EPNAME/FID Element property name, such as "K" or “ZOFFS" (as in the documentation
of the element bulk data entries), or field number on an element bulk
data entry.
LABL# Constant label. Must match with a constant label of a DTABLE entry.
No default (Character)
Comments
Types
Depending on the TYPE entry, the FID of the appropriate design parameter can be determined
from the table below.
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
FID 11-20 M33 M41 M42 M43 M44 M51 M52 M53
FID 21-30 M54 M55 M61 M62 M63 M64 M65 M66
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
CONM2 M X1 X2 X3
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
CMASS2 M
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
CMASS4 M
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
CDAMP2 B
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
CDAMP4 B
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
CBAR X1 X2 X3
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
CBEAM X1 X2 X3
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
CONROD A J C NSM
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
CELAS2 K GE S
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
CELAS4 K GE S
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
CTRIA3 ZOFFS
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
CTRIA6
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
CQUAD4 ZOFFS
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
CQUAD8
Description
Defines the relationship between a design variable and a grid point location.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
2. Multiple references to the same grid ID will yield a summation of perturbation vectors for
the given grid.
3. The DVGRID data defines perturbations in the locations of the grids. The updated
location of the grid is:
where, DVj is the value of design variable j and [N]T is the coordinate transformation
matrix based on the CID and the GRID location.
Description
Linearly relates a design variable to properties of an MBD entity using the equation:
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
5 1.
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
5 1.
Field Contents
No default (Character)
BID/EID Body ID or Element ID number. When TYPE is PRBODY, this field is the ID
number of a rigid body. When TYPE is CMBUSH(M), CMBEAM(M), or
CMSPDP(m), this field is the ID number of a corresponding element.
PNAME Property name, such as "A" or "L" (as in the documentation of the
PRBODY, CMBEAM(M), CMBUSH(M), and CMSPDP(M) cards).
1. Available TYPEs are PRBODY, CMBUSH, CMBUSHM, CMBEAM, CMBEAMM, CMSPDP, and
CMSPDPM.
PRBODY IXX
IYY
IZZ
IXY
IXZ
IYZ
J Torsional constant.
K4 ~ K6 Rotational stiffness.
B1 ~ B3 Translational damping.
B4 ~ B6 Rotational damping.
P1 ~ P3 Translational preload.
P4 ~ P6 Rotational preload.
CMSPDP/CMSPDPM K Stiffness
B Damping
PF Preload force.
DVMBREL2 – Relates Design Variables to Properties of MBD Entities via Relationship Defined
by User-supplied Equation
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
LABL8 etc.
Field Contents
No default (Character)
PNAME Property name, such as "A" or "L" (as in the documentation of the PRBODY,
CMBEAM(M), CMBUSH(M), and CMSPDP(M) cards).
No default (Character)
Comments
1. Available TYPE are PRBODY, CMBUSH, CMBUSHM, CMBEAM, CMBEAMM, CMSPDP, and
CMSPDPM.
PRBODY IXX
IYY
IZZ
IXY
IXZ
IYZ
J Torsional constant.
K4 ~ K6 Rotational stiffness.
B1 ~ B3 Translational damping.
B4 ~ B6 Rotational damping.
P1 ~ P3 Translational preload.
P4 ~ P6 Rotational preload.
CMSPDP/CMSPDPM K Stiffness
B Damping
PF Preload force
Description
Linearly relates a design variable to an analysis model material property using the equation:
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 1
To relate the Damping Coefficient value on a MAT1 card (field 9) to Design Variable 5.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
5 1.0
Example 2
This example is the same as example 1 (above), except that it defines MPNAME in place of
FID.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
5 1.0
Associated Cards
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
TYPE Material type to be related (MAT1, MAT2, MAT4, MAT5, MAT8, and
MAT9).
No default (Character)
MPNAME/FID Material property name, such as "E" or “RHO" (as in the documentation of
the material bulk data entries), or field number on a material bulk data
entry.
Comments
1. See the DVMREL - Types section for details on the supported material fields and the
MPNAME/FID entries.
Description
Relates design variables to an analysis model material property using a relationship defined by
a DEQATN card. The equation inputs come from the referenced DESVAR values and constants
defined on a DTABLE card.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
LABL8 etc.
Example 1
To relate the Damping Coefficient value on a MAT1 card (field 9) to some user-defined
relationship of design variables 5 and 6 and the table entry GE0.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DVMREL 17 MAT1 22 9 1
2
DESVAR 5 6
DTABLE GE0
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DVMREL 17 MAT1 22 GE 1
2
DESVAR 5 6
DTABLE GE0
Associated Cards
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
TYPE Material type to be related (MAT1, MAT2, MAT4, MAT5, MAT8, and
MAT9).
No default (Character)
MPNAME/FID Material property name, such as "E" or “RHO" (as in the documentation
of the material bulk data entries), or field number on a material bulk data
entry.
LABL# Constant label. Must match with a constant label of a DTABLE entry.
No default (Character)
Comments
1. See the DVMREL - Types section for details on the supported material fields and the
MPNAME/FID entries.
Types
Depending on the TYPE entry, the FID of the appropriate design parameter can be determined
from the table below.
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
FID 21- GE
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
FID 11-20 G23 G24 G25 G26 G33 G34 G35 G36
Description
Linearly relates a design variable to an analysis model property using the equation:
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
5 1.
Example 2
This example is the same as example 1 (above), except that it defines PNAME.
5 1.
Field Contents
No default (Character)
PNAME/FID Property name, such as "A" or "T" (as in the documentation of the
property cards), or field number in property card (see table below). For
the PSHELL property 12I/T3, only the filed number (6) is allowed. For
PBARL and PBEAML only property names are allowed, as different
sections use different fields.
Comments
2. When TYPE is PCOMPG, either global plies or property specific plies may be selected.
To select property specific plies, the format is similar to that used for other property
types where the property identification number of the PCOMPG is entered in the PID field
and then either PNAME or FID is used to identify the value to be related. In this scenario,
only the property with an ID given in the PID field is affected.
To select global plies, G# is entered in the PID field where, # is the GPLYID of a global
ply. In this instance, FID is not applicable so T or THETA is used in the PNAME field to
relate either the thickness or orientation respectively. In this scenario, all plies that use
the given GPLYID are affected.
When TYPE is PCOMPP, P# is entered in the PID field where # is the ID of a PLY entity.
In this instance, FID is not applicable so T or THETA is used in the PNAME field to relate
either the thickness or orientation respectively.
3. PBEAML definitions with more than one section definition may not be referenced by a
DVPREL1.
5. When TYPE is PBARL or PBEAML, users should pay close attention to the variable ranges
to avoid invalid dimensions. For example, the inner radius of a tube cross-section cannot
exceed the outer radius. It is necessary to prevent combinations of dimensions from
taking on values that are physically meaningless. Some constraints are applied
automatically on section dimensions. The table below summarizes these constraints.
Constraints are satisfied when they are < 0.0.
I DIM4 – DIM2
DIM4 – DIM3
DIM3 – DIM1
T DIM3 – DIM2
DIM4 – DIM1
DIM3 – DIM2
H DIM4 – DIM3
T1 DIM4 – DIM1
I1 DIM3 – DIM4
Z DIM3 – DIM4
2 • DIM1 – DIM4
T2 DIM4 – DIM1
DIM3 – DIM2
2 * DIM2 – DIM3
L DIM3 – DIM2
DIM4 – DIM1
2 * DIM4 – DIM2
DVPREL2 – Relates Design Variables to Analysis Model Properties via Relationship Defined by
User-supplied Equation
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
LABL8 etc.
Example 1
A rectangular bar of width W and depth D is defined using the PBAR card. The required
fields on the PBAR for Area, I1 and I2 are all related to the width and depth, which are the
design variables, by the referenced equations.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DESVAR 5 6
DESVAR 5 6
DESVAR 5 6
Example 2
This example is the same as example 1 (above), except that it defines PNAME.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DESVAR 5 6
DESVAR 5 6
DESVAR 5 6
Associated Cards
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Character)
PNAME/ Property name, such as "A" or "T" (as in the documentation of the property
FID cards), or field number in property card (see table below). For the PSHELL
property 12I/T3, only the filed number (6) is allowed. For PBARL and
PBEAML only property names are allowed, as different sections use different
fields.
No default (Character)
Comments
2. When Type is PBARL or PBEAML, users should pay close attention to the variable ranges
to avoid invalid dimensions.
3. PBEAML definitions with more than one section definition may not be referenced by a
DVPREL1.
5. When TYPE is PCOMPG, either global plies or property specific plies may be selected.
To select property specific plies, the format is similar to that used for other property
types where the property identification number of the PCOMPG is entered in the PID field
and then either PNAME or FID is used to identify the value to be related. In this scenario,
only the property with an ID given in the PID field is affected.
To select global plies, G# is entered in the PID field where # is the GPLYID of a global ply.
In this instance, FID is not applicable so T or THETA is used in the PNAME field to relate
either the thickness or orientation respectively. In this scenario, all plies that use the
given GPLYID are affected.
When TYPE is PCOMPP, P# is entered in the PID field where # is the ID of a PLY entity.
In this instance, FID is not applicable so T or THETA is used in the PNAME field to relate
either the thickness or orientation respectively.
Types
Depending on the TYPE entry, the FID of the appropriate design parameter can be determined
from the table below.
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
CONM2 M X1 X2 X3
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
PBAR A I1 I2 J NSM
FID 11-20 C1 C2 D1 D2 E1 E2 F1 F2
Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10
FID 11-20 C 1(A) C 2(A) D1(A) D2(A) E1(A) E2(A) F1(A) F2(A)
FID 21-30
Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6
PBUSH K1 K2 K3 K4 K5 K6
B1 B2 B3 B4 B5 B6
Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6
PCOMP Z0 NSM
… … … … …
Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6
PCOMPG Z0 NSM
… … …
Type Field numbers do not apply for PCOMPG when referencing global plies. See
comment 2 (DVPREL1).
PCOMPG T THETA
Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6
PCOMPP Z0 NSM
Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6
PDAMP B B B B
Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6
PELAS K S K S
Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6
PMASS M M M M
Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
PROD A NSM
Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6
Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6
PSHEAR T NSM F1 F2
Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6
PVISC CE CR CE CR
Description
Defines geometry and restraining force per unit length for an edge blank holder in a one-step
stamping simulation.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Real)
BSID Blank holder set identifier for retrieving the input file back to HyperForm.
Not used by the solver.
1. This entry is only valid with an @HyperForm statement in the first line of the input file.
Description
Defines location and restraining force per unit length for a draw bead in a one-step stamping
simulation.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Real)
DSID Draw bead set identifier for retrieving the input file back to HyperForm. Not
used by the solver.
1. This entry is only valid with an @HyperForm statement in the first line of the input file.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
EIC G 4 MAX 15
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
EIGC 4 MAX
15
Example 3
EIGC 4 MAX
1000.0 1000.0 15
Field Contents
Default = MAX
Comments
2. ALPHAAJ and OMEGAAJ are only useful for direct complex eigenvalue analysis. If there is
no METHOD command present in the subcase control area, the direct method is
considered for the complex eigenvalue analysis. Otherwise, modal method is used.
3. The 3rd field is reserved for a numerical complex eigensolution (METHOD). Currently, this
field should be left blank;however, certain method types (INV, HESS and CLAN) will be
accepted, but there will be no effect on the analysis.
Description
Defines the data required to perform real eigenvalue analysis with the Automated Multi-Level
Sub-structuring technique.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
V2 must be present.
Default = 0.0 for V1 (V1 < V2, Real, or blank for V1)
more accurate results and longer running times. See comments 6 and
9.
Comments
2. The eigenvectors are normalized with respect to the mass matrix by default.
3. The roots are found in order of increasing magnitude; those closest to zero are found
first. The number and type of roots to be found can be determined from the following
table.
5. In vibration analysis, small negative roots are usually computational zeros, indicating rigid
body modes. Finite negative roots are an indication of modeling problems. If V1 is set to
zero explicitly, V1 is ignored.
6. AMPFFACT is used to increase the accuracy of the eigenvalue and eigenvectors at the
expense of slightly longer run times. It is recommended to use higher values of
AMPFFACT, between [5.0, 15.0], for solid structures like engine blocks and suspension
components.
7. EIGRA data can be referenced by multiple normal modes subcases with different MPC set
SID’s in each subcase. However, only one can be used for modal frequency response or
modal transient analysis.
9. If AMPFFACT is not specified by you and the model contains a large number of solid
elements, then the value of AMPFFACT is automatically reset to 10.
Description
Defines data required to perform real eigenvalue analysis (vibration or buckling) with the
Lanczos Method.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
SHFSCL For vibration analysis: Estimate of the frequency of the first flexible
mode.
Default = MASS for normal modes analysis; Default = MAX for linear
buckling analysis (MASS or MAX)
Comments
1. In vibration analysis, the units of V1 and V2 are cycles per unit time. In buckling analysis,
V1 and V2 are eigenvalues. Each buckling eigenvalue is the factor by which the
prebuckling state of stress is multiplied to produce buckling in the shape defined by the
corresponding eigenvector.
2. In vibration analysis, eigenvectors are normalized with respect to the mass matrix by
default. In buckling analysis, eigenvectors are normalized to have unit value. NORM =
MASS is not a valid option for linear buckling analysis.
3. The roots are found in order of increasing magnitude: that is, those closest to zero are
found first. The number and type of roots to be found can be determined from the
following table. In vibration analysis, blank V1 defaults to -10.
4. The Lanczos eigensolver provides two different ways of solving the problem. If the
eigenvalue range is defined with no upper bound (V2 blank) and less than 50 modes (ND <
50), the faster method is applied.
5. Eigenvalues are sorted in the order of magnitude for output. An eigenvector is found for
each eigenvalue.
6. In vibration analysis, small negative roots are usually computational zeros, indicating rigid
body modes. Finite negative roots are an indication of modeling problems. If V1 is set to
zero explicitly, V1 is ignored. It is recommended that V1 not be set to zero when
extracting rigid body modes.
7. MSGLVL controls the amount of diagnostic output during the eigenvalue extraction. The
default value of zero suppresses all diagnostic output. A value of one prints eigenvalues
accepted at each shift. Higher values result in increasing levels of diagnostic output.
8. MAXSET is used to limit the maximum block size in the Lanczos solver. It may be reduced
if there is insufficient memory available. The default value is recommended.
ELEMQUAL – Resets the Default Bound Values for Element Quality Check
Description
Resets the default values of the warning and error bound limits for element quality check.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 1
For CTRIA3 elements, change the upper limit of aspect ratio for error message to 300.0
(default is 500).
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 2
For CTETRA elements, change the bound limits of collapse for warning message to 0.01 and
10.0 (default lower and upper limits are 0.001 and 100.0).
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ETYPE Element type. Allowable entries are: TRIA3 (CTRIA3), QUAD4 (CQUAD4),
TETRA (1st-order CTETRA), TET10 (2nd-order CTETRA), PENTA (1st-order
CPENTA), PENT15 (2nd-order CPENTA), HEXA (1st-order CHEXA), HEX20
(2nd-order CHEXA), PYRA (1st-order CPYRA), PYRA13 (2nd-order CPYRA),
TAXI3 (1st-order CTAXI or CTRIAX6), TAXI6 (2nd-order CTAXI or
CTRIAX6), GASK8 (CGASK8), GASK16 (CGASK16), GASK6 (CGASK6), and
GASK12 (CGASK12).
PTYPE Geometric property type. Allowable entries are: ARATIO (Aspect Ratio),
SKEW (Skew Angle), TAPER (Face Taper), WARP (Warp Angle), TWIST
(Twist Angle), EDGE (Edge Angle), COLLAPSE, ANGLE (Vertex Angle),
HOENOR (Hoe Normal Offset), HOETAN (Hoe Tangent Offset).
No default (Real)
No default (Real)
Comments
1. Element quality checks and their default settings are described in the Element Quality
Check section.
2. All specified values (V1 and V2) are checked against the corresponding limits used for
validity check. Data outside the validity range is ignored.
Description
Specifies damp shell elements for a fluid volume. ELIST entries are referenced by the MFLUID
entry.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
Comments
1. By default, for elements only damp on one side (see WSURF1 on MFLUID entry), the damp
side of an element is on the same side of the element’s normal. But a negative EIDi
indicates that the fluid is opposite to the normal. If there are negative EIDi’s specified in
a "THRU" range, then both EIDi’s in the range must be negative.
3. ELIST entries are internally converted to SET entries. The continuation is optional.
ENDMETADATA – Indicates the end of metadata that is to be passed to the metadata output
file.
Description
ENDMETADATA indicates the end of metadata that is to be passed to the metadata output file.
Metadata between the METADATA and ENDMETADATA commands is passed to the
<filename>_metadata.xml file.
Example
METADATA
This line will be passed to the filename_metadata.xml file.
So will this information: Color=blue
ENDMETADATA
Comments
1. There can be two sections of metadata; one in the Solution Control section and one in
the Bulk Data section.
2. Metadata can be used to pass information from the pre-processor seamlessly through the
solver to a post-processing program.
Description
The END bulk data entry indicates the end of data that is used to describe a specific entity
(or entities) for inclusion in a model. The END entry is used in conjunction with the BEGIN
entry to define the data required for a specific entity.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
TYPE Specifies the entity type that will be defined by the END data entry (see
comment 2).
(HYPRBEAM or FEMODEL)
NAME This field specifies the name of the entity that is defined by the END entry
(see comment 2).
(Character String)
1. The BEGIN and END bulk data entries can be used in conjunction to define a part within
the full model (for TYPE = FEMODEL).
2. TYPE = HYPRBEAM:
Data required for the definition of an arbitrary beam section will be specified between the
BEGIN and END data entries.
TYPE = FEMODEL:
In a model containing multiple parts, the parts are included within the full model specifying
part data between the BEGIN and END bulk data entries (the INCLUDE entry can also be
used for part data referencing). The name of the included part should be specified in the
NAME field.
3. The INCLUDE entry, similar to almost any other bulk data entry, is allowed between BEGIN
and END entries. However, BEGIN and END should exist in the same file.
4. Models are often defined in separate files, and the block (BEGIN – END) contains only
INCLUDE entries. It is possible to duplicate a single part by including the same file(s) in
different BEGIN-END blocks.
5. There can be multiple sections of arbitrary beam data; one for each beam section.
6. An example set of data for the definition of an arbitrary beam section is as follows:
BEGIN,HYPRBEAM,SQUARE
$
GRIDS,1,0.0,0.0
GRIDS,2,1.0,0.0
GRIDS,3,1.0,1.0
GRIDS,4,0.0,1.0
$
CSEC2,10,100,1,2
CSEC2,20,100,2,3
CSEC2,30,100,3,4
CSEC2,40,100,4,1
$
PSEC,100,1000,0.1
$
END,HYPRBEAM
Description
Defines one or more sets of elements as panels for equivalent radiated power output for a
frequency response analysis of a coupled fluid-structural model.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NAME5 SID5 …
Field Contents
ESLTADD – Combination of selected time steps for Geometric Nonlinear ESLM Optimization or a
Multi-body Dynamics ESLM Optimization
Description
Defines a combined time step selection set as a union of selected time steps defined via
ESLTIME entries for Geometric Nonlinear ESLM optimization or a Multi-body Dynamics ESLM
optimization.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ESLTADD SID S1 S2 S3 S4 S5 S6 S7
S8 S9 etc.
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ESLTADD 101 9 11 13
Field Contents
(Integer > 0)
Si Set identification numbers of time step selections defined via ESLTIME bulk
data entries.
(Integer > 0)
Comments
1. ESLTADD can be selected within the subcase information section using the command
ESLTIME=SID.
2. Si should be unique and may not be the identification number of a set defined by another
ESLTADD entry.
ESLTIME – Time Step selection control for Geometric Nonlinear Response ESLM Optimization
and Multi-body Dynamics ESLM Optimization
Description
Defines time step selection control for geometric nonlinear response ESL Optimization and
Multi-body dynamics ESLM optimization.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
...
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ESLTIME 100
11 -19.9 99.9
12 1
13
(Integer > 0)
(Integer > 0)
(Real, or blank)
(Real, or blank)
TYPE# Flag to select the time steps at which the highest or lowest
response values or peaks or troughs of the response, occur.
Comments
2. The SID and RID fields cannot be left blank. Other fields, if blank, will be ignored.
3. Lower bounds TLB and LB must be smaller than upper bounds TUB and UB respectively.
5. Using fields LB and UB, the user can define the range of a specific response. OptiStruct
will then select the time steps with response values in this range for ESL generation
(Figure 1).
6. If TYPE = 1, time steps which have the highest response values will be selected.
If TYPE = -1, time steps which have the lowest response values will be selected.
If TYPE = -2, time steps at which response troughs occur will be selected.
9. All continuation lines on the ESLTIME entry are ignored in Multi-body dynamics ESLM
optimization. Only the first line (ESLTIME, SID, TLB, TUB) is considered.
Description
Defines elements, and associated fatigue properties, for consideration in a fatigue analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
FATDEF ID TOPSTR
Optional continuation lines for selecting elements, and associated fatigue properties, using
element sets (ELSET)
ELSID4 PFATID4 … … … …
… …
Optional continuation lines for selecting elements and associated fatigue properties through
referenced properties (PSHELL)
PID4 PFATID4 … … … …
… …
Optional continuation lines for selecting elements and associated fatigue properties through
referenced properties (PSOLID)
PID4 PFATID4 … … … …
… …
XELSID8 … … … … … …
… …
XEID8 … … … … … …
… …
Field Contents
ID Each FATDEF card must have a unique ID. FATDEF Subcase Information entry
may reference this ID.
TOPSTR Top stress fraction. Elements with combined stress not in this top fraction of
each MATFAT group will be screened out and have no results. This field is
ignored in fatigue analysis on a transient subcase.
Default = blank (100% will be used internally), (0.0 < Real < 1.0)
ELSET ELSET flag indicating that a list of pairs of ELSET and PFAT IDs will follow,
defining elements, and their associated fatigue properties, for consideration in
fatigue analyses where this FATDEF is selected.
ELSID# Element Set ID. Elements in this set will be considered in fatigue analyses
where this FATDEF is selected.
PFATID# Fatigue property ID. This is identification number of a PFAT entry, which
indicates the fatigue property used by the preceding elements defined by
ELSID# or PID#.
PSHELL PSHELL flag indicating that a list of pairs of PSHELL property IDs and PFAT
IDs will follow; defining elements and their associated fatigue properties for
consideration in fatigue analyses where this FATDEF is selected.
PSOLID PSOLID flag indicating that a list of pairs of PSOLID property IDs and PFAT
IDs will follow; defining elements and their associated fatigue properties for
consideration in fatigue analyses where this FATDEF is selected.
XELSET XELSET flag indicating that IDs of elements sets excluded from fatigue
analysis follow.
XELSID# Element set ID. Elements in these sets will be excluded from fatigue analyses
where this FATDEF is selected.
XELEM XELEM flag indicating that IDs of elements excluded from fatigue analysis
follow.
XEID# Element ID. These elements will be excluded from fatigue analyses where this
FATDEF is selected.
Comments
1. At least one of the optional continuation lines ELSET or PROP must be present.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
ID Each FATEVNT card must have a unique ID. This identifier may be referenced
by a FATSEQ definition.
Comments
1. FATLOAD entries referenced on this bulk data entry may reference different subcases.
3. These FATLOAD entries should reference the subcase types. For example, either static
subcases or transient subcases can be referenced, but not both. Referencing a
combination of subcase types via FATLOAD entries on the same FATEVNT entry is not
allowed.
4. If a specified FATLOAD entry references a transient subcase, only one FATLOAD entry is
allowed.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
ID Each FATLOAD card must have a unique ID. This identifier may be
referenced by a FATEVNT definition.
LDM The magnitude of the FEA load in the same units as those for the time
history. It is ignored in fatigue analyses based on a transient analysis
subcase (see comment 2).
Scale Scale factor applied to the load or time history. It is ignored in fatigue
analyses based on a transient analysis subcase.
Offset Offset applied to the load or time history. It is ignored in fatigue analyses
based on a transient analysis subcase.
Comments
1. This magnitude is used as a scale factor to normalize the finite element stresses/strains
to obtain the stress/strain distribution due to a unit loading.
2. The sequence below depicts how LDM, Scale and Offset values work together to scale
the FEA stress tensor at time t:
ij . FEA
ij (t ) ( P (t ) Scale Offset )
LDM
Description
This bulk data entry can be used to define parameters required for a Fatigue Analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
FATPARM ID Type
FOS FOSType
Field Contents
ID Each FATPARM card must have a unique ID. The FATPARM Subcase Information
entry may reference this identifier.
Default = SN
(SN = Stress Life, EN = Strain Life, FOS = Factor of Safety Analysis - see
comment 9)
STRESS STRESS flag indicating that parameters are to follow which define how the
stress is used in fatigue calculation. This flag and following parameters will be
used only when the "Type" field is set to SN or EN.
For Stress Life, combined stress value is used; For Strain Life, combined strain
value is used.
For Strain Life, shear strain components are engineering shear strain (two times
tensor shear strain).
StressUnit FE analysis Stress Tensor Unit. The Unit is necessary because the S-N/E-N
curve (MATFAT card) might be defined in different unit, and FEA stress needs
to be converted before looking up the fatigue life for a given stress level on the
S-N curve. See comment 10.
RAINFLOW The RAINFLOW flag indicates that parameters required for Rainflow counting are
to follow. This flag and its related parameters will be used only when the “Type”
field is set to SN or EN.
Default = LOAD
GateRel Relative fraction of maximum gate range. The reference value is the maximum
range multiplied by GateRel, and used for gating out small disturbances or
"noise" in the time series.
CERTNTY The CERTNTY flag indicates that parameters that define certainties in fatigue
analysis are to follow. This flag and the following parameter will be used only
when the “Type” field is set to SN or EN.
SurvCert Certainty of survival based on the scatter of the S-N curve. See comment 4.
FOS The FOS flag indicates that the following parameters are for Factor of Safety
analysis (Type = FOS). This flag and following parameter will be used only when
the “Type” field is set to FOS.
FOSType This field can be used to select the Factor of safety analysis type.
Default = DANGVAN
Comments
1. RType = Load is valid when there is only one static load case defined in an event. If the
event contains multiple static load cases, then RType will automatically be set to STRESS
because there will be stress super-positioning among different load cases; doing rainflow
counting on load-time history could not deal with it.
2. When RType = Load, load-time history will be cycle counted using the rainflow cycle
counting method. The cycle counting results (load Ranges and Means) will be scaled by
combined FEA stress. Doing rainflow counting on load-time is much faster than doing it
on stress-time (RType=Stress), especially when the load-time history is complex and
contains a large number of time points, but it is less accurate.
3. When RType = Stress, stress-time history will be cycle counted using the rainflow cycle
counting method. The stress-time history has the same length as load-time, while each
point of the stress time is the combined stress value where the stress tensor is FEA
stress scaled by y point value of the corresponding load-time history.
5. When fatigue optimization is performed, EN method with SWT mean stress correction is
changed to EN method with Morrow mean stress correction automatically.
6. Correction=GERBER2 improves the GERBER method by ignoring the effect of negative mean
stress.
Se = Sa / (1 - Sm / Sy )
9. The “STRESS”, “RAINFLOW” and “CERTNTY” continuation lines are ignored in a factor of
safety analysis (Type=FOS).
10. If UNITS=# or DTI UNITS is present, the default value of StressUnit should be determined
by UNITS=# or DTI UNITS. If UNITS=# and DTI UNITS are absent, the default value of
StressUnit is MPA. If UNITS=# or DTI UNITS is present, and StressUnit is also specified,
but they are not consistent, an error will be issued.
Description
This bulk data entry can be used to define a loading sequence for a Fatigue Analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
FATSEQ ID
FID5 N5
Field Contents
ID Each FATSEQ card must have a unique ID. FATSEQ Subcase Information entry
may reference this identifier. Alternatively this ID may be referenced by other
FATSEQ definitions.
N# Number of times this loading sequence or event is repeated (see Comment 4).
Comments
1. Identification numbers of FATSEQ and FATEVNT entries share the same ID pool.
2. Repeat number (N#) has no effect on the results of a Factor of Safety (FOS) analysis.
3. A fatigue subcase should reference the same subcase types through FATSEQ and
FATEVNT entries (for example, either static subcases or transient subcases can be
referenced, but not both). Referencing a combination of subcase types is not allowed.
Description
Defines a forming limit curve as a table of minor and major strain values in a one-step
stamping simulation.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
FLDATA 2 … …
Field Contents
1. This entry is only valid with an @HyperForm statement in the first line of the input file.
Description
Defines a static force at a grid point by specifying a vector. It can also be used to define the
EXCITEID field (Amplitude “A”) of dynamic loads in RLOAD1, RLOAD2, TLOAD1 and TLOAD2 bulk
data entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
FORC E SID G C ID F N1 N2 N3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
F Scale factor.
(Real)
Comments
3. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on FORCE entries in the model. A fully qualified reference
(“PartName.number”) is similar to the format of a numeric reference. “PartName” is the
name of the part that contains the referenced local entry (part names are defined on the
BEGIN Bulk Data Entry in the model). “number” is the identification number of a
referenced local entry in the part “PartName”. See Parts and Instances in the User’s
Guide for detailed information on the use of fully qualified references.
Description
Used to define a static force by specification of a value and two grid points that determine
the direction. It can also be used to define the EXCITEID field (Amplitude “A”) of dynamic
loads in RLOAD1, RLOAD2, TLOAD1 and TLOAD2 bulk data entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
FORC E1 SID G F G1 G2
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
FORC E1 6 13 -2.93 16 13
Field Contents
(Integer > 0)
(Integer > 0)
F Value of force.
(Real)
Description
Used to define a static force by specification of a value and four grid points that determine
the direction. It can also be used to define the EXCITEID field (Amplitude “A”) of dynamic
loads in RLOAD1, RLOAD2, TLOAD1 and TLOAD2 bulk data entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
FORC E2 SID G F G1 G2 G3 G4
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
FORC E2 6 13 -2.93 16 13 18 19
Field Contents
(Integer > 0)
(Integer > 0)
F Value of force.
(Real)
where, is a unit vector parallel to a vector calculated by the cross product of vectors
from G1 to G2 and G3 to G4.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
FREQ SID F1 F2 F3 F4 F5 F6 F7
F8 … … … … … … …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
F# Frequency value.
Comments
1. FREQ entries must be selected with the I/O Options or Subcase Information command
FREQUENCY = SID.
where, DFREQ is a user parameter with a default of 10 -5 * fMAX , and fMIN are the maximum
and minimum excitation frequencies of the combined FREQi entries.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
DF Frequency increment.
1. FREQ1 entries must be selected with the I/O Options or Subcase Information command
FREQUENCY = SID.
4. All FREQi entries with the same set identification numbers will be used. Duplicate
frequencies will be ignored. and are considered duplicated if:
where, DFREQ is a user parameter with a default of 10 -5 * fMAX , and are the maximum
and minimum excitation frequencies of the combined FREQi entries.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
FREQ2 SID F1 F2 NF
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
1. FREQ2 entries must be selected with the I/O Options or Subcase Information command
FREQUENCY = SID.
4. All FREQi entries with the same set identification numbers will be used. Duplicate
frequencies will be ignored. and are considered duplicated if:
where, DFREQ is a user parameter with a default of 10 -5 * fMAX , and are the maximum
and minimum excitation frequencies of the combined FREQi entries.
Description
Defines a set of frequencies for the modal method of frequency response analysis by
specifying the number of frequencies between modal frequencies.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
Define a set of frequencies such that there will be 10 frequencies between each mode,
within the frequency range 20 to 200, plus 10 frequencies between 20 and the lowest
mode in the range, plus 10 frequencies between the highest mode in the range and 200.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Real > 0.0 for TYPE = LINEAR ; Real > 0.0 for TYPE = LOG)
NEF Number of excitation frequencies within each sub range including the end
points. The first sub range is between F1 and the first modal frequency
within the bounds. Intermediate sub ranges exist between each mode
calculated within the bounds. The last sub range is between the last
modal frequency within the bounds and F2.
CLUSTER Specifies cluster of the excitation frequency near the end points of the
range. See comment 5.
Comments
2. FREQ3 entries must be selected in the Subcase Information section with FREQUENCY =
SID.
3. Since the forcing frequencies are near structural resonances, it is important that some
amount of damping be specified.
4. All FREQi entries with the same set identification numbers will be used. Duplicate
frequencies will be ignored. and are considered duplicated if:
where, DFREQ is a user parameter, with a default of 10 -5 * fMAX and are the maximum
and minimum excitation frequencies of the combined FREQi entries.
5. CLUSTER is used to obtain better resolution near the modal frequencies where the
response variation is highest, in accordance with:
= frequency at the lower limit of the sub range. (If TYPE is LOG, then this is
the logarithm of the frequency.)
= frequency at the upper limit of the sub range. (If TYPE is LOG, then this is
the logarithm of the frequency.)
= the k-th excitation frequency. (If TYPE is LOG, then this is the logarithm of
the frequency.)
CLUSTER > 1.0 provides closer spacing of excitation frequency towards the ends of the
frequency range, while values of less than 1.0 provide closer spacing towards the center
of the frequency range.
For example, if the frequency range is between 10 and 20, NEF = 11, TYPE = "LINEAR";
then, the excitation frequencies for various values of CLUSTER would be as shown in the
table below.
CLUSTER
Excitation
Frequency 0.25 0.50 1.0 2.0 4.0
Number
Excitation Frequencies in Hertz
6. In design optimization, the excitation frequencies are derived from the modal frequencies
computed at each design iteration.
7. In modal analysis, solutions for modal degrees-of-freedom from rigid body modes at zero
excitation frequencies may be discarded. Solutions for non-zero modes are retained.
Description
Defines a set of frequencies for the modal method of frequency response analysis by
specifying the amount of "spread" around each modal frequency and the number of equally
spaced frequencies within the spread.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
Define a set of frequencies such that there will be 21 equally spaced frequencies across a
frequency band of to for each modal frequency that occurs between 20
and 200.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
FSPD Frequency spread, +/- the fractional amount specified for each mode
which occurs in the frequency range F1 to F2.
Comments
2. FREQ4 entries must be selected in the Subcase Information section with FREQUENCY =
SID.
4. Excitation frequencies may be based on modal frequencies that are not within the range
(F1 and F2) as long as the calculated excitation frequencies are within the range.
Similarly, an excitation frequency calculated based on natural frequencies within the
range (F1 through F2) may be excluded if it falls outside the range.
5. The frequency spread can be used also to define the half-power bandwidth. The half-
power bandwidth is given by , where, is the damping ratio. Therefore, if FSPD
is specified equal to the damping ratio for the mode, NFM specifies the number of
excitation frequencies within the half-power bandwidth.
7. All FREQi entries with the same set identification numbers will be used. Duplicate
frequencies will be ignored. and are considered duplicated if:
where, DFREQ is a user parameter, with a default of 10-5. The values and are
the maximum and minimum excitation frequencies of the combined FREQi entries.
8. In design optimization, the excitation frequencies are derived from the modal frequencies
computed at each design iteration.
9. In modal analysis, solutions for modal degrees-of-freedom from rigid body modes at zero
excitation frequencies may be discarded. Solutions for non-zero modes are retained.
Description
Defines a set of frequencies for the modal method of frequency response analysis by
specification of a frequency range and fractions of the natural frequencies within that range.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
Define a set of frequencies such that the list of frequencies will be 0.6, 0.8, 0.9, 0.95, 1.0,
1.05, 1.1, and 1.2 times each modal frequency between 20 and 200.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
Comments
2. FREQ5 entries must be selected in the Subcase Information section with FREQUENCY =
SID.
If this computation results in excitation frequencies less than F1 and greater than F2,
those computed excitation frequencies are ignored.
4. Excitation frequencies may be based on natural frequencies that are not within the range
(F1 and F2) as long as the calculated excitation frequencies are within the range.
5. Since the forcing frequencies are near structural resonances, it is important that some
amount of damping be specified.
6. All FREQi entries with the same set identification numbers will be used. Duplicate
frequencies will be ignored. and are considered duplicated if:
where, DFREQ is a user parameter, with a default of 10-5. The values and are
the maximum and minimum excitation frequencies of the combined FREQi entries.
7. In design optimization, the excitation frequencies are derived from the modal frequencies
computed at each design iteration.
8. In modal analysis, solutions for modal degrees-of-freedom from rigid body modes at zero
excitation frequencies may be discarded. Solutions for non-zero modes are retained.
Description
Defines parameters that control connectivity and configuration checks for gap elements (CGAP
and CGAPG). Most of these parameters also affect contact elements that are automatically
created on CONTACT interfaces – see individual descriptions for details.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
While textual values are recommended for clarity, their integer equivalents will also be read.
The available parameters and their values are listed below (click the parameter name for
parameter descriptions).
Parameter Value
GAPOFFS YES, NO
Default = YES
GPCOINC <Real>
Defaults
For GAP elements: 1.0e-04
For CONTACT elements: Calculated
automatically based on element size on the
master face.
Comments
1. The GAPPRM entry changes the default settings of control parameters for the gap
elements connectivity and checks for configuration errors. None of the parameters of this
entry are required.
2. The gap alignment check controlled by the default value of CKGPDIR = ERR applies
correctly to the most typical situations wherein there is an initial opening between bodies
A and B, and the gap element is used to enforce non-penetration condition. For cases of
overlapping meshes (combined with a prescribed coordinate system), the REV value is
appropriate – it allows both aligned and reversed gap directions (respective to the gap
axis defined by the prescribed system).
CHKRN NO, 0, YES, or 1 Stop the run after the gap element checks are
completed.
Default = NO
If NO or 0, OptiStruct will run to completion unless
other errors are present.
Note:
GAPGPRJ NORM, 1, SHORT, or 2 For CGAPG and contact elements, controls how
the projection onto the obstacle element (or
Default = SHORT node patch) is performed.
GAPOFFS YES, NO, AUTO If YES, frictional offset for gap and contact analysis is
active.
Default = AUTO
If NO, frictional offset for gap and contact analysis in
inactive.
GPCOINC <Real> This parameter defines the distance below which the end
points of gap/contact elements (for example, the GA, GB
See the Note fields of the CGAP bulk data entry) are considered
for defaults coincident (as they may be too close to define the gap
direction accurately).
Note:
HMGAPST NO, 0, YES, or 1 Create HyperMesh command file that defines sets
containing open and closed gaps for the initial set up and
Default = NO for each nonlinear subcase. The file name is
<my_job>.hm.gapstat.cmf.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
-.39-6 .1-9
Example 3
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
GENEL 435 11 1 23 4 72 0
17 2
8.9
K .1 .2 .3 .4 .5 .6 .7
.8
UD 12 2 47 0
Field Contents
GIi/CIi Grid (or scalar point) and component identification numbers ordered
according to stiffness or flexibility values specified after KZmn. For scalar
points, CIi is zero.
UD Flag indicating that the subsequent fields and continuation entries contain
values for GDj/CDj until “K”, “Z”, or “S” is specified in field 2 or it is the
end of the entry.
No default (Character)
GDj/CDj Grid (or scalar point) and component identification numbers ordered
according to the columns in the “S” matrix.
K or Z Flag indicating that the next fields and continuation entries contain
stiffness values until “UD” or “S” is specified in field 2 or it is the end of
the entry.
No default (Character)
the row number and “n” is the column number. Only the lower triangular
terms in the matrix need to be specified. Zero values must be specified
as blank or 0.0.
S Flag indicating that the subsequent fields and continuation entries contain
values for the S matrix.
No default (Character)
Sij “S” matrix values where “i” corresponds to GIi/CIi list and “j” corresponds
to GDj/CDj list until “K”, “Z”, or “UD” is specified in field 2 or it is the end
of the entry. All the terms in the matrix must be specified and zero
values must be specified as blank or 0.0.
Comments
1. GIi/CIi and KZmn are required inputs. Either “K” or “Z” must be specified, but not both.
2. “UD”, “K”, “Z”, and “S”, may be specified in any order as demonstrated in the third
example.
3. “UD” and “S” are optional inputs. “S” defines the motion between the GIi/CIi and GDj/CDj
degrees-of-freedom according to:
But if “S” is specified then GDj/CDj must also be specified. If “S” is not specified then
GDj/CDj may contain six and only six degrees of freedom and they cannot refer to
SPOINTs.
4. If only “K” or “Z” is input without “UD” then it is recommended that the resulting stiffness
represents the unsupported element, containing all of the rigid body modes. If not, then
the “UD” option allows for the reintroduction of the rigid body modes with “S” which is
provided by you or computed internally.
a) If “K” and “UD” are specified then the program will form the complete stiffness as
defined by the following equation:
Where the K matrix is formed from the KZmn values and the S matrix is formed from the
Sij values or computed automatically.
Where the Z matrix is formed from the KZmn values and the S matrix is formed from the
Sij values or computed automatically. Z must be nonsingular.
5. PARAM,CK3 may be used to scale the stiffness produced by all GENEL elements.
6. All lower triangular values in K and Z and all values in S have to be accounted for in the
input. Zero values may be specified as 0.0 or be left blank, however if all entries in any
continuation line are zero, then at least one visible character must appear on this line (it
can be 0.0 in any field or the plus sign (+) in the first column) because blank lines are
treated as comment. Unused fields (after the last matrix entry) must be blank.
Description
Defines the gravity vectors for use in determining gravity loading for the structural model. It
can also be used to define the EXCITEID field (Amplitude “A”) of dynamic loads in RLOAD1,
RLOAD2, TLOAD1 and TLOAD2 bulk data entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
GRAV SID C ID G N1 N2 N3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
1. The gravity vector is defined by g = G(N1, N2, N3). The direction of G is the direction of
free fall. N1, N2, and N3 are in coordinate system CID.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
GRDSET 16 32 3456
Field Contents
1. The contents of fields 3, 7, or 8 of this entry are assumed for the corresponding fields of
any GRID entry whose field 3, 7, and 8 are blank. If any of these fields on the GRID entry
are blank, the default option defined by this entry occurs for that field. If no permanent
single-point constraints are desired or one of the coordinate systems is basic, the default
may be overridden on the GRID entry by entering zero in the corresponding field. Only
one GRDSET entry may appear in the bulk data section.
2. The primary purpose of this entry is to minimize the burden of preparing data for problems
with a large amount of repetition (for example, two-dimensional pinned-joint problems).
Description
Defines the location of a geometric grid point of the structural model, the directions of its
displacement, and its permanent single-point constraints.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
GRID ID CP X1 X2 X3 CD PS
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Real)
See the GRDSET entry for default options for fields 3, 7, and 8.
Comments
1. All grid point identification numbers must be unique with respect to all other structural grid
and scalar points. A duplicate identification number is only allowed if all fields on the
duplicated entries are exactly the same, unless PARAM,DUPTOL is used. PARAM,DUPTOL
can be used to set a tolerance that will allow a GRID with same ID, CP, CD, and PS to
have slightly different coordinates. Refer to Guidelines for Bulk Data Entries.
2. The meaning of X1, X2, and X3 depends on the type of coordinate system, CP, as
follows: (see CORDI entry descriptions).
Type X1 X2 X3
Rectangular X Y Z
Cylindrical R q(degrees) Z
3. The collection of all CD coordinate systems defined on all GRID entries is called the Global
Coordinate System. All degrees-of-freedom, constraints, and solution vectors are
expressed in the Global Coordinate System.
4. If CD = -1, then this defines a fluid grid point in the coupled fluid-structural analysis. This
type of point may only connect the CHEXA, CPENTA, and CTETRA elements to defined
fluid elements.
5. If CP, PS, or CD is blank, information from the GRDSET data will be used. If CP or CD
contains a zero, the basic coordinate system will be used. If PS contains a zero, single
point constraints on the GRDSET data are ignored.
6. Input data replication is available for the GRID data. This can be used to generate
additional GRID data, based on incrementing the GRID ID and coordinate locations.
Description
Defines a grid point on the y-z plane, using cartesian coordinates, for use in the definition of
arbitrary beam cross-sections.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
GRIDS ID Y Z
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
ID Identification number.
No default (Real)
No default (Real)
Comments
1. All grid point identification numbers within a section definition must be unique with respect
to all other grid point identification numbers within the same section definition.
2. This entry is only valid when it appears between the BEGIN and END statements.
Description
Defines a ground body out of a list of finite element properties, elements, and grid points.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ID8 …
TYPE# …
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
GROUND 3 SUPPORTING_BEAM
PSHELL 23 21
PBEAM 9 59 48
C ONM2 2345
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PBAR 10 11 13 15 22 99 88
44
Field Contents
BODY_NAME Unique body name. The body name for this PRBODY.
TYPE# Flag indicating that the following list of IDs refer to entities of this
type. All property definitions; CELAS2, CONM2, PLTOEL, RBE2, RBE3,
RBAR, RROD, and GRID are valid types for this field.
Comments
1. Any number of property definitions; CELAS2, CONM2, PLOTEL, RBAR, RBE2, RBE3, or RROD
elements or grid points can be given.
3. A property definition, CELAS2, CONM2, PLOTEL, RBE2, REB3, RBAR, or RROD element or
grid point can only belong to one ground or rigid or flexible body.
Description
This bulk data entry defines the application of modal damping to the residual structure in a
direct or transient frequency response analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
SID Unique hybrid damping SID (Referred to by the HYBDAMP I/O section
data).
KDAMP If KDAMP is set to -1/YES, modal damping is entered into the complex
stiffness matrix as material damping, instead of viscous damping. The
default is 1/NO to enter the damping as viscous damping.
Default = 1 (Integer)
Comments
1. HYBDAMP SID can be set by the HYBDAMP I/O Options Entry in the I/O section of the input
data.
Where,
g( ) are equal to twice the critical damping ratios calculated from the TABDMP1 entry
This bulk data card is identical to the I/O options entry, INCLUDE.
Description
The INSTNCE bulk data entry can be used to define the location of a part in the global
structure. Each INSTNCE entry should reference a unique part name.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
INSTNC E ID name NN
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
INSTNC E 2 C rankShaft 32
Field Contents
(Integer > 0)
name This field specifies the unique name of a part that is to be attached to the
global part (see comment 2). It should match the name of one of the parts
defined using the BEGIN, FEMODEL, name entry.
(Character String)
NN ID of a RELOC bulk data entry. This field defines the actual location of the part
in the final model via the RELOC entry.
1. The full model consists of several parts, one part is designated as global and the rest of
the parts are attached to the global part using INSTNCE entries. The global part can have
an arbitrary name (it is identified by the presence of INSTNCE entries). A minimum of one
INSTNCE entry should always be present in the model.
2. All INSTNCE entries should exist within a global part and no INSTNCE entry can reference
the name of a global part on the “name” field.
3. Each INSTNCE entry should reference a different part name. However, not every part has
to be defined using an INSTNCE entry. Such parts are still contained within the full model
without any relocation.
4. A global part can be moved to a different location, however, this is not recommended as
it may lead to inaccuracies in locating other parts.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
VX VY VZ WX WY WZ
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
INVELB 1 3
1000.0
Field Contents
(Integer > 0)
(Integer > 0)
(Integer > 0)
(Blank or Real)
(Blank or Real)
Comments
1. Only one initial velocity per body can be defined in a load set.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
No default
VT Translational velocity
VR Rotational velocity
Comments
1. Only one initial velocity per joint can be defined in a load set.
Description
Defines a joint.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
X4, G4 Y4 Z4
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
399
Field Contents
(Integer > 0)
(BALL, FIX, REV, TRANS, CYL, UNIV, CV, PLANAR, INLINE, PERP, PARA,
INPLANE, or ORIENT).
G1, G2 Geometric grid point identification number. Used to identify the bodies
to be connected and, for many JTYPEs, the location of the joint.
(Integer > 0)
(Real)
(Integer > 0)
(Real)
(Integer > 0)
Comments
2. G1 and G2 identify the bodies being joined and must, therefore, belong to different bodies.
Perpendicular Two perpendicular PERP G1,G2 and · The first selected axis is
axes are selected either X3, defined by the vector
that are always to Y3, Z3 or X3, Y3, Z3 or
remain G3 and alternatively the vector
perpendicular. either X4, from G1 to G3.
Therefore, Y4, Z4 or · The second selected axis
rotations about G4 is defined by the vector
both selected X4, Y4, Z4 or
axes and all alternatively the vector
translations are from G2 to G4.
free. Rotation · The selected vectors
about the cross- must be perpendicular to
product of the one another.
two selected
vectors is fixed.
Parallel Axes Two parallel axes PARA G1,G2 · The first selected axis is
are selected that and either defined by the vector X3,
are always to X3, Y3, Y3, Z3 or alternatively
the vector from G1 to
Description
Defines a joint using two grids which have a marker card associated with them.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(BALL, FIX, REV, TRANS, CYL, UNIV, CV, PLANAR, INLINE, PERP, PARA,
INPLANE, or ORIENT)
(Integer > 0)
Comments
2. M1 and M2 must belong to different bodies and must have a marker card associated with
them.
Description
Definition of a line.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
GA1 GB1
GA2 GB2
GA3 GB3
... ...
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
33 34
34 35
35 36
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
EID9 -etc-
In this format, a line is defined by a SET of elements. With this approach, the line is composed
of all the edges of all selected 1-D, 2-D or 3-D elements in the SET.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
Comments
1. LINEID is not unique, multiple LINE cards with the same LINEID compose a line group.
Description
Defines a static load as a linear combination of load sets defined via FORCE, MOMENT,
FORCE1, MOMENT1, PLOAD, PLOAD1, PLOAD2, PLOAD4, RFORCE, DAREA and GRAV entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
LOAD SID S S1 L1 S2 L2 S3 L3
S4 L4 -etc-
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
S Scale factor.
(Real)
Si Scale factors.
(Real)
Li Load set identification numbers defined via entry typed enumerated above.
(Integer > 0)
4. Load sets must be selected in the Subcase Information section (LOAD=SID) if they are to
be applied to the structural model.
5. A LOAD entry may not reference a set identification number defined by another LOAD
entry.
Description
Defines a static load as a linear combination of load sets defined via FORCE, MOMENT,
FORCE1, MOMENT1, PLOAD, PLOAD1, PLOAD2, PLOAD4, RFORCE, DAREA, and GRAV entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
LOADADD SID S S1 L1 S2 L2 S3 L3
S4 L4 -etc-
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Real)
(Real)
Li Load set identification numbers defined via entry typed enumerated above
(Integer > 0)
Comments
Where,
r
P is the static load as a linear combination of the defined load sets.
Si
are the scale factors defined in the S1, S2,…, Sn fields.
r
PLi
are the loads, whose id’s, are referenced by the L1, L2,…, Ln fields.
4. Load sets must be selected in the Subcase Information section (LOAD=SID) if they are to
be applied to the structural model.
5. A LOADADD entry may not reference a set identification number defined by another
LOADADD entry.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
1. Each marker has a unique ID. The marker gets its location from the grid corresponding to
the GID and the orientation from the coordinate system (CID).
2. Multiple markers can be located at the same grid with the same or with a different CID.
Description
Defines the material properties for linear, temperature-independent, and isotropic materials.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ST SC SS
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
E Young’s Modulus.
G Shear Modulus.
NU Poisson’s Ratio.
No default (Real)
No default (Real)
No default (Real)
ST, SC, SS Stress limits in tension, compression and shear. Used for composite ply
failure calculations
No default (Real)
Comments
1. The material identification number must be unique for all MAT1, MAT2, MAT8 and MAT9
entries.
2. The mass density, RHO, is used to automatically compute mass for all structural elements.
5. If E and NU are both blank, they are both given the value 0.0.
6. If G and NU are both blank, they are both given the value 0.0.
7. Implausible data on one or more MAT1 entries result in a warning message. Implausible
data is defined as:
E < 0.0 or
G < 0.0 or
NU > 0.5 or
NU < -1.0 or
8. It is strongly recommended that only two of the three values E, G, and NU be input.
11. To obtain the damping coefficient GE, multiply the critical damping ratio, C/C0 by 2.0.
12. TREF and GE are ignored if a MAT1 entry is referenced by a PCOMP entry.
Element Type E NU G
Membrane Membrane
CQUAD and CTRIA Transverse Shear
and Bending and Bending
CHEX, CTETRA,
CPENTA, CPRYRA and Deformation N/A
CSEAM
Description
Defines the material properties for linear, temperature-independent, anisotropic materials for
two-dimensional elements.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
A1 A2 A12 TREF GE ST SC SS
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Real)
No default (Real)
No default (Real)
TREF Reference temperature for the calculation of thermal loads. See comment
6.
No default (Real)
ST, SC, SS Stress limits in tension, compression and shear. Used for composite ply
failure calculations.
No default (Real)
Comments
1. The material identification number must be unique for all MAT1, MAT2, MAT8 and MAT9
entries.
2. The mass density, RHO, is used to automatically compute mass for all structural elements.
3. The convention for the Gij in fields 3 through 8 are represented by the matrix relationship:
4. If this entry is referenced by the MID3 field (transverse shear) on the PSHELL, G13, G23,
and G33 must be blank.
5. Unlike the MAT1 entry, data from the MAT2 entry is used directly, without adjustment of
equivalent E, G, or NU values.
6. TREF is used as the reference temperature for the calculation of thermal loads.
8. To obtain the damping coefficient GE, multiply the critical damping ratio, C/C0, by 2.0.
Description
Defines the material properties for linear, temperature-independent, and orthotropic materials
used by the CTAXI and CTRIAX6 axisymmetric elements.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
direction.
NUTHZ = Poisson’s Ratio for strain in the z direction when stress in the θ
direction.
NUZX = Poisson’s Ratio for strain in the x direction when stress in the z
direction.
No default (Real)
No default (Real)
No default (Real)
Comments
1. The material identification number must be unique for all MAT1, MAT2, MAT8 and MAT9
entries.
2. Values of all seven elastic constants, EX, ETH, EZ, NUXTH, NUTHZ, NUZX and GZX must
be present.
4. The x, θ and z directions are principal material directions of the material coordinate
system. Each element (that is a CTAXI or CTRIAX6 element) supporting the use of MAT3
contains a “Theta” field to relate the principal material directions to the basic coordinate
system.
6. To obtain the damping coefficient GE, multiply the critical damping ratio, C/C0, by 2.0.
Description
Defines constant thermal material properties for conductivity, density, and heat generation.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
K Thermal conductivity.
RHO Density.
HGEN Heat generation capability used with QVOL entries. HGEN is the scale factor
used with QVOL (See comment 3).
Comments
1. The material identification number may be the shared with structural material property
definitions (MAT1, MAT2, MAT8, MAT9 or MGASK) but must be unique with respect to
other thermal material property definitions (MAT4 or MAT5).
2. MAT4 may specify material properties for any conduction elements. MAT4 also provides
the heat transfer coefficient for free convection (see CONV).
3. HGEN is the scale factor and QVOL is the power generated per unit volume, Pin = volume *
HGEN * QVOL.
4. This card is represented as a material in HyperMesh.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
RHO HGEN
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
2e5
Field Contents
RHO Density.
HGEN Heat generation capability used with QVOL entries. HGEN is the scale factor
used with QVOL (See comment 3).
Comments
1. The material identification number may be the shared with structural material property
definitions (MAT1, MAT2, MAT8, MAT9 or MGASK), but must be unique with respect to
other thermal material property definitions (MAT4 or MAT5).
3. HGEN is the scale factor and QVOL is the power generated per unit volume, Pin = volume *
HGEN * QVOL.
4. This card is represented as a material in HyperMesh.
Description
Defines the material properties for linear temperature-independent orthotropic material for
two-dimensional elements.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
A1 A2 TREF Xt Xc Yt Yc S
GE F12 STRN
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
NU12
Poisson’s ratio ( for uniaxial loading in 1-direction). Note that for
uniaxial loading in 2-direction is related to by the relation
.
No default (Real)
No default (Real)
No default (Real)
No default (Real)
TREF Reference temperature for the calculation of thermal loads. See comment 3.
Xt, Xc, Allowable stresses or strains in the longitudinal and lateral directions. Used for
Yt, Yc composite ply failure calculations.
No default (Real)
No default (Real)
STRN Indicates whether Xt, Xc, Yt, or Yc are stress or strain allowables.
Default = blank (Real = 1.0 for strain allowables, blank for stress allowables)
Comments
1. The material identification number must be unique for all MAT1, MAT2, MAT8 and MAT9
entries.
2. If G1, Z and G2, Z values are specified as zero or are not supplied, a penalty term is used
to enforce very high transverse shear stiffness.
3. An approximate value for G1, Z and G2, Z is the inplane shear modulus G12. If test data
not available to accurately determine G1, Z and G2, Z for the material and transverse
shear calculations, the value of G12 may be supplied for G1, Z and G2, Z.
7. The option of interpreting Xt, Xc, Yt, and Yc as strains is only available for composite
definitions (PCOMP or PCOMPG) using the STRN failure criterion. In this case, the STRN
flag indicates whether Xt, Xc, Yt, and Yc are stress or strain allowables.
For all other failure criteria Xt, Xc, Yt, and Yc are always interpreted as stresses,
regardless of the value of the STRN flag.
8. The value of E1 should be greater than that of E2 for the material to be stable. If E1 <
E2, then the material matrix becomes indefinite leading to an unstable material.
Description
Defines the material properties for linear, temperature-independent, and anisotropic materials
for solid elements.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
A2 A3 A4 A5 A6 TREF GE
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
6.2+3
6.5-6 125.
Field Contents
No default (Real)
No default (Real)
No default (Real)
TREF Reference temperature for the calculation of thermal loads. See comment 6.
No default (Real)
Comments
1. The material identification number must be unique for all MAT1, MAT2, MAT8, MAT9ORT
and MAT9 entries.
2. The mass density, RHO, is used to automatically compute mass for all structural elements.
3. The convention for the Gij in fields 3 through 8 are represented by the matrix relationship.
The subscripts 1 to 6 refer to x, y, z, xy, yz, and zx of the material coordinate system
defined by the CORDM field on the PSOLID entry.
4. Unlike the MAT1 entry, data from the MAT9 entry is used directly, without adjustment of
equivalent E, G, or NU values.
6. TREF is used as the reference temperature for the calculation of thermal loads.
9. To obtain the damping coefficient GE, multiply the critical damping ratio, C/C0, by 2.0.
Description
Defines the material properties for linear, temperature-independent, and orthotropic materials
for solid elements in terms of engineering constants.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
MID Material identification number. Must be unique with respect to other MAT1,
MAT2, MAT8, MAT9, and MAT9ORT definitions
No default (Real)
No default (Real)
No default (Real)
No default (Real)
No default (Real)
No default (Real)
TREF Reference temperature for the calculation of thermal loads. See comment 5.
Comments
and
4. It may be difficult to find all nine orthotropic constants. In some practical problems, the
material properties may be reduced to normal anisotropy in which the material is isotropic
in a plane (for example, plane 1-2), and has different properties in the direction normal to
this plane.
with and
In case the material has a planar anisotropy, in which the material is orthotropic only in a
plane, the elastic constants are reduced to seven .
5. TREF is used as the reference temperature for the calculation of thermal loads.
6. To obtain the damping coefficient GE, multiply the critical damping ratio, C/C0 by 2.0.
7. Internal conversion from MAT9ORT to MAT9. The material property fields of the MAT9
entry are calculated internally from the MAT9ORT entry using the following formula:
The values of , E and G for the expressions in the above equations in comment 7 are
taken from the NUij , Ei and Gij fields respectively of this MAT9ORT entry where i, j €
{1,2,3} and the values of (see above equations
in comment 7) are used to populate the G11, G22, G33, G44, G55, G66, G12, G13, and G23
fields (G12=G21, G13=G31 and G23=G32 due to symmetry) of the MAT9 entry. The
remaining elements of the MAT9 entry (that is G14, G15, G24, and so on) are equal to
zero.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
C Speed of sound.
No default (Real)
ALPHA
Normalized porous material damping coefficient. See comment 6.
No default (Real)
Comments
2. The material identification number must be unique with respect to MAT1, MAT2, MAT3,
MAT9, and MAT10 entries, but may be shared with MAT4, MAT5 or MATFAT.
3. The mass density RHO will be used to compute the mass automatically.
Two out of the three must be specified, and the other will be calculated according to this
equation.
5. To obtain the damping coefficient GE, multiply the critical damping ratio C/C0 by 2.0.
6. Since the admittance is a function of frequency, the value of ALPHA should be chosen for
the frequency range of interest for the analysis.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
STATIC YS UTS
SN SR1 b1 Nc1 b2 FL SE
EN Sf b c Ef np Kp Nc
SEe SEp
Field Contents
UNIT Defines the units of stress values specified on the YS, UTS, SRI1, FL, Sf, and
Kp fields
STATIC STATIC flag indicates that static material properties are defined in the following
fields.
SN SN flag indicating that fatigue material properties for SN analysis are following.
b1 The first fatigue strength exponent. It is the slope of the first segment of SN
curve in log-log scale.
Nc1 In one-segment S-N curve, this is the cycle limit of endurance (see NC1 in
Figure 1).
In two-segment S-N curve, this is the transition point (see NC1 in Figure 2).
b2 The second fatigue strength exponent. It is the slope of the second segment
of SN curve in log-log scale.
FL Fatigue Limit; No damage occurs if the stress range is less than FL (see FL in
Figures 1 and 2). See comment 6.
EN EN flag indicating that fatigue material properties for EN analysis are following.
Nc Reversal limit of endurance. One cycle contains two reversals. See comment
6.
FOS The FOS flag indicates that material properties for factor of safety analysis are
defined in the following fields.
Figure 1a: One-segment S-N curve in log-log scale Figure 1b: One-segment S-N curve in log-log scale
(b2=0) (b2=0)
(Nc1 is not defined or less conservative than FL) (FL is not defined or less conservative than Nc1)
Comments
1. UTS or YS is used in mean stress correction (SN) and surface finish correction (SN and
EN). If both UTS and YS are defined, UTS will be used. It is not allowed that both UTS
and YS are blanks.
2. S-N data defined in the MATFAT card is expected to be obtained from standard
experiments that are fully reversed bending on mirror-polished specimens.
3. S-N curves are defined in Stress range – Cycle form. Stress range is the algebraic
difference between the maximum and minimum stress in a cycle. SN curve is expressed
as:
Where S r is the stress range, SRI1 is the fatigue strength coefficient, is the cycle
number, is the fatigue strength exponent.
4. E-N curves are defined in Strain amplitude - Reversal form. Strain amplitude is half of the
algebraic difference between the maximum and minimum strain in a cycle, and one strain
cycle contains two reversals. EN curve is expressed as:
Where, is the strain amplitude, is the fatigue strength coefficient, E is the Young's
modulus, is the cycle number, is the fatigue strength exponent, is the fatigue
5. Empirical formula can be used to estimate SN/EN data from ultimate tensile strength
(UTS) and Young’s modulus (E):
6. For one-segment SN curve (b2=0.0), if FL is blank, the fatigue limit is the stress range at
Nc1. If both Nc1 and FL are defined, the more conservative value (larger damage) will be
used (Figure 1).
When fatigue optimization is performed, fatigue limit FL of S-N data and reversal limit Nc
of E-N data will be ignored in order to get continuous changes in fatigue results when
stress/strain changes.
Description
Specifies frequency-dependent material properties on MAT1 entry fields via TABLEDi entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATF1 17 32 17 53
Field Contents
(Integer > 0)
(Integer or blank)
T(ST) Identification number of a TABLEDi entry for the tension stress limit.
Comments
2. The MATF1 entries may refer to blank entries on the respective MAT1 card. In this case,
they will be applied to default values of respective parameters. Initial values of E, G, or
NU will be supplied according to comment 4 on the MAT1 entry.
3. Table references must be present for each item that is frequency dependent. For
example, it is not sufficient to only give table references for fields 3 and 4 (Young’s
modulus and shear modulus) if density is also frequency dependent.
Description
Specifies frequency-dependent material properties on MAT2 entry fields via TABLEDi entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATF2 17 32 15 44
62
Field Contents
(Integer > 0)
coefficient.
(Integer or blank)
T(ST) Identification number of a TABLEDi entry for the tension stress limit.
Comments
2. The MATF2 entries may refer to blank entries on the respective MAT2 card. In this case,
they will be applied to default values of respective parameters.
Description
Specifies frequency-dependent material properties on MAT3 data entry fields via TABLEDi
entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATF3 17 32 19
52
Field Contents
(Integer > 0)
T(EX) Identification numbers of TABLEDi entries for Young’s moduli in the x, θ and z
T(ETH) directions.
T(EZ)
Default = blank (Integer > 0 or blank)
T(EX) Identification numbers of TABLEDi entries for Poisson’s ratios in the xθ, θz
T(ETH) and zx directions.
Comments
2. Blank or zero entries mean that there is no frequency dependence of the field on the
MAT3 entry. Any quantity modified by this entry must have a value on the MAT3 entry.
Description
Specifies frequency-dependent material properties on MAT8 entry fields via TABLEDi entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
T(GE) T(F12)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATF8 17 32 15
52
Field Contents
(Integer > 0)
T(NU12) Identification number of a TABLEDi entry for the Poisson’s ratio 12.
T(G1Z) Identification number of a TABLEDi entry for transverse shear modulus 1Z.
T(G2Z) Identification number of a TABLEDi entry for transverse shear modulus 2Z.
T(A1) Identification number of a TABLEDi entry for the thermal expansion coefficient
1. See comment 3.
(Integer or blank)
T(A2) Identification number of a TABLEDi entry for the thermal expansion coefficient
2.
(Integer or blank)
T(Xt) Identification number of a TABLEDi entry for the tension stress/strain limit 1.
Comments
2. Blank or zero entries mean that there is no frequency dependence of the fields on the
MAT8 entry. The MATF8 entries may refer to blank entries on the respective MAT8 card.
In which case, they will be applied to default values of the respective parameters.
Description
Specifies frequency-dependent material properties on MAT9 entry fields via TABLEDi entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATF9 17 32 18 17
12 5
10
Field Contents
(Integer > 0)
T(Gij) Identification number of a TABLEDi entry for the terms in the material
property matrix.
(Integer or blank)
Comments
2. If the fields are zero or blank, there is no frequency dependence of the field on the MAT9
entry. The MATF9 entries may refer to blank entries on the respective MAT9 card. In
which case, they will be applied to default values of respective parameters.
Description
Specifies frequency-dependent material properties on MAT10 entry fields via TABLEDi entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATF10 2 10 13 17 19
Field Contents
(Integer > 0)
damping coefficient.
Comments
2. If the fields are zero or blank, there is no frequency dependence of the field on the
MAT10 entry. The MATF10 entries may refer to blank entries on the respective MAT10
card. In which case, they will be applied to default values of respective parameters.
Description
The MATHE bulk data entry defines material properties for nonlinear hyperelastic materials. The
Polynomial form is available and various material types (comment 3) can be defined by
specifying the corresponding coefficients.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C 20 C 11 C 02 D2 NA ND
C 30 C 21 C 12 C 03 D3
C 40 C 31 C 22 C 13 C 04 D4
C 50 C 41 C 32 C 23 C 14 C 05 D5
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATHE 2 MOONEY
80 20 0.001
Field Contents
ND Order of the volumetric strain energy polynomial function (see comment 2).
Default = 1 (Integer)
TAB1 Table identification number of a TABLES1 entry that contains simple tension-
compression data to be used in the estimation of the material constants,
Cpq, related to distortional deformation. The x-values in the TABLES1 entry
should be the stretch ratios and y-values should be values of the engineering
stress.
TAB4 Table identification number of a TABLES1 entry that contains pure shear data
to be used in the estimation of the material constants, Cpq, related to
distortional deformation. The x-values in the TABLES1 entry should be the
stretch ratios and y-values should be values of the nominal stress.
Comments
1.
curve fit values based on the corresponding TAB# tables. However, any Cpq values set to
0.0 are not overwritten.
Where,
N2 is the order of the volumetric strain energy polynomial function (ND). Currently only
first order volumetric strain energy functions are supported (ND=1).
Dp are material constants related to volumetric deformation (Dp). These values define the
compressibility of the material.
3. The polynomial form can be used to model the following material types by specifying the
corresponding coefficients (Cpq, Dp) on the MATHE entry:
Mooney-Rivlin Material:
N1 = N2 =1
1 2
U C10 I1 3 C01 I 2 3 J elas 1
D1
Reduced Polynomial:
q=0
N1 N2
p 1 2p
U C p 0 I1 3 J elas 1
p 1 p 1 Dp
Neo-Hooken Material
N1= N2 =1, q=0
1 2
U C10 I1 3 J elas 1
D1
N1 = N2 =3, q=0
1 2 2 1 4 3 1 6
U C10 I1 3 J elas 1 C20 I1 3 J elas 1 C30 I1 3 J elas 1
D1 D2 D3
Signiorini Material:
2
U C10 I1 3 C01 I 2 3 C20 I1 3
4. The MATHE hyperelastic material supports CTETRA (4, 10), CPENTA (6, 15), and CHEXA
(8, 20) element types.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
E Young’s Modulus.
No default (Real)
NU Poisson’s Ratio.
Y Yield stress.
No default (Real)
K Strength coefficient.
No default (Real)
Comments
1. This entry is only valid with a @HyperForm statement in the first line of the input file.
2. The TABLEID and the corresponding curve are required only when material data is
specified with a stress-strain curve. For such case, material parameter such as K, n and
EPS0 are extracted from the stress strain curve.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATPE1 17 1 10 1.0
Field Contents
MAT1 Material identification number of the MAT1 bulk data entry (or MATF1 if it is
frequency-dependent) for the skeleton.
MAT10 Identification number of MAT10 bulk data entry for the porous material.
Comments
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TYPSTRN
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
H Work hardening slope (slope of stress versus plastic strain) in units of stress.
For elastic-perfectly plastic cases, H = 0.0. For more than a single slope in
the plastic range, the stress-strain data must be supplied on a TABLES1
entry referenced by TID, and this field must be blank. See comment 2.
(Real > 0)
2 = Kinematic Hardening
See comment 4.
TYPSTRN Specifies the type of strain used on the x-axis of the table pointed to by
TID. The strain type is selected by one of the following values. See
comment 5.
Default = 0 (Integer, 0, or 1)
1. For nonlinear elastic material, the stress-strain data given in the TABLES1 entry will be
used to determine the stress for a given value of strain. The values H, YF, HR, and
LIMIT1 will not be used in this case. Nonlinear elastic material is only available in NLGEOM
subcases.
2. For elastoplastic materials, the elastic stress-strain matrix is computed from a MAT1
entry, and the isotropic plasticity theory is used to perform the plastic analysis. In this
case, either the table identification TID or the work hardening slope H may be specified,
but not both. If the TID is omitted, the work hardening slope H must be specified unless
the material is perfectly plastic. The plasticity modulus (H) is related to the tangential
modulus (ET ) by
where, E is the elastic modulus and is the slope of the uniaxial stress-strain
curve in the plastic region.
3. If TID is given, TABLES1 entries (Xi,Yi) of stress-strain data ( ) must conform to the
following rules:
If TYPE = "PLASTIC", the curve must be defined in the first quadrant. The data points
must be in ascending order. If the table is defined in terms of total strain (TYPSTRN = 0),
the first point must be at the origin (X1 = 0, Y1 = 0) and the second point (X2, Y2) must
be at the initial yield point (Y 1) specified on the MATS1 entry. The slope of the line
joining the origin to the yield stress must be equal to the value of E. If the table is
defined in terms of plastic strain (TYPSTRN = 1), the first point (X1, Y1), corresponding to
yield point (Y 1), must be at X1=0. TID may reference a TABLEST entry. In this case, the
above rules apply to all TABLES1 tables pointed to by TABLEST.
If TYPE = “NLELAST”, the full stress-strain curve may be defined in the first and third
quadrants to accommodate different uniaxial compression data. If the curve is defined
only in the first quadrant, then the curve must start at the origin (X1 = 0.0, Y1 = 0.0).
For analyses where small deformations are assumed, there should be little or no difference
If the deformations go past the values defined in the table, the curve is extrapolated
linearly.
4. Kinematic hardening and Mixed hardening are supported only for solids.
5. The conversion of the relation stress vs. total strain (TYPSTRN=0) into stress vs. plastic
strain (TYPSTRN=1) is illustrated below. This is clearly different than simply shifting the
entire table along the epsilon-axis.
9. Linear Buckling Analysis and Preloaded Analysis are not supported with models containing
nonlinear (MATS1) material entries. However, you can use PARAM,PRESUBNL,YES to force
OptiStruct to run in such models. Linear Buckling Analysis or Preloaded Analysis is not
recommended in models with nonlinear materials or in large displacement nonlinear
analysis. It is the user’s responsibility to interpret the results with caution.
Description
Specifies temperature-dependent material properties on MAT1 entry fields via TABLEMi entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATT1 17 32 15
52
Field Contents
MID Material property identification number that matches the identification number
on MAT1 entry.
(Integer > 0)
(Integer or blank)
T(ST) Identification number of a TABLEMi entry for the tension stress limit.
Comments
1. Fields 3, 4, and so on, of this entry correspond, field-by-field, to fields 3, 4, and so on, of
the MAT1 entry referenced in field 2. The value in a particular field of the MAT1 entry is
replaced or modified by the table referenced in the corresponding field of this entry. In
the example shown, E is modified; TABLEMi 32, A is modified by TABLEMi 15; and ST is
modified by TABLEMi 52. Blank or zero entries mean that there is no temperature
dependence of the field on the MAT1 entry.
2. The MATT1 entries may refer to blank entries on the respective MAT1 card. In this case,
they will be applied to default values of respective parameters. Initial values of E, G, or
NU will be supplied according to comment 4 on the MAT1 entry.
3. Table references must be present for each item that is temperature dependent. For
example, it is not sufficient to only give table references for fields 3 and 4 (Young’s
modulus and shear modulus) if Poisson’s ratio is temperature dependent.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATT2 17 32 15
62
Field Contents
MID Material property identification number that matches the identification number
on a MAT2 entry.
(Integer > 0)
T(Gij) Identification number of a TABLEMk entry for the terms in the material
property matrix.
(Integer or blank)
T(ST) Identification number of a TABLEMk entry for the tension stress limit.
Comments
2. The MATT2 entries may refer to blank entries on the respective MAT2 card. In which
case, they will be applied to default values of respective parameters.
Description
Specifies temperature-dependent material properties on MAT3 entry fields via TABLEMi entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATT3 17 32 19
52
Field Contents
(Integer > 0)
T(EX), Identification number of a TABLEMi entry for the Young’s moduli in the x, θ
T(ETH), and z directions.
T(EZ)
Default = blank (Integer > 0 or blank)
T(NUXTH), Identification number of a TABLEMi entry for the Poisson’s ratios in the xθ, θz
Comments
1. Fields 3, 4, and so on, of this entry correspond, field-by-field, to fields 3, 4, and so on, of
the MAT3 entry referenced in field 2. The value in a particular field of the MAT3 entry is
replaced or modified by the table referenced in the corresponding field of this entry. In
the example shown, EX is modified; TABLEMi 32, EZ is modified by TABLEMi 19; and GZX is
modified by TABLEMi 52. Blank or zero entries mean that there is no temperature
dependence of the field on the MAT3 entry.
2. Any quantity modified by this entry must have a value on the MAT3 entry.
Description
Defines temperature-dependent material properties for the corresponding MAT4 bulk data
entry fields via TABLEMi entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATT4 24 200
Field Contents
MID Material identification number of a MAT4 bulk data entry that is temperature
dependent.
Comments
1. The quantities defined on the MAT4 bulk data entry are multiplied by the tabular function
referenced by the MATT4 bulk data card to generate the corresponding material
properties.
2. If the fields are blank or zero, then constant properties defined on the MAT4 bulk data
card are used.
Description
Specifies temperature-dependent material properties on MAT8 entry fields via TABLEMi entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
T(GE) T(F12)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATT8 17 32 15
15 52
Field Contents
(Integer > 0)
T(NU12) Identification number of a TABLEMi entry for the Poisson’s ratio 12.
T(G1Z) Identification number of a TABLEMi entry for transverse shear modulus 1Z.
T(G2Z) Identification number of a TABLEMi entry for transverse shear modulus 2Z.
(Integer or blank)
(Integer or blank)
T(Xt) Identification number of a TABLEMi entry for the tension stress/strain limit 1.
Comments
2. The MATT8 entries may refer to blank entries on the respective MAT8 card. In which
case, they will be applied to default values of respective parameters.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATT9 17 32 18 17
12
5 10
Field Contents
MID Material property identification number that matches the identification number
on a MAT9 entry.
(Integer > 0)
T(Gij) Identification number of a TABLEMk entry for the terms in the material
property matrix.
Comments
2. The MATT9 entries may refer to blank entries on the respective MAT9 card. In which
case, they will be applied to default values of respective parameters.
MATX0 – Material Property Extension for Void Material for Geometric Nonlinear Analysis
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATX0 MID
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATX0 102
Field Contents
Comments
1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATX0 material extension can be associated with a particular MAT1.
2. MATX0 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN subcase entry. For all other subcases, it is
treated as an elastic material defined by the associated MAT1.
Description
Defines additional material properties for Johnson-Cooke elastic-plastic material for geometric
nonlinear analysis. This is an elasto-plastic law with strain rate and temperature effects.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
IC C FSMOOTH FC UT M TMELT RC P
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Real > 0)
(Real > 0)
ICC Flag for strain rate dependency of σmax (See comment 5).
FCUT Cutoff frequency for strain rate filtering. Only for shell and solid elements.
M Temperature exponent.
Comments
1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.
2. MATX02 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. This is an elastic-plastic law with strain rate and thermal effects. It follows:
with:
= plastic strain
= strain rate
4. If the plastic strain reaches EPSMAX, shell elements are deleted. Solid elements are not
deleted, but the deviatoric stress is set to zero.
7. Strain rate filtering is used to smooth strain rates. The input FCUT is available only for
shell and solid elements.
8. To take into account the temperature effect, strain rate dependence must be activated.
If the temperature exponent M = 0; there is no temperature effect. No temperature
effect is considered on rod, bar, and beam elements.
MATX13 – Material Property Extension for Rigid Material for Geometric Nonlinear Analysis
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATX13 MID
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATX13 102
Field Contents
Comments
1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.
2. MATX13 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
MATX21 – Material Property Extension for Rock-Concrete Material for Geometric Nonlinear
Analysis
Description
Defines additional material properties for Rock-Concrete material for geometric nonlinear
analysis. This law is based on the Drücker-Prager yield criteria and is used to model materials
with internal friction such as rock-concrete. The plastic behavior of these materials is
dependent on the pressure in the material. This law is only applicable to solid elements.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATX21 102 3
1 1E10
Field Contents
A0 Coefficient.
(Real)
A1 Coefficient.
(Real)
A2 Coefficient.
(Real)
TPID Identification number of a TABLES1 that defines the volumetric strain vs.
pressure function.
(Real)
Comments
1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATX21 material extension can be associated with a particular MAT1.
2. MATX21 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
4. Drücker-Prager yield criteria uses a modified von Mises yield criteria to incorporate the
effects of pressure for massive structures:
where,
P: pressure.
vm 3 A0
A1 = A2 = 0 means that the yield criteria is von Mises ( )
6. External pressure is required if relative pressure formulation is used. In this specific case,
yield criteria and energy integration require the value of total pressure.
MATX25 – Material Property Extension for Tsai-Wu and CRASURVT Materials for Geometric
Nonlinear Analysis
Description
Defines an elasto-plastic orthotropic material with Tsai-Wu and CRASURVT yield criteria for
composite shell materials.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
FSMOOTH FC UT IFORM
B N FMAX
C EPSR0 ALFA IC C G
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
1E10 1E10
Field Contents
(Real)
(Real)
(Real)
(Real)
Default = 0 (Integer)
= 3: if for each layer, Wp* > Wp*max or tensile failure in direction 2(t2)
= 4: if for each layer, Wp* > Wp*max or tensile failure in directions 1(t1) and
2(t2)
= 5: if for all layers: Wp* > Wp*max or tensile failure in direction 1(t1)
or if for all layers: Wp* > Wp*max or tensile failure in direction 2(t2)
= 6: if for each layer, Wp* > Wp*max or tensile failure in direction 1(t1) or
2(t2)
< 0.0: the element will be deleted if all of the layers but one fail (the number
of layers that did not fail is equal to 1).
IFORM = TSAI
B Hardening parameter.
(Real)
N Hardening exponent.
(Real > 0)
(Real > 0)
(Real > 0)
(Real > 0)
(Real > 0)
(Real > 0)
(Real)
(Real)
ICC Flag for yield stress in shear and strain rate (See comment 9).
(Integer)
= 0: Default set to 1
= 1: Strain rate effect on FMAX no effect on WPMAX
= 2: No strain rate effect on FMAX and WPMAX
= 3: Strain rate effect on FMAX and WPMAX
= 4: No strain rate effect on FMAX effect on WPMAX
IFORM = CRAS
(Real)
(Real)
ICCG Global composite plasticity parameters flag for strain rate computation: (See
comment 9).
Default = 1 (Integer)
(Real > 0)
(Real)
Default = C (Real)
(Real > 0)
Default = C (Real)
(Real > 0)
Default = C (Real)
(Real > 0)
Default = C (Real)
(Real > 0)
Default = C (Real)
Comments
1. The material identification number must be that of an existing MAT8 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT8.
2. MATX25 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. Tsai-Wu formula (IFORM=TSAI) is not available with QEPH (ISHELL=24 on PCOMPX) shell
elements, it is only available with Q4 (ISHELL=1,2,3,4 on PCOMPX) and QBAT(ISHELL=12
on PCOMPX) shell elements.
with:
where,
n = Hardening exponent
Another modification concerns the parameters F ij which are expressed now in function of
plastic work and plastic work rate as below:
6. If the total tensile failure value EPSF1 is reached in the direction 1 and respectively ε
EPSF2 in the direction 2, the stresses tensor in the layer is permanently reset to 0.
When ICC=2,3,4 for Tsai-Wu formula, when ICCG=3,4 for CRASURV formula.
with applies to the all shell and not independently per each layer.
11. Thereby, the coefficients GAMINI, GAMMAX, and DMAX considered, are the coefficients
which are defined in the global material associated to the shell equivalent out-of-plane
shear strain.
12. The IOFF and RATIO field values are utilized only if they are defined in the material
assigned to a part, these fields are not considered if they are only defined in material
used for a layer in the property entry. This option is not available for solid elements.
MATX27 – Material Property Extension for Elastic-Plastic Brittle Material for Geometric
Nonlinear Analysis
Description
Defines additional material properties for elastic-plastic brittle material for geometric nonlinear
analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
IC C
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Real > 0)
(Real > 0)
Comments
1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.
2. MATX27 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. This law is only applicable with shell elements. The isotropic elasto-plastic model is the
same as with MATX02. However, MATX27 allows material damage and brittle failure to be
modeled.
6. An element is removed if one layer reaches the tensile failure strain EPS1.
MATX28 – Material Property Extension for Honeycomb Material for Geometric Nonlinear
Analysis
Description
Defines additional material properties for Honeycomb material for geometric nonlinear analysis.
This law is only applicable to solid elements.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATX28 MID
TIID11 TIID22 TIID33 IFLAG1 FSC AI11 FSC AI22 FSC AI33
TIID12 TIID23 TIID31 IFLAG2 FSC AI12 FSC AI23 FSC AI31
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
102
MATX28
0 0 0
Field Contents
TIID11 Identification number of a TABLES1 that defines the initial yield stress function
in direction 11.
TIID22 Identification number of a TABLES1 that defines the initial yield stress function
in direction 22.
TIID33 Identification number of a TABLES1 that defines the initial yield stress function
in direction 33.
IFLAG1 Strain formulation for yield functions 11, 22, and 33. See comment 4.
(Real)
(Real)
(Real)
TIID12 Identification number of a TABLES1 that defines the initial shear yield stress
function in direction 12.
TIID23 Identification number of a TABLES1 that defines the initial shear yield stress
function in direction 23.
TIID31 Identification number of a TABLES1 that defines the initial shear yield stress
function in direction 31.
IFLAG2 Strain formulation for yield functions 12, 23, and 31.
FSCAI12 Scale factor on initial shear yield stress function in direction 12.
FSCAI23 Scale factor on initial shear yield stress function in direction 23.
FSCAI31 Scale factor on initial shear yield stress function in direction 31.
(Real)
(Real)
(Real)
Comments
1. The material identification number must be that of an existing MAT9ORT bulk data entry.
Only one MATX28 material extension can be associated with a particular MAT9ORT.
2. MATX28 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. This law is compatible with 10 node tetrahedron elements, and it is compatible with
ISOLID = 1, 2, or 12 on PSOLIDX card.
4. This law is not compatible with IFRAME = OFF, if it is referenced by the PSOLIDX card.
6. If one of the failure or shear failure strains is reached, the element is deleted.
7. Transition strains define transition from initial yield stress function to residual yield stress
function.
8. If one of the transition or shear transition strains is reached, the element has yield stress
described by residual functions in each direction. Transition is applied to the neighboring
elements.
MATX33 – Material Property Extension for Visco-Elastic Plastic Foam Material for Geometric
Nonlinear Analysis
Description
Defines additional material properties for visco-elastic plastic foam material for geometric
nonlinear analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
A B C E1 E2 ET ETAC ETAS
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATX33 133 0
Field Contents
TID Identification number of TABLES1 entry that defines the yield stress vs.
volumetric strain curve.
A Yield parameter.
B Yield parameter.
C Yield parameter.
No default (Real)
No default (Real)
ET Tangent modulus.
Comments
1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.
2. MATX33 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. This material can be used only with solid elements, typically used to model low density,
closed cell polyurethane foams such as impact limiters.
where, is the volumetric strain, Φ is the porosity, P0 is the initial air pressure, 0 is the
initial volumetric strain. The volumetric strain < 0 in compression.
E = max(E, E1 + E2)
MATX36 – Material Property Extension for Piece-wise Linear Elastic-plastic Material for
Geometric Nonlinear Analysis
Description
Defines additional material properties for piece-wise linear elastic-plastic material for geometric
nonlinear analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TPID PSC A
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATX36 102
10 1.0
7 1.0 0.0
FCUT Cutoff frequency for strain rate filtering. Only for shell and solid elements.
Between 0.0 and 1.0 - Hardening is interpolated between the two models.
TIDi Identification number of a TABLES1 that defines the yield stress vs. plastic
strain function corresponding to EPSRi. Separate functions must be defined
for different strain rates.
EPSRi Strain rate. Strain rate values must be given strictly in ascending order.
(Real)
Comments
1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.
2. MATX36 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. The first point of yield stress functions (plastic strain vs. stress) should have a plastic
strain value of zero. If the last point of the first (static) function equals 0 in stress, the
default value of EPSMAX is set to the value of the corresponding plastic strain.
5. If the first principal strain ε1 reaches εt1 = EPST1, the stress σ is reduced by
6. If the first principal strain ε1 reaches εt2 = EPST2, the stress is reduced to 0 (but the
element is not deleted).
8. Strain rate filtering is used to smooth strain rates. The input FCUT is available only for
shell and solid elements.
10. The kinematic hardening model is not available with global formulation (NIP = 0 on
PSHELX), that is hardening is fully isotropic.
11. In case of kinematic hardening and strain rate dependency, the yield stress depends on
the strain rate.
12. TPID is used to distinguish the behavior in tension and compression for certain materials
(that is pressure dependent yield). This is available for both shell and solid elements.
The effective yield stress is then obtained by multiplying the nominal yield stress by the
yield factor PSCA corresponding to the actual pressure.
13. The first function TID1 is used for strain rate values from 0 to the corresponding strain
rate EPSR1. However, the last function used in the model does not extend to the
maximum strain rate; for higher strain rates, a linear extrapolation will be applied. Hence,
if < EPSRi, the yield stress is interpolated between TIDi and TIDi-1. If < EPSR1, TID1
is used. Above EPSRmax the yield stress is extrapolated.
14. Strain rate values must be given strictly in ascending order. Separate functions must be
defined for different strain rates.
15. At least one strain rate is needed under which the yield stress vs. plastic strain function
is defined.
MATX42 – Material Property Extension for Ogden, Mooney-Rivlin Material for Geometric
Nonlinear Analysis
Description
Defines additional material properties for Ogden, Mooney-Rivlin material for geometric nonlinear
analysis. This material is used to model rubber, polymers, and elastomers.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PRONY G1 T1 G2 T2 G3 T3
G4 T4 G5 T5 ...
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATX42 102
TBID Identification number of a TABLES1 to define the bulk function f(J) that scales
the bulk modulus vs. relative volume. If TBID = 0, f(J) = const. = 1.0.
MUi Parameter µi
(Real)
ALFAi Parameter αi
(Real)
(Real)
(Real)
Comments
1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.
2. MATX42 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
P = K * FBULK * f (J) * (J - 1)
W = C1 0 (I1 - 3) + C0 1 (I2 - 3)
where, Ii is ith invariant of the right-hand Cauchy-Green Tensor. It can be modeled using
the following parameters:
µ1 = 2 * C1 0
α1 = 2.0
α2 = -2.0
and
MATX43 – Material Property Extension for Hill Orthotropic Material for Geometric Nonlinear
Analysis
Description
Defines additional material properties for Hill Orthotropic material for geometric nonlinear
analysis. This law is only applicable to two-dimensional elements.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
… … …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
1 1.0 0.1
2 1.0 0.05
TIDi Identification number of a TABLES1 that defines the yield stress vs. plastic
strain function corresponding to EPSRi. Separate functions must be defined
for different strain rates.
Integer > 0
(Real)
Comments
1. The material identification number must be that of an existing MAT8 bulk data entry. Only
one MATX43 material extension can be associated with a particular MAT8. E1 must be
equal to E2 on MAT8 that is extended by MATX43.
2. MATX43 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. The yield stress is defined by a user function and the yield stress is compared to
equivalent stress.
4. Angles for Lankford parameters are defined with respect to orthotropic direction 1.
5. The Lankford parameters rα are determined from a simple tensile test at an angle α to the
orthotropic direction 1.
6. The hardening coefficient is used to describe the hardening model. Its value must be
between 0 and 1:
7. If the last point of the first (static) function equals 0 in stress, default value of failure
plastic strain EPSPF is set to the corresponding value of plastic strain, p.
8. If plastic strain εp reaches failure plastic strain εpmax , the element is deleted.
9. If ε1 (largest principal strain) > εt1(EPST1), stress is reduced according to the following
relation:
10. If ε1 (largest principal strain) > εt2(EPST2), the stress is reduced to be 0 (but the
element is not deleted). If (EPSRn), yield is interpolated between ƒn and ƒn-1. If
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATX44 144
Field Contents
(Real > 0)
(Real > 0)
ICC Flag for strain rate dependency of σmax (See comment 5).
Comments
1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.
2. MATX44 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. The Cowper-Symonds models an elastic-plastic material, only for solids and shells. The
basic principle is the same as the standard Johnson-Cook model; the only difference
between the two lies in the expression for strain rate effect on flow stress
7. Strain rate filtering is used to smooth strain rates. The input FCUT is available only for
shell and solid elements.
9. If the first principal strain ε1 reaches εt1 = EPST1, the stress σ is reduced by
10. If the first principal strain ε1 reaches εt2 = EPST2, the stress is reduced to 0 (but the
element is not deleted).
11. If the first principal strain ε1 reaches εf = EPSF, the element is deleted.
MATX60 – Material Property Extension for Piece-wise Nonlinear Elastic-plastic Material for
Geometric Nonlinear Analysis
Description
Defines additional material properties for piece-wise nonlinear elastic-plastic material for
geometric nonlinear analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TPID PSC A
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATX60 102
FCUT Cutoff frequency for strain rate filtering. Only for shell and solid elements.
TIDi Identification number of a TABLES1 that defines the yield stress vs. plastic
strain rate function corresponding to EPSRi. Separate functions must be
defined for different strain rates.
EPSRi Strain rate. Strain rate values must be given strictly in ascending order.
(Real)
Comments
1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATX60 material extension can be associated with a particular MAT1.
2. MATX60 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. The first point of yield stress functions (plastic strain vs. stress) should have a plastic
strain value of zero. If the last point of the first (static) function equals 0 in stress, the
default value of EPSMAX is set to the value of the corresponding plastic strain.
5. If the first principal strain ε1 reaches εt1 (EPST1), the stress σ is reduced by
6. If the first principal strain ε1 reaches εt2 (EPST2), the stress is reduced to 0 (but the
element is not deleted).
8. Strain rate filtering is used to smooth strain rates. The input FCUT is available only for
shell and solid elements.
10. The kinematic hardening model is not available with global formulation (NIP = 0 on
PSHELX), that is hardening is fully isotropic.
11. In case of kinematic hardening and strain rate dependency, the yield stress depends on
the strain rate.
12. TPID is used to distinguish the behavior in tension and compression for certain materials
(that is pressure dependent yield). This is available for solid elements only. The effective
yield stress is then obtained by multiplying the nominal yield stress by the yield factor
PSCA corresponding to the actual pressure.
14. Strain rate values must be given strictly in ascending order. Separate functions must be
defined for different strain rates.
MATX62 – Material Property Extension for Hyper-visco-elastic Material for Geometric Nonlinear
Analysis
Description
Defines additional material properties for Hyper-visco-elastic material for geometric nonlinear
analysis. This material is used to model rubber, polymers, and elastomers.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATX62 102
MUi Parameter µi
(Real)
ALFAi Parameter αi
(Real)
MAXWELL Indicates that MAXWELL model parameter pairs GAMi and Ti follow.
(Real)
(Real)
Comments
1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.
2. MATX62 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
with λi being the ith principal stretch, J = λ1 * λ2 * λ3 being the relative volume and
MATX65 – Material Property Extension for Tabulated Strain Rate Dependent Elastic-Plastic
Material for Geometric Nonlinear Analysis
Description
Defines additional material properties for tabulated strain rate dependent elastic-plastic
material for geometric nonlinear analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATX65 91 2.70E-06 1
1 2
Field Contents
(Real > 0)
TIDL Identification number of TABLES1 entry that defines the loading stress-strain
function.
(Integer > 0)
TIDU Identification number of TABLES1 entry that defines the unloading stress-
strain function.
(Integer > 0)
Comments
1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.
2. MATX65 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. The material law is defined by pairs of stress functions for loading and unloading at a
constant strain rate. For each strain rate, the yield stress is defined by the intersection
between loading and unloading curves. Unloading follows unloading curve shifted by
plastic strain value. Strain rates are interpolated using input values. In the elastic range,
stress smaller than the yield value, the material behavior is elastic with hysteresis. It is
The Young's modulus must be greater than the maximum function slopes, and is used to
follow loading and unloading paths between limiting curves.
For a constant strain rate, user defined functions set the limits for the cycling loading.
MATX68 – Material Property Extension for Honeycomb Material for Geometric Nonlinear
Analysis
Description
Defines additional material properties for Honeycomb material for geometric nonlinear analysis.
This law is only applicable to solid elements.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATX68 MID
TIID11 TIID22 TIID33 IFLAG1 FSC AI11 FSC AI22 FSC AI33
TIID12 TIID23 TIID31 IFLAG2 FSC AI12 FSC AI23 FSC AI31
Example
102
MATX68
0 0 0
Field Contents
TIID11 Identification number of a TABLES1 that defines initial yield stress function in
direction 11.
TIID22 Identification number of a TABLES1 that defines initial yield stress function in
direction 22.
TIID33 Identification number of a TABLES1 that defines initial yield stress function in
direction 33.
IFLAG1 Strain formulation for yield functions 11, 22, and 33. See comment 4.
(Real)
(Real)
(Real)
TIID12 Identification number of a TABLES1 that defines initial shear yield stress
TIID23 Identification number of a TABLES1 that defines Initial shear yield stress
function in direction 23.
TIID31 Identification number of a TABLES1 that defines Initial shear yield stress
function in direction 31.
IFLAG2 Strain formulation for yield functions 12, 23, and 31.
FSCAI12 Scale factor on initial shear yield stress function in direction 12.
FSCAI23 Scale factor on initial shear yield stress function in direction 23.
FSCAI31 Scale factor on initial shear yield stress function in direction 31.
(Real)
(Real)
(Real)
TIID21 Identification number of a TABLES1 that defines Initial shear yield stress
function in direction 21.
TIID32 Identification number of a TABLES1 that defines Initial shear yield stress
function in direction 32.
TIID13 Identification number of a TABLES1 that defines Initial shear yield stress
function in direction 13.
FSCAI21 Scale factor on initial shear yield stress function in direction 21.
FSCAI32 Scale factor on initial shear yield stress function in direction 32.
FSCAI13 Scale factor on initial shear yield stress function in direction 13.
TRID11 Identification number of a TABLES1 that defines residual yield stress function
in direction 11.
TRID22 Identification number of a TABLES1 that defines residual yield stress function
in direction 22.
TRID33 Identification number of a TABLES1 that defines residual yield stress function
in direction 33.
(Real)
(Real)
(Real)
TRID12 Identification number of a TABLES1 that defines residual shear yield stress
function in direction 12.
TRID23 Identification number of a TABLES1 that defines residual shear yield stress
function in direction 23.
TRID31 Identification number of a TABLES1 that defines residual shear yield stress
function in direction 31.
FSCAR12 Scale factor on residual shear yield stress function in direction 12.
FSCAR23 Scale factor on residual shear yield stress function in direction 23.
FSCAR31 Scale factor on residual shear yield stress function in direction 31.
(Real)
(Real)
(Real)
TRID21 Identification number of a TABLES1 that defines residual shear yield stress
function in direction 21.
TRID32 Identification number of a TABLES1 that defines residual shear yield stress
function in direction 32.
TRID13 Identification number of a TABLES1 that defines residual shear yield stress
function in direction 13.
FSCAR21 Scale factor on residual shear yield stress function in direction 21.
FSCAR32 Scale factor on residual shear yield stress function in direction 32.
FSCAR13 Scale factor on residual shear yield stress function in direction 13.
Comments
1. The material identification number must be that of an existing MAT9ORT bulk data entry.
Only one MATX68 material extension can be associated with a particular MAT9ORT.
2. MATX68 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. This law is compatible with 8 node brick elements with ISOLID =1 or ISOLID =2 on
PSOLIDX only.
5. If one of the failure or shear failure strains is reached, the element is deleted.
6. Transition strains define transition from initial yield stress function to residual yield stress
function.
7. If one of the transition or shear transition strains is reached, the element has yield stress
described by residual functions in each direction, Transition is applied to the neighbor
elements.
MATX70 – Material Property Extension for Tabulated Visco-elastic Foam Material for
Geometric Nonlinear Analysis
Description
Defines additional material properties for tabulated visco-elastic foam material for geometric
nonlinear analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SHAPE HYS
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(Real > 0)
(Real > 0)
Default = 1, if FLAG = 0
Default = 0, if FLAG = 1, 2, 3, or 4
(Integer > 0)
Default = 0 (Integer)
3 – The loading curve is used for both loading and unloading. For unloading,
the deviatoric stress is modified. The unloading curves are ignored.
4 - The loading curve is used for both loading and unloading. For unloading,
the stress tensor is modified. The unloading curves are ignored.
TIDL Identification number of TABLES1 entry that defines the loading function.
(Integer > 0)
TIDU Identification number of TABLES1 entry that defines the unloading function.
Comments
1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.
2. MATX70 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
IFLAG = 0 - The material behavior follows the defined curves for loading and unloading.
NLOAD and NULOAD must be greater than 0.
IFLAG = 1 - Both loading curves are used respectively. For unloading, the deviatoric
stress is modified by using the quasi-static unloading curve
are the current stresses computed respectively from the unloading and quasi-static
curves.
IFLAG = 2 - Both loading and unloading curves are used respectively. For unloading,
the stress tensor is modified using the quasi-static unloading curve σ = (1 - D)σ, where
D is calculated from the quasi-static unloading curve,
are the current stresses computed respectively from the unloading and quasi-static
curves.
where, Wcur and Wmax are the current and maximum energy, respectively.
IFLAG = 4 - The loading curves are used for both loading and unloading behavior. The
unloading curve is ignored. The unloading stress tensor is modified using σ = (1 - D)σ.
where, Wcur and Wmax are the current and maximum energy, respectively.
6. For stresses above the last load function, the behavior is extrapolated by using the two
last load functions. In order to avoid huge stress values, it is recommended to repeat the
last load function.
7. When maximum plastic strain EPSMAX is reached, EMAX is used whatever the curve
definition is.
8. If EMAX is blank, EMAX is set and equal to Young modulus on MAT1 card.
9. If EPSMAX is blank, it will be calculated automatically if EMAX is less than the maximum
tangent according to the input stress-strain curves.
10. Young's modulus E on MAT1 card would be modified automatically if it is less than the
initial value according to the input stress-strain curves' tangents.
MATX82 – Material Property Extension for Ogden Material for Geometric Nonlinear Analysis
Description
Defines additional material properties for Ogden material for geometric nonlinear analysis. This
material is used to model rubber, polymers, and elastomers.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATX82 MID
...
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MATX82 102
Field Contents
MUi Parameter µi
(Real)
ALFAi Parameter αi
(Real)
Di Parameter Di
(Real)
Comments
1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.
2. MATX82 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. NU is defined on the corresponding MAT1. For material without Poisson effect, a small NU
(for example, =1.E-10) should be defined.
with λi being the ith principal stretch, J = λ1 * λ2 * λ3 being the relative volume and
If NU = 0, then
Description
Defines the entity/set that needs to be activated in the multi-body system for the
subsequent simulation.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
or
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MBAC T ID MOTION 92
Field Contents
(Integer > 0)
(Integer > 0)
(Integer > 0)
Comments
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
CNFTYPE Contact Normal Force Type. Select from LINEAR and POISSON.
RADIUS Radius of the sphere geometry centered at the origin of the I marker.
Comments
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C OUL .1 .8
Field Contents
Default = POISSON
STVEL Stiction transition velocity. Defines the slip velocity at which the static
coefficient of friction MUSTAT is applied.
FTVEL Friction transition velocity. Defines the slip velocity at which the
dynamic coefficient of friction MUDYN is applied.
Comments
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
X1 Y1 X2 Y2 … … Xn Yn
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MBC RV 399
5.0 12.1
Field Contents
Default = blank
Comments
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MBC VC V 1 1 0 0
2 0 1
Field Contents
G3 This grid specifies the guess for the initial contact point on the first
curve.
V1 Specifies the sliding velocity of the contact point relative to the part on
which the curve is etched. V1 is positive when contact point is moving
toward the start of the curve and vice-versa.
G4 This grid specifies the guess for the initial contact point on the second
curve.
V2 Specifies the sliding velocity of the contact point relative to the part on
which the curve is etched. V2 is positive when contact point is moving
toward the start of the curve and vice-versa.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
G1 G2 G3 …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
ENDTYPEL Select from NATURAL, PARABOLIC, PERIODIC and CANTILEVER. See comment
1.
Default = NATURAL
LAMBDAL This parameter is only applicable for CANTILEVER type end condition. It should
be left blank for other end conditions.
A real valued parameter in the interval [0,1] that controls the left end
condition for CUBIC spline interpolation. A value of 0 implies NATURAL end
condition while a value of 1 implies PARABOLIC end condition.
ENDTYPER Select from: NATURAL, PARABOLIC, PERIODIC and CANTILEVER. See comment
1.
Default = NATURAL
LAMBDAR This parameter is only applicable for CANTILEVER type end condition. It should
be left blank for other end conditions.
A real valued parameter in the interval [0,1] that controls the left end
condition for CUBIC spline interpolation. A value of 0 implies NATURAL end
condition while a value of 1 implies PARABOLIC end condition.
G1, G2, G3, Ordered list of grid IDs defining the curve.
…
Comments
1. The deformable curve is generated using the CUBIC spline interpolation which requires
assumptions on the second derivative of the interpolating function at either end of the
curve. The keywords NATURAL, PARABOLIC, PERIODIC and CANTILEVER represent the
four standard assumptions defined as follows:
Note that λ =0.0 implies NATURAL (or free) end conditions and λ =1.0 implies PARABOLIC
end conditions.
Description
Defines the entity/set that needs to be deactivated in the multi-body system for the
subsequent simulation.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
or
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
(Integer > 0)
Comments
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
G1 G2 G3 G4 G5 G6 …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
217 218
Field Contents
Default = NATURAL
NSEGU, NSEGV Number of segments along the U and V coordinates used to discretize the
deformable surface for animation purposes.
G1, G2, … Row-wise list of nodes. The first NROW IDs form the first row; the second
NROW IDs form the second row, and so on. The list must contain a total of
NROW*NCOL grid IDs.
Comments
1. The deformable surface is generated using the CUBIC spline interpolation which requires
assumptions on the second derivative of the interpolating function at the end of the
surface. The keywords NATURAL, PARABOLIC and PERIODIC represent assumptions defined
as follows:
2. The MBDSRF element is not supported by the Force Imbalance method of static
equilibrium.
3. The MBDSRF element does not possess any inherent inertia, stiffness or damping.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
G4
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
201
Field Contents
F Force magnitude.
No default (Real)
(Integer > 0)
N1, N2, N3 Defines the direction of the force vector. At least one of the vector
components must be non-zero.
G4 Grid point identification number whose parent body hosts the coordinate
system with respect to which the force is defined. The force vector
changes direction with the orientation of the body. See comment 1.
Comments
1. If G4 is not specified, the force is defined with respect to the ground body (that is the
basic coordinate systems).
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
INT EID G4
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
AKIMA 41 201
Field Contents
CVID Set identification number of the MBCRV entry that gives the load vs.
independent variable measured in the coordinate system defined by
CID.
(Integer > 0)
(Integer > 0)
N1, N2, N3 Defines the direction of the force vector. At least one of the vector
components must be non-zero.
Default = AKIMA
EID Set identification number of the MBVAR for the independent variable
expression.
G4 Grid point identification number whose parent body hosts the coordinate
system with respect to which the force is defined. The force vector
changes direction with the orientation of the body. See comment 1.
Comments
1. If G4 is undefined, the force is defined with respect to the ground body (that is the basic
coordinate systems).
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
G4
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
201
Field Contents
EID Expression identification number of the MBVAR entry that gives the load
measured in the coordinate system defined by CID.
(Integer > 0)
N1, N2, N3 Defines the direction of the force vector. At least one of the vector
components must be non-zero.
G4 Grid point identification number whose parent body hosts the coordinate
system with respect to which the force is defined. The force vector
changes direction with the orientation of the body. See comment 1.
Comments
1. If G4 is undefined, the force is defined with respect to the ground body (that is the basic
coordinate systems).
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
Comments
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
M Moment magnitude.
No default (Real)
(Integer > 0)
N1,N2,N3 Defines the direction of the force vector. At least one of the vector
components must be non-zero.
Comments
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
INT EID
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
AKIMA 42
Field Contents
CVID Set identification number of the MBCRV entry that gives the load vs.
independent variable measured in the coordinate system defined by
CID.
(Integer > 0)
(Integer > 0)
N1,N2,N3 Defines the direction of the force vector. At least one of the vector
components must be non-zero.
Default = AKIMA
EID Set identification number of the MBVAR for the independent variable
expression.
Comments
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
EID Expression identification number of the MBVAR entry that gives the load
measured in the coordinate system defined by CID.
(Integer > 0)
N1, N2, N3 Defines the direction of the force vector. At least one of the vector
components must be non-zero.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
G1 G2 G3 G4 G5
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MBPC RV 1 1 0 1 5
Field Contents
CRVPTS Curve points. Specify 1 if the curve must pass through the nodes, and 0 if
the B-spline curve does not pass through the nodes, but stays close.
Comments
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MBPTC V 1 21 2 25 0
Field Contents
G3 This grid specifies the guess for the initial contact point on the curve.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MBPTDC V 1 21 2
Field Contents
Comments
1. The deformable curve is generated using the CUBIC spline interpolation which requires
assumptions on the second derivative of the interpolating function at either end of the
curve. The keywords NATURAL, PARABOLIC, PERIODIC and CANTILEVER represent the
four standard assumptions defined as follows:
2. The MBPTDCV element is not supported by the Force Imbalance method of static
equilibrium.
3. In most cases, the interpolation produces a smooth curve but in some cases, it produces
a curve that wiggles too much. In those cases, the TENSION parameter may be specified
to smooth out the wiggles in the curve. A TENSION value of unity is a good first guess.
After that, higher values of TENSION may be tried if necessary.
4. The deformable element itself does not possess any inherent inertia, stiffness or damping
properties. You must include other modeling elements to capture those effects.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MBPTDSF 1 21 2
Field Contents
Comments
1. The deformable curve is generated using the CUBIC spline interpolation which requires
assumptions on the second derivative of the interpolating function at either end of the
curve. The keywords NATURAL, PARABOLIC, PERIODIC and CANTILEVER represent the four
standard assumptions defined as follows:
2. The MBPTDCV element is not supported by the Force Imbalance method of static
equilibrium.
3. In most cases, the interpolation produces a smooth curve but in some cases, it produces
a curve that wiggles too much. In those cases, the UTENSION and VTENSION parameters
may be specified to smooth out the wiggles in the curve. A value of unity is a good first
guess. After that, higher values may be tried if necessary.
4. The deformable surface itself does not possess any inherent inertia, stiffness or damping
properties. You must include other modeling elements to capture those effects. For
example, you may use a deformable surface in conjunction with a flexible body to simulate
contact with a rigid body.
Description
Defines a multi-body as a combination of request sets defined via MBREQE and MBREQM.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MBREQ SID R1 R2 R3 R4 R5 R6 R7
R8 R9 …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MBREQ 3 31 34 35
Field Contents
(Integer > 0)
(Integer > 0)
Comments
2. Request sets must be selected in the Subcase Information section (REQUEST = SID) if
they are to be applied.
Description
Defines a multi-body solver output request to output the results of a set of expressions.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MBREQE 235 10 20 30 40
Field Contents
(Integer > 0)
(Integer > 0)
E1 ID of MBVAR.
(Integer > 0)
4. Request ID must be unique with respect to all other MBREQM and MBREQE cards.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
No default
Comments
1. The output request is usually of IMARK with respect to JMARK resolved in RMARK.
2. If the JMARK is not specified, the results are with respect to global frame.
3. If the RMARK is not specified, the results are resolved in the global frame.
5. Request ID must be unique with respect to all other MBREQM and MBREQE cards.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MBSEQ 9 99 12 43
Field Contents
(Integer > 0)
Comments
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MBSFRC SID G1 G2 F
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
F Value of load
(Real)
1. MBSFRC applies a translational action-reaction force along the line of action defined by
the line segment connecting G1 and G2.
2. The action force is applied to G1 and the reaction force is applied to G2.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
CVID Set identification number of the MBCRV entry that gives the load vs.
independent variable measured in the coordinate system defined by
CID.
(Integer > 0)
Default = AKIMA
EID Set identification number of the MBVAR for the independent variable
expression.
Comments
1. MBSFRCC applies a translational action-reaction force along the line of action defined by
the line segment connecting G1 and G2.
2. The action force is applied to G1 and the reaction force is applied to G2.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
1. MBSFRCE applies a translational action-reaction force along the line of action defined by
the line segment connecting G1 and G2.
2. The action force is applied to G1 and the reaction force is applied to G2.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
or
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 2
3 4 TRUE
Example 3
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MBSIM 91 STAT
Field Contents
(Integer > 0)
No default
No default
No default
Default = DSTIFF
VTOLFAC A factor that multiplies DTOL to yield the error tolerance for velocity
states.
DCRMNIT The minimum number of iterations that the corrector is allowed to take
before it checks for corrector divergence.
DVCTRL A logical flag that controls whether the velocity states are checked
for local integration error at each step.
DEVLXP The number of integration steps after which the evaluation pattern
defined by DJCEVL is ignored, and the default evaluation pattern is to
be used.
Default = MKM
Comments
1. The continuation card is used to distinguish between either a TRANS or STAT simulation
type. The reader will look for appropriate options based on the type of simulation
specified.
2. When the simulation type is static (STAT), the solver will perform a static simulation if the
termination type, termination time/duration, step type, delta/nsteps are not provided. A
quasi-static simulation will be performed if that information is provided.
3. If the output step type is DELTA, then the next argument is expected to be a positive
real value, and it is the output step time during the simulation run. If the step type is
NSTEPS, then the next argument is expected to be a positive integer value which will be
the number of output steps during the simulation. If the step type is PRINCR, then the
next argument is expected to be a positive integer value which will be print increment.
Solver will output at every intermediate print increment value. If the PRINCR is set to 1,
then the solver will output intermediate results at every integrator step.
4. ITYPE, DTOL, H0, HMAX, HMIN, VTOLFAC, MAXODR, DAEIDX, DCNTOL, DCRMXIT,
DCRMNIT, DVCTRL, DJACEVL, and DEVLEXP are only applicable for TRANS simulation types.
The 2nd continuation card (DAEIDX, DCNTOL, DCRMXIT, DCRMNIT, DVCTRL, DJACEVL,
5. KETOL, DQTOL, NITER are only applicable for STATIC simulation type.
6. RESTOL, FITOL, NITER, TLIMIT, ALIMIT are applicable for the force imbalance static
method used for quasi-static solutions.
7. Static solver type is used to select from the two static solution types currently offered.
FIM represents the Force Imbalance Method and MKM represents the Maximum Kinetic
Energy Attrition Method.
8. Note that when quasi-static simulation is requested (STAT with termination time), then
the STTYPE option is ignored and the quasi-static simulation will be performed using the
force imbalance method.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
Comments
Description
Defines a constant scalar moment on two gird points along the specified vector.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
T Value of moment.
(Real)
(Integer > 0)
Vx X component of vector V.
Vy Y component of vector V.
Vz Z component of vector V.
Comments
1. MBSMNT applies a scalar action-reaction moment on G1 and G2 along the vector defined
by Vx, Vy, and Vz.
2. The action moment is applied to G1 and the reaction moment is applied to G2.
Description
Defines a curve scalar moment on two grid points along the specified vector.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
INT EID
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
AKIMA 1
Field Contents
CVID Set identification number of the MBCRV entry that gives the load vs.
independent variable measured in the coordinate system defined by CID.
(Integer > 0)
(Integer > 0)
Vx X component of vector V.
Vy Y component of vector V.
Vz Z component of vector V.
Default = AKIMA
EID Set identification number of the MBVAR for the independent variable
expression.
Comments
1. MBSCMTC applies a scalar action-reaction moment on G1 and G2 along the vector defined
by Vx, Vy, and Vz.
2. The action moment is applied to G1 and the reaction moment is applied to G2.
Description
Defines an expression scalar moment on two grid points along the specified vector
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
Vx X component of Vector V.
Vy Y component of Vector V.
Vz Z component of Vector V.
Comments
1. MBSMNTE applies a scalar action-reaction moment on G1 and G2 along the vector defined
by Vx, Vy, and Vz.
2. The action moment is applied to G1 and the reaction moment is applied to G2.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
00,1.0,0.5,0.000)
Field Contents
(Integer > 0)
EXPR Character string expression. The expression can spawn multiple lines. The
continuation lines will start from the second column. Refer to Function
Expressions.
Comments
Description
METADATA indicates the beginning of metadata that is to be passed to the metadata output
file. Metadata between the METADATA and ENDMETADATA commands is passed to the
<filename>_metadata.xml file.
Example
METADATA
This line will be passed to the filename_metadata.xml file.
So will this information: Color=blue
ENDMETADATA
Comments
1. There can be two sections of metadata; one in the Solution Control section and one in
the Bulk Data section.
2. Metadata can be used to pass information from the pre-processor seamlessly through the
solver to a post-processing program.
Description
Defines the parameters and damp shell elements for a fluid volume.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
RMAX
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
ZFS Location of the free surface on the z-axis of the CID coordinate system.
WSURF1 Set identification number of a SURF or SET bulk data entry. This list
identifies shell elements that are damp on only one side of the element or
an exterior face of solid elements (see SURF,ELFACE).
WSURF2 Set identification number of a SURF or SET bulk data entry. This list
identifies shell elements that are damp on both sides of the element.
N - no symmetry
S - symmetric
A - antisymmetric
Default = N (Character = N, S, A)
N - no symmetry
S - symmetric
A - antisymmetric
Default = N (Character = N, S, A)
Comments
1. An MFLUID entry must be selected by the MFLUID = SID command in the Subcase
Information section.
2. More than one MFLUID entry may be specified to define multiple fluid volumes.
3. Either WSURF1 or WSURF2, or both must be specified and non-zero. In other words,
WSURF1 and WSURF2 cannot be both blank or zero.
4. An element with all its vertices located on or above the free surface will be ignored in the
fluid volume’s mass calculation. An element vertex is considered to be located on the free
5. By default for elements referenced by WSURF1, the damp side of the element is assumed
to be on the same side as the element’s normal. If this condition is not true for a given
element, then the standard SURF entry format with “ELFACE” (not the alternative SET
format) must be used to redefine the normal into the fluid by setting NORMAL=1 on SURF
entry.
6. ELIST is an alternative to SET and SURF, but ELIST is intended only to provide
compatibility with Nastran decks and therefore is considered deprecated. Also,
The SURF and SET entries may not be combined with ELIST entries to define damp
elements.
ELIST entries are internally converted to SET entries. If ELIST is used, then all MFLUID
entries must reference ELIST entries. This means that if an MFLUID references a
missing ELIST,25, then the program will not search for a SET,25.
7. Planes of symmetry may be defined with PLANE1 and PLANE2.
Description
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABLU8
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
"T" TEMP1
"T" TEMP2
-etc.-
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
T 20.0
PLUS
T 100.0
PLUS
T 300.0
Field Contents
0 – elasto-plastic material
1 – elastic material with damage
YPRS Initial yield pressure for the thickness direction of the gasket material.
Applies only to elasto-plastic behavior (BEHAV=0).
For the groups of data starting with “PLUS”, default is the corresponding
field value defined at the first line.
For the groups of data starting with “PLUS”, default is the corresponding
field value defined at the first line.
GPL Transverse shear modulus of the gasket material (the unit of measure
depends on the value of the GPLUNIT field).
For the groups of data starting with “PLUS”, default is the corresponding
field value defined at the first line.
For the groups of data starting with “PLUS”, default is the corresponding
field value defined at the first line.
TABLD Identifier of a TABLES1 table providing loading path of the gasket material
(pressure vs. closure).
TEMPj Temperature for the group of data above. See comment 11.
No default (Real)
PLUS Keyword indicating that the following is a group of data defined at another
temperature. See comment 12.
Comments
1. The material identification number must be unique for all MAT1, MAT2, MAT3, MAT8,
MAT9 and MGASK entries.
2. MGASK mainly defines nonlinear properties in the thickness direction for gasket-like
materials under compression. MGASK has anisotropy only in the thickness direction, which
is called normal anisotropy. For linear analysis, the thickness-direction modulus (stress
per unit displacement) is defined by the slope of the first segment of the loading
pressure-closure curve TABLD.
3. MGASK also defines the transverse shear and thickness-direction tension behaviors with
linear properties. (The membrane properties of the gasket are defined by a MAT1,
referenced from the PGASK property.)
4. The thickness direction of gasket material is the principal direction (local 3-direction) in
3D solids.
5. If EPL is defined as a tension stabilization coefficient (EPLTYPE = 0), the tensile modulus
will be calculated as the initial slope of the first segment of the loading curve TABLD
multiplied by EPL. If EPL is defined as a direct tensile modulus (EPLTYPE = 1), its unit of
measure is stress per unit displacement. If EPL is zero, a small tensile modulus will be used
automatically for stabilization (no matter EPLTYPE is 0 or 1).
6. All the data points in tables TABLD and TABLUi are specified in the first quadrant. Points
The initial yield pressure should match a point in table TABLD. If the initial yield
pressure is not specified, it will be determined automatically by finding the first point on
the TABLD curve where the slope changes by more than 10%.
The loading path starts from the origin to initial yield pressure (nonlinear elastic range)
and continues with strain hardening slope into the plastic region.
All unloading/reloading paths must start with zero pressure and positive closure
distance, and end at the loading path in the plastic region. Subsequent unloading/
reloading curves must start with larger closure distances (when pressure is zero) and
end with larger closure distances than previous unloading/reloading curves.
8. For elastic material with damage (BEHAV = 1),
All loading and unloading/reloading curves must start at the origin of the coordinate
system (0, 0).
All unloading/reloading paths must end at the loading path. Subsequent unloading/
reloading curves must end with larger closure distances than previous unloading/
reloading curves.
9. Unloading/reloading behavior at undefined paths will be interpolated between two
adjacent unloading/reloading paths.
10. For closures larger than the last user-specified closure, the pressure-closure relationship
is calculated as follows:
For elasto-plastic material (BEHAV = 0), it follows the last segment of the furthest
unloading/reloading curve. This behavior is fully elastic and represents crushed gasket.
For elastic material with damage (BEHAV = 1), it follows last slope computed from the
user-specified data.
11. If temperature dependency is defined, TEMPj should be provided in ascending order and
the loading path (and unloading/reloading paths, if required) should be provided for each
Example
12. BEHAV, EPLTYPE and GPLUNIT fields after any “PLUS” field should remain blank because
their values are always the same as those of the first-group data.
Description
Defines a multi-body as a linear combination of load sets defined via GRAV, MBFRC, MBFRCC,
MBFRCE, MBMNT, MBMNTC, MBMNTE, MBSFRC, MBSFRCC, MBSFRCE, MBSMNT, MBSMNTC, and
MBSMNTE.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MLOAD SID L1 L2 L3 L4 L5 L6 L7
L8 L9 …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MLOAD 3 31 34 35
Field Contents
(Integer > 0)
Li Load set identification numbers defined via entry typed enumerated above.
(Integer > 0)
Comments
2. Load sets must be selected in the Subcase Information section (MLOAD = SID) if they are
to be applied.
Description
Defines a static moment at a grid point by specifying a vector. It can also be used to define
the EXCITEID field (Amplitude “A”) of dynamic loads in RLOAD1, RLOAD2, TLOAD1 and TLOAD2
bulk data entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MOMENT SID G C ID M N1 N2 N3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
M Scale factor.
(Real)
Comments
3. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on MOMENT entries in the model. A fully qualified reference
(“PartName.number”) is similar to the format of a numeric reference. “PartName” is the
name of the part that contains the referenced local entry (part names are defined on the
BEGIN Bulk Data Entry in the model). “number” is the identification number of a
referenced local entry in the part “PartName”. See Parts and Instances in the User’s
Guide for detailed information on the use of fully qualified references.
Description
Defines a static moment by specification of a value and two grid points, which determine the
direction. It can also be used to define the EXCITEID field (Amplitude “A”) of dynamic loads in
RLOAD1, RLOAD2, TLOAD1 and TLOAD2 bulk data entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MOMENT1 SID G M G1 G2
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MOMENT1 6 13 -2.93 16 13
Field Contents
(Integer > 0)
(Integer > 0)
M Value of moment.
(Real)
Description
Defines a static moment by specification of a value and four grid points, which determine the
direction. It can also be used to define the EXCITEID field (Amplitude “A”) of dynamic loads in
RLOAD1, RLOAD2, TLOAD1 and TLOAD2 bulk data entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MOMENT2 SID G M G1 G2 G3 G4
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MOMENT2 6 13 -2.93 16 13 18 19
Field Contents
(Integer > 0)
(Integer > 0)
M Value of moment.
(Real)
where, is a unit vector parallel to a vector calculated from the cross product of the
vectors from G1 to G2 and G3 to G4.
Description
Defines a multi-body as a combination of motion sets defined via MOTNJ, MOTNJC, MOTNJE,
MOTNG, MOTNGC, and MOTNGE.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MOTION SID M1 M2 M3 M4 M5 M6 M7
M8 M9 …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MOTION 3 31 34 35
Field Contents
(Integer > 0)
(Integer > 0)
Comments
2. Motion sets must be selected in the Subcase Information section (MOTION=SID) if they
are to be applied.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MOTNG SID G1 C1 G2 D D0 V0
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
D Scale factor.
Comments
1. If G1 and G2 are defined, the motion is a relative motion between the two grid points; if
G2 is blank, absolute motion of G1 is defined.
2. The types and directions of motion for the component numbers are given in the following
table.
1, 2, and 3 Displacement X, Y, Z
4, 5, and 6 Rotation X, Y, Z
The component numbers and directions of motion are in the format: 1->X, 2->Y and 3->Z
for Displacement and this format is followed for all the types in the table.
MOTNGC – Grid Point Motion vs. Time Curve for Multi-body Solution Sequence
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
D0 V0
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
CVID Set identification number of the MBCRV entry that gives the motion vs.
time.
(Integer > 0)
Default = AKIMA
EID Set identification number of the MBVAR for the independent variable
expression.
Comments
1. If G1 and G2 are defined, the motion is a relative motion between the two grid points; if
G2 is blank, absolute motion of G1 is defined.
2. The types and directions of motion for the component numbers are given in the following
table.
1, 2, and 3 Displacement X, Y, Z
4, 5, and 6 Rotation X, Y, Z
The component numbers and directions of motion are in the format: 1->X, 2->Y and 3->Z
for Displacement and this format is followed for all the types in the table.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MOTNGE 3 345 3 4
Field Contents
(Integer > 0)
(Integer > 0)
EID Expression identification number of the MBVAR entry that gives the motion
vs. time.
(Integer > 0)
Comments
2. The types and directions of motion for the component numbers are given in the following
table.
1, 2, and 3 Displacement X, Y, Z
4, 5, and 6 Rotation X, Y, Z
The component numbers and directions of motion are in the format: 1->X, 2->Y and 3->Z
for Displacement and this format is followed for all the types in the table.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
D Value of motion.
(Real)
DTYPE Motion data type (DIS or VEL or ACC), blank means displacement
motion.
Comments
1. Joint motion can only be applied to cylindrical joints (MTYPE = TRANS or ROT), revolute
joints (MTYPE = ROT), and translational joints (MTYPE = TRANS).
MOTNJC – Joint Motion vs. Time Curve for Multi-body Solution Sequence
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
D0 V0
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
CVID Set identification number of the MBCRV entry that gives the motion vs.
time.
(Integer > 0)
Default = AKIMA
EID Set identification number of the MBVAR for the independent variable
expression.
DTYPE Motion data type (DIS or VEL or ACC), blank means displacement motion.
Comments
1. Joint motion can only be applied to cylindrical joints (MTYPE = TRANS or ROT), revolute
joints (MTYPE = ROT), and translational joints (MTYPE = TRANS).
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MOTNJE 3 345 3 1
Field Contents
(Integer > 0)
(Integer > 0)
EID Expression identification number of the MBVAR entry that gives the
motion vs. time. If blank or zero, a constant motion of D is applied.
DTYPE Motion data type (DIS or VEL or ACC), blank means displacement
motion.
Comments
1. Joint motion can only be applied to cylindrical joints (MTYPE = TRANS or ROT), revolute
joints (MTYPE = ROT), and translational joints (MTYPE = TRANS).
Description
The MPC bulk data entry defines a multipoint constraint equation of the form.
Aj u j 0
j
Where,
Aj
is the coefficient that can be used to define the relationship between the degrees of
freedom associated with grid points (or a scalar point) in the model.
uj
is the degree of freedom associated with a grid point (or a scalar point).
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
1 4 -2.91
Field Contents
(Integer > 0)
(Integer zero or blank for scalar points, or any one of the digits 1-6 for grid
points)
A Coefficient that can be used to define the relationship between the degrees of
freedom associated with grid points (or a scalar point).
Comments
2. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).
3. The component refers to the coordinate system referenced by the grid point.
4. Illustrative Example:
Figure 1 can be used to illustrate an MPC application. Independent grid points G1 and G2
of a 2D quad element are connected with the help of an MPC; where Gd is the dependent
grid point. The objective of this example is to force the displacement of Gd to be equal to
the sum of the displacements of grid points G1 and G2 in the X (1) direction using an
MPC.
A1u1 A2 u2 A3 u3 0
ud u1 u2
Where,
ud
is the displacement of grid point Gd in X direction
u1
is the displacement of grid point G1 in X direction
u2
is the displacement of grid point G2 in X direction
5. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on MPC entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry
in the model). “number” is the identification number of a referenced local entry in the part
“PartName”. See Parts and Instances in the User’s Guide for detailed information on the
use of fully qualified references.
Description
Defines a multipoint constraint set as a union of multipoint constraint sets defined via MPC
entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
S8 S9 etc.
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
Comments
1. Multipoint constraint sets must be selected with the Subcase Information command
MPC=SID.
2. The Sj field should not reference the identification number of a multipoint constraint set
3. MPCADD entries take precedence over MPC entries. If both have the same SID, only the
MPCADD entry will be used.
4. If all Si are non-existent, the solver will exit with an error termination.
5. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on MPCADD entries in the model. A fully qualified reference
(“PartName.number”) is similar to the format of a numeric reference. “PartName” is the
name of the part that contains the referenced local entry (part names are defined on the
BEGIN Bulk Data Entry in the model). “number” is the identification number of a
referenced local entry in the part “PartName”. See Parts and Instances in the User’s
Guide for detailed information on the use of fully qualified references.
Description
Defines a loading condition for nonlinear problems as a linear combination of load sets defined
via NLOAD1.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NLOAD SID S S1 L1 S2 L2 S3 L3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
-2.0 201
Field Contents
S Scale factor.
No default (Real)
Si Scale factors.
No default (Real)
Comments
1. Dynamic load sets must be selected in the I/O Options or Subcase Information sections
with NLOAD=SID.
5. An NLOAD entry may not reference a set identification number defined by another NLOAD
entry.
Description
Defines a time-dependent load or enforced motion for use in geometric nonlinear analysis.
f(t) = A * C * F(t/B)
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TSTART TEND
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NLOAD1 5 7 LOAD 13
Field Contents
(Integer > 0)
EXCITEID SID number of DAREA, SPCD or static load set that defines A. See
comments 2 and 3.
(Integer > 0)
(Integer > 0)
TYPE Defines the type of the dynamic excitation. See comments 2 and 3.
TID Identification number of TABLEDi entry defining the load history F(t).
(Integer > 0)
Comments
1. Time-dependent load sets must be selected with the Subcase Information command
NLOAD = SID. It can only be selected in geometric nonlinear analysis subcases which are
defined by an ANALYSIS = NLGEOM, IMPDYN or EXPDYN subcase entry.
2. The type of the dynamic excitation is specified by TYPE (field 5) according to the
following table:
(Default)
3. TYPE (field 5) also determines the manner in which EXCITEID (field 3) is used by the
program as described below.
Excitation specified by TYPE is applied load. The EXCITEID may reference DAREA, or
(and) static load set entries. If EXCITEID references both DAREA and static load set,
the two loads will be super-imposed.
Excitation specified by TYPE is enforced motion. The EXCITEID must reference SPCD
entries.
4. TSTART and TEND are only considered for enforced displacement, velocity, and
acceleration. The continuation line is optional.
Description
The NLPARM bulk data entry defines parameters for nonlinear static analysis or heat transfer
analysis solution control.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NLPARM 99 5
Field Contents
(Integer > 0)
(Integer > 0)
MAXITER Limit on number of implicit iterations for each load increment. If reached, the
solution is terminated (ANALYSIS = NLSTAT and ANALYSIS=NLHEAT).
Comments
1. The NLPARM bulk data entry is selected by the Subcase Information command
NLPARM=option. Each subcase for which nonlinear analysis is desired requires an NLPARM
command.
2. The solution method for quasi-static nonlinear analysis (ANALYSIS = NLSTAT) is full
Newton. The stiffness matrix is updated at each iteration. NINC > 0 represents the
number of equal subdivisions that the total load in a given subcase will be divided into. If
NINC is blank, the entire load for a given subcase is applied at once. The Newton method
will be applied to consecutive load levels until the final load is reached.
3. Additional control for geometric nonlinear implicit static solution schemes (ANALYSIS =
NLGEOM) can be defined using the NLPARMX bulk data entry. Defaults will be used if
NLPARMX is not present.
4. The solution method for geometric nonlinear implicit analysis (ANALYSIS = NLGEOM) is
modified or Quasi-Newton. The frequency of stiffness matrix updates is controlled by
KSTEP. For highly nonlinear problems, it is recommended to reduce KSTEP for better
performance. KSTEP = 1 means full Newton.
If the loading is defined using NLOAD, the termination time TTERM must defined by a
TTERM subcase entry. The initial implicit time step is TTERMS/NINC with TTERMS =
TTERM – T0. All subsequent time steps will be determined automatically. In a simulation
with multiple nonlinear subcases, T0 is the end time of the previous load step. If there is
only a single nonlinear subcase, T0 = 0.0.
If the loading is defined using LOAD, TTERM is not mandatory. These loads are treated as
linear ramp-up. If TTERM is defined, the load ramps up from the end time of the previous
subcase to TTERM. If TTERM is absent, it will be determined from the subcase sequence
such that the duration of each subcase TTERMS = 1.0. In this case, the initial time step
is 1.0/NINC.
5. For Nastran compatibility, NLPCI is imported if present. Only the fields ID, TYPE are
interpreted. With NLPCI present, the default for NLPARMX, SACC will be reset to RIKS.
TYPE will be translated into CTYPE; all other entries are set to default. A warning will be
issued. NLPCI and NLPARMX cannot be used simultaneously. It is recommended to remove
NLPCI and use NLPARMX with the appropriate definitions.
6. For more information about nonlinear quasi-static analysis, see the Nonlinear Quasi-static
Analysis section.
7. For more information about geometric nonlinear analysis, see the Geometric Nonlinear
Analysis section.
8. For more information about nonlinear steady-state heat transfer analysis, see the
Nonlinear Steady-State Heat Transfer Analysis section.
NLPARMX – Optional Parameters for Geometric Nonlinear Implicit Static Analysis Control
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NLPARM 99
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NLPARM 99
NLPARMX 99 0.1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NLPARM 99 3 PW
NLPARMX 99 0.1
Field Contents
DTA Output time step for animation files. If zero, no output (See comment 3).
DTTH Output time step for time history files. If zero, no output (See comment 3).
NPRINT Print every NPRINT iterations. If negative, to .out and standard output; if
positive, only to .out file.
Default = -1 (Integer)
RIKS – Riks method for post-buckling analysis (only with SOLV = NEWT).
DTMIN Minimum implicit time step. If DTMIN is reached, simulation will be terminated
(See comment 3).
DTMAX Maximum implicit time step from which time step is set constant (See
comment 3).
FIXTID Identification number of a TABLEDi entry. The x values of the table define
fixed time points that the automatic time step control will adhere to.
(Integer > 0)
KINER Inertia Stiffness for handling models that are not sufficiently constrained.
May require definition of DTSCQ (See comment 4).
DTSCQ Scale factor for inertia stiffness matrix used in quasi-static analysis (KINER =
ON, See comment 4).
SPRBK Perform spring back analysis. Equilibrium is reached when the internal forces
are less or equal to the tolerances given on NLPARM.
ITW If the solution of a time step converges within ITW iterations the next time
step will be increased by a factor controlled by DTSCI.
DTSCI Maximum scale factor for increasing the time step (TSCTRL = ARC, RIKS).
Scale factor for TSCTRL = SIMP.
LDTN Maximum number of iterations before resetting and decreasing the time step
by a factor of DTSCD.
(Integer > 0)
DTSCD Scale factor for decreasing the time step (TSCTRL = ARC, SIMP, RIKS).
WSCAL Scale factor for controlling the loading contribution in the constraint
equation.
Comments
1. The NLPARMX bulk data entry is selected by the Subcase Information command NLPARM =
option. There must also be an NLPARM bulk data entry with the same ID. It is only used
in geometric nonlinear implicit static analysis (ANALYSIS = NLGEOM); it is ignored in other
analyses.
2. The solution method for geometric nonlinear implicit analysis is selected by SOLV. The
frequency of stiffness matrix updates is controlled by KSTEP. For highly nonlinear
problems, it is recommended to reduce KSTEP for better performance. KSTEP = 1 means
full Newton.
3. If the loading is defined using NLOAD, the termination time TTERM must be defined by a
TTERM subcase entry. The initial implicit time step is DTINI = TTERMS/NINC with TTERMS
= TTERM – T0. All subsequent time steps will be determined automatically. In a
simulation with multiple nonlinear subcases, T0 is the end time of the previous load step.
If there is only a single nonlinear subcase, T0 = 0.0.
If the loading is defined using LOAD, TTERM is not mandatory. These loads are treated as
linear ramp-up. If TTERM is defined, the load ramps up from the end time of the previous
subcase to TTERM. If TTERM is absent, it will be determined from the subcase sequence
such that the duration of each subcase TTERMS = 1.0. In this case, the initial time step
is DTINI = 1.0/NINC.
4. For models that are not sufficiently constrained, inertia stiffness can be used to overcome
a singular stiffness matrix. The inertia stiffness [K]inertia = 1/(DTSCQ*dt)^2[M] is added
to the stiffness matrix [K]. Care needs to be taken in the selection of DTSCQ. Too large
of an added mass may lead to wrong results.
5. Linear static and normal modes analysis within geometric nonlinear analysis (ILIN = LIN,
LINC) are provided for debugging purposes. They may help detecting modeling errors. All
materials are linearized, and linear displacements are assumed as well. The load is taken
at the termination time. To run normal modes analysis, a METHOD subcase entry that
refers to an EIGL bulk data entry must be provided.
Where, u is displacement, j the scale factor (WSCAL) , l a load factor, and r the arc-
length.
Where, is the displacement, due to a unit load factor, and is the displacement
increment from the conventional Newton type method. The meaning of u, j, l, and r are
the same as those above.
7. For Nastran compatibility, NLPCI is imported if present. Only the fields ID, TYPE are
interpreted. With NLPCI present, the default for TSCTRL will be reset to RIKS. TYPE will
be translated into CTYP; all other entries are set to default. A warning will be issued.
NLPCI and NLPARMX cannot be used simultaneously. It is recommended to remove NLPCI
and use NLPARMX with the appropriate definitions
8. For more information about geometric nonlinear analysis, see the Geometric Nonlinear
Analysis section.
NLPCI – Implicit Time Step Control for Riks Type Arc-Length Method
Description
Define implicit automatic time step control with Riks type arc-length method.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NLPC I ID TYPE
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NLPC I 5 C RIS
Field Contents
Comments
1. The NLPCI bulk data entry is selected by the Subcase Information command NLPARM =
option. There must also be an NLPARM entry with the same ID. It is only used in
geometric nonlinear (quasi-)static analysis (ANALYSIS = NLGEOM).
2. NLPCI is implemented for Nastran compatibility and imported if present. Only the fields ID,
TYPE are interpreted. With NLPCI present, the default for NLPARMX, SACC will be reset
to RIKS. TYPE will be translated into CTYPE; all other entries are set to default. A
warning will be issued. NLPCI and NLPARMX cannot be used simultaneously. It is
Description
Defines a nonlinear radial (circular) gap for direct transient response analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NOLIN1 21 3 4 XY 3 10 6 1.6
Field Contents
Comments
1. Nonlinear radial gap must be selected by the Subcase Information data selector
NONLINEAR.
3. The NLRGAP is not an element, but a nonlinear load similar to the NOLIN1, NOLIN2, NOLIN3
and NOLIN4 entries. It computes the relative displacements of GA and GB in the selected
plane and applies appropriate nonlinear loads to simulate the radial contact.
4. The degrees of freedom in the XY, YZ and ZX planes (depending on the PLANE defined) of
GA and GB must be members of the solution set. This means that they must not be
dependent degrees of freedom and the must not have SPCs applied to them. If RADIUS is
> 0.0, then the in-plane rotation degree of freedom must also be in the solution set.
6. The XY, YZ and ZX planes are relative to the displacement coordinate systems of GA and
GB.
7. GA and GB must both be grid points, they must both be coincident, and they must have
parallel displacement coordinate systems. If any of these conditions are not met, an error
termination will occur.
8. The shaft radius is used only for the computation of friction induced torque.
11. If the integer entered in the TABK field is positive, it is the ID of a TABLED1 entry defining
time vs. gap stiffness. If the integer is negative, then the absolute value of the integer is
the ID of a TABLED1 entry defining gap penetration vs. gap force.
12. Forces due to TABK and TABU at GA and GB are only present when the gap is closed. A
moment is applied only when the gap is closed and RADIUS > 0.0.
Description
Function of displacement:
Function of velocity:
where, and are the displacement and velocity at point GJ in the direction of CJ.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NOLIN1 21 3 4 2.1 3 10 6
Field Contents
S Scale factor.
No default (Real)
Comments
1. Nonlinear loads must be selected by the Subcase Information data selector NONLINEAR.
4. Nonlinear loads as a function of velocity are denoted by components ten greater than the
actual component number; that is the component 11 indicates velocity in the 1
component direction. The velocity is determined by:
where, is the time step interval and is the displacement of GJ-CJ for the
previous time step.
5. The time step algorithm in transient solution sequences may loose unconditional stability
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NOLIN2 SID GI CI S GJ CJ GK CK
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NOLIN2 14 2 1 2.9 2 1 2
Field Contents
S Scale factor.
No default (Real)
Displacement Velocity
Type
Comments
1. Nonlinear loads must be selected by the Subcase Information data selector NONLINEAR.
where, is the time step interval and is the displacement of GJ-CJ or GK-CK for the
previous time step.
6. The time step algorithm in transient solution sequences may loose unconditional stability
when this load entry is used. In most practical cases, the time step size chosen to reach
a certain accuracy is below the stability limit. It is recommended to decrease the time
step if results diverge.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NOLIN3 SID GI CI S GJ CJ A
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
S Scale factor.
No default (Real)
No default (Real)
Comments
1. Nonlinear loads must be selected by the Subcase Information data selector NONLINEAR.
where, is the time step interval and is the displacement of GJ-CJ for the
previous time step.
6. The time step algorithm in transient solution sequences may loose unconditional stability
when this load entry is used. In most practical cases, the time step size chosen to reach
a certain accuracy is below the stability limit. It is recommended to decrease the time
step if results diverge.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NOLIN4 SID GI CI S GJ CJ A
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
S Scale factor.
No default (Real)
No default (Real)
Comments
1. Nonlinear loads must be selected by the Subcase Information data selector NONLINEAR.
where, is the time step interval and is the displacement of GJ-CJ for the
previous time step.
6. The time step algorithm in transient solution sequences may loose unconditional stability
when this load entry is used. In most practical cases, the time step size chosen to reach
a certain accuracy is below the stability limit. It is recommended to decrease the time
step if results diverge.
Description
Defines non-structural mass per unit area or per unit length for a list of elements or
properties.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
TYPE This can be one of the properties PSHELL, PCOMP, PBAR, PBARL, PBEAM,
PBEAML, PROD, CONROD, PSHEAR, or PTUBE, in which case the list of IDs will
refer to properties of the stated type, or it can be ELEMENT, in which case the
list is of individual element IDs of elements that can have NSM.
No default (Real)
Comments
1. Refer to the User's Guide section on Non-structural Mass for more information on the use
of this card.
2. Non-structural mass in this format must be selected by the NSM Subcase Information
selector.
NSM1 – Non-structural Mass per Unit Area or per Unit Length, Alternate Form 1
Description
Defines non-structural mass per unit area or per unit length for a list of elements or
properties.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ID ID ID -etc.-
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
TYPE This can be one of the properties PSHELL, PCOMP, PBAR, PBARL, PBEAM, PBEAML,
PROD, CONROD, PSHEAR, or PTUBE, in which case the list of IDs will refer to
properties of the stated type, or it can be ELEMENT, in which case the list is of
individual element IDs of elements that can have NSM.
No default (Real)
Comments
1. Refer to the User's Guide section on Non-structural Mass for more information on the use
of this card.
2. Non-structural mass in this format must be selected by the NSM Subcase Information
selector.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NSMADD SID S1 S2 S3 S4 S5 S6 S7
S8 S9 S10 -etc.-
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
S# Identification number of nonstructural mass sets defined via NSM, NSM1, NSML,
and NSML1 entries.
VALUE A lumped mass value to be distributed over all the listed elements and elements
referencing listed properties.
No default (Real)
Comments
1. Refer to the User's Guide section on Non-structural Mass for more information on the use
of this card.
2. Non-structural mass in this format must be selected by the NSM Subcase Information
selector.
4. NSMADD entries take precedence over NSM, NSML, NSM1 or NSML1 entries. If both have
the same SID, only the NSMADD entry will be used.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
TYPE This can be one of the properties PSHELL, PCOMP, PBAR, PBARL, PBEAM,
PBEAML, PROD, CONROD, PSHEAR, or PTUBE, in which case the list of IDs will
refer to properties of the stated type, or it can be ELEMENT, in which case the
list is of individual element IDs of elements that can have NSM.
VALUE A lumped mass value to be distributed over all the listed elements and elements
referencing listed properties.
No default (Real)
Comments
1. Refer to the User's Guide section on Non-structural Mass for more information on the use
of this card.
2. Non-structural mass in this format must be selected by the NSM Subcase Information
selector.
3. This entry will calculated an equivalent non-structural mass per unit area or per unit
length using the lumped mass values provided.
4. You cannot mix "area" and "line" elements on the same entry. The "area" elements are:
CQUAD4, CQUAD8, CTRIA3, CTRIA6, and CSHEAR; and the "line" elements are: CBAR,
CBEAM, CTUBE, CROD, and CONROD.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ID ID ID -etc.-
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
TYPE This can be one of the properties PSHELL, PCOMP, PBAR, PBARL, PBEAM, PBEAML,
PROD, CONROD, PSHEAR, or PTUBE, in which case the list of IDs will refer to
properties of the stated type, or it can be ELEMENT, in which case the list is of
individual element IDs of elements that can have NSM.
VALUE A lumped mass value to be distributed over all the listed elements and elements
referencing listed properties.
No default (Real)
Comments
1. Refer to the User's Guide section on Non-structural Mass for more information on the use
of this card.
2. Non-structural mass in this format must be selected by the NSM Subcase Information
selector.
3. This entry will calculated an equivalent non-structural mass per unit area or per unit
length using the lumped mass values provided.
4. You cannot mix "area" and "line" elements on the same entry. The "area" elements are:
CQUAD4, CQUAD8, CTRIA3, CTRIA6, and CSHEAR; and the "line" elements are: CBAR,
CBEAM, CTUBE, CROD, and CONROD.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
TZREID Identification of the TABLEDi entry that defines the resistance as a function of
frequency. The real part of the impedance.
TZIMID Identification of the TABLEDi entry that defines the reactance as a function of
frequency. The imaginary part of impedance.
A Area factor when 1 or 2 grid points are specified in the CAABSF entry.
RHOC Constant used in data recovery for calculating an absorption coefficient. RHO is
the media density and C is the speed of sound in the media.
$$
$$ Optistruct Input Deck Generated by HyperMesh Version : 10.0build60
$$ Generated using HyperMesh-Optistruct Template Version : 10.0-SA1-120
$$
$$ Template: optistruct
$$
$$
$
DISPLACEMENT(PHASE) = 1
OUTPUT,HGFREQ,ALL
OUTPUT,OPTI,ALL
OUTPUT,H3D,ALL
OUTPUT,PUNCH,ALL
$$------------------------------------------------------------------------------$
$$ Case Control Cards $
$$------------------------------------------------------------------------------$
$
$HMNAME LOADSTEP 1"Piston_Load" 6
$
SUBCASE 1
LABEL Piston_Load
SPC = 12
METHOD(STRUCTURE) = 4
METHOD(FLUID) = 5
FREQUENCY = 3
DLOAD = 9
XYPUNCH DISP 1/ 11(T1)
XYPUNCH DISP 1/ 43(T1)
XYPUNCH DISP 1/ 55(T1)
XYPUNCH DISP 1/ 67(T1)
XYPUNCH DISP 1/ 79(T1)
XYPUNCH DISP 1/ 91(T1)
XYPUNCH DISP 1/ 103(T1)
XYPUNCH DISP 1/ 115(T1)
$
$$--------------------------------------------------------------
$$ HYPERMESH TAGS
$$--------------------------------------------------------------
$$BEGIN TAGS
$$END TAGS
$
BEGIN BULK
ACMODL
$$
$$ Stacking Information for Ply-Based Composite Definition
$$
PARAM,AUTOSPC,YES
PARAM,POST,-1
$$
$$ DESVARG Data
$$
$$
$$ GRID Data
$$
GRID 9 0.492 0.0 -1.72-15 -1
GRID 10 0.246 0.0 -8.59-16 -1
GRID 11 0.0 0.0 0.0 -1
GRID 12 -0.246 0.0 8.589-16 -1
GRID 13 -0.492 0.0 1.718-15 -1
GRID 14 -0.492 0.246 1.718-15 -1
GRID 15 -0.492 0.492 1.718-15 -1
GRID 16 -0.246 0.492 8.589-16 -1
GRID 17 0.0 0.492 0.0 -1
GRID 18 0.246 0.492 -8.59-16 -1
GRID 19 0.492 0.492 -1.72-15 -1
GRID 20 0.492 0.246 -1.72-15 -1
GRID 21 0.0 0.246 0.0 -1
GRID 22 -0.246 0.246 8.589-16 -1
GRID 23 0.246 0.246 -8.59-16 -1
GRID 24 0.492 -0.246 -1.72-15 -1
GRID 25 0.492 -0.492 -1.72-15 -1
GRID 26 0.246 -0.492 -8.59-16 -1
$
$$
$$ PSHELL Data
$$
$
$
$
$
$
$
$
$HMNAME PROP 1"tube" 4
$HWCOLOR PROP 1 52
PSHELL 1 20.1 2 2 0.0
$$
ALTDOCTAG "0mjpRI@DXd^3_0ASnbi`;l;q6A23R@9_67hgW8R?OiZ]
Eq:PeN``A;WXh3ITgJeq5NZRd5jSHQK3X@:`a12;n4qD_I^RYMo"
ADI0.1.0 2011-02-11T20:16:20 0of1 OSQA
ENDDOCTAG
Comments
2. If only one grid point is specified on the CAABSF entry, then the impedance Z(f) = ZR +
iZi is the total impedance at the point. If two grids are specified, then the impedance is
the impedance per unit length. If three or four points are specified, then the impedance
is the impedance per unit area. ZR(f) = TZREID(f) + B and Zi(f) = TZIMID(f) – K/(ω).
4. The impedance scale factor S is used in computing element stiffness and damping terms
as:
5. To create a non-reflecting boundary, set the values of the TABLEDi entry referenced by
Where, is the density of the fluid and, is the speed of sound in the fluid.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
K M
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
SYNTH Request the calculation of B, K, and M from the specified tables TIDi.
TID3 Identification of the TABLEDi entry that defines the weighting function.
$$------------------------------------------------------------------------------$
$$ $
$$ NASTRAN Input Deck Generated by HyperMesh Version : 8.0SR1 $
$$ Generated using HyperMesh-Nastran Template Version : 8.0sr1
$$ $
$$ Template: general $
$$ $
$$------------------------------------------------------------------------------$
$$------------------------------------------------------------------------------$
$$ Executive Control Cards $
$$------------------------------------------------------------------------------$
SOL 111
CEND
$$------------------------------------------------------------------------------$
$$ Case Control Cards $
$$------------------------------------------------------------------------------$
SET 1 = 1734
DISPLACEMENT = 1
$
$HMNAME LOADSTEP 1"Load2"
SUBCASE 1
LABEL= Load2
SPC = 4
FREQUENCY = 5
DLOAD = 2
$$------------------------------------------------------------------------------$
$$ Bulk Data Cards $
$$------------------------------------------------------------------------------$
BEGIN BULK
ALTDOCTAG "HqTD_ARNMI\S\pMpN13G;5oANN]l[enE7fmSbTJro20LOpNriZFOQfUk]
_`5hfS5ATf6pT7RXMjA3e@k_r^K?GP;?OeEbD0"
ADI0.1.0 2011-05-13T19:57:45 0of1 OSQA
ENDDOCTAG
2. If SYNTH = “YES”, then TID1 and TID2 must be supplied (TID3 is optional) and the
equivalent structural model will be derived from tables TIDi. If TID3 is blank, then the
weighting function defaults to 1.0.
3. If SYNTH=”NO”, then the equivalent structural model will be derived from B, K and M.
Description
Defines up to four sets of grid points or elements as panels for panel participation output for a
frequency response analysis of a coupled fluid-structural model.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
Comments
1. If a set of elements is defined, the panel will consist of all grid points connected to these
elements.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
Comments
1. The panel type indicates the context in which the panel should be used. PFP indicates
that the panel should be considered for panel participation output (similar to PANEL). ERP
indicates that the panel should be considered for equivalent radiated power output
2. Panels of type ERP/SOUND (or blank) may be defined as a set of elements, a set of grid
points, or both. If a set of elements is defined, the panel will consist of all grid points
connected to these elements. If both sets are defined, the panel will consist of the
intersection of those sets.
4. The element set can also consist of solid elements. In such cases, grids on the wetted
surface are automatically detected to define the panel.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PARAM N V
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
N Name of Parameter.
V Value of Parameter.
The available parameters and their values are listed below (click the parameter name for
parameter descriptions).
AMSESLM Indicate if the AMSES numerical mode for enforced <YES, NO>
motion based modal dynamic analysis with large Default = NO
mass method will be activated or not.
BUSHRLMT Issues a WARNING when the stiffness value for <Real Number > 0.0>
rotational components on the PBUSH entry exceeds
Default = 1.0E+09
the specified limit (BUSHRLMT).
BUSHSTIF Specifies a value to replace large stiffness values <Real Number > 0.0>
(>1.0E+07) input in field K of the PBUSH data entry. No default
BUSHTLMT Issues a WARNING when the stiffness value for <Real Number > 0.0>
translational components on the PBUSH entry
Default = 1E+07
exceeds the specified limit (BUSHTLMT).
CMFTINIT Defines lower threshold for *.HM.comp.cmf and 0.0 < REAL < 1.0
*.HM.ent.cmf HyperMesh command files. Default = 0.0
CMFTSTEP Defines step or interval value for *.HM.comp.cmf 0.0 < REAL < 1.0
and *.HM.ent.cmf HyperMesh command. Default = 0.1
CMSALOD Controls the inclusion of mass contribution from the <YES, NO>
mass matrix stored in the PUNCH DMIG or the H3D Default = YES
DMIG files for the generation of RFORCE and Gravity
Loads.
YES, NO,
COMP2SHL Results of homogenization of composite properties.
BULK
Default = NO
COUPMASS Use coupled mass matrix approach for eigenvalue -1, 0, 1, YES, NO
analysis. Default = NO
CSTEVAL Use wall time based cost evaluation for Lanczos <YES, NO>
steps. Default = YES
Default = 10-5
EFFMAS Output modal participation factors and effective YES, NO, Integer
mass for normal modes analyses. Default = NO
ELASRLMT Issues a WARNING when the stiffness value for <Real Number > 0.0>
rotational components on the CELAS2/4 or PELAS
Default = 1.0E + 09
entry exceeds the specified limit (ELASRLMT).
ELASSTIF Specifies a value to replace large stiffness values <Real Number > 0.0>
(>1.0E+07) input in field K of the PELAS data entry. No default
ELASTLMT Issues a WARNING when the stiffness value for <Real Number > 0.0>
translational components on the CELAS2/4 or PELAS
Default = 1E+07
entry exceeds the specified limit (ELASTLMT).
ERPC The speed of sound used in the ERP calculation Real > 0.0
Default = 1.0
ERPREFDB The reference value in decibels (dB) used in ERP Real > 0.0
calculations. Default = 1.0
ERPRHO The fluid density used in ERP calculations. Real > 0.0
Default = 1.0
ERPRLF The Radiation Loss Factor used in ERP calculation. Real > 0.0
Default = 1.0
EXCEXB Controls the output of the AVL/EXCITE .exb file <YES, BOTH, NO>
directly from OptiStruct. Default = BOTH
FLEXH3D Generate flexh3d files for flexible bodies in an MBD <AUTO, YES, NO>
analysis. Default = AUTO
GPSLOC Controls where the grid point stresses are calculated Z1, Z2 and MID
for output to the .mnf file. Default = Z1
GRIDFORM This parameter controls the output format of the <LONG, SHORT>
.grid file. Default = SHORT
K4CUTOFF Sets cut-off value if the low rank representation for <REAL>
the structural damping matrix is selected. Default = 0.1
LFREQ Can be used to remove the Rigid Body Modes from <REAL>
the Modal Space. Default = None
LMSOUT Output the condensed Flex Body Modes, full Diagonal YES, NO, STRESS
Mass Matrix, and modal stresses to the .op2 file. Default = NO
LOWRANK Indicates to FastFRS which solution strategy to use <0, -1, 1>
to handle the modal structural damping matrix. Default = 0
MBDH3D Choose the type of the results output to the .h3d NODAL, MODAL, BOTH,
file for MBD analyses. NONE
Default = BOTH
MBDREC Create a small and large flexible body files during YES, NO
Component Mode Synthesis (CMS). Default = NO
MFILTER Defines a threshold for the mode tracking matrix to <0.0 < real number <
check eigenvector correspondence. 1.0>
NEGMASS Allows run to proceed with negative diagonal mass <0, 1>
terms. Default = 0
NLRUN Controls the run of geometric nonlinear analysis after <YES, NO>
bulk to block conversion. Default = YES
OGEOM Output model data to the OUTPUT2 results file. <YES, NO>
Default = YES
OMID Output stress and strain results for shell and <YES, NO>
membrane elements with reference to the material Default = NO
coordinate system.
OP2GM34 Controls the output of GEOM3 and GEOM4 data <TRUE, FALSE>
blocks to the .op2 file. Default = TRUE
PLIGEXT Print the applied load vector in DMIG form to the <YES,NO>
.pligext file. Default = NO
POSTEXT Output the modal complex stiffness matrix and modal YES, NO
viscous damping matrix to the OUTPUT2 results file. Default = NO
Analysis.
PRINFACC Controls the output of inertial relief rigid body forces <1, 0>
and accelerations.
RBE2FREE Used to convert ERROR 725 into WARNING 825 when <YES, NO>
singular RBE2 elements are present in the model. Default = NO
RBE3FREE Used to convert ERROR 772 into WARNING 824 when <YES, NO>
free spiders on RBE3 elements are present in the Default = NO
model. These free spiders may contain singular
degrees of freedom.
REANAL Reanalyze the final iteration of a topology 0.0 < REAL < 1.0
optimization without penalization. No default
RENUMOK Allows you to correctly renumber the reversed (but <YES, NO, BLANK>
acceptable) sequence of element grids without Default = NO
having to run (import and re-export) the model
through HyperMesh.
RFIOUT This parameter controls the output of modal super <YES, NO>
element for use in the RecurDyn multibody dynamics Default = NO
software from FunctionBay.
RHOCP The scale factor used to calculate ERP in decibels Real > 0.0
(dB). Default = 1.0
SEP1XOVR The old and new location of moved shell grid points 0, 16
are printed if SEP1XOVR = 16. Default = 0
SEPLOT Output display model to .seplot file, from a CMS <YES, NO>
run. Default = YES
SHELOS11 Allows you to revert to the first order shell element <YES, NO>
formulation (for CQUAD4 and CTRIA3) used in version Default = NO
11.0.240 and earlier.
SHL2MEM A shell property (defined by the PSHELL bulk data <Real Number > 0.0>
entry) is automatically converted into a membrane No default
property if the membrane thickness (field T) of the
PSHELL bulk data entry is less than the value
specified using PARAM, SHL2MEM.
SPLC Specifies the speed of sound used in the wave Real > 0.0
number and the complex particle velocity vector Default = 1.0
calculations.
SPLFAC Specifies the scale factor (q ) used to calculate the Real > 0.0
Sound Pressure Level in Radiated Sound Analysis. Default = 1.0
SPLREFDB Specifies the reference sound pressure value used Real > 0.0
to calculate the Sound Pressure Level (SPL) in Default = 1.0
decibels (dB).
SPLRHO Specifies the density of the acoustic medium in the Real > 0.0
calculation of the complex acoustic sound pressure Default = 1.0
and the complex particle velocity vector.
SRCOMPS Outputs the strength ratios for composite elements <YES, NO>
that have failure indices requested. Default = NO
THCNTPEN Controls the penalty factor used in thermal contact AUTO, LOW, HIGH
analysis. Default = AUTO
TRAKMETH Used to select the criterion employed for mode <0, 1, 2>
tracking. Default = 0
TRAKMTX Controls output of the mode tracking matrix during <0, 1>
optimization. Default = 0
TPS Activate fast transient response analysis (only shell <YES, NO>
stress results output). Default = YES
VMOPT Allows you to prevent the inclusion of the Virtual <Integer = 0, 1, 2>
WTMASS Convert weights to masses using this multiplier. REAL > 0.0
Default = 1.0
Comments
ACMODL <YES, NO> PARAM, ACMODL12, YES can be used to restore the
ACMODL formulation used in version 12.0 and earlier for the
Default = NO
Fluid-Structure Interface.
Note
AKUSMOD <YES, NO> If YES, this indicates that OptiStruct should use a fluid-
Default = NO structure coupling matrix generated by AKUSMOD. In this
case, the ACMODL data is ignored.
AMSESLM <YES, NO> YES: The EIGRA (AMSES) numerical method for enforced
Default = NO motion based modal dynamic analysis with large mass
method will be activated.
ASCOUP <YES, NO> If YES, the fluid-structure coupling (area) matrix will
Default = YES be calculated and used in the solution.
BUSHRLMT <Real Number > This parameter is used to issue a WARNING when the
0.0> stiffness value for rotational components on the PBUSH
entry exceeds the specified limit (BUSHRLMT).
Default = 1.0E +
09 Note: This check is overridden when PARAM, BUSHSTIF
is used to control the maximum stiffness value.
This parameter can accept two arguments. If only one argument is specified, the same value
is used for the second argument.
Format
PARAM, BUSHSTIF, <BUSHSTIFT>, <BUSHSTIFR>
BUSHSTIFT <Real Number > This parameter controls the value of field “K” in the
0.0> PBUSH property entries.
No default BUSHSTIFT:
This value applies to translational stiffness fields on the
property entry (first three values).
BUSHSTIFR <Real Number >
0.0> BUSHSTIFR:
This value applies to rotational stiffness values on the
Default = property entry.
<BUSHSTIFT>
Note:
3. Defaults:
BUSHTLMT <Real Number > This parameter is used to issue a WARNING when the
0.0> stiffness value for translational components on the
PBUSH entry exceeds the specified limit (BUSHTLMT).
Default = 1E+07
Note: This check is overridden when PARAM, BUSHSTIF
is used to control the maximum stiffness value.
CB2 Real CB2 specified factors for the direct input damping matrix.
Default = 1.0 The total damping matrix is:
CHECKEL NO, YES, FULL If NO, element quality checks are not performed, but
Default = YES mathematical validity checks are performed.
CHECKMAT YES, NO, FULL If YES, the material properties for all referenced material
Default = YES definitions are checked for adherence to the default
material requirements as described on the Material
Property Check page. The amount of output is limited.
CHKGPDIR YES, NO, WARN, If YES, all gap elements of non-zero length (distance
FULL, REVERSE between GA-GB) that have a prescribed coordinate
Default = YES system CID are checked for misalignment of gap
prescribed axis (x-axis of CID) with the vector GA->GB
(angles larger than 30 degrees produce errors). The
amount of output is limited to the first ten occurrences.
Note that this check applies correctly to the most
typical situations where in there is an initial opening
between bodies A and B, and the gap element is used
to enforce non-penetration condition (for other cases,
see the REVERSE option below).
CK2 Real CK2 specifies factors for the direct input stiffness matrix.
Default = 1.0 The total stiffness matrix is:
CK3 Real CK3 specifies factors for the stiffness matrix produced by
Default = 1.0 GENEL cards. The total stiffness matrix is:
CM2 Real CM2 specifies factors for the direct input mass matrix. The
Default = 1.0 total mass matrix is:
CMFTINIT 0.0 < REAL < 1.0 PARAM, CMFTINIT defines the lower threshold value used
Default = 0.0 for the HyperMesh command files *.HM.comp.cmf and
*.HM.ent.cmf.
CMFTSTEP 0.0 < REAL < 1.0 PARAM, CMFTSTEP defines the step or interval value
Default = 0.1 used for the HyperMesh command files *.HM.comp.cmf
and *.HM.ent.cmf.
CMSALOD <YES, NO> PARAM, CMSALOD controls the generation of RFORCE and
Default = YES Gravity loads from the mass matrix stored in the PUNCH
DMIG or H3DDMIG file.
COEFFC Real > 0.0 Value of the friction coefficient on curvatures for one-
step stamping simulation.
COUPMASS -1, 0, 1, YES, If -1, 0 or NO, the lumped mass matrix approach is used
NO for eigenvalue analysis.
Default = NO
If 1 or YES, the coupled mass matrix approach is used
for eigenvalue analysis.
CP2 Real CP2 specifies factors for the direct input load matrix.
Default = 1.0 The total load matrix is:
CSTEVAL YES, NO This parameter controls whether to use wall time based
Default = YES cost evaluation to provide the optimal performance in
running Lanczos steps.
DISIFMCK <YES, NO> For vibrational eigenvalue analysis, the mass matrix must be
Default = NO positive semi-definite. However, if this is simply caused by
numerical ill-conditioning, then PARAM,DISIFMCK may be used
to skip the indefinite mass matrix check.
DUPTOL <0, 1, 2, 3, 4, 5> PARAM, DUPTOL controls how many decimal places
Default = 0 can differ when comparing X, Y, and Z coordinates on
GRID and CORDxx cards with identical ID. Obsolete,
use SYSSETTINGS,DUPTOL command.
EFFMA <YES, When EFFMAS < 0 or NO, the modal participation factors, modal
S NO, participation factor ratio, and modal effective mass are not output for
Integer> normal modes analysis.
Default =
NO When EFFMAS > 0 or YES, the modal participation factors, modal
participation factor ratio, and modal effective mass will be computed and
output to the .out and .pch files for normal modes analysis. They are
computed as follows:
The Modal Participation Factor Ratio is the Modal Participation Factor for
each rotational and translational direction divided by the maximum Modal
Participation Factor of all the modes for that direction. So, each of the
six directions will have a value of 1.0 for the mode that has the
maximum Modal Participation Factor and the other modes will have a
value less than 1.0.
[V] is the objective function matrix. Six rigid body modes are
used as objective function in normal modes analysis to
obtain [PF] and [EFFMAS].
EHD <YES, NO> This parameter is used to print the inverse of the
Default = NO stiffness matrix created by static reduction to FORTRAN
unit 3. The inverse reduced stiffness matrix is written in
NASTRAN MATPRN format.
ELASRLMT <Real Number > This parameter is used to issue a WARNING when the
0.0> stiffness value for rotational components on the
CELAS2/4 or PELAS entry exceeds the specified limit
Default = 1.0E +
(ELASRLMT).
09
Note: This check is overridden when PARAM, ELASSTIF
is used to control the maximum stiffness value.
This parameter can accept two arguments. If only one argument is specified, the same value
is used for the second argument.
Format
PARAM, ELASSTIF, <ELASSTIFT>, <ELASSTIFR>
ELASSTIFT <Real Number > This parameter controls the value of field “K” in the
0.0> PELAS scalar elastic property entry and the CELAS2/
CELAS4 scalar spring property and connection entries.
No default
ELASSTIFT:
This value applies to translational stiffness fields on the
PELAS scalar elastic property entry and the CELAS2/
CELAS4 scalar spring property and connection entries.
ELASSTIFR:
This value applies to rotational stiffness values on the
ELASSTIFR <Real Number > PELAS scalar elastic property entry and the CELAS2/
0.0> CELAS4 scalar spring property and connection entries.
Default =
Note:
<ELASSTIFT>
1. Any value on the field “K” on the PELAS or CELAS2/
CELAS4 entry which exceeds ELASSTIFT or
ELASSTIFR, respectively will be replaced by
ELASSTIFT or ELASSTIFR.
3. Defaults:
ELASTLMT <Real Number > This parameter is used to issue a WARNING when the
0.0> stiffness value for translational components on the
CELAS2/4 or PELAS entry exceeds the specified limit
Default = 1E+07
(ELASTLMT).
ERPC Real > 0.0 The speed of sound used in the ERP calculation:
Default = 1.0
ERPREFDB Real > 0.0 This parameter can be used to specify the reference
Default = 1.0 power value used to calculate Equivalent Radiated Power
(ERP) in decibels (dB).
Note:
Where,
ERPRHO Real > 0.0 The fluid density used in ERP calculations:
Default = 1.0
ERPRLF Real > 0.0 The Radiation Loss Factor used in the ERP calculation:
Default = 1.0
EXCEXB <YES, BOTH, NO> This parameter controls the output of the AVL/EXCITE
.exb file directly from OptiStruct.
Defaults
If this parameter If YES, the AVL/EXCITE .exb file is output.
is included in the
If BOTH, the AVL/EXCITE .exb file and the old files
input file, but, no
(.doft, .geom, _mff.out4, _x2oa.out4, and .out4)
value is provided,
then the default are output.
value is YES. If NO, the AVL EXCITE interface output files are not
If this parameter output.
is not included in Note: PARAM, EXCEXB, YES/BOTH should be used in
the input file (and conjunction with PARAM, EXCOUT. OptiStruct will
PARAM, EXCOUT error out if PARAM, EXCEXB, YES/BOTH is
is present), then specified without PARAM, EXCOUT in the model.
the default value
is BOTH.
0 All output.
EXPERTNL YES, NO, YES activates a nonlinear "expert system" that aids in the
CNTSTB, convergence of small displacement nonlinear problems
AUTO (NLSTAT). This version is designed to facilitate obtaining
converged, high accuracy solutions without much concern
Default = for computational time. The system monitors the
AUTO convergence of nonlinear processes and, if needed,
implements measures designed to improve convergence for
poorly converging cases. These measures include:
performing additional iterations, under-relaxation, automatic
adjustment of the load increment, as well as backing off to
the last convergent solution and retrying. This may lead to
a large number of nonlinear iterations for poorly converging
problems.
FASTFR <YES, NO> If, AUTO (Default), the faster method is automatically
Default = AUTO chosen by the program for Modal Frequency Response
Analysis. If the FASTFR method is not activated, the
standard method is used (see comments).
Comments:
The FASTFR method will be ignored for Modal Frequency
Response Analysis, if:
FFRS <YES, NO> This parameter is used to invoke the external FastFRS
Default = NO (Fast Frequency Response Solver). This solver is very
efficient for a certain class of large modal frequency
response problems, such as those common in automotive
NVH analysis. Note that FastFRS must be installed on the
system and the environment variable FASTFRS_EXE must
point to the FastFRS executable for this setting to work.
Note
FLEXH3D AUTO, YES, NO This parameter controls the generation of flexh3d files
Default = AUTO for flexible bodies in an MBD analysis.
FLIPOK NO, YES If YES, severely distorted and possibly inverted elements
Default = NO will be accepted by the solver. This is limited to first
order tetra (CTETRA) and tria (CTRIA3) elements.
FZERO <Real> This parameter defines the maximum frequency for a rigid
Default = 0.1 body mode for the Lanczos eigensolver. That is all
eigenmodes with frequency at or below this cutoff will be
regarded as rigid body modes in the inertia relief
analysis.
Note:
Note:
GFL <Real> GFL specifies the uniform fluid damping coefficient in the
Default = 0.0 formulation of dynamics problems. To obtain the value
for the parameter GFL, multiply the critical damping
ration, C/C0, by 2.0.
GPSLOC Z1, Z2 and MID Used to control the where grid point stresses are
calculated for output to the .mnf file.
Default = Z1
The highest stresses are at the bottom (Z1) or top (Z2)
surface of the shell. For pure bending, they have the
same magnitude.
Note:
GRODFORM < LONG, SHORT > This parameter controls the output format of the
Default = SHORT .grid file.
HFREQ Real> Modes with frequencies higher than HFREQ are not used
(Hertz) in Modal Frequency Response and Modal Transient
Analysis.
Default = None
HFREQ is used in Response Spectrum Analysis to specify
Defaults the upper bound of the frequency range of interest for
modal combination.
If PARAM,
HFREQ is input Note:
without
specifying a 1. The Residual Vector (RESVEC) calculation still
value, then the includes the modes above HFREQ so that they are
solution runs normalized correctly.
into an error 2. Modes that are eliminated by PARAM, HFREQ will
display:
HFREQFL Real> Modes with frequencies greater than HFREQFL are not
(Hertz) used in Coupled Modal Frequency Response Analysis.
HFREQFL can be used to remove Rigid Body Modes from
Default = None the Modal Space.
INREL < 0, -1, -2 > INREL controls the calculation of inertia relief.
ITAPE -1, 0 If ITAPE = -1, then the ‘Tape Label’ is written at the
Default = -1 beginning of the OUTPUT2 results file.
Comments
1. When the fluid domain is represented by an MFLUID card, and PARAM, INTRFACE, YES is
specified, OptiStruct generates the .wetel file which contains data about the wet
elements resulting from MFLUID cards. The .wetel file can then be loaded into HyperMesh
to visualize the locations of submerged/damp elements in the model.
KDAMP < 1, -1 > If KDAMP is set to –1, modal damping is entered into the
Default = 1 complex stiffness matrix as material damping.
Note:
LFREQ <Real> Modes with frequencies less than LFREQ are not used in
(Hertz) Modal Frequency Response and Modal Transient Analysis.
LFREQ can be used to remove Rigid Body Modes from the
Default = None Modal Space.
LFREQFL Real> Modes with frequencies less than LFREQFL are not used
(Hertz) in Coupled Modal Frequency Response Analysis. LFREQFL
can be used to remove Rigid Body Modes from the Modal
Default = None Space.
LMSOUT <YES, NO, This parameter controls the output of the condensed flex
STRESS> body modes, full diagonal mass matrix, and modal stresses
Default = NO to the .op2 file.
If YES, the condensed flex body modes and the full diagonal
mass matrix are output to the .op2 file.
MBDH3D NODAL, MODAL, This parameter controls the type of results output
BOTH, NONE to the .h3d results format for MBD analyses.
Default = BOTH
If NODAL, nodal based results are output to the
.h3d results file.
T = O + A + M.
T = max(O,A) + M.
MFILTER <0.0 < real This parameter defines a threshold for the mode tracking
number < 1.0> matrix to check eigenvector correspondence.
The value of
PARAM,
MFILTER is
equal to 0.7 if
PARAM,
TRAKMETH is
set to 0 or 1.
The value of
PARAM,
MFILTER is
equal to 0.5 if
PARAM,
TRAKMETH is
set to 2.
MODETRAK -1, 0, 1, YES, If -1, 0 or NO, mode tracking is not used. Mode numbers
NO are determined by frequency.
Default = NO
If 1 or YES, mode tracking is used. Mode numbers are
tracked by comparing eigenvectors between iterations.
NLAFILE <YES, NO> This parameter controls the output of animation files (A-File)
Default = NO in geometric nonlinear analysis.
NLFAT <YES, NO> PARAM, NLFAT, YES, forces OptiStruct to run models in which
Default = NO fatigue solutions (using the FATLOAD entry) reference
nonlinear quasi-static analysis (NLSTAT) subcases.
Defaults:
PARAM, NLFAT, NO, does not allow NLSTAT subcases to be
1. If this referenced by the FATLOAD data entry and the solution
parameter errors out if such models are run.
does not
exist in the Note:
deck, the
default PARAM, NLFAT, YES can be introduced to force OptiStruct to
behavior is run fatigue analysis based on a nonlinear subcase
NO. (ANALYSIS=NLSTAT). Nonlinear analysis results are not
recommended for use in a fatigue analysis because
2. If this nonlinear stresses and strains cannot be scaled and
parameter superimposed, however, acceptable results may be generated
exists in the in the following cases:
deck,
however, no During a nonlinear run (ANALYSIS=NLSTAT),
value (YES/ acceptable results may be generated if a model uses
NO) is elasto-plastic material and NEUBER correction is turned
specified, OFF (Plasticity field on FATPARM bulk data entry). This
then the statement is based on the assumption that nonlinear
default analysis is run until shakedown is achieved. If strain
behavior is results from the nonlinear analysis are used prior to
NO. shakedown, the fatigue results will most likely be
incorrect since the magnitude of plastic strain may not
be close to the steady state strain value.
Additionally, acceptable results may be generated if
contact based nonlinearity exists in the model
(ANALYSIS=NLSTAT) and the contact area is not
expected to change appreciably as the load increases
(for example, surfaces that match from the beginning).
In both cases, the Scale and Offset fields on the FATLOAD
entry should be left blank as the stresses and strains cannot
be scaled and superimposed.
NLRFILE <YES, NO> This parameter controls the output of restart files (R-File) in
Default = NO geometric nonlinear analysis.
NPRBAR <INTEGER> Controls the number of the output INFORMATION #741 for
Default = 3 RBAR elements.
NPRBE2 <INTEGER> Controls the number of the output INFORMATION #741 for
Default = 3 RBE2 elements.
NUMEG <Integer> When ND on the EIGRL/EIGRA data is blank, the disk space
1000 estimate in the .out file for modal frequency response and
the transient analysis is based on the number of modes
specified by PARAM,NUMEG. When Lanczos is used, the disk
space estimate is based on this value plus the number of the
potential residual vectors. When AMLS/AMSES is used, the
disk space estimate is based only on the value of
PARAM,NUMEG. In this case, it is assumed that
PARAM,NUMEG includes the number of potential residual
vectors.
OGEOM <YES, NO> PARAM, OGEOM controls the output of model (geometry)
Default = YES data to the .op2 file. This functionality is also
controlled by the MODEL/NOMODEL option on the
OUTPUT, OP2 I/O option, but this parameter setting will
override the OUTPUT, OP2 setting.
OMACHPR <YES, NO> PARAM, OMACHPR controls the Nastran version for some
Default = NO OP2 datablocks.
OMID <YES, NO> Controls the coordinate system used by shell and
Default = YES membrane elements for stress and strain results.
OP2GM34 <TRUE, FALSE> PARAM, OP2GM34 controls the output of GEOM3 and
Default = TRUE GEOM4 data blocks to the .op2 file if PARAM, POST, -1 is
specified.
PLIGEXT <YES, NO> This parameter is used to print the applied load vector in
Default = NO DMIG form to the .pligext file. The DMIG NAME is
PLIGEXT.
POST <0, -1, -2, -5> Adding PARAM, POST to the bulk data section of the
Default = 0 input deck will activate the creation of the .op2 file.
PRGPST < YES, NO, ALL, PRGPST controls the printing of AUTOSPC information
NONE,< number of to the .out file.
DOFs> >
PARAM, PRGPST, YES
Default = YES
A maximum of 100 degrees of freedom (DOF) of
AUTOSPC data will be printed in the .out file.
PARAM, PRGPST, NO
PRINFACC <1, 0> If 1, the inertia relief rigid body forces and
accelerations are printed to the .out file.
Defaults
If 0, the inertia relief rigid body forces and
1. The default is
accelerations are NOT printed to the .out file.
0, when the
parameter is
not present in
the deck.
2. The default is
1, when
PARAM,
PRINFACC is
input without
specifying a
value.
RBE2FREE <YES, NO> Modeling errors can result in the creation of RBE2 elements
with rigid body rotations. This parameter can be used to
Default = NO convert ERROR 725 into WARNING 825 when singular RBE2
elements, with rotational rigid body modes in all three
directions, are present in the model.
YES
Note:
RBE3FREE <YES, NO> Modeling errors can result in the creation of RBE3 elements
with free spiders. This parameter can be used to convert
Default = NO ERROR 772 into WARNING 824 when free spiders on RBE3
elements are present in the model. These free spiders may
contain singular degrees of freedom.
YES
REANAL 0.0 < Real < 1.0 This parameter is for restart runs of topology
No default optimizations only.
Note:
Defaults
1. The mode shapes of the condensed system (only) generated during CMS are output when
this parameter is not present in the deck.
2. If PARAM, RECOVER is input without specifying a value, the program results in an ERROR.
RENUMOK <YES, NO, If YES or BLANK, when the solid element grids are listed
BLANK> in the order that would make the element inside out,
Default = NO they are automatically re-ordered. In this way, running
(importing and exporting) the model through HyperMesh
to get the corrected element grid sequence can be
avoided.
Note:
RFIOUT <YES, NO> This parameter controls the output of modal super
Default = NO element for use in the RecurDyn multibody dynamics
software from FunctionBay. This information is written
to the .rfi file. This should be used with CMSMETH
CBN and ASET DOF for the connection points.
Note:
RHOCP Real > 0.0 The scale factor used to calculate ERP in decibels (dB).
Default = 1.0 The calculation is:
SEP1XOVR 0, 16 The old and new location of moved shell grid points are
Default = 0 printed if SEP1XOVR = 16. When the RSSCON shell-to-
solid element connector is used. By default, the moved
shell grid points are not printed, SEP1XOVR = 0.
SEPLOT <YES, NO> PARAM, SEPLOT can be used during CMS analysis (only
Default = YES with the CBN method) to create a .seplot file that
contains the ASET grid data as well as the GRID and
Defaults: PLOTEL data defined using the MODEL I/O Option. The
data is written to the .seplot file in OptiStruct.
The value of this
parameter is YES,
YES: The .seplot file is created.
if it is included in
the input file, but
NO: The .seplot file is not created.
no value is
provided.
SHELOS11 YES, NO YES can be used to restore the formulation used in version
11.0.240 and earlier for first-order shell elements (CQUAD4
Default = NO and CTRIA3).
SHL2MEM <Real Number > A shell property (defined by the PSHELL bulk data
0.0> entry) is automatically converted into a membrane
property if the membrane thickness (field T) of the
No default
PSHELL bulk data entry is less than or equal to the
(see note 6) value specified using PARAM, SHL2MEM. This is done by
setting MID2 and MID3 to blank for the PSHELL.
Note:
6. Defaults:
Note:
Second order approximation is appropriate and provides
better accuracy for buckling of thin shells, which is
dominated by bending.
PARAM,SIMPACK,1
Writes CMS Matrices [k] and [m] to the SIMPACK
.fbi file.
Writes modes and eigenvectors of the SE to the
SIMPACK .fbi file.
PARAM,SIMPACK,2
This option writes out all the information specified in
PARAM, SIMPACK,1 (above) and additionally writes
model information to the SIMPACK .fbi file. See
Comment 2 about MODEL data.
PARAM,SIMPACK,3
This option writes out all the information specified in
PARAM, SIMPACK, 2 (above) to the SIMPACK .fbi
file and additionally includes the following:
PARAM,SIMPACK,4
This option writes out all the information specified in
PARAM, SIMPACK, 3 (above) to the SIMPACK .fbi
file and additionally includes the following:
Comments
1. Refer to the SIMPACK section of “Coupling OptiStruct with Third Party Software” in the
User’s Guide for more information.
2. If PARAM, SIMPACK, 2 is specified, the MODEL I/O Options Entry does not have any effect
on the output. The entire model is written to the SIMPACK .fbi file.
SMDISP < 0, 1 > This parameter is used to specify that small displacement
Default = 0 formulation or large displacement formulation is used. It
affects Geometric Nonlinear Implicit Static Analysis
(ANALYSIS = NLGEOM) and Geometric Nonlinear Implicit
Dynamic Analysis (ANALYSIS = IMPDYN).
SPLC Real > 0.0 This parameter is used to specify the speed of sound used
Default = 1.0 in the wave number and the complex particle velocity
vector calculations, as shown below (see the Radiated
Sound Analysis section in the User’s Guide for further
information):
Wave Number
Where,
pj ( f )
is the complex acoustic pressure due to source grid
j at the microphone location.
X̂ j
is the unit vector from the source grid j to the
microphone grid
r r
Xj Xj
X̂ j r
Xj rj
(see Figure 1)
rj
is the distance from the acoustic source grid j on the
SPLFAC Real > 0.0 This parameter specifies the scale factor (q ) used to
Default = 1.0 calculate the Sound Pressure Level in Radiated Sound
Analysis. The equation used for the calculation is:
Sound Pressure
Where,
f is the frequency of the sound wave in the medium.
is the density of the acoustic medium defined by
PARAM, SPLRHO.
rj
is the distance from the acoustic source grid j on the
panel to the microphone location grid (see Figure 1).
V flux f
j
is the velocity flux of the source grid j .
SPLREFDB Real > 0.0 This parameter can be used to specify the reference sound
Default = 1.0 pressure value used to calculate the Sound Pressure Level
(SPL) in decibels (dB).
Note:
SPLRHO Real > 0.0 This parameter is used to specify the density of the
Default = 1.0 acoustic medium in the calculation of the complex acoustic
sound pressure and the complex particle velocity vector,
as shown below (see the Radiated Sound Analysis section
of the User’s Guide for further information):
Where,
rj
is the distance from the acoustic source grid j on the
panel to the microphone location grid (see Figure 1).
V flux f
j
is the velocity flux of the source grid j .
Where,
pj ( f )
is the complex acoustic pressure due to source
X̂ j
is the unit vector from the source grid j to the
microphone grid
r r
Xj Xj
X̂ j r
Xj rj
(see Figure 1)
rj
is the distance from the acoustic source grid j on the
panel to the microphone grid (see Figure 1).
SRCOMPS <YES, NO> If YES, the strength ratios are output for composite
Default = NO elements that have failure indices requested. (The
Output formats currently supported are: H3D, HM, OP2,
PCH and OPT)
Note:
1
Strength Ratio
Failure Index
1
Strength Ratio
Failure Index
1
Strength Ratio
Failure Index
Note
THCNTPEN AUTO, LOW, PARAM, THCNTPEN controls the penalty factor used in
HIGH thermal contact analysis.
Default = AUTO
AUTO:
Determines the value of conductivity for each contact/
gap element based on the conductivity of surrounding
elements.
LOW:
Imposes a lower penalty factor that reduces the
conductivity of each contact/gap element compared to
the conductivities of the surrounding elements. It can be
used when the program runs into convergence
difficulties.
HIGH:
Imposes a higher penalty factor that increases the
conductivity of each contact/gap element compared to
the conductivities of the surrounding elements. It can be
used to enforce stronger conduction.
Note:
If TRAKMETH = 2
Where,
is the current eigenvector.
is the previous eigenvector.
is the mass matrix.
TRAKMTX <0, 1> TRAKMTX is a parameter that controls the output of the
Default = 0 mode tracking matrix during optimization.
Defaults: If TRAKMTX = 1
The mode tracking matrix will be printed to the output file
-The value of this at each iteration.
parameter is 0 if
it is not included If TRAKMTX = 0
in input file. The mode tracking matrix will not be printed to the
output file.
-If this parameter
is included in the Note:
input file, but no Each element of the mode tracking matrix stores the
value is provided, correlation value of two eigenvectors which is calculated
then running the using certain mode tracking criteria (see PARAM,
program will result TRAKMETH).
in an error.
Example
TPS <YES, NO> PARAM, TPS may be used with transient response
Default = YES analysis. When only shell stress results are required from
a transient response analysis, significant speed
improvements in run time can be obtained with the use of
this parameter.
UCORD <CID> If = -1, the mass moment of inertia is calculated about the
center of gravity and is output in the basic coordinate
system.
Default = -1 If = 0, the mass moment of inertia is calculated about the
origin of the basic coordinate system. The output values
are expressed in the basic coordinate system.
Note:
where:
where:
PARAM, WR3, 0
PARAM, WR4, 0
Note
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PAXI 2 203
Field Contents
Comments
Description
The PBAR bulk data entry defines the properties of a simple beam (bar), which is used to
create bar elements via the CBAR entry.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C1 C2 D1 D2 E1 E2 F1 F2
K1 K2 I12
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
2.0 4.0
Field Contents
J Torsional constant.
Comments
1. For structural problems, MID may reference only a MAT1 material entry. For heat transfer
problems, MID may reference only a MAT4 material entry.
2. The transverse shear stiffness in planes 1 and 2 are (K1)AG and (K2)AG, respectively.
The default values for K1 and K2 are infinite; in other words, the transverse shear
used for K1 and K2, the transverse shear flexibilities are set to 0.0 (K1 and K2 are
interpreted as infinite).
Description
Defines the properties of a simple beam (bar) by cross-sectional dimensions, which is used to
create bar elements via the CBAR entry.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DIM9 … NSM
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PBARL 12 7 BOX
10. 6. .5 .5
Field Contents
TYPE Cross-section type. When GROUP field is blank, this field is TYPE.
NAME Name of arbitrary beam section definition. Refer to Arbitrary Beam Section
Definition in the User’s Guide. When the value of GROUP is HYPRBEAM, this field
is NAME.
Default = blank
NSM Nonstructural mass per unit length. NSM is specified after the last DIMi.
Comments
1. For structural problems, MID may reference only a MAT1 material entry. For heat transfer
problems, MID may reference only a MAT4 material entry.
2. The cross-sectional properties, shear flexibility factors, and stress recovery points (C, D,
E, and F) are computed using the TYPE and DIMi as shown below. The origin of the
element coordinate system is centered at the shear center of the cross-section oriented
as shown. The PBARL does not account for offsets between the neutral axis and the
shear center. Therefore, the CHAN cross-sections may produce incorrect results. The
PBEAML entry is recommended.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
PID Property identification number of the associated PBAR or PBARL card. See
comment 1.
Default = 2 (Integer = 1, 2)
Comments
1. The property identification number must be that of an existing PBAR bulk data entry. Only
one PBARX property extension can be associated with a particular PBAR.
3. If the small strain option is activated (ISMSTR = 1), the strain and stress are engineering
strain and stress; otherwise they are true strain and stress.
Description
The PBEAM bulk data entry defines the properties of beam elements defined via the CBEAM
entry.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
The following two continuation lines may be repeated up to ten times. They are used to
define stations along the beam element.
C1 C2 D1 D2 E1 E2 F1 F2
K1 K2 NSIA NSIB
Example 1
This example represents a straight beam with stress recovery, only at end A.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NO 1.0
2.1
0.5
Example 2
This example represents a tapered beam with an intermediate section defined halfway
along its length and stress recovery at both end A and end B.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
2.1
0.5
Field Contents
I1(A) Area moment inertia in plane 1 about the neutral axis at end A.
I2(A) Area moment inertia in plane 2 about the neutral axis at end A.
Ci(A), Di(A), The y and z locations in element coordinates for stress data recovery at
Ei(A), Fi(A) end A. (i=1 is y and i=2 is z)
SO Stress output request option for intermediate stations and end B. See
comments 5 through 8.
I1 Area moment inertia in plane 1 about the neutral axis for intermediate
stations.
I2 Area moment inertia in plane 2 about the neutral axis for intermediate
stations.
Ci, Di, Ei, Fi The y and z locations in element coordinates for stress data recovery for
intermediate stations. (i=1 is y and i=2 is z). See comments 5 through 8.
NSIA Nonstructural mass moment of inertia per unit length about nonstructural
mass center of gravity at end A.
NSIB Nonstructural mass moment of inertia per unit length about nonstructural
mass center of gravity at end B.
Comments
1. For structural problems, MID may reference only a MAT1 material entry. For heat transfer
problems, MID may reference only a MAT4 material entry.
2. Blank fields for K1 and K2 are defaulted to 1.0. If a value of 0.0 is used for K1 and K2,
the transverse shear flexibilities are set to 0.0.
5. Stress recovery is only allowed at end A and end B. Stress recovery at intermediate
stations is not supported.
6. If no stress data at end A is to be recovered, but a stress recovery location is defined for
end B, then the first continuation entry, which contains the fields C1(A) through F2(A),
may be omitted.
7. If the continuation line containing values C1 through F2 is entirely blank for end B, then
the stress recovery locations defined for end A are used. However, if any entry is defined
on this line, then all blank entries will default to 0.0 and not the corresponding entry for
end A.
8. Stress recovery locations must be the same for end A and end B.
9. OSDIAG, 166, 1 may be input in the I/O options section of the input deck to bypass error
terminations caused by PBEAM definitions which violate the rules outlined in comments 5
and 8. In such instances, the following occurs:
Warning messages regarding the violations are echoed to the .out file.
12. The NSM specified at end A is the default value for NSM at end B. The default for all
other stations is a linear interpolation between end A and end B. So, for a constant NSM
over the length of the beam, only NSM at end A is required.
If the NSM value is different in different stations, it is averaged over all the stations and
the average is used in the element calculation.
Description
Defines the properties of a beam element by cross-sectional dimensions that are used to
create beam elements via the CBEAM entry.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
NSM(B)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PBEAML 99 21 T
TYPE Cross-section shape. When GROUP field is blank, this field is TYPE.
Default = blank
X(B)/XB Distance form end A to end B in the element coordinate system, divided
by the length of the element.
Comments
1. For structural problems, MID may reference only a MAT1 material entry. For heat transfer
problems, MID may reference only a MAT4 material entry.
2. Up to eleven stations are allowed (end A and B, and nine intermediate stations #).
3. The cross-sectional properties, shear flexibility factors, and stress recovery points (C, D,
E, and F) are computed using the TYPE and DIMi as shown below. The element
coordinate system is located at the shear center.
Type = I1 Type = L
Type = T1 Type = T2
4. For PBEAML entries with more than one section, an equivalent PBEAM entry is derived. An
echo request will cause a printout of the derived PBEAM.
5. Stress recovery is only allowed at end A and end B. Stress recovery at intermediate
stations is not supported.
6. For tapered beams, a single prismatic beam is created with dimensions obtained by
weighted averaging of all station dimensions.
7. DIMi and NSM have to be specified fully on station A. On station B, blank means that the
dimensions are the same as at A. On other stations, it is a linear interpolation between A
and B.
8. The NSM specified at end A is the default value for NSM at end B. The default for all
other stations is a linear interpolation between end A and end B. So, for a constant NSM
over the length of the beam, only NSM at end A is required.
If the NSM value is different in different stations, it is averaged over all the stations and
the average is used in the element calculation.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
Default = 2 (Integer = 1, 2)
Comments
1. The property identification number must be that of an existing PBEAM bulk data entry.
Only one PBEAMX property extension can be associated with a particular PBEAM.
3. If the small strain option is activated (ISMSTR = 1), the strain and stress are engineering
strain and stress; otherwise they are true strain and stress.
Description
Defines the nominal property values for a generalized spring-damper-mass structural element.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PBUSH PID K K1 K2 K3 K4 K5 K6
B B1 B2 B3 B4 B5 B6
M M1 M2 M3 M4 M5 M6
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
GE 0.02
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PBUSH 35 B 4.35
M 1.2 7.1
No default (Character)
No default (Character)
GE Flag indicating that the next 1 to 6 fields are the structural damping
constants.
No default (Character)
Comments
The nominal values are used for all analysis types except frequency response. For modal
frequency response, the normal modes are computed using the nominal Ki values. The
frequency-dependent values are used at every excitation frequency.
4. To obtain the damping coefficient GE, multiply the critical damping ratio C/C0 by 2.0.
6. For upward compatibility, if ONLY GE1 is specified on a PBUSH entry and GEi, i = 2 to 6 are
blank on that PBUSH entry, then a single structural damping is assumed and applied to all
Ki of that PBUSH. If a PBUSH entry has a GEi, i = 2 to 6 specified, then the GEi fields are
considered variable for that PBUSH entry.
7. The Mi fields do not contribute to mass and inertia properties. Their contributions to
gravity and/or centrifugal loading are also not included.
8. The keyword RIGID may be used in place of a stiffness value for Ki entries. When RIGID is
defined, a very high relative stiffness (relative to the surrounding structure) is selected
for that degree-of-freedom simulating a rigid connection.
Description
Defines the linear and nonlinear properties for a one-dimensional spring-and-damper structural
element.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PBUSH1D PID K B M
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PBUSH1D 35 4.35
SPRING TABLE 43
Field Contents
K Stiffness.
B Viscous damping.
M Total mass.
SPRING String indicating that a function defining the spring characteristics follows.
Comments
1. Either the stiffness K, or the damping B, or the mass M must be specified. B and M are
ignored in static subcases.
2. The SPRING continuation line is used in nonlinear analysis solution sequences only. The
table input supersedes the stiffness K.
Description
Defines property values for a generalized spring and damper structural element.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
... ...
Field Contents
PID Property identification number. Must match with a PID of a PBUSH Bulk
Data Entry.
If TYPE is K, then the following six fields are stiffness vs. frequency table
references for dofs 1 through 6, respectively.
If TYPE is B, then the following six fields are viscous damping vs. frequency
table references for dofs 1 through 6, respectively.
If TYPE is GE, then the following six fields are structural damping vs.
frequency table references for dofs 1 through 6, respectively.
If TYPE is M, then the following six fields are directional mass vs. frequency
table references for dofs 1 through 6, respectively.
If TYPE is KN, then the following six fields are force vs. deflection table
references for dofs 1 through 6, respectively.
See comment 4.
Comments
1. The K, B, GE, and M fields are associated with the same entries on the PBUSH entry
2. PBUSHT may only be referenced by CBUSH elements in the residual structure which do not
attach to any omitted degrees-of-freedom.
3. The TYPEs can be defined in any order, but may only appear once per PBUSH definition.
4. TYPE=K, B, GE and M are allowed for frequency response analysis only, while TYPE=KN is
allowed only for nonlinear analysis.
5. For upward computability, if ONLY the dof1 field for the GE line (line where TYPE=GE) is
specified on ALL PBUSHT entries and the other dofs for the GE line are blank on ALL
PBUSH entries, then a single structural damping table for each PBUSHT applied to all
defined dofs on the K line for each PBUSH is assumed. If ANY PBUSHT entry has a dof
field other than dof1 for the GE line specified, then the GE fields are considered variable
on ALL PBUSH and PBUSHT entries.
Description
Defines properties TYPE2 tied CONTACT interface for geometric nonlinear analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PC NTX2 PID
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
STFAC VISC
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PC ONT 34
PC NTX2 34
IGNORE Flag to ignore slave nodes if no master segment found for TIE contact
(See comment 7).
Default = 5.
20, 21, 22 - formulation with failure. Not compatible with nodal time step
GRID(CST) on XSTEP card. The stress is computed for each slave node
according to the "equivalent" surface around the node. The equivalent
surface is defined accordingly:
20 - Surface computed using shell and brick faces attached to the node.
21 - Surface computed using only the shell attached to the node.
22 - Surface computed using only the brick faces attached to the node.
25 - Penalty formulation.
30 - Formulation with cubic curvature of master segment. Not compatible
with nodal time step GRID(CST) on XSTEP card.
Default = 2 (Integer)
0 - No deletion.
RUPT Failure model (only available with FSPOT = 20, 21, 22) (Integer).
See comment 7.
Default = 0 (Integer = 0, 1)
0 - No filtering
STFAC Interface stiffness scale factor. (Only used with FSPOT = 25)
Comments
1. The property identification number must be that of an existing PCONT bulk data entry.
Only one PCNTX2 property extension can be associated with a particular PCONT.
2. PCNTX2 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. If FRIC is not explicitly defined on the PCONTX/PCNTX# entries, the MU1 value on the
CONTACT or PCONT entry is used for FRIC in the /INTER entries for Geometric Nonlinear
Analysis. Otherwise, FRIC on PCONTX/PCNTX# overwrites the MU1 value on CONTACT/
PCONT.
6. The default value for SRCHDIS is the average of the mater segments.
7. If IGNORE = 1 or 2, the slave nodes without a master segment found during the searching
are deleted from the interface;
If INGORE = 1 and SRCHDIS is blank, then the default value of the distance for searching
closest master segment is the average size of the master segments;
If IGNORE = 2 and SRCHDIS is blank, then the distance for searching closest master
segment is computed as follows for each slave node:
d2 = 0.05 * T md
where,
T s - Thickness of the element connected to the slave node, for solids T s = 0.0
8. Master nodes of an interface type 2 may be slave nodes of another interface type 2 if the
hierarchy level of the first interface is lower than the hierarchy level of the second
interface. Hierarchy levels are only available with FSPOT=2.
9. For failure (FSPOT = 20, 21, 22), it could model glue connection. In this case, the force in
slave node will be scaled by reduced force coefficient f N (f T ), which is computed as;
: normal stress
: tangential stress
Once the rupture criterion (defined by Rupt) is reached, the contact will be deleted.
11. If FSPOT = 30, slave mass/inertia/stiffness distribution to the master node is based on
the Kirschoff model: bi-cubic form functions are used instead of linear (standard
formulation). It allows a softer contact behavior since the element shape curvature is
taken into account in the force/moment transmission.
12. If IDELG = 1, then when a 4-node shell, a 3-node shell or a solid element is deleted, it is
also removed from the master side of the interface (kinematic condition is suppressed on
relative slave nodes).
13. If IFILT is set to 1, the normal and tangential stresses are filtered with an alpha filter, as
follows:
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
FRIC DAT C1 C2 C3 C4 C5 C6
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PC ONT 34
PC NTX5 34
Field Contents
Default = 0 (Integer)
0 - No closure
1 - Closure
0 - No deletion.
1 - When all the elements (shells, solids) associated to one segment are
deleted, the segment is removed from the master side of the interface.
Additionally, non-connected nodes are removed from the slave side of
the interface.
IRM Renumbering flag for segments of the master surface (Integer = 0, 1, 2).
0 - No action.
3 - Change slave node coordinates to avoid small initial penetrations.
4 - Change master node coordinates to avoid small initial penetrations.
Invalid entries are ignored.
NO - No filter is used.
SIMP - Simple numerical filter.
PER - Standard -3dB filter with filtering period.
CUTF - Standard -3dB filter with cutting frequency.
FRICDAT FRICDAT flag indicates that additional information for IFRIC will follow.
Only available when IFRIC = GEN, DARM or REN.
C1, C2, C3, Coefficients to define variable friction coefficient in IFRIC = GEN, DARM,
C4, C5, C6 REN.
Comments
1. The property identification number must be that of an existing PCONT bulk data entry.
Only one PCNTX5 property extension can be associated with a particular PCONT.
2. PCNTX5 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM or IMPDYN. It is ignored for all other subcases.
4. In implicit analysis, different contact formulations are used for contact where slave and
master set do not overlap and where they overlap (self-contact).
In the case of self-contact, the gap cannot be zero and a constant gap is used. For
small initial gaps, the convergence will be more stable and faster if GAP is larger than the
initial gap.
In implicit analysis, sometimes a stiffness with scaling factor reduction (for example,
STFAC = 0.01) or reduction in impacted thickness (if rigid one) might reduce unbalanced
forces and improve convergence, particularly in shell structures under bending where the
effective stiffness is much lower than membrane stiffness; but it should be noted that too
low of a value could also lead to divergence.
6. INACTI = 3, 4 are only recommended for small initial penetrations and should be used with
caution because:
For IFRIC > 0 the friction coefficient is set by a function (µ = µ (p, V)), where p is the
pressure of the normal force on the master segment and V is the tangential velocity of
the slave node.
µ = FRIC + C1 * p + C2 * V + C3 * p * v + C4 * p2 + C5 * v2
0 < V < C5
C6 < V
where:
The static friction coefficient C1 and the dynamic friction coefficient C2, must be lower
than the maximum friction C3 (C1 < C3 and C2 < C3).
The minimum friction coefficient C4, must be lower than the static friction coefficient
C1 and the dynamic friction coefficient C2 (C4 < C1 and C4 < C2).
8. IFILT defines the method for computing the friction filtering coefficient. If IFILT NO,
the tangential friction forces are smoothed using a filter:
F T = α * F'T + (1 - α) * F'T-1
where,
F T - Tangential force
α - filtering coefficient
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PC NTX7 PID
C URVDA G1 G2
T
FRIC DAT C1 C2 C3 C4 C5 C6
Example
PC ONT 34
PC NTX7 34
Field Contents
Default = 0.
0 - No heat transfer.
VAR, VAR2, VAR3 - Gap is variable (in space, not in time) according to
the characteristics of the impacting surfaces and nodes (See comment
7).
Default = 0 (Integer).
0 - No closure.
1 - Closure.
0 - No deletion.
1 - When all the elements (shells, solids) associated to one segment are
deleted, the segment is removed from the master side of the interface.
Additionally, non-connected nodes are removed from the slave side of
the interface.
Integer 0, ..., 3.
0 - No curvature.
1 - Spherical curvature.
2 - Cylindrical curvature.
IADM Computing local curvature flag for adaptive meshing (See comments 9
and 10).
0 - Not activated.
GAPFAC Gap scale factor (used only when IGAP = VAR2 and VAR3).
GAPMAX Maximum gap (used only when IGAP = VAR2 and VAR3).
(Real)
IREMGAP Flag to deactivate slave nodes if element size < gap value, in case of
self-impact contact (See comment 20).
Default = 1 (Integer)
0 - No action.
1 - Deactivation of stiffness on nodes.
2 - Deactivation of stiffness on elements.
3 - Change slave node coordinates to avoid small initial penetrations.
gap0 = gap - P0
NO - No filter is used.
SIMP - Simple numerical filter.
PER - Standard -3dB filter with filtering period.
CUTF - Standard -3dB filter with cutting frequency.
No default (Integer)
CURVDAT CURVDAT flag indicates that additional information about ICURV will
follow. Only available when ICURV = 1 or 2.
(Integer)
G2 Second grid identifier (used only when ICURV = 2, ignored when ICURV =
1)
(Integer)
FRICDAT FRICDAT flag indicates that additional information for IFRIC will follow.
Only available when IFRIC = GEN, DARM or REN.
C1, C2, C3, Coefficients to define variable friction coefficient in IFRIC = GEN, DARM,
C4, C5, C6 REN.
ADMDAT ADMDAT flag indicates that additional information about IADM will follow.
Only available when IADM = 2.
NRADM Number of elements through a 90 degree radius 3 (used only when IADM
= 2)
(Integer)
PADM Criteria on the percentage of penetration (used only when IADM = 2).
(Real)
THEDAT THEDAT flag indicates that additional information about ITHE will follow.
Only available when ITHE = 1.
RTHE Heat conduction coefficient (used only when ITHE = 1, see comment 18)
(Real).
(Real)
ITHEF Heat contact formulation flag (used only when ITHE = 1, Integer).
No default (Real)
DRAD Maximum distance for radiation computation (used only when ITHE = 1)
No default (Real)
FHEATS Frictional heating factor of the slave (used only when ITHE = 1, see
comment 25)
No default (Real)
FHEATM Frictional heating factor of the master (used only when ITHE = 1, see
comment 25)
No default (Real)
Comments
1. The property identification number must be that of an existing PCONT bulk data entry.
Only one PCNTX7 property extension can be associated with a particular PCONT.
2. PCNTX7 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. If FRIC is not explicitly defined on the PCONTX/PCNTX# entries, the MU1 value on the
CONTACT or PCONT entry is used for FRIC in the /INTER entries for Geometric Nonlinear
Analysis. Otherwise, FRIC on PCONTX/PCNTX# overwrites the MU1 value on CONTACT/
PCONT.
4. In implicit analysis, different contact formulations are used for contact where slave and
master set do not overlap and where they overlap (self-contact).
In the case of self-contact, the gap cannot be zero and a constant gap is used. For
small initial gaps, the convergence will be more stable and faster if GAP is larger than the
In implicit analysis, sometimes a stiffness with scaling factor reduction (for example,
STFAC = 0.01) or reduction in impacted thickness (if rigid one) might reduce unbalanced
forces and improve convergence, particularly in shell structures under bending where the
effective stiffness is much lower than membrane stiffness; but it should be noted that too
low of a value could also lead to divergence.
5.
and/or the slave segment stiffness Ks.
The master stiffness is computed from Km = STFAC * B * S * S/V for solids, Km = 0.5 *
STFAC * E * t for shells.
The slave stiffness is an equivalent nodal stiffness computed as Ks = STFAC * B * V-3 for
solids, Ks = 0.5 * STFAC * E * t for shells.
In these equations, B is the Bulk Modulus, S is the segment area, and V is the volume of a
solid. There is no limitation to the value of stiffness factor (but a value larger than 1.0
can reduce the initial time step).
The interface stiffness is then K = max (STMIN, min (STMAX, K1)) with:
ISTF = 0, K1 = Km
ISTF = 2, K1 = 0.5 * (Km + Ks)
ISTF = 3, K1 = max (Km, Ks)
ISTF = 4, K1 = min (Km, Ks)
ISTF = 5, K1 = Km * Ks / (Km + Ks)
6. The default for the constant gap (IGAP = CONST) is the minimum of:
with:
gs = t/2, t - largest thickness of the shell elements connected to the slave node.
element.
8. If ICURV = 1, a spherical curvature is defined for the gap with node_ID1 (center of the
sphere).
If ICURV = 2, a cylindrical curvature is defined for the gap with node_ID1 and node_ID2
(on the axis of the cylinder).
If ICURV = 3, the master surface shape is obtained with a bicubic interpolation, respecting
continuity of the coordinates and the normal from one segment to the other.
In case of a large change in curvature, this formulation might become unstable (will be
improved in future version).
If the contact occurs in a zone (master side) whose radius of curvature is lower than the
element size (slave side), the element on the slave side will be divided (if not yet at
maximum level).
If the contact occurs in a zone (master side) where the angles between the normals are
greater than Angladm and the percentage of penetration is greater than Padm, the
element on the slave side will be divided (if not yet at maximum level).
11. The coefficients NRADM, PADM, and ANGLADM are used only adaptive meshing and IADM
= 2.
12. If GAPMAX is equal to zero, there is no maximum value for the gap.
13. INACTI = 3, is only recommended for small initial penetrations and should be used with
caution because:
For IFRIC > 0 the friction coefficient is set by a function ( = (p, V)), where p is the
pressure of the normal force on the master segment and V is the tangential velocity of
the slave node.
= FRIC + C1 * p + C2 * V + C3 * p * v + C4 * p2 + C5 * v2
0 < V < C5
C5 < V < C6
C6 < V
where:
The static friction coefficient C1 and the dynamic friction coefficient C2, must be lower
than the maximum friction C3 (C1 < C3) and C2 < C3).
15.
the tangential friction forces are smoothed using a filter:
F T = α * F'T + (1 - α) * F'T-1
where,
F T - Tangential force
α - filtering coefficient
The viscous (total) formulation (IFORM = VISC) computes an adhesive force as:
F adh T
The stiffness (incremental) formulation (IFORM = STIFF) computes an adhesive force as:
F adh = F Told + F T
F T = K * VT * dt
19. Slave segment contact is deactivated when the segment kinematic time step calculated
for this contact is lower than DTMIN.
20. With IREMGAP = 2, this allows the element size < gap values:
21. When SENSID is defined for activation/deactivation of the interface, TSTART and TSTOP
are not taken into account.
22. If FRAD is not equal to zero, and d, the distance from the slave node to the master
segment, is in the range: Gap < d < DRAD, then radiation is calculated. The radiant heat
transfer conductance is calculated as:
Where, is the Stefan Boltzman constant, 1 is the emissivity of the slave surface, and
2 is the emissivity of the master surface.
23. If FRAD is not equals to zero, then the default value of DRAD is calculated as the
maximum of:
25. Frictional energy is converted into heat when heat transfer is activated (ITHE > 0) on the
interface. Options FHEATS and FHEATM are used to control this option.
When FHEATS and FHEATM = 0, the conversion of the frictional sliding energy to heat is
not activated. Non-zero values of FHEATS and FHEATM define the fraction of this energy
which is converted into heat and transferred to the slave and master respectively.
Slave:
Master: (ITHEF=1)
Slave:
Master: (ITHEF=1)
PCNTX11 – Extended Contact (CONTX11) Property type 11 for Geometric Nonlinear Analysis
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PC ONT 34
PC NTX11 34
Field Contents
0 - No deletion.
1 - When all the elements (shells and solids) associated to one segment
are deleted, the segment is removed from the master side of the
interface. Additionally, non-connected nodes are removed from the
slave side of the interface.
STFAC
0 - No action.
1 - Deactivation of stiffness on nodes.
2 - Deactivation of stiffness on elements.
3 - Change slave node coordinates to avoid small initial penetrations.
5 - GAP is a variable with time and initial gap is adjusted as follows:
gap0 = gap - P0
BMULT Sorting factor. Can be used to speed up the sorting algorithm and is
machine-dependent.
Comments
1. The property identification number must be that of an existing PCONT bulk data entry.
Only one PCNTX11 property extension can be associated with a particular PCONT.
2. PCNTX11 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. If FRIC is not explicitly defined on the PCONTX/PCNTX# entries, the MU1 value on the
CONTACT or PCONT entry is used for FRIC in the /INTER entries for Geometric Nonlinear
Analysis. Otherwise, FRIC on PCONTX/PCNTX# overwrites the MU1 value on CONTACT/
PCONT.
4. PCNTX11 defines the properties of contact interface type CONTX11, it describes the edge
to edge or line to line interface. This interface simulates impact between lines, a line can
be a beam or truss element or a shell edge or spring elements. The interface properties
are:
The master stiffness is computed from Km = STFAC * B * S * S/V for solids, Km = 0.5 *
STFAC * E * t for shells.
The slave stiffness is an equivalent nodal stiffness computed as Ks = STFAC * B * V-3 for
solids, Ks = 0.5 * STFAC * E * t for shells.
In these equations, B is the Bulk Modulus, S is the segment area, and V is the volume of a
solid. There is no limitation to the value of stiffness factor (but a value larger than 1.0
can reduce the initial time step).
The interface stiffness is then, K = max (STMIN, min (STMAX, K1)) with:
ISTF = 0, K1 = Km
ISTF = 2, K1 = 0.5 * (Km + Ks)
ISTF = 3, K1 = max (Km, Ks)
ISTF = 4, K1 = min (Km, Ks)
6. The default for the constant gap (IGAP = CONST) is equal to GAP.
with:
element.
8. INACTI = 3, is only recommended for small initial penetrations and should be used with
caution because:
9. The sorting factor BUMULT is used to speed up the sorting algorithm, it is machine
dependent.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
FPENMAX
FRIC DAT C1 C2 C3 C4 C5 C6
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PC ONT 34
PC NTX20 34
Field Contents
IEDGE Flag for edge generation from slave and master surfaces.
NO – No edge generation.
All – All segment edges are included.
BORD – External border of slave and master surface is used.
FEAT – External border as well as features defined by FANG are used.
Default = 91 (Real).
Default = 0 (Integer).
0 - No closure.
1 - Closure.
0 - No deletion.
1 - When all the elements (shells and solids) associated to one segment
are deleted, the segment is removed from the master side of the
FPENMAX Maximum initial penetration factor (0 < FPENMAX < 1) (See comment 8).
0 - No action.
1 - Deactivation of stiffness on nodes.
2 - Deactivation of stiffness on elements.
3 - Change slave node coordinates to avoid small initial penetrations.
5 - Gap is variable with time but initial gap is slightly de-penetrated as
follows:
NO - No filter is used.
SIMP - Simple numerical filter.
PER - Standard -3dB filter with filtering period.
CUTF - Standard -3dB filter with cutting frequency.
FRICDAT FRICDAT flag indicates that additional information for IFRIC will follow.
Only available when IFRIC = GEN, DARM or REN.
C1, C2, C3, Coefficients to define variable friction coefficient in IFRIC = GEN, DARM,
C4, C5, C6 REN.
Comments
1. The property identification number must be that of an existing PCONT bulk data entry.
Only one PCNTX20 property extension can be associated with a particular PCONT.
3. If FRIC is not explicitly defined on the PCONTX/PCNTX# entries, the MU1 value on the
CONTACT or PCONT entry is used for FRIC in the /INTER entries for Geometric Nonlinear
Analysis. Otherwise, FRIC on PCONTX/PCNTX# overwrites the MU1 value on CONTACT/
PCONT.
4. In implicit analysis, different contact formulations are used for contact where slave and
master set do not overlap and where they overlap (self-contact).
In the case of self-contact, the gap cannot be zero and a constant gap is used. For
small initial gaps, the convergence will be more stable and faster if GAP is larger than the
initial gap.
In implicit analysis, sometimes a stiffness with scaling factor reduction (for example,
STFAC = 0.01) or reduction in impacted thickness (if rigid one) might reduce unbalanced
forces and improve convergence, particularly in shell structures under bending where the
effective stiffness is much lower than membrane stiffness; but it should be noted that too
low of a value could also lead to divergence.
5.
and/or the slave segment stiffness Ks.
The master stiffness is computed from Km = STFAC * B * S * S/V for solids, Km = 0.5 *
STFAC * E * t for shells.
The slave stiffness is an equivalent nodal stiffness computed as Ks = STFAC * B * V-3 for
solids, Ks = 0.5 * STFAC * E * t for shells.
In these equations, B is the Bulk Modulus, S is the segment area, and V is the volume of a
solid. There is no limitation to the value of stiffness factor (but a value larger than 1.0
can reduce the initial time step).
The interface stiffness is then K = max (STMIN, min (STMAX, K1)) with:
ISTF = 0, K1 = Km
with:
gs = t/2, t - largest thickness of the shell elements connected to the slave node.
element.
If the slave node is connected to multiple shells and/or beams or trusses, the largest
computed slave gap is used.
8. Maximum penetration value is set as a fraction of the actual gap (including variable gap):
If the initial penetration of a slave node is greater than the calculated maximum value
(Penmax), the node will be deactivated from the interface (node stiffness deactivation).
9. INACTI = 3, is only recommended for small initial penetrations and should be used with
caution because:
p, V
For IFRIC > 0, the friction coefficient is set by a function ( )
µ = FRIC + C1 * p + C2 * V + C3 * p * v + C4 * p2 + C5 * v2
0 < V < C5
C5 < V < C6
C6 < V
where:
The static friction coefficient C1 and the dynamic friction coefficient C2, must be lower
than the maximum friction C3 (C1 < C3 and C2 < C3).
The minimum friction coefficient C4, must be lower than the static friction coefficient
C1 and the dynamic friction coefficient C2 (C4 < C1 and C4 < C2).
11. IFILT defines the method for computing the friction filtering coefficient. If IFILT NO,
the tangential friction forces are smoothed using a filter:
F T = α * F'T + (1 - α) * F'T-1
F T - Tangential force
α - filtering coefficient
The viscous (total) formulation (IFORM = VISC) computes an adhesive force as:
F adh T
The stiffness (incremental) formulation (IFORM = STIFF) computes an adhesive force as:
F adh = F Told + ∆F T
∆F T = K * VT * dt
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PC NTX24 PID
ISTF
GAPMAXs GAPMAXm
FRIC DAT C1 C2 C3 C4 C5 C6
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PC ONT 34
PC NTX24 34
No default (Real)
No default (Real)
IGAP0 Gap modification flag for slave shell nodes on the free edges.
(Integer)
0 - No change
(Integer)
IPENMAX Maximum initial penetration: Penetration higher than this value will not be
taken into account.
(Real)
IPENMIN Minimum initial penetration: Penetration higher than this value will be
(Real)
NO - No filter is used.
SIMP - Simple numerical filter.
PER - Standard -3dB filter with filtering period.
CUTF - Standard -3dB filter with cutting frequency.
No default (Integer)
FRICDAT FRICDAT flag indicates that additional information for IFRIC will follow.
Only available when IFRIC = GEN, DARM or REN.
C1, C2, C3, Coefficients to define variable friction coefficient in IFRIC = GEN, DARM,
C4, C5, C6 REN.
Comments
1. The property identification number must be that of an existing PCONT bulk data entry.
Only one PCNTX24 property extension can be associated with a particular PCONT.
2. PCNTX24 is only supported for geometric nonlinear explicit dynamic analysis subcase
defined by ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. If FRIC is not explicitly defined on the PCONTX/PCNTX# entries, the MU1 value on the
CONTACT or PCONT entry is used for FRIC in the /INTER entries for Geometric Nonlinear
Analysis. Otherwise, FRIC on PCONTX/PCNTX# overwrites the MU1 value on CONTACT/
PCONT.
4. In implicit analysis, different contact formulations are used for contact where slave and
master set do not overlap and where they overlap (self-contact).
In the case of self-contact, the gap cannot be zero and a constant gap is used. For
small initial gaps, the convergence will be more stable and faster if GAP is larger than the
initial gap.
In implicit analysis, sometimes a stiffness with scaling factor reduction (for example,
STFAC = 0.01) or reduction in impacted thickness (if rigid one) might reduce unbalanced
forces and improve convergence, particularly in shell structures under bending where the
effective stiffness is much lower than membrane stiffness; but it should be noted that too
low of a value could also lead to divergence.
The master stiffness is computed from Km = STFAC * B * S * S/V for solids, Km = 0.5 *
STFAC * E * t for shells.
The slave stiffness is an equivalent nodal stiffness computed as Ks = STFAC * B * V-3 for
solids, Ks = 0.5 * STFAC * E * t for shells.
In these equations, B is the Bulk Modulus, S is the segment area, and V is the volume of a
solid. There is no limitation to the value of stiffness factor (but a value larger than 1.0
can reduce the initial time step).
The interface stiffness is then K = max (STMIN, min (STMAX, K1)) with:
ISTF = 0, K1 = Km
ISTF = 2, K1 = 0.5 * (Km + Ks)
ISTF = 3, K1 = max (Km, Ks)
ISTF = 4, K1 = min (Km, Ks)
ISTF = 5, K1 = Km * Ks / (Km + Ks)
6. The gap is computed automatically (similar with IGAP = VAR on PCNTX7) for each impact
as gs + gm;
with:
gs = t/2, t - largest thickness of the shell elements connected to the slave node.
element.
gm and gs are limited separately by GAPMAXm and GAPMAXs before the gap
computation.
8. INACTI = 0 ignores the initial penetrations, but the contacts are not deleted, new
contact will be well detected once the penetrations are disappeared. INACTI = 5 is similar
to the one of interface type 7, but once the initial penetration is gone, the new contact
will be detected using not-adjusted gap (P0 is reset to zero).
where, p is the pressure of the normal force on the master segment and V is the
tangential velocity of the slave node.
FRIC + C1 * p + C2 * V + C3 * p * v + C4 * p2 + C5 * v2
0 < V < C5
C5 < V < C6
C6 < V
where:
The static friction coefficient C1 and the dynamic friction coefficient C2, must be lower
than the maximum friction C3 (C1 < C3 and C2 < C3).
The minimum friction coefficient C4, must be lower than the static friction coefficient
C1 and the dynamic friction coefficient C2 (C4 < C1 and C4 < C2).
10. IFILT defines the method for computing the friction filtering coefficient. If IFILT NO,
the tangential friction forces are smoothed using a filter:
where,
F T - Tangential force
α - filtering coefficient
The viscous (total) formulation (IFORM = VISC) computes an adhesive force as:
F adh T
The stiffness (incremental) formulation (IFORM = STIFF) computes an adhesive force as:
F adh = F Told + ∆F T
∆F T = K * VT * dt
12. When SENSID is defined for activation/deactivation of the interface, TSTART and TSTOP
are not taken into account.
13. When the contact type is the symmetric surface to surface, the output normal contact
forces in TH file are correctly calculated if the two surfaces are well separated.
14. IPEN0 = 0 excludes the initial auto-impacts in the same part (shell and solid elements
only). IPEN0 = 1 takes into account the initial auto-impacts in the same part, but in some
complex situations, wrong initial penetrations might be given.
15. For implicit test: Interface type24 is now only available with SMP. The default of ISTF will
be set to 4. The default INACTI will be set to -1 .
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DS
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
1.0
Field Contents
Real Number - It represents the distance from the shell element reference
plane to the bottom surface of the shell (Default = -0.5 * Thick, Thick
being the composite total thickness (Real or blank)).
No default (Real)
LAM Laminate option. If blank, all plies must be specified and all stiffness
terms are developed. The following options are supported:
SYM: Only plies on the bottom half of the composite lay-up needs to be
specified. These plies are automatically symmetrically reflected to the top
half of the composite and given consecutive numbers from bottom to top.
MEM: All plies must be specified, but only membrane terms MID1 are
developed. Prescribed Z0 is ignored (assumed to be: -0.5* Thick).
BEND: All plies must be specified, but only bending terms MID2 are
developed. Prescribed Z0 is ignored (assumed to be: -0.5* Thick).
SMCORE: All plies must be specified. The last ply specifies core properties
and the previous plies specify face sheet properties. The face sheet
properties are calculated without regard for stacking sequence; half of the
total face sheet thickness is then placed on top of the core, and half is
placed on the bottom, to produce a symmetric laminate. Stiffness of the
core is ignored while its density is included in inertia calculations.
Prescribed Z0 is ignored (assumed to be: -0.5* Thick).
SYMEM: Only plies on the bottom half of the composite lay-up needs to
be specified. These plies are automatically symmetrically reflected to the
top half of the composite and given consecutive numbers from bottom to
top. Only membrane terms are developed for the full laminate. Prescribed
Z0 is ignored (assumed to be: -0.5* Thick).
SYBEND: Only plies on the bottom half of the composite lay-up needs to
be specified. These plies are automatically symmetrically reflected to the
top half of the composite and given consecutive numbers from bottom to
top. Only bending terms are developed for the full laminate. Prescribed
Z0 is ignored (assumed to be: -0.5* Thick).
SYSMEAR: Only plies on the bottom half of the composite lay-up needs to
be specified. These plies are automatically symmetrically reflected to the
top half of the composite and given consecutive numbers from bottom to
top. Stacking sequence is ignored, and MID1 is set equal to MID2 on the
derived equivalent PSHELL, while MID3, MID4, TS/T and 12I/T**3 are set
to zero. Prescribed Z0 is ignored (assumed to be: -0.5* Thick).
Default = blank, that is all plies must be specified (SYM, MEM, BEND,
SMEAR, SMCORE, SYMEM, SYBEND or SYSMEAR)
MIDi Material IDs of individual plies. The plies are identified by consecutively
numbering them from 1 at the bottom layer. The MIDs must refer to
MAT1, MAT2, MAT4, MAT5, or MAT8 bulk data entries. If MIDi is not
specified, default is the last defined MIDi.
Default = last defined MIDi (Integer>0 or blank, except that MID1 must be
specified)
Default = last defined Ti (Real > 0.0 or blank, except that T1 must be
specified)
SOUTi Stress, Strain and Failure Index output request for individual plies. See
comments 2 and 3.
Comments
1. TREF specified on the PCOMP entry overrides reference temperatures given for individual
ply materials. If TREF is not specified (blank) on the PCOMP card, then all the ply
materials must have the same reference temperature.
2. Stress, Strain and Failure Index output for individual plies is activated by setting SOUTi to
YES for a given ply. In addition, the I/O Options CSTRESS (controlling Stress and Failure
Index output) and/or CSTRAIN (controlling Strain output) must be defined. Failure Index
output also requires that the FT and SB fields be defined and that stress/strain allowables
on the referenced materials are defined.
3. An additional piece of information available with ply results is "failure index for the
element," which is the maximum of failure indices for individual plies in this element. Note
that only the plies with SOUTi set to YES are considered in the evaluation of this
maximum.
5. The signs given to stress limits for compression and tension (ST, SC, for MAT1; Xt, Xc,
and so on for MAT8) are of no relevance. Absolute values are taken and used in the
appropriate context to calculate failure indices.
6. For com
bottom and top surfaces of the shell are produced.
7.
This is because the membrane-bending coupling resulting from composite offset is not
included in the differential stiffness matrix. Hence, the preferred method of incorporating
offset in buckling analysis is the element offset ZOFFS.
8. Element GRID thicknesses cannot be defined for elements that reference PCOMP data.
9. Plies are listed from the bottom surface upwards, in respect to the element’s normal
direction. In the image below, (a) shows the stacking sequence for a non-symmetrical
laminate, and (b) shows the stacking sequence for a symmetrical laminate.
10. GE given on the PCOMP entry will be used for the element, and the values supplied on
material entries for individual plies are ignored. You are responsible for supplying the
equivalent damping value on the PCOMP entry.
11. To obtain the damping coefficient GE, multiply the critical damping ratio C/C0 by 2.0.
12. For convenience, element output for the SMEAR and SMCORE options includes both
homogenized shell stresses and individual ply stresses. However, because stacking
sequence is ignored in these options, individual ply stresses will only be valid in cases of
13. Note that Hill’s failure theory does not differentiate between compressive and tensile
strength. Hence, while different values of respective strength limits are accepted, it is
still recommended that Xt is set to be equal to Xc and Yt is set to be equal to Yc when
this criteria is used. Xt and Xc are allowable tensile and compressive stresses in the
principle x direction of the material. Yt and Yc are allowable tensile and compressive
stresses in the principle y direction of the material.
14. Failure index calculation according to Maximum Strain Theory is based on mechanical
component of strain only, not on total strain. This is because only the mechanical strain
contributes to actual damage of the respective ply (pure thermal expansion produces no
damaging effects).
15. According to the formula, some failure criteria (for example, Tsai-Wu and Hoffman) would
produce a negative ply failure, depending on the problem.
16. If ‘PARAM, SRCOMPS, YES’ is added to the input file, strength ratios with respect to
designated failure theory are output for composite elements that have failure indices
requested.
17. The following two formats are permissible for the Z0 field:
Real Number:
It represents the distance from the shell element reference plane to the bottom surface
of the shell (Default = -0.5 * Thick, Thick being the composite total thickness (Real or
blank)).
Surface:
Top:
The shell reference plane, the plane defined by the grid points, and the top surface of the
shell are coplanar.
This makes the effective "Real" Z0 value equal to the composite total thickness (-1.0 *
Thick). See Figure 1.
Bottom:
The shell reference plane, the plane defined by the grid points, and the bottom surface of
the shell are coplanar.
Automatic offset control is available in composite free-size and sizing optimization where
the specified offset values are automatically updated based on thickness changes.
Description
Defines the structure and properties of a composite laminate material, allowing for global ply
identification.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
… … … … …
DS
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
1.0
No default (Real)
LAM Laminate option. If blank, all plies must be specified and all stiffness
terms are developed. The following options are supported:
MEM: All plies must be specified, but only membrane terms MID1 are
developed. Prescribed Z0 is ignored (assumed to be: -0.5* Thick).
BEND: All plies must be specified, but only bending terms MID2 are
developed. Prescribed Z0 is ignored (assumed to be: -0.5* Thick).
SMCORE: All plies must be specified. The last ply specifies core
properties and the previous plies specify face sheet properties. The
face sheet properties are calculated without regard for stacking
sequence; half of the total face sheet thickness is then placed on top
of the core, and half is placed on the bottom, to produce a symmetric
laminate. Stiffness of the core is ignored while its density is included in
inertia calculations. Prescribed Z0 is ignored (assumed to be: -0.5*
Thick).
SYMEM: Only plies on the bottom half of the composite lay-up needs to
be specified. These plies are automatically symmetrically reflected to
the top half of the composite and given consecutive numbers from
bottom to top. Only membrane terms are developed for the full
laminate. Prescribed Z0 is ignored (assumed to be: -0.5* Thick).
SYBEND: Only plies on the bottom half of the composite lay-up needs
to be specified. These plies are automatically symmetrically reflected
to the top half of the composite and given consecutive numbers from
bottom to top. Only bending terms are developed for the full laminate.
Prescribed Z0 is ignored (assumed to be: -0.5* Thick).
SYSMEAR: Only plies on the bottom half of the composite lay-up needs
to be specified. These plies are automatically symmetrically reflected
to the top half of the composite and given consecutive numbers from
bottom to top. Stacking sequence is ignored, and MID1 is set equal to
MID2 on the derived equivalent PSHELL, while MID3, MID4, TS/T and
12I/T**3 are set to zero. Prescribed Z0 is ignored (assumed to be: -
0.5* Thick).
Default = blank, that is all plies must be specified (SYM, MEM, BEND,
SMEAR, SMCORE, SYMEM, SYBEND or SYSMEAR)
MID# Material IDs of individual plies. The plies are identified by consecutively
numbering them from 1 at the bottom layer. The MIDs must refer to
MAT1, MAT2, MAT4, MAT5, or MAT8 bulk data entries. If MID# is not
specified, default is the last defined MID#.
Default = last defined MID# (Integer > 0 or blank, except that MID1
must be specified)
Default = last defined T# (Real > 0.0 or blank, except that T1 must be
specified)
SOUT# Stress and failure index output request for individual plies. See
comments 2 and 3.
Comments
1. TREF specified on the PCOMPG entry overrides reference temperatures given for individual
ply materials. If TREF is not specified (blank) on the PCOMPG card, then all the ply
materials must have the same reference temperature.
2. For SOUTi to take effect, CSTRESS must be requested in the I/O options section of the
input deck. Individual ply results will be available in addition to shell stresses and strains
3. An additional piece of information available with ply results is "failure index for the
element", which is the maximum of failure indices for individual plies in this element. Note
that only the plies with SOUTi set to YES are considered in the evaluation of this
maximum.
4. If all plies specify zero transverse shear coefficients (G1Z, G2Z on MAT8 card, isotropic G
for MAT1, not available for MAT2), the in-plane shear modulus will be used to determine
transverse shear stiffness of the composite.
5. The signs given to stress limits for compression and tension (ST, SC, for MAT1; Xt, Xc,
and so on for MAT8) are of no relevance. Absolute values are taken and used in the
appropriate context to calculate failure indices.
6.
bottom and top surfaces of the shell are produced.
7.
This is because the membrane-bending coupling resulting from composite offset is not
included in the differential stiffness matrix. Hence, the preferred method of incorporating
offset in buckling analysis is the element offset ZOFFS.
8. Element GRID thicknesses cannot be defined for elements that reference PCOMPG data.
9. Plies are listed from the bottom surface upwards, in respect to the element’s normal
direction. The image below shows the stacking sequence for a non-symmetrical
laminate.
10. GE given on the PCOMP entry will be used for the element, and the values supplied on
material entries for individual plies are ignored. You are responsible for supplying the
equivalent damping value on the PCOMPG entry.
12. The global ply identification number must be unique with respect to other plies in the
entry.
13. For convenience, element output for the SMEAR and SMCORE options includes both
homogenized shell stresses and individual ply stresses. However, because stacking
sequence is ignored in these options, individual ply stresses will only be valid in cases of
pure membrane deformation.
14. Note that Hill’s failure theory does not differentiate between compressive and tensile
strength. Hence, while different values of respective strength limits are accepted, it is
still recommended that Xt is set to be equal to Xc and Yt is set to be equal to Yc when
this criteria is used. Xt and Xc are allowable tensile and compressive stresses in the
principle x direction of the material. Yt and Yc are allowable tensile and compressive
stresses in the principle y direction of the material.
15. Failure index calculation according to Maximum Strain Theory is based on mechanical
component of strain only, not on total strain. This is because only the mechanical strain
contributes to actual damage of the respective ply (pure thermal expansion produces no
damaging effects).
16. According to the formula, some failure criteria (for example, Tsai-Wu and Hoffman) would
produce a negative ply failure, depending on the problem.
17. If ‘PARAM, SRCOMPS, YES’ is added to the input file, strength ratios with respect to
designated failure theory are output for composite elements that have failure indices
requested.
18. The following two formats are permissible for the Z0 field:
Real Number:
It represents the distance from the shell element reference plane to the bottom surface
of the shell (Default = -0.5 * Thick, Thick being the composite total thickness (Real or
blank)).
Surface:
Top:
The shell reference plane, the plane defined by the grid points, and the top surface of the
shell are coplanar.
This makes the effective "Real" Z0 value equal to the composite total thickness (-1.0 *
Thick). See Figure 1.
Bottom:
The shell reference plane, the plane defined by the grid points, and the bottom surface of
the shell are coplanar.
Automatic offset control is available in composite free-size and sizing optimization where
the specified offset values are automatically updated based on thickness changes.
Description
Defines the properties of a composite laminate material used in ply-based composite definition.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Real)
Comments
1. The PCOMPP card is used in combination with the STACK and PLY cards to create
composite properties through the ply-based definition.
2. TREF specified on the PCOMPP entry overrides reference temperatures given for individual
ply materials. If TREF is not specified (blank) on the PCOMPP card, then all the ply
materials must have the same reference temperature.
3.
bottom and top surfaces of the shell are produced.
4.
correct. This is because the membrane-bending coupling resulting from composite offset
is not included in the differential stiffness matrix. Hence, the preferred method of
incorporating offset in buckling analysis is the element offset ZOFFS.
5. Element GRID thicknesses cannot be defined for elements that reference PCOMPP data.
6. GE given on the PCOMPP entry will be used for the element, and the values supplied on
material entries for individual plies are ignored. You are responsible for supplying the
equivalent damping value on the PCOMPP entry.
8. Note that Hill’s failure theory does not differentiate between compressive and tensile
strength. Hence, while different values of respective strength limits are accepted, it is
still recommended that Xt is set to be equal to Xc and Yt is set to be equal to Yc when
this criteria is used. Xt and Xc are allowable tensile and compressive stresses in the
principle x direction of the material. Yt and Yc are allowable tensile and compressive
stresses in the principle y direction of the material.
10. According to the formula, some failure criteria (for example, Tsai-Wu and Hoffman) would
produce a negative ply failure, depending on the problem.
11. If ‘PARAM, SRCOMPS, YES’ is added to the input file, strength ratios with respect to
designated failure theory are output for composite elements that have failure indices
requested.
12. The following two formats are permissible for the Z0 field:
Real Number:
It represents the distance from the shell element reference plane to the bottom surface
of the shell (Default = -0.5 * Thick, Thick being the composite total thickness (Real or
blank)).
Surface:
Top:
The shell reference plane, the plane defined by the grid points, and the top surface of the
shell are coplanar.
This makes the effective "Real" Z0 value equal to the composite total thickness (-1.0 *
Thick). See Figure 1.
Bottom:
The shell reference plane, the plane defined by the grid points, and the bottom surface of
Automatic offset control is available in composite free-size and sizing optimization where
the specified offset values are automatically updated based on thickness changes.
PCOMPX – Optional Composite Laminate Property Extension for Geometric Nonlinear Analysis
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DM DN ITHIC K IPLAS
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PC OMP 73
PC OMPX 73 24
Field Contents
IPLAS Flag for shell plane stress plasticity (with MATX27 only).
Comments
2. PCOMPX is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
4. If the small strain option (ISMSTR) is set to 1 or 3, engineering strain and stress are
used; otherwise they are true strain and stress.
6. If ITHICK = VAR or IPLAS = NEWT, the small strain option is automatically deactivated.
QEPH 24 1.5%
QBAT 12 0%
QEPH 24 1.5%
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
FRIC ESL
Examples
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PC ONT 34 STIC K
Field Contents
GPAD “Padding” of the interface to account for additional layers, such as shell
thickness. This value is subtracted from the contact gap opening as
calculated from the location of nodes. See comment 1.
CLEARANCE Prescribed initial gap opening between master and slave, irrespective of
the actual distance between the nodes. See comment 11.
Comments
1. The initial contact gap opening is calculated automatically based on the relative location
of slave and master nodes (in the original, undeformed mesh). To account for additional
material layers covering master and slave objects, the GPAD entry can be used. GPAD
option THICK automatically accounts for shell thickness on both sides of the contact
interface (this also includes the effects of shell element offset ZOFFS or composite offset
Z0).
2. Option STIFF=AUTO determines the value of normal stiffness for each contact element
using the stiffness of surrounding elements. Additional options SOFT and HARD create
respectively softer or harder penalties. SOFT can be used in cases of convergence
difficulties and HARD can be used if undesirable penetration is detected in the solution.
4. Prescribing MU1=FREEZE enforces zero relative motion on the contact surface – the
contact gap opening remains fixed at the original value and the sliding distance is zero.
Also, rotations at the slave node are matched to the rotations of the master patch. The
If FRIC is not explicitly defined on the PCONTX/PCNTX# entries, the MU1 value on the
CONTACT or PCONT entry is used for FRIC in the /INTER entries for Geometric Nonlinear
Analysis. Otherwise, FRIC on PCONTX/PCNTX# overwrites the MU1 value on CONTACT/
PCONT.
The CONTACT force displacement behavior in nonlinear analysis is illustrated in the figure
below. While the contact is open, its normal stiffness is essentially zero (a small value of
KB =10-14 *STIFF is used to avoid singularities). When the contact element closes, the
stiffness becomes STIFF.
6. When contact is open, there is no transverse stiffness. When the contact is closed,
friction is activated and the contact has stiffness KT=mu1*STIFF in the transverse
direction (KT=0.1*STIFF in case of STICK). This acts as a linear spring in linear solution
sequences. For nonlinear solution sequences, frictional force increases with sliding
distance in proportion to KT until it reaches static friction force MU1 * Fx, Fx being the
normal force in the contact element. With further transverse deformation, friction
becomes kinetic and the friction force is MU2 * Fx. See the figure below for a one-
dimensional illustration.
Note that the nonlinear contact element's force-displacement behavior may produce
negative contributions to the compliance of the structure. As an example, when slave
and master bodies have initial overlap and the contact releases elastic energy during the
solution.
7. Effective in Release 12.0, two models of friction are available in nonlinear analysis:
This latter model typically shows better performance in solution of frictional problems
thanks to more stable handling of transitions from stick to slip. Key differences between
the two available models are illustrated in the figure below (F 1 and F 2 represent two
different values of normal force F x ):
Model (a), based on fixed stiffness KT, is relatively simple, yet has certain drawback in
modeling nonlinear friction. Namely, in Coulomb friction the frictional resistance depends
upon normal force. Using fixed KT will predict different range of stick/slip boundary for
different normal forces, and thus may qualify the same configuration as stick or slip,
depending on normal force.
Model (b), based on Elastic Slip Distance, provides unique identification of stick or slip
and generally performs better in solution of problems with friction. This model does
require prescribing elastic slip distance FRICESL – for contact interfaces this value is
determined automatically as 0.5% of typical element size on all Master contact
surfaces.
The model (b), which is currently the default, is recommended for solution of nonlinear
problems with friction. For backwards compatibility, the model based on fixed KT can be
activated by prescribing FRICESL=0 on PCONT or CONTPRM card.
8. The model of friction in OptiStruct is relatively simple. The frictional force is always
directed back to the point where the slave and master first came into contact (changed
status from open to closed). Its location is estimated using proportional interpolation
between the current position and the last converged solution before penetration.
OptiStruct CONTACT should not be used for modeling frictional problems with complex
deformation paths and changing sliding directions.
9. The presence of friction can introduce moment loadings and counter-intuitive results into
the problem by way of frictional offset. The reason for this is that, for contact elements
with non-zero length (distance between slave node and master segment), the actual
location of the contact interface is presumed to be in the middle of the contact element’s
length (see figure below).
The frictional forces act along this contact surface. Transferring these forces to the
slave and master objects requires an offset operation that produces both forces and
moments at slave and master. Similarly, the sliding distance at the contact interface is a
result of nodal displacements and rotations of the slave node and master segment (see
figure below).
Master segments, which consist of several nodes, can effectively resist these offset
forces and moments. However, for slave bodies that do not support moments (nodes of
solid elements, for example), this offset may render friction ineffective because the free
rotations at slave nodes offer no effective resistance to friction. With the stick condition
formally satisfied, for example, slave and master can move relative to each other (see
figure below).
In practice, for contact interfaces that are initially open, AUTOSPC will effectively fix
respective unsupported rotations. However, for contacts that are initially closed (for
example, pre-penetrating contact with MORIENT=NORMAL) the frictional terms will
prevent AUTOSPC from being effective. Hence, respective SPC on rotations need to be
applied manually to respective slave nodes.
Effective in the Release 12.0, to avoid such counter-intuitive behavior, the frictional
offset operation is by default turned off if the model involves friction or stick and contains
at least one nonlinear subcase (of NLSTAT type). (Note that for consistency, this affects
both linear and nonlinear contact elements.) This produces more intuitive results with
friction. However, it may violate the rigid body balance of the body.
The above default setting can be changed via the GAPOFFS command on the GAPPRM
card.
10. The presence of friction, due to its strongly nonlinear, non-conservative nature, may
cause difficulties in nonlinear convergence, especially when sliding is present. If frictional
resistance is essential to the solution of the problem and convergence problems are
encountered, enforcing the stick condition (by prescribing KT>0 and MU=0) may be a
viable solution that will often result in better convergence than with Coulomb friction.
Note however, that this only applies to problems in which minimal sliding is expected. In
the case of larger sliding motions, the stick condition may lead to divergence through a
"tumbling" mode.
11. Prescribing CLEARANCE overrides the default contact behavior of calculating initial gap
opening from the actual distance between Slave and Master. CLEARANCE now becomes
the distance that Slave and Master have to move towards each other in order to close
the contact. Negative value of CLEARANCE means that the bodies have initial pre-
penetration.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Examples
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PC ONTHT 2 1E6
PC ONTHT 2 AUTO
PC ONTHT 2 10
Clearance and pressure based conductivity for contact (see comments 3 and 4):
PC ONTHT 2 1E6 10 20
Field Contents
PID Property identification number. Must match with a PID of a PCONT bulk
data entry. See comment 1.
Default = 10-14 * KC (Real > 0.0) This default is also set when KO =0.
Comments
1. PCONTHT provides heat transfer conductivity for CONTACT element. PCONTHT must
match PID with an existing PCONT.
2. KC and KO represent conductivity values for closed and open contacts. Theoretically,
while higher conductivity values enforce a perfect conductor, excessively high values may
cause poor conditioning of the conductivity matrix. If any such symptoms are observed,
it may be beneficial to reduce the value of conductivity, or use conductivity based
contact clearance and pressure.
Option KC=AUTO determines the value of KC for each contact element using the
conductivity of surrounding elements.
3. TPID points to a TABLED# entry that specifies conductivity based on contact pressure.
TPID overrides KC.
4. TCID points to a TABLED# entry that specifies contact based on contact clearance. TCID
overrides KO. TPID can be specified together with TCID. When TPID is specified together
with TCID, conductivity is determined from the table with TCID for open contact, and
from the table with TPID for closed contact.
6. Thermal-structural analysis problems involving contact are fully coupled since contact/gap
status changes thermal conductivity. Refer to Contact-based Thermal Analysis in the
User’s Guide for more information.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TSTART TEND
C1 C2 C3 C4 C5 C6
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PC ONT 34
PC ONTX 34
Field Contents
0 - No deletion.
1 - When all the elements (shells, solids) associated to one segment are
deleted, the segment is removed from the master side of the interface.
Additionally, non-connected nodes are removed from the slave side of
the interface.
0 - No action.
1 - Deactivation of stiffness on nodes.
2 - Deactivation of stiffness on elements.
3 - Change slave node coordinates to avoid small initial penetrations.
4 - Change master node coordinates to avoid small initial penetrations.
5 - Gap is variable with time but initial gap is slightly de-penetrated as
follows:
IEDGE Flag for edge generation from slave and master surfaces.
NO – No edge generation.
All – All segment edges are included.
BORD – External border of slave and master surface is used.
FEAT – External border as well as features defined by FANG are used.
FANG Feature angle for edge generation (Only with IEDGE = FEAT).
MULTIMP Maximum average number of impacted master segments per slave node
NO - No filter is used.
SIMP - Simple numerical filter.
PER - Standard -3dB filter with filtering period.
CUTF - Standard -3dB filter with cutting frequency.
C1, C2, C3, Coefficients to define variable friction coefficient in IFRIC = GEN, DARM,
C4, C5, C6 REN.
Comments
1. The property identification number must be that of an existing PCONT bulk data entry.
Only one PCONTX property extension can be associated with a particular PCONT.
2. PCONTX is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. If FRIC is not explicitly defined on the PCONTX/PCNTX# entries, the MU1 value on the
CONTACT or PCONT entry is used for FRIC in the /INTER entries for Geometric Nonlinear
Analysis. Otherwise, FRIC on PCONTX/PCNTX# overwrites the MU1 value on CONTACT/
PCONT.
4. In implicit analysis, different contact formulations are used for contact where slave and
master set do not overlap and where they overlap (self-contact).
In the case of self-contact, the gap cannot be zero and a constant gap is used. For
small initial gaps, the convergence will be more stable and faster if GAP is larger than the
initial gap.
In implicit analysis, sometimes a stiffness with scaling factor reduction (for example,
STFAC = 0.01) or reduction in impacted thickness (if rigid one) might reduce unbalanced
forces and improve convergence, particularly in shell structures under bending where the
effective stiffness is much lower than membrane stiffness; but it should be noted that too
low of a value could also lead to divergence.
5.
and/or the slave segment stiffness Ks.
The master stiffness is computed from Km = STFAC * B * S * S/V for solids, Km = 0.5 *
STFAC * E * t for shells.
The interface stiffness is then K = max (STMIN, min (STMAX, K1)) with
ISTF = 0, K1 = Km
ISTF = 2, K1 = 0.5 * (Km + Ks)
6. The default for the constant gap (IGAP = CONST) is the minimum of
lmin/2, lmin – smallest side length of all master segments (shell or solid).
with:
gs = 0 if the slave node is not connected to any element or is only connected to solid or
spring elements.
gs = t/2, t - largest thickness of the shell elements connected to the slave node.
If the slave node is connected to multiple shells and/or beams or trusses, the largest
computed slave gap is used.
8. INACTI = 3, 4 are only recommended for small initial penetrations and should be used with
caution because:
For IFRIC > 0 the friction coefficient is set by a function (m = m (p, V)), where p is the
pressure of the normal force on the master segment and V is the tangential velocity of
the slave node.
m = FRIC + C1 * p + C2 * V + C3 * p * v + C4 * p2 + C5 * v2
0 < V < C5
C5 < V < C6
C6 < V
where:
The static friction coefficient C1 and the dynamic friction coefficient C2, must be lower
than the maximum friction C3 (C1 < C3) and C2 < C3).
The minimum friction coefficient C4, must be lower than the static friction coefficient
C1 and the dynamic friction coefficient C2 (C4 < C1 and C4 < C2).
F adh T
F adh = F T old + ∆F T
∆F T = K * VT * dt
11.
the tangential friction forces are smoothed using a filter:
F T = α * F'T + (1 - α) * F'T - 1
where,
F T - Tangential force
α - filtering coefficient
Description
Defines a free convection boundary condition properties.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
Comments
q = H * (T - TAMB)E XP F * (T - TAMB)
If FORM = 1, 11, 21
q = H * (T E XP F - TAMBE XP F ))
q = H * (T-TAMB)
Description
Specifies the damping of a scalar damper element using defined CDAMP1 or CDAMP3 entry.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Real)
Comments
1. Damping values are defined directly on the CDAMP2 entry and therefore do not require a
PDAMP entry.
2. A structural viscous damper, CVISC, may also be used for geometric grid points.
Description
Defines criteria used for the automatic identification of loading frequencies at which result
peaks occur. Other result output may then be requested at these “peak” loading frequencies.
This feature is only supported for frequency response solution sequences.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PEAKOUT SID NPEAK NEAR FAR LFREQ HFREQ RTYPE PSC ALE
... ...
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
GRIDC 65 1 11 66 1 10
67 1 11 68 1 11
Field Contents
NEAR Minimum allowed distance between two peaks. If two peaks are closer
than this value, the loading frequency of the lower peak will be ignored.
See comment 2.
FAR Maximum allowed distance between two peaks. Additional peaks will be
selected (in addition to NPEAK) if the distance between the peaks is
greater than this value. See comment 2.
RTYPE Result type for peak identification for the structural domain.
PSCALE Pressure scaling method for peak identification for the fluid domain.
The result for a fluid grid can be the scale of pressure, decibels (DB) or A-
weighted decibels (DBA). See comment 3 for decibel calculations and
reference pressure settings. For DBA, standard A-weighting is used.
CUTOFF# The cutoff value can be a real value or an integer value. See comment 2.
If the entry is a real value, then this is the value of the cutoff (in the
same unit specified by RTYPE and PSCALE).
Comments
2. The following example shows how the different criteria work in identifying peaks.
In order to ensure that peaks are neither too far apart nor too close together, the FAR
and NEAR criteria, respectively, may be used.
In the above example, should a value of 50HZ be defined for FAR, P4 would be selected in
addition to the other peaks because D2 (~54 Hz) is greater than 50Hz, and so an
additional peak is required to satisfy the FAR criterion.
Similarly, should a value of 15Hz be defined for NEAR, then P2 will be omitted, as D1 (~11
Hz) is less than 15Hz.
3. The dB value is calculated using 20 * log10 (P/P0), where P0 is the reference pressure.
The reference pressure is dependent on the units specified on the UNITS input data. If
the units are SI, the value is set as 2.0E-5 Pa. If they are CGS, it is set as 2.0E-4 barye.
If they are MPa, it is set as 2.0E-11 MPa. If they are BG or EE, then it is set as 4.17E-7
lbf/ft 2. If no UNITS data is present, the default value is 2.0E-11 MPa.
4. If you wish to include interior points of a superelement (in a CMS model) for the purposes
of peak identification using the PEAKOUT bulk data entry, the SEINTPNT entry can be
used in the subcase information section to convert the interior grid points to exterior grid
points (since points referenced by PEAKOUT should be exterior points only).
Description
Used to define the stiffness and stress coefficient of a scalar elastic element (spring) by
means of the CELAS1 or CELAS3 entry.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Real)
S Stress coefficient.
3. To obtain the damping coefficient GE, multiply the critical damping ratio, C/C0, by 2.
F = k * (u1 – u2)
Where, k is the stiffness coefficient for the scalar element and u1 is the displacement of
the first degree-of-freedom listed on the CELAS entry. Element stresses are calculated
from the equation: s = S * F, where, S is the stress coefficient as defined above.
Description
Defines the frequency dependent property values for a PELAS bulk data entry.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
PID Property identification number. Must match with a PID of a PELAS bulk data
entry.
TKID Identification number of a TABLED# entry that defines the force per unit
displacement versus frequency relationship.
TGEID Identification number of a TABLED# entry that defines the element structural
damping coefficient versus frequency relationship.
TKNID Identification number of a TABLED# entry that defines the nonlinear force
versus displacement relationship.
Comments
2. PELAST is ignored in all solution sequences except frequency response analysis. Nominal
values from the PELAS entry are used in all the analyses except frequency response
analysis.
Description
The PERBC bulk data entry can be used to define a connection between opposite edges/faces
of the structure. This entry is used to apply Periodic Boundary Conditions to the model.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PERBC 2 45 32 0.01
Field Contents
(Integer > 0)
GSID Identification number of a SET of grid points on one side of the structure.
(Integer > 0)
RLID Identification number of a RELOC bulk data entry that maps the nodes on one
side of the structure to the other. An exact one-to-one match between the two
sides is required.
(Integer > 0)
TOL Specifies the numeric value defining the maximum distance between two grid
points to allow equivalence. All grid points in the set defined by GSID and the
set of grid points on the other side of the structure (mapping defined by the
RELOC entry) are considered for equivalence based on the tolerance.
1. The PERBC entry can be used to apply periodic boundary conditions, to match results
from one side of the structure to another.
2. The referenced RELOC Bulk Data Entry should be defined with TYPE=MOVE or
TYPE=ROTATE. For TYPE=ROTATE, a simple rotation about a single axis should only be
defined. All grids on one side of the structure (defined via GSID) and matching grids on
the other side should cannot have a coordinate system (Field CD on GRID entry) defined.
If RELOC(ROTATE) is specified, then all matching grids will have CD assigned automatically
to match the structure.
3. Periodic Boundary Conditions are supported for all solution sequences (except OptiStruct-
Multi-body Dynamics (OS-MBD) and Geometric Nonlinear Analysis (ANALYSIS=NLGEOM/
IMPDYN/EXPDYN)) and all optimization types. In shape optimization, when GRID’s identified
on the PERBC entry are in or near the optimized zone, their location changes should be
properly linked through DVGRID, otherwise the results may be incorrect.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
0.8
Field Contents
MFLAG Flag to indicate how the coordinate system specified by MCID will be
used.
Default = 0 (Integer)
GE Structural damping.
Comments
1. For a CFAST element, no material needs to be specified in the corresponding PFAST card
- the stiffness of the element is directly specified in the PFAST card with KTi and KRi
entries.
2. The diameter D will not be involved in the stiffness calculation directly. It is used along
with GA and GB to find appropriate auxiliary points and related shell elements and grids. In
this case, the stiffness contribution of the fastener depends not only on the stiffness
values specified for KTi and KRi, but also the diameter D, because the location of the
auxiliary points will be used to weight the contribution of the shell element grids to GA and
GB of the fastener.
3. Element stiffness coordinate system. The three stiffness values KT1, KT2 and KT3 will be
applied along the three axes of the element coordinate system. The unit vectors of the
three axes are denoted as e1, e2 and e3.
e2 is defined as being perpendicular to e1 and lined up with the closest axis of the basic
system. This is accomplished by taking the inner product of e1 with the basic system unit
vectors. The smallest will define the basic system direction which is closest to the plane
e3 = e1 x e2
The T2 direction specified by MCID will be used to define the orientation vector v of the
fastener.
At last, the e2 can be easily calculated by the cross product of e3 and e1 as follows:
e2 = e3 x e1
c)
used directly as e1, e2 and e3. The element forces will be computed in the coordinate
system defined in comment 3(a).
d) If MCID refers to a cylindrical or spherical coordinate system, the local origin used to
locate the system is selected as follow: (i) if GA of the CFAST is specified, use GA as
the local origin; (ii) if GA is not specified but GS is specified, use GS as the local origin;
(iii) if neither GA nor GS is specified, use the point (XS, YS, ZS) as the local origin.
4. The final length of the CFAST element is defined by the distance between GA and GB. If
the length is zero, the normal to shell patch A is used to define the axis of the fastener.
5. For the mass of the fastener, half of the value defined in the MASS entry is placed
directly onto the translational degrees-of-freedom of GA and GB. Then they are
distributed, via auxiliary points, to corresponding shell grids. As the result, while the mass
will be represented correctly for general representation of the fastener in the vibrations of
the structure, the moments of inertia relative to the local axes of the fastener will only be
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
ID Each PFAT card must have a unique ID. This ID may be referenced from a
FATDEF definition.
When it is a float value, it will be used to modify the fatigue limit by multiplied
with the original fatigue limit.
Treatment Material Surface Treatment for Material S-N Curve, a process used to enhance
the fatigue life. See comment 3.
When it is a float value, it will be used to modify the fatigue limit by multiplied
with the original fatigue limit.
1. If shell elements are used, it is necessary to specify the appropriate layer or Surface of
results to use Top or Bottom. Worst is the worst result of Top and Bottom (the one with
larger damage).
2. Fatigue strength reduction factor takes into account the effect of notch effects, size
effects, and loading type influence,
where, Cnotch , Csize, and Cloading are correction factors for notch effect, size effect, and
loading type influence.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PFPATH 10 11 12 DISP 18 23
RPTYPE DISP/VELO/ACCE Criterion for the type of the response; the response type
corresponding to a structural degree of freedom could be
displacement, velocity or acceleration.
Default = DISP
Comments
2. If CONREL is specified in the 7th entry, the RIGID element IDs must be unique.
Description
Defines a flexible body out of a list of finite element properties, elements, and grid points.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ID8 …
TYPE# …
FLXNODE NOAUTO/C 1 G1 G2 G3 G4 G5 G6
FLXNODE C2 G8 G9 …
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PFBODY 3 C ontrol_arm
PSHELL 23 21
PBEAM 9 59 48
C ONM2 2345
C MS CB 50
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PFBODY 3 Linkage
PSOLID 13 15
C MS CB 2000.0
FLXNODE NOAUTO
FLXNODE 123456 11 12 13
Field Contents
This name is used as the Flex H3D file name to which the reduced
flexible body information will be written out for the PFBODY.
TYPE# Flag indicating that the following list of IDs refer to entities of this
type. All property definitions; CELAS2, CONM2, PLOTEL, RBE2, RBE3,
RBAR, RROD, and GRID are valid types for this field.
CMS CMS flag indicating that information on the method used for reducing
the flexible body is to follow.
CB - Craig-Bampton
CC - Craig-Chang
UB_FREQ Upper bound frequency for the eigenvalue analysis. If 0.0 or blank, no
FLXNODE FLXNODE flag indicating that flexible body interface node information is
to follow. See comment 11.
NOAUTO NOAUTO flag to not automatically determine the interface nodes for the
flexible body.
No default (up to 6 unique digits (0 < digit < 6) may be placed in the
field with no embedded blanks)
(Integer > 0)
Comments
3. Any number of property definitions; CELAS2, CONM2, PLOTEL, RBAR, RBE2, RBE3 or RROD
elements or grid points can be given.
5. A property definition; CELAS2, CONM2, PLOTEL, RBE2, RBE3, RBAR or RROD element or grid
point can only belong to one body (flexible or rigid).
6. All property definitions, elements and grid points defined on a PFBODY bulk data entry
form one flexible body.
7. CMS definition defines the component mode synthesis method to reduce the flexible body
for the multi-body analysis. Exactly one must be defined for each PFBODY.
9. When UB_FREQ = 0.0 and NMODES = 0, this is a special case where no eigen modes will
be included in CMS mode generation.
10. If FLXNODE is not defined, a default set of interface nodes and degrees-of-freedom. will
be generated based on the actual interface nodes and degrees-of-freedom of the flexible
body.
11. One FLXNODE line can have up to six interface grid IDs. No continuation lines are
allowed. Add multiple FLXNODE lines to add more than six interface nodes.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Examples
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Default = 10-14 * KB (Real > 0.0). This default is also set when KB=0.
MU1 Coefficient of static friction (ms). See comments 8 through 10. (Ignored in
linear analysis).
Comments
1. The gap element coordinate system is presented in the following figure. See the CGAP or
CGAPG entry for a more detailed description.
2. With the optional value AUTO, the initial gap opening U0 is calculated automatically,
based on the distance between nodes GA and GB (in the original, undeformed mesh). For
gap elements with prescribed coordinate systems, this becomes a projection of vector
GA->GB onto the prescribed axis on the gap element (axis 1 of the coordinate system).
3. The gap element force-displacement behavior is different in linear and nonlinear analysis
(see Nonlinear Quasi-Static Analysis for more information on nonlinear solutions). In linear
analysis, the gap stiffness is constant and depends on the initial gap opening U0 (as
shown in the figure below).
The gap force displacement behavior in nonlinear analysis is illustrated in the figure below.
While the gap is open, its normal stiffness is defined by KB. When the gap relative
displacement UA - UB becomes equal to the initial opening U0, first contact occurs. The
gap stiffness becomes KA upon contact.
4. When the gap is open, there is no transverse stiffness. When the gap is closed, friction
is activated and the gap has stiffness KT in the transverse direction (see 5 below for
alternative version). KT acts as a linear spring in linear solution sequences. For nonlinear
solution sequences, frictional force increases with sliding distance in proportion to KT until
it reaches static friction force MU1 * Fx, Fx being the normal force in the gap element.
With further transverse deformation, friction becomes kinetic and the friction force is MU2
* Fx. See the figure below for a one-dimensional illustration.
5. In addition to the above formulation, in Release 12.0 an additional model of friction has
been introduced, based on Elastic Slip Distance and activated by presence of non-zero
FRICESL. This model typically has better performance in solution of frictional problems
thanks to more stable handling of transitions from stick to slip. Key differences between
the two available models are illustrated in the figure below (F 1 and F 2 represent two
different values of normal force F x ):
Model (a), based on fixed stiffness KT, is relatively simpler and only requires prescribing
coefficient of friction MU1 and MU2 (while KT can be determined automatically).
However, in Coulomb friction the frictional resistance depends upon normal force. Using
fixed KT will predict different range of stick/slip boundary for different normal forces,
and thus may qualify the same configuration as stick or slip, depending on normal
force.
7. Reasonable gap stiffness: the gap stiffness values KA and KT essentially represent penalty
springs that are hard enough to prevent perceptible penetration of contacting nodes.
While, theoretically, higher stiffness values enforce the contact conditions more precisely,
excessively high values may cause difficulties in convergence or poor conditioning of the
stiffness matrix (this is especially true for KT). If any such symptoms are observed, it may
be beneficial to reduce the value of gap stiffness. A reasonable range of gap stiffness is
of the order of:
(103 to 106 ) * E * h
where, E is the typical value of elastic modulus and h is the typical element size in the
area surrounding the gap elements. Such a range will generally keep the gap penetration
below one thousandth / one millionth of the element size, respectively. A good value for
KT is of the order of 0.1*KA.
Option KA=AUTO determines the value of KA for each gap element using the stiffness
of surrounding elements. Additional options SOFT and HARD create respectively softer
or harder penalties. SOFT can be used in cases of convergence difficulties and HARD
can be used if undesirable penetration is detected in the solution.
Option KT=AUTO automatically calculates the value of KT. If MU1>0, the result here is
the same as with blank KT -- its value is calculated as MU1*KA. However, if MU1=0 or
blank, KT=AUTO produces a non-zero value of KT, calculated as KT=0.1*KA.
Therefore, KT=AUTO can be used to prescribe enforced stick conditions (see below).
8. Prescribing MU1=STICK is interpreted as an enforced stick condition. (This can also be
accomplished by prescribing KT>0 or KT=AUTO with MU1=0 or blank). Such gap elements
will not enter the sliding phase. Of course, the enforced stick only applies to gaps that
are closed. Note that, in order to effectively enforce stick condition on gaps of non-zero
length,frictional offset may need to be turned off (See comment 10).
9. Prescribing MU1=FREEZE enforces zero relative motion of the gap – the gap opening
remains fixed at the original value and the sliding distance is zero. Also, rotations at GA
node are matched to the rotations of GB or the obstacle patch B. The FREEZE conditions
applies no matter whether the gap is open or closed (hence, U0 is of no relevance in this
case). The prescribed values of KB and KT are ignored. The value of KA is respected,
10. The presence of friction or stick can introduce moment loadings and counter-intuitive
results into the problem by way of frictional offset. The reason is that for gap elements
with non-zero length (distance between GA and GB), the actual location of the contact
interface is presumed to be in the middle of the gap length (see figure below).
The frictional forces act along this contact surface. Transferring these forces to the grid
points GA and GB requires an offset operation that produces both forces and moments at
the gap grid points. Similarly, the sliding distance at the gap interface is a result of nodal
displacements and rotations at GA and GB (see figure below).
For contact between bodies that do not support moments (solid elements, for example),
this offset may render friction ineffective because the free rotations at gap nodes offer
no effective resistance to friction. With the stick condition formally satisfied, for
example, nodes GA and GB can move relative to each other (see figure below).
In practice, for gaps that are initially open, AUTOSPC will effectively fix respective
unsupported rotations. However, for gap elements that are initially closed (U0 < 0 or
U0=AUTO with CID=FLIP), the frictional terms will prevent AUTOSPC from being effective.
Hence, respective SPC on rotations need to be applied manually. (Note that this only
applies to "individual" gap end nodes GA and GB and is not needed for elements or patches
of nodes on the obstacle side of GAPG elements).
Effective in the Release 12.0, to avoid such counter-intuitive behavior, the frictional
offset operation is by default turned off if the model involves friction or stick and contains
at least one nonlinear subcase (of NLSTAT type). (Note that for consistency, this affects
both linear and nonlinear gap elements.) This produces more intuitive results with friction.
However, it may violate the rigid body balance of the body.
For linear gap analysis and for FREEZE condition, the offset operation is applied by default
(this produces correct rigid body balance, especially in natural frequency analysis).
The above default setting can be changed via the GAPOFFS command on the GAPPRM
card.
11. The GPAD option allows you to account for additional layers on the surface on obstacles
A and B, such as shell thickness or coatings on the surface of solids. Positive value
substracts from the gap opening U0, when calculated using AUTO option (GPAD is only
allowed when U0 is set to AUTO).
The GPAD option THICK automatically accounts for shell thickness on both sides of the
gap (this also includes the effects of shell element offset ZOFFS or composite offset Z0).
The THICK option applies only to CGAPG elements and is ignored for CGAP.
PGAPHT – Gap Element Heat Transfer Conduction Property for Heat Transfer Analysis
Description
Defines heat transfer conduction properties of the gap (CGAP or CGAPG) elements for heat
transfer analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Examples
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PGAPHT 2 1E6
PGAPHT 2 AUTO
Minimum data required to prescribe clearance based contact conduction (see comments 2
and 3):
PGAPHT 2 10
Field Contents
Default = 10-14 * KAHT (Real > 0.0) This default is also set when KBHT=0.
TCID Identification number of a TABLED# entry. This table specifies total gap
conduction based on gap clearance. See comments 2, 3, and 4.
Comments
1. PGAPHT provides heat transfer conductivity for CGAP/CGAPG element. PGAPHT must
match PID with an existing PGAP.
2. KAHT and KBHT represent total gap conduction values for closed and open gaps.
Theoretically, while higher conduction values enforce a perfect conductor, excessively
high values may cause poor conditioning of the conductivity matrix. If any such
symptoms are observed, it may be beneficial to reduce the value of gap conduction, or
use conduction based contact clearance and pressure.
Option KAHT=AUTO determines the value of KAHT for each gap element using the
conduction of surrounding elements.
3. TCID points to a TABLED# entry that specifies total conduction based on gap clearance.
TCID overrides KBHT. TCID is ignored for linear CGAP/CGAPG elements.
4. Thermal-structural analysis problems involving contact are fully coupled since contact/gap
status changes thermal conductivity. Refer to Contact-based Thermal Analysis in the
User’s Guide for more information.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
STABMT
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PGASK 1 2 1 1 0.5
Field Contents
MID1 A MAT1 entry identification number that defines membrane properties and
mass density of the gasket.
-1 means the element local coordinate system, while 0 means the basic
coordinate system.
0 - no stabilization.
Default = 0 (Integer = 0 or 1)
Comments
1. All gasket element property entries must have unique identification numbers.
2. PGASK refers to two material entries, MGASK and MAT1. MGASK defines the thickness-
direction and transverse shear behaviors of the gasket material, and MAT1 defines the
membrane behavior of the gasket material.
The thickness-direction stiffness is defined with the unit of stress per unit displacement
(the pressure—closure distance relationship for the thickness compression), the
transverse shear stiffness is defined with either the unit of stress per unit displacement
or the unit of force per unit area, and the membrane stiffness is defined with the unit of
force per unit area (the stress—strain relationship).
4. The initial thickness includes initial open gap and initial void of the gasket.
5. The total closure of a gasket element consists of the mechanical closure and the thermal
closure, that is:
The effective closure, C, which is used to determine pressure with the loading/unloading
of tables defined in the MGASK card, is calculated as:
C = Cmech – GAP
6. The sealing status of gasket is detected with the leakage pressure. If the gasket pressure
is larger than the leakage pressure, it is detected to be sealed – the output status index
value is 1; otherwise, it is leaking – the output status index value is 0.
Description
Defines the thickness, material, blank holder, binder and Forming Limit Curve references for a
shell property in a one-step stamping simulation.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PHFSHL 1 1 0.01 6 2
Field Contents
T Thickness
1. This entry is only valid with an @HyperForm statement in the first line of the input file.
2. All shell element property entries must have unique identification numbers.
Description
Defines a static pressure load on a triangular or quadrilateral element. It can also be used to
define the EXCITEID field (Amplitude “A”) of dynamic loads in RLOAD1, RLOAD2, TLOAD1 and
TLOAD2 bulk data entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PLOAD SID P G1 G2 G3 G4
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PLOAD 1 -4.0 16 32 11 0
Field Contents
(Integer > 0)
P Pressure.
Comments
1. The grid points define either a triangular or a quadrilateral element to which a pressure is
applied. If G4 is zero or blank, the element is triangular.
2. The total load on the element, AP, is divided into three equal parts and applied to the grid
points as concentrated loads. A minus sign in field 3 reverses the direction of the load.
3. In the case of a quadrilateral element, the grid points G1, G2, G3, and G4 should form a
consecutive sequence around the perimeter. The right-hand rule is applied to find the
assumed direction of the pressure.
Description
Defines concentrated, uniformly distributed, or linearly distributed applied loads to the CBAR or
CBEAM elements at user-chosen points along the axis. It can also be used to define the
EXCITEID field (Amplitude “A”) of dynamic loads in RLOAD1, RLOAD2, TLOAD1 and TLOAD2 bulk
data entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (FX, FY, FZ, FXE, FYE, FZE, MX, MY, MZ, MXE, MYE or MZE)
SCALE Determines scale factor for X1, X2. See comments 6, 7, 8 and 9.
X1, X2 Distances along the CBAR or CBEAM element axis from end A.
For X1: No default; For X2: Default = blank (Real, 0 < X1 < X2)
Comments
1. In the static solution sequences, the load set ID (SID) is selected by the LOAD command
in the Subcase Information section.
2.
positions X1 and X2, having an intensity per unit length of bar equal to P1 at X1 and
equal to P2 at X2, except as noted in comments 8 and 9.
4.
will be applied between positions X1 and X2, except as noted in comments 8 and 9.
"FX", "FY" or "FZ": Force in the x, y, or z direction of the basic coordinate system.
"MX", "MY" or "MZ": Moment in the x, y, or z direction of the basic coordinate system.
"FXE", "FYE" or "FZE": Force in the x, y, or z direction of the element’s coordinate system.
6. If SCALE = "LE" (length), the xi values are actual distances along the element axis, and, if
7. If SCALE = "FR" (fractional), the xi values are ratios of the distance along the axis to the
8. If SCALE = "LEPR" (length projected), the xi values are actual distances along the element
element.
If SCALE = "LE", the total load applied to the bar is P1 (X2 – X1) in the y-basic direction.
If SCALE = "LEPR", the total load applied to the bar is P1 (X2 – X1) cosα in the y-basic
direction.
9. If SCALE = "FRPR" (fractional projected), the Xi values are ratios of the actual distance to
10. Element identification numbers for CBAR and CBEAM entries must be unique.
11. Loads on CBEAM elements defined with PLOAD1 entries are applied along the line of the
shear centers.
12. If on the TYPE field of the PLOAD1 entry, the element coordinate system direction (for
example, TYPE = FYE) option is selected, then the projection (SCALE=FRPR or LEPR)
option is ignored and the result is the same as the SCALE=FR (or LE) option.
Description
Defines a uniform static pressure load applied to two-dimensional elements. Only QUAD4 or
TRIA3 elements may have a pressure load applied to them via this entry. It can also be used
to define the EXCITEID field (Amplitude “A”) of dynamic loads in RLOAD1, RLOAD2, TLOAD1
and TLOAD2 bulk data entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PLOAD2 21 -3.6 4 16 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
P Pressure value.
Comments
3. If the alternate form is used, all elements EID1 through EID2 must be two-dimensional.
4. The direction of the pressure is computed according to the right-hand rule using the grid
point sequence specified on the element entry. Refer to the PLOAD entry.
Description
Defines a load on a face of a HEXA, PENTA, TETRA, PYRA, TRIA3, TRIA6, QUAD4, or QUAD8
element. It can also be used to define the EXCITEID field (Amplitude “A”) of dynamic loads in
RLOAD1, RLOAD2, TLOAD1 and TLOAD2 bulk data entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ID N1 N2 N3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C ID N1 N2 N3
(Integer > 0)
P1, P2, P3, P4 Load per unit surface area (pressure) at the corners of the face of the
element (real or blank). (P1 is the default for P2, P3, and P4).
G4 Identification number of the TETRA grid point located at the corner not
on the face being loaded. This is required data and is used for TETRA
elements only.
(Integer > 0)
Comments
1. The continuation is optional. If fields 2, 3, 4, and 5 of the continuation are blank, the
load is assumed to be a pressure acting normal to the face. If these fields are not blank,
the load acts in the direction defined in these fields. Note that, if CID is a curvilinear
coordinate system, the direction of load may vary over the surface of the element. The
load intensity is the load per unit of surface area, not the load per unit of area normal to
2. For solid elements the direction of positive pressure (defaulted continuation card) is
inward. The load intensity P1 acts at grid point G1 and load intensities P2, P3 (and P4)
act at the other corners in a sequence determined by applying the right hand rule to the
outward normal.
3. For plate elements the direction of positive pressure (defaulted continuation) is in the
direction of positive normal, determined by applying the right hand rule to the sequence of
connected grid points. The load intensities PI, P2, P3 (and P4) act respectively at corner
points G1, G2, G3 (and G4). (See plate connection).
4. If P2, P3 (and P4) are blank fields, the load intensity is uniform and equal to P1. P4 has
no meaning for a triangular face and may be left blank in this case.
5. Equivalent grid point loads are computed by linear (or bilinear) interpolation of load
intensity, followed by numerical integration using isoperimetric shape functions. Note that
uniform load intensity does not necessarily result in equal equivalent grid point loads.
6. G1 and G3 are ignored for TRIA3, TRIA6, QUAD4, and QUAD8 elements.
7. The alternate form is available only for TRIA3, TRIA6, QUAD4, and QUAD8 elements. The
continuation card may be used in the alternate form.
9. For the quadrilateral face of the PYRA element, G1 is an identification number of a corner
grid point on the face and the G3 or G4 field is left blank. For the triangular faces, G1 and
G3 must specify the grids on the edge of the face that borders the quadrilateral face and
the grids must be ordered so that they define an inward normal using the right hand rule.
Description
Defines a static surface traction on the CTAXI and CTRIAX6 axisymmetric elements.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
No default (Real)
GA, GB Identification numbers of two adjacent corner grid points on the element
side.
Theta Angle between surface traction and inward normal to the line segment.
Comments
1. The surface traction is assumed to vary linearly along the element side between GA and
GB.
3. “Theta” is measured counter-clockwise from the inward normal of the straight line
between GA and GB, to the vector of the applied load, as shown in the figure below.
Positive pressure is in the direction of inward normal to the line segment.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PLOTEL EID G1 G2
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PLOTEL 29 35 16
Field Contents
Comments
1. This element is not used in the model during any of the solution phases of a problem. It is
used to simplify the plotting of structures with large numbers of collinear grid points,
where the plotting of each grid point along with the elements connecting them would
result in a confusing plot.
2. Element identification numbers should be unique with respect to all other element
identification numbers.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PLOTEL3 EID G1 G2 G3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PLOTEL3 29 35 16 22
Field Contents
Comments
1. This element is not used in the model during any of the solution phases of a problem. It is
used to simplify the plotting of large structures.
2. Element identification numbers should be unique with respect to all other element
identification numbers.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PLOTEL4 EID G1 G2 G3 G4
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PLOTEL4 29 35 16 22 23
Field Contents
Comments
1. This element is not used in the model during any of the solution phases of a problem. It is
used to simplify the plotting of large structures.
2. Element identification numbers should be unique with respect to all other element
identification numbers.
Description
The PLSOLID bulk data entry defines the properties of nonlinear hyperelastic solid elements,
referenced by CHEXA, CPENTA, and CTETRA bulk data entries. The MATHE hyperelastic
material can be referenced to define corresponding material properties.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PLSOLID
Field Contents
Comments
1. All solid element property entries must have unique identification numbers.
2. The PLSOLID bulk data entry can be referenced by a CHEXA, CPENTA or CTETRA bulk
data entry.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ESID9 …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
MID Material identification number. Must refer to a MAT1, MAT2 or MAT8 bulk data
entry.
T Ply thickness.
THETA Ply orientation angle, in degrees, of the longitudinal direction relative to the x-
axis of the material coordinate system associated with a given element. If no
material coordinate system is prescribed for the element, the angle is measured
relative to side 1-2 of this element.
SOUT Stress, Strain, and Failure Index output request. See comments 2 and 3.
DID Draping identification number. Must refer to a DRAPE bulk data entry.
ESID# Element SET identification numbers. Lists the elements for which this PLY card
is defined. No continuation line indicates that all elements should be included.
Comments
1. The PLY card is used in combination with the PCOMPP and STACK cards to create
composite properties through the ply-based definition.
2. Stress, Strain and Failure Index output for the PLY is activated by setting SOUT to YES.
In addition, the I/O Options CSTRESS (controlling Stress and Failure Index output) and/or
CSTRAIN (controlling Strain output) must be defined. Failure Index output also requires
that the FT and SB fields be defined on the corresponding PCOMPP card, and that stress/
strain allowables on the referenced materials are defined.
3. An additional piece of information available with ply results is "failure index for the
element," which is the maximum of failure indices for individual plies in this element. Note
that only the plies with SOUT set to YES are considered in the evaluation of this
maximum.
4. TMANUF defines the thickness of one manufacturable ply. This parameter is used during
sizing optimization to automatically create discrete design variables such that the
thickness of the ply bundle is equal to a multiple of TMANUF.
Description
Defines the mass value of a scalar mass element (CMASS1 or CMASS3 entry).
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Real)
Comments
1. Mass values are defined directly on the CMASS2 entry, and therefore do not require a
PMASS entry.
Description
Defines a rigid body out of a list of finite element properties, elements and grid points.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ID8 …
TYPE# …
MASS M
C OG X,G Y Z
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PRBODY 3 ARM1
PSHELL 23 21
PBEAM 9 59 48
C ONM2 2345
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PRBODY 4 LEVER
PBAR 10 11 13 15 22 99 88
44
MASS 100.0
C OG 29
Field Contents
BODY_NAME Unique body name. This body name for this PRBODY.
TYPE# Flag indicating that the following list of IDs refer to entities of this
type. All property definitions; CELAS2, CONM2, PLOTEL, RBE2, RBE3,
RBAR, RROD, and GRID are valid types for this field.
MASS Flag to overwrite the finite element mass of the body. Indicates that
a mass value is to follow.
M Mass.
INERTIA Flag to overwrite the finite element inertia of the body. Indicates
that the inertia properties are to follow.
COG Flag to overwrite the finite element center of gravity of the body.
Indicates that the center of gravity is to follow.
(Real)
(Integer > 0)
Comments
1. Any number of property definitions; CELAS2, CONM2, PLOTEL, RBAR, RBE2, RBE3 or RROD
elements or grid points can be given.
3. A property definition; CELAS2, CONM2, PLOTEL, RBE2, RBE3, RBAR or RROD element or grid
point can only belong to one rigid or flexible body.
4. All property definitions, elements and grid points defined on a PRBODY bulk data entry
form one rigid body. The mass and inertia properties are defined by the finite element and
mass properties unless they are overwritten by the mass and inertia properties given on
the continuation lines.
5. The mass, inertia and center of gravity input is optional if element/property information is
provided in the PRBODY definition.
6. If one of MASS, INERTIA or COG continuations is provided, all three continuations must be
provided.
9. If just the principal inertia is specified, IXX, IYY, and IZZ must be positive non-zero
values and they must satisfy the condition: the sum of two inertia values must be greater
than the third (IXX + IYY > IZZ, IYY+IZZ > IXX, IZZ+IXX > IYY).
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Examples
1D pretensioned bolt:
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PRETENS 2 5
3D pretensioned bolt:
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PRETENS 3 4
Field Contents
EID Element identification number of a bar, beam or rod element for defining
1D pretensioned bolt.
See comment 2.
G1, G2, G3 Three grid identifiers that define the plane where its normal is the
direction of the bolt.
Default = blank (Integer > 0). When prescribed, all three nodes must
be prescribed.
X1, X2, X3 Coordinates, in basic system, of the vector that defines direction of
pretension.
For cylindrical and spherical systems, the local z-axis defines the
pretension direction.
SPNTID SPOINT that defines the DOF containing the pretension deformation and
load.
Comments
3. The default direction of pretension is defined automatically from the configuration of the
pretension section.
Description
Defines parameters that control initial loading conditions on pretension sections for 1D and 3D
bolt pretensioning. These parameters also control the printing of diagnostic information about
pretension sections.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
The available parameters and their values are listed below (click the parameter name for
parameter descriptions).
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
A Area of rod.
No default (Real)
J Torsional constant.
No default (Real)
No default (Real)
Comments
1. For structural problems, MID may reference only a MAT1 material entry. For heat transfer
problems, MID may reference only a MAT4 material entry.
2. All rod property entries must have unique property identification numbers.
CM
J
Where,
M
is the torsional moment
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
Comments
1. Material MID is used to calculate the stiffness of the connector (the fictitious CHEXA).
MID can only refer to the MAT1 or MAT9 bulk data entry.
2. The distance between GS and GE is the length of the element. The width of the seam
weld is measured perpendicular to the length and lies in the plane of Shell A or B. See
figure below.
3. If the entry of T is left blank, the thickness of this seam weld will be calculated as the
averaged thickness of Shell A and B.
Description
Defines property information for planar section elements used in the definition of arbitrary
beam cross-sections.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
T Thickness.
Comments
1. All property identification numbers within a section definition must be unique with respect
to all other property identification numbers within the same section definition.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PSHEAR 21 2 .001
Field Contents
(Integer > 0)
(Integer > 0)
(Real)
F1 Effectiveness factor for extensional stiffness along edges 1-2 and 3-4. See
comment 2.
F2 Effectiveness factor for extensional stiffness along edges 2-3 and 1-4. See
comment 2.
Comments
1. The effective extensional area is defined by means of equivalent rods on the perimeter of
the element. If F1 < 1.01, the areas of the rods on edges 1-2 and 3-4 are set equal to
(F1 ×× T ×× PA)/(L12 + L34), where PA is the panel surface areas - half the vector
cross product area of the diagonals - and L12 and L34 are the lengths of sides 1-2 and 3-
4. Thus, if F1 = 1.0, the panel is fully effective for extension in the 1-2 direction. If F1 >
1.01, the areas of the rods on edges 1-2 and 3-4 are each set equal to 0.5 ×× F1 ×× T.
Thus, if F1 = 30, the effective width of skin contributed by the panel to the flanges on
edges 1-2 and 3-4 is equal to 15T. The significance of F2 for edges 2-3 and 1-4 is
similar.
Description
Defines the membrane, bending, transverse shear, and membrane-bending coupling of shell
elements.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Z1 Z2 MID4 T0 ZOFFS
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
T Default value for the membrane thickness (Real > 0.0). If T0 is defined for
topology optimization, T is the total thickness.
(Real)
Z1,Z2 Fiber distances for stress computation. The positive direction is determined by
the right hand rule and the order in which the grid points are listed on the
connection entry.
(Integer > 0 or blank, must be blank unless MID1>0 and MID2>0, may not be
equal to MID1 or MID2). See comments 10 and 11.
T0 The base thickness of the elements in topology optimization. Only for MAT1,
T0 can be >0.0. If T0 is blank, then the elements are not included in the
topology design volume or space.
(Real > 0.0 or blank for MAT1, Real = 0.0 or blank for MAT2, MAT8)
ZOFFS Offset from the plane defined by element grid points to the shell reference
plane.
Comments
1. All shell element property entries must have unique identification numbers.
3. MID1 cannot be left blank. The effect of leaving an MID2 or MID3 field blank is:
5. This entry is used in connection with the CTRIA3, CQUAD4, CTRIA6, and CQUAD8 entries.
6. PSHELL entries may reference MAT1, MAT2, MAT4, MAT5, and MAT8 material property
entries.
7. The default for Z1 is -T/2, and for Z2 it is +T/2. T is the local plate thickness, defined by
T on this entry. For free-sizing optimization, Z1 and Z2 definitions are ignored and the
defaults of –T/2 and +T/2 are used for each element.
8. If MID3 references a MAT2 material, then G33 on the MAT2 data must be blank.
9. If MID3 references a MAT8 material, then G1Z and G2Z must not be blank.
10. MID4 provides a way to represent shells with offset (shell element centerline being offset
from the plane of the grid points) or shells with material properties that are not symmetric
with respect to the middle surface of the shell. However, whenever possible, the
preferred method of representing such shells is through the use of element offset ZOFFS
or the composite property PCOMP. This is because MID4 does not provide sufficient
information about the shell structure to correctly calculate all respective results,
specifically:
The shell stresses calculated in the presence of MID4 are generally incorrect, as they
do not reflect the actual shell offset or the non-uniform material structure.
The effects of MID4 are not considered in the calculation of differential stiffness.
Hence, it is recommended that MID4 be left blank in buckling analysis.
11. If MID4 points to a MAT2 card with a material ID greater than 400,000,000, then the
thermal membrane-bending coefficients A1, A2, and A12 have a modified interpretation,
and represent [G]*[alpha] rather then [alpha]. Here, [G] is a matrix composed of G11,
G22,…G33. This is to maintain consistency with respective terms generated internally by
the PCOMP card.
12. Thermal expansion coefficients provided for materials referenced as MID2 or MID3 are
ignored in shell analysis - only the thermal expansion terms for materials referenced as
MID1 (membrane) and MID4 (coupling) are considered. Furthermore, the reference
temperature (TREF) for the shell property is taken from the material referenced as MID1 -
TREF's provided for other MID's are ignored.
14. In plane strain computations, in-plane loads are interpreted as line loads with a value
equal to the load, divided by the thickness. Thus, if a thickness of "1.0" is used, the
value of the line-load equals the load value. Pressure can be approximated with multiple
line loads where the pressure value equals the line-load, divided by the length between
the loads.
15. The shell reference plane can be offset from the plane defined by the element nodes by
means of ZOFFS. In this case all other information, such as material matrices or fiber
locations for the calculation of stresses, is given relative to the offset reference plane.
Shell results, such as shell element forces, are output on the offset reference plane.
ZOFFS can be used in all types of analysis and optimization.
1. Real:
A positive or a negative value of ZOFFS is specified in this format. A positive value of
ZOFFS implies that the reference plane of each shell element is offset a distance of
ZOFFS along the positive z-axis of its element coordinate system.
2. Surface:
This format allows you to select either “Top” or “Bottom” option to specify the offset
value.
Top:
The top surface of the shell element and the plane defined by the element nodes are
coplanar.
This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
element. (The sign of the ZOFFS value would depend on the direction of the offset with
respect to the positive z-axis of the element coordinate system, as defined in the Real
section). See Figure 1.
Bottom:
The bottom surface of the shell element and the plane defined by the element nodes are
coplanar.
This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
element. (The sign of the ZOFFS value would depend on the direction of the offset with
When ZOFFS is used, both MID1 and MID2 must be specified; otherwise singular matrices
would result.
Moreover, while offset is correctly applied in geometric stiffness matrix and thus can be
used in linear buckling analysis, caution is advised in interpreting the results. Without
offset, a typical simple structure will bifurcate and loose stability “instantly” at the critical
load, shown in Figure (a). With offset though, the loss of stability is gradual and
asymptotically reaches a limit load, as shown below in Figure (b).
Thus, the structure with offset can reach excessive deformation before the limit load is
reached. Note that the above illustrations apply to linear buckling – in a fully nonlinear
limit load simulation, additional instability points may be present on the load path.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DM DN ITHIC K IPLAS
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PSHELL 73 7 1.0 7 7
PSHELLX 73 24 5
Field Contents
30 - DKT18.
31 - DKT_S3.
NIP Number of integration points through the thickness. NIP = 0 defines global
integration.
IPLAS Flag for shell plane stress plasticity (with MATX2, MATX27, and MATX36 only).
Comments
1. The property identification number must be that of an existing PSHELL bulk data entry.
Only one PSHELLX property extension can be associated with a particular PSHELL.
2. PSHELLX is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
QBAT: Modified BATOZ Q4g 24 shell with 4 Gauss integration points and reduced
integration for in-plane shear. No hourglass control is needed for this shell.
6. Global integration (NIP = 0) is only compatible with MAT1, MATS1, MATX2, and MATX36.
7. For MAT1, membrane only behavior happens if NIP = 1. Otherwise, NIP is ignored and
global integration (NIP = 0) is used.
9. If ITHICK = VAR or IPLAS = NEWT, the small strain option is automatically deactivated.
10. For MATX2, the default value for IPLAS and global integration (NIP=0) is IPLAS = RAD.
11. For MATS1, MATX36 the default value for IPLAS and global integration (NIP=0) is IPLAS =
NEWT.
QEPH 24 1.5%
QBAT 12 0%
QEPH 24 1.5%
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
QB HV DTMIN C ID IP IORTH
Vx Vy Vz THETA
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PSOLID 77 7
PSLDX6 77 24
Field Contents
where:
ISMSTR Flag for small strain formulation (ISOLID = 1, 2, 14, and 24 only).
(Integer > 0)
IP Reference plane.
Default = 0 (Integer)
(Integer = 0, 1)
(Real)
(Real)
(Real)
Comments
1. The property identification number must be that of an existing PSOLID bulk data entry.
Only one PSLDX6 property extension can be associated with a particular PSOLID.
2. PSLDX6 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. PSLDX6 is only compatible with 8-node linear solid elements. Quadratic 20-node brick and
6-node pentahedron elements are not compatible, these element types should only be
used with PSOLIDX.
4. The ISOLID flag is not used with CTETRA elements. For elements with 4 and 10 nodes,
the number of integration points is fixed at 1 and 4, respectively.
6. With the small strain option (ISMSTR), strain and stress is engineering strain and stress.
Otherwise, it is true strain and stress.
7. In time history and animation files, the stress tensor is written in the co-rotational frame.
8. Fully-integrated elements (ISOLID =12) only use full geometric non-linearity (corresponds
to ISMSTR = 4). Time step limit has no effect.
9. ISMSTR =10 is only compatible with materials using total strain formulation (MATX42).
10. The time step control XSTEP, TYPEi = SOLID, TSCi = CST only works on elements with
ISMSTR =2.
11. Co-rotational formulation: For ISOLID = 1, 2, 12 and IFRAME = ON, the stress tensor is
computed in a co-rotational coordinate system. This formulation is more accurate if large
rotations are involved. It comes at the expense of higher computation cost. It is
recommended in case of elastic or visco-elastic problems with important shear
deformations. The co-rotational formulation is compatible with 8 node solids.
12. For HA8 (ISOLID = 14) elements: this element uses a locking-free general solid
formulation, co-rotational. The number of Gauss points is defined by NIP flag: for
example, combined with NIP = 222 gives an 8 Gauss integration point element, similar to
ISOLID = 12. The HA8 formulation is compatible with all material laws. Under-integration
for pressure should be used (ICPRE = ON in case of elastic or visco-elastic material; ICPRE
= VAR in case of elasto-plastic material).
13. For H8C (SOLID = 17) elements: Their brick deviatoric behavior is the same as ISOLID =
12, but the bulk behavior can be chosen with ICPRE, and is compatible with all solid type
material laws. ICPRE = VAR is the default value and ICPRE = OFF will not reduce pressure
integration.
14. For HEPH (ISOLID = 24) elements: This element uses an hourglass formulation similar to
QEPH shell elements.
Description
Defines the properties of solid elements, referenced by CHEXA, CPENTA, CPYRA and CTETRA
bulk data entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PSOLID 2 100 1
Field Contents
Comments
2. Special integration flags MODPAST and REDPLAST affect only elasto-plastic materials (as
identified by presence of MATS1) in nonlinear quasi-static subcases. They do not affect
element behavior in linear analysis.
3. The FULL option in the ISOP field provides stable and convergent results, although it may
appear “stiff” and converge rather slowly in cases of significant plastic deformation.
MODPLAST uses special handling for volumetric pressure term, in effect providing good
resolution of plastic flow while avoiding excessive flexibility that would lead to spurious
modes. REDPLAST adds further release of locking tendencies and usually the “softest”
behavior. It may, theoretically, exhibit spurious deformation modes in single unattached
elements, although in practice these modes should vanish in fields of many elements.
5. Stresses are calculated in the material coordinate system. The material coordinate
system may be defined as the basic coordinate system (CORDM = 0), a defined system
(CORDM = Integer > 0), or the element coordinate system (CORDM = -1). Refer to the
CHEXA, CPENTA, CPYRA and CTETRA pages of the Reference Guide for details on how the
material coordinate system is defined for each element.
6. If the material referenced by MID is a MAT9 material definition, then CORDM defines the
material coordinate system for Gij on the MAT9 entry.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PSOLID 77 7
PSOLIDX 77 24
Field Contents
where:
ISMSTR Flag for small strain formulation (ISOLID = 1, 2, 14, and 24 only).
ICPRE Flag for reduced pressure integration (ISOLID = 14, 17, and 24 only).
Default = OFF for ISOLID = 14, 24, ON for ISOLID = 17 (ON, OFF, or
VAR)
No default (Real)
No default (Real)
Default = 1 (Integer = 1, 2)
1. The property identification number must be that of an existing PSOLID bulk data entry.
Only one PSOLIDX property extension can be associated with a particular PSOLID.
2. PSOLIDX is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. The ISOLID flag is not used with CTETRA elements. For these elements with four and ten
nodes, the number of integration points is fixed at one and four, respectively.
4. For fully integrated solids (SOLID =12), the deviatoric behavior is computed using 8 Gauss
points; bulk behavior is under-integrated to avoid element locking. It is currently
compatible with material MAT1, MATS1, MATX33, and MATX36.
5. With the small strain option (ISMSTR), strain and stress is engineering strain and stress.
Otherwise, it is true strain and stress.
6. In time history and animation files, the stress tensor is written in the co-rotational frame.
7. Fully integrated elements (ISOLID =12) only uses full geometric non-linearity (corresponds
to ISMSTR = 4). Time step limit has no effect.
8. ISMSTR = 10 is only compatible with materials using total strain formulation (MATX42).
9. The time step control XSTEP, TYPEi = SOLID, TSCi = CST only works on elements with
ISMSTR = 2.
10. Co-rotational formulation: For ISOLID = 1, 2, 12 and IFRAME = ON, the stress tensor is
computed in a co-rotational coordinate system. This formulation is more accurate if large
rotations are involved. It comes at the expense of higher computation cost. It is
recommended in case of elastic or visco-elastic problems with important shear
deformations. The co-rotational formulation is compatible with 8 node solids.
11. HA8 (ISOLID = 14) elements: this element uses a locking-free general solid formulation,
co-rotational. The number of Gauss points is defined by NIP flag: for example, combined
with NIP = 222 gives an 8 Gauss integration point element, similar to ISOLID = 12. The
HA8 formulation is compatible with all material laws. Under-integration for pressure should
be used (ICPRE = ON in case of elastic or visco-elastic material; ICPRE = VAR in case of
elasto-plastic material).
12. H8C (SOLID = 17) elements: Their brick deviatoric behavior is the same as ISOLID = 12,
but the bulk behavior can be chosen with ICPRE, and is compatible with all solid type
material laws. ICPRE = VAR is the default value and ICPRE = OFF will not reduce pressure
integration.
13. HEPH (ISOLID = 24) elements: This element uses an hourglass formulation similar to QEPH
shell elements.
Description
Defines a pretension load as a linear combination of load sets defined via PTFORCE, PTFORC1,
PTADJST and PTADJS1 entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PTADD PSID S S1 L1 S2 L2 S3 L3
S4 L4 -etc-
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Real)
No default (Real)
Where,
Li is the pretension load set defined via PTFORCE, PTFORC1, PTADJST andPTADJS1
entries.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PTADJS1 3 0.05 1 3 4
Field Contents
(Integer > 0)
(Real)
(Integer > 0)
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PTADJST 3 5 0.5
Field Contents
(Integer > 0)
(Integer > 0)
(Real)
Comments
3. Pretensioning adjustment using PTADJST can also be used to define additional shortening
to a pretensioned section. Therefore, when adjustment is applied to a section that has
already been pretensioned, the final effect will be a sum of the status reached in the
preceding pretensioning subcase plus the amount of adjustment through PTADJST.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PTFORC E 3 5 0.5
Field Contents
(Integer > 0)
(Integer > 0)
(Real)
Comments
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PTFORC 1 3 500.0 1 3 4
Field Contents
(Integer > 0)
(Real)
(Integer > 0)
2. Pretensioning force is actually a pair of forces, applied to the opposite sides of the
pretension section. This represents the effect of tightening the nut by a prescribed
longitudinal force (which is related to the applied torque).
Description
PTUBE defines the properties of a thin-walled cylindrical tube element, referenced by a CTUBE
entry.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
T Thickness of tube.
(Real)
OD2 Diameter of tube at second grid point – G2 on CTUBE entry. See comment
4.
Comments
3. For structural problems, PTUBE entries may only reference MAT1 material entries.
5. PTUBE data is converted to PROD data as it is read. CTUBE data is converted to CROD
data.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
CE1, CE2 Viscous damping values for extension in units of force per unit
velocity.
No default (Real)
CR1, CR2 Viscous damping values for rotation in units of force per unit velocity.
No default (Real)
Comments
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PWELD 30 2 2.5
Field Contents
Comments
1. Material MID, diameter D, and the length are used to calculate the stiffness of the
connector in 6 directions. MID can only refer to the MAT1 bulk data entry. The length is
the distance of GA to GB (see below).
3. If TYPE="SPOT" and if the formats PARTPAT, ELPAT, or ELEMID on the CWELD entry are
used, then the effective length for the stiffness of the CWELD element is set to
regardless of the distance GA to GB. t A and t B are the shell thicknesses of
shell A and B respectively. For all other cases, the effective length of the CWELD
element is equal to the true length, the distance of GA and GB, as long as the ratio of
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Alternate Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Real)
EID# CHBDYE surface element identification numbers. With alternate format using
“THRU” EID2 > EID1.
Comments
1. QBDY1 entries must be selected with the Case Control command LOAD=SID in order to be
used in static analysis. The total power into an element is given by the equation:
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
...
Field Contents
SID
Load set identification number.
QVOL
Power input per unit volume produced by a heat conduction element.
No default (Real)
EID#
A list of heat conduction elements.
Comments
1. EID# has material properties (MAT4/MAT5) that include HGEN, the scale factor for
volumetric heat generation. This association is made through the element EID.
2. QVOL provides the constant volumetric heat generation rate. QVOL is positive for heat
generation. For steady-state analysis, the total power into an element is:
Where, HGEN is the scale factor from the MAT4 and MAT5 data.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PARAM5 VALUE5
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
The available parameters and their values are listed below (click the parameter name for
detailed parameter descriptions).
Comments
1. The parameters defined by RADPRM bulk card are only applied in geometric nonlinear
analysis subcases which are defined by ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is
ignored for all other subcases.
Note
RADSND – Defines Grids (microphone locations) where sound levels will be calculated and the
locations of the corresponding source (vibrating panel) grids.
Description
Defines a set of grid points where the sound will be calculated as well as the panels that are
generating the sound.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
RADSND 10 100
Field Contents
PANEL Flag indicating that the following panel ID’s will contribute to the sound
at the MSET grids (see comment 4).
Comments
2. Multiple continuations or multiple RADSND with the same SID are allowed if more than 7
SOUND panels need to be defined.
3. The RADSND bulk data entry is referenced by the RADSND command in the Subcase
Information section of the input data.
4. The MSET and PIDi fields are used to specify the microphone locations (receiving grids)
and the vibrating panels (source grids) respectively.
Description
Defines load set power spectral density factors for use in random analysis having the
frequency dependent form S (F) = (X + iY) G(F).
jk
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
(Real)
Integer > 0
Comments
3. Set identification number must be selected in the Subcase Information section (RANDOM
= SID) to activate the RANDPS data.
Description
Defines time lag constants for use in random analysis autocorrelation function computation.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
1. At least one RANDPS entry must be present with the same set identification number.
3. Time lag sets must be selected in the Subcase Information section (RANDOM = SID) to
activate the RANDT1 data.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
RBAR EID GA GB C NA C NB C MA C MB
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
1. The total number of components in CNA and CNB must equal six, for example, CNA =
1236, CNB = 34. Furthermore, they must jointly be capable of representing any general
rigid body motion of the element.
2. If both CMA and CMB are zero or blank, all of the degrees-of-freedom not in CNA and CNB
are made dependent.
3. The degree of freedom declared dependent on this entry may not be:
6. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on RBAR entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry
in the model). “number” is the identification number of a referenced local entry in the part
“PartName”. See Parts and Instances in the User’s Guide for detailed information on the
use of fully qualified references.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Integer)
GNi Grid points at which independent degrees-of-freedom for the element are
assigned.
GMi Grid points at which dependent degrees-of-freedom for the element are
assigned.
Comments
1. The total number of components in CN1 to CN6 must equal six; furthermore, they must
jointly be capable of representing and general rigid body motion of the element. The first
continuation entry is not required if there are fewer than four GN points.
5. Rigid elements, unlike MPCs, may not be selected for use in individual subcases; they
apply to all subcases.
7. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on RBE1 entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry
in the model). “number” is the identification number of a referenced local entry in the part
“PartName”. See Parts and Instances in the User’s Guide for detailed information on the
use of fully qualified references.
Description
Defines a rigid body whose independent degrees-of-freedom are specified at a single grid point
and whose dependent degrees-of-freedom are specified at an arbitrary number of grid points.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
RBE2 9 8 12 10 12 14 15 16
20
Field Contents
GN The grid point to which all six independent degrees-of-freedom for the
element are assigned.
Comments
1. The components indicated by CM are made dependent at all grid points, GMi.
5. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on RBE2 entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry
in the model). “number” is the identification number of a referenced local entry in the part
“PartName”. See Parts and Instances in the User’s Guide for detailed information on the
use of fully qualified references.
Description
Defines the motion at a "reference" grid point as the weighted average of the motions at a set
of other grid points.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
5 4.7 1 2 4 6 5.2 2
7 8 9 5.1 1 15 16
UM 15 123 5 13 7 3
REFGRID Reference grid point. This is the dependent GRID. Some, or all, of the
dependent degrees-of-freedom of this grid can be made independent by
redefining all of the dependent degrees-of-freedom following the UM flag.
REFC Global components of motion whose values will be computed at the reference
grid point. Any of the digits 1, 2, ..., 6 with no embedded blanks.
(Integer > 0)
WTi Weighting factor for components of motion on the following entry at grid points
Gi,j.
(Real)
Ci Global components of motion that have weighting factor WTi, at grid points Gi,j.
Any of the digits 1, 2, ..., 6, with no embedded blanks.
(Integer > 0)
Gi,j Grid point whose components Ci have weighting factor WTi in the averaging
equations.
UM Optional flag indicating that a data set redefining the entire dependent degree-
of-freedom set is to follow. The default is that all of the components in REFC at
the reference grid point form the dependent degree-of-freedom set. See
comments 4, 5 and 6.
GMi Grid points with components in the redefined dependent degree-of-freedom set.
(Integer > 0)
1. It is recommended that for most applications only the translation components 123 be
used for Ci. An exception is the case where the Gij are collinear. A rotation component
may then be added to one grid point, to stabilize its associated rigid body mode for the
element.
3. The default for the dependent degree-of-freedom set should be used except in cases
where you want to redefine some or all REFC components as the dependent degree-of-
freedom set. If the default is not used for the dependent degree-of-freedom set:
The total number of components therein (that is, the total number of dependent
degrees-of-freedom defined by the element) must be equal to the number of
components in REFC (four components in the example).
The components therein must be a subset of the components mentioned in REFC and
Gij_Ci.
The coefficient matrix [Rm] in the constraints equation [RM] {um} + [Rn] {un} = 0
must be nonsingular, where um denotes the dependent degree-of-freedom set and un
denotes the independent degree-of-freedom set.
4. When the AMSES or AMLS eigenvalue solver is used, the UM data should be used when
loaded RBE3 have more than 500 DOF. Large loaded RBE3 will dramatically increase the
run times for AMSES or AMLS because the residual vectors will contain many DOF, unless
the UM data is used to make the loaded center GRID independent. When UM data is used,
the stiffness matrix becomes full for all the independent DOF of the RBE3, which can
increase the run time for very large RBE3. The number of grids can be reduced using a
HyperMesh macro. The macro is listed as Script 1068 in the Altair HyperWorks Script
Exchange:
www.altairhyperworks.com
5. UM data should not be used on large unloaded RBE3, as this will lead to an increase in the
run time.
6. Dependent degrees-of-freedom assigned by one rigid element may not also be assigned
dependent by another rigid element or by a multi-point constraint, and may not be
specified on SPC data.
7. In version 5.0, the RBE3 element calculation was modified in order to make the results
independent of the units used in the model. For this purpose, the weights of the
rotational degrees-of-freedom have been scaled by the square of the average distance
between the independent grid points and the reference point. This change will only affect
the results if independent grid points with rotational degrees-of-freedom exist in the RBE3
element. The previous RBE3 formulation can be enforced with the debug statement
debug, OLDRBE3,1.0.
9. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on RBE3 entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry
Description
Defines a pair of response quantities for computing the cross-power spectral density functions
in random response analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
1. This entry is required for computing the cross-power spectral density function. SID must
be selected with the I/O Option RCROSS. Fields RTYPE1, ID1, and COMP1 represent the
first response quantity and fields RTYPE2, ID2, and COMP2 represent the second response
quantity.
Keyword Description
Normal Y 7 or 13
Normal Z 8 or 14
Shear XY 9 or 15
Shear YZ 10 or 16
Shear XZ 11 or 17
Normal X at Z2 10 or 11
Normal Y at Z1 5 or 6
Normal Y at Z2 12 or 13
Shear XY at Z1 7 or 8
Shear XY at Z2 14 or 15
Translation X 1 or 7
Translation Y 2 or 8
Translation Z 3 or 9
Rotation X 4 or 10
Rotation Y 5 or 11
Rotation Z 6 or 12
Description
The RELOC bulk data entry can be used to map grid points from one location to another. This
entry allows you to translate, match, rotate or mirror grid points. The grid ID fields can be
input as either numeric or fully qualified references to grid points in the model.
Format
The format of this entry depends on the TYPE field input; the various versions are listed as
follows:
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Format 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
RELOC ID TYPE dx dy dz
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
TYPE This field specifies the type of mapping between grid points in a model. The
format of the RELOC card is different for different values of the TYPE field (see
Comment 2 for detailed information on each option).
Translation (Format 1)
GID1 Grid point identification number for translation to the reference point location.
Grid point GID1 is moved from its original location to the GID2 location.
GID2 Reference grid point identification number for translation. GID2 is used as a
reference point to move another grid point (GID1) from its original location to
the GID2 location.
Translation (Format 2)
dx, dy, dz Defines the distance that the referenced part (INSTNCE entry) should be
translated in the basic coordinate system. Each entry specifies the
corresponding distance moved in the X, Y, and Z axes, respectively (see
Comment 2).
(Real or blank)
Rotation (Format 1)
GID1 Specifies the identification number of a grid point that will be used as a center
of rotation based on the angles specified in the following fields.
ang_x, Defines the angle (in degrees) of rotation about the X, Y, and Z axes,
ang_y, respectively with the grid point (GID1) as the center of rotation. In a 2D
ang_z model, only ang_z is specified (see Comment 2).
(Real or blank)
Matching (Format 1)
GIDA1, Specifies the identification numbers of grid points (initial location) that will be
GIDA2, moved to match with the corresponding grid points GIDB1,2,3 (final location,
GIDA3 defined in the following fields). Any rotation, translation or mirroring required
to complete this matching process is accomplished internally by OptiStruct.
These three grid points cannot be collinear.
GIDB1, Specifies the identification numbers of grid points which will be matched with
GIDB2, the corresponding grid points defined in the GIDA1,2,3 fields. Any rotation,
GIDB3 translation or mirroring required to complete this matching process is
accomplished internally by OptiStruct. These three grid points cannot be
collinear.
Mirroring (Format 1)
GIDA1, Specifies the identification numbers of grid points about which the entire part
GIDA2, (defined via INSTNCE) will be laterally mirrored (flipped) by 180 degrees. The
GIDA3 grid points GIDA1,2,3 define an absolute plane of symmetry flip. Any rotation
or translation required to complete this mirroring process is accomplished
internally by OptiStruct. The three grid points specified for mirroring cannot be
collinear. In a 2D model, only GIDA1 and GIDA2 should be specified.
Comments
1. A RELOC entry can be referenced by a INSTNCE entry to define the location of a part in
the full model.
2. The following illustrations depict part relocation examples for each of the four TYPE field
options. All grid point ID’s used on the RELOC entry can belong to any part in the model.
Only their initial locations are relevant. All RELOC entries are evaluated before any parts
Translation - Format 1:
2 2 2
D dx dy dz
Where,
3. In a 2D model, only two TYPE options are allowed: ROTATE and MIRROR. All grid points in
the model should have the same Z coordinate. Rotation and mirroring are defined in the X-
Y plane.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
4. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on RELOC entries in the model. A fully qualified reference
(“PartName.number”) is similar to the format of a numeric reference. “PartName” is the
name of the part that contains the referenced local entry (part names are defined on the
BEGIN bulk data entry in the model). “number” is the identification number of a referenced
local entry in the part “PartName”. See Parts and Instances in the User’s Guide for
detailed information on the use of fully qualified references.
Description
Defines a static loading condition due to a centrifugal force field. It can also be used to define
the EXCITEID field (Amplitude “A”) of dynamic loads in RLOAD1, RLOAD2, TLOAD1 and TLOAD2
bulk data entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
RFORC E SID G C ID A R1 R2 R3
RAC C
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
1.0
Field Contents
G Grid point identification number through which the rotation vector acts.
RACC Scale factor of the rotational acceleration in revolutions per unit time
squared.
(Real)
Comments
1. The rotational forces that are created with an RFORCE entry for a constant angular
velocity (A), act in the positive radial direction. They represent the initial forces on the
structure due to a constant angular velocity. The rotational forces defined for a
constant angular acceleration (RACC), act in the same direction as the angular
acceleration. They would be opposite to the inertia forces on the structure due to a
constant angular acceleration.
The following plot shows that the RFORCE vector at node Gi is given by:
where,
angular velocity =
angular acceleration =
4. The RFORCE load is selected for use in a subcase by the Subcase Information entry LOAD.
5. The load vector generated by this entry can be printed using the I/O Option OLOAD.
7. For CONM1 and CONM2 entries, OptiStruct calculates the torque, due to rotation, as
follows:
Description
Bulk Data Entry for the inclusion of data required to perform Rotor Dynamics analysis in Modal
Frequency Response Analysis and/or Modal Complex Eigenvalue Analysis. The RGYRO Bulk Data
Entry is referenced by a corresponding RGYRO Subcase Information Entry in a specific
subcase.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
REFROTR <INTEGER > 0> rotid: Reference rotor ID. This field selects
the rotor that will be used in THE Rotor
dynamic analysis.
(no default)
SPDUNIT <RPM, FREQ> RPM: RPM specifies that the entries SPDLOW,
SPDHIGH and SPEED are input in
(No default) Revolutions Per Minute.
Default = 0.0
Default = 99999.0
Comments
1. Multiple RGYRO bulk data entries with the same RID cannot exist.
2. The values entered on some optional fields of the RGYRO bulk data entry depend on
factors such as: solution sequence used, type of analysis performed, and the value of
specific parameters. The following table shows some of the optional fields and their
relevance based on the listed factors. Synchronous analysis is performed when the rotor
speed is equal to the modal frequency (Complex eigenvalue analysis) or the frequency of
the forcing function (Frequency response analysis) and Asynchronous analysis is
Synchronous/
Required PARAM,
Solution Sequence Asynchronous Comment
Entry GYROAVG
Analysis
Asynchronous SPEED 0 -
Asynchronous SPEED -1 4
Asynchronous SPEED - 4
3. When multiple rotors are present within the system being modeled, one of the rotors is
chosen as a reference rotor. The speeds of the rest of the rotors are linearly dependent
of the reference rotor. Scale factors S1 and S2 are used to relate the speeds.
S1 S 2 * ref
Where,
ref
is the speed of the reference rotor
The scale factors S1 and S2 will be calculated by a least-mean-square fit of the relative
rotor speeds specified on the RSPINR entries (between SPDLOW to SPDHIGH of the
reference rotor). If the SPDLOW or SPDHIGH values are beyond the range specified on
the RSPINR entry, the values will be extrapolated from the RSPINR entry values.
4. PARAM, WR3 and PARAM, WR4 are necessary for rotor damping.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
RLOAD1 5 3 1
Field Contents
Comments
1. Dynamic load sets must be selected in the I/O Options or Subcase Information sections
with the command DLOAD = SID.
2. If any DELAY, DPHASE, TC, or TD fields are blank or zero, the corresponding , , C( ), or
D( ) will be zero. Either TC or TD may be blank or zero, but not both.
3. RLOAD1 loads may be combined with RLOAD2 loads only by specification on a DLOAD
entry. This means that the SID on a RLOAD1 entry must not be the same as that on a
RLOAD2 entry.
5. The type field identifies the type of dynamic excitation. Valid entries for this field are
listed alongside a description of the dynamic excitation with they invoke.
Type Description
6. When EXCITEID refers to an SPCD entry, the modal space will be augmented with
displacement vector(s) from linear static analysis with unit prescribed displacement at
each of the SPCD degrees-of-freedom.
7. All static structural loads can be referenced by EXCITEID by referring to the SID on the
structural load. The structural loads are FORCE, FORCE1, FORCE2, MOMENT, MOMENT1,
MOMENT2, PLOAD, PLOAD1, PLOAD2, PLOAD4, RFORCE, and GRAV. EXCITEID cannot
reference the LOAD and LOADADD Bulk Data entries.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
RLOAD2 5 3 7
Field Contents
Comments
1. Dynamic load sets must be selected in the I/O Options or Subcase Information sections
with the command DLOAD = SID.
2. If any DELAY, DPHASE, or TP fields are blank or zero, the corresponding , , or will
be zero.
3. RLOAD2 loads may be combined with RLOAD1 loads only by specification on a DLOAD
entry. This means that the SID on a RLOAD2 entry must not be the same as that on a
RLOAD1 entry.
5. The TYPE field identifies the type of dynamic excitation. Valid entries for this field are
listed below alongside a description of the dynamic excitation which they invoke.
Type Description
6. When EXCITEID refers to an SPCD entry, the modal space will be augmented with
displacement vector(s) from linear static analysis with unit prescribed displacement at
each of the SPCD degrees-of-freedom.
7. All static structural loads can be referenced by EXCITEID by referring to the SID on the
structural load. The structural loads are FORCE, FORCE1, FORCE2, MOMENT, MOMENT1,
MOMENT2, PLOAD, PLOAD1, PLOAD2, PLOAD4, RFORCE, and GRAV. EXCITEID cannot
reference the LOAD and LOADADD Bulk Data entries.
Description
This Bulk Data Entry is used for the specification of grids that determine the Rotor Line model.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Alternate Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
GRIDi <INTEGER > 0> List of grids that define the rotor line model.
No default
THRU Flag indicating that a range of grid identification numbers is defined. The
initial and final grids are specified on the fields either side of the field
(Optional)
containing the THRU flag.
Comments
1. All grid point entries specified on the ROTORG entry must be unique. The program will run
into an error, if duplicate grid entries are specified.
3. This ROTORG entry is used to define a Rotor Line model; therefore, for a specific
ROTORID, all grids specified on the ROTORG entry must be collinear. OptiStruct
automatically checks if the grids are collinear during a run.
4. If superelements are not used, connections between grids in the Rotor Line model and
those not listed on the ROTORG entry must be defined using MPC’s or rigid elements.
5. If superelements are used, connections between grids in the Rotor Line model and those
in the residual structure must be defined using MPC’s or rigid elements.
6. The mass of the Rotor Line model should be defined on the grids defined on the grids
specified by the ROTORG bulk data entry.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
RROD EID GA GB C MA C MB
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
RROD 14 1 1115 2
Field Contents
CMA,CMB Component number of one and only one dependent translational degree-
of-freedom in the global coordinate system assigned by you to either
GA or GB. Integer equal to 1, 2, or 3, or blank. Either CMA or CMB
must contain the integer and the other must be blank.
Comments
6. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on RROD entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry
in the model). “number” is the identification number of a referenced local entry in the part
“PartName”. See Parts and Instances in the User’s Guide for detailed information on the
use of fully qualified references.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
MCOMB Method for modal combination. Can be either absolute sum (ABS),
square root of sum of squares (SRSS), complete quadratic combination
(CQC), or Navy Reseach Laboratory’s SRSS (NRL).
Comments
3. Refer to Response Spectrum Analysis in the User’s Guide for more details.
Description
This bulk data entry is used to specify a set of reference rotor speed values for asynchronous
analysis in Rotor Dynamics.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
RSPEED 25 1500 50 5
No default
S1 <Real > 0.0> Specifies the first reference rotor speed in the set.
No default
Default = 1
Comments
1. The RSPEED bulk data entry is referenced by the SPEED field on the RGYRO bulk data
entry. If an integer value is specified in the SPEED field, multiple reference rotor speeds
specified in the RSPEED entry are used in asynchronous analysis.
2. In asynchronous frequency response analysis, if the RSPEED bulk data entry is referenced
in RGYRO, only the first frequency is considered. In complex eigenvalue analysis, the full
range specified by RSPEED is considered.
3. The following formula is used to populate the set of reference rotor speeds:
Ri ( S1 ( DS ) * i) i 1 to NDS
Description
This entry defines the relative spin rates between rotors during a rotor dynamic analysis in
Modal Complex Eigenvalue or Frequency Response solution sequences.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
GR ALPHAR1 ALPHAR2
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
0.03 5600
No default
GRIDA <Integer > 0> GRIDA identifies a grid on the Rotor Line Model.
GRIDB <Integer > 0> GRIDB identifies a grid on the Rotor Line Model.
SPDUNIT <RPM, FREQ> RPM: RPM specifies that the relative spin
rates are input in Revolutions Per
(No default) Minute.
SPTID <Integer > 0/Real> <Integer > 0> If an integer value (must be greater
than 0) is input, it references a
(No default) DDVAL bulk data entry that specifies
the relative rotor spin rates (see
comment 3).
ALPHAR1 <Real> Scale factor applied to the rotor mass matrix for
Rayleigh Damping (see comments 5 and 6).
Default = 0.0
ALPHAR2 <Real> Scale factor applied to the rotor stiffness matrix for
Rayleigh Damping (see comments 5 and 6).
Default = 0.0
Comments
1. A RSPINR entry must exist for each rotor line model defined using the ROTORG bulk data
entry.
2. GRIDA and GRIDB define the positive rotor spin direction. The vector connecting GRIDA
and GRIDB is the positive direction vector. The rotor axis is defined using the ROTORG bulk
data entry and the two grids (GRIDA, GRIDB) are also specified on the ROTORG bulk data
entry.
3. An integer or a real number can be input in the SPTID field. If SPTID is an integer, it
references a DDVAL bulk data entry that specifies the relative rotor spin rates. Each rotor
must be assigned the same number of spin rates. To determine relative spin rates, the
table entries which contain the sequence of spin rates are correlated. The i’th entry for
each rotor corresponds to the relative spin rates between rotors at RPMi/FREQi. The spin
rates for the reference rotor must be specified in ascending or descending order.
4. Rotor structural damping factor (GR) can be incorporated as either equivalent viscous
damping or structural damping depending on the solution sequence.
GR
BRotor structural
K rotor
WR3
Or,
Where,
Solution Sequence -
Damping Circulation
Analysis
[ BRC ] R1 [ M RC ] R2 [ K RC ]
Frequency Response i ([ BR ] R1 [ M R ] R 2 [ K R ])
R ( ref ) GR 1
(ASYNC) i (GR[ K R ] [ K 4 R ]) [ K RC ] [ K 4CR ]
[ BR ] R1 [M R ] R2 [KR ] [ BRC ] R1 [ M RC ] R2 [ K RC ]
Frequency Response i GR 1 R ( ref ) GR 1
(ASYNC + GYROAVG, -1) [KR ] [ K 4R ] [ K RC ] [ K 4CR ]
WR3 WR 4 WR3 WR 4
[ BRC ] R1 [ M RC ] R2 [ K RC ]
Frequency Response i ([ BR ] R1 [ M R ] R 2 [ K R ])
R ( ) GR 1
(SYNC) i (GR[ K R ] [ K 4 R ]) [ K RC ] [ K 4CR ]
[ BRC ] R1 [ M RC ] R2 [ K RC ]
R GR 1
[ BR ] R1 [M R ] R2 [KR ] [ K RC ] [ K 4CR ]
Frequency Response i
(SYNC + GYROAVG, -1)
GR 1
[KR ] [ K 4 R[ B
] C] [ M RC ] [ K RC ]
WR3 WR 4 R R1 R2
R GR 1
[ K RC ] [ K 4CR ]
[ BR ] R1 [M R ] R2 [KR ] [ BRC ] R1 [ M RC ] R2 [ K RC ]
Complex Eigenvalue i GR 1 ( ) GR 1
(ASYNC) [KR ] [RK 4 Rref] [ K RC ] [ K 4CR ]
WR3 WR 4 WR3 WR 4
[ BRC ] R1 [ M RC ] R2 [ K RC ]
R GR 1
[ BR ] R1 [M R ] R2 [KR ] [ K RC ] [ K 4CR ]
Complex Eigenvalue i
(SYNC)
GR 1
[KR ] [ K 4 R[ B
] C] [ M RC ] [ K RC ]
WR3 WR 4 R R1 R2
R GR 1
[ K RC ] [ K 4CR ]
Where,
[ BR ]
is the rotor viscous damping
[M R ]
is the rotor mass
[K R ]
is the rotor stiffness
[ K 4R ]
is the rotor material damping
C
[B ]
R
is the circulation, due to rotor viscous damping
C
[M ] R
is the circulation, due to rotor ‘mass’
[ K RC ]
is the circulation, due to rotor structural ‘stiffness’
C
[K 4 ] R
is the circulation, due to rotor material damping
R1 R2
and are used to define the Rayleigh viscous damping, as follows:
[ BR ]Rayleigh R1 [M R ] R2 [K R ]
WR3 and WR4 are defined by the parameters PARAM, WR3 and PARAM, WR4,
respectively.
7. Rotor damping is cumulative and caution should be exercised when multiple damping
effects are assigned.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C4 G5 C5 G6 … …
… …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
123 75 123 71
Field Contents
D/L Ratio of the diameter of the elastic tube to the sum of the lengths of all
segments.
Comments
1. Displacements are interpolated from the equations of an elastic beam passing through the
grid points. This is a linear method only element.
2. A blank field for C# indicates that all six degrees-of-freedom at G# are independent.
Since G1 must be independent, no field is provided for C1. Since the last grid point must
also be independent, the last field must be a G#, not a C#. For the example shown G1,
G3 and G6 are independent. G2 has six constrained degrees-of-freedom, while G4 and G5
each have three.
5. Rigid elements (including RSPLINE), unlike MPCs, form part of the model and do not need
to be selected from within a subcase definition.
7. The constraint coefficient matrix is affected by the order of the Gi Ci pairs on the RSPLINE
entry. The order of the pairs should be specified in the same order that they appear
along the line that joins the two regions. If this order is not followed, then the RSPLINE
will have folds in it that may yield some unexpected interpolation results.
8. The independent degrees-of-freedom that are the rotation components most nearly
parallel to the line joining the regions should not normally be constrained.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
Comments
2. The shell grid point must lie on the line connecting the two solid grid points. It can have
an offset from this line, which can not be more than 5% of the distance between the two
solid grid points. The shell grid points that are out of the tolerance will not be
constrained, and a fatal message will be issued. This tolerance is adjustable. Refer to
PARAM,TOLRSC and PARAM,SEPIXOVR.
The GRID option does not verify that the grids used are valid shell and/or solid grids.
5. It is recommended that the height of the solid element’s face is approximately equal to
the shell element’s thickness of the shell. The shell edge should then be placed in the
middle of the solid face.
6. The shell edge may coincide with the upper or lower edge of the solid face.
7. The RSSCON entry, unlike MPCs, is part of the model and does not need to be selected in
a subcase definition.
Description
Defines a rigid wall set as a union of rigid walls defined via RWALL entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
RWALADD SID S1 S2 S3 S4 S5 S6 S7
S8 S9 etc.
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
RWALADD 101 2 3 1 6 4
Field Contents
(Integer > 0)
Sj Set identification numbers of rigid wall sets defined via RWALL entries.
(Integer > 0)
Comments
1. Multipoint constraint sets must be selected with the Subcase Information command
RWALL=SID.
2. The Sj must be unique and may not be the identification number of a rigid wall set defined
by another RWALADD entry.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
X1 Y1 Z1 X2 Y2 Z2 DIA
MASS VX VY VZ
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
21 2 1
11 24 12
340 7 13 32
Field Contents
SLIDE – Sliding.
TIED – Tied.
SLFRIC – Sliding with friction.
GSID1 Grid set ID defining slave grids to be added to the rigid wall.
(Integer > 0)
GSID2 Grid set ID defining slave grids to be deleted from the rigid wall.
(Integer > 0)
(Real > 0)
G0 Grid identifier defining M, definition ignores Y0, Z0. Moving rigid wall.
(Integer > 0)
X0, Y0, Z0 Coordinates of a point M defining rigid wall location if G0 not defined.
Rigid wall does not move.
(Real)
Default = 0 (Integer = 0, …, 3)
X1, Y1, Z1 Coordinates of a point defining M1 for RWTYPE = PLANE, CYL, PARAL.
(Real)
(Real)
(Real > 0)
(Real > 0)
(Real)
Comments
1. RWALL must be selected in the subcase with RWALL = SID or by RWALADD. It can only
be selected in geometric nonlinear analysis subcases which are defined by an ANALYSIS =
NLGEOM, IMPDYN or EXPDYN subcase entry.
2. Initially the slave nodes can be defined at a distance lower than DIST.
3. Nodal thickness of rigid wall slave nodes is not taken into account.
4. IFILT defines the method for computing the friction filtering coefficient. Friction filtering
F T = α * F'T + (1 - α) * F'T-1
F T - Tangential force
α - filtering coefficient
IFILT = 1 – α = FFAC
Type Description
PARAL MM1 and MM2 define the parallelogram with the normal
as cross product MM1 x MM2.
SECT – Section Definition for Section Force Output in Geometric Nonlinear Analysis
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DT
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
G0, G1, G2 Grid points defining the local axes of the section. G0 and G1 define
the local x-axis while G0, G1, and G3 define the local xy-plane.
ELSET Element set ID. Only sets of SOLID, SHELL, ROD, BAR, and BEAM
elements can be used.
(Integer > 0)
IFRAME Flag for computing the center of the output coordinate system.
The local system is defined by G0, G1, and G2.
Comments
1. SECT output must be selected for time history output with XHIST. It is only available for
geometric nonlinear analysis subcases which are defined by an ANALYSIS = NLGEOM,
IMPDYN or EXPDYN subcase entry.
2. Moments are computed with respect to the section center defined by the parameter
IFRAME and expressed in the local section frame.
3. Normal force is the component normal to the XY plane of the section. The tangential
force is the component in the plane of the section.
G0, G1, G2 blank – the local system of the section is built from the grid points defining
the CORD1R or CORD3R.
The element set is created automatically from the elements intersected by the xy-
plane of CID.
Description
Defines a sensor for geometric nonlinear analysis. Sensors may be used to activate loads
(see NLOAD1).
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
… …
G1 G2 DMIN DMAX
SID1 SID2
SID1
C ID
RWID
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SENSOR 100 AC C EL 1
7 X 500.0 0.03
Field Contents
(Real > 0)
(Integer > 0)
X – X direction
Y – Y direction
Z – Z direction
XY – XY plane
YZ – YZ plane
ZX – ZX plane
(Real > 0)
(Real > 0)
G1 Grid ID 1.
(Integer > 0)
G2 Grid ID 2.
(Integer > 0)
(Real > 0)
(Real > 0)
(Integer > 0)
(Integer > 0)
(Integer > 0)
RWID Rigid Wall identifier, references the ID of a RWALL bulk data entry.
(Integer > 0)
Comments
2. For STYPE=TIME, the sensor is activated after the time delay (DELAY).
The time of activation of the sensor is the time at which the above criteria is first met
plus the time delay (DELAY).
4. For STYPE=DIST, the sensor is activated once the distance between G1 and G2 moves
outside the allowable range (between DMIN and DMAX).
The time of activation of the sensor is the time at which the above criteria is first met,
plus the time delay (DELAY).
5. For STYPE=SENS, the sensor is activated once the referenced sensor SID1 is activated.
The minimum activation duration is given by the time delay (DELAY). After this minimum
activation duration, the sensor is deactivated if referenced sensor SID2 is activated. If
there is no SID2 referenced, then the sensor is deactivated after the time delay.
7. For STYPE=OR, the sensor is activated once either of the referenced sensors (SID1 or
SID2) are activated.
8. For STYPE=NOT, the sensor is active whenever the referenced sensor SID1 is not active.
10. For STYPE=RWAL, the sensor is activated once the referenced rigid wall (RWID) is
impacted. The sensor is deactivated if there is no impact during a time equal to the time
delay (DELAY).
Description
Defines a set of grids, elements, design variables, MBD entities, mode numbers, frequencies or
times for reference by other input definitions.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ID9/ … … … … … … …
MODE9/
REAL9/
NAME9/
SID9
… …
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ID7 … ENDTHRU
The following set contains the grids 1, 17, 22, 23, 29, 33, 35, 48, 88, 93 and 102. It is
defined using a simple ID list (assuming that these GRID cards are present in the Bulk
Data).
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
88 93 17 1 23 29 35 48
33 102 22
Example 2
The following set contains the elements 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 33,
34, 34, 35, 36, 37, 38, 41, 42, 43, 44, 45, 94, 95, 96. 97, 98, 99, 106, 107, 108, 109, 110,
111, 120, 121 and 125. It is defined using a combination of ID ranges and lists.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
11 THRU 22
Example 3
The following set includes any element included in sets 29, 30 or 31. It is defined as
Boolean set.
SET 50 ELEM OR
29 30 31
Example 4
The following set defines GRID/Component list; intended for use by PFMODE.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SET 11 GRIDC
12 T1 15 R2 128 T3
Example 5
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SET 11 LABEL
Example 6
The following set defines list of all elements with specific properties.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 7
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PLOTEL
Field Contents
TYPE Identifies what type of entities the set is comprised of. See comment 2
for description of the types.
SUBTYPE Indicates how the set is defined. See comment 2 for description of
subtypes.
ID# ID list. Only valid for certain combinations of TYPE and SUBTYPE. The
entity to which the ID corresponds depends on the TYPE and SUBTYPE
of the set (see comment 2).
MODE# Mode number list. Only valid when TYPE is MODE (see comment 2).
REAL# Real value list. Only valid when TYPE is FREQ or TIME (see comment
2).
No default (Real)
NAME# Keyword list. Only valid for certain combinations of TYPE and SUBTYPE.
The keyword EXCEPT is allowed only as the first entry in a keyword list.
X1, Y1, Z1 X, Y & Z coordinates of two opposing corners of a cuboid. Only valid
X2, Y2, Z2 when SUBTYPE is BBOX (see comment 2).
No default (Real)
G1, G2 Grid ID’s (G1, G2) can be used instead of (X1, Y1, Z1), (X2, Y2, Z2)
data (see field descriptions above). G1, G2 should be defined in the
basic coordinate system (CP field on the GRID entries should be blank).
ALL Keyword used for ID lists to indicate that all IDs of the appropriate
entity type are to be included in the set.
THRU Keyword used for ID ranges to indicate that all IDs between the
preceding ID and the following ID are to be included in the set.
EXCEPT Keyword used for ID ranges and keyword lists to indicate that the
following IDs or keywords are to be excluded from the set.
When ALL is given as the first entry for an ID list, EXCEPT may be given
as the second entry, in which case all subsequent IDs are excluded from
the set of ALL entities of the defined TYPE.
ENDTHRU Optional keyword used after EXCEPT to indicate the end of an excluded
ID list definition.
Comments
1. SID must be unique with respect to all other SET definitions (regardless of type). It must
also be unique with respect to any SURF entries and any legacy SET/PSET I/O Options
definitions.
2. The following table describes subtype combinations and the set TYPEs for which they are
valid.
LABEL LIST List of arbitrary labels. Each label must start with a
or letter and contain only letters or digits.
undefined
PLY LIST This is a set of ply ID’s defined in the PLY or PCOMPG
or data entries.
undefined
3. SET definitions using IDs may refer to non-existing entities. This is allowed, but the
actual SET will contain only grids or elements which are actually present in the structure.
4. The Boolean operators OR, AND, NOT and MINUS are recognized for SET combinations.
These operators are described here:
Operator Description
AND An entity is included in the SET if it is included in all of the listed sets. Is
the entity in set1 and set2 and set3 …?
NOT An entity is included in the SET if it is not included in the listed set. Is
the entity in set1?; if not then it is included in this set.
MINUS An entity is included in the SET if it is included in the first set, but not in
the second set. Only two sets may be listed for when this operator is
used.
5. Boolean SET definitions can only be used when all listed sets are of the same TYPE.
6. Boolean SET definitions can reference other Boolean sets, but circular references must be
avoided. Boolean SET can be defined only for GRID, ELEM, or RIGID set types.
7. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on SET entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN bulk data entry
in the model). “number” is the identification number of a referenced local entry in the part
“PartName”. See Parts and Instances in the User’s Guide for detailed information on the
use of fully qualified references.
The SET bulk data entry can be used in the global part to reference SET’s defined within
different parts. These SET entries in the global part can contain fully qualified references
to part-specific SET data only if logical operators (OPERATOR field) are used. For
example:
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ID8 etc.
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SET1 3 31 62 93 124 16 17 18
19
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
17 57
Field Contents
(Integer > 0)
(Integer > 0 or "THRU, ENDTHRU, and EXCEPT"; for the "THRU" option,
ID1 < ID2)
Comments
2. All set ID’s must be unique for all bulk data SET, SET1, SET3, and solution control SET
data.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SET3 1 PROP 11 12 13 15 18 21
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
TYPE Set type (Character). Valid options include "GRID," "ELEM," and "PROP."
(Integer > 0)
Comments
1. If the set type is PROP, then a list of elements associated with the property ID's listed is
created.
2. All set ID’s must be unique for all bulk data SET, SET1, SET3, and solution control SET
data.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SLOAD SID S1 F1 S2 F2 S3 F3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
F# Load magnitude.
No default (Real)
Comments
SOLVTYP – Solver Selection for Static Analysis and Geometric Nonlinear Implicit Analysis
Description
This bulk data entry can be used to define the solver type to be used for linear and nonlinear
static analysis and geometric nonlinear implicit analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
ORDM
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SOLVTYP 4 PC G
FAI
Alternate Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SOLVTYP 1 MUMPS
Field Contents
Default = BCS - for linear static analysis and geometric nonlinear implicit
dynamic analysis (ANALYSIS = IMPDYN);
NO - No Pre-conditioner
DJ - Diagonal Jacobi
b||
ORDM Ordering method for the MUMPS solver (see comments 8 and 9).
Comments
1. SOLVTYP bulk data must be referenced by a SOLVTYP subcase statement. It only applies
to linear static subcases, geometric nonlinear implicit static analysis (ANALYSIS=NLGEOM)
and geometric nonlinear implicit dynamic analysis (ANALYSIS=IMPDYN).
3. MUMPS is the default non-symmetric solver for nonlinear contact analysis when friction is
present; it is also available as an optional symmetric solver for static runs. MUMPS is SMP
parallelized. Generally, MUMPS performance is similar to or better than the performance of
BCS, especially for 2D models.
6. The performance of the iterative solver depends on the conditioning of the stiffness
matrix. For compact solid models, the iterative solver may perform considerably better
than the direct solver in terms of memory usage and elapsed times for a single linear
static subcase. In the case of multiple linear static subcases, the iterative solver may
perform worse than the direct solver. The breakeven point is at about 4-6 subcases.
The performance depends on model, hardware, operating system, and potentially the
system load. The performance may be below expectations on Itanium-based computers.
7. When the automatic solver option (SOLVER = AUTO) has been chosen, PCG is used first,
the solver will be changed automatically to direct solver (BCS) if PCG performance is
estimated slower than direct solver. In this case, direct solver will be used for the
remainder of the run.
9. For further information about the MUMPS solver ordering method (ORDM) options, refer to
the MUMPS 4.10 manual.
Description
Defines sets of single-point constraints, enforced displacements for static analysis, and
thermal boundary conditions for heat transfer analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SPC SID G C D G C D
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
C Component numbers.
(Integer zero or blank for scalar points, or up to six unique digits (0 < digit <
6) may be placed in the field with no embedded blanks for grid points. The
components refer to the coordinate system referenced by the grid points.)
(Real)
Comments
7. For static and dynamic analyses, when the SPSYNTAX setting on the SYSSETTING I/O
option is set to CHECK (default) or STRICT, it is required for grid/component pairs (G#/
C#) that the component be 0 or blank when the grid reference is a scalar point (SPOINT),
and that the component be > 1 when the grid reference is a structural grid point (GRID).
When SPSYNTAX is set to MIXED, it is allowed for grid/component pairs (G#/C#) that the
grid reference be either a scalar point (SPOINT) or a structural grid point (GRID) when the
component is 0, 1 or blank; interpreting all of these as 0 for scalar points and as 1 for
structural grids. When the component is greater than 1, the grid reference must always
be a structural grid (GRID).
8. For linear steady-state heat transfer analysis, an SPC may be used to define a
temperature boundary condition. For thermal boundary conditions, the component should
be 0 or blank when the SPSYNTAX setting on the SYSSETTING I/O option is set to
CHECK(default) or STRICT. When SPSYNTAX is set to MIXED 1 is also accepted as the
component.
9. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on SPC entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry
in the model). “number” is the identification number of a referenced local entry in the part
“PartName”. See Parts and Instances in the User’s Guide for detailed information on the
use of fully qualified references.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SPC 1 SID C G1 G2 G3 G4 G5 G6
G7 G8 G9 -etc.-
Alternate Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SPC 1 3 2 7 3 10 9 6 5
THRU 8 33 71
Field Contents
(Integer > 0)
(Integer zero or blank for scalar points, or up to six unique digits (0 < digit <
6) may be placed in the field with no embedded blanks for grid points. The
components refer to the coordinate system referenced by the grid points.)
(Integer > 0)
Comments
4. Multiple “thru” sequences can be used on a single card, and can span across continuation
lines.
6. If the "thru" comment is used, G1 and G2 must exist, but the grid points between G1 and
G2 are not required to exist.
7. For static and dynamic analyses, when the SPSYNTAX setting on the SYSSETTING I/O
option is set to CHECK (default) or MIXED, it is allowed that when grid lists are provided
for a given component, that the grid references be either scalar points (SPOINT) or
structural grid points (GRID) when the component is 0, 1 or blank; interpreting all of these
as 0 for scalar points and as 1 for structural grids. When SPSYNTAX is set to STRICT, it
is required for grid/component pairs (G#/C#) that the component be 0 or blank when the
grid references are to scalar points (SPOINT), and that the component be > 1 when the
grid references are to structural grid points (GRID). When the component is greater than
1, the grid references must always be a structural grid (GRID).
8. For linear steady-state heat transfer analysis, SPC1 may be used to define temperature
boundary conditions; however, unless paired with an SPCD entry, the enforced
temperature is 0.0. For thermal boundary conditions, the component should be 0 or blank
when the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT. When SPSYNTAX is set to MIXED, 1 is also accepted as the component.
Description
Defines a single-point constraint set as a union of single-point constraint sets defined via SPC
or SPC1 entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
S8 S9 -etc-
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
Comments
1. The Si field should not reference the identification number of a single-point constraint set
defined by another SPCADD entry.
4. If all Si are non-existent the solver will exit with an error termination.
5. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on SPCADD entries in the model. A fully qualified reference
(“PartName.number”) is similar to the format of a numeric reference. “PartName” is the
name of the part that contains the referenced local entry (part names are defined on the
BEGIN Bulk Data Entry in the model). “number” is the identification number of a
referenced local entry in the part “PartName”. See Parts and Instances in the User’s
Guide for detailed information on the use of fully qualified references.
Description
Defines an enforced displacement value for static analysis, an enforced displacement, velocity
or acceleration for dynamic analysis and a thermal boundary condition for heat transfer (or
transient heat transfer) analysis. It can also be used to define the EXCITEID field (Amplitude
“A”) of dynamic loads in RLOAD1, RLOAD2, TLOAD1 and TLOAD2 bulk data entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SPC D SID G C D G C D
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(6 > Integer > 0; up to six unique such digits may be placed in the field with
no embedded blanks)
D Value of enforced motion for all grids and components designated by G and
C.
(Real)
Comments
2. For use in linear static and linear steady state heat transfer analyses, the load set
identification number must be selected by the LOAD subcase information command.
3. Values of D will override the values specified on an SPC bulk data entry if selected for use
in the same subcase.
4. For use in dynamic analysis, the load set identification number must be referenced by the
EXCITEID field of an RLOAD1, RLOAD2, TLOAD1, or TLOAD2 bulk data entry that has
enforced motion specified in its TYPE field.
5. The bulk data LOAD combination entry cannot combine an SPCD load.
8. For use in transient heat transfer analysis, the load set identification number must be
referenced by the EXCITEID field of a TLOAD1 or TLOAD2 bulk data entry that has
enforced temperature specified in its TYPE field (TYPE = 1).
9. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on SPCD entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry
in the model). “number” is the identification number of a referenced local entry in the part
“PartName”. See Parts and Instances in the User’s Guide for detailed information on the
use of fully qualified references.
SPOINT – Scalar-Point
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Alternate Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SPOINT 3 18 1 4 16 2 6 THRU
8 47 99 THRU 128
Field Contents
Comments
1. A scalar point defined by its appearance on the connection entry for a scalar element
(see the CELAS, CMASS, and CDAMP entries) need not appear on an SPOINT entry.
3. This entry is used primarily to define scalar points appearing in single-point or multipoint
constraint equations to which no scalar elements are connected.
4. If the alternate format is used, all scalar points ID1 through ID2 are defined. ID1 must be
less than ID2.
5. Alternate format can be combined with regular format, and it can span across
continuation lines.
Description
Defines the stacking information and stacking sequence for ply-based composite definition.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PLYID7 …
... ...
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
1010400 1020400
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
STAC K 2
SUB 1 top 11 12 13 14
SUB 2 left 21 22 23 24
SUB 3 right 31 32 33 34
SUB 4 middle 41 42 43
INT 14 21
INT 14 31
INT 21 41
INT 43 31
LAM Laminate option. If blank, all plies must be specified and all stiffness terms are
developed. The following options are supported:
SYM: Only plies on the bottom half of the composite lay-up need to be
specified. These plies are automatically symmetrically reflected to the
top half of the composite and given consecutive numbers from bottom
to top.
MEM: All plies must be specified, but only membrane terms are developed.
BEND: All plies must be specified, but only bending terms are developed.
SMEAR: All plies must be specified, stacking sequence is ignored, and MID1 is
set equal to MID2 on the derived equivalent PSHELL, while MID3, MID4,
TS/T, and 12I/T**3 are set to zero.
SMEARZ0: All plies must be specified, stacking sequence is ignored. While the
laminate is still considered to be made of homogenized (smeared)
material, the effect of offset Z0 is taken into account. Hence, if Z0 is
not equal to -0.5*Thick, the equivalent PSHELL will include MID1,
MID2 and MID4. MID3 is still set to zero, that is no transverse shear
deformation is considered.
SMCORE: All plies must be specified. The last ply specifies core properties and
the previous plies specify face sheet properties. The face sheet
properties are calculated without regard for stacking sequence; half of
the total face sheet thickness is then placed on top of the core, and
half is placed on the bottom, to produce a symmetric laminate.
Stiffness of the core is ignored while its density is included in inertia
calculations.
SYMEM: Only plies on the bottom half of the composite lay-up need to be
specified. These plies are automatically symmetrically reflected to the
top half of the composite and given consecutive numbers from bottom
to top. Only membrane terms are developed for the full laminate.
SYBEND: Only plies on the bottom half of the composite lay-up need to be
specified. These plies are automatically symmetrically reflected to the
top half of the composite and given consecutive numbers from bottom
to top. Only bending terms are developed for the full laminate.
SYSMEAR: Only plies on the bottom half of the composite lay-up need to be
specified. These plies are automatically symmetrically reflected to the
top half of the composite and given consecutive numbers from bottom
to top. Stacking sequence is ignored, and MID1 is set equal to MID2
on the derived equivalent PSHELL, while MID3, MID4, TS/T and 12I/
T**3 are set to zero.
Default = blank, that is all plies must be specified (SYM, MEM, BEND, SMEAR,
SMCORE, SYMEM, SYBEND or SYSMEAR)
Comments
1. The STACK card is used in combination with the PCOMPP and PLY cards to create
composite properties through the ply-based definition.
2. Plies are listed from the bottom surface upward, in respect to the element’s normal
direction. In the image below, (a) shows the stacking sequence for a non-symmetrical
laminate, and (b) shows the stacking sequence for a symmetrical laminate.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SUPORT 16 215
Field Contents
C# Component numbers.
Comments
1. The SUPORT entry specifies reference degrees-of-freedom for rigid body motion. It is not
intended to be used in place of a constraint (SPCi entry or PS on the GRID entry, for
example).
2. SUPORT and/or SUPORT1 entries are required to activate inertia relief unless PARAM,
INREL, -2 is specified, then SUPORT and/or SUPORT1 entries are not required.
5. An alternative to SUPORT is the SUPORT1 entry, which is requested by the SUPORT1 I/O
Options and Subcase Information command.
Description
Defines determinate reaction degrees-of-freedom in a free body. The SUPORT1 bulk data
entry must be requested in the I/O Options or Subcase Information sections by the SUPORT1
data selection command.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SUPORT1 5 16 215
Field Contents
C# Component numbers.
1. SUPORT1 bulk data entries will not be used unless specifically selected in a subcase
definition by the SUPORT1 subcase information entry.
3. The SUPORT1 bulk data entry must be requested in the I/O Options or Subcase
Information sections by the SUPORT1 data selection command. The degrees-of-freedom
specified on SUPORT1 will be combined with those on the SUPORT entry.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
... ...
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
... ...
A surface may also be defined using a form of the SET bulk data entry. With this approach,
the surface is composed of all selected 2D elements and the external faces of all selected 3D
elements; that is, those faces that are not connected to any other 3D elements faces in the
model.
To use this format, the SURF keyword is used in place of the SET keyword and the TYPE must
be ELEM. All methods for defining a set of type ELEM are valid for this form of surface
definition. Refer to the SET bulk data entry.
Field Contents
GA# Identification number of a grid point at the corner of the desired face of a
3D element.
NORMAL Identifies the normal direction for a face of the surface. The normal of a
face of a surface may be different from the normal of the underlying
elements.
Default = 0 (0 or 1)
Comments
For PENTA elements: Quad faces: Identification number of a grid point at a corner of
the desired face that is diagonally opposite GA.
For TETRA Identification number of a grid point at the corner opposite the
elements: desired face.
Tria faces: GA and GB must specify the grids on the edge of the
face that borders the quadrilateral face, and the
grids must be ordered so that they define an inward
normal using the right hand rule.
Description
Defines values of parameters used during the CWELD and CSEAM connectivity search.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Alternate Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
-etc.-
SHOWAU 1
X
Field Contents
While textual values are recommended for clarity, their integer equivalents will
also be read. The available parameters and their values are listed below (click
the parameter name for parameter descriptions).
Parameter Value
SHOWAUX 0, 1, 2, 3
Default = 0
Comments
1. The SWLDPRM entry changes the default settings of parameters for the CWELD and
CSEAM connectivity entries. None of the parameters of this entry are required. The
default settings should be changed only for diagnostic and debug purposes. Only one
SWLDPRM entry is allowed in the bulk data section.
2. Connectivities are created for the CSEAM element and for the CWELD element with
PARTPAT, ELPAT, ELEMID and GRIDID formats. With the parameters on this entry, you
can debug and alter the search algorithm which creates these connector elements.
3. Before the presence of any keyword of the connector, that is CWELD and CSEAM, the
parameter set on the entry will be regarded as “global,” and it will be applied to all of the
connector elements unless it only serves a specific type of connector.
4. Any parameter following a connector keyword will only be applied to the element type
specified by the keyword until the presence of another keyword.
5. Blank fields are allowed in this entry. However, blank fields are not allowed between the
parameter name and the corresponding parameter value or between the connector
keyword and the parameter name followed. If the parameter name or the connector
keyword is located just before the continuation field, then the following content must be
placed in the first field after the continuation marker.
6. Further detailed information about the individual connector elements can be found on the
pertinent CWELD and CSEAM bulk data entries.
7. Some of the above parameters apply only to selected connector types. Such information
is provided within the detailed description of individual parameters.
CHKRUN NO, 0, YES, or 1 Stop or allow the run after the connectivities of all the
connector elements have been generated. This
Default = NO parameter must be global, meaning it should be placed
before the presence of the first connector keyword.
CNRAGLI 90.0 < Real < 180.0 For CSEAM element only. Minimum angle allowed
or -1.0 between the free edges (no other element shares
these edges) of shell elements EIDSA and EIDEA or
Default = 160.0 EIDSB and EIDEB. The CSEAM element will be rejected
if this minimum angle is violated. See the following
figure.
CNRAGLO 0.0 < Real < 90.0 For CSEAM element only. Maximum angle allowed
or -1.0 between the normal vectors of EIDSA and EIDEA or
EIDSB and EIDEB. The CSEAM element will not be
Default = 20.0 generated if the angle between these two normal
vectors is greater than the value of CNRAGLO. This
prevents generating single CSEAM element across a very
curved shell configuration. See the following figure.
GMCHK NO, 0, YES, 1, FULL, or A switch to perform geometry check for certain
2 types of connector elements (presently it only
applies to CSEAM).
Default = NO
If NO or 0, no geometry check.
GSMOVE Integer > 0 Maximum number of times GS for the CWELD (PARTPAT or
ELPAT format) or GS/GE for the CSEAM is moved in cases
Default = 0 when not all auxiliary points have projections onto the patch
of shells.
GSPROJ 0.0 < Real < 90.0 Maximum angle allowed between the normal vectors of
or -1.0 Shell A and Shell B. Shell A and Shell B are located on
the two different shell surfaces that need to be
Default = 20.0 connected by the connector element. The connector
element will not be generated if the angle between
these two normal vectors is greater than the value of
GSPROJ. This prevents the generation of connector
elements between shell components that depart from
being parallel to each other. See the following figure.
GSTOL Real > 0.0 Presently it only applies to CSEAM. Maximum distance
between GS-SA, GS-SB, GE-EA and GE-EB for CSEAM.
Default = 0.0 See the following figure.
NREDIA 0 < Integer < 4 Maximum number of times the diameter (which is used in
locating auxiliary points) is reduced by half when not all
Default = 0 auxiliary points have projections onto the patch of shells.
This parameter is for CWELD (PARTPAT and ELPAT) only.
PROJTOL 0.0 < Real < 0.5 Tolerance to accept the projected points (from GS for
CWELD and from GS/GE for CSEAM) if the computed
Default = 0.05 coordinates of the projection point lies outside the shell
element but is located within PROJTOL×(dimension of
the shell element). PROJTOL is only activated when a
search without PROJTOL finds no candidate shell to
build connectivity for a connector element. This
prevents the search from picking the wrong shell
element in cases when PROJTOL is not needed.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
f1 g1 f2 g2 f3 g3 f4 g4
f5 g5 … … … … … …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABDMP 2
1
Field Contents
Damping value.
No default (Real)
Comments
1. Modal damping tables must be selected in the Subcase Information section, using the
SDAMPING command. This form of damping is used only in the modal method of frequency
response analysis.
3. The frequency values, , must be specified in either ascending or descending order, but
not both.
4. Discontinuities may be specified between any two points except the two starting points
or two end points. For example, in Figure 1 discontinuities are allowed only between
points f2 through f7. Also, if g is evaluated at a discontinuity, then the average value of
g is used. In Figure 1, the value of g at f=f3 is g = (g3+g4)/2.
6. Any or entry may be ignored by placing 'SKIP' in either of the two fields used for
that entry.
7. The end of the table is indicated by the existence of 'ENDT' in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag 'ENDT'.
where, f is input to the table and g is returned. The table look-up is performed
using linear interpolation within the table and linear extrapolation outside the table using
the two starting or end points. See Figure 1. No warning messages are issued if table
data is input incorrectly.
9. The KDAMP option, on the PARAM card, may be used to switch between viscous and
structural damping. Viscous is the default and is used when PARAM, KDAMP is not
present.
KDAMP Result
1 (default) B matrix
-1 (1+ig)K matrix
10. If TYPE is 'G' or blank, the damping values are in units of equivalent viscous dampers
as follows:
If TYPE is 'CRIT', the damping values are in units of fraction of critical damping C/C0.
If TYPE is 'Q', the damping values are in the units of amplification or quality factor, Q.
These constants are related by the following equations:
The TYPE field in the TABDMP1 bulk data entry should be set to CRIT. This TABDMP1 bulk
data entry is referenced by the SDAMPING subcase information entry.
Set the damping value (field ) in the TABDMP1 bulk data entry equal to half of the
value of PARAM, G (set the constant value to C/C0).
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
x1 y1 x2 y2 x3 y3 x4 y4
x5 y5 … … … … … …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABLED1 32
Field Contents
Comments
4. Any x, y pair may be ignored by placing 'SKIP' in either of the two fields used for that
entry.
5. The end of the table is indicated by the existence of 'ENDT' in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag 'ENDT'.
where, x is input to the table and y is returned. The table look-up is performed using
interpolation within the table and linear extrapolation outside the table using the two
starting or end points. See Figure 1. The algorithms used for interpolation or
extrapolation are:
7. Linear extrapolation is not used for Fourier transform methods. The function is zero
outside the range of the table.
9. Tabular values on an axis if X-Axis or Y-Axis = LOG must be positive. A fatal message will
be issued if an axis has a tabular value < 0.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABLED2 TID X1
x1 y1 x2 y2 x3 y3 x4 y4
x5 y5 … … … … … …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABLED2 15 -10.5
Field Contents
No default (Real)
No default (Real)
Comments
4. Any x, y pair may be ignored by placing 'SKIP' in either of the two fields used for that
entry.
5. The end of the table is indicated by the existence of 'ENDT' in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag 'ENDT'.
where, x is input to the table and y is returned. The table look-up is performed using
interpolation within the table and linear extrapolation outside the table using the two
starting or end points. See Figure 1. No warning messages are issued if table data is
input incorrectly.
7. Linear extrapolation is not used for Fourier transform methods. The function is zero
outside the range of the table.
8. For frequency-dependent loads, X1 and x# are measured in cycles per unit time.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABLED3 TID X1 X2
x1 y1 x2 y2 x3 y3 x4 y4
x5 y5 … … … … … …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
No default (Real)
Comments
4. Any x, y pair may be ignored by placing 'SKIP' in either of the two fields used for that
entry.
5. The end of the table is indicated by the existence of 'ENDT' in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag 'ENDT'.
where, x is input to the table and y is returned. The table look-up is performed using
interpolation within the table and linear extrapolation outside the table using the two
starting or end points. See Figure 1. No warning messages are issued if table data is
input incorrectly.
7. Linear extrapolation is not used for Fourier transform methods. The function is zero
outside the range of the table.
8. For frequency-dependent loads, X1, X2, and x# are measured in cycles per unit time.
Description
Defines the coefficients of a power series for use in generating frequency-dependent and
time-dependent dynamic loads. Also contains parametric data for use with the table.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABLED4 TID X1 X2 X3 X4
A0 A1 A2 A3 A4 A5 A6 A7
A8 … … … … … … …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
X# Table parameters.
A# Coefficients.
No default (Real)
Comments
2. The end of the table is indicated by the existence of 'ENDT' in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag 'ENDT'.
where, x is input to the table, y is returned and N is the number of pairs. Whenever x <
X3, use X3 for x; whenever x > X4, use X4 for x. There are N + 1 entries in the table.
There are no error returns from this table look-up procedure.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABFAT ID y1 y2 y3 y4 y5 y6 y7
y8 … …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
No default (Real)
Comments
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABLEM1 TID
x1 y1 x2 y2 x3 y3 -etc.- "ENDT"
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABLEM1 32
Field Contents
(Integer > 0)
(Real)
4. Any xi- yi pair may be ignored by placing 'SKIP' in either of the two fields.
5. The end of the table is indicated by the existence of "ENDT" in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag "ENDT".
y= yT(x)
where, x is input to the table and y is returned. The table look-up is performed using
linear interpolation within the table and linear extrapolation outside the table using the
two start or end points (see figure). No warning messages are issued, if the table data is
input incorrectly.
y = zyT(x)
Where. x is input to the table, y is returned, and z is supplied from the MAT4 entry.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABLEM2 TID X1
x1 y1 x2 y2 x3 y3 -etc.-
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABLEM2 15 -10.5
Field Contents
(Integer > 0)
X1 Table parameter.
(Real)
(Real)
Comments
4. Any xi-yi pair may be ignored by placing 'SKIP' in either of the two fields.
5. The end of the table is indicated by the existence of "ENDT" in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag "ENDT".
y= zyT(x – X1)
where, x is input to the table, y is returned, and z is supplied from the MATi entry. The
table look-up is performed using linear interpolation within the table and linear
extrapolation outside the table using the two start or end points (see figure). No warning
messages are issued if table data is input incorrectly.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABLEM3 TID X1 X2
x1 y1 x2 y2 x3 y3 -etc.-
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Real)
1. Tabular values for xi must be specified in either ascending or descending order, but not
both.
2. Discontinuities may be specified between any two points except the two start points or
two end points. For example, in the figure below, discontinuities are allowed only
between points x2 through x7 . Also, if y is evaluated at a discontinuity, then the average
value of y is used. In the figure, the value of y at x = x3 is y = (y3+y4)/2 .
4. Any xi-yi pair may be ignored by placing 'SKIP' in either of the two fields.
5. The end of the table is indicated by the existence of "ENDT" in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag "ENDT".
where, x is input to the table, y is returned and z is supplied from the MATi entry. The
table look-up is performed using linear interpolation within the table and linear
extrapolation outside the table using the two starting or end points (see figure). No
warning messages are issued if table data is input incorrectly.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABLEM4 TID X1 X2 X3 X4
A0 A1 A2 A3 A4 A5 -etc.-
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
Xi Table parameters.
Ai Coefficients.
(Real)
2. The end of the table is indicated by the existence of "ENDT" in the field following the last
entry. An error is detected if any continuations follow the entry containing the end-of-
table flag "ENDT".
where, x is input to the table, y is returned, and z is supplied from the MATi entry.
Whenever x < X3 , use X3 for x; whenever x > X4 , use X4 for x. There are N + 1 entries in
the table. There are no error returns from this table look-up procedure.
Description
Defines a tabular function for use as stress-strain curve in elasto-plastic material properties
MATS1, MATX33, MATX65, MATHF, as well as material curve in nonlinear material properties
MATX36, MATX42, and MATX70.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABLES1 TID
x1 y1 x2 y2 x3 y3 x4 y4
x5 y5 … … … … … …
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABLES1 32
Field Contents
Comments
4. Any x, y pair may be ignored by placing 'SKIP' in either of the two fields used for that
entry.
5. The end of the table is indicated by the existence of 'ENDT' in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag 'ENDT'.
where, x is input to the table and y is returned. The table look-up is performed using
interpolation within the table and linear extrapolation outside the table using the two
starting or end points. See Figure 1. The algorithms used for interpolation or
extrapolation is:
8. Linear extrapolation is not used for Fourier transform methods. The function is zero
outside the range of the table.
10. Some warning or error messages are issued if table data in input incorrectly. However,
since TABLES1 can serve different and distinct purposes, error checking is limited.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABLEST TID
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABLEST 101
Field Contents
(Integer > 0)
Ti Temperature values.
(Real)
(Integer > 0)
1. TIDi must be unique with respect to all TABLES1 and TABLEST table identification
numbers.
3. The end of the table is indicated by the existence of ENDT in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag ENDT.
4. This table is referenced by MATS1 entries that define elasto-plastic (TYPE = "PLASTIC")
materials.
Description
Defines power spectral density as a tabular function of frequency for use in random analysis.
Referenced on the RANDPS entry.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
f1 g1 f2 g2 f3 g3 f4 g4
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TABRND1 3
etc.
Field Contents
(Integer > 0)
XAXIS Specifies a linear or logarithmic interpolation for the x-axis. See comment
6.
YAXIS Specifies a linear or logarithmic interpolation for the y-axis. See comment
6.
(Real)
Comments
2. Jumps between two points ( ) are allowed, but not at the end points.
4. Any f-g entry may be ignored by placing the BCD string "SKIP" in either of the two field
used for that entry.
5. The end of the table is indicated by the existence of the BCD string "ENDT" in either of
the two fields following the last entry. An error is detected if any continuations follow
the entry containing the end-of-table flag "ENDT".
G = g T(F)
where, F is input to the table and G is returned. The table look-up gT(f) is performed
using linear extrapolation outside the table using the last two end points at the
appropriate table end. At jump points, the average gT(F) is used. There are no error
returns from this table look-up procedure.
Description
Defines temperature at grid points for determination of Thermal Loading and Stress recovery.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
T Temperature.
(Real)
Comments
2. From one to three grid point temperatures may be defined on a single entry.
Description
Defines a temperature value for all grid points of the structural model that have not been
given a temperature on a TEMP entry.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TEMPD 1 216.3
Field Contents
(Integer > 0)
(Real)
Comments
Description
Defines values for the initial conditions of variables used in structural transient analysis and
explicit analysis. Both displacement and velocity values may be specified at independent
degrees-of-freedom.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TIC SID G C U0 V0
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
C Component numbers.
(Any one of the integers 1 through 6 for grid points, integer zero or blank for
scalar points)
(Real or blank)
V0 Initial velocity.
(Real or blank)
Comments
1. Transient analysis initial condition sets must be selected with the IC subcase information
command.
2. If no TIC set is selected in the Subcase Information section, all initial conditions are
assumed to be zero.
3. Initial conditions for coordinates not specified on TIC entries will be assumed to be zero.
4. In direct transient analysis, wherein the TIC bulk data entry is selected by an IC subcase
information command, G may reference only grid or scalar points.
6. The initial conditions for the independent degrees-of-freedom specified by this bulk data
entry are distinct from, and may be used in conjunction with, the initial conditions for the
enforced degrees-of-freedom specified by NLOAD1, TLOAD1 and/or TLOAD2 bulk data
entries.
7. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).
8. Each degree-of-freedom (grid/component pair: G#/C#) should define a unique value for
U0 and/or V0 within any TIC ID set, but U0 and V0 may be specified on separate TIC
cards. When multiple cards with the same degree-of-freedom are present, only non-zero
values for U0 and V0 are used by the solver. When two non-zero values are defined for
U0 or for V0 for the same degree-of-freedom, a fatal error message will be issued, even if
values match.
Description
Defines values for the initial velocity of a set of grids along and about an axis for explicit
analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
GA/XA YA ZA GB/XB YB ZB
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Real)
(Real)
GA/ XA, Axis origin. These fields define the origin of the axis. The point may be
YA, ZA defined by entering a grid ID in the GA field or by entering X, Y, and Z
coordinates in the XA, YA, and ZA fields; these coordinates will be in the
basic coordinate system.
Default is the origin of the basic system (Real in all three fields or Integer in
first field)
GB/ XB, Direction of vector for axis definition. These fields define a point. The
YB, ZB vector goes from the anchor point to this point. The point may be defined
by entering a grid ID in the GB field or by entering X, Y, and Z coordinates in
the XB, YB, and ZB fields; these coordinates will be in the basic coordinate
system.
Comments
1. Explicit analysis initial condition sets must be selected with the Subcase Information
command IC = SID. It can only be selected in explicit subcases which are defined by an
ANALYSIS = NLGEOM subcase entry.
2. TICA is primarily used for simulating the uniform rotation of a structure about an axis by
defining VR and an axis. A helical (or spiral) shaped motion can also be achieved by
defining VR, VT and an axis.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DISC RET
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TIE 5 7 8 0.01
N25
Field Contents
(Integer > 0)
(Integer > 0)
(Integer > 0)
SRCHDIS Search distance criterion for creating contact condition. When specified,
only slave nodes that are within SRCHDIS distance from master surface will
have contact condition checked.
ADJUST Adjustment of slave nodes onto the master surface at the start of a
simulation.
Default = NO.
NO – no adjustment.
AUTO – A real value equal to 5% of the average edge length on the master
surface is internally assigned as the depth criterion (see Comment 7).
Real > 0.0 – Value of the depth criterion which defines the zone in which a
search is conducted for slave nodes (for which contact elements have been
created). These slave nodes (with created contact elements) are then
adjusted onto the master surface. The assigned depth criterion is used to
define the searching zone in the pushout direction (see Comment 7).
Comments
(Nonlinear quasi-static analysis)
1. TIE contact needs to keep a unique ID from all CONTACT definitions.
2. The TIE contact is constructed by searching for each slave node for a respective facet of
the master surface, which contains the normal projection of the slave and is within
SRCHDIS distance from the slave node. If no master segment with normal projection is
found, then the nearest segment is picked if the direction from slave to master is within a
certain angle (30 degrees) relative to the normal to the master segment. Having found a
feasible master segment for the slave node, a tie element is created.
3. The slave entity (SSID) always consists of grid nodes. It may be specified as:
5. TIE element is created of a same structure as FREEZE CONTACT element. TIE element
enforces zero relative motion on the contact surface – the contact gap opening remains
fixed at the original value and the sliding distance is forced to be zero. Also, rotations at
the slave node are matched to the rotations of the master patch.
6. Presently one TIE element is created for each slave node. This assures reasonably
efficient numerical computations without creating an excessive number of tie elements.
However, this may require special handling in some cases, such as when a master surface
wraps around the slave set. In such cases, switching the role of slave and master may
be recommended. Alternatively, multiple TIE elements can be created in order to cover all
possible directions of relative motion (a simplified illustration is shown in Figure 3).
Figure 3: Special case - Master surface wraps around a slave node set.
7. The adjustment of slave nodes doesn’t create any strain in the model. If DISCRET=N2S is
selected, it is treated as a change in the initial model geometry. If DISCRET=S2S is
selected, it is treated as a change in the initial contact opening/penetration.
If a node on the slave entity lies outside the projection zone of the master surface, it will
always be skipped during adjustment since no contact element has been constructed for
it.
If different contact interfaces involve the same nodes, nodal adjustment definitions are
processed sequentially in the order of identification numbers of the contact interfaces.
Care must be taken to avoid conflicts between the nodal adjustments; otherwise, contact
element errors or lack of compliance may occur.
Depth Criterion
The depth criterion (A non-negative real value for ADJUST) is used to define the searching
zone for adjustment as shown in Figure 4. This searching zone is created in the pushout
direction up to a distance equal to the value of the ADJUST field. The slave nodes within
the searching zone (with defined contact elements) are then considered for adjustment
based on the rules specified within this comment (Comment 7).
c) If the ADJUST field is set to an integer value (the identification number of a grid SET
entry), the nodes shared by the slave entity and the grid SET will be checked for
contact creation, that is SRCHDIS will be ignored for these nodes, and then adjusted if a
projection is found. The nodes belonging to the grid SET but not to the slave entity will
be simply ignored.
10. The slave entity (SSID) always consists of grid nodes. It may be specified as:
a surface defined using SURF card (the slave nodes are picked from the respective
nodes of the SURF faces).
a set of elements (shells or solids) defined using SET card. Slave nodes are picked
from the respective nodes of the elements in the set. For 3D solids, only nodes on the
surface of the solid body are selected; internal nodes are not considered.
11. The master entity (MSID) may be defined as:
Description
Where,
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TLOAD1 5 7 LOAD 13
Field Contents
(Integer > 0)
(Integer > 0)
TYPE Defines the type of the dynamic excitation. See comments 2 and 3.
(Integer > 0)
Comments
1. Dynamic excitation sets must be selected with the subcase information command
DLOAD=SID.
2. The type of dynamic excitation is specified by TYPE (field 5) based on the following table:
TYPE
TYPE of Dynamic Excitation
Integer Character
Excitation specified by TYPE is applied load. The EXCITEID must reference DAREA,
FORCEx, MOMENTx, PLOAD, RFORCE, GRAV, QVOL or QBDY1 entries.
Excitation specified by TYPE is enforced motion. The EXCITEID must reference SPC/SPCD
entries.
TYPE = 1 must be specified if the EXCITEID field references SPCD data used in transient
heat transfer analysis to define time-dependent thermal boundary conditions.
4. TLOAD1 loads may be combined with TLOAD2 loads only by specification on a DLOAD
entry. That is, the SID on a TLOAD1 entry may not be the same as that on a TLOAD2
entry.
5. SID must be unique for all TLOAD1, TLOAD2, RLOAD1, and RLOAD2 entries.
6. If TLOAD1 entries are selected for Fourier analysis, then the time-dependent loads on the
TLOAD1 entries are transformed to the frequency domain. Then the analysis is performed
as a frequency response analysis, but the solution and the output are converted to and
printed in the time domain.
8. When EXCITEID refers to an SPCD entry, the modal space will be augmented with
displacement vector(s) from linear static analysis with unit prescribed displacement at
each of the SPCD degrees-of-freedom. EXCITEID cannot reference the LOAD and
LOADADD bulk data entries.
Description
Where,
A defines the amplitude of the dynamic excitation and is referenced by the EXCITEID field.
is the time delay defined in the DELAY field.
B, C, and are the growth coefficient, exponential coefficient, frequency and phase angle
respectively and are defined in the corresponding B, C, F and P fields.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
C B
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
(Integer > 0)
TYPE Defines the type of the dynamic excitation. See comments 2 and 3.
T1 Time constant.
T2 Time constant.
(Real; T2>T1)
C Exponential coefficient.
B Growth coefficient.
Comments
1. Dynamic excitation sets must be selected with the subcase information command with
DLOAD=SID.
2. The type of dynamic excitation is specified by TYPE (field 5) based on the following
table:
TYPE
TYPE of Dynamic Excitation
Integer Character
3. TYPE (field 5) also determines the manner in which EXCITEID (field 3) is used by the
program as described below.
If the type of dynamic excitation specified by TYPE is applied load, then EXCITEID must
reference DAREA, FORCEx, MOMENTx, PLOAD, RFORCE, GRAV, QVOL or QBDY1 entries.
If the type of dynamic excitation specified by TYPE is enforced motion, then EXCITEID
must reference SPC/SPCD entries.
TYPE = 1 must be specified if the EXCITEID field references SPCD data used in transient
heat transfer analysis to define time-dependent thermal boundary conditions
5. TLOAD1 loads may be combined with TLOAD2 loads only by specification on a DLOAD
entry. That is, the SID on a TLOAD1 entry may not be the same as that on a TLOAD2
entry.
9. When EXCITEID refers to an SPCD entry, the modal space will be augmented with
displacement vector(s) from linear static analysis with unit prescribed displacement at
each of the SPCD degrees-of-freedom. EXCITEID cannot reference the LOAD and
LOADADD bulk data entries.
Description
Defines time step intervals at which a solution will be generated and output in transient
analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
-etc.-
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TSTEP 2 10 .001 5
9 0.01 1
Field Contents
N0# Skip factor for output. Every N0i-th step will be saved for output.
W3,# The frequency of interest in radians per unit time; used for the conversion of
overall structural damping into equivalent viscous damping. See comment 3.
W4,# The frequency of interest in radians per unit time; used for the conversion of
element structural damping into equivalent viscous damping. See comment 3.
Comments
1. TSTEP entries must be selected with the Subcase Iinformation command TSTEP = SID.
2. Note that the entry permits changes in the size of the time step during the course of the
solution. Thus, in the example shown, there are 10 time steps of value .001, followed by
9 time steps of value .01. Also, in the case of this example, you have requested that the
output be recorded for t = 0.0, .005, .01, .02, .03, and so on.
4. Different values for W3 and W4 may be set for each set of time increments. If any of the
fields are left blank then the value is taken from the PARAM, W3 or PARAM, W4 definition.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TSTEPNL 99 0.01
Field Contents
(Integer > 0)
Default = UPW
Default = 1.0E-2
Default = 1.0E-2
Default = 1.0E-3
Comments
1. The TSTEPNL bulk data entry is selected by the Subcase Information command TSTEPNL
= option. Each subcase for which nonlinear implicit dynamic analysis is desired requires a
TSTEPNL command.
2. Additional control for geometric nonlinear implicit dynamic solution schemes (ANALYSIS =
IMPDYN) can be defined using TSTEPNX bulk data entry. Defaults will be used if TSTEPNX
is not present.
3. The solution method for geometric nonlinear implicit dynamic analysis (ANALYSIS =
IMPDYN) is modified or Quasi-Newton. The frequency of stiffness matrix updates is
controlled by KSTEP. For highly nonlinear problems, it is recommended to reduce KSTEP
4. The time integration scheme for implicit transient is defined on TSTEPNX. The default
method is α-HHT.
5. For more information about geometric nonlinear analysis, refer to the Geometric Nonlinear
Analysis section.
TSTEPNX – Optional Parameters for Geometric Nonlinear Implicit Dynamic Analysis Control
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example 1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TSTEPNL 99 0.01
Example 2
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TSTEPNL 99 0.01
TSTEPNX 99 0.1
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
TSTEPNL 99 0.01 3 PW
0.01 0.01
TSTEPNX 99 0.1
Field Contents
DTA Output time step for animation files. If zero, no output (See comment 3).
DTTH Output time step for time history files. If zero, no output (See comment
3).
NPRINT Print every NPRINT iterations. If negative, to .out and standard output;
if positive, only to .out file.
Default = -1 (Integer)
DTMAX Maximum geometric nonlinear implicit time step from which time step is set
constant (See comment 3).
FIXTID Identification number of a TABLEDi entry. The x values of the table define
fixed time points that the automatic time step control will adhere to.
(Integer > 0)
NLOAD - The time points in all TABLEDi that are referenced by NLOAD1 in
one subcase.
ITW If the solution of a time step converges within ITW iterations, the next
time step will be increased by a factor controlled by DTSCI.
(Integer > 0)
DTSCI Maximum scale factor for increasing the time step (TSCTRL = ARC). Scale
factor for TSCTRL = SIMP.
LDTN Maximum number of iterations before resetting and decreasing the time
step by a factor of DTSCD.
(Integer > 0)
DTSCD Scale factor for decreasing the time step (TSCTRL = ARC, SIMP).
Comments
1. The TSTEPNX bulk data entry is selected by the Subcase Information command TSTEP =
option. There must also be a TSTEPNL bulk data entry with the same ID. It is only used
in geometric nonlinear implicit dynamic analysis (ANALYSIS = IMPDYN); it is ignored in
other analyses.
2. The solution method for geometric nonlinear implicit analysis is selected by SOLV. The
frequency of stiffness matrix updates is controlled by TSTEPNL, KSTEP. For highly
nonlinear problems, it is recommended to reduce KSTEP for better performance. KSTEP =
1 means full Newton.
Description
This entry defines the unbalanced rotating load during a rotor dynamic analysis in Frequency
Response solution sequences. The unbalanced load is specified in a cylindrical system where
the rotor rotation axis is the Z-axis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
MASS <Integer > 0/Real> Defines the magnitude of unbalanced mass (see
comment 4).
(No default)
ROFFSET <Integer > 0/Real> <Integer > 0> If an integer value (must be greater
than 0) is input, it references the
Default = 1.0 identification number of a TABLEDi
entry that specifies the offset values
as a function of frequency (see
comment 4).
ZOFFSET <Integer > 0/Real> <Integer > 0> If an integer value (must be greater than
0) is input, it references the identification
Default = 0.0 number of a TABLEDi entry that specifies
the offset values as a function of
frequency (see comment 4).
F ON <Real > 0> This field defines the starting frequency at which the
unbalanced load is applied (see comment 5).
Default = 0.0
F OFF <Real > 0> This field defines the stopping (final) frequency at which
the unbalanced load is applied (see comment 5).
Default = 999999.0
Comments
1. Currently, models containing multiple UNBALNC bulk data entries with the same set
identification number (SID) are not supported. Each UNBALNC bulk data entry must have a
unique SID.
2. For frequency response analysis, the UNBALNC bulk data entry is referenced by a DLOAD
Subcase Information entry.
Unbalanced mass of the system (rotor) about its axis of rotation (MASS field on the
UNBALNC entry).
The magnitude of separation between the rotating axis and the unbalanced mass
(ZOFFSET and ROFFSET fields on the UNBALNC entry).
The angular spin speed of the rotor (specific fields on the RGYRO and RSPINR bulk data
entries).
4. ROFFSET field:
Each entry in the TABLEDi entry specifies the distance by which the unbalanced mass is
offset in the X-Y plane (perpendicular to the axis of rotation of the rotor).
ZOFFSET field:
Each entry in the TABLEDi entry specifies the distance by which the unbalanced mass is
offset in the Z direction (axis of rotation of the rotor).
6. The initial position of the unbalanced mass and the direction of its subsequent rotation
are defined with respect to a cylindrical coordinate system. Its angular position is
measured from the plane defined by both the Z-axis and the vector (X1, X2, and X3) with
THETA=0.0 being the direction of the vector (X1, X2, and X3) itself. The rotation of the
unbalanced load occurs in the positive Z direction.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
USET SNAME G1 C1 G2 C2 G3 C3
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
Ci Component numbers.
3. For normal modes analysis with the Lanczos eigensolver, the case control command
RESVEC=YES must be used to create residual vectors based on the USET DOF . If the
AMSES or AMLS eigensolvers are used, the residual vectors will always be created. The
residual vectors are calculated using the unit load method.
4. For modal frequency response and modal transient analysis, the USET residual vectors are
always calculated if the AMSES and AMLS eigensolvers are used, and are not calculated if
the Lanczos eigensolver is used.
5. The residual vectors are then exported together with the eigenvectors to the H3D,
PUNCH, and OUTPUT2 files. If stress output is requested, the stress state for each mode
is output to the H3D, PUNCH, and OUTPUT files.
7. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
USET1 SNAME C G1 G2 G3 G4 G5 G6
G7 G8 G9 -etc.-
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
USET1 U6 123 34 88 4 12 19 7
1234 65
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
C Component number.
Comments
1. If the alternate format is used, all points in the sequence G1 through G2 are not required
to exist, but there must be at least one boundary degree-of-freedom for the model or a
fatal error will result. Any grids implied in the THRU that do not exist will collectively
produce a warning message, but will otherwise be ignored.
3. For normal modes analysis with the Lanczos eigensolver, the case control command
RESVEC=YES must be used to create residual vectors based on the USET1 DOF. If the
AMSES or AMLS eigensolvers are used, the residual vectors will always be created. The
residual vectors are calculated using the unit load method.
4. For modal frequency response and modal transient analysis, the USET1 residual vectors
are always calculated if the AMSES and AMLS eigensolvers are used, and are never
calculated if the Lanczos eigensolver is used.
5. USET1 is applied to normal modes analysis subcases that have the case control
RESVEC=YES specified. In such cases, residual vectors are calculated using the unit load
method. The residual vectors are then exported together with the eigenvectors to the
H3D, PUNCH, and OUTPUT2 files. If stress output is requested, the stress state for each
mode is output to the H3D, PUNCH, and OUTPUT files.
7. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
MIXED, it is allowed that when grid lists are provided for a given component, that the grid
references be either scalar points (SPOINT) or structural grid points (GRID) when the
component is 0, 1 or blank; interpreting all of these as 0 for scalar points and as 1 for
structural grids. When SPSYNTAX is set to STRICT it is required for grid/component pairs
(G#/C#) that the component be 0 or blank when the grid references are to scalar points
(SPOINT), and that the component be > 1 when the grid references are to structural grid
points (GRID). When the component is greater than 1, the grid references must always
be a structural grid (GRID).
Description
Defines values for Raleigh damping for geometric nonlinear dynamic analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
(Integer > 0)
GSID Grid set identification number. Damping is applied to the grid points
in this set.
(Real > 0)
(Real > 0)
1. Rayleigh damping is applied to all geometric nonlinear dynamic analysis subcases, implicit
and explicit. It is ignored in all other subcases.
2. In implicit dynamic analysis damping is applied to all grid points and GSID is ignored.
Multiple XDAMP is not allowed in implicit dynamic analysis.
4. Grid sets in all XDAMP statements must contain unique sets of grid points.
5. The viscous damping matrix B is calculated from the mass matrix M and stiffness matrix K
using:
B = ALFA * M + BETA * K
Description
Defines a time history output set as a union of time history outputs defined via XHIST
entries.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
XHISADD SID S1 S2 S3 S4 S5 S6 S7
S8 S9 etc.
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
XHISADD 101 2 3 1 6 4
Field Contents
(Integer > 0)
(Integer > 0)
Comments
1. Multipoint constraint sets must be selected with the Subcase Information command
XHIST=SID.
3. XHISADD entries take precedence over XHIST entries. If both have the same SID, only
the XHISADD entry will be used.
Description
Defines the time history output request for geometric nonlinear analysis.
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
VAR8 ...
ID8 ...
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
XHIST 100
GRID
DATA DEF AX AY
(Integer > 0)
(Integer > 0)
DTTHM Output time step for time history files. Once it is specified, it will
overwrite DTTH on NLPARMX, TSTEPNX and XSTEP to control the output
time step of history file specified by FILE in this card.
DATA DATA flag indicating that data labels follow. If no DATA is specified, the
default is VAR1 = DEF.
(Character)
(Integer > 0)
Comments
1. XHIST sets must be selected with the Subcase Information command XHIST = SID or by
XHISADD. It can only be selected in geometric nonlinear analysis subcases which are
defined by an ANALYSIS = NLGEOM, IMPDYN or EXPDYN subcase entry.
2. Table 1 below gives the definitions of TYPE, VARi, and IDi. The notation DEF (DX, DY, DZ,
VX, VY, VZ) means that if DEF is selected, all six values following in parenthesis are
written at once. However, instead of requesting DEF each value can be requested
individually. Details on the output requests can be found in Table 2.
4. It is not possible to have the same grid point several times in the same GRID group.
OptiStruct provides an error message in such cases.
GRID DEF (DX, DY, DZ, VX, VY, VZ), D (DX, DY, DZ), Grid ID
V (VX, VY, VZ), A (AX, AY, AZ), VR (VRX, VRY,
VRZ) AR (ARX, ARY, ARZ), XYZ (X, Y, Z),
REACX, REACY, REACZ, REACXX, REACYY,
REACZZ
PROP DEF (IE, KE, XMOM, YMOM, ZMOM, MASS, HE), Property ID
XCG, YCG, ZCG, XXMOM, YYMOM, ZZMOM, IXX,
IYY, IZZ, IXY, IYZ, IZX, RIE, KERB, RKERB, RKE
SHELL DEF (F1, F2, F12, M1, M2, M12, IEM, IEB, EMIN, Element ID
EMAX, OFF), STRESS (F1, F2, F12, Q1, Q2, M1,
M2, M12), STRAIN (E1, E2, E12, SH1, SH2, K1,
K2, K12), PLAS (EMIN, EMAX)
SOLID DEF (SX , SY, SZ, SXY, SYZ, SXZ, IE, DENS, Element ID
PLAS, TEMP, OFF), STRESS (SX, SY, SZ, SXY,
SYZ, SXZ), LOCSTRS (LSX, LSY, LSZ, LSXY,
LSYZ, LSXZ), BULK, VOL, DAM1, DAM2, DAM3,
DAM4, DAM5, DAMA, EPSXX, EPSYY, EPSZZ,
EPSXY, EPSXZ, EPSYZ
RWALL DEF (FNX, FNY, FNZ, FTX, FTY, FTZ), FN (FNX, Load set ID of
FNY, FNZ), FT (FTX, FTY, FTZ) RWALL
CONTCT DEF (FNX, FNY, FNZ, FTX, FTY, FTZ), FN (FNX, Contact ID
FNY, FNZ), FT (FTX, FTY, FTZ), M (MX, MY,
MZ)
SECT DEF (FNX, FNY, FNZ, FTX, FTY, FTZ, M1, M2, Load set ID of
M3), FN (FNX, FNY, FNZ), FT (FTX, FTY, FTZ), XSECT
M (MX, MY, MZ), GLOBAL (FNX, FNY, FNZ, FTX,
FTY, FTZ, MX, MY, MZ), LOCAL (F1, F2, F3, M1,
M2, M3), CENTER (CX, CY, CZ)
SPRING, DEF (FX, FY, FZ, MX, MY, MZ, LX, LY, LZ, RX, Element ID
BUSH RY, RZ, IE, OFF)
BEAM, BAR DEF (F1, F2, M2, M3, IE, OFF), F3, M1 Element ID
KE Kinetic energy.
CE Contact energy.
HE Hourglass energy.
DT Time step.
TER
DTE_REL
GRID X, Y, Z Coordinates.
KE Kinetic energy.
HE Hourglass energy.
See comment 8.
THIC Thickness.
IE Internal energy.
DENS Density.
VOL Volume.
Only MATX02.
TEMP Temperature.
See comment 8.
CONTCT FNX, FNY, FNZ, FTX, FTY, Normal and tangential force
FTZ components.
RWALL FNX, FNY, FNZ, FTX, FTY, Normal and tangential force
FTZ components.
SECT FNX, FNY, FNZ, FTX, FTY, Normal and tangential force
FTZ components.
SPRING, BUSH FX, FY, FZ, MX, MY, MZ Forces and moment components.
IE Internal energy.
BEAM, BAR F1, F2, F3, M1, M2, M3 Forces and moments in element
coordinates
IE Internal energy
M Torsional moment
IE Internal energy
XSHLPRM – Default Definition for Shell Element Properties for Geometric Nonlinear Analysis
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
XSHLPRM 14 2 NEWT 5
Field Contents
Default = 24 (Integer)
Default = 2 (Integer)
30 - DKT18.
31 - DKT_S3.
Default = 2 (Integer)
IPLAS Flag for shell plane stress plasticity (MATX2, MATX27, and MATX36
only).
0 = No
1 = Yes
Comments
1. XSHLPRM defines default settings for solid properties that can be overwritten by PSHELLX.
2. XSHLPRM is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
QBAT: Modified BATOZ Q4 24 shell with 4 Gauss integration points and reduced
integration for in-plane shear. No hourglass control is needed for this shell.
5. If the small strain option (ISMSTR) is set to 1 or 3, the strain and stress are engineering
strain and stress; otherwise they are true strain and stress.
6. Global integration (NIP = 0) is only compatible with MAT1, MATX2, and MATX36.
7. For MAT1, membrane only behavior happens if NIP = 1. Otherwise, NIP is ignored and
global integration (NIP = 0) is used.
9. For MATX2, the default value for IPLAS and global integration (NIP=0) is IPLAS = RAD.
10. For MATX36, the default value for IPLAS and global integration (NIP=0) is IPLAS = NEWT.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
XSOLPRM 24 222
Field Contents
ISMSTR Flag for small strain formulation (ISOLID = 1, 2, 14, and 24 only).
Default = 4 (Integer)
where:
Comments
1. XSOLPRM defines default settings for solid properties that can be overwritten by PSOLIDX.
2. XSOLPRM is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.
3. The ISOLID flag is not used with CTETRA elements. For these, elements with four and
ten nodes the number of integration points is fixed at one and four, respectively.
5. With the small strain option (ISMSTR), strain and stress is engineering strain and stress.
Otherwise, it is true strain and stress.
6. In time history and animation files, the stress tensor is written in the co-rotational frame.
7. Fully integrated elements (ISOLID =12) only uses full geometric non-linearity (corresponds
to ISMSTR = 4). Time step limit has no effect.
8. ISMSTR = 10 is only compatible with materials using total strain formulation (MATX42).
9. The time step control XSTEP, TYPEi = SOLID, TSCi = CST only works on elements with
ISMSTR = 2.
10. Co-rotational formulation: For ISOLID = 1, 2, 12 and IFRAME = ON, the stress tensor is
computed in a co-rotational coordinate system. This formulation is more accurate if large
rotations are involved. It comes at the expense of higher computation cost. It is
recommended in case of elastic or visco-elastic problems with important shear
deformations. The co-rotational formulation is compatible with 8 node solids.
11. HA8 (ISOLID = 14) elements: this element uses a locking-free general solid formulation,
co-rotational. The number of Gauss points is defined by NIP flag: for example, combined
with NIP = 222 gives an 8 Gauss integration point element, similar to ISOLID = 12. The
HA8 formulation is compatible with all material laws.
12. HEPH (ISOLID = 24) elements: This element uses an hourglass formulation similar to QEPH
shell elements.
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
-etc.-
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
XSTEP 2
0.9 DETAIL
Field Contents
(Integer > 0)
DTA Output time step for animation files. If zero, no output (See
comment 3).
DTTH Output time step for time history files. If zero, no output (See
comment 3).
DTSCA Default scale factor on explicit time step for all elements.
TACT Action if minimum time step is reached (For TSTYP = GRID, ELEM,
CONTACT, See comment 3).
DTi Time step scale factor for entity type (See comment 4).
ESIDi
AMS).
AMSTi Tolerance for advanced mass scaling convergence (Only for TYPEi =
AMS).
Comments
1. The XSTEP bulk data entry is selected by the Subcase Information command XSTEP =
option. It is only used in explicit analysis (ANALYSIS = EXPDYN); it is ignored in other
analyses.
With TSTYP = GRID, the nodal time step is used. With this option, the computation of
each cycle is slightly more expensive, but the time step can be higher, mainly for non-
optimized meshes and therefore the overall runtime shorter.
For TSTYP = GRID, TACT = CST, the mass of the grid that reaches DTMIN1 is increased.
You should check the evolution of the mass of the model.
For TSTYP = ELEM, TACT = CST, the element formulation switches to small strain for
each element that reaches the DTMIN1.
With TYPEi = GRID, the nodal time step is used. With this option, the computation of
each cycle is slightly more expensive, but the time step can be higher, mainly for non-
optimized meshes and therefore the overall runtime shorter.
With TYPEi = CONTACT and TSCi = DEL, the impacted node which fixes the time step is
removed from the interface.
TYPEi = SOLID and TSCi = CST is only active for solid elements with the flag ISMSTR = 2
set on PSOLIDX. This option is not available for 8 integration points.
5. For more information about geometric nonlinear analysis, refer to the Geometric Nonlinear
Analysis section.
6. TSTYP = NODA and TACT = AMS can activate elementary time step for Advanced Mass
Scaling, as well as TYPEi = NODA and TSCi = AMS.
7. NITER and NPAMS are only valid for Advanced Mass Scaling (AMS). If more NITER
iterations have been performed before convergence of the conjugate gradient, the
computation stops and error out. If NPAMS is specified, at each NPAMS cycle an
additional output is provided including: the number of iterations before convergence of
In order to prevent analyses from being carried out on badly discretized models, an element
quality check is incorporated into the pre-processing phase. The element quality check is
controlled jointly by the CHECKEL parameter (see PARAM, CHECKEL) and the ELEMQUAL bulk
data entry.
With the CHECKEL parameter, type 2 and 3 checks may be controlled and the ELEMQUAL bulk
data entry may be used to set the error and warning limits. However, the "validity" check,
type 1, is always performed – even when the value of PARAM, CHECKEL is NO.
A check for collapsed element nodes is performed for all elements. All other property checks
are performed after this collapsed node check, and will be skipped if collapsed nodes are
found. If the element quality check is activated, the checks for each element are performed
according to the following precedence: (1) validity check, (2) quality check for error limits,
and (3) quality check for warning limits. Violation of any check will skip the subsequent
check(s).
The warp angle check on CQUAD4 elements is relaxed for topography optimization. This
relaxation prevents premature error termination of the optimization due to element quality
concerns. However, be aware that the resulting mesh from a topography optimization may fail
the CQUAD4 warp angle check when reanalyzed.
The checks performed and the default bound values for each element type are outlined in the
following topics:
CGASK6 Element Checks and Default Bound Values
CGASK8 Element Checks and Default Bound Values
CGASK12 Element Checks and Default Bound Values
CGASK16 Element Checks and Default Bound Values
CTRIA3 Element Checks and Default Bound Values
CTRIA6 Element Checks and Default Bound Values
CQUAD4 Element Checks and Default Bound Values
CQUAD8 Element Checks and Default Bound Values
CTAXI / CTRIAX6 Element Checks and Default Bound Values
CTETRA Element Checks and Default Bound Values
CPENTA Element Checks and Default Bound Values
CHEXA Element Checks and Default Bound Values
The element check and default bounds of the CGASK6 element are identical as those of the
first-order (6-noded) CPENTA element.
The element check and default bounds of the CGASK8 element are identical as those of the
first-order (8-noded) CHEXA element.
The element check and default bounds of the CGASK12 element are identical as those of the
second-order (15-noded) CPENTA element. Notice that CGASK12 has six 3-node edges of
which Hoe Normal Offset and Hoe Tangent Offset are checked.
The element check and default bounds of the CGASK16 element are identical as those of the
second-order (20-noded) CHEXA element. Notice that CGASK16 has 8 3-node edges of which
Hoe Normal Offset and Hoe Tangent Offset are checked.
Aspect Ratio
The aspect ratio of a CTRIA3 element is defined as the ratio of the maximum side
length to the minimum side length.
Skew Angle
The skew angle of a CTRIA3 element is the difference between 90 degrees and the
minimum of three angles: a1, a2 and a3. These angles are defined, for the CTRIA3
element, as the smallest of the angles created when a line drawn from a node to the
midpoint of the opposing side intersects a line connecting the midpoints of the
adjacent two sides. The skew angle has a range from 0 degrees for a perfect triangle
to 90 degrees for a collapsed triangle.
SKEW = 90 - MIN(a1,a2,a2 )
Vertex Angle
For each vertex, the angle is measured between its two adjacent edges. The minimum
and maximum values of the three nodes are reported for the element.
The values used for warning and error checks may be adjusted by the ELEMQUAL bulk data
entry, but validity checks are hard-coded.
Vertex Angle
For each vertex, the angle is measured between its two adjacent edges. The minimum
and maximum values of the four nodes are reported for the element.
Aspect Ratio
The aspect ratio of a CQUAD4 element is the length of its longest side, divided by the
length of its shortest side.
Skew Angle
The skew angle in a CQUAD4 element is calculated by finding the minimum angle
between two lines joining opposite mid-sides of the element. Ninety degrees minus the
minimum angle found is reported.
Warp Angle
The warpage of a CQUAD4 element is calculated by splitting the quad into two trias
and finding the angle between the two planes which the trias form. The quad is then
split again, this time using the opposite corners and forming the second set of trias.
The angle between the two planes, which the trias form, is then found. The maximum
angle found between the planes is the warp angle of the element.
The values used for warning and error checks may be adjusted by the ELEMQUAL bulk data
entry, but validity checks are hard-coded.
Vertex Angle
This quality is calculated using only the corner nodes. For each vertex, the angle is
measured between its two adjacent edges. The minimum and maximum values of the
four nodes are reported for the element.
Aspect Ratio
This quality is calculated using only the corner nodes. The aspect ratio of a CQUAD8
element is the length of its longest side, divided by the length of its shortest side.
Skew Angle
This quality is calculated using only the corner nodes. The skew angle in a CQUAD8
element is calculated by finding the minimum angle between two lines joining opposite
mid-sides of the element. Ninety degrees minus the minimum angle found is reported.
Warp Angle
This quality is calculated using only the corner nodes. The warpage of a CQUAD8
element is calculated by splitting the quad into two trias and finding the angle between
the two planes which the trias form. The quad is then split again, this time using the
opposite corners and forming the second set of trias. The angle between the two
planes, which the trias form, is then found. The maximum angle found between the
planes is the warp angle of the element.
Lower Limit Upper Limit Lower Limit Upper Limit Lower Limit Upper Limit
Lower Limit Upper Limit Lower Limit Upper Limit Lower Limit Upper Limit
The values used for warning and error checks may be adjusted by the ELEMQUAL bulk data
entry, but validity checks are hard-coded.
The element check and default bounds of the 3-node CTAXI or CTRIAX6 element are identical
as those of the CTRIA3 element.
The element check and default bounds of the 6-node CTAXI or CTRIAX6 element are identical
as those of the CTRIA3 element.
Aspect Ratio
This quality is calculated using only the corner nodes. It is defined as the ratio of the
maximum side length to the minimum side length.
Skew Angle
This quality is calculated using only the corner nodes. It is the difference between 90
degrees and the minimum of three angles: a1, a2 and a3. These angles are defined, for
the CTRIA6 element, as the smallest of the angles created when a line drawn from a
node to the midpoint of the opposing side intersects a line connecting the midpoints of
the adjacent two sides. The skew angle has a range from 0 degrees for a perfect
triangle to 90 degrees for a collapsed triangle.
Vertex Angle
This quality is calculated using only the corner nodes. For each vertex, the angle is
measured between its two adjacent edges. The minimum and maximum values of the
three nodes are reported for the element.
The values used for warning and error checks may be adjusted by the ELEMQUAL bulk data
entry, but validity checks are hard-coded.
= di / li
= hi / li
Aspect Ratio
The aspect ratio of a CTETRA 1st-order element is defined as the maximum of the aspect
ratio of its four triangular faces. Each face is treated as a CTRIA3 element.
The face skew angle of a CTETRA 1st-order element is defined as the maximum of the
skew angles of its four triangular faces. Each face is treated as a CTRIA3 element.
Vertex Angle
The same vertex angle check is performed for all of the faces, and each is treated as a
triangular (CTRIA3) or quadrilateral (CQUAD4) element. The minimum and maximum values
reported for the element.
Collapse
The collapse of a CTETRA 1st-order element is defined as the minimum of four values,
each calculated as the ratio between the distance from a vertex to its opposing face, and
the square root of the area of the opposing face.
The reported value is normalized by 1.2408, which gives the equilateral tetra a collapse
value of 1. As the tetra collapses, the collapse value approaches 0.
Edge Angle
An edge angle is the absolute value of the angle between two faces sharing a common
edge subtracted from 90 degrees. The edge angle (EA) of a CTETRA 1st-order element is
defined as the maximum of its six edge angles.
Where, Nki and Nli are the normal vectors of faces k and l that have a common edge i.
Aspect Ratio
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CTETRA 1st-order element.
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CTETRA 1st-order element.
Vertex Angle
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CTETRA 1st-order element.
Collapse
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CTETRA 1st-order element.
Edge Angle
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CTETRA 1st-order element.
The hoe normal and tangent offsets of the CTETRA 2nd-order element are defined as the
maximum of the hoe normal and tangent offsets of its 6 edges, respectively. See the
definition of hoe normal offset of 3-node edge.
The hoe normal and tangent offsets of the CTETRA 2nd-order element are defined as the
maximum of the hoe normal and tangent offsets of its 6 edges, respectively. See
definition of hoe tangent offset of 3-node edge.
The values used for warning and error checks may be adjusted by the ELEMQUAL bulk data
entry, but validity checks are hard-coded.
Aspect Ratio
The aspect ratio of a CPENTA 1st-order element is defined as the maximum of the aspect
ratios of its three quadrilateral faces and two triangular faces. Each quadrilateral face is
treated as a CQUAD4 element and each triangular face as a CTRIA3 element.
The skew angle of a CPENTA 1st-order element is defined as the maximum skew angle
among its three quadrilateral faces and two triangular faces. Each quadrilateral face is
treated as a CQUAD4 element and each triangular face as a CTRIA3 element.
Vertex Angle
The same vertex angle check is performed for all of the faces, and each is treated as a
triangular (CTRIA3) or quadrilateral (CQUAD4) element. The minimum and maximum values
reported for the element.
Face Warpage
The face warpage of a CPENTA 1st-order element is defined as the maximum warpage
among the three quadrilateral faces, each treated as a CQUAD4 element.
Twist Angle
The twist angle is defined as the rotation of one triangular face with respect to the
opposite triangular face. The rotation is computed as follows: first construct a reference
plane perpendicular to the line connecting the centroids of the two triangular faces. The
three edges of each triangular are then projected to this reference plane. The maximum
angle between the corresponding edges of the two projected triangles is reported as the
twist angle of the CPENTA 1st-order element.
Edge Angle
The edge angle is the absolute value of the angle between two faces sharing a common
edge, subtracted from 90 degrees. For warped quadrilateral faces, the projected planes
defined by the plane vectors are used to compute the face normals (see definition of
reference plane for quadrilateral element or face), which are used in the angle calculation.
The edge angle of a CPENTA 1st-order is defined as the maximum edge angles in the
element.
Aspect Ratio
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPENTA 1st-order element.
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPENTA 1st-order element.
Vertex Angle
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPENTA 1st-order element.
Face Warpage
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPENTA 1st-order element.
Twist Angle
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPENTA 1st-order element.
Edge Angle
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPENTA 1st-order element.
The hoe normal offset is the maximum of its edges normal offset values. See the definition
of hoe normal offset of 3-node edge.
The hoe tangent offset is the maximum of its edges tangent offset values. See the
definition of hoe tangent offset of 3-node edge.
The values used for warning and error checks may be adjusted by the ELEMQUAL bulk data
entry, but validity checks are hard-coded.
where, V1, V2, V3, and V4 are the vectors that connect the four corner nodes with the
centroid of the quadrilateral. These two plane vectors and the centroid are then used to
construct the reference plane. These vectors of a non-warping quadrilateral face are shown
below:
Aspect Ratio
The aspect ratio of a CHEXA 1st-order element is defined as the maximum aspect ratio
among its six faces; each treated as a CQUAD4 element.
The face skew angle of a CHEXA 1st-order element is defined as the maximum skew angle
among its six faces; each treated as a CQUAD4 element.
Vertex Angle
The same vertex angle check is performed for all of the faces, and each is treated as a
quadrilateral (CQUAD4) element. The minimum and maximum values reported for the
element.
Face Warpage
The face warpage of a CHEXA 1st-order element is defined as the maximum warpage
among its six faces; each treated as a CQUAD4 element.
Twist Angle
The twist angle of a CHEXA 1st-order element is defined as the maximum rotation of one
face with respect to its opposite face. The calculation is done as follows:
where, PL1 and PL2 are the place vectors of the face treated as CQUAD4. See the
definition of reference plane for quadrilateral element or face. The diagonal vectors for a
planar parallelogram can be show below:
Then, for each pair of opposing faces, a reference plane that is perpendicular to the axis
connecting the centroids of the faces is constructed. The diagonal vectors D1 and D2 of
each of the two opposite faces are projected onto this reference plane. The angles
between the projected and the projected are computed as t 1 and t 2. The
maximum of t 1 and t 2 is defined as the relative rotation between these two opposite faces
(TAF). Finally, the twist angle (TA) of a CHEXA 1st-order is calculated as the maximum
relative rotation of its three pairs of opposing faces.
An edge angle is the absolute value of the angle between two faces sharing a common
edge, subtracted from 90 degrees. For warped faces, the projected planes are used to
compute the face normals used for the angle calculation. The edge angle of a CHEXA 1st-
order is defined as the maximum edge angle in the element.
Aspect Ratio
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CHEXA 1st-order element.
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CHEXA 1st-order element.
Vertex Angle
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CHEXA 1st-order element.
Face Warpage
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CHEXA 1st-order element.
Twist Angle
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CHEXA 1st-order element.
Edge Angle
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CHEXA 1st-order element.
The hoe normal offset is the maximum of its edges normal offset values. See the definition
of hoe normal offset of 3-node edge.
The hoe tangent offset is the maximum of its edges tangent offset values. See the
definition of hoe tangent offset of 3-node edge.
The values used for warning and error checks may be adjusted by the ELEMQUAL bulk data
entry, but validity checks are hard-coded.
Aspect Ratio
The aspect ratio of a CPYRA 1st-order element is defined as the maximum of the aspect
ratios of its four triangular faces and the quadrilateral base face. Each triangular face is
treated as a CTRIA3 element and the quadrilateral face as a CQUAD4 element.
The face skew angle of a CPYRA 1st-order element is defined as the maximum of the skew
angles of its four triangular faces and the quadrilateral base face. Each triangular face is
treated as a CTRIA3 element and the quadrilateral face as a CQUAD4 element.
Vertex Angle
The same vertex angle check is performed for all of the faces, and each is treated as a
triangular (CTRIA3) or quadrilateral (CQUAD4) element. The minimum and maximum values
reported for the element.
Face Warpage
The face skew angle of a CPYRA 1st-order element is defined as the warpage of its
quadrilateral base face, which is treated as a CQUAD4 element.
Aspect Ratio
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPYRA 1st-order element.
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPYRA 1st-order element.
Vertex Angle
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPYRA 1st-order element.
Face Warpage
This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPYRA 1st-order element.
The hoe normal offset is the maximum of its edges normal offset values. See the definition
of hoe normal offset of 3-node edge.
The hoe tangent offset is the maximum of its edges tangent offset values. See the
definition of hoe tangent offset of 3-node edge.
The values used for warning and error checks may be adjusted by the ELEMQUAL bulk data
entry, but validity checks are hard-coded.
In order to prevent analyses from being carried out on models with poor material definitions, a
material property check is incorporated into the pre-processing phase. The material property
check is controlled by the CHECKMAT parameter (see the PARAM input format).
There are several levels of requirements that material data needs to satisfy:
2. Mathematical requirements - These have to be satisfied so that the stiffness matrix can
be formulated at all, and are usually not very strict. For example, to avoid division by
zero, MAT1 in 3D must have n¹-1 and n¹0.5. Composite homogenization adds additional
mathematical requirements. Failure to meet these criteria will always result in an error
termination.
Full stability - This means that the material is stable; when pulled it stretches rather
than shrinks, etc. For example, E>0 assures stability for a rod. In a mathematical
sense, stability assures that the stiffness matrix (with proper support) will be Semi-
Positive Definite (SPD).
Semi-stability - This is a slight extension of stability to include borderline cases such as
allowing E=0. It guarantees that the stiffness matrix (with proper support) will be
Semi-Positive Semi-Definite (SPSD). However, this can lead to infinite or very large
compliances.
Not all zeros - This is an additional requirement that at least one deformation mode of
the material is active (non-zero stiffness). This avoids element stiffness matrices that
are identically zero. However, It does not prevent infinite or very large compliances.
An error termination will occur if a material has negative stiffness.
An error termination will occur if all modes of deformation have zero stiffness.
You may choose to perform only those checks that are necessary to avoid crashes in the
element routines (that is the Mathematical Requirement checks). This is facilitated through
the specification of PARAM,CHECKMAT,NO in the bulk data section of the input deck.
The checks performed for MAT1, MAT2, MAT3, MAT8, and MAT9 are outlined in the following
topics:
Material Property Checks for MAT1
Material Property Checks for MAT2
In addition to the property requirements, there are usage and recalculation rules for MAT1
data.
Element Type E G n
ROD, BEAM, Used for bending and Used for torsion. Unused.
BAR tension.
QUAD, TRIA Used in combination with Used for transverse Used in combination with
n for bending and shear. E for bending and
membrane. membrane.
In cases when not all material parameters are given for MAT1, here are the recalculation rules
for the remaining parameters. Note that in cases of two prescribed parameters, this is
obvious; while in cases of a single prescribed parameter, you are making an assumption as to
which one is assumed to be zero.
Given Mean
E G n E G n
The property requirements on MAT1 vary depending on whether it is used for 1D, 2D, or 3D
elements. The details are provided in the table below.
Semi-stability E < 0 or G < 0 results E < 0, G < 0, n < -1 E < 0, n < -1, or n >
in error termination. > or -n > 0.5 results 0.5 results in error
in error termination. termination.
PARAM,CHECKMAT,NO
will disable this error. PARAM,CHECKMAT,N PARAM,CHECKMAT,N
O will disable this O will disable this
n < -1 or n > 0.5 error. error.
results in a warning
(however, this is
unused in 1D).
Not all zeros If both E = 0 and G = If both E = 0 and G E < 0 results in error
0, an error termination = 0, an error termination.
occurs. termination occurs.
If either E = 0 or G = If either E = 0 or G =
0, a warning is given. 0, a warning is
given.
Mathematical none
Not all zeros If all eigenvalues of [G] = 0, an error termination will occur.
Consistency none
Mathematical If EX = 0, ETH = 0, EZ = 0 or
Consistency none
Comments
1. By substitution of
into
If E1 = 0, E2 = 0 , or G1 2 = 0, a warning is provided.
Comments
Mathematical none
Not all zeros If all eigenvalues of [G] = 0, an error termination will occur.
Consistency none
Descriptions for individual output files can be accessed by selecting from the links for each
entry, listed below in groups according to type and alphabetically on the Files Created by
OptiStruct page.
The filenames listed on this page contain only the tail part of the name. For most files, the
full filename is controlled by the OUTFILE command (ASSIGN,OUTFILE), and in the absence of
OUTFILE, they use the root of input filename. Unless otherwise noted for a specific file type
(.#.eigv), all output files have the same root and are located in the same folder. The only
exception is <BODY_NAME>.h3d; these files may not have a common root in the filename.
HyperMesh OptiStruct
HTML
Microsoft Excel
The filenames listed on this page contain only the tail part of the name. For most files, the
full filename is controlled by the OUTFILE command (ASSIGN,OUTFILE), and in the absence of
OUTFILE, they use the root of input filename. Unless otherwise noted for a specific file type
(.#.eigv), all output files have the same root and are located in the same folder. The only
exception is <BODY_NAME>.h3d; these files may not have a common root in the filename.
.#.#.#.dis file
.#.#.dis file
.#.#.dis.# file
.#.#.els file
.#.#.fat file
.#.asens file
.#.dis file
.#.dis.# file
.#.eigv file
.#.els file
.#.els.# file
.#.grid file
.#.h3d file
.#.mass file
.#.sens file
.#.sh file
.#.slk file
.amls_singularity.cmf file
.cntf file
.contgap.fem file
.cstr file
.dens file
.desvar file
.dis.# file
.disp file
.dvgrid file
.echo file
.els.# file
.force file
.fsthick file
.gpf file
.grid file
File Creation
This file is created when the PATRAN format is chosen and normal modes analyses are
performed. (See documentation for the I/O Option FORMAT).
File Contents
Result Description
Comments
1. One such file is created for each calculated mode at each iteration where the I/O Option
RESULTS requests analytical results to be output.
File Creation
This file is created when the PATRAN format is chosen and linear static analysis is performed.
(See documentation for the I/O Option FORMAT).
File Contents
Result Description
Comments
1. One such file is created for each subcase at each iteration where the I/O Option RESULTS
requests analytical results to be output.
File Creation
This file is created when the APATRAN format is chosen and normal modes analyses are
performed. (See documentation for the I/O Option FORMAT).
File Contents
Result Description
Comments
1. One such file is created for each calculated mode at each iteration where the I/O Option
RESULTS requests analytical results to be output.
File Creation
This file is created when the PATRAN format is chosen and linear static analysis is performed.
(See documentation for the I/O Option FORMAT).
File Contents
Result Description
Stress Stress results from linear static analysis. Output is controlled by the I/O
Option STRESS (or ELSTRESS).
Comments
1. One such file is created for each subcase at each iteration where the I/O Option RESULTS
requests analytical results to be output.
File Creation
File Contents
This file contains the average fatigue life/damage, top five damaged elements, and the
detailed damage information (contribution from each static loadcase).
Comments
2. The second # in the file name is the user-defined fatigue subcase ID.
3. If a fatigue optimization is performed, this file is created for each fatigue subcase at the
first and last iterations.
File Creation
This file is created when an optimization is performed. Creation of this file is controlled by the
I/O option OUTPUT.
File Contents
The file contains sensitivity information for all responses with respect to topology design
variables (density) at a given iteration (denoted by the # in the file name).
File Format
The sensitivities are listed in a single column and are grouped by response. A blank line
separates each response grouping.
Comments
File Creation
This file is created when the PATRAN format is chosen and shape or topography design
variables are present. (See documentation for the I/O Option FORMAT).
File Contents
Result Description
Comments
1. One such file is created for each iteration where the I/O Option DENSRES requests
topography or shape results to be output.
File Creation
This file is created when the APATRAN format is chosen and linear static analysis is performed.
(See documentation for the I/O Option FORMAT).
File Contents
Result Description
Comments
1. One such file is created for each subcase at each iteration where the I/O Option RESULTS
requests analytical results to be output.
File Creation
This file is created by the subcase information entry EIGVSAVE. The prefix for the file name is
controlled by the I/O option EIGVNAME.
File Contents
Result Description
Comments
1. This file is used to store eigenvalue results from normal modes analyses for retrieval by
modal frequency response subcases. The EIGVRETRIEVE subcase information entry is
used to retrieve values from this file.
File Creation
This file is created when the PATRAN format is chosen and topology design variables are
present. (See documentation for the I/O Option FORMAT).
File Contents
Result Description
Comments
1. One such file is created for each iteration where the I/O Option DENSRES requests
topology results to be output.
File Creation
This file is created when the APATRAN format is chosen and linear static analysis is performed.
(See documentation for the I/O Option FORMAT).
File Contents
Result Description
Stress Stress results from linear static analysis. Output is controlled by the I/O
option STRESS (or ELSTRESS).
Comments
1. One such file is created for each subcase at each iteration where the I/O option RESULTS
requests analytical results to be output.
File Creation
This file is created when topography or shape optimization is performed. Output of this file is
controlled by the I/O Option SHRES.
File Contents
Result Description
File Format
The file uses the following format for each grid in the model:
GRID Id Cp X1 X2 X3 Cd Ps
where:
Cp is blank.
X1, X2, X3 provide the location of the grid point in the global coordinate
system.
Comments
The .#.h3d files are compressed binary files, containing model, analysis, and optimization
result data. They can be used to post-process results in HyperView or when using the
HyperView Player.
File Creation
The .#.h3d files are created when the OUTPUT, H3D, <frequency>, BYITER output option is
present and an optimization is performed.
File Contents
The .#.h3d files contain node and element definitions. In the case of shape optimization, the
model is updated to the shape of the respective iteration. The following results are included:
Result Description
Composite ply strain Ply strain results for composite materials from static
analyses.
Composite ply stress Ply stress results for composite materials from static and
analyses.
Composite failure indices Failure indices for composite materials from static
analyses.
Element strain energy Element strain energy results from static and normal
modes analyses.
Grid point stress Grid point stress results for 3D elements from static
analyses.
Comments
2. Grid point stresses are output for the entire model and for each individual component.
This allows grid point stresses to be accurately obtained at the interface of two
components referencing different material definitions.
File Creation
File Contents
File Format
The file is formatted into blocks separated by blank lines. Each block represents a modal
subcase. The subcases are in order of occurrence in the input deck.
Each block contains six columns and a number of rows. The number of rows is equal to the
number of requested modes for this subcase. The columns, from left to right, contain the
total effective mass fraction for X-translation, Y-translation, Z-translation, X-rotation, Y-
rotation, and Z-rotation. The summary of each column is 100%.
Comments
2. This file is used by the _mass.#.mvw session file which automatically creates bar charts
for the results.
File Creation
This file is created when an optimization is performed. Creation of this file is controlled by the
I/O Option OUTPUT.
File Content
The file contains sensitivity information for all responses to size and shape design variables at
a given iteration (denoted by the # in the file name).
File Format
The sensitivities are listed in a single column and are grouped by response. A blank line
separates each response grouping.
Comments
2. The _sens.#.mvw HyperView script file automatically creates histogram plots for the
results contained in this file.
File Creation
This file is created when an optimization is performed. Output of this file is controlled by the
I/O Option SHRES.
File Contents
Comments
File Creation
This file is only created when size or shape optimization is performed. Output of this file is
controlled by the SENSITIVITY and SENSOUT I/O options.
File Contents
The file contains sensitivity information for size and shape design variables.
File Format
The only values that can be changed in this file are those listed in the "New" column. All
other values are either fixed or their calculation is fixed. When the .slk file is created, the
values in the "New" column match those in the "Reference" column. These values may be
adjusted, but should always remain within the design variable's bounds.
Each size and shape design variable in the model is listed in the left-hand column of the
sensitivity table. Information concerning a particular design variable is given in the row where
its label is listed. The current value and the upper and lower bounds of the design variables
are given in the columns, "Reference," "Lower," and "Upper" respectively.
Each referenced response in the model has its own column. These response columns are on
the right-hand side of the sensitivity table. The calculated sensitivity of a response to
changes in a design variable at the current iteration is given in the row corresponding to that
design variable and the column corresponding to that response.
Beneath the list of design variables, in the left-hand column, are the headings "Response lower
bound," "Response reference," and "Response upper bound". If a response is constrained, the
constraint value will be given in either the "Response lower bound" or the "Response upper
bound" row of the column corresponding to that response. The value given in the "Response
reference" row is the calculated value of the response using the design variable reference
values.
At the bottom of the left-hand column are the headings: "Response linear," "Response
reciprocal," and "Response conservative". The response values in these rows are the
predicted values of the responses for three different approximations. Initially, these values
will match one another and the "Response reference" value for each response. This is
because these are the predicted values of the response at the given variable settings, which
initially are the same settings used to calculate the "Response reference" value. Once the
design variable values in the "New" column are altered, these values will change.
The "Response linear" row predicts the response value using linear approximation. This is
calculated as:
where:
The "Response reciprocal" row predicts the response value using reciprocal approximation.
This is calculated as:
where:
The "Response conservative" row predicts the response value using a combination of the
above approximations where linear approximation is used, when the sensitivity is positive, and
reciprocal approximation is used when the sensitivity is negative. Therefore, if all sensitivities
are positive, the conservative prediction will match the linear prediction. If all sensitivities are
negative, it will match the reciprocal prediction, but if there is a mixture of positive and
negative sensitivities for a given response then the conservative prediction will match neither
the linear nor the reciprocal prediction.
The normalized values simply show the predicted response as a fraction of the response
reference value.
File Creation
This file is created when an AMLS run is performed and singular grid points are detected by
AMLS.
File Contents
This file contains a list of GRID point identification numbers which are found to be singular
during an AMLS run.
Format
*entitysetcreate("^AMLS singular grids",nodes,#)
*createmark(nodes,#)
Comments
1. Verify that the corresponding model is loaded in HyperMesh when executing the command
file.
File Creation
This file is created when the OPTI format is selected in the CONTF I/O Options Entry for
nonlinear quasi-static analysis (NLSTAT) runs.
File Contents
Result Description
Contact Forces Contact force results from nonlinear quasi-static analysis (with
contact) runs. Output is controlled by the I/O option CONTF.
File Format
where:
iter is a keyword identifying that the next field is the iteration number.
Within the iteration section, the following information is provided for each subcase:
LABEL: <Label>
FORCE-X is the component of the total contact force along the X-axis
of the Basic System.
FORCE-Y is the component of the total contact force along the Y-axis
of the Basic System.
FORCE-Z is the component of the total contact force along the Z-axis
of the Basic System.
The .contgap.fem file is an ASCII format file. It is used to visualize the internally created
contact elements. The contact elements are presented as CGAPG elements.
File Creation
File Contents
The file contains CGAPG elements, PGAP properties, and the auxiliary GRIDs for contact
visualization.
File Format
The formats of GRID, CGAPG, and PGAP are the same as for the bulk data entries.
Comments
1. To visualize the configuration of the contact elements, load the original FEA model in
HyperMesh and import this file. Ensure that the FE overwrite option is turned on in the
import panel.
2. During optimization, this file contains the contact elements at the latest iteration. To
visualize this configuration correctly for shape optimization, the shape of the FEA model
should be updated by applying shape change results.
File Creation
This file is created when the OPTI, OS or BOTH formats are chosen. (See documentation for
the I/O options FORMAT and OUTPUT).
File Contents
Result Description
Composite stress or strain Composite stress and strain results from linear static.
Output is controlled by the I/O options CSTRESS or
CSTRAIN. On PCOMP, SOUT=YES needs to be selected.
File Format
The composite stress file format is self-explanatory. It gives the stress, strain and composite
failure for each element and its plies.
Comments
1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.
File Creation
This file is created when the OPTI, OS or BOTH formats are chosen and a topology
optimization is performed. (See documentation for the I/O options FORMAT and OUTPUT).
File Contents
Result Description
File Format
where:
iter is a keyword identifying that the next field is the iteration number.
Within the iteration section, the following information is provided for each element:
EID Mat_dens
where:
File Creation
File Contents
File Format
The format for design variable output is the same as for the bulk data entries.
File Creation
This file is created when the APATRAN format is chosen and shape or topography design
variables are present. (See documentation for the I/O options FORMAT and OUTPUT).
File Contents
Result Description
Comments
1. One such file is created for each iteration where the I/O option DENSRES requests
topography or shape results to be output.
File Creation
This file is created when the OPTI, OS or BOTH formats are chosen. (See documentation for
the I/O options FORMAT and OUTPUT).
File Contents
Result Description
Displacement Displacement results from linear static, inertia relief, and frequency
response analyses. Output is controlled by the I/O option
DISPLACEMENT.
Eigenvector Eigenvector results from normal modes and linear buckling analyses.
Output is controlled by the I/O option DISPLACEMENT.
File Format
where:
where:
LCID is the output ID for the subcase or mode. This is not
necessarily the same as the subcase ID defined in the input
data.
SPCcase is the SPC set identification number for linear static, inertia
relief, or frequency response subcases or 1 for eigenvectors.
where:
NID is the node identification number.
Comments
1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.
File Creation
This file is only created when an analysis is performed. Creation of this file is controlled by
the I/O Option OUTPUT.
File Contents
The file contains shape variable definitions for the displacements or eigenvectors resulting
from linear static, inertia relief, or normal modes analyses.
File Format
DESVAR and DVGRID definitions are provided for each linear static subcase and for each
calculated normal mode.
Output for linear static subcases begins with a header in the following format:
$
$ DESVAR and DVGRIDs for static load case subcase_id
$
where:
Output for calculated normal modes begins with a header in the following format:
$
$ DESVAR and DVGRIDs for eigenvalue load case subcase_id, Mode Number
mode_number
$
where:
The DESVAR and DVGRID definitions are formatted as per the bulk data descriptions.
File Creation
File Contents
The file represents a copy of the input deck in a form suitable to use for another solution
which, when used with the same subcase information and I/O options entries, should generate
identical results (round off error may be noticeable if the original input deck uses large field
format).
File Creation
This file is created when the APATRAN format is chosen and topology design variables are
present. (See documentation for the I/O options FORMAT and OUTPUT).
File Contents
Result Description
Comments
1. One such file is created for each iteration where the I/O option DENSRES requests
topology results to be output.
File Creation
File Contents
Result Description
Force Force results from linear static analysis for ELAS (CELAS1, CELAS2,
CELAS3, CELAS4), ROD (CROD), BAR (CBAR, CBEAM), BUSH (CBUSH),
PLATE (CQUAD, CTRIA), and GAP (CGAP) elements.
File Format
The file is divided up by iteration. Output from each iteration starts with a line in the following
format:
where:
Each iteration section is divided up by subcase. Output for each subcase starts with a line in
the following format:
where:
Each subcase section is divided up by element-type. Output for each element-type section
starts with one of the following formats (depending on the elements present in the model):
ELAS # FORC E
Element force output is then listed under these headings, depending on the type of elements
for which this output was selected. The format of the element output matches the
corresponding header, that is for ROD elements you would get FORCE-A and FORCE-B;
whereas, for PLATE elements you would get MEMB-X, MEMB-Y, MEMB-XY, BEND-X, BEND-Y,
TWIST-XY, SHEAR-XZ, SHEAR-YZ.
where:
Comments
1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.
File Creation
This file is created when free size optimization is performed and OUTPUT, FSTHICK, YES is
present in the I/O Options section.
File Contents
Result Description
Element definition The element definitions for those elements that were part of a free
size design space. The optimized thickness of these elements are
provided as nodal thickness values (Ti).
File Format
The format for the .fsthick file is the same as for the corresponding bulk data entries.
File Creation
File Contents
Result Description
Grid point force Grid point force balance table for linear static analysis.
balance table
File Format
The file is divided up by iteration. Output from each iteration starts with a line in the following
format:
ITERATION Iteration_number
where:
ITERATION is a keyword denoting the beginning of a new iteration.
Each iteration section contains a force balance table for each node, for which this output
format was selected, in each linear static subcase.
where:
Node_id is the ID of the node to which the force balance table applies.
where:
Element_id is only valid for force contributions from elastic elements. This is
the element's ID.
Comments
1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.
File Creation
This file is created when topography or shape optimization is performed. Output of this file is
controlled by the I/O Option SHRES or by the GRID keyword on the OUTPUT card.
File Contents
Result Description
Nodal locations The nodal coordinates of the model for the last iteration of the
optimization.
File Format
The file uses the following format for each grid in the model:
GRID Id Cp X1 X2 X3 Cd Ps
where:
X1, X2, X3 provide the location of the grid point in the global coordinate
system.
The .h3d file is a compressed binary file, containing both model and result data. It can be
used to post-process results in HyperView or when using the HyperView Player.
File Creation
The .h3d file is created when the H3D format is chosen (see I/O options FORMAT and
OUTPUT), and an analysis only run is performed (meaning no design variables or design spaces
are defined in the model); the I/O option ANALYSIS is present; or the command line switch -
analysis is used (see Run Options for OptiStruct).
File Contents
The .h3d file contains node and element definitions in addition to the following results:
Result Description
Composite ply strain Ply strain results for composite materials from static
analyses.
Composite ply stress Ply stress results for composite materials from static
and analyses.
Composite failure indices Failure indices for composite materials from static
analyses.
Element energy loss per cycle Element energy loss per cycle and energy loss per cycle
density output from frequency response analysis.
Element kinetic energy Element kinetic energy and kinetic energy density
output from frequency response analysis.
Element strain energy Element strain energy and strain energy density results
from static, normal modes and frequency response
analyses.
Grid point stress Grid point stress results for 3D elements from static and
normal modes analyses.
Power flow field Power flow field output from frequency response and
acoustic analyses.
Comments
1. Grid point stresses are output for the entire model and for each individual component.
This allows grid point stresses to be accurately obtained at the interface of two
components referencing different material definitions.
2. For dynamic analyses like frequency response, transient response, and multi-body
dynamics, it is recommended that sets be used to reduce the amount of model and
results output data. The output file can become very large since results are output for
each frequency or time step.
File Creation
This file is created when an optimization is performed. Creation of this file is controlled by the
I/O Option DESHIS.
File Contents
This file may contain the iteration history of the objective function, constraint functions,
design variables, and response functions. Contents of this file are controlled by the I/O
option HISOUT.
File Creation
This file is created when an optimization is performed. Creation of this file is controlled by the
I/O Option DESHIS.
File Contents
This file contains the iteration history of the objective function, maximum constrain violation,
design variables, DRESP1 type responses, and DRESP2 type responses. Contents of this file
are controlled by the I/O option HISOUT.
File Format
The section outlines the format of the .hist OptiStruct ASCII file.
where:
Comments
1. The value of each design variable, DRESP1 response and DRESP2 response, is provided in
its own column.
File Creation
The .HM.comp.cmf file is created when a topology optimization is performed (see Topology
Optimization in the OptiStruct User's Guide).
File Contents
When executed in HyperMesh, the .HM.comp.cmf file organizes all elements in the model into
ten new components based on their material densities at the final iteration. The components
are named 0.0-0.1, 0.1-0.2, 0.2-0.3, and so on, up to 0.9-1.0. All elements with a material
density between 0% and 10% are contained in 0.0-0.1. All elements with a material density
between 10% and 20% are contained in 0.1-0.2, and so on. This helps you visualize results
by turning components on and off.
Comments
1. Ensure the corresponding model is loaded in HyperMesh when executing the command file.
2. Since elements cannot be in more than one component in HyperMesh, the original
components do not contain any elements.
File Creation
The .HM.conn.cmf file is created when a topology optimization is performed and 1D elements
form part of the topological design space (see Topology Optimization in the OptiStruct Users
Guide).
File Contents
When executed in HyperMesh, the .HM.conn.cmf file creates connector definitions for those
1D elements which formed part of the topological design space and organizes these
connectors into ten new components based on their material densities at the final iteration.
The components are named 0.0-0.1, 0.1-0.2, 0.2-0.3, and so on, up to 0.9-1.0. The
connector corresponding to those elements with a material density between 0% and 10% are
contained in the 0.0-0.1 component. The connectors corresponding to those elements with a
material density between 10% and 20% are contained in the 0.1-0.2 component, and so on.
This helps you to visualize results by turning components on and off.
Comments
1. Make sure that the corresponding model is loaded in HyperMesh when executing the
command file.
File Creation
File Contents
3. CBUSH or CELAS elements with excessive stiffness values (PARAM, BUSHSTIF and PARAM,
ELASSTIF).
When executed in HyperMesh, the .HM.elcheck.cmf file organizes all elements into separate
sets depending on which quality check they fail. One set is created for each failed quality
check. This helps you to visualize results by finding (displaying) elements by set.
Comments
1. Ensure the corresponding model is loaded in HyperMesh when executing the command file.
File Creation
The file is created, as required, when an element quality check is performed for optimization
iterations.
File Contents
3. CBUSH or CELAS elements with excessive stiffness values (PARAM, BUSHSTIF and PARAM,
ELASSTIF).
When executed in HyperMesh, the .HM.elcheck_###.cmf file organizes all elements into
separate sets depending on which quality check they fail. One set is created for each failed
quality check. This helps you to visualize results by finding (displaying) elements by set.
Comments
1. Ensure the corresponding model is loaded in HyperMesh when executing the command file.
2. The ### in the file name represents the optimization iteration number.
File Creation
The .HM.ent.cmf file is created when a topology optimization is performed (see Topology
Optimization in the OptiStruct User's Guide).
File Contents
When executed in HyperMesh, the .HM.ent.cmf file organizes all elements in the model into
ten new entity sets based on their material densities at the final iteration. The sets are
named 0.0-0.1, 0.1-0.2, 0.2-0.3, and so on, up to 0.9-1.0. All elements with a material
density between 0% and 10% are contained in 0.0-0.1. All elements with a material density
between 10% and 20% are contained in 0.1-0.2, and so on. You can then visualize the
results by masking the entity sets which contain those elements with lower density.
Comments
1. Ensure the corresponding model is loaded in HyperMesh when executing the command file.
2. The advantage of this method over the .HM.comp.cmf method is that the elements
remain in their original components, but can still be selected and masked by entity set.
File Creation
This file is created when a nonlinear gap analysis is performed and GAPPRM, HMGAPST is set
as YES or 1.
File Contents
When executed in HyperMesh, the .HM.gapstat.cmf file organizes gap elements into two
sets, open or closed, depending on the status of the gap at the end of the analysis.
Comments
1. Be sure that the corresponding model is loaded in HyperMesh when executing the
command file.
File Creation
File Contents
This file contains a problem summary and results summary of the run.
The problem summary contains information on the finite element model, subcase definitions,
and optimization parameters.
The results summary lists the following results for an analysis or the final iteration of an
optimization:
File Creation
File Contents
This acoustic coupling interface matrix visualization file contains element definitions.
Comments
2. Import this file into HyperMesh with the acoustic model already loaded. For best
performance, ensure that the FE overwrite option is turned on in the HyperMesh import
panel.
The .k.op2 file is a Nastran output2 format file containing the stiffness matrix.
File Creation
This file is created when PARAM, POST, -5 is present in the bulk data section.
File Contents
File Creation
File Contents
Result Description
File Format
where:
iter is a keyword denoting the beginning of a new iteration.
Each iteration section is divided up by subcase. Output for each subcase starts with a line
in the following format:
where:
The following information is then provided for each node, for which this output was
requested:
where:
Comments
1. The I/O option RESULTS controls the frequency of output for analytical results during an
Optimization.
The .m.op2 file is a Nastran output2 format file containing the mass matrix.
File Creation
This file is created when PARAM, POST, -5 is present in the bulk data section.
File Contents
File Creation
This file is only created when modal analyses are performed. Creation of this file is controlled
by the I/O Option OUTPUT.
File Contents
Result Description
Modal Effective Masses Modal effective mass results from modal analyses.
File Format
The file is formatted into blocks separated by blank lines. Each block represents a modal
subcase; the subcases are in order of occurrence in the input deck.
Each block contains a number of rows equal to the number of requested modes for that
subcase.
The columns, from left to right, contain results for modal effective mass for X-translation, Y-
translation, Z-translation, X-rotation, Y-rotation, and Z-rotation.
Comments
1. The _mass.mvw HyperView script file automatically creates plots for the results contained
in this file.
File Creatio n
This file is created when OUTPUT, ADAMSMNF is presented during flexible body generation.
File Contents
Comments
File Creation
File Contents
Result Description
File Format
The file is divided up by iteration. Output from each iteration starts with a line in the following
format:
ITERATION Iteration_number
where:
ITERATION is a keyword denoting the beginning of a new iteration.
Each iteration section contains the multi-point force of constraint for each node, for which
this output format was selected, in each linear static subcase. Each subcase section is
given the following header:
where:
Subcase_id is the user-defined subcase ID to which the mpc forces apply.
MPC force information is then provided, for each node, in the following format:
where:
Comments
1. The I/O option RESULTS controls the frequency of output for analytical results during an
Optimization.
The .op2 file is a Nastran output2 format for model and results data.
File Creation
This file is created when the O2, OUT2, or OUTPUT2 formats are chosen. (See documentation
for the I/O options FORMAT and OUTPUT).
File Contents
Result Description
Composite ply strain Ply strain results for composite materials from static analyses.
Composite ply stress Ply stress results for composite materials from static analyses.
Composite failure Failure indices for composite materials from static analyses.
indices
Output is controlled by the I/O option CSTRESS, by the SOUTi,
SB and FT fields on the PCOMP definition, and by the related
fields on the relevant material definition (see MAT1, MAT2,
MAT8).
Element energy Element energy loss per cycle and energy loss per cycle density
loss per cycle output from frequency response analysis.
Element force Element force results from static, frequency response, acoustic,
and transient response analyses.
Element kinetic Element kinetic energy and kinetic energy density output from
energy frequency response analysis.
Element strain Element strain energy and strain energy density results from
energy static, normal modes, frequency response, and transient
response analyses.
Grid point stress Grid point stress results for 3D elements from static analyses.
PSD element strain Power spectral density function of element strains from random
response analysis.
PSD element stress Power spectral density function of element stresses from
random response analysis.
RMS element strain Root mean square value of element strains from random
response analysis.
RMS element stress Root mean square value of element stresses from random
response analysis.
Comments
1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.
2. In addition to the analysis and optimization results, the finite element model description
(nodes, elements, coordinates systems, and properties) is written to the .op2 file. This
model can be read by HyperView and fatigue codes. To turn off the model output, use
the NOMODEL option on OUTPUT, OP2.
3. To be able to read the model directly from the .op2 file, newer versions of FEMFAT,
Medina (7.4.8 or newer), and Animator (3.0.6.6c or newer) must be used.
File Creation
File Contents
The file contains default settings for running OSSmooth after a successful optimization.
Comments
1. The format of this file is described on the OSSmooth Input Data page.
File Creation
File Contents
File Format
The file starts with an OptiStruct banner, and is followed by three sections which outline the
problem definition:
Element quality information (If any of the warning or error limits are exceeded).
Global force balance tables for each linear static subcase. (When SPCFORCE or
GPFORCE is a requested output).
Objective function value
Maximum constrain violation % and the ID of this constraint.
Design volume fraction value if topology design variables are present, otherwise the
total volume is given, and the total mass.
Individual subcase compliances and weightings and the total weighted compliance.
Retained responses table
If the constraint violation is higher than 1%, the constraint is flagged as V (violated). If the
violation is lower than 1%, it is flagged as A (active). For stress constraint in topology
optimization, if there is no violation, it is flagged as Inactive; otherwise, it is flagged as
Active.
Design variable values and bounds if shape or size design variables are present.
Designed property/material/connectivity items table if size design variables are present.
A list of calculated buckling modes and their eigenvalues.
A list of calculated normal modes, their frequencies, eigenvalues and weighting and the
value of the frequencies weighted across the reciprocal eigenvalues.
Center of Gravity table
Max Viol. – Represents the maximum violation of the specified manufacturing constraint
(Type).
Avg Viol. – Represents the average violation of all the violated elements for the
specified manufacturing constraint (Type).
Pct Viol. – Represents the percentage of the total number of elements in the design
space for which the specified manufacturing constraint (Type) is violated.
The Constraint Information columns are self-explanatory and may vary from one
constraint type to the other.
Avg. U – Represents the average displacement of all elements for a particular iteration
for a subcase
File Creation
This file is created when the NASTRAN or PUNCH formats are chosen. (See documentation for
the I/O options FORMAT and OUTPUT).
File Contents
Result Description
Element energy Element energy loss per cycle and energy loss per cycle density
loss per cycle output from frequency response analysis.
Element force Element force results from static, frequency response, acoustic,
and transient response analyses.
Element kinetic Element kinetic energy and kinetic energy density output from
energy frequency response analysis.
Element strain Element strain energy and strain energy density results from
energy static, normal modes and frequency response analyses.
Grid point stress Grid point stress results for 3D elements from static analysis.
PSD element strain Power spectral density function of element strains from random
response analysis. (see comment 2)
PSD element stress Power spectral density function of element stresses from
random response analysis. (see comment 2)
RMS element strain Root mean square value of element strains from random
response analysis.
RMS element stress Root mean square value of element stresses from random
response analysis.
Comments
1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.
2. Multiple RANDOM subcase information entries with non-unique ID’s are allowed in a single
model. Therefore, if the plot-type field on the XYPUNCH output request is set to PSDF,
then the RANDOM ID will be added to the XYPUNCH headers in the corresponding result
sections of the .pch file when multiple RANDOM entries are present in the same deck. If
only one RANDOM entry is present, the RANDOM ID is not printed.
File Creation
File Contents
This file contains elements and PCOMPG property information for each STACK.
File Creation
This file is created when XYPLOT, XYPEAK, or XYPUNCH is requested in random response
analysis.
File Contents
This file contains the root mean square value, the number of positive crossings, and the peak
power spectral density and responses.
File Creation
File Contents
Result Description
File Format
The file is sorted by iteration. Output from each iteration starts in the following format:
ITERATION Iteration_number
Where:
Each iteration section contains the force/adjustment values for each pretension bolt in
each static subcase. Each such subcase section is given the following header:
Where:
Where:
Pretension section ID denotes the pretension section ID (SID of the PRETENS bulk data
entry).
Force-incr is the incremental pretension force value when compared to the previous
subcase in the loading sequence.
Comments
1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.
File Creation
This file is output when sizing optimization is performed. Creation of this file is controlled by
the PROPERTY I/O option.
File Contents
Result Description
Property definition The property definitions, for those properties that were affected
in the sizing optimization, used for the final iteration of the
optimization.
File Format
The format for the property output is the same as for the bulk data entries.
File Creation
This file is only created for random response subcases. This file is only created if XYPLOT is
defined in random response.
File Contents
Result Description
Comments
1. The # in the file name is the user-defined subcase ID from which these results are
obtained.
2. The _rand.mvw HyperView script file automatically creates plots for the results contained
in this file.
File Creation
The .res file is created when either no format statement is given or when the HM, HYPER, or
BOTH formats are chosen. (See documentation for the I/O options FORMAT and OUTPUT).
File Contents
Result Description
Composite ply strain Ply strain results for composite materials from static
analyses.
Composite ply stress Ply stress results for composite materials from static
analyses.
Composite failure indices Failure indices for composite materials from static analyses.
Element strain energy Element strain energy results from static and normal modes
analyses.
Grid point stress Grid point stress results for 3D elements from static
analyses.
2. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.
3. Grid point stresses are output for the entire model and for each individual component.
This allows grid point stresses to be accurately obtained at the interface of two
components referencing different material definitions.
4. For dynamic analyses, like frequency response, transient response, and multi-body
dynamics, it is recommended that sets be used to reduce the amount of model and
results output data. The output file can become very large since results are output for
each frequency or time step.
File Creation
This file is created when the MODEL, PLOT, and PARAM, SEPLOT, YES options are presented
and the CBN method is used to reach a Component Mode Synthesis solution.
File Contents
Comments
1. By including this file in a residual run, the results of the superelement part will be
recovered and post-processed.
File Creation
This file is created when an optimization is performed. Output of this file is controlled by the
I/O option SHRES.
File Contents
Contains information necessary to restart the optimization from the final iteration.
File Creation
This file is created in a residual run when DMIG's are present in the model. The .spcd file
contains displacement results at interface grid points.
File Contents
Result Description
File Format
SUBCASE SID
where:
where:
1. Only one .spcd file is created even if there are multiple DMIG’s in the model.
File Creation
File Contents
Result Description
File Format
where:
iter is a keyword denoting the beginning of a new iteration.
Each iteration section is divided up by subcase. Output for each subcase starts with a line
in the following format:
where:
SPC-force information is then provided, for each node, in the following format:
where:
Comments
1. The I/O option RESULTS controls the frequency of output for analytical results during an
Optimization.
File Creation
File Contents
This file provides details on CPU and elapsed time for each solver module.
File Format
File Creation
This file is created when OPTI, OS, or ASCII formats are chosen. (See documentation for the
I/O options FORMAT and OUTPUT).
File Contents
Result Description
Strain Strain results from linear static analysis. Output is controlled by the I/O
option STRAIN.
File Format
where:
iter is a keyword denoting the beginning of a new iteration.
Numlds is the number of load cases for which this output is created.
Each iteration section is divided up by subcase. Output for each subcase starts with a line
in the following format:
Id Number_of_els STRN:Spc_id
where:
Id is the output identification number for the subcase. This is
not the same as the subcase ID used in the input data.
Strain information is then provided, for each element, in the following format:
where:
Strain1 is von Mises strain for 2D and 3D elements, or Axial strain for 1D
elements.
Comments
1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.
File Creation
This file is created when the OPTI, OS or BOTH formats are chosen. (See documentation for
the I/O options FORMAT and OUTPUT).
File Contents
Result Description
Stress Stress results from linear static analysis. Output is controlled by the I/O
option STRESS (or ELSTRESS).
File Format
where:
iter is a keyword denoting the beginning of a new iteration.
Numlds is the number of load cases for which this output is created.
Each iteration section is divided up by subcase. Output for each subcase starts with a line
in the following format:
Id Number_of_els STRS:Spc_id(Datatype)
where:
Id is the output identification number for the subcase. This is not
the same as the subcase ID used in the input data.
Stress information is then provided, for each element, in the following format:
where:
Stress1 von Mises stress for 2D and 3D elements, Maximum Axial stress for 1D
elements, or maximum stress in CWELD elements.
Comments
1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.
The _des.h3d file is a compressed binary file, containing both model and result data. It can
be used to post-process results in HyperView or when using the HyperView Player.
File Creation
The _des.h3d file is created when the H3D format is chosen (see documentation for the I/O
option FORMAT), and an optimization run is performed.
File Contents
The _des.h3d file contains node and element definitions in addition to the following results:
Result Description
File Creation
This file is automatically created when freeshape and topography (or shape) optimization runs
are terminated due to mesh distortion.
File Contents
Result Description
Nodal locations It contains the nodal coordinates of the distorted mesh for
freeshape and topography (or shape) optimization.
File Format
The file uses the following format for each grid in the model:
GRID Id Cp X1 X2 X3 Cd Ps
where:
Cp is blank.
X1, X2, X3 provide the location of the grid point in the global coordinate
system.
File Creation
File Contents
The file contains two frames. The top frame opens one of the .h3d files using the HyperView
Player browser plug-in. The .h3d file opened depends on the results selected for display in
the bottom frame. The bottom frame opens the _menu.html file, which facilitates the
selection of results to be displayed.
Comments
2. This file is linked to from the "Results summary" section of the .html file and is created
primarily for this purpose.
File Creation
This file is created when frequency response optimization is performed and OUTPUT,HGFREQ is
requested.
Comments
2. This file may be opened from the File menu in HyperView or HyperGraph. It automatically
creates plots for the results contained in the files: _s#_a.#.frf, _s#_d.#.frf, and
_s#_v.#.frf.
File Creation
This file is only created when frequency response analysis is performed. Creation of this file is
controlled by the I/O option OUTPUT.
File Contents
This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph. The file automatically creates plots for each of the results contained in the
files: _s#_a.frf, _s#_d.frf, and _s#_v.frf.
The _gauge.h3d file is a compressed binary file containing both model and result data. It can
be used to post-process shell thickness (gauge) sensitivity in HyperView.
File Creation
This file is created when an optimization is performed. Creation of this file is controlled by the
I/O option OUTPUT.
File Contents
The _gauge.h3d file contains node and element definitions in addition to the following results:
Result Description
Comments
The _gso.slk file is a Microsoft SLK Data Import format results file.
File Creation
This file is created when Global Search Option (GSO) is activated and executed using the
DGLOBAL I/O entry and the DGLOBAL Bulk Data entry, respectively. This file outputs the
results of Global Search Option (GSO).
File Contents
Result Description
Optimized Designs It contains the list of unique and similar optimized designs based
on the Global Search Option (GSO) method. The designs in this
resulting subset of the total design space are then sorted based
on their rank (based on the number of convergences from unique
starting points to result in a specific design).
File Format
The file uses the following format for the designs optimized from specified starting points:
Unique Designs
Design Startin Times Directo Objecti C onstr Max. Avg. Max. Avg. DV1 DVN
Rank g Point Found ry ve aint Obj. Obj. DV DV
Name Functio Violatio Deviati Deviati Deviati Deviati
n n on on on on
All Designs
Where,
Design Rank Denotes the rank of the design. This is assigned based initially on the values
of Constraint Violation and then the Objective Function values.
Starting Point Denotes the starting point of the optimization for a design in the design
space.
Times Found The number of times designs (from unique starting points) converge to the
same design.
Directory Name of the Directory where the output files associated with the specified
Name design are stored.
Constraint The value of the Constraint Violation for the current design
Violation
Maximum The maximum deviation (of a design) from the objective function among
Objective designs from unique starting points that converged to this unique design.
Deviation
Average The average deviation (of a design) from the objective function among
Objective designs from unique starting points that converged to this unique design.
Deviation
Maximum DV The maximum deviation between two design variables in the design space
Deviation among designs from unique starting points that converged to this unique
design.
Average DV The average deviation between design variables in the design space among
Deviation designs from unique starting points that converged to this unique design.
DV# The various design variables values represented by DV1, DV2,….., DVN.
Unique Design This represents the Design Rank used in the UNIQUE DESIGN Table.
File Creation
This file is created when an optimization is performed. Creation of this file is controlled by the
I/O option DESHIS.
File Contents
This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph. The file automatically creates individual plots for each of the results contained in
the .hist file. Each plot occupies its own page within HyperView (HyperGraph).
File Creation
Comments
2. This file may be opened from the File menu in HyperView or HyperGraph. It automatically
creates bar charts for the results contained in .#.mass file.
File Creation
This file is only created when modal analyses are performed. Creation of this file is controlled
by the I/O option OUTPUT.
File Contents
This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph. The file automatically creates plots for the results contained in the .mass file.
The _mbd.h3d file is a compressed binary file containing both model and result data from a
multi-body dynamics analysis. It can be used to post-process results in HyperView.
File Creation
File Contents
The _mbd.h3d file contains node and element definitions in addition to the following results:
Result Description
Comments
1. This file format is the most compressed animation output for multi-body dynamics
analyses. It generates the smallest files compared to other formats.
The _mbd.log file is an ASCII format log file from a multi-body dynamics analysis.
File Creation
This file is created when a multi-body dynamics subcase is executed. It is a direct output file
of MotionSolve.
File Contents
File Creation
This file is created when a multi-body dynamics subcase is defined. The file contains time
history data that can be used for 2D plotting in HyperGraph. Some data is written by default,
and some needs to be requested.
File Contents
KE Kinetic energy
Data output by request. The request needs to be defined through a REQUEST I/O statement.
Type
Component Description
File Creation
This file is only created when a multi-body dynamics analysis is performed. Creation of this
file is controlled by the I/O option OUTPUT.
File Contents
This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph. The file automatically creates plots for each of the results contained in the
files: _s#_a.mbd, _s#_d.mbd, and _s#_v.mbd.
The _mbd.xml file is a MotionSolve XML file from a multi-body dynamics analysis.
File Creation
File Contents
The file format is documented in the MotionSolve manual. The purpose is the communication
between the OptiStruct core and the integrated MotionSolve. This file, together with the
<BODY_NAME>.h3d files, forms a full representation of the multi-body dynamics model which
can be run separately in MotionSolve.
File Creation
File Contents
This file facilitates the selection of the appropriate .h3d file, for the HyperView Player browser
plug-in in the top frame of the _frames.html file, based on chosen results.
Comments
File Creation
This file is only created for frequency response and transient analyses. Creation of this file is
controlled by the I/O option OUTPUT (with the HGMODFAC keyword).
File Contents
This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph3D. The file contains HyperGraph3D plots of modal participation factors. The plots
display the mode number on the x-axis, the frequency (for frequency response analyses) or
time (for transient analyses) on the y-axis, and the modal participation factor on the z-axis.
Modal participation factor vs. frequency or time for a given mode number
Modal participation factor vs. mode number at a given frequency or time
For frequency response analyses, plots are generated for the real part, the imaginary part and
the magnitude of the participation factors. Magnitude plot is visible by default, while real and
imaginary plots are hidden by default.
Comments
File Creation
This file is only created for frequency response and transient analyses. Creation of this file is
controlled by the I/O option OUTPUT (with the HGMODFAC keyword).
File Contents
This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph3D. The file contains HyperGraph3D plots of modal participation factors. The plots
display the mode number on the x-axis, the frequency (for frequency response analyses) or
time (for transient analyses) on the y-axis, and the modal participation factor on the z-axis.
Modal participation factor vs. frequency or time for a given mode number
Modal participation factor vs. mode number at a given frequency or time
For frequency response analyses, plots are generated for the real part, the imaginary part and
the magnitude of the participation factors. Magnitude plot is visible by default, while real and
imaginary plots are hidden by default.
Comments
1. This file is generated for an analysis-only run; the _modal.#.mvw is generated for
optimization runs where # is the iteration number.
File Creation
This file is only created when random response analysis is performed. This file is only created
if XYPLOT is defined in random response.
File Contents
This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph. The file automatically creates plots for each of the results contained in .rand
files.
The _s#.h3d file is a compressed binary file, containing both model and result data. It can be
used to post-process results in HyperView or using the HyperView Player.
File Creation
The _s#.h3d file is created when the H3D format is chosen (See documentation for the I/O
option FORMAT), and an optimization is performed containing a linear static subcase. A similar
file is created for each static subcase.
File Contents
The _s#.h3d file contains node and element definitions in addition to the following results:
Result Description
Element strain energy Element strain energy results from linear static analysis.
Output is controlled by the I/O option ESE.
Comments
2. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.
File Creation
This file is only created for frequency response optimization. Output is controlled by the I/O
option ACCELERATION and OUTPUT,HGFREQ.
File Contents
This file contains the acceleration results from frequency response optimization.
File Format
If the real and imaginary format was selected on the ACCELERATION card, the file starts with
the following header:
If the phase and magnitude format was selected on the DISPLACEMENT card, the file starts
with the following header:
In either case, the results are grouped by node with results for different nodes separated by a
blank line. The format of each line after the header is as follows:
where:
X-rl/ph is either the real component in the x-direction or the phase angle
in the x-direction component.
Y-rl/ph is either the real component in the y-direction or the phase angle
in the y-direction component.
Z-rl/ph is either the real component in the z-direction or the phase angle
in the z-direction component.
Comments
3. The_freq.#.mvw HyperView script file automatically creates plots for the results
contained in this file.
File Creation
This file is only created for frequency response subcases. Creation of this file is controlled by
the I/O option OUTPUT.
File Contents
Result Description
File Format
If the real and imaginary format was selected on the ACCELERATION card, the file starts with
the following header:
If the phase and magnitude format was selected on the ACCELERATION card, the file starts
with the following header:
In either case the results are grouped by node with results for different nodes separated by a
blank line. The format of each line after the header is as follows:
where:
X-rl/ph is either the real component in the x-direction or the phase angle
Y-rl/ph is either the real component in the y-direction or the phase angle
in the y-direction component.
Z-rl/ph is either the real component in the z-direction or the phase angle
in the z-direction component.
Comments
1. The # in the file name is the user-defined subcase ID from which these results are
obtained.
2. The _freq.mvw HyperView script file automatically creates plots for the results contained
in this file.
File Creation
This file is only created for Multi-Body Dynamics subcases. Creation of this file is controlled
by the I/O option OUTPUT.
File Contents
Result Description
File Format
Comments
1. The # in the file name is the user-defined subcase ID from which these results are
obtained.
2. The _mbd.mvw HyperView script file automatically creates plots for the results contained
in this file.
File Creation
This file is only created for transient response subcases. Creation of this file is controlled by
the I/O option OUTPUT.
File Contents
Result Description
File Format
Comments
1. The # in the file name is the user-defined subcase ID from which these results are
obtained.
2. The _tran.mvw HyperView script file automatically creates plots for the results contained
in this file.
File Creation
This file is only created for frequency response optimization. Output is controlled by the I/O
option DISPLACEMENT and OUTPUT,HGFREQ.
File Contents
This file contains the displacement results from frequency response optimization.
File Format
If the real and imaginary format was selected on the DISPLACEMENT card, the file starts with
the following header:
If the phase and magnitude format was selected on the DISPLACEMENT card, the file starts
with the following header:
In either case, the results are grouped by node with results for different nodes separated by a
blank line. The format of each line after the header is as follows:
where:
X-rl/ph is either the real component in the x-direction or the phase angle
in the x-direction component.
Y-rl/ph is either the real component in the y-direction or the phase angle
in the y-direction component.
Z-rl/ph is either the real component in the z-direction or the phase angle
in the z-direction component.
Comments
3. The _freq.#.mvw HyperView script file automatically creates plots for the results
contained in this file.
File Creation
This file is only created for frequency response subcases. Creation of this file is controlled by
the I/O option OUTPUT.
File Contents
Result Description
File Format
If the real and imaginary format was selected on the DISPLACEMENT card, the file starts with
the following header:
If the phase and magnitude format was selected on the DISPLACEMENT card, the file starts
with the following header:
In either case, the results are grouped by node with results for different nodes separated by a
blank line. The format of each line after the header is as follows:
where:
X-rl/ph is either the real component in the x-direction or the phase angle
Y-rl/ph is either the real component in the y-direction or the phase angle
in the y-direction component.
Z-rl/ph is either the real component in the z-direction or the phase angle
in the z-direction component.
Comments
1. The # in the file name is the user-defined subcase ID from which these results are
obtained.
2. The _freq.mvw HyperView script file automatically creates plots for the results contained
in this file.
File Creation
This file is only created for Multi-Body Dynamics subcases. Creation of this file is controlled
by the I/O option OUTPUT.
File Contents
Result Description
File Format
Comments
1. The # in the file name is the user-defined subcase ID from which these results are
obtained.
2. The _mbd.mvw HyperView script file automatically creates plots for the results contained
in this file.
File Creation
This file is only created for transient response subcases. Creation of this file is controlled by
the I/O option OUTPUT.
File Contents
Result Description
File Format
Comments
1. The # in the file name is the user-defined subcase ID from which these results are
obtained.
2. The _tran.mvw HyperView script file automatically creates plots for the results contained
in this file.
File Creation
This file is only created for frequency response optimization. Output is controlled by the I/O
option VELOCITY and OUTPUT,HGFREQ.
File Contents
This file contains the velocity results from frequency response optimization.
File Format
If the real and imaginary format was selected on the VELOCITY card, the file starts with the
following header:
If the phase and magnitude format was selected on the DISPLACEMENT card, the file starts
with the following header:
In either case, the results are grouped by node with results for different nodes separated by a
blank line. The format of each line after the header is as follows:
where:
X-rl/ph is either the real component in the x-direction or the phase angle
in the x-direction component.
Y-rl/ph is either the real component in the y-direction or the phase angle
in the y-direction component.
Z-rl/ph is either the real component in the z-direction or the phase angle
in the z-direction component.
Comments
3. The _freq.#.mvw HyperView script file automatically creates plots for the results
contained in this file.
File Creation
This file is only created for frequency response subcases. Creation of this file is controlled by
the I/O option OUTPUT.
File Contents
Result Description
File Format
If the real and imaginary format was selected on the VELOCITY card, the file starts with the
following header:
If the phase and magnitude format was selected on the VELOCITY card, the file starts with
the following header:
In either case, the results are grouped by node with results for different nodes separated by a
blank line. The format of each line after the header is as follows:
where:
X-rl/ph is either the real component in the x-direction or the phase angle
in the x-direction component.
Y-rl/ph is either the real component in the y-direction or the phase angle
in the y-direction component.
Z-rl/ph is either the real component in the z-direction or the phase angle
in the z-direction component.
Comments
1. The # in the file name is the user-defined subcase ID from which these results are
obtained.
2. The _freq.mvw HyperView script file automatically creates plots for the results contained
in this file.
File Creation
This file is only created for multi-body dynamics subcases. Creation of this file is controlled by
the I/O option OUTPUT.
File Contents
Result Description
File Format
Comments
1. The # in the file name is the user-defined subcase ID from which these results are
obtained.
2. The _mbd.mvw HyperView script file automatically creates plots for the results contained
in this file.
File Creation
This file is only created for transient response subcases. Creation of this file is controlled by
the I/O option OUTPUT.
File Contents
Result Description
File Format
Comments
1. The # in the file name is the user-defined subcase ID from which these results are
obtained.
2. The _tran.mvw HyperView script file automatically creates plots for the results contained
in this file.
File Creation
This file is created when an optimization is performed. Creation of this file is controlled by the
I/O option OUTPUT.
File Contents
This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph. The file automatically creates a histogram for each of the results contained in
the .#.sens file. The plots are grouped so that design variable sensitivities for different
responses are given on separate pages.
Comments
File Creation
This file is created when OUTPUT, SZTOSH (sizing to shuffling) is requested during the ply-
based sizing optimization phase.
File Contents
This file is a ply-based stacking optimization input deck. It contains the updated PLY and
STACK cards describing the stacking model, as well as a DSHUFFLE card defining shuffling
design variables.
Comments
File Creation
This file is created when OUTPUT, FSTOSZ (free-sizing to sizing) is requested during the free-
sizing optimization phase.
File Contents
This file is a ply-based sizing optimization input deck. It contains PCOMPP, STACK, PLY, and
SET cards describing the ply-based composite model, as well as DCOMP, DESVAR, and DVPREL
cards defining the optimization data.
Comments
The _topol.h3d file is a compressed binary file containing both model and result data. It can
be used to post-process topology (density) sensitivity in HyperView.
File Creation
This file is created when an optimization is performed. Creation of this file is controlled by the
I/O option OUTPUT.
File Contents
The _topol.h3d file contains node and element definitions in addition to the following results:
Result Description
Comments
File Creation
This file is only created when a transient response analysis is performed. Creation of this file
is controlled by the I/O option OUTPUT.
File Contents
This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph. The file automatically creates plots for each of the results contained in the files
_s#_a.trn, _s#_d.trn, and _s#_v.trn.
The <BODY_NAME>.h3d file is a compressed binary file from a multi-body dynamics analysis
that uses flexible bodies defined through a PFBODY bulk data entry.
File Creation
This file is created when a multi-body dynamics subcase is executed. One file for each
PFBODY entry is generated. BODY_NAME is taken directly from PFBODY, BODY_NAME. If no
BODY_NAME is given, the default is OUTFILE_body_<BID>.h3d. By default, the flexible body is
only generated once; and if a file already exists in the execution directory, the flexible body
generation is not repeated. The default can be changed by the parameter PARAM, FLEXH3D.
File Contents
This file contains the modal representation of the flexible body for direct use in the multi-body
dynamics solution sequence or in MotionSolve. It is generated using a Component Mode
Synthesis. Each flexible body is written to a separate file.
The tables in this section summarize the results output for different analysis types. They
show the formats available for each result and the I/O option entry that controls the output
of the result.
Controlling
H3D HM OP2 PCH OPT PAT
I/O Option
Controlling
H3D HM OP2 PCH OPT PAT
I/O Option
Eigenvectors DISPLACEMENT
Controlling
H3D OP2 PCH
I/O Option
Eigenvectors DISPLACEMENT
Controlling
H3D HM OP2 PCH OPT
I/O Option
Eigenvectors DISPLACEMENT
Controlling
H3D HM OP2 PCH OPT XYPUNCH
I/O Option
XYPLOT
XYPUNCH PUNCH OP2 H3D
(HyperGraph)
Shell Stress
Shell Strain
Solid Stress
Solid Strain
CBUSH Force
Controlling
Controlling
H3D OP2 PCH I/O Option
I/O Option
(Block Format)
/ANIM/VECT/DISP
Nodal Displacements DISPLACEMENT
/ANIM/VECT/DROT
/ANIM/BRICK/TENS/
STRESS
/ANIM/SHELL/TENS/
STRESS/UPPER
Element Stresses* STRESS /ANIM/SHELL/TENS/
STRESS/LOWER
/ANIM/BEAM/VONM
/ANIM/TRUSS/SIGX
/ANIM/BRICK/TENS/
STRAIN
/ANIM/SHELL/TENS/
Element Strains* STRAIN
STRAIN/UPPER
/ANIM/SHELL/TENS/
STRAIN/LOWER
/ANIM/SHELL/TENS/
STRESS/N
Ply Stresses CSTRESS
/ANIM/SHELL/TENS/
STRESS/ALL
/ANIM/SHELL/TENS/
Ply Strains CSTRAIN
STRAIN/ALL
Composite Failure
CSTRESS N/A
Indices
/ANIM/GPS1/TENS
Grid Point Stresses GPSTRESS
/ANIM/GPS1/SHELL/
UPPER
/ANIM/GPS1/SHELL/
LOWER
/ANIM/VECT/FREAC
SPC Forces SPCFORCE
/ANIM/VECT/MREAC
/ANIM/ELEM/EPSP
/ANIM/SHELL/EPSP/
STRAIN
Plastic Strain UPPER
(PLASTIC)
/ANIM/SHELL/EPSP/
LOWER
/ANIM/ELEM/ENER
Element Energy ENERGY
/ANIM/ELEM/HOURG
Optimization Results
Controlling
H3D HM OP2 PCH OPT PAT
I/O Option
% Thickness THICKNESS
Shape SHAPE
* The element stress and strain results written to the various output streams are not
always the same. Refer to the following pages for more details on the stress results
available in the different output streams:
Strain Results Written in HyperView .h3d Format
Strain Results Written in Nastran .op2 and .pch Formats
Strain Results Written in HyperMesh .res Format
Stress Results Written in HyperView .h3d Format
Stress Results Written in Nastran .op2 and .pch Format
Stress Results Written in HyperMesh .res Format
1D Elements
The following strain results are output for CBAR/CBEAM elements defined via PBARL/PBEAML
property entries. The Result type: HyperView is CBAR/CBEAM Strains (<TYPE>), where the
<TYPE> entry is based on the selected cross-section (TYPE/NAME field) on the PBARL/PBEAML
entries. The element strain results can be reviewed for each cross-section type,
corresponding evaluation point, at element ends (A or B). The maximum normal/shear/von
Mises strains can also be reviewed.
Syntax
Where,
<Type> = BAR, BOX, BOX1, CHAN, CHAN1, CHAN2, CROSS, H, HAT, I, I1, ROD, T, T1,
T2, TUBE, Z.
<Strain Result Output> = normal, shear, and von Mises
<evaluation point> = evaluation point of the element
- CBAR/CBEAM Strains(BAR)
Normal S1N(A)
Normal S1N(B)
Shear S4S(A)
Shear S4S(B)
von Mises S8V(A)
von Mises S8V(B)
Example descriptions
Normal S3N(B): normal strain at the 3rd evaluation point of the beam element (end B);
Shear S6S(A): shear strain at the 6th evaluation point of the beam element (end A);
von Mises S5V(B): von Mises strain at the 5th evaluation point of the beam element (end
B).
Review evaluation points via: DRESP1 - Static Strain Item Codes for Bar Elements using
PBARL, PBEAML Properties
The von Mises strains for all CBEAM/CBAR elements with PBARL/PBEAML properties at the same
time can be output using the Result type: CBAR/CBEAM vonMises Strains.
Syntax
Where,
2D Elements
DIRECT option
Von Mises Strain
Maximum Principal Strain
Von Mises Strain (Z1)
Von Mises Strain (Z2)
Von Mises Strain (mid)
P1 (major) Strain (Z1)
P1 (major) Strain (Z2)
P1 (major) Strain (mid)
VON option
Von Mises Strain - This is equal to max[Von Mises Strain (Z1), Von Mises Strain
(Z2)]
PRINC option
Von Mises Strain
Maximum Principal Strain
3D Elements
DIRECT option
Von Mises Strain
Signed Von Mises Strain
P1 (major) Strain (solid)
P2 (mid) Strain (solid)
P3 (minor) Strain (solid)
Normal X Strain (solid)
Normal Y Strain (solid)
Normal Z Strain (solid)
Shear XY Strain (solid)
Shear YZ Strain (solid)
Shear XZ Strain (solid)
VON option
Von Mises Strain
PRINC option
Comments
1. In the TENSOR mode, pass tensor components to HyperView which then calculates derived
results on-the-fly.
1D elements
CROD Axial Strain
CELAS Strain
CBAR SA1
CBAR SA2
CBAR SA3
CBAR SA4
CBAR Axial
CBAR SA-maximum
CBAR SA-minimum
CBAR SB1
CBAR SB2
CBAR SB3
CBAR SB4
CBAR SB-maximum
CBAR SB-minimum
2D elements
Fibre Distance (Z1)
Normal XX Strain (Z1)
Normal YY Strain (Z1)
Shear XY Strain (Z1)
Principal Strain Angle (Z1)
Major Principal Strain (Z1)
Minor Principal Strain (Z1)
Von Mises Strain (Z1)
Fibre Distance (Z2)
Normal XX Strain (Z2)
Normal YY Strain (Z2)
Shear XY Strain (Z2)
3D elements
Normal XX Strain
Shear XY Strain
Major Principal Strain
Major Principal X Cosine
Mid Principal X Cosine
Minor Principal X Cosine
Mean Strain
Von Mises Strain
Normal YY Strain
Shear YZ Strain
Mid Principal Strain
Major Principal Y Cosine
Mid Principal Y Cosine
Minor Principal Y Cosine
Normal ZZ Strain
Shear XZ Strain
Minor principal Strain
Major Principal Y Cosine
Mid Principal Y Cosine
Minor Principal Y Cosine
Eigenvalue Loadcases
1D elements
None.
2D elements
Fibre Distance (Z1)
Normal XX Strain (Z1)
Normal YY Strain (Z1)
Shear XY Strain (Z1)
Principal Strain Angle (Z1)
Major Principal Strain (Z1)
Minor Principal Strain (Z1)
Von Mises Strain (Z1)
Fibre Distance (Z2)
Normal XX Strain (Z2)
Normal YY Strain (Z2)
Shear XY Strain (Z2)
Principal Strain Angle (Z2)
Major Principal Strain (Z2)
Minor Principal Strain (Z2)
Normal XX Strain
Shear XY Strain
Major Principal Strain
Major Principal X Cosine
Mid Principal X Cosine
Minor Principal X Cosine
Mean Strain
Von Mises Strain
Normal YY Strain
Shear YZ Strain
Mid Principal Strain
Major Principal Y Cosine
Mid Principal Y Cosine
Minor Principal Y Cosine
Normal ZZ Strain
Shear XZ Strain
Minor principal Strain
Major Principal Y Cosine
Mid Principal Y Cosine
Minor Principal Y Cosine
1D elements
CROD Axial Strain
CELAS Strain
CBAR SA1
CBAR SA2
CBAR SA3
CBAR SA4
CBAR Axial
CBAR SA-maximum
CBAR SA-minimum
CBAR SB1
CBAR SB2
CBAR SB3
CBAR SB4
CBAR SB-maximum
CBAR SB-minimum
2D elements
Fibre Distance (Z1)
Normal XX Strain (real) (Z1)
Normal XX Strain (imag) (Z1)
Normal YY Strain (real) (Z1)
Normal YY Strain (imag) (Z1)
Shear XY Strain (real) (Z1)
Shear XY Strain (imag) (Z1)
Fibre Distance (Z2)
Normal XX Strain (real) (Z2)
Normal XX Strain (imag) (Z2)
Normal YY Strain (real) (Z2)
Normal YY Strain (imag) (Z2)
Shear XY Strain (real) (Z2)
Shear XY Strain (imag) (Z2)
3D elements
Normal XX Strain (real)
Normal YY Strain (real)
Normal ZZ Strain (real)
Shear XY Strain (real)
Shear YZ Strain (real)
Shear XZ Strain (real)
Normal XX Strain (imag)
Normal YY Strain (imag)
Normal ZZ Strain (imag)
Shear XY Strain (imag)
Shear YZ Strain (imag)
Shear XZ Strain (imag)
Comments
1. The order above reflects the contents of the OP2 file, but post-processors such as
HyperView may display results in a different manner.
VON option
Von Mises Strain
PRINC option
Von Mises Strain
Maximum Principal Strain
Comments
1. "von Mises Strain" and "Maximum Principal Strain" apply to 1D, 2D, and 3D elements
simultaneously. Other results apply to 2D or 3D elements exclusively. There are no
specific results for 1D elements.
2. For frequency response loadcases, (comp) may be replaced by (real) (imag) (magn) and/or
(phas), depending on the complex format request.
6. "Signed von Mises Strain" is the von Mises strain with traction/compression sign:
sign(P1+P2+P3) * VonMises.
1D Elements
The following stress results are output for CBAR/CBEAM elements defined via PBARL/PBEAML
property entries. The Result type: HyperView is CBAR/CBEAM Stresses (<TYPE>), where the
<TYPE> entry is based on the selected cross-section (TYPE/NAME field) on the PBARL/PBEAML
entries. The element stress results can be reviewed for each cross-section type,
corresponding evaluation point, at element ends (A or B). The maximum normal/shear/von
Mises stresses can also be reviewed.
Syntax
Where,
<Type> = BAR, BOX, BOX1, CHAN, CHAN1, CHAN2, CROSS, H, HAT, I, I1, ROD, T, T1,
T2, TUBE, Z.
- CBAR/CBEAM Stresses(BAR)
Normal S1N(A)
Normal S1N(B)
Shear S4S(A)
Shear S4S(B)
von Mises S8V(A)
von Mises S8V(B)
Example descriptions
Normal S3N(B): normal stress at the 3rd evaluation point of the beam element (end B);
Shear S6S(A): shear stress at the 6th evaluation point of the beam element (end A);
von Mises S5V(B): von Mises stress at the 5th evaluation point of the beam element (end
B).
Review evaluation points via: DRESP1 - Static Stress Item Codes for Bar Elements using
PBARL, PBEAML Properties
The von Mises stresses for all CBEAM/CBAR elements with PBARL/PBEAML properties at the
same time can be output using the Result type: CBAR/CBEAM vonMises Stresses.
Syntax
Where,
2D Elements
DIRECT option
Von Mises Stress
Maximum Principal Stress
Von Mises Stress (Z1)
Von Mises Stress (Z2)
VON option - This is equal to max[Von Mises Stress (Z1), Von Mises Stress (Z2)]
PRINC option
Von Mises Stress
Maximum Principal Stress
3D Elements
DIRECT option
Von Mises Stress
Signed Von Mises Stress
P1 (major) Stress (solid)
P2 (mid) Stress (solid)
P3 (minor) Stress (solid)
Normal X Stress (solid)
Normal Y Stress (solid)
Normal Z Stress (solid)
Shear XY Stress (solid)
Shear YZ Stress (solid)
Shear XZ Stress (solid)
VON option
Von Mises Stress
Comments
1. In the TENSOR mode, pass tensor components to HyperView, which then calculates
derived results on-the-fly.
1D elements
CROD Axial Stress
CELAS Stress
CBAR SA1
CBAR SA2
CBAR SA3
CBAR SA4
CBAR Axial
CBAR SA-maximum
CBAR SA-minimum
CBAR SB1
CBAR SB2
CBAR SB3
CBAR SB4
CBAR SB-maximum
CBAR SB-minimum
2D elements
Fibre Distance (Z1)
Normal XX Stress (Z1)
Normal YY Stress (Z1)
Shear XY Stress (Z1)
Principal Stress Angle (Z1)
Major Principal Stress (Z1)
Minor Principal Stress (Z1)
Von Mises Stress (Z1)
Fibre Distance (Z2)
Normal XX Stress (Z2)
Normal YY Stress (Z2)
3D elements
Normal XX Stress
Shear XY Stress
Major Principal Stress
Major Principal X Cosine
Mid Principal X Cosine
Minor Principal X Cosine
Mean Stress
Von Mises Stress
Normal YY Stress
Shear YZ Stress
Mid Principal Stress
Major Principal Y Cosine
Mid Principal Y Cosine
Minor Principal Y Cosine
Normal ZZ Stress
Shear XZ Stress
Minor principal Stress
Major Principal Y Cosine
Mid Principal Y Cosine
Minor Principal Y Cosine
Eigenvalue Loadcases
1D elements
None
2D elements
Fibre Distance (Z1)
Normal XX Stress (Z1)
Normal YY Stress (Z1)
Shear XY Stress (Z1)
Principal Stress Angle (Z1)
Major Principal Stress (Z1)
Minor Principal Stress (Z1)
Von Mises Stress (Z1)
Fibre Distance (Z2)
Normal XX Stress (Z2)
Normal YY Stress (Z2)
Shear XY Stress (Z2)
Principal Stress Angle (Z2)
Major Principal Stress (Z2)
Minor Principal Stress (Z2)
1D elements
CROD Axial Stress
CELAS Stress
CBAR SA1
CBAR SA2
CBAR SA3
CBAR SA4
CBAR Axial
CBAR SA-maximum
CBAR SA-minimum
CBAR SB1
CBAR SB2
CBAR SB3
CBAR SB4
CBAR SB-maximum
CBAR SB-minimum
2D elements
Fibre Distance (Z1)
Normal XX Stress (real) (Z1)
Normal XX Stress (imag) (Z1)
Normal YY Stress (real) (Z1)
Normal YY Stress (imag) (Z1)
Shear XY Stress (real) (Z1)
Shear XY Stress (imag) (Z1)
Fibre Distance (Z2)
Normal XX Stress (real) (Z2)
Normal XX Stress (imag) (Z2)
Normal YY Stress (real) (Z2)
Normal YY Stress (imag) (Z2)
Shear XY Stress (real) (Z2)
Shear XY Stress (imag) (Z2)
3D elements
Normal XX Stress (real)
Normal YY Stress (real)
Normal ZZ Stress (real)
Shear XY Stress (real)
Shear YZ Stress (real)
Shear XZ Stress (real)
Normal XX Stress (imag)
Normal YY Stress (imag)
Normal ZZ Stress (imag)
Shear XY Stress (imag)
Shear YZ Stress (imag)
Shear XZ Stress (imag)
Comments
1. The order above reflects the contents of the OP2 file, but post-processors such as
HyperView may display results in a different manner.
2. For 2D elements, results are printed at the center of the element, followed by results at
each grid when corner stresses are requested.
3. For 3D elements, results are printed at the center of the element, followed by results at
each grid when corner stresses are requested. In the OP2 format, regardless of the
corner stress request, results are printed at each grid by duplicating results at the
center.
VON option
Von Mises Stress
PRINC option
Von Mises Stress
Maximum Principal Stress
1. "von Mises Stress" and "Maximum Principal Stress" apply to 1D, 2D, and 3D elements
simultaneously. Other results apply to 2D or 3D elements exclusively. There are no
specific results for 1D elements.
2. For frequency response loadcases, (comp) may be replaced by (real) (imag) (magn) and/or
(phas), depending on the complex format request.
6. "Signed von Mises Stress" is the von Mises stress with traction/compression sign:
sign(P1+P2+P3) * VonMises.
OptiStruct will continue to support the old input format from version 3.5. The new
optimization capabilities will not be available if the old format is used for the set up of the
optimization problem, that is, if matfrac, mini, maxi, ubcon or lbcon are present.
This section is intended to be used for the purpose of debugging or re-running older decks.
Matinit <real>def. = 0.9 or This card declares the initial material fraction.
constraint val. For runs with mass as the objective, default is
0.9. For runs with constrained mass, default is
reset to constraint value.
Setting up an optimization was simpler in OptiStruct 3.5, but it was also very limited. Starting
with OptiStruct 5.0, a lot more flexibility has been added to the way objectives and
constraints are set up, but the problem setup is more complex. Although versions of
OptiStruct (including and beyond 5.0) will execute OptiStruct 3.5 decks flawlessly, users are
urged to create decks using the new optimization format. This section demonstrates how
objectives and constraints in OptiStruct 3.5 (such as comp, freq, wcomp, wfreq, and comb)
can be set up in OptiStruct 5.0 and higher.
The new optimization capabilities of OptiStruct 5.0 and higher will not be available if the old
format is used for the setup of the optimization problem (if matfrac, mini, maxi, ubcon, or
lbcon are present in the setup).
In OptiStruct 3.5, two cards were used to do this kind of optimization: mini, comp and ubcon,
0.3, volume.
The new setup is as follows: mini, comp is replaced by DESOBJ(MIN) = 1 and ubcon, 0.3,
volume is replaced by DESGLB = 101. Three cards (two DRESP1s and one DCONSTR) defining
the responses and constraint values referenced in the header are added after the BEGIN BULK
statement as shown below:
$
DESGLB = 101
$
SUBCASE 1
LOAD = 2
SPC = 1
DESOBJ(MIN) = 1
$
BEGIN BULK
$
DRESP1, 1, comp, COMP
DRESP1, 100, massf, MASSFRAC
DCONSTR, 101, 100, , 0.300
$
The deck setup for this problem is similar to the previous one. Since the objective is global
(mass), the DESOBJ statement goes outside of the load case definition. The constraint on
displacement is only active for the first load case; thus a DESSUB statement is used within
that load case.
$
DESOBJ(MIN) = 1
$
SUBCASE 1
LOAD = 2
SPC = 1
DESSUB = 101
OptiStruct provides the response type WCOMP, weighted compliance, to be defined on the
DRESP1 card. In addition, you need to define the weight factors for each load case included
in the weighted compliance function. Note that both the objective and constraint are global
quantities (not specific to any single load case) and thus the DESOBJ and DESGLB statements
occur before the load case declarations.
$
DESOBJ = 50
DESGLB = 101
$
SUBCASE 1
LOAD = 2
SPC = 1
WEIGHT = 2.0
$
SUBCASE 2
LOAD = 3
SPC = 1
WEIGHT = 1.0
$
BEGIN BULK
$
DRESP1, 50, wcomp, WCOMP
$
DRESP1, 100, weight, MASS
DCONSTR, 101, 100, , 1.560
$
The setup for this deck is similar to that for the first two decks except that, starting with
OptiStruct 5.0, the volume response now refers to the actual volume (not the volume
fraction).
$
DESGLB = 101
$
SUBCASE 1
METHOD = 2
SPC = 1
DESOBJ(MAX) = 1
$
In OptiStruct 3.5, the weighted frequency response (wfreq), was minimized since the inverse
of the eigenvalues was being summed together. This was done so that increasing the
frequencies of the lower modes would have a larger effect on the objective function than
increasing the frequencies of the higher modes. If the frequencies of all modes are simply
added together, OptiStruct will put more effort into increasing the higher modes than the
lower modes. Note that the DESOBJ statement goes above the first load case since wfreq is
a global response. To duplicate the frequency weighting and summing in OptiStruct 3.5, use
the following approach:
$
DESGLB = 101
$
DESOBJ(MIN) = 11
SUBCASE 1
METHOD = 2
SPC = 1
MODEWEIGHT, 1, 1.0
MODEWEIGHT, 2, 1.0
$
BEGIN BULK
$
DRESP1, 11, wfreq, WFREQ
$
DRESP1, 100, vol, VOLUME
DCONSTR, 101, 100, , 20000.0
$
In OptiStruct 3.5, the combined reciprocal frequency and compliance response (comb)
required a normalization factor in order to properly add frequency values and compliance. The
equivalent setup for OptiStruct 5.0 and higher is shown below.
If no NORM is given, OptiStruct will evaluate the frequencies and compliances in the initial
iteration step to automatically select a NORM factor.
$
DESOBJ(MIN) = 50
DESGLB = 101
$
NORM = 1000.0
$
SUBCASE 1
Description
Format
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SID/XS YS ZS UC YC
Example
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Field Contents
BID PID or DID (Integer > 0; no default). This field can contain the PSHELL
or PCOMP property ID of the elements or the desvar number of any set
of DVGRIDs present in the deck to be optimized for topography. If field
6 contains data, OptiStruct will assume that the BEAD card references
a property, otherwise it assumes that the card references a DESVAR
and its corresponding DVGRIDs.
MW Bead minimum width (Real > 0.0; no default). This parameter controls
the width of the beads in the model [recommended value between 1.5
and 2.5 times the average element width]. See comment 1.
ANG Draw angle in degrees (1.0 < Real < 89.0; no default). This parameter
controls the angle of the sides of the beads [recommended value
between 60 and 75 degrees]. See comment 1.
BF Buffer zone (‘yes’ or ‘no’; default = ‘yes’). This parameter will establish
a buffer zone between elements in the design domain and elements
outside the design domain.
HGT Draw height: (Real > 0.0; no default). This parameter sets the
maximum height of the beads to be drawn. This field is only valid if a
PID is declared in field 2.
norm/XD,YD,ZD Draw direction (‘norm’ in field 7 or Real in all three fields; default =
‘norm’). If field 7 is ‘norm’, the shape variables will be created in the
normal directions of the elements. If all the fields are real, the shape
variable will be created in the direction specified by the xyz vector
defined by fields 7, 8, and 9. The X, Y, and Z values are in the basic
coordinate system. This field is only valid if a PID is declared in field 2.
SKIP Boundary skip (‘both’, ‘bc’, ‘spc’, ‘load’, or ‘none’; default = ‘both’). This
parameter tells OptiStruct to leave certain nodes out of the design
domain. If ‘none’, all nodes attached to elements whose PID was
specified in field 2 will be a part of the shape variables. If ‘bc’ or ‘spc’,
any nodes which have SPC or SPC1 declarations are omitted from the
design domain. If ‘load’, any nodes which have FORCE, FORCE1,
MOMENT, MOMENT1, or SPCD declarations are omitted from the design
domain. If ‘both’, nodes with either ‘spc’ or ‘load’ declarations are
omitted from the design domain. This field is only valid if a PID is
declared in field 2.
FID/XF,YF,ZF Direction of first vector for variable pattern grouping (Real in all three
fields or Integer in field 12; default = blank). These fields define an xyz
vector which determines how grids are grouped into variables. The X,
Y, and Z values are in the global coordinate system. You may put a
grid ID in field 12 to define the first vector. This vector goes from the
anchor point to this grid. If all fields are blank and field 20 is not blank
or zero, OptiStruct gives an error.
AID/XA,YA,ZA Variable grouping pattern anchor point (Real in all three fields or integer
in field 15; default = blank). These fields define a point which
LB Lower bound on variables controlling grid movement (Real < UB, default
= 0.0). This sets the lower bound on grid movement equal to LB*HGT.
UB Upper bound on variables controlling grid movement (Real > LB, default
= 1.0). This sets the upper bound on grid movement equal to UB*HGT.
SID/XS,YS,ZS Direction used to determine second vector for variable pattern grouping
(Real in all three fields or Integer in field 22; default = blank). These
fields define an xyz vector which, when combined with the first vector,
form a plane. The second vector is calculated to lie in that plane and
is perpendicular to the first vector. The second vector is sometimes
required to determine how grids are grouped into variables. The X, Y,
and Z values are in the global coordinate system. You may put a grid
ID in field 22 to define the second vector. This vector goes from the
anchor point to this grid. If all fields are blank and field 20 contains a
value of 20 or higher, OptiStruct gives an error.
Comments
1. The BEAD bulk data entry will no longer be supported for the definition of topography
optimization. All definitions must be provided using the DTPG bulk data entry. HyperMesh
will continue to read BEAD entries, but will convert them into DTPG entries.
MINMETH Integer = 1,2 Specifies the method of minimum member size control.
Default = 2 Method 2 is set as default since it achieves more
discrete solutions for most examples.
Description
The MASSTOH3D command can be used in the I/O Options section to request the output of the
mass matrix to the .h3d file.
Format
MASSTOH3D = option
option <YES, ALL, NO, NONE, YES, ALL, blank: Mass matrix is output to .h3d
blank> file.
Default = ALL
NO, NONE: Mass matrix is not output.
Comments
2. This option is only for use with MotionView's MBD Flexbody utility.
Description
The ROTATION command can be used in the I/O Options or Subcase Information sections to
request the output of rotation information for all subcases or individual subcases respectively.
Format
ROTATION (format, form) = option
option <YES, ALL, YES, ALL, blank: Rotations are output for all nodes.
NO, NONE, SID>
Comments
2. The form argument is only applicable for frequency response analysis. It is ignored for
other analysis types.
3. The form BOTH does not apply to the .frf output files. Results are output to these files
using the rectangular form of complex output when BOTH is the chosen form.
4. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or
FORMAT commands for which the result is available. See Results Output for information on
which results are available in which formats.
6. For optimization, the frequency of output to a given format is controlled by the I/O option
OUTPUT. In previous versions of OptiStruct, a combination of the I/O options FORMAT
and RESULTS were used; this method is still supported, but not recommended as it does
not allow different frequencies for different formats.
Description
The FLSPOUT command can be used in the I/O Options section to control output of modal
participation factors for coupled fluid-structure models.
Format
Default = 1.0e-11
Default = 1.0e-11
Default = 1.0e-11
Default = 1.0e-11
Default =
ABSOLUTE
Comments
MODELMPC –
Description
MODELMPC command can be used in the Subcase Information section while including h3d DMIG
in residual runs. This card converts interior DOFs of the DMIG to exterior DOFs.
Format
MODELMPC = setdof
Examples
MODELMPC = 100
SET,100,GRIDC,
+,10643,T1,10643,T2,10643,T3
setdof < SID > Interior DOF of h3d DMIG to be converted into exterior
DOF. SID refers to the ID of a SET of type GRIDC.
Comments
1. After the conversion with MODELMPC, these DOFs are part of the analysis DOFs and can be
used as connection points, load DOFs, response DOFs during optimization.
INRGAP <YES, NO> PARAM, INRGAP can be used during nonlinear gap analysis
Default = NO to improve the performance for some models. In this
method, an internal super element which includes all of
the gap elements is created automatically, and the
nonlinear iterations are only processed in this super
element. If the degrees-of-freedom associated with gap
elements make up less than 3% of the total degrees-of-
freedom and the gap elements are concentrated in one
area of the model, this approach may be beneficial.
However, a performance gain is not guaranteed.
PRTRENUM <YES, NO, LIST> If YES, prints a warning message when element
Default = YES nodes have been renumbered, including the number
of such elements. (Renumbering is applied to
elements that have node sequence reversed with
respect to the standard numbering as described on
respective bulk data cards).
Description
Format
UPDATE option
Option Description
Example
UPDATE verbose,unique
Comments
Description
The INFILE command is used in the I/O Options section to identify the file containing the bulk
data entries.
Format
INFILE = option
option <file prefix> file prefix: The path to and prefix of the .fem
file containing the bulk data entries.
Default = passed
in from the
command line.
Comments
1. This card is used in the obsolete two-file setup; the one-file or multiple-file setups are
recommended (see The Input File for more information).
2. Prefixes specified on the INFILE card can be arbitrary file prefixes with optional paths
appropriate to the operating system (Windows or UNIX). They may be enclosed in
quotes (double or single quotes can be used), and either forward slash (/) or back slash
(\) characters can be used to separate parts of the path name.
The following rules are used to locate a file referenced on the INFILE card:
When the argument contains the absolute path of the file (if it starts with "/" on UNIX
or a drive letter, such as "D:", on Windows, for example), the file at the given location
is used.
When only the file prefix is given (without the path), the file has to be located in the
same directory as the file containing the INFILE command.
When the argument contains a relative path (../filename or sub/filename, for
example), it is located in the directory relative to the file containing the INFILE
command and is NOT relative to the directory in which the solver was executed, or to
the directory where the main file is located.
3. The total length of information on this card is limited to 200 characters (including the card
name and spaces between arguments). This data can be on a single line or span multiple
continuation lines. See Guidelines for I/O Options and Subcase Information Entries for an
example showing how to enter long file names on multiple lines.
Description
The SET and PSET commands can be used in the I/O Options or Subcase Information section
input deck to define sets of grids, elements, properties, or frequencies.
Format
SET n = i1, i2, …, in Integer sets are used for sets of grids,
elements, modes, and design variables.
SET n = r1, r2, …, rn Real value sets are used for frequencies or
times.
SET n = i1, c1, i2, c2, …, in, cn Sets of Gird/Component pairs are used for
PFMODE data.
Example:
SET 24 = 12, T1, 15, R2, 128, T3
PSET n = PID1, PID2, …, PIDn Property identification numbers are used for
property set definition.
Comments
1. Every SET must have a unique identification number, n, regardless of whether the SET is
defined within a subcase or in the I/O Options section. Also, a SET cannot have the same
ID as a PSET or the bulk data entries SET, SET1, or SURF.
2. From 10.0 onwards, it is recommended to use the SET bulk data entry for set definitions.
Description
The DENSRES command can be used in the I/O Options section to control the frequency of
output of design results (density, shape, or thickness).
Format
DENSRES = frequency
frequency <FIRST, LAST, FIRST: Optimization results are output for the first
FL, ALL, N> iteration only.
Default = ALL
LAST: Optimization results are output for the final
iteration only.
Comments
2. When the DENSRES command is not present, results are output for all iterations.
3. From 10.0 onwards, it is recommended to use the OUTPUT I/O Option entry to control this
output.
Description
The SHRES command can be used in the I/O Options section to control the frequency of
output of the state files (.sh file and the .grid file).
Format
SHRES = frequency
frequency <FIRST, LAST, FIRST: The files are output for the first
FL, ALL, NONE, N> iteration only.
Default = LAST
LAST, blank: The files are output for the final
iteration only.
Comments
1. When a SHRES command is not present, state files are output for the final iteration only.
2. The .grid file is only output for shape, topography, and free-shape optimization.
4. The .grid file output may also be controlled by the GRID keyword on the OUTPUT card.
5. From 10.0 onwards, it is recommended to use the OUTPUT I/O Option entry to control this
output.