HyperWorks 13.0 OptiStruct Reference Guide
HyperWorks is a division of Altair
altairhyperworks.com
Altair Engineering Support Contact Information Web site
www.altairhyperworks.com
Location
Telephone
e-mail
Australia
64.9.413.7981
[email protected]
Brazil
55.11.3884.0414
[email protected]
Canada
416.447.6463
[email protected]
China
86.400.619.6186
[email protected]
France
33.1.4133.0992
[email protected]
Germany
49.7031.6208.22
[email protected]
India
91.80. 6629.4500 1.800.425.0234 (toll free)
[email protected]
Italy
39.800.905.595
[email protected]
Japan
81.3.5396.2881
[email protected]
Korea
82.70.4050.9200
[email protected]
Mexico
55.56.58.68.08
[email protected]
New Zealand
64.9.413.7981
[email protected]
North America
248.614.2425
[email protected]
Scandinavia
46.46.460.2828
[email protected]
United Kingdom
01926.468.600
[email protected]
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 Copyright© Altair Engineering Inc. All Rights Reserved for: HyperMesh® 1990-2014; HyperCrash® 2001-2014; OptiStruct® 1996-2014; RADIOSS®1986-2014; HyperView®1999-2014; HyperView Player® 2001-2014; HyperStudy® 1999-2014; HyperGraph®1995-2014; MotionView® 1993-2014; MotionSolve® 20022014; HyperForm® 1998-2014; HyperXtrude® 1999-2014; Process Manager™ 2003-2014; Templex™ 1990-2014; TextView™ 1996-2014; MediaView™ 1999-2014; TableView™ 2013-2014; BatchMesher™ 2003-2014; HyperMath® 2007-2014; Manufacturing Solutions™ 2005-2014; HyperWeld® 2009-2014; HyperMold® 2009-2014; solidThinking® 1993-2014; solidThinking Inspire® 2009-2014; solidThinking Evolve®™ 1993-2014; Durability Director™ 2009-2014; Suspension Director™ 2009-2014; AcuSolve® 1997-2014; AcuConsole® 2006-2014; SimLab®™2004-2014 and Virtual Wind Tunnel™ 2012-2014. 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. Copyright notice does not imply publication
OptiStruct 13.0 Reference Guide
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
i
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Reference Guide Input Data Output Data Legacy Data
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
1
Input Data I/O Options Section Subcase Information Section Bulk Data Section Element Quality Check Material Property Check
2
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
The Bulk Data Input File The input file in OptiStruct is composed of three distinct sections: The I/O Options Section The Subcase Information Section The Bulk Data Section The I/O Options Section controls the overall running of the analysis or optimization. It controls the type, format, and frequency of the output, the type of run (check, analysis, super element generation, optimization or optimization restart), and the location and names of input, output, and scratch files. 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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
3
These sections can be arranged in either a one-file setup or a multi-file setup (there is also an obsolete two-file setup that is no longer recommended).
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. input.fem file
sub2.inc
$ Subcase 1 SPC = 1 Load = 2 $ INCLUDE sub2.inc $ BEGIN BULK $
Subcase 2 SPC = 1 Load = 3
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 $
4
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Two-File Setup This setup is obsolete; the one-file or multiple-file setups are recommended. 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. Notes: The format of the input sections in OptiStruct are similar to those of the Nastran format. File names specified on INCLUDE and other cards (RESTART, EIGVNAME, LOADLIB, OUTFILE, TMPDIR, ASSIGN) 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 pathname. The solver uses the following rules to locate a file name on the INCLUDE cards: 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 name is given (without the path), the file has to be located in the same directory as the file containing the INCLUDE statement. 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 INCLUDE statement and is NOT relative to the directory in which the solver was executed, or to the directory where the main file is located.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
5
Compressed input 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.
6
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Guidelines for I/O Options and Subcase Information Entries 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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
7
Continuation lines are marked with a trailing comma character in the preceding line. Numeric entries must start with a digit, ‘+’, or ‘-’. Integer entries may not contain decimal points or exponent parts, and must fit in the range of values allowed for INTEGER*4 (usually –2**31
Examples
The following three lines are equivalent: DISPLACEMENT (form) = option disp FORM option displa ,, form , oPTIOn
The following is a card with multiple continuation lines: XYPLOT, XYPEAK, VELO, PSDF / 3(T2), 6(T2), 8(T2), 10(T2), 20(T2)
The following is a path split across several lines: INCLUDE "path/ /split into multiple / lines /filename.txt " 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.
8
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Guidelines for Bulk Data Entries 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 eight characters (shown below).
Large Field 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 '*'.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
9
Large field free format and short field free format are available, but there is no limit on the length of entries, and all floating numbers are read and stored with full precision (64-bit REAL*8) in either case. The only difference between large and short free format is that the latter allows for 8 data fields in each line (in positions 2 – 9), while the former allows for 4 data fields per line (similar to the large field fixed format detailed above). 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.
10
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
No entry can contain blanks within the data. Character entries (labels) must start with a letter. Numeric entries must start with a digit, ‘+’ or ‘-‘. Integer entries may not contain a decimal point or an exponent part, and must fit in the range of values allowed for INTEGER*4 (usually –2**31
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
11
Replication of GRID data 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 ==. Incrementing a value from the previous entry is indicated by coding *x or *(x), where x is the value of the increment. “x” should be a real number for real fields or an integer for integer fields. The parentheses will be ignored and removed. Only the fields for ID, CP, X, Y, Z, and CD can be incremented. The PS data cannot be incremented. Replication data can follow other replication data. Entered entries: GRID,101,17,1.0,10.5,,17,3456 GRID,*1,=,*(0.2),== GRID,*100,,=,=,*10.0,== GRID,20,17,== Generated entries: GRID
101
17
1.0
10.5
17
3456
GRID
102
17
1.2
10.5
17
3456
GRID
202
1.2
10.5
10.0
17
3456
GRID
20
1.2
10.5
10.0
17
3456
17
Removal of duplicate entries Removal of duplicate entries is a limited to GRID, CORD1R, CORD1C, CORD1S, CORD2R, CORD2C, CORD2S, CORD3R, and CORD4R entries only. To be considered duplicates, the GRID ID, CP, CD, and PS fields must be the same. The GRID coordinates should be the same within the setting determined by PARAM,DUPTOL. For the coordinate information to be considered duplicate, the CID and GID must be the same and the vector components and axis locations must be the same within the setting determined by PARAM,DUPTOL. The removal of duplicated GRID data is performed after any GRID data is generated using the GRID replication feature. For all other cards which require a unique ID, it is an error if any given ID appears more than once. However, to facilitate application of changes resulting from optimization, it is possible to redefine content of some cards using a separate file defined with
12
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
ASSIGN,UPDATE.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
13
Solution Sequences - Data Selectors (Table)
Key: R
Required Data Selector.
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.
A
Exactly one selector marked A is required. 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.
14
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Summary of Defaults for I/O Options Output Format Controls
Card
When card is not present
When card is present, but no argument is given
FORMAT
HM & H3D*
error
OUTPUT
no effect
no effect
*The OptiStruct Configuration File may be used to change the default settings.
Run Controls
Card
When card is not present
When card is present, but no argument is given
CHECK
no effect
active (has no arguments)
CMSMETH
no effect
no effect
RESTART
no effect
.sh
SYSSETTING
no effect
no effect
@HyperForm
no effect
active (has no arguments)
File Names, Headers, and Locations
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
15
Card
When card is not present
When card is present, but no argument is given
ASSIGN
N/A
error
EIGVNAME
OUTFILE is used
error
INCLUDE
N/A
error
LOADLIB
N/A
error
OUTFILE
prefix of filename
error
SUBTITLE
N/A
blank
TITLE
N/A
blank
TMPDIR
./ or .\
error
Card
When card is not present
When card is present, but no argument is given
ACCELERATION
NONE
ALL
AUTOSPC
NO
YES
CONTF
NONE
ALL
CSTRAIN
NONE
ALL
CSTRESS
NONE
ALL
DAMAGE
NONE
ALL
DISPLACEMENT
ALL †
ALL
EDE
NONE
ALL
Analysis Output
16
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Card
When card is not present
When card is present, but no argument is given
EKE
NONE
ALL
ELFORCE
See FORCE
ELSTRESS
See STRESS
ENERGY
NONE
ALL
ERP
NONE
ALL
ESE
NONE
ALL
FLUX
NONE
ALL
FORCE
NONE
ALL
FORMAT
no effect
FLX
GPFORCE
NONE
ALL
GPKE
NONE
ALL
GPSTRESS
NONE
ALL
GSTRESS
See GPSTRESS
LIFE
NONE
ALL
MBFORCE
no effect
ALL
MECHCHECK
no effect
N/A
MODALDE
NONE
ALL
MODALKE
NONE
ALL
MODALSE
NONE
ALL
MPCFORCE
NONE
ALL
OLOAD
NONE
ALL
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
17
18
Card
When card is not present
When card is present, but no argument is given
PFGRID
NONE
error
PFMODE
NONE
error
PFPANEL
NONE
error
PFPATH
NONE
error
POWERFLOW
NONE
ALL
PRESSURE
ALL †
ALL
PRETBOLT
NO
YES
REQUEST
NONE
error (has no arguments)
SACCELERATION
NONE
ALL
SDISPLACEMENT
NONE
ALL
SINTENS
NONE
ALL
SPCFORCE
NONE
ALL
SPL
NONE
ALL
SPOWER
NONE
ALL
STRAIN
NONE
ALL
STRESS
ALL ‡
ALL
SVELOCITY
NONE
ALL
TCURVE
N/A
blank
THERMAL
NONE
ALL
THIN
NONE
ALL
UNITS
NONE
error (has no arguments)
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Card
When card is not present
When card is present, but no argument is given
VELOCITY
NONE
ALL
XTITLE
N/A
blank
XYPEAK
NONE
error
XYPLOT
NONE
error
XYPUNCH
NONE
error
YTITLE
N/A
blank
† Except for frequency response subcases, where the default is NONE. ‡ Except for frequency response and transient subcases, where the default is NONE.
Optimization Output
Card
When card is not present
When card is present, but no argument is given
DENSITY
ALL
ALL
DESGLB
no effect
error
DESHIS
ALL
ALL
DSA
no effect
error
HISOUT
15
15
PROPERTY
FILE
FILE
RESPRINT
no effect
no effect
RESULTS
FL
FL
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
19
Card
When card is not present
When card is present, but no argument is given
SENSITIVITY
NONE
NOSTRESS
SENSOUT
FL
FL
SHAPE
ALL
ALL
THICKNESS
ALL
ALL
Other Output Controllers
20
Card
When card is not present
When card is present, but no argument is given
DMIGNAME
AX
AX
ECHO
no effect
active
ECHOON
no effect
active (has no arguments)
ECHOOFF
no effect
active (has no arguments)
MODEL
ALL
ALL
MSGLMT
no effect
error
OFREQUENCY
ALL
ALL
OMODES
ALL
ALL
OTIME
ALL
ALL
SCREEN
NONE
OUT
TTERM
NONE
REAL
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Random Response
Card
When card is not present
When card is present, but no argument is given
RCROSS
NONE
ERROR
Card
When card is not present
When card is present, but no argument is given
DGLOBAL
NONE
ERROR
Card
When card is not present
When card is present, but no argument is given
HYBDAMP
NONE
ERROR
RADSND
no effect
ERROR
Optimization
FE Analysis
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
21
I/O Options Section
22
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
@HYPERFORM I/O Options Entry @HyperForm - One-step Stamping Simulation Run 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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
23
ACCELERATION I/O Options and Subcase Information Entry ACCELERATION - Output Request 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
Argument
Options
Description
sorting
This argument only applies to the PUNCH format (.pch file) or the OUTPUT2 format (.op2 file) output for normal modes, frequency response, and transient subcases. It will be ignored without warning if used elsewhere.
Default = blank
format
SORT1:
Results for each frequency/ timestep are grouped together.
SORT2:
Results for each grid/element are grouped together (See comment 8).
blank:
For frequency response analysis, if no grid SET is specified, SORT1 is used, otherwise, SORT2 is used; for transient analysis, SORT2 is used.
H3D: Default = blank HG:
24
Results are output in HyperMesh binary format (.res file). Results are output in Hyper3D format (.h3d file). Results are output in HyperGraph presentation format (_freq.mvw file and _tran.mvw file) – see OUTPUT keywords HGFREQ and HGTRANS.
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument
Options
Description OPTI:
Results are output in OptiStruct results format (.dispfile).
PUNCH:
Results are output in Nastran punch results format (.pch file).
OP2:
Results are output in Nastran output2 format (.op2 file) (see comment 11).
PLOT:
Results are output in Nastran output2 format (.op2 file) when PARAM, POST is defined in the bulk data section. If PARAM, POST is not defined in the bulk data section, this format allows the form for complex results to be defined for XYPUNCH output without having other output.
form
blank:
Results are output in all active formats for which the result is available.
COMPLEX (HM only), blank:
Provides a combined magnitude/ phase form of complex output to the .res file for the HM output format.
Default (HM only) = COMPLEX REAL or IMAG: Default (all other formats) = REAL PHASE:
Provides rectangular format (real and imaginary) of complex output (See comment 9). Provides polar format (magnitude and phase) of complex output. Phase output is in degrees (See comment 9).
BOTH (HM only): Provides both polar and rectangular formats of complex output.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
25
Argument
Options
Description
rotations
ROTA:
Requests output of rotational acceleration results (in addition to translational acceleration results).
NOROTA:
Rotational acceleration results are not output.
PSDF:
Requests PSD and RMS results from random response analysis to be output.
Default = NOROTA
random
No default
Only valid for the H3D format. The "RMS over Frequencies" output is at the end of the Random results. RMS:
Requests only the “RMS over Frequencies” result from random response analysis to be output. Valid only for the H3D format.
peakoutput
PEAKOUT:
If PEAKOUT is present, only the filtered frequencies from the PEAKOUT card will be considered for this output.
YES, ALL, blank:
Acceleration is output for all nodes.
Default = ALL
NO, NONE:
Acceleration is not output.
SID:
If a set ID is given, acceleration is output only for nodes listed in that set.
Default = blank
option
26
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Comments 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 ( (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).
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
27
ASSIGN I/O Options and Subcase Information Entry ASSIGN – Input Definition Description The ASSIGN command can be used in the I/O Options section to identify external files and their contents. Format ASSIGN, type, option1, option2
Type
Option1
Option 2
Description
AKUSMOD
filename
N/A
Identifies an external file from which to read the AKUSMOD fluid-structure coupling matrix. If this is not defined, it is presumed that the AKUSMOD coupling matrix is to be found in the same directory as the solver input file and is given the file name, ftn.70. Use of the AKUSMOD fluid-structure coupling matrix requires the presence of PARAM,AKUSMOD,YES.
ENGINE
SUBCASE ID
filename
Identifies an external file from which to read modification commands to be applied on the intermediate RADIOSS Engine file translated in the NLGEOM, IMPDYN and EXPDYN solutions. SUBCASE ID=0 means all NLGEOM, IMPDYN and EXPDYN subcases. 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. While running an AVL/EXCITE analysis, a .INP4 file is generated that contains the modal participation factors. The .INP4 file can be used along with the original flex h3d file to recover stresses, strains, displacements, velocities, and accelerations from a
28
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Type
Option1
Option 2
Description dynamic analysis run. The SUBCASE ID is used to specify which SUBCASE the modal participation factors should be used for.
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.
H3DCAA
Load ID
filename
Identifies an external file that contains information necessary for Computational Aero-Acoustic (CAA) analysis. The information in this external file is then used to conduct frequency response analyses. This file (.h3d format) is currently generated by AcuSolve and includes pressure values from Computational Fluid Dynamics (CFD) Analysis at each loading frequency. The specified “LoadID” can be referenced by CAALOAD data (CAAID field) for the application of load in a model.
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
29
Type
Option1
Option 2
Description
MBDINP
SUBCASE ID
filename
Identifies an external file from which to read the modal participation factors calculated by MotionSolve for transient analysis. While running MotionSolve, an .mrf file is generated that contains the modal participation factors. The .mrf file can be used along with the original flex h3d file to recover stresses, strains, displacements, velocities, and accelerations during a transient analysis run. The SUBCASE ID is used to specify which SUBCASE the modal participation factors should be used for.
MMO
Model Name
filename
Identifies an external file to be included in a MultiModel Optimization (MMO) run. “Model Name” is a user-defined label for the model, which can be used to qualify model-specific responses referenced on the DRESPM continuation lines of the DRESP2/ DRESP3 entries.
PUNCH
filename
N/A
Identifies an external file as the location to write DMIG data in PUNCH format.
STARTER
SUBCASE ID
filename
Identifies an external file from which to read modification commands to be applied on the intermediate RADIOSS Starter file translated in the NLGEOM, IMPDYN and EXPDYN solutions. SUBCASE ID=0 means all NLGEOM, IMPDYN and EXPDYN subcases. See comment 1.
SIMPINP
30
SUBCASE
filename
Identifies an external .unv file generated while running a multi-body dynamic analysis in SIMPACK. The resulting CMS flexbody modal participation factors in the .unv file can be used by OptiStruct to recover the dynamic displacements, velocities,
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Type
Option1
Option 2
Description accelerations, stresses and strains. The SUBCASE ID is used to specify which SUBCASE the modal participation factors should be used for.
UPDATE
filename
N/A
Identifies an external file from which to read the updated cards after an optimization run. Currently, the following cards are supported: GRID MAT1, MAT2, MAT3, MAT4, MAT5, MAT8, MAT9, MAT10 PSHELL, PSOLID, PBAR, PBEAM, PELAS, PVISC, PDAMP, PBARL, PBEAML, PMASS, PROD, PBUSH, PBUSH1D, PACABS PAABSF, PWELD, PCOMPP, PSHEAR, PTUBE CTRIA3, CQUAD4, CTRIA6, CQUAD8 CONM2
Examples ASSIGN, PUNCH, C:\CMS\h3ddmig.pch ASSIGN, H3DDMIG, AX, C:\CMS\h3ddmig.h3d 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 Usage:
Inserts content between keywords /INSERT and /ENDINS to the intermediate RADIOSS Block deck at line number LINENUM.
Syntax:
/INSERT,LINENUM Content to be inserted /ENDINS
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
31
replace Usage:
Uses content between keywords /REPLACE and /ENDREP to replace the content in the intermediate RADIOSS Block deck between line numbers LINENUM1 and LINENUM2.
Syntax:
/REPLACE,LINENUM1, LIMENUM2 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.
32
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
AUTOSPC I/O Options Entry AUTOSPC - Automatically Constrains Stiffness Singularities Description The AUTOSPC command requests that stiffness singularities and near singularities be constrained automatically with single point constraints. Format
Argument
Description
PRINT
Enables the printout of a summary table of singularities. (Default)
NOPRINT
Disables the printout of a summary table of singularities.
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 1.
YES is the default.
2.
Replaces parameters PARAM,AUTOSPC and PARAM,PRGPST.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
33
CDSMETH I/O Options Entry CDSMETH – Run Control 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
Argument
Option
Description
CDSID
ID of CDSMETH in bulk data section.
Default = NONE
Comments 1.
If CDSMETH is specified, only one subcase is allowed. The data corresponding to component dynamic synthesis will be stored in an H3D file with the name, filename_CDS.h3d.
2.
The subcase must be a modal frequency response subcase, except it does not require a DLOAD card for load specification.
34
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
CHECK I/O Options Entry CHECK - Run Control 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 1.
Perform model check only.
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
35
CMDE I/O Options Entry CMDE - Output Request 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
Argument
Options
Description
format
H3D:
Results are output in Hyper3D format (.h3d file).
blank:
Results are output in all active formats for which the result is available.
Default = blank
thresh
Specifies an absolute threshold under which results should not be output.
No default
rthresh
Specifies a relative threshold under which results should not be output. This value is relative to the corresponding total modal energy.
No default
topn
Specifies that only the top N values should be output.
No default
36
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument
Options
type
The average of the energy is output.
Default = AVERAGE
AMPLITUDE:
The amplitude of the energy is output.
PEAK:
The peak energy is output. This is the sum of AVERAGE and AMPLITUDE.
mset
Description
ALL: Default = ALL
option
Default = ALL
Modal energy is output for all modes.
SID:
If a set ID is given, modal energy is output only for modes listed in that set.
TOTAL:
Only the total energy is output.
YES, ALL, blank: Modal energy is output.
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
37
CMKE I/O Options Entry CMKE - Output Request 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
Argument
Options
Description
format
H3D:
Results are output in Hyper3D format (.h3d file).
blank:
Results are output in all active formats for which the result is available.
Default = blank
thresh
Specifies an absolute threshold under which results should not be output.
No default
rthresh
Specifies a relative threshold under which results should not be output. This value is relative to the corresponding total modal energy.
No default
topn
Specifies that only the top N values should be output.
No default
38
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument
Options
Description
type
AVERAGE:
The average of the energy is output.
Default = AVERAGE
AMPLITUDE:
The amplitude of the energy is output.
PEAK:
The peak energy is output. This is the sum of AVERAGE and AMPLITUDE.
mset
ALL: Default = ALL
option
Modal energy is output for all modes.
SID:
If a set ID is given, modal energy is output only for modes listed in that set.
TOTAL:
Only the total energy is output.
YES, ALL, blank: Modal energy is output.
Default = ALL
NO, NONE:
Modal energy is not output.
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
39
CMSE I/O Options Entry CMSE - Output Request 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
Argument
Options
Description
format
H3D:
Results are output in Hyper3D format (.h3d file).
blank:
Results are output in all active formats for which the result is available.
Default = blank
thresh
Specifies an absolute threshold under which results should not be output.
No default
rthresh
Specifies a relative threshold under which results should not be output. This value is relative to the corresponding total modal energy.
No default
topn
Specifies that only the top N values should be output.
No default
40
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument
Options
Description
type
AVERAGE:
The average of the energy is output.
Default = AVERAGE
AMPLITUDE:
The amplitude of the energy is output.
PEAK:
The peak energy is output. This is the sum of AVERAGE and AMPLITUDE.
ALL:
Modal energy is output for all modes.
SID:
If a set ID is given, modal energy is output only for modes listed in that set.
TOTAL:
Only the total energy is output.
YES, ALL, blank:
Modal energy is output.
NO, NONE:
Modal energy is not output.
mset
Default = ALL
option
Default = ALL
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
41
5.
42
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.
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
CONTF I/O Options and Subcase Information Entry CONTF – Output Request for Contact Results 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
Type
Options
Description
format
H3D:
Results are output in Hyper3D format (.h3d file). See below for type.
OPTI:
The total contact force results are output to the .cntf file.
blank:
Results are output in all active formats for which the result is available.
ALL:
All available contact results types are output.
FORCE:
Contact force results are output.
PCONT:
Pressure-type contact results are output: pressure, open-closed status, contact gap opening and penetration (see comment 2).
FRICT:
Friction-related results are output: frictional traction, sliding distance, and stick-slip status (see comment 2).
YES, ALL,
Contact results are output for all grid
Default = blank
type
Default = ALL
option
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
43
Type
Options
Description
NO, NONE, SID>
blank:
points.
Default = ALL
NO, NONE:
Contact results are not output.
SID:
If a set ID is given, contact results are output only for grid points listed in that set.
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.
44
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
CSTRAIN I/O Options and Subcase Information Entry CSTRAIN - Output Request 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
Argument
Options
Description
format
HM:
Results are output in HyperMesh results format (.res file).
H3D:
Results are output in Hyper3D format (.h3d file).
OPTI:
Results are output in OptiStruct results format (.cstr file).
PUNCH:
Results are output in Nastran punch results format (.pch file).
OP2:
Results are output in Nastran output2 format (.op2 file) (see comment 10).
PLOT:
Results are output in Nastran output2 format (.op2 file) when PARAM, POST is defined in the bulk data section.
blank:
Results are output in all active formats, for which the result is available.
Default = blank
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
45
Argument
Options
Description
type
ALL, blank:
All strain results are output.
PRINC:
Only principal strain results are output.
MECH:
Output Mechanical strain (in addition to total strain). This output is only available for H3D format.
THER:
Output Thermal strain (in addition to total strain). This output is only available for H3D format.
YES, ALL, blank:
Results are output for all elements.
Default = YES
NO, NONE:
Results are not output.
SID:
If a set ID is given, results are output only for elements listed in that set.
PSID:
If a property set ID is given, results for the elements referencing properties listed in the property set are output.
Default = ALL
extras
No default
option
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.
46
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
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 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).
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
47
CSTRESS I/O Options and Subcase Information Entry CSTRESS - Output Request 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
Argument
Options
Description
format
HM:
Results are output in HyperMesh results format (.res file).
Default = blank
H3D:
Results are output in Hyper3D format (.h3d file).
OPTI:
Results are output in OptiStruct results format (.cstr file).
PUNCH:
Results are output in Nastran punch results format (.pch file).
OP2:
Results are output in Nastran output2 format (.op2 file) (see comment 10).
blank:
Results are output in all active formats, for which the result is available.
type
Default = ALL
48
ALL, blank:
All stress results are output.
PRINC:
Only principal stress results are output.
FI:
Only failure index results are output. Failure Index results are not available in the .pch and .op2 files.
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument
Options
Description
Option
YES, ALL, blank:
Results are output for all elements.
Default = YES
NO, NONE:
Results are not output.
SID:
If a set ID is given, results are output only for elements listed in that set.
PSID:
If a property set ID is given, results for the elements referencing properties listed in the property set are 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
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
49
format (.op2 file).
50
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
DAMAGE I/O Options and Subcase Information Entry DAMAGE – Output Request 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
Argument
Options
Description
format
H3D:
Results are output in Hyper3D format (.h3d file).
OPTI:
Results are output in OptiStruct results format (.fat file).
blank:
Results are output in all active formats for which the result is available.
SUB:
Only the total damage from the fatigue subcase is output.
LOAD:
Damage contribution from each static subcase and total damage from the fatigue subcases are output.
EVENT:
Damage contribution from each FATEVNT and total damage from fatigue subcases are output.
ALL:
Damage contribution from each FATEVNT, damage contribution from each static subcase and total damage from fatigue subcases are all output.
Default = blank
type
Default = SUB
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
51
Argument
Options
Description
option
YES, ALL, blank:
Results are output for all elements.
NO, NONE:
Results are not output.
SID:
If a set ID is specified, results are output only for elements listed in that set.
Default = ALL
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.
52
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
DENSITY I/O Options and Subcase Information Entry DENSITY - Output Request 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
Argument
Options
Description
format
HM:
Results are output in HyperMesh results format (.res file).
H3D:
Results are output in Hyper3D format (.h3d file).
OPTI:
Results are output in OptiStruct results format (.dens file).
PUNCH:
Results are output in Nastran punch results format (.pch file).
OP2:
Results are output in Nastran output2 format (.op2 file) (see comment 6).
PLOT:
Results are output in Nastran output2 format (.op2 file) when PARAM, POST is defined in the bulk data section (see comment 6).
blank:
Results are output in all active formats for which the result is available.
ALL:
Results are output in all simulations.
DES, blank:
Results are only output in the design history simulations.
Default = blank
type
Default = DES
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
53
Argument
Options
Description
option
YES, ALL, blank:
Results are output
Default = YES
NO, NONE:
Results are not output.
Comments 1.
When the DENSITY command is not present, density results are output.
2.
Density results are only available for topology optimizations.
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.
54
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
DESGLB I/O Options Entry DESGLB – Constraint Selection 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
Argument
Options
Description
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.
3.
This entry is represented as an optimizationconstraint in HyperMesh.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
55
DESHIS I/O Options Entry DESHIS - Output Control 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
Argument
Options
Description
option
YES, ALL, blank: Default = YES
NO:
.hgdata file is created. .hgdata is not created.
Comments 1.
56
When the DESHIS command is not present, the .hgdata file is created.
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
DGLOBAL I/O Options Entry DGLOBAL - Input Definition Description The DGLOBAL command can be used in the I/O Options section to activate the Global Search Option (GSO). Format DGLOBAL = n
Argument
Options
Description
n
(Integer > 0)
Identification of a DGLOBAL bulk data entry.
No default Comments 1.
This command must reference a DGLOBAL bulk data entry to run GSO.
2.
This data can exist only once in the I/O section.
3.
This command activates a global search algorithm to run an optimization of user-defined design variables from multiple starting points.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
57
DISPLACEMENT I/O Options and Subcase Information Entry DISPLACEMENT - Output Request 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
Argument
Options
Description
sorting
This argument only applies to the PUNCH format (.pch file) or the OUTPUT2 format (.op2 file) output for normal modes, frequency response, and transient subcases. It will be ignored without warning if used elsewhere.
Default = blank
format
58
SORT1:
Results for each frequency/timestep are grouped together.
SORT2:
Results for each grid/element are grouped together (See comment 9).
blank:
For frequency response analysis, if no grid SET is specified, SORT1 is used, otherwise, SORT2 is used; for transient analysis, SORT2 is used.
HM:
Results are output in HyperMesh results format (.res file).
H3D:
Results are output in Hyper3D format (.h3d file).
Default = blank
OPTI:
Results are output in OptiStruct results format (.disp file).
PUNCH:
Results are output in Nastran punch results format (.pch file).
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument
Options
Description OP2:
Results are output in Nastran output2 format (.op2 file) (see comment 12).
PATRAN:
Results are output in Patran format (multiple files).
HG:
Results are output in HyperGraph presentation format (_freq.mvw file and _tran.mvw file) – see OUTPUT keywords HGFREQ and HGTRANS.
APATRAN:
Results are output in Alternative Patran format (multiple files).
PLOT:
Results are output in Nastran output2 format (.op2 file) when PARAM, POST is defined in the bulk data section. If PARAM, POST is not defined in the bulk data section, this format allows the form for complex results to be defined for XYPUNCH output without having other output.
blank:
form
Results are output in all active formats for which the result is available.
COMPLEX (HM only), blank:
Provides a combined magnitude/phase form of complex output to the .res file for the HM output format.
Default (HM only) = COMPLEX
REAL or IMAG:
Provides rectangular format (real and imaginary) of complex output (See comment 10).
Default (all other formats) = REAL PHASE:
Provides polar format (magnitude and phase) of complex output. Phase output is in degrees (See comment 10).
BOTH (HM only): Provides both polar and rectangular formats of complex output.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
59
Argument
Options
Description
rotations
ROTA:
Rotational displacement results are output. Only works with H3D and HM output streams. Rotations are always output with translations for other output streams.
NOROTA:
Rotational displacement results are not output. Only works with H3D and HM output streams. Rotations are always output with translations for other output streams.
PSDF:
Requests PSD and RMS results from random response analysis to be output.
Default = NOROTA
random
No default
Only valid for the H3D format. The "RMS over Frequencies" output is at the end of the Random results. RMS:
Requests only the “RMS over Frequencies” result from random response analysis to be output. Valid only for the H3D format.
peakoutput
PEAKOUT:
If PEAKOUT is present, only the filtered frequencies from the PEAKOUT card will be considered for this output.
MODAL:
If MODAL is present, displacements of the structural modes and residual vectors are output to the PUNCH and OUTPUT2 files for modal frequency response and transient analysis.
Default = Blank
modal
Default = Blank
60
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument
Options
complex eigenvalue analysis
option
Description UNSTABLE:
If UNSTABLE is present, the displacement results from the unstable modes (only) of a complex eigenvalue analysis are output.
Blank:
Displacement results are output for all modes by default (See comment 1).
Default = Blank
YES, ALL, blank: Displacement is output for all grids.
Default = ALL
NO, NONE:
Displacement is not output.
SID:
If a set ID is given, displacement is output only for grids listed in that set.
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.
7.
Rotation results are output in radians.
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
61
9.
In general, HyperView does not recognize the SORT2 format for results from the .op2 file. When results are output only in SORT2 format ( (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.
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. 11. The four-letter abbreviation DISP is interchangeable with DISPLACEMENT. 12. format=OUTPUT2 can also be used to request results to be output in the Nastran output2 format (.op2 file).
62
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
DMIGNAME I/O Options Entry DMIGNAME - Reduced Matrix Name Definition 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
Argument
Options
Description
mtxname
The name given to the reduced matrices written to an external data file, when PARAM, EXTOUT is present in the bulk data section.
Default = AX
If PARAM, EXTOUT, DMIGPCH is used, then the file outfile_mtxname.pch is created. If PARAM,EXTOUT, DMIGBIN is used, then the file outfile_mtxname.dmg is created. Both files contain the matrices: KAmtxname - reduced stiffness matrix MAmtxname - reduced mass matrix Pmtxname - reduced loading matrix Note: The reduced mass matrix is only output if an eigenvalue subcase is present in the input file and the reduced loading matrix is only output if a linear static subcase is present in the input file.
Comments 1.
When a DMIGNAME command is not present, AX is used for mtxname.
2.
Only one occurrence of DMIGNAME is permitted.
3.
DMIGNAME must appear before the first subcase.
4.
See Direct Matrix Approach in the User's Guide for more detailed usage information.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
63
DSA I/O Options and Subcase Information Entry DSA - Design Sensitivity Analysis Output Request 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
Argument
Options
Description
TYPE
Default = DISP
PEAKOUT
Default = blank
PROPERTY
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.
If the “PROPERTY” flag is present: This indicates that design sensitivities represent the change in design response due to a change in design properties (instead of design variables). If the “PROPERTY” flag is not present: This indicates that design sensitivities represent the change in design response due to a change in design variables.
64
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument
Options
SID
Description SID refers to the ID of a SET of type GRIDC.
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.
Sensitivities output from a complete Optimization setup (User-defined/specified responses via DRESP1, DRESP2, DRESP3)
Output
Sensitivities requested via the DSA output request
OUTPUT, H3DSENS, USER
Yes
Yes
OUTPUT, H3DSENS, NOUSER
Yes
No
(responses are automatically defined)
Design variables and their corresponding design properties must be defined in the input deck if sensitivity output is requested through the DSA entry.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
65
ECHO/ECHOON/ECHOOFF I/O Options Entry ECHO - Output Control ECHOON - Output Control ECHOOFF - Output Control 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)
Argument Options
Description
option1
SHORT:
Only entries having less than 20 instances are echoed to the .out file.
PUNCH:
Writes interpreted echo of all bulk data entries to the .echo file.
{cardname}:
Only bulk data entries with the given {cardname} are echoed to the .out file.
Default = blank
66
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument Options
Option2
Description
EXCEPT {cardname}:
Only bulk data entries with the given {cardname} are not echoed.
blank:
Writes interpreted forms of all subcase information and bulk data entries to the .out file.
MAT, PROP, ELEM:
Adds all cards of the specified class to the list for ECHO.
PARSED:
Bulk data entries are converted to free format (comma separated) before echoing.
blank:
Bulk data entries are echoed verbatim.
Default = blank
Comments 1.
When an ECHO command is not present, no input information is echoed.
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
67
6.
The interpreted echo is always printed using a fixed field format (8 character fields) except GRID and DMIG cards, which are printed using free format (comma separated fields) with 10 decimal digits accuracy. Note that the use of IDs larger than 99,999,999 is allowed, but ECHO will not be usable in these cases as such IDs cannot be printed in fixed format. 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.
68
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
EDE I/O Options and Subcase Information Entry EDE - Output Request 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
Argument
Option
Description
format
HM:
Results are output in HyperMesh results format (.res file).
H3D:
Results are output in Hyper3D format (.h3d file).
PUNCH:
Results are output in Nastran punch results format (.pch file).
OP2:
Results are output in Nastran output2 format (.op2 file) (see comment 8).
PLOT:
Results are output in Nastran output2 format (.op2 file) when PARAM, POST is defined in the bulk data section.
blank:
Results are output in all active formats for which the result is available.
AVERAGE:
In frequency response analysis average energy is output.
AMPLITUDE:
In frequency response analysis the amplitude of energy is output.
PEAK:
In frequency response analysis the peak energy is output. This is the sum of AVERAGE and AMPLITUDE.
Default = blank
type
Default = AVERAGE see Comment 7
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
69
Argument
Option
Description
dmig
DMIG:
Results are provided for external superelements in the .out file.
NODMIG:
Results are not provided for external superelements in the .out file.
YES, ALL, blank:
Element damping energy and damping energy density are output for all elements.
NO, NONE:
Element damping energy and damping energy density are not output.
SID:
If a set ID is given, element damping energy and damping energy density are output only for elements listed in that set.
Default = NODMIG
option
Default = ALL
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.
6.
Type only applies to frequency response analysis.
7.
There are three ways to calculate the Element Damping Energy in Frequency Response Analysis. They are listed as follows:
70
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Type of Output
Formula
Average
Amplitude
Peak Where, E = Elemental Energy {Ur } = Displacement (Real Part) {Ui } = Displacement (Imaginary Part) [Be ] = Elemental Damping 8.
format=OUTPUT2 can also be used to request results to be output in the Nastran output2 format (.op2 file).
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
71
EIGVNAME I/O Options Entry EIGVNAME - Filename Prefix Definition 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. The external eigenvalue data file name is of the form _#.eigv, where is defined here, # is the integer argument of the EIGVSAVE subcase information entry or one of the integer arguments of the EIGVRETRIEVE subcase information entry.
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.
2.
Only one occurrence of EIGVNAME is permitted.
3.
EIGVNAME must appear before the first subcase.
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. OptiStruct uses the following rules for the EIGVNAME card: 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.
72
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
When only the file prefix is given (without the path), .eigv files will be created in the current directory, meaning the directory from which OptiStruct 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), .eigv files will be created in a directory relative to where OptiStruct is executed and NOT relative to the directory where the input file is located.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
73
EKE I/O Options and Subcase Information Entry EKE - Output Request 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
Argument
Option
Description
format
HM:
Results are output in HyperMesh results format (.res file).
H3D:
Results are output in Hyper3D format (.h3d file).
PUNCH:
Results are output in Nastran punch results format (.pch file).
OP2:
Results are output in Nastran output2 format (.op2 file) (see comment 8).
PLOT:
Results are output in Nastran output2 format (.op2 file) when PARAM, POST is defined in the bulk data section.
blank:
Results are output in all active formats for which the result is available.
AVERAGE:
In frequency response analysis average energy is output.
Default = AVERAGE
AMPLITUDE:
In frequency response analysis the amplitude of energy is output.
PEAK:
In frequency response analysis the peak energy is output. This is the sum of AVERAGE and AMPLITUDE.
Default = blank
type
see Comment 7
74
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument
Option
Description
dmig
DMIG:
Results are provided for external superelements in the .out file.
Default = NODMIG
NODMIG:
Results are not provided for external superelements in the .out file.
PEAKOUT:
If PEAKOUT is present, only the filtered frequencies from the PEAKOUT card will be considered for this output.
peakoutput
Default = blank
option
blank:
Element kinetic energy and kinetic energy density are output for all elements.
Default = ALL NO, NONE:
Element kinetic energy and kinetic energy density are not output.
SID:
If a set ID is given, element kinetic energy and kinetic energy density are output only for elements listed in that set.
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
75
6.
Type only applies to frequency response analysis.
7.
There are three ways to calculate the Element Kinetic Energy in Frequency Response Analysis. They are listed as follows: Type of Output
Formula
Average
Amplitude
Peak Where, E = Element Energy {vr } = Real part of Velocity {vi } = Imaginary part of Velocity [Me] = Element Mass 8.
76
format=OUTPUT2 can also be used to request results to be output in the Nastran output2 format (.op2 file).
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
ENERGY I/O Options and Subcase Information Entry ENERGY - Output Request for Geometric Nonlinear Analysis Subcase 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
Argument
Option
Description
format
H3D:
Results are output in Hyper3D format (.h3d file).
blank:
Results are output in all active formats for which the result is available.
ALL:
All energy results are output.
ENERG:
All energy results without hourglass energy are output.
HOURG:
Hourglass energy only is output.
Default = blank
type
Default = ALL
option
Energy results are output for all elements.
Default = ALL
NO, NONE:
Energy results are not output.
SID:
If a set ID is given, energy results are output only for elements listed in that set.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
77
Argument
Option
Description PSID:
If a property set ID is given, energy results for the elements referencing properties listed in the property set are 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.
78
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
ERP I/O Options and Subcase Information Entry ERP - Output Request 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
Argument
Option
Description
format
H3D:
Results are output in Hyper3D format (.h3d file).
PUNCH:
Results are output in Nastran punch results format (.pch file).
blank:
Results are output in all active formats for which the result is available.
GRID:
Output the contribution of each grid in addition to the ERP results for the PANEL, defined by ERPPNL or PANELG (TYPE=ERP). This is a normal velocity squared for each grid specified in the panel definition.
Default = blank
grid
Default = blank
option
Default = ALL
YES, ALL, Equivalent radiated power is output for all panels. blank: 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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
79
2.
Multiple instances of this card are allowed; if instances are conflicting, the last instance dominates.
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.
80
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
ESE I/O Options and Subcase Information Entry ESE - Output Request 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
Argument
Option
Description
format
HM:
Results are output in HyperMesh results format (.res file).
H3D:
Results are output in Hyper3D format (.h3d file).
PUNCH:
Results are output in Nastran punch results format (.pch file).
OP2:
Results are output in Nastran output2 format (.op2 file) (see comment 8).
PLOT:
Results are output in Nastran output2 format (.op2 file) when PARAM, POST is defined in the bulk data section.
blank:
Results are output in all active formats for which the result is available.
AVERAGE:
In frequency response analysis average energy is output.
AMPLITUDE:
In frequency response analysis the amplitude of energy is output.
PEAK:
In frequency response analysis the peak energy is output. This is the sum of AVERAGE and AMPLITUDE.
Default = blank
type
Default = AVERAGE See Comment 7
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
81
Argument
Option
Description
dmig
DMIG:
Results are provided for external superelements in the .out file.
NODMIG:
Results are not provided for external superelements in the .out file.
PEAKOUT:
If PEAKOUT is present, only the filtered frequencies from the PEAKOUT card will be considered for this output.
YES, ALL, blank:
Element strain energy and strain energy density are output for all elements.
NO, NONE:
Element strain energy and strain energy density are not output.
SID:
If a set ID is given, element strain energy and strain energy density are output only for elements listed in that set.
Default = NODMIG
peakoutput Default = blank
option
Default = ALL
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.
82
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
6.
Type only applies to frequency response analysis.
7.
There are three ways to calculate the Element Strain Energy in Frequency Response Analysis. They are listed as follows: Type of Output
Formula
Average
Amplitude
Peak Where, E = Elemental Energy {u r } = Displacement (Real Part) {u i } = Displacement (Imaginary Part) [Ke] = Elemental Stiffness 8.
format=OUTPUT2 can also be used to request results to be output in the Nastran output2 format (.op2 file).
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
83
FLUX I/O Options and Subcase Information Entry FLUX – Output Request 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
Argument
Options
Description
format
PUNCH:
Results are output in Nastran punch results format (.pch file).
OP2:
Results are output in Nastran output2 format (.op2 file) (see comment 5).
PLOT:
Results are output in Nastran output2 format (.op2 file) when PARAM, POST is defined in the bulk data section.
H3D:
Results are output in Hyper3D format (.h3d file).
blank:
Results are output in all active formats for which the result is available.
YES, ALL, blank:
Flux results are output for all valid elements.
Default = ALL
NO, NONE:
Flux results are not output.
SID:
If a set ID is given, flux results are output only for elements referenced by that set.
Default = blank
option
84
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Comments 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).
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
85
FORCE/ELFORCE I/O Options and Subcase Information Entry FORCE - Output Request 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
Argument
Options
Description
sorting
This argument only applies to the PUNCH format (.pch file) or the OUTPUT2 format (.op2 file) output for normal modes, frequency response, and transient subcases. It will be ignored without warning if used elsewhere.
Default = blank
format
SORT1:
Results for each frequency/ timestep are grouped together.
SORT2:
Results for each grid/element are grouped together (See comment 8).
blank:
For frequency response analysis, if no element SET is specified, SORT1 is used, otherwise, SORT2 is used; for transient analysis, SORT2 is used.
HM:
Results are output in HyperMesh result format (.res file).
H3D:
Results are output in Hyper3D format (.h3d file).
OPTI:
Results are output in OptiStruct results format (.force file).
Default = blank
86
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument
Options
Description PUNCH:
Results are output in Nastran punch results format (.pch file).
OP2:
Results are output in Nastran output2 format (.op2 file) (see comment 11).
PLOT:
Results are output in Nastran output2 format (.op2 file) when PARAM, POST is defined in the bulk data section. If PARAM, POST is not defined in the bulk data section, this format allows the form for complex results to be defined for XYPUNCH output without having other output.
blank:
form
Default (HM only) = COMPLEX
COMPLEX (HM Provides a combined magnitude/ only), blank: phase form of complex output to the .res file for the HM output format. REAL, IMAG:
Provides rectangular format (real and imaginary) of complex output.
PHASE:
Provides polar format (phase and magnitude) of complex output.
BOTH (HM only):
Provides both rectangular and polar formats of complex output.
TENSOR:
Force results are output for all solution sequences in which force results are supported. The Tensor
Default (all other formats) = REAL
type
Default = TENSOR
Altair Engineering
Results are output in all active formats for which the result is available.
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
87
Argument
Options
Description format is used for H3D output (See comment 9).
location
Default = CENTER
random
DIRECT:
Force results are output for all solution sequences in which force results are supported. The Direct format is used for H3D output (See comment 9).
CENTER:
Element forces for shell and solid elements are output at the element center only.
CUBIC:
Element forces for shell elements are output at the element center and grid points using the strain gage approach with cubic bending correction.
SGAGE:
Element forces for shell elements are output at the element center and grid points using the strain gage approach.
CORNER or BILIN:
Element forces for shell elements are output at the element center and at the grid points using bilinear extrapolation.
PSDF:
Requests PSD and RMS results from random response analysis to be output for CBUSH elements only.
No default
Only valid for H3D format. The "RMS over Frequencies" output is at the end of the Random results in the .h3d file. RMS:
88
Requests only the “RMS over Frequencies” result from random response analysis to be output for CBUSH elements only.
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument
Options
Description Valid only for the H3D format.
peakoutput
PEAKOUT:
If PEAKOUT is present, only the filtered frequencies from the PEAKOUT card will be considered for this output.
MODAL:
If MODAL is present, element forces of the structural modes and residual vectors are output to the PUNCH and OUTPUT2 files for modal frequency response and transient analysis.
YES, ALL, blank:
Element force is output for all valid elements.
Default = ALL
NO, NONE:
Force is not output.
SID:
If a set ID is given, force is output only for valid elements listed in that set.
Default = blank
modal
Default = blank
option
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
89
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 ( (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).
90
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
FORMAT I/O Options Entry FORMAT - Output Control 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
Argument Options
Description
option
OPTI, OS, ASCII:
OptiStruct ASCII results files are output.
HM, HYPER:
The HyperMesh binary results file (.res file) is output.
BOTH:
Same as defining both HM and OPTI.
H3D:
Hyper3D binary results file (.h3d file) and an HTML report (.html file) are output.
FLX:
Same as defining both HM and H3D.
NASTRAN, PUNCH:
The Nastran punch file format (.pch file) is output.
PATRAN, PATRAN:
A number of Patran ASCII results files are output. APATRAN outputs the same files using an alternative file naming convention.
O2, OUT2, OP2:
Nastran binary output2 file format (.op2 file) is output
Default = FLX
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
91
Argument Options
Description (see comment 4). PLOT:
Results are output in Nastran output2 format (.op2 file) when PARAM, POST is defined in the bulk data section.
NONE:
Analysis output is not required. Cannot be used in combination with other FORMAT commands.
Comments 1.
Information provided on OUTPUT entries takes precedence over information provided on FORMAT entries. If neither of these entries are defined, the output formats defined in the OptiStruct Configuration File are used. If no format is defined by the OptiStruct configuration file, then both the HM and H3D formats are active by default.
2.
Multiple FORMAT commands are allowed.
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).
92
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
FOS I/O Options and Subcase Information Entry FOS – Output Request 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 FOS (format_list) = option
Argument
Options
Description
format
H3D: Default = blank
option
Default = ALL
Results are output in Hyper3D format (.h3d file).
OPTI:
Results are output in OptiStruct results format (.fat file).
blank:
Results are output in all active formats for which the result is available.
YES,ALL, Results are output for all elements. blank: NO,NONE: Results are not output. SID:
If a set ID is provided, results are output only for elements listed in that set.
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
93
GPFORCE I/O Options and Subcase Information Entry GPFORCE - Output Request 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
Argument
Options
Description
format
H3D:
Results are output in Hyper3D format (.h3d file).
OPTI:
Results are output in OptiStruct results format (.gpf file).
PUNCH:
Results are output in Nastran punch results format (.pch file).
OP2:
Results are output in Nastran output2 format (.op2 file) (see comment 9).
PLOT:
Results are output in Nastran output2 format (.op2 file) when PARAM, POST is defined in the bulk data section.
NOELEM:
GPFORCE results in the H3D output file will not include element contributions. However, the TOTAL value for each GRID includes the element contributions.
ELEM:
GPFORCE results in the H3D output file includes element contributions.
REAL, IMAG:
Provides rectangular format (real and imaginary) of complex output.
Default = blank
elem (H3D only)
Default = NOELEM
form
94
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument
Options
Description
Default = REAL
PHASE:
Provides polar format (phase and magnitude) of complex output.
PEAKOUT:
If PEAKOUT is present, only the filtered frequencies from the PEAKOUT card will be considered for this output.
MODAL:
If MODAL is present, grid point forces of the structural modes and residual vectors are output to the PUNCH and OUTPUT2 files for modal frequency response and transient analysis.
peakoutput Default = blank
modal
Default = blank
option
blank: Default = ALL
Grid point force balance is output for all elements.
NO, NONE:
Grid point force balance is not output.
SID:
If a set ID is given, grid point force balance is output only for nodes listed in that set.
Comments 1.
When a GPFORCE command is not present, grid point force balance is not output.
2.
GPFORCE output is available for the following solution sequences: Solution Sequences
Output Formats
Static Analysis
H3D, OP2, PCH, OPT
Normal Modes Analysis
H3D, OP2, PCH
Direct Frequency Response Analysis
H3D, OP2, PCH, OPT
Modal Frequency Response Analysis
H3D, OP2, PCH, OPT
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
95
3.
The form argument is only applicable for frequency response analysis. It is ignored in other instances.
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).
96
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
GPKE I/O Options and Subcase Information Entry GPKE - Output Request for Grid Point Kinetic Energy 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 GPKE (format_list) = option
Argument
Options
Description
format
PUNCH:
Default = blank option
Results are output in Nastran punch results format (.pch file).
YES, ALL, blank: GPKE results are output for all elements.
Default = ALL
NO, NONE:
GPKEs results are not output.
SID:
If a set ID is given, GPKE results are output only for grids listed in that set.
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
97
GPSTRESS/GSTRESS I/O Options and Subcase Information Entry GPSTRESS - Output Request 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
Argument
Options
Description
format
HM:
Results are output in HyperMesh results format (.res file).
H3D:
Results are output in Hyper3D format (.h3d file).
PUNCH:
Results are output in Nastran punch format (.pch file).
OP2:
Results are output in Nastran output2 format (.op2 file) (see comment 8).
blank:
Results are output in all active formats for which the result is available.
GLOBAL:
Only the globally averaged GPSTRESS results are output.
BYPROP, blank:
Both the globally averaged GPSTRESS results and the GPSTRESS results averaged by property for each property are output.
Default = blank
averaging
Default = BYPROP
98
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument
Options
Description
type
VON:
Only von Mises Stress results are output.
PRINC, MAXS, SHEAR:
The von Mises and maximum principal stress results are output.
ALL, blank:
All stress results are output.
TENSOR:
All stress results are output. Tensor format is used for H3D output.
DIRECT:
All stress results are output. Direct format is used for H3D output.
YES, ALL, blank:
Grid point stresses output for all elements.
Default = ALL
NO, NONE:
Grid point stresses are not output.
SID:
If a set ID is given, grid point stresses are output only for nodes listed in that set.
Default = ALL
option
Comments 1.
When a GPSTRESS command is not present, grid point stresses are not output.
2.
Grid point stresses are only available for solid elements.
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
99
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.
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).
100
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
HISOUT I/O Options Entry HISOUT - Output Control 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
Argument
Options
Description
option
HISOUT value is equal to the sum of the desired options: Default = 31
1: Design variable. 2: Objective function and maximum percent constraint violation. 4: All non-stress responses. 8: All DRESP2 responses. 16: All DRESP3 responses. If blank: no output to .hgdata file. Example: If you wanted design variables and all DRESP2 responses, you would enter: HISOUT = 9
Comments 1.
When a HISOUT command is not present, a value of 31 is assumed.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
101
HYBDAMP I/O Options Entry HYBDAMP – Apply Hybrid Damping to the Residual Structure in a Direct or Transient Frequency Response Analysis 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
Argument
Option
Description
option
< SID >
SID: Set identification of HYBDAMP in bulk data entry.
No default Comments 1.
102
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.
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
INCLUDE I/O Options and Bulk Data Entry INCLUDE - File Selection 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
Argument
Options
Description
option
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. 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 INCLUDE 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 INCLUDE command supports path names of up to 200 characters in length. 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.
4.
Represented through the master model in HyperMesh.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
103
LIFE I/O Options and Subcase Information Entry LIFE – Output Request 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
Argument
Options
Description
format
H3D:
Results are output in Hyper3D format (.h3d file).
OPTI:
Results are output in OptiStruct results format (.fat file).
blank:
Results are output in all active formats for which the result is available.
YES, ALL, blank:
Results are output for all elements.
NO, NONE:
Results are not output.
SID:
If a set ID is given, results are output only for elements listed in that set.
Default = blank
option
Default = ALL
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.
104
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
LOADLIB I/O Options Entry LOADLIB - External Library and File Reference 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
Argument
Options
Description
type
TYPE identifier that defines the type of library(or file) to be loaded into OptiStruct. Currently only one type implemented - DRESP3.
No default group
GROUP identifier that is referenced by a DRESP3 bulk data entry.
No default path
The path to the external shared or dynamic 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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
105
MBFORCE I/O Options Entry MBFORCE – Output Control 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
Argument
Options
Description
option
YES, ALL, blank: Force is output for all joints and force elements.
Default = ALL
NO, NONE: Forces are not output. SID: If a set ID is given, forces are output only for joints and force elements listed in that set. Note: Joints and force elements may share IDs. When MBFORCE is requested for a SET, force results are output for all entities whose ID is part of the SET definition.
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.
106
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
MECHCHECK I/O Options Entry MECHCHECK - Massless Mechanism Check 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
…
-----------------------------------------------------
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
107
MODALDE I/O Options Entry MODALDE – Output Request 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
Argument
Options
Description
format
H3D:
Results are output in Hyper3D format (.h3d file).
blank:
Results are output in all active formats for which the result is available.
Default = blank
thresh
Specifies an absolute threshold under which results should not be output.
No default
rthresh
topn
No default
Specifies a relative threshold under which results should not be output. This value is relative to the corresponding total modal energy.
Specifies that only the top N values should be output.
No default
type
108
AVERAGE:
The average of the energy is output.
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument
mset
option
Options
Description
Default = AVERAGE
AMPLITUDE:
The amplitude of the energy is output.
PEAK:
The peak energy is output. This is the sum of AVERAGE and AMPLITUDE.
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.
TOTAL:
Only the total energy is output.
YES, ALL, blank:
Modal energy is output for all modes.
NO, NONE:
Modal energy is not output.
Default = ALL
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
109
MODALKE I/O Options Entry MODALKE – Output Request 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
Argument
Options
Description
format
H3D:
Results are output in Hyper3D format (.h3d file).
blank:
Results are output in all active formats for which the result is available.
Default = blank
thresh
Specifies an absolute threshold under which results should not be output.
No default
rthresh
topn
No default
Specifies a relative threshold under which results should not be output. This value is relative to the corresponding total modal energy.
Specifies that only the top N values should be output.
No default
type
110
AVERAGE:
The average of the energy is output.
Default = AVERAGE
AMPLITUDE:
The amplitude of the energy is output.
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument
mset
option
Options
Description PEAK:
The peak energy is output. This is the sum of AVERAGE and AMPLITUDE.
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.
TOTAL:
Only the total energy is output.
YES, ALL, blank:
Modal energy is output.
NO, NONE:
Modal energy is not output.
Default = ALL
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
111
MODALSE I/O Options Entry MODALSE – Output Request 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
Argument
Options
Description
format
H3D:
Results are output in Hyper3D format (.h3d file).
blank:
Results are output in all active formats for which the result is available.
Default = blank
thresh
No default
rthresh
topn
Specifies an absolute threshold under which results should not be output.
No default
Specifies a relative threshold under which results should not be output. This value is relative to the corresponding total modal energy.
Specifies that only the top N values should be output.
No default
type
112
AMPLITUDE: Default = AVERAGE
The average of the energy is output. The amplitude of the energy is output.
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument
mset
Options
Description PEAK:
The peak energy is output. This is the sum of AVERAGE and AMPLITUDE.
ALL:
Modal energy is output for all modes.
SID:
If a set ID is given, modal energy is output only for modes listed in that set.
TOTAL:
Only the total energy is output.
YES, ALL, blank:
Modal energy is output.
Default = ALL
NO, NONE:
Modal energy is not output.
Default = ALL
option
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
113
MODEL I/O Options Entry MODEL - Output Control 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 MODEL = elset, gridset, rigidset
Argument Options
Description
elset
SID:
Default (analysis run) = ALL
PLOTEL: Default (CMS SE creation) = NONE ALL:
gridset
rigidset
ID of an element SET. A set of elements that describe the subset of the model for which results and model information is to be output. All GRID and SPOINT associated with these elements will also be output. All PLOTELs in the model and their associated GRID will be output. All elements in the model and their associated GRID will be output.
NONE:
No elements.
SID:
SID of a SET. A set of grids to be added to the subset associated with the preceding elset field.
Default = NONE
ALL:
All grids.
NONE:
No grids are added to the subset described by the preceding elset field.
RIGID/ ALL:
All rigid elements and their associated GRID will be output.
Default (analysis run) =RIGID/ALL
114
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument Options
Description
Default (CMS SE NORIGID/ creation) = NONE: NORIGID/NONE SID:
No rigid elements will be output.
ID of a rigid element SET. A set of rigid elements that describe the subset of the model for which model information is to be output. All GRID and SPOINT associated with these rigid elements will also be output.
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.
3.
When PARAM,EXCOUT with values of 0, 3, 4, 5 or 6 is used during CMS superelement creation, the default is to output the entire model, as well as results to the .h3d file and AVL/EXCITE files.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
115
MPCFORCE I/O Options and Subcase Information Entry MPCFORCE - Output Request 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
Argument Options
Description
sorting
This argument only applies to the PUNCH format (.pch file) or the OUTPUT2 format (.op2 file) output for normal modes, frequency response, and transient subcases. It will be ignored without warning if used elsewhere.
Default = blank
format
SORT1:
Results for each frequency/timestep are grouped together.
SORT2:
Results for each grid/element are grouped together (See comment 5).
blank:
For frequency response analysis, if no grid SET is specified, SORT1 is used, otherwise, SORT2 is used; for transient analysis, SORT2 is used.
OPTI:
Results are output in OptiStruct results format (.mpcf file).
PUNCH:
Results are output in Nastran punch results format (.pch file).
OP2:
Results are output in Nastran otput2 format (.op2 file) (see comment 6).
PLOT:
Results are output in Nastran output2 format (.op2 file) when PARAM, POST is defined in the bulk data section.
Default = blank
116
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument Options
form
Description
blank:
Results are output in all active formats for which the result is available.
REAL, IMAG:
Provides rectangular format (real and imaginary) of complex output.
PHASE:
Provides polar format (phase and magnitude) of complex output.
PEAKOUT:
If PEAKOUT is present, only the filtered frequencies from the PEAKOUT card will be considered for this output.
MODAL:
If MODAL is present, multi-point constraint forces of the structural modes and residual vectors are output to the PUNCH and OUTPUT2 files for modal frequency response and transient analysis.
Default = REAL
peakoutpu t
Default = blank
modal
Default = blank
option
YES, ALL, Multi-point force of constraint vector is output for all grids. blank:
Default = ALL
NO, NONE:
Multi-point force of constraint vector is not output.
SID:
If a set ID is given, multi-point force of constraint vector is output only for grids listed in that set.
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
117
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 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 ( (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).
118
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
MSGLMT I/O Options and Subcase Information Entry MSGLMT - Output Control 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 (type) = value MSGLMT, type, value MSGLMT, mode Examples MSGLMT (WARNING) = 1000 MSGLMT (101) = 50
Argument
Options
Description
type
ERROR:
Limits the total number of ERROR messages allowed to the value provided. Once this limit is reached, the run terminates.
WARNING:
Limits the total number of WARNING and INFORMATION messages reported in the .out file to the value provided.
ID:
Limits the number of instances of a message with the given ID reported in the .out file to the value provided.
INTEGER:
If a positive integer is given, the limit is set to this number.
No default
value
See comments 1 and 2 for
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
119
Argument
Options
Description
defaults.
OFF or NONE: “value=NONE” can only be used if “type = ID”. See Comment 3. ERROR:
Valid only when the type is ID. Messages with this ID will be treated as ERRORs, that is, continuation at the end of the current stage will be disallowed unless the message is encountered during the solver, where full postprocessing of the results will be allowed before termination; optimization runs will terminate as if the limit of allowed iterations had been reached.
ABORT:
Valid only when type is ID. Messages with this ID will be treated as abort ERRORs, that is, the solver will terminate immediately. If the message is encountered during the solver, no output files will be generated. If it happens during reading or verification of input data, then remaining parts of input will not be processed.
mode
Default =
STRICT:
All messages are printed according to MSGLMT.
UNREF:
Messages 1931, 1932 and 2010 are suppressed.
BRIEF:
Messages 741, 742, 1935, 1931, 1932, 2010, 1052, 1305, and 1436 are suppressed.
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.
3.
The following table lists some special cases of MSGLMT usage:
120
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Special Cases
Effect
MSGLMT(Message ID/WARNING/ ERROR) = 1
Prevents any information about consecutive occurrences of the specified message to be registered and counted. If WARNING/ERROR is used, only the first WARNING/ERROR is printed.
MSGLMT(Message ID/WARNING/ ERROR) = 0
Message ID: All occurrences of the specified message will be displayed.
MSGLMT(Message ID/WARNING/ ERROR) = OFF
WARNING: All Warnings will be displayed. ERROR: All Errors will be displayed.
MSGLMT(Message ID) = NONE
The specified message (and multiple occurrences of the same, if any) will not be printed in the output file. 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. 3. Using MSGLMT(Message ID)=NONE for ERROR messages is not recommended.
MSGLMT(Message ID) =
Negative values are not supported. A “Syntax error” will be displayed, if negative integer values are used.
4.
MSGLMT may be set in the OptiStruct Configuration File.
5.
Multiple instances of MSGLMT may occur. If any instances conflict, then the last instance will be honored.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
121
6.
Some messages print lists of ID's, which can be very long, MSGLMT can be used to control the number of ID's that are printed. For Example: MSGLMT, 1692, or MSGLMT (1692) =, prints the first number of duplicate GRID ID’s: *** WARNING # 1692 Found duplicate GRID cards, removed 74 item(s) of identical data. 10001
10002
… (up to number)
MSGLMT, 1692, OFF or MSGLMT (1692) =OFF, prints all duplicate GRID ID’s: *** WARNING # 1692 Found duplicate GRID cards, removed 86 item(s) of identical data. 10001
122
10002
10003
10004
10005
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
NLRESTART I/O Options Entry NLRESTART - Run Control Command 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
n
Nonlinear SUBCASE ID to be restarted from in the current nonlinear solution sequence. If n is not given, it will restart from the first nonlinear subcase ending with error in previous run.
Comments 1.
This command applies only to geometric nonlinear subcases (ANALYSIS = NLGEOM, IMPDYN or EXPDYN).
2.
Only one NLRESTART entry can be defined, and it must be above the first subcase.
3.
NLRESTART is also available in command line option as “-nlrestart n” or “-nlrestart.” If NLRESTART is defined in both bulk data and command line option, the former overrides the latter.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
123
OFREQUENCY I/O Options and Subcase Information Entry OFREQUENCY - Output Control 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
Argument
Options
Description
option
ALL, blank: Output is for all frequencies.
Default = ALL SID:
If a set ID is given, output is only for frequencies listed in that set.
Comments 1.
When OFREQUENCY is not present, output is for all frequencies.
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.
124
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
OLOAD I/O Options and Subcase Information Entry OLOAD - Output Request 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
Argument
Options
Description
format
H3D:
Results are output in Hyper3D format (.h3d file).
OPTI:
Results are output in OptiStruct results format (.load file).
Default = blank
PUNCH:
OP2:
type
Results are output in Nastran punch results format (.pch file). Results are output in Nastran output2 format (.op2 file) (see comment 6).
blank:
Results are output in all active formats for which the result is available.
ALL:
Output for all selected nodes is printed.
SPARSE:
This is only available for the OPTI output format. Output for selected nodes without a component of magnitude 1.0e-10 is not printed.
Default (OPTI) = SPARSE Default (H3D, PUNCH, OP2) = ALL
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
125
Argument
Options
Description
option
YES, ALL, blank:
Load data is output for all nodes.
NO, NONE:
Loads are not output.
SID:
If a set ID is given, load data is only output for nodes listed in that set.
Default = ALL
Comments 1.
When OLOAD command is not present, loads 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 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).
126
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
OMODES I/O Options Entry OMODES - Output Control 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
Argument
Options
Description
option
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 1.
When OMODES is not present, output is for all modes.
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
127
OTIME I/O Options and Subcase Information Entry OTIME - Output Control 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
Argument
Options
Description
option
< ALL, SID >
ALL, blank:
Output is at all times.
SID:
If a set ID is given, output is only at times in that set.
Default = ALL
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).
\
128
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
OUTFILE I/O Options Entry OUTFILE - Filename Definition Description The OUTFILE command is used in the I/O Options section to define the prefix for the results files output. Format OUTFILE = option
Argument
Options
Description
option
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. The following rules are used for the OUTFILE card: 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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
129
OUTPUT I/O Options Entry OUTPUT – Output Control 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
Argument
Options
Description
keyword
See below
See below
frequency
FIRST, LAST, FL, ALL, NONE, N or blank
FIRST:
Output first iteration only.
LAST:
Output last iteration only.
FL:
Output first and last iterations.
ALL:
Output all iterations.
NONE:
No output
N:
Output first and last iterations and every Nth iteration. If N=5, output occurs at iterations 0, 5, 10, 15, 20, and so on, and the final iteration.
blank:
The default listed below for the given keyword.
option
See below
See below
Standard Result Outputs 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.
130
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Keyword Description
HM
Output results in HyperMesh binary format.
Default frequency FL
Affect ed files *.res
Options
Details
Determines whether or not to output results for interior points of external superelements. See comment 16.
Default = DMIGSET
NODMIG: recovery is deactivated 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)
H3D, HV
Output results in Hyper3D format.
FL
*.h3d
Default = BYSUB
Determines the way the output files are arranged in an optimization run. See comment 15.
(Applicable to optimization runs only). Default = DMIGSET
Determines whether or not to output results for interior points of external superelements. See comment 16. NODMIG: recovery is deactivated DMIGALL: recovery is activated for all grids/ elements DMIGSET: recovery is activated for grids/elements in the SET defined on the corresponding output request
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
131
Keyword Description
Default frequency
Affect ed files
Options
Details
(default)
OP2, OUT2, OUTPUT2
Output analysis results in Nastran output2 format.
FL
*.op2
Turns on / off the output of the model data to the file.
Default = MODEL
See comments 11 and 12.
Default = DMIGSET
Determines whether or not to output results for interior points of external superelements. See comment 16. NODMIG: recovery is deactivated 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)
NASTRAN , PUNCH
Output analysis results in Nastran punch format.
FL
*.pch
Default = DMIGSET
Determines whether or not to output results for interior points of external superelements. See comment 16. NODMIG: recovery is deactivated DMIGALL: recovery is activated for all grids/ elements
132
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Keyword Description
Default frequency
Affect ed files
Options
Details
DMIGSET: recovery is activated for grids/elements in the SET defined on the corresponding output request (default) OPTI, ASCII, OS
Output results in OptiStruct ASCII format.
FL
*.cstr , *.dens , *.disp , *.forc e, *.gpf, *.load , *.mpcf , *.spcf , *.strs
-
-
PATRAN, APATRAN
Output analysis results in Patran ASCII format.
FL
*.#.#. #.dis, *.#.#. dis, *.#.#. els, *.#.di s, *.#.el s,
-
-
(APATRAN uses an alternate file naming convention , with the iteration number after the file extension).
Altair Engineering
*.#.#. dis.#, *.#.di s.#, *.#.el s.#, *.dis. #, *.els. #
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
133
Keyword Description
NONE
Default frequency
Affect ed files
-
-
Default frequenc y
Affected files
Results are not output in any of the formats listed above.
Options
Details
-
-
Optimization Outputs
Keyword
Description
DESIGN
Controls the frequency of output for design results such as DENSITY, SHAPE, and THICKNESS
ALL
SHRES
Controls the frequency of output of the shape files.
GRID
Requests the output of the state file (.grid file) for topography or shape optimization.
Options
Details
All files that design results are written to.
-
-
L
*.sh, *.grid
-
-
L
*.grid
BASIC: Grid definitions are Default = BASIC output to the .grid file, referencing the basic coordinate system. LOCAL: Grid definitions are output to the .grid file, referencing local coordinate systems as
134
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Keyword
Description
Default frequenc y
Affected files
Options
Details
defined by the CP field on the GRID definitions. FSTOSZ
Automatic generation of a sizing model after freesizing of a composite structure.
L
*_sizing.fe m
1.
Bundles
See comment 18.
Integer > 0 Default = 4 2.
Method Default = ADVFREE
3.
SZTOSH
Automatic generation of a shuffling model after ply-based sizing optimization.
L
*_shuffling .fem
FSTHICK
Controls output of freesizing results to .fsthick file.
-
*.fsthick
Requests the output of updated design variable values.
L
DESVAR
Ignore -
-
See comment 13.
Default = NO
*.desvar, *.out
Default = FILE
FILE: Updated property design variable values are output to the .desvar file. OUT: Updated design variable values are output to the .out file.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
135
Keyword
Description
Default frequenc y
Affected files
Options
Details
BOTH: Updated design variable values are output to both the .out file and the .desvar file. NONE: Updated design variable values are not output. PROPERTY
Requests the output of the updated property definitions.
L
*.prop, *.out
ANY: All properties are output.
Default = DESIGN
DESIGN: Only designable properties are output.
Note: In the Description and Details columns of the PROPERTY keyword: “Property” stands for “Properties, Materials and Elements”.
FILE: Updated property definitions and non-design properties are output to the .prop file. OUT: Updated property definitions and non-design properties are output to the .out file. BOTH: Updated property definitions and non-design properties are output to both the .out file and the .prop file.
136
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Keyword
Description
Default frequenc y
Affected files
Options
Details NONE: Updated property definitions are not output.
Specialized Result Outputs
Keyword
Description
ADAMSMNF
Output of flexible body to a modal neutral file for MSC.ADAMS.
Default Affected files frequenc y -
*.mnf
Options
Details
-
Default = YES
See comment 17. HGFREQ
Frequency Analysis output presentation for HyperGraph.
FL
*_freq.mvw, *_s#_a.frf, *_s#_d.frf, *_s#_v.frf
-
-
-
*_tran.mvw, *_s#_a.trn, *_s#_d.trn, *_s#_v.trn
-
-
See comment 3. HGTRANS
Transient Analysis output presentation for HyperGraph. See comments 2 and 3.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
137
Keyword
Description
HGMBD
Multi-body Dynamics output presentation for HyperGraph.
Default Affected files frequenc y -
*_mbd.mvw, *_s#_a.mbd, *_s#_d.mbd, *_s#_v.mbd
Options
-
Details
-
See comments 2 and 3. HGSENS
Sensitivity output presentation for HyperGraph.
FL
*_sens.#.mvw, *.#.sens
See comment 4 for details on options.
Default = NOSTRESS MSSENS
Sensitivity output in Microsoft Excel SYLK format.
FL
*.#.slk
See comment 4 for details on options.
Default = NOSTRESS ASCSENS
H3DSENS
H3DTOPOL
138
Topology and free-sizing sensitivity (response with respect to design element density) output in ASCII format.
FL
Sensitivity output in H3D format.
FL
Sensitivity output in H3D format for contouring of topology and
FL
*.#.asens
See comment 4 for details on options.
Default = NOSTRESS
*_dsa.#.h3d
Default = NOUSER
*_topol.#.h3d
See comment 19 for details on options.
See comment 4 for details on options.
Default =
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Keyword
Description
Default Affected files frequenc y
free-sizing sensitivity. H3DGAUGE
HGHIST
Sensitivity output in H3D format for contouring of shell thickness sensitivity. Design history output presentation for HyperGraph.
HGEFFMASS Effective mass is output as a HyperGraph bar chart. HGMODFAC
DVGRID
Modal participation factor output presentation for HyperGraph3D. Output of shape variable definitions to .dvgrid file.
Options
Details
NOSTRESS
FL
*_gauge.#.h3d
See comment 4 for details on options.
Default = NOSTRESS -
-
FL
*_hist.mvw, *.hist *.hgdata
*.mass, *_mass.mvw
*_modal.mvw, *_modal.#.mvw
Integer < 32 Default = 31
-
See comment 5 for details on options.
-
See comment 14.
Default = REGULAR -
*.dvgrid
-
-
*.out
-
The center of gravity is specified in the basic coordinate system. The Mass Properties are with respect to the
See comment 6. MASSPROP
Controls the output of Center of Gravity and Mass Moments of Inertia tables based on properties to .out file.
Altair Engineering
FL
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
139
Keyword
Description
Default Affected files frequenc y
Options
Details
center of gravity of the item. MASSCOMP
Controls the output of Mass based on HyperMesh Components to .out file.
REGCOMPL
Controls the output of regional compliance table to .out file.
FL
*.out
*.out
-
-
Default = YES
File Output Controls
Keyword
Description
CMF
Controls output of .cmf files.
OSS
Default frequenc y
Affected files
Options
-
*.HM.badel.c mf, *.HM.comp.cm f, *.HM.ent.cmf , *.HM.conn.cm f
Default = YES
Controls output of .oss file.
-
*.oss
Default = YES
HTML
Controls output of .html file.
-
*.html
Default = YES
STAT
Controls output
-
*.stat
140
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Details
See comment 9.
Altair Engineering
Keyword
Description
Default frequenc y
Affected files
of .stat file.
Options
Details
Default = YES
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.
2.
HGTRANS and HGMBD are currently available for analysis only.
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.
4.
For HGSENS, ASCSENS, or MSSENS options: 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.
5.
For HGHIST options: The integer value given is equal to the sum of the desired options: 1: Design Variable. 2: Objective function and maximum % constraint violation. 4: All non-stress responses. 8: All DRESP2 responses. 16: All DRESP3 responses. If blank: all of the above are output. 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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
141
9.
If OUTPUT,STAT,NO is defined, the *.stat file is deleted at the end of the run (as long as the run was successful), but the file always exists during the run.
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 freesize design spaces. The element definitions have the optimized thickness defined as nodal thicknesses (Ti) for each element. 14. The HGMODFAC keyword generates a HyperGraph3D presentation providing 3D 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 yaxis and the modal participation factor on the z-axis. The NORM option normalizes the participation factors with respect to 1. In HyperGraph3D, it is possible to define cross-sections to generate 2D plots of either: a) Modal participation factor vs. frequency or time for a given number. b) 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. 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).
142
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
BYITER outputs one .#.h3d file per iteration that contains the optimization and analysis results for all subcases per iteration. Frequency determines at which iteration these files are created. It overwrites the default of OUTPUT, DESIGN unless an actual OUTPUT, DESIGN statement is present. In the case of a shape optimization, the GRID coordinates of the model in the respective iteration are updated to the new shape. (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. 18. For FSTOSZ options: 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. ADVFREE: Advanced algorithm with free thicknesses. ADVMAN: Advanced algorithm with manufacturable thicknesses. SIMFREE: Simple algorithm with free thicknesses. SIMMAN: Simple algorithm with manufacturable thicknesses. 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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
143
PFGRID I/O Options Entry PFGRID – Output Request for Acoustic Grid Participation 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
Argumen Options t
Description
setg
ALL:
Output acoustic grid participation for all structural grid points at the fluid-structure interface.
NONE:
Do not output acoustic grid participation for any structural grid points.
SID:
Output acoustic grid participation factors for a set of grids. SID refers to the ID of a SET of type GRID.
ALL:
Output acoustic grid participation for all fluid grid points at the fluid-structure interface.
NONE:
Do not output acoustic grid participation for any fluid grid points.
SID:
Output acoustic grid participation factors for a set of grids. SID refers to the ID of a SET of type GRID.
Default = NONE
setfl
Default = NONE
144
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argumen Options t
Description
setf
ALL:
Participation factors are processed for all excitation frequencies.
SID:
Participation factors are only processed for a set of excitation frequencies. SID refers to the ID of a SET of type FREQ.
Default = ALL
ipower
When the magnitude of a grid participation is below 10 to the minus ipower, the grid participation will not be output. In other words, if the grid participation is less than 10-ipower, the result output for this grid will be skipped.
Default = 30
rval
Default = 0.0
rpdba
Default = 0.0
CONTOUR
(YES/NO) Default = YES
PEAKOUT
The grid participation will be calculated at the excited frequencies when the magnitude of the pressure is above rval. The excitation frequency will be a subset of setf.
RPDBACUT is the decibel pressure cutoff value for fluid responses, and is similar to RPCUTOFF. It will take precedence over RPCUTOFF for fluid responses. A weighting is applied to RPDBACUT values at the excitation frequency. The grid 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.
If CONTOUR is specified as YES, the area projected value for the fluid grid participation is output. Otherwise, the output of fluid grid participation would be the actual complex value.
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
145
Argumen Options t
Description
setdof/ PEAKOUT
Degrees of freedom for which the grid participation factors are 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 1.
Output is to the H3D file only.
2.
Acoustic grid participation factors are available in a coupled frequency response analysis (both in direct and modal frequency response).
3.
The FREQUENCY keyword can be used to select a subset of excitation frequencies available.
4.
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.
146
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
PFMODE I/O Options Entry PFMODE – Output Request for Modal Participation 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
Argument Options
Description
type
STRUCTURE:
Requests output of structural modal participation factors.
FLUID:
Requests output of acoustic modal participation factors.
ALL:
Participation factors will be computed for all calculated fluid modes.
Default = STRUCTURE
fmp
Default = NONE N:
NONE:
Altair Engineering
Number of fluid modes for which modal participation factors will be computed, based on the largest magnitude of modal contribution. Participation factors are not calculated for fluid modes.
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
147
Argument Options
Description
smp
ALL:
Default = NONE N:
setp
Participation factors are not calculated for structural modes.
ALL:
Output structural modal participation for each panel specified in the PANEL data.
NONE:
Do not output panel modal participation.
ALL:
Participation factors are processed for all excitation frequencies.
SID:
Participation factors are only processed for a set of excitation frequencies. SID refers to the ID of a SET of type FREQ.
Default = ALL
fratio
Specifies the value of a filter to be applied to the output. Values of modal participation below fratio times the displacement or pressure are not output.
Default = 0.001
ipower
When the magnitude of a modal participation is below 10 to the minus ipower, the modal participation will not be output. In other words, if the modal participation is less than 10-ipower, the result output for this mode will be skipped.
Default = 30
rval
Default = 0.0
148
Number of structural modes for which modal participation factors will be computed based on the largest magnitude of modal contribution.
NONE:
Default = NONE
setf
Participation factors will be computed for all calculated structural modes.
The modal participation will be calculated at the excited frequencies when the magnitude of the response is above rval. The excitation frequency will be a subset of setf.
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument Options
Description
rpdba
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
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
Default = ALL
Component modal participation of all the H3D superelements will be output by default. However, you can specify a specific set of superelement names for output.
rtype
The Structural modal participation will be output for Displacement, Velocity or Acceleration respectively based on Default = DISP the specified option (DISP, VELO, ACCE).
outfile
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
149
Argument Options
Description
setdof/ PEAKOUT
Degrees-of-freedom for which the participation factors are to be processed. SID refers to the ID of a SET of type GRIDC for structure participation and GRID for fluid participation. If “PEAKOUT” is specified instead of SID, the output will be considered at the filtered frequencies corresponding to the degree of freedom on the PEAKOUT card in the bulk section.
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.
4.
Keywords FLUIDMP and PANELMP are only valid if FLUID is specified.
5.
If STRUCTURE is specified, setdof must reference a set of structural degrees-of-freedom. If FLUID is specified, setdof must reference a set of acoustic degrees-of-freedom.
6.
The FREQUENCY keyword can be used to select a subset of excitation frequencies available.
7.
The filter is applied to the magnitude of the modal participation factors. Only modal participation factors that pass the filter are output.
8.
If the magnitude of the total response at a selected response degree-of-freedom is less than 10-ipower, then no modal participation factors are processed. If ipower is not in the range of 1 to 31, the default of 30 is used.
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 option for the sedof/PEAKOUT argument.
150
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
PFPANEL I/O Options Entry PFPANEL – Output Request for Acoustic Panel Participation 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 PFPANEL (PANEL=setp, FREQUENCY=setf, outfile,peakout) = setdof/PEAKOUT Examples PFPANEL(PANEL=ALL,FREQUENCY=45)=12 PFPANEL(H3D, PEAKOUT)=56 PFPANEL(H3D, PEAKOUT)=PEAKOUT PFPANEL(PUNCH)=32
Argumen Options t
Description
setp
ALL:
Output acoustic panel participation for all panels.
NONE:
Do not output acoustic panel participation.
ALL:
Participation factors are processed for all excitation frequencies.
SID:
Participation factors are only processed for a set of excitation frequencies. SID refers to the ID of a SET of type FREQ.
Default = NONE
setf
Default = ALL
outfile
Default = H3D
Altair Engineering
Panel participation can be exported either into a H3D file or a PUNCH file. Because of the large volume of data, it is recommended to export the panel participation data into a H3D file.
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
151
Argumen Options t
Description
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.
setdof/ PEAKOUT
Degrees-of-freedom for which the panel participation factors are 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 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).
3.
The FREQUENCY keyword can be used to select a subset of excitation frequencies available. The closest loading frequency will be chosen in this case.
4.
Legacy format for the export of acoustic panel participation to H3D or PUNCH files: PFPANEL (OUTPUT=outfile)=setdof/PEAKOUT is also supported.
152
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
PFPATH I/O Options Entry PFPATH – Output Request 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 SID references a PFPATH card in the Bulk Data section.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
153
POWERFLOW I/O Options Entry POWERFLOW – Output Request 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
Argument Options
Description
format
H3D:
Results are output in Hyper3D format (.h3d file).
PEAKOUT:
If PEAKOUT is present, only the filtered frequencies from the PEAKOUT card will be considered for this output.
Default = H3D
peakoutpu t Default = blank
option
blank: Default = ALL
Power flow field is output for all elements.
NO, NONE:
Power flow field is not output.
SID:
If a set ID is given, power flow field is output only for the contents of that set.
Comments 1.
Power flow field output is only available to the .h3d file.
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.
154
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
PRESSURE I/O Options and Subcase Information Entry PRESSURE - Output Request Description The PRESSURE command is analogous to the DISPLACEMENT command. Refer to the documentation for the DISPLACEMENT command.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
155
PRETBOLT I/O Options and Subcase Information Entry PRETBOLT - Output Request 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
Argument
Options
Description
format
OPTI:
Results are output in OptiStruct results format (.pret file).
blank:
Results are output in all active formats for which the result is available.
YES:
Pretension force/adjustment values are output for all bolts.
NO:
Pretension force/adjustment values are not output.
Default = blank
option
Default = YES
Example PRETBOLT (OPTI) = YES 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.
156
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
PROPERTY I/O Options Entry PROPERTY - Output Control 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
Argument
Options
Description
option
FILE or blank: Updated property definitions are output to the .prop file.
Default = FILE
OUT:
Updated property definitions are output to the .out file.
BOTH:
Updated property definitions are output to both the .out file and the .prop file.
NONE:
Updated property definitions are not output.
Comments 1.
When a PROPERTY command is not present the updated property definitions will not be output.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
157
RADSND I/O Options and Subcase Information Entry 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
Argument
Options
Description
option
SID:
ID of RADSND bulk data entry.
No default Comments 1.
158
Multiple instances of this card are allowed. If the instances are conflicting, the last instance will be considered.
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
RCROSS I/O Options Entry RCROSS – Output Request 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
Argume nt
Options
Description
format
PUNCH:
Results are output in Nastran punch results format (.pch file).
blank:
Results are output in all active formats for which the result is available.
COMPLEX:
Provides a combined magnitude/phase form of complex output to the .res file if HM output format is chosen. The REAL form of complex output is used for other formats if they are not specifically defined. (Phase output is in degrees).
REAL or IMAG:
Provides rectangular format (real and imaginary) of complex output.
PHASE:
Provides polar format (phase and magnitude) of complex output.
BOTH:
Provides both rectangular and polar formats of complex output.
PSDF:
Requests the cross-power spectral density function be calculated and output for random analysis postprocessing.
Default = blank
form
Default = COMPLEX
type
Default = PSDF
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
159
Argume nt
Options
Description
option
RCROSS_ID:
Set identification of an RCROSS bulk data entry.
randid
Set identification number of a RANDPS bulk data entry (see comments 3 and 4).
Comments 1.
The RCROSS I/O option must be used in conjunction with the RANDOM subcase information entry.
2.
Response quantities, such as DISPLACEMENT, STRESS and STRAIN, must be requested by corresponding I/O Options in order to compute cross-power spectral density between the two response quantities specified by the RCROSS bulk data entry.
3.
Multiple RCROSS bulk data entries must be defined when each RCROSS subcase information entry references different randid. For example: rcross(PUNCH, rcross(PUNCH, rcross(PUNCH, rcross(PUNCH,
4.
160
PHASE, PHASE, PHASE, PHASE,
PSDF, PSDF, PSDF, PSDF,
randid=210020)=451 randid=210050)=452 randid=210070)=453 randid=210090)=454
randid= must be specified within the RCROSS I/O options entry when multiple RANDOM subcase information entries are present.
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
REQUEST I/O Options and Subcase Information Entry REQUEST – Multi-Body Request Selection 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
Argument
Option
Description
option
SID:
Set identification of MBREQ, MBREQE, or MBREQM bulk data entries.
No default Comments 1.
Only one REQUEST entry can be present for each subcase.
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 multibody 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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
161
RESPRINT I/O Options Entry RESPRINT - Output Control 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
Argument Options
Description
option
MASS:
Mass and massfrac responses are output.
VOLUME:
Volume and volfrac responses are output.
DISP:
Acceleration, Displacement and Velocity responses are output.
BUCK:
Buckling responses are output.
STRESS:
Stress responses, including CSTRESS and CFAILURE responses, are output.
FREQ:
Frequency responses are output.
EQUA, WCOMP, WFREQ, or COMB:
All equation and combination responses are output.
EXTERNAL:
External responses (defined by DRESP3) are output.
COMP:
Compliance responses are output.
No default
162
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
Argument Options
Description STRAIN:
Strain responses, including CSTRAIN responses, are output.
FORCE:
Force responses are output.
COG:
Center of gravity responses are output.
INERTIA:
Inertia responses are output.
MANUF:
Manufacturing constraints for composites are output.
ALL:
All design responses are output. However, manufacturing constraints for composites are not listed.
Comments 1.
When a RESPRINT command is not present, only retained responses will be output.
2.
The arguments may be placed on a single card in a comma-separated list. For example: RESPRINT = STRESS, DISP will force all stress and displacement responses referenced as either an objective or constraint to be output.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
163
RESTART I/O Options Entry RESTART - Run Control Command 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
Argument
Options
Description
option
File prefix:
Default = prefix of .fem file
The prefix of the .sh file to be used as the starting iteration for the restart.
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.
3.
This I/O Option is not valid for analysis mode.
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.
164
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
RESULTS I/O Options Entry RESULTS - Output Control 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
Argument
Options
Description
frequency
FIRST:
Output analysis results for the first iteration only.
Default = FL
LAST:
Output analysis results for the final iteration only.
FL, blank:
Output analysis results for both the first and last iterations.
ALL:
Output analysis results for all iterations.
NONE:
Do not output analysis results.
N:
Output analysis results for the first and last iterations and for every Nth iteration. If N = 5, output occurs for iterations 0, 5, 10, 15, 20, and so on, and the final iteration. All equation and combination responses are output.
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.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
165
3.
166
It is recommended to use the OUTPUT command as it allows different frequencies of output to be defined for different formats.
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
SACCELERATION I/O Options and Subcase Information Entry SACCELERATION - Output Request 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
Argument
Options
Description
sorting
This argument only applies to the PUNCH format (.pch file) or the OUTPUT2 format (.op2 file) output for normal modes, frequency response, and transient subcases. It will be ignored without warning if used elsewhere.
Default = blank
format
SORT1:
Results for each frequency/ timestep are grouped together.
SORT2:
Results for each grid/element are grouped together (See comment 7).
blank:
SORT1 is used for all results except for transient analysis, where SORT2 is used.
H3D:
Results are output in Hyper3D format (.h3d file).
Default = blank
PUNCH:
Results are output in Nastran punch results format (.pch file).
OP2:
Results are output in Nastran output2 format (.op2 file) (see comment 9).
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
167
Argument
form
Options
Description PLOT:
Results are output in Nastran output2 format (.op2 file) when PARAM, POST is defined in the bulk data section.
blank:
Results are output in all active formats for which the result is available.
REAL or IMAG:
Provides rectangular format (real and imaginary) of complex output.
PHASE:
Provides polar format (magnitude and phase) of complex output. Phase output is in degrees.
PEAKOUT:
If PEAKOUT is present, only the filtered frequencies from the PEAKOUT card will be considered for this output.
YES, ALL, blank:
Results are output.
Default = ALL
NO, NONE:
Results are not output.
Default = REAL
peakoutput
Default = blank
option
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.
168
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
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.
In general, HyperView does not recognize the SORT2 format for results from the .op2 file. When results are output only in SORT2 format ( (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.
8.
The abbreviations SACCE and SACCEL are interchangeable with SACCELERATION.
9.
format=OUTPUT2 can also be used to request results to be output in the Nastran output2 format (.op2 file).
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
169
SCREEN I/O Options Entry SCREEN - Output Control 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
Argument
Options
Description
option
OUT, blank:
The .out file is echoed to the screen.
Default = NONE
LOG:
A log of the optimization process is echoed to the screen.
NONE:
No information is echoed to the screen.
Comments 1.
When a SCREEN command is not present, no information is echoed to the screen.
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.
170
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
SDISPLACEMENT I/O Options and Subcase Information Entry SDISPLACEMENT - Output Request 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
Argument
Options
Description
sorting
This argument only applies to the PUNCH format (.pch file) or the OUTPUT2 format (.op2 file) output for normal modes, frequency response, and transient subcases. It will be ignored without warning if used elsewhere.
Default = blank
format
SORT1:
Results for each frequency/timestep are grouped together.
SORT2:
Results for each grid/element are grouped together (See comment 7).
blank:
SORT1 is used for all results except for transient analysis, where SORT2 is used.
Results are output in Hyper3D format (.h3d file).
Default = blank
PUNCH:
Results are output in Nastran punch results format (.pch file).
OP2:
Results are output in Nastran output2 format (.op2 file) (see comment 9).
PLOT:
Results are output in Nastran output2 format (.op2 file) when PARAM, POST is defined in the bulk data section.
Altair Engineering
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
171
Argument
Options
Description blank:
form
Results are output in all active formats for which the result is available.
REAL, IMAG:
Provides rectangular format (real and imaginary) of complex output.
PHASE:
Provides polar format (magnitude and phase) of complex output. Phase output is in degrees.
PEAKOUT:
If PEAKOUT is present, only the filtered frequencies from the PEAKOUT card will be considered for this output.
YES, ALL, blank:
Results are output.
Default = ALL
NO, NONE:
Results are not output.
Default = REAL
peakoutput Default = blank
option
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.
172
OptiStruct 13.0 Reference Guide Proprietary Information of Altair Engineering
Altair Engineering
7.
In general, HyperView does not recognize the SORT2 format for results from the .op2 file. When results are output only in SORT2 format ( (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.