optistruct 13.0 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; RADIOSS1986-2014; HyperView1999-2014; HyperView Player 2001-2014; HyperStudy 1999-2014; HyperGraph1995-2014; MotionView 1993-2014; MotionSolve 2002-2014; 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; SimLab2004-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
http://www.altairhyperworks.com/

OptiStruct 13.0 Reference Guidei Altair Engineering

Proprietary Information of Altair Engineering

OptiStruct 13.0 Reference Guide

........................................................................................................................................... 1Reference Guide

............................................................................................................................................... 2Input Data

................................................................................................................................... 3The Bulk Data Input File

................................................................................................................................... 7Guidelines for I/O Options and Subcase Information Entries

................................................................................................................................... 9Guidelines for Bulk Data Entries

................................................................................................................................... 14Solution Sequences - Data Selectors (Table)

................................................................................................................................... 15Summary of Defaults for I/O Options

................................................................................................................................... 22I/O Options Section

................................................................................................................................... 233Subcase Information Section

................................................................................................................................... 318Bulk Data Section

................................................................................................................................... 2160Element Quality Check

................................................................................................................................... 2189Material Property Check

............................................................................................................................................... 2197Output Data

................................................................................................................................... 2200List of Files Created by OptiStruct (Alphabetical)

................................................................................................................................... 2346Results Output by OptiStruct

............................................................................................................................................... 2378Legacy Data

................................................................................................................................... 2379Previous (OS3.5) Input Format

................................................................................................................................... 2384

Setting Up Decks in OptiStruct 5.0 with OptiStruct 3.5 Objectives andConstraints

................................................................................................................................... 2388Previously Supported Input

Altair Engineering OptiStruct 13.0 Reference Guide 1


Reference Guide

Input Data

Output Data

Legacy Data

OptiStruct 13.0 Reference Guide2 Altair Engineering


Input Data

I/O Options Section

Subcase Information Section

Bulk Data Section

Element Quality Check

Material Property Check



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. Itcontrols 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 ofinput, output, and scratch files.

The Subcase Information Section contains information for specific subcases. It identifieswhich loads and boundary conditions are to be used in a subcase. It can control output typeand frequency, and may contain objective and constraint information for optimizationproblems. For more information on solution sequences, see the table included on the SolutionSequences page of the online help.

The Bulk Data Section contains all finite element data for the finite element model, such asgrids, elements, properties, materials, loads and boundary conditions, and coordinatessystems. For optimization, it contains the design variables, responses, and constraintdefinitions. The bulk data section begins with the BEGIN BULK statement.



These sections can be arranged in either a one-file setup or a multi-file setup (there is also anobsolete 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 sectionmust 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 informationappropriate to the section.

The following example shows how an additional subcase can be added to the SubcaseInformation section.

input.fem file sub2.inc

$Subcase 1SPC = 1Load = 2$INCLUDE sub2.inc$BEGIN BULK$

Subcase 2SPC = 1Load = 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 1SPC = 1Load = 2$Subcase 2SPC = 1Load = 3$BEGIN BULK$



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 Informationsection) from the model data (Bulk Data section). If the input file does not contain a BEGINBULK 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 thiscard 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 nothave 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 singlemodel 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 OptiStructare 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 optionalpaths appropriate to the operating system (Windowsor UNIX). They may be enclosed in quotes (double orsingle quotes can be used), and either forward slash(/) or back slash (\) characters can be used toseparate parts of the pathname.

The solver uses the following rules to locate a file nameon the INCLUDE cards:

When the argument contains the absolute pathof the file (if it starts with "/" on UNIX or a driveletter, 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 asthe 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 filecontaining the INCLUDE statement and is NOTrelative to the directory in which the solver wasexecuted, or to the directory where the main fileis located.



Compressed input files

An input file and referenced included files can be optionally compressed using gzipcompression. 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 afile 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.



Guidelines for I/O Options and Subcase InformationEntries

The following guidelines apply to all entries in the I/O Options and Subcase Informationsections:

All input cards are limited to 80 characters per line; all characters after the 80th areskipped. SYSSETTING,CARDLENGTH may be used to change the number of charactersallowed 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 ). Whencombining 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 aspart 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 arediscouraged since they prevent moving files from one location to another, and maycause 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 replacesthe 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 configfile. 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 areseparated 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 fieldsper line and are the only entries which allow continuation.

Dollar signs, $, in any column denote comments. All characters after the dollar signuntil 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 commentlines. Blank lines are also assumed to be comment lines.



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 therange of values allowed for INTEGER*4 (usually 2**31



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 areignored. The only exception is for the INCLUDE data entry. SYSSETTING,CARDLENGTHcan 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 toother formats (shown below). Large field format is recognized by the first characterafter 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 eachfirst 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 notsignificant. Two consecutive commas define empty (blank) fields. If a comma ispresent in a line of data, it is assumed to be free format data. Continuation lines forfree format start with a blank, '+' or '*'.



Large field free format and short field free format are available, but there is no limit onthe 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 freeformat is that the latter allows for 8 data fields in each line (in positions 2 9), whilethe former allows for 4 data fields per line (similar to the large field fixed formatdetailed above).

If there is a comma within the first 10 characters in a line, the line is assumed to be infree format; otherwise, if there is an '*' immediately after the card name or acontinuation 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 theaccuracy 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 fieldof each continuation line are silently skipped when fixed format is used (other codescan 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 notaccepted. An error message is issued when a free format card contains more than 9fields. 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 signuntil the end of the line are ignored. Dollar signs can only appear in quoted filesnames.

Lines which begin with two slashes, //, or a pound symbol, #, are read as commentlines. 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 entryoptions 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 entryis 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 entryare 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 eachcontinuation card, is disregarded.

Each entry can be placed anywhere within the field. For example, blanks precedingand following an entry are ignored, except the keyword entry, which must be leftjustified in its field.



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 inthe range of values allowed for INTEGER*4 (usually 2**31



Replication of GRID data

Replication is a limited data generation capability which may be used for GRID dataonly.

Duplication of fields from the preceding GRID entry is accomplished by coding thesymbol =.

Duplication of all trailing fields from the preceding entry is accomplished by codingthe 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 fieldsor 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 datacannot 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 17 1.2 10.5 10.0 17 3456

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 bethe same and the vector components and axis locations must be the same within thesetting determined by PARAM,DUPTOL.

The removal of duplicated GRID data is performed after any GRID data is generatedusing the GRID replication feature.

For all other cards which require a unique ID, it is an error if any given ID appears morethan once. However, to facilitate application of changes resulting from optimization, itis possible to redefine content of some cards using a separate file defined with



ASSIGN,UPDATE.



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 tooverride inheritance from default settings (data selectors appearing before the firstsubcase).

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 anysubcase 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 fluidparts, but a warning is issued in such cases.

Direct Frequency and Transient solutions only allow reference of FREQ, FREQ1 andFREQ2. Modal Frequency and Transient solutions also allow reference of FREQ3, FREQ4and FREQ5.



Summary of Defaults for I/O Options

Output Format Controls

CardWhen 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 defaultsettings.

Run Controls


present


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




present


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

Analysis Output


present


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




present


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




present


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)




present


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 thedefault is NONE.

Optimization Output


present


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




present


given

SENSITIVITY NONE NOSTRESS

SENSOUT FL FL

SHAPE ALL ALL

THICKNESS ALL ALL

Other Output Controllers


present


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



Random Response


present


given

RCROSS NONE ERROR

Optimization


present


given

DGLOBAL NONE ERROR

FE Analysis


present


given

HYBDAMP NONE ERROR

RADSND no effect ERROR



I/O Options Section



@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 relatedbulk data entries to be accepted as input.



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

Default = blank

This argument only applies to the PUNCH format(.pch file) or the OUTPUT2 format (.op2 file) output

for normal modes, frequency response, andtransient subcases. It will be ignored withoutwarning if used elsewhere.

SORT1: Results for each frequency/timestep are grouped together.

SORT2: Results for each grid/element aregrouped together (See comment8).

blank: For frequency response analysis,if no grid SET is specified, SORT1is used, otherwise, SORT2 isused; for transient analysis,SORT2 is used.

format

Default = blank

HM: Results are output in HyperMeshbinary format (.res file).

H3D: Results are output in Hyper3Dformat (.h3d file).

HG: Results are output in HyperGraphpresentation format (_freq.mvwfile and _tran.mvw file) seeOUTPUT keywords HGFREQ andHGTRANS.




OPTI: Results are output in OptiStructresults format (.dispfile).

PUNCH: Results are output in Nastranpunch results format (.pch file).

OP2: Results are output in Nastranoutput2 format (.op2 file) (seecomment 11).

PLOT: Results are output in Nastranoutput2 format (.op2 file) when PARAM, POST is defined in thebulk data section.

If PARAM, POST is not defined inthe bulk data section, this formatallows the form for complexresults to be defined for XYPUNCHoutput without having otheroutput.

blank: Results are output in all activeformats for which the result isavailable.

form

Default (HM only) =COMPLEX

Default (all otherformats) = REAL

COMPLEX (HM

only), blank:

Provides a combined magnitude/phase form of complex output tothe .res file for the HM output

format.

REAL or IMAG: Provides rectangular format (realand imaginary) of complex output(See comment 9).

PHASE: Provides polar format (magnitudeand phase) of complex output. Phase output is in degrees (Seecomment 9).

BOTH (HM only): Provides both polar andrectangular formats of complexoutput.




rotations

Default = NOROTA

ROTA: Requests output of rotationalacceleration results (in additionto translational accelerationresults).

NOROTA: Rotational acceleration results arenot output.

random

No default

PSDF: Requests PSD and RMS resultsfrom random response analysis tobe output.

Only valid for the H3D format. The "RMS over Frequencies"output is at the end of theRandom results.

RMS: Requests only the RMS overFrequencies result from randomresponse analysis to be output.

Valid only for the H3D format.

peakoutput

Default = blank

PEAKOUT: If PEAKOUT is present, only the

filtered frequencies from the PEAKOUT card will be considered

for this output.

option

Default = ALL

YES, ALL, blank: Acceleration is output for allnodes.

NO, NONE: Acceleration is not output.

SID: If a set ID is given, accelerationis output only for nodes listed inthat set.



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 analysissolution sequences.

3. The form argument is only applicable for frequency response analysis. It is ignored forother 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 noformat is specified, then this output control applies to all formats defined by OUTPUT orFORMAT commands for which the result is available. See Results Output for informationon the results available and their respective formats.

6. Multiple instances of this card are allowed; if instances are conflicting, the last instancedominates.

7. For optimization, the frequency of output to a given format is controlled by the I/Ooption OUTPUT. In previous versions of OptiStruct, a combination of the I/O optionsFORMAT and RESULTS were used; this method is still supported, but not recommended asit 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 andSORT2 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 requiredformats. 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).



ASSIGN


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 theAKUSMOD fluid-structure coupling matrix.

If this is not defined, it is presumed that theAKUSMOD coupling matrix is to be found in the samedirectory as the solver input file and is given the filename, ftn.70.

Use of the AKUSMOD fluid-structure coupling matrixrequires the presence of PARAM,AKUSMOD,YES.

ENGINE SUBCASE ID filename Identifies an external file from which to readmodification commands to be applied on theintermediate RADIOSS Engine file translated in theNLGEOM, IMPDYN and EXPDYN solutions.

SUBCASE ID=0 means all NLGEOM, IMPDYN andEXPDYN subcases.

See comment 1.

EXCINP SUBCASE ID filename Identifies an external file from which to read themodal 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 participationfactors. The .INP4 file can be used along with the

original flex h3d file to recover stresses, strains,displacements, velocities, and accelerations from a




dynamic analysis run. The SUBCASE ID is used tospecify which SUBCASE the modal participationfactors should be used for.

H3DDMIG matrixname filename Identifies an external nodal flexh3d file from which toread DMIG matrices. Provides a prefix (matrixname)for the matrices contained therein, and the path toand the name of the flexh3d file. All of the matricesin the h3d file are used in the analysis by default. Ifonly some of the matrices are to be used, then usethe K2GG, M2GG, K42GG, and B2GG data to specifywhich matrices are to be used. The unreferencedmatrices will not be used in this case.

H3DCAA Load ID filename Identifies an external file that contains informationnecessary for Computational Aero-Acoustic (CAA)analysis. The information in this external file is thenused to conduct frequency response analyses. Thisfile (.h3d format) is currently generated by

AcuSolve and includes pressure values fromComputational Fluid Dynamics (CFD) Analysis ateach loading frequency. The specified LoadID canbe referenced by CAALOAD data (CAAID field) forthe application of load in a model.

H3DCDS matrixname filename Identifies an external file from which to read complexdynamic matrices for a CDS residual run. Provides aprefix (matrixname) for the matrices containedtherein 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 whichcontains the analysis recovery information fordisplacements, velocities, accelerations, stressesand strains. Provides a Flex Body ID for theinformation therein, and the path to and the nameof the flexh3d file.




MBDINP SUBCASE ID filename Identifies an external file from which to read themodal participation factors calculated byMotionSolve 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 transientanalysis run. The SUBCASE ID is used to specifywhich SUBCASE the modal participation factorsshould be used for.

MMO Model Name filename Identifies an external file to be included in a Multi-Model Optimization (MMO) run. Model Name is auser-defined label for the model, which can be usedto qualify model-specific responses referenced onthe DRESPM continuation lines of the DRESP2/DRESP3 entries.

PUNCH filename N/A Identifies an external file as the location to writeDMIG data in PUNCH format.

STARTER SUBCASE ID filename Identifies an external file from which to readmodification commands to be applied on theintermediate RADIOSS Starter file translated in theNLGEOM, IMPDYN and EXPDYN solutions.

SUBCASE ID=0 means all NLGEOM, IMPDYN andEXPDYN subcases.

See comment 1.

SIMPINP SUBCASE filename Identifies an external .unv file generated while

running a multi-body dynamic analysis in SIMPACK.The resulting CMS flexbody modal participationfactors in the .unv file can be used by OptiStruct to

recover the dynamic displacements, velocities,




accelerations, stresses and strains.

The SUBCASE ID is used to specify which SUBCASEthe modal participation factors should be used for.

UPDATE filename N/A Identifies an external file from which to read theupdated 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 inthe external file defined with ASSIGN,STARTER/ENGINE: insert and replace.

insert

Usage: Inserts content between keywords /INSERT and /ENDINS to theintermediate RADIOSS Block deck at line number LINENUM.

Syntax: /INSERT,LINENUM

Content to be inserted

/ENDINS



replace

Usage: Uses content between keywords /REPLACE and /ENDREP to replace thecontent in the intermediate RADIOSS Block deck between line numbersLINENUM1 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 andone 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,STARTERsettings should be identical.



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 DOFfor 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.



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

Default = NONE

ID of CDSMETH in bulk data section.

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 aDLOAD card for load specification.



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 spacerequirements is given.

3. Useful for large runs since the amount of memory and time required to perform thisfunction is very small.



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 individualsubcases respectively.

Format

CMDE(format_list,THRESH=thresh,RTHRESH=rthresh,TOP=topn,MODES=mset,TYPE=type)= option


format

Default = blank



thresh

No default

Specifies an absolute threshold under which resultsshould not be output.

rthresh

No default

Specifies a relative threshold under which resultsshould not be output. This value is relative to thecorresponding total modal energy.

topn

No default

Specifies that only the top N values should beoutput.




type

Default = AVERAGE

AVERAGE: The average of the energy isoutput.

AMPLITUDE: The amplitude of the energy isoutput.

PEAK: The peak energy is output. Thisis the sum of AVERAGE and

AMPLITUDE.

mset

Default = ALL

ALL: Modal energy is output for allmodes.

SID: If a set ID is given, modal energyis output only for modes listed inthat set.

TOTAL: Only the total energy is output.

option

Default = ALL

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 frequencyresponse analysis (both direct and modal methods). It is intended for use when externalCMS superelements are used.

3. Multiple formats are allowed on the same entry; these should be comma separated. If noformat is specified, then this output control applies to all formats defined by OUTPUT orFORMAT commands for which the result is available. See Results Output for informationon which results are available in which formats.


5. For optimization, the frequency of output to a given format is controlled by the I/Ooption OUTPUT. In previous version of OptiStruct, a combination of the I/O optionsFORMAT and RESULTS were used; this method is still supported, but not recommended asit does not allow different frequencies for different formats.



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 individualsubcases respectively.

Format

CMKE(format_list,THRESH=thresh,RTHRESH=rthresh,TOP=topn,MODES=mset,TYPE=type)= option


format

Default = blank



thresh

No default


rthresh

No default


topn

No default





type

Default = AVERAGE



PEAK: The peak energy is output. Thisis the sum of AVERAGE and

AMPLITUDE.

mset

Default = ALL


SID: If a set ID is given, modal energyis output only for modes listed inthat set.


option

Default = ALL

YES, ALL, blank: Modal energy is 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 responseanalysis (both direct and modal methods). It is intended for use when external CMSsuperelements are used.






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 individualsubcases respectively.

Format

CMSE(format_list,THRESH=thresh,RTHRESH=rthresh,TOP=topn,MODES=mset,TYPE=type)= option


format

Default = blank



thresh

No default


rthresh

No default


topn

No default





type

Default = AVERAGE



PEAK: The peak energy is output. This isthe sum of AVERAGE and

AMPLITUDE.

mset

Default = ALL


SID: If a set ID is given, modal energy isoutput only for modes listed in thatset.


option

Default = ALL

YES, ALL,

blank:

Modal energy is output.


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 responseanalysis (both direct and modal methods). It is intended for use when external CMSsuperelements are used.





CONTF


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 analysissubcases respectively.

Format

CONTF (format, type) = option

Type Options Description

format

Default = blank

H3D: Results are output in Hyper3D format(.h3d file). See below for type.

OPTI: The total contact force results areoutput to the .cntf file.


type

Default = ALL

ALL: All available contact results typesare output.

FORCE: Contact force results are output.

PCONT: Pressure-type contact results areoutput: pressure, open-closedstatus, contact gap opening andpenetration (see comment 2).

FRICT: Friction-related results are output:frictional traction, sliding distance,and stick-slip status (see comment2).

option



Type Options Description

NO, NONE,SID>

Default = ALL

blank: points.

NO, NONE: Contact results are not output.

SID: If a set ID is given, contact resultsare output only for grid points listedin 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 thatmay require clarification are listed below:

Open/Closed status is represented by 0.0 for Open and 1.0 for Closed. On graphicaldisplay, intermediate values may appear due to transition from open to closed acrossindividual elements,

Slip/Stick Status is represented by 0.0 for Open, 1.0 for Slip and 2.0 for Stick. Ongraphical display, intermediate values may appear due to transition of status acrossindividual elements,

Sliding Distance represents total sliding distance accumulated while the surfaces are incontact. This may be different than just the difference in displacements between thestarting and final position.

3. The calculation of contact results on both sides of contact interface involves projectionsand mappings. Therefore, a perfect match of results between two sides cannot beexpected, especially on mismatched meshes. Also, the resolution of different types ofresults (pressure versus gap opening) differs according to their respective FEAinterpolation order. Therefore, such results may appear locally inconsistent, especially onsecond order meshes and mismatched mesh densities. (Usually pressure and traction willappear 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 noformat 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 instancedominates.



CSTRAIN


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 allsubcases or individual subcases respectively.

Format

CSTRAIN (format_list,type,extras_list) = option


format

Default = blank

HM: Results are output in HyperMeshresults format (.res file).


OPTI: Results are output in OptiStructresults format (.cstr file).

PUNCH: Results are output in Nastran punchresults format (.pch file).


PLOT: Results are output in Nastranoutput2 format (.op2 file) whenPARAM, POST is defined in the bulkdata section.

blank: Results are output in all activeformats, for which the result isavailable.




type

Default = ALL

ALL, blank: All strain results are output.

PRINC: Only principal strain results areoutput.

extras

No default

MECH: Output Mechanical strain (inaddition to total strain). Thisoutput is only available for H3Dformat.

THER: Output Thermal strain (in additionto total strain). This output is onlyavailable for H3D format.

option

Default = YES

YES, ALL, blank: Results are output for all elements.

NO, NONE: Results are not output.

SID: If a set ID is given, results areoutput only for elements listed inthat set.

PSID: If a property set ID is given, resultsfor the elements referencingproperties listed in the property setare output.

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 solutionsequences.

3. The STRAIN I/O option controls the output of strain results for the homogenized

composite material.




FORMAT commands, for which the result is available. See Results Output for information

on which results are available in which formats.


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/Ooption 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 thetotal strain.


format (.op2 file).



CSTRESS


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


format

Default = blank


H3D: Results are output in Hyper3D format(.h3d file).

OPTI: Results are output in OptiStruct resultsformat (.cstr file).


OP2: Results are output in Nastran output2format (.op2 file) (see comment 10).

blank: Results are output in all activeformats, for which the result isavailable.

type

Default = ALL

ALL, blank: All stress results are output.

PRINC: Only principal stress results areoutput.

FI: Only failure index results areoutput. Failure Index results arenot available in the .pch and .op2

files.




Option

Default = YES

YES, ALL,

blank:

Results are output for allelements.


SID: If a set ID is given, results areoutput only for elements listed inthat set.

PSID: If a property set ID is given,results for the elementsreferencing properties listed in theproperty 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 solutionsequences.

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 noformat is specified, then this output control applies to all formats defined by OUTPUT orFORMAT commands, for which the result is available. See Results Output for informationon which results are available in which formats.


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 onthe 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/Ooption OUTPUT. In previous versions of OptiStruct, a combination of the I/O optionsFORMAT and RESULTS were used; this method is still supported, but not recommended as it


9. Failure Index results are not available in the .pch and .op2 files.




format (.op2 file).



DAMAGE


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 subcasesrespectively.

Format

DAMAGE (format, type) = option


format

Default = blank

H3D: Results are output in Hyper3D format (.h3d

file).

OPTI: Results are output in OptiStruct resultsformat (.fat file).

blank: Results are output in all active formats forwhich the result is available.

type

Default = SUB

SUB: Only the total damage from the fatiguesubcase is output.

LOAD: Damage contribution from each staticsubcase and total damage from the fatiguesubcases are output.

EVENT: Damage contribution from each FATEVNTand total damage from fatigue subcases areoutput.

ALL: Damage contribution from each FATEVNT,damage contribution from each staticsubcase and total damage from fatiguesubcases are all output.




option

Default = ALL

YES, ALL,blank:

Results are output for all elements.


SID: If a set ID is specified, results are outputonly for elements listed in that set.

Comments


FORMAT commands for which the result is available. See Results Output by OptiStruct for

information on which results are available in which formats.




DENSITY


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


format

Default = blank



OPTI: Results are output in OptiStructresults format (.dens file).



PLOT: Results are output in Nastranoutput2 format (.op2 file) whenPARAM, POST is defined in the bulkdata section (see comment 6).


type

Default = DES

ALL: Results are output in all simulations.

DES, blank: Results are only output in thedesign history simulations.




option

Default = YES

YES, ALL,

blank:

Results are 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 onthe 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.


6. Density results are reported as element strain energy in the .op2 file.




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


integer < SID >

No default

SID: Set identification of a DCONSTR or DCONADD bulkdata entry.

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.



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


option

Default = YES

YES, ALL, blank: .hgdata file is created.

NO: .hgdata is not created.

Comments

1. When the DESHIS command is not present, the .hgdata file is created.



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


n (Integer > 0)

No default

Identification of a DGLOBAL bulk data entry.

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-defineddesign variables from multiple starting points.



DISPLACEMENT


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,complexeigenvalue analysis) = option


sorting

Default = blank

This argument only applies to the PUNCH format (.pchfile) or the OUTPUT2 format (.op2 file) output for

normal modes, frequency response, and transientsubcases. It will be ignored without warning if usedelsewhere.

SORT1: Results for each frequency/timestep aregrouped together.

SORT2: Results for each grid/element aregrouped together (See comment 9).

blank: For frequency response analysis, if nogrid SET is specified, SORT1 is used,

otherwise, SORT2 is used; for transient

analysis, SORT2 is used.

format

Default = blank

HM: Results are output in HyperMesh resultsformat (.res file).

H3D: Results are output in Hyper3D format(.h3d file).

OPTI: Results are output in OptiStruct resultsformat (.disp file).





OP2: Results are output in Nastran output2format (.op2 file) (see comment 12).

PATRAN: Results are output in Patran format(multiple files).

HG: Results are output in HyperGraphpresentation format (_freq.mvw file and_tran.mvw file) see OUTPUT keywordsHGFREQ and HGTRANS.

APATRAN: Results are output in Alternative Patranformat (multiple files).

PLOT: Results are output in Nastran output2format (.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 formfor complex results to be defined forXYPUNCH output without having otheroutput.

blank: Results are output in all active formatsfor which the result is available.

form

Default (HMonly) = COMPLEX

Default (all otherformats) = REAL

COMPLEX (HM

only), blank:

Provides a combined magnitude/phaseform of complex output to the .res file

for the HM output format.

REAL or IMAG: Provides rectangular format (real andimaginary) of complex output (Seecomment 10).

PHASE: Provides polar format (magnitude andphase) of complex output. Phaseoutput is in degrees (See comment10).

BOTH (HM only): Provides both polar and rectangularformats of complex output.




rotations

Default =NOROTA

ROTA: Rotational displacement results areoutput. Only works with H3D and HMoutput streams. Rotations are alwaysoutput with translations for otheroutput streams.

NOROTA: Rotational displacement results are notoutput. Only works with H3D and HMoutput streams. Rotations are alwaysoutput with translations for otheroutput streams.

random

No default

PSDF: Requests PSD and RMS results fromrandom response analysis to be output.

Only valid for the H3D format. The"RMS over Frequencies" output is atthe end of the Random results.

RMS: Requests only the RMS overFrequencies result from randomresponse analysis to be output.

Valid only for the H3D format.

peakoutput

Default = Blank

PEAKOUT: If PEAKOUT is present, only the filtered

frequencies from the PEAKOUT card will

be considered for this output.

modal

Default = Blank

MODAL: If MODAL is present, displacements of

the structural modes and residualvectors are output to the PUNCH andOUTPUT2 files for modal frequencyresponse and transient analysis.




complexeigenvalueanalysis

Default = Blank

UNSTABLE: If UNSTABLE is present, the

displacement results from the unstablemodes (only) of a complex eigenvalueanalysis are output.

Blank: Displacement results are output for allmodes by default (See comment 1).

option

Default = ALL

YES, ALL, blank: Displacement is output for all grids.

NO, NONE: Displacement is not output.

SID: If a set ID is given, displacement isoutput 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 forother analysis types.

3. The forms BOTH and COMPLEX do not apply to the .frf output files.



6. For optimization, the frequency of output to a given format is controlled by the I/Ooption 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


7. Rotation results are output in radians.

8. For normal modes output, if there is USET U6 data the static residual displacementvectors associated with the USET U6, DOF are also output to the PUNCH, H3D, and

OUTPUT2 files.



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 andSORT2 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 requiredformats. Results in ASCII formats are output in the specified/requested FORM.

11. The four-letter abbreviation DISP is interchangeable with DISPLACEMENT.


format (.op2 file).



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


mtxname

Default = AX

The name given to the reduced matrices written to anexternal data file, when PARAM, EXTOUT is present inthe bulk data section.

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 aneigenvalue subcase is present in the input fileand the reduced loading matrix is only output if alinear 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.



DSA


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


TYPE

Default = DISP

The options are Displacement, Pressure, Velocity andAcceleration respectively.

PEAKOUT Default = blank If PEAKOUT is present inside the parentheses of the DSA

entry, the filtered frequencies from the PEAKOUT card

will be considered for DSA results.

PROPERTY Default = blank If the PROPERTY flag is present:This indicates that design sensitivities represent thechange in design response due to a change in designproperties (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.




SID 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 instancedominates. If this entry is defined above the first subcase then it is applied to allsubcases. 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 DESVARs), then aMASS objective function is automatically created along with responses and constraintscorresponding 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 whenthe PROPERTY argument is present in the DSA entry, so the scaling factor is not requiredin 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.

Output

Sensitivities requested viathe DSA output request

(responses areautomatically defined)

Sensitivities output from acomplete Optimization setup

(User-defined/specifiedresponses via DRESP1,

DRESP2, DRESP3)

OUTPUT, H3DSENS, USER Yes Yes

OUTPUT, H3DSENS, NOUSER Yes No

5. Design variables and their corresponding design properties must be defined in the inputdeck if sensitivity output is requested through the DSA entry.



ECHO/ECHOON/ECHOOFF

I/O Options Entry

ECHO - Output ControlECHOON - Output ControlECHOOFF - 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 bulkdata 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)


option1

Default = blank

SHORT: Only entries having less than 20instances are echoed to the .outfile.

PUNCH: Writes interpreted echo of allbulk data entries to the .echofile.

{cardname}: Only bulk data entries with thegiven {cardname} are echoed tothe .out file.




EXCEPT

{cardname}:Only bulk data entries with thegiven {cardname} are notechoed.

blank: Writes interpreted forms of allsubcase information and bulkdata entries to the .out file.

MAT, PROP,ELEM:

Adds all cards of the specifiedclass to the list for ECHO.

Option2

Default = blank

PARSED: Bulk data entries are convertedto free format (commaseparated) before echoing.

blank: Bulk data entries are echoedverbatim.

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 outputcontrol cards.

3. The cards are organized within groups, for example, optimization cards appear after modeldefinition cards, and most cards are sorted by their numerical IDs.

4. The interpreted echo may contain some cards that are automatically generated orconverted 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 beequivalent, but not identical to the input:

For most of the optional fields, the blank from input will be printed in ECHO as defaultvalue.

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 afteradjustment.

Optional continuation cards may be printed even if they did not appear in the input.



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 separatedfields) with 10 decimal digits accuracy. Note that the use of IDs larger than 99,999,999is allowed, but ECHO will not be usable in these cases as such IDs cannot be printed infixed 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 interpretedecho 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 accumulat

optistruct 13.0 reference guide

Documents