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, blank> Default = blank
H3D: Results are output in Hyper3D format (.h3d file).
blank: Results are output in all active formats for which the result is available.
thresh <Real> No default
Specifies an absolute threshold under which results should not be output.
rthresh <Real> No default
Specifies a relative threshold under which results should not be output. This value is relative to the corresponding total modal energy.
topn <Integer> No default
Specifies that only the top N values should be output.
type <AVERAGE,
AMPLITUDE, PEAK> Default = AVERAGE
AVERAGE: The average of the energy is output. AMPLITUDE: The amplitude of the energy is output.
Argument Options Description
PEAK: The peak energy is output. This is the sum of AVERAGE and AMPLITUDE.
mset <ALL, SID,
TOTAL> Default = ALL
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.
option <YES, ALL, NO, NONE>
Default = ALL
YES, ALL, blank:
Modal energy is output.
NO, NONE: Modal energy is not output. Comments
1. When MODALSE command is not present, modal strain energy is not output. 2. Modal strain energy output is only available for modal frequency response analysis. 3. Multiple formats are allowed on the same entry; these should be comma separated. If no
format is specified, then this output control applies to all formats defined by OUTPUT or FORMAT commands for which the result is available. See Results Output for information on which results are available in which formats.
4. Multiple instances of this card are allowed; if instances are conflicting, the last instance dominates.
5. For optimization, the frequency of output to a given format is controlled by the I/O option OUTPUT. In previous version of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it does not allow different frequencies for different formats.
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, PLOTEL, ALL, NONE> Default (analysis run) = ALL Default (CMS SE creation) = NONE
SID: 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.
PLOTEL: All PLOTELs in the model and their associated GRID will be output.
ALL: All elements in the model and their associated GRID will be output.
NONE: No elements.
gridset <SID, ALL, NONE>
Default = NONE
SID: SID of a SET. A set of grids to be added to the subset associated with the preceding elset field.
ALL: All grids.
NONE: No grids are added to the subset described by the preceding elset field.
rigidset <RIGID/ALL, NORIGID/NONE, SID> Default (analysis run) =RIGID/ALL RIGID/ ALL:
All rigid elements and their associated GRID will be output.
Argument Options Description Default (CMS SE creation) = NORIGID/NONE NORIGID/ NONE:
No rigid elements will be output.
SID: 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.
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 <SORT1, SORT2> Default = blank
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.
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.
format <OPTI, PUNCH, OP2, PLOT, blank>
Default = blank
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.
Argument Options Description
blank: Results are output in all active formats for which the result is available.
form <REAL, IMAG,
PHASE>
Default = REAL
REAL, IMAG:
Provides rectangular format (real and imaginary) of complex output.
PHASE: Provides polar format (phase and magnitude) of complex output.
peakoutpu t
<PEAKOUT> Default = blank
PEAKOUT: If PEAKOUT is present, only the filtered frequencies from the PEAKOUT card will be considered for this output.
modal <MODAL> Default = blank
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.
option <YES, ALL, NO, NONE, SID> Default = ALL
YES, ALL, blank:
Multi-point force of constraint vector is output for all grids.
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.
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 (<Result Keyword> (SORT2, OUTPUT2, … .)), the results are written by OptiStruct into the .op2 file in SORT2 format, but when the .op2 file is imported into HyperView, the results in SORT2 format are not recognized. Therefore, the SORT1 option is recommended for results output in OUTPUT2 format and SORT2 option is recommended for results output in PUNCH format.
6. format=OUTPUT2 can also be used to request results to be output in the Nastran output2 format (.op2 file).
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,
WARNING, ID> No default
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.
value <INTEGER, OFF, NONE, ERROR, ABORT>
See comments 1 and 2 for
INTEGER: If a positive integer is given, the limit is set to this number.
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 post- processing 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
<STRICT, UNREF, BRIEF> Default = <BRIEF>
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.
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
MSGLMT(Message ID/WARNING/ ERROR) = OFF
Message ID: All occurrences of the specified message will be displayed. 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
Integer>
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.
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, <Integer> or MSGLMT (1692) =<integer>, prints the first <integer> number of duplicate GRID ID’s:
*** WARNING # 1692
Found duplicate GRID cards, removed 74 item(s) of identical data. 10001 10002 … (up to <integer> 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 10002 10003 10004 10005