OptiStruct 13.0 Reference Guide

(1)

HyperWorks 13.0

OptiStruct Reference Guide

(2)

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

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® 2002-2014; HyperForm® 1998-2002-2014; HyperXtrude® 1999-2002-2014; Process Manager™ 2003-2002-2014; Templex™ 1990-2002-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.

(3)

OptiStruct 13.0 Reference Guide

... 1 Reference Guide ... 2 Input Data ... 3 The Bulk Data Input File

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

... 9 Guidelines for Bulk Data Entries

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

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

... 22 I/O Options Section

... 233 Subcase Information Section

... 318 Bulk Data Section

... 2160 Element Quality Check

... 2189 Material Property Check

... 2197Output Data ... 2200 List of Files Created by OptiStruct (Alphabetical)

... 2346 Results Output by OptiStruct

... 2378Legacy Data ... 2379 Previous (OS3.5) Input Format

... 2384 Setting Up Decks in OptiStruct 5.0 with OptiStruct 3.5 Objectives and

Constraints

... 2388 Previously Supported Input

(4)

Reference Guide

Input Data Output Data Legacy Data

(5)

Input Data

I/O Options Section

Subcase Information Section Bulk Data Section

Element Quality Check Material Property Check

(6)

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.

(7)

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 $

(8)

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.

(9)

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.

(10)

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.

(11)

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<x<2**31).

Integer data placed in the field reserved for real valued data is accepted and converted to a double precision.

Character entries longer than eight characters are silently truncated, except for the title strings and file names. All character strings, except user-provided labels, titles, and file names, are case insensitive (can be typed in lower or upper case). File names are always case sensitive, except with Windows, where the operating system does not care for case.

Abbreviated keyword entries are accepted and recognized properly using the first four characters. When a four character abbreviation is not unique, the full length keyword has to appear on the data line (but only the first eight characters are used if the keyword is longer).

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.

(12)

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 '*'.

(13)

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.

(14)

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<x<2**31).

Integer data placed in the field reserved for real valued data is accepted and converted to a double precision. However, certain fields have alternate functions where the nature of the number entered indicates the desired function; one function requires an integer while the other requires a real number – in this case, no conversion is performed.

Real valued data can be entered without exponent part, with exponent part and

explicit letter ‘E’ or ‘D’ or with exponent part starting with a sign (without ‘E’ or ‘D’). All real values are stored internally as double precision data (64-bit REAL*8) without regards to which format was used to enter them. Following are valid examples of input for real valued data:

1. 0.1 .1 +.1 -0.1 1e5 1e+5 1+5 1.0E-5 .1d-5 .00001-05

Character entries longer than eight characters are silently truncated in large field and free field formats, with the exception of file names on the INCLUDE entry (see

documentation for INCLUDE entry) and the “LABEL’ field on DESVAR, DRESP1, DRESP2, DRESP3, and DTABLE entries (allows up to 16 characters).

Continuation lines do not have to be in the same format as the parent entries. It is allowed to mix lines in different formats within a single bulk data card.

Invisible tab characters are equivalent to the number of spaces needed to advance to the nearest tab stop. Tab stops are placed at the beginning of each eight-character field. Use the SYSSETTINGS,TABSTOPS option to change this value, for example, to tab stops at 4-character fields.

(15)

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

(16)

(17)

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.

(18)

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

present

given

CHECK no effect active (has no arguments)

CMSMETH no effect no effect

RESTART no effect <prefix of filename>.sh

SYSSETTING no effect no effect

@HyperForm no effect active (has no arguments)

(19)

Card When card is not 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

(20)

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

(21)

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

(22)

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

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

(23)

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

(24)

Random Response

present

given

RCROSS NONE ERROR

Optimization

present

given

DGLOBAL NONE ERROR

FE Analysis

present

given

HYBDAMP NONE ERROR

(25)

(26)

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

(27)

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

format <HM, H3D, HG, OPTI, PUNCH, OP2, PLOT, blank>

Default = blank

HM: Results are output in HyperMesh

binary format (.res file).

H3D: Results are output in Hyper3D

format (.h3d file).

HG: Results are output in HyperGraph

presentation format (_freq.mvw file and _tran.mvw file) – see OUTPUT keywords HGFREQ and HGTRANS.

(28)

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.

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

form <COMPLEX, REAL,

IMAG, PHASE, BOTH>

Default (HM only) = COMPLEX

Default (all other formats) = REAL

COMPLEX (HM only), blank:

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

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

PHASE: 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.

(29)

rotations <ROTA, NOROTA> Default = NOROTA

ROTA: Requests output of rotational

acceleration results (in addition to translational acceleration results).

NOROTA: Rotational acceleration results are not output.

random <PSDF, RMS> No default

PSDF: Requests PSD and RMS results

from random response analysis to be output.

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> Default = blank

PEAKOUT: If PEAKOUT is present, only the filtered frequencies from the PEAKOUT card will be considered for this output.

option <YES, ALL, NO, NONE, SID> Default = ALL

YES, ALL, blank: Acceleration is output for all nodes.

NO, NONE: Acceleration is not output.

SID: If a set ID is given, acceleration is output only for nodes listed in that set.

(30)

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 (<Result Keyword> (SORT2, OUTPUT2, … .)), the results are written by OptiStruct into the .op2 file in SORT2 format, but when the .op2 file is imported into HyperView, the results in SORT2 format are not recognized. Therefore, the SORT1 option is recommended for results output in OUTPUT2 format and SORT2 option is recommended for results output in PUNCH format.

9. Results in binary format (.h3d or .op2) are always output in PHASE/MAG form, regardless of the options specified in the FORM field. The corresponding post-processors

(HyperView/HyperGraph) can easily convert the PHASE/MAG format to the required formats. Results in ASCII formats are output in the specified/requested FORM. 10. The abbreviations ACCE and ACCEL are interchangeable with ACCELERATION.

11. format=OUTPUT2 can also be used to request results to be output in the Nastran output2 format (.op2 file).

(31)

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

(32)

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.

(33)

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 Multi-Model Optimization (MMO) run. “Multi-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 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,

(34)

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

(35)

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.

(36)

AUTOSPC

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.

(37)

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 <INTEGER> 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 a DLOAD card for load specification.

(38)

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.

(39)

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

format <H3D, blank> Default = blank

format (.h3d file).

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.

(40)

type <AVERAGE,

AMPLITUDE, PEAK> Default = AVERAGE

AVERAGE: The average of the energy is output.

AMPLITUDE: The amplitude of the energy is output.

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

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.

(41)

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

format (.h3d file).

(42)

type <AVERAGE,

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.

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

(43)

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

format (.h3d file).

(44)

type <AVERAGE,

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.

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.

(45)

(46)

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, OPTI, blank>

Default = blank

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.

type <ALL,FORCE, PCONT,FRICT> Default = ALL

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

(47)

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

(48)

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

format <HM, H3D, OPTI, PUNCH, OP2, PLOT, blank>

Default = blank

results format (.res file).

format (.h3d file).

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

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

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.

(49)

type <ALL, PRINC> Default = ALL

ALL, blank: All strain results are output.

PRINC: Only principal strain results are output.

extras <MECH, THER> No default

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.

option <YES, ALL, NO, NONE, SID, PSID> 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 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 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.

(50)

4. Multiple formats are allowed on the same entry; these should be comma separated. If no format is specified, then this output control applies to all formats defined by OUTPUT or FORMAT commands, for which the result is available. See Results Output for information on which results are available in which formats.

6. 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).

(51)

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

format <HM, H3D, OPTI, PUNCH,OP2, blank> Default = blank

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

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 <ALL, PRINC, FI> Default = ALL

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.

(52)

Option <YES, ALL, NO, NONE, SID, PSID> Default = YES

YES, ALL, blank:

Results are output for all elements.

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.

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.

(53)

(54)

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

format <H3D, OPTI, blank>

Default = blank

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

type <SUB, LOAD,

EVENT, ALL> Default = SUB

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.

(55)

option <YES, ALL, NO, NONE, SID> Default = ALL

YES, ALL, blank:

Results are output for all elements.

SID: If a set ID is specified, results are output only for elements listed in that set. 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.

(56)

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

format <HM, H3D, OPTI, PUNCH, OP2, PLOT, blank>

Default = blank

results format (.res file).

format (.h3d file).

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

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.

type <ALL, DES> Default = DES

ALL: Results are output in all simulations.

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

(57)

Default = YES

YES, ALL, blank:

Results are output

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.

(58)

DESGLB

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 bulk data 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.

(59)

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 <YES, ALL, NO> Default = YES

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

NO: .hgdata is not created.

Comments

(60)

DGLOBAL

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

(61)

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

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

format <HM, H3D, OPTI, PUNCH,OP2, PATRAN, HG, APATRAN, PLOT, blank> Default = blank

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

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