You are on page 1of 2412

HyperWorks 13.

OptiStruct Reference Guide

HyperWorks is a division of Altair altairhyperworks.com


Altair Engineering Support Contact Information
Web site www.altairhyperworks.com

Location Telephone e-mail

Australia 64.9.413.7981 anzsupport@altair.com

Brazil 55.11.3884.0414 br_support@altair.com

Canada 416.447.6463 support@altairengineering.ca

China 86.400.619.6186 support@altair.com.cn

France 33.1.4133.0992 francesupport@altair.com

Germany 49.7031.6208.22 hwsupport@altair.de

India 91.80. 6629.4500 support@india.altair.com


1.800.425.0234 (toll free)

Italy 39.800.905.595 support@altairengineering.it

Japan 81.3.5396.2881 support@altairjp.co.jp

Korea 82.70.4050.9200 support@altair.co.kr

Mexico 55.56.58.68.08 mx-support@altair.com

New Zealand 64.9.413.7981 anzsupport@altair.com

North America 248.614.2425 hwsupport@altair.com

Scandinavia 46.46.460.2828 support@altair.se

United Kingdom 01926.468.600 support@uk.altair.com

In addition, the following countries have resellers for Altair Engineering: Colombia, Czech Republic, Ecuador, Israel, Russia,
Netherlands, Turkey, Poland, Singapore, Vietnam, Indonesia
Official offices with resellers: Canada, China, France, Germany, India, Malaysia, Italy, Japan, Korea, Spain, Taiwan, United
Kingdom, USA

Copyright© Altair Engineering Inc. All Rights Reserved for:


HyperMesh® 1990-2014; HyperCrash® 2001-2014; OptiStruct® 1996-2014; RADIOSS®1986-2014; HyperView®1999-2014;
HyperView Player® 2001-2014; HyperStudy® 1999-2014; HyperGraph®1995-2014; MotionView® 1993-2014; MotionSolve® 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; SimLab®™2004-2014 and Virtual Wind Tunnel™ 2012-2014.

In addition to HyperWorks® trademarks noted above, Display Manager™, Simulation Manager™, Compute Manager™, PBS™,
PBSWorks™, PBS GridWorks®, PBS Professional®, PBS Analytics™, PBS Desktop™, PBS Portal™, PBS Application Services™,
e-BioChem™, e-Compute™ and e-Render™ are trademarks of ALTAIR ENGINEERING INC.

Altair trademarks are protected under U.S. and international laws and treaties. Copyright© 1994-2014. Additionally, Altair software
is protected under patent #6,859,792 and other patents pending. All other marks are the property of their respective owners.

ALTAIR ENGINEERING INC. Proprietary and Confidential. Contains Trade Secret Information. Not for use or disclosure outside of
ALTAIR and its licensed clients. Information contained inHyperWorks® shall not be decompiled, disassembled, or “unlocked”,
reverse translated, reverse engineered, or publicly displayed or publicly performed in any manner. Usage of the software is only as
explicitly permitted in the end user software license agreement.

Copyright notice does not imply publication


OptiStruct 13.0 Reference Guide

Reference Guide
........................................................................................................................................... 1
Input Data
............................................................................................................................................... 2
The Bulk Data Input File
................................................................................................................................... 3
Guidelines for I/O Options and Subcase Information Entries
................................................................................................................................... 7
Guidelines for Bulk Data Entries
................................................................................................................................... 9
Solution Sequences - Data Selectors (Table)
................................................................................................................................... 14
Summary of Defaults for I/O Options
................................................................................................................................... 15
I/O Options Section
................................................................................................................................... 22
Subcase Information Section
................................................................................................................................... 233
Bulk...................................................................................................................................
Data Section 318
Element Quality Check
................................................................................................................................... 2160
Material Property Check
................................................................................................................................... 2189
Output Data
............................................................................................................................................... 2197
List of Files Created by OptiStruct (Alphabetical)
................................................................................................................................... 2200
Results Output by OptiStruct
................................................................................................................................... 2346
Legacy Data
............................................................................................................................................... 2378
Previous (OS3.5) Input Format
................................................................................................................................... 2379
Setting Up Decks in OptiStruct 5.0 with OptiStruct 3.5 Objectives and
Constraints
................................................................................................................................... 2384
Previously Supported Input
................................................................................................................................... 2388

i OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Reference Guide
Input Data
Output Data
Legacy Data

Altair Engineering OptiStruct 13.0 Reference Guide 1

Proprietary Information of Altair Engineering


Input Data
I/O Options Section
Subcase Information Section
Bulk Data Section
Element Quality Check
Material Property Check

2 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


The Bulk Data Input File

The input file in OptiStruct is composed of three distinct sections:

The I/O Options Section


The Subcase Information Section
The Bulk Data Section
The I/O Options Section controls the overall running of the analysis or optimization. It
controls the type, format, and frequency of the output, the type of run (check, analysis,
super element generation, optimization or optimization restart), and the location and names of
input, output, and scratch files.

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

The Bulk Data Section contains all finite element data for the finite element model, such as
grids, elements, properties, materials, loads and boundary conditions, and coordinates
systems. For optimization, it contains the design variables, responses, and constraint
definitions. The bulk data section begins with the BEGIN BULK statement.

Altair Engineering OptiStruct 13.0 Reference Guide 3

Proprietary Information of Altair Engineering


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

The solver reads all files and positions the lines of the included file at the location of the
INCLUDE statement in the input.fem file. An echo of the input.fem file as read by
OptiStruct would be:

$
Subcase 1
SPC = 1
Load = 2
$
Subcase 2
SPC = 1
Load = 3
$
BEGIN BULK
$

4 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Two-File Setup

This setup is obsolete; the one-file or multiple-file setups are recommended.

The two-file setup separates the control data (I/O Options section and Subcase Information
section) from the model data (Bulk Data section). If the input file does not contain a BEGIN
BULK statement, the solver attempts to read the model data from another file:

If the INFILE card is present in the I/O Options section, the argument given on this
card is the name of the file that contains the model data.
If the INFILE card is not present in the I/O Options section, and the input file does not
have the extension .fem, the name of the file containing the model data will be
constructed from the input file by replacing the extension with .fem.

The two-file setup allows you to perform runs using multiple control data files and a single
model file and vice versa. It is recommended that the .parm extension be used for control
data files and the .fem extension be used for model data files.

Notes: The format of the input sections in OptiStruct


are similar to those of the Nastran format.

File names specified on INCLUDE and other cards


(RESTART, EIGVNAME, LOADLIB, OUTFILE, TMPDIR,
ASSIGN) can be arbitrary file names with optional
paths appropriate to the operating system (Windows
or UNIX). They may be enclosed in quotes (double or
single quotes can be used), and either forward slash
(/) or back slash (\) characters can be used to
separate parts of the pathname.

The solver uses the following rules to locate a file name


on the INCLUDE cards:

When the argument contains the absolute path


of the file (if it starts with "/" on UNIX or a drive
letter, such as "D:", on Windows, for example),
the file at the given location is used.
When only the file name is given (without the path),
the file has to be located in the same directory as
the file containing the INCLUDE statement.
When the argument contains a relative path
(../filename or sub/filename, for example), it
is located in the directory relative to the file
containing the INCLUDE statement and is NOT
relative to the directory in which the solver was
executed, or to the directory where the main file
is located.

Altair Engineering OptiStruct 13.0 Reference Guide 5

Proprietary Information of Altair Engineering


Compressed input files

An input file and referenced included files can be optionally compressed using gzip
compression. A compressed file has to have the extension .gz appended to the file name.
Valid example file names are: input.fem.gz, input.gz, and input.dat.gz. Compressed files
can be mixed with plain ASCII files. The INCLUDE card does not have to be modified when a
file is compressed. For example, if the card INCLUDE infile.dat were present, the reader
would search for infile.dat and continue on to search for the compressed file,
infile.dat.gz, if not found. Other input files (such as RESTART, ASSIGN) cannot be
compressed.

6 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Guidelines for I/O Options and Subcase Information
Entries

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

All input cards are limited to 80 characters per line; all characters after the 80th are
skipped. SYSSETTING,CARDLENGTH may be used to change the number of characters
allowed in each line.
Cards which require a file name (OUTFILE, RESTART, INCLUDE, LOADLIB, TMPDIR,
EIGVNAME, ASSIGN) can contain up to 200 characters in a single line. Alternatively,
the file name may be continued in several lines if it is enclosed in quotes (" or ‘). When
combining continuation lines, all trailing and leading blanks in each line are omitted.
Other blanks, including all blanks between the quote and file name, are considered as
part of the file name.
File names can contain an absolute or relative path. Forward slash (/) or back slash
(\) characters can be used to separate parts of a path name. Absolute paths are
discouraged since they prevent moving files from one location to another, and may
cause unexpected failures, as in PBS or a similar batch environment.
Windows style file names, starting with the drive letter (for example: D:/users/mbg/
workarea), can be used on UNIX/Linux only when environment variable(s)
DOS_DRIVE_# are defined. Content of the respective environment variable replaces
the first two letters (‘D:’) in the file name, and the expanded file name must fit within
200 characters. Alternatively, the DOS_DRIVE_# option can be specified in the config
file. UNC format (//server/path/filename) is not accepted.

Each line of data contains up to ten fields in free format. Entries in the free format are
separated by any number of characters from the following set:
(blank)

, (comma)

File names and titles (TITLE, SUBTITLE, LABEL) are exceptions to this rule.

P2G / K2GG / M2GG / B2GG entries allow more than ten fields per line (up to
CARDLENGTH limit).
GROUNDCHECK / WEIGHTCHECK / EIGVRETRIEVE / XYPLOT allow more than ten fields
per line and are the only entries which allow continuation.
Dollar signs, $, in any column denote comments. All characters after the dollar sign
until the end of the line are ignored. A dollar sign can be a part of a file name or title,
but the full title or file name must be enclosed in quotes (" or ‘) in such cases.
Lines which begin with two slashes, //, or a pound symbol, #, are read as comment
lines. Blank lines are also assumed to be comment lines.

Altair Engineering OptiStruct 13.0 Reference Guide 7

Proprietary Information of Altair Engineering


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.

8 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Guidelines for Bulk Data Entries

The following guidelines apply to all entries in the bulk data section:

Data may contain 80 characters per line at most. All characters after the 80th are
ignored. The only exception is for the INCLUDE data entry. SYSSETTING,CARDLENGTH
can be used to change the number of characters allowed in each line.
Each line of data contains up to nine fields in one of the three accepted formats:

Fixed Format

Each field consists of eight characters (shown below).

Large Field Fixed Format

Each field consists of 16 characters; two consecutive lines form nine fields, similar to
other formats (shown below). Large field format is recognized by the first character
after the keyword, or by the first character in each continuation line, which must be
‘*’. The second line (‘half line’), if present, must also contain ‘*’ in the first column.
The first and last field in each half line is eight characters long. The last field on each
first half-line and the first field on each second half-line are ignored.

The following examples show the same card in fixed and large field formats:

Free Format

Fields are separated by commas; blank characters surrounding commas are not
significant. Two consecutive commas define empty (blank) fields. If a comma is
present in a line of data, it is assumed to be free format data. Continuation lines for
free format start with a blank, '+' or '*'.

Altair Engineering OptiStruct 13.0 Reference Guide 9

Proprietary Information of Altair Engineering


Large field free format and short field free format are available, but there is no limit on
the length of entries, and all floating numbers are read and stored with full precision
(64-bit REAL*8) in either case. The only difference between large and short free
format is that the latter allows for 8 data fields in each line (in positions 2 – 9), while
the former allows for 4 data fields per line (similar to the large field fixed format
detailed above).

If there is a comma within the first 10 characters in a line, the line is assumed to be in
free format; otherwise, if there is an '*' immediately after the card name or a
continuation line starts with '*', then the line is accepted as large field fixed format.
All other lines are read in as fixed format.
Use of fixed format limits the range of integer data (-9,999,999 .. 99,999,999) and the
accuracy of floating point numbers, but does not influence the internal storage of data
– in particular all floating point numbers are always read and stored with full precision
(64-bit REAL*8).

Bulk data is always limited to 9 fields per line. Content of 10th field and the first field
of each continuation line are silently skipped when fixed format is used (other codes
can use these fields for special purposes, such as to mark matching continuation lines).
Extensions of free format (which may allow more than 9 fields in a line) are not
accepted. An error message is issued when a free format card contains more than 9
fields. This error can be disabled (changed to non-fatal warning) through the use of
SYSSETING,SKIP10FIELD.
Dollar signs, $, in any column denote comments. All characters after the dollar sign
until the end of the line are ignored. Dollar signs can only appear in quoted files
names.
Lines which begin with two slashes, //, or a pound symbol, #, are read as comment
lines. Blank lines are also assumed to be comment lines.
The full keyword of each bulk data entry must be given starting from the first column.
Abbreviated keywords are not allowed.
The format of most bulk data entries is similar to that for Nastran. Not all entry
options are supported by OptiStruct. Consult the list of fields and options supported.
Continuation entries must follow the parent entries. If the first character of any entry
is either a blank, a ‘+’, or an ‘*’, it is treated as a continuation of the previous entry.
If the entire line is blank, it is treated as a comment line.
An ENDDATA entry or end-of-file denotes end of data. Lines after the ENDDATA entry
are ignored.
All Bulk Data entries must appear after the BEGIN BULK statement in the input data.
The content of the tenth field in each card, and that of the first field in each
continuation card, is disregarded.
Each entry can be placed anywhere within the field. For example, blanks preceding
and following an entry are ignored, except the keyword entry, which must be left
justified in its field.

10 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


No entry can contain blanks within the data.

Character entries (labels) must start with a letter.


Numeric entries must start with a digit, ‘+’ or ‘-‘.
Integer entries may not contain a decimal point or an exponent part, and must fit in
the range of values allowed for INTEGER*4 (usually –2**31<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.

Altair Engineering OptiStruct 13.0 Reference Guide 11

Proprietary Information of Altair Engineering


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

12 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


ASSIGN,UPDATE.

Altair Engineering OptiStruct 13.0 Reference Guide 13

Proprietary Information of Altair Engineering


Solution Sequences - Data Selectors (Table)

Key:

R Required Data Selector.

O Optional Data Selector. All optional data selectors can be set equal to zero in order to
override inheritance from default settings (data selectors appearing before the first
subcase).

E Either one of the selectors marked E are required, both are optional.

A Exactly one selector marked A is required.

Data selector may be defined above the first subcase, in which case it is used in any
subcase where it is allowed (as long as it has not been defined specifically).

** METHOD(Fluid) and SDAMPING(Fluid) are allowed when the model does not contain fluid
parts, but a warning is issued in such cases.

‡ Direct Frequency and Transient solutions only allow reference of FREQ, FREQ1 and
FREQ2. Modal Frequency and Transient solutions also allow reference of FREQ3, FREQ4
and FREQ5.

14 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Summary of Defaults for I/O Options

Output Format Controls

When card is present,


When card is not
Card but no argument is
present
given

FORMAT HM & H3D* error

OUTPUT no effect no effect

*The OptiStruct Configuration File may be used to change the default


settings.

Run Controls

When card is present,


When card is not
Card but no argument is
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)

File Names, Headers, and Locations

Altair Engineering OptiStruct 13.0 Reference Guide 15

Proprietary Information of Altair Engineering


When card is present,
When card is not
Card but no argument is
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

When card is present,


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

16 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


When card is present,
When card is not
Card but no argument is
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

Altair Engineering OptiStruct 13.0 Reference Guide 17

Proprietary Information of Altair Engineering


When card is present,
When card is not
Card but no argument is
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)

18 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


When card is present,
When card is not
Card but no argument is
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 the


default is NONE.

Optimization Output

When card is present,


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

Altair Engineering OptiStruct 13.0 Reference Guide 19

Proprietary Information of Altair Engineering


When card is present,
When card is not
Card but no argument is
present
given

SENSITIVITY NONE NOSTRESS

SENSOUT FL FL

SHAPE ALL ALL

THICKNESS ALL ALL

Other Output Controllers

When card is present,


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

20 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Random Response

When card is present,


When card is not
Card but no argument is
present
given

RCROSS NONE ERROR

Optimization

When card is present,


When card is not
Card but no argument is
present
given

DGLOBAL NONE ERROR

FE Analysis

When card is present,


When card is not
Card but no argument is
present
given

HYBDAMP NONE ERROR

RADSND no effect ERROR

Altair Engineering OptiStruct 13.0 Reference Guide 21

Proprietary Information of Altair Engineering


I/O Options Section

22 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


@HYPERFORM

I/O Options Entry

@HyperForm - One-step Stamping Simulation Run

Description

The @HyperForm statement indicates an input file for one-step stamping simulation written
from HyperForm.

Format

@HyperForm

Comments

1. Must be present as the first line of the input file to allow the one-step stamping related
bulk data entries to be accepted as input.

Altair Engineering OptiStruct 13.0 Reference Guide 23

Proprietary Information of Altair Engineering


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> This argument only applies to the PUNCH format
(.pch file) or the OUTPUT2 format (.op2 file) output
Default = blank for normal modes, frequency response, and
transient subcases. It will be ignored without
warning if used elsewhere.

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, HM: Results are output in HyperMesh
PUNCH, OP2, PLOT, binary format (.res file).
blank>
H3D: Results are output in Hyper3D
Default = blank format (.h3d file).

HG: Results are output in HyperGraph


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

24 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

OPTI: Results are output in OptiStruct


results format (.dispfile).

PUNCH: Results are output in Nastran


punch results format (.pch file).

OP2: Results are output in Nastran


output2 format (.op2 file) (see
comment 11).

PLOT: Results are output in Nastran


output2 format (.op2 file) when
PARAM, POST is defined in the
bulk data section.

If PARAM, POST is not defined in


the bulk data section, this format
allows the form for complex
results to be defined for XYPUNCH
output without having other
output.

blank: Results are output in all active


formats for which the result is
available.

form <COMPLEX, REAL, COMPLEX (HM Provides a combined magnitude/


IMAG, PHASE, only), blank: phase form of complex output to
BOTH> the .res file for the HM output
format.
Default (HM only) =
COMPLEX REAL or IMAG: Provides rectangular format (real
and imaginary) of complex output
Default (all other (See comment 9).
formats) = REAL
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.

Altair Engineering OptiStruct 13.0 Reference Guide 25

Proprietary Information of Altair Engineering


Argument Options Description

rotations <ROTA, NOROTA> ROTA: Requests output of rotational


acceleration results (in addition
Default = NOROTA
to translational acceleration
results).

NOROTA: Rotational acceleration results are


not output.

random <PSDF, RMS> PSDF: Requests PSD and RMS results


from random response analysis to
No default 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> PEAKOUT: If PEAKOUT is present, only the


filtered frequencies from the
Default = blank PEAKOUT card will be considered
for this output.

option <YES, ALL, NO, YES, ALL, blank: Acceleration is output for all
NONE, SID> nodes.

Default = ALL NO, NONE: Acceleration is not output.

SID: If a set ID is given, acceleration


is output only for nodes listed in
that set.

26 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. When the ACCELERATION command is not present, acceleration results are not output.

2. Acceleration output is only available for frequency response and transient analysis
solution sequences.

3. The form argument is only applicable for frequency response analysis. It is ignored for
other analysis types.

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

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

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

7. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as
it does not allow different frequencies for different formats.

8. In general, HyperView does not recognize the SORT2 format for results from the .op2 file.
When results are output only in SORT2 format (<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).

Altair Engineering OptiStruct 13.0 Reference Guide 27

Proprietary Information of Altair Engineering


ASSIGN

I/O Options and Subcase Information Entry

ASSIGN – Input Definition

Description

The ASSIGN command can be used in the I/O Options section to identify external files and
their contents.

Format

ASSIGN, type, option1, option2

Type Option1 Option 2 Description

AKUSMOD filename N/A Identifies an external file from which to read the
AKUSMOD fluid-structure coupling matrix.

If this is not defined, it is presumed that the


AKUSMOD coupling matrix is to be found in the same
directory as the solver input file and is given the file
name, ftn.70.

Use of the AKUSMOD fluid-structure coupling matrix


requires the presence of PARAM,AKUSMOD,YES.

ENGINE SUBCASE ID filename Identifies an external file from which to read


modification commands to be applied on the
intermediate RADIOSS Engine file translated in the
NLGEOM, IMPDYN and EXPDYN solutions.

SUBCASE ID=0 means all NLGEOM, IMPDYN and


EXPDYN subcases.

See comment 1.

EXCINP SUBCASE ID filename Identifies an external file from which to read the
modal participation factors calculated by AVL/
EXCITE for both transient and FRF residual runs.

While running an AVL/EXCITE analysis, a .INP4 file is


generated that contains the modal participation
factors. The .INP4 file can be used along with the
original flex h3d file to recover stresses, strains,
displacements, velocities, and accelerations from a

28 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Type Option1 Option 2 Description

dynamic analysis run. The SUBCASE ID is used to


specify which SUBCASE the modal participation
factors should be used for.

H3DDMIG matrixname filename Identifies an external nodal flexh3d file from which to
read DMIG matrices. Provides a prefix (matrixname)
for the matrices contained therein, and the path to
and the name of the flexh3d file. All of the matrices
in the h3d file are used in the analysis by default. If
only some of the matrices are to be used, then use
the K2GG, M2GG, K42GG, and B2GG data to specify
which matrices are to be used. The unreferenced
matrices will not be used in this case.

H3DCAA Load ID filename Identifies an external file that contains information


necessary for Computational Aero-Acoustic (CAA)
analysis. The information in this external file is then
used to conduct frequency response analyses. This
file (.h3d format) is currently generated by
AcuSolve and includes pressure values from
Computational Fluid Dynamics (CFD) Analysis at
each loading frequency. The specified “LoadID” can
be referenced by CAALOAD data (CAAID field) for
the application of load in a model.

H3DCDS matrixname filename Identifies an external file from which to read complex
dynamic matrices for a CDS residual run. Provides a
prefix (matrixname) for the matrices contained
therein and the path to and the name of the
filename_CDS.h3d file. All of the matrices in the
filename_CDS.h3d file are used in the analysis.

H3DMBD Flex Body ID filename Identifies an external nodal flexh3d file which
contains the analysis recovery information for
displacements, velocities, accelerations, stresses
and strains. Provides a Flex Body ID for the
information therein, and the path to and the name
of the flexh3d file.

Altair Engineering OptiStruct 13.0 Reference Guide 29

Proprietary Information of Altair Engineering


Type Option1 Option 2 Description

MBDINP SUBCASE ID filename Identifies an external file from which to read the
modal participation factors calculated by
MotionSolve for transient analysis.

While running MotionSolve, an .mrf file is generated


that contains the modal participation factors. The
.mrf file can be used along with the original flex h3d
file to recover stresses, strains, displacements,
velocities, and accelerations during a transient
analysis run. The SUBCASE ID is used to specify
which SUBCASE the modal participation factors
should be used for.

MMO Model Name filename Identifies an external file to be included in a Multi-


Model Optimization (MMO) run. “Model Name” is a
user-defined label for the model, which can be used
to qualify model-specific responses referenced on
the DRESPM continuation lines of the DRESP2/
DRESP3 entries.

PUNCH filename N/A Identifies an external file as the location to write


DMIG data in PUNCH format.

STARTER SUBCASE ID filename Identifies an external file from which to read


modification commands to be applied on the
intermediate RADIOSS Starter file translated in the
NLGEOM, IMPDYN and EXPDYN solutions.

SUBCASE ID=0 means all NLGEOM, IMPDYN and


EXPDYN subcases.

See comment 1.

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

30 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Type Option1 Option 2 Description

accelerations, stresses and strains.

The SUBCASE ID is used to specify which SUBCASE


the modal participation factors should be used for.

UPDATE filename N/A Identifies an external file from which to read the
updated cards after an optimization run.

Currently, the following cards are supported:

GRID

MAT1, MAT2, MAT3, MAT4, MAT5, MAT8, MAT9,


MAT10

PSHELL, PSOLID, PBAR, PBEAM, PELAS, PVISC,


PDAMP, PBARL, PBEAML, PMASS, PROD, PBUSH,
PBUSH1D, PACABS

PAABSF, PWELD, PCOMPP, PSHEAR, PTUBE

CTRIA3, CQUAD4, CTRIA6, CQUAD8

CONM2

Examples

ASSIGN, PUNCH, C:\CMS\h3ddmig.pch


ASSIGN, H3DDMIG, AX, C:\CMS\h3ddmig.h3d

Comments

1. For geometric nonlinear subcases, two types of modification commands are available in
the external file defined with ASSIGN,STARTER/ENGINE: insert and replace.

insert

Usage: Inserts content between keywords /INSERT and /ENDINS to the


intermediate RADIOSS Block deck at line number LINENUM.

Syntax: /INSERT,LINENUM

Content to be inserted
/ENDINS

Altair Engineering OptiStruct 13.0 Reference Guide 31

Proprietary Information of Altair Engineering


replace

Usage: Uses content between keywords /REPLACE and /ENDREP to replace the
content in the intermediate RADIOSS Block deck between line numbers
LINENUM1 and LINENUM2.

Syntax: /REPLACE,LINENUM1, LIMENUM2

Content as replacement

/ENDREP

2. The SEINTPNT subcase information entry can only be used to convert interior super
element grid points in .h3d files referenced by ASSIGN, H3DDMIG.

Limitations:

Each subcase can only be defined with a maximum of one ASSIGN,STARTER entry and
one ASSIGN,ENGINE entry.
In the external file, the line numbers (LINENUM after /INSERT, and LINENUM1 after /
REPLACE) should be input in increasing order.
For subcases in the same load sequence (defined by CNTNLSUB), ASSIGN,STARTER
settings should be identical.

32 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


AUTOSPC

I/O Options Entry

AUTOSPC - Automatically Constrains Stiffness Singularities

Description

The AUTOSPC command requests that stiffness singularities and near singularities be
constrained automatically with single point constraints.

Format

Argument Description

PRINT Enables the printout of a summary table of singularities.

(Default)

NOPRINT Disables the printout of a summary table of singularities.

PUNCH Creates a PUNCH file with SPC data for each AUTOSPC DOF
for each SUBCASE. The SPC SID is the SUBCASE ID.

NOPUNCH Do not create a PUNCH file with SPC data for each
AUTOSPC DOF for each SUBCASE.

(Default)

Comments

1. YES is the default.

2. Replaces parameters PARAM,AUTOSPC and PARAM,PRGPST.

Altair Engineering OptiStruct 13.0 Reference Guide 33

Proprietary Information of Altair Engineering


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> ID of CDSMETH in bulk data section.

Default = NONE

Comments

1. If CDSMETH is specified, only one subcase is allowed. The data corresponding to


component dynamic synthesis will be stored in an H3D file with the name,
filename_CDS.h3d.

2. The subcase must be a modal frequency response subcase, except it does not require a
DLOAD card for load specification.

34 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHECK

I/O Options Entry

CHECK - Run Control

Description

The CHECK command can be used in the I/O Options section to request that only a model
check be performed.

Format
CHECK

Comments

1. Perform model check only.

2. If this keyword is present, only the subroutines which read in the input files are executed.
A report that provides information on errors in the model and the memory and disk space
requirements is given.

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

Altair Engineering OptiStruct 13.0 Reference Guide 35

Proprietary Information of Altair Engineering


CMDE

I/O Options Entry

CMDE - Output Request

Description

The CMDE command can be used above the first SUBCASE or within a SUBCASE definition to
request component modal synthesis damping energy output for all subcases or individual
subcases respectively.

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

Argument Options Description

format <H3D, blank> H3D: Results are output in Hyper3D


format (.h3d file).
Default = blank
blank: Results are output in all active
formats for which the result is
available.

thresh <Real> Specifies an absolute threshold under which results


should not be output.
No default

rthresh <Real> Specifies a relative threshold under which results


should not be output. This value is relative to the
No default corresponding total modal energy.

topn <Integer> Specifies that only the top N values should be


output.
No default

36 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

type <AVERAGE, AVERAGE: The average of the energy is


AMPLITUDE, PEAK> output.

Default = AVERAGE AMPLITUDE: The amplitude of the energy is


output.

PEAK: The peak energy is output. This


is the sum of AVERAGE and
AMPLITUDE.

mset <ALL, SID, TOTAL> ALL: Modal energy is output for all
modes.
Default = ALL
SID: If a set ID is given, modal energy
is output only for modes listed in
that set.

TOTAL: Only the total energy is output.

option <YES, ALL, NO, YES, ALL, blank: Modal energy is output.
NONE>
Default = ALL
NO, NONE: Modal energy is not output.

Comments

1. When the CMDE command is not present, component modal synthesis damping energy is
not output.

2. Component modal synthesis damping energy output is only available for frequency
response analysis (both direct and modal methods). It is intended for use when external
CMS superelements are used.

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

4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

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

Altair Engineering OptiStruct 13.0 Reference Guide 37

Proprietary Information of Altair Engineering


CMKE

I/O Options Entry

CMKE - Output Request

Description

The CMKE command can be used above the first SUBCASE or within a SUBCASE definition to
request component modal synthesis kinetic energy output for all subcases or individual
subcases respectively.

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

Argument Options Description

format <H3D, blank> H3D: Results are output in Hyper3D


format (.h3d file).
Default = blank
blank: Results are output in all active
formats for which the result is
available.

thresh <Real> Specifies an absolute threshold under which results


should not be output.
No default

rthresh <Real> Specifies a relative threshold under which results


should not be output. This value is relative to the
No default corresponding total modal energy.

topn <Integer> Specifies that only the top N values should be


output.
No default

38 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

type <AVERAGE, AVERAGE: The average of the energy is


AMPLITUDE, PEAK> output.

Default = AVERAGE AMPLITUDE: The amplitude of the energy is


output.

PEAK: The peak energy is output. This


is the sum of AVERAGE and
AMPLITUDE.

mset <ALL, SID, TOTAL> ALL: Modal energy is output for all
modes.
Default = ALL
SID: If a set ID is given, modal energy
is output only for modes listed in
that set.

TOTAL: Only the total energy is output.

option <YES, ALL, NO, YES, ALL, blank: Modal energy is output.
NONE>

Default = ALL NO, NONE: Modal energy is not output.

Comments

1. When the CMKE command is not present, component modal synthesis kinetic energy is not
output.

2. Component modal synthesis kinetic energy output is only available for frequency response
analysis (both direct and modal methods). It is intended for use when external CMS
superelements are used.

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

4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

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

Altair Engineering OptiStruct 13.0 Reference Guide 39

Proprietary Information of Altair Engineering


CMSE

I/O Options Entry

CMSE - Output Request

Description

The CMSE command can be used above the first SUBCASE or within a SUBCASE definition to
request component modal synthesis strain energy output for all subcases or individual
subcases respectively.

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

Argument Options Description

format <H3D, blank> H3D: Results are output in Hyper3D


format (.h3d file).
Default = blank
blank: Results are output in all active
formats for which the result is
available.

thresh <Real> Specifies an absolute threshold under which results


should not be output.
No default

rthresh <Real> Specifies a relative threshold under which results


should not be output. This value is relative to the
No default corresponding total modal energy.

topn <Integer> Specifies that only the top N values should be


output.
No default

40 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

type <AVERAGE, AVERAGE: The average of the energy is


AMPLITUDE, PEAK> output.

Default = AVERAGE AMPLITUDE: The amplitude of the energy is


output.

PEAK: The peak energy is output. This is


the sum of AVERAGE and
AMPLITUDE.

mset <ALL, SID, ALL: Modal energy is output for all


TOTAL> modes.
Default = ALL
SID: If a set ID is given, modal energy is
output only for modes listed in that
set.

TOTAL: Only the total energy is output.

option <YES, ALL, NO, YES, ALL, Modal energy is output.


NONE> blank:
Default = ALL
NO, NONE: Modal energy is not 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.

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

4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

Altair Engineering OptiStruct 13.0 Reference Guide 41

Proprietary Information of Altair Engineering


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.

42 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CONTF

I/O Options and Subcase Information Entry

CONTF – Output Request for Contact Results

Description

The CONTF entry can be used in the I/O Options or Subcase Information sections to request
contact results output for all nonlinear analysis subcases or individual nonlinear analysis
subcases respectively.

Format
CONTF (format, type) = option

Type Options Description

format <H3D, OPTI, H3D: Results are output in Hyper3D format


blank> (.h3d file). See below for type.

Default = blank
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, ALL: All available contact results types


PCONT,FRICT> are output.

Default = ALL
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).

option <YES, ALL, YES, ALL, Contact results are output for all grid

Altair Engineering OptiStruct 13.0 Reference Guide 43

Proprietary Information of Altair Engineering


Type Options Description

NO, NONE, blank: points.


SID>
NO, NONE: Contact results are not output.
Default = ALL

SID: If a set ID is given, contact results


are output only for grid points listed
in that set.

Comments

1. The CONTF entry is only applicable in nonlinear analysis subcases that are identified by the
presence of an NLPARM subcase entry. The specific detailed result types displayed differ
slightly between NLSTAT and geometrically nonlinear subcases.

2. Most of the contact results are real numbers and are self-explanatory. Some results that
may require clarification are listed below:

Open/Closed status is represented by 0.0 for Open and 1.0 for Closed. On graphical
display, intermediate values may appear due to transition from open to closed across
individual elements,
Slip/Stick Status is represented by 0.0 for Open, 1.0 for Slip and 2.0 for Stick. On
graphical display, intermediate values may appear due to transition of status across
individual elements,
Sliding Distance represents total sliding distance accumulated while the surfaces are in
contact. This may be different than just the difference in displacements between the
starting and final position.
3. The calculation of contact results on both sides of contact interface involves projections
and mappings. Therefore, a perfect match of results between two sides cannot be
expected, especially on mismatched meshes. Also, the resolution of different types of
results (pressure versus gap opening) differs according to their respective FEA
interpolation order. Therefore, such results may appear locally inconsistent, especially on
second order meshes and mismatched mesh densities. (Usually pressure and traction will
appear smoother than gap opening or penetration.)

4. Only formats that have been activated by an OUTPUT or FORMAT statement are valid for
use on this entry.

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

6. Multiple instances of this entry are allowed; if the instances conflict, the last instance
dominates.

44 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CSTRAIN

I/O Options and Subcase Information Entry

CSTRAIN - Output Request

Description

The CSTRAIN command can be used in the I/O Options or Subcase Information sections to
request ply strain output for elements referencing PCOMP or PCOMPG properties for all
subcases or individual subcases respectively.

Format
CSTRAIN (format_list,type,extras_list) = option

Argument Options Description

format <HM, H3D, OPTI, HM: Results are output in HyperMesh


PUNCH, OP2, PLOT, results format (.res file).
blank>
H3D: Results are output in Hyper3D
Default = blank format (.h3d file).

OPTI: Results are output in OptiStruct


results format (.cstr file).

PUNCH: Results are output in Nastran punch


results format (.pch file).

OP2: Results are output in Nastran


output2 format (.op2 file) (see
comment 10).

PLOT: Results are output in Nastran


output2 format (.op2 file) when
PARAM, POST is defined in the bulk
data section.

blank: Results are output in all active


formats, for which the result is
available.

Altair Engineering OptiStruct 13.0 Reference Guide 45

Proprietary Information of Altair Engineering


Argument Options Description

type <ALL, PRINC> ALL, blank: All strain results are output.

Default = ALL
PRINC: Only principal strain results are
output.

extras <MECH, THER> MECH: Output Mechanical strain (in


addition to total strain). This
No default 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, YES, ALL, blank: Results are output for all elements.
NONE, SID, PSID>

Default = YES NO, NONE: Results are not output.

SID: If a set ID is given, results are


output only for elements listed in
that set.

PSID: If a property set ID is given, results


for the elements referencing
properties listed in the property set
are output.

Comments

1. When the CSTRAIN command is not present, ply strain results are not output.

2. This output is not currently available for the frequency response or transient solution
sequences.

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

46 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


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

5. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

6. The SOUT field on the PCOMP or PCOMPG bulk data entry must be set to YES to activate
strain results calculation for the corresponding ply.

7. For plies defined on a PCOMPG bulk data entry, the results are grouped by GPLYID.

8. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.

9. The mechanical and thermal contributions to strain may be requested in addition to the
total strain.

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

Altair Engineering OptiStruct 13.0 Reference Guide 47

Proprietary Information of Altair Engineering


CSTRESS

I/O Options and Subcase Information Entry

CSTRESS - Output Request

Description

The CSTRESS command can be used in the I/O Options or Subcase Information sections to
request ply stress and failure index output for elements referencing PCOMP or PCOMPG
properties for all subcases or individual subcases respectively.

Format
CSTRESS (format_list,type) = option

Argument Options Description

format <HM, H3D, OPTI, HM: Results are output in HyperMesh


PUNCH,OP2, blank> results format (.res file).

Default = blank H3D: Results are output in Hyper3D format


(.h3d file).

OPTI: Results are output in OptiStruct results


format (.cstr file).

PUNCH: Results are output in Nastran punch


results format (.pch file).

OP2: Results are output in Nastran output2


format (.op2 file) (see comment 10).

blank: Results are output in all active


formats, for which the result is
available.

type <ALL, PRINC, FI> ALL, blank: All stress results are output.

Default = ALL
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.

48 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

Option <YES, ALL, NO, YES, ALL, Results are output for all
NONE, SID, PSID> blank: elements.

Default = YES
NO, NONE: Results are not output.

SID: If a set ID is given, results are


output only for elements listed in
that set.

PSID: If a property set ID is given,


results for the elements
referencing properties listed in the
property set are output.

Comments

1. When the CSTRESS command is not present, ply stress and failure index results are not
output.

2. This output is not currently available for the frequency response or transient solution
sequences.

3. The STRESS I/O option controls the output of stress results for the homogenized
composite material.

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

5. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

6. The SOUT field on the PCOMP or PCOMPG bulk data entry must be set to YES to activate
stress results calculation for the corresponding ply. For Failure Indices to be calculated,
the FT and SB fields on PCOMP or PCOMPG bulk data and stress (or strain) allowables on
the referenced materials need to be defined.

7. For plies defined on a PCOMPG bulk data entry, the results are grouped by GPLYID.

8. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.

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

10. format=OUTPUT2 can also be used to request results to be output in the Nastran output2

Altair Engineering OptiStruct 13.0 Reference Guide 49

Proprietary Information of Altair Engineering


format (.op2 file).

50 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DAMAGE

I/O Options and Subcase Information Entry

DAMAGE – Output Request

Description

The DAMAGE command can be used in the I/O Options or Subcase Information sections to
request fatigue damage results output for all fatigue subcases or individual fatigue subcases
respectively.

Format
DAMAGE (format, type) = option

Argument Options Description

format <H3D, OPTI, H3D: Results are output in Hyper3D format (.h3d
blank> file).
Default = blank
OPTI: Results are output in OptiStruct results
format (.fat file).

blank: Results are output in all active formats for


which the result is available.

type <SUB, LOAD, SUB: Only the total damage from the fatigue
EVENT, ALL> subcase is output.
Default = SUB
LOAD: Damage contribution from each static
subcase and total damage from the fatigue
subcases are output.

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.

Altair Engineering OptiStruct 13.0 Reference Guide 51

Proprietary Information of Altair Engineering


Argument Options Description

option <YES, ALL, NO, YES, ALL, Results are output for all elements.
NONE, SID> blank:
Default = ALL
NO, NONE: Results are not output.

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.

2. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

52 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DENSITY

I/O Options and Subcase Information Entry

DENSITY - Output Request

Description

The DENSITY command can be used in the I/O Options section to request density output for a
topology optimization.

Format
DENSITY (format_list,type) = option

Argument Options Description

format <HM, H3D, OPTI, HM: Results are output in HyperMesh


PUNCH, OP2, PLOT, results format (.res file).
blank>
H3D: Results are output in Hyper3D
Default = blank format (.h3d file).

OPTI: Results are output in OptiStruct


results format (.dens file).

PUNCH: Results are output in Nastran punch


results format (.pch file).

OP2: Results are output in Nastran


output2 format (.op2 file) (see
comment 6).

PLOT: Results are output in Nastran


output2 format (.op2 file) when
PARAM, POST is defined in the bulk
data section (see comment 6).

blank: Results are output in all active


formats for which the result is
available.

type <ALL, DES> ALL: Results are output in all simulations.

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

Altair Engineering OptiStruct 13.0 Reference Guide 53

Proprietary Information of Altair Engineering


Argument Options Description

option <YES, ALL, NO, YES, ALL, Results are output


NONE> blank:

Default = YES
NO, NONE: Results are not output.

Comments

1. When the DENSITY command is not present, density results are output.

2. Density results are only available for topology optimizations.

3. Outputting the density results in all simulations allows analysis results to be plotted on
the density iso-surface in HyperView.

4. The frequency of this output is controlled by the DESIGN keyword on an OUTPUT definition
or, if no OUTPUT definition exists with the DESIGN keyword, by the DENSRES I/O option.

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

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

7. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

54 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DESGLB

I/O Options Entry

DESGLB – Constraint Selection

Description

The DESGLB command can be used in the I/O Options section, before the first subcase
statement, to select a constraint set that is not subcase dependent.

Format
DESGLB = integer

Argument Options Description

integer < SID > SID: Set identification of a DCONSTR or DCONADD bulk
data entry.
No default

Comments

1. The constrained response referenced by the DESGLB constraint selection must not be
subcase dependent.

2. Only one DESGLB entry can be defined in the I/O options section for the entire model.

3. This entry is represented as an optimizationconstraint in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 55

Proprietary Information of Altair Engineering


DESHIS

I/O Options Entry

DESHIS - Output Control

Description

The DESHIS command can be used in the I/O Options section to control the creation of the
optimization history file .hgdata.

Format
DESHIS = option

Argument Options Description

option <YES, ALL, NO> YES, ALL, blank: .hgdata file is created.

Default = YES
NO: .hgdata is not created.

Comments

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

56 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DGLOBAL

I/O Options Entry

DGLOBAL - Input Definition

Description

The DGLOBAL command can be used in the I/O Options section to activate the Global Search
Option (GSO).

Format
DGLOBAL = n

Argument Options Description

n (Integer > 0) Identification of a DGLOBAL bulk data entry.

No default

Comments

1. This command must reference a DGLOBAL bulk data entry to run GSO.

2. This data can exist only once in the I/O section.

3. This command activates a global search algorithm to run an optimization of user-defined


design variables from multiple starting points.

Altair Engineering OptiStruct 13.0 Reference Guide 57

Proprietary Information of Altair Engineering


DISPLACEMENT

I/O Options and Subcase Information Entry

DISPLACEMENT - Output Request

Description

The DISPLACEMENT command can be used in the I/O Options or Subcase Information sections
to request displacement vector output for all subcases or individual subcases respectively.

Format
DISPLACEMENT (sorting,format,form,rotations,random,peakoutput,modal,complex
eigenvalue analysis) = option

Argument Options Description

sorting <SORT1, SORT2> This argument only applies to the PUNCH format (.pch
file) or the OUTPUT2 format (.op2 file) output for
Default = blank normal modes, frequency response, and transient
subcases. It will be ignored without warning if used
elsewhere.

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, HM: Results are output in HyperMesh results
PUNCH,OP2, format (.res file).
PATRAN, HG,
APATRAN, PLOT, H3D: Results are output in Hyper3D format
blank> (.h3d file).

Default = blank OPTI: Results are output in OptiStruct results


format (.disp file).

PUNCH: Results are output in Nastran punch


results format (.pch file).

58 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

OP2: Results are output in Nastran output2


format (.op2 file) (see comment 12).

PATRAN: Results are output in Patran format


(multiple files).

HG: Results are output in HyperGraph


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

APATRAN: Results are output in Alternative Patran


format (multiple files).

PLOT: Results are output in Nastran output2


format (.op2 file) when PARAM, POST is
defined in the bulk data section.

If PARAM, POST is not defined in the bulk


data section, this format allows the form
for complex results to be defined for
XYPUNCH output without having other
output.

blank: Results are output in all active formats


for which the result is available.

form <COMPLEX, COMPLEX (HM Provides a combined magnitude/phase


REAL, IMAG, only), blank: form of complex output to the .res file
PHASE, BOTH> for the HM output format.

Default (HM REAL or IMAG: Provides rectangular format (real and


only) = COMPLEX imaginary) of complex output (See
comment 10).
Default (all other
formats) = REAL PHASE: Provides polar format (magnitude and
phase) of complex output. Phase
output is in degrees (See comment
10).

BOTH (HM only): Provides both polar and rectangular


formats of complex output.

Altair Engineering OptiStruct 13.0 Reference Guide 59

Proprietary Information of Altair Engineering


Argument Options Description

rotations <ROTA, NOROTA> ROTA: Rotational displacement results are


output. Only works with H3D and HM
Default = output streams. Rotations are always
NOROTA output with translations for other
output streams.

NOROTA: Rotational displacement results are not


output. Only works with H3D and HM
output streams. Rotations are always
output with translations for other
output streams.

random <PSDF, RMS> PSDF: Requests PSD and RMS results from
random response analysis to be output.
No default
Only valid for the H3D format. The
"RMS over Frequencies" output is at
the end of the Random results.

RMS: Requests only the “RMS over


Frequencies” result from random
response analysis to be output.

Valid only for the H3D format.

peakoutput <PEAKOUT> PEAKOUT: If PEAKOUT is present, only the filtered


frequencies from the PEAKOUT card will
Default = Blank be considered for this output.

modal <MODAL> MODAL: If MODAL is present, displacements of


the structural modes and residual
Default = Blank vectors are output to the PUNCH and
OUTPUT2 files for modal frequency
response and transient analysis.

60 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

complex <UNSTABLE> UNSTABLE: If UNSTABLE is present, the


eigenvalue displacement results from the unstable
Default = Blank
analysis modes (only) of a complex eigenvalue
analysis are output.

Blank: Displacement results are output for all


modes by default (See comment 1).

option <YES, ALL, NO, YES, ALL, blank: Displacement is output for all grids.
NONE, SID>

Default = ALL NO, NONE: Displacement is not output.

SID: If a set ID is given, displacement is


output only for grids listed in that set.

Comments

1. When DISPLACEMENT command is not present, displacement is output for all grids for all
subcases, except for frequency response subcases.

2. The form argument is only applicable for frequency response analysis. It is ignored for
other analysis types.

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

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

5. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

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

7. Rotation results are output in radians.

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

Altair Engineering OptiStruct 13.0 Reference Guide 61

Proprietary Information of Altair Engineering


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

10. Results in binary format (.h3d or .op2) are always output in PHASE/MAG form, regardless
of the options specified in the FORM field. The corresponding post-processors
(HyperView/HyperGraph) can easily convert the PHASE/MAG format to the required
formats. Results in ASCII formats are output in the specified/requested FORM.

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

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

62 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DMIGNAME

I/O Options Entry

DMIGNAME - Reduced Matrix Name Definition

Description

The DMIGNAME command can be used in the I/O Options section to define the name given to
the reduced matrices written to an external data file.

Format
DMIGNAME = mtxname

Argument Options Description

mtxname <up to 6 The name given to the reduced matrices written to an


characters> external data file, when PARAM, EXTOUT is present in
the bulk data section.
Default = AX
If PARAM, EXTOUT, DMIGPCH is used, then the file
outfile_mtxname.pch is created.

If PARAM,EXTOUT, DMIGBIN is used, then the file


outfile_mtxname.dmg is created.

Both files contain the matrices:

KAmtxname - reduced stiffness matrix


MAmtxname - reduced mass matrix
Pmtxname - reduced loading matrix
Note: The reduced mass matrix is only output if an
eigenvalue subcase is present in the input file
and the reduced loading matrix is only output if a
linear static subcase is present in the input file.

Comments

1. When a DMIGNAME command is not present, AX is used for mtxname.

2. Only one occurrence of DMIGNAME is permitted.

3. DMIGNAME must appear before the first subcase.

4. See Direct Matrix Approach in the User's Guide for more detailed usage information.

Altair Engineering OptiStruct 13.0 Reference Guide 63

Proprietary Information of Altair Engineering


DSA

I/O Options and Subcase Information Entry

DSA - Design Sensitivity Analysis Output Request

Description

The DSA command can be used in the I/O Options section to request Design Sensitivity
Analysis results in a frequency response analysis.

Format
DSA (TYPE, PEAKOUT, PROPERTY) = SID

Examples
DSA(DISP,PROPERTY)=12

DSA(VELO,PEAKOUT)=45

DSA(ACCE,PEAKOUT,SCALE)=23

Argument Options Description

TYPE <DISP,PRES,VELO The options are Displacement, Pressure, Velocity and


,ACCE> Acceleration respectively.

Default = DISP

PEAKOUT Default = blank If PEAKOUT is present inside the parentheses of the DSA
entry, the filtered frequencies from the PEAKOUT card
will be considered for DSA results.

PROPERTY Default = blank If the “PROPERTY” flag is present:


This indicates that design sensitivities represent the
change in design response due to a change in design
properties (instead of design variables).

If the “PROPERTY” flag is not present:


This indicates that design sensitivities represent the
change in design response due to a change in design
variables.

64 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

SID <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 instance
dominates. If this entry is defined above the first subcase then it is applied to all
subcases. If it is defined within a specific subcase then it is applied to that subcase only.
2. If the input deck doesn't contain any optimization data (apart from DESVAR’s), then a
MASS objective function is automatically created along with responses and constraints
corresponding to the DSA request. If the input deck contains a valid optimization setup,
then it's augmented with the DSA request.
3. In the H3D file, the "SCALE" value is only printed when the PROPERTY argument is not
present within the parentheses of the DSA entry. The sensitivities are pre-scaled when
the PROPERTY argument is present in the DSA entry, so the scaling factor is not required
in the H3D file.
4. OUTPUT, H3DSENS can be used to include (or exclude) user-defined responses in the DSA
output. The table below lists the sensitivities that are output for each option.

Sensitivities output from a


Sensitivities requested via complete Optimization setup
Output the DSA output request (User-defined/specified
(responses are
automatically defined)
responses 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 input
deck if sensitivity output is requested through the DSA entry.

Altair Engineering OptiStruct 13.0 Reference Guide 65

Proprietary Information of Altair Engineering


ECHO/ECHOON/ECHOOFF

I/O Options Entry

ECHO - Output Control


ECHOON - Output Control
ECHOOFF - Output Control

Description

The ECHO command can be used in the I/O Options section causing the output of the
interpreted forms of subcase information and bulk data entries to the .out file.

The ECHOON command can be used in the I/O Options, Subcase Information, or Bulk Data
sections causing the (verbatim) output of any subsequent I/O options, subcase information,
or bulk data entries to the .out file until an ECHOOFF command is encountered.

The ECHOOFF command can be used in the I/O Options, Subcase Information, or Bulk Data
sections suppressing the output of any subsequent I/O options, subcase information, or bulk
data entries to the .out file until and ECHOON command is encountered.

Format
ECHO = option1

ECHOON = option2

ECHOOFF

Example
ECHO = SORT(EIGR,EIGRL,ASET1,SPOINT,PARAM,SPC1,SPCADD,MPCADD,

DLOAD,RLOAD2,DAREA,DPHASE,FREQ1,TABLED1,TABDMP1)

Argument Options Description

option1 <SHORT, PUNCH, SHORT: Only entries having less than 20


{cardname}, EXCEPT instances are echoed to the .out
{cardname}, blank> file.

<MAT, PROP, ELEM> PUNCH: Writes interpreted echo of all


bulk data entries to the .echo
Default = blank file.

{cardname}: Only bulk data entries with the


given {cardname} are echoed to
the .out file.

66 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

EXCEPT Only bulk data entries with the


{cardname}: given {cardname} are not
echoed.

blank: Writes interpreted forms of all


subcase information and bulk
data entries to the .out file.

MAT, PROP, Adds all cards of the specified


ELEM: class to the list for ECHO.

Option2 <PARSED> PARSED: Bulk data entries are converted


to free format (comma
Default = blank separated) before echoing.

blank: Bulk data entries are echoed


verbatim.

Comments

1. When an ECHO command is not present, no input information is echoed.

2. The interpreted echo always includes SUBCASE cards (solution related), but not output
control cards.

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

4. The interpreted echo may contain some cards that are automatically generated or
converted during reading (for example, a CQUADR card shows as CQUAD4, or a CMASS1 card
shows as a CMASS3 when only scalar points are referenced). Unreferenced cards may not
show in the printout. PARAM,DOPTRM,OSDIAG will not be shown.

5. ECHO will be produced from internal representation of each card, thus it will be
equivalent, but not identical to the input:

For most of the optional fields, the blank from input will be printed in ECHO as default
value.
Fields which are not recognized or not used by OptiStruct are left blank.
Some values which would generate warning on the input will be printed after
adjustment.
Optional continuation cards may be printed even if they did not appear in the input.

Altair Engineering OptiStruct 13.0 Reference Guide 67

Proprietary Information of Altair Engineering


6. The interpreted echo is always printed using a fixed field format (8 character fields)
except GRID and DMIG cards, which are printed using free format (comma separated
fields) with 10 decimal digits accuracy. Note that the use of IDs larger than 99,999,999
is allowed, but ECHO will not be usable in these cases as such IDs cannot be printed in
fixed format.

DMIG cards are usually very large and are not shown in the interpreted echo. Adding the
card:
OSDIAG,167,1

anywhere in the control section will force full printout of DMIG cards if the interpreted
echo is requested.

7. {cardname} contains the list of all cards which are to be included in the interpreted echo
(or excluded, if EXCEPT keyword is present). This list may contain ELEM, MAT, or PROP
keywords, which is equivalent to listing all valid element, material, or property names,
respectively.

8. Multiple ECHO cards are allowed; all parameters of these cards are accumulated in the
order in which they are input. EXCEPT may appear anywhere (for example, before or after
{cardname} list) and may be repeated on multiple cards.

9. ECHOON / ECHOOFF cards may appear in any section of the input deck.

10. All comment cards, empty cards, and characters after the $ character on any card will
not be printed in any ECHO format.

11. The .echo file generated when 'ECHO = PUNCH' is defined represents a copy of the input
deck in a form suitable to use for another solution which, when used with the same
Subcase Information and I/O Options entries, should generate identical results (round off
error may be noticeable if the original input deck uses large field format). However, in
some cases, the ECHO may require manual editing before being acceptable as input for
OptiStruct. In particular, some optimization cards may be printed with information already
modified internally, and they will be not correct. Also some cards with a negative ID may
be printed in ECHO; those cards are automatically generated internally to OptiStruct, and
should simply be deleted.

68 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


EDE

I/O Options and Subcase Information Entry

EDE - Output Request

Description

The EDE command can be used in the I/O Options or Subcase Information sections to request
element energy loss per cycle and element energy loss per cycle density output for all
subcases or individual subcases respectively.

Format
EDE (format_list, type, dmig) = option

Argument Option Description

format <HM, H3D, HM: Results are output in HyperMesh


PUNCH, OP2, results format (.res file).
PLOT, blank>
H3D: Results are output in Hyper3D format
Default = blank (.h3d file).

PUNCH: Results are output in Nastran punch


results format (.pch file).

OP2: Results are output in Nastran output2


format (.op2 file) (see comment 8).

PLOT: Results are output in Nastran output2


format (.op2 file) when PARAM, POST is
defined in the bulk data section.

blank: Results are output in all active formats


for which the result is available.

type <AVERAGE, AVERAGE: In frequency response analysis average


AMPLITUDE, energy is output.
PEAK>
AMPLITUDE: In frequency response analysis the
Default = amplitude of energy is output.
AVERAGE
PEAK: In frequency response analysis the
see Comment 7
peak energy is output. This is the sum
of AVERAGE and AMPLITUDE.

Altair Engineering OptiStruct 13.0 Reference Guide 69

Proprietary Information of Altair Engineering


Argument Option Description

dmig <DMIG, NODMIG> DMIG: Results are provided for external


superelements in the .out file.
Default =
NODMIG
NODMIG: Results are not provided for external
superelements in the .out file.

option <YES, ALL, NO, YES, ALL, Element damping energy and damping
NONE, SID> blank: energy density are output for all
elements.
Default = ALL
NO, NONE: Element damping energy and damping
energy density are not output.

SID: If a set ID is given, element damping


energy and damping energy density are
output only for elements listed in that
set.

Comments

1. When an EDE command is not present, element damping energy and damping energy
density is not output.

2. Initial thermal strain is included in the calculation of element energy loss per cycle and
element energy loss per cycle density.

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

4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

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

6. Type only applies to frequency response analysis.

7. There are three ways to calculate the Element Damping Energy in Frequency Response
Analysis. They are listed as follows:

70 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Type of Output Formula

Average

Amplitude

Peak

Where,

E = Elemental Energy

{Ur } = Displacement (Real Part)

{Ui } = Displacement (Imaginary Part)

[Be ] = Elemental Damping

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

Altair Engineering OptiStruct 13.0 Reference Guide 71

Proprietary Information of Altair Engineering


EIGVNAME

I/O Options Entry

EIGVNAME - Filename Prefix Definition

Description

The EIGVNAME command can be used in the I/O Options section to define the prefix to be
used for external eigenvalue data files (.eigv).

Format
EIGVNAME = prefix

Argument Description

prefix The prefix to be used for the saving and retrieval of external eigenvalue
data files.

The external eigenvalue data file name is of the form <prefix>_#.eigv,


where <prefix> is defined here, # is the integer argument of the
EIGVSAVE subcase information entry or one of the integer arguments of
the EIGVRETRIEVE subcase information entry.

Comments

1. When an EIGVNAME command is not present, the OUTFILE prefix definition is used. If
OUTFILE is not defined, the prefix of the input file is used.

2. Only one occurrence of EIGVNAME is permitted.

3. EIGVNAME must appear before the first subcase.

4. The total length of information on this card is limited to 200 characters (including the card
name and spaces between arguments). This data can be on a single line or span multiple
continuation lines. See Guidelines for I/O Options and Subcase Information Entries for an
example showing how to enter long file names on multiple lines.

5. Prefixes specified on the EIGVNAME card can be arbitrary file prefixes with optional paths
appropriate to the operating system (Windows or UNIX). They may be enclosed in quotes
(double or single quotes can be used), and either forward slash (/) or back slash (\)
characters can be used to separate parts of the path name.

OptiStruct uses the following rules for the EIGVNAME card:

When the argument contains an absolute path of the file (if it starts with "/" on UNIX
or a drive letter, such as "D:", on Windows, for example), OptiStruct creates .eigv
files at the given location.

72 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


When only the file prefix is given (without the path), .eigv files will be created in the
current directory, meaning the directory from which OptiStruct has been executed, and
NOT in the directory where the input file is located.
When the argument contains a relative path (../filename or sub/filename, for
example), .eigv files will be created in a directory relative to where OptiStruct is
executed and NOT relative to the directory where the input file is located.

Altair Engineering OptiStruct 13.0 Reference Guide 73

Proprietary Information of Altair Engineering


EKE

I/O Options and Subcase Information Entry

EKE - Output Request

Description

The EKE command can be used in the I/O Options or Subcase Information sections to request
kinetic energy and kinetic energy density output for all subcases or individual subcases
respectively.

Format
EKE (format_list, type, dmig, peakoutput) = option

Argument Option Description

format <HM, H3D, HM: Results are output in HyperMesh


PUNCH, OP2, results format (.res file).
PLOT, blank>
H3D: Results are output in Hyper3D format
Default = blank (.h3d file).

PUNCH: Results are output in Nastran punch


results format (.pch file).

OP2: Results are output in Nastran output2


format (.op2 file) (see comment 8).

PLOT: Results are output in Nastran output2


format (.op2 file) when PARAM, POST is
defined in the bulk data section.

blank: Results are output in all active formats


for which the result is available.

type <AVERAGE, AVERAGE: In frequency response analysis average


AMPLITUDE, energy is output.
PEAK>
Default = AMPLITUDE: In frequency response analysis the
AVERAGE amplitude of energy is output.

see Comment 7
PEAK: In frequency response analysis the
peak energy is output. This is the sum
of AVERAGE and AMPLITUDE.

74 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Option Description

dmig <DMIG, DMIG: Results are provided for external


NODMIG> superelements in the .out file.

Default = NODMIG: Results are not provided for external


NODMIG
superelements in the .out file.

peakoutput <PEAKOUT> PEAKOUT: If PEAKOUT is present, only the filtered


frequencies from the PEAKOUT card will
Default = blank be considered for this output.

option <YES, ALL, NO, YES, ALL, Element kinetic energy and kinetic
NONE, SID> blank: energy density are output for all
elements.
Default = ALL
NO, NONE: Element kinetic energy and kinetic
energy density are not output.

SID: If a set ID is given, element kinetic


energy and kinetic energy density are
output only for elements listed in that
set.

Comments

1. When an EKE command is not present, element kinetic energy and kinetic energy density
is not output.

2. Initial thermal strain is included in the calculation of kinetic energy and kinetic energy
density.

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

4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

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

Altair Engineering OptiStruct 13.0 Reference Guide 75

Proprietary Information of Altair Engineering


6. Type only applies to frequency response analysis.

7. There are three ways to calculate the Element Kinetic Energy in Frequency Response
Analysis. They are listed as follows:

Type of Output Formula

Average

Amplitude

Peak

Where,

E = Element Energy

{vr } = Real part of Velocity

{vi } = Imaginary part of Velocity

[Me] = Element Mass

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

76 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


ENERGY

I/O Options and Subcase Information Entry

ENERGY - Output Request for Geometric Nonlinear Analysis Subcase

Description

The ENERGY command can be used in the I/O Options or Subcase Information sections to
request energy output for all geometric nonlinear analysis subcases or individual geometric
nonlinear analysis subcases respectively.

Format
ENERGY (format, type) = option

Argument Option Description

format <H3D, blank> H3D: Results are output in Hyper3D format


(.h3d file).
Default = blank
blank: Results are output in all active formats
for which the result is available.

type
<ALL, ENERG, ALL: All energy results are output.
HOURG>
Default = ALL ENERG: All energy results without hourglass
energy are output.

HOURG: Hourglass energy only is output.

option
<YES, ALL, NO, YES, ALL, Energy results are output for all
NONE, SID, blank: elements.
PSID>
Default = ALL NO, NONE: Energy results are not output.

SID: If a set ID is given, energy results are


output only for elements listed in that
set.

Altair Engineering OptiStruct 13.0 Reference Guide 77

Proprietary Information of Altair Engineering


Argument Option Description

PSID: If a property set ID is given, energy


results for the elements referencing
properties listed in the property set are
output.

Comments

1. ENERGY is only applicable for geometric nonlinear analysis subcases which are defined by
an ANALYSIS = NLGEOM, IMPDYN or EXPDYN subcase entry. It is ignored for all other
subcases.

2. Only formats that have been activated by an OUTPUT or FORMAT statement are valid for
use on this card.

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

4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

78 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


ERP

I/O Options and Subcase Information Entry

ERP - Output Request

Description

The ERP command can be used in the I/O Options or Subcase Information sections to request
equivalent radiated power output for all subcases or individual subcases, respectively.

Format
ERP (format_list, grid) = option

Argument Option Description

format <H3D, PUNCH, H3D: Results are output in Hyper3D format (.h3d
blank> file).

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

blank: Results are output in all active formats for


which the result is available.

grid <GRID> GRID: Output the contribution of each grid in


addition to the ERP results for the PANEL,
Default = blank defined by ERPPNL or PANELG (TYPE=ERP).
This is a normal velocity squared for each
grid specified in the panel definition.

option <YES, ALL, NO, YES, ALL, Equivalent radiated power is output for all
NONE> blank: panels.

Default = ALL
NO, NONE: Equivalent radiated power is not output.

Comments

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

Altair Engineering OptiStruct 13.0 Reference Guide 79

Proprietary Information of Altair Engineering


2. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

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

4. In addition to the ERP values, the following results are output to the .pch file: total ERP
over the loading frequencies, fraction of the total ERP at each loading frequency, and ERP
expressed in decibels ERBdB = 10 * log 10 (ERP) at each loading frequency.

5. The ERP is calculated as half the normal velocity squared of each grid multiplied by the
associated area of each grid on the panel. The parameters for the speed of sound
(ERPC), fluid density (ERPRHO), and radiation loss factor (ERPRLF) are used in the
calculation of ERP using the formula below.

6. The calculation of ERP in decibels (dB) is performed using the PARAM data RHOCP and
ERPREFDB in the equation below. ERPREFDB is the reference value in dB and RHOCP is the
scale factor:

7. At least one of the bulk data entries ERPPNL or PANELG (TYPE=ERP) needs to be
specified, if the ERP Output Request is used.

80 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


ESE

I/O Options and Subcase Information Entry

ESE - Output Request

Description

The ESE command can be used in the I/O Options or Subcase Information sections to request
strain energy and strain energy density output for all subcases or individual subcases
respectively.

Format
ESE (format_list, type, dmig, peakoutput) = option

Argument Option Description

format <HM, H3D, HM: Results are output in HyperMesh


PUNCH, OP2, results format (.res file).
PLOT, blank>
H3D: Results are output in Hyper3D format
Default = blank (.h3d file).

PUNCH: Results are output in Nastran punch


results format (.pch file).

OP2: Results are output in Nastran output2


format (.op2 file) (see comment 8).

PLOT: Results are output in Nastran output2


format (.op2 file) when PARAM, POST
is defined in the bulk data section.

blank: Results are output in all active formats


for which the result is available.

type <AVERAGE, AVERAGE: In frequency response analysis average


AMPLITUDE, energy is output.
PEAK>
AMPLITUDE: In frequency response analysis the
Default = amplitude of energy is output.
AVERAGE
PEAK: In frequency response analysis the
See Comment 7
peak energy is output. This is the sum
of AVERAGE and AMPLITUDE.

Altair Engineering OptiStruct 13.0 Reference Guide 81

Proprietary Information of Altair Engineering


Argument Option Description

dmig <DMIG, NODMIG> DMIG: Results are provided for external


superelements in the .out file.
Default =
NODMIG
NODMIG: Results are not provided for external
superelements in the .out file.

peakoutput <PEAKOUT> PEAKOUT: If PEAKOUT is present, only the filtered


frequencies from the PEAKOUT card will
Default = blank be considered for this output.

option <YES, ALL, NO, YES, ALL, Element strain energy and strain
NONE, SID> blank: energy density are output for all
elements.
Default = ALL
NO, NONE: Element strain energy and strain
energy density are not output.

SID: If a set ID is given, element strain


energy and strain energy density are
output only for elements listed in that
set.

Comments

1. When an ESE command is not present, element strain energy and strain energy density is
not output.

2. Initial thermal strain is included in the calculation of strain energy and strain energy
density.

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

4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

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

82 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


6. Type only applies to frequency response analysis.

7. There are three ways to calculate the Element Strain Energy in Frequency Response
Analysis. They are listed as follows:

Type of Output Formula

Average

Amplitude

Peak

Where,

E = Elemental Energy

{u r } = Displacement (Real Part)

{u i } = Displacement (Imaginary Part)

[Ke] = Elemental Stiffness

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

Altair Engineering OptiStruct 13.0 Reference Guide 83

Proprietary Information of Altair Engineering


FLUX

I/O Options and Subcase Information Entry

FLUX – Output Request

Description

The FLUX command can be used in the I/O Options or Subcase Information sections to
request temperature gradient and flux output for all steady-state heat transfer analysis
subcases, transient heat transfer analysis subcases or individual heat transfer analysis
subcases, respectively.

Format
FLUX (format_list) = option

Argument Options Description

format <PUNCH, OP2, PUNCH: Results are output in Nastran punch results
H3D, PLOT, format (.pch file).
blank>
OP2: Results are output in Nastran output2 format
Default = blank (.op2 file) (see comment 5).

PLOT: Results are output in Nastran output2 format


(.op2 file) when PARAM, POST is defined in the
bulk data section.

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

blank: Results are output in all active formats for


which the result is available.

option <YES, ALL, NO, YES, ALL, Flux results are output for all valid elements.
NONE, SID> blank:

Default = ALL
NO, NONE: Flux results are not output.

SID: If a set ID is given, flux results are output only


for elements referenced by that set.

84 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. When the FLUX command is not present, flux results are not output.

2. Flux output is only available for steady-state heat transfer analysis and transient heat
transfer analysis solution sequences.

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

4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

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

Altair Engineering OptiStruct 13.0 Reference Guide 85

Proprietary Information of Altair Engineering


FORCE/ELFORCE

I/O Options and Subcase Information Entry

FORCE - Output Request

Description

The FORCE command can be used in the I/O Options or Subcase Information sections to
request element force output for all subcases or individual subcases respectively.

Format
FORCE (sorting, format_list, form, type, location, random, peakoutput, modal)
= option

Argument Options Description

sorting <SORT1, SORT2> This argument only applies to the PUNCH


format (.pch file) or the OUTPUT2 format (.op2
Default = blank 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 element SET is specified,
SORT1 is used, otherwise, SORT2
is used; for transient analysis,
SORT2 is used.

format <HM, H3D, OPTI, HM: Results are output in HyperMesh


PUNCH, OP2, PLOT, result format (.res file).
blank>
H3D: Results are output in Hyper3D
Default = blank format (.h3d file).

OPTI: Results are output in OptiStruct


results format (.force file).

86 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

PUNCH: Results are output in Nastran


punch results format (.pch file).

OP2: Results are output in Nastran


output2 format (.op2 file) (see
comment 11).

PLOT: Results are output in Nastran


output2 format (.op2 file) when
PARAM, POST is defined in the
bulk data section.

If PARAM, POST is not defined in


the bulk data section, this format
allows the form for complex
results to be defined for XYPUNCH
output without having other
output.

blank: Results are output in all active


formats for which the result is
available.

form <COMPLEX, REAL, COMPLEX (HM Provides a combined magnitude/


IMAG, PHASE, only), blank: phase form of complex output to
BOTH> the .res file for the HM output
format.
Default (HM only) =
COMPLEX REAL, IMAG: Provides rectangular format (real
and imaginary) of complex
Default (all other output.
formats) = REAL
PHASE: Provides polar format (phase and
magnitude) of complex output.

BOTH (HM Provides both rectangular and


only): polar formats of complex output.

type <TENSOR, DIRECT> TENSOR: Force results are output for all
solution sequences in which force
Default = TENSOR
results are supported. The Tensor

Altair Engineering OptiStruct 13.0 Reference Guide 87

Proprietary Information of Altair Engineering


Argument Options Description

format is used for H3D output


(See comment 9).

DIRECT: Force results are output for all


solution sequences in which force
results are supported. The Direct
format is used for H3D output
(See comment 9).

location <CENTER, CUBIC, CENTER: Element forces for shell and solid
SGAGE, CORNER, elements are output at the
BILIN> element center only.
Default = CENTER
CUBIC: Element forces for shell elements
are output at the element center
and grid points using the strain
gage approach with cubic bending
correction.

SGAGE: Element forces for shell elements


are output at the element center
and grid points using the strain
gage approach.

CORNER or Element forces for shell elements


BILIN: are output at the element center
and at the grid points using
bilinear extrapolation.

random <PSDF, RMS> PSDF: Requests PSD and RMS results


from random response analysis to
No default be output for CBUSH elements
only.

Only valid for H3D format. The


"RMS over Frequencies" output is
at the end of the Random results
in the .h3d file.

RMS: Requests only the “RMS over


Frequencies” result from random
response analysis to be output
for CBUSH elements only.

88 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

Valid only for the H3D format.

peakoutput <PEAKOUT> PEAKOUT: If PEAKOUT is present, only the


filtered frequencies from the
Default = blank PEAKOUT card will be considered
for this output.

modal <MODAL> MODAL: If MODAL is present, element


forces of the structural modes
Default = blank
and residual vectors are output
to the PUNCH and OUTPUT2 files
for modal frequency response and
transient analysis.

option <YES, ALL, NO, YES, ALL, Element force is output for all
NONE, SID> blank: valid elements.

Default = ALL
NO, NONE: Force is not output.

SID: If a set ID is given, force is


output only for valid elements
listed in that set.

Comments

1. When neither FORCE nor ELFORCE commands are present, force is not output.

2. FORCE results are available for ELAS (CELAS1, CELAS2, CELAS3, CELAS4), ROD (CROD),
BAR (CBAR, CBEAM), BUSH (CBUSH), PLATE (CQUAD, CTRIA), GAP (CGAP), FASTENER
(CFAST)*, VISCOUS DAMPER (CVISC), SCALAR DAMPER (CDAMP1, CDAMP2, CDAMP3,
CDAMP4) and WELD (CWELD) elements.

* CFAST elements or their corresponding force results are available for post-processing in
HyperView only if the .fem file is loaded as a model (procedure used in comment 9).

3. The form argument is only applicable for frequency response analysis. It is ignored in
other instances.

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

Altair Engineering OptiStruct 13.0 Reference Guide 89

Proprietary Information of Altair Engineering


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

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

7. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.

8. In general, HyperView does not recognize the SORT2 format for results from the .op2 file.
When results are output only in SORT2 format (<Result Keyword> (SORT2, OUTPUT2, …
.)), the results are written by OptiStruct into the .op2 file in SORT2 format, but when
the .op2 file is imported into HyperView, the results in SORT2 format are not recognized.
Therefore, the SORT1 option is recommended for results output in OUTPUT2 format and
SORT2 option is recommended for results output in PUNCH format.

9. Vector and Tensor plots of some element force results (weld, beam/bar and gap
elements) are available for post-processing in HyperView only if the .fem file is loaded in
the Load Model field and the results file is loaded in the Load Results field (below is an
example illustration of the HyperView Load model and results: panel).

Make sure that the Advanced option is selected from the Result Math Template: menu.

10. For shell elements force results are given as force/unit length.

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

90 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


FORMAT

I/O Options Entry

FORMAT - Output Control

Description

The FORMAT command can be used in the I/O Options section to indicate the format in which
results are to be output.

Format
FORMAT = option

Argument Options Description

option <ASCII, OS, OPTI, OPTI, OS, ASCII: OptiStruct ASCII results
HM, HYPER, BOTH, files are output.
H3D, FLX, NASTRAN,
PUNCH, PATRAN, HM, HYPER: The HyperMesh binary
APATRAN, O2, results file (.res file) is
OUT2, OP2, PLOT, output.
NONE>
BOTH: Same as defining both HM
Default = FLX and OPTI.

H3D: Hyper3D binary results file


(.h3d file) and an HTML
report (.html file) are
output.

FLX: Same as defining both HM


and H3D.

NASTRAN, PUNCH: The Nastran punch file


format (.pch file) is
output.

PATRAN, PATRAN: A number of Patran ASCII


results files are output.
APATRAN outputs the
same files using an
alternative file naming
convention.

O2, OUT2, OP2: Nastran binary output2 file


format (.op2 file) is output

Altair Engineering OptiStruct 13.0 Reference Guide 91

Proprietary Information of Altair Engineering


Argument Options Description

(see comment 4).

PLOT: Results are output in


Nastran output2 format
(.op2 file) when PARAM,
POST is defined in the bulk
data section.

NONE: Analysis output is not


required. Cannot be used
in combination with other
FORMAT commands.

Comments

1. Information provided on OUTPUT entries takes precedence over information provided on


FORMAT entries. If neither of these entries are defined, the output formats defined in the
OptiStruct Configuration File are used. If no format is defined by the OptiStruct
configuration file, then both the HM and H3D formats are active by default.

2. Multiple FORMAT commands are allowed.

3. It is recommended to use the OUTPUT command instead of the FORMAT command since it is
more flexible and allows different frequencies of output for different formats during an
optimization.

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

92 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


FOS

I/O Options and Subcase Information Entry

FOS – Output Request

Description

The FOS command can be used in the I/O Options or Subcase Information sections to request
fatigue factor of safety output for all fatigue subcases or individual fatigue subcases.

Format

FOS (format_list) = option

Argument Options Description

format <H3D,OPTI, blank> H3D: Results are output in Hyper3D format (.h3d
file).
Default = blank
OPTI: Results are output in OptiStruct results format
(.fat file).

blank: Results are output in all active formats for


which the result is available.

option <YES,ALL,NO, YES,ALL, Results are output for all elements.


NONE,SID,PSID> blank:

Default = ALL NO,NONE: Results are not output.

SID: If a set ID is provided, results are output only


for elements listed in that set.

Comments

1. When a FOS command is not present, fatigue FOS results are not output.

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

3. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

Altair Engineering OptiStruct 13.0 Reference Guide 93

Proprietary Information of Altair Engineering


GPFORCE

I/O Options and Subcase Information Entry

GPFORCE - Output Request

Description

The GPFORCE command can be used in the I/O Options or Subcase Information sections to
request grid point force balance output for all subcases or individual subcases respectively.

Format
GPFORCE (format_list, elem, form, peakoutput, modal) = option

Argument Options Description

format <H3D, OPTI, H3D: Results are output in Hyper3D format (.h3d
PUNCH, OP2, file).
PLOT, blank>
OPTI: Results are output in OptiStruct results
Default = blank format (.gpf file).

PUNCH: Results are output in Nastran punch results


format (.pch file).

OP2: Results are output in Nastran output2 format


(.op2 file) (see comment 9).

PLOT: Results are output in Nastran output2 format


(.op2 file) when PARAM, POST is defined in
the bulk data section.

elem <ELEM, NOELEM: GPFORCE results in the H3D output file will
(H3D only) NOELEM> not include element contributions. However,
the TOTAL value for each GRID includes the
Default = element contributions.
NOELEM
ELEM: GPFORCE results in the H3D output file
includes element contributions.

form <REAL, IMAG, REAL, IMAG: Provides rectangular format (real and
PHASE> imaginary) of complex output.

94 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

Default = REAL PHASE: Provides polar format (phase and magnitude)


of complex output.

peakoutput <PEAKOUT> PEAKOUT: If PEAKOUT is present, only the filtered


frequencies from the PEAKOUT card will be
Default = blank considered for this output.

modal <MODAL> MODAL: If MODAL is present, grid point forces of the


structural modes and residual vectors are
Default = blank
output to the PUNCH and OUTPUT2 files for
modal frequency response and transient
analysis.

option <YES, ALL, NO, YES, ALL, Grid point force balance is output for all
NONE, SID> blank: elements.

Default = ALL
NO, NONE: Grid point force balance is not output.

SID: If a set ID is given, grid point force balance


is output only for nodes listed in that set.

Comments

1. When a GPFORCE command is not present, grid point force balance is not output.

2. GPFORCE output is available for the following solution sequences:

Solution Sequences Output Formats

Static Analysis H3D, OP2, PCH, OPT

Normal Modes Analysis H3D, OP2, PCH

Direct Frequency Response Analysis H3D, OP2, PCH, OPT

Modal Frequency Response Analysis H3D, OP2, PCH, OPT

Altair Engineering OptiStruct 13.0 Reference Guide 95

Proprietary Information of Altair Engineering


3. The form argument is only applicable for frequency response analysis. It is ignored in
other instances.

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

5. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

6. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.

7. GPFORCE in .op2 output can only be post-processed with the Free Body Diagram (FBD)
tools in HyperMesh.

8. GPFORCE in .h3d output is specifically added for the load transfer path analysis with
NVDirector. It is only available for linear static, frequency response, and acoustic
analyses.

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

96 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GPKE

I/O Options and Subcase Information Entry

GPKE - Output Request for Grid Point Kinetic Energy

Description

The GPKE command can be used in the I/O Options or Subcase Information sections to
request grid point kinetic energy output for normal modes subcases.

Format

GPKE (format_list) = option

Argument Options Description

format <PUNCH, blank> PUNCH: Results are output in Nastran punch results
format (.pch file).
Default = blank

option <YES, ALL, NO, YES, ALL, blank: GPKE results are output for all elements.
NONE, SID>
NO, NONE: GPKEs results are not output.
Default = ALL

SID: If a set ID is given, GPKE results are output


only for grids listed in that set.

Comments

1. Grid point kinetic energy is written in % of the total kinetic energy of all grids in the
structure. Therefore, GPKE results for each grid are the same regardless of the requested
option (ALL, YES, or SID).

2. Note that if the coupled mass matrix is used (PARAM,COUPMASS,YES), then the results at
each GRID are influenced by all GRID connected to that GRID. Using a diagonal mass
matrix formulation (PARAM,COUPMASS,NO) provides more meaningful results.

3. For large problems solved using EIGRA, run times increase if GPKE=ALL or a coupled mass
matrix (PARAM,COUPMASS,YES) is specified, as the entire eigenvector for each mode
must be calculated and stored.

Altair Engineering OptiStruct 13.0 Reference Guide 97

Proprietary Information of Altair Engineering


GPSTRESS/GSTRESS

I/O Options and Subcase Information Entry

GPSTRESS - Output Request

Description

The GPSTRESS command can be used in the I/O Options or Subcase Information sections to
request grid point stresses output for all subcases or individual subcases respectively.

Format
GPSTRESS (format_list, averaging, type) = option

Argument Options Description

format <HM, H3D, PUNCH, HM: Results are output in


OP2, blank> HyperMesh results format
(.res file).
Default = blank
H3D: Results are output in
Hyper3D format (.h3d file).

PUNCH: Results are output in


Nastran punch format (.pch
file).

OP2: Results are output in


Nastran output2 format
(.op2 file) (see comment 8).

blank: Results are output in all


active formats for which the
result is available.

averaging <GLOBAL, BYPROP> GLOBAL: Only the globally averaged


GPSTRESS results are output.
Default = BYPROP

BYPROP, blank: Both the globally averaged


GPSTRESS results and the
GPSTRESS results averaged
by property for each
property are output.

98 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

type <VON, PRINC, MAXS, VON: Only von Mises Stress


SHEAR, ALL, results are output.
TENSOR, DIRECT>
PRINC, MAXS, The von Mises and maximum
Default = ALL SHEAR: principal stress results are
output.

ALL, blank: All stress results are


output.

TENSOR: All stress results are output.


Tensor format is used for
H3D output.

DIRECT: All stress results are output.


Direct format is used for
H3D output.

option <YES, ALL, NO, YES, ALL, blank: Grid point stresses output
NONE, SID> for all elements.

Default = ALL NO, NONE: Grid point stresses are not


output.

SID: If a set ID is given, grid


point stresses are output
only for nodes listed in that
set.

Comments

1. When a GPSTRESS command is not present, grid point stresses are not output.

2. Grid point stresses are only available for solid elements.

3. Grid point stresses are not available for elements which form part of a topology design
space. When an analysis only run is performed, grid point stresses are available for all
solid elements. When PARAM, REANAL is used, grid point stress contributions are only
calculated for fully dense elements.

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

Altair Engineering OptiStruct 13.0 Reference Guide 99

Proprietary Information of Altair Engineering


5. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

6. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.

7. Grid point stresses are output for the entire model and for each individual PSOLID
component. This allows grid point stresses to be accurately obtained at the interface of
two components referencing different material definitions.

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

100 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


HISOUT

I/O Options Entry

HISOUT - Output Control

Description

The HISOUT command can be used in the I/O Options section to control the amount of data
printed to the .hgdata file.

Format
HISOUT = option

Argument Options Description

option <Integer <32> HISOUT value is equal to the sum of the desired options:

Default = 31 1: Design variable.

2: Objective function and maximum percent constraint


violation.

4: All non-stress responses.

8: All DRESP2 responses.

16: All DRESP3 responses.

If blank: no output to .hgdata file.

Example:
If you wanted design variables and all DRESP2 responses,
you would enter:

HISOUT = 9

Comments

1. When a HISOUT command is not present, a value of 31 is assumed.

Altair Engineering OptiStruct 13.0 Reference Guide 101

Proprietary Information of Altair Engineering


HYBDAMP

I/O Options Entry

HYBDAMP – Apply Hybrid Damping to the Residual Structure in a Direct or Transient


Frequency Response Analysis

Description

The HYBDAMP command can be used in the I/O Options section to request modal damping as a
function of the natural frequency of the model in Dynamic Analysis.

Format
HYBDAMP = option

Argument Option Description

option < SID > SID: Set identification of HYBDAMP in bulk data entry.

No default

Comments

1. HYBDAMP can be set at the global level in the I/O Options section. It can exist only once
in the I/O Options section.

102 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


INCLUDE

I/O Options and Bulk Data Entry

INCLUDE - File Selection

Description

The INCLUDE command can be used in the I/O Options, Subcase Information, or Bulk Data
sections to indicate that the contents of another file are to be inserted into the input file at
the exact location of the include command.

Format
INCLUDE option

Argument Options Description

option <filename> filename: the path to and the name of the file to be
included.
No default

Comments

1. INCLUDE commands may be placed at any location in the input file, but must include
information appropriate to that location.

2. Names specified on the INCLUDE card can be arbitrary file names with optional paths
appropriate to the operating system (Windows or UNIX). They may be enclosed in quotes
(double or single quotes can be used), and either forward slash (/) or back slash (\)
characters can be used to separate parts of the path name.

The following rules are used to locate a file referenced on the INCLUDE card:

When the argument contains the absolute path of the file (if it starts with "/" on UNIX
or a drive letter, such as "D:", on Windows, for example), the file at the given location
is used.
When only the file prefix is given (without the path), the file has to be located in the
same directory as the file containing the INCLUDE command.

When the argument contains a relative path (../filename or sub/filename, for


example), it is located in the directory relative to the file containing the INCLUDE
command and is NOT relative to the directory in which the solver was executed, or to
the directory where the main file is located.
3. The INCLUDE command supports path names of up to 200 characters in length. This data
can be on a single line or span multiple continuation lines. See Guidelines for I/O Options
and Subcase Information Entries for an example showing how to enter long file names on
multiple lines.

4. Represented through the master model in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 103

Proprietary Information of Altair Engineering


LIFE

I/O Options and Subcase Information Entry

LIFE – Output Request

Description

The LIFE command can be used in the I/O Options or Subcase Information sections to
request output of fatigue life results for all fatigue subcases or individual fatigue subcases
respectively.

Format
LIFE (format_list) = option

Argument Options Description

format <H3D, OPTI, blank> H3D: Results are output in Hyper3D format (.h3d
file).
Default = blank
OPTI: Results are output in OptiStruct results
format (.fat file).

blank: Results are output in all active formats for


which the result is available.

option <YES, ALL, NO, YES, ALL, Results are output for all elements.
NONE, SID> blank:

Default = ALL
NO, NONE: Results are not output.

SID: If a set ID is given, results are output only


for elements listed in that set.

Comments

1. When a LIFE command is not present, fatigue life results are not output.

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

3. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

104 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


LOADLIB

I/O Options Entry

LOADLIB - External Library and File Reference

Description

The LOADLIB entry can be used in the I/O Options section to define the external libraries and
external files to be loaded into OptiStruct. External functions can be implemented within
dynamic libraries (.dll) under Windows, shared libraries (.so) under Linux, by using
HyperMath (.hml) on Windows and Linux, and external files by using Microsoft Excel (.xls or
.xlsx) on Windows.

Format
LOADLIB = type, group, path

Argument Options Description

type <DRESP3> TYPE identifier that defines the type of library(or


file) to be loaded into OptiStruct. Currently only
No default one type implemented - DRESP3.

group <Character string> GROUP identifier that is referenced by a DRESP3


bulk data entry.
No default

path <Path including file The path to the external shared or dynamic
name and extension> library to be loaded.

No default

Comments

1. Absolute paths (those starting with a drive letter or a slash) will be used as they are
defined on the LOADLIB card. Relative library or file paths will be appended to the path
corresponding to the input deck's location.

2. The total length of information on this card is limited to 200 characters (including the card
name and spaces between arguments). This data can be on a single line or span multiple
continuation lines. See Guidelines for I/O Options and Subcase Information Entries for an
example showing how to enter long file names on multiple lines.

Altair Engineering OptiStruct 13.0 Reference Guide 105

Proprietary Information of Altair Engineering


MBFORCE

I/O Options Entry

MBFORCE – Output Control

Description

The MBFORCE command can be used in the I/O Options section to request force output for a
set of joints and/or force elements from multi-body dynamics subcases.

Format
MBFORCE = option

Argument Options Description

option <YES, ALL, NO, YES, ALL, blank: Force is output for all joints and
NONE, SID> force elements.

Default = ALL NO, NONE: Forces are not output.

SID: If a set ID is given, forces are output only


for joints and force elements listed in that set.

Note: Joints and force elements may share IDs.


When MBFORCE is requested for a SET,
force results are output for all entities
whose ID is part of the SET definition.

Comments

1. When MBFORCE is not present, force results for joints and force elements are not output.

2. The force results for selected joints and force elements are output to the .mrf file.

106 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MECHCHECK

I/O Options Entry

MECHCHECK - Massless Mechanism Check

Description

The MECHCHECK command can be used in the I/O options section to perform a massless
mechanism check on the model.

Format
MECHCHECK

Comments

1. Running the normal mode analysis by adding MECHCHECK helps detect the massless
mechanism where the massless mechanism shows up as rigid body modes.

2. A massless mechanism occurs due to degrees of freedom that do not possess both
stiffness and mass. To find such degrees of freedom, a small amount of mass is added to
the mass matrix so that the massless mechanism shows up as a rigid body mode (the
stiffness matrix K is still zero but the mass matrix M becomes non-zero) in normal modes
analysis. This is the reason why you have to set the lower bound on the EIGRL bulk data
entry to blank or zero when MECHCHECK is used.

3. The analysis results with this card cannot be used since the model is changed internally.
It can only be used to find the massless mechanism. The message “RESULTS FROM THIS
SOLVER RUN ARE INACCURATE AS IT IS IN MECHCHECK MODE” is also displayed in the .out
file when MECHCHECK is included in the I/O Options section of the solver deck.

4. MECHCHECK results (in the .out file) include a list of rigid body modes in the following
format:
ANALYSIS RESULTS:
------------------
ITERATION #
Rigid Modes in Eigenvalue Loadcase: #
-----------------------------------------------------
Mode Grid No. Type x-comp y-comp z-comp
-----------------------------------------------------
1 ## Tran ## ### ###
2 ## Rotn ## ### ###
… …. … etc … … …
-----------------------------------------------------

Altair Engineering OptiStruct 13.0 Reference Guide 107

Proprietary Information of Altair Engineering


MODALDE

I/O Options Entry

MODALDE – Output Request

Description

The MODALDE command can be used above the first SUBCASE or within a SUBCASE definition
to request modal damping energy (the energy loss per cycle) output for all subcases or
individual subcases respectively. Note that this modal damping energy only includes the
energy contribution from viscous dampers. Structural damping and modal damping are not
included.

Format
MODALDE(format_list,THRESH=thresh,RTHRESH=rthresh,TOP=topn,MODES=mset,TYPE=typ
e) = option

Argument Options Description

format <H3D, blank> H3D: Results are output in Hyper3D format (.h3d
file).
Default = blank
blank: Results are output in all active formats for
which the result is available.

thresh <Real> Specifies an absolute threshold under which results should


not be output.
No default

rthresh <Real> Specifies a relative threshold under which results should


not be output. This value is relative to the corresponding
No default total modal energy.

topn <Integer> Specifies that only the top N values should be output.

No default

type <AVERAGE, AVERAGE: The average of the energy is output.


AMPLITUDE, PEAK>

108 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

Default = AVERAGE AMPLITUDE: The amplitude of the energy is output.

PEAK: The peak energy is output. This is the sum


of AVERAGE and AMPLITUDE.

mset <ALL, SID, ALL: Modal energy is output for all modes.
TOTAL>
SID: If a set ID is given, modal energy is output
Default = ALL
only for modes listed in that set.

TOTAL: Only the total energy is output.

option <YES, ALL, NO, YES, ALL, Modal energy is output for all modes.
NONE> blank:
Default = ALL
NO, NONE: Modal energy is not output.

Comments

1. When MODALDE command is not present, modal damping energy is not output.

2. Modal damping energy output is only available for modal frequency response analysis.

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

4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

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

6. Note that this modal damping energy only includes the energy contribution from viscous
dampers. Structural damping and modal damping are not included.

Altair Engineering OptiStruct 13.0 Reference Guide 109

Proprietary Information of Altair Engineering


MODALKE

I/O Options Entry

MODALKE – Output Request

Description

The MODALKE command can be used above the first SUBCASE or within a SUBCASE definition
to request modal kinetic energy output for all subcases or individual subcases respectively.

Format

MODALKE(format_list,THRESH=thresh,RTHRESH=rthresh,TOP=topn,MODES=mset,TYPE=typ
e) = option

Argument Options Description

format <H3D, blank> H3D: Results are output in Hyper3D format (.h3d
file).
Default = blank
blank: Results are output in all active formats for
which the result is available.

thresh <Real> Specifies an absolute threshold under which results should


not be output.
No default

rthresh <Real> Specifies a relative threshold under which results should


not be output. This value is relative to the corresponding
No default total modal energy.

topn <Integer> Specifies that only the top N values should be output.

No default

type <AVERAGE, AVERAGE: The average of the energy is output.


AMPLITUDE, PEAK>
AMPLITUDE: The amplitude of the energy is output.
Default = AVERAGE

110 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

PEAK: The peak energy is output. This is the sum


of AVERAGE and AMPLITUDE.

mset <ALL, SID, ALL: Modal energy is output for all modes.
TOTAL>
SID: If a set ID is given, modal energy is output
Default = ALL
only for modes listed in that set.

TOTAL: Only the total energy is output.

option <YES, ALL, NO, YES, ALL, Modal energy is output.


NONE> blank:
Default = ALL
NO, NONE: Modal energy is not output.

Comments

1. When MODALKE command is not present, modal kinetic energy is not output.

2. Modal kinetic energy output is only available for modal frequency response analysis.

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

4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

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

Altair Engineering OptiStruct 13.0 Reference Guide 111

Proprietary Information of Altair Engineering


MODALSE

I/O Options Entry

MODALSE – Output Request

Description

The MODALSE command can be used above the first SUBCASE or within a SUBCASE definition
to request modal strain energy output for all subcases or individual subcases respectively.

Format

MODALSE(format_list,THRESH=thresh,RTHRESH=rthresh,TOP=topn,MODES=mset,TYPE=typ
e) = option

Argument Options Description

format <H3D, blank> H3D: Results are output in Hyper3D format (.h3d
file).
Default = blank
blank: Results are output in all active formats for
which the result is available.

thresh <Real> Specifies an absolute threshold under which results should


not be output.
No default

rthresh <Real> Specifies a relative threshold under which results should


not be output. This value is relative to the corresponding
No default total modal energy.

topn <Integer> Specifies that only the top N values should be output.

No default

type <AVERAGE, AVERAGE: The average of the energy is output.


AMPLITUDE, PEAK>
AMPLITUDE: The amplitude of the energy is output.
Default = AVERAGE

112 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

PEAK: The peak energy is output. This is the


sum of AVERAGE and AMPLITUDE.

mset <ALL, SID, ALL: Modal energy is output for all modes.
TOTAL>
SID: If a set ID is given, modal energy is output
Default = ALL
only for modes listed in that set.

TOTAL: Only the total energy is output.

option <YES, ALL, NO, YES, ALL, Modal energy is output.


NONE> blank:

Default = ALL
NO, NONE: Modal energy is not output.

Comments

1. When MODALSE command is not present, modal strain energy is not output.

2. Modal strain energy output is only available for modal frequency response analysis.

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

4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

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

Altair Engineering OptiStruct 13.0 Reference Guide 113

Proprietary Information of Altair Engineering


MODEL

I/O Options Entry

MODEL - Output Control

Description

The MODEL command can be used in the I/O Options section to request output of only a
subset of the model and related results for H3D and OUTPUT results files as well as for CMS
superelements.

Format

MODEL = elset, gridset, rigidset

Argument Options Description

elset <SID, PLOTEL, SID: ID of an element SET. A set of elements that


ALL, NONE> describe the subset of the model for which results
and model information is to be output. All GRID
Default and SPOINT associated with these elements will
(analysis run) = also be output.
ALL
PLOTEL: All PLOTELs in the model and their associated
Default (CMS SE GRID will be output.
creation) =
NONE ALL: All elements in the model and their associated
GRID will be output.

NONE: No elements.

gridset <SID, ALL, SID: SID of a SET. A set of grids to be added to the
NONE> subset associated with the preceding elset field.

Default = NONE ALL: All grids.

NONE: No grids are added to the subset described by


the preceding elset field.

rigidset <RIGID/ALL, RIGID/ All rigid elements and their associated GRID will be
NORIGID/NONE, ALL: output.
SID>

Default
(analysis run)
=RIGID/ALL

114 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

Default (CMS SE
NORIGID/ No rigid elements will be output.
creation) = NONE:
NORIGID/NONE

SID: ID of a rigid element SET. A set of rigid elements


that describe the subset of the model for which
model information is to be output. All GRID and
SPOINT associated with these rigid elements will
also be output.

Comments

1. For CMS superelements output in h3d format, only the ASET DOF are output when the
MODEL data is not present. When the MODEL data is present, the .h3d file contains the
ASET DOF and what is specified on the MODEL data.

2. In addition to the results output, the MODEL data controls the portion of the model that is
written to the .op2 and .h3d files.

3. When PARAM,EXCOUT with values of 0, 3, 4, 5 or 6 is used during CMS superelement


creation, the default is to output the entire model, as well as results to the .h3d file and
AVL/EXCITE files.

Altair Engineering OptiStruct 13.0 Reference Guide 115

Proprietary Information of Altair Engineering


MPCFORCE

I/O Options and Subcase Information Entry

MPCFORCE - Output Request

Description

The MPCFORCE command can be used in the I/O Options or Subcase Information sections to
request multi-point force of constraint vector is output for all subcases or individual subcases
respectively.

Format
MPCFORCE (sorting, format, form_list, peakoutput, modal) = option

Argument Options Description

sorting <SORT1, SORT2> This argument only applies to the PUNCH format (.pch file) or
the OUTPUT2 format (.op2 file) output for normal modes,
Default = blank frequency response, and transient subcases. It will be
ignored without warning if used elsewhere.

SORT1: Results for each frequency/timestep are grouped


together.

SORT2: Results for each grid/element are grouped


together (See comment 5).

blank: For frequency response analysis, if no grid SET is


specified, SORT1 is used, otherwise, SORT2 is
used; for transient analysis, SORT2 is used.

format <OPTI, PUNCH, OPTI: Results are output in OptiStruct results format
OP2, PLOT, (.mpcf file).
blank>
PUNCH: Results are output in Nastran punch results
Default = blank format (.pch file).

OP2: Results are output in Nastran otput2 format


(.op2 file) (see comment 6).

PLOT: Results are output in Nastran output2 format


(.op2 file) when PARAM, POST is defined in the
bulk data section.

116 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

blank: Results are output in all active formats for which


the result is available.

form <REAL, IMAG, REAL, Provides rectangular format (real and imaginary)
PHASE> IMAG: of complex output.

Default = REAL
PHASE: Provides polar format (phase and magnitude) of
complex output.

peakoutpu <PEAKOUT> PEAKOUT: If PEAKOUT is present, only the filtered


t frequencies from the PEAKOUT card will be
Default = blank considered for this output.

modal <MODAL> MODAL: If MODAL is present, multi-point constraint


forces of the structural modes and residual
Default = blank
vectors are output to the PUNCH and OUTPUT2
files for modal frequency response and transient
analysis.

option <YES, ALL, NO, YES, ALL, Multi-point force of constraint vector is output
NONE, SID> blank: for all grids.

Default = ALL
NO, NONE: Multi-point force of constraint vector is not
output.

SID: If a set ID is given, multi-point force of


constraint vector is output only for grids listed in
that set.

Comments

1. When an MPCFORCE command is not present, multi-point force of constraint vector is not
output.

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

Altair Engineering OptiStruct 13.0 Reference Guide 117

Proprietary Information of Altair Engineering


3. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

4. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were use; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.

5. In general, HyperView does not recognize the SORT2 format for results from the .op2 file.
When results are output only in SORT2 format (<Result Keyword> (SORT2, OUTPUT2, …
.)), the results are written by OptiStruct into the .op2 file in SORT2 format, but when
the .op2 file is imported into HyperView, the results in SORT2 format are not recognized.
Therefore, the SORT1 option is recommended for results output in OUTPUT2 format and
SORT2 option is recommended for results output in PUNCH format.

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

118 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MSGLMT

I/O Options and Subcase Information Entry

MSGLMT - Output Control

Description

The MSGLMT command can be used in the I/O Options section to limit the number of ERROR,
WARNING and INFORMATION messages output, or to elevate a WARNING or INFORMATION
message to an ERROR.

Format

MSGLMT (type) = value

MSGLMT, type, value

MSGLMT, mode

Examples
MSGLMT (WARNING) = 1000

MSGLMT (101) = 50

Argument Options Description

type <ERROR, ERROR: Limits the total number of ERROR


WARNING, ID> messages allowed to the value
provided. Once this limit is reached,
No default the run terminates.

WARNING: Limits the total number of WARNING and


INFORMATION messages reported in
the .out file to the value provided.

ID: Limits the number of instances of a


message with the given ID reported in
the .out file to the value provided.

value <INTEGER, OFF, INTEGER: If a positive integer is given, the limit is


NONE, ERROR, set to this number.
ABORT>

See comments 1
and 2 for

Altair Engineering OptiStruct 13.0 Reference Guide 119

Proprietary Information of Altair Engineering


Argument Options Description

defaults. OFF or NONE: “value=NONE” can only be used if “type


= ID”. See Comment 3.

ERROR: Valid only when the type is ID.

Messages with this ID will be treated as


ERRORs, that is, continuation at the end
of the current stage will be disallowed
unless the message is encountered
during the solver, where full post-
processing of the results will be allowed
before termination; optimization runs will
terminate as if the limit of allowed
iterations had been reached.

ABORT: Valid only when type is ID.

Messages with this ID will be treated as


abort ERRORs, that is, the solver will
terminate immediately. If the message
is encountered during the solver, no
output files will be generated. If it
happens during reading or verification of
input data, then remaining parts of
input will not be processed.

mode
<STRICT, STRICT: All messages are printed according to
UNREF, BRIEF> MSGLMT.

Default = UNREF: Messages 1931, 1932 and 2010 are


<BRIEF>
suppressed.

BRIEF: Messages 741, 742, 1935, 1931, 1932,


2010, 1052, 1305, and 1436 are
suppressed.

Comments

1. By default, the limit for most individual ERROR and WARNING/INFORMATION messages is
10.

2. The default limit for the total number of ERROR messages is 10,000 and for the total
number of WARNING/INFORMATION messages is 1,000.

3. The following table lists some special cases of MSGLMT usage:

120 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Special Cases Effect

MSGLMT(Message ID/WARNING/ Prevents any information about


ERROR) = 1 consecutive occurrences of the
specified message to be registered
and counted.

If WARNING/ERROR is used, only the


first WARNING/ERROR is printed.

MSGLMT(Message ID/WARNING/ Message ID: All occurrences of the


ERROR) = 0 specified message will be displayed.

MSGLMT(Message ID/WARNING/ WARNING: All Warnings will be


ERROR) = OFF displayed.

ERROR: All Errors will be displayed.

MSGLMT(Message ID) = NONE The specified message (and multiple


occurrences of the same, if any) will
not be printed in the output file.

Note:
1. If the Message ID belongs to an
error, the specified error and multiple
occurrences of the same error will
not be printed in the output file.
However, this will not allow the
solver to continue after error
suppression. This can sometimes
generate an output file which states
that an error occurred without any
information regarding the nature of
the error, since it was suppressed.

2. Suppressed ERROR/WARNING
messages still count toward
respective limits and are reported in
the job summary.

3. Using MSGLMT(Message ID)=NONE


for ERROR messages is not
recommended.

MSGLMT(Message ID) = <Negative Negative values are not supported. A


Integer> “Syntax error” will be displayed, if
negative integer values are used.

4. MSGLMT may be set in the OptiStruct Configuration File.

5. Multiple instances of MSGLMT may occur. If any instances conflict, then the last instance
will be honored.

Altair Engineering OptiStruct 13.0 Reference Guide 121

Proprietary Information of Altair Engineering


6. Some messages print lists of ID's, which can be very long, MSGLMT can be used to control
the number of ID's that are printed.

For Example:

MSGLMT, 1692, <Integer> or MSGLMT (1692) =<integer>, prints the first <integer>
number of duplicate GRID ID’s:

*** WARNING # 1692

Found duplicate GRID cards, removed 74 item(s) of identical data.

10001 10002 … (up to <integer> number)

MSGLMT, 1692, OFF or MSGLMT (1692) =OFF, prints all duplicate GRID ID’s:

*** WARNING # 1692

Found duplicate GRID cards, removed 86 item(s) of identical data.

10001 10002 10003 10004 10005

122 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


NLRESTART

I/O Options Entry

NLRESTART - Run Control Command

Description

The NLRESTART command can be used in the I/O Options section to indicate the current
nonlinear solution sequence is to be restarted from a specified nonlinear subcase.

Format
NLRESTART = n

Argument Description

n Nonlinear SUBCASE ID to be restarted from in the current


nonlinear solution sequence.

If n is not given, it will restart from the first nonlinear subcase


ending with error in previous run.

Comments

1. This command applies only to geometric nonlinear subcases (ANALYSIS = NLGEOM,


IMPDYN or EXPDYN).

2. Only one NLRESTART entry can be defined, and it must be above the first subcase.

3. NLRESTART is also available in command line option as “-nlrestart n” or “-nlrestart.”


If NLRESTART is defined in both bulk data and command line option, the former overrides
the latter.

Altair Engineering OptiStruct 13.0 Reference Guide 123

Proprietary Information of Altair Engineering


OFREQUENCY

I/O Options and Subcase Information Entry

OFREQUENCY - Output Control

Description

The OFREQUENCY command can be used in the I/O Options or Subcase Information sections to
request a set of frequencies for output requests for all subcases or individual subcases
respectively.

Format
OFREQUENCY = option

Argument Options Description

option <ALL, SID> ALL, blank: Output is for all frequencies.

Default = ALL
SID: If a set ID is given, output is only for
frequencies listed in that set.

Comments

1. When OFREQUENCY is not present, output is for all frequencies.

2. The SET definition referenced by the OFREQUENCY card must be a real value set.

3. The number of solutions selected will always be equal to the number of quantities in the
selected set. The closest values will be used.

124 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


OLOAD

I/O Options and Subcase Information Entry

OLOAD - Output Request

Description

The OLOAD command can be used in the I/O Options or Subcase Information sections to
request the form of applied load vector output for all subcases or individual subcases
respectively.

Format
OLOAD (format_list,type) = option

Argument Options Description

format <H3D, OPTI, PUNCH, H3D: Results are output in Hyper3D


OP2, blank> format (.h3d file).

Default = blank OPTI: Results are output in


OptiStruct results format
(.load file).

Results are output in Nastran


PUNCH:
punch results format (.pch
file).
Results are output in Nastran
OP2:
output2 format (.op2 file)
(see comment 6).

blank: Results are output in all active


formats for which the result is
available.

type <SPARSE, ALL> ALL: Output for all selected nodes


is printed.
Default (OPTI) = SPARSE
SPARSE: This is only available for the
Default (H3D, PUNCH, OP2) OPTI output format. Output
= ALL for selected nodes without a
component of magnitude
1.0e-10 is not printed.

Altair Engineering OptiStruct 13.0 Reference Guide 125

Proprietary Information of Altair Engineering


Argument Options Description

option <NONE, NO, YES, ALL, YES, ALL, Load data is output for all
SID> blank: nodes.

Default = ALL
NO, NONE: Loads are not output.

SID: If a set ID is given, load data


is only output for nodes listed
in that set.

Comments

1. When OLOAD command is not present, loads are not output.

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

3. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

4. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.

5. The SPARSE output type is only available when the OPTI output format is used.

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

126 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


OMODES

I/O Options Entry

OMODES - Output Control

Description

The OMODES command can be used in the I/O Options or Subcase Information sections to
request a set of modes for output requests for all subcases or for individual subcases,
respectively. This command is applicable for normal modes and linear buckling solution
sequences only.

Format
OMODES = option

Argument Options Description

option <ALL, SID> ALL, blank: Output is calculated for all modes.

Default = ALL
SID: If a set ID is given, output is calculated for
only modes listed in that set.

Comments

1. When OMODES is not present, output is for all modes.

2. The SET definition referenced by the OMODES card must be an integer value set.

3. This output control is not available for frequency response subcases; OFREQUENCY should
be used instead.

4. If both the OMODES and OFREQUENCY requests appear, the OMODES request takes
precedence.

Altair Engineering OptiStruct 13.0 Reference Guide 127

Proprietary Information of Altair Engineering


OTIME

I/O Options and Subcase Information Entry

OTIME - Output Control

Description

The OTIME command can be used in the I/O Options or Subcase Information sections to
request a set of times for output requests for transient analysis for all subcases or individual
subcases respectively.

Format
OTIME = option

Argument Options Description

option < ALL, SID > ALL, blank: Output is at all times.

Default = ALL
SID: If a set ID is given, output is only at times in
that set.

Comments

1. When an OTIME command is not present the output for all times will be computed.

2. This command is particularly useful for requesting a subset of the output (for example,
stresses at only peak times, and so on).
\

128 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


OUTFILE

I/O Options Entry

OUTFILE - Filename Definition

Description

The OUTFILE command is used in the I/O Options section to define the prefix for the results
files output.

Format
OUTFILE = option

Argument Options Description

option <file prefix> file prefix: The path to and file prefix used for
the results files output.
Default = passed
in from the
command line.

Comments

1. Prefixes specified on the OUTFILE card can be arbitrary file prefixes with optional paths
appropriate to the operating system (Windows or UNIX). They may be enclosed in quotes
(double or single quotes can be used), and either forward slash (/) or back slash (\)
characters can be used to separate parts of the path name.

The following rules are used for the OUTFILE card:

When the argument contains an absolute path of the file (if it starts with "/" on UNIX
or a drive letter, such as "D:", on Windows, for example), output files are created at
the given location.
When only the file prefix is given (without the path), output files will be created in the
current directory, meaning the directory from which the solver has been executed, and
not in the directory where the input file is located.
When the argument contains a relative path (../filename or sub/filename, for
example), output is created in a directory relative to where the solver is executed and
NOT relative to the directory where the input file is located.
2. The total length of information on this card is limited to 200 characters (including the card
name and spaces between arguments). This data can be on a single line or span multiple
continuation lines. See Guidelines for I/O Options and Subcase Information Entries for an
example showing how to enter long file names on multiple lines.

Altair Engineering OptiStruct 13.0 Reference Guide 129

Proprietary Information of Altair Engineering


OUTPUT

I/O Options Entry

OUTPUT – Output Control

Description

The OUTPUT command can be used in the I/O Options section to control the format of results
output and the creation of certain results files.

Format
OUTPUT, keyword, frequency, option1, option2

Argument Options Description

keyword See below See below

frequency FIRST, LAST, FIRST: Output first iteration only.


FL, ALL, NONE,
N or blank
LAST: Output last iteration only.

FL: Output first and last iterations.

ALL: Output all iterations.

NONE: No output

N: Output first and last iterations and every Nth


iteration. If N=5, output occurs at iterations
0, 5, 10, 15, 20, and so on, and the final
iteration.

blank: The default listed below for the given


keyword.

option See below See below

Standard Result Outputs

Note that if there is no result OUTPUT defined, then default result output is both HM and
H3D. If any result OUTPUT commands exist, then there is no default OUTPUT type.

130 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Affect
Default
Keyword Description ed Options Details
frequency
files

HM Output FL *.res <NODMIG, Determines whether or not to


results in DMIGALL, output results for interior
HyperMesh DMIGSET> points of external
binary superelements. See
format. Default = comment 16.
DMIGSET
NODMIG: recovery is
deactivated

DMIGALL: recovery is
activated for all grids/
elements

DMIGSET: recovery is
activated for grids/elements
in the SET defined on the
corresponding output request
(default)

H3D, Output FL *.h3d <BYSUB, Determines the way the


HV results in BYITER> output files are arranged in
Hyper3D an optimization run. See
format. Default = comment 15.
BYSUB

(Applicable to
optimization
runs only).

<NODMIG, Determines whether or not to


DMIGALL, output results for interior
DMIGSET> points of external
superelements. See
Default = comment 16.
DMIGSET
NODMIG: recovery is
deactivated

DMIGALL: recovery is
activated for all grids/
elements

DMIGSET: recovery is
activated for grids/elements
in the SET defined on the
corresponding output request

Altair Engineering OptiStruct 13.0 Reference Guide 131

Proprietary Information of Altair Engineering


Affect
Default
Keyword Description ed Options Details
frequency
files

(default)

OP2, Output FL *.op2 <MODEL, Turns on / off the output


OUT2, analysis NOMODEL> of the model data to the file.
OUTPUT2 results in
Nastran Default =
output2 MODEL See comments 11 and 12.
format.
<NODMIG, Determines whether or not to
DMIGALL, output results for interior
DMIGSET> points of external
superelements. See
Default = comment 16.
DMIGSET
NODMIG: recovery is
deactivated

DMIGALL: recovery is
activated for all grids/
elements

DMIGSET: recovery is
activated for grids/elements
in the SET defined on the
corresponding output request
(default)

NASTRAN Output FL *.pch <NODMIG, Determines whether or not to


, PUNCH analysis DMIGALL, output results for interior
results in DMIGSET> points of external
Nastran superelements. See
punch Default = comment 16.
format. DMIGSET
NODMIG: recovery is
deactivated

DMIGALL: recovery is
activated for all grids/
elements

132 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Affect
Default
Keyword Description ed Options Details
frequency
files

DMIGSET: recovery is
activated for grids/elements
in the SET defined on the
corresponding output request
(default)

OPTI, Output FL *.cstr - -


ASCII, results in ,
OS OptiStruct *.dens
ASCII ,
format. *.disp
,
*.forc
e,
*.gpf,
*.load
,
*.mpcf
,
*.spcf
,
*.strs

PATRAN, Output FL *.#.#. - -


APATRAN analysis #.dis,
results in *.#.#.
Patran dis,
ASCII *.#.#.
format. els,
*.#.di
(APATRAN s,
uses an *.#.el
alternate s,
file naming
convention *.#.#.
, with the dis.#,
iteration *.#.di
number s.#,
after the *.#.el
file s.#,
extension). *.dis.
#,
*.els.
#

Altair Engineering OptiStruct 13.0 Reference Guide 133

Proprietary Information of Altair Engineering


Affect
Default
Keyword Description ed Options Details
frequency
files

NONE Results are - - - -


not output
in any of
the
formats
listed
above.

Optimization Outputs

Default
frequenc Affected
Keyword Description Options Details
y files

DESIGN Controls the ALL All files that - -


frequency of design results
output for are written
design results to.
such as
DENSITY,
SHAPE, and
THICKNESS

SHRES Controls the L *.sh, - -


frequency of *.grid
output of the
shape files.

GRID Requests the L *.grid <LOCAL, BASIC> BASIC: Grid


output of the definitions are
state file (.grid Default = BASIC output to the
file) for .grid file,
topography or referencing the
shape basic coordinate
optimization. system.

LOCAL: Grid
definitions are
output to the
.grid file,
referencing local
coordinate
systems as

134 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Default
frequenc Affected
Keyword Description Options Details
y files

defined by the
CP field on the
GRID definitions.

FSTOSZ Automatic L *_sizing.fe 1. Bundles See comment 18.


generation of m
a sizing model Integer > 0
after free- Default = 4
sizing of a
composite 2. Method
structure. <ADVFREE,
ADVMAN,
SIMFREE,
SIMMAN>

Default =
ADVFREE

3. Ignore
<IGNORE>-

SZTOSH Automatic L *_shuffling - -


generation of .fem
a shuffling
model after
ply-based
sizing
optimization.

FSTHICK Controls - *.fsthick <YES, NO> See comment


output of free- 13.
sizing results Default = NO
to .fsthick
file.

DESVAR Requests the L *.desvar, <FILE, OUT, FILE: Updated


output of *.out BOTH, NONE> property design
updated variable values
design variable Default = FILE are output to
values. the .desvar file.

OUT: Updated
design variable
values are output
to the .out file.

Altair Engineering OptiStruct 13.0 Reference Guide 135

Proprietary Information of Altair Engineering


Default
frequenc Affected
Keyword Description Options Details
y files

BOTH: Updated
design variable
values are output
to both the .out
file and the
.desvar file.

NONE: Updated
design variable
values are not
output.

PROPERTY Requests the L *.prop, <ANY, DESIGN, ANY: All


output of the *.out FILE, OUT, properties are
updated BOTH, NONE> output.
property
definitions. Default = DESIGN: Only
DESIGN designable
Note:
properties are
In the
output.
Description
and Details FILE: Updated
columns of the property
PROPERTY definitions and
keyword: non-design
“Property” properties are
stands for output to the
.prop file.
“Properties,
Materials and
OUT: Updated
Elements”.
property
definitions and
non-design
properties are
output to the
.out file.

BOTH: Updated
property
definitions and
non-design
properties are
output to both
the .out file and
the .prop file.

136 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Default
frequenc Affected
Keyword Description Options Details
y files

NONE: Updated
property
definitions are
not output.

Specialized Result Outputs

Default
Keyword Description Affected files Options Details
frequenc
y

ADAMSMNF Output of - *.mnf <YES, NO> -


flexible body to
a modal neutral Default = YES
file for
MSC.ADAMS.

See comment
17.

HGFREQ Frequency FL *_freq.mvw, - -


Analysis output *_s#_a.frf,
presentation for *_s#_d.frf,
HyperGraph. *_s#_v.frf

See comment
3.

HGTRANS Transient - *_tran.mvw, - -


Analysis output *_s#_a.trn,
presentation for *_s#_d.trn,
HyperGraph. *_s#_v.trn

See comments
2 and 3.

Altair Engineering OptiStruct 13.0 Reference Guide 137

Proprietary Information of Altair Engineering


Default
Keyword Description Affected files Options Details
frequenc
y

HGMBD Multi-body - *_mbd.mvw, - -


Dynamics *_s#_a.mbd,
output *_s#_d.mbd,
presentation for *_s#_v.mbd
HyperGraph.

See comments
2 and 3.

HGSENS Sensitivity FL *_sens.#.mvw, <ALL, See comment 4


output NOSTRESS, for details on
presentation for *.#.sens STRESS> options.
HyperGraph.
Default =
NOSTRESS

MSSENS Sensitivity FL *.#.slk <ALL, See comment 4


output in NOSTRESS, for details on
Microsoft Excel STRESS> options.
SYLK format.
Default =
NOSTRESS

ASCSENS Topology and FL *.#.asens <ALL, See comment 4


free-sizing NOSTRESS, for details on
sensitivity STRESS> options.
(response with
respect to Default =
design element NOSTRESS
density) output
in ASCII format.

H3DSENS Sensitivity FL *_dsa.#.h3d <USER, See comment


output in H3D NOUSER> 19 for details
format. on options.
Default =
NOUSER

H3DTOPOL Sensitivity FL *_topol.#.h3d <ALL, See comment 4


output in H3D NOSTRESS, for details on
format for STRESS> options.
contouring of
topology and Default =

138 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Default
Keyword Description Affected files Options Details
frequenc
y

free-sizing NOSTRESS
sensitivity.

H3DGAUGE Sensitivity FL *_gauge.#.h3d <ALL, See comment 4


output in H3D NOSTRESS, for details on
format for STRESS> options.
contouring of
shell thickness Default =
sensitivity. NOSTRESS

HGHIST Design history - *_hist.mvw, Integer < 32 See comment 5


output *.hist for details on
presentation for *.hgdata Default = 31 options.
HyperGraph.

HGEFFMASS Effective mass - *.mass, - -


is output as a *_mass.mvw
HyperGraph bar
chart.

HGMODFAC Modal FL *_modal.mvw, <REGULAR, See comment


participation *_modal.#.mvw NORM> 14.
factor output
presentation for Default =
HyperGraph3D. REGULAR

DVGRID Output of - *.dvgrid - -


shape variable
definitions to
.dvgrid file.

See comment
6.

MASSPROP Controls the FL *.out - The center of


output of gravity is
Center of specified in the
Gravity and basic
Mass Moments coordinate
of Inertia tables system. The
based on Mass Properties
properties to are with
.out file. respect to the

Altair Engineering OptiStruct 13.0 Reference Guide 139

Proprietary Information of Altair Engineering


Default
Keyword Description Affected files Options Details
frequenc
y

center of
gravity of the
item.

MASSCOMP Controls the FL *.out - -


output of Mass
based on
HyperMesh
Components to
.out file.

REGCOMPL Controls the *.out <YES, NO>


output of
regional Default = YES
compliance
table to .out
file.

File Output Controls

Default
Keyword Description frequenc Affected files Options Details
y

CMF Controls output - *.HM.badel.c <YES, NO>


of .cmf files. mf, Default = YES
*.HM.comp.cm
f,
*.HM.ent.cmf
,
*.HM.conn.cm
f

OSS Controls output - *.oss <YES, NO>


of .oss file. Default = YES

HTML Controls output - *.html <YES, NO>


of .html file. Default = YES

STAT Controls output - *.stat <YES, NO> See comment 9.

140 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Default
Keyword Description frequenc Affected files Options Details
y

of .stat file. Default = YES

Comments

1. Frequency does not apply for any of the keywords where a dash (-) is given as the
default frequency in the keywords table above.

2. HGTRANS and HGMBD are currently available for analysis only.

3. HGFREQ, HGTRANS, and HGMBD will only use output requests where a Set ID is specified.
For example, if DISPLACEMENT = ALL or DISPLACEMENT(HG) = ALL is given, displacement
information will not be present in the presentation, whereas if DISPLACEMENT = 1 or
DISPLACEMENT(HG) = 1 is given, displacement information will be present in the
presentation for the constituent nodes of Set 1.

4. For HGSENS, ASCSENS, or MSSENS options:

If NOSTRESS or blank: results are printed, but stress, strain, and force responses are
ignored.

If ALL or STRESS: results are printed, including stress, strain, and force responses.

5. For HGHIST options:

The integer value given is equal to the sum of the desired options:

1: Design Variable.

2: Objective function and maximum % constraint violation.

4: All non-stress responses.

8: All DRESP2 responses.

16: All DRESP3 responses.

If blank: all of the above are output.

For example: If you want Design Variables and all DRESP2 responses, you would use 9.

6. The DVGRID option creates shape variable definitions for displacement or eigenvector
results of linear static, normal modes, or liner buckling analyses. These shape variable
definitions can then be used in subsequent optimizations. This process facilitates the use
of "natural" shape functions.

7. For the keywords HM, H3D, HV, ASCII, OPTI, OS, NASTRAN, PUNCH, OP2, OUT2,
OUTPUT2, PATRAN and APATRAN, the information provided by the OUTPUT I/O option
entry takes precedence over information provided on the older FORMAT and RESULTS I/O
option entries.

8. OUTPUT entries are read sequentially; therefore, where multiple OUTPUT entries exist with
the same keyword, the last instance is used.

Altair Engineering OptiStruct 13.0 Reference Guide 141

Proprietary Information of Altair Engineering


9. If OUTPUT,STAT,NO is defined, the *.stat file is deleted at the end of the run (as long as
the run was successful), but the file always exists during the run.

10. OUTPUT,DESIGN takes precedence over the information provided on the older DENSRES I/O
option entry. OUTPUT,DESIGN will write design results, at the frequency defined, to all
active output formats (HM, H3D, or OPTI), regardless of the frequency chosen for that
output format. By default, HM is the only active output format.

11. When CMSMETH is used, or when a full multi-body dynamics run is performed, the CMS
stress modes can be written to OP2 format. This only happens when OUTPUT,OP2 (or
FORMAT,OP2) is defined. One file for each is generated. Stresses are written for shells
and solids, while forces are written for bars/beams and welds. Each mode is written as a
static load case with ID equal to the mode index. This output is compatible with FEMFAT
by MAGNA.

12. The MODEL/NOMODEL option for OUTPUT, OP2 may be overridden by the PARAM, OGEOM
bulk data entry.

13. The FSTHICK keyword generates a file with the .fsthick extension. The file contains
bulk data entries for elements (CQUAD4, CQUAD8, CTRIA3, and CTRIA6) contained in free-
size design spaces. The element definitions have the optimized thickness defined as
nodal thicknesses (Ti) for each element.

14. The HGMODFAC keyword generates a HyperGraph3D presentation providing 3D plots of


modal participation factors. The plots display the mode number on the x-axis, the
frequency (for frequency response analyses) or time (for transient analyses) on the y-
axis and the modal participation factor on the z-axis.

The NORM option normalizes the participation factors with respect to 1.

In HyperGraph3D, it is possible to define cross-sections to generate 2D plots of either:

a) Modal participation factor vs. frequency or time for a given number.

b) Modal participation factor vs. mode number at a given frequency or time.

For frequency response analyses, plots are generated for the real part, the imaginary part
and the magnitude of the participation factors. Magnitude plot is visible by default, while
real and imaginary plots are hidden by default.

15. The H3D output from optimization runs consists of a number of files. The BYSUB/BYITER
option allows switching between two modes of H3D output. There is a no default option
(BYSUB/BYITER) for analysis runs.

BYSUB (This is the default option for optimization runs) outputs one _des.h3d file for
the animation of the optimization history. The frequency of the optimization results in
this file is defined by OUTPUT, DESIGN (Default = ALL). In addition, an _si.h3d file for
each subcase i is written that contains the history of the analysis results for each
subcase. Frequency determines the analysis result output frequency. Optimization
results can be written to the subcase files using DENSITY, SHAPE, or THICKNESS output
requests.

(Using OUTPUT, H3D, or BYSUB for analysis runs (without optimization) will output the
same files as above (except for the _des.h3d file), however no design results or
analysis history will be available within the files).

142 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


BYITER outputs one .#.h3d file per iteration that contains the optimization and
analysis results for all subcases per iteration. Frequency determines at which iteration
these files are created. It overwrites the default of OUTPUT, DESIGN unless an actual
OUTPUT, DESIGN statement is present. In the case of a shape optimization, the GRID
coordinates of the model in the respective iteration are updated to the new shape.

(Using OUTPUT, H3D, or BYITER for analysis runs (without optimization) will output
only one .h3d file since there are no multiple iterations).

16. Results for interior points of external superelements will be output by default to HM, H3D,
PUNCH, and OP2 files.

17. If GPSTRESS output is requested in addition to OUTPUT, ADAMSMNF, then nodal stress
results for solid elements will be written to the .mnf file.

18. For FSTOSZ options:

Bundles: This specifies the number of ply bundles to be generated per fiber orientation.

Method: Ply bundle thicknesses are determined based on the method defined.

ADVFREE: Advanced algorithm with free thicknesses.

ADVMAN: Advanced algorithm with manufacturable thicknesses.

SIMFREE: Simple algorithm with free thicknesses.

SIMMAN: Simple algorithm with manufacturable thicknesses.

The advanced algorithm is available for 2, 4 and 8 ply bundles. It takes into account the
thickness distribution when generating the ply bundles, which results in a more accurate
representation of the original free-sized thickness profile.

Ply bundle thickness can also be multiples of the manufacturable ply thickness.

Ignore: Elements may be ignored in a given ply orientation when their thickness is less
than 5% of the maximum thickness. This option is inactive by default.

19. H3DSENS, USER indicates that the user-defined responses should be included in the DSA
output. NOUSER indicates that user-defined responses should not be included. In both
cases, responses defined through the DSA output request are included in the DSA output.

Altair Engineering OptiStruct 13.0 Reference Guide 143

Proprietary Information of Altair Engineering


PFGRID

I/O Options Entry

PFGRID – Output Request for Acoustic Grid Participation

Description

The PFGRID command can be used in the I/O Options section to request output of acoustic
grid participation factors for all frequency response subcases. The output will be in the .h3d
file.

Format
PFGRID (GRIDS=setg, GRIDF=setfl, FREQUENCY=setf, NULL=ipower, RPCUTOFF=rval,
RPDBACUT=rpdba, CONTOUR=YES/NO,PEAKOUT) = setdof/PEAKOUT

Examples
PFGRID(FREQUENCY=391)=12

PFGRID(PEAKOUT)=23

PFGRID(PEAKOUT)=PEAKOUT

Argumen Options Description


t

setg <ALL, NONE, ALL: Output acoustic grid participation for all structural grid
SID> points at the fluid-structure interface.

Default = NONE NONE: Do not output acoustic grid participation for any
structural grid points.

SID: Output acoustic grid participation factors for a set of


grids. SID refers to the ID of a SET of type GRID.

setfl <ALL, NONE, ALL: Output acoustic grid participation for all fluid grid points
SID> at the fluid-structure interface.

Default = NONE NONE: Do not output acoustic grid participation for any fluid
grid points.

SID: Output acoustic grid participation factors for a set of


grids. SID refers to the ID of a SET of type GRID.

144 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argumen Options Description
t

setf <ALL, SID> ALL: Participation factors are processed for all excitation
frequencies.
Default = ALL
SID: Participation factors are only processed for a set of
excitation frequencies. SID refers to the ID of a SET of
type FREQ.

ipower <INTEGER> When the magnitude of a grid participation is below 10 to the


minus ipower, the grid participation will not be output. In other
Default = 30
words, if the grid participation is less than 10-ipower, the result
output for this grid will be skipped.

rval <REAL> The grid participation will be calculated at the excited


frequencies when the magnitude of the pressure is above rval.
Default = 0.0 The excitation frequency will be a subset of setf.

rpdba <Non- RPDBACUT is the decibel pressure cutoff value for fluid
Negative responses, and is similar to RPCUTOFF. It will take precedence
REAL> over RPCUTOFF for fluid responses. A weighting is applied to
RPDBACUT values at the excitation frequency. The grid
Default = 0.0
participation will be calculated when the magnitude of the
response is about the cutoff value. See comment 4 for decibel
calculations and reference pressure settings.

CONTOUR (YES/NO) If CONTOUR is specified as YES, the area projected value for the
fluid grid participation is output. Otherwise, the output of fluid
Default = YES grid participation would be the actual complex value.

PEAKOUT If PEAKOUT is present as an option inside the parenthesis of the PFGRID data,
then the filtered frequencies from the PEAKOUT data will be considered for output
of grid participation.

Altair Engineering OptiStruct 13.0 Reference Guide 145

Proprietary Information of Altair Engineering


Argumen Options Description
t

setdof/ <SID/ Degrees of freedom for which the grid participation factors are
PEAKOUT PEAKOUT> to be processed. SID refers to the ID of a SET of type GRID.
If “PEAKOUT” is specified instead of SID, the output will be
considered at the filtered frequencies corresponding to the
degree of freedom in the PEAKOUT card in the bulk section.

Comments

1. Output is to the H3D file only.

2. Acoustic grid participation factors are available in a coupled frequency response analysis
(both in direct and modal frequency response).

3. The FREQUENCY keyword can be used to select a subset of excitation frequencies


available.

4. The dB value is calculated using 20 * log10(P/P0), where P0 is the reference pressure.


The reference pressure is dependent on the units specified on the UNITS input data. If
the units are SI, the value is set as 2.0E-5 Pa. If they are CGS, it is set as 2.0E-4 barye.
If they are MPa, it is set as 2.0E-11 MPa. If they are BG or EE, then it is set as 4.17E-7
lbf/ft 2. If no UNITS data is present, the default value is 2.0E-11 MPa.

146 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PFMODE

I/O Options Entry

PFMODE – Output Request for Modal Participation

Description

The PFMODE command can be used in the I/O Options section to request output of modal
participation factors for all modal frequency response subcases.

Format
PFMODE (type, FLUIDMP=fmp, STRUCTMP=smp, PANELMP=setp, FREQUENCY=setf,
FILTER=fratio, NULL=ipower, RPCUTOFF=rval, RPDBACUT=rpdba, MTYPE=otype,
CMSSET=seset, RTYPE=rtype, outfile, PEAKOUT) = setdof/PEAKOUT

Examples
PFMODE(FLUID,STRUCTMP=30,FREQUENCY=391,PANELMP=ALL)=393

PFMODE(STRUCTURE,H3D)=23

PFMODE(FLUID,H3D,PEAKOUT)=11

PFMODE(STRUCTURE,H3D,PEAKOUT)=PEAKOUT

PFMODE(FLUID,PUNCH)=31

Argument Options Description

type <STRUCTURE, STRUCTURE: Requests output of structural modal participation


FLUID> factors.

Default = FLUID: Requests output of acoustic modal participation


STRUCTURE
factors.

fmp <ALL, N, ALL: Participation factors will be computed for all


NONE> calculated fluid modes.

Default = NONE N: Number of fluid modes for which modal


participation factors will be computed, based on
the largest magnitude of modal contribution.

NONE: Participation factors are not calculated for fluid


modes.

Altair Engineering OptiStruct 13.0 Reference Guide 147

Proprietary Information of Altair Engineering


Argument Options Description

smp <ALL, N, ALL: Participation factors will be computed for all


NONE> calculated structural modes.

Default = NONE N: Number of structural modes for which modal


participation factors will be computed based on
the largest magnitude of modal contribution.

NONE: Participation factors are not calculated for


structural modes.

setp <ALL, NONE> ALL: Output structural modal participation for each
panel specified in the PANEL data.
Default = NONE
NONE: Do not output panel modal participation.

setf <ALL, SID> ALL: Participation factors are processed for all
excitation frequencies.
Default = ALL
SID: Participation factors are only processed for a set
of excitation frequencies. SID refers to the ID of
a SET of type FREQ.

fratio <REAL> Specifies the value of a filter to be applied to the output.


Values of modal participation below fratio times the
Default = displacement or pressure are not output.
0.001

ipower <INTEGER> When the magnitude of a modal participation is below 10 to the


minus ipower, the modal participation will not be output. In
Default = 30
other words, if the modal participation is less than 10-ipower, the
result output for this mode will be skipped.

rval <REAL> The modal participation will be calculated at the excited


frequencies when the magnitude of the response is above rval.
Default = 0.0 The excitation frequency will be a subset of setf.

148 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

rpdba <Non-Negative RPDBACUT is the decibel pressure cutoff value for fluid
REAL> responses, and is similar to RPCUTOFF. It will take precedence
over RPCUTOFF for fluid responses. A weighting is applied to
Default = 0.0 RPDBACUT values at the excitation frequency. The modal
participation will be calculated when the magnitude of the
response is about the cutoff value. See comment 9 for decibel
calculations and reference pressure settings.

otype <ALL, SYSTEM, For SYSTEM, the output related to PFMODE will correspond to
CMS> the whole model. Component modal participation will not be
output by default. However, when using ALL or CMS, the
Default = component modal participation will be output. For the CMS
SYSTEM
option, there will not be system modal participation. Component
modal participation can also be calculated for internal grids in
the superelement.

seset <ALL, SID> Component modal participation of all the H3D superelements will
be output by default. However, you can specify a specific set
Default = ALL of superelement names for output.

rtype <DISP, VELO, The Structural modal participation will be output for
ACCE> Displacement, Velocity or Acceleration respectively based on
Default = DISP the specified option (DISP, VELO, ACCE).

outfile <PUNCH, H3D> Modal participation can be exported either into the H3D file or
PUNCH file. Because of the large volume of data, it is
Default = H3D
recommended to export the modal participation data into a H3D
file.

PEAKOUT If PEAKOUT is present inside the bracket of the PFMODE option, the filtered
frequencies from the PEAKOUT card will be considered for the output of modal
participation.

Altair Engineering OptiStruct 13.0 Reference Guide 149

Proprietary Information of Altair Engineering


Argument Options Description

setdof/ <SID/ Degrees-of-freedom for which the participation factors are to be


PEAKOUT PEAKOUT> processed. SID refers to the ID of a SET of type GRIDC for
structure participation and GRID for fluid participation. If
“PEAKOUT” is specified instead of SID, the output will be
considered at the filtered frequencies corresponding to the
degree of freedom on the PEAKOUT card in the bulk section.

Comments

1. The output of both the PFMODE and PFPANEL must be either to an H3D file or to a PUNCH
file. Both PFPANEL and PFMODE must have the same output option.

2. The modal participation output is sorted in descending order by magnitude of the modal
participation in the PUNCH file output.

3. PFMODE(FLUID,..) and PFMODE(STRUCTURE,…) can coexist in the input data, but only
one PFMODE(FLUID) and one PFMODE(STRUCTURE) are allowed in a single SUBCASE.

4. Keywords FLUIDMP and PANELMP are only valid if FLUID is specified.

5. If STRUCTURE is specified, setdof must reference a set of structural degrees-of-freedom.


If FLUID is specified, setdof must reference a set of acoustic degrees-of-freedom.

6. The FREQUENCY keyword can be used to select a subset of excitation frequencies


available.

7. The filter is applied to the magnitude of the modal participation factors. Only modal
participation factors that pass the filter are output.

8. If the magnitude of the total response at a selected response degree-of-freedom is less


than 10-ipower, then no modal participation factors are processed. If ipower is not in the
range of 1 to 31, the default of 30 is used.

9. The dB value is calculated using 20 * log10 (P/P0), where P0 is the reference pressure.
The reference pressure is dependent on the units specified on the UNITS input data. If
the units are SI, the value is set as 2.0E-5 Pa. If they are CGS, it is set as 2.0E-4 barye.
If they are MPa, it is set as 2.0E-11 MPa. If they are BG or EE, then it is set as 4.17E-7
lbf/ft 2. If no UNITS data is present, the default value is 2.0E-11 MPa.

10. Legacy format for the export of modal participation to H3D or PUNCH files: PFMODE (type,
OUTPUT=outfile)=setdof/PEAKOUT is also supported.

11. If you wish to output modal participation factors for interior points of a superelement (in a
CMS model), the SEINTPNT entry can be used in the subcase information section to
convert the interior points of interest to exterior points. After conversion, these points
can now be referenced by the <SID/PEAKOUT> option for the sedof/PEAKOUT argument.

150 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PFPANEL

I/O Options Entry

PFPANEL – Output Request for Acoustic Panel Participation

Description

The PFPANEL command can be used in the I/O Options section to request output of acoustic
panel participation factors for all frequency response subcases.

Format

PFPANEL (PANEL=setp, FREQUENCY=setf, outfile,peakout) = setdof/PEAKOUT

Examples
PFPANEL(PANEL=ALL,FREQUENCY=45)=12

PFPANEL(H3D, PEAKOUT)=56

PFPANEL(H3D, PEAKOUT)=PEAKOUT

PFPANEL(PUNCH)=32

Argumen Options Description


t

setp <ALL, NONE> ALL: Output acoustic panel participation for all panels.

Default = NONE
NONE: Do not output acoustic panel participation.

setf <ALL, SID> ALL: Participation factors are processed for all excitation
frequencies.
Default = ALL
SID: Participation factors are only processed for a set of
excitation frequencies. SID refers to the ID of a SET
of type FREQ.

outfile <PUNCH, H3D> Panel participation can be exported either into a H3D file or a
PUNCH file. Because of the large volume of data, it is
Default = H3D recommended to export the panel participation data into a H3D
file.

Altair Engineering OptiStruct 13.0 Reference Guide 151

Proprietary Information of Altair Engineering


Argumen Options Description
t

PEAKOUT If PEAKOUT is present as an option inside the parentheses of the PFPANEL data,
then the filtered frequencies from the PEAKOUT data will be considered for output
of panel participation.

setdof/ <SID/ Degrees-of-freedom for which the panel participation factors


PEAKOUT PEAKOUT> are to be processed. SID refers to the ID of a SET of type
GRID. If “PEAKOUT” is specified instead of SID, the output will
be considered at the filtered frequencies corresponding to the
degree-of-freedom in the PEAKOUT card in the bulk section.

Comments

1. Output is to the H3D or PUNCH files only. The output of both PFMODE and PFPANEL must
be either to an H3D file or to a PUNCH file. Both PFPANEL and PFMODE must have the same
output option.

2. Acoustic panel participation factors are available in a coupled frequency response analysis
(both in direct and modal frequency response).

3. The FREQUENCY keyword can be used to select a subset of excitation frequencies


available. The closest loading frequency will be chosen in this case.

4. Legacy format for the export of acoustic panel participation to H3D or PUNCH files:
PFPANEL (OUTPUT=outfile)=setdof/PEAKOUT is also supported.

152 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PFPATH

I/O Options Entry

PFPATH – Output Request

Description

The PFPATH command can be used in the I/O Options section for transfer path analysis for a
response at the connection points.

Format
PFPATH = SID

Comments

SID references a PFPATH card in the Bulk Data section.

Altair Engineering OptiStruct 13.0 Reference Guide 153

Proprietary Information of Altair Engineering


POWERFLOW

I/O Options Entry

POWERFLOW – Output Request

Description

The POWERFLOW command can be used in the I/O Options section to request output of the
power flow field.

Format
POWERFLOW (format,peakoutput) = option

Argument Options Description

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

Default = H3D

peakoutpu <PEAKOUT> PEAKOUT: If PEAKOUT is present, only the filtered


t frequencies from the PEAKOUT card will be
Default = considered for this output.
blank

option <YES, ALL, NO, YES, ALL, Power flow field is output for all elements.
NONE, SID> blank:

Default = ALL
NO, NONE: Power flow field is not output.

SID: If a set ID is given, power flow field is output


only for the contents of that set.

Comments

1. Power flow field output is only available to the .h3d file.

2. The power flow field indicates the magnitude and direction of vibrational energy which
travels in dynamically loaded structures. It helps with identifying the energy transmission
paths as well as the vibration sources and energy sinks. Structural intensity, defined as
the power flow per unit area, is also available.

3. The references used in the calculation of the power flow field are listed in the References
section of the User’s Guide.

154 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PRESSURE

I/O Options and Subcase Information Entry

PRESSURE - Output Request

Description

The PRESSURE command is analogous to the DISPLACEMENT command. Refer to the


documentation for the DISPLACEMENT command.

Altair Engineering OptiStruct 13.0 Reference Guide 155

Proprietary Information of Altair Engineering


PRETBOLT

I/O Options and Subcase Information Entry

PRETBOLT - Output Request

Description

The PRETBOLT command can be used in the I/O Options or Subcase Information sections to
request output of pretension force/adjustment values in the pretension bolts for all
pretensioning and pretensioned subcases.

Format
PRETBOLT (format) = option

Argument Options Description

format <OPTI, blank> OPTI: Results are output in OptiStruct results


format (.pret file).
Default = blank
blank: Results are output in all active formats
for which the result is available.

option <YES, NO> YES: Pretension force/adjustment values are


output for all bolts.
Default = YES
NO: Pretension force/adjustment values are
not output.

Example

PRETBOLT (OPTI) = YES

PRETBOLT = NO

PRETBOLT (OPTI)

PRETBOLT

Comments

1. When a PRETBOLT command is not present, pretension force/adjustment values are not
output.

2. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

156 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PROPERTY

I/O Options Entry

PROPERTY - Output Control

Description

The PROPERTY command can be used in the I/O Options section to request the output of the
property definitions used in the final iteration of an optimization.

Format
PROPERTY = option

Argument Options Description

option <FILE, OUT, FILE or blank: Updated property definitions are output
BOTH, NONE> to the .prop file.

Default = FILE OUT: Updated property definitions are output


to the .out file.

BOTH: Updated property definitions are output


to both the .out file and the .prop file.

NONE: Updated property definitions are not


output.

Comments

1. When a PROPERTY command is not present the updated property definitions will not be
output.

Altair Engineering OptiStruct 13.0 Reference Guide 157

Proprietary Information of Altair Engineering


RADSND

I/O Options and Subcase Information Entry

RADSND - References RADSND Bulk Data to specify sound generation panels and microphone
field points

Description

The RADSND command can be used in the I/O Options or Subcase Information sections to
request radiated sound output for all subcases or individual subcases respectively.

Format
RADSND = option

Argument Options Description

option <SID> SID: ID of RADSND bulk data entry.

No default

Comments

1. Multiple instances of this card are allowed. If the instances are conflicting, the last
instance will be considered.

158 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


RCROSS

I/O Options Entry

RCROSS – Output Request

Description

The RCROSS command can be used in the I/O Options section to request computation and
output of cross-power spectral density functions for random response analysis.

Format
RCROSS(format_list,form,type, randid=RANDPS_ID) = option

Argume Options Description


nt

format <PUNCH, PUNCH: Results are output in Nastran punch results format
blank> (.pch file).

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

form <COMPLEX, COMPLEX: Provides a combined magnitude/phase form of


REAL, IMAG, complex output to the .res file if HM output format
PHASE, is chosen. The REAL form of complex output is used
BOTH> for other formats if they are not specifically defined.
(Phase output is in degrees).
Default =
COMPLEX
REAL or Provides rectangular format (real and imaginary) of
IMAG: complex output.

PHASE: Provides polar format (phase and magnitude) of


complex output.

BOTH: Provides both rectangular and polar formats of


complex output.

type <PSDF> PSDF: Requests the cross-power spectral density function


be calculated and output for random analysis post-
Default = processing.
PSDF

Altair Engineering OptiStruct 13.0 Reference Guide 159

Proprietary Information of Altair Engineering


Argume Options Description
nt

option <RCROSS_ID> RCROSS_ID: Set identification of an RCROSS bulk data entry.

randid <RANDPS_ID, RANDPS_ID: Set identification number of a RANDPS bulk data


blank> entry (see comments 3 and 4).

Comments

1. The RCROSS I/O option must be used in conjunction with the RANDOM subcase information
entry.

2. Response quantities, such as DISPLACEMENT, STRESS and STRAIN, must be requested by


corresponding I/O Options in order to compute cross-power spectral density between the
two response quantities specified by the RCROSS bulk data entry.

3. Multiple RCROSS bulk data entries must be defined when each RCROSS subcase
information entry references different randid.

For example:
rcross(PUNCH, PHASE, PSDF, randid=210020)=451
rcross(PUNCH, PHASE, PSDF, randid=210050)=452
rcross(PUNCH, PHASE, PSDF, randid=210070)=453
rcross(PUNCH, PHASE, PSDF, randid=210090)=454

4. randid=<RANDPS_ID> must be specified within the RCROSS I/O options entry when
multiple RANDOM subcase information entries are present.

160 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


REQUEST

I/O Options and Subcase Information Entry

REQUEST – Multi-Body Request Selection

Description

The REQUEST command can be used in the I/O Options or Subcase Information sections to
select a multi-body request definition to be used in a multi-body problem.

Format
REQUEST = option

Argument Option Description

option <SID> SID: Set identification of MBREQ, MBREQE, or MBREQM


bulk data entries.
No default

Comments

1. Only one REQUEST entry can be present for each subcase.

2. This subcase information entry is only valid when it appears in a multi-body subcase.

3. If the SID referenced by the REQUEST subcase information entry matches with the SID
defined for an MBREQ bulk data entry, the information on this entry alone is selected.
However, if no MBREQ bulk data entry has the referenced SID defined, any of the multi-
body motion entries: MBREQE or MBREQM which have this SID will be selected.

4. If present above the first subcase, it is applied to each multi-body dynamics subcase
without a REQUEST entry.

Altair Engineering OptiStruct 13.0 Reference Guide 161

Proprietary Information of Altair Engineering


RESPRINT

I/O Options Entry

RESPRINT - Output Control

Description

The RESPRINT command can be used in the I/O Options section to force all unretained
responses of a certain type to be printed to the output file, provided they are referenced
either as an objective or a constraint. This also applies to manufacturing constraints for
composites.

Format
RESPRINT = option

Argument Options Description

option <MASS, VOLUME, DISP, MASS: Mass and massfrac


BUCK, STRESS, FREQ, responses are output.
EQUA, EXTERNAL, WCOMP,
WFREQ, COMB, COMP, VOLUME: Volume and volfrac
STRAIN, FORCE, COG, responses are output.
INERTIA, MANUF, ALL>
DISP: Acceleration, Displacement
No default and Velocity responses are
output.

BUCK: Buckling responses are


output.

STRESS: Stress responses, including


CSTRESS and CFAILURE
responses, are output.

FREQ: Frequency responses are


output.

EQUA, WCOMP, All equation and combination


WFREQ, or COMB: responses are output.

EXTERNAL: External responses (defined


by DRESP3) are output.

COMP: Compliance responses are


output.

162 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

STRAIN: Strain responses, including


CSTRAIN responses, are
output.

FORCE: Force responses are output.

COG: Center of gravity responses


are output.

INERTIA: Inertia responses are output.

MANUF: Manufacturing constraints for


composites are output.

ALL: All design responses are


output. However,
manufacturing constraints for
composites are not listed.

Comments

1. When a RESPRINT command is not present, only retained responses will be output.

2. The arguments may be placed on a single card in a comma-separated list.

For example:
RESPRINT = STRESS, DISP

will force all stress and displacement responses referenced as either an objective or
constraint to be output.

Altair Engineering OptiStruct 13.0 Reference Guide 163

Proprietary Information of Altair Engineering


RESTART

I/O Options Entry

RESTART - Run Control Command

Description

The RESTART command can be used in the I/O Options section to indicate that the current
optimization is to be restarted from the final iteration of a previous optimization.

Format
RESTART = option

Argument Options Description

option <File prefix> File prefix: The prefix of the .sh file to be
used as the starting iteration
Default = prefix of .fem for the restart.
file

Comments

1. To restart an optimization, you will need information about the final iteration of a previous
optimization run. This information is contained in the .sh file.

2. The purpose of the restart functionality is for restarting with unconverged optimization
runs or optimization runs that were terminated before completion (due to a power outage,
and so on). Only limited changes are allowed to be made to the model data. Refer to
the User's Guide section Restarting OptiStruct.

3. This I/O Option is not valid for analysis mode.

4. Output files from a restart run are appended with the extension _rst#, where # is a 3
digit number indicating the starting iteration for the restart run. For example,
filename_rst030.out is the .out file created when restarting filename.fem from
iteration 30.

5. The total length of information on this card is limited to 200 characters (including the card
name and spaces between arguments). This data can be on a single line or span multiple
continuation lines. See Guidelines for I/O Options and Subcase Information Entries for an
example showing how to enter long file names on multiple lines.

164 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


RESULTS

I/O Options Entry

RESULTS - Output Control

Description

The RESULTS command can be used in the I/O Options or Subcase Information sections to
determine the frequency of output of analysis results for all subcases or for individual
subcases respectively.

Format
RESULTS = frequency

Argument Options Description

frequency <FIRST, LAST, FL, FIRST: Output analysis results for the first
ALL, NONE, N> iteration only.

Default = FL LAST: Output analysis results for the final


iteration only.

FL, blank: Output analysis results for both the first


and last iterations.

ALL: Output analysis results for all iterations.

NONE: Do not output analysis results.

N: Output analysis results for the first and


last iterations and for every Nth
iteration. If N = 5, output occurs for
iterations 0, 5, 10, 15, 20, and so on,
and the final iteration. All equation and
combination responses are output.

Comments

1. When a RESULTS command is not present, analysis results are output for formats that are
activated by the FORMAT command for both the first and last iterations.

2. The information on this card pertains to all analysis output formats that are not
specifically described by an OUTPUT command.

Altair Engineering OptiStruct 13.0 Reference Guide 165

Proprietary Information of Altair Engineering


3. It is recommended to use the OUTPUT command as it allows different frequencies of
output to be defined for different formats.

166 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SACCELERATION

I/O Options and Subcase Information Entry

SACCELERATION - Output Request

Description

The SACCELERATION command can be used in the I/O Options or Subcase Information sections
to request the form and type of modal participation accelerations output for all subcases or
individual subcases respectively.

Format
SACCELERATION (sorting,format_list,form,peakoutput) = option

Argument Options Description

sorting <SORT1, SORT2> This argument only applies to the PUNCH format
(.pch file) or the OUTPUT2 format (.op2 file) output
Default = blank for normal modes, frequency response, and
transient subcases. It will be ignored without
warning if used elsewhere.

SORT1: Results for each frequency/


timestep are grouped together.

SORT2: Results for each grid/element are


grouped together (See comment
7).

blank: SORT1 is used for all results


except for transient analysis,
where SORT2 is used.

format <H3D, PUNCH, OP2, H3D: Results are output in Hyper3D


PLOT, blank> format (.h3d file).

Default = blank PUNCH: Results are output in Nastran


punch results format (.pch file).

OP2: Results are output in Nastran


output2 format (.op2 file) (see
comment 9).

Altair Engineering OptiStruct 13.0 Reference Guide 167

Proprietary Information of Altair Engineering


Argument Options Description

PLOT: Results are output in Nastran


output2 format (.op2 file) when
PARAM, POST is defined in the
bulk data section.

blank: Results are output in all active


formats for which the result is
available.

form <REAL, IMAG, REAL or IMAG: Provides rectangular format (real


PHASE> and imaginary) of complex
output.
Default = REAL
PHASE: Provides polar format (magnitude
and phase) of complex output.
Phase output is in degrees.

peakoutput <PEAKOUT> PEAKOUT: If PEAKOUT is present, only the


filtered frequencies from the
Default = blank PEAKOUT card will be considered
for this output.

option <YES, ALL, NO, YES, ALL, blank: Results are output.
NONE>

Default = ALL NO, NONE: Results are not output.

Comments

1. When the SACCELERATION command is not present, modal participation accelerations are
not output.

2. The SACCELERATION command is only valid for modal frequency response and modal
transient solution sequences.

3. The OFREQUENCY and OTIME I/O Options may be used to control the amount of output.

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

168 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


5. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

6. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.

7. In general, HyperView does not recognize the SORT2 format for results from the .op2 file.
When results are output only in SORT2 format (<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.

8. The abbreviations SACCE and SACCEL are interchangeable with SACCELERATION.

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

Altair Engineering OptiStruct 13.0 Reference Guide 169

Proprietary Information of Altair Engineering


SCREEN

I/O Options Entry

SCREEN - Output Control

Description

The SCREEN command can be used in the I/O Options section to control the output of model,
analysis, and optimization information to the UNIX or DOS shell.

Format
SCREEN = option

Argument Options Description

option <OUT, LOG, OUT, blank: The .out file is echoed to the screen.
NONE>
LOG: A log of the optimization process is echoed
Default = NONE
to the screen.

NONE: No information is echoed to the screen.

Comments

1. When a SCREEN command is not present, no information is echoed to the screen.

2. If the option LOG is chosen, the value of the objective function and the maximum
constraint violation at every iteration, as well as indication of satisfied convergence
ratios, are echoed to the screen.

170 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SDISPLACEMENT

I/O Options and Subcase Information Entry

SDISPLACEMENT - Output Request

Description

The SDISPLACEMENT command can be used in the I/O Options or Subcase Information sections
to request the form and type of modal participation displacements output for all subcases or
individual subcases respectively.

Format
SDISPLACEMENT (sorting,format_list,form,peakoutput) = option

Argument Options Description

sorting <SORT1, SORT2> This argument only applies to the PUNCH format (.pch
file) or the OUTPUT2 format (.op2 file) output for normal
Default = blank modes, frequency response, and transient subcases. It
will be ignored without warning if used elsewhere.

SORT1: Results for each frequency/timestep are


grouped together.

SORT2: Results for each grid/element are


grouped together (See comment 7).

blank: SORT1 is used for all results except for


transient analysis, where SORT2 is used.

format <H3D, PUNCH, H3D: Results are output in Hyper3D format


OP2, PLOT, blank> (.h3d file).

Default = blank PUNCH: Results are output in Nastran punch


results format (.pch file).

OP2: Results are output in Nastran output2


format (.op2 file) (see comment 9).

PLOT: Results are output in Nastran output2


format (.op2 file) when PARAM, POST is
defined in the bulk data section.

Altair Engineering OptiStruct 13.0 Reference Guide 171

Proprietary Information of Altair Engineering


Argument Options Description

blank: Results are output in all active formats


for which the result is available.

form <REAL, IMAG, REAL, IMAG: Provides rectangular format (real and
PHASE> imaginary) of complex output.

Default = REAL
PHASE: Provides polar format (magnitude and
phase) of complex output. Phase
output is in degrees.

peakoutput <PEAKOUT> PEAKOUT: If PEAKOUT is present, only the filtered


frequencies from the PEAKOUT card will
Default = blank be considered for this output.

option <YES, ALL, YES, ALL, blank: Results are output.


NO, NONE>

Default = ALL NO, NONE: Results are not output.

Comments

1. When the SDISPLACEMENT command is not present, modal participation displacements are
not output.

2. The SDISPLACEMENT command is only valid for modal frequency response and modal
transient solution sequences.

3. The OFREQUENCY and OTIME I/O options may be used to control the amount of output.

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

5. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

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

172 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


7. In general, HyperView does not recognize the SORT2 format for results from the .op2 file.
When results are output only in SORT2 format (<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.

8. The abbreviation SDISP is interchangeable with SDISPLACEMENT.

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

Altair Engineering OptiStruct 13.0 Reference Guide 173

Proprietary Information of Altair Engineering


SENSITIVITY

I/O Options Entry

SENSITIVITY - Output Request

Description

The SENSITIVITY command can be used in the I/O Options section to request the output of
the responses and sensitivities for size and shape design variables to a Microsoft Excel
spreadsheet.

Format
SENSITIVITY = option

Argument Options Description

option <YES, NO, ALL, NONE, NO, NONE: The results and sensitivities are not
STRESS, NOSTRESS> output.

Default = NONE YES, The results and sensitivities are


NOSTRESS, output excepting stress, strain, and
blank: force responses.

ALL or The results and sensitivities are


STRESS: output including stress, strain, and
force responses.

Comments

1. This command is ignored when OUTPUT, MSSENS command is present.

2. When SENSITIVITY is not present, sensitivity information is not output.

3. The frequency of this output is controlled by the SENSOUT option.

4. For more details on the output format, go to the #.slk file page in the output section of
the Reference Guide.

5. Additional sensitivity output requests for topology, free-sizing and gauge design variables
can be made through OUTPUT,H3DTOPOL and OUTPUT,H3DGAUGE (in H3D format), and
OUTPUT,ASCSENS (ASCII format).

174 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SENSOUT

I/O Options Entry

SENSOUT - Output Control

Description

The SENSOUT command can be used in the I/O Options section to control the frequency of
output of responses and sensitivities for size and shape design variables to a Microsoft Excel
spreadsheet.

Format
SENSOUT = frequency

Argument Options Description

frequency <FIRST, LAST, FIRST: The results and sensitivities are output for the
FL, ALL, N> first iteration only.

Default = FL LAST: The results and sensitivities are output for the
final iteration only.

FL, The results and sensitivities are output for


blank: both the first and last iterations.

ALL: The results and sensitivities are output for all


iterations.

N: The results and sensitivities are output for the


first and last iterations and for every Nth
iteration. If N = 5, output occurs for iterations
0, 5, 10, 15, 20, and so on, and the final
iteration. All equation and combination
responses are output.

Comments

1. This command is ignored when OUTPUT, MSSENS command is present.

Altair Engineering OptiStruct 13.0 Reference Guide 175

Proprietary Information of Altair Engineering


SHAPE

I/O Options and Subcase Information Entry

SHAPE - Output Request

Description

The SHAPE command can be used in the I/O Options section to request altered shape output
for a shape optimization.

Format
SHAPE (format_list,type) = option

Argument Options Description

format <HM, H3D, blank> HM: Results are output in HyperMesh results
format (.res file).
Default = blank
H3D: Results are output in Hyper3D format
(.h3d file).

blank: Results are output in all active formats


for which the result is available.

type <ALL, DES> ALL: Results are output in all simulations.

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

option <YES, ALL, NO, YES, ALL, Results are output.


NONE> blank:

Default = YES
NO, NONE: Results are not output.

Comments

1. When the SHAPE command is not present, shape results are output.

2. Shape results are only available for shape, topography, and free-shape optimizations.

176 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. Outputting the shape results in all simulations allows analysis results to be plotted on the
altered shape.

4. The frequency of this output is controlled by the DESIGN keyword on an OUTPUT definition
or, if no OUTPUT definition exists with the DESIGN keyword, by the DENSRES I/O option.

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

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

Altair Engineering OptiStruct 13.0 Reference Guide 177

Proprietary Information of Altair Engineering


SINTENS

I/O Options and Subcase Information Entry

SINTENS - Output Request

Description

The SINTENS command can be used in the I/O Options section to request Sound Intensity
output for all frequency response subcases. The SINTENS command can be used in the I/O
Options or Subcase Information sections to request Sound Intensity output for all subcases or
individual subcases respectively.

Format
SINTENS(type) = option

Argument Options Description

type <PANEL, NOPANEL> PANEL, Sound Intensity is output for both panels
blank: and microphone locations.
Default = PANEL

NOPANEL: Sound Intensity is output only for


microphone locations.

option <ALL> ALL, Sound Intensity is output for all panel


blank: grids and all grids defined as microphone
Default = ALL locations on the RADSND bulk data. In
addition, the total Sound Intensity for
each Panel and all the microphone
locations is output.

Note: Sound Intensity is output only for


microphone locations if
type=NOPANEL is specified.

Comments

1. When the SINTENS command is present, Sound Intensity is output for all RADSND panel
grids and all microphone grids for all frequency response subcases. (If type=NOPANEL is
specified, sound intensity results are output only for microphone locations).

2. Sound Intensity results (via SINTENS) are output to the .h3d file.

3. SINTENS can only be requested for frequency response subcases.


4. Sound intensity is always output for microphone locations regardless of the specified type
(PANEL/NOPANEL).

178 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SPCFORCE

I/O Options and Subcase Information Entry

SPCFORCE - Output Request

Description

The SPCFORCE command can be used in the I/O Options or Subcase Information sections to
request single-point force of constraint vector output for all subcases or individual subcases
respectively.

Format
SPCFORCE (sorting,format_list,form,type,peakoutput) = option

Argument Options Description

sorting <SORT1, SORT2> This argument only applies to the PUNCH format (.pch
file) or the OUTPUT2 format (.op2 file) output for
Default = blank normal modes, frequency response, and transient
subcases. It will be ignored without warning if used
elsewhere.

SORT1: Results for each frequency/timestep are


grouped together.

SORT2: Results for each grid/element are grouped


together (See comment 10).

blank: For frequency response analysis, if no grid


SET is specified, SORT1 is used, otherwise,
SORT2 is used.

format <HM, H3D, OPTI, HM: Results are output in HyperMesh results
PUNCH, OP2, format (.res file).
PLOT, blank>
H3D: Results are output in Hyper3D format (.h3d
Default = blank file).

OPTI: Results are output in OptiStruct results


format (.spcf file).

PUNCH: Results are output in Nastran punch results

Altair Engineering OptiStruct 13.0 Reference Guide 179

Proprietary Information of Altair Engineering


Argument Options Description

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.

blank: Results are output in all active formats for


which the result is available.

form <COMPLEX, REAL, COMPLEX Provides a combined magnitude/phase form


IMAG, PHASE, (HM only), of complex output to the .res file for the
BOTH> blank: HM output format.

Default (HM only)


= COMPLEX REAL, Provides rectangular format (real and
IMAG: imaginary) of complex output.
Default (all other
formats) = REAL
PHASE: Provides polar format (magnitude and
phase) of complex output. Phase output is
in degrees.

BOTH (HM Provides both polar and rectangular formats


only): of complex output.

type <SPARSE, ALL> ALL: Single-point force of constraint is output


for all selected nodes.
Default = SPARSE

SPARSE: Single-point force of constraint is output


only for selected nodes with a component
with a magnitude of 1.0E-10 or greater.

peakoutput <PEAKOUT> PEAKOUT: If PEAKOUT is present, only the filtered


frequencies from the PEAKOUT card will be
Default = blank considered for this output.

180 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

option <YES, ALL, NO, YES, ALL, Single-point force of constraint is output
NONE, SID> blank: for all nodes.

Default = ALL
NO, NONE: Single-point force of constraint is not
output.

SID: If a set ID is given, single-point force of


constraint is output only for nodes listed in
that set.

Comments

1. When an SPCFORCE command is not present, single-point force of constraint vector is not
output.

2. Single-point force of constraint values are highly dependent on mesh density and type of
elements used.

3. For modal frequency analysis, residual forces are zero only in modal space. Therefore,
the single-point force of constraint vector may not be accurate unless all modes are used
in the modal solution. When all possible modes in the model space are used, the modal
frequency analysis solution should match the direct frequency analysis solution.

4. When single-point force of constraint is calculated, the reaction force summary, the load
summary, and the strain energy residuals for the affected subcases are written to the
.out file.

5. The form argument is only applicable for frequency response analysis. It is ignored in
other instances.

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

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

8. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

9. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.

Altair Engineering OptiStruct 13.0 Reference Guide 181

Proprietary Information of Altair Engineering


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

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

182 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SPL

I/O Options and Subcase Information Entry

SPL - Output Request

Description

The SPL command can be used in the I/O Options or Subcase Information sections to request
Sound Pressure output for all subcases or individual subcases respectively. SPL can only be
requested for frequency response subcases.

Format
SPL = option

Argument Options Description

option <ALL> ALL, Sound Pressure is output for all grids


blank: defined as microphone locations on the
Default = ALL RADSND bulk data.

Comments

1. When the SPL command is present, Sound Pressure is output for all microphone grids for
all frequency response subcases.

2. Sound Pressure results (via SPL) are output to the .h3d file.

Altair Engineering OptiStruct 13.0 Reference Guide 183

Proprietary Information of Altair Engineering


SPOWER

I/O Options and Subcase Information Entry

SPOWER - Output Request

Description

The SPOWER command can be used in the I/O Options or Subcase Information sections to
request Sound Power output for all subcases or individual subcases respectively. SPOWER can
only be requested for frequency response subcases.

Format
SPOWER(type) = option

Argument Options Description

type <PANEL, NOPANEL> PANEL, Sound Power is output for both panels
blank: and microphone locations.
Default = PANEL

NOPANEL: Sound Power is output only for


microphone locations.

option <ALL> ALL, Sound Power is output for all panel grids
blank: and all grids defined as microphone
Default = ALL locations on the RADSND bulk data. In
addition, the total Sound Power for each
Panel and all the microphone locations is
output.

Note:

Sound Power is output only for


microphone locations if type=NOPANEL is
specified.

Comments

1. When the SPOWER command is present, Sound Power is output for all RADSND panel grids
and all microphone grids for all frequency response subcases. (If type=NOPANEL is
specified, sound power results are output only for microphone locations).

2. Sound power is always output for microphone locations regardless of the specified type
(PANEL/NOPANEL).

3. Sound Power results (via SPOWER) are output to the .h3d file.

184 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


STRAIN

I/O Options and Subcase Information Entry

STRAIN - Output Request

Description

The STRAIN command can be used in the I/O Options or Subcase Information sections to
request strain output for all subcases or individual subcases respectively.

Format
STRAIN
(sorting,format_list,form,type,location,extras_list,random,peakoutput,modal) =
option

Argument Options Descriptions

sorting <SORT1, SORT2> This argument only applies to the PUNCH format (.pch
file) or the OUTPUT2 format (.op2 file) output for
Default = blank normal modes, frequency response, and transient
subcases. It will be ignored without warning if used
elsewhere.

SORT1: Results for each frequency/timestep


are grouped together.

SORT2: Results for each grid/element are


grouped together (See comment 12).

blank: For frequency response analysis, if no


element SET is specified, SORT1 is
used, otherwise, SORT2 is used; for
transient analysis, SORT2 is used.

format <HM, H3D, OPTI, HM: Results are output in HyperMesh


PUNCH, OP2, results format (.res file). Refer to
PLOT, blank> Strain Results Written in HyperMesh
.res Format.
Default = blank
H3D: Results are output in Hyper3D format
(.h3d file). Refer to Strain Results
Written in HyperView .h3d Format.

Altair Engineering OptiStruct 13.0 Reference Guide 185

Proprietary Information of Altair Engineering


Argument Options Descriptions

OPTI: Results are output in OptiStruct


results format (.strn file).

PUNCH: Results are output in Nastran punch


results format (.pch file). Refer to
Strain Results Written in Nastran .op2
and .pch Formats.

OP2: Results are output in Nastran output2


format (.op2 file) (see comment 15,
and also refer to Strain Results
Written in Nastran .op2 and .pch
Formats).

PLOT: Results are output in Nastran output2


format (.op2 file) when PARAM, POST
is defined in the bulk data section.
Refer to Strain Results Written in
Nastran .op2 and .pch Formats.

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, COMPLEX (HM Provides a combined magnitude/phase


IMAG, PHASE, only), blank: form of complex output to the .res
BOTH> file for the HM output format.

Default (HM REAL or IMAG: Provides rectangular format (real and


only) = COMPLEX imaginary) of complex output.

Default (all other PHASE: Provides polar format (phase and


formats) = REAL magnitude) of complex output.

BOTH (HM only): Provides both rectangular and polar


formats of complex output.

186 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Descriptions

type <VON, PRINC, VON: Only von Mises strain results are
MAXS, SHEAR, output.
ALL, TENSOR,
DIRECT> PRINC, MAXS, von Mises and maximum principal
SHEAR: strain results are output.
Default = ALL

ALL: All strain results are output.

TENSOR: All strain results are output. Tensor


format is used for H3D output.

DIRECT: All strain results are output. Direct


format is used for H3D output.

location <CENTER, CENTER: Element strains for shell and solid


CUBIC, SGAGE, elements are output at the element
CORNER, BILIN> center only.
Default = CENTER
CUBIC: Element strains for shell and solid
elements are output at the element
center and grid points using the
strain gage approach with cubic
bending correction.

SGAGE: Element strains for shell and solid


elements are output at the element
center and grid points using the
strain gage approach.

CORNER or Element strains for shell elements are


BILIN: output at the element center and at
the grid points using bilinear
extrapolation. (see comment 11)

extras <MECH, THER, MECH: Output Mechanical strain (in addition


PLASTIC> to total strain). This output is only
available for H3D format.
No default

Altair Engineering OptiStruct 13.0 Reference Guide 187

Proprietary Information of Altair Engineering


Argument Options Descriptions

THER: Output Thermal strain (in addition to


total strain). This output is only
available for H3D format.

PLASTIC: Output Plastic strain (in addition to


total strain). This output is only
available for H3D format.

random <PSDF, RMS> PSDF: Requests PSD and RMS results from
random response analysis to be
No default output for solid and shell elements
only (See comment 13).

Only valid for the H3D format. The


"RMS over Frequencies" output is at
the end of the Random results in the
.h3d file.

RMS: Requests only the “RMS over


Frequencies” result from random
response analysis to be output for
solid and shell elements only (see
comment 13).

Valid only for the H3D format.

peakoutput <PEAKOUT> PEAKOUT: If PEAKOUT is present, only the


filtered frequencies from the PEAKOUT
Default = blank card will be considered for this
output.

modal <MODAL> MODAL: If MODAL is present, strain results of


the structural modes and residual
Default = blank vectors are output to the PUNCH,
OUTPUT2 and H3D files for modal
frequency response and transient
analyses.

188 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Descriptions

option <YES, ALL, NO, YES, ALL, blank: Results are output for all elements.
NONE, SID,
PSID>
NO, NONE: Results are not output.
Default = ALL

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 STRAIN command is not present, no strain data is output.

2. HyperView can internally derive strain results from the strain tensor when the options
TENSOR or ALL are used. If the option DIRECT is used, it will display the strain results
that were directly computed.

3. The von Mises and Principal stresses are not available for frequency response analysis.

4. For elements that reference PCOMP and PCOMPG properties, the STRAIN I/O option controls
only strain results for the homogenized composite. The CSTRAIN I/O option must be used
to obtain ply strain results.

5. The form argument is only applicable for frequency response analysis. It is ignored in
other instances.

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

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

8. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

9. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.

10. The mechanical and thermal contributions to strain may be requested in addition to the
total strain.

11. Corner strain of solid element is not available.

Altair Engineering OptiStruct 13.0 Reference Guide 189

Proprietary Information of Altair Engineering


12. In general, HyperView does not recognize the SORT2 format for results from the .op2 file.
When results are output only in SORT2 format (<Result Keyword> (SORT2, OUTPUT2, …
.)), the results are written by OptiStruct into the .op2 file in SORT2 format, but when
the .op2 file is imported into HyperView, the results in SORT2 format are not recognized.
Therefore, the SORT1 option is recommended for results output in OUTPUT2 format and
SORT2 option is recommended for results output in PUNCH format.

13. PSDF and RMS von Mises strain results based on the Segalman Method are also written to
the .h3d file for Random Response Analysis (only available in the H3D format).

14. The four-letter abbreviation STRA is interchangeable with STRAIN.

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

190 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


STRESS/ELSTRESS

I/O Options and Subcase Information Entry

STRESS - Output Request

Description

The STRESS command can be used in the I/O Options or Subcase Information sections to
request stress output for all subcases or individual subcases respectively.

Format
STRESS (sorting,format_list,form,type,location,random,peakoutput,modal) =
option

Argument Options Description

sorting <SORT1, SORT2> This argument only applies to the PUNCH


format (.pch file) or the OUTPUT2 format
Default = blank (.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
12).

blank: For normal modes analysis,


SORT1 is used; for
frequency response
analysis, if no element SET
is specified, SORT1 is used,
otherwise, SORT2 is used;
for transient analysis,
SORT2 is used.

format <HM, H3D, OPTI, PUNCH, HM: Results are output in


OP2, PATRAN, APATRAN, HyperMesh results format
(.res file). Refer to Stress

Altair Engineering OptiStruct 13.0 Reference Guide 191

Proprietary Information of Altair Engineering


Argument Options Description

PLOT, blank> Results Written in


HyperMesh .res Format.
Default = blank
H3D: Results are output in
Hyper3D format (.h3d file).
Refer to Stress Results
Written in HyperView .h3d
Format.

OPTI: Results are output in


OptiStruct results format
(multiple files).

PUNCH: Results are output in


Nastran punch results
format (.pch file). Refer
to Stress Results Written in
Nastran .op2 and .pch
formats.

OP2: Results are output in


Nastran output2 format
(.op2 file) (see comment
15, and also refer to Stress
Results Written in Nastran
.op2 and .pch Formats).

PATRAN: Results are output in


Patran format (multiple
files).

APATRAN: Results are output in


Patran format (multiple
files).

PLOT: Results are output in


Nastran output2 format
(.op2 file) when PARAM,
POST is defined in the bulk
data section. Refer to
Stress Results Written in
Nastran .op2 and .pch
Formats.

If PARAM, POST is not


defined in the bulk data
section, this format allows

192 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

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, COMPLEX (HM Provides a combined


PHASE, BOTH> only), blank: magnitude/phase form of
complex output to the .res
Default (HM only) = file for the HM output
COMPLEX format.
Default (all other formats)
= REAL REAL or IMAG: Provides rectangular format
(real and imaginary) of
complex output.

PHASE: Provides polar format


(phase and magnitude) of
complex output.

BOTH (HM Provides both rectangular


only): and polar formats of
complex output.

type <VON, PRINC, MAXS, SHEAR, VON: Only von Mises stress
ALL, TENSOR, DIRECT> results are output (HM,
OPTI, and H3D only).
Default = ALL, TENSOR
PRINC, MAXS, von Mises and maximum
SHEAR: principal stress results are
output (HM and H3D only).

ALL: All stress results are


output.

TENSOR: All stress results are


output. Tensor format is
used for H3D output.

Altair Engineering OptiStruct 13.0 Reference Guide 193

Proprietary Information of Altair Engineering


Argument Options Description

DIRECT: All stress results are


output. Direct format is
used for H3D output.

location <CENTER, CUBIC, SGAGE, CENTER: Element stresses for shell


CORNER, BILIN> and solid elements are
output at the element
Default = CENTER center only.

CUBIC: Element stresses for shell


elements are output at the
element center and grid
points using the strain
gage approach with cubic
bending correction.

SGAGE: Element stresses for shell


elements are output at the
element center and grid
points using the strain
gage approach.

CORNER or Element stresses for shell


BILIN: and solid elements are
output at the element
center and grid points
using bilinear extrapolation.

random <PSDF, RMS> PSDF: Requests PSD and RMS


results from random
No default response analysis to be
output for solid and shell
elements only (See
comment 13).

Only valid for OUTPUT2 and


H3D formats. The "RMS
over Frequencies" output is
at the end of the Random
results in the .h3d file and
labeled "Simulation 1" in
the .op2 file.

194 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

RMS: Requests only the “RMS


over Frequencies” result
from random response
analysis to be output for
solid and shell elements
only (See comment 13).

Valid only for OUTPUT2 and


H3D formats. It is labeled
“Simulation 1” in the .op2
file.

peakoutput <PEAKOUT> PEAKOUT: If PEAKOUT is present, only


the filtered frequencies
Default = blank from the PEAKOUT card will
be considered for this
output.

modal <MODAL> MODAL: If MODAL is present,


stresses of the structural
Default = blank modes and residual vectors
are output to the PUNCH
and OUTPUT2 files for modal
frequency response and
transient analysis.

option <YES, ALL, NO, NONE, SID, YES, ALL, blank: Stress results are output
PSID> for all elements.

Default = ALL NO, NONE: Stress results are not


output.

SID: If a set ID is given, stress


results are output only for
elements listed in that set.

PSID: If a property set ID is


given, stress results for the
elements referencing
properties listed in the

Altair Engineering OptiStruct 13.0 Reference Guide 195

Proprietary Information of Altair Engineering


Argument Options Description

property set are output.

Comments

1. When a STRESS command is not present, stress results are output for all elements for all
linear static analysis, nonlinear quasi-static gap analysis, and inertia relief analysis
subcases.

2. HyperView can internally derive STRESS results from the stress tensor when the options
TENSOR or ALL are used. If the option DIRECT is used, it will display the stress result that
were directly computed.

3. For elements that reference PCOMP or PCOMPG properties, the STRESS I/O option controls
only stress results for the homogenized composite. The CSTRESS I/O option must be used
to obtain ply stress and failure index results.

4. The Von Mises and Principal stresses are not available for frequency response analyses.

5. The form argument is only applicable for frequency response analysis. It is ignored in
other instances.

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

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

8. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

9. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.

10. For normal modes analysis output, if there is USET U6 data, the stresses for each residual
displacement vector associated with the USET U6 DOF are also output to the H3D, PUNCH,
and OUTPUT2 files.

11. For modal frequency response and transient analysis, the stress vectors associated with
the residual vectors are written to the .op2 and .pch files after the modal stress vectors
if the keyword MODAL is used.

12. In general, HyperView does not recognize the SORT2 format for results from the .op2 file.
When results are output only in SORT2 format (<Result Keyword> (SORT2, OUTPUT2, …
.)), the results are written by OptiStruct into the .op2 file in SORT2 format, but when
the .op2 file is imported into HyperView, the results in SORT2 format are not recognized.
Therefore, the SORT1 option is recommended for results output in OUTPUT2 format and
SORT2 option is recommended for results output in PUNCH format.

196 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


13. PSDF and RMS von Mises stress results based on the Segalman Method are also written to
the .h3d file for Random Response Analysis (only available in the H3D format).

14. The four-letter abbreviation STRE is interchangeable with STRESS.

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

Altair Engineering OptiStruct 13.0 Reference Guide 197

Proprietary Information of Altair Engineering


SUBTITLE

I/O Options Entry

SUBTITLE - File Header

Description

The SUBTITLE command can be used in the I/O Options or Subcase Information sections to
define the subtitle for all subcases or for individual subcases respectively.

Format
SUBTITLE = name

Argument Description

name The subtitle for the subcase.

No default

Comments

1. The subtitle is written to the output files.

198 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SVELOCITY

I/O Options and Subcase Information Entry

SVELOCITY - Output Request

Description

The SVELOCITY command can be used in the I/O Options or Subcase Information sections to
request the form and type of modal participation velocities output for all subcases or individual
subcases respectively.

Format
SVELOCITY (sorting,format_list,form,peakoutput) = option

Argument Options Description

sorting <SORT1, SORT2> This argument only applies to the PUNCH format
(.pch file) or the OUTPUT2 format (.op2 file)
Default = blank output for normal modes, frequency response, and
transient subcases. It will be ignored without
warning if used elsewhere.

SORT1: Results for each frequency/


timestep are grouped together.

SORT2: Results for each grid/element are


grouped together (see comment
7).

blank: SORT1 is used for all results


except for transient analysis,
where SORT2 is used.

format <H3D, PUNCH, OP2, H3D: Results are output in Hyper3D


PLOT, blank> format (.h3d file).

Default = blank PUNCH: Results are output in Nastran


punch results format (.pch file).

OP2: Results are output in Nastran


output2 format (.op2 file) (see
comment 9).

Altair Engineering OptiStruct 13.0 Reference Guide 199

Proprietary Information of Altair Engineering


Argument Options Description

PLOT: Results are output in Nastran


output2 format (.op2 file) when
PARAM, POST is defined in the
bulk data section.

blank: Results are output in all active


formats for which the result is
available.

form <REAL, IMAG, REAL, IMAG: Provides rectangular format (real


PHASE> and imaginary) of complex
output.
Default = REAL
PHASE: Provides polar format (magnitude
and phase) of complex output.
Phase output is in degrees.

peakoutput <PEAKOUT> PEAKOUT: If PEAKOUT is present, only the


filtered frequencies from the
Default = blank PEAKOUT card will be considered
for this output.

option <YES, ALL, YES, ALL, blank: Results are output.


NO, NONE>

Default = YES NO, NONE: Results are not output.

Comments

1. When the SVELOCITY command is not present, modal participation velocities are not
output.

2. The SVELOCITY command is only valid for modal frequency response and modal transient
solution sequences.

3. The OFREQUENCY and OTIME I/O Options may be used to control the amount of output.

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

200 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


5. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

6. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.

7. In general, HyperView does not recognize the SORT2 format for results from the .op2 file.
When results are output only in SORT2 format (<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.

8. The abbreviation SVELO is interchangeable with SVELOCITY.

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

Altair Engineering OptiStruct 13.0 Reference Guide 201

Proprietary Information of Altair Engineering


SYSSETTING

I/O Options Entry

SYSSETTING – Run Control

Description

The SYSSETTING command can be used in the I/O Options section to alter system settings.
Any setting defined here may be over-ridden by command line arguments (see Run Options for
OptiStruct). Most of these options can also be specified in one of the config files (see
OptiStruct Configuration File).

Format
SYSSETTING(setting=option_list,setting=option_list,…)

Examples
SYSSETTING(RAMDISK=100)

SYSSETTING(SCRFMODE=buffered,stripe)

SYSSETTING(SPSYNTAX=mixed,RAMDISK=100,SCRFMODE=buffered,stripe,OS_RAM=1234)

Setting Options Description

BARPROP <STRICT, MIXED> STRICT: The CBAR and CBEAM beam element
connections cannot reference the PBEAM beam
Default = STRICT
property entries, respectively.

MIXED: The CBAR and CBEAM beam element


connections can reference the PBEAM and PBAR
beam property entries, respectively.

BUFFSIZE BUFFSIZE = 16832 The maximum size in 8 byte words of the records of
data written to the .op2 file. Use -1 to turn off
buffering.

CARDLENGTH <Integer> Defines the number of characters read on a single


line in the I/O Options and Subcase Information
Default = 80 sections. This can vary between 80 and 132
characters.

In the Bulk Data section, CARDLENGTH applies to


free and long free format lines only (fixed and long
format lines are always limited to 72 characters).

202 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Setting Options Description

DUPTOL Integer <0-5> Controls accuracy used during elimination of


potential duplicate cards. Two cards with identical
Default = 0 ID's are replaced by the first one, if all integer
values on both cards match exactly, and all float
values match with accuracy controlled by this
setting, otherwise identical IDs are flagged as
ERROR. Currently only GRID, CORDxx, and base
MAT/PROP entry duplicates are allowed (MATX,
MATT, and PROPX entries do not allow duplicates).

0: no tolerance, the values defined must be an


exact match.

1: for standard fixed 8-character without


exponent, the value must match up to 6 decimal
places.

2: for standard fixed 8-character without


exponent, the value must match up to 5 decimal
places.

3: for standard fixed 8-character without


exponent, the value must match up to 4 decimal
places.

4: for standard fixed 8-character without


exponent, the value must match up to 3 decimal
places.

5: for standard fixed 8-character without


exponent, the value must match up to just 2
decimal places.

If values are too large or too small to represent


without exponent, then both values must match
exactly when converted to 8-character form. Also,
for negative values, the accuracy is one digit
lower.

H3DVTAG <YES, NO> Appends the version of the H3D format used, onto
the .h3d file output by OptiStruct.
Default = NO
So the results file would then be
{filename}.h3d11 or {filename}.h3d12.

Note: It is not possible to select the H3D format


used for output; this is built into the
executable.

MAXLEN <Integer> Used to define the maximum allowable amount of

Altair Engineering OptiStruct 13.0 Reference Guide 203

Proprietary Information of Altair Engineering


Setting Options Description

memory to be used in MB. There is no default.

MAXLEN is not supported when the MUMPS solver


is used (including –ddm parallel runs).

MINLEN <Integer> Used to define the initial memory allocation in MB.


The default is 10% of OS_RAM. This is the same
as the legacy command, OS_RAM_INIT.

NPROC <Integer> Same as –nproc and -cpu options (see Run


(legacy Options for OptiStruct). Sets number of
command: CPU) Default = 1 processors in a multiprocessor (SMP) run.

OS_RAM <RAM in Mbytes> Memory limit in Mb. The solver will attempt to run
at least the minimum core solution regardless of
Default = 1Gbyte the memory limit. See Memory Limititations in the
User’s Guide for details.

PLOTELID <UNIQUE, ALLOWFIX> Controls the numbering scheme of the PLOTEL ID.

Default = UNIQUE UNIQUE requires all PLOTEL elements have unique


element IDs.

ALLOWFIX allows OptiStruct to automatically fix ID


collisions for PLOTEL. If PLOTEL elements have the
same IDs as some other elements, OptiStruct
renumbers the IDs of all PLOTEL by adding a large
offset value.

RAM_SAFETY <Real> Same as -rsf option. (see Run Options for


OptiStruct).
Default = 1.0

RAMDISK <RAM in Mbytes> Specifies an area in RAM allocated to store


information which otherwise would be stored in
Default = See comment scratch files on the hard drive.
5
See comment 5 below for more details.

SAVEFILE SAVEFILE = OUT SAVEFILE controls the behavior of the solver when
an output file with the same name already exists
when the program starts.

SAVEFILE = ALL will prevent overwriting output

204 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Setting Options Description

files by renaming an existing file by adding numeric


suffix, for example, jobname.h3d will be renamed
to jobname_nnn.h3d where nnn represents the
smallest number for file which does not exists yet.
This option tries to preserve files with all known
extensions, and it may use a large amount of disk
space if the same run is repeated multiple times.

SAVEFILE = OUT (default) will preserve only .out


and .stat files.

SAVEFILE = NONE will allow the solver to overwrite


any existing file.

SAVEFILE = ext, where ext is arbitrary file


extension (case insensitive, up to 9 characters).

See comments 8 and 9.

SCRFMODE <primary_option, Allows for the selection of different modes of


secondary_option> storing scratch files for a linear solver process
(especially for out-of-core and minimum-core
Primary options: BASIC, modes).
BUFFERED, UNBUFFER,
STRIPE BASIC: FORTRAN mode, direct access file.

Secondary option: BUFFERED: FORTRAN buffered.


MIXFCIO
UNBUFFER: C i/o mode (default).
Default =
1. For Linux: UNBUFFER STRIPE: Stripe main solver files on multiple disks
(except ones marked as slow).
2. For Windows
(without AMSES): MIXFCIO (only valid when combined with
BUFFERED, MIXFCIO BUFFERED): Use C (native) I/O routines instead of
FORTRAN read/write for main solver files.
3. For Windows (using
AMSES): BASIC See comment 7 below for more details.

SKIP10FIELD <CHECK, WARN> To detect disallowed use of potential expansion of


free format, error will be generated when 10 or
Default = CHECK more data fields is found on a bulk data card in free
format. Use SKIP10FIELD=WARN to allow reading
such card (extra fields will be disregarded instead
of causing error).

Altair Engineering OptiStruct 13.0 Reference Guide 205

Proprietary Information of Altair Engineering


Setting Options Description

SPSYNTAX <STRICT, CHECK, Controls how strict the checks are in the reader for
MIXED> mixing GRIDs and SPOINTs.

STRICT: When both grid/component pairs (G#/C#)


Default = CHECK
and grid lists for a given component (as on the
alternate formats ASET1 and USET1 bulk data
entries) are defined, this option will require that
the component be 0 or blank when the grid
reference is a scalar point (SPOINT), and that the
component be > 1 when the grid reference is a
structural grid point (GRID).

CHECK: When grid/component pairs (G#/C#) are


defined, this option will require that the component
be 0 or blank when the grid reference is a scalar
point (SPOINT), and that the component be > 1
when the grid reference is a structural grid point
(GRID). But when grid lists for a given component
(as on alternate formats ASET1 and USET1 bulk
data entries) are defined, this option will allow the
grid reference to be scalar points (SPOINT) or
structural grid points (GRID) when the component
is 0, 1 or blank; interpreting all of these as 0 for
scalar points and as 1 for structural grids.

MIXED: When grid/component pairs (G#/C#) and


grid lists for a given component (as on alternate
formats ASET1 and USET1 bulk data entries) are
defined, this option will allow the grid reference to
be scalar points (SPOINT) or structural grid points
(GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and
as 1 for structural grids.

See comment 6 below for more details.

SYNTAX <ALLOWINT, STRICT> Controls how strict the syntax checker in the
reader is.
Default = ALLOWINT
ALLOWINT is the default setting for OptiStruct, and
converts integer values to real values whenever
real values are expected. In those instances,
where the form of the input (Integer or Real)
indicates the nature of the input (for example,
when reading vector entries (X,Y,Z) with alternate
form (GID, , )), a negative integer value in the first
field, or a non-blank value in the second or third
field indicates the (X,Y,Z) format and all fields are

206 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Setting Options Description

read as real values.

STRICT follows more closely with other Nastran


codes, where integer values may only be entered in
integer value fields and real values must be entered
in real value fields. An error termination will occur
if an integer value is placed in a real value field
when this setting is chosen.

Note: This setting never changes results – it can


only cause the rejection of files that do not
follow the restrictions.

TABSTOPS TABSTOPS = 8 TABSTOPS allows you to change interpretation of


TAB character in the input. By default TAB stops
are spaced by 8 columns, which is standard on all
Unix/Linux terminals. Possible values are 4 (used
often on Windows) and 1 (replace each TAB with
exactly one space).

UNDEFTEMP <STRICT, ZERO> STRICT OptiStruct will error out if there


are some grid points without a
Default = STRICT
specified temperature (that is, a
minimum of one, but not all, grid
points in the model has a specified
temperature). The error message
includes information about GRID ID,
Element ID, and Load Set number.

ZERO OptiStruct will use a value of zero


for grids without a specified
temperature (that is, a minimum of
one, but not all, grid points in the
model has a specified
temperature). This allows users to
revert to the behavior of versions
prior to OptiStruct 13.0.

UPDATE UPDATE option Controls the behavior of


(quiet, verbose, ASSIGN,UPDATE,<filename>.
strict, off, unique,
permissive) quiet Less output (default).

Defaults = quiet and verbose More output including old and new
strict values.

Altair Engineering OptiStruct 13.0 Reference Guide 207

Proprietary Information of Altair Engineering


Setting Options Description

strict Do not allow non-supported cards


in update deck (default).

off Disable update.

unique Each ID only once.

permissive Allow all cards and repeat IDs.

Choose only one option from: quiet, verbose.

Choose only one option from: strict, off,


unique, permissive.

USERAM <RAM in Mbytes> Memory limit in Mb. The solver will use more than
the minimum memory required up to this limit, but
only if it improves the speed of the solution. See
Memory Limitations in the User’s Guide for details.

Comments

1. The number of fields in this card is not limited to 10, but it is limited by the current line
length (default 80).

2. Continuation lines are not allowed, multiple SYSSETTING cards are allowed.

3. The settings CPU and NPROC are interchangeable, and can also be specified on the
command line.

4. Each option except SCRFMODE must have exactly one argument. SCRFMODE arguments
should be comma separated.

5. For RAMDISK setting:


a) Use of a virtual disk instead of physical files may speed up solutions by reducing wait
time to access physical disk drives. Note that the use of RAMDISK will reduce the
amount of memory available for the solver and for file buffering performed by the
operating system (by Linux or Windows), and because of that it may not always
reduce the wall clock time for the solution. The most impact can be observed on
machines with very large physical memory (20GB or more) or when used to speed-up
main solver scratch file access using the SCRFMODE setting.
b) RAMDISK is automatically protected for overflow, so it is fine to specify 200MB for
RAMDISK when the total amount of scratch files will be larger than that.
c) RAMDISK is automatically specified for very small jobs, (less than 10,000 GRIDS). This
can be disabled by specifying RAMDISK=0. Automatic RAMDISK is not allocated for
fixed RAM jobs (the -fixlen command line option is used, see Run Options for
OptiStruct).
6. For SPSYNTAX setting:

208 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


a) When the component from a grid/component pair or for a list of grids (as on alternate
formats ASET1 and USET1 bulk data entries) is greater than 1, the grid reference must
always be a structural grid (GRID).
b) This control may also be set in the OptiStruct Configuration File.
7. For SCRFMODE setting:
a) This command controls the way scratch files from the linear equation solver are written
to the disk. These files are usually written and read several times, often in random
pattern, and this can have a significant impact on the total (wall clock) time for the
solution of large jobs. The default mode is optimal in most configurations, but choosing
between BASIC, BUFFERED or UNBUFFER may improve speed for some hardware and/or
some types of solution sequences, especially jobs including Lanczos eigenvalue solver.
b) In out-of-core and minimum-core solver modes, the solver creates one large scratch
file for each subcase and this file may be optionally located across multiple TMPDIRs.
In order to use this capability, SCRFMODE=STRIPE must be defined, otherwise the same
method as for other files (BASIC, BUFFERED or UNBUFFER) is used, and this large file
must therefore fit on a single TMPDIR.
c) STRIPE mode can be used when all TMPDIRs (not marked as SLOW) are fully
independent (that is, they should not be partitions on the same physical drive). This
mode results in the access to all disks similar to RAID0 - consecutive blocks of data
are split between separate TMPDIRs, and accessed in parallel, which can speed up disk
access considerably.

Warning: Using STRIPE with TMPDIRs allocated on the


same physical drive (even on different
partitions) will usually slow down the solution by
increasing wait times. Check with your system
administrator for information on the actual
hardware structure of your computer.

d) STRIPE requires multiple TMPDIR cards and has effect only for out-of-core or minimum-
core solutions.
e) Most modern operating systems (Linux in particular) use excess available RAM for the
buffering of disk i/o. The SCRFMODE command will have effect only for jobs which
exceed the capabilities of this buffer.
f) When AMSES is used on Windows, BASIC mode is enforced during AMSES calculations.
g) The –scrfmode option can be specified on the command line (see Run Options for
OptiStruct) – this overrides any information specified in the input file.
8. The SAVEFILE option tries to preserve only files in the start directory, that is, this option
has no effect when the input file is specified with a path, or the OUTFILE option defines a
different location for all output files. Unless SAVEFILE,NONE is specified, standard .out
and .stat files are always renumbered, even if they are created in different folder. All
files are renumbered at program start – .out file is preserved first, and then the same
NNN is used for all files found in the current folder. Only files with default names are
preserved (that is those starting with the same root as outfile). Note that this option
may sometimes cause the solver to fail if it renames the file which is intended for the
input.

9. Multiple SAVEFILE cards overwrite each other (the last one is in effect). Multiple
SAVEFILE,ext cards can be used (up to 5 extensions can be defined), but using of any of
the standard options (NONE/ALL/OUT) empties the list of previously defined extensions.

Altair Engineering OptiStruct 13.0 Reference Guide 209

Proprietary Information of Altair Engineering


TCURVE

I/O Options Entry

TCURVE – Output Request

Description

The TCURVE command can be used in the I/O Options section to define the plot title for
XYPLOT output from a random response analysis.

Format
TCURVE = title

Argument Description

title Character string.

Default = A default title is provided.

Comments

1. TCURVE may not be continued onto the next line.

2. A TCURVE definition applies to all plots defined after TCURVE until another definition of
TCURVE occurs.

Example:
XTITLE = X-A
YTITLE = Y-A
XYPLOT (first plot definition)
YTITLE = Y-B
TCURVE = C-A
XYPLOT (second plot definition)
would assign X-A, Y-A and the default plot title to the first plot, then X-A, Y-B and C-A
to the second plot.

210 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


THERMAL

I/O Options and Subcase Information Entry

THERMAL – Output Request

Description

The THERMAL command can be used in the I/O Options or Subcase Information sections to
request temperature output for all heat transfer analysis subcases or individual heat transfer
analysis subcases respectively.

Format
THERMAL (format_list) = option

Argument Options Description

format <PUNCH, PUNCH: Results are output in Nastran punch results


OP2, PLOT, format (.pch file).
H3D, blank>
OP2: Results are output in Nastran output2 format
Default =
(.op2 file) (see comment 7).
blank

PLOT: Results are output in Nastran output2 format


(.op2 file) when PARAM, POST is defined in the
bulk data section.

H3D: Results are output in Hyper3D format (.h3d


file).

blank: Results are output in all active formats for


which the result is available.

option <YES, ALL, YES, ALL, Thermal results are output at all grid points
NO, NONE, blank: for which temperature results are available.
SID>

Default = ALL NO, NONE: Thermal results are not output

SID: If a set ID is specified, Thermal results are


output only for grid points referenced by that
set.

Comments

1. When the THERMAL command is not present, thermal results are not output.

Altair Engineering OptiStruct 13.0 Reference Guide 211

Proprietary Information of Altair Engineering


2. Thermal output is only available for the heat transfer analysis solution sequence.

3. The PUNCH output produces TEMP bulk data entries, and the SID on the entries will be the
subcase number (=1 if no SUBCASES are specified).

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

5. Temperature output via the THERMAL output request is available for both linear steady
state heat transfer and linear transient heat transfer analyses.

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

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

212 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


THICKNESS

I/O Options and Subcase Information Entry

THICKNESS - Output Request

Description

The THICKNESS command can be used in the I/O Options section to request thickness output
for elements referencing a PSHELL or PCOMP property in:

Size/Free-size optimization
Analysis runs
Topology optimization

Format
THICKNESS (format_list, comp) = option

Argument Options Description

format <HM, H3D, blank> HM: Results are output in HyperMesh


results format (.res file).
Default = blank
H3D: Results are output in Hyper3D
format (.h3d file).

blank: Results are output in all active


formats for which the result is
available. (See comments 1 and
2)

comp <ALL, DESIGN, ALL: Thickness results are output for


NOPLY> all plies.

Default = DESIGN DESIGN, blank: Thickness results are output for


designable plies only.

NOPLY: No ply thickness results are


output.

Altair Engineering OptiStruct 13.0 Reference Guide 213

Proprietary Information of Altair Engineering


Argument Options Description

option <YES, ALL, NO, NONE> YES, ALL, blank: Thickness results are output

Default = YES
NO, NONE: Thickness results are not output.

Comments

1. When the THICKNESS command is not present, thickness results are output. THICKNESS
results for analysis runs, however, are not output by default and will be output only if
the THICKNESS data entry is present in the solver deck.

2. Thickness results are available for analysis runs, size/free-size optimization, and topology
optimization only.

3. When thickness results are output to the .h3d file, percentage thickness change is also
output.

4. Outputting the density results in all simulations allows analysis results to be plotted on
the density iso-surface in HyperView.

5. The frequency of this output is controlled by the DESIGN keyword on an OUTPUT definition
or, if no OUTPUT definition exists with the DESIGN keyword, by the DENSRES I/O option.

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

7. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

214 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


THIN

I/O Options and Subcase Information Entry

THIN - Output Request for Geometric Nonlinear Analysis Subcase

Description

The THIN command can be used in the I/O Options or Subcase Information sections to
request thinning and thickness output for all geometric nonlinear analysis subcases or
individual geometric nonlinear analysis subcases respectively.

Format
THIN (format, type) = option

Argument Options Description

format <H3D, blank> H3D: Results are output in Hyper3D


format (.h3d file).
Default = blank
blank: Results are output in all active
formats for which the result is
available.

type <ALL, THIN, THICK> ALL: Thinning and thickness results


are output.
Default = ALL
THIN: Percentage element thinning only
is output.

THICK: Element thickness only is output.

option <YES, ALL, NO, NONE, YES, ALL, blank: Thinning/thickness are output for
SID, PSID> all elements.

Default = ALL NO, NONE: Thinning/thickness are not


output.

SID: If a set ID is given, thinning/


thickness are output only for
elements listed in that set.

Altair Engineering OptiStruct 13.0 Reference Guide 215

Proprietary Information of Altair Engineering


Argument Options Description

PSID: If a property set ID is given,


thinning/thickness results for the
elements referencing properties
listed in the property set are
output.

Comments

1. THIN is only applicable for geometric nonlinear analysis subcases which are defined by an
ANALYSIS = NLGEOM subcase entry.

2. Only formats that have been activated by an OUTPUT or FORMAT statement are valid for
use on this card.

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

4. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

216 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


TITLE

I/O Options Entry

TITLE - File Header

Description

The TITLE command can be used in the I/O Options section to define the title for the
OptiStruct job.

Format
TITLE = name

Argument Description

name The title for the job.

No default

Comments

1. The title is printed into the output and results files.

Altair Engineering OptiStruct 13.0 Reference Guide 217

Proprietary Information of Altair Engineering


TMPDIR

I/O Options Entry

TMPDIR - Directory Selection

Description

The TMPDIR command is used in the I/O Options section to choose the directory in which the
scratch files are to be written.

Format
TMPDIR = <options> path

Argument Options Description

options -FILESIZE=n Maximum allowable file size in GB.

SLOW=1 Non-zero value denotes a network drive.

path <directory path> The path to the directory where scratch files are to be
written.
Default = ./

Examples

Windows Operating System

Local Drive

TMPDIR = -FILESIZE=13 D:\Dir1\Dir2\...\DirN\Scratch

TMPDIR = -FILESIZE=13 D:\Dir1\Dir2\...\DirN\Scratch Files

Network Drive

1. Map the network drive (drive on a remote machine) to a drive (Y:\) on your computer.

2. Use the path to your preferred scratch directory on the mapped network drive as the
“path” argument for TMPDIR.

TMPDIR = -FILESIZE=13 SLOW=1 Y:\Scratch

TMPDIR = -FILESIZE=13 SLOW=1 Y:\Scratch Files

218 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Linux Operating System

Local Drive
TMPDIR = -FILESIZE=13 /Dir1/Dir2/.../DirN/Scratch

TMPDIR = -FILESIZE=13 D:/Dir1/Dir2/.../DirN/Scratch Files

Comments

1. The total length of information on this card is limited to 200 characters (including the card
name and spaces between arguments). This data can be on a single line or span multiple
continuation lines. See Guidelines for I/O Options and Subcase Information Entries for an
example showing how to enter long file names on multiple lines.

2. Multiple TMPDIR cards are allowed (up to five entries). Scratch files will be allocated in all
directories depending on the options defined (see comments 3 through 8).

3. Before opening any scratch file during the solution process, the solver checks the
available free space on all TMPDIRs and allocates that file on the directory which has most
free space. This algorithm tends to spread disk usage between different directories, but
does not guarantee full usage of each TMPDIR area.

4. The main scratch file used during a linear solver process (that is solution of linear system
or eigen problem) can be split between multiple TMPDIRs (see SCRFMODE).

5. When TMPDIR is marked as SLOW, it is used only after other TMPDIRs are filled up.
Selecting directories for TMPDIR on disk drives shared across the network (that is on
different computers or on centralized file servers) is not recommended, and should be
avoided if possible. Some scratch files (especially for out-of-core and minimum-core
mode) are heavily used, and accessing them across the network will dramatically increase
wall clock time for the solution. The main purpose of the TMPDIR command is to avoid
this delay when work areas (home directories) are allocated on a central server, as is
customary at many large organizations. All scratch files are stored in the specified
directories. The scratch files are automatically removed at the end of the analysis unless
there is a system error or core dump (in which case, the scratch file may need to be
cleaned up manually).

6. See the SCRFMODE setting on the SYSSETTING I/O option for an additional way to use
multiple TMPDIR cards for large jobs.

7. The –tmpdir option can be specified on the command line (see Run Options for
OptiStruct); this overrides any information specified in the input file.

8. The filesize option is needed in rare cases when there is a file size limit imposed by
operating system. This limit is large enough for all practical problems in most cases. The
following cases are known to have a file size limit of 2GB:

FAT32 file system (Windows, sometimes Linux)


ext2 file system (older Linux distributions)
NFS version 2
It is recommended to upgrade hardware and/or operating system in these cases.

Altair Engineering OptiStruct 13.0 Reference Guide 219

Proprietary Information of Altair Engineering


220 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


TTERM

I/O Options and Subcase Information Entry

TTERM - Termination Time for Geometric Nonlinear Analysis Subcase

Description

The TTERM command can be used in a geometric nonlinear subcase to define the termination
time.

Format
TTERM = value

Argument Description

value Termination time for a geometric nonlinear subcase.

Default = 1.0 (Real)

Comments

1. TTERM is only allowed in geometric nonlinear subcases which are defined by an ANALYSIS
= NLGEOM, IMPDYN, or EXPDYN subcase entry.

Altair Engineering OptiStruct 13.0 Reference Guide 221

Proprietary Information of Altair Engineering


UNITS

I/O Options Entry

UNITS - Unit System for the Model

Description

The UNITS command can be used in the I/O Options section to define a system of units for
the model.

Format
UNITS = system

Argument Options Description

system <SI, CGS, MPA, SI: International system of units.


BG>
Length: meter = m
No default Mass: kilogram = kg
Time: second = s
Temperature: Kelvin = K
Pressure - Pa

CGS: Centimeter-gram-second system of units.


Length: centimeter = cm
Mass: gram = g
Time: second = s
Temperature: Kelvin = K
Pressure = barye = 0.1 Pa

MPA: Mega
Length: millimeter = mm
Mass: tonne = tonne
Time: second = s
Temperature: Kelvin = K
Pressure - MPa

BG: British Gravitational system of units.


Length: feet = ft
Mass: slug = slug
Time: second = s
Temperature: Rankine = R

222 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

Pressure = Ibf/ft 2

Comments

1. Only one instance of this card is supported. If multiple instances are defined, the last
occurrence will be used.

2. This UNITS data entry is the same as the DTI,UNITS entry.

Altair Engineering OptiStruct 13.0 Reference Guide 223

Proprietary Information of Altair Engineering


VELOCITY

I/O Options and Subcase Information Entry

VELOCITY - Output Request

Description

The VELOCITY command can be used in the I/O Options or Subcase Information sections to
request velocity vector output for all subcases or individual subcases respectively.

Format
VELOCITY(sorting,format,form,rotations,random,peakoutput) = option

Argument Options Description

sorting <SORT1, SORT2> This argument only applies to the PUNCH format
(.pch file) or the OUTPUT2 format (.op2 file)
Default = blank output for normal modes, frequency response, and
transient subcases. It will be ignored without
warning if used elsewhere.

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, OPTI, HM: Results are output in HyperMesh


PUNCH, OP2, HG, results format (.res file).
PLOT, blank>
H3D: Results are output in Hyper3D
Default = blank format (.h3d file).

OPTI: Results are output in OptiStruct


results format (.disp file).

224 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

PUNCH: Results are output in Nastran


punch results format (.pch file).

OP2: Results are output in Nastran


output2 format (.op2 file) (see
comment 11).

HG: Results are output in HyperGraph


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

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, COMPLEX (HM Provides a combined magnitude/


IMAG, PHASE, only), blank: phase form of complex output to
BOTH> the .res file for the HM output
format.
Default (HM only)
= COMPLEX REAL or IMAG: Provides rectangular format (real
and imaginary) of complex
Default (all other output (See comment 9).
formats) = REAL
PHASE: Provides polar format (magnitude
and phase) of complex output.
Phase output is in degrees (See
comment 9).

Altair Engineering OptiStruct 13.0 Reference Guide 225

Proprietary Information of Altair Engineering


Argument Options Description

BOTH (HM only): Provides both polar and


rectangular formats of complex
output.

rotations <ROTA, NOROTA> ROTA: Requests output of rotational


velocity results (in addition to
Default = NOROTA
rotational velocity results).

NOROTA: Rotational velocity results are


not output.

random <PSDF, RMS> PSDF: Requests PSD and RMS results


from random response analysis
No default 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> PEAKOUT: If PEAKOUT is present, only the


filtered frequencies from the
Default = blank PEAKOUT card will be considered
for this output.

option <YES, ALL, NO, YES, ALL, blank: Velocity is output for all nodes.
NONE, SID>

Default = YES NO, NONE: Velocity is not output.

226 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

SID: If a set ID is given, velocity is


output only for nodes listed in
that set.

Comments

1. When the VELOCITY command is not present, velocity vector is not output.

2. Velocity output is available for frequency response and transient analysis solution
sequences.

3. The form argument is only applicable for frequency response analysis. It is ignored for
other analysis types.

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

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

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

7. For optimization, the frequency of output to a given format is controlled by the I/O
option OUTPUT. In previous versions of OptiStruct, a combination of the I/O options
FORMAT and RESULTS were used; this method is still supported, but not recommended as it
does not allow different frequencies for different formats.

8. In general, HyperView does not recognize the SORT2 format for results from the .op2 file.
When results are output only in SORT2 format (<Result Keyword> (SORT2, OUTPUT2, …
.)), the results are written by OptiStruct into the .op2 file in SORT2 format, but when
the .op2 file is imported into HyperView, the results in SORT2 format are not recognized.
Therefore, the SORT1 option is recommended for results output in OUTPUT2 format and
SORT2 option is recommended for results output in PUNCH format.

9. Results in binary format (.h3d or .op2) are always output in PHASE/MAG form, regardless
of the options specified in the FORM field. The corresponding post-processors
(HyperView/HyperGraph) can easily convert the PHASE/MAG format to the required
formats. Results in ASCII formats are output in the specified/requested FORM.

10. The four-letter abbreviation VELO is interchangeable with VELOCITY.

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

Altair Engineering OptiStruct 13.0 Reference Guide 227

Proprietary Information of Altair Engineering


XTITLE

I/O Options Entry

XTITLE – Output Request

Description

The XTITLE command can be used in the I/O Options section to define the x-axis label for
XYPUNCH or XYPLOT output from a random response analysis.

Format

XTITLE = title

Argument Description

title Character string.

Default = blank

Comments

1. XTITLE may not be continued onto the next line.

2. An XTITLE definition applies to all plots defined after XTITLE until another definition of
XTITLE occurs.

Example:
XTITLE = X-A
YTITLE = Y-A
XYPLOT (first plot definition)
YTITLE = Y-B
TCURVE = C-A
XYPLOT (second plot definition)
would assign X-A, Y-A and the default plot title to the first plot, then X-A, Y-B, and C-A
to the second plot.

228 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


XYPEAK / XYPLOT / XYPUNCH

I/O Options Entry

XYPEAK - Output Request


XYPLOT - Output Request
XYPUNCH - Output Request

Description

The XYPEAK, XYPLOT, and XYPUNCH commands can be used in the I/O Options section to
request output from a random response analysis. The XYPUNCH command can also be used
with the RESPONSE plot-type to request .pch file output from a frequency response analysis.

Format
operation, curve-type, plot-type / entity ID(item code) list

Argument Options Description

operation <XYPEAK, XYPEAK: Generates a .peak file containing a summary of the


XYPLOT, requested output for random response analysis.
XYPUNCH>
XYPLOT: Generates a HyperGraph session file and related
No default data files for the requested output for random
response analysis.

XYPUNCH: Generates a .pch file for the requested output for


random response analysis.

With the plot-type RESPONSE, this command can


also be used to generate .pch file output for
frequency response analysis.

curve-type <DISP, VELO, DISP: Requests output for displacement.

ACCE, FORCE,
VELO: Requests output for velocity.
STRESS,
STRAIN>
ACCE: Requests output for acceleration.
No default
FORCE: Requests output for force.

For plot-type RESPONSE:


CBUSH and CELAS elements only.

Altair Engineering OptiStruct 13.0 Reference Guide 229

Proprietary Information of Altair Engineering


Argument Options Description

For plot-type PSDF:


CBUSH, CVISC, CDAMP, and CELAS elements only.

STRESS: Requests output for element stress.

For plot-types PSDF and AUTO.

STRAIN: Requests output for element strain.

For plot-types PSDF and AUTO.

plot-type <PSDF, AUTO, PSDF: Requests power spectral density function for
RESPONSE> random response analysis. (see comment 5)

No default
AUTO: Requests autocorrelation for random response
analysis.

RESPONSE: Requests time or frequency in SORT2 format or


grid identification numbers in SORT1 format.

RESPONSE is only supported for the XYPUNCH


operation for frequency response analysis.

entity ID (item List of grid or GRID: Each entry consists of a GRID or SPOINT ID
code) list element, followed by a component of motion (T1, T2, T3,
component R1, R2, or R3) in parentheses. In the components
pairs. of motion, T signifies translation and R signifies
rotation while the numbers indicate the
The list must translational direction or rotational axis.
come after a
slash "/". For frequency response analyses, the
Each entry in components of motion are T1RM, T2RM, T3RM,
the list is T1IP, T2IP, T3IP, R1RM, R2RM, R3RM, R1IP, R2IP,
comma and R3IP, where RM signifies Real or Magnitude
separated. and IP signifies Imaginary or Phase. The type of
the response depends on a preceding output
No default request.

For SPOINTs, the component must be T1, T1RM,


or T1IP.

230 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

ELEMENT: For elements, the item code (number code only)


represents a component of the element stress/
strain, which is described in DRESP1 – Frequency
Response Stress/Strain Item Codes and DRESP1 –
_Frequency Response Force Item Codes

Examples

XYPLOT, XYPEAK, VELO, PSDF / 3(T2), 6(T2)

XYPEAK, DISP, AUTO / 223(T3)

XYPEAK, XYPLOT, XYPUNCH, ACCE, PSDF / 8(T1), 9(T1), 8(T2), 9(T2)

Comments

1. Unlike other output requests, XYPEAK, XYPLOT, and XYPUNCH may be combined on a single
line (as shown in the example above).

2. If the XYPEAK, XYPLOT, or XYPUNCH commands are not supplied, then no random response
results will be output.

3. If the XYPEAK, XYPLOT, or XYPUNCH commands are supplied, but with an incomplete
definition, an error termination will occur.

4. For complex results, the format of XYPUNCH output (Real/Imaginary or Phase/Magnitude) is


determined by the relevant result output request (ACCELERATION, DISPLACEMENT,
STRESS, STRAIN, FORCE or VELOCITY). Real/Imaginary is the default if not otherwise
indicated.

5. Multiple RANDOM subcase information entries with non-unique ID’s are allowed in a single
model. Therefore, if the plot-type field is set to PSDF, then the RANDOM ID will be added
to the XYPUNCH headers in the corresponding result sections of the .pch file when
multiple RANDOM entries are present in the same deck. If only one RANDOM entry is
present, the RANDOM ID is not printed.

Altair Engineering OptiStruct 13.0 Reference Guide 231

Proprietary Information of Altair Engineering


YTITLE

I/O Options Entry

YTITLE – Output Request

Description

The YTITLE command can be used in the I/O Options section to define the y-axis label for
XYPUNCH or XYPLOT output from a random response analysis.

Format
YTITLE = title

Argument Description

title Character string.

Default = blank

Comments

1. YTITLE may not be continued onto the next line.

2. A YTITLE definition applies to all plots defined after YTITLE until another definition of
YTITLE occurs.

Example:
XTITLE = X-A
YTITLE = Y-A
XYPLOT (first plot definition)
YTITLE = Y-B
TCURVE = C-A
XYPLOT (second plot definition)
would assign X-A, Y-A and the default plot title to the first plot, then X-A, Y-B, and C-A
to the second plot.

232 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Subcase Information Section

Altair Engineering OptiStruct 13.0 Reference Guide 233

Proprietary Information of Altair Engineering


A2GG

Subcase Information Entry

A2GG - Direct Input Fluid-Structure Coupling Matrix Selection

Description

The A2GG command can be used in the Subcase Information section to select a direct input
fluid-structure coupling matrix.

Format
A2GG = name

Argument Description

name Name of a fluid-structure coupling matrix that is input in the bulk data
section using the DMIG card.

Comments

1. DMIG matrices will not be used unless selected in the Subcase Information section.

2. The matrix selected applies to all subcases.

3. The selected fluid-structure coupling matrix is always added to the computed coupling
matrix.

4. The referenced DMIG entry must be a square matrix (field 4 must be 1), where GJ
corresponds to fluid points, CJ = 0, Gi corresponds to structural points, Ci corresponds to
DOF, and Ai corresponds to the area values.

5. Multiple instances of A2GG are not allowed, and will result in an error termination.

234 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


ANALYSIS

Subcase Information Entry

ANALYSIS - Run Control and Solution Sequence Identifier

Description

The ANALYSIS command can be used in the I/O Options section to request that only a finite
element analysis be performed (optimization input is ignored). It may also be used in the I/O
Options or Subcase Information sections to identify the solution sequence for all subcases or
for individual subcases, respectively.

Format
ANALYSIS = option

Argument Options Description

option <ONLY, OPTSKIP, The first two options ONLY and OPTSKIP refer to the run
STATICS, NLSTAT, control functionality of the ANALYSIS command:
MODES, MCEIG,
BUCK, DFREQ, ONLY: Performs finite element analysis run only.
MFREQ, DTRAN, Optimization inputs are checked but
MTRAN, DFOUR, ignored.
MFOUR, HEAT,
NLHEAT, MBD, OPTSKIP:
Performs finite element analysis run only.
NLGEOM, IMPDYN,
Optimization inputs are ignored.
EXPDYN, FATIGUE>

Default = ONLY The remaining options refer to the solution sequence


identification functionality of the ANALYSIS command:

STATICS: Linear static or nonlinear quasi-static gap


analysis.

NLSTAT: Nonlinear quasi-static analysis.

HEAT: Linear steady-state heat transfer analysis


or linear transient heat transfer analysis.

NLHEAT: Nonlinear steady-state heat transfer


analysis.

MODES: Normal modes analysis.

MCEIG: Modal complex eigenvalue analysis.

Altair Engineering OptiStruct 13.0 Reference Guide 235

Proprietary Information of Altair Engineering


Argument Options Description

BUCK: Linear buckling analysis.

DFREQ: Direct frequency response analysis.

MFREQ: Modal frequency response analysis.

DTRAN: Direct transient response analysis.

MTRAN: Modal transient response analysis.

DFOUR: Direct transient response analysis through


Fourier transformation.

MFOUR: Model transient response analysis through


Fourier transformation.

MBD: Multi-body dynamics analysis.

NLGEOM: Geometric nonlinear implicit (quasi-)static


analysis.

IMPDYN: Geometric nonlinear implicit dynamic


analysis.

EXPDYN: Geometric nonlinear explicit dynamic


analysis.

FATIGUE: Fatigue analysis.

Comments

1. ANALYSIS=ONLY or ANALYSIS=OPTSKIP are only applicable in the I/O Options section.

2. ANALYSIS=ONLY or ANALYSIS=OPTSKIP may be used in combination with one of the other


ANALYSIS options.

3. When ANALYSIS=ONLY or ANALYSIS=OPTSKIP are used, all elements (including design


elements) are treated as non-design elements.

4. When ANALYSIS=ONLY or ANALYSIS=OPTSKIP are used, all properties and grids referenced
by size and shape variables will be set at the values on the associated property and GRID
data.

236 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


B2GG

Subcase Information Entry

B2GG – Direct Input Viscous Damping Matrix Selection

Description

The B2GG command can be used in the Subcase Information section to select a direct input
viscous damping matrix.

Format
B2GG = name

Argument Description

name Name of a damping matrix that is input in the bulk data section using the
DMIG card.

Comments

1. DMIG matrices will not be used unless selected.

2. This matrix is handled like the damper elements CDAMPi and CVISC.

3. Terms are added to the viscous damping matrix before any constraints are applied.

4. The matrix must be symmetric, that is field 4 on the referenced DMIG entry must contain
the integer 6.

5. When multiple instances of this card occur, the referenced DMIG entries are combined.
This behavior differs from that of Nastran, which only recognizes the last instance of this
card in the same situation.

Altair Engineering OptiStruct 13.0 Reference Guide 237

Proprietary Information of Altair Engineering


CMETHOD

Subcase Information Entry

CMETHOD – Data Selection

Description

The CMETHOD command can be used in the Subcase Information section to select the method
for complex eigenvalue extraction.

Format
CMETHOD = option

Argument Options Description

option < SID > SID: Set identification of an EIGC bulk data entry.

No default

Comments

1. Only one CMETHOD entry can be defined in a subcase.

2. A CMETHOD entry is required for complex eigenvalue analysis.

3. If present above the first subcase, it is applied to all complex eigenvalue subcases.

238 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CMSMETH

Subcase Information Entry

CMSMETH – Run Control

Description

The CMSMETH command can be used in the Subcase Information section to request that only a
component mode synthesis solution be performed and to select a component mode synthesis
method definition to be used.

Format
CMSMETH = option

Argument Option Description

option <CMSID> CMSID: Identification of a CMSMETH bulk data entry.

No default

Comments

1. All subcases must have the same MPC reference; in which case it runs the component
mode synthesis (flexible-body preparation) solution sequence using the CMSMETH reference
and the common MPC reference.

Altair Engineering OptiStruct 13.0 Reference Guide 239

Proprietary Information of Altair Engineering


CNTNLSUB

Subcase Information Entry

CNTNLSUB – Continue nonlinear solution sequence from a preceding nonlinear subcase

Description

The CNTNLSUB command can be used in the Subcase Information section to continue a
nonlinear solution from a preceding nonlinear subcase, and thus create complex loading
sequences.

Format
CNTNLSUB = option

Argumen Option Description


t

option <Yes, No, Yes: This nonlinear subcase continues the nonlinear
SID> solution from the nonlinear subcase immediately
preceding.
Default = Yes
"Preceding" refers to the sequence of subcases
in the deck, not the subcase numbering. If
CNTNLSUB,YES is used within a subcase, then
the preceding subcase must be nonlinear
subcase of the same type. If CNTNLSUB,YES is
used above the first subcase, then all the
consecutive nonlinear subcases of the same
type will continue each other (however, other
types of subcases interspersed between
nonlinear ones will “break” the continuation
sequence).

No: This nonlinear subcase executes a new solution


sequence starting from the initial, stress-free
state of the model. See comment 1.

SID: Subcase This nonlinear subcase continues nonlinear


ID solution from SUBCASE SID. SUBCASE SID must
precede the current subcase in the deck and
must be a nonlinear subcase of the same type.
See comment 1.

240 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. This command applies only to nonlinear subcases.

Nonlinear subcases may only be continued from other nonlinear subcases of the same
analysis type. that is, geometric linear subcases (ANALYSIS=NLSTAT) may only be
continued from other geometric linear subcases, and geometric nonlinear subcases
(ANALYSIS=NLGEOM, IMPDYN or EXPDYN) may only be continued from other geometric
nonlinear subcases.

2. Only one CNTNLSUB entry can be defined for each subcase.

3. If CNTNLSUB = option is present above the first subcase, it is applied to all nonlinear
subcases. (CNTNLSUB = SID is only allowed within a subcase).

4. CNTNLSUB is mostly relevant in path-dependent problems, such as plasticity or gap/


contact analysis with friction/stick. In these problems, subcase continuation can be used
to create complex loading paths that will typically produce very different results than
simple proportional loading of a single subcase. CNTNLSUB also affects the convergence
history and, to some extent, the results in problems that typically are not path-
dependent, such as gap/contact analysis without friction.

Altair Engineering OptiStruct 13.0 Reference Guide 241

Proprietary Information of Altair Engineering


DEFORM

Subcase Information Entry

DEFORM – Data Selection

Description

The DEFORM command can be used in the Subcase Information section to select an element
deformation set.

Format
DEFORM = option

Argument Options Description

option < SID > SID: Set identification of a DEFORM bulk data entry.

Comments

1. Only one DEFORM entry can be defined for each subcase.

2. If present above the first subcase, it is applied to all linear static, linear buckling, and
nonlinear quasi-static (Gap/Contact) subcases.

242 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DESOBJ

Subcase Information Entry

DESOBJ – Objective Selection

Description

The DESOBJ command is used in the Subcase Information section to select a single response
definition as the objective function of an optimization, or to select system response definitions
when the objective function is the least squares sum of these definitions. The DESOBJ
command also indicates if this response is to be minimized or maximized.

Format
DESOBJ (type) = integer, PROB

Argument Options Description

type <MIN, MAX, MIN: The objective is to minimize the


MINP, MAXP> response.

Default = MIN MAX: The objective is to maximize the


response.

MINP: The objective is to minimize the percentile


value of the response (see comment 8).

MAXP: The objective is to maximize the


percentile value of the response (see
comment 8).

integer < ID > ID: Identification number of a DRESP1,


DRESP2, DRESP3, or DSYSID bulk data
No default entry.

PROB <Probability> Probability Probability related to the reliability


requirement (see comment 8).
<50.0 < Real <
100.00>

Altair Engineering OptiStruct 13.0 Reference Guide 243

Proprietary Information of Altair Engineering


Comments

1. Only one DESOBJ card can be present.

2. For global DRESP1 responses (responses which are not subcase dependent) or DRESP2 or
DRESP3 responses containing either DRESP1L/DRESP2L data or global DRESP1 responses,
the DESOBJ data must be above the first SUBCASE statement.

3. If the DESOBJ data references responses that are subcase specific, then the DESOBJ
statement must be within the appropriate subcase definition and the subcase must be of
the appropriate type.

4. If the DSYSID entry is referenced by a DESOBJ subcase entry, a least squares objective
function is used in the optimization. The objective function is the sum of the squared,
weighted, normalized differences between the target responses and those calculated by
the finite element analysis.

5. DSYSID entries must have unique identification numbers with respect to DRESP1, DRESP2,
and DRESP3 entries.

6. DRESP1, DRESP2, and DRESP3 entries referenced by the DSYSID entry can define only a
single response per subcase when the DESOBJ formulation is used.

7. Time dependent responses should not be referenced by the DESOBJ entry. The minmax
formulation should be used for optimization problems that have time-dependent responses
as the objective functions. The minmax formulation can be selected using the MINMAX or
MAXMIN subcase information entry.

8. The MAXP, MINP, and PROB options can be input during a Reliability-based Design
Optimization run. MINP and MAXP are not supported if random design variables or random
parameters are not defined in the model.

9. This entry is represented as an optimization objective in HyperMesh.

244 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DESSUB

Subcase Information Entry

DESSUB – Constraint Selection

Description

The DESSUB command can be used in the Subcase Information section, within a subcase
definition, to select a constraint set that is subcase dependent.

Format
DESSUB = integer

Argument Options Description

integer < SID > SID: Set identification of a DCONSTR or DCONADD


bulk data entry.
No default

Comments

1. The constrained response referenced by the DESSUB constraint selection must be subcase
dependent.

2. This entry is represented as an optimizationconstraint in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 245

Proprietary Information of Altair Engineering


DESVAR

Subcase Information Entry

DESVAR – Data Selection

Description

The DESVAR command can be used in the Subcase Information section to select a set of
design variables for use in an optimization run.

Format
DESVAR = option

Argument Options Description

option <ALL, SID > ALL: All design variables in the input data, as defined
by DESVAR bulk data entries, are used in the
Default = ALL optimization.

SID: The ID of a SET I/O Option definition. Only


those design variables, as defined by DESVAR
bulk data entries with IDs appearing in the
referenced SET entry are considered in the
optimization.

Comments

1. Only one DESVAR command may appear in the Subcase Information section and should
appear before the first SUBCASE statement.

2. The DESVAR command is optional. If it is absent, all DESVAR bulk data entries will be
used.

3. DESVAR bulk data entries that are not selected by this command are frozen at their initial
values (that is same as setting XINIT=XLB=XUB) and all referenced properties will still be
governed by the DESVAR settings.

246 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DLOAD

Subcase Information Entry

DLOAD - Data Selection

Description

The DLOAD command can be used in the Subcase Information section to select a dynamic load
to be applied in a transient or frequency response problem.

Format
DLOAD = option

Argument Options Description

option < SID > SID: Set identification of a DLOAD, TLOAD1, TLOAD2,
RLOAD1, RLOAD2, ACSRCE, or CAALOAD bulk data
No default entry.

Comments

1. RLOAD1 and RLOAD2 are for frequency response loadings.

2. TLOAD1 and TLOAD2 are for transient response loadings.

Altair Engineering OptiStruct 13.0 Reference Guide 247

Proprietary Information of Altair Engineering


EIGVRETRIEVE

Subcase Information Entry

EIGVRETRIEVE - External Data Selection

Description

The EIGVRETRIEVE command can be used in the Subcase Information section to retrieve
eigenvalue and eigenvector results of a normal modes analysis from an external data file
(.eigv).

Format
EIGVRETRIEVE = integer1, integer2, integer3, ...

Argument Options Description

integer# <integer> Retrieves eigenvalues and eigenvectors from


external data files for use in a modal frequency
No default response analysis.

The external eigenvalue data file names are of the


form:
<prefix>_#.eigv

where <prefix> is defined by the EIGVNAME I/O


Options entry and # is one of the integer
arguments defined here.

Comments

1. Only one occurrence of EIGVRETRIEVE is permitted per subcase.

2. When multiple integer arguments are provided, eigenvalues are retrieved from multiple
external data files and combined.

3. If EIGVRETRIEVE is not present, eigenvalue and eigenvector results are not retrieved from
external data files and a normal modes analysis is performed for the modal frequency
response or modal transient response analysis subcase.

248 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


EIGVSAVE

Subcase Information Entry

EIGVSAVE - Output Request

Description

The EIGVSAVE command can be used in the Subcase Information section to output eigenvalue
and eigenvector results of a normal modes analysis to an external data file (.eigv).

Format
EIGVSAVE = integer

Argument Options Description

integer <integer> Outputs eigenvalues and eigenvectors obtained


from a normal modes analysis to an external data
No default file.

The external eigenvalue data file name is of the


form:
<prefix>_#.eigv

where, <prefix> is defined by the EIGVNAME I/O


Options entry and # is the integer argument
defined here.

Comments

1. Only one occurrence of EIGVSAVE per subcase is permitted.

2. If EIGVSAVE is not present, eigenvalue and eigenvector results do not get exported to an
external data file.

Altair Engineering OptiStruct 13.0 Reference Guide 249

Proprietary Information of Altair Engineering


ESLTIME

Subcase Information Entry

ESLTIME – Data Selection

Description

The ESLTIME command can be used in the Subcase Information section to select particular
time steps for geometric nonlinear response ESLM optimization or Multi-body Dynamics ESLM
optimization.

Format
ESLTIME = option

Argument Option Description

option < SID > SID: Set identification number of an ESLTADD or


ESLTIME bulk data entries (see Comments 1 and
No default 2).

Comments

1. Only one ESLTIME entry can be present for each subcase. It can only be used in
subcases that contain an ANALYSIS = NLGEOM, IMPDYN, EXPDYN or MBD entry.

2. If the SID referenced by the ESLTIME subcase information entry matches with the SID
defined for an ESLTADD bulk data entry, then the information on this entry alone is
selected. However, if an ESLTADD bulk data entry does not exists with the referenced
SID, then any ESLTIME bulk data entries that have this SID will be selected.

250 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


EXCLUDE

Subcase Information Entry

EXCLUDE - Exclusion Set Selection

Description

The EXCLUDE command can be used in the Subcase Information section to select a set of
elements to be excluded from a linear buckling analysis.

Format
EXCLUDE = option

Argument Options Description

option <ESID> ESID - set identification number of an element set.

No default

Comments

1. The element set is defined using the SET bulk data entry.

2. This subcase information entry is only valid when it appears in a buckling subcase.

3. The excluded elements are only removed from the geometric stiffness matrix, resulting in
a buckling analysis with elastic boundary conditions. This means that the excluded
elements may still be showing movement in the buckling mode.

4. Extreme caution is advised when using the EXCLUDE command. In general, excluding any
region from buckling analysis can, and usually will, result in a higher, overestimated critical
load calculation, which then may produce false overconfidence in a structure’s load
bearing capacity. The excluded region will have no effect on the calculated critical load
only if the excluded modes are geometrically separated from, or orthogonal to, the actual
critical buckling mode.

5. A descriptive engineering explanation is as follows: buckling analysis by design seeks the


weakest, least stable configuration of the structure. Excluding any region from this
search can cause you to miss the actual critical buckling mode that involves the
respective region and has the least load bearing capacity.

Altair Engineering OptiStruct 13.0 Reference Guide 251

Proprietary Information of Altair Engineering


FATDEF

Subcase Information Entry

FATDEF – Data Selection

Description

The FATDEF command can be used in the Subcase Information section to select a FATDEF bulk
data entry that will define the elements, and their associated fatigue properties, to be
considered for fatigue analysis.

Format

FATDEF = option

Argument Option Description

Option < SID > SID: Set identification of a FATDEF bulk data entry.

No default

Comments

1. FATDEF bulk data entries will not be used unless selected in the Subcase Information
section.

2. If present above the first subcase, it is applied to all fatigue analysis subcases.

252 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


FATPARM

Subcase Information Entry

FATPARM – Data Selection

Description

The FATPARM command can be used in the Subcase Information section to select a FATPARM
bulk data entry that will define the parameters to be used for a fatigue analysis.

Format

FATPARM = option

Argument Option Description

Option < SID > SID: Set identification of a FATPARM bulk data entry.

No default

Comments

1. FATPARM bulk data entries will not be used unless selected in the Subcase Information
section.

2. If present above the first subcase, it is applied to all fatigue analysis subcases.

Altair Engineering OptiStruct 13.0 Reference Guide 253

Proprietary Information of Altair Engineering


FATSEQ

Subcase Information Entry

FATSEQ – Data Selection

Description

The FATSEQ command can be used in the Subcase Information section to indicate that a
subcase is a fatigue analysis subcase and to select a FATSEQ bulk data entry that will define
the loading sequence for the fatigue analysis.

Format

FATSEQ = option

Argument Option Description

Option < SID > SID: Set identification of a FATSEQ bulk data entry.

No default

Comments

1. This command may not appear above the first subcase.

254 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


FREQUENCY

Subcase Information Entry

FREQUENCY - Data Selection

Description

The FREQUENCY command can be used in the Subcase Information section to select the set of
forcing frequencies to be solved in a frequency response problem.

Format
FREQUENCY = option

Argument Option Description

option < SID > SID: Set identification of FREQ, FREQ1, FREQ2, FREQ3,
FREQ4, and FREQ5 bulk data entries.
No default

Comments

1. A frequency set selection is required for transient response by the Fourier transform
method when TSTEP (FOURIER) is used. The Fourier transform will be performed at the
frequencies specified.

2. All FREQi data with the same set identification number will be used.

3. If present above the first subcase, it is applied to each frequency response or transient
subcase without a FREQUENCY command.

Altair Engineering OptiStruct 13.0 Reference Guide 255

Proprietary Information of Altair Engineering


GLOBSUB

Subcase Information Entry

GLOBSUB - Global Model and Transfer Zone Selection

Description

The GLOBSUB entry can be used in the Subcase Information section to select a subcase that
references the global structure for local-global analysis. A set of grid points in the local
structure that defines the transfer zone can also be specified.

Format
GLOBSUB, SUBID, SID

Argument Value Description

SUBID <integer > 0> Specifies the identification number of the subcase that
contains the global structure definition (via SUBMODEL).

SID <integer > 0> Specifies the set of grid points in the local structure
that defines the transfer zone. The displacements from
the global structure are interpolated and applied to this
set of grid points.

Comments

1. The transfer zone should contain only 3-dimensional elements in both the local and global
structures. Second order elements (for example, CHEXA20) are allowed. There is no
further restriction on element types elsewhere in the structure.

2. The transfer zone may represent single or multiple cuts (sections) through the structure.
Multiple cuts should be separated from each other, that is, they should not exist closer
than the element size of the global model.

3. The GLOBSUB entry should always reference the subcase ID of a global subcase that is
defined above its corresponding local subcase.

256 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GROUNDCHECK

Subcase Information Entry

GROUNDCHECK – Rigid Body Motion Grounding Check

Description

The GROUNDCHECK command can be used in the Subcase Information section to perform a
grounding check analysis on the stiffness matrix to expose unintentional constraints by moving
the model rigidly.

Format
GROUNDCHECK(print,GRID=gid,THRESH=thresh) = option

Argument Option Description

print < PRINT, NOPRINT > PRINT: Write output to the .out file.
Default = PRINT
NOPRINT: Do not write output to the .out file.

grid < GID > Grid Point ID: Reference grid point for the
Default = geometric calculation of the rigid body motion.
center of the
structure.

thresh <e> Maximum strain energy which passes the check.


Default = largest term
in the stiffness matrix,
divided by 1.0E10.

option < YES, NO > YES: Grounding check is performed.


Default = YES
NO: Grounding check is not performed.

Comments

1. GROUNDCHECK must be specified before the first SUBCASE.

Altair Engineering OptiStruct 13.0 Reference Guide 257

Proprietary Information of Altair Engineering


2. Grounding check is performed on all degrees-of-freedom of the model and all degrees-of-
freedom that are not constrained by SPC. MPC equations are not used in the check.

3. Any MPC that will be violated due to rigid body modes is reported. An equivalent energy
magnitude is also calculated between MPC violation and the strain energy. The
equivalent energy from MPC violation is added to the strain energy when performing the
grounding check.

258 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


IC

Subcase Information Entry

IC – Transient and Explicit Analysis Initial Condition Set Selection

Description

The IC command may be used in the Subcase Information section to select initial conditions
for transient and explicit analysis.

Format
IC = option

Example
IC = 10

Argument Option Description

option < SID > SID: Set identification number of TEMP, TEMPD, TIC,
TICA bulk data entries.
No default

Comments

1. TIC and TICA entries will not be used (therefore, no initial conditions) unless selected in
the Subcase Information section.

2. Initial conditions cannot be used with modal transient analysis.

Altair Engineering OptiStruct 13.0 Reference Guide 259

Proprietary Information of Altair Engineering


INVEL

Subcase Information Entry

INVEL – Multi-Body Initial Velocity Selection

Description

The INVEL command can be used in the Subcase Information section to select a multi-body
initial velocity set to be applied in a multi-body problem.

Format
INVEL = option

Argument Option Description

option < SID > SID: Set identification if INVELB or INVELJ bulk data
entries.
No default

Comments

1. Only one INVEL entry can be present for each subcase.

2. This subcase information entry is only valid when it appears in a multi-body subcase.

260 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


K2GG

Subcase Information Entry

K2GG - Direct Input Stiffness Matrix Selection

Description

The K2GG command can be used in the Subcase Information section to select a direct input
stiffness matrix.

Format
K2GG = name

Argument Description

name Name of a stiffness matrix that is input in the bulk data section using
the DMIG card or name list, with or without factors.

Example
K2GG=KAAX
K2GG=1.25*KAAX,1.5*KBBX

Comments

1. DMIG matrices will not be used unless selected in the Subcase Information section.

2. The matrix selected applies to all subcases.

3. The matrix must be symmetric, that is field 4 on the referenced DMIG entry must contain
the integer 6.

4. When multiple instances of this card occur, the referenced DMIG entries are combined.
This behavior differs from that of Nastran, which only recognizes the last instance of this
card in the same situation.

5. The entries in the name list are separated by comma or blank. With factors, each entry
consists of a factor followed by a star and a name. The factors are real numbers.

Altair Engineering OptiStruct 13.0 Reference Guide 261

Proprietary Information of Altair Engineering


K2PP

Subcase Information Entry

K2PP - Direct Input Stiffness Matrix Selection

Description

The K2PP command can be used in the Subcase Information section to select a direct input
stiffness matrix, which is not included in normal modes.

Format
K2PP = name

Argument Description

name Name of a stiffness matrix that is input in the bulk data section using
the DMIG card.

Comments

1. DMIG matrices will not be used unless selected in the Subcase Information section.

2. The matrix selected applies to all subcases.

3. K2PP matrices are used only in dynamic response problems. They are not used in normal
modes.

4. When multiple instances of this card occur, the referenced DMIG entries are combined.
This behavior differs from that of Nastran, which only recognizes the last instance of this
card in the same situation.

262 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


K42GG

Subcase Information Entry

K42GG - Direct Input Structural Element Damping Matrix Selection

Description

The K42GG command can be used in the Subcase Information section to select a direct input
structural element damping matrix.

Format
K42GG = name

Argument Description

name Name of a damping matrix that is input in the bulk data section using the
DMIG card.

Comments

1. DMIG matrices will not be used unless selected.

2. This matrix is handled like the contributions from the structural element damping
coefficients GE on MATi, PBUSH, and PELAS.

3. Terms are added to the damping matrix before any constraints are applied.

4. The matrix must be symmetric, that is field 4 on the referenced DMIG entry must contain
the integer 6.

5. When multiple instances of this card occur, the referenced DMIG entries are combined.
This behavior differs from that of Nastran, which only recognizes the last instance of this
card in the same situation.

Altair Engineering OptiStruct 13.0 Reference Guide 263

Proprietary Information of Altair Engineering


LABEL

Subcase Information Entry

LABEL - Subcase Label

Description

The LABEL command can be used in the Subcase Information section to provide a subcase
with a label.

Format
LABEL = name

Argument Description

name Any string of ASCII characters can be used to label a subcase.

Comments

1. This label is inserted into output files for post-processing purposes.

264 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


LOAD

Subcase Information Entry

LOAD – Data Selection

Description

The LOAD command can be used in the Subcase Information section to select a static load set
to be applied in linear static solutions.

Format
LOAD = option

Argument Options Description

option < SID > SID: Set identification of a LOAD bulk data entry or,
if no LOAD bulk data entry exists with this SID,
No default the set identification of FORCE, FORCE1,
MOMENT, MOMENT1, PLOAD, PLOAD1, PLOAD2,
PLOAD4, GRAV, RFORCE, and SPCD, bulk data
entries.

Comments

1. Only one LOAD entry can be present for each subcase.

2. A METHOD entry cannot be present in the same subcase definition as a LOAD entry.

3. If the SID referenced by the LOAD subcase information entry matches with the SID
defined for a LOAD bulk data entry, the information on this entry alone is selected.
However, if no LOAD bulk data entry has the referenced SID defined, any of the static
load entries: FORCE, FORCE1, MOMENT, MOMENT1, PLOAD, PLOAD1, PLOAD2, PLOAD4,
GRAV, RFORCE, and SPCD, which have this SID will be selected.

4. In versions of OptiStruct prior to 8.0, thermal loads were selected in the Subcase
Information section using the LOAD data selector. In version 8.0, the TEMPERATURE data
selector was added to perform this function. It is possible to revert to the old behavior
mode by setting the LOADTEMP option to SHAREID in the OptiStruct Configuration File.

Altair Engineering OptiStruct 13.0 Reference Guide 265

Proprietary Information of Altair Engineering


M2GG

Subcase Information Entry

M2GG - Direct Input Mass Matrix Selection

Description

The M2GG command can be used in the Subcase Information section to select a direct input
mass matrix.

Format
M2GG = name

Argument Description

name Name of a mass matrix that is input in the bulk data section using the
DMIG card.

Comments

1. DMIG matrices will not be used unless selected in the Subcase Information section.

2. The matrix selected applies to all subcases.

3. The matrix must be symmetric, that is field 4 on the referenced DMIG entry must contain
the integer 6.

4. By default, mass contribution of the external mass matrix (M2GG) is considered for the
generation of gravity and centrifugal loads.

5. When multiple instances of this card occur, the referenced DMIG entries are combined.
This behavior differs from that of Nastran, which only recognizes the last instance of this
card in the same situation.

266 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MBSIM

Subcase Information Entry

MBSIM – Multi-Body Simulation Selection

Description

The MBSIM command can be used in the Subcase Information section to select a multi-body
simulation definition to be applied in a multi-body problem.

Format
MBSIM = option

Argument Option Description

option < SID > SID: Set identification of MBSEQ, MBSIM, or MBLIN bulk
data entries.
No default

Comments

1. Only one MBSIM entry can be present for each subcase.

2. This subcase information entry is only valid when it appears in a multi-body subcase.

3. MBSIM can be used to select only one bulk data entry. MBSEQ, MBSIM, and MBLIN must
have unique IDs.

Altair Engineering OptiStruct 13.0 Reference Guide 267

Proprietary Information of Altair Engineering


METHOD

Subcase Information Entry

METHOD - Data Selection

Description

The METHOD command can be used in the Subcase Information section to select a method for
real eigenvalue extraction.

Format
METHOD (type) = option

Argument Options Description

type <STRUCTURE, The referenced EIGRL or EIGRA bulk data entry is applied
FLUID> to the structural (STRUCTURE) or fluid (FLUID) portion of
the model.
Default =
Structure

option < SID > SID: Set identification of an EIGRL or EIGRA bulk data
entry.
No default

Comments

1. Only one METHOD entry of each type can be defined for each subcase.

If only one type of METHOD entry is defined (either METHOD(STRUCTURE) or


METHOD(FLUID)), this definition will be used for both the structure and the fluid portion of
the model.

2. A METHOD entry cannot be present in the same subcase definition as a LOAD entry.

3. A METHOD entry is required for normal modes, linear buckling, modal frequency response,
and modal transient response solution sequences.

4. If present above the first subcase, it is used in all subsequent subcases which can accept
a METHOD entry. However, this does not apply to subcases which already contain their
own METHOD entry.

5. AMSES can be used for the fluid (FLUID) part of the model. METHOD(FLUID) can reference
an EIGRA bulk data entry.

268 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MFLUID

Subcase Information Entry

MFLUID - Virtual Fluid Mass Selection

Description

The MFLUID command can be used in the Subcase Information section to select the
parameters and damp elements and activate the calculation of virtual fluid mass.

Format
MFLUID = option

Argument Options Description

option < SID > SID: Set identification number of one or more MFLUID
bulk data entries.
No default

Comments

1. Only one MFLUID entry can be present.

2. MFLUID may be requested for a normal modes, complex eigenvalue, frequency response,
or transient response analysis.

Altair Engineering OptiStruct 13.0 Reference Guide 269

Proprietary Information of Altair Engineering


MINMAX or MAXMIN

Subcase Information Entry

MINMAX / MAXMIN - Objective Selection

Description

The MINMAX or MAXMIN commands can be used in the Subcase Information section to select
normalized response or system identification definitions as the objective function for a
"Minmax" or "Maxmin" optimization.

Format
MINMAX = integer
MAXMIN = integer

Argument Options Description

integer < DOID > DOID: Design objective identification number of a


DOBJREF or DSYSID bulk data entry.
No default

Comments

1. Multiple MINMAX entries are allowed and multiple MAXMIN entries are allowed, but a MAXMIN
entry cannot appear in the same input file as a MINMAX entry.

2. The multiple MINMAX or MAXMIN entries define the same optimization problem.

3. Refer to the Optimization Problem page of the User's Guide for more information on
"Minmax" optimization.

4. If the DSYSID entry is referenced by a MINMAX or a MAXMIN subcase entry, the beta
method is applied in the optimization as follows:

5. This entry is represented as an optimization objective in HyperMesh.

270 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MLOAD

Subcase Information Entry

MLOAD – Multi-Body Load Selection

Description

The MLOAD command can be used in the Subcase Information section to select a multi-body
load set to be applied in a multi-body problem.

Format
MLOAD = option

Argument Option Description

option < SID > SID: Set identification of GRAV, MBFRC, MBFRCC,
MBFRCE, MBMNT, MBMNTC, MBMNTE, MBSFRC,
No default MBSFRCC, MBSFRCE, MBSMNT, MBSMNTC,
MBSMNTE, and MLOAD bulk data entries.

Comments

1. Only one MLOAD entry can be present for each subcase.

2. This subcase information entry is only valid when it appears in a multi-body subcase.

3. If the SID referenced by the MLOAD subcase information entry matches with the SID
defined for an MLOAD bulk data entry, the information on this entry alone is selected.
However, if no MLOAD bulk data entry has the referenced SID defined, any of the multi-
body load entries: GRAV, MBFRC, MBFCC, MBFRCE, MBMNT, MBMNTC, MBMNTE, MBSFRC,
MBSFRCC, MBSFRCE, MBSMNT, MBSMNTC, or MBSMNTE which have this SID will be
selected.

Altair Engineering OptiStruct 13.0 Reference Guide 271

Proprietary Information of Altair Engineering


MODESELECT

I/O Options and Subcase Information Entry

MODESELECT – Mode Selection

Description

The MODESELECT command can be used in the I/O Options or the Subcase Information section
to select a subset of computed modes in modal dynamic analysis subcases.

Format
MODESELECT (type) = n

Mode selection based on arbitrary mode numbers.

Alternate Format 1
MODESELECT (type, LMODES = lm)

Mode selection based on lowest modes.

Alternate Format 2
MODESELECT (type, LMODENM = lom, HMODENM = him)

Mode selection based on a range of mode numbers.

Alternate Format 3
MODESELECT (type, LFREQ = lof, HFREQ = hif, UNCONSET = m)

Mode selection based on a range of frequencies.

Argument Options Description

type STRUCTURE If STRUCTURE is specified, the MODESELECT command


references modes associated with structural analysis only.
(Default)

FLUID If FLUID is specified, the MODESELECT command references


modes associated with fluid analysis only.

n n > 0 Set identification number n of a set of mode numbers. The


modes corresponding to the mode numbers specified in set n
(Integer)
will be included in the analysis. If no such set exists, then
mode n will be included in the analysis.

n < 0 Set identification number |n| of a set of mode numbers. The


modes corresponding to the mode numbers specified in set |
(Integer)
n| will be excluded from the analysis. If no such set exists,

272 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

then mode |n| will be excluded from the analysis.

LMODES lm Specifies the number of lowest modes to be selected.

(Integer > 0)

LMODENM lom Specifies the lower bound of the mode number range for
selecting modes (See comment 3).
(Integer > 0)

HMODENM him Specifies the upper bound of the mode number range for
selecting modes (See comment 3).
(Integer > lom
> 0)

LFREQ lof Specifies the lower bound of the frequency range for
selecting modes (See comment 4).
(Real > 0.0)

HFREQ hif Specifies the upper bound of the frequency range for
selecting modes (See comment 4).
(Real > lof >
0.0)

UNCONSET UNCONSET This flag indicates that the following fields specify a single
mode or a set of modes for unconditional inclusion or
exclusion.

m m > 0 Set identification number m of a set of mode numbers. The


modes corresponding to the mode numbers specified in set m
(Integer)
will be unconditionally included in the analysis. If no such set
exists, then mode m will be unconditionally included in the
analysis.

m < 0 Set identification number |m| of a set of mode numbers. The


modes corresponding to the mode numbers specified in set |
(Integer)
m| will be unconditionally excluded from the analysis. If no
such set exists, then mode |m| will be unconditionally
excluded from the analysis.

Comments

1. The MODESELECT I/O Options entry is only supported in modal frequency response, modal
transient and complex eignenvalue analyses. It is not supported in Response Spectrum
Analysis.

2. Multiple MODESELECT entries are allowed in a model. MODESELECT entries can be specified
above the first subcase or within each subcase.

Altair Engineering OptiStruct 13.0 Reference Guide 273

Proprietary Information of Altair Engineering


3. If LMODENM is specified without HMODENM, a default value of 10000000 (ten million) is
assumed for HMODENM. If HMODENM is specified without LMODENM, a default value of 1 is
assumed for LMODENM.

LMODENM HMODENM
Defaults specified 1.0E+7
1 specified

4. If LFREQ is specified without HFREQ, a default value of 1.0E+30 is assumed for HFREQ. If
HFREQ is specified without LFREQ, a default value of 0.0 is assumed for LFREQ.

LFREQ HFREQ
Defaults specified 1.0E+30
0.0 specified

5. When the MODESELECT Case Control command is used in conjunction with the parameter
LFREQ, the MODESELECT Case Control takes precedence.

6. If the use of MODESELECT results in all or none of the computed modes for use, you are
informed with a message.

7. The faster method for modal frequency response analysis (activated by


PARAM,FASTFR,YES) cannot be used in conjunction with MODESELECT.

8. Modes that are eliminated by MODESELECT will display:

a) an “S” next to the mode number, if the mode is eliminated by MODESELECT in one
subcase and PARAM, LFREQ or PARAM, HFREQ in another subcase, or

b) an “M” next to the mode number, if eliminated by MODESELECT in at least one


subcase.

274 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MODEWEIGHT

Subcase Information Entry

MODEWEIGHT - Optimization Parameter

Description

The MODEWEIGHT command can be used in the Subcase Information section to define a
multiplier for computed eigenvalues that are to be used in the calculation of the "weighted
reciprocal eigenvalue" and "combined compliance index" optimization responses.

Format
MODEWEIGHT (mode) = weight

Argument Description

mode Mode number.

No default (0 < Integer < highest calculated mode)

weight The multiplier to be used for the corresponding mode in the calculation of
"weighted reciprocal eigenvalue" or "combined compliance index."

Default = 1.0 (Real)

Comments

1. OptiStruct will terminate with an error if no mode number is provided.

2. Modes for which there is no MODEWEIGHT definition are not included in the calculation of
the "weighted reciprocal eigenvalue" and "combined compliance index" optimization
responses.

3. Refer to the Responses page of the User's Guide for more information on "weighted
reciprocal eigenvalue" and "combined compliance index" optimization response
calculations.

4. MODEWEIGHT is only used in conjunction with DRESP1, RTYPE = WFREQ, COMB.

5. If there is no MODEWEIGHT defined, but a DRESP1 with RTYPE = WCOMP exists, the
following default is applied:

MODEWEIGHT (1) = 1.0 in most cases for topology optimization.

MODEWEIGHT (7) = 1.0 if no SPC is defined for the subcase, EIGRL does not define a V1
> 0.0, and it is solving for more than 6 modes or all modes below an upper bound.
6. This entry is represented as an optimization response in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 275

Proprietary Information of Altair Engineering


MODTRAK

Subcase Information Entry

MODTRAK – Controls Mode Tracking

Description

The MODTRAK command can be used in the Subcase Information section to control mode
tracking.

Format

MODTRAK = option

Argument Options Description

option <ON, OFF, blank> ON or blank: Mode tracking is active.

Default = OFF
OFF: Mode tracking is not active.

Comments

1. MODTRAK entry is only valid for normal modes subcases.

2. If a MODTRAK entry is present in the input, then PARAM, MODETRAK is ignored.

3. Positive integers are accepted as option, and are interpreted as ON.

4. Negative integers or 0 are not accepted as option and will result in an error termination.

276 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MOTION

Subcase Information Entry

MOTION – Multi-Body Motion Selection

Description

The MOTION command can be used in the Subcase Information section to select a multi-body
motion set to be applied in a multi-body problem.

Format
MOTION = option

Argument Option Description

option < SID > SID: Set identification of MOTION, MOTNG, MOTNGC,
MOTNGE, MOTNJ, MOTNJC, and MOTNJE bulk data
No default entries.

Comments

1. Only one MOTION entry can be present for each subcase.

2. This subcase information entry is only valid when it appears in a multi-body subcase.

3. If the SID referenced by the MOTION subcase information entry matches with the SID
defined for a MOTION bulk data entry, the information on this entry alone is selected.
However, if no MOTION bulk data entry has the referenced SID defined, any of the multi-
body motion entries: MOTNG, MOTNGC, MOTNGE, MOTNJ, MOTHJC, or MOTIONJE which have
this SID will be selected.

Altair Engineering OptiStruct 13.0 Reference Guide 277

Proprietary Information of Altair Engineering


MPC

Subcase Information Entry

MPC - Data Selection

Description

The MPC command can be used in the Subcase Information section to select a multi-point
constraint set.

Format
MPC = option

Argument Options Description

option < SID > SID: Set identification of a MPCADD bulk data entry or, if
no MPCADD bulk data entry exists with this SID, the
No default set identification of an MPC bulk data entry.

Comments

1. Only one MPC entry can be present for each subcase.

2. If the SID referenced by the MPC subcase information entry matches with the SID defined
for a MPCADD bulk data entry, then the information on this entry alone is selected.
However, if no MPCADD bulk data entry has the referenced SID defined, then any MPC bulk
data entries that have this SID defined will be selected.

3. If present above the first subcase, it is the default for each subcase without an MPC
command, with the exception of linear buckling analysis subcases. Linear buckling
analysis subcases inherit the MPC information from the referenced static subcase.

4. MPC may be set to 0 to override the default in subcases where no MPC is required.

278 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


NLOAD

Subcase Information Entry

NLOAD - Data Selection

Description

The NLOAD command can be used in the Subcase Information section to select a time
dependent load to be applied in geometric nonlinear analysis problem.

Format
NLOAD = option

Argument Options Description

option < SID > SID: Set identification of an NLOAD or NLOAD1 bulk data
entry.
No default

Comments

1. NLOAD can only be used in subcases that contain an ANALYSIS = NLGEOM entry.

Altair Engineering OptiStruct 13.0 Reference Guide 279

Proprietary Information of Altair Engineering


NLPARM

Subcase Information Entry

NLPARM - Data Selection

Description

The NLPARM command can be used in the Subcase Information section to activate nonlinear
solution methods for this subcase and to select the parameters used for nonlinear quasi-static
analysis and geometric nonlinear implicit analysis.

Format
NLPARM = option

Argument Option Description

option < SID > SID: Set identification of an NLPARM bulk data entry.

No default

Comments

1. NLPARM bulk data entries will not be used unless selected in the Subcase Information
section.

2. If present above the first subcase, it is applied to all linear static subcases. Nonlinear
quasi-static analysis subcases, by their definition, will already have an NLPARM reference
which is used.

3. The NLPARM command is supported in quasi-static analysis, geometric nonlinear analysis,


and optimization subcases.

280 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


NONLINEAR

Subcase Information Entry

NONLINEAR - Data Selection

Description

The NONLINEAR command can be used in the Subcase Information section to select a
nonlinear dynamic load set for direct transient analyses.

Format
NONLINEAR = option

Argument Option Description

option < SID > SID: Set identification of NOLIN1, NOLIN2, NOLIN3,
NOLIN4 or NLRGAP bulk data entries.
No default

Comments

1. NONLINEAR is only allowed in direct transient analysis subcases.

Altair Engineering OptiStruct 13.0 Reference Guide 281

Proprietary Information of Altair Engineering


NORM

Subcase Information Entry

NORM - Optimization Parameter

Description

The NORM command can be used in the Subcase Information section to define a normalization
factor used in the computation of the "combined compliance index" optimization response.

Format
NORM = option

Argument Description

option Normalization factor.

Default = OptiStruct determines a weighting factor based on the lowest


eigenvalue and highest compliance of the initial iteration step. (Real)

Comments

1. Refer to the Responses page of the User's Guide for more information on the "combined
compliance index" optimization response calculation.

282 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


NSM

Subcase Information Entry

NSM – Data Selection

Description

The NSM command can be used in the Subcase Information section to select a non-structural
mass set for mass generation. The selector command must appear before the first SUBCASE
statement.

Format
NSM = option

Argument Option Description

option < SID > SID: Set identification number of a NSMADD bulk data
entry or, if no NSMADD bulk data entry exists with
No default this SID, the set identification of NSM, NSM1,
NSML and NSML1 bulk data entries.

Comments

1. Only one NSM subcase information entry can be present in the model.

2. This subcase information entry must appear before the first SUBCASE statement.

Altair Engineering OptiStruct 13.0 Reference Guide 283

Proprietary Information of Altair Engineering


P2G

Subcase Information Entry

P2G – Direct Input Load Matrix Selection

Description

The P2G command is used before the first subcase to select a direct input load matrix.

Format

P2G = name

Examples
P2G = PAX

P2G = PAX + 2*PAY

Argument Description

name Name of a load matrix that is input in the bulk data section using the
DMIG card.

Comments

1. Terms are added to the load matrix before any constraints are applied.

2. The DMIG matrix must be rectangular (columnar), that is field 4 on the referenced DMIG
entry must contain the integer 9.

3. A scale factor may be applied to this input using the CP2 parameter (See PARAM bulk data
entry).

4. By default, gravity and centrifugal loads are not generated based on the external mass
matrix (M2GG). In this case, gravity and centrifugal loads should be included in generating
the reduced loads in the DMIG.

5. When multiple instances of this card occur, the referenced DMIG entries are combined.
This behavior differs from that of Nastran, which only recognizes the last instance of this
card in the same situation.

6. The P2G statement must be above the first SUBCASE.

7. If the DMIG data referenced by the P2G statement has multiple load columns, then they
are applied in order in the linear and nonlinear static structural analysis subcases. If
there are more static subcases than columns, then only the subcases up to the number
of columns will get loads. If there are more columns than static subcases, then the
number of columns used with be the number of static subcases. For example, if the DMIG
has two columns and there are three static subcases, only the first two subcases will get

284 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


loads. If the DMIG has two columns and there is just one static subcase, then only the
first column is used.

8. For more control, to add a single DMIG load to one of multiple static subcases, use
P2GSUB.

Altair Engineering OptiStruct 13.0 Reference Guide 285

Proprietary Information of Altair Engineering


P2GSUB

Subcase Information Entry

P2GSUB – Direct Input Load Matrix Selection

Description

The P2GSUB command is used in a specific subcase to select a direct input load matrix.

Format

P2GSUB = factor*name (column index)

Examples
P2GSUB = PAX

P2GSUB = PAY(2)

P2GSUB = 2.5*PAZ(3)

Argument Description

factor Optional scale factor

<Real>

Default = 1.0

name Name of a load matrix that is input in the bulk data section using the
DMIG card.

column index Optional column index value

<Integer > 0>

Default = 1

Comments

1. Terms are added to the load matrix before any constraints are applied.

2. The DMIG matrix must be rectangular (columnar), that is field 4 on the referenced DMIG
entry must contain the integer 9.

3. A scale factor may be applied to this input using the CP2 parameter (see PARAM bulk data
entry).

4. By default, gravity and centrifugal loads are not generated based on the external mass
matrix (M2GG). In this case, gravity and centrifugal loads should be included in generating
the reduced loads in the DMIG.

286 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


5. Only one name may be specified on each P2GSUB entry. Multiple P2GSUB entries may be
used inside a single subcase section to combine multiple DMIG entries (or to combine
multiple columns from the same DMIG).

6. The P2GSUB statement cannot be specified above the first SUBCASE.

Altair Engineering OptiStruct 13.0 Reference Guide 287

Proprietary Information of Altair Engineering


PEAKOUT

Subcase Information Entry

PEAKOUT – Data Selection

Description

The PEAKOUT command can be used in the Subcase Information section to select the criteria
for automatic identification of loading frequencies at which result peaks occur. Other result
output may then be requested at these “peak” loading frequencies. This data selector is for
frequency response solution sequences only.

Format

PEAKOUT = option

Argument Option Description

option < SID > SID: Set identification of a PEAKOUT bulk data entry.

No default

Comments

1. Only one PEAKOUT entry can be defined for each subcase.

2. If present above the first subcase, it is applied to all subcases which can accept it but do
not contain a PEAKOUT card.

3. Other result output may be obtained at the peak loading frequencies by using the PEAK
keyword in the option field. Currently, support is only available for PFMODE, PFPANEL,
and PFGRID.

4. OFREQ is ignored when PEAKOUT is used.

288 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PRETENSION

Subcase Information Entry

PRETENSION – Data Selection

Description

The PRETENSION command can be used in the Subcase Information section to select and
activate a pretensioning bolt load.

Format
PRETENSION = option

Argument Option Description

option < PSID > Pretensioning load set identification of a PTADD bulk
data entry or, if no PTADD bulk data entry exists with
this PSID, the set identification of PTFORCE, PTFORC1,
PTADJST and PTADJS1 bulk data entry.

Comments

1. Only one PRETENSION entry can be defined for each subcase.

2. Combinations of PRETENSION and STATSUB(PRETENS) can be used to create more complex


pretensioning sequences.

3. The rules for sequencing pretensioning subcases on the same pretension section are as
follows:

a) Pretensioning force (PTFORCE) can only be activated in the new or “fresh”


pretensioning subcase for a given section. In other words, a subcase with PRETENSION
pointing to PTFORCE cannot also include STATSUB(PRETENS) referencing a subcase that
had already pretensioned this section.
b) Pretensioning adjustment (PTADJST) may be activated in any of the pretensioning
subcases for a given section. The effect of adjustment is cumulative relative to the
pretensioning status reached in the respective previous subcase, as referenced by
STATSUB(PRETENS).

Altair Engineering OptiStruct 13.0 Reference Guide 289

Proprietary Information of Altair Engineering


RANDOM

Subcase Information Entry

RANDOM – Random Analysis Set Selection

Description

Selects the RANDPS and RANDT1 bulk data entries to be used in random analysis.

Format

RANDOM = n

Example
RANDOM = 177

Argument Option Description

n (Integer > 0) Set identification of RANDPS and RANDT1 bulk data


entries to be used in random analysis.

Comments

1. This command must select RANDPS bulk data entries in order to perform random analysis.

2. Multiple RANDOM data can exist in the Subcase Information section.

3. This data can be placed anywhere in the Subcase Information section. It is not SUBCASE
specific.

290 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


REPGLB

Subcase Information Entry

REPGLB – Selection of Response to be Reported without being Constrained.

Description

The REPGLB command can be used in the Subcase Information section, before the first
subcase statement, to select a report set that is not subcase dependent.

Format

REPGLB = integer

Argument Options Description

integer < DRID > DRID: Set identification of a DREPORT or DREPADD bulk
data entry.
No default

Comments

1. The response referenced by the REPGLB selection must not be subcase dependent.

Altair Engineering OptiStruct 13.0 Reference Guide 291

Proprietary Information of Altair Engineering


REPSUB

Subcase Information Entry

REPSUB – Selection of Response to be Reported without being Constrained

Description

The REPSUB command can be used in the Subcase Information section, within a subcase
definition, to select a report set that is subcase dependent.

Format

REPSUB = integer

Argument Options Description

integer < DRID > DRID: Set identification of a DREPORT or DREPADD bulk
data entry.
No default

Comments

1. The response referenced by the REPSUB selection must be subcase dependent.

292 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


RESVEC

Subcase Information Entry

RESVEC – Controls Residual Vector Calculation

Description

The RESVEC command can be used in the Subcase Information section to control the
calculation of residual vectors.

Format
RESVEC(type, damping) = option

Argument Options Description

type <UNITLOD, UNITLOD: Generates residual vectors based on unit


APPLOD> loads at the dynamic loading's degrees of
freedom. A unit load residual vector is
Default = created for every loaded DOF from all
UNITLOD SUBCASEs. For normal modes and modal
complex eigenvalue analysis, a residual
vector is created for each USET and USET1
U6 DOF.

APPLOD: Generates residual vectors based on the


dynamic loading of the modal frequency
response analysis at zero Hz.and transient
analysis at time = zero. For frequency
response analysis, one or two residual
vectors are generated for each SUBCASE
based on whether the real and imaginary
loads are different at zero Hz. A single
residual vector is created for each
transient SUBCASE. The values at each
loaded DOF correspond to the load on that
DOF at zero Hz. or time = zero. APPLOD is
not valid for normal modes analysis and
UNITLOD will always be used.

damping <DAMPLOD, DAMPLOD: Generates a viscous damping residual


NODAMP> vector for each viscous element based on
the eigenvector of the viscous element.
Default =
DAMPLOD

Altair Engineering OptiStruct 13.0 Reference Guide 293

Proprietary Information of Altair Engineering


Argument Options Description

NODAMP: Turns off the generation of the viscous


damping residual vectors.

option <YES, NO> YES: Residual vectors are calculated.

See comments
NO: Residual vectors are not calculated.
for default.

Comments

1. RESVEC can be requested for normal modes, modal complex eigenvalue analysis, modal
frequency response, and modal transient response analysis subcases.

2. If the RESVEC does not exist in a subcase (and is not defined above the first subcase),
then the default is YES for modal frequency response and transient response analysis
subcases, and the default is NO for all other applicable subcases. If a RESVEC card exists
without the YES/NO option, the default is YES.

3. If EXCITEID=SPCD is defined on RLOAD1/RLOAD2 or TLOAD1/TLOAD2, unit residual vectors


for each enforced motion DOF are always computed, even if RESVEC=NO.

4. For normal modes analysis, the unit load method (type=UNITLOD) is applied to the
degrees-of-freedom defined by USET and USET1 U6 entities. If the Lanczos eigensolver is
used then RESVEC=YES must be present. If the AMSES or AMLS eigensolver is used, then
the USET and USET1 U6 residual vectors will always be calculated (even if RESVEC=NO is
specified).

5. Even though DAMPLOD and NODAMP may be defined inside each subcase, the setting from
the last RESVEC data will be used for all of the modal complex eigenvalue analysis, modal
frequency response, and modal transient subcases in the model.

6. Residual vectors from USET and USET1 U6 data are only available for modal complex
eigenvalue analysis when AMSES or AMLS is used to calculate the normal modes. They
are not created if Lanczos is used.

7. For modal frequency response and modal transient analysis, the USET and USET1 U6
residual vectors will always be calculated if the AMSES or AMLS eigensolver is used, and
they will never be calculated if the Lanczos eigensolver is used. The RESVEC command
has no effect on the USET and USET1 U6 residual vector creation for modal frequency
response and modal transient analysis.

294 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


RGYRO

Subcase Information Entry

RGYRO – This data entry can be used in the subcase information section to activate
gyroscopic effects in Rotor dynamics

Description

Identifies a RGYRO bulk data entry that contains information required to implement Rotor
dynamics in Modal Complex Eigenvalue Analysis and/or Modal Frequency Response Analysis.

Format
RGYRO = option

Example
RGYRO = 3

RGYRO = NO

Argument Option Description

option <SID,NO> SID: Identification number of a RGYRO bulk data entry.

(Integer)

NO: Gyroscopic effects are not included in any solution


sequences.

Comments

1. Multiple RGYRO subcase information entries are allowed in different subcases, however,
only one RGYRO subcase entry can exist within each subcase.

Altair Engineering OptiStruct 13.0 Reference Guide 295

Proprietary Information of Altair Engineering


RSPEC

Subcase Information Entry

RSPEC – Data Selection

Description

The RSPEC command can be used in the Subcase Information section to reference combination
rules, excitation degrees of freedom, and input spectra for use in response spectrum analysis.

Format

RSPEC = option

Argument Options Description

option < SID > SID: Set identification of an RSPEC bulk data entry.

No default

Comments

1. Only valid in a response spectrum analysis subcase.

2. Refer to the Response Spectrum Analysis section of the User’s Guide for more details.

296 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


RWALL

Subcase Information Entry

RWALL – Data Selection

Description

The RWALL command can be used in the Subcase Information section to select rigid walls for
geometric nonlinear analysis.

Format
RWALL = option

Argument Option Description

option < SID > SID: Set identification of an RWALADD bulk data entry
or, if no RWALADD bulk data entry exists with this
No default SID, the set identification of RWALL bulk data
entries.

Comments

1. Only one RWALL entry can be present for each subcase. It can only be used in subcases
that contain an ANALYSIS = NLGEOM entry.

2. If the SID referenced by the RWALL subcase information entry matches with the SID
defined for an RWALADD bulk data entry, then the information on this entry alone is
selected. However, if no RWALADD bulk data entry has the referenced SID defined, then
any XHSIT bulk data entries that have this SID defined will be selected.

Altair Engineering OptiStruct 13.0 Reference Guide 297

Proprietary Information of Altair Engineering


SDAMPING

Subcase Information Entry

SDAMPING - Data Selection

Description

The SDAMPING command can be used in the Subcase Information section to apply modal
damping as a function of natural frequency in modal solutions.

Format
SDAMPING (type) = option

Argument Option Description

type < STRUCTURE, FLUID > The referenced bulk data entry is applied to the
Default = STRUCTURE structural (STRUCTURE) or fluid (FLUID) portion of
the model.

option < SID > SID: Set identification of a TABDMP1 bulk data
entry.
No default

Comments

1. SDAMPING can only be used in modal transient, modal frequency response and modal
complex eigenvalue analyses; and must reference a TABDMP1 bulk data entry.

2. Only one SDAMPING entry of each type can be defined for each subcase.

3. If only one type of SDAMPING entry is defined (either SDAMPING(STRUCTURE) or


SDAMPING(FLUID)), this definition will be used for both the structure and the fluid portion
of the model.

4. If present above the first subcase, it is applied to each modal frequency or modal
transient subcase without an SDAMPING entry.

5. To achieve identical displacements in Modal frequency response or Modal transient


analyses when the SDAMPING bulk data entry is used instead of PARAM, G, the steps
described here can be followed:

The TYPE field in the TABDMP1 bulk data entry should be set to CRIT. This TABDMP1 bulk
data entry is referenced by the SDAMPING subcase information entry.

Set the damping value (field gi) in the TABDMP1 bulk data entry equal to half of the
value of PARAM, G (that is set the constant value to C/C0).

Set PARAM, KDAMP,-1.

298 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SEINTPNT

Subcase Information Entry

SEINTPNT - Selection of Super Element Internal Point

Description

The SEINTPNT command can be used in the Subcase Information section to select a set of
interior DOF of super elements to be converted to exterior DOF.

Format
SEINTPNT = option

Example
SEINTPNT = 100

BEGIN BULK

SET,100,GRIDC,

+,10643,T1,10643,T2,10643,T3

GRID 10643 1 234 55 322

Argument Option Description

option <SID> SID refers to the ID of a bulk card SET of type GRIDC.

No default

Comments

1. SEINTPNT can be used when CMS super elements in .h3d files are present in residual runs.
After the conversion, these DOF are part of the analysis DOF and can be used as
connection points, load DOF, response DOF during optimization.

2. SEINTPNT is not supported for fluid grids.

3. GRID point information for interior grids (that are to be converted to exterior grids) should
be included in the GRID bulk data entry, which in turn should be included in the solver
deck if SEINTPNT is used.

Altair Engineering OptiStruct 13.0 Reference Guide 299

Proprietary Information of Altair Engineering


SOLVTYP

Subcase Information Entry

SOLVTYP - Solver Selection

Description

The SOLVTYP command can be used in the Subcase Information section to select the solver
for linear and nonlinear static subcases, nonlinear geometric implicit static subcase
(ANALYSIS=NLGEOM), and nonlinear geometric implicit dynamic subcase (ANALYSIS=IMPDYN).

Format
SOLVTYP = option

Argument Option Description

option < SID > SID: Set identification of an SOLVTYP bulk data entry.

Selects a SOLVTYP bulk data entry that is used to


define various settings for the solver, such as
different pre-conditioners and convergence criteria
for the solver.

Comments

1. Only one SOLVTYP entry can be defined for each linear and nonlinear static subcases or
nonlinear geometric implicit subcase.

2. If present above the first subcase, it is applied to all compatible linear and nonlinear
static subcases and nonlinear geometric implicit subcases. For more details on subcase
type and solver compatibility, refer to the SOLVTYP bulk data entry.

3. If SOLVTYP is present in a subcase, a solver, specified by the referenced SOLVTYP in the


bulk data, is used in the solution of linear and nonlinear static subcases and nonlinear
geometric implicit subcases. The option selects the SOLVTYP bulk data entry that can be
used to define alternate settings such as different pre-conditioners and convergence
criteria for the solver.

4. In optimization, if the responses DRESP1, RTYPE = DISP, LAMA, STESS, STRAIN,


CSTRESS, CSTRAIN, CFAILURE, or FORCE are present the solver is automatically reverted
to the direct solver.

5. The iterative solver is a preconditioned conjugate gradient solver. A Factored


Approximate Inverse Preconditioner is the default method. This solver is also SMP
parallelized.

6. The performance of the iterative solver depends on the conditioning of the stiffness
matrix. For compact solid models, the iterative solver may perform considerably better
than the direct solver in terms of memory usage and elapsed times for a single linear

300 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


static subcase. In the case of multiple linear static subcases, the iterative solver may
perform worse than the direct solver. The break-even point is at about 4-6 subcases.
The performance depends on model, hardware, operating system, and potentially the
system load.

Altair Engineering OptiStruct 13.0 Reference Guide 301

Proprietary Information of Altair Engineering


SPC

Subcase Information Entry

SPC - Data Selection

Description

The SPC command can be used in the Subcase Information section to select a single-point
constraint set.

Format
SPC = option

Argument Option Description

option < SID > SID: Set identification of an SPCADD bulk data entry or,
if no SPCADD bulk data entry exists with this SID,
No default the set identification of SPC or SPC1 bulk data
entries.

Comments

1. Only one SPC entry can be present for each subcase.

2. If the SID referenced by the SPC subcase information entry matches with the SID defined
for an SPCADD bulk data entry, then the information on this entry alone is selected.
However, if no SPCADD bulk data entry has the referenced SID defined, then any SPC or
SPC1 bulk data entries that have this SID defined will be selected.

3. If present above the first subcase, it is the default for each subcase without an SPC
command, with the exception of linear buckling analysis subcases. Linear buckling
analysis subcases inherit the SPC information from the referenced static subcase.

4. SPC may be set to 0 to override the default in subcases where no SPC is required.

5. SPC must be present for linear static solutions. The SID may be set to 0 to run linear
static solutions with no constraints.

302 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


STATSUB

Subcase Information Entry

STATSUB - Subcase Selection

Description

The STATSUB command can be used in the Subcase Information section to select a static
solution subcase.

Format
STATSUB(type) = option

Argument Option Description

type <BUCKLING, BUCKLING: Referenced static subcase is used in forming


PRELOAD, the geometric stiffness needed for the linear
PRETENS, buckling solution.
STRUCTURE>
PRELOAD: Referenced static subcase defines a preload.
Default =
BUCKLING
PRETENS: Referenced static subcase introduces
pretensioning loads on bolts. (See comment
4).

STRUCTURE: Referenced static subcase will determine the


CONTACT / GAP status for a heat transfer
analysis (See comment 6).

option < SID > SID: Subcase identification number of a static


solution subcase. (See comment 5).
No default

Comments

1. A METHOD entry to define the eigenvalue extraction method is required in addition to a


STATSUB entry for a linear buckling solution subcase.

2. A linear buckling solution cannot be performed on a linear static subcase that uses inertia
relief.

3. STATSUB(PRELOAD) is supported for linear static, normal modes, and direct frequency
response solution sequences.

4. STATSUB(PRETENS) is supported for linear and nonlinear static subcases. Other subcase
types can use STATSUB(PRELOAD), which refers to a pretension subcase, in order to
incorporate the effect of pretensioning on natural frequencies, dynamic solutions, and so

Altair Engineering OptiStruct 13.0 Reference Guide 303

Proprietary Information of Altair Engineering


on.

5. STATSUB(PRETENS) can only reference a subcase that precedes the current subcase in
the input deck.

6. STATSUB(STRUCTURE) is supported for both steady-state and transient heat transfer


solution sequences.

7. STATSUB(PRELOAD) can be used with the AMSES eigensolver.

304 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SUBCASE

Subcase Information Entry

SUBCASE - Subcase Selection

Description

The SUBCASE command can be used in the Subcase Information section to indicate the start
of a new subcase definition.

Format
SUBCASE = integer

Argument Description

integer Subcase identification number (SID)

No default (Integer > 0)

Comments

1. Each subcase must be declared with a separate SUBCASE header and a unique SID.

2. The SUBCASE header is not needed if there is just one subcase.

Altair Engineering OptiStruct 13.0 Reference Guide 305

Proprietary Information of Altair Engineering


SUBCOM

Subcase Information Entry

SUBCOM - Combination Subcase Delimiter

Description

Delimits and identifies a combination subcase.

Format

SUBCOM = n

Example
SUBCOM = 125

Argument Description

n Subcase identification number

(Integer > 2)

Comments

1. A SUBSEQ command must follow this command.

2. SUBCOM may only be used with STATIC subcases.

3. Output requests above the subcase level will be used.

4. If the referenced subcases contain thermal loads or element deformations, you must
define the temperature field in the SUBCOM with a TEMP(LOAD) command or the element
deformations with a DEFORM command.

5. If the reference subcases contain STATSUB(PRELOAD), then all of the referenced


subcases must contain the same STATSUB(PRELOAD); the same STATSUB(PRELOAD)
should also be used in the SUBCOM.

306 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SUBMODEL

Subcase Information Entry

SUBMODEL - Subcase-specific Model Selection

Description

The SUBMODEL entry can be used in the Subcase Information section to select a submodel as
a set of elements. Subcase entries specific to the selected element set can be used to solve
the submodel without affecting the rest of the structure.

Format
SUBMODEL, SID, SID_r

Argument Value Description

SID <integer>0> Specifies the SID of a SET of elements that defines the
submodel.

SID_R <integer>0>, <integer>0> Specifies the SID of a set of rigid


NONE, blank elements to be included with the
submodel.

NONE: The subcase containing this SUBMODEL


entry will skip all rigid elements in the
input deck.

blank: If SID_r is blank, the subcase containing


this SUBMODEL entry will include all rigid
elements defined in the input deck.

Comments

1. A SUBMODEL entry can only be defined within a subcase and cannot be specified above
the first subcase.

2. The SUBMODEL entry does not automatically apply the specific attributes (loads,
constraints and so on) to the defined submodel. It is your responsibility to specify
corresponding attributes that apply exclusively to the subcase-specific model defined via
SUBMODEL.

Altair Engineering OptiStruct 13.0 Reference Guide 307

Proprietary Information of Altair Engineering


SUBSEQ

Subcase Information Entry

SUBSEQ - Subcase Sequence Coefficients

Description

Gives the coefficients for forming a linear combination of the previous static subcases.

Format

SUBSEQ=R1 [, R2, R3, ..., Rn]

Example
SUBSEQ=1.0, -1.0, 0.0, 2.0

Argument Description

Ri Coefficients of the previously occurring static subcases.

(Real)

Comments

1. Can only appear after a SUBCOM command.

2. R1 to Rn refer to the immediately preceding statis subcases. Rn is applied to the most


recently appearing static subcase, R(n-1) is applied to the second most recently
appearing static subcase, and so on. The embedded comments ($) describe the following
example:
DISPL = ALL
SUBCASE 1
SUBCASE 2
SUBCOM 3
SUBSEQ = 1.0, -1.0 $ SUBCASE 1 - SUBCASE 2
SUBCASE 11
SUBCASE 12
SUBCOM 13
SUBSEQ = 0.0, 0.0, 1.0, -1.0 $ SUBCASE 11 - SUBCASE 12
or
SUBSEQ = 1.0, -1.0 $ EQUIVALENT TO PRECEDING COMMAND. USE ONLY ONE.

308 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SUPORT1

Subcase Information Entry

SUPORT1 - Data Selection

Description

The SUPORT1 command can be used in the Subcase Information section to select the fictitious
support set to be applied to the model.

Format
SUPORT1 = option

Argument Options Description

option < SID > SID: Set identification of a SUPORT1 bulk data entry.

No default

Comments

1. SUPORT1 entries will not be used unless selected in the Subcase Information section by
the SUPORT1 command.

2. SUPORT1 entries will be applied in all subcases.

Altair Engineering OptiStruct 13.0 Reference Guide 309

Proprietary Information of Altair Engineering


TEMPERATURE

Subcase Information Entry

TEMPERATURE – Temperature Set Selection

Description

Selects the temperature set to be used in either material property calculations or thermal
loading.

Format
TEMPERATURE (type) = option

Examples
TEMPERATURE(LOAD)=15
TEMP(MATERIAL)=7
TEMPERATURE=7

Argument Option Description

type <INITIAL, INITIAL: The selected temperature set will be used


MATERIAL, to determine initial temperature
LOAD, BOTH> distribution.

Default = BOTH MATERIAL: The selected temperature set will be used


to determine temperature-dependent
material properties indicated on the MATTi
bulk data entries.

In addition, the SUBCASE ID of a thermal


analysis SUBCASE can be specified. The
calculated temperature field is then used to
determine temperature-dependent material
properties indicated on the MATTi bulk data
entries.

LOAD: The selected temperature set will be used


to determine an equivalent static load.

BOTH: Both MATERIAL and LOAD will use the same


temperature set.

option < SID > SID: Set identification number of TEMP or TEMPD
bulk data entries.
No default

310 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. Only one of TEMPERATURE(MATERIAL) or TEMPERATURE (INITIAL) is allowed in any


problem and should be specified above the subcase level (although it will be accepted
inside the subcase).

2. TEMPERATURE(BOTH) and TEMPERATURE(LOAD) can be used before the subcase level or


inside the subcase. If used before the subcase level, it will apply to all subcases that do
not have their own TEMP(BOTH) or TEMP(LOAD) command.

3. If multiple temperature-dependent material requests are made (for example, by using


TEMP(MATERIAL) and TEMP(BOTH)), then the last request will be used to define material
properties.

4. The total load applied will be the sum of external (LOAD command), thermal (TEMP(LOAD)
command) and constrained displacement (SPC command) loads.

5. Static and thermal loads should have unique set identification numbers.

6. In linear static analysis, temperature strains are calculated with:

where, A(T0 ) is the thermal expansion coefficient defined on the MATi bulk data entries, T
is the load temperature defined with TEMPERATURE(LOAD), and T0 is the initial temperature
which is defined in one of the following ways:

If TEMPERATURE(INITIAL) and TREF (specified on the MATi or PCOMPi cards) are


specified, then the TEMPERATURE(INITIAL) set will be used as the initial temperature
to calculate both the thermal loads and the material properties.
If TEMPERATURE(MATERIAL) and TREF are specified, then TREF will be used as the initial
temperature in calculating the thermal load and the TEMPERATURE (MATERIAL) set will
be used for the calculation of the material properties.
If neither TEMPERATURE(MATERIAL) nor TEMPERATURE(INITIAL) are specified, TREF will
be used to calculate both the thermal load and the material properties.

If none of TEMPERATURE(INITIAL),TEMPERATURE(MATERIAL), and TEMPERATURE(BOTH)


is present, TREF will be used to calculate the load. The material properties will be
obtained from the MATi entry. The MATTi is not used in this case.
7. In versions of OptiStruct prior to 8.0, thermal loads were selected in the Subcase
Information section using the LOAD data selector. In version 8.0, the TEMPERATURE data
selector was added to perform this function. It is possible to revert to the old behavior
mode by setting the LOADTEMP option to SHAREID in the OptiStruct Configuration File.

8. TEMPERATURE(LOAD) or TEMPERATURE(MATERIAL) can point to a heat transfer subcase or


TSTRU ID. The temperature field from a steady state heat transfer analysis or at the final
time step of a transient heat transfer analysis will be used.

Altair Engineering OptiStruct 13.0 Reference Guide 311

Proprietary Information of Altair Engineering


TSTEP

Subcase Information Entry

TSTEP – Transient Time Step Set Selection

Description

The TSTEP command can be used in the Subcase Information section to select integration for
transient analysis.

Format
TSTEP (type) = option

Example
TSTEP = 731
TSTEP (FOURIER) = 755

Argument Option Description

type <TIME, FOURIER> TIME: The transient response is computed by


time step integration in the time domain.
Default = TIME
FOURIER: The transient response is computed in the
frequency domain using the Fourier
transform method.

option < SID > SID: Set identification number of a TSTEP bulk
data entry.
No default

Comments

1. A TSTEP entry must be selected to execute a transient analysis.

2. A TSTEP entry can also be used to execute a transient thermal analysis (only for
type=TIME or Default).

3. For the application of time-dependent loads in modal frequency response analysis, a


TSTEP bulk data entry must be selected by the TSTEP (FOURIER) command. The time-
dependent loads will be recomputed in the frequency domain by a Fourier transform.

312 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


TSTEPNL

Subcase Information Entry

TSTEPNL – Nonlinear Implicit Dynamics Time Step Set Selection

Description

The TSTEPNL command can be used in the Subcase Information section to select integration
and other parameters for nonlinear implicit dynamics analysis.

Format
TSTEPNL = option

Example
TSTEPNL = 731

Argument Option Description

option < SID > SID: Set identification number of a TSTEPNL


bulk data entry.
No default

Comments

1. A TSTEPNL entry must be selected to execute a nonlinear implicit dynamic analysis.

Altair Engineering OptiStruct 13.0 Reference Guide 313

Proprietary Information of Altair Engineering


TSTRU

Subcase Information Entry

TSTRU - Temperature Set ID for Structural Analysis

Description

The TSTRU command can be used in the Subcase Information section to assign a temperature
set identification number to the resulting nodal temperatures of a steady-state heat transfer
analysis or the last time step of a transient heat transfer analysis.

Format
TSTRU = option

Argument Option Description

option < SID > SID: This is a temperature set identification number.
It may be referenced from a static analysis
Default = Subcase ID subcase, in which case the resulting nodal
temperatures of a steady-state heat transfer
analysis or the last time step of a transient
heat transfer analysis are considered as applied
loads for the static analysis.

Comments

1. TSTRU is only valid in a heat transfer subcase.

2. If TSTRU does not explicitly appear in a heat transfer subcase, then the Subcase ID is
used as the default.

3. A temperature set from a heat transfer analysis will override any temperature set defined
by the bulk data entries TEMP or TEMPD.

314 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


WEIGHT

Subcase Information Entry

WEIGHT - Optimization Parameter

Description

The WEIGHT command can be used in the Subcase Information section to define a weighting
factor (multiplier) for the compliances of individual linear static solution subcases, which are
used in the calculation of the "weighted compliance" and "combined compliance index"
optimization responses.

Format
WEIGHT = value

Argument Description

value The multiplier to be used for the compliance of this subcase in the
calculation of "weighted compliance" or "combined compliance index."

Default = 1.0 (Real)

Comments

1. Refer to the Responses page of the User's Guide for more information on "weighted
compliance" and "combined compliance index" optimization response calculations.

2. WEIGHT is only used in conjunction with DRESP1, RTYPE = WCOMP, COMB.

3. If a WEIGHT is not defined in any subcase, but a DRESP1 with RTYPE = WCOMP or COMB
exists, all static subcases are assigned a WEIGHT of 1.0 by default.

4. This entry is represented as an optimization response in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 315

Proprietary Information of Altair Engineering


XHIST

Subcase Information Entry

XHIST – Data Selection

Description

The XHIST command can be used in the Subcase Information section to select time history
output for geometric nonlinear analysis.

Format
XHIST = option

Argument Option Description

option < SID > SID: Set identification of an XHISTADD bulk data entry
or, if no XHISTADD bulk data entry exists with this
No default SID, the set identification of XHIST bulk data
entries.

Comments

1. Only one XHIST entry can be present for each subcase. It can only be used in subcases
that contain an ANALYSIS = NLGEOM entry.

2. If the SID referenced by the XHIST subcase information entry matches with the SID
defined for an XHISTADD bulk data entry, then the information on this entry alone is
selected. However, if no XHISTADD bulk data entry has the referenced SID defined, then
any XHSIT bulk data entries that have this SID defined will be selected.

316 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


XSTEP

Subcase Information Entry

XSTEP – Explicit Analysis Parameter Selection

Description

The XSTEP command can be used in the Subcase Information section to activate the explicit
solution method for this subcase and to select the parameters used for explicit analysis.

Format
XSTEP = option

Argument Option Description

option < SID > SID: Set identification of an XSTEP bulk data entry.

No default

Comments

1. XSTEP bulk data entries will not be used unless selected in the Subcase Information
section.

2. The XSTEP command is supported in explicit analysis and optimization subcases.

Altair Engineering OptiStruct 13.0 Reference Guide 317

Proprietary Information of Altair Engineering


Bulk Data Section

318 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


ACCLR

Bulk Data Entry

ACCLR – Accelerometer for Geometric Nonlinear Analysis

Description

Defines accelerometer for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

AC C LR AID GID FC UT

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

AC C LR 100 34 100.0

Field Contents

AID Unique accelerometer identification number.

(Integer > 0)

GID Grid point identification number.

(Integer > 0)

FCUT Cutoff frequency.

(Real > 0)

Comments

1. The accelerometer option computes a filtered acceleration in the output system.

2. These filtered accelerations provided by an accelerometer are used in either a SENSOR or


in post-processing acceleration time history without aliasing problems.

3. A 4-pole Butterworth filter is used.

4. The recommended value for FCUT is 1650 Hz (1.65 ms-1) to obtain a class 1000 SAE
filtering.

Altair Engineering OptiStruct 13.0 Reference Guide 319

Proprietary Information of Altair Engineering


5. In addition to these filtered accelerations, the accelerometer also allows the output of
the integrals of X, Y, and Z of the raw accelerations projected to the output coordinate
system to time history. These quantities are not used by SENSOR.

6. Note that if the coordinates are moving, the integrals of X, Y, and Z raw accelerations
projected to the output coordinate system are not the same as the velocities projected
to the output coordinate system, as described in XHIST. Computation of these integrals
in a post-processor allows retrieving the accelerations projected to the output coordinate
system without aliasing problems. Integration and differentiation are acting like another
filter on top of the 4-pole Butterworth.

7. This card is unsupported in HyperMesh.

320 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


ACMODL

Bulk Data Entry

ACMODL – Fluid-Structure Interface Parameters

Description

Defines model parameters for the Fluid-Structure interface.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

AC MODL INTER INFOR FSET SSET NORMAL SKNEPS DSKNEPS

INTOL SRC HUNIT MAXSGRID

Field Contents

INTER Fluid-structure interface type.

Default = DIFF (IDENT or DIFF)

INFOR Defines whether grids or elements identified by FSET and SSET are to be
used to define the fluid-structure interface.

Default = GRID (GRID or ELEMENT)

FSET ID of a SET of fluid elements or grids to be considered for the interface.

Default = blank (Integer)

SSET ID of a SET of structural elements or grids to be considered for the interface

Default = blank (Integer)

NORMAL Fluid normal tolerance.

Default = 1.0 when INTER = DIFF;


Default = 0.001 when INTER = IDENT (Real)

SKNEPS Fluid skin growth tolerance (See comments 4 and 5).

Default = 0.5 (Real)

DSKNEPS Secondary fluid skin growth tolerance (See comments 4 and 5).

Altair Engineering OptiStruct 13.0 Reference Guide 321

Proprietary Information of Altair Engineering


Field Contents

Default = 1.5 * SKNEPS (Real)

INTOL Tolerance of inward normal.

Default = 0.5 (Real)

SRCHUNIT Search units. ABS for absolute model units or REL for relative model units
based on element size.

Default = REL (ABS or REL)

MAXSGRID The maximum number of structural grids that can be interfaced with one fluid
element face.

Default = 200 (Integer > 0)

Comments

1. ACMODL card is optional in the deck. If provided, only one ACMODL card is allowed.

2. For INTER=IDENT, the interface would be calculated based on a grid to grid match
between fluid and structural parts. For INTER=IDENT, INFOR must be GRID or blank. Each
grid specified on the FSET/SSET must be able to find a matching interface grid. If either
FSET or SSET is not provided, a searching algorithm would find the grids on the skin of
the surface.

3. For INTER=DIFF, if FSET/SSET is provided, the skin of the surface would be based on the
set. If either FSET or SSET is not provided, a searching algorithm would find the skin of
the surface. The searching algorithm for this case is based on the normal distance from
the fluid face. When INTER=DIFF, a grid to grid match is no longer a requirement.

4. The search box is described by several parameters:

322 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


The height of the searching box is based on the NORMAL parameter. If L is the
smallest edge of the fluid element face, the height of the search box would be NORMAL
x L.
SKNEPS represents the enlargement of the plane of the fluid surface used to define the
search box. The diagonal distance, D, from the center of the fluid surface to each
surface grid is pushed out by (1.0+SKNEPS) x D.
DSKNEPS represents a secondary enlargement of the plane of the fluid surface used to
define the search box if SKNEPS fails to find ANY structural elements. The diagonal
distance from the center of the fluid surface to each surface grid is pushed out by (1.0
+DSKNEPS) x D.

INTOL represents a normal direction into the fluid for the case when the fluid protrudes
past the structural interface. It is defined as INTOL x L, where L is the smallest edge
of the fluid element surface.
5. The value required in the secondary fluid skin growth tolerance (DSKNEPS) field must
always be greater than the value of the fluid growth tolerance (SKNEPS).

If the required value of DSKNEPS is less than SKNEPS, then an ERROR message will be
output and the run will be terminated.
If the DSKNEPS field is left blank, a default value equal to 1.5 * SKNEPS is assigned to
it.
6. This card is represented as a control card in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 323

Proprietary Information of Altair Engineering


ACSRCE

Bulk Data Entry

ACSRCE – Acoustic Source

Description

Defines acoustic source as a function of power vs. frequency.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

AC SRC E SID EXC ITEID DELAY DPHASE TP RHO B

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

AC SRC E 111 29 -0.2 87 14 1.0 15

Field Contents

SID Identification number of a dynamic load set.

No default (Integer > 0)

EXCITEID Identification number of an SLOAD entry set that defines A.

No default (Integer > 0)

DELAY Defines time delay . If it is a non-zero integer, it represents the


identification number of a DELAY bulk data entry that defines . If it is
real, then it directly defines the value of that will be used for all
degrees-of-freedom that are excited by this dynamic load entry.

Default = 0 (Integer > 0, or Real)

DPHASE Defines phase . If it is a non-zero integer, it represents the identification


number of a DPHASE bulk data entry that defines . If it is real, then it

324 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

directly defines the value of that will be used for all degrees-of-freedom
that are excited by this dynamic load entry.

Default = 0 (Integer > 0, or Real)

TP Set identification number of the TABLED1, TABLED2, TABLED3, or TABLED4


entry that gives P(f).

Default = 0 (Integer > 0)

RHO Fluid Density

No default (Real > 0.0)

B Bulk modulus of fluid.

No default (Real > 0.0)

Comments

1.

where,

2. Dynamic load sets must be selected in the I/O Options or Subcase Information sections
with the command DLOAD = SID.

3. SID must be unique with respect to other dynamic load sets, that is ACSRCE, DLOAD,
RLOAD1, RLOAD2, TLOAD1, and TLOAD2 entries.

4. The referenced EXCITEID, DELAY and DPHASE entries must specify fluid points only.

5. If either DELAY or DPHASE are blank or zero, the corresponding or will be zero.

Altair Engineering OptiStruct 13.0 Reference Guide 325

Proprietary Information of Altair Engineering


ASET

Bulk Data Entry

ASET – Boundary Degrees-of-Freedom of a Superelement Assembly

Description

Defines the boundary degrees-of-freedom of a superelement assembly for matrix reduction.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ASET G1 C1 G2 C2 G3 C3 G4 C4

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ASET 564 4 765 4561 8 5

Field Contents

Gi Grid or scalar point identification numbers.

No default (Integer > 0)

Ci Component numbers.

(Integer zero or blank for scalar points, or up to 6 unique digits (0 < integer
< 6) may be placed in the field with no embedded blanks for grid points.
The components refer to the coordinate system referenced by the grid
points.)

Comments

1. Refer to the User's Guide section on The Direct Matrix Approach for more information on
the use of this card.

2. A fatal error will be issued if the input contains ASET or ASET1, but PARAM, EXTOUT is
not given.

326 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).

4. This card is represented as a constraint load in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 327

Proprietary Information of Altair Engineering


ASET1

Bulk Data Entry

ASET1 – Boundary Degrees-of-Freedom of a Superelement Assembly, Alternate Form

Description

Defines the boundary degrees-of-freedom of a superelement assembly for matrix reduction.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ASET1 C G1 G2 G3 G4 G5 G6 G7

G8 G9 G10 -etc.-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ASET1 123 34 88 4 12 19 7 70

1234 65

Alternate Format and Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ASET1 C G1 "THRU" G2

ASET1 123456 88 THRU 207

328 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

C Component number.

(Integer zero or blank for scalar points, or up to 6 unique digits (0 < integer
< 6) may be placed in the field with no embedded blanks for grid points. The
components refer to the coordinate system referenced by the grid points.)

Gi Grid or scalar point identification numbers.

(Integer > 0, for THRU option, G1 < G2)

Comments

1. If the alternate format is used, all points in the sequence G1 through G2 are not required
to exist, but there must be at least one boundary degree-of-freedom for the model, or a
fatal error will result. Any grids implied in the THRU that do not exist will collectively
produce a warning message, but will otherwise be ignored.

2. Refer to the User's Guide section on The Direct Matrix Approach for more information on
the use of this card.

3. A fatal error will be issued if the input contains ASET or ASET1, but PARAM, EXTOUT is
not given.

4. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
MIXED, it is allowed that when grid lists are provided for a given component, that the grid
references be either scalar points (SPOINT) or structural grid points (GRID) when the
component is 0, 1 or blank; interpreting all of these as 0 for scalar points and as 1 for
structural grids. When SPSYNTAX is set to STRICT it is required for grid/component pairs
(G#/C#) that the component be 0 or blank when the grid references are to scalar points
(SPOINT), and that the component be > 1 when the grid references are to structural grid
points (GRID). When the component is greater than 1, the grid references must always
be a structural grid (GRID).

5. This card is represented as a constraint load in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 329

Proprietary Information of Altair Engineering


BEAD

The BEAD bulk data entry will no longer be supported for the definition of topography
optimization. All definitions must be provided using the DTPG bulk data entry. HyperMesh will
continue to read BEAD entries, but will convert them into DTPG entries.

Information regarding the BEAD entry can be found in the Previously Supported Input section
of the Reference Guide.

330 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


BEGIN

Bulk Data Entry

BEGIN – Indicates the beginning of data input for a specific entity.

Description

The BEGIN bulk data entry indicates the beginning of data that is used to describe a specific
entity (or entities) for inclusion in a model. The BEGIN entry is used in conjunction with the
END entry to define the data required for a specific entity.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

BEGIN TYPE NAME

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

BEGIN FEMODEL Bumper

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

BEGIN HYPRBEAM Square

Field Contents

TYPE Specifies the entity type that will be defined by the BEGIN data entry (see
Comment 2).

(HYPRBEAM or FEMODEL)

NAME This field specifies the name of the entity that is defined by the BEGIN entry
(see Comment 2).

(Character String)

Altair Engineering OptiStruct 13.0 Reference Guide 331

Proprietary Information of Altair Engineering


Comments

1. The BEGIN and END bulk data entries are used in conjunction to define an entity within
the full model.

2. TYPE = HYPRBEAM:

Data required for the definition of an arbitrary beam section will be specified between the
BEGIN and END data entries.

TYPE = FEMODEL:

In a model containing multiple parts, the parts are included within the full model specifying
part data between the BEGIN and END bulk data entries (the INCLUDE entry can also be
used for part data referencing). The name of the included part should be specified in the
NAME field.

3. The INCLUDE entry, similar to almost any other bulk data entry, is allowed between BEGIN
and END entries. However, BEGIN and END should exist in the same file.

4. Models are often defined in separate files, and the block (BEGIN – END) contains only
INCLUDE entries. It is possible to duplicate a single part by including the same file(s) in
different BEGIN-END blocks.

5. There can be multiple sections of arbitrary beam data; one for each beam section.

6. An example set of data for the definition of an arbitrary beam section is as follows:
BEGIN,HYPRBEAM,SQUARE
$
GRIDS,1,0.0,0.0
GRIDS,2,1.0,0.0
GRIDS,3,1.0,1.0
GRIDS,4,0.0,1.0
$
CSEC2,10,100,1,2
CSEC2,20,100,2,3
CSEC2,30,100,3,4
CSEC2,40,100,4,1
$
PSEC,100,1000,0.1
$
END,HYPRBEAM

332 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


BLKHDF

Bulk Data Entry

BLKHDF – Blank Holder Force for One-Step Stamping Simulation

Description

Defines the blank holder force in a one-step stamping simulation.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

BLKHDF BHID MU FORC E TOGGLE

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

BLKHDF 6 0.3 3.0 0.0

Field Contents

BHID Blank holder identification number.

No default (Integer > 0)

MU Coefficient of friction.

No default (Real > 0.0)

FORCE Blank holder force.

No default (Real)

TOGGLE Flag assigned based on option (Pressure or Tonnage).

0.0 – Uniform pressure is applied on blank holder.

1.0 – Net force is applied on blank holder.

Comments

1. This entry is only valid with an @HyperForm statement in the first line of the input file.

Altair Engineering OptiStruct 13.0 Reference Guide 333

Proprietary Information of Altair Engineering


BMFACE

Bulk Data Entry

BMFACE – Barrier Mesh Face

Description

Defines quad or tria faces that are in turn used to define a barrier to limit the total
deformation for free-shape design regions.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

BMFAC E BMID G1 G2 G3 G4

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

BMFAC E 10 8203 8204 8100

Field Contents

BMID Barrier mesh identification number. Referenced from a DSHAPE bulk data
entry.

No default (Integer > 0)

G# Grid point identification number of connection points. G1, G2, and G3 are
required to define tria faces, G4 is required to define quad faces.

No default (Integer > 0, all unique)

Comments

1. Grid points used in the definition of BMFACE entries cannot be used to define structural
elements.

334 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


BNDFIX

Bulk Data Entry

BNDFIX – Boundary Degrees-of-Freedom of a Superelement Assembly

Description

Defines the degrees-of-freedom to be fixed during DMIG generation using CMSMETH card.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

BNDFIX GID1 IC 1 GID2 IC 2 GID3 IC 3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

BNDFIX 1220 12345

Field Contents

GIDi Grid of scalar point identification numbers.

No default (Integer > 0)

ICi Component numbers.

No default (Integer > 0)

Comments

1. BNDFIX and BSET are equivalent.

2. ASET, BNDFIX and BNDFREE; all three are not allowed in the same deck.

3. If BNDFREE and ASET are present, the DOFs associated with ASET would be in BNDFIX;
except the DOF assigned to BNDFREE.

4. If BNDFIX and ASET are present, the DOFs associated with ASET would be in BNDFREE;
except the DOF assigned to BNDFIX.

Altair Engineering OptiStruct 13.0 Reference Guide 335

Proprietary Information of Altair Engineering


BNDFIX1

Bulk Data Entry

BNDFIX1 – Fixed Boundary Degrees-of-Freedom of a Superelement Assembly

Description

Defines the fixed (B-set) degrees-of-freedom to be fixed during DMIG generation using
CMSMETH card.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

BNDFIX1 C GID1 GID2 GID3 GID4 "thru" GID6 GID7

GID8 GID9 etc.

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

BNDFIX1 12345 1220 1221 THRU 1229

Field Contents

C Component numbers.
No default (Integer > 0 or blank). Zero or blank for SPOINT and any unique
combination of integers 1 through 6 for grid points with no embedded
blanks.

GIDi Grid of scalar point identification numbers.

No default (Integer > 0)

THRU Keyword to allow a range of GID. THRU can be in any field.

336 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. BNDFIX1 and BSET1 are equivalent.

2. The combination of the three ASET/ASET1, BNDFIX/BNDFIX1 and BNDFREE/BNDFRE1 are


not allowed together in the same input data.

3. If BNDFREE/BNDFRE1 and ASET/ASET1 are present, the DOFs associated with ASET will be
in the B-set; except the DOF assigned to BNDFREE which will be in the C-set.

4. If BNDFIX/BNDFIX1 and ASET/ASET1 are present, the DOFs associated with ASET would
be in C-set; except the DOF assigned to BNDFIX which will be in the B-set.

5. Multiple “thru” sequences can be used on a single card, and can span across continuation
lines.

6. If the "thru" comment is used, G1 and G2 must exist, but the grid points between G1 and
G2 are not required to exist.

Altair Engineering OptiStruct 13.0 Reference Guide 337

Proprietary Information of Altair Engineering


BNDFRE1

Bulk Data Entry

BNDFRE1 – Free Boundary Degrees-of-Freedom of a Superelement Assembly

Description

Defines the free (C-set) degrees-of-freedom to be fixed during DMIG generation using
CMSMETH card.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

BNDFRE1 C GID1 GID2 GID3 GID4 "thru" GID6 GID7

GID8 GID9 etc.

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

BNDFRE 12345 1220 1221 thru 1229


1

Field Contents

C Component numbers.

No default (Integer > 0 or blank). Zero or blank for SPOINT and any unique
combination of integers 1 through 6 for grid points with no embedded blanks.

GIDi Grid of scalar point identification numbers.

No default (Integer > 0)

THRU Keyword to allow a range of GID. THRU can be in any field.

338 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. BNDFRE1 and CSET1 are equivalent.

2. The combination of the three ASET/ASET1, BNDFIX/BNDFIX1, and BNDFREE/BNDFRE1 are


not allowed together in the same input data.

3. If BNDFREE/BNDFRE1 and ASET/ASET1 are present, the DOFs associated with ASET will be
in the B-set; except the DOF assigned to BNDFREE which will be in the C-set.

4. If BNDFIX/BNDFIX1 and ASET/ASET1 are present, the DOFs associated with ASET would
be in C-set; except the DOF assigned to BNDFIX which will be in the B-set. Any number of
continuations may appear.

5. Multiple “thru” sequences can be used on a single card, and can span across continuation
lines.

6. If the "thru" comment is used, G1 and G2 must exist, but the grid points between G1 and
G2 are not required to exist.

Altair Engineering OptiStruct 13.0 Reference Guide 339

Proprietary Information of Altair Engineering


BNDFREE

Bulk Data Entry

BNDFREE – Boundary Degrees-of-Freedom of a Superelement Assembly

Description

Defines the degrees-of-freedom to be fixed during DMIG generation using CMSMETH card.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

BNDFREE GID1 IC 1 GID2 IC 2 GID3 IC 3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

BNDFREE 1220 12345

Field Contents

GIDi Grid of scalar point identification numbers.

No default (Integer > 0)

ICi Component numbers.

No default (Integer > 0)

Comments

1. BNDFREE and CSET are equivalent.

2. ASET, BNDFIX and BNDFREE are not allowed in the same deck.

3. If BNDFREE and ASET are present, the DOFs associated with ASET would be in BNDFIX;
except the DOF assigned to BNDFREE.

4. If BNDFIX and ASET are present, the DOFs associated with ASET would be in BNDFREE;
except the DOF assigned to BNDFIX.

340 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


BSET

Bulk Data Entry

BSET – Boundary Degrees-of-Freedom of a Superelement Assembly

Description

BSET entry is equivalent to BNDFIX.

Refer to the documentation for the BNDFIX Bulk Data Entry.

Altair Engineering OptiStruct 13.0 Reference Guide 341

Proprietary Information of Altair Engineering


BSET1

Bulk Data Entry

BSET1– Fixed Boundary Degrees-of-Freedom of a Superelement Assembly

Description

BSET1 entry is equivalent to BNDFIX1.

Refer to the documentation for the BNDFIX1 Bulk Data Entry.

342 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CAABSF

Bulk Data Entry

CAABSF – Frequency-dependant Fluid Acoustic Absorber Element

Description

Defines the frequency-dependant fluid acoustic absorber element in coupled fluid-structural


analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C AABSF EID PID G1 G2 G3 G4

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C AABSF 71 4 1 10 5

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PAABSF property entry.

No default (Integer > 0)

Gi Grid point identification numbers of fluid connection points.

Default = blank (Integer > 0 or blank)

Input File - mdcaabsf.parm

Altair Engineering OptiStruct 13.0 Reference Guide 343

Proprietary Information of Altair Engineering


$$
$$ Optistruct Input Deck Generated by HyperMesh Version : 10.0build60
$$ Generated using HyperMesh-Optistruct Template Version : 10.0-SA1-120
$$
$$ Template: optistruct
$$
$$
$
DISPLACEMENT(PHASE) = 1
OUTPUT,HGFREQ,ALL
OUTPUT,OPTI,ALL
OUTPUT,H3D,ALL
OUTPUT,PUNCH,ALL
$$------------------------------------------------------------------------------$
$$ Case Control Cards $
$$------------------------------------------------------------------------------$
$
$HMNAME LOADSTEP 1"Piston_Load" 6
$
SUBCASE 1
LABEL Piston_Load
SPC = 12
METHOD(STRUCTURE) = 4
METHOD(FLUID) = 5
FREQUENCY = 3
DLOAD = 9
XYPUNCH DISP 1/ 11(T1)
XYPUNCH DISP 1/ 43(T1)
XYPUNCH DISP 1/ 55(T1)
XYPUNCH DISP 1/ 67(T1)
XYPUNCH DISP 1/ 79(T1)
XYPUNCH DISP 1/ 91(T1)
XYPUNCH DISP 1/ 103(T1)
XYPUNCH DISP 1/ 115(T1)
XYPUNCH DISP 1/ 127(T1)
XYPUNCH DISP 1/ 139(T1)
XYPUNCH DISP 1/ 151(T1)
XYPUNCH DISP 1/ 163(T1)
XYPUNCH DISP 1/ 175(T1)
XYPUNCH DISP 1/ 187(T1)
XYPUNCH DISP 1/ 199(T1)
XYPUNCH DISP 1/ 531(T1)
XYPUNCH DISP 1/ 543(T1)
XYPUNCH DISP 1/ 555(T1)
XYPUNCH DISP 1/ 567(T1)
XYPUNCH DISP 1/ 579(T1)
XYPUNCH DISP 1/ 591(T1)
XYPUNCH DISP 1/ 603(T1)
XYPUNCH DISP 1/ 615(T1)
XYPUNCH DISP 1/ 627(T1)
XYPUNCH DISP 1/ 639(T1)
XYPUNCH DISP 1/ 651(T1)
XYPUNCH DISP 1/ 663(T1)
XYPUNCH DISP 1/ 675(T1)
XYPUNCH DISP 1/ 687(T1)
$
$HMSET 1 1 "pressure"
SET 1 = 43,55,67,79,91,103,115,
127,139,151,163,175,187,199,
531,543,555,567,579,591,603,
615,627,639,651,663,675,687,
6798

$
$$--------------------------------------------------------------
$$ HYPERMESH TAGS
$$--------------------------------------------------------------
$$BEGIN TAGS
$$END TAGS

344 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


$
BEGIN BULK
ACMODL
$$
$$ Stacking Information for Ply-Based Composite Definition
$$

PARAM,AUTOSPC,YES
PARAM,POST,-1
$$
$$ DESVARG Data
$$
$$
$$ GRID Data
$$
GRID 9 0.492 0.0 -1.72-15 -1
GRID 10 0.246 0.0 -8.59-16 -1
GRID 11 0.0 0.0 0.0 -1
GRID 12 -0.246 0.0 8.589-16 -1
GRID 13 -0.492 0.0 1.718-15 -1
GRID 14 -0.492 0.246 1.718-15 -1
GRID 15 -0.492 0.492 1.718-15 -1
GRID 16 -0.246 0.492 8.589-16 -1
GRID 17 0.0 0.492 0.0 -1
GRID 18 0.246 0.492 -8.59-16 -1
GRID 19 0.492 0.492 -1.72-15 -1
GRID 20 0.492 0.246 -1.72-15 -1
GRID 21 0.0 0.246 0.0 -1
GRID 22 -0.246 0.246 8.589-16 -1
GRID 23 0.246 0.246 -8.59-16 -1
GRID 24 0.492 -0.246 -1.72-15 -1
GRID 25 0.492 -0.492 -1.72-15 -1
GRID 26 0.246 -0.492 -8.59-16 -1
GRID 27 0.0 -0.492 0.0 -1
GRID 28 -0.246 -0.492 8.589-16 -1
GRID 29 -0.492 -0.492 1.718-15 -1
GRID 30 -0.492 -0.246 1.718-15 -1
GRID 31 0.0 -0.246 0.0 -1
GRID 32 0.246 -0.246 -8.59-16 -1
GRID 33 -0.246 -0.246 8.589-16 -1
GRID 34 0.246 5.049-29-.300073 -1
GRID 35 -5.99-130.0 -.300073 -1
GRID 36 -5.62-130.246 -.300073 -1
GRID 37 0.246 0.246 -.300073 -1
GRID 38 0.246 2.524-29-.600146 -1
GRID 39 -1.2-12 0.0 -.600146 -1
GRID 40 -1.12-120.246 -.600146 -1
GRID 41 0.246 0.246 -.600146 -1
GRID 42 0.246 2.919-29-0.90022 -1
GRID 43 -1.79-120.0 -.900219 -1
GRID 44 -1.68-120.246 -.900219 -1
GRID 45 0.246 0.246 -0.90022 -1
GRID 46 0.246 3.787-29-1.20029 -1
GRID 47 -2.39-120.0 -1.20029 -1
GRID 48 -2.24-120.246 -1.20029 -1
GRID 49 0.246 0.246 -1.20029 -1
GRID 50 0.246 4.733-29-1.50037 -1
GRID 51 -3.0-12 0.0 -1.50037 -1
GRID 52 -2.81-120.246 -1.50037 -1
GRID 53 0.246 0.246 -1.50037 -1
GRID 54 0.246 5.364-29-1.80044 -1
GRID 55 -3.6-12 0.0 -1.80044 -1
GRID 56 -3.37-120.246 -1.80044 -1
GRID 57 0.246 0.246 -1.80044 -1
GRID 58 0.246 6.311-29-2.10051 -1
GRID 59 -4.2-12 0.0 -2.10051 -1
GRID 60 -3.93-120.246 -2.10051 -1
GRID 61 0.246 0.246 -2.10051 -1
GRID 62 0.246 7.258-29-2.40059 -1

Altair Engineering OptiStruct 13.0 Reference Guide 345

Proprietary Information of Altair Engineering


GRID 63 -4.79-120.0 -2.40059 -1
GRID 64 -4.49-120.246 -2.40059 -1
GRID 65 0.246 0.246 -2.40059 -1
GRID 66 0.246 8.204-29-2.70066 -1
GRID 67 -5.39-120.0 -2.70066 -1
GRID 68 -5.06-120.246 -2.70066 -1
GRID 69 0.246 0.246 -2.70066 -1
GRID 70 0.246 8.835-29-3.00073 -1
GRID 71 -5.99-120.0 -3.00073 -1
GRID 72 -5.62-120.246 -3.00073 -1
GRID 73 0.246 0.246 -3.00073 -1
GRID 74 0.246 9.782-29-3.30081 -1
GRID 75 -6.59-120.0 -3.30081 -1
GRID 76 -6.18-120.246 -3.30081 -1
GRID 77 0.246 0.246 -3.30081 -1
GRID 78 0.246 1.073-28-3.60088 -1
GRID 79 -7.19-120.0 -3.60088 -1
GRID 80 -6.74-120.246 -3.60088 -1
GRID 81 0.246 0.246 -3.60088 -1
GRID 82 0.246 1.136-28-3.90095 -1
GRID 83 -7.78-120.0 -3.90095 -1
GRID 84 -7.3-12 0.246 -3.90095 -1
GRID 85 0.246 0.246 -3.90095 -1
GRID 86 0.246 1.231-28-4.20102 -1
GRID 87 -8.38-120.0 -4.20102 -1
GRID 88 -7.86-120.246 -4.20102 -1
GRID 89 0.246 0.246 -4.20102 -1
GRID 90 0.246 1.294-28-4.5011 -1
GRID 91 -8.99-120.0 -4.5011 -1
GRID 92 -8.43-120.246 -4.5011 -1
GRID 93 0.246 0.246 -4.5011 -1
GRID 94 0.246 1.388-28-4.80117 -1
GRID 95 -9.59-120.0 -4.80117 -1
GRID 96 -8.99-120.246 -4.80117 -1
GRID 97 0.246 0.246 -4.80117 -1
GRID 98 0.246 1.452-28-5.10124 -1
GRID 99 -1.02-110.0 -5.10124 -1
GRID 100 -9.55-120.246 -5.10124 -1
GRID 101 0.246 0.246 -5.10124 -1
GRID 102 0.246 1.515-28-5.40132 -1
GRID 103 -1.08-110.0 -5.40132 -1
GRID 104 -1.01-110.246 -5.40132 -1
GRID 105 0.246 0.246 -5.40132 -1
GRID 106 0.246 1.609-28-5.70139 -1
GRID 107 -1.14-110.0 -5.70139 -1
GRID 108 -1.07-110.246 -5.70139 -1
GRID 109 0.246 0.246 -5.70139 -1
GRID 110 0.246 1.672-28-6.00146 -1
GRID 111 -1.2-11 0.0 -6.00146 -1
GRID 112 -1.12-110.246 -6.00146 -1
GRID 113 0.246 0.246 -6.00146 -1
GRID 114 0.246 1.735-28-6.30154 -1
GRID 115 -1.26-110.0 -6.30154 -1
GRID 116 -1.18-110.246 -6.30154 -1
GRID 117 0.246 0.246 -6.30154 -1
GRID 118 0.246 1.83-28 -6.60161 -1
GRID 119 -1.32-110.0 -6.60161 -1
GRID 120 -1.23-110.246 -6.60161 -1
GRID 121 0.246 0.246 -6.60161 -1
GRID 122 0.246 1.893-28-6.90168 -1
GRID 123 -1.38-110.0 -6.90168 -1
GRID 124 -1.29-110.246 -6.90168 -1
GRID 125 0.246 0.246 -6.90168 -1
GRID 126 0.246 1.956-28-7.20176 -1
GRID 127 -1.44-110.0 -7.20176 -1
GRID 128 -1.35-110.246 -7.20176 -1
GRID 129 0.246 0.246 -7.20176 -1
GRID 130 0.246 2.019-28-7.50183 -1
GRID 131 -1.5-11 0.0 -7.50183 -1

346 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 132 -1.4-11 0.246 -7.50183 -1
GRID 133 0.246 0.246 -7.50183 -1
GRID 134 0.246 2.083-28-7.8019 -1
GRID 135 -1.55-110.0 -7.8019 -1
GRID 136 -1.46-110.246 -7.8019 -1
GRID 137 0.246 0.246 -7.8019 -1
GRID 138 0.246 2.146-28-8.10198 -1
GRID 139 -1.61-110.0 -8.10198 -1
GRID 140 -1.51-110.246 -8.10198 -1
GRID 141 0.246 0.246 -8.10198 -1
GRID 142 0.246 2.209-28-8.40205 -1
GRID 143 -1.67-110.0 -8.40205 -1
GRID 144 -1.57-110.246 -8.40205 -1
GRID 145 0.246 0.246 -8.40205 -1
GRID 146 0.246 2.272-28-8.70212 -1
GRID 147 -1.73-110.0 -8.70212 -1
GRID 148 -1.63-110.246 -8.70212 -1
GRID 149 0.246 0.246 -8.70212 -1
GRID 150 0.246 2.335-28-9.0022 -1
GRID 151 -1.79-110.0 -9.0022 -1
GRID 152 -1.68-110.246 -9.0022 -1
GRID 153 0.246 0.246 -9.0022 -1
GRID 154 0.246 2.398-28-9.30227 -1
GRID 155 -1.85-110.0 -9.30227 -1
GRID 156 -1.74-110.246 -9.30227 -1
GRID 157 0.246 0.246 -9.30227 -1
GRID 158 0.246 2.461-28-9.60234 -1
GRID 159 -1.91-110.0 -9.60234 -1
GRID 160 -1.79-110.246 -9.60234 -1
GRID 161 0.246 0.246 -9.60234 -1
GRID 162 0.246 2.524-28-9.90241 -1
GRID 163 -1.97-110.0 -9.90241 -1
GRID 164 -1.85-110.246 -9.90241 -1
GRID 165 0.246 0.246 -9.90241 -1
GRID 166 0.246 2.556-28-10.2025 -1
GRID 167 -2.03-110.0 -10.2025 -1
GRID 168 -1.91-110.246 -10.2025 -1
GRID 169 0.246 0.246 -10.2025 -1
GRID 170 0.246 2.619-28-10.5026 -1
GRID 171 -2.09-110.0 -10.5026 -1
GRID 172 -1.96-110.246 -10.5026 -1
GRID 173 0.246 0.246 -10.5026 -1
GRID 174 0.246 2.682-28-10.8026 -1
GRID 175 -2.15-110.0 -10.8026 -1
GRID 176 -2.02-110.246 -10.8026 -1
GRID 177 0.246 0.246 -10.8026 -1
GRID 178 0.246 2.745-28-11.1027 -1
GRID 179 -2.21-110.0 -11.1027 -1
GRID 180 -2.07-110.246 -11.1027 -1
GRID 181 0.246 0.246 -11.1027 -1
GRID 182 0.246 2.777-28-11.4028 -1
GRID 183 -2.27-110.0 -11.4028 -1
GRID 184 -2.13-110.246 -11.4028 -1
GRID 185 0.246 0.246 -11.4028 -1
GRID 186 0.246 2.84-28 -11.7029 -1
GRID 187 -2.33-110.0 -11.7029 -1
GRID 188 -2.19-110.246 -11.7029 -1
GRID 189 0.246 0.246 -11.7029 -1
GRID 190 0.246 2.871-28-12.0029 -1
GRID 191 -2.39-110.0 -12.0029 -1
GRID 192 -2.24-110.246 -12.0029 -1
GRID 193 0.246 0.246 -12.0029 -1
GRID 194 0.246 2.935-28-12.303 -1
GRID 195 -2.45-110.0 -12.303 -1
GRID 196 -2.3-11 0.246 -12.303 -1
GRID 197 0.246 0.246 -12.303 -1
GRID 198 0.246 2.966-28-12.6031 -1
GRID 199 -2.51-110.0 -12.6031 -1
GRID 200 -2.35-110.246 -12.6031 -1

Altair Engineering OptiStruct 13.0 Reference Guide 347

Proprietary Information of Altair Engineering


GRID 201 0.246 0.246 -12.6031 -1
GRID 522 0.246 2.935-28-12.903 -1
GRID 523 -7.36-110.0 -12.903 -1
GRID 524 -6.9-11 0.246 -12.903 -1
GRID 525 0.246 0.246 -12.903 -1
GRID 526 0.246 2.903-28-13.2031 -1
GRID 527 -7.42-110.0 -13.2031 -1
GRID 528 -6.95-110.246 -13.2031 -1
GRID 529 0.246 0.246 -13.2031 -1
GRID 530 0.246 2.84-28 -13.5032 -1
GRID 531 -7.48-110.0 -13.5032 -1
GRID 532 -7.01-110.246 -13.5032 -1
GRID 533 0.246 0.246 -13.5032 -1
GRID 534 0.246 2.777-28-13.8032 -1
GRID 535 -7.54-110.0 -13.8032 -1
GRID 536 -7.06-110.246 -13.8032 -1
GRID 537 0.246 0.246 -13.8032 -1
GRID 538 0.246 2.745-28-14.1033 -1
GRID 539 -7.6-11 0.0 -14.1033 -1
GRID 540 -7.12-110.246 -14.1033 -1
GRID 541 0.246 0.246 -14.1033 -1
GRID 542 0.246 2.682-28-14.4034 -1
GRID 543 -7.67-110.0 -14.4034 -1
GRID 544 -7.19-110.246 -14.4034 -1
GRID 545 0.246 0.246 -14.4034 -1
GRID 546 0.246 2.619-28-14.7034 -1
GRID 547 -7.73-110.0 -14.7034 -1
GRID 548 -7.24-110.246 -14.7034 -1
GRID 549 0.246 0.246 -14.7034 -1
GRID 550 0.246 2.587-28-15.0035 -1
GRID 551 -7.78-110.0 -15.0035 -1
GRID 552 -7.3-11 0.246 -15.0035 -1
GRID 553 0.246 0.246 -15.0035 -1
GRID 554 0.246 2.524-28-15.3036 -1
GRID 555 -7.84-110.0 -15.3036 -1
GRID 556 -7.35-110.246 -15.3036 -1
GRID 557 0.246 0.246 -15.3036 -1
GRID 558 0.246 2.461-28-15.6037 -1
GRID 559 -7.9-11 0.0 -15.6037 -1
GRID 560 -7.41-110.246 -15.6037 -1
GRID 561 0.246 0.246 -15.6037 -1
GRID 562 0.246 2.398-28-15.9037 -1
GRID 563 -7.96-110.0 -15.9037 -1
GRID 564 -7.47-110.246 -15.9037 -1
GRID 565 0.246 0.246 -15.9037 -1
GRID 566 0.246 2.335-28-16.2038 -1
GRID 567 -8.02-110.0 -16.2038 -1
GRID 568 -7.52-110.246 -16.2038 -1
GRID 569 0.246 0.246 -16.2038 -1
GRID 570 0.246 2.272-28-16.5039 -1
GRID 571 -8.08-110.0 -16.5039 -1
GRID 572 -7.58-110.246 -16.5039 -1
GRID 573 0.246 0.246 -16.5039 -1
GRID 574 0.246 2.209-28-16.804 -1
GRID 575 -8.14-110.0 -16.804 -1
GRID 576 -7.63-110.246 -16.804 -1
GRID 577 0.246 0.246 -16.804 -1
GRID 578 0.246 2.146-28-17.104 -1
GRID 579 -8.2-11 0.0 -17.104 -1
GRID 580 -7.69-110.246 -17.104 -1
GRID 581 0.246 0.246 -17.104 -1
GRID 582 0.246 2.083-28-17.4041 -1
GRID 583 -8.26-110.0 -17.4041 -1
GRID 584 -7.75-110.246 -17.4041 -1
GRID 585 0.246 0.246 -17.4041 -1
GRID 586 0.246 2.019-28-17.7042 -1
GRID 587 -8.32-110.0 -17.7042 -1
GRID 588 -7.8-11 0.246 -17.7042 -1
GRID 589 0.246 0.246 -17.7042 -1

348 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 590 0.246 1.956-28-18.0042 -1
GRID 591 -8.38-110.0 -18.0042 -1
GRID 592 -7.86-110.246 -18.0042 -1
GRID 593 0.246 0.246 -18.0042 -1
GRID 594 0.246 1.893-28-18.3043 -1
GRID 595 -8.44-110.0 -18.3043 -1
GRID 596 -7.91-110.246 -18.3043 -1
GRID 597 0.246 0.246 -18.3043 -1
GRID 598 0.246 1.83-28 -18.6044 -1
GRID 599 -8.5-11 0.0 -18.6044 -1
GRID 600 -7.97-110.246 -18.6044 -1
GRID 601 0.246 0.246 -18.6044 -1
GRID 602 0.246 1.735-28-18.9045 -1
GRID 603 -8.56-110.0 -18.9045 -1
GRID 604 -8.03-110.246 -18.9045 -1
GRID 605 0.246 0.246 -18.9045 -1
GRID 606 0.246 1.672-28-19.2045 -1
GRID 607 -8.62-110.0 -19.2045 -1
GRID 608 -8.08-110.246 -19.2045 -1
GRID 609 0.246 0.246 -19.2045 -1
GRID 610 0.246 1.609-28-19.5046 -1
GRID 611 -8.68-110.0 -19.5046 -1
GRID 612 -8.14-110.246 -19.5046 -1
GRID 613 0.246 0.246 -19.5046 -1
GRID 614 0.246 1.515-28-19.8047 -1
GRID 615 -8.74-110.0 -19.8047 -1
GRID 616 -8.19-110.246 -19.8047 -1
GRID 617 0.246 0.246 -19.8047 -1
GRID 618 0.246 1.452-28-20.1048 -1
GRID 619 -8.8-11 0.0 -20.1048 -1
GRID 620 -8.25-110.246 -20.1048 -1
GRID 621 0.246 0.246 -20.1048 -1
GRID 622 0.246 1.388-28-20.4048 -1
GRID 623 -8.86-110.0 -20.4048 -1
GRID 624 -8.31-110.246 -20.4048 -1
GRID 625 0.246 0.246 -20.4048 -1
GRID 626 0.246 1.294-28-20.7049 -1
GRID 627 -8.92-110.0 -20.7049 -1
GRID 628 -8.36-110.246 -20.7049 -1
GRID 629 0.246 0.246 -20.7049 -1
GRID 630 0.246 1.231-28-21.005 -1
GRID 631 -8.98-110.0 -21.005 -1
GRID 632 -8.42-110.246 -21.005 -1
GRID 633 0.246 0.246 -21.005 -1
GRID 634 0.246 1.136-28-21.3051 -1
GRID 635 -9.04-110.0 -21.3051 -1
GRID 636 -8.47-110.246 -21.3051 -1
GRID 637 0.246 0.246 -21.3051 -1
GRID 638 0.246 1.073-28-21.6051 -1
GRID 639 -9.1-11 0.0 -21.6051 -1
GRID 640 -8.53-110.246 -21.6051 -1
GRID 641 0.246 0.246 -21.6051 -1
GRID 642 0.246 9.782-29-21.9052 -1
GRID 643 -9.16-110.0 -21.9052 -1
GRID 644 -8.59-110.246 -21.9052 -1
GRID 645 0.246 0.246 -21.9052 -1
GRID 646 0.246 8.835-29-22.2053 -1
GRID 647 -9.22-110.0 -22.2053 -1
GRID 648 -8.64-110.246 -22.2053 -1
GRID 649 0.246 0.246 -22.2053 -1
GRID 650 0.246 8.204-29-22.5053 -1
GRID 651 -9.28-110.0 -22.5053 -1
GRID 652 -8.7-11 0.246 -22.5053 -1
GRID 653 0.246 0.246 -22.5053 -1
GRID 654 0.246 7.258-29-22.8054 -1
GRID 655 -9.34-110.0 -22.8054 -1
GRID 656 -8.75-110.246 -22.8054 -1
GRID 657 0.246 0.246 -22.8054 -1
GRID 658 0.246 6.311-29-23.1055 -1

Altair Engineering OptiStruct 13.0 Reference Guide 349

Proprietary Information of Altair Engineering


GRID 659 -9.4-11 0.0 -23.1055 -1
GRID 660 -8.81-110.246 -23.1055 -1
GRID 661 0.246 0.246 -23.1055 -1
GRID 662 0.246 5.364-29-23.4056 -1
GRID 663 -9.46-110.0 -23.4056 -1
GRID 664 -8.87-110.246 -23.4056 -1
GRID 665 0.246 0.246 -23.4056 -1
GRID 666 0.246 4.733-29-23.7056 -1
GRID 667 -9.52-110.0 -23.7056 -1
GRID 668 -8.92-110.246 -23.7056 -1
GRID 669 0.246 0.246 -23.7056 -1
GRID 670 0.246 3.787-29-24.0057 -1
GRID 671 -9.58-110.0 -24.0057 -1
GRID 672 -8.98-110.246 -24.0057 -1
GRID 673 0.246 0.246 -24.0057 -1
GRID 674 0.246 2.84-29 -24.3058 -1
GRID 675 -9.64-110.0 -24.3058 -1
GRID 676 -9.04-110.246 -24.3058 -1
GRID 677 0.246 0.246 -24.3058 -1
GRID 678 0.246 1.893-29-24.6059 -1
GRID 679 -9.7-11 0.0 -24.6059 -1
GRID 680 -9.09-110.246 -24.6059 -1
GRID 681 0.246 0.246 -24.6059 -1
GRID 682 0.246 9.466-30-24.9059 -1
GRID 683 -9.76-110.0 -24.9059 -1
GRID 684 -9.15-110.246 -24.9059 -1
GRID 685 0.246 0.246 -24.9059 -1
GRID 686 0.246 4.151-12-25.206 -1
GRID 687 -9.82-112.767-12-25.206 -1
GRID 688 -9.16-110.246 -25.206 -1
GRID 689 0.246 0.246 -25.206 -1
GRID 690 0.492 4.323-13-.300073 -1
GRID 691 0.492 0.246 -.300073 -1
GRID 692 0.492 1.621-13-.600146 -1
GRID 693 0.492 0.246 -.600146 -1
GRID 694 0.492 1.592-13-0.90022 -1
GRID 695 0.492 0.246 -0.90022 -1
GRID 696 0.492 2.009-13-1.20029 -1
GRID 697 0.492 0.246 -1.20029 -1
GRID 698 0.492 2.5-13 -1.50037 -1
GRID 699 0.492 0.246 -1.50037 -1
GRID 700 0.492 3.004-13-1.80044 -1
GRID 701 0.492 0.246 -1.80044 -1
GRID 702 0.492 3.51-13 -2.10051 -1
GRID 703 0.492 0.246 -2.10051 -1
GRID 704 0.492 4.016-13-2.40059 -1
GRID 705 0.492 0.246 -2.40059 -1
GRID 706 0.492 4.522-13-2.70066 -1
GRID 707 0.492 0.246 -2.70066 -1
GRID 708 0.492 5.028-13-3.00073 -1
GRID 709 0.492 0.246 -3.00073 -1
GRID 710 0.492 5.534-13-3.30081 -1
GRID 711 0.492 0.246 -3.30081 -1
GRID 712 0.492 6.041-13-3.60088 -1
GRID 713 0.492 0.246 -3.60088 -1
GRID 714 0.492 6.547-13-3.90095 -1
GRID 715 0.492 0.246 -3.90095 -1
GRID 716 0.492 7.053-13-4.20102 -1
GRID 717 0.492 0.246 -4.20102 -1
GRID 718 0.492 7.559-13-4.5011 -1
GRID 719 0.492 0.246 -4.5011 -1
GRID 720 0.492 8.066-13-4.80117 -1
GRID 721 0.492 0.246 -4.80117 -1
GRID 722 0.492 8.572-13-5.10124 -1
GRID 723 0.492 0.246 -5.10124 -1
GRID 724 0.492 9.078-13-5.40132 -1
GRID 725 0.492 0.246 -5.40132 -1
GRID 726 0.492 9.584-13-5.70139 -1
GRID 727 0.492 0.246 -5.70139 -1

350 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 728 0.492 1.009-12-6.00146 -1
GRID 729 0.492 0.246 -6.00146 -1
GRID 730 0.492 1.06-12 -6.30154 -1
GRID 731 0.492 0.246 -6.30154 -1
GRID 732 0.492 1.11-12 -6.60161 -1
GRID 733 0.492 0.246 -6.60161 -1
GRID 734 0.492 1.161-12-6.90168 -1
GRID 735 0.492 0.246 -6.90168 -1
GRID 736 0.492 1.212-12-7.20176 -1
GRID 737 0.492 0.246 -7.20176 -1
GRID 738 0.492 1.262-12-7.50183 -1
GRID 739 0.492 0.246 -7.50183 -1
GRID 740 0.492 1.313-12-7.8019 -1
GRID 741 0.492 0.246 -7.8019 -1
GRID 742 0.492 1.363-12-8.10198 -1
GRID 743 0.492 0.246 -8.10198 -1
GRID 744 0.492 1.414-12-8.40205 -1
GRID 745 0.492 0.246 -8.40205 -1
GRID 746 0.492 1.465-12-8.70212 -1
GRID 747 0.492 0.246 -8.70212 -1
GRID 748 0.492 1.515-12-9.0022 -1
GRID 749 0.492 0.246 -9.0022 -1
GRID 750 0.492 1.566-12-9.30227 -1
GRID 751 0.492 0.246 -9.30227 -1
GRID 752 0.492 1.616-12-9.60234 -1
GRID 753 0.492 0.246 -9.60234 -1
GRID 754 0.492 1.667-12-9.90242 -1
GRID 755 0.492 0.246 -9.90242 -1
GRID 756 0.492 1.718-12-10.2025 -1
GRID 757 0.492 0.246 -10.2025 -1
GRID 758 0.492 1.768-12-10.5026 -1
GRID 759 0.492 0.246 -10.5026 -1
GRID 760 0.492 1.819-12-10.8026 -1
GRID 761 0.492 0.246 -10.8026 -1
GRID 762 0.492 1.87-12 -11.1027 -1
GRID 763 0.492 0.246 -11.1027 -1
GRID 764 0.492 1.92-12 -11.4028 -1
GRID 765 0.492 0.246 -11.4028 -1
GRID 766 0.492 1.971-12-11.7029 -1
GRID 767 0.492 0.246 -11.7029 -1
GRID 768 0.492 2.021-12-12.0029 -1
GRID 769 0.492 0.246 -12.0029 -1
GRID 770 0.492 2.072-12-12.303 -1
GRID 771 0.492 0.246 -12.303 -1
GRID 772 0.492 2.123-12-12.6031 -1
GRID 773 0.492 0.246 -12.6031 -1
GRID 934 0.492 6.223-12-12.903 -1
GRID 935 0.492 0.246 -12.903 -1
GRID 936 0.492 6.274-12-13.2031 -1
GRID 937 0.492 0.246 -13.2031 -1
GRID 938 0.492 6.324-12-13.5032 -1
GRID 939 0.492 0.246 -13.5032 -1
GRID 940 0.492 6.375-12-13.8032 -1
GRID 941 0.492 0.246 -13.8032 -1
GRID 942 0.492 6.425-12-14.1033 -1
GRID 943 0.492 0.246 -14.1033 -1
GRID 944 0.492 6.476-12-14.4034 -1
GRID 945 0.492 0.246 -14.4034 -1
GRID 946 0.492 6.527-12-14.7034 -1
GRID 947 0.492 0.246 -14.7034 -1
GRID 948 0.492 6.577-12-15.0035 -1
GRID 949 0.492 0.246 -15.0035 -1
GRID 950 0.492 6.628-12-15.3036 -1
GRID 951 0.492 0.246 -15.3036 -1
GRID 952 0.492 6.679-12-15.6037 -1
GRID 953 0.492 0.246 -15.6037 -1
GRID 954 0.492 6.729-12-15.9037 -1
GRID 955 0.492 0.246 -15.9037 -1
GRID 956 0.492 6.78-12 -16.2038 -1

Altair Engineering OptiStruct 13.0 Reference Guide 351

Proprietary Information of Altair Engineering


GRID 957 0.492 0.246 -16.2038 -1
GRID 958 0.492 6.83-12 -16.5039 -1
GRID 959 0.492 0.246 -16.5039 -1
GRID 960 0.492 6.881-12-16.804 -1
GRID 961 0.492 0.246 -16.804 -1
GRID 962 0.492 6.932-12-17.104 -1
GRID 963 0.492 0.246 -17.104 -1
GRID 964 0.492 6.982-12-17.4041 -1
GRID 965 0.492 0.246 -17.4041 -1
GRID 966 0.492 7.033-12-17.7042 -1
GRID 967 0.492 0.246 -17.7042 -1
GRID 968 0.492 7.083-12-18.0042 -1
GRID 969 0.492 0.246 -18.0042 -1
GRID 970 0.492 7.134-12-18.3043 -1
GRID 971 0.492 0.246 -18.3043 -1
GRID 972 0.492 7.185-12-18.6044 -1
GRID 973 0.492 0.246 -18.6044 -1
GRID 974 0.492 7.235-12-18.9045 -1
GRID 975 0.492 0.246 -18.9045 -1
GRID 976 0.492 7.286-12-19.2045 -1
GRID 977 0.492 0.246 -19.2045 -1
GRID 978 0.492 7.337-12-19.5046 -1
GRID 979 0.492 0.246 -19.5046 -1
GRID 980 0.492 7.387-12-19.8047 -1
GRID 981 0.492 0.246 -19.8047 -1
GRID 982 0.492 7.438-12-20.1048 -1
GRID 983 0.492 0.246 -20.1048 -1
GRID 984 0.492 7.488-12-20.4048 -1
GRID 985 0.492 0.246 -20.4048 -1
GRID 986 0.492 7.539-12-20.7049 -1
GRID 987 0.492 0.246 -20.7049 -1
GRID 988 0.492 7.59-12 -21.005 -1
GRID 989 0.492 0.246 -21.005 -1
GRID 990 0.492 7.64-12 -21.3051 -1
GRID 991 0.492 0.246 -21.3051 -1
GRID 992 0.492 7.691-12-21.6051 -1
GRID 993 0.492 0.246 -21.6051 -1
GRID 994 0.492 7.742-12-21.9052 -1
GRID 995 0.492 0.246 -21.9052 -1
GRID 996 0.492 7.792-12-22.2053 -1
GRID 997 0.492 0.246 -22.2053 -1
GRID 998 0.492 7.843-12-22.5053 -1
GRID 999 0.492 0.246 -22.5053 -1
GRID 1000 0.492 7.893-12-22.8054 -1
GRID 1001 0.492 0.246 -22.8054 -1
GRID 1002 0.492 7.944-12-23.1055 -1
GRID 1003 0.492 0.246 -23.1055 -1
GRID 1004 0.492 7.995-12-23.4056 -1
GRID 1005 0.492 0.246 -23.4056 -1
GRID 1006 0.492 8.045-12-23.7056 -1
GRID 1007 0.492 0.246 -23.7056 -1
GRID 1008 0.492 8.096-12-24.0057 -1
GRID 1009 0.492 0.246 -24.0057 -1
GRID 1010 0.492 8.146-12-24.3058 -1
GRID 1011 0.492 0.246 -24.3058 -1
GRID 1012 0.492 8.197-12-24.6059 -1
GRID 1013 0.492 0.246 -24.6059 -1
GRID 1014 0.492 8.248-12-24.9059 -1
GRID 1015 0.492 0.246 -24.9059 -1
GRID 1016 0.492 5.534-12-25.206 -1
GRID 1017 0.492 0.246 -25.206 -1
GRID 1018 -5.24-130.492 -.300073 -1
GRID 1019 0.246 0.492 -.300073 -1
GRID 1020 -1.05-120.492 -.600146 -1
GRID 1021 0.246 0.492 -.600146 -1
GRID 1022 -1.57-120.492 -.900219 -1
GRID 1023 0.246 0.492 -0.90022 -1
GRID 1024 -2.09-120.492 -1.20029 -1
GRID 1025 0.246 0.492 -1.20029 -1

352 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1026 -2.63-120.492 -1.50037 -1
GRID 1027 0.246 0.492 -1.50037 -1
GRID 1028 -3.15-120.492 -1.80044 -1
GRID 1029 0.246 0.492 -1.80044 -1
GRID 1030 -3.67-120.492 -2.10051 -1
GRID 1031 0.246 0.492 -2.10051 -1
GRID 1032 -4.19-120.492 -2.40059 -1
GRID 1033 0.246 0.492 -2.40059 -1
GRID 1034 -4.72-120.492 -2.70066 -1
GRID 1035 0.246 0.492 -2.70066 -1
GRID 1036 -5.24-120.492 -3.00073 -1
GRID 1037 0.246 0.492 -3.00073 -1
GRID 1038 -5.76-120.492 -3.30081 -1
GRID 1039 0.246 0.492 -3.30081 -1
GRID 1040 -6.29-120.492 -3.60088 -1
GRID 1041 0.246 0.492 -3.60088 -1
GRID 1042 -6.81-120.492 -3.90095 -1
GRID 1043 0.246 0.492 -3.90095 -1
GRID 1044 -7.33-120.492 -4.20102 -1
GRID 1045 0.246 0.492 -4.20102 -1
GRID 1046 -7.87-120.492 -4.5011 -1
GRID 1047 0.246 0.492 -4.5011 -1
GRID 1048 -8.39-120.492 -4.80117 -1
GRID 1049 0.246 0.492 -4.80117 -1
GRID 1050 -8.91-120.492 -5.10124 -1
GRID 1051 0.246 0.492 -5.10124 -1
GRID 1052 -9.44-120.492 -5.40132 -1
GRID 1053 0.246 0.492 -5.40132 -1
GRID 1054 -9.96-120.492 -5.70139 -1
GRID 1055 0.246 0.492 -5.70139 -1
GRID 1056 -1.05-110.492 -6.00146 -1
GRID 1057 0.246 0.492 -6.00146 -1
GRID 1058 -1.1-11 0.492 -6.30154 -1
GRID 1059 0.246 0.492 -6.30154 -1
GRID 1060 -1.15-110.492 -6.60161 -1
GRID 1061 0.246 0.492 -6.60161 -1
GRID 1062 -1.2-11 0.492 -6.90168 -1
GRID 1063 0.246 0.492 -6.90168 -1
GRID 1064 -1.26-110.492 -7.20176 -1
GRID 1065 0.246 0.492 -7.20176 -1
GRID 1066 -1.31-110.492 -7.50183 -1
GRID 1067 0.246 0.492 -7.50183 -1
GRID 1068 -1.36-110.492 -7.8019 -1
GRID 1069 0.246 0.492 -7.8019 -1
GRID 1070 -1.41-110.492 -8.10198 -1
GRID 1071 0.246 0.492 -8.10198 -1
GRID 1072 -1.46-110.492 -8.40205 -1
GRID 1073 0.246 0.492 -8.40205 -1
GRID 1074 -1.52-110.492 -8.70212 -1
GRID 1075 0.246 0.492 -8.70212 -1
GRID 1076 -1.57-110.492 -9.0022 -1
GRID 1077 0.246 0.492 -9.0022 -1
GRID 1078 -1.62-110.492 -9.30227 -1
GRID 1079 0.246 0.492 -9.30227 -1
GRID 1080 -1.67-110.492 -9.60234 -1
GRID 1081 0.246 0.492 -9.60234 -1
GRID 1082 -1.73-110.492 -9.90241 -1
GRID 1083 0.246 0.492 -9.90241 -1
GRID 1084 -1.78-110.492 -10.2025 -1
GRID 1085 0.246 0.492 -10.2025 -1
GRID 1086 -1.83-110.492 -10.5026 -1
GRID 1087 0.246 0.492 -10.5026 -1
GRID 1088 -1.88-110.492 -10.8026 -1
GRID 1089 0.246 0.492 -10.8026 -1
GRID 1090 -1.94-110.492 -11.1027 -1
GRID 1091 0.246 0.492 -11.1027 -1
GRID 1092 -1.99-110.492 -11.4028 -1
GRID 1093 0.246 0.492 -11.4028 -1
GRID 1094 -2.04-110.492 -11.7029 -1

Altair Engineering OptiStruct 13.0 Reference Guide 353

Proprietary Information of Altair Engineering


GRID 1095 0.246 0.492 -11.7029 -1
GRID 1096 -2.09-110.492 -12.0029 -1
GRID 1097 0.246 0.492 -12.0029 -1
GRID 1098 -2.14-110.492 -12.303 -1
GRID 1099 0.246 0.492 -12.303 -1
GRID 1100 -2.2-11 0.492 -12.6031 -1
GRID 1101 0.246 0.492 -12.6031 -1
GRID 1262 -6.43-110.492 -12.903 -1
GRID 1263 0.246 0.492 -12.903 -1
GRID 1264 -6.49-110.492 -13.2031 -1
GRID 1265 0.246 0.492 -13.2031 -1
GRID 1266 -6.54-110.492 -13.5032 -1
GRID 1267 0.246 0.492 -13.5032 -1
GRID 1268 -6.59-110.492 -13.8032 -1
GRID 1269 0.246 0.492 -13.8032 -1
GRID 1270 -6.64-110.492 -14.1033 -1
GRID 1271 0.246 0.492 -14.1033 -1
GRID 1272 -6.71-110.492 -14.4034 -1
GRID 1273 0.246 0.492 -14.4034 -1
GRID 1274 -6.76-110.492 -14.7034 -1
GRID 1275 0.246 0.492 -14.7034 -1
GRID 1276 -6.81-110.492 -15.0035 -1
GRID 1277 0.246 0.492 -15.0035 -1
GRID 1278 -6.86-110.492 -15.3036 -1
GRID 1279 0.246 0.492 -15.3036 -1
GRID 1280 -6.91-110.492 -15.6037 -1
GRID 1281 0.246 0.492 -15.6037 -1
GRID 1282 -6.97-110.492 -15.9037 -1
GRID 1283 0.246 0.492 -15.9037 -1
GRID 1284 -7.02-110.492 -16.2038 -1
GRID 1285 0.246 0.492 -16.2038 -1
GRID 1286 -7.07-110.492 -16.5039 -1
GRID 1287 0.246 0.492 -16.5039 -1
GRID 1288 -7.12-110.492 -16.804 -1
GRID 1289 0.246 0.492 -16.804 -1
GRID 1290 -7.18-110.492 -17.104 -1
GRID 1291 0.246 0.492 -17.104 -1
GRID 1292 -7.23-110.492 -17.4041 -1
GRID 1293 0.246 0.492 -17.4041 -1
GRID 1294 -7.28-110.492 -17.7042 -1
GRID 1295 0.246 0.492 -17.7042 -1
GRID 1296 -7.33-110.492 -18.0042 -1
GRID 1297 0.246 0.492 -18.0042 -1
GRID 1298 -7.39-110.492 -18.3043 -1
GRID 1299 0.246 0.492 -18.3043 -1
GRID 1300 -7.44-110.492 -18.6044 -1
GRID 1301 0.246 0.492 -18.6044 -1
GRID 1302 -7.49-110.492 -18.9045 -1
GRID 1303 0.246 0.492 -18.9045 -1
GRID 1304 -7.54-110.492 -19.2045 -1
GRID 1305 0.246 0.492 -19.2045 -1
GRID 1306 -7.59-110.492 -19.5046 -1
GRID 1307 0.246 0.492 -19.5046 -1
GRID 1308 -7.65-110.492 -19.8047 -1
GRID 1309 0.246 0.492 -19.8047 -1
GRID 1310 -7.7-11 0.492 -20.1048 -1
GRID 1311 0.246 0.492 -20.1048 -1
GRID 1312 -7.75-110.492 -20.4048 -1
GRID 1313 0.246 0.492 -20.4048 -1
GRID 1314 -7.8-11 0.492 -20.7049 -1
GRID 1315 0.246 0.492 -20.7049 -1
GRID 1316 -7.86-110.492 -21.005 -1
GRID 1317 0.246 0.492 -21.005 -1
GRID 1318 -7.91-110.492 -21.3051 -1
GRID 1319 0.246 0.492 -21.3051 -1
GRID 1320 -7.96-110.492 -21.6051 -1
GRID 1321 0.246 0.492 -21.6051 -1
GRID 1322 -8.01-110.492 -21.9052 -1
GRID 1323 0.246 0.492 -21.9052 -1

354 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1324 -8.07-110.492 -22.2053 -1
GRID 1325 0.246 0.492 -22.2053 -1
GRID 1326 -8.12-110.492 -22.5053 -1
GRID 1327 0.246 0.492 -22.5053 -1
GRID 1328 -8.17-110.492 -22.8054 -1
GRID 1329 0.246 0.492 -22.8054 -1
GRID 1330 -8.22-110.492 -23.1055 -1
GRID 1331 0.246 0.492 -23.1055 -1
GRID 1332 -8.27-110.492 -23.4056 -1
GRID 1333 0.246 0.492 -23.4056 -1
GRID 1334 -8.33-110.492 -23.7056 -1
GRID 1335 0.246 0.492 -23.7056 -1
GRID 1336 -8.38-110.492 -24.0057 -1
GRID 1337 0.246 0.492 -24.0057 -1
GRID 1338 -8.43-110.492 -24.3058 -1
GRID 1339 0.246 0.492 -24.3058 -1
GRID 1340 -8.48-110.492 -24.6059 -1
GRID 1341 0.246 0.492 -24.6059 -1
GRID 1342 -8.54-110.492 -24.9059 -1
GRID 1343 0.246 0.492 -24.9059 -1
GRID 1344 -8.59-110.492 -25.206 -1
GRID 1345 0.246 0.492 -25.206 -1
GRID 1346 0.492 0.492 -.300073 -1
GRID 1347 0.492 0.492 -.600146 -1
GRID 1348 0.492 0.492 -0.90022 -1
GRID 1349 0.492 0.492 -1.20029 -1
GRID 1350 0.492 0.492 -1.50037 -1
GRID 1351 0.492 0.492 -1.80044 -1
GRID 1352 0.492 0.492 -2.10051 -1
GRID 1353 0.492 0.492 -2.40059 -1
GRID 1354 0.492 0.492 -2.70066 -1
GRID 1355 0.492 0.492 -3.00073 -1
GRID 1356 0.492 0.492 -3.30081 -1
GRID 1357 0.492 0.492 -3.60088 -1
GRID 1358 0.492 0.492 -3.90095 -1
GRID 1359 0.492 0.492 -4.20102 -1
GRID 1360 0.492 0.492 -4.5011 -1
GRID 1361 0.492 0.492 -4.80117 -1
GRID 1362 0.492 0.492 -5.10124 -1
GRID 1363 0.492 0.492 -5.40132 -1
GRID 1364 0.492 0.492 -5.70139 -1
GRID 1365 0.492 0.492 -6.00146 -1
GRID 1366 0.492 0.492 -6.30154 -1
GRID 1367 0.492 0.492 -6.60161 -1
GRID 1368 0.492 0.492 -6.90168 -1
GRID 1369 0.492 0.492 -7.20176 -1
GRID 1370 0.492 0.492 -7.50183 -1
GRID 1371 0.492 0.492 -7.8019 -1
GRID 1372 0.492 0.492 -8.10198 -1
GRID 1373 0.492 0.492 -8.40205 -1
GRID 1374 0.492 0.492 -8.70212 -1
GRID 1375 0.492 0.492 -9.0022 -1
GRID 1376 0.492 0.492 -9.30227 -1
GRID 1377 0.492 0.492 -9.60234 -1
GRID 1378 0.492 0.492 -9.90242 -1
GRID 1379 0.492 0.492 -10.2025 -1
GRID 1380 0.492 0.492 -10.5026 -1
GRID 1381 0.492 0.492 -10.8026 -1
GRID 1382 0.492 0.492 -11.1027 -1
GRID 1383 0.492 0.492 -11.4028 -1
GRID 1384 0.492 0.492 -11.7029 -1
GRID 1385 0.492 0.492 -12.0029 -1
GRID 1386 0.492 0.492 -12.303 -1
GRID 1387 0.492 0.492 -12.6031 -1
GRID 1468 0.492 0.492 -12.903 -1
GRID 1469 0.492 0.492 -13.2031 -1
GRID 1470 0.492 0.492 -13.5032 -1
GRID 1471 0.492 0.492 -13.8032 -1
GRID 1472 0.492 0.492 -14.1033 -1

Altair Engineering OptiStruct 13.0 Reference Guide 355

Proprietary Information of Altair Engineering


GRID 1473 0.492 0.492 -14.4034 -1
GRID 1474 0.492 0.492 -14.7034 -1
GRID 1475 0.492 0.492 -15.0035 -1
GRID 1476 0.492 0.492 -15.3036 -1
GRID 1477 0.492 0.492 -15.6037 -1
GRID 1478 0.492 0.492 -15.9037 -1
GRID 1479 0.492 0.492 -16.2038 -1
GRID 1480 0.492 0.492 -16.5039 -1
GRID 1481 0.492 0.492 -16.804 -1
GRID 1482 0.492 0.492 -17.104 -1
GRID 1483 0.492 0.492 -17.4041 -1
GRID 1484 0.492 0.492 -17.7042 -1
GRID 1485 0.492 0.492 -18.0042 -1
GRID 1486 0.492 0.492 -18.3043 -1
GRID 1487 0.492 0.492 -18.6044 -1
GRID 1488 0.492 0.492 -18.9045 -1
GRID 1489 0.492 0.492 -19.2045 -1
GRID 1490 0.492 0.492 -19.5046 -1
GRID 1491 0.492 0.492 -19.8047 -1
GRID 1492 0.492 0.492 -20.1048 -1
GRID 1493 0.492 0.492 -20.4048 -1
GRID 1494 0.492 0.492 -20.7049 -1
GRID 1495 0.492 0.492 -21.005 -1
GRID 1496 0.492 0.492 -21.3051 -1
GRID 1497 0.492 0.492 -21.6051 -1
GRID 1498 0.492 0.492 -21.9052 -1
GRID 1499 0.492 0.492 -22.2053 -1
GRID 1500 0.492 0.492 -22.5053 -1
GRID 1501 0.492 0.492 -22.8054 -1
GRID 1502 0.492 0.492 -23.1055 -1
GRID 1503 0.492 0.492 -23.4056 -1
GRID 1504 0.492 0.492 -23.7056 -1
GRID 1505 0.492 0.492 -24.0057 -1
GRID 1506 0.492 0.492 -24.3058 -1
GRID 1507 0.492 0.492 -24.6059 -1
GRID 1508 0.492 0.492 -24.9059 -1
GRID 1509 0.492 0.492 -25.206 -1
GRID 1510 -0.246 0.0 -.300073 -1
GRID 1511 -0.492 8.522-26-.300073 -1
GRID 1512 -0.492 0.246 -.300073 -1
GRID 1513 -0.246 0.246 -.300073 -1
GRID 1514 -0.246 0.0 -.600146 -1
GRID 1515 -0.492 1.441-26-.600146 -1
GRID 1516 -0.492 0.246 -.600146 -1
GRID 1517 -0.246 0.246 -.600146 -1
GRID 1518 -0.246 0.0 -.900219 -1
GRID 1519 -0.492 2.685-27-.900219 -1
GRID 1520 -0.492 0.246 -.900219 -1
GRID 1521 -0.246 0.246 -.900219 -1
GRID 1522 -0.246 0.0 -1.20029 -1
GRID 1523 -0.492 8.709-28-1.20029 -1
GRID 1524 -0.492 0.246 -1.20029 -1
GRID 1525 -0.246 0.246 -1.20029 -1
GRID 1526 -0.246 0.0 -1.50037 -1
GRID 1527 -0.492 6.595-28-1.50037 -1
GRID 1528 -0.492 0.246 -1.50037 -1
GRID 1529 -0.246 0.246 -1.50037 -1
GRID 1530 -0.246 0.0 -1.80044 -1
GRID 1531 -0.492 7.258-28-1.80044 -1
GRID 1532 -0.492 0.246 -1.80044 -1
GRID 1533 -0.246 0.246 -1.80044 -1
GRID 1534 -0.246 0.0 -2.10051 -1
GRID 1535 -0.492 7.936-28-2.10051 -1
GRID 1536 -0.492 0.246 -2.10051 -1
GRID 1537 -0.246 0.246 -2.10051 -1
GRID 1538 -0.246 0.0 -2.40058 -1
GRID 1539 -0.492 8.993-28-2.40058 -1
GRID 1540 -0.492 0.246 -2.40058 -1
GRID 1541 -0.246 0.246 -2.40058 -1

356 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1542 -0.246 0.0 -2.70066 -1
GRID 1543 -0.492 1.01-27 -2.70066 -1
GRID 1544 -0.492 0.246 -2.70066 -1
GRID 1545 -0.246 0.246 -2.70066 -1
GRID 1546 -0.246 0.0 -3.00073 -1
GRID 1547 -0.492 1.185-27-3.00073 -1
GRID 1548 -0.492 0.246 -3.00073 -1
GRID 1549 -0.246 0.246 -3.00073 -1
GRID 1550 -0.246 0.0 -3.3008 -1
GRID 1551 -0.492 1.313-27-3.3008 -1
GRID 1552 -0.492 0.246 -3.3008 -1
GRID 1553 -0.246 0.246 -3.3008 -1
GRID 1554 -0.246 0.0 -3.60088 -1
GRID 1555 -0.492 1.341-27-3.60088 -1
GRID 1556 -0.492 0.246 -3.60088 -1
GRID 1557 -0.246 0.246 -3.60088 -1
GRID 1558 -0.246 0.0 -3.90095 -1
GRID 1559 -0.492 1.36-27 -3.90095 -1
GRID 1560 -0.492 0.246 -3.90095 -1
GRID 1561 -0.246 0.246 -3.90095 -1
GRID 1562 -0.246 0.0 -4.20102 -1
GRID 1563 -0.492 1.447-27-4.20102 -1
GRID 1564 -0.492 0.246 -4.20102 -1
GRID 1565 -0.246 0.246 -4.20102 -1
GRID 1566 -0.246 0.0 -4.5011 -1
GRID 1567 -0.492 1.549-27-4.5011 -1
GRID 1568 -0.492 0.246 -4.5011 -1
GRID 1569 -0.246 0.246 -4.5011 -1
GRID 1570 -0.246 0.0 -4.80117 -1
GRID 1571 -0.492 1.775-27-4.80117 -1
GRID 1572 -0.492 0.246 -4.80117 -1
GRID 1573 -0.246 0.246 -4.80117 -1
GRID 1574 -0.246 0.0 -5.10124 -1
GRID 1575 -0.492 1.907-27-5.10124 -1
GRID 1576 -0.492 0.246 -5.10124 -1
GRID 1577 -0.246 0.246 -5.10124 -1
GRID 1578 -0.246 0.0 -5.40132 -1
GRID 1579 -0.492 2.023-27-5.40132 -1
GRID 1580 -0.492 0.246 -5.40132 -1
GRID 1581 -0.246 0.246 -5.40132 -1
GRID 1582 -0.246 0.0 -5.70139 -1
GRID 1583 -0.492 2.136-27-5.70139 -1
GRID 1584 -0.492 0.246 -5.70139 -1
GRID 1585 -0.246 0.246 -5.70139 -1
GRID 1586 -0.246 0.0 -6.00146 -1
GRID 1587 -0.492 2.248-27-6.00146 -1
GRID 1588 -0.492 0.246 -6.00146 -1
GRID 1589 -0.246 0.246 -6.00146 -1
GRID 1590 -0.246 0.0 -6.30154 -1
GRID 1591 -0.492 2.36-27 -6.30154 -1
GRID 1592 -0.492 0.246 -6.30154 -1
GRID 1593 -0.246 0.246 -6.30154 -1
GRID 1594 -0.246 0.0 -6.60161 -1
GRID 1595 -0.492 2.474-27-6.60161 -1
GRID 1596 -0.492 0.246 -6.60161 -1
GRID 1597 -0.246 0.246 -6.60161 -1
GRID 1598 -0.246 0.0 -6.90168 -1
GRID 1599 -0.492 2.551-27-6.90168 -1
GRID 1600 -0.492 0.246 -6.90168 -1
GRID 1601 -0.246 0.246 -6.90168 -1
GRID 1602 -0.246 0.0 -7.20176 -1
GRID 1603 -0.492 2.693-27-7.20176 -1
GRID 1604 -0.492 0.246 -7.20176 -1
GRID 1605 -0.246 0.246 -7.20176 -1
GRID 1606 -0.246 0.0 -7.50183 -1
GRID 1607 -0.492 2.965-27-7.50183 -1
GRID 1608 -0.492 0.246 -7.50183 -1
GRID 1609 -0.246 0.246 -7.50183 -1
GRID 1610 -0.246 0.0 -7.8019 -1

Altair Engineering OptiStruct 13.0 Reference Guide 357

Proprietary Information of Altair Engineering


GRID 1611 -0.492 3.113-27-7.8019 -1
GRID 1612 -0.492 0.246 -7.8019 -1
GRID 1613 -0.246 0.246 -7.8019 -1
GRID 1614 -0.246 0.0 -8.10198 -1
GRID 1615 -0.492 3.067-27-8.10198 -1
GRID 1616 -0.492 0.246 -8.10198 -1
GRID 1617 -0.246 0.246 -8.10198 -1
GRID 1618 -0.246 0.0 -8.40205 -1
GRID 1619 -0.492 2.979-27-8.40205 -1
GRID 1620 -0.492 0.246 -8.40205 -1
GRID 1621 -0.246 0.246 -8.40205 -1
GRID 1622 -0.246 0.0 -8.70212 -1
GRID 1623 -0.492 3.233-27-8.70212 -1
GRID 1624 -0.492 0.246 -8.70212 -1
GRID 1625 -0.246 0.246 -8.70212 -1
GRID 1626 -0.246 0.0 -9.0022 -1
GRID 1627 -0.492 3.323-27-9.00219 -1
GRID 1628 -0.492 0.246 -9.00219 -1
GRID 1629 -0.246 0.246 -9.0022 -1
GRID 1630 -0.246 0.0 -9.30227 -1
GRID 1631 -0.492 3.67-27 -9.30227 -1
GRID 1632 -0.492 0.246 -9.30227 -1
GRID 1633 -0.246 0.246 -9.30227 -1
GRID 1634 -0.246 0.0 -9.60234 -1
GRID 1635 -0.492 3.58-27 -9.60234 -1
GRID 1636 -0.492 0.246 -9.60234 -1
GRID 1637 -0.246 0.246 -9.60234 -1
GRID 1638 -0.246 0.0 -9.90241 -1
GRID 1639 -0.492 3.454-27-9.90241 -1
GRID 1640 -0.492 0.246 -9.90241 -1
GRID 1641 -0.246 0.246 -9.90241 -1
GRID 1642 -0.246 0.0 -10.2025 -1
GRID 1643 -0.492 3.782-27-10.2025 -1
GRID 1644 -0.492 0.246 -10.2025 -1
GRID 1645 -0.246 0.246 -10.2025 -1
GRID 1646 -0.246 0.0 -10.5026 -1
GRID 1647 -0.492 3.659-27-10.5026 -1
GRID 1648 -0.492 0.246 -10.5026 -1
GRID 1649 -0.246 0.246 -10.5026 -1
GRID 1650 -0.246 0.0 -10.8026 -1
GRID 1651 -0.492 4.003-27-10.8026 -1
GRID 1652 -0.492 0.246 -10.8026 -1
GRID 1653 -0.246 0.246 -10.8026 -1
GRID 1654 -0.246 0.0 -11.1027 -1
GRID 1655 -0.492 4.154-27-11.1027 -1
GRID 1656 -0.492 0.246 -11.1027 -1
GRID 1657 -0.246 0.246 -11.1027 -1
GRID 1658 -0.246 0.0 -11.4028 -1
GRID 1659 -0.492 4.274-27-11.4028 -1
GRID 1660 -0.492 0.246 -11.4028 -1
GRID 1661 -0.246 0.246 -11.4028 -1
GRID 1662 -0.246 0.0 -11.7029 -1
GRID 1663 -0.492 4.388-27-11.7028 -1
GRID 1664 -0.492 0.246 -11.7028 -1
GRID 1665 -0.246 0.246 -11.7029 -1
GRID 1666 -0.246 0.0 -12.0029 -1
GRID 1667 -0.492 4.5-27 -12.0029 -1
GRID 1668 -0.492 0.246 -12.0029 -1
GRID 1669 -0.246 0.246 -12.0029 -1
GRID 1670 -0.246 0.0 -12.303 -1
GRID 1671 -0.492 4.358-27-12.303 -1
GRID 1672 -0.492 0.246 -12.303 -1
GRID 1673 -0.246 0.246 -12.303 -1
GRID 1674 -0.246 0.0 -12.6031 -1
GRID 1675 -0.492 4.424-27-12.6031 -1
GRID 1676 -0.492 0.246 -12.6031 -1
GRID 1677 -0.246 0.246 -12.6031 -1
GRID 1998 -0.246 0.0 -12.903 -1
GRID 1999 -0.492 1.381-26-12.903 -1

358 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 2000 -0.492 0.246 -12.903 -1
GRID 2001 -0.246 0.246 -12.903 -1
GRID 2002 -0.246 0.0 -13.2031 -1
GRID 2003 -0.492 1.395-26-13.2031 -1
GRID 2004 -0.492 0.246 -13.2031 -1
GRID 2005 -0.246 0.246 -13.2031 -1
GRID 2006 -0.246 0.0 -13.5032 -1
GRID 2007 -0.492 1.407-26-13.5031 -1
GRID 2008 -0.492 0.246 -13.5031 -1
GRID 2009 -0.246 0.246 -13.5032 -1
GRID 2010 -0.246 0.0 -13.8032 -1
GRID 2011 -0.492 1.418-26-13.8032 -1
GRID 2012 -0.492 0.246 -13.8032 -1
GRID 2013 -0.246 0.246 -13.8032 -1
GRID 2014 -0.246 0.0 -14.1033 -1
GRID 2015 -0.492 1.429-26-14.1033 -1
GRID 2016 -0.492 0.246 -14.1033 -1
GRID 2017 -0.246 0.246 -14.1033 -1
GRID 2018 -0.246 0.0 -14.4034 -1
GRID 2019 -0.492 1.441-26-14.4034 -1
GRID 2020 -0.492 0.246 -14.4034 -1
GRID 2021 -0.246 0.246 -14.4034 -1
GRID 2022 -0.246 0.0 -14.7034 -1
GRID 2023 -0.492 1.452-26-14.7034 -1
GRID 2024 -0.492 0.246 -14.7034 -1
GRID 2025 -0.246 0.246 -14.7034 -1
GRID 2026 -0.246 0.0 -15.0035 -1
GRID 2027 -0.492 1.463-26-15.0035 -1
GRID 2028 -0.492 0.246 -15.0035 -1
GRID 2029 -0.246 0.246 -15.0035 -1
GRID 2030 -0.246 0.0 -15.3036 -1
GRID 2031 -0.492 1.454-26-15.3036 -1
GRID 2032 -0.492 0.246 -15.3036 -1
GRID 2033 -0.246 0.246 -15.3036 -1
GRID 2034 -0.246 0.0 -15.6037 -1
GRID 2035 -0.492 1.38-26 -15.6037 -1
GRID 2036 -0.492 0.246 -15.6037 -1
GRID 2037 -0.246 0.246 -15.6037 -1
GRID 2038 -0.246 0.0 -15.9037 -1
GRID 2039 -0.492 1.479-26-15.9037 -1
GRID 2040 -0.492 0.246 -15.9037 -1
GRID 2041 -0.246 0.246 -15.9037 -1
GRID 2042 -0.246 0.0 -16.2038 -1
GRID 2043 -0.492 1.505-26-16.2038 -1
GRID 2044 -0.492 0.246 -16.2038 -1
GRID 2045 -0.246 0.246 -16.2038 -1
GRID 2046 -0.246 0.0 -16.5039 -1
GRID 2047 -0.492 1.519-26-16.5039 -1
GRID 2048 -0.492 0.246 -16.5039 -1
GRID 2049 -0.246 0.246 -16.5039 -1
GRID 2050 -0.246 0.0 -16.804 -1
GRID 2051 -0.492 1.531-26-16.804 -1
GRID 2052 -0.492 0.246 -16.804 -1
GRID 2053 -0.246 0.246 -16.804 -1
GRID 2054 -0.246 0.0 -17.104 -1
GRID 2055 -0.492 1.542-26-17.104 -1
GRID 2056 -0.492 0.246 -17.104 -1
GRID 2057 -0.246 0.246 -17.104 -1
GRID 2058 -0.246 0.0 -17.4041 -1
GRID 2059 -0.492 1.553-26-17.4041 -1
GRID 2060 -0.492 0.246 -17.4041 -1
GRID 2061 -0.246 0.246 -17.4041 -1
GRID 2062 -0.246 0.0 -17.7042 -1
GRID 2063 -0.492 1.564-26-17.7042 -1
GRID 2064 -0.492 0.246 -17.7042 -1
GRID 2065 -0.246 0.246 -17.7042 -1
GRID 2066 -0.246 0.0 -18.0042 -1
GRID 2067 -0.492 1.576-26-18.0042 -1
GRID 2068 -0.492 0.246 -18.0042 -1

Altair Engineering OptiStruct 13.0 Reference Guide 359

Proprietary Information of Altair Engineering


GRID 2069 -0.246 0.246 -18.0042 -1
GRID 2070 -0.246 0.0 -18.3043 -1
GRID 2071 -0.492 1.477-26-18.3043 -1
GRID 2072 -0.492 0.246 -18.3043 -1
GRID 2073 -0.246 0.246 -18.3043 -1
GRID 2074 -0.246 0.0 -18.6044 -1
GRID 2075 -0.492 1.58-26 -18.6044 -1
GRID 2076 -0.492 0.246 -18.6044 -1
GRID 2077 -0.246 0.246 -18.6044 -1
GRID 2078 -0.246 0.0 -18.9045 -1
GRID 2079 -0.492 1.606-26-18.9045 -1
GRID 2080 -0.492 0.246 -18.9045 -1
GRID 2081 -0.246 0.246 -18.9045 -1
GRID 2082 -0.246 0.0 -19.2045 -1
GRID 2083 -0.492 1.62-26 -19.2045 -1
GRID 2084 -0.492 0.246 -19.2045 -1
GRID 2085 -0.246 0.246 -19.2045 -1
GRID 2086 -0.246 0.0 -19.5046 -1
GRID 2087 -0.492 1.632-26-19.5046 -1
GRID 2088 -0.492 0.246 -19.5046 -1
GRID 2089 -0.246 0.246 -19.5046 -1
GRID 2090 -0.246 0.0 -19.8047 -1
GRID 2091 -0.492 1.643-26-19.8047 -1
GRID 2092 -0.492 0.246 -19.8047 -1
GRID 2093 -0.246 0.246 -19.8047 -1
GRID 2094 -0.246 0.0 -20.1048 -1
GRID 2095 -0.492 1.655-26-20.1048 -1
GRID 2096 -0.492 0.246 -20.1048 -1
GRID 2097 -0.246 0.246 -20.1048 -1
GRID 2098 -0.246 0.0 -20.4048 -1
GRID 2099 -0.492 1.666-26-20.4048 -1
GRID 2100 -0.492 0.246 -20.4048 -1
GRID 2101 -0.246 0.246 -20.4048 -1
GRID 2102 -0.246 0.0 -20.7049 -1
GRID 2103 -0.492 1.677-26-20.7049 -1
GRID 2104 -0.492 0.246 -20.7049 -1
GRID 2105 -0.246 0.246 -20.7049 -1
GRID 2106 -0.246 0.0 -21.005 -1
GRID 2107 -0.492 1.572-26-21.005 -1
GRID 2108 -0.492 0.246 -21.005 -1
GRID 2109 -0.246 0.246 -21.005 -1
GRID 2110 -0.246 0.0 -21.3051 -1
GRID 2111 -0.492 1.68-26 -21.3051 -1
GRID 2112 -0.492 0.246 -21.3051 -1
GRID 2113 -0.246 0.246 -21.3051 -1
GRID 2114 -0.246 0.0 -21.6051 -1
GRID 2115 -0.492 1.708-26-21.6051 -1
GRID 2116 -0.492 0.246 -21.6051 -1
GRID 2117 -0.246 0.246 -21.6051 -1
GRID 2118 -0.246 0.0 -21.9052 -1
GRID 2119 -0.492 1.722-26-21.9052 -1
GRID 2120 -0.492 0.246 -21.9052 -1
GRID 2121 -0.246 0.246 -21.9052 -1
GRID 2122 -0.246 0.0 -22.2053 -1
GRID 2123 -0.492 1.733-26-22.2053 -1
GRID 2124 -0.492 0.246 -22.2053 -1
GRID 2125 -0.246 0.246 -22.2053 -1
GRID 2126 -0.246 0.0 -22.5053 -1
GRID 2127 -0.492 1.745-26-22.5053 -1
GRID 2128 -0.492 0.246 -22.5053 -1
GRID 2129 -0.246 0.246 -22.5053 -1
GRID 2130 -0.246 0.0 -22.8054 -1
GRID 2131 -0.492 1.756-26-22.8054 -1
GRID 2132 -0.492 0.246 -22.8054 -1
GRID 2133 -0.246 0.246 -22.8054 -1
GRID 2134 -0.246 0.0 -23.1055 -1
GRID 2135 -0.492 1.767-26-23.1055 -1
GRID 2136 -0.492 0.246 -23.1055 -1
GRID 2137 -0.246 0.246 -23.1055 -1

360 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 2138 -0.246 0.0 -23.4056 -1
GRID 2139 -0.492 1.778-26-23.4056 -1
GRID 2140 -0.492 0.246 -23.4056 -1
GRID 2141 -0.246 0.246 -23.4056 -1
GRID 2142 -0.246 0.0 -23.7056 -1
GRID 2143 -0.492 1.666-26-23.7056 -1
GRID 2144 -0.492 0.246 -23.7056 -1
GRID 2145 -0.246 0.246 -23.7056 -1
GRID 2146 -0.246 0.0 -24.0057 -1
GRID 2147 -0.492 1.78-26 -24.0057 -1
GRID 2148 -0.492 0.246 -24.0057 -1
GRID 2149 -0.246 0.246 -24.0057 -1
GRID 2150 -0.246 0.0 -24.3058 -1
GRID 2151 -0.492 1.809-26-24.3058 -1
GRID 2152 -0.492 0.246 -24.3058 -1
GRID 2153 -0.246 0.246 -24.3058 -1
GRID 2154 -0.246 0.0 -24.6059 -1
GRID 2155 -0.492 1.823-26-24.6059 -1
GRID 2156 -0.492 0.246 -24.6059 -1
GRID 2157 -0.246 0.246 -24.6059 -1
GRID 2158 -0.246 0.0 -24.9059 -1
GRID 2159 -0.492 1.835-26-24.9059 -1
GRID 2160 -0.492 0.246 -24.9059 -1
GRID 2161 -0.246 0.246 -24.9059 -1
GRID 2162 -0.246 1.384-12-25.206 -1
GRID 2163 -0.492 1.272-26-25.206 -1
GRID 2164 -0.492 0.246 -25.206 -1
GRID 2165 -0.246 0.246 -25.206 -1
GRID 2166 -0.492 0.492 -.300073 -1
GRID 2167 -0.246 0.492 -.300073 -1
GRID 2168 -0.492 0.492 -.600146 -1
GRID 2169 -0.246 0.492 -.600146 -1
GRID 2170 -0.492 0.492 -.900219 -1
GRID 2171 -0.246 0.492 -.900219 -1
GRID 2172 -0.492 0.492 -1.20029 -1
GRID 2173 -0.246 0.492 -1.20029 -1
GRID 2174 -0.492 0.492 -1.50037 -1
GRID 2175 -0.246 0.492 -1.50037 -1
GRID 2176 -0.492 0.492 -1.80044 -1
GRID 2177 -0.246 0.492 -1.80044 -1
GRID 2178 -0.492 0.492 -2.10051 -1
GRID 2179 -0.246 0.492 -2.10051 -1
GRID 2180 -0.492 0.492 -2.40058 -1
GRID 2181 -0.246 0.492 -2.40058 -1
GRID 2182 -0.492 0.492 -2.70066 -1
GRID 2183 -0.246 0.492 -2.70066 -1
GRID 2184 -0.492 0.492 -3.00073 -1
GRID 2185 -0.246 0.492 -3.00073 -1
GRID 2186 -0.492 0.492 -3.3008 -1
GRID 2187 -0.246 0.492 -3.3008 -1
GRID 2188 -0.492 0.492 -3.60088 -1
GRID 2189 -0.246 0.492 -3.60088 -1
GRID 2190 -0.492 0.492 -3.90095 -1
GRID 2191 -0.246 0.492 -3.90095 -1
GRID 2192 -0.492 0.492 -4.20102 -1
GRID 2193 -0.246 0.492 -4.20102 -1
GRID 2194 -0.492 0.492 -4.5011 -1
GRID 2195 -0.246 0.492 -4.5011 -1
GRID 2196 -0.492 0.492 -4.80117 -1
GRID 2197 -0.246 0.492 -4.80117 -1
GRID 2198 -0.492 0.492 -5.10124 -1
GRID 2199 -0.246 0.492 -5.10124 -1
GRID 2200 -0.492 0.492 -5.40132 -1
GRID 2201 -0.246 0.492 -5.40132 -1
GRID 2202 -0.492 0.492 -5.70139 -1
GRID 2203 -0.246 0.492 -5.70139 -1
GRID 2204 -0.492 0.492 -6.00146 -1
GRID 2205 -0.246 0.492 -6.00146 -1
GRID 2206 -0.492 0.492 -6.30154 -1

Altair Engineering OptiStruct 13.0 Reference Guide 361

Proprietary Information of Altair Engineering


GRID 2207 -0.246 0.492 -6.30154 -1
GRID 2208 -0.492 0.492 -6.60161 -1
GRID 2209 -0.246 0.492 -6.60161 -1
GRID 2210 -0.492 0.492 -6.90168 -1
GRID 2211 -0.246 0.492 -6.90168 -1
GRID 2212 -0.492 0.492 -7.20176 -1
GRID 2213 -0.246 0.492 -7.20176 -1
GRID 2214 -0.492 0.492 -7.50183 -1
GRID 2215 -0.246 0.492 -7.50183 -1
GRID 2216 -0.492 0.492 -7.8019 -1
GRID 2217 -0.246 0.492 -7.8019 -1
GRID 2218 -0.492 0.492 -8.10198 -1
GRID 2219 -0.246 0.492 -8.10198 -1
GRID 2220 -0.492 0.492 -8.40205 -1
GRID 2221 -0.246 0.492 -8.40205 -1
GRID 2222 -0.492 0.492 -8.70212 -1
GRID 2223 -0.246 0.492 -8.70212 -1
GRID 2224 -0.492 0.492 -9.00219 -1
GRID 2225 -0.246 0.492 -9.0022 -1
GRID 2226 -0.492 0.492 -9.30227 -1
GRID 2227 -0.246 0.492 -9.30227 -1
GRID 2228 -0.492 0.492 -9.60234 -1
GRID 2229 -0.246 0.492 -9.60234 -1
GRID 2230 -0.492 0.492 -9.90241 -1
GRID 2231 -0.246 0.492 -9.90241 -1
GRID 2232 -0.492 0.492 -10.2025 -1
GRID 2233 -0.246 0.492 -10.2025 -1
GRID 2234 -0.492 0.492 -10.5026 -1
GRID 2235 -0.246 0.492 -10.5026 -1
GRID 2236 -0.492 0.492 -10.8026 -1
GRID 2237 -0.246 0.492 -10.8026 -1
GRID 2238 -0.492 0.492 -11.1027 -1
GRID 2239 -0.246 0.492 -11.1027 -1
GRID 2240 -0.492 0.492 -11.4028 -1
GRID 2241 -0.246 0.492 -11.4028 -1
GRID 2242 -0.492 0.492 -11.7028 -1
GRID 2243 -0.246 0.492 -11.7029 -1
GRID 2244 -0.492 0.492 -12.0029 -1
GRID 2245 -0.246 0.492 -12.0029 -1
GRID 2246 -0.492 0.492 -12.303 -1
GRID 2247 -0.246 0.492 -12.303 -1
GRID 2248 -0.492 0.492 -12.6031 -1
GRID 2249 -0.246 0.492 -12.6031 -1
GRID 2410 -0.492 0.492 -12.903 -1
GRID 2411 -0.246 0.492 -12.903 -1
GRID 2412 -0.492 0.492 -13.2031 -1
GRID 2413 -0.246 0.492 -13.2031 -1
GRID 2414 -0.492 0.492 -13.5031 -1
GRID 2415 -0.246 0.492 -13.5032 -1
GRID 2416 -0.492 0.492 -13.8032 -1
GRID 2417 -0.246 0.492 -13.8032 -1
GRID 2418 -0.492 0.492 -14.1033 -1
GRID 2419 -0.246 0.492 -14.1033 -1
GRID 2420 -0.492 0.492 -14.4034 -1
GRID 2421 -0.246 0.492 -14.4034 -1
GRID 2422 -0.492 0.492 -14.7034 -1
GRID 2423 -0.246 0.492 -14.7034 -1
GRID 2424 -0.492 0.492 -15.0035 -1
GRID 2425 -0.246 0.492 -15.0035 -1
GRID 2426 -0.492 0.492 -15.3036 -1
GRID 2427 -0.246 0.492 -15.3036 -1
GRID 2428 -0.492 0.492 -15.6037 -1
GRID 2429 -0.246 0.492 -15.6037 -1
GRID 2430 -0.492 0.492 -15.9037 -1
GRID 2431 -0.246 0.492 -15.9037 -1
GRID 2432 -0.492 0.492 -16.2038 -1
GRID 2433 -0.246 0.492 -16.2038 -1
GRID 2434 -0.492 0.492 -16.5039 -1
GRID 2435 -0.246 0.492 -16.5039 -1

362 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 2436 -0.492 0.492 -16.804 -1
GRID 2437 -0.246 0.492 -16.804 -1
GRID 2438 -0.492 0.492 -17.104 -1
GRID 2439 -0.246 0.492 -17.104 -1
GRID 2440 -0.492 0.492 -17.4041 -1
GRID 2441 -0.246 0.492 -17.4041 -1
GRID 2442 -0.492 0.492 -17.7042 -1
GRID 2443 -0.246 0.492 -17.7042 -1
GRID 2444 -0.492 0.492 -18.0042 -1
GRID 2445 -0.246 0.492 -18.0042 -1
GRID 2446 -0.492 0.492 -18.3043 -1
GRID 2447 -0.246 0.492 -18.3043 -1
GRID 2448 -0.492 0.492 -18.6044 -1
GRID 2449 -0.246 0.492 -18.6044 -1
GRID 2450 -0.492 0.492 -18.9045 -1
GRID 2451 -0.246 0.492 -18.9045 -1
GRID 2452 -0.492 0.492 -19.2045 -1
GRID 2453 -0.246 0.492 -19.2045 -1
GRID 2454 -0.492 0.492 -19.5046 -1
GRID 2455 -0.246 0.492 -19.5046 -1
GRID 2456 -0.492 0.492 -19.8047 -1
GRID 2457 -0.246 0.492 -19.8047 -1
GRID 2458 -0.492 0.492 -20.1048 -1
GRID 2459 -0.246 0.492 -20.1048 -1
GRID 2460 -0.492 0.492 -20.4048 -1
GRID 2461 -0.246 0.492 -20.4048 -1
GRID 2462 -0.492 0.492 -20.7049 -1
GRID 2463 -0.246 0.492 -20.7049 -1
GRID 2464 -0.492 0.492 -21.005 -1
GRID 2465 -0.246 0.492 -21.005 -1
GRID 2466 -0.492 0.492 -21.3051 -1
GRID 2467 -0.246 0.492 -21.3051 -1
GRID 2468 -0.492 0.492 -21.6051 -1
GRID 2469 -0.246 0.492 -21.6051 -1
GRID 2470 -0.492 0.492 -21.9052 -1
GRID 2471 -0.246 0.492 -21.9052 -1
GRID 2472 -0.492 0.492 -22.2053 -1
GRID 2473 -0.246 0.492 -22.2053 -1
GRID 2474 -0.492 0.492 -22.5053 -1
GRID 2475 -0.246 0.492 -22.5053 -1
GRID 2476 -0.492 0.492 -22.8054 -1
GRID 2477 -0.246 0.492 -22.8054 -1
GRID 2478 -0.492 0.492 -23.1055 -1
GRID 2479 -0.246 0.492 -23.1055 -1
GRID 2480 -0.492 0.492 -23.4056 -1
GRID 2481 -0.246 0.492 -23.4056 -1
GRID 2482 -0.492 0.492 -23.7056 -1
GRID 2483 -0.246 0.492 -23.7056 -1
GRID 2484 -0.492 0.492 -24.0057 -1
GRID 2485 -0.246 0.492 -24.0057 -1
GRID 2486 -0.492 0.492 -24.3058 -1
GRID 2487 -0.246 0.492 -24.3058 -1
GRID 2488 -0.492 0.492 -24.6059 -1
GRID 2489 -0.246 0.492 -24.6059 -1
GRID 2490 -0.492 0.492 -24.9059 -1
GRID 2491 -0.246 0.492 -24.9059 -1
GRID 2492 -0.492 0.492 -25.206 -1
GRID 2493 -0.246 0.492 -25.206 -1
GRID 2494 -0.246 -0.246 -.300073 -1
GRID 2495 -5.62-13-0.246 -.300073 -1
GRID 2496 -0.246 -0.246 -.600146 -1
GRID 2497 -1.12-12-0.246 -.600146 -1
GRID 2498 -0.246 -0.246 -.900219 -1
GRID 2499 -1.68-12-0.246 -.900219 -1
GRID 2500 -0.246 -0.246 -1.20029 -1
GRID 2501 -2.24-12-0.246 -1.20029 -1
GRID 2502 -0.246 -0.246 -1.50037 -1
GRID 2503 -2.81-12-0.246 -1.50037 -1
GRID 2504 -0.246 -0.246 -1.80044 -1

Altair Engineering OptiStruct 13.0 Reference Guide 363

Proprietary Information of Altair Engineering


GRID 2505 -3.37-12-0.246 -1.80044 -1
GRID 2506 -0.246 -0.246 -2.10051 -1
GRID 2507 -3.93-12-0.246 -2.10051 -1
GRID 2508 -0.246 -0.246 -2.40058 -1
GRID 2509 -4.49-12-0.246 -2.40059 -1
GRID 2510 -0.246 -0.246 -2.70066 -1
GRID 2511 -5.06-12-0.246 -2.70066 -1
GRID 2512 -0.246 -0.246 -3.00073 -1
GRID 2513 -5.62-12-0.246 -3.00073 -1
GRID 2514 -0.246 -0.246 -3.3008 -1
GRID 2515 -6.18-12-0.246 -3.30081 -1
GRID 2516 -0.246 -0.246 -3.60088 -1
GRID 2517 -6.74-12-0.246 -3.60088 -1
GRID 2518 -0.246 -0.246 -3.90095 -1
GRID 2519 -7.3-12 -0.246 -3.90095 -1
GRID 2520 -0.246 -0.246 -4.20102 -1
GRID 2521 -7.86-12-0.246 -4.20102 -1
GRID 2522 -0.246 -0.246 -4.5011 -1
GRID 2523 -8.43-12-0.246 -4.5011 -1
GRID 2524 -0.246 -0.246 -4.80117 -1
GRID 2525 -8.99-12-0.246 -4.80117 -1
GRID 2526 -0.246 -0.246 -5.10124 -1
GRID 2527 -9.55-12-0.246 -5.10124 -1
GRID 2528 -0.246 -0.246 -5.40132 -1
GRID 2529 -1.01-11-0.246 -5.40132 -1
GRID 2530 -0.246 -0.246 -5.70139 -1
GRID 2531 -1.07-11-0.246 -5.70139 -1
GRID 2532 -0.246 -0.246 -6.00146 -1
GRID 2533 -1.12-11-0.246 -6.00146 -1
GRID 2534 -0.246 -0.246 -6.30154 -1
GRID 2535 -1.18-11-0.246 -6.30154 -1
GRID 2536 -0.246 -0.246 -6.60161 -1
GRID 2537 -1.23-11-0.246 -6.60161 -1
GRID 2538 -0.246 -0.246 -6.90168 -1
GRID 2539 -1.29-11-0.246 -6.90168 -1
GRID 2540 -0.246 -0.246 -7.20176 -1
GRID 2541 -1.35-11-0.246 -7.20176 -1
GRID 2542 -0.246 -0.246 -7.50183 -1
GRID 2543 -1.4-11 -0.246 -7.50183 -1
GRID 2544 -0.246 -0.246 -7.8019 -1
GRID 2545 -1.46-11-0.246 -7.8019 -1
GRID 2546 -0.246 -0.246 -8.10198 -1
GRID 2547 -1.51-11-0.246 -8.10198 -1
GRID 2548 -0.246 -0.246 -8.40205 -1
GRID 2549 -1.57-11-0.246 -8.40205 -1
GRID 2550 -0.246 -0.246 -8.70212 -1
GRID 2551 -1.63-11-0.246 -8.70212 -1
GRID 2552 -0.246 -0.246 -9.0022 -1
GRID 2553 -1.68-11-0.246 -9.0022 -1
GRID 2554 -0.246 -0.246 -9.30227 -1
GRID 2555 -1.74-11-0.246 -9.30227 -1
GRID 2556 -0.246 -0.246 -9.60234 -1
GRID 2557 -1.79-11-0.246 -9.60234 -1
GRID 2558 -0.246 -0.246 -9.90241 -1
GRID 2559 -1.85-11-0.246 -9.90241 -1
GRID 2560 -0.246 -0.246 -10.2025 -1
GRID 2561 -1.91-11-0.246 -10.2025 -1
GRID 2562 -0.246 -0.246 -10.5026 -1
GRID 2563 -1.96-11-0.246 -10.5026 -1
GRID 2564 -0.246 -0.246 -10.8026 -1
GRID 2565 -2.02-11-0.246 -10.8026 -1
GRID 2566 -0.246 -0.246 -11.1027 -1
GRID 2567 -2.07-11-0.246 -11.1027 -1
GRID 2568 -0.246 -0.246 -11.4028 -1
GRID 2569 -2.13-11-0.246 -11.4028 -1
GRID 2570 -0.246 -0.246 -11.7029 -1
GRID 2571 -2.19-11-0.246 -11.7029 -1
GRID 2572 -0.246 -0.246 -12.0029 -1
GRID 2573 -2.24-11-0.246 -12.0029 -1

364 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 2574 -0.246 -0.246 -12.303 -1
GRID 2575 -2.3-11 -0.246 -12.303 -1
GRID 2576 -0.246 -0.246 -12.6031 -1
GRID 2577 -2.35-11-0.246 -12.6031 -1
GRID 2738 -0.246 -0.246 -12.903 -1
GRID 2739 -6.9-11 -0.246 -12.903 -1
GRID 2740 -0.246 -0.246 -13.2031 -1
GRID 2741 -6.95-11-0.246 -13.2031 -1
GRID 2742 -0.246 -0.246 -13.5032 -1
GRID 2743 -7.01-11-0.246 -13.5032 -1
GRID 2744 -0.246 -0.246 -13.8032 -1
GRID 2745 -7.06-11-0.246 -13.8032 -1
GRID 2746 -0.246 -0.246 -14.1033 -1
GRID 2747 -7.12-11-0.246 -14.1033 -1
GRID 2748 -0.246 -0.246 -14.4034 -1
GRID 2749 -7.19-11-0.246 -14.4034 -1
GRID 2750 -0.246 -0.246 -14.7034 -1
GRID 2751 -7.24-11-0.246 -14.7034 -1
GRID 2752 -0.246 -0.246 -15.0035 -1
GRID 2753 -7.3-11 -0.246 -15.0035 -1
GRID 2754 -0.246 -0.246 -15.3036 -1
GRID 2755 -7.35-11-0.246 -15.3036 -1
GRID 2756 -0.246 -0.246 -15.6037 -1
GRID 2757 -7.41-11-0.246 -15.6037 -1
GRID 2758 -0.246 -0.246 -15.9037 -1
GRID 2759 -7.47-11-0.246 -15.9037 -1
GRID 2760 -0.246 -0.246 -16.2038 -1
GRID 2761 -7.52-11-0.246 -16.2038 -1
GRID 2762 -0.246 -0.246 -16.5039 -1
GRID 2763 -7.58-11-0.246 -16.5039 -1
GRID 2764 -0.246 -0.246 -16.804 -1
GRID 2765 -7.63-11-0.246 -16.804 -1
GRID 2766 -0.246 -0.246 -17.104 -1
GRID 2767 -7.69-11-0.246 -17.104 -1
GRID 2768 -0.246 -0.246 -17.4041 -1
GRID 2769 -7.75-11-0.246 -17.4041 -1
GRID 2770 -0.246 -0.246 -17.7042 -1
GRID 2771 -7.8-11 -0.246 -17.7042 -1
GRID 2772 -0.246 -0.246 -18.0042 -1
GRID 2773 -7.86-11-0.246 -18.0042 -1
GRID 2774 -0.246 -0.246 -18.3043 -1
GRID 2775 -7.91-11-0.246 -18.3043 -1
GRID 2776 -0.246 -0.246 -18.6044 -1
GRID 2777 -7.97-11-0.246 -18.6044 -1
GRID 2778 -0.246 -0.246 -18.9045 -1
GRID 2779 -8.03-11-0.246 -18.9045 -1
GRID 2780 -0.246 -0.246 -19.2045 -1
GRID 2781 -8.08-11-0.246 -19.2045 -1
GRID 2782 -0.246 -0.246 -19.5046 -1
GRID 2783 -8.14-11-0.246 -19.5046 -1
GRID 2784 -0.246 -0.246 -19.8047 -1
GRID 2785 -8.19-11-0.246 -19.8047 -1
GRID 2786 -0.246 -0.246 -20.1048 -1
GRID 2787 -8.25-11-0.246 -20.1048 -1
GRID 2788 -0.246 -0.246 -20.4048 -1
GRID 2789 -8.31-11-0.246 -20.4048 -1
GRID 2790 -0.246 -0.246 -20.7049 -1
GRID 2791 -8.36-11-0.246 -20.7049 -1
GRID 2792 -0.246 -0.246 -21.005 -1
GRID 2793 -8.42-11-0.246 -21.005 -1
GRID 2794 -0.246 -0.246 -21.3051 -1
GRID 2795 -8.47-11-0.246 -21.3051 -1
GRID 2796 -0.246 -0.246 -21.6051 -1
GRID 2797 -8.53-11-0.246 -21.6051 -1
GRID 2798 -0.246 -0.246 -21.9052 -1
GRID 2799 -8.59-11-0.246 -21.9052 -1
GRID 2800 -0.246 -0.246 -22.2053 -1
GRID 2801 -8.64-11-0.246 -22.2053 -1
GRID 2802 -0.246 -0.246 -22.5053 -1

Altair Engineering OptiStruct 13.0 Reference Guide 365

Proprietary Information of Altair Engineering


GRID 2803 -8.7-11 -0.246 -22.5053 -1
GRID 2804 -0.246 -0.246 -22.8054 -1
GRID 2805 -8.75-11-0.246 -22.8054 -1
GRID 2806 -0.246 -0.246 -23.1055 -1
GRID 2807 -8.81-11-0.246 -23.1055 -1
GRID 2808 -0.246 -0.246 -23.4056 -1
GRID 2809 -8.87-11-0.246 -23.4056 -1
GRID 2810 -0.246 -0.246 -23.7056 -1
GRID 2811 -8.92-11-0.246 -23.7056 -1
GRID 2812 -0.246 -0.246 -24.0057 -1
GRID 2813 -8.98-11-0.246 -24.0057 -1
GRID 2814 -0.246 -0.246 -24.3058 -1
GRID 2815 -9.04-11-0.246 -24.3058 -1
GRID 2816 -0.246 -0.246 -24.6059 -1
GRID 2817 -9.09-11-0.246 -24.6059 -1
GRID 2818 -0.246 -0.246 -24.9059 -1
GRID 2819 -9.15-11-0.246 -24.9059 -1
GRID 2820 -0.246 -0.246 -25.206 -1
GRID 2821 -9.16-11-0.246 -25.206 -1
GRID 2822 -0.492 -0.246 -.300074 -1
GRID 2823 -0.492 -0.246 -.600146 -1
GRID 2824 -0.492 -0.246 -.900219 -1
GRID 2825 -0.492 -0.246 -1.20029 -1
GRID 2826 -0.492 -0.246 -1.50037 -1
GRID 2827 -0.492 -0.246 -1.80044 -1
GRID 2828 -0.492 -0.246 -2.10051 -1
GRID 2829 -0.492 -0.246 -2.40058 -1
GRID 2830 -0.492 -0.246 -2.70066 -1
GRID 2831 -0.492 -0.246 -3.00073 -1
GRID 2832 -0.492 -0.246 -3.3008 -1
GRID 2833 -0.492 -0.246 -3.60088 -1
GRID 2834 -0.492 -0.246 -3.90095 -1
GRID 2835 -0.492 -0.246 -4.20102 -1
GRID 2836 -0.492 -0.246 -4.5011 -1
GRID 2837 -0.492 -0.246 -4.80117 -1
GRID 2838 -0.492 -0.246 -5.10124 -1
GRID 2839 -0.492 -0.246 -5.40132 -1
GRID 2840 -0.492 -0.246 -5.70139 -1
GRID 2841 -0.492 -0.246 -6.00146 -1
GRID 2842 -0.492 -0.246 -6.30154 -1
GRID 2843 -0.492 -0.246 -6.60161 -1
GRID 2844 -0.492 -0.246 -6.90168 -1
GRID 2845 -0.492 -0.246 -7.20176 -1
GRID 2846 -0.492 -0.246 -7.50183 -1
GRID 2847 -0.492 -0.246 -7.8019 -1
GRID 2848 -0.492 -0.246 -8.10198 -1
GRID 2849 -0.492 -0.246 -8.40205 -1
GRID 2850 -0.492 -0.246 -8.70212 -1
GRID 2851 -0.492 -0.246 -9.00219 -1
GRID 2852 -0.492 -0.246 -9.30227 -1
GRID 2853 -0.492 -0.246 -9.60234 -1
GRID 2854 -0.492 -0.246 -9.90241 -1
GRID 2855 -0.492 -0.246 -10.2025 -1
GRID 2856 -0.492 -0.246 -10.5026 -1
GRID 2857 -0.492 -0.246 -10.8026 -1
GRID 2858 -0.492 -0.246 -11.1027 -1
GRID 2859 -0.492 -0.246 -11.4028 -1
GRID 2860 -0.492 -0.246 -11.7028 -1
GRID 2861 -0.492 -0.246 -12.0029 -1
GRID 2862 -0.492 -0.246 -12.303 -1
GRID 2863 -0.492 -0.246 -12.6031 -1
GRID 2944 -0.492 -0.246 -12.903 -1
GRID 2945 -0.492 -0.246 -13.2031 -1
GRID 2946 -0.492 -0.246 -13.5031 -1
GRID 2947 -0.492 -0.246 -13.8032 -1
GRID 2948 -0.492 -0.246 -14.1033 -1
GRID 2949 -0.492 -0.246 -14.4034 -1
GRID 2950 -0.492 -0.246 -14.7034 -1
GRID 2951 -0.492 -0.246 -15.0035 -1

366 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 2952 -0.492 -0.246 -15.3036 -1
GRID 2953 -0.492 -0.246 -15.6037 -1
GRID 2954 -0.492 -0.246 -15.9037 -1
GRID 2955 -0.492 -0.246 -16.2038 -1
GRID 2956 -0.492 -0.246 -16.5039 -1
GRID 2957 -0.492 -0.246 -16.804 -1
GRID 2958 -0.492 -0.246 -17.104 -1
GRID 2959 -0.492 -0.246 -17.4041 -1
GRID 2960 -0.492 -0.246 -17.7042 -1
GRID 2961 -0.492 -0.246 -18.0042 -1
GRID 2962 -0.492 -0.246 -18.3043 -1
GRID 2963 -0.492 -0.246 -18.6044 -1
GRID 2964 -0.492 -0.246 -18.9045 -1
GRID 2965 -0.492 -0.246 -19.2045 -1
GRID 2966 -0.492 -0.246 -19.5046 -1
GRID 2967 -0.492 -0.246 -19.8047 -1
GRID 2968 -0.492 -0.246 -20.1048 -1
GRID 2969 -0.492 -0.246 -20.4048 -1
GRID 2970 -0.492 -0.246 -20.7049 -1
GRID 2971 -0.492 -0.246 -21.005 -1
GRID 2972 -0.492 -0.246 -21.3051 -1
GRID 2973 -0.492 -0.246 -21.6051 -1
GRID 2974 -0.492 -0.246 -21.9052 -1
GRID 2975 -0.492 -0.246 -22.2053 -1
GRID 2976 -0.492 -0.246 -22.5053 -1
GRID 2977 -0.492 -0.246 -22.8054 -1
GRID 2978 -0.492 -0.246 -23.1055 -1
GRID 2979 -0.492 -0.246 -23.4056 -1
GRID 2980 -0.492 -0.246 -23.7056 -1
GRID 2981 -0.492 -0.246 -24.0057 -1
GRID 2982 -0.492 -0.246 -24.3058 -1
GRID 2983 -0.492 -0.246 -24.6059 -1
GRID 2984 -0.492 -0.246 -24.9059 -1
GRID 2985 -0.492 -0.246 -25.206 -1
GRID 2986 -0.246 -0.492 -.300073 -1
GRID 2987 -5.24-13-0.492 -.300073 -1
GRID 2988 -0.246 -0.492 -.600146 -1
GRID 2989 -1.05-12-0.492 -.600146 -1
GRID 2990 -0.246 -0.492 -.900219 -1
GRID 2991 -1.57-12-0.492 -.900219 -1
GRID 2992 -0.246 -0.492 -1.20029 -1
GRID 2993 -2.09-12-0.492 -1.20029 -1
GRID 2994 -0.246 -0.492 -1.50037 -1
GRID 2995 -2.63-12-0.492 -1.50037 -1
GRID 2996 -0.246 -0.492 -1.80044 -1
GRID 2997 -3.15-12-0.492 -1.80044 -1
GRID 2998 -0.246 -0.492 -2.10051 -1
GRID 2999 -3.67-12-0.492 -2.10051 -1
GRID 3000 -0.246 -0.492 -2.40058 -1
GRID 3001 -4.19-12-0.492 -2.40059 -1
GRID 3002 -0.246 -0.492 -2.70066 -1
GRID 3003 -4.72-12-0.492 -2.70066 -1
GRID 3004 -0.246 -0.492 -3.00073 -1
GRID 3005 -5.24-12-0.492 -3.00073 -1
GRID 3006 -0.246 -0.492 -3.3008 -1
GRID 3007 -5.76-12-0.492 -3.30081 -1
GRID 3008 -0.246 -0.492 -3.60088 -1
GRID 3009 -6.29-12-0.492 -3.60088 -1
GRID 3010 -0.246 -0.492 -3.90095 -1
GRID 3011 -6.81-12-0.492 -3.90095 -1
GRID 3012 -0.246 -0.492 -4.20102 -1
GRID 3013 -7.33-12-0.492 -4.20102 -1
GRID 3014 -0.246 -0.492 -4.5011 -1
GRID 3015 -7.87-12-0.492 -4.5011 -1
GRID 3016 -0.246 -0.492 -4.80117 -1
GRID 3017 -8.39-12-0.492 -4.80117 -1
GRID 3018 -0.246 -0.492 -5.10124 -1
GRID 3019 -8.91-12-0.492 -5.10124 -1
GRID 3020 -0.246 -0.492 -5.40132 -1

Altair Engineering OptiStruct 13.0 Reference Guide 367

Proprietary Information of Altair Engineering


GRID 3021 -9.44-12-0.492 -5.40132 -1
GRID 3022 -0.246 -0.492 -5.70139 -1
GRID 3023 -9.96-12-0.492 -5.70139 -1
GRID 3024 -0.246 -0.492 -6.00146 -1
GRID 3025 -1.05-11-0.492 -6.00146 -1
GRID 3026 -0.246 -0.492 -6.30154 -1
GRID 3027 -1.1-11 -0.492 -6.30154 -1
GRID 3028 -0.246 -0.492 -6.60161 -1
GRID 3029 -1.15-11-0.492 -6.60161 -1
GRID 3030 -0.246 -0.492 -6.90168 -1
GRID 3031 -1.2-11 -0.492 -6.90168 -1
GRID 3032 -0.246 -0.492 -7.20176 -1
GRID 3033 -1.26-11-0.492 -7.20176 -1
GRID 3034 -0.246 -0.492 -7.50183 -1
GRID 3035 -1.31-11-0.492 -7.50183 -1
GRID 3036 -0.246 -0.492 -7.8019 -1
GRID 3037 -1.36-11-0.492 -7.8019 -1
GRID 3038 -0.246 -0.492 -8.10198 -1
GRID 3039 -1.41-11-0.492 -8.10198 -1
GRID 3040 -0.246 -0.492 -8.40205 -1
GRID 3041 -1.46-11-0.492 -8.40205 -1
GRID 3042 -0.246 -0.492 -8.70212 -1
GRID 3043 -1.52-11-0.492 -8.70212 -1
GRID 3044 -0.246 -0.492 -9.0022 -1
GRID 3045 -1.57-11-0.492 -9.0022 -1
GRID 3046 -0.246 -0.492 -9.30227 -1
GRID 3047 -1.62-11-0.492 -9.30227 -1
GRID 3048 -0.246 -0.492 -9.60234 -1
GRID 3049 -1.67-11-0.492 -9.60234 -1
GRID 3050 -0.246 -0.492 -9.90241 -1
GRID 3051 -1.73-11-0.492 -9.90241 -1
GRID 3052 -0.246 -0.492 -10.2025 -1
GRID 3053 -1.78-11-0.492 -10.2025 -1
GRID 3054 -0.246 -0.492 -10.5026 -1
GRID 3055 -1.83-11-0.492 -10.5026 -1
GRID 3056 -0.246 -0.492 -10.8026 -1
GRID 3057 -1.88-11-0.492 -10.8026 -1
GRID 3058 -0.246 -0.492 -11.1027 -1
GRID 3059 -1.94-11-0.492 -11.1027 -1
GRID 3060 -0.246 -0.492 -11.4028 -1
GRID 3061 -1.99-11-0.492 -11.4028 -1
GRID 3062 -0.246 -0.492 -11.7029 -1
GRID 3063 -2.04-11-0.492 -11.7029 -1
GRID 3064 -0.246 -0.492 -12.0029 -1
GRID 3065 -2.09-11-0.492 -12.0029 -1
GRID 3066 -0.246 -0.492 -12.303 -1
GRID 3067 -2.14-11-0.492 -12.303 -1
GRID 3068 -0.246 -0.492 -12.6031 -1
GRID 3069 -2.2-11 -0.492 -12.6031 -1
GRID 3230 -0.246 -0.492 -12.903 -1
GRID 3231 -6.43-11-0.492 -12.903 -1
GRID 3232 -0.246 -0.492 -13.2031 -1
GRID 3233 -6.49-11-0.492 -13.2031 -1
GRID 3234 -0.246 -0.492 -13.5032 -1
GRID 3235 -6.54-11-0.492 -13.5032 -1
GRID 3236 -0.246 -0.492 -13.8032 -1
GRID 3237 -6.59-11-0.492 -13.8032 -1
GRID 3238 -0.246 -0.492 -14.1033 -1
GRID 3239 -6.64-11-0.492 -14.1033 -1
GRID 3240 -0.246 -0.492 -14.4034 -1
GRID 3241 -6.71-11-0.492 -14.4034 -1
GRID 3242 -0.246 -0.492 -14.7034 -1
GRID 3243 -6.76-11-0.492 -14.7034 -1
GRID 3244 -0.246 -0.492 -15.0035 -1
GRID 3245 -6.81-11-0.492 -15.0035 -1
GRID 3246 -0.246 -0.492 -15.3036 -1
GRID 3247 -6.86-11-0.492 -15.3036 -1
GRID 3248 -0.246 -0.492 -15.6037 -1
GRID 3249 -6.91-11-0.492 -15.6037 -1

368 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 3250 -0.246 -0.492 -15.9037 -1
GRID 3251 -6.97-11-0.492 -15.9037 -1
GRID 3252 -0.246 -0.492 -16.2038 -1
GRID 3253 -7.02-11-0.492 -16.2038 -1
GRID 3254 -0.246 -0.492 -16.5039 -1
GRID 3255 -7.07-11-0.492 -16.5039 -1
GRID 3256 -0.246 -0.492 -16.804 -1
GRID 3257 -7.12-11-0.492 -16.804 -1
GRID 3258 -0.246 -0.492 -17.104 -1
GRID 3259 -7.18-11-0.492 -17.104 -1
GRID 3260 -0.246 -0.492 -17.4041 -1
GRID 3261 -7.23-11-0.492 -17.4041 -1
GRID 3262 -0.246 -0.492 -17.7042 -1
GRID 3263 -7.28-11-0.492 -17.7042 -1
GRID 3264 -0.246 -0.492 -18.0042 -1
GRID 3265 -7.33-11-0.492 -18.0042 -1
GRID 3266 -0.246 -0.492 -18.3043 -1
GRID 3267 -7.39-11-0.492 -18.3043 -1
GRID 3268 -0.246 -0.492 -18.6044 -1
GRID 3269 -7.44-11-0.492 -18.6044 -1
GRID 3270 -0.246 -0.492 -18.9045 -1
GRID 3271 -7.49-11-0.492 -18.9045 -1
GRID 3272 -0.246 -0.492 -19.2045 -1
GRID 3273 -7.54-11-0.492 -19.2045 -1
GRID 3274 -0.246 -0.492 -19.5046 -1
GRID 3275 -7.59-11-0.492 -19.5046 -1
GRID 3276 -0.246 -0.492 -19.8047 -1
GRID 3277 -7.65-11-0.492 -19.8047 -1
GRID 3278 -0.246 -0.492 -20.1048 -1
GRID 3279 -7.7-11 -0.492 -20.1048 -1
GRID 3280 -0.246 -0.492 -20.4048 -1
GRID 3281 -7.75-11-0.492 -20.4048 -1
GRID 3282 -0.246 -0.492 -20.7049 -1
GRID 3283 -7.8-11 -0.492 -20.7049 -1
GRID 3284 -0.246 -0.492 -21.005 -1
GRID 3285 -7.86-11-0.492 -21.005 -1
GRID 3286 -0.246 -0.492 -21.3051 -1
GRID 3287 -7.91-11-0.492 -21.3051 -1
GRID 3288 -0.246 -0.492 -21.6051 -1
GRID 3289 -7.96-11-0.492 -21.6051 -1
GRID 3290 -0.246 -0.492 -21.9052 -1
GRID 3291 -8.01-11-0.492 -21.9052 -1
GRID 3292 -0.246 -0.492 -22.2053 -1
GRID 3293 -8.07-11-0.492 -22.2053 -1
GRID 3294 -0.246 -0.492 -22.5053 -1
GRID 3295 -8.12-11-0.492 -22.5053 -1
GRID 3296 -0.246 -0.492 -22.8054 -1
GRID 3297 -8.17-11-0.492 -22.8054 -1
GRID 3298 -0.246 -0.492 -23.1055 -1
GRID 3299 -8.22-11-0.492 -23.1055 -1
GRID 3300 -0.246 -0.492 -23.4056 -1
GRID 3301 -8.27-11-0.492 -23.4056 -1
GRID 3302 -0.246 -0.492 -23.7056 -1
GRID 3303 -8.33-11-0.492 -23.7056 -1
GRID 3304 -0.246 -0.492 -24.0057 -1
GRID 3305 -8.38-11-0.492 -24.0057 -1
GRID 3306 -0.246 -0.492 -24.3058 -1
GRID 3307 -8.43-11-0.492 -24.3058 -1
GRID 3308 -0.246 -0.492 -24.6059 -1
GRID 3309 -8.48-11-0.492 -24.6059 -1
GRID 3310 -0.246 -0.492 -24.9059 -1
GRID 3311 -8.54-11-0.492 -24.9059 -1
GRID 3312 -0.246 -0.492 -25.206 -1
GRID 3313 -8.59-11-0.492 -25.206 -1
GRID 3314 -0.492 -0.492 -.300073 -1
GRID 3315 -0.492 -0.492 -.600146 -1
GRID 3316 -0.492 -0.492 -.900219 -1
GRID 3317 -0.492 -0.492 -1.20029 -1
GRID 3318 -0.492 -0.492 -1.50037 -1

Altair Engineering OptiStruct 13.0 Reference Guide 369

Proprietary Information of Altair Engineering


GRID 3319 -0.492 -0.492 -1.80044 -1
GRID 3320 -0.492 -0.492 -2.10051 -1
GRID 3321 -0.492 -0.492 -2.40058 -1
GRID 3322 -0.492 -0.492 -2.70066 -1
GRID 3323 -0.492 -0.492 -3.00073 -1
GRID 3324 -0.492 -0.492 -3.3008 -1
GRID 3325 -0.492 -0.492 -3.60088 -1
GRID 3326 -0.492 -0.492 -3.90095 -1
GRID 3327 -0.492 -0.492 -4.20102 -1
GRID 3328 -0.492 -0.492 -4.5011 -1
GRID 3329 -0.492 -0.492 -4.80117 -1
GRID 3330 -0.492 -0.492 -5.10124 -1
GRID 3331 -0.492 -0.492 -5.40132 -1
GRID 3332 -0.492 -0.492 -5.70139 -1
GRID 3333 -0.492 -0.492 -6.00146 -1
GRID 3334 -0.492 -0.492 -6.30154 -1
GRID 3335 -0.492 -0.492 -6.60161 -1
GRID 3336 -0.492 -0.492 -6.90168 -1
GRID 3337 -0.492 -0.492 -7.20176 -1
GRID 3338 -0.492 -0.492 -7.50183 -1
GRID 3339 -0.492 -0.492 -7.8019 -1
GRID 3340 -0.492 -0.492 -8.10198 -1
GRID 3341 -0.492 -0.492 -8.40205 -1
GRID 3342 -0.492 -0.492 -8.70212 -1
GRID 3343 -0.492 -0.492 -9.00219 -1
GRID 3344 -0.492 -0.492 -9.30227 -1
GRID 3345 -0.492 -0.492 -9.60234 -1
GRID 3346 -0.492 -0.492 -9.90241 -1
GRID 3347 -0.492 -0.492 -10.2025 -1
GRID 3348 -0.492 -0.492 -10.5026 -1
GRID 3349 -0.492 -0.492 -10.8026 -1
GRID 3350 -0.492 -0.492 -11.1027 -1
GRID 3351 -0.492 -0.492 -11.4028 -1
GRID 3352 -0.492 -0.492 -11.7028 -1
GRID 3353 -0.492 -0.492 -12.0029 -1
GRID 3354 -0.492 -0.492 -12.303 -1
GRID 3355 -0.492 -0.492 -12.6031 -1
GRID 3436 -0.492 -0.492 -12.903 -1
GRID 3437 -0.492 -0.492 -13.2031 -1
GRID 3438 -0.492 -0.492 -13.5031 -1
GRID 3439 -0.492 -0.492 -13.8032 -1
GRID 3440 -0.492 -0.492 -14.1033 -1
GRID 3441 -0.492 -0.492 -14.4034 -1
GRID 3442 -0.492 -0.492 -14.7034 -1
GRID 3443 -0.492 -0.492 -15.0035 -1
GRID 3444 -0.492 -0.492 -15.3036 -1
GRID 3445 -0.492 -0.492 -15.6037 -1
GRID 3446 -0.492 -0.492 -15.9037 -1
GRID 3447 -0.492 -0.492 -16.2038 -1
GRID 3448 -0.492 -0.492 -16.5039 -1
GRID 3449 -0.492 -0.492 -16.804 -1
GRID 3450 -0.492 -0.492 -17.104 -1
GRID 3451 -0.492 -0.492 -17.4041 -1
GRID 3452 -0.492 -0.492 -17.7042 -1
GRID 3453 -0.492 -0.492 -18.0042 -1
GRID 3454 -0.492 -0.492 -18.3043 -1
GRID 3455 -0.492 -0.492 -18.6044 -1
GRID 3456 -0.492 -0.492 -18.9045 -1
GRID 3457 -0.492 -0.492 -19.2045 -1
GRID 3458 -0.492 -0.492 -19.5046 -1
GRID 3459 -0.492 -0.492 -19.8047 -1
GRID 3460 -0.492 -0.492 -20.1048 -1
GRID 3461 -0.492 -0.492 -20.4048 -1
GRID 3462 -0.492 -0.492 -20.7049 -1
GRID 3463 -0.492 -0.492 -21.005 -1
GRID 3464 -0.492 -0.492 -21.3051 -1
GRID 3465 -0.492 -0.492 -21.6051 -1
GRID 3466 -0.492 -0.492 -21.9052 -1
GRID 3467 -0.492 -0.492 -22.2053 -1

370 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 3468 -0.492 -0.492 -22.5053 -1
GRID 3469 -0.492 -0.492 -22.8054 -1
GRID 3470 -0.492 -0.492 -23.1055 -1
GRID 3471 -0.492 -0.492 -23.4056 -1
GRID 3472 -0.492 -0.492 -23.7056 -1
GRID 3473 -0.492 -0.492 -24.0057 -1
GRID 3474 -0.492 -0.492 -24.3058 -1
GRID 3475 -0.492 -0.492 -24.6059 -1
GRID 3476 -0.492 -0.492 -24.9059 -1
GRID 3477 -0.492 -0.492 -25.206 -1
GRID 3478 0.246 -0.246 -.300073 -1
GRID 3479 0.492 -0.246 -.300074 -1
GRID 3480 0.246 -0.246 -.600146 -1
GRID 3481 0.492 -0.246 -.600146 -1
GRID 3482 0.246 -0.246 -0.90022 -1
GRID 3483 0.492 -0.246 -0.90022 -1
GRID 3484 0.246 -0.246 -1.20029 -1
GRID 3485 0.492 -0.246 -1.20029 -1
GRID 3486 0.246 -0.246 -1.50037 -1
GRID 3487 0.492 -0.246 -1.50037 -1
GRID 3488 0.246 -0.246 -1.80044 -1
GRID 3489 0.492 -0.246 -1.80044 -1
GRID 3490 0.246 -0.246 -2.10051 -1
GRID 3491 0.492 -0.246 -2.10051 -1
GRID 3492 0.246 -0.246 -2.40059 -1
GRID 3493 0.492 -0.246 -2.40059 -1
GRID 3494 0.246 -0.246 -2.70066 -1
GRID 3495 0.492 -0.246 -2.70066 -1
GRID 3496 0.246 -0.246 -3.00073 -1
GRID 3497 0.492 -0.246 -3.00073 -1
GRID 3498 0.246 -0.246 -3.30081 -1
GRID 3499 0.492 -0.246 -3.30081 -1
GRID 3500 0.246 -0.246 -3.60088 -1
GRID 3501 0.492 -0.246 -3.60088 -1
GRID 3502 0.246 -0.246 -3.90095 -1
GRID 3503 0.492 -0.246 -3.90095 -1
GRID 3504 0.246 -0.246 -4.20102 -1
GRID 3505 0.492 -0.246 -4.20102 -1
GRID 3506 0.246 -0.246 -4.5011 -1
GRID 3507 0.492 -0.246 -4.5011 -1
GRID 3508 0.246 -0.246 -4.80117 -1
GRID 3509 0.492 -0.246 -4.80117 -1
GRID 3510 0.246 -0.246 -5.10124 -1
GRID 3511 0.492 -0.246 -5.10124 -1
GRID 3512 0.246 -0.246 -5.40132 -1
GRID 3513 0.492 -0.246 -5.40132 -1
GRID 3514 0.246 -0.246 -5.70139 -1
GRID 3515 0.492 -0.246 -5.70139 -1
GRID 3516 0.246 -0.246 -6.00146 -1
GRID 3517 0.492 -0.246 -6.00146 -1
GRID 3518 0.246 -0.246 -6.30154 -1
GRID 3519 0.492 -0.246 -6.30154 -1
GRID 3520 0.246 -0.246 -6.60161 -1
GRID 3521 0.492 -0.246 -6.60161 -1
GRID 3522 0.246 -0.246 -6.90168 -1
GRID 3523 0.492 -0.246 -6.90168 -1
GRID 3524 0.246 -0.246 -7.20176 -1
GRID 3525 0.492 -0.246 -7.20176 -1
GRID 3526 0.246 -0.246 -7.50183 -1
GRID 3527 0.492 -0.246 -7.50183 -1
GRID 3528 0.246 -0.246 -7.8019 -1
GRID 3529 0.492 -0.246 -7.8019 -1
GRID 3530 0.246 -0.246 -8.10198 -1
GRID 3531 0.492 -0.246 -8.10198 -1
GRID 3532 0.246 -0.246 -8.40205 -1
GRID 3533 0.492 -0.246 -8.40205 -1
GRID 3534 0.246 -0.246 -8.70212 -1
GRID 3535 0.492 -0.246 -8.70212 -1
GRID 3536 0.246 -0.246 -9.0022 -1

Altair Engineering OptiStruct 13.0 Reference Guide 371

Proprietary Information of Altair Engineering


GRID 3537 0.492 -0.246 -9.0022 -1
GRID 3538 0.246 -0.246 -9.30227 -1
GRID 3539 0.492 -0.246 -9.30227 -1
GRID 3540 0.246 -0.246 -9.60234 -1
GRID 3541 0.492 -0.246 -9.60234 -1
GRID 3542 0.246 -0.246 -9.90241 -1
GRID 3543 0.492 -0.246 -9.90242 -1
GRID 3544 0.246 -0.246 -10.2025 -1
GRID 3545 0.492 -0.246 -10.2025 -1
GRID 3546 0.246 -0.246 -10.5026 -1
GRID 3547 0.492 -0.246 -10.5026 -1
GRID 3548 0.246 -0.246 -10.8026 -1
GRID 3549 0.492 -0.246 -10.8026 -1
GRID 3550 0.246 -0.246 -11.1027 -1
GRID 3551 0.492 -0.246 -11.1027 -1
GRID 3552 0.246 -0.246 -11.4028 -1
GRID 3553 0.492 -0.246 -11.4028 -1
GRID 3554 0.246 -0.246 -11.7029 -1
GRID 3555 0.492 -0.246 -11.7029 -1
GRID 3556 0.246 -0.246 -12.0029 -1
GRID 3557 0.492 -0.246 -12.0029 -1
GRID 3558 0.246 -0.246 -12.303 -1
GRID 3559 0.492 -0.246 -12.303 -1
GRID 3560 0.246 -0.246 -12.6031 -1
GRID 3561 0.492 -0.246 -12.6031 -1
GRID 3722 0.246 -0.246 -12.903 -1
GRID 3723 0.492 -0.246 -12.903 -1
GRID 3724 0.246 -0.246 -13.2031 -1
GRID 3725 0.492 -0.246 -13.2031 -1
GRID 3726 0.246 -0.246 -13.5032 -1
GRID 3727 0.492 -0.246 -13.5032 -1
GRID 3728 0.246 -0.246 -13.8032 -1
GRID 3729 0.492 -0.246 -13.8032 -1
GRID 3730 0.246 -0.246 -14.1033 -1
GRID 3731 0.492 -0.246 -14.1033 -1
GRID 3732 0.246 -0.246 -14.4034 -1
GRID 3733 0.492 -0.246 -14.4034 -1
GRID 3734 0.246 -0.246 -14.7034 -1
GRID 3735 0.492 -0.246 -14.7034 -1
GRID 3736 0.246 -0.246 -15.0035 -1
GRID 3737 0.492 -0.246 -15.0035 -1
GRID 3738 0.246 -0.246 -15.3036 -1
GRID 3739 0.492 -0.246 -15.3036 -1
GRID 3740 0.246 -0.246 -15.6037 -1
GRID 3741 0.492 -0.246 -15.6037 -1
GRID 3742 0.246 -0.246 -15.9037 -1
GRID 3743 0.492 -0.246 -15.9037 -1
GRID 3744 0.246 -0.246 -16.2038 -1
GRID 3745 0.492 -0.246 -16.2038 -1
GRID 3746 0.246 -0.246 -16.5039 -1
GRID 3747 0.492 -0.246 -16.5039 -1
GRID 3748 0.246 -0.246 -16.804 -1
GRID 3749 0.492 -0.246 -16.804 -1
GRID 3750 0.246 -0.246 -17.104 -1
GRID 3751 0.492 -0.246 -17.104 -1
GRID 3752 0.246 -0.246 -17.4041 -1
GRID 3753 0.492 -0.246 -17.4041 -1
GRID 3754 0.246 -0.246 -17.7042 -1
GRID 3755 0.492 -0.246 -17.7042 -1
GRID 3756 0.246 -0.246 -18.0042 -1
GRID 3757 0.492 -0.246 -18.0042 -1
GRID 3758 0.246 -0.246 -18.3043 -1
GRID 3759 0.492 -0.246 -18.3043 -1
GRID 3760 0.246 -0.246 -18.6044 -1
GRID 3761 0.492 -0.246 -18.6044 -1
GRID 3762 0.246 -0.246 -18.9045 -1
GRID 3763 0.492 -0.246 -18.9045 -1
GRID 3764 0.246 -0.246 -19.2045 -1
GRID 3765 0.492 -0.246 -19.2045 -1

372 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 3766 0.246 -0.246 -19.5046 -1
GRID 3767 0.492 -0.246 -19.5046 -1
GRID 3768 0.246 -0.246 -19.8047 -1
GRID 3769 0.492 -0.246 -19.8047 -1
GRID 3770 0.246 -0.246 -20.1048 -1
GRID 3771 0.492 -0.246 -20.1048 -1
GRID 3772 0.246 -0.246 -20.4048 -1
GRID 3773 0.492 -0.246 -20.4048 -1
GRID 3774 0.246 -0.246 -20.7049 -1
GRID 3775 0.492 -0.246 -20.7049 -1
GRID 3776 0.246 -0.246 -21.005 -1
GRID 3777 0.492 -0.246 -21.005 -1
GRID 3778 0.246 -0.246 -21.3051 -1
GRID 3779 0.492 -0.246 -21.3051 -1
GRID 3780 0.246 -0.246 -21.6051 -1
GRID 3781 0.492 -0.246 -21.6051 -1
GRID 3782 0.246 -0.246 -21.9052 -1
GRID 3783 0.492 -0.246 -21.9052 -1
GRID 3784 0.246 -0.246 -22.2053 -1
GRID 3785 0.492 -0.246 -22.2053 -1
GRID 3786 0.246 -0.246 -22.5053 -1
GRID 3787 0.492 -0.246 -22.5053 -1
GRID 3788 0.246 -0.246 -22.8054 -1
GRID 3789 0.492 -0.246 -22.8054 -1
GRID 3790 0.246 -0.246 -23.1055 -1
GRID 3791 0.492 -0.246 -23.1055 -1
GRID 3792 0.246 -0.246 -23.4056 -1
GRID 3793 0.492 -0.246 -23.4056 -1
GRID 3794 0.246 -0.246 -23.7056 -1
GRID 3795 0.492 -0.246 -23.7056 -1
GRID 3796 0.246 -0.246 -24.0057 -1
GRID 3797 0.492 -0.246 -24.0057 -1
GRID 3798 0.246 -0.246 -24.3058 -1
GRID 3799 0.492 -0.246 -24.3058 -1
GRID 3800 0.246 -0.246 -24.6059 -1
GRID 3801 0.492 -0.246 -24.6059 -1
GRID 3802 0.246 -0.246 -24.9059 -1
GRID 3803 0.492 -0.246 -24.9059 -1
GRID 3804 0.246 -0.246 -25.206 -1
GRID 3805 0.492 -0.246 -25.206 -1
GRID 3806 0.246 -0.492 -.300073 -1
GRID 3807 0.492 -0.492 -.300074 -1
GRID 3808 0.246 -0.492 -.600146 -1
GRID 3809 0.492 -0.492 -.600146 -1
GRID 3810 0.246 -0.492 -0.90022 -1
GRID 3811 0.492 -0.492 -0.90022 -1
GRID 3812 0.246 -0.492 -1.20029 -1
GRID 3813 0.492 -0.492 -1.20029 -1
GRID 3814 0.246 -0.492 -1.50037 -1
GRID 3815 0.492 -0.492 -1.50037 -1
GRID 3816 0.246 -0.492 -1.80044 -1
GRID 3817 0.492 -0.492 -1.80044 -1
GRID 3818 0.246 -0.492 -2.10051 -1
GRID 3819 0.492 -0.492 -2.10051 -1
GRID 3820 0.246 -0.492 -2.40059 -1
GRID 3821 0.492 -0.492 -2.40059 -1
GRID 3822 0.246 -0.492 -2.70066 -1
GRID 3823 0.492 -0.492 -2.70066 -1
GRID 3824 0.246 -0.492 -3.00073 -1
GRID 3825 0.492 -0.492 -3.00073 -1
GRID 3826 0.246 -0.492 -3.30081 -1
GRID 3827 0.492 -0.492 -3.30081 -1
GRID 3828 0.246 -0.492 -3.60088 -1
GRID 3829 0.492 -0.492 -3.60088 -1
GRID 3830 0.246 -0.492 -3.90095 -1
GRID 3831 0.492 -0.492 -3.90095 -1
GRID 3832 0.246 -0.492 -4.20102 -1
GRID 3833 0.492 -0.492 -4.20102 -1
GRID 3834 0.246 -0.492 -4.5011 -1

Altair Engineering OptiStruct 13.0 Reference Guide 373

Proprietary Information of Altair Engineering


GRID 3835 0.492 -0.492 -4.5011 -1
GRID 3836 0.246 -0.492 -4.80117 -1
GRID 3837 0.492 -0.492 -4.80117 -1
GRID 3838 0.246 -0.492 -5.10124 -1
GRID 3839 0.492 -0.492 -5.10124 -1
GRID 3840 0.246 -0.492 -5.40132 -1
GRID 3841 0.492 -0.492 -5.40132 -1
GRID 3842 0.246 -0.492 -5.70139 -1
GRID 3843 0.492 -0.492 -5.70139 -1
GRID 3844 0.246 -0.492 -6.00146 -1
GRID 3845 0.492 -0.492 -6.00146 -1
GRID 3846 0.246 -0.492 -6.30154 -1
GRID 3847 0.492 -0.492 -6.30154 -1
GRID 3848 0.246 -0.492 -6.60161 -1
GRID 3849 0.492 -0.492 -6.60161 -1
GRID 3850 0.246 -0.492 -6.90168 -1
GRID 3851 0.492 -0.492 -6.90168 -1
GRID 3852 0.246 -0.492 -7.20176 -1
GRID 3853 0.492 -0.492 -7.20176 -1
GRID 3854 0.246 -0.492 -7.50183 -1
GRID 3855 0.492 -0.492 -7.50183 -1
GRID 3856 0.246 -0.492 -7.8019 -1
GRID 3857 0.492 -0.492 -7.8019 -1
GRID 3858 0.246 -0.492 -8.10198 -1
GRID 3859 0.492 -0.492 -8.10198 -1
GRID 3860 0.246 -0.492 -8.40205 -1
GRID 3861 0.492 -0.492 -8.40205 -1
GRID 3862 0.246 -0.492 -8.70212 -1
GRID 3863 0.492 -0.492 -8.70212 -1
GRID 3864 0.246 -0.492 -9.0022 -1
GRID 3865 0.492 -0.492 -9.0022 -1
GRID 3866 0.246 -0.492 -9.30227 -1
GRID 3867 0.492 -0.492 -9.30227 -1
GRID 3868 0.246 -0.492 -9.60234 -1
GRID 3869 0.492 -0.492 -9.60234 -1
GRID 3870 0.246 -0.492 -9.90241 -1
GRID 3871 0.492 -0.492 -9.90242 -1
GRID 3872 0.246 -0.492 -10.2025 -1
GRID 3873 0.492 -0.492 -10.2025 -1
GRID 3874 0.246 -0.492 -10.5026 -1
GRID 3875 0.492 -0.492 -10.5026 -1
GRID 3876 0.246 -0.492 -10.8026 -1
GRID 3877 0.492 -0.492 -10.8026 -1
GRID 3878 0.246 -0.492 -11.1027 -1
GRID 3879 0.492 -0.492 -11.1027 -1
GRID 3880 0.246 -0.492 -11.4028 -1
GRID 3881 0.492 -0.492 -11.4028 -1
GRID 3882 0.246 -0.492 -11.7029 -1
GRID 3883 0.492 -0.492 -11.7029 -1
GRID 3884 0.246 -0.492 -12.0029 -1
GRID 3885 0.492 -0.492 -12.0029 -1
GRID 3886 0.246 -0.492 -12.303 -1
GRID 3887 0.492 -0.492 -12.303 -1
GRID 3888 0.246 -0.492 -12.6031 -1
GRID 3889 0.492 -0.492 -12.6031 -1
GRID 4050 0.246 -0.492 -12.903 -1
GRID 4051 0.492 -0.492 -12.903 -1
GRID 4052 0.246 -0.492 -13.2031 -1
GRID 4053 0.492 -0.492 -13.2031 -1
GRID 4054 0.246 -0.492 -13.5032 -1
GRID 4055 0.492 -0.492 -13.5032 -1
GRID 4056 0.246 -0.492 -13.8032 -1
GRID 4057 0.492 -0.492 -13.8032 -1
GRID 4058 0.246 -0.492 -14.1033 -1
GRID 4059 0.492 -0.492 -14.1033 -1
GRID 4060 0.246 -0.492 -14.4034 -1
GRID 4061 0.492 -0.492 -14.4034 -1
GRID 4062 0.246 -0.492 -14.7034 -1
GRID 4063 0.492 -0.492 -14.7034 -1

374 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 4064 0.246 -0.492 -15.0035 -1
GRID 4065 0.492 -0.492 -15.0035 -1
GRID 4066 0.246 -0.492 -15.3036 -1
GRID 4067 0.492 -0.492 -15.3036 -1
GRID 4068 0.246 -0.492 -15.6037 -1
GRID 4069 0.492 -0.492 -15.6037 -1
GRID 4070 0.246 -0.492 -15.9037 -1
GRID 4071 0.492 -0.492 -15.9037 -1
GRID 4072 0.246 -0.492 -16.2038 -1
GRID 4073 0.492 -0.492 -16.2038 -1
GRID 4074 0.246 -0.492 -16.5039 -1
GRID 4075 0.492 -0.492 -16.5039 -1
GRID 4076 0.246 -0.492 -16.804 -1
GRID 4077 0.492 -0.492 -16.804 -1
GRID 4078 0.246 -0.492 -17.104 -1
GRID 4079 0.492 -0.492 -17.104 -1
GRID 4080 0.246 -0.492 -17.4041 -1
GRID 4081 0.492 -0.492 -17.4041 -1
GRID 4082 0.246 -0.492 -17.7042 -1
GRID 4083 0.492 -0.492 -17.7042 -1
GRID 4084 0.246 -0.492 -18.0042 -1
GRID 4085 0.492 -0.492 -18.0042 -1
GRID 4086 0.246 -0.492 -18.3043 -1
GRID 4087 0.492 -0.492 -18.3043 -1
GRID 4088 0.246 -0.492 -18.6044 -1
GRID 4089 0.492 -0.492 -18.6044 -1
GRID 4090 0.246 -0.492 -18.9045 -1
GRID 4091 0.492 -0.492 -18.9045 -1
GRID 4092 0.246 -0.492 -19.2045 -1
GRID 4093 0.492 -0.492 -19.2045 -1
GRID 4094 0.246 -0.492 -19.5046 -1
GRID 4095 0.492 -0.492 -19.5046 -1
GRID 4096 0.246 -0.492 -19.8047 -1
GRID 4097 0.492 -0.492 -19.8047 -1
GRID 4098 0.246 -0.492 -20.1048 -1
GRID 4099 0.492 -0.492 -20.1048 -1
GRID 4100 0.246 -0.492 -20.4048 -1
GRID 4101 0.492 -0.492 -20.4048 -1
GRID 4102 0.246 -0.492 -20.7049 -1
GRID 4103 0.492 -0.492 -20.7049 -1
GRID 4104 0.246 -0.492 -21.005 -1
GRID 4105 0.492 -0.492 -21.005 -1
GRID 4106 0.246 -0.492 -21.3051 -1
GRID 4107 0.492 -0.492 -21.3051 -1
GRID 4108 0.246 -0.492 -21.6051 -1
GRID 4109 0.492 -0.492 -21.6051 -1
GRID 4110 0.246 -0.492 -21.9052 -1
GRID 4111 0.492 -0.492 -21.9052 -1
GRID 4112 0.246 -0.492 -22.2053 -1
GRID 4113 0.492 -0.492 -22.2053 -1
GRID 4114 0.246 -0.492 -22.5053 -1
GRID 4115 0.492 -0.492 -22.5053 -1
GRID 4116 0.246 -0.492 -22.8054 -1
GRID 4117 0.492 -0.492 -22.8054 -1
GRID 4118 0.246 -0.492 -23.1055 -1
GRID 4119 0.492 -0.492 -23.1055 -1
GRID 4120 0.246 -0.492 -23.4056 -1
GRID 4121 0.492 -0.492 -23.4056 -1
GRID 4122 0.246 -0.492 -23.7056 -1
GRID 4123 0.492 -0.492 -23.7056 -1
GRID 4124 0.246 -0.492 -24.0057 -1
GRID 4125 0.492 -0.492 -24.0057 -1
GRID 4126 0.246 -0.492 -24.3058 -1
GRID 4127 0.492 -0.492 -24.3058 -1
GRID 4128 0.246 -0.492 -24.6059 -1
GRID 4129 0.492 -0.492 -24.6059 -1
GRID 4130 0.246 -0.492 -24.9059 -1
GRID 4131 0.492 -0.492 -24.9059 -1
GRID 4132 0.246 -0.492 -25.206 -1

Altair Engineering OptiStruct 13.0 Reference Guide 375

Proprietary Information of Altair Engineering


GRID 4133 0.492 -0.492 -25.206 -1
GRID 6776 -0.246 -0.246 8.589-16
GRID 6777 0.246 -0.246 -8.59-16
GRID 6778 0.0 -0.246 0.0
GRID 6779 -0.492 -0.246 1.718-15
GRID 6780 -0.492 -0.492 1.718-15
GRID 6781 -0.246 -0.492 8.589-16
GRID 6782 0.0 -0.492 0.0
GRID 6783 0.246 -0.492 -8.59-16
GRID 6784 0.492 -0.492 -1.72-15
GRID 6785 0.492 -0.246 -1.72-15
GRID 6786 0.246 0.246 -8.59-16
GRID 6787 -0.246 0.246 8.589-16
GRID 6788 0.0 0.246 0.0
GRID 6789 0.492 0.246 -1.72-15
GRID 6790 0.492 0.492 -1.72-15
GRID 6791 0.246 0.492 -8.59-16
GRID 6792 0.0 0.492 0.0
GRID 6793 -0.246 0.492 8.589-16
GRID 6794 -0.492 0.492 1.718-15
GRID 6795 -0.492 0.246 1.718-15
GRID 6796 -0.492 0.0 1.718-15
GRID 6797 -0.246 0.0 8.589-16
GRID 6798 0.0 0.0 0.0
GRID 6799 0.246 0.0 -8.59-16
GRID 6800 0.492 0.0 -1.72-15
$$
$$ SPOINT Data
$$
$
$ CQUAD4 Elements
$
CQUAD4 5627 1 6778 6798 6799 6777
CQUAD4 5629 1 6782 6778 6777 6783
CQUAD4 6116 1 6777 6799 6800 6785
CQUAD4 6122 1 6783 6777 6785 6784
CQUAD4 6125 1 6799 6798 6788 6786
CQUAD4 6520 1 6779 6796 6797 6776
CQUAD4 6521 1 6776 6797 6798 6778
CQUAD4 6523 1 6780 6779 6776 6781
CQUAD4 6528 1 6781 6776 6778 6782
CQUAD4 6954 1 6797 6796 6795 6787
CQUAD4 7220 1 6788 6787 6793 6792
CQUAD4 7647 1 6787 6795 6794 6793
CQUAD4 7652 1 6798 6797 6787 6788
CQUAD4 7945 1 6786 6788 6792 6791
CQUAD4 7948 1 6789 6786 6791 6790
CQUAD4 7955 1 6800 6799 6786 6789
$
$HMMOVE 5
$ 5627 5629 6116 6122 6125 6520THRU 6521 6523
$ 6528 6954 7220 7647 7652 7945 7948 7955
$
$
$ CHEXA Elements: First Order
$
CHEXA 17 2 10 11 21 23 34 35
+ 36 37
CHEXA 18 2 34 35 36 37 38 39
+ 40 41
CHEXA 19 2 38 39 40 41 42 43
+ 44 45
CHEXA 20 2 42 43 44 45 46 47
+ 48 49
CHEXA 21 2 46 47 48 49 50 51
+ 52 53
CHEXA 22 2 50 51 52 53 54 55
+ 56 57
CHEXA 23 2 54 55 56 57 58 59

376 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 60 61
CHEXA 24 2 58 59 60 61 62 63
+ 64 65
CHEXA 25 2 62 63 64 65 66 67
+ 68 69
CHEXA 26 2 66 67 68 69 70 71
+ 72 73
CHEXA 27 2 70 71 72 73 74 75
+ 76 77
CHEXA 28 2 74 75 76 77 78 79
+ 80 81
CHEXA 29 2 78 79 80 81 82 83
+ 84 85
CHEXA 30 2 82 83 84 85 86 87
+ 88 89
CHEXA 31 2 86 87 88 89 90 91
+ 92 93
CHEXA 32 2 90 91 92 93 94 95
+ 96 97
CHEXA 33 2 94 95 96 97 98 99
+ 100 101
CHEXA 34 2 98 99 100 101 102 103
+ 104 105
CHEXA 35 2 102 103 104 105 106 107
+ 108 109
CHEXA 36 2 106 107 108 109 110 111
+ 112 113
CHEXA 37 2 110 111 112 113 114 115
+ 116 117
CHEXA 38 2 114 115 116 117 118 119
+ 120 121
CHEXA 39 2 118 119 120 121 122 123
+ 124 125
CHEXA 40 2 122 123 124 125 126 127
+ 128 129
CHEXA 41 2 126 127 128 129 130 131
+ 132 133
CHEXA 42 2 130 131 132 133 134 135
+ 136 137
CHEXA 43 2 134 135 136 137 138 139
+ 140 141
CHEXA 44 2 138 139 140 141 142 143
+ 144 145
CHEXA 45 2 142 143 144 145 146 147
+ 148 149
CHEXA 46 2 146 147 148 149 150 151
+ 152 153
CHEXA 47 2 150 151 152 153 154 155
+ 156 157
CHEXA 48 2 154 155 156 157 158 159
+ 160 161
CHEXA 49 2 158 159 160 161 162 163
+ 164 165
CHEXA 50 2 162 163 164 165 166 167
+ 168 169
CHEXA 51 2 166 167 168 169 170 171
+ 172 173
CHEXA 52 2 170 171 172 173 174 175
+ 176 177
CHEXA 53 2 174 175 176 177 178 179
+ 180 181
CHEXA 54 2 178 179 180 181 182 183
+ 184 185
CHEXA 55 2 182 183 184 185 186 187
+ 188 189
CHEXA 56 2 186 187 188 189 190 191
+ 192 193
CHEXA 57 2 190 191 192 193 194 195
+ 196 197

Altair Engineering OptiStruct 13.0 Reference Guide 377

Proprietary Information of Altair Engineering


CHEXA 58 2 194 195 196 197 198 199
+ 200 201
CHEXA 139 2 198 199 200 201 522 523
+ 524 525
CHEXA 140 2 522 523 524 525 526 527
+ 528 529
CHEXA 141 2 526 527 528 529 530 531
+ 532 533
CHEXA 142 2 530 531 532 533 534 535
+ 536 537
CHEXA 143 2 534 535 536 537 538 539
+ 540 541
CHEXA 144 2 538 539 540 541 542 543
+ 544 545
CHEXA 145 2 542 543 544 545 546 547
+ 548 549
CHEXA 146 2 546 547 548 549 550 551
+ 552 553
CHEXA 147 2 550 551 552 553 554 555
+ 556 557
CHEXA 148 2 554 555 556 557 558 559
+ 560 561
CHEXA 149 2 558 559 560 561 562 563
+ 564 565
CHEXA 150 2 562 563 564 565 566 567
+ 568 569
CHEXA 151 2 566 567 568 569 570 571
+ 572 573
CHEXA 152 2 570 571 572 573 574 575
+ 576 577
CHEXA 153 2 574 575 576 577 578 579
+ 580 581
CHEXA 154 2 578 579 580 581 582 583
+ 584 585
CHEXA 155 2 582 583 584 585 586 587
+ 588 589
CHEXA 156 2 586 587 588 589 590 591
+ 592 593
CHEXA 157 2 590 591 592 593 594 595
+ 596 597
CHEXA 158 2 594 595 596 597 598 599
+ 600 601
CHEXA 159 2 598 599 600 601 602 603
+ 604 605
CHEXA 160 2 602 603 604 605 606 607
+ 608 609
CHEXA 161 2 606 607 608 609 610 611
+ 612 613
CHEXA 162 2 610 611 612 613 614 615
+ 616 617
CHEXA 163 2 614 615 616 617 618 619
+ 620 621
CHEXA 164 2 618 619 620 621 622 623
+ 624 625
CHEXA 165 2 622 623 624 625 626 627
+ 628 629
CHEXA 166 2 626 627 628 629 630 631
+ 632 633
CHEXA 167 2 630 631 632 633 634 635
+ 636 637
CHEXA 168 2 634 635 636 637 638 639
+ 640 641
CHEXA 169 2 638 639 640 641 642 643
+ 644 645
CHEXA 170 2 642 643 644 645 646 647
+ 648 649
CHEXA 171 2 646 647 648 649 650 651
+ 652 653
CHEXA 172 2 650 651 652 653 654 655

378 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 656 657
CHEXA 173 2 654 655 656 657 658 659
+ 660 661
CHEXA 174 2 658 659 660 661 662 663
+ 664 665
CHEXA 175 2 662 663 664 665 666 667
+ 668 669
CHEXA 176 2 666 667 668 669 670 671
+ 672 673
CHEXA 177 2 670 671 672 673 674 675
+ 676 677
CHEXA 178 2 674 675 676 677 678 679
+ 680 681
CHEXA 179 2 678 679 680 681 682 683
+ 684 685
CHEXA 180 2 682 683 684 685 686 687
+ 688 689
CHEXA 181 2 9 10 23 20 690 34
+ 37 691
CHEXA 182 2 690 34 37 691 692 38
+ 41 693
CHEXA 183 2 692 38 41 693 694 42
+ 45 695
CHEXA 184 2 694 42 45 695 696 46
+ 49 697
CHEXA 185 2 696 46 49 697 698 50
+ 53 699
CHEXA 186 2 698 50 53 699 700 54
+ 57 701
CHEXA 187 2 700 54 57 701 702 58
+ 61 703
CHEXA 188 2 702 58 61 703 704 62
+ 65 705
CHEXA 189 2 704 62 65 705 706 66
+ 69 707
CHEXA 190 2 706 66 69 707 708 70
+ 73 709
CHEXA 191 2 708 70 73 709 710 74
+ 77 711
CHEXA 192 2 710 74 77 711 712 78
+ 81 713
CHEXA 193 2 712 78 81 713 714 82
+ 85 715
CHEXA 194 2 714 82 85 715 716 86
+ 89 717
CHEXA 195 2 716 86 89 717 718 90
+ 93 719
CHEXA 196 2 718 90 93 719 720 94
+ 97 721
CHEXA 197 2 720 94 97 721 722 98
+ 101 723
CHEXA 198 2 722 98 101 723 724 102
+ 105 725
CHEXA 199 2 724 102 105 725 726 106
+ 109 727
CHEXA 200 2 726 106 109 727 728 110
+ 113 729
CHEXA 201 2 728 110 113 729 730 114
+ 117 731
CHEXA 202 2 730 114 117 731 732 118
+ 121 733
CHEXA 203 2 732 118 121 733 734 122
+ 125 735
CHEXA 204 2 734 122 125 735 736 126
+ 129 737
CHEXA 205 2 736 126 129 737 738 130
+ 133 739
CHEXA 206 2 738 130 133 739 740 134
+ 137 741

Altair Engineering OptiStruct 13.0 Reference Guide 379

Proprietary Information of Altair Engineering


CHEXA 207 2 740 134 137 741 742 138
+ 141 743
CHEXA 208 2 742 138 141 743 744 142
+ 145 745
CHEXA 209 2 744 142 145 745 746 146
+ 149 747
CHEXA 210 2 746 146 149 747 748 150
+ 153 749
CHEXA 211 2 748 150 153 749 750 154
+ 157 751
CHEXA 212 2 750 154 157 751 752 158
+ 161 753
CHEXA 213 2 752 158 161 753 754 162
+ 165 755
CHEXA 214 2 754 162 165 755 756 166
+ 169 757
CHEXA 215 2 756 166 169 757 758 170
+ 173 759
CHEXA 216 2 758 170 173 759 760 174
+ 177 761
CHEXA 217 2 760 174 177 761 762 178
+ 181 763
CHEXA 218 2 762 178 181 763 764 182
+ 185 765
CHEXA 219 2 764 182 185 765 766 186
+ 189 767
CHEXA 220 2 766 186 189 767 768 190
+ 193 769
CHEXA 221 2 768 190 193 769 770 194
+ 197 771
CHEXA 222 2 770 194 197 771 772 198
+ 201 773
CHEXA 303 2 772 198 201 773 934 522
+ 525 935
CHEXA 304 2 934 522 525 935 936 526
+ 529 937
CHEXA 305 2 936 526 529 937 938 530
+ 533 939
CHEXA 306 2 938 530 533 939 940 534
+ 537 941
CHEXA 307 2 940 534 537 941 942 538
+ 541 943
CHEXA 308 2 942 538 541 943 944 542
+ 545 945
CHEXA 309 2 944 542 545 945 946 546
+ 549 947
CHEXA 310 2 946 546 549 947 948 550
+ 553 949
CHEXA 311 2 948 550 553 949 950 554
+ 557 951
CHEXA 312 2 950 554 557 951 952 558
+ 561 953
CHEXA 313 2 952 558 561 953 954 562
+ 565 955
CHEXA 314 2 954 562 565 955 956 566
+ 569 957
CHEXA 315 2 956 566 569 957 958 570
+ 573 959
CHEXA 316 2 958 570 573 959 960 574
+ 577 961
CHEXA 317 2 960 574 577 961 962 578
+ 581 963
CHEXA 318 2 962 578 581 963 964 582
+ 585 965
CHEXA 319 2 964 582 585 965 966 586
+ 589 967
CHEXA 320 2 966 586 589 967 968 590
+ 593 969
CHEXA 321 2 968 590 593 969 970 594

380 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 597 971
CHEXA 322 2 970 594 597 971 972 598
+ 601 973
CHEXA 323 2 972 598 601 973 974 602
+ 605 975
CHEXA 324 2 974 602 605 975 976 606
+ 609 977
CHEXA 325 2 976 606 609 977 978 610
+ 613 979
CHEXA 326 2 978 610 613 979 980 614
+ 617 981
CHEXA 327 2 980 614 617 981 982 618
+ 621 983
CHEXA 328 2 982 618 621 983 984 622
+ 625 985
CHEXA 329 2 984 622 625 985 986 626
+ 629 987
CHEXA 330 2 986 626 629 987 988 630
+ 633 989
CHEXA 331 2 988 630 633 989 990 634
+ 637 991
CHEXA 332 2 990 634 637 991 992 638
+ 641 993
CHEXA 333 2 992 638 641 993 994 642
+ 645 995
CHEXA 334 2 994 642 645 995 996 646
+ 649 997
CHEXA 335 2 996 646 649 997 998 650
+ 653 999
CHEXA 336 2 998 650 653 999 1000 654
+ 657 1001
CHEXA 337 2 1000 654 657 1001 1002 658
+ 661 1003
CHEXA 338 2 1002 658 661 1003 1004 662
+ 665 1005
CHEXA 339 2 1004 662 665 1005 1006 666
+ 669 1007
CHEXA 340 2 1006 666 669 1007 1008 670
+ 673 1009
CHEXA 341 2 1008 670 673 1009 1010 674
+ 677 1011
CHEXA 342 2 1010 674 677 1011 1012 678
+ 681 1013
CHEXA 343 2 1012 678 681 1013 1014 682
+ 685 1015
CHEXA 344 2 1014 682 685 1015 1016 686
+ 689 1017
CHEXA 345 2 23 21 17 18 37 36
+ 1018 1019
CHEXA 346 2 37 36 1018 1019 41 40
+ 1020 1021
CHEXA 347 2 41 40 1020 1021 45 44
+ 1022 1023
CHEXA 348 2 45 44 1022 1023 49 48
+ 1024 1025
CHEXA 349 2 49 48 1024 1025 53 52
+ 1026 1027
CHEXA 350 2 53 52 1026 1027 57 56
+ 1028 1029
CHEXA 351 2 57 56 1028 1029 61 60
+ 1030 1031
CHEXA 352 2 61 60 1030 1031 65 64
+ 1032 1033
CHEXA 353 2 65 64 1032 1033 69 68
+ 1034 1035
CHEXA 354 2 69 68 1034 1035 73 72
+ 1036 1037
CHEXA 355 2 73 72 1036 1037 77 76
+ 1038 1039

Altair Engineering OptiStruct 13.0 Reference Guide 381

Proprietary Information of Altair Engineering


CHEXA 356 2 77 76 1038 1039 81 80
+ 1040 1041
CHEXA 357 2 81 80 1040 1041 85 84
+ 1042 1043
CHEXA 358 2 85 84 1042 1043 89 88
+ 1044 1045
CHEXA 359 2 89 88 1044 1045 93 92
+ 1046 1047
CHEXA 360 2 93 92 1046 1047 97 96
+ 1048 1049
CHEXA 361 2 97 96 1048 1049 101 100
+ 1050 1051
CHEXA 362 2 101 100 1050 1051 105 104
+ 1052 1053
CHEXA 363 2 105 104 1052 1053 109 108
+ 1054 1055
CHEXA 364 2 109 108 1054 1055 113 112
+ 1056 1057
CHEXA 365 2 113 112 1056 1057 117 116
+ 1058 1059
CHEXA 366 2 117 116 1058 1059 121 120
+ 1060 1061
CHEXA 367 2 121 120 1060 1061 125 124
+ 1062 1063
CHEXA 368 2 125 124 1062 1063 129 128
+ 1064 1065
CHEXA 369 2 129 128 1064 1065 133 132
+ 1066 1067
CHEXA 370 2 133 132 1066 1067 137 136
+ 1068 1069
CHEXA 371 2 137 136 1068 1069 141 140
+ 1070 1071
CHEXA 372 2 141 140 1070 1071 145 144
+ 1072 1073
CHEXA 373 2 145 144 1072 1073 149 148
+ 1074 1075
CHEXA 374 2 149 148 1074 1075 153 152
+ 1076 1077
CHEXA 375 2 153 152 1076 1077 157 156
+ 1078 1079
CHEXA 376 2 157 156 1078 1079 161 160
+ 1080 1081
CHEXA 377 2 161 160 1080 1081 165 164
+ 1082 1083
CHEXA 378 2 165 164 1082 1083 169 168
+ 1084 1085
CHEXA 379 2 169 168 1084 1085 173 172
+ 1086 1087
CHEXA 380 2 173 172 1086 1087 177 176
+ 1088 1089
CHEXA 381 2 177 176 1088 1089 181 180
+ 1090 1091
CHEXA 382 2 181 180 1090 1091 185 184
+ 1092 1093
CHEXA 383 2 185 184 1092 1093 189 188
+ 1094 1095
CHEXA 384 2 189 188 1094 1095 193 192
+ 1096 1097
CHEXA 385 2 193 192 1096 1097 197 196
+ 1098 1099
CHEXA 386 2 197 196 1098 1099 201 200
+ 1100 1101
CHEXA 467 2 201 200 1100 1101 525 524
+ 1262 1263
CHEXA 468 2 525 524 1262 1263 529 528
+ 1264 1265
CHEXA 469 2 529 528 1264 1265 533 532
+ 1266 1267
CHEXA 470 2 533 532 1266 1267 537 536

382 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 1268 1269
CHEXA 471 2 537 536 1268 1269 541 540
+ 1270 1271
CHEXA 472 2 541 540 1270 1271 545 544
+ 1272 1273
CHEXA 473 2 545 544 1272 1273 549 548
+ 1274 1275
CHEXA 474 2 549 548 1274 1275 553 552
+ 1276 1277
CHEXA 475 2 553 552 1276 1277 557 556
+ 1278 1279
CHEXA 476 2 557 556 1278 1279 561 560
+ 1280 1281
CHEXA 477 2 561 560 1280 1281 565 564
+ 1282 1283
CHEXA 478 2 565 564 1282 1283 569 568
+ 1284 1285
CHEXA 479 2 569 568 1284 1285 573 572
+ 1286 1287
CHEXA 480 2 573 572 1286 1287 577 576
+ 1288 1289
CHEXA 481 2 577 576 1288 1289 581 580
+ 1290 1291
CHEXA 482 2 581 580 1290 1291 585 584
+ 1292 1293
CHEXA 483 2 585 584 1292 1293 589 588
+ 1294 1295
CHEXA 484 2 589 588 1294 1295 593 592
+ 1296 1297
CHEXA 485 2 593 592 1296 1297 597 596
+ 1298 1299
CHEXA 486 2 597 596 1298 1299 601 600
+ 1300 1301
CHEXA 487 2 601 600 1300 1301 605 604
+ 1302 1303
CHEXA 488 2 605 604 1302 1303 609 608
+ 1304 1305
CHEXA 489 2 609 608 1304 1305 613 612
+ 1306 1307
CHEXA 490 2 613 612 1306 1307 617 616
+ 1308 1309
CHEXA 491 2 617 616 1308 1309 621 620
+ 1310 1311
CHEXA 492 2 621 620 1310 1311 625 624
+ 1312 1313
CHEXA 493 2 625 624 1312 1313 629 628
+ 1314 1315
CHEXA 494 2 629 628 1314 1315 633 632
+ 1316 1317
CHEXA 495 2 633 632 1316 1317 637 636
+ 1318 1319
CHEXA 496 2 637 636 1318 1319 641 640
+ 1320 1321
CHEXA 497 2 641 640 1320 1321 645 644
+ 1322 1323
CHEXA 498 2 645 644 1322 1323 649 648
+ 1324 1325
CHEXA 499 2 649 648 1324 1325 653 652
+ 1326 1327
CHEXA 500 2 653 652 1326 1327 657 656
+ 1328 1329
CHEXA 501 2 657 656 1328 1329 661 660
+ 1330 1331
CHEXA 502 2 661 660 1330 1331 665 664
+ 1332 1333
CHEXA 503 2 665 664 1332 1333 669 668
+ 1334 1335
CHEXA 504 2 669 668 1334 1335 673 672
+ 1336 1337

Altair Engineering OptiStruct 13.0 Reference Guide 383

Proprietary Information of Altair Engineering


CHEXA 505 2 673 672 1336 1337 677 676
+ 1338 1339
CHEXA 506 2 677 676 1338 1339 681 680
+ 1340 1341
CHEXA 507 2 681 680 1340 1341 685 684
+ 1342 1343
CHEXA 508 2 685 684 1342 1343 689 688
+ 1344 1345
CHEXA 509 2 20 23 18 19 691 37
+ 1019 1346
CHEXA 510 2 691 37 1019 1346 693 41
+ 1021 1347
CHEXA 511 2 693 41 1021 1347 695 45
+ 1023 1348
CHEXA 512 2 695 45 1023 1348 697 49
+ 1025 1349
CHEXA 513 2 697 49 1025 1349 699 53
+ 1027 1350
CHEXA 514 2 699 53 1027 1350 701 57
+ 1029 1351
CHEXA 515 2 701 57 1029 1351 703 61
+ 1031 1352
CHEXA 516 2 703 61 1031 1352 705 65
+ 1033 1353
CHEXA 517 2 705 65 1033 1353 707 69
+ 1035 1354
CHEXA 518 2 707 69 1035 1354 709 73
+ 1037 1355
CHEXA 519 2 709 73 1037 1355 711 77
+ 1039 1356
CHEXA 520 2 711 77 1039 1356 713 81
+ 1041 1357
CHEXA 521 2 713 81 1041 1357 715 85
+ 1043 1358
CHEXA 522 2 715 85 1043 1358 717 89
+ 1045 1359
CHEXA 523 2 717 89 1045 1359 719 93
+ 1047 1360
CHEXA 524 2 719 93 1047 1360 721 97
+ 1049 1361
CHEXA 525 2 721 97 1049 1361 723 101
+ 1051 1362
CHEXA 526 2 723 101 1051 1362 725 105
+ 1053 1363
CHEXA 527 2 725 105 1053 1363 727 109
+ 1055 1364
CHEXA 528 2 727 109 1055 1364 729 113
+ 1057 1365
CHEXA 529 2 729 113 1057 1365 731 117
+ 1059 1366
CHEXA 530 2 731 117 1059 1366 733 121
+ 1061 1367
CHEXA 531 2 733 121 1061 1367 735 125
+ 1063 1368
CHEXA 532 2 735 125 1063 1368 737 129
+ 1065 1369
CHEXA 533 2 737 129 1065 1369 739 133
+ 1067 1370
CHEXA 534 2 739 133 1067 1370 741 137
+ 1069 1371
CHEXA 535 2 741 137 1069 1371 743 141
+ 1071 1372
CHEXA 536 2 743 141 1071 1372 745 145
+ 1073 1373
CHEXA 537 2 745 145 1073 1373 747 149
+ 1075 1374
CHEXA 538 2 747 149 1075 1374 749 153
+ 1077 1375
CHEXA 539 2 749 153 1077 1375 751 157

384 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 1079 1376
CHEXA 540 2 751 157 1079 1376 753 161
+ 1081 1377
CHEXA 541 2 753 161 1081 1377 755 165
+ 1083 1378
CHEXA 542 2 755 165 1083 1378 757 169
+ 1085 1379
CHEXA 543 2 757 169 1085 1379 759 173
+ 1087 1380
CHEXA 544 2 759 173 1087 1380 761 177
+ 1089 1381
CHEXA 545 2 761 177 1089 1381 763 181
+ 1091 1382
CHEXA 546 2 763 181 1091 1382 765 185
+ 1093 1383
CHEXA 547 2 765 185 1093 1383 767 189
+ 1095 1384
CHEXA 548 2 767 189 1095 1384 769 193
+ 1097 1385
CHEXA 549 2 769 193 1097 1385 771 197
+ 1099 1386
CHEXA 550 2 771 197 1099 1386 773 201
+ 1101 1387
CHEXA 631 2 773 201 1101 1387 935 525
+ 1263 1468
CHEXA 632 2 935 525 1263 1468 937 529
+ 1265 1469
CHEXA 633 2 937 529 1265 1469 939 533
+ 1267 1470
CHEXA 634 2 939 533 1267 1470 941 537
+ 1269 1471
CHEXA 635 2 941 537 1269 1471 943 541
+ 1271 1472
CHEXA 636 2 943 541 1271 1472 945 545
+ 1273 1473
CHEXA 637 2 945 545 1273 1473 947 549
+ 1275 1474
CHEXA 638 2 947 549 1275 1474 949 553
+ 1277 1475
CHEXA 639 2 949 553 1277 1475 951 557
+ 1279 1476
CHEXA 640 2 951 557 1279 1476 953 561
+ 1281 1477
CHEXA 641 2 953 561 1281 1477 955 565
+ 1283 1478
CHEXA 642 2 955 565 1283 1478 957 569
+ 1285 1479
CHEXA 643 2 957 569 1285 1479 959 573
+ 1287 1480
CHEXA 644 2 959 573 1287 1480 961 577
+ 1289 1481
CHEXA 645 2 961 577 1289 1481 963 581
+ 1291 1482
CHEXA 646 2 963 581 1291 1482 965 585
+ 1293 1483
CHEXA 647 2 965 585 1293 1483 967 589
+ 1295 1484
CHEXA 648 2 967 589 1295 1484 969 593
+ 1297 1485
CHEXA 649 2 969 593 1297 1485 971 597
+ 1299 1486
CHEXA 650 2 971 597 1299 1486 973 601
+ 1301 1487
CHEXA 651 2 973 601 1301 1487 975 605
+ 1303 1488
CHEXA 652 2 975 605 1303 1488 977 609
+ 1305 1489
CHEXA 653 2 977 609 1305 1489 979 613
+ 1307 1490

Altair Engineering OptiStruct 13.0 Reference Guide 385

Proprietary Information of Altair Engineering


CHEXA 654 2 979 613 1307 1490 981 617
+ 1309 1491
CHEXA 655 2 981 617 1309 1491 983 621
+ 1311 1492
CHEXA 656 2 983 621 1311 1492 985 625
+ 1313 1493
CHEXA 657 2 985 625 1313 1493 987 629
+ 1315 1494
CHEXA 658 2 987 629 1315 1494 989 633
+ 1317 1495
CHEXA 659 2 989 633 1317 1495 991 637
+ 1319 1496
CHEXA 660 2 991 637 1319 1496 993 641
+ 1321 1497
CHEXA 661 2 993 641 1321 1497 995 645
+ 1323 1498
CHEXA 662 2 995 645 1323 1498 997 649
+ 1325 1499
CHEXA 663 2 997 649 1325 1499 999 653
+ 1327 1500
CHEXA 664 2 999 653 1327 1500 1001 657
+ 1329 1501
CHEXA 665 2 1001 657 1329 1501 1003 661
+ 1331 1502
CHEXA 666 2 1003 661 1331 1502 1005 665
+ 1333 1503
CHEXA 667 2 1005 665 1333 1503 1007 669
+ 1335 1504
CHEXA 668 2 1007 669 1335 1504 1009 673
+ 1337 1505
CHEXA 669 2 1009 673 1337 1505 1011 677
+ 1339 1506
CHEXA 670 2 1011 677 1339 1506 1013 681
+ 1341 1507
CHEXA 671 2 1013 681 1341 1507 1015 685
+ 1343 1508
CHEXA 672 2 1015 685 1343 1508 1017 689
+ 1345 1509
CHEXA 673 2 12 13 14 22 1510 1511
+ 1512 1513
CHEXA 674 2 1510 1511 1512 1513 1514 1515
+ 1516 1517
CHEXA 675 2 1514 1515 1516 1517 1518 1519
+ 1520 1521
CHEXA 676 2 1518 1519 1520 1521 1522 1523
+ 1524 1525
CHEXA 677 2 1522 1523 1524 1525 1526 1527
+ 1528 1529
CHEXA 678 2 1526 1527 1528 1529 1530 1531
+ 1532 1533
CHEXA 679 2 1530 1531 1532 1533 1534 1535
+ 1536 1537
CHEXA 680 2 1534 1535 1536 1537 1538 1539
+ 1540 1541
CHEXA 681 2 1538 1539 1540 1541 1542 1543
+ 1544 1545
CHEXA 682 2 1542 1543 1544 1545 1546 1547
+ 1548 1549
CHEXA 683 2 1546 1547 1548 1549 1550 1551
+ 1552 1553
CHEXA 684 2 1550 1551 1552 1553 1554 1555
+ 1556 1557
CHEXA 685 2 1554 1555 1556 1557 1558 1559
+ 1560 1561
CHEXA 686 2 1558 1559 1560 1561 1562 1563
+ 1564 1565
CHEXA 687 2 1562 1563 1564 1565 1566 1567
+ 1568 1569
CHEXA 688 2 1566 1567 1568 1569 1570 1571

386 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 1572 1573
CHEXA 689 2 1570 1571 1572 1573 1574 1575
+ 1576 1577
CHEXA 690 2 1574 1575 1576 1577 1578 1579
+ 1580 1581
CHEXA 691 2 1578 1579 1580 1581 1582 1583
+ 1584 1585
CHEXA 692 2 1582 1583 1584 1585 1586 1587
+ 1588 1589
CHEXA 693 2 1586 1587 1588 1589 1590 1591
+ 1592 1593
CHEXA 694 2 1590 1591 1592 1593 1594 1595
+ 1596 1597
CHEXA 695 2 1594 1595 1596 1597 1598 1599
+ 1600 1601
CHEXA 696 2 1598 1599 1600 1601 1602 1603
+ 1604 1605
CHEXA 697 2 1602 1603 1604 1605 1606 1607
+ 1608 1609
CHEXA 698 2 1606 1607 1608 1609 1610 1611
+ 1612 1613
CHEXA 699 2 1610 1611 1612 1613 1614 1615
+ 1616 1617
CHEXA 700 2 1614 1615 1616 1617 1618 1619
+ 1620 1621
CHEXA 701 2 1618 1619 1620 1621 1622 1623
+ 1624 1625
CHEXA 702 2 1622 1623 1624 1625 1626 1627
+ 1628 1629
CHEXA 703 2 1626 1627 1628 1629 1630 1631
+ 1632 1633
CHEXA 704 2 1630 1631 1632 1633 1634 1635
+ 1636 1637
CHEXA 705 2 1634 1635 1636 1637 1638 1639
+ 1640 1641
CHEXA 706 2 1638 1639 1640 1641 1642 1643
+ 1644 1645
CHEXA 707 2 1642 1643 1644 1645 1646 1647
+ 1648 1649
CHEXA 708 2 1646 1647 1648 1649 1650 1651
+ 1652 1653
CHEXA 709 2 1650 1651 1652 1653 1654 1655
+ 1656 1657
CHEXA 710 2 1654 1655 1656 1657 1658 1659
+ 1660 1661
CHEXA 711 2 1658 1659 1660 1661 1662 1663
+ 1664 1665
CHEXA 712 2 1662 1663 1664 1665 1666 1667
+ 1668 1669
CHEXA 713 2 1666 1667 1668 1669 1670 1671
+ 1672 1673
CHEXA 714 2 1670 1671 1672 1673 1674 1675
+ 1676 1677
CHEXA 795 2 1674 1675 1676 1677 1998 1999
+ 2000 2001
CHEXA 796 2 1998 1999 2000 2001 2002 2003
+ 2004 2005
CHEXA 797 2 2002 2003 2004 2005 2006 2007
+ 2008 2009
CHEXA 798 2 2006 2007 2008 2009 2010 2011
+ 2012 2013
CHEXA 799 2 2010 2011 2012 2013 2014 2015
+ 2016 2017
CHEXA 800 2 2014 2015 2016 2017 2018 2019
+ 2020 2021
CHEXA 801 2 2018 2019 2020 2021 2022 2023
+ 2024 2025
CHEXA 802 2 2022 2023 2024 2025 2026 2027
+ 2028 2029

Altair Engineering OptiStruct 13.0 Reference Guide 387

Proprietary Information of Altair Engineering


CHEXA 803 2 2026 2027 2028 2029 2030 2031
+ 2032 2033
CHEXA 804 2 2030 2031 2032 2033 2034 2035
+ 2036 2037
CHEXA 805 2 2034 2035 2036 2037 2038 2039
+ 2040 2041
CHEXA 806 2 2038 2039 2040 2041 2042 2043
+ 2044 2045
CHEXA 807 2 2042 2043 2044 2045 2046 2047
+ 2048 2049
CHEXA 808 2 2046 2047 2048 2049 2050 2051
+ 2052 2053
CHEXA 809 2 2050 2051 2052 2053 2054 2055
+ 2056 2057
CHEXA 810 2 2054 2055 2056 2057 2058 2059
+ 2060 2061
CHEXA 811 2 2058 2059 2060 2061 2062 2063
+ 2064 2065
CHEXA 812 2 2062 2063 2064 2065 2066 2067
+ 2068 2069
CHEXA 813 2 2066 2067 2068 2069 2070 2071
+ 2072 2073
CHEXA 814 2 2070 2071 2072 2073 2074 2075
+ 2076 2077
CHEXA 815 2 2074 2075 2076 2077 2078 2079
+ 2080 2081
CHEXA 816 2 2078 2079 2080 2081 2082 2083
+ 2084 2085
CHEXA 817 2 2082 2083 2084 2085 2086 2087
+ 2088 2089
CHEXA 818 2 2086 2087 2088 2089 2090 2091
+ 2092 2093
CHEXA 819 2 2090 2091 2092 2093 2094 2095
+ 2096 2097
CHEXA 820 2 2094 2095 2096 2097 2098 2099
+ 2100 2101
CHEXA 821 2 2098 2099 2100 2101 2102 2103
+ 2104 2105
CHEXA 822 2 2102 2103 2104 2105 2106 2107
+ 2108 2109
CHEXA 823 2 2106 2107 2108 2109 2110 2111
+ 2112 2113
CHEXA 824 2 2110 2111 2112 2113 2114 2115
+ 2116 2117
CHEXA 825 2 2114 2115 2116 2117 2118 2119
+ 2120 2121
CHEXA 826 2 2118 2119 2120 2121 2122 2123
+ 2124 2125
CHEXA 827 2 2122 2123 2124 2125 2126 2127
+ 2128 2129
CHEXA 828 2 2126 2127 2128 2129 2130 2131
+ 2132 2133
CHEXA 829 2 2130 2131 2132 2133 2134 2135
+ 2136 2137
CHEXA 830 2 2134 2135 2136 2137 2138 2139
+ 2140 2141
CHEXA 831 2 2138 2139 2140 2141 2142 2143
+ 2144 2145
CHEXA 832 2 2142 2143 2144 2145 2146 2147
+ 2148 2149
CHEXA 833 2 2146 2147 2148 2149 2150 2151
+ 2152 2153
CHEXA 834 2 2150 2151 2152 2153 2154 2155
+ 2156 2157
CHEXA 835 2 2154 2155 2156 2157 2158 2159
+ 2160 2161
CHEXA 836 2 2158 2159 2160 2161 2162 2163
+ 2164 2165
CHEXA 837 2 11 12 22 21 35 1510

388 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 1513 36
CHEXA 838 2 35 1510 1513 36 39 1514
+ 1517 40
CHEXA 839 2 39 1514 1517 40 43 1518
+ 1521 44
CHEXA 840 2 43 1518 1521 44 47 1522
+ 1525 48
CHEXA 841 2 47 1522 1525 48 51 1526
+ 1529 52
CHEXA 842 2 51 1526 1529 52 55 1530
+ 1533 56
CHEXA 843 2 55 1530 1533 56 59 1534
+ 1537 60
CHEXA 844 2 59 1534 1537 60 63 1538
+ 1541 64
CHEXA 845 2 63 1538 1541 64 67 1542
+ 1545 68
CHEXA 846 2 67 1542 1545 68 71 1546
+ 1549 72
CHEXA 847 2 71 1546 1549 72 75 1550
+ 1553 76
CHEXA 848 2 75 1550 1553 76 79 1554
+ 1557 80
CHEXA 849 2 79 1554 1557 80 83 1558
+ 1561 84
CHEXA 850 2 83 1558 1561 84 87 1562
+ 1565 88
CHEXA 851 2 87 1562 1565 88 91 1566
+ 1569 92
CHEXA 852 2 91 1566 1569 92 95 1570
+ 1573 96
CHEXA 853 2 95 1570 1573 96 99 1574
+ 1577 100
CHEXA 854 2 99 1574 1577 100 103 1578
+ 1581 104
CHEXA 855 2 103 1578 1581 104 107 1582
+ 1585 108
CHEXA 856 2 107 1582 1585 108 111 1586
+ 1589 112
CHEXA 857 2 111 1586 1589 112 115 1590
+ 1593 116
CHEXA 858 2 115 1590 1593 116 119 1594
+ 1597 120
CHEXA 859 2 119 1594 1597 120 123 1598
+ 1601 124
CHEXA 860 2 123 1598 1601 124 127 1602
+ 1605 128
CHEXA 861 2 127 1602 1605 128 131 1606
+ 1609 132
CHEXA 862 2 131 1606 1609 132 135 1610
+ 1613 136
CHEXA 863 2 135 1610 1613 136 139 1614
+ 1617 140
CHEXA 864 2 139 1614 1617 140 143 1618
+ 1621 144
CHEXA 865 2 143 1618 1621 144 147 1622
+ 1625 148
CHEXA 866 2 147 1622 1625 148 151 1626
+ 1629 152
CHEXA 867 2 151 1626 1629 152 155 1630
+ 1633 156
CHEXA 868 2 155 1630 1633 156 159 1634
+ 1637 160
CHEXA 869 2 159 1634 1637 160 163 1638
+ 1641 164
CHEXA 870 2 163 1638 1641 164 167 1642
+ 1645 168
CHEXA 871 2 167 1642 1645 168 171 1646
+ 1649 172

Altair Engineering OptiStruct 13.0 Reference Guide 389

Proprietary Information of Altair Engineering


CHEXA 872 2 171 1646 1649 172 175 1650
+ 1653 176
CHEXA 873 2 175 1650 1653 176 179 1654
+ 1657 180
CHEXA 874 2 179 1654 1657 180 183 1658
+ 1661 184
CHEXA 875 2 183 1658 1661 184 187 1662
+ 1665 188
CHEXA 876 2 187 1662 1665 188 191 1666
+ 1669 192
CHEXA 877 2 191 1666 1669 192 195 1670
+ 1673 196
CHEXA 878 2 195 1670 1673 196 199 1674
+ 1677 200
CHEXA 959 2 199 1674 1677 200 523 1998
+ 2001 524
CHEXA 960 2 523 1998 2001 524 527 2002
+ 2005 528
CHEXA 961 2 527 2002 2005 528 531 2006
+ 2009 532
CHEXA 962 2 531 2006 2009 532 535 2010
+ 2013 536
CHEXA 963 2 535 2010 2013 536 539 2014
+ 2017 540
CHEXA 964 2 539 2014 2017 540 543 2018
+ 2021 544
CHEXA 965 2 543 2018 2021 544 547 2022
+ 2025 548
CHEXA 966 2 547 2022 2025 548 551 2026
+ 2029 552
CHEXA 967 2 551 2026 2029 552 555 2030
+ 2033 556
CHEXA 968 2 555 2030 2033 556 559 2034
+ 2037 560
CHEXA 969 2 559 2034 2037 560 563 2038
+ 2041 564
CHEXA 970 2 563 2038 2041 564 567 2042
+ 2045 568
CHEXA 971 2 567 2042 2045 568 571 2046
+ 2049 572
CHEXA 972 2 571 2046 2049 572 575 2050
+ 2053 576
CHEXA 973 2 575 2050 2053 576 579 2054
+ 2057 580
CHEXA 974 2 579 2054 2057 580 583 2058
+ 2061 584
CHEXA 975 2 583 2058 2061 584 587 2062
+ 2065 588
CHEXA 976 2 587 2062 2065 588 591 2066
+ 2069 592
CHEXA 977 2 591 2066 2069 592 595 2070
+ 2073 596
CHEXA 978 2 595 2070 2073 596 599 2074
+ 2077 600
CHEXA 979 2 599 2074 2077 600 603 2078
+ 2081 604
CHEXA 980 2 603 2078 2081 604 607 2082
+ 2085 608
CHEXA 981 2 607 2082 2085 608 611 2086
+ 2089 612
CHEXA 982 2 611 2086 2089 612 615 2090
+ 2093 616
CHEXA 983 2 615 2090 2093 616 619 2094
+ 2097 620
CHEXA 984 2 619 2094 2097 620 623 2098
+ 2101 624
CHEXA 985 2 623 2098 2101 624 627 2102
+ 2105 628
CHEXA 986 2 627 2102 2105 628 631 2106

390 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 2109 632
CHEXA 987 2 631 2106 2109 632 635 2110
+ 2113 636
CHEXA 988 2 635 2110 2113 636 639 2114
+ 2117 640
CHEXA 989 2 639 2114 2117 640 643 2118
+ 2121 644
CHEXA 990 2 643 2118 2121 644 647 2122
+ 2125 648
CHEXA 991 2 647 2122 2125 648 651 2126
+ 2129 652
CHEXA 992 2 651 2126 2129 652 655 2130
+ 2133 656
CHEXA 993 2 655 2130 2133 656 659 2134
+ 2137 660
CHEXA 994 2 659 2134 2137 660 663 2138
+ 2141 664
CHEXA 995 2 663 2138 2141 664 667 2142
+ 2145 668
CHEXA 996 2 667 2142 2145 668 671 2146
+ 2149 672
CHEXA 997 2 671 2146 2149 672 675 2150
+ 2153 676
CHEXA 998 2 675 2150 2153 676 679 2154
+ 2157 680
CHEXA 999 2 679 2154 2157 680 683 2158
+ 2161 684
CHEXA 1000 2 683 2158 2161 684 687 2162
+ 2165 688
CHEXA 1001 2 22 14 15 16 1513 1512
+ 2166 2167
CHEXA 1002 2 1513 1512 2166 2167 1517 1516
+ 2168 2169
CHEXA 1003 2 1517 1516 2168 2169 1521 1520
+ 2170 2171
CHEXA 1004 2 1521 1520 2170 2171 1525 1524
+ 2172 2173
CHEXA 1005 2 1525 1524 2172 2173 1529 1528
+ 2174 2175
CHEXA 1006 2 1529 1528 2174 2175 1533 1532
+ 2176 2177
CHEXA 1007 2 1533 1532 2176 2177 1537 1536
+ 2178 2179
CHEXA 1008 2 1537 1536 2178 2179 1541 1540
+ 2180 2181
CHEXA 1009 2 1541 1540 2180 2181 1545 1544
+ 2182 2183
CHEXA 1010 2 1545 1544 2182 2183 1549 1548
+ 2184 2185
CHEXA 1011 2 1549 1548 2184 2185 1553 1552
+ 2186 2187
CHEXA 1012 2 1553 1552 2186 2187 1557 1556
+ 2188 2189
CHEXA 1013 2 1557 1556 2188 2189 1561 1560
+ 2190 2191
CHEXA 1014 2 1561 1560 2190 2191 1565 1564
+ 2192 2193
CHEXA 1015 2 1565 1564 2192 2193 1569 1568
+ 2194 2195
CHEXA 1016 2 1569 1568 2194 2195 1573 1572
+ 2196 2197
CHEXA 1017 2 1573 1572 2196 2197 1577 1576
+ 2198 2199
CHEXA 1018 2 1577 1576 2198 2199 1581 1580
+ 2200 2201
CHEXA 1019 2 1581 1580 2200 2201 1585 1584
+ 2202 2203
CHEXA 1020 2 1585 1584 2202 2203 1589 1588
+ 2204 2205

Altair Engineering OptiStruct 13.0 Reference Guide 391

Proprietary Information of Altair Engineering


CHEXA 1021 2 1589 1588 2204 2205 1593 1592
+ 2206 2207
CHEXA 1022 2 1593 1592 2206 2207 1597 1596
+ 2208 2209
CHEXA 1023 2 1597 1596 2208 2209 1601 1600
+ 2210 2211
CHEXA 1024 2 1601 1600 2210 2211 1605 1604
+ 2212 2213
CHEXA 1025 2 1605 1604 2212 2213 1609 1608
+ 2214 2215
CHEXA 1026 2 1609 1608 2214 2215 1613 1612
+ 2216 2217
CHEXA 1027 2 1613 1612 2216 2217 1617 1616
+ 2218 2219
CHEXA 1028 2 1617 1616 2218 2219 1621 1620
+ 2220 2221
CHEXA 1029 2 1621 1620 2220 2221 1625 1624
+ 2222 2223
CHEXA 1030 2 1625 1624 2222 2223 1629 1628
+ 2224 2225
CHEXA 1031 2 1629 1628 2224 2225 1633 1632
+ 2226 2227
CHEXA 1032 2 1633 1632 2226 2227 1637 1636
+ 2228 2229
CHEXA 1033 2 1637 1636 2228 2229 1641 1640
+ 2230 2231
CHEXA 1034 2 1641 1640 2230 2231 1645 1644
+ 2232 2233
CHEXA 1035 2 1645 1644 2232 2233 1649 1648
+ 2234 2235
CHEXA 1036 2 1649 1648 2234 2235 1653 1652
+ 2236 2237
CHEXA 1037 2 1653 1652 2236 2237 1657 1656
+ 2238 2239
CHEXA 1038 2 1657 1656 2238 2239 1661 1660
+ 2240 2241
CHEXA 1039 2 1661 1660 2240 2241 1665 1664
+ 2242 2243
CHEXA 1040 2 1665 1664 2242 2243 1669 1668
+ 2244 2245
CHEXA 1041 2 1669 1668 2244 2245 1673 1672
+ 2246 2247
CHEXA 1042 2 1673 1672 2246 2247 1677 1676
+ 2248 2249
CHEXA 1123 2 1677 1676 2248 2249 2001 2000
+ 2410 2411
CHEXA 1124 2 2001 2000 2410 2411 2005 2004
+ 2412 2413
CHEXA 1125 2 2005 2004 2412 2413 2009 2008
+ 2414 2415
CHEXA 1126 2 2009 2008 2414 2415 2013 2012
+ 2416 2417
CHEXA 1127 2 2013 2012 2416 2417 2017 2016
+ 2418 2419
CHEXA 1128 2 2017 2016 2418 2419 2021 2020
+ 2420 2421
CHEXA 1129 2 2021 2020 2420 2421 2025 2024
+ 2422 2423
CHEXA 1130 2 2025 2024 2422 2423 2029 2028
+ 2424 2425
CHEXA 1131 2 2029 2028 2424 2425 2033 2032
+ 2426 2427
CHEXA 1132 2 2033 2032 2426 2427 2037 2036
+ 2428 2429
CHEXA 1133 2 2037 2036 2428 2429 2041 2040
+ 2430 2431
CHEXA 1134 2 2041 2040 2430 2431 2045 2044
+ 2432 2433
CHEXA 1135 2 2045 2044 2432 2433 2049 2048

392 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 2434 2435
CHEXA 1136 2 2049 2048 2434 2435 2053 2052
+ 2436 2437
CHEXA 1137 2 2053 2052 2436 2437 2057 2056
+ 2438 2439
CHEXA 1138 2 2057 2056 2438 2439 2061 2060
+ 2440 2441
CHEXA 1139 2 2061 2060 2440 2441 2065 2064
+ 2442 2443
CHEXA 1140 2 2065 2064 2442 2443 2069 2068
+ 2444 2445
CHEXA 1141 2 2069 2068 2444 2445 2073 2072
+ 2446 2447
CHEXA 1142 2 2073 2072 2446 2447 2077 2076
+ 2448 2449
CHEXA 1143 2 2077 2076 2448 2449 2081 2080
+ 2450 2451
CHEXA 1144 2 2081 2080 2450 2451 2085 2084
+ 2452 2453
CHEXA 1145 2 2085 2084 2452 2453 2089 2088
+ 2454 2455
CHEXA 1146 2 2089 2088 2454 2455 2093 2092
+ 2456 2457
CHEXA 1147 2 2093 2092 2456 2457 2097 2096
+ 2458 2459
CHEXA 1148 2 2097 2096 2458 2459 2101 2100
+ 2460 2461
CHEXA 1149 2 2101 2100 2460 2461 2105 2104
+ 2462 2463
CHEXA 1150 2 2105 2104 2462 2463 2109 2108
+ 2464 2465
CHEXA 1151 2 2109 2108 2464 2465 2113 2112
+ 2466 2467
CHEXA 1152 2 2113 2112 2466 2467 2117 2116
+ 2468 2469
CHEXA 1153 2 2117 2116 2468 2469 2121 2120
+ 2470 2471
CHEXA 1154 2 2121 2120 2470 2471 2125 2124
+ 2472 2473
CHEXA 1155 2 2125 2124 2472 2473 2129 2128
+ 2474 2475
CHEXA 1156 2 2129 2128 2474 2475 2133 2132
+ 2476 2477
CHEXA 1157 2 2133 2132 2476 2477 2137 2136
+ 2478 2479
CHEXA 1158 2 2137 2136 2478 2479 2141 2140
+ 2480 2481
CHEXA 1159 2 2141 2140 2480 2481 2145 2144
+ 2482 2483
CHEXA 1160 2 2145 2144 2482 2483 2149 2148
+ 2484 2485
CHEXA 1161 2 2149 2148 2484 2485 2153 2152
+ 2486 2487
CHEXA 1162 2 2153 2152 2486 2487 2157 2156
+ 2488 2489
CHEXA 1163 2 2157 2156 2488 2489 2161 2160
+ 2490 2491
CHEXA 1164 2 2161 2160 2490 2491 2165 2164
+ 2492 2493
CHEXA 1165 2 21 22 16 17 36 1513
+ 2167 1018
CHEXA 1166 2 36 1513 2167 1018 40 1517
+ 2169 1020
CHEXA 1167 2 40 1517 2169 1020 44 1521
+ 2171 1022
CHEXA 1168 2 44 1521 2171 1022 48 1525
+ 2173 1024
CHEXA 1169 2 48 1525 2173 1024 52 1529
+ 2175 1026

Altair Engineering OptiStruct 13.0 Reference Guide 393

Proprietary Information of Altair Engineering


CHEXA 1170 2 52 1529 2175 1026 56 1533
+ 2177 1028
CHEXA 1171 2 56 1533 2177 1028 60 1537
+ 2179 1030
CHEXA 1172 2 60 1537 2179 1030 64 1541
+ 2181 1032
CHEXA 1173 2 64 1541 2181 1032 68 1545
+ 2183 1034
CHEXA 1174 2 68 1545 2183 1034 72 1549
+ 2185 1036
CHEXA 1175 2 72 1549 2185 1036 76 1553
+ 2187 1038
CHEXA 1176 2 76 1553 2187 1038 80 1557
+ 2189 1040
CHEXA 1177 2 80 1557 2189 1040 84 1561
+ 2191 1042
CHEXA 1178 2 84 1561 2191 1042 88 1565
+ 2193 1044
CHEXA 1179 2 88 1565 2193 1044 92 1569
+ 2195 1046
CHEXA 1180 2 92 1569 2195 1046 96 1573
+ 2197 1048
CHEXA 1181 2 96 1573 2197 1048 100 1577
+ 2199 1050
CHEXA 1182 2 100 1577 2199 1050 104 1581
+ 2201 1052
CHEXA 1183 2 104 1581 2201 1052 108 1585
+ 2203 1054
CHEXA 1184 2 108 1585 2203 1054 112 1589
+ 2205 1056
CHEXA 1185 2 112 1589 2205 1056 116 1593
+ 2207 1058
CHEXA 1186 2 116 1593 2207 1058 120 1597
+ 2209 1060
CHEXA 1187 2 120 1597 2209 1060 124 1601
+ 2211 1062
CHEXA 1188 2 124 1601 2211 1062 128 1605
+ 2213 1064
CHEXA 1189 2 128 1605 2213 1064 132 1609
+ 2215 1066
CHEXA 1190 2 132 1609 2215 1066 136 1613
+ 2217 1068
CHEXA 1191 2 136 1613 2217 1068 140 1617
+ 2219 1070
CHEXA 1192 2 140 1617 2219 1070 144 1621
+ 2221 1072
CHEXA 1193 2 144 1621 2221 1072 148 1625
+ 2223 1074
CHEXA 1194 2 148 1625 2223 1074 152 1629
+ 2225 1076
CHEXA 1195 2 152 1629 2225 1076 156 1633
+ 2227 1078
CHEXA 1196 2 156 1633 2227 1078 160 1637
+ 2229 1080
CHEXA 1197 2 160 1637 2229 1080 164 1641
+ 2231 1082
CHEXA 1198 2 164 1641 2231 1082 168 1645
+ 2233 1084
CHEXA 1199 2 168 1645 2233 1084 172 1649
+ 2235 1086
CHEXA 1200 2 172 1649 2235 1086 176 1653
+ 2237 1088
CHEXA 1201 2 176 1653 2237 1088 180 1657
+ 2239 1090
CHEXA 1202 2 180 1657 2239 1090 184 1661
+ 2241 1092
CHEXA 1203 2 184 1661 2241 1092 188 1665
+ 2243 1094
CHEXA 1204 2 188 1665 2243 1094 192 1669

394 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 2245 1096
CHEXA 1205 2 192 1669 2245 1096 196 1673
+ 2247 1098
CHEXA 1206 2 196 1673 2247 1098 200 1677
+ 2249 1100
CHEXA 1287 2 200 1677 2249 1100 524 2001
+ 2411 1262
CHEXA 1288 2 524 2001 2411 1262 528 2005
+ 2413 1264
CHEXA 1289 2 528 2005 2413 1264 532 2009
+ 2415 1266
CHEXA 1290 2 532 2009 2415 1266 536 2013
+ 2417 1268
CHEXA 1291 2 536 2013 2417 1268 540 2017
+ 2419 1270
CHEXA 1292 2 540 2017 2419 1270 544 2021
+ 2421 1272
CHEXA 1293 2 544 2021 2421 1272 548 2025
+ 2423 1274
CHEXA 1294 2 548 2025 2423 1274 552 2029
+ 2425 1276
CHEXA 1295 2 552 2029 2425 1276 556 2033
+ 2427 1278
CHEXA 1296 2 556 2033 2427 1278 560 2037
+ 2429 1280
CHEXA 1297 2 560 2037 2429 1280 564 2041
+ 2431 1282
CHEXA 1298 2 564 2041 2431 1282 568 2045
+ 2433 1284
CHEXA 1299 2 568 2045 2433 1284 572 2049
+ 2435 1286
CHEXA 1300 2 572 2049 2435 1286 576 2053
+ 2437 1288
CHEXA 1301 2 576 2053 2437 1288 580 2057
+ 2439 1290
CHEXA 1302 2 580 2057 2439 1290 584 2061
+ 2441 1292
CHEXA 1303 2 584 2061 2441 1292 588 2065
+ 2443 1294
CHEXA 1304 2 588 2065 2443 1294 592 2069
+ 2445 1296
CHEXA 1305 2 592 2069 2445 1296 596 2073
+ 2447 1298
CHEXA 1306 2 596 2073 2447 1298 600 2077
+ 2449 1300
CHEXA 1307 2 600 2077 2449 1300 604 2081
+ 2451 1302
CHEXA 1308 2 604 2081 2451 1302 608 2085
+ 2453 1304
CHEXA 1309 2 608 2085 2453 1304 612 2089
+ 2455 1306
CHEXA 1310 2 612 2089 2455 1306 616 2093
+ 2457 1308
CHEXA 1311 2 616 2093 2457 1308 620 2097
+ 2459 1310
CHEXA 1312 2 620 2097 2459 1310 624 2101
+ 2461 1312
CHEXA 1313 2 624 2101 2461 1312 628 2105
+ 2463 1314
CHEXA 1314 2 628 2105 2463 1314 632 2109
+ 2465 1316
CHEXA 1315 2 632 2109 2465 1316 636 2113
+ 2467 1318
CHEXA 1316 2 636 2113 2467 1318 640 2117
+ 2469 1320
CHEXA 1317 2 640 2117 2469 1320 644 2121
+ 2471 1322
CHEXA 1318 2 644 2121 2471 1322 648 2125
+ 2473 1324

Altair Engineering OptiStruct 13.0 Reference Guide 395

Proprietary Information of Altair Engineering


CHEXA 1319 2 648 2125 2473 1324 652 2129
+ 2475 1326
CHEXA 1320 2 652 2129 2475 1326 656 2133
+ 2477 1328
CHEXA 1321 2 656 2133 2477 1328 660 2137
+ 2479 1330
CHEXA 1322 2 660 2137 2479 1330 664 2141
+ 2481 1332
CHEXA 1323 2 664 2141 2481 1332 668 2145
+ 2483 1334
CHEXA 1324 2 668 2145 2483 1334 672 2149
+ 2485 1336
CHEXA 1325 2 672 2149 2485 1336 676 2153
+ 2487 1338
CHEXA 1326 2 676 2153 2487 1338 680 2157
+ 2489 1340
CHEXA 1327 2 680 2157 2489 1340 684 2161
+ 2491 1342
CHEXA 1328 2 684 2161 2491 1342 688 2165
+ 2493 1344
CHEXA 1329 2 33 12 11 31 2494 1510
+ 35 2495
CHEXA 1330 2 2494 1510 35 2495 2496 1514
+ 39 2497
CHEXA 1331 2 2496 1514 39 2497 2498 1518
+ 43 2499
CHEXA 1332 2 2498 1518 43 2499 2500 1522
+ 47 2501
CHEXA 1333 2 2500 1522 47 2501 2502 1526
+ 51 2503
CHEXA 1334 2 2502 1526 51 2503 2504 1530
+ 55 2505
CHEXA 1335 2 2504 1530 55 2505 2506 1534
+ 59 2507
CHEXA 1336 2 2506 1534 59 2507 2508 1538
+ 63 2509
CHEXA 1337 2 2508 1538 63 2509 2510 1542
+ 67 2511
CHEXA 1338 2 2510 1542 67 2511 2512 1546
+ 71 2513
CHEXA 1339 2 2512 1546 71 2513 2514 1550
+ 75 2515
CHEXA 1340 2 2514 1550 75 2515 2516 1554
+ 79 2517
CHEXA 1341 2 2516 1554 79 2517 2518 1558
+ 83 2519
CHEXA 1342 2 2518 1558 83 2519 2520 1562
+ 87 2521
CHEXA 1343 2 2520 1562 87 2521 2522 1566
+ 91 2523
CHEXA 1344 2 2522 1566 91 2523 2524 1570
+ 95 2525
CHEXA 1345 2 2524 1570 95 2525 2526 1574
+ 99 2527
CHEXA 1346 2 2526 1574 99 2527 2528 1578
+ 103 2529
CHEXA 1347 2 2528 1578 103 2529 2530 1582
+ 107 2531
CHEXA 1348 2 2530 1582 107 2531 2532 1586
+ 111 2533
CHEXA 1349 2 2532 1586 111 2533 2534 1590
+ 115 2535
CHEXA 1350 2 2534 1590 115 2535 2536 1594
+ 119 2537
CHEXA 1351 2 2536 1594 119 2537 2538 1598
+ 123 2539
CHEXA 1352 2 2538 1598 123 2539 2540 1602
+ 127 2541
CHEXA 1353 2 2540 1602 127 2541 2542 1606

396 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 131 2543
CHEXA 1354 2 2542 1606 131 2543 2544 1610
+ 135 2545
CHEXA 1355 2 2544 1610 135 2545 2546 1614
+ 139 2547
CHEXA 1356 2 2546 1614 139 2547 2548 1618
+ 143 2549
CHEXA 1357 2 2548 1618 143 2549 2550 1622
+ 147 2551
CHEXA 1358 2 2550 1622 147 2551 2552 1626
+ 151 2553
CHEXA 1359 2 2552 1626 151 2553 2554 1630
+ 155 2555
CHEXA 1360 2 2554 1630 155 2555 2556 1634
+ 159 2557
CHEXA 1361 2 2556 1634 159 2557 2558 1638
+ 163 2559
CHEXA 1362 2 2558 1638 163 2559 2560 1642
+ 167 2561
CHEXA 1363 2 2560 1642 167 2561 2562 1646
+ 171 2563
CHEXA 1364 2 2562 1646 171 2563 2564 1650
+ 175 2565
CHEXA 1365 2 2564 1650 175 2565 2566 1654
+ 179 2567
CHEXA 1366 2 2566 1654 179 2567 2568 1658
+ 183 2569
CHEXA 1367 2 2568 1658 183 2569 2570 1662
+ 187 2571
CHEXA 1368 2 2570 1662 187 2571 2572 1666
+ 191 2573
CHEXA 1369 2 2572 1666 191 2573 2574 1670
+ 195 2575
CHEXA 1370 2 2574 1670 195 2575 2576 1674
+ 199 2577
CHEXA 1451 2 2576 1674 199 2577 2738 1998
+ 523 2739
CHEXA 1452 2 2738 1998 523 2739 2740 2002
+ 527 2741
CHEXA 1453 2 2740 2002 527 2741 2742 2006
+ 531 2743
CHEXA 1454 2 2742 2006 531 2743 2744 2010
+ 535 2745
CHEXA 1455 2 2744 2010 535 2745 2746 2014
+ 539 2747
CHEXA 1456 2 2746 2014 539 2747 2748 2018
+ 543 2749
CHEXA 1457 2 2748 2018 543 2749 2750 2022
+ 547 2751
CHEXA 1458 2 2750 2022 547 2751 2752 2026
+ 551 2753
CHEXA 1459 2 2752 2026 551 2753 2754 2030
+ 555 2755
CHEXA 1460 2 2754 2030 555 2755 2756 2034
+ 559 2757
CHEXA 1461 2 2756 2034 559 2757 2758 2038
+ 563 2759
CHEXA 1462 2 2758 2038 563 2759 2760 2042
+ 567 2761
CHEXA 1463 2 2760 2042 567 2761 2762 2046
+ 571 2763
CHEXA 1464 2 2762 2046 571 2763 2764 2050
+ 575 2765
CHEXA 1465 2 2764 2050 575 2765 2766 2054
+ 579 2767
CHEXA 1466 2 2766 2054 579 2767 2768 2058
+ 583 2769
CHEXA 1467 2 2768 2058 583 2769 2770 2062
+ 587 2771

Altair Engineering OptiStruct 13.0 Reference Guide 397

Proprietary Information of Altair Engineering


CHEXA 1468 2 2770 2062 587 2771 2772 2066
+ 591 2773
CHEXA 1469 2 2772 2066 591 2773 2774 2070
+ 595 2775
CHEXA 1470 2 2774 2070 595 2775 2776 2074
+ 599 2777
CHEXA 1471 2 2776 2074 599 2777 2778 2078
+ 603 2779
CHEXA 1472 2 2778 2078 603 2779 2780 2082
+ 607 2781
CHEXA 1473 2 2780 2082 607 2781 2782 2086
+ 611 2783
CHEXA 1474 2 2782 2086 611 2783 2784 2090
+ 615 2785
CHEXA 1475 2 2784 2090 615 2785 2786 2094
+ 619 2787
CHEXA 1476 2 2786 2094 619 2787 2788 2098
+ 623 2789
CHEXA 1477 2 2788 2098 623 2789 2790 2102
+ 627 2791
CHEXA 1478 2 2790 2102 627 2791 2792 2106
+ 631 2793
CHEXA 1479 2 2792 2106 631 2793 2794 2110
+ 635 2795
CHEXA 1480 2 2794 2110 635 2795 2796 2114
+ 639 2797
CHEXA 1481 2 2796 2114 639 2797 2798 2118
+ 643 2799
CHEXA 1482 2 2798 2118 643 2799 2800 2122
+ 647 2801
CHEXA 1483 2 2800 2122 647 2801 2802 2126
+ 651 2803
CHEXA 1484 2 2802 2126 651 2803 2804 2130
+ 655 2805
CHEXA 1485 2 2804 2130 655 2805 2806 2134
+ 659 2807
CHEXA 1486 2 2806 2134 659 2807 2808 2138
+ 663 2809
CHEXA 1487 2 2808 2138 663 2809 2810 2142
+ 667 2811
CHEXA 1488 2 2810 2142 667 2811 2812 2146
+ 671 2813
CHEXA 1489 2 2812 2146 671 2813 2814 2150
+ 675 2815
CHEXA 1490 2 2814 2150 675 2815 2816 2154
+ 679 2817
CHEXA 1491 2 2816 2154 679 2817 2818 2158
+ 683 2819
CHEXA 1492 2 2818 2158 683 2819 2820 2162
+ 687 2821
CHEXA 1493 2 30 13 12 33 2822 1511
+ 1510 2494
CHEXA 1494 2 2822 1511 1510 2494 2823 1515
+ 1514 2496
CHEXA 1495 2 2823 1515 1514 2496 2824 1519
+ 1518 2498
CHEXA 1496 2 2824 1519 1518 2498 2825 1523
+ 1522 2500
CHEXA 1497 2 2825 1523 1522 2500 2826 1527
+ 1526 2502
CHEXA 1498 2 2826 1527 1526 2502 2827 1531
+ 1530 2504
CHEXA 1499 2 2827 1531 1530 2504 2828 1535
+ 1534 2506
CHEXA 1500 2 2828 1535 1534 2506 2829 1539
+ 1538 2508
CHEXA 1501 2 2829 1539 1538 2508 2830 1543
+ 1542 2510
CHEXA 1502 2 2830 1543 1542 2510 2831 1547

398 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 1546 2512
CHEXA 1503 2 2831 1547 1546 2512 2832 1551
+ 1550 2514
CHEXA 1504 2 2832 1551 1550 2514 2833 1555
+ 1554 2516
CHEXA 1505 2 2833 1555 1554 2516 2834 1559
+ 1558 2518
CHEXA 1506 2 2834 1559 1558 2518 2835 1563
+ 1562 2520
CHEXA 1507 2 2835 1563 1562 2520 2836 1567
+ 1566 2522
CHEXA 1508 2 2836 1567 1566 2522 2837 1571
+ 1570 2524
CHEXA 1509 2 2837 1571 1570 2524 2838 1575
+ 1574 2526
CHEXA 1510 2 2838 1575 1574 2526 2839 1579
+ 1578 2528
CHEXA 1511 2 2839 1579 1578 2528 2840 1583
+ 1582 2530
CHEXA 1512 2 2840 1583 1582 2530 2841 1587
+ 1586 2532
CHEXA 1513 2 2841 1587 1586 2532 2842 1591
+ 1590 2534
CHEXA 1514 2 2842 1591 1590 2534 2843 1595
+ 1594 2536
CHEXA 1515 2 2843 1595 1594 2536 2844 1599
+ 1598 2538
CHEXA 1516 2 2844 1599 1598 2538 2845 1603
+ 1602 2540
CHEXA 1517 2 2845 1603 1602 2540 2846 1607
+ 1606 2542
CHEXA 1518 2 2846 1607 1606 2542 2847 1611
+ 1610 2544
CHEXA 1519 2 2847 1611 1610 2544 2848 1615
+ 1614 2546
CHEXA 1520 2 2848 1615 1614 2546 2849 1619
+ 1618 2548
CHEXA 1521 2 2849 1619 1618 2548 2850 1623
+ 1622 2550
CHEXA 1522 2 2850 1623 1622 2550 2851 1627
+ 1626 2552
CHEXA 1523 2 2851 1627 1626 2552 2852 1631
+ 1630 2554
CHEXA 1524 2 2852 1631 1630 2554 2853 1635
+ 1634 2556
CHEXA 1525 2 2853 1635 1634 2556 2854 1639
+ 1638 2558
CHEXA 1526 2 2854 1639 1638 2558 2855 1643
+ 1642 2560
CHEXA 1527 2 2855 1643 1642 2560 2856 1647
+ 1646 2562
CHEXA 1528 2 2856 1647 1646 2562 2857 1651
+ 1650 2564
CHEXA 1529 2 2857 1651 1650 2564 2858 1655
+ 1654 2566
CHEXA 1530 2 2858 1655 1654 2566 2859 1659
+ 1658 2568
CHEXA 1531 2 2859 1659 1658 2568 2860 1663
+ 1662 2570
CHEXA 1532 2 2860 1663 1662 2570 2861 1667
+ 1666 2572
CHEXA 1533 2 2861 1667 1666 2572 2862 1671
+ 1670 2574
CHEXA 1534 2 2862 1671 1670 2574 2863 1675
+ 1674 2576
CHEXA 1615 2 2863 1675 1674 2576 2944 1999
+ 1998 2738
CHEXA 1616 2 2944 1999 1998 2738 2945 2003
+ 2002 2740

Altair Engineering OptiStruct 13.0 Reference Guide 399

Proprietary Information of Altair Engineering


CHEXA 1617 2 2945 2003 2002 2740 2946 2007
+ 2006 2742
CHEXA 1618 2 2946 2007 2006 2742 2947 2011
+ 2010 2744
CHEXA 1619 2 2947 2011 2010 2744 2948 2015
+ 2014 2746
CHEXA 1620 2 2948 2015 2014 2746 2949 2019
+ 2018 2748
CHEXA 1621 2 2949 2019 2018 2748 2950 2023
+ 2022 2750
CHEXA 1622 2 2950 2023 2022 2750 2951 2027
+ 2026 2752
CHEXA 1623 2 2951 2027 2026 2752 2952 2031
+ 2030 2754
CHEXA 1624 2 2952 2031 2030 2754 2953 2035
+ 2034 2756
CHEXA 1625 2 2953 2035 2034 2756 2954 2039
+ 2038 2758
CHEXA 1626 2 2954 2039 2038 2758 2955 2043
+ 2042 2760
CHEXA 1627 2 2955 2043 2042 2760 2956 2047
+ 2046 2762
CHEXA 1628 2 2956 2047 2046 2762 2957 2051
+ 2050 2764
CHEXA 1629 2 2957 2051 2050 2764 2958 2055
+ 2054 2766
CHEXA 1630 2 2958 2055 2054 2766 2959 2059
+ 2058 2768
CHEXA 1631 2 2959 2059 2058 2768 2960 2063
+ 2062 2770
CHEXA 1632 2 2960 2063 2062 2770 2961 2067
+ 2066 2772
CHEXA 1633 2 2961 2067 2066 2772 2962 2071
+ 2070 2774
CHEXA 1634 2 2962 2071 2070 2774 2963 2075
+ 2074 2776
CHEXA 1635 2 2963 2075 2074 2776 2964 2079
+ 2078 2778
CHEXA 1636 2 2964 2079 2078 2778 2965 2083
+ 2082 2780
CHEXA 1637 2 2965 2083 2082 2780 2966 2087
+ 2086 2782
CHEXA 1638 2 2966 2087 2086 2782 2967 2091
+ 2090 2784
CHEXA 1639 2 2967 2091 2090 2784 2968 2095
+ 2094 2786
CHEXA 1640 2 2968 2095 2094 2786 2969 2099
+ 2098 2788
CHEXA 1641 2 2969 2099 2098 2788 2970 2103
+ 2102 2790
CHEXA 1642 2 2970 2103 2102 2790 2971 2107
+ 2106 2792
CHEXA 1643 2 2971 2107 2106 2792 2972 2111
+ 2110 2794
CHEXA 1644 2 2972 2111 2110 2794 2973 2115
+ 2114 2796
CHEXA 1645 2 2973 2115 2114 2796 2974 2119
+ 2118 2798
CHEXA 1646 2 2974 2119 2118 2798 2975 2123
+ 2122 2800
CHEXA 1647 2 2975 2123 2122 2800 2976 2127
+ 2126 2802
CHEXA 1648 2 2976 2127 2126 2802 2977 2131
+ 2130 2804
CHEXA 1649 2 2977 2131 2130 2804 2978 2135
+ 2134 2806
CHEXA 1650 2 2978 2135 2134 2806 2979 2139
+ 2138 2808
CHEXA 1651 2 2979 2139 2138 2808 2980 2143

400 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 2142 2810
CHEXA 1652 2 2980 2143 2142 2810 2981 2147
+ 2146 2812
CHEXA 1653 2 2981 2147 2146 2812 2982 2151
+ 2150 2814
CHEXA 1654 2 2982 2151 2150 2814 2983 2155
+ 2154 2816
CHEXA 1655 2 2983 2155 2154 2816 2984 2159
+ 2158 2818
CHEXA 1656 2 2984 2159 2158 2818 2985 2163
+ 2162 2820
CHEXA 1657 2 28 33 31 27 2986 2494
+ 2495 2987
CHEXA 1658 2 2986 2494 2495 2987 2988 2496
+ 2497 2989
CHEXA 1659 2 2988 2496 2497 2989 2990 2498
+ 2499 2991
CHEXA 1660 2 2990 2498 2499 2991 2992 2500
+ 2501 2993
CHEXA 1661 2 2992 2500 2501 2993 2994 2502
+ 2503 2995
CHEXA 1662 2 2994 2502 2503 2995 2996 2504
+ 2505 2997
CHEXA 1663 2 2996 2504 2505 2997 2998 2506
+ 2507 2999
CHEXA 1664 2 2998 2506 2507 2999 3000 2508
+ 2509 3001
CHEXA 1665 2 3000 2508 2509 3001 3002 2510
+ 2511 3003
CHEXA 1666 2 3002 2510 2511 3003 3004 2512
+ 2513 3005
CHEXA 1667 2 3004 2512 2513 3005 3006 2514
+ 2515 3007
CHEXA 1668 2 3006 2514 2515 3007 3008 2516
+ 2517 3009
CHEXA 1669 2 3008 2516 2517 3009 3010 2518
+ 2519 3011
CHEXA 1670 2 3010 2518 2519 3011 3012 2520
+ 2521 3013
CHEXA 1671 2 3012 2520 2521 3013 3014 2522
+ 2523 3015
CHEXA 1672 2 3014 2522 2523 3015 3016 2524
+ 2525 3017
CHEXA 1673 2 3016 2524 2525 3017 3018 2526
+ 2527 3019
CHEXA 1674 2 3018 2526 2527 3019 3020 2528
+ 2529 3021
CHEXA 1675 2 3020 2528 2529 3021 3022 2530
+ 2531 3023
CHEXA 1676 2 3022 2530 2531 3023 3024 2532
+ 2533 3025
CHEXA 1677 2 3024 2532 2533 3025 3026 2534
+ 2535 3027
CHEXA 1678 2 3026 2534 2535 3027 3028 2536
+ 2537 3029
CHEXA 1679 2 3028 2536 2537 3029 3030 2538
+ 2539 3031
CHEXA 1680 2 3030 2538 2539 3031 3032 2540
+ 2541 3033
CHEXA 1681 2 3032 2540 2541 3033 3034 2542
+ 2543 3035
CHEXA 1682 2 3034 2542 2543 3035 3036 2544
+ 2545 3037
CHEXA 1683 2 3036 2544 2545 3037 3038 2546
+ 2547 3039
CHEXA 1684 2 3038 2546 2547 3039 3040 2548
+ 2549 3041
CHEXA 1685 2 3040 2548 2549 3041 3042 2550
+ 2551 3043

Altair Engineering OptiStruct 13.0 Reference Guide 401

Proprietary Information of Altair Engineering


CHEXA 1686 2 3042 2550 2551 3043 3044 2552
+ 2553 3045
CHEXA 1687 2 3044 2552 2553 3045 3046 2554
+ 2555 3047
CHEXA 1688 2 3046 2554 2555 3047 3048 2556
+ 2557 3049
CHEXA 1689 2 3048 2556 2557 3049 3050 2558
+ 2559 3051
CHEXA 1690 2 3050 2558 2559 3051 3052 2560
+ 2561 3053
CHEXA 1691 2 3052 2560 2561 3053 3054 2562
+ 2563 3055
CHEXA 1692 2 3054 2562 2563 3055 3056 2564
+ 2565 3057
CHEXA 1693 2 3056 2564 2565 3057 3058 2566
+ 2567 3059
CHEXA 1694 2 3058 2566 2567 3059 3060 2568
+ 2569 3061
CHEXA 1695 2 3060 2568 2569 3061 3062 2570
+ 2571 3063
CHEXA 1696 2 3062 2570 2571 3063 3064 2572
+ 2573 3065
CHEXA 1697 2 3064 2572 2573 3065 3066 2574
+ 2575 3067
CHEXA 1698 2 3066 2574 2575 3067 3068 2576
+ 2577 3069
CHEXA 1779 2 3068 2576 2577 3069 3230 2738
+ 2739 3231
CHEXA 1780 2 3230 2738 2739 3231 3232 2740
+ 2741 3233
CHEXA 1781 2 3232 2740 2741 3233 3234 2742
+ 2743 3235
CHEXA 1782 2 3234 2742 2743 3235 3236 2744
+ 2745 3237
CHEXA 1783 2 3236 2744 2745 3237 3238 2746
+ 2747 3239
CHEXA 1784 2 3238 2746 2747 3239 3240 2748
+ 2749 3241
CHEXA 1785 2 3240 2748 2749 3241 3242 2750
+ 2751 3243
CHEXA 1786 2 3242 2750 2751 3243 3244 2752
+ 2753 3245
CHEXA 1787 2 3244 2752 2753 3245 3246 2754
+ 2755 3247
CHEXA 1788 2 3246 2754 2755 3247 3248 2756
+ 2757 3249
CHEXA 1789 2 3248 2756 2757 3249 3250 2758
+ 2759 3251
CHEXA 1790 2 3250 2758 2759 3251 3252 2760
+ 2761 3253
CHEXA 1791 2 3252 2760 2761 3253 3254 2762
+ 2763 3255
CHEXA 1792 2 3254 2762 2763 3255 3256 2764
+ 2765 3257
CHEXA 1793 2 3256 2764 2765 3257 3258 2766
+ 2767 3259
CHEXA 1794 2 3258 2766 2767 3259 3260 2768
+ 2769 3261
CHEXA 1795 2 3260 2768 2769 3261 3262 2770
+ 2771 3263
CHEXA 1796 2 3262 2770 2771 3263 3264 2772
+ 2773 3265
CHEXA 1797 2 3264 2772 2773 3265 3266 2774
+ 2775 3267
CHEXA 1798 2 3266 2774 2775 3267 3268 2776
+ 2777 3269
CHEXA 1799 2 3268 2776 2777 3269 3270 2778
+ 2779 3271
CHEXA 1800 2 3270 2778 2779 3271 3272 2780

402 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 2781 3273
CHEXA 1801 2 3272 2780 2781 3273 3274 2782
+ 2783 3275
CHEXA 1802 2 3274 2782 2783 3275 3276 2784
+ 2785 3277
CHEXA 1803 2 3276 2784 2785 3277 3278 2786
+ 2787 3279
CHEXA 1804 2 3278 2786 2787 3279 3280 2788
+ 2789 3281
CHEXA 1805 2 3280 2788 2789 3281 3282 2790
+ 2791 3283
CHEXA 1806 2 3282 2790 2791 3283 3284 2792
+ 2793 3285
CHEXA 1807 2 3284 2792 2793 3285 3286 2794
+ 2795 3287
CHEXA 1808 2 3286 2794 2795 3287 3288 2796
+ 2797 3289
CHEXA 1809 2 3288 2796 2797 3289 3290 2798
+ 2799 3291
CHEXA 1810 2 3290 2798 2799 3291 3292 2800
+ 2801 3293
CHEXA 1811 2 3292 2800 2801 3293 3294 2802
+ 2803 3295
CHEXA 1812 2 3294 2802 2803 3295 3296 2804
+ 2805 3297
CHEXA 1813 2 3296 2804 2805 3297 3298 2806
+ 2807 3299
CHEXA 1814 2 3298 2806 2807 3299 3300 2808
+ 2809 3301
CHEXA 1815 2 3300 2808 2809 3301 3302 2810
+ 2811 3303
CHEXA 1816 2 3302 2810 2811 3303 3304 2812
+ 2813 3305
CHEXA 1817 2 3304 2812 2813 3305 3306 2814
+ 2815 3307
CHEXA 1818 2 3306 2814 2815 3307 3308 2816
+ 2817 3309
CHEXA 1819 2 3308 2816 2817 3309 3310 2818
+ 2819 3311
CHEXA 1820 2 3310 2818 2819 3311 3312 2820
+ 2821 3313
CHEXA 1821 2 29 30 33 28 3314 2822
+ 2494 2986
CHEXA 1822 2 3314 2822 2494 2986 3315 2823
+ 2496 2988
CHEXA 1823 2 3315 2823 2496 2988 3316 2824
+ 2498 2990
CHEXA 1824 2 3316 2824 2498 2990 3317 2825
+ 2500 2992
CHEXA 1825 2 3317 2825 2500 2992 3318 2826
+ 2502 2994
CHEXA 1826 2 3318 2826 2502 2994 3319 2827
+ 2504 2996
CHEXA 1827 2 3319 2827 2504 2996 3320 2828
+ 2506 2998
CHEXA 1828 2 3320 2828 2506 2998 3321 2829
+ 2508 3000
CHEXA 1829 2 3321 2829 2508 3000 3322 2830
+ 2510 3002
CHEXA 1830 2 3322 2830 2510 3002 3323 2831
+ 2512 3004
CHEXA 1831 2 3323 2831 2512 3004 3324 2832
+ 2514 3006
CHEXA 1832 2 3324 2832 2514 3006 3325 2833
+ 2516 3008
CHEXA 1833 2 3325 2833 2516 3008 3326 2834
+ 2518 3010
CHEXA 1834 2 3326 2834 2518 3010 3327 2835
+ 2520 3012

Altair Engineering OptiStruct 13.0 Reference Guide 403

Proprietary Information of Altair Engineering


CHEXA 1835 2 3327 2835 2520 3012 3328 2836
+ 2522 3014
CHEXA 1836 2 3328 2836 2522 3014 3329 2837
+ 2524 3016
CHEXA 1837 2 3329 2837 2524 3016 3330 2838
+ 2526 3018
CHEXA 1838 2 3330 2838 2526 3018 3331 2839
+ 2528 3020
CHEXA 1839 2 3331 2839 2528 3020 3332 2840
+ 2530 3022
CHEXA 1840 2 3332 2840 2530 3022 3333 2841
+ 2532 3024
CHEXA 1841 2 3333 2841 2532 3024 3334 2842
+ 2534 3026
CHEXA 1842 2 3334 2842 2534 3026 3335 2843
+ 2536 3028
CHEXA 1843 2 3335 2843 2536 3028 3336 2844
+ 2538 3030
CHEXA 1844 2 3336 2844 2538 3030 3337 2845
+ 2540 3032
CHEXA 1845 2 3337 2845 2540 3032 3338 2846
+ 2542 3034
CHEXA 1846 2 3338 2846 2542 3034 3339 2847
+ 2544 3036
CHEXA 1847 2 3339 2847 2544 3036 3340 2848
+ 2546 3038
CHEXA 1848 2 3340 2848 2546 3038 3341 2849
+ 2548 3040
CHEXA 1849 2 3341 2849 2548 3040 3342 2850
+ 2550 3042
CHEXA 1850 2 3342 2850 2550 3042 3343 2851
+ 2552 3044
CHEXA 1851 2 3343 2851 2552 3044 3344 2852
+ 2554 3046
CHEXA 1852 2 3344 2852 2554 3046 3345 2853
+ 2556 3048
CHEXA 1853 2 3345 2853 2556 3048 3346 2854
+ 2558 3050
CHEXA 1854 2 3346 2854 2558 3050 3347 2855
+ 2560 3052
CHEXA 1855 2 3347 2855 2560 3052 3348 2856
+ 2562 3054
CHEXA 1856 2 3348 2856 2562 3054 3349 2857
+ 2564 3056
CHEXA 1857 2 3349 2857 2564 3056 3350 2858
+ 2566 3058
CHEXA 1858 2 3350 2858 2566 3058 3351 2859
+ 2568 3060
CHEXA 1859 2 3351 2859 2568 3060 3352 2860
+ 2570 3062
CHEXA 1860 2 3352 2860 2570 3062 3353 2861
+ 2572 3064
CHEXA 1861 2 3353 2861 2572 3064 3354 2862
+ 2574 3066
CHEXA 1862 2 3354 2862 2574 3066 3355 2863
+ 2576 3068
CHEXA 1943 2 3355 2863 2576 3068 3436 2944
+ 2738 3230
CHEXA 1944 2 3436 2944 2738 3230 3437 2945
+ 2740 3232
CHEXA 1945 2 3437 2945 2740 3232 3438 2946
+ 2742 3234
CHEXA 1946 2 3438 2946 2742 3234 3439 2947
+ 2744 3236
CHEXA 1947 2 3439 2947 2744 3236 3440 2948
+ 2746 3238
CHEXA 1948 2 3440 2948 2746 3238 3441 2949
+ 2748 3240
CHEXA 1949 2 3441 2949 2748 3240 3442 2950

404 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 2750 3242
CHEXA 1950 2 3442 2950 2750 3242 3443 2951
+ 2752 3244
CHEXA 1951 2 3443 2951 2752 3244 3444 2952
+ 2754 3246
CHEXA 1952 2 3444 2952 2754 3246 3445 2953
+ 2756 3248
CHEXA 1953 2 3445 2953 2756 3248 3446 2954
+ 2758 3250
CHEXA 1954 2 3446 2954 2758 3250 3447 2955
+ 2760 3252
CHEXA 1955 2 3447 2955 2760 3252 3448 2956
+ 2762 3254
CHEXA 1956 2 3448 2956 2762 3254 3449 2957
+ 2764 3256
CHEXA 1957 2 3449 2957 2764 3256 3450 2958
+ 2766 3258
CHEXA 1958 2 3450 2958 2766 3258 3451 2959
+ 2768 3260
CHEXA 1959 2 3451 2959 2768 3260 3452 2960
+ 2770 3262
CHEXA 1960 2 3452 2960 2770 3262 3453 2961
+ 2772 3264
CHEXA 1961 2 3453 2961 2772 3264 3454 2962
+ 2774 3266
CHEXA 1962 2 3454 2962 2774 3266 3455 2963
+ 2776 3268
CHEXA 1963 2 3455 2963 2776 3268 3456 2964
+ 2778 3270
CHEXA 1964 2 3456 2964 2778 3270 3457 2965
+ 2780 3272
CHEXA 1965 2 3457 2965 2780 3272 3458 2966
+ 2782 3274
CHEXA 1966 2 3458 2966 2782 3274 3459 2967
+ 2784 3276
CHEXA 1967 2 3459 2967 2784 3276 3460 2968
+ 2786 3278
CHEXA 1968 2 3460 2968 2786 3278 3461 2969
+ 2788 3280
CHEXA 1969 2 3461 2969 2788 3280 3462 2970
+ 2790 3282
CHEXA 1970 2 3462 2970 2790 3282 3463 2971
+ 2792 3284
CHEXA 1971 2 3463 2971 2792 3284 3464 2972
+ 2794 3286
CHEXA 1972 2 3464 2972 2794 3286 3465 2973
+ 2796 3288
CHEXA 1973 2 3465 2973 2796 3288 3466 2974
+ 2798 3290
CHEXA 1974 2 3466 2974 2798 3290 3467 2975
+ 2800 3292
CHEXA 1975 2 3467 2975 2800 3292 3468 2976
+ 2802 3294
CHEXA 1976 2 3468 2976 2802 3294 3469 2977
+ 2804 3296
CHEXA 1977 2 3469 2977 2804 3296 3470 2978
+ 2806 3298
CHEXA 1978 2 3470 2978 2806 3298 3471 2979
+ 2808 3300
CHEXA 1979 2 3471 2979 2808 3300 3472 2980
+ 2810 3302
CHEXA 1980 2 3472 2980 2810 3302 3473 2981
+ 2812 3304
CHEXA 1981 2 3473 2981 2812 3304 3474 2982
+ 2814 3306
CHEXA 1982 2 3474 2982 2814 3306 3475 2983
+ 2816 3308
CHEXA 1983 2 3475 2983 2816 3308 3476 2984
+ 2818 3310

Altair Engineering OptiStruct 13.0 Reference Guide 405

Proprietary Information of Altair Engineering


CHEXA 1984 2 3476 2984 2818 3310 3477 2985
+ 2820 3312
CHEXA 1985 2 32 10 9 24 3478 34
+ 690 3479
CHEXA 1986 2 3478 34 690 3479 3480 38
+ 692 3481
CHEXA 1987 2 3480 38 692 3481 3482 42
+ 694 3483
CHEXA 1988 2 3482 42 694 3483 3484 46
+ 696 3485
CHEXA 1989 2 3484 46 696 3485 3486 50
+ 698 3487
CHEXA 1990 2 3486 50 698 3487 3488 54
+ 700 3489
CHEXA 1991 2 3488 54 700 3489 3490 58
+ 702 3491
CHEXA 1992 2 3490 58 702 3491 3492 62
+ 704 3493
CHEXA 1993 2 3492 62 704 3493 3494 66
+ 706 3495
CHEXA 1994 2 3494 66 706 3495 3496 70
+ 708 3497
CHEXA 1995 2 3496 70 708 3497 3498 74
+ 710 3499
CHEXA 1996 2 3498 74 710 3499 3500 78
+ 712 3501
CHEXA 1997 2 3500 78 712 3501 3502 82
+ 714 3503
CHEXA 1998 2 3502 82 714 3503 3504 86
+ 716 3505
CHEXA 1999 2 3504 86 716 3505 3506 90
+ 718 3507
CHEXA 2000 2 3506 90 718 3507 3508 94
+ 720 3509
CHEXA 2001 2 3508 94 720 3509 3510 98
+ 722 3511
CHEXA 2002 2 3510 98 722 3511 3512 102
+ 724 3513
CHEXA 2003 2 3512 102 724 3513 3514 106
+ 726 3515
CHEXA 2004 2 3514 106 726 3515 3516 110
+ 728 3517
CHEXA 2005 2 3516 110 728 3517 3518 114
+ 730 3519
CHEXA 2006 2 3518 114 730 3519 3520 118
+ 732 3521
CHEXA 2007 2 3520 118 732 3521 3522 122
+ 734 3523
CHEXA 2008 2 3522 122 734 3523 3524 126
+ 736 3525
CHEXA 2009 2 3524 126 736 3525 3526 130
+ 738 3527
CHEXA 2010 2 3526 130 738 3527 3528 134
+ 740 3529
CHEXA 2011 2 3528 134 740 3529 3530 138
+ 742 3531
CHEXA 2012 2 3530 138 742 3531 3532 142
+ 744 3533
CHEXA 2013 2 3532 142 744 3533 3534 146
+ 746 3535
CHEXA 2014 2 3534 146 746 3535 3536 150
+ 748 3537
CHEXA 2015 2 3536 150 748 3537 3538 154
+ 750 3539
CHEXA 2016 2 3538 154 750 3539 3540 158
+ 752 3541
CHEXA 2017 2 3540 158 752 3541 3542 162
+ 754 3543
CHEXA 2018 2 3542 162 754 3543 3544 166

406 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 756 3545
CHEXA 2019 2 3544 166 756 3545 3546 170
+ 758 3547
CHEXA 2020 2 3546 170 758 3547 3548 174
+ 760 3549
CHEXA 2021 2 3548 174 760 3549 3550 178
+ 762 3551
CHEXA 2022 2 3550 178 762 3551 3552 182
+ 764 3553
CHEXA 2023 2 3552 182 764 3553 3554 186
+ 766 3555
CHEXA 2024 2 3554 186 766 3555 3556 190
+ 768 3557
CHEXA 2025 2 3556 190 768 3557 3558 194
+ 770 3559
CHEXA 2026 2 3558 194 770 3559 3560 198
+ 772 3561
CHEXA 2107 2 3560 198 772 3561 3722 522
+ 934 3723
CHEXA 2108 2 3722 522 934 3723 3724 526
+ 936 3725
CHEXA 2109 2 3724 526 936 3725 3726 530
+ 938 3727
CHEXA 2110 2 3726 530 938 3727 3728 534
+ 940 3729
CHEXA 2111 2 3728 534 940 3729 3730 538
+ 942 3731
CHEXA 2112 2 3730 538 942 3731 3732 542
+ 944 3733
CHEXA 2113 2 3732 542 944 3733 3734 546
+ 946 3735
CHEXA 2114 2 3734 546 946 3735 3736 550
+ 948 3737
CHEXA 2115 2 3736 550 948 3737 3738 554
+ 950 3739
CHEXA 2116 2 3738 554 950 3739 3740 558
+ 952 3741
CHEXA 2117 2 3740 558 952 3741 3742 562
+ 954 3743
CHEXA 2118 2 3742 562 954 3743 3744 566
+ 956 3745
CHEXA 2119 2 3744 566 956 3745 3746 570
+ 958 3747
CHEXA 2120 2 3746 570 958 3747 3748 574
+ 960 3749
CHEXA 2121 2 3748 574 960 3749 3750 578
+ 962 3751
CHEXA 2122 2 3750 578 962 3751 3752 582
+ 964 3753
CHEXA 2123 2 3752 582 964 3753 3754 586
+ 966 3755
CHEXA 2124 2 3754 586 966 3755 3756 590
+ 968 3757
CHEXA 2125 2 3756 590 968 3757 3758 594
+ 970 3759
CHEXA 2126 2 3758 594 970 3759 3760 598
+ 972 3761
CHEXA 2127 2 3760 598 972 3761 3762 602
+ 974 3763
CHEXA 2128 2 3762 602 974 3763 3764 606
+ 976 3765
CHEXA 2129 2 3764 606 976 3765 3766 610
+ 978 3767
CHEXA 2130 2 3766 610 978 3767 3768 614
+ 980 3769
CHEXA 2131 2 3768 614 980 3769 3770 618
+ 982 3771
CHEXA 2132 2 3770 618 982 3771 3772 622
+ 984 3773

Altair Engineering OptiStruct 13.0 Reference Guide 407

Proprietary Information of Altair Engineering


CHEXA 2133 2 3772 622 984 3773 3774 626
+ 986 3775
CHEXA 2134 2 3774 626 986 3775 3776 630
+ 988 3777
CHEXA 2135 2 3776 630 988 3777 3778 634
+ 990 3779
CHEXA 2136 2 3778 634 990 3779 3780 638
+ 992 3781
CHEXA 2137 2 3780 638 992 3781 3782 642
+ 994 3783
CHEXA 2138 2 3782 642 994 3783 3784 646
+ 996 3785
CHEXA 2139 2 3784 646 996 3785 3786 650
+ 998 3787
CHEXA 2140 2 3786 650 998 3787 3788 654
+ 1000 3789
CHEXA 2141 2 3788 654 1000 3789 3790 658
+ 1002 3791
CHEXA 2142 2 3790 658 1002 3791 3792 662
+ 1004 3793
CHEXA 2143 2 3792 662 1004 3793 3794 666
+ 1006 3795
CHEXA 2144 2 3794 666 1006 3795 3796 670
+ 1008 3797
CHEXA 2145 2 3796 670 1008 3797 3798 674
+ 1010 3799
CHEXA 2146 2 3798 674 1010 3799 3800 678
+ 1012 3801
CHEXA 2147 2 3800 678 1012 3801 3802 682
+ 1014 3803
CHEXA 2148 2 3802 682 1014 3803 3804 686
+ 1016 3805
CHEXA 2149 2 31 11 10 32 2495 35
+ 34 3478
CHEXA 2150 2 2495 35 34 3478 2497 39
+ 38 3480
CHEXA 2151 2 2497 39 38 3480 2499 43
+ 42 3482
CHEXA 2152 2 2499 43 42 3482 2501 47
+ 46 3484
CHEXA 2153 2 2501 47 46 3484 2503 51
+ 50 3486
CHEXA 2154 2 2503 51 50 3486 2505 55
+ 54 3488
CHEXA 2155 2 2505 55 54 3488 2507 59
+ 58 3490
CHEXA 2156 2 2507 59 58 3490 2509 63
+ 62 3492
CHEXA 2157 2 2509 63 62 3492 2511 67
+ 66 3494
CHEXA 2158 2 2511 67 66 3494 2513 71
+ 70 3496
CHEXA 2159 2 2513 71 70 3496 2515 75
+ 74 3498
CHEXA 2160 2 2515 75 74 3498 2517 79
+ 78 3500
CHEXA 2161 2 2517 79 78 3500 2519 83
+ 82 3502
CHEXA 2162 2 2519 83 82 3502 2521 87
+ 86 3504
CHEXA 2163 2 2521 87 86 3504 2523 91
+ 90 3506
CHEXA 2164 2 2523 91 90 3506 2525 95
+ 94 3508
CHEXA 2165 2 2525 95 94 3508 2527 99
+ 98 3510
CHEXA 2166 2 2527 99 98 3510 2529 103
+ 102 3512
CHEXA 2167 2 2529 103 102 3512 2531 107

408 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 106 3514
CHEXA 2168 2 2531 107 106 3514 2533 111
+ 110 3516
CHEXA 2169 2 2533 111 110 3516 2535 115
+ 114 3518
CHEXA 2170 2 2535 115 114 3518 2537 119
+ 118 3520
CHEXA 2171 2 2537 119 118 3520 2539 123
+ 122 3522
CHEXA 2172 2 2539 123 122 3522 2541 127
+ 126 3524
CHEXA 2173 2 2541 127 126 3524 2543 131
+ 130 3526
CHEXA 2174 2 2543 131 130 3526 2545 135
+ 134 3528
CHEXA 2175 2 2545 135 134 3528 2547 139
+ 138 3530
CHEXA 2176 2 2547 139 138 3530 2549 143
+ 142 3532
CHEXA 2177 2 2549 143 142 3532 2551 147
+ 146 3534
CHEXA 2178 2 2551 147 146 3534 2553 151
+ 150 3536
CHEXA 2179 2 2553 151 150 3536 2555 155
+ 154 3538
CHEXA 2180 2 2555 155 154 3538 2557 159
+ 158 3540
CHEXA 2181 2 2557 159 158 3540 2559 163
+ 162 3542
CHEXA 2182 2 2559 163 162 3542 2561 167
+ 166 3544
CHEXA 2183 2 2561 167 166 3544 2563 171
+ 170 3546
CHEXA 2184 2 2563 171 170 3546 2565 175
+ 174 3548
CHEXA 2185 2 2565 175 174 3548 2567 179
+ 178 3550
CHEXA 2186 2 2567 179 178 3550 2569 183
+ 182 3552
CHEXA 2187 2 2569 183 182 3552 2571 187
+ 186 3554
CHEXA 2188 2 2571 187 186 3554 2573 191
+ 190 3556
CHEXA 2189 2 2573 191 190 3556 2575 195
+ 194 3558
CHEXA 2190 2 2575 195 194 3558 2577 199
+ 198 3560
CHEXA 2271 2 2577 199 198 3560 2739 523
+ 522 3722
CHEXA 2272 2 2739 523 522 3722 2741 527
+ 526 3724
CHEXA 2273 2 2741 527 526 3724 2743 531
+ 530 3726
CHEXA 2274 2 2743 531 530 3726 2745 535
+ 534 3728
CHEXA 2275 2 2745 535 534 3728 2747 539
+ 538 3730
CHEXA 2276 2 2747 539 538 3730 2749 543
+ 542 3732
CHEXA 2277 2 2749 543 542 3732 2751 547
+ 546 3734
CHEXA 2278 2 2751 547 546 3734 2753 551
+ 550 3736
CHEXA 2279 2 2753 551 550 3736 2755 555
+ 554 3738
CHEXA 2280 2 2755 555 554 3738 2757 559
+ 558 3740
CHEXA 2281 2 2757 559 558 3740 2759 563
+ 562 3742

Altair Engineering OptiStruct 13.0 Reference Guide 409

Proprietary Information of Altair Engineering


CHEXA 2282 2 2759 563 562 3742 2761 567
+ 566 3744
CHEXA 2283 2 2761 567 566 3744 2763 571
+ 570 3746
CHEXA 2284 2 2763 571 570 3746 2765 575
+ 574 3748
CHEXA 2285 2 2765 575 574 3748 2767 579
+ 578 3750
CHEXA 2286 2 2767 579 578 3750 2769 583
+ 582 3752
CHEXA 2287 2 2769 583 582 3752 2771 587
+ 586 3754
CHEXA 2288 2 2771 587 586 3754 2773 591
+ 590 3756
CHEXA 2289 2 2773 591 590 3756 2775 595
+ 594 3758
CHEXA 2290 2 2775 595 594 3758 2777 599
+ 598 3760
CHEXA 2291 2 2777 599 598 3760 2779 603
+ 602 3762
CHEXA 2292 2 2779 603 602 3762 2781 607
+ 606 3764
CHEXA 2293 2 2781 607 606 3764 2783 611
+ 610 3766
CHEXA 2294 2 2783 611 610 3766 2785 615
+ 614 3768
CHEXA 2295 2 2785 615 614 3768 2787 619
+ 618 3770
CHEXA 2296 2 2787 619 618 3770 2789 623
+ 622 3772
CHEXA 2297 2 2789 623 622 3772 2791 627
+ 626 3774
CHEXA 2298 2 2791 627 626 3774 2793 631
+ 630 3776
CHEXA 2299 2 2793 631 630 3776 2795 635
+ 634 3778
CHEXA 2300 2 2795 635 634 3778 2797 639
+ 638 3780
CHEXA 2301 2 2797 639 638 3780 2799 643
+ 642 3782
CHEXA 2302 2 2799 643 642 3782 2801 647
+ 646 3784
CHEXA 2303 2 2801 647 646 3784 2803 651
+ 650 3786
CHEXA 2304 2 2803 651 650 3786 2805 655
+ 654 3788
CHEXA 2305 2 2805 655 654 3788 2807 659
+ 658 3790
CHEXA 2306 2 2807 659 658 3790 2809 663
+ 662 3792
CHEXA 2307 2 2809 663 662 3792 2811 667
+ 666 3794
CHEXA 2308 2 2811 667 666 3794 2813 671
+ 670 3796
CHEXA 2309 2 2813 671 670 3796 2815 675
+ 674 3798
CHEXA 2310 2 2815 675 674 3798 2817 679
+ 678 3800
CHEXA 2311 2 2817 679 678 3800 2819 683
+ 682 3802
CHEXA 2312 2 2819 683 682 3802 2821 687
+ 686 3804
CHEXA 2313 2 26 32 24 25 3806 3478
+ 3479 3807
CHEXA 2314 2 3806 3478 3479 3807 3808 3480
+ 3481 3809
CHEXA 2315 2 3808 3480 3481 3809 3810 3482
+ 3483 3811
CHEXA 2316 2 3810 3482 3483 3811 3812 3484

410 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 3485 3813
CHEXA 2317 2 3812 3484 3485 3813 3814 3486
+ 3487 3815
CHEXA 2318 2 3814 3486 3487 3815 3816 3488
+ 3489 3817
CHEXA 2319 2 3816 3488 3489 3817 3818 3490
+ 3491 3819
CHEXA 2320 2 3818 3490 3491 3819 3820 3492
+ 3493 3821
CHEXA 2321 2 3820 3492 3493 3821 3822 3494
+ 3495 3823
CHEXA 2322 2 3822 3494 3495 3823 3824 3496
+ 3497 3825
CHEXA 2323 2 3824 3496 3497 3825 3826 3498
+ 3499 3827
CHEXA 2324 2 3826 3498 3499 3827 3828 3500
+ 3501 3829
CHEXA 2325 2 3828 3500 3501 3829 3830 3502
+ 3503 3831
CHEXA 2326 2 3830 3502 3503 3831 3832 3504
+ 3505 3833
CHEXA 2327 2 3832 3504 3505 3833 3834 3506
+ 3507 3835
CHEXA 2328 2 3834 3506 3507 3835 3836 3508
+ 3509 3837
CHEXA 2329 2 3836 3508 3509 3837 3838 3510
+ 3511 3839
CHEXA 2330 2 3838 3510 3511 3839 3840 3512
+ 3513 3841
CHEXA 2331 2 3840 3512 3513 3841 3842 3514
+ 3515 3843
CHEXA 2332 2 3842 3514 3515 3843 3844 3516
+ 3517 3845
CHEXA 2333 2 3844 3516 3517 3845 3846 3518
+ 3519 3847
CHEXA 2334 2 3846 3518 3519 3847 3848 3520
+ 3521 3849
CHEXA 2335 2 3848 3520 3521 3849 3850 3522
+ 3523 3851
CHEXA 2336 2 3850 3522 3523 3851 3852 3524
+ 3525 3853
CHEXA 2337 2 3852 3524 3525 3853 3854 3526
+ 3527 3855
CHEXA 2338 2 3854 3526 3527 3855 3856 3528
+ 3529 3857
CHEXA 2339 2 3856 3528 3529 3857 3858 3530
+ 3531 3859
CHEXA 2340 2 3858 3530 3531 3859 3860 3532
+ 3533 3861
CHEXA 2341 2 3860 3532 3533 3861 3862 3534
+ 3535 3863
CHEXA 2342 2 3862 3534 3535 3863 3864 3536
+ 3537 3865
CHEXA 2343 2 3864 3536 3537 3865 3866 3538
+ 3539 3867
CHEXA 2344 2 3866 3538 3539 3867 3868 3540
+ 3541 3869
CHEXA 2345 2 3868 3540 3541 3869 3870 3542
+ 3543 3871
CHEXA 2346 2 3870 3542 3543 3871 3872 3544
+ 3545 3873
CHEXA 2347 2 3872 3544 3545 3873 3874 3546
+ 3547 3875
CHEXA 2348 2 3874 3546 3547 3875 3876 3548
+ 3549 3877
CHEXA 2349 2 3876 3548 3549 3877 3878 3550
+ 3551 3879
CHEXA 2350 2 3878 3550 3551 3879 3880 3552
+ 3553 3881

Altair Engineering OptiStruct 13.0 Reference Guide 411

Proprietary Information of Altair Engineering


CHEXA 2351 2 3880 3552 3553 3881 3882 3554
+ 3555 3883
CHEXA 2352 2 3882 3554 3555 3883 3884 3556
+ 3557 3885
CHEXA 2353 2 3884 3556 3557 3885 3886 3558
+ 3559 3887
CHEXA 2354 2 3886 3558 3559 3887 3888 3560
+ 3561 3889
CHEXA 2435 2 3888 3560 3561 3889 4050 3722
+ 3723 4051
CHEXA 2436 2 4050 3722 3723 4051 4052 3724
+ 3725 4053
CHEXA 2437 2 4052 3724 3725 4053 4054 3726
+ 3727 4055
CHEXA 2438 2 4054 3726 3727 4055 4056 3728
+ 3729 4057
CHEXA 2439 2 4056 3728 3729 4057 4058 3730
+ 3731 4059
CHEXA 2440 2 4058 3730 3731 4059 4060 3732
+ 3733 4061
CHEXA 2441 2 4060 3732 3733 4061 4062 3734
+ 3735 4063
CHEXA 2442 2 4062 3734 3735 4063 4064 3736
+ 3737 4065
CHEXA 2443 2 4064 3736 3737 4065 4066 3738
+ 3739 4067
CHEXA 2444 2 4066 3738 3739 4067 4068 3740
+ 3741 4069
CHEXA 2445 2 4068 3740 3741 4069 4070 3742
+ 3743 4071
CHEXA 2446 2 4070 3742 3743 4071 4072 3744
+ 3745 4073
CHEXA 2447 2 4072 3744 3745 4073 4074 3746
+ 3747 4075
CHEXA 2448 2 4074 3746 3747 4075 4076 3748
+ 3749 4077
CHEXA 2449 2 4076 3748 3749 4077 4078 3750
+ 3751 4079
CHEXA 2450 2 4078 3750 3751 4079 4080 3752
+ 3753 4081
CHEXA 2451 2 4080 3752 3753 4081 4082 3754
+ 3755 4083
CHEXA 2452 2 4082 3754 3755 4083 4084 3756
+ 3757 4085
CHEXA 2453 2 4084 3756 3757 4085 4086 3758
+ 3759 4087
CHEXA 2454 2 4086 3758 3759 4087 4088 3760
+ 3761 4089
CHEXA 2455 2 4088 3760 3761 4089 4090 3762
+ 3763 4091
CHEXA 2456 2 4090 3762 3763 4091 4092 3764
+ 3765 4093
CHEXA 2457 2 4092 3764 3765 4093 4094 3766
+ 3767 4095
CHEXA 2458 2 4094 3766 3767 4095 4096 3768
+ 3769 4097
CHEXA 2459 2 4096 3768 3769 4097 4098 3770
+ 3771 4099
CHEXA 2460 2 4098 3770 3771 4099 4100 3772
+ 3773 4101
CHEXA 2461 2 4100 3772 3773 4101 4102 3774
+ 3775 4103
CHEXA 2462 2 4102 3774 3775 4103 4104 3776
+ 3777 4105
CHEXA 2463 2 4104 3776 3777 4105 4106 3778
+ 3779 4107
CHEXA 2464 2 4106 3778 3779 4107 4108 3780
+ 3781 4109
CHEXA 2465 2 4108 3780 3781 4109 4110 3782

412 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 3783 4111
CHEXA 2466 2 4110 3782 3783 4111 4112 3784
+ 3785 4113
CHEXA 2467 2 4112 3784 3785 4113 4114 3786
+ 3787 4115
CHEXA 2468 2 4114 3786 3787 4115 4116 3788
+ 3789 4117
CHEXA 2469 2 4116 3788 3789 4117 4118 3790
+ 3791 4119
CHEXA 2470 2 4118 3790 3791 4119 4120 3792
+ 3793 4121
CHEXA 2471 2 4120 3792 3793 4121 4122 3794
+ 3795 4123
CHEXA 2472 2 4122 3794 3795 4123 4124 3796
+ 3797 4125
CHEXA 2473 2 4124 3796 3797 4125 4126 3798
+ 3799 4127
CHEXA 2474 2 4126 3798 3799 4127 4128 3800
+ 3801 4129
CHEXA 2475 2 4128 3800 3801 4129 4130 3802
+ 3803 4131
CHEXA 2476 2 4130 3802 3803 4131 4132 3804
+ 3805 4133
CHEXA 2477 2 27 31 32 26 2987 2495
+ 3478 3806
CHEXA 2478 2 2987 2495 3478 3806 2989 2497
+ 3480 3808
CHEXA 2479 2 2989 2497 3480 3808 2991 2499
+ 3482 3810
CHEXA 2480 2 2991 2499 3482 3810 2993 2501
+ 3484 3812
CHEXA 2481 2 2993 2501 3484 3812 2995 2503
+ 3486 3814
CHEXA 2482 2 2995 2503 3486 3814 2997 2505
+ 3488 3816
CHEXA 2483 2 2997 2505 3488 3816 2999 2507
+ 3490 3818
CHEXA 2484 2 2999 2507 3490 3818 3001 2509
+ 3492 3820
CHEXA 2485 2 3001 2509 3492 3820 3003 2511
+ 3494 3822
CHEXA 2486 2 3003 2511 3494 3822 3005 2513
+ 3496 3824
CHEXA 2487 2 3005 2513 3496 3824 3007 2515
+ 3498 3826
CHEXA 2488 2 3007 2515 3498 3826 3009 2517
+ 3500 3828
CHEXA 2489 2 3009 2517 3500 3828 3011 2519
+ 3502 3830
CHEXA 2490 2 3011 2519 3502 3830 3013 2521
+ 3504 3832
CHEXA 2491 2 3013 2521 3504 3832 3015 2523
+ 3506 3834
CHEXA 2492 2 3015 2523 3506 3834 3017 2525
+ 3508 3836
CHEXA 2493 2 3017 2525 3508 3836 3019 2527
+ 3510 3838
CHEXA 2494 2 3019 2527 3510 3838 3021 2529
+ 3512 3840
CHEXA 2495 2 3021 2529 3512 3840 3023 2531
+ 3514 3842
CHEXA 2496 2 3023 2531 3514 3842 3025 2533
+ 3516 3844
CHEXA 2497 2 3025 2533 3516 3844 3027 2535
+ 3518 3846
CHEXA 2498 2 3027 2535 3518 3846 3029 2537
+ 3520 3848
CHEXA 2499 2 3029 2537 3520 3848 3031 2539
+ 3522 3850

Altair Engineering OptiStruct 13.0 Reference Guide 413

Proprietary Information of Altair Engineering


CHEXA 2500 2 3031 2539 3522 3850 3033 2541
+ 3524 3852
CHEXA 2501 2 3033 2541 3524 3852 3035 2543
+ 3526 3854
CHEXA 2502 2 3035 2543 3526 3854 3037 2545
+ 3528 3856
CHEXA 2503 2 3037 2545 3528 3856 3039 2547
+ 3530 3858
CHEXA 2504 2 3039 2547 3530 3858 3041 2549
+ 3532 3860
CHEXA 2505 2 3041 2549 3532 3860 3043 2551
+ 3534 3862
CHEXA 2506 2 3043 2551 3534 3862 3045 2553
+ 3536 3864
CHEXA 2507 2 3045 2553 3536 3864 3047 2555
+ 3538 3866
CHEXA 2508 2 3047 2555 3538 3866 3049 2557
+ 3540 3868
CHEXA 2509 2 3049 2557 3540 3868 3051 2559
+ 3542 3870
CHEXA 2510 2 3051 2559 3542 3870 3053 2561
+ 3544 3872
CHEXA 2511 2 3053 2561 3544 3872 3055 2563
+ 3546 3874
CHEXA 2512 2 3055 2563 3546 3874 3057 2565
+ 3548 3876
CHEXA 2513 2 3057 2565 3548 3876 3059 2567
+ 3550 3878
CHEXA 2514 2 3059 2567 3550 3878 3061 2569
+ 3552 3880
CHEXA 2515 2 3061 2569 3552 3880 3063 2571
+ 3554 3882
CHEXA 2516 2 3063 2571 3554 3882 3065 2573
+ 3556 3884
CHEXA 2517 2 3065 2573 3556 3884 3067 2575
+ 3558 3886
CHEXA 2518 2 3067 2575 3558 3886 3069 2577
+ 3560 3888
CHEXA 2599 2 3069 2577 3560 3888 3231 2739
+ 3722 4050
CHEXA 2600 2 3231 2739 3722 4050 3233 2741
+ 3724 4052
CHEXA 2601 2 3233 2741 3724 4052 3235 2743
+ 3726 4054
CHEXA 2602 2 3235 2743 3726 4054 3237 2745
+ 3728 4056
CHEXA 2603 2 3237 2745 3728 4056 3239 2747
+ 3730 4058
CHEXA 2604 2 3239 2747 3730 4058 3241 2749
+ 3732 4060
CHEXA 2605 2 3241 2749 3732 4060 3243 2751
+ 3734 4062
CHEXA 2606 2 3243 2751 3734 4062 3245 2753
+ 3736 4064
CHEXA 2607 2 3245 2753 3736 4064 3247 2755
+ 3738 4066
CHEXA 2608 2 3247 2755 3738 4066 3249 2757
+ 3740 4068
CHEXA 2609 2 3249 2757 3740 4068 3251 2759
+ 3742 4070
CHEXA 2610 2 3251 2759 3742 4070 3253 2761
+ 3744 4072
CHEXA 2611 2 3253 2761 3744 4072 3255 2763
+ 3746 4074
CHEXA 2612 2 3255 2763 3746 4074 3257 2765
+ 3748 4076
CHEXA 2613 2 3257 2765 3748 4076 3259 2767
+ 3750 4078
CHEXA 2614 2 3259 2767 3750 4078 3261 2769

414 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 3752 4080
CHEXA 2615 2 3261 2769 3752 4080 3263 2771
+ 3754 4082
CHEXA 2616 2 3263 2771 3754 4082 3265 2773
+ 3756 4084
CHEXA 2617 2 3265 2773 3756 4084 3267 2775
+ 3758 4086
CHEXA 2618 2 3267 2775 3758 4086 3269 2777
+ 3760 4088
CHEXA 2619 2 3269 2777 3760 4088 3271 2779
+ 3762 4090
CHEXA 2620 2 3271 2779 3762 4090 3273 2781
+ 3764 4092
CHEXA 2621 2 3273 2781 3764 4092 3275 2783
+ 3766 4094
CHEXA 2622 2 3275 2783 3766 4094 3277 2785
+ 3768 4096
CHEXA 2623 2 3277 2785 3768 4096 3279 2787
+ 3770 4098
CHEXA 2624 2 3279 2787 3770 4098 3281 2789
+ 3772 4100
CHEXA 2625 2 3281 2789 3772 4100 3283 2791
+ 3774 4102
CHEXA 2626 2 3283 2791 3774 4102 3285 2793
+ 3776 4104
CHEXA 2627 2 3285 2793 3776 4104 3287 2795
+ 3778 4106
CHEXA 2628 2 3287 2795 3778 4106 3289 2797
+ 3780 4108
CHEXA 2629 2 3289 2797 3780 4108 3291 2799
+ 3782 4110
CHEXA 2630 2 3291 2799 3782 4110 3293 2801
+ 3784 4112
CHEXA 2631 2 3293 2801 3784 4112 3295 2803
+ 3786 4114
CHEXA 2632 2 3295 2803 3786 4114 3297 2805
+ 3788 4116
CHEXA 2633 2 3297 2805 3788 4116 3299 2807
+ 3790 4118
CHEXA 2634 2 3299 2807 3790 4118 3301 2809
+ 3792 4120
CHEXA 2635 2 3301 2809 3792 4120 3303 2811
+ 3794 4122
CHEXA 2636 2 3303 2811 3794 4122 3305 2813
+ 3796 4124
CHEXA 2637 2 3305 2813 3796 4124 3307 2815
+ 3798 4126
CHEXA 2638 2 3307 2815 3798 4126 3309 2817
+ 3800 4128
CHEXA 2639 2 3309 2817 3800 4128 3311 2819
+ 3802 4130
CHEXA 2640 2 3311 2819 3802 4130 3313 2821
+ 3804 4132
$
$HMMOVE 2
$ 17THRU 58 139THRU 222 303THRU 386
$ 467THRU 550 631THRU 714 795THRU 878
$ 959THRU 1042 1123THRU 1206 1287THRU 1370
$ 1451THRU 1534 1615THRU 1698 1779THRU 1862
$ 1943THRU 2026 2107THRU 2190 2271THRU 2354
$ 2435THRU 2518 2599THRU 2640
$
$$
$$------------------------------------------------------------------------------$
$$ HyperMesh name and color information for generic components $
$$------------------------------------------------------------------------------$
$HMNAME COMP 2"Air" 2 "Air" 5
$HWCOLOR COMP 2 5
$

Altair Engineering OptiStruct 13.0 Reference Guide 415

Proprietary Information of Altair Engineering


$HMNAME COMP 5"Piston"
$HWCOLOR COMP 5 8
$
$HMNAME COMP 6"absorber"
$HWCOLOR COMP 6 3
$
$
$HMDPRP
$ 17THRU 58 139THRU 222 303THRU 386
$ 467THRU 550 631THRU 714 795THRU 878
$ 959THRU 1042 1123THRU 1206 1287THRU 1370
$ 1451THRU 1534 1615THRU 1698 1779THRU 1862
$ 1943THRU 2026 2107THRU 2190 2271THRU 2354
$ 2435THRU 2518 2599THRU 2640 5627 5629 6116
$ 6122 6125 6520THRU 6521 6523 6528 6954 7220
$ 7647 7652 7945 7948 7955
$

$
$$
$$ PSHELL Data
$$
$
$
$
$
$
$
$
$HMNAME PROP 1"tube" 4
$HWCOLOR PROP 1 52
PSHELL 1 20.1 2 2 0.0
$$
$$ PSOLID Data
$$
$HMNAME PROP 2"Air" 5
$HWCOLOR PROP 2 4
PSOLID 2 1 PFLUID
$$
$$ MAT1 Data
$$
$HMNAME MAT 2"alum" "MAT1"
$HWCOLOR MAT 2 3
MAT1 21.0+7 0.3 0.000254
$$
$$ MAT10 Data
$HMNAME MAT 1"Air" "MAT10"
$HWCOLOR MAT 1 3
MAT10 1 1.21-7 13000.0
$$
$$------------------------------------------------------------------------------$
$$ HyperMesh Commands for loadcollectors name and color information $
$$------------------------------------------------------------------------------$
$HMNAME LOADCOL 2"spc"
$HWCOLOR LOADCOL 2 6
$$
$HMNAME LOADCOL 8"Force"
$HWCOLOR LOADCOL 8 7
$$
$HMNAME LOADCOL 12"SPC"
$HWCOLOR LOADCOL 12 5
$$
$$
$$ FREQi cards
$$
$HMNAME LOADCOL 3"Freq"
$HWCOLOR LOADCOL 3 6
$FREQ1 3 0.0 5.0 600
FREQ 3480.

416 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


$
$$
$$ RLOAD1 cards
$$
$HMNAME LOADCOL 6"Rload"
$HWCOLOR LOADCOL 6 6
RLOAD1 6 8 7 0 VELO
$$
$$
$$ TABLED1 cards
$$
$HMNAME LOADCOL 7"Table"
$HWCOLOR LOADCOL 7 6
TABLED1 7 LINEAR LINEAR
+ 0.0 1.0 3000.0 1.0ENDT
$$
$HMNAME LOADCOL 10"reactance"
$HWCOLOR LOADCOL 10 5
TABLED1 10 LINEAR LINEAR
+ 0.0 0.00154 3000.0 0.00154ENDT
$$
$HMNAME LOADCOL 11"Impedance"
$HWCOLOR LOADCOL 11 5
TABLED1 11 LINEAR LINEAR
+ 0.0 0.0 3000.0 0.0ENDT
$$
$$
$$ DLOAD cards
$$
$HMNAME LOADCOL 9"Dload"
$HWCOLOR LOADCOL 9 6
DLOAD 91.0 1.0 6
$$
$$ EIGRL cards
$$
$HMNAME LOADCOL 4"EigrlTube"
$HWCOLOR LOADCOL 4 6
EIGRL 4 5 MASS
$HMNAME LOADCOL 5"EigrlAir"
$HWCOLOR LOADCOL 5 6
EIGRL 5 30 MASS
$$
$$ SPC Data
$$
SPC1 12123456 6776 thru 6800
spcd 86776 3 1.0
spcd 86777 3 1.0
spcd 86778 3 1.0
spcd 86779 3 1.0
spcd 86780 3 1.0
spcd 86781 3 1.0
spcd 86782 3 1.0
spcd 86783 3 1.0
spcd 86784 3 1.0
spcd 86785 3 1.0
spcd 86786 3 1.0
spcd 86788 3 1.0
spcd 86789 3 1.0
spcd 86790 3 1.0
spcd 86791 3 1.0
spcd 86792 3 1.0
spcd 86793 3 1.0
spcd 86794 3 1.0
spcd 86795 3 1.0
spcd 86796 3 1.0
spcd 86797 3 1.0
spcd 86798 3 1.0
spcd 86799 3 1.0
spcd 86800 3 1.0

Altair Engineering OptiStruct 13.0 Reference Guide 417

Proprietary Information of Altair Engineering


$
$ DAREA Data
$
$$
$$ DAREA Data
$$
DAREA 8 6798 3-15.0
$$
$$
CAABSF 7957 5 689 688 687 686
CAABSF 7960 5 1017 689 686 1016
CAABSF 7964 5 1345 1344 688 689
CAABSF 7969 5 1509 1345 689 1017
CAABSF 7972 5 2165 2164 2163 2162
CAABSF 7977 5 688 2165 2162 687
CAABSF 7978 5 4133 3805 3804 4132
CAABSF 7980 5 2493 2492 2164 2165
CAABSF 7984 5 1344 2493 2165 688
CAABSF 7985 5 2821 687 2162 2820
CAABSF 7988 5 2820 2162 2163 2985
CAABSF 7990 5 3313 2821 2820 3312
CAABSF 7994 5 3312 2820 2985 3477
CAABSF 7996 5 3805 1016 686 3804
CAABSF 7998 5 3804 686 687 2821
CAABSF 8003 5 4132 3804 2821 3313
PAABSF 5 11 10
ENDDATA
$$
$$------------------------------------------------------------------------------$$
$$ Data Definition for AutoDV $$
$$------------------------------------------------------------------------------$$
$$
$$-----------------------------------------------------------------------------$$
$$ Design Variables Card for Control Perturbations $$
$$-----------------------------------------------------------------------------$$
$
$------------------------------------------------------------------------------$
$ Domain Element Definitions $
$------------------------------------------------------------------------------$
$$
$$------------------------------------------------------------------------------$$
$$ Nodeset Definitions $$
$$------------------------------------------------------------------------------$$
$$ Design domain node sets
$$
$$------------------------------------------------------------------------------$$
$$ Control Perturbation $$
$$------------------------------------------------------------------------------$$
$$
$$
$$ CONTROL PERTURBATION Data
$$

ALTDOCTAG "0mjpRI@DXd^3_0ASnbi`;l;q6A23R@9_67hgW8R?OiZ]
Eq:PeN``A;WXh3ITgJeq5NZRd5jSHQK3X@:`a12;n4qD_I^RYMo"
ADI0.1.0 2011-02-11T20:16:20 0of1 OSQA
ENDDOCTAG

418 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. Element identification numbers should be unique with respect to all other element
identification numbers.

2. If only G1 is specified, then a point impedance is assumed. If G1 and G2 are specified,


then a line impedance is assumed. If G1, G2 and G3 are specified, then an impedance is
associated with the area of the triangular face. If G1 through G4 are specified, then an
impedance is associated with the quadrilateral face.

3. The CAABSF element must connect entirely to fluid points on the fluid-structure
boundary.

4. This card is represented as a CAABSF element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 419

Proprietary Information of Altair Engineering


CAALOAD

Bulk Data Entry

CAALOAD – Pressure from CFD Analysis

Description

The CAALOAD bulk data entry defines the CFD pressure that is transferred to the structural
side for frequency response analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C AALOAD SID C AAID SRFID AC SC AL PSC AL

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C AALOAD 110 5 20 1.0

Field Contents

SID Identification number of a dynamic load set.

No default (Integer > 0)

CAAID Identification number of the H3D file (loadID) specified by ASSIGN,H3DCAA (See
comments 1 and 2).

Default = no default (Integer > 0)

SRFID Identification number of a SURF bulk data entry that defines the surface where
CFD pressure is applicable (See comment 1).

Default = 0 (Integer > 0)

ACSCAL Scale factor of the acoustic source term.

Default = 1.0 (Real > 0)

420 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

PSCAL Scale factor of CFD pressure.

Default = 1.0 (Real > 0)

Comments

1. The surface GRIDs associated with the CFD pressure must be fluid grids. The pressures
from CFD analysis at each loading frequency are stored in an H3D file. This H3D file can be
referenced using the ASSIGN I/O Options Entry (ASSIGN, H3DCAA, loadID, and filename).

2. The pressure from the fluid grids will be transferred to structural grids for frequency
response analysis.

3. CAALOAD can be chosen as a dynamic load in the I/O Options or Subcase Information
sections with the command DLOAD = SID.

4. The SID field in this CAALOAD entry must be unique with respect to other dynamic load
sets (ACSRCE, DLOAD, RLOAD1, RLOAD2, TLOAD1, and TLOAD2 entries).

Altair Engineering OptiStruct 13.0 Reference Guide 421

Proprietary Information of Altair Engineering


CBAR

Bulk Data Entry

CBAR – Simple Beam Element Connection

Description

The CBAR bulk data entry defines a simple beam element (BAR) of the structural model.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C BAR EID PID GA GB X1/G0 X2 X3 OFFT

PA PB W1A W2A W3A W1B W2B W3B

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C BAR 2 39 7 3 13

513

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PBAR or PBARL property entry.

Default = EID (Integer > 0)

GA,GB Grid point identification numbers of connection points.

422 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

X1,X2,X3 Components of vector v, at end A, measured at end A, parallel to


the components of the displacement coordinate system for GA, or
the basic coordinate system, to determine (with the vector from
end A to end B) the orientation of the element coordinate system
for the BAR element. See comment 5.

No default (Real)

G0 Grid point identification number to optionally supply X1, X2, X3.


Direction of orientation vector is GA to G0.

No default (Integer > 0)

OFFT Character String specifying the interpretation of the offset vector


specification. See comment 5.

Default = GGG (Character or blank)

PA,PB Pin flags for bar ends A and B, respectively. Used to remove
connections between the grid point and selected degrees-of-
freedom of the bar. The degrees-of-freedom are defined in the
element’s coordinate system. The bar must have stiffness
associated with the PA and PB degrees-of-freedom to be released
by the pin flags. For example, if PA=4 is specified, the PBAR entry
must have a value for J, the torsion stiffness.

No default (Integer > 0; up to 5 of the unique digits 1-6 with no


embedded blanks)

W1A,W2A,W3A Components of offset vectors wa and wb in displacement


W1B,W2B,W3B coordinate systems at points GA and GB, respectively, or in the
element coordinate system. See comment 5.

Default = blank (Real or blank)

Altair Engineering OptiStruct 13.0 Reference Guide 423

Proprietary Information of Altair Engineering


Fig 1: Bar element coordinate system (for C BAR element)

Fig 2: Moments and Internal Forces in the x-y Plane (for a C BAR element)

424 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Fig 3: Moments and Internal Forces in the x-z Plane (for a C BAR element)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. If there are no pin flags or offsets, the continuation may be omitted.

3. G0 cannot be located at GA or GB.

4. If X1/G0 is a positive integer and X2 and X3 are blank, then G0 is used to orient the
element, otherwise X1, X2, X3 is used.

5. The OFFT character string specifies how the offset and orientation vector components
are computed. By default, the offset vectors are specified in the Global (local
displacement) coordinate system of each grid A and B, and the orientation vector is
specified in the Global coordinate system of grid A. Using the codes below, the offset
vector can be specified in the element coordinate system and the orientation vector can
be specified in the basic coordinate system. The valid character strings and their
meanings are shown below:

OFFT Orientation Vector End A Offset End B Offset

GGG Global Global Global

BGG Basic Global Global

GGO Global Global Element

BGO Basic Global Element

GOG Global Element Global

BOG Basic Element Global

GOO Global Element Element

BOO Basic Element Element

The element system x-axis is defined from GA to GB. The orientation vector and the
element system x-axis are then used to define the z and y axes of the element system.
A vector is formed from the cross product of a vector going from Grid A to Grid B and the
orientation vector to create the element coordinate z-direction.

6. Offset vectors are treated like rigid elements. The length of the offset vectors is not
affected by thermal loads.

7. This card is represented as a bar2 element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 425

Proprietary Information of Altair Engineering


CBEAM

Bulk Data Entry

CBEAM – Beam Element Connection

Description

The CBEAM bulk data entry defines a beam element (BEAM) of the structural model.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C BEAM EID PID GA GB X1/G0 X2 X3 OFFT

PA PB W1A W2A W3A W1B W2B W3B

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C BEAM 2 39 7 3 13

513 3.0

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of PBEAM or PBEAML property entry.

Default = EID (Integer > 0)

GA,GB Grid point identification numbers of connection points.

426 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

X1,X2,X3 Components of vector v, at end A, measured at the offset point for


end A, parallel to the components of the displacement coordinate
system for GA, or the basic coordinate system, to determine (with
the vector from offset end A to offset end B) the orientation of the
element coordinate system for the beam element. See comment 5.

No default (Real; See comment 2)

G0 Grid point identification number to optionally supply X1, X2, X3.


Direction of orientation vector is GA to G0.

No default (Integer > 0; See comment 2).

OFFT Character string specifying the interpretation of the offset vector


specification. See comment 5.

Default = GGG (Character or blank)

PA, PB Pin flags for beam ends A and B respectively. Used to remove
connections between the grid point and selected degrees-of-freedom
of the beam. The degrees-of-freedom are defined in the element’s
coordinate system and the pin flags are applied at the offset ends of
the beam. The beam must have stiffness associated with the PA and
PB degrees-of-freedom to be released by the pin flags. For example,
if PA=4, the PBEAM entry must have a non-zero value for J, the
torsion stiffness.

No default (Integer > 0; up to 5 of the unique digits 1-6 with no


embedded blanks)

W1A,W2A,W3A, Components of offset vectors, measured in the displacement


coordinate systems at grid points A and B or in the element
W1B,W2B,W3B coordinate system, from the grid points to the end points of the axis
of shear center. See comment 5.

Default = blank (Real or blank)

Altair Engineering OptiStruct 13.0 Reference Guide 427

Proprietary Information of Altair Engineering


Fig 1: Beam element coordinate system.

Fig 2: Direction of Internal Forces and Moments (for C BEAM entry)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. If X1/G0 is a positive integer and X2 and X3 are blank, then G0 is used to orient the
element, otherwise X1, X2, X3 is used.

3. G0 GA or GB.

4. If there are no pin flags or offsets the continuation may be omitted.

428 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


5. The OFFT character string specifies how the offset and orientation vector components
are computed. By default, the offset vectors are specified in the Global (local
displacement) coordinate system of each grid A and B, and the orientation vector is
specified in the Global coordinate system of grid A. Using the codes below, the offset
vector can be specified in the element coordinate system and the orientation vector can
be specified in the basic coordinate system. The valid character strings and their
meanings are shown below:

OFFT Orientation Vector End A Offset End B Offset

GGG Global Global Global

BGG Basic Global Global

GGO Global Global Element

BGO Basic Global Element

GOG Global Element Global

BOG Basic Element Global

GOO Global Element Element

BOO Basic Element Element

The element system x-axis is defined from GA to GB. The orientation vector and the
element system x-axis are then used to define the z and y axes of the element system.
A vector is formed from the cross product of a vector going from Grid A to Grid B and the
orientation vector to create the element coordinate z-direction.

6. Offset vectors are treated like rigid elements. The length of the offset vectors is not
affected by thermal loads.

7. Torsional stiffness due to warping of the cross-section is not considered.

8. This card is represented as a bar2 element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 429

Proprietary Information of Altair Engineering


CBUSH

Bulk Data Entry

CBUSH – Bushing Element

Description

Defines a generalized spring-damper structural element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C BUSH EID PID GA GB G0/X1 X2 X3 C ID

S OC ID S1 S2 S3

Example 1

Spring-damper element defined with default orientation and location; default orientation is
only valid when only K1, and/or K4 are defined on referenced PBUSH.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C BUSH 2 6 8 1

Example 2

Spring-damper location is offset from mid-point of GA-GB.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C BUSH 19 7 1 2 4

0.3

430 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Example 3

Spring-damper is oriented by referencing coordinate system 5, and spring-damper location


is explicitly defined using OCID, S1, S2, and S3.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C BUSH 41 9 1 2 5

7 1.0 0.5 -0.7

Field Contents

EID Element identification number.

No default (Integer > 0)

PID Property identification number of a PBUSH entry.

Default = EID (Integer > 0)

GA,GB Grid point identification number of connection points.

No default (Integer > 0 or <PartName.number>) See comments 6, 9 and


10.

Xi Components of orientation vector , from GA, in the displacement


coordinate system of GA.

(Real)

G0 Alternate method to supply vector using grid point GO. Direction of

is from GA to GO. is then transferred to End A.

(Integer > 0 or <PartName.number>) See comments 3 and 9.

CID Element coordinate system identification. A 0 means the basic


coordinate system. If CID is blank, then the element coordinate system
is determined from GO or Xi.

(Integer > 0 or blank) See comments 2 and 3.

Altair Engineering OptiStruct 13.0 Reference Guide 431

Proprietary Information of Altair Engineering


Field Contents

S Location of spring-damper as a fraction along the line segment between


GA and GB.

Default = 0.5 (0.0 < Real < 1.0)

OCID Coordinate system identification for spring-damper offset. See comment


7.

Default = -1 (Integer > -1; -1 indicates that the offset is along GA-GB)

Si Components of the spring-damper offset in the OCID coordinate system,


ignored if OCID is -1.

(Real)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

C BUSH element

432 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Alternate C BUSH element definition

2. CID > 0 overrides GO and Xi. Then the element x-axis is along T1, the element y-axis is
along T2, and the element z-axis is along T3 of the CID coordinate system. If the CID
refers to a cylindrical coordinate system or a spherical coordinate system, the grid GA is
used to locate the system. If for cylindrical or spherical coordinate, GA falls on the z-axis
used to define them, it is recommended that another CID be selected to define the
element x-axis.

3.

specified, the line AB is the element x-axis and the orientation vector lies in the x-y
plane (similar to the CBEAM element).

4.
specified, the line AB is the element x-axis. This option is valid only when K1 or K4 or
both on the PBUSH entry are specified (but K2, K3, K5, and K6 are not specified). If K2,
K3, K5, or K6 are specified, the solver will terminate with an error.

5. If GA and GB are coincident, or if GB is blank, then CID must be specified.

6. If OCID refers to a cylindrical or spherical coordinate system, then grid GA is used to


locate the system.

7. A CBUSH element, referencing a PBUSH property with a single stiffness term, is equivalent
to a CELAS1 or CELAS2 element, only when the elements have zero length. A non-zero
length CBUSH assumes rigid body connections from the connection points, GA and GB, to
the spring-damper location, as defined either by S or the OCID and Si fields.

8. Bushing elements are ignored in heat transfer analysis.

Altair Engineering OptiStruct 13.0 Reference Guide 433

Proprietary Information of Altair Engineering


9. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on CBUSH entries in the model. A fully qualified reference
(“PartName.number”) is similar to the format of a numeric reference. “PartName” is the
name of the part that contains the referenced local entry (part names are defined on the
BEGIN Bulk Data Entry in the model). “number” is the identification number of a
referenced local entry in the part “PartName”. See Parts and Instances in the User’s
Guide for detailed information on the use of fully qualified references.

10. The CBUSH element force is calculated as follows:

F = K(UGB - UGA )

Therefore, the sign of the force will depend on the grids GA and GB. If the grids are
switched, then the element force will be reversed.

11. This card is represented as a spring element in HyperMesh.

434 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CBUSH1D

Bulk Data Entry

CBUSH1D – Rod-type Spring-Damper Element

Description

Defines a one-dimensional spring-damper structural element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C BUSH1D EID PID GA GB C ID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C BUSH1D 2 6 8 1

Field Contents

EID Element identification number.

No default (Integer > 0)

PID Property identification number of a PBUSH1D entry.

Default = EID (Integer > 0)

GA,GB Grid point identification numbers of connection points.

No default (Integer > 0 or <PartName.number>) See comments 2 and 7.

CID Element coordinate system identification number. If a value of 0 is input,


the basic coordinate system is selected.

(Integer > 0 or blank) See comments 2 through 4.

Altair Engineering OptiStruct 13.0 Reference Guide 435

Proprietary Information of Altair Engineering


Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2.
axis. In geometric nonlinear analysis, the element axis (line GA to GB) follows the
deformation of grids GA and GB.

3. If GA and GB are coincident, or if GB is blank, then CID must be specified.

4. If CID > 0, the x-axis of CID is the element axis. In geometric nonlinear analysis,
depending on the referenced system being movable or fixed, the axis of the element will
move or not move with the axes of the system, respectively. Geometric nonlinear
analysis is selected by an ANALYSIS = NLGEOM, IMPDYN or EXPDYN subcase entry.

5. In all linear subcases, as well as small displacement nonlinear quasi-static


(ANALYSIS=NLSTAT) subcases, PBUSH1D and CBUSH1D are converted internally to the
equivalent PBUSH (with PBUSHT, if necessary) and CBUSH.

6. Rod-type spring-damper elements are ignored in heat transfer analysis.

7. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on CBUSH1D entries in the model. A fully qualified reference
(“PartName.number”) is similar to the format of a numeric reference. “PartName” is the
name of the part that contains the referenced local entry (part names are defined on the
BEGIN bulk data entry in the model). “number” is the identification number of a referenced
local entry in the part “PartName”. See Parts and Instances in the User’s Guide for
detailed information on the use of fully qualified references.

8. This card is represented as a spring element in HyperMesh.

436 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CDAMP1

Bulk Data Entry

CDAMP1 – Scalar Damper Connection

Description

Defines a scalar damper element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C DAMP1 EID PID G1 C1 G2 C2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C DAMP1 2 10 0 26 3

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PDAMP property entry.

Default = EID (Integer > 0)

G1, G2 Geometric grid point or scalar point identification number.

Default = 0 (Integer > 0)

C1, C2 Component number in the displacement coordinate system specified by


the CD entry of the GRID data.

Default = 0 (0 < Integer < 6)

Altair Engineering OptiStruct 13.0 Reference Guide 437

Proprietary Information of Altair Engineering


Comments

1. Zero or blank may be used to indicate a grounded terminal G1 or G2 with a corresponding


blank or zero C1 or C2. A grounded terminal is a point whose displacement is constrained
to zero.

2. Scalar points may be used for G1 and/or G2, (with corresponding C1 and/or C2 of zero or
blank). If only scalar points and/or grounded terminals are involved, it is more efficient to
use the CDAMP3 entry.

3. Element identification numbers must be unique with respect to all other element
identification numbers.

4. The two connection points (G1, C1) and (G2, C2) must be distinct.

5. A scalar point specified on this entry need not be defined on an SPOINT entry.

6. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).

7. Scalar damper elements are ignored in heat transfer analysis.

8. This card is represented as a spring or mass element in HyperMesh.

438 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CDAMP2

Bulk Data Entry

CDAMP2 – Scalar Damper Property and Connection

Description

Defines a scalar damper element without reference to a property entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C DAMP2 EID B G1 C1 G2 C2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C DAMP2 2 3.12 12 2

Field Contents

EID Unique element identification number.

No default (Integer > 0)

B Value of the scalar damper.

No default (Real)

G1, G2 Geometric grid point identification number.

Default = blank (Integer > 0)

C1, C2 Component number in the displacement coordinate system


specified by the CD entry of the GRID data.

Default = 0 (0 < Integer < 6)

Altair Engineering OptiStruct 13.0 Reference Guide 439

Proprietary Information of Altair Engineering


Comments

1. Zero or blank may be used to indicate a grounded terminal G1 or G2 with a corresponding


blank or zero C1 or C2. A grounded terminal is a point whose displacement is constrained
to zero.

2. Scalar points may be used for G1 and/or G2, (with a corresponding C1 and/or C2 of zero
or blank). If only scalar points and/or grounded terminals are involved, it is more efficient
to use the CDAMP4 entry.

3. Element identification numbers must be unique with respect to all other element
identification numbers.

4. This single entry completely defines the element since no material or geometric properties
are required.

5. The two connection points (G1, C1) and (G2, C2) must be distinct.

6. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).

7. Scalar damper elements are ignored in heat transfer analysis.

8. This card is represented as a spring or mass element in HyperMesh.

440 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CDAMP3

Bulk Data Entry

CDAMP3 – Scalar Damper Connection to Scalar Points Only

Description

Defines a scalar damper element that is connected only to scalar points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C DAMP3 EID PID S1 S2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C DAMP3 16 978 24 36

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Property identification number of a PDAMP property entry.

Default = EID (Integer > 0)

S1, S2 Scalar point identification numbers.

Default = 0 (Integer >

Comments

1. S1 or S2, but not both, may be blank or zero, indicating a constrained coordinate.

2. Element identification numbers should be unique with respect to all other element
identification numbers.

Altair Engineering OptiStruct 13.0 Reference Guide 441

Proprietary Information of Altair Engineering


3. Only one scalar damper element may be defined on a single entry.

4. A scalar point specified on this entry need not be defined on an SPOINT entry.

5. Scalar damper elements are ignored in heat transfer analysis.

6. This card is represented as a spring or mass element in HyperMesh.

442 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CDAMP4

Bulk Data Entry

CDAMP4 – Scalar Damper Property and Connection to Scalar Points Only

Description

Defines a scalar damper element that is connected only to scalar points and is without
reference to a material or property entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C DAMP4 EID B S1 S2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C DAMP4 16 -2.6 4 9

Field Contents

EID Unique element identification number.

No default (Integer > 0)

B Scalar damper value.

No default (Real)

S1, S2 Scalar point identification numbers.

Default = 0 (Integer >

Altair Engineering OptiStruct 13.0 Reference Guide 443

Proprietary Information of Altair Engineering


Comments

1. S1 or S2, but not both, may be blank or zero, indicating a constrained coordinate.

2. Element identification numbers should be unique with respect to all other element
identification numbers.

3. This single entry completely defines the element since no material or geometric properties
are required.

4. Only one scalar damper element may be defined on a single entry.

5. A scalar point specified on this entry need not be defined on an SPOINT entry.

6. Scalar damper elements are ignored in heat transfer analysis.

7. This card is represented as a spring or mass element in HyperMesh.

444 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CDSMETH

Bulk Data Entry

CDSMETH - Run Control

Description

The CDSMETH command can be used in the component dynamic synthesis method for
generating component dynamic matrices at each loading frequency.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C DSMETH C DSID GTYPE TF OSET TOL SSF RSF

C MSOUT SPID SPID_F GP_RC

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C DSMETH 10 SVDNP YES

C MSOUT 9000001 9000001 YES

Argumen Options Description


t

CDSID <INTEGER> Identification number of CDSMETH.

Default = NONE

GTYPE <SVDNP/ SVDNP: Dynamic Stiffness Matrix is calculated by singular value


BME> decomposition of transfer function after scaling
rotational DOF’s (Comment 6).
Default =

Altair Engineering OptiStruct 13.0 Reference Guide 445

Proprietary Information of Altair Engineering


Argumen Options Description
t

SVDNP BME:
Dynamic Stiffness Matrix is calculated by block matrix
elimination (Comment 6).

TF <YES, NO> Generate transfer functions at the connection and


interior points at each loading frequency.
Default = NO

OSET <INTEGER> Grid set for interior grids. The responses corresponding
to interior grids may be recovered in the residual run
Default = BLANK
(Comment 5).

TOL <REAL/BLANK> Tolerance value for the Singular Value Decomposition


(SVD) operation that involves pseudo–inversion of the
Default = 1.0e-20
transfer function matrix to obtain the dynamic stiffness
matrix.

SSF <REAL/BLANK> Structural scale factor used to scale transfer function


terms associated with the structural degrees of freedom
Default = 1.0
prior to the singular value decomposition (SVD)
operation.

RSF <REAL/BLANK> Rotational scale factor used to scale transfer function


terms associated with the rotational degrees of freedom
Default = 1.0e-3
prior to the singular value decomposition (SVD)
operation.

CMSOUT <CMSOUT/BLANK> This is an optional keyword to specify the creation of


the component model synthesis (CMS) super element
Default = BLANK generated using the General Modal method with free –
free boundary (Craig-Chang method).

446 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argumen Options Description
t

SPID <INTEGER> The starting SPOINT ID to be used in CMS matrix output


for the structural eigenmodes. There is no default. This
is only valid, if CMSOUT is specified.

SPID_F <INTEGER> The starting SPOINT ID to be used in CMS matrix output


for the fluid eigenmodes. There is no default, if fluid
grids are present in the model. However, this must be
used, if there are fluid grids in the model. This is only
valid, if CMSOUT is specified.

GP_RC <YES, NO> Grid participation recovery control. If YES, the fluid-
structural interface connection matrix is calculated and
Default = NO stored as a part of the CMS super element. This is only
valid, if CMSOUT is specified.

Comments

1. The responses available for recovery, and the attachment points available for connection
in the residual structure, must be specified on a BNDFRE1, BNDFREE, CSET or CSET1 data
entry for a modal frequency response analysis in which CDSMETH has been specified.

2. Frequencies available for recovery must be specified, using the FREQ or FREQ# (# ranges
from 1 to 5) data entries, in the modal frequency response analysis in which CDSMETH
has been specified.

3. A MODEL card may be used for additional response output for the optional CMS
superelement output.

4. Reasonable speedup may be achieved by reducing the number of ASET points in the
residual run when CDSMETH is used.

5. If OSET is specified, TF is automatically set to YES.

6. Performance may be an issue with the Block Matrix Elimination (BME) method for large
models. The BME option for the GTYPE field is only recommended for small models or when
other methods fail to work.

Altair Engineering OptiStruct 13.0 Reference Guide 447

Proprietary Information of Altair Engineering


CELAS1

Bulk Data Entry

CELAS1 – Scalar Spring Connection

Description

Defines a scalar spring element of the structural model.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ELAS1 EID PID G1 C1 G2 C2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ELAS1 2 6 8 1

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PELAS property entry.

Default = EID (Integer > 0)

G1,G2 Geometric grid point or scalar point identification number.

Default = 0 (Integer > 0)

C1,C2 Component number in the displacement coordinate system specified by


the CD entry of the GRID data.

Default = 0 (0 < Integer < 6)

448 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. Zero or blank may be used to indicate a grounded terminal G1 or G2 with a corresponding


blank or zero C1 or C2. A grounded terminal is a point whose displacement is constrained
to zero.

2. Scalar points may be used for G1 and/or G2 (with a corresponding C1 and/or C2 of zero or
blank). If only scalar points and/or grounded terminals are involved, it is more efficient to
use the CELAS3 entry.

3. Element identification numbers must be unique with respect to all other element
identification numbers.

4. The two connection points (G1, C1) and (G2, C2) must be distinct.

5. A scalar point specified on this entry need not be defined on an SPOINT entry.

6. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).

7. A CBUSH element, referencing a PBUSH property with a single stiffness term, is equivalent
to a CELAS1 or CELAS2 element, only when the elements have zero length. A non-zero
length CBUSH assumes rigid body connections from the connection points, GA and GB, to
the spring-damper location, as defined either by S or the OCID and Si fields.

8. This card is represented as a spring or mass element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 449

Proprietary Information of Altair Engineering


CELAS2

Bulk Data Entry

CELAS2 – Scalar Spring Property and Connection

Description

Defines a scalar spring element of the structural model without reference to a property entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ELAS2 EID K G1 C1 G2 C2 GE S

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ELAS2 28 6.2+3 19 4

Field Contents

EID Unique element identification number.

No default (Integer > 0)

K Spring stiffness.

No default (Real)

G1, G2 Geometric grid point or scalar point identification number.

Default = 0 (Integer > 0)

C1, C2 Component number in the displacement coordinate system specified by


the CD entry of the GRID data.

Default = 0 (0 < Integer < 6)

450 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

GE Damping coefficient. (See comment 7).

Default = 0.0 (Real)

S Stress coefficient.

Default = 0.0 (Real)

Comments

1. Zero or blank may be used to indicate a grounded terminal G1 or G2 with a corresponding


blank or zero C1 or C2. A grounded terminal is a point whose displacement is constrained
to zero.

2. Scalar points may be used for G1 and/or G2 (with a corresponding C1 and/or C2 of zero or
blank). If only scalar points and/or grounded terminals are involved, it is more efficient to
use the CELAS4 entry.

3. Element identification numbers must be unique with respect to all other element
identification numbers.

4. This single entry completely defines the element since no material or geometric properties
are required.

5. The two connection points (G1, C1) and (G2, C2) must be distinct.

6. To obtain the damping coefficient GE, multiply the critical damping ratio, C/C0, by 2.

7. If PARAM, W4 is not specified, GE is ignored in transient analysis.

8. A scalar point specified on this entry need not be defined on an SPOINT entry.

9. The element force of a spring is calculated from the equation: F = k * (u1 – u2)

Where, k is the stiffness coefficient for the scalar element and u1 is the displacement of
the first degree-of-freedom listed on the CELAS entry. Element stresses are calculated
from the equation: s = S * F, where, S is the stress coefficient as defined above.

10. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).

11. A CBUSH element, referencing a PBUSH property with a single stiffness term, is equivalent
to a CELAS1 or CELAS2 element, only when the elements have zero length. A non-zero
length CBUSH assumes rigid body connections from the connection points, GA and GB, to
the spring-damper location, as defined either by S or the OCID and Si fields.

Altair Engineering OptiStruct 13.0 Reference Guide 451

Proprietary Information of Altair Engineering


12. This card is represented as a spring or mass element in HyperMesh.

452 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CELAS3

Bulk Data Entry

CELAS3 – Scalar Spring Connection to Scalar Points Only

Description

Defines a scalar spring element that connects only to scalar points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ELAS3 EID PID S1 S2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ELAS3 19 2 14 15

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Property identification number of a PELAS entry.

S1, S2 Scalar point identification numbers.

Default = 0 (Integer >

Comments

1. S1 or S2 may be blank or zero indicating a constrained coordinate.

2. Element identification numbers should be unique with respect to all other element
identification numbers.

3. Only one scalar spring element may be defined on a single entry.

Altair Engineering OptiStruct 13.0 Reference Guide 453

Proprietary Information of Altair Engineering


4. A scalar point specified on this entry need not be defined on an SPOINT entry.

5. This card is represented as a spring or mass element in HyperMesh.

454 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CELAS4

Bulk Data Entry

CELAS4 – Scalar Spring Property and Connection to Scalar Points Only

Description

Defines a scalar spring element that is connected only to scalar points without reference to a
property entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ELAS4 EID K S1 S2 GE S

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ELAS4 42 6.2-3 2

Field Contents

EID Unique element identification number.

No default (Integer > 0)

K Stiffness of the scalar spring.

No default (Real)

S1, S2 Scalar point identification numbers.

Default = 0 (Integer >

GE Damping coefficient. See comment 7.

Default = 0.0 (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 455

Proprietary Information of Altair Engineering


Field Contents

S Stress coefficient

Default = 0.0 (Real)

Comments

1. S1 or S2, but not both, may be blank or zero indicating a constrained coordinate.

2. Element identification numbers should be unique with respect to all other element
identification numbers.

3. This single entry completely defines the element since no material or geometric properties
are required.

4. Only one scalar spring element may be defined on a single entry.

5. A scalar point specified on this entry need not be defined on an SPOINT entry.

6. The element force of a spring is calculated from the equation: F = k * (u1 – u2)

Where, k is the stiffness coefficient for the scalar element and u1 is the displacement of
the first degree-of-freedom listed on the CELAS entry. Element stresses are calculated
from the equation: s = S * F, where, S is the stress coefficient as defined above.

7. If PARAM, W4 is not specified, GE is ignored in transient analysis.

8. This card is represented as a spring or mass element in HyperMesh.

456 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CFAST

Bulk Data Entry

CFAST – Fastener Element Connection

Description

Define a fastener with material orientation connecting two shell surfaces.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C FAST EID PID C TYPE PIDA/ PIDB/ GS GA GB


SHIDA SHIDB

XS YS ZS

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C FAST 22 1 PROP 2 3

0.2 0.3 0.3

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C FAST 22 1 ELEM 101 201 21 30

Field Contents

EID Unique element identification number.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 457

Proprietary Information of Altair Engineering


Field Contents

PID Identification number of a PFAST entry.

Default = EID (Integer > 0)

CTYPE The type of connection between the patches. Either format


connects up to 3 x 3 elements per patch (possibly more for triangular
elements).

For PROP, the connection of surface patch to surface patch is


defined by specifying the property numbers of shells on side A and B,
PIDA and PIDB, respectively.

For ELEM, the connection of surface patch to surface patch is


defined by specifying IDs of shells SHIDA and SHIDB, respectively.

No default

PIDA,PIDB Property identification numbers of PSHELL entries defining surface A


and B, respectively. Required when CTYPE = PROP.

SHIDA, SHIDB Element identification numbers of shells defining fastener ends A and
B, respectively. Required when CTYPE = ELEM.

GS Identification number of a grid point which defines the location of the


connector. See comment 2.

(Integer > 0)

GA, GB These represent grid identification numbers of piercing points on


surface A and surface B respectively. See comment 3.

(Integer > 0)

XS, YS, ZS Coordinates of point that defines the location of the fastener in the
basic coordinate system. It is an alternative way of specifying the
location of GS.

(Real)

Comments

1. CFAST defines a flexible connection between two shell surface patches. An internally-
generated CBUSH element will be created automatically for a CFAST, and the end points
of this bushing will be connected to the grids of corresponding shell elements. Then the

458 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


stiffness, mass and structural damping of the CBUSH will be transferred to the
corresponding shell grids. GS, GA and GB do not hold any independent DOF. See the
figure below:

2. A CFAST element connects Shell A and Shell B. An internal CBUSH is generated for the
CFAST and supported by fictitious auxiliary points. Auxiliary points, in turn, are
constrained by corresponding shell grids. (To have a clear view, only one of these kind of
constraint relationships is shown with dotted lines).

3. The end points of the internally-generated CBUSH element are defined from GS, GA, and
GB (not all are required). If GA or GB is not specified, they are generated from the normal
projection of GS onto the surface patches. If GA and GB (or, GA only) are (is) specified,
they take precedence over GS in defining the respective end points (If only GA is
specified, then GA is used as a normal projection point (similar to GS) to generate GB on
Shell B). Also, their locations will be corrected so that they lie on surface patch A and B,
respectively. If neither GS nor GA is specified, then (XS, YS, and ZS), in the basic
coordinate system, must be specified. The length of the connector is the distance
between projected points GA and GB.

4. The connections of the internally-generated bushing to surface patches A and B are


defined in the following way: the axis GA-GB is used to define four pairs of auxiliary points
GAHi, GBHi, i=1,4 that are located on patches A and B, respectively. The cross-section
area of the resulting hexahedral is equivalent to the area of the connector, defined from
diameter D on PFAST card. The connector stiffness matrix is first built by connecting the
internally-generated bushing element to the auxiliary points, and then constraining them
to supporting shell nodes using respective shape functions. Similarly, the mass of the
fastener is divided by ½ to each side and then distributed via auxiliary points to
supporting shell nodes.

Altair Engineering OptiStruct 13.0 Reference Guide 459

Proprietary Information of Altair Engineering


5. Since the geometry for finding the correct projection could be various and complicated,
sometimes the default projection algorithm may fail. However, the default projection rules
and tolerances can be modified to some extent via the SWLDPRM card.

460 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CGAP

Bulk Data Entry

CGAP – Gap Element Connection

Description

Defines a gap or friction element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C GAP EID PID GA GB GO/X1 X2 X3 C ID

Examples

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C GAP 6 6 233 223 3.0 -1.0 1.0

Minimum necessary data when GA and GB are not coincident:

C GAP 247 1 233 223

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PGAP entry.

Default = EID (Integer > 0)

GA,GB Connected grid points at ends A and B.

Altair Engineering OptiStruct 13.0 Reference Guide 461

Proprietary Information of Altair Engineering


Field Contents

X1, X2, Components of the orientation vector, from GA, in the displacement
X3 coordinate system at GA.

Default determined automatically - See comment 7. (Real)

G0 Alternate method to supply orientation vector, using grid point G0. Direction
of orientation vector is from GA to G0.

No default (Integer > 0)

CID Element coordinate system identification number. CID must be specified if


GA and GB are coincident (distance from GA to GB < 10-4).

Alternatively: FLIP – reverses the direction of the gap axis (See comment
5).

Default = blank (Integer > 0 or flip or blank) - See comments 2 through 6.

Comments

1. For linear subcases, the CGAP element will produce a linear stiffness matrix which remains
linear with the initial stiffness. The stiffness used depends on the value for the initial gap
opening (U0 field in the PGAP entry).

2. The gap element coordinate system is defined by one of the following methods:

Prescribed CID: If the coordinate system CID is specified, the element coordinate
system is established using that coordinate system. In this case, the element x-axis is
in the coordinate system’s 1-direction, and the y-axis is in the coordinate system’s 2-
direction (for rectangular coordinate systems; the 1-direction is the x-direction and
the 2-direction is the y-direction). The orientation vector will be ignored in this case.

CID field blank: If the CID field is blank and the grid points GA and GB are not
coincident (distance from GA to GB > 10-4), then the line GA-GB is the element x-axis
and the orientation vector lies in the x-y plane (as with the CBEAM element).
FLIP option: the x-axis of the gap coordinate system is reversed with respect to the
default orientation described above. This option is useful when meshes of bodies A
and B overlap, rather than have a gap between them (See comment 5).
For gaps with coincident nodes (the distance between GA and GB < 1.0e-4), the gap
coordinate system must be specified.

3. In typical applications, leaving the CID field blank is appropriate when the nodes GA and
GB obstacle are initially separated. If the meshes of bodies A and B overlap, then a
coordinate system CID should be specified or the FLIP option should be used as discussed
below.

462 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


4. When prescribing the gap coordinate system CID, it is essential to assure that its x-axis
points in the general direction from body A (the one associated with node GA) towards
the body B (the one associated with node GB). This will assure that the gap element
acts to prevent contact/overlap of these bodies. An incorrect orientation of the x-axis
will result in gap elements being ineffective, or will even act to "glue" the bodies together,
rather than prevent them from overlapping. The solver checks for such misalignment and
prints respective error and warning messages. For more information, see the GAPPRM bulk
data card.

5. The FLIP option in the CID field is useful when meshes of bodies A and B overlap, rather
than have a gap between them. In such cases, the defaults gap axis vector GA-GB
would be opposite to the overall direction from body A to body B and therefore would
produce a "gluing" effect, rather than a resolution of the contact condition. The FLIP
option reverses the default gap direction so that the gap axis correctly points from the
bulk of body A towards body B in such cases. The effect of FLIP is equivalent to defining
a coordinate system with axis 1 pointing in direction GB-GA, rather then GA-GB.

Aside from setting the FLIP option to correctly resolve the cases with initial penetration,
U0 on the PGAP card needs to be properly set to a negative value, or an AUTO option
needs to be used in the U0 field.

Alternatively, FLIP can be used to define a simple cable element. If such an arrangement
is used, then it should be noted that:

a) F0 corresponds to a pair of forces acting on the ends of the cable (pointing inwards),
while U0 corresponds to pre-existing “slack” or extra length in the cable.

b) Gap “open” status corresponds to the cable being “shortened”, while “closed” gap
status corresponds to the cable being “elongated.”

c) Positive gap force reported in the results corresponds to the cable being in tension
(note that the force also includes the effect of F0).

6. The element coordinate system does not rotate as a result of deflections.

7. If neither coordinate system nor orientation vector are specified, the orientation vector is
defined automatically as a vector aligned with the axis of the basic coordinate system
that makes the largest angle with the gap direction (gap x-axis).

8. Initial gap openings are specified on the PGAP entry and not derived from the separation
distance between GA and GB.

9. Forces, which are requested with the FORCE card in the I/O Options or Subcase
Information sections, are output in the element coordinate system. F x is positive for
compression.

Altair Engineering OptiStruct 13.0 Reference Guide 463

Proprietary Information of Altair Engineering


C GAP Element C oordinate System

10. For more information on using nonlinear gaps, refer to the Nonlinear Quasi-Static Analysis
section of the User's Guide.

11. Heat transfer properties can be defined for Gap elements using the PGAPHT bulk data
entry.

12. This card is represented as a gap or mass element in HyperMesh.

464 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CGAPG

Bulk Data Entry

CGAPG – General Node-to-Obstacle Gap Element

Description

Defines a node-to-obstacle gap element. The obstacle may be an element face or a patch of
nodes.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C GAPG EID PID GA TYP X1/G0 X2 X3 C ID

GB1/ELIDB GB2/G1 GB3/G3 GB4/ GB5 GB6 GB7 GB8


or G4

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C GAPG 6 6 233 ELEM 3.0 -1.0 1.0

257

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C GAPG 6 6 233 QUAD

110 111 114 113

Altair Engineering OptiStruct 13.0 Reference Guide 465

Proprietary Information of Altair Engineering


Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PGAP entry.

Default = EID (Integer > 0)

GA Grid point serving as end A of CGAPG.

No default (Integer > 0)

TYP Character string indicating the type of obstacle on the B end of CGAPG
(opposing node GA):

QUAD indicates that the obstacle is defined as a quadrilateral patch of grid


points. The patch is defined with grid identification numbers GB#.

TRIA indicates that the obstacle is defined as a triangular patch of grid


points. The patch is defined with grid identification numbers GB#.

ELEM indicates that the obstacle is defined as element face.

No default (QUAD, TRIA or ELEM)

X1, X2, X3 Components of the orientation vector, from GA, in the displacement
coordinate system at GA.

Default determined automatically – See comment 6. (Real)

G0 Alternate method to supply orientation vector, using grid point G0.


Direction of orientation vector is from GA to G0.

No default (Integer > 0)

CID Prescribed element coordinate system identification number. CID, when


prescribed, is used to define both the gap axis and orientation vector.

Additional keywords that can be used in this field:

FLIP – reverses the default orientation of gap axis, so it points from


obstacle B towards GA.

PUSHOUT – for obstacles defined as solid elements using ELIDB, gap axis is
automatically defined so as to create “pushout” force that prevents GA

466 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

from entering the interior of the element ELIDB.

PUSHNORM – gap axis is automatically defined so as to create “pushout”


force from obstacle B towards GA along the default vector normal to the
obstacle B.

PUSHREVN – creates pushout force reversed relative to the PUSHNORM


option.

Default = blank (Integer > 0, FLIP, PUSHOUT, PUSHNORM, PUSHREVN, or


blank). See comments 2 through 5.

GB# Grid identification number of the grid surface patch on the B (obstacle)
end of the CGAPG element. GB1 to GB3 are required.

No default (Integer > 0). See comment 7.

ELIDB Element identification number of the element on the B (obstacle) end of


the CGAPG element.

No default (Integer > 0)

G1 For solid element ELIDB: identification number of a grid point connected to


a corner of the face that defines the second end of the CGAPG element.
For PYRA elements, this grid must be on an edge of the quadrilateral face.

Default = blank (Integer > 0 or blank). See comments 8 through 11.

G3 For solid element ELIDB: identification number of a grid point connected to


a corner diagonally opposite to G1 on the same face of a HEXA or PENTA
element. Needed only if G1 has been specified. It is required data for
quadrilateral faces of HEXA and PENTA elements only (Integer or blank).
G3 must be omitted for a triangular surface on a PENTA element and the
quadrilateral face on a PYRA element. For triangular faces of PYRA
elements, this grid must be on the edge next to the quadrilateral face. G1
and G3 must define a positive direction into the element using the right
hand rule.

Default = blank (Integer > 0 or blank). See comments 8 through 11.

G4 For solid element ELIDB: identification number of the TETRA grid point
located at the corner, not on the face being loaded. This is used for
TETRA elements only. It is required data if G1 has been specified.

Default = blank (Integer > 0 or blank)

Altair Engineering OptiStruct 13.0 Reference Guide 467

Proprietary Information of Altair Engineering


Comments

1. CGAPG defines a contact element between a point and an obstacle. The obstacle may be
defined as a patch of nodes or as an element face. See figure below:

Typical configuration of C GAPG between node GA and a grid patch GB1…GB4.

2. The gap element coordinate system is defined via one of the following methods:

Prescribed CID: if the coordinate system CID is specified, the element coordinate
system is established using that coordinate system. In this case, the element x-axis is
in the coordinate system’s 1-direction, and the y-axis is in the coordinate system’s 2-
direction (for rectangular coordinate systems; the 1-direction is the x-direction and
the 2-direction is the y-direction). The orientation vector will be ignored in this case.
CID field blank: if the CID field is blank and the grid point GA does not lie on the
element face or node patch (distance from GA to the surface > 10-4), then the x-axis
is defined along the shortest distance from GA to the element face or node patch. The
orientation of gap x-axis points from GA towards the patch or element face (see figure
above). The orientation vector defines the x-y plane of the gap coordinate system
(similarly as for the CGAP element).

If the grid point GA lies on the element face or node patch (distance from GA to the
surface < 10-4), then CID must be prescribed.
FLIP option: the x-axis of the gap coordinate system is reversed with respect to the
default orientation described above. This option is useful when meshes of bodies A
and B overlap rather than have a gap between them (See comment 5).
PUSHOUT option: the x-axis of the gap coordinate system is oriented so as to prevent
GA from entering interior of body B. This is only available for obstacles defined as 3D
solid elements with ELIDB.

468 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


With the PUSHNORM option, the gap axis is so oriented so as to produce “pushout”
force from obstacle B towards GA along the default normal vector to the obstacle –
element face or node patch. (Note that this pushout force direction is opposite to the
gap axis, which points from GA towards the obstacle.)

In cases when GA does not have a direct normal projection onto the obstacle B, and
the "shortest distance" projection is used (GAPGPRJ set to SHORT on the GAPPRM
card), the pushout force is oriented along the shortest distance line, yet with the
orientation aligned with the normal vector.

PUSHREVN creates pushout force reversed relative to the PUSHNORM option.

Note that for faces on solid elements, the default normal is pointing inwards, so that it
is the PUSHREVN option that will prevent penetration (PUSHOUT is a more
straightforward option to use on solid faces).
3. In typical applications, leaving the CID field blank is appropriate when the node GA and
the obstacle are initially separated; that is, there is a gap between respective bodies A
and B (see figure above). If the meshes of bodies A and B overlap, then a coordinate
system CID should be specified (See comment 4). Alternatively, and usually more
intuitively, one of the FLIP, PUSHOUT, PUSHNORM, or PUSHREVN options may be used.

4. When prescribing the gap coordinate system CID, it is essential to assure that the
resulting gap x-axis points in the general direction from body A (the one associated with
node GA) towards body B (the one associated with element ELIDB or patch GB#). This
assures that the gap element will act to prevent the contact/overlap of these bodies. An
incorrect orientation of the x-axis will result in the gap element being ineffective or can
even act to "glue" the bodies together rather than prevent their overlap. The solver
checks for such misalignment and prints respective error and warning messages. For more
information, see the GAPPRM bulk data card.

5. The FLIP option in the CID field is useful when the meshes of bodies A and B overlap
rather than have a gap between them. In such cases, the default gap axis vector would
be opposite to the overall direction from body A to body B, and therefore would produce a
"gluing" effect rather than a resolution of the contact condition. The FLIP option reverses
the default gap direction so that the gap axis correctly points from the bulk of body A
towards body B in such cases.

Aside from setting the FLIP option or prescribing CID to correctly resolve the cases with
initial penetration, U0 on the PGAP card needs to be properly set to a negative value or
an AUTO option needs to be used in the U0 field.

6. If neither coordinate system CID nor orientation vector is specified, the orientation vector
is defined automatically as a vector aligned with the axis of the basic coordinate system
that makes the largest angle with the gap direction (gap x-axis).

7. GB# are required when TYP is QUAD or TRIA. At least 3, and at most 8, grid IDs may be
specified for GB#. Triangular and quadrilateral element definition sequences apply for the
order of GB# (see below). Missing mid-side nodes are allowed.

Altair Engineering OptiStruct 13.0 Reference Guide 469

Proprietary Information of Altair Engineering


Quadrilateral and triangular surface patches as defined when TYP is QUAD or TRIA.

8. If ELIDB represents a solid element and G1, G3/G4 fields are blank, then the element face
closest to the grid GA is selected as the respective obstacle face.

Note that if the meshes are overlapping (such as in the case of initial penetration), this
option should not be used, and the contact face should be explicitly prescribed.
Otherwise, the face closest to GA may be an internal face within the solid body, rather
than the outside surface of body B.

9. G1 and G3 are ignored for shell elements (TRIA3, QUAD4, TRIA6 and QUAD8).

10. For triangular faces of PENTA elements, G1 is an identification number of a corner grid
point that is on the face being loaded and the G3 or G4 field is left blank. For faces of
TETRA elements, G1 is an identification number of a corner grid point that is on the face
being loaded and G4 is an identification number of the corner grid point that is not on the
face being loaded. Since a TETRA has only four corner points, this point, G4, is unique
and different for each of the four faces of a TETRA element.

11. For the quadrilateral face of the PYRA element, G1 is an identification number of a corner
grid point on the face and the G3 or G4 field is left blank. For the triangular faces, G1 and
G3 must specify the grids on the edge of the face that borders the quadrilateral face and
the grids must be ordered so that they define an inward normal using the right hand rule.

12. The element coordinate system does not rotate as a result of deformation.

13. Initial gap openings are specified on the PGAP entry and not derived from the separation
distance between GA and GB, unless the AUTO option is used on the PGAP card.

14. Gap forces, which are requested with the FORCE card in the I/O Options or Subcase
Information sections, are output in the gap element coordinate system. F x is positive for
compression.

15. For linear subcases, the CGAPG element will produce a linear stiffness matrix which
remains linear with the initial stiffness. The stiffness used depends on the value for the
initial gap opening (U0 field in the PGAP entry).

16. For more information on using nonlinear gaps, refer to the Nonlinear Quasi-Static Analysis
section of the User's Guide.

470 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


17. This card is represented as a gap or mass element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 471

Proprietary Information of Altair Engineering


CGASK6

Bulk Data Entry

CGASK6 – Five-sided Solid Gasket Element with Six Grid Nodes

Description

Defining the connections of the GASK6 solid gasket element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C GASK6 EID PID G1 G2 G3 G4 G5 G6

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C GASK6 71 4 3 4 5 6 7 8

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PGASK property entry.

Default = EID (Integer > 0)

G# Grid point identification number of connection points.

No default (Integer > 0)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

472 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


2. Grid points G1, …, G3 must be given in consecutive order at the bottom face of the
gasket element. G4, …, G6 must be on the top face with G4 opposite G1, G5 opposite G2,
and so on.

3. If the user-prescribed node numbering on the bottom and top faces is reversed as
compared to the sequence shown above, then the nodes are renumbered to produce
right-handed orientation of numbering. This is accomplished by swapping nodes G1 with
G3 and G4 with G6. In such cases, the element local coordinate system will be built on
the renumbered node sequence.

4. The element coordinate system for the CGASK6 element is defined below.

The local 3-direction (the gasket material thickness direction in default) is defined as the
simple average of the unit normal directions on the top and bottom surfaces of the
element. After the local 3-direction is defined, a local 1-2 plane is generated accordingly.

Then, the local 1-direction and 2-direction are defined as follows: Project the basic x-axis
onto the local 1-2 plane, and set it to be the default local 1-direction. If the basic x-axis
is within 0.1° difference as the local 3-direction, project the basic z-axis onto the local 1-
2 plane and set it to be the local 1-direction. The local 2-direction is determined then.

5. The gasket material coordinate system is the same as the element coordinate system in
default and can be defined as a prescribed system through PGASK entry.

6. This card is represented as a gask6 element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 473

Proprietary Information of Altair Engineering


CGASK8

Bulk Data Entry

CGASK8 – Six-sided Solid Gasket Element with Eight Grid Nodes

Description

Defining the connections of the GASK8 solid gasket element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C GASK8 EID PID G1 G2 G3 G4 G5 G6

G7 G8

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C GASK8 71 4 3 4 5 6 7 8

9 10

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PGASK property entry.

Default = EID (Integer > 0)

G# Grid point identification number of connection points.

No default (Integer > 0)

474 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. Grid points G1, …, G4 must be given in consecutive order at the bottom face of the
gasket element. G5, …, G8 must be on the top face with G5 opposite G1, G6 opposite G2,
and so on.

3. If the user-prescribed node numbering on the bottom and top faces is reversed as
compared to the sequence shown above, then the nodes are renumbered to produce
right-handed orientation of numbering. This is accomplished by swapping nodes G1 with
G3 and G5 with G7. In such cases, the element local coordinate system will be built on
the renumbered node sequence.

4. The element coordinate system for the CGASK8 element is defined below.

The local 3-direction (the gasket material thickness direction in default) is defined as the
simple average of the unit normal directions on the top and bottom surfaces of the
element. After the local 3-direction is defined, a local 1-2 plane is generated accordingly.

Then, the local 1-direction and 2-direction are defined as follows: Project the basic x-axis
onto the local 1-2 plane, and set it to be the default local 1-direction. If the basic x-axis
is within 0.1° difference as the local 3-direction, project the basic z-axis onto the local 1-
2 plane and set it to be the local 1-direction. The local 2-direction is determined then.

5. The gasket material coordinate system is the same as the element coordinate system in
default and can be defined as a prescribed system through PGASK entry.

6. This card is represented as a gask8 element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 475

Proprietary Information of Altair Engineering


CGASK12

Bulk Data Entry

CGASK12 – Five-sided Solid Gasket Element with Twelve Grid Nodes

Description

Defining the connections of the GASK12 solid gasket element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C GASK12 EID PID G1 G2 G3 G4 G5 G6

G7 G8 G9 G10 G11 G12

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C GASK12 71 4 3 4 5 6 7 8

9 10 11 12 13 14

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PGASK property entry.

Default = EID (Integer > 0)

G# Grid point identification number of connection points.

No default (Integer > 0)

476 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. Corner grid points G1, …, G3 must be given in consecutive order at the bottom face of the
gasket element. Corner grid points G4, …, G6 must be on the top face with G4 opposite
G1, G5 opposite G2, and so on.

Edge grid points G7, …, G9 must be given in consecutive order at the bottom face of the
gasket element. Edge grid points G10, …, G12 must be on the top face with G10 opposite
G7, G11 opposite G8, and so on.

3. If the user-prescribed node numbering on the bottom and top faces is reversed as
compared to the sequence shown above, then the nodes are renumbered to produce
right-handed orientation of numbering. This is accomplished by swapping nodes G1 with
G3 and G4 with G6. In such cases, the element local coordinate system will be built on
the renumbered node sequence.

4. The element coordinate system for the CGASK12 element is defined below.

The local 3-direction (the gasket material thickness direction in default) is defined as the
simple average of the unit normal directions on the top and bottom surfaces of the
element. After the local 3-direction is defined, a local 1-2 plane is generated accordingly.

Then, the local 1-direction and 2-direction are defined as follows: Project the basic x-axis
onto the local 1-2 plane, and set it to be the default local 1-direction. If the basic x-axis
is within 0.1° difference as the local 3-direction, project the basic z-axis onto the local 1-
2 plane and set it to be the local 1-direction. The local 2-direction is determined then.

5. The gasket material coordinate system is the same as the element coordinate system in
default and can be defined as a prescribed system through PGASK entry.

6. This card is represented as a gask12 element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 477

Proprietary Information of Altair Engineering


CGASK16

Bulk Data Entry

CGASK16 – Six-sided Solid Gasket Element with Sixteen Grid Nodes

Description

Defining the connections of the GASK16 solid gasket element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C GASK16 EID PID G1 G2 G3 G4 G5 G6

G7 G8 G9 G10 G11 G12 G13 G14

G15 G16

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C GASK16 71 4 3 4 5 6 7 8

9 10 11 12 13 14 15 16

17 18

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PGASK property entry.

Default = EID (Integer > 0)

478 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

G# Grid point identification number of connection points.

No default (Integer > 0)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. Corner grid points G1, …, G4 must be given in consecutive order at the bottom face of the
gasket element. Corner grid points G5, …, G8 must be on the top face with G5 opposite
G1, G6 opposite G2, and so on.

Edge grid points G9, …, G12 must be given in consecutive order at the bottom face of the
gasket element. Edge grid points G13, …, G16 must be on the top face with G13 opposite
G9, G14 opposite G10, and so on.

3. If the user-prescribed node numbering on the bottom and top faces is reversed as
compared to the sequence shown above, then the nodes are renumbered to produce
right-handed orientation of numbering. This is accomplished by swapping nodes G1 with
G3 and G5 with G7. In such cases, the element local coordinate system will be built on
the renumbered node sequence.

4. The element coordinate system for the CGASK16 element is defined below.

The local 3-direction (the gasket material thickness direction in default) is defined as the
simple average of the unit normal directions on the top and bottom surfaces of the
element. After the local 3-direction is defined, a local 1-2 plane is generated accordingly.

Then, the local 1-direction and 2-direction are defined as follows: Project the basic x-axis
onto the local 1-2 plane, and set it to be the default local 1-direction. If the basic x-axis
is within 0.1° difference as the local 3-direction, project the basic z-axis onto the local 1-
2 plane and set it to be the local 1-direction. The local 2-direction is determined then.

5. The gasket material coordinate system is the same as the element coordinate system in
default and can be defined as a prescribed system through PGASK entry.

Altair Engineering OptiStruct 13.0 Reference Guide 479

Proprietary Information of Altair Engineering


6. This card is represented as a gask16 element in HyperMesh.

480 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHACAB

Bulk Data Entry

CHACAB – Six-sided, Frequency-dependent Structural Acoustic Absorber Element

Description

Defines the frequency-dependent structural acoustic absorber element in coupled fluid-


structural analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C HAC AB EID PID G1 G2 G3 G4 G5 G6

G7 G8 G9 G10 G11 G12

G17 G18 G19 G20

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C HAC AB 71 4 3 4 5 6 7 8

9 10

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PACABS property entry.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 481

Proprietary Information of Altair Engineering


Field Contents

Gi Grid point identification numbers of connection points.

Default = blank (Integer > 0 or blank)

Input File - chacab.fem

$$------------------------------------------------------------------------------$
$$ $
$$ NASTRAN Input Deck Generated by HyperMesh Version : 8.0SR1 $
$$ Generated using HyperMesh-Nastran Template Version : 8.0sr1
$$ $
$$ Template: general $
$$ $
$$------------------------------------------------------------------------------$
$$------------------------------------------------------------------------------$
$$ Executive Control Cards $
$$------------------------------------------------------------------------------$
SOL 111
CEND
$$------------------------------------------------------------------------------$
$$ Case Control Cards $
$$------------------------------------------------------------------------------$
SET 1 = 1734
DISPLACEMENT = 1
$
$HMNAME LOADSTEP 1"Load2"
SUBCASE 1
LABEL= Load2
SPC = 4
FREQUENCY = 5
DLOAD = 2
$$------------------------------------------------------------------------------$
$$ Bulk Data Cards $
$$------------------------------------------------------------------------------$
BEGIN BULK

$CHEXA 1056 2 1650 1661 1662 1651 1671 1682+


$+ 1683 1672
CHACAB 1056 100 1650 1645 1657 1658 1676 1675+
+ 1671 1672
PACABS,100,YES,1,2,3,1.5,10.0,2.0
PARAM,G,0.001
PARAM,COUPMASS,-1
PARAM,POST,-1
$ACMODL DIFF 0.1
$$
EIGRL,20,,,300
EIGRL,21,,,300
$$ GRID Data
$$
GRID 1 2.0 2.0 0.0 -1
GRID 2 2.0 1.5 0.0 -1
GRID 3 2.0 1.0 0.0 -1
GRID 4 2.0 0.5 0.0 -1
GRID 5 2.0 0.0 0.0 -1
GRID 6 2.0 -0.5 0.0 -1
GRID 7 2.0 -1.0 0.0 -1
GRID 8 2.0 -1.5 0.0 -1
GRID 9 2.0 -2.0 0.0 -1

482 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 10 1.5 2.0 0.0 -1
GRID 11 1.5 1.5 0.0 -1
GRID 12 1.5 1.0 0.0 -1
GRID 13 1.5 0.5 0.0 -1
GRID 14 1.5 0.0 0.0 -1
GRID 15 1.5 -0.5 0.0 -1
GRID 16 1.5 -1.0 0.0 -1
GRID 17 1.5 -1.5 0.0 -1
GRID 18 1.5 -2.0 0.0 -1
GRID 19 1.0 2.0 0.0 -1
GRID 20 1.0 1.5 0.0 -1
GRID 21 1.0 1.0 0.0 -1
GRID 22 1.0 0.5 0.0 -1
GRID 23 1.0 0.0 0.0 -1
GRID 24 1.0 -0.5 0.0 -1
GRID 25 1.0 -1.0 0.0 -1
GRID 26 1.0 -1.5 0.0 -1
GRID 27 1.0 -2.0 0.0 -1
GRID 28 0.5 2.0 0.0 -1
GRID 29 0.5 1.5 0.0 -1
GRID 30 0.5 1.0 0.0 -1
GRID 31 0.5 0.5 0.0 -1
GRID 32 0.5 0.0 0.0 -1
GRID 33 0.5 -0.5 0.0 -1
GRID 34 0.5 -1.0 0.0 -1
GRID 35 0.5 -1.5 0.0 -1
GRID 36 0.5 -2.0 0.0 -1
GRID 37 0.0 2.0 0.0 -1
GRID 38 0.0 1.5 0.0 -1
GRID 39 0.0 1.0 0.0 -1
GRID 40 0.0 0.5 0.0 -1
GRID 41 0.0 0.0 0.0 -1
GRID 42 0.0 -0.5 0.0 -1
GRID 43 0.0 -1.0 0.0 -1
GRID 44 0.0 -1.5 0.0 -1
GRID 45 0.0 -2.0 0.0 -1
GRID 46 -0.5 2.0 0.0 -1
GRID 47 -0.5 1.5 0.0 -1
GRID 48 -0.5 1.0 0.0 -1
GRID 49 -0.5 0.5 0.0 -1
GRID 50 -0.5 0.0 0.0 -1
GRID 51 -0.5 -0.5 0.0 -1
GRID 52 -0.5 -1.0 0.0 -1
GRID 53 -0.5 -1.5 0.0 -1
GRID 54 -0.5 -2.0 0.0 -1
GRID 55 -1.0 2.0 0.0 -1
GRID 56 -1.0 1.5 0.0 -1
GRID 57 -1.0 1.0 0.0 -1
GRID 58 -1.0 0.5 0.0 -1
GRID 59 -1.0 0.0 0.0 -1
GRID 60 -1.0 -0.5 0.0 -1
GRID 61 -1.0 -1.0 0.0 -1
GRID 62 -1.0 -1.5 0.0 -1
GRID 63 -1.0 -2.0 0.0 -1
GRID 64 -1.5 2.0 0.0 -1
GRID 65 -1.5 1.5 0.0 -1
GRID 66 -1.5 1.0 0.0 -1
GRID 67 -1.5 0.5 0.0 -1
GRID 68 -1.5 0.0 0.0 -1
GRID 69 -1.5 -0.5 0.0 -1
GRID 70 -1.5 -1.0 0.0 -1
GRID 71 -1.5 -1.5 0.0 -1
GRID 72 -1.5 -2.0 0.0 -1
GRID 73 -2.0 2.0 0.0 -1
GRID 74 -2.0 1.5 0.0 -1
GRID 75 -2.0 1.0 0.0 -1
GRID 76 -2.0 0.5 0.0 -1
GRID 77 -2.0 0.0 0.0 -1
GRID 78 -2.0 -0.5 0.0 -1

Altair Engineering OptiStruct 13.0 Reference Guide 483

Proprietary Information of Altair Engineering


GRID 79 -2.0 -1.0 0.0 -1
GRID 80 -2.0 -1.5 0.0 -1
GRID 81 -2.0 -2.0 0.0 -1
GRID 82 2.5 2.0 0.0 -1
GRID 83 2.5 1.5 0.0 -1
GRID 84 2.5 1.0 0.0 -1
GRID 85 2.5 0.5 0.0 -1
GRID 86 2.5 0.0 0.0 -1
GRID 87 2.5 -0.5 0.0 -1
GRID 88 2.5 -1.0 0.0 -1
GRID 89 2.5 -1.5 0.0 -1
GRID 90 2.5 -2.0 0.0 -1
GRID 91 -2.5 2.0 0.0 -1
GRID 92 -2.5 1.5 0.0 -1
GRID 93 -2.5 1.0 0.0 -1
GRID 94 -2.5 0.5 0.0 -1
GRID 95 -2.5 0.0 0.0 -1
GRID 96 -2.5 -0.5 0.0 -1
GRID 97 -2.5 -1.0 0.0 -1
GRID 98 -2.5 -1.5 0.0 -1
GRID 99 -2.5 -2.0 0.0 -1
GRID 100 2.5 2.5 0.0 -1
GRID 101 2.5 -2.5 0.0 -1
GRID 102 2.0 2.5 0.0 -1
GRID 103 2.0 -2.5 0.0 -1
GRID 104 1.5 2.5 0.0 -1
GRID 105 1.5 -2.5 0.0 -1
GRID 106 1.0 2.5 0.0 -1
GRID 107 1.0 -2.5 0.0 -1
GRID 108 0.5 2.5 0.0 -1
GRID 109 0.5 -2.5 0.0 -1
GRID 110 0.0 2.5 0.0 -1
GRID 111 0.0 -2.5 0.0 -1
GRID 112 -0.5 2.5 0.0 -1
GRID 113 -0.5 -2.5 0.0 -1
GRID 114 -1.0 2.5 0.0 -1
GRID 115 -1.0 -2.5 0.0 -1
GRID 116 -1.5 2.5 0.0 -1
GRID 117 -1.5 -2.5 0.0 -1
GRID 118 -2.0 2.5 0.0 -1
GRID 119 -2.0 -2.5 0.0 -1
GRID 120 -2.5 2.5 0.0 -1
GRID 121 -2.5 -2.5 0.0 -1
GRID 727 2.5 2.5 1.0 -1
GRID 728 2.5 2.0 1.0 -1
GRID 729 2.0 2.0 1.0 -1
GRID 730 2.0 2.5 1.0 -1
GRID 731 2.5 1.5 1.0 -1
GRID 732 2.0 1.5 1.0 -1
GRID 733 2.5 1.0 1.0 -1
GRID 734 2.0 1.0 1.0 -1
GRID 735 2.5 0.5 1.0 -1
GRID 736 2.0 0.5 1.0 -1
GRID 737 2.5 -4.2E-191.0 -1
GRID 738 2.0 -6.5E-201.0 -1
GRID 739 2.5 -0.5 1.0 -1
GRID 740 2.0 -0.5 1.0 -1
GRID 741 2.5 -1.0 1.0 -1
GRID 742 2.0 -1.0 1.0 -1
GRID 743 2.5 -1.5 1.0 -1
GRID 744 2.0 -1.5 1.0 -1
GRID 745 2.5 -2.0 1.0 -1
GRID 746 2.0 -2.0 1.0 -1
GRID 747 2.5 -2.5 1.0 -1
GRID 748 2.0 -2.5 1.0 -1
GRID 749 1.5 2.0 1.0 -1
GRID 750 1.5 2.5 1.0 -1
GRID 751 1.5 1.5 1.0 -1
GRID 752 1.5 1.0 1.0 -1

484 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 753 1.5 0.5 1.0 -1
GRID 754 1.5 -9.8E-211.0 -1
GRID 755 1.5 -0.5 1.0 -1
GRID 756 1.5 -1.0 1.0 -1
GRID 757 1.5 -1.5 1.0 -1
GRID 758 1.5 -2.0 1.0 -1
GRID 759 1.5 -2.5 1.0 -1
GRID 760 1.0 2.0 1.0 -1
GRID 761 1.0 2.5 1.0 -1
GRID 762 1.0 1.5 1.0 -1
GRID 763 1.0 1.0 1.0 -1
GRID 764 1.0 0.5 1.0 -1
GRID 765 1.0 -1.5E-211.0 -1
GRID 766 1.0 -0.5 1.0 -1
GRID 767 1.0 -1.0 1.0 -1
GRID 768 1.0 -1.5 1.0 -1
GRID 769 1.0 -2.0 1.0 -1
GRID 770 1.0 -2.5 1.0 -1
GRID 771 0.5 2.0 1.0 -1
GRID 772 0.5 2.5 1.0 -1
GRID 773 0.5 1.5 1.0 -1
GRID 774 0.5 1.0 1.0 -1
GRID 775 0.5 0.5 1.0 -1
GRID 776 0.5 -2.3E-221.0 -1
GRID 777 0.5 -0.5 1.0 -1
GRID 778 0.5 -1.0 1.0 -1
GRID 779 0.5 -1.5 1.0 -1
GRID 780 0.5 -2.0 1.0 -1
GRID 781 0.5 -2.5 1.0 -1
GRID 782 0.0 2.0 1.0 -1
GRID 783 0.0 2.5 1.0 -1
GRID 784 0.0 1.5 1.0 -1
GRID 785 0.0 1.0 1.0 -1
GRID 786 0.0 0.5 1.0 -1
GRID 787 0.0 -3.5E-231.0 -1
GRID 788 0.0 -0.5 1.0 -1
GRID 789 0.0 -1.0 1.0 -1
GRID 790 0.0 -1.5 1.0 -1
GRID 791 0.0 -2.0 1.0 -1
GRID 792 0.0 -2.5 1.0 -1
GRID 793 -0.5 2.0 1.0 -1
GRID 794 -0.5 2.5 1.0 -1
GRID 795 -0.5 1.5 1.0 -1
GRID 796 -0.5 1.0 1.0 -1
GRID 797 -0.5 0.5 1.0 -1
GRID 798 -0.5 -5.3E-241.0 -1
GRID 799 -0.5 -0.5 1.0 -1
GRID 800 -0.5 -1.0 1.0 -1
GRID 801 -0.5 -1.5 1.0 -1
GRID 802 -0.5 -2.0 1.0 -1
GRID 803 -0.5 -2.5 1.0 -1
GRID 804 -1.0 2.0 1.0 -1
GRID 805 -1.0 2.5 1.0 -1
GRID 806 -1.0 1.5 1.0 -1
GRID 807 -1.0 1.0 1.0 -1
GRID 808 -1.0 0.5 1.0 -1
GRID 809 -1.0 -8.1E-251.0 -1
GRID 810 -1.0 -0.5 1.0 -1
GRID 811 -1.0 -1.0 1.0 -1
GRID 812 -1.0 -1.5 1.0 -1
GRID 813 -1.0 -2.0 1.0 -1
GRID 814 -1.0 -2.5 1.0 -1
GRID 815 -1.5 2.0 1.0 -1
GRID 816 -1.5 2.5 1.0 -1
GRID 817 -1.5 1.5 1.0 -1
GRID 818 -1.5 1.0 1.0 -1
GRID 819 -1.5 0.5 1.0 -1
GRID 820 -1.5 -9.3E-181.0 -1
GRID 821 -1.5 -0.5 1.0 -1

Altair Engineering OptiStruct 13.0 Reference Guide 485

Proprietary Information of Altair Engineering


GRID 822 -1.5 -1.0 1.0 -1
GRID 823 -1.5 -1.5 1.0 -1
GRID 824 -1.5 -2.0 1.0 -1
GRID 825 -1.5 -2.5 1.0 -1
GRID 826 -2.0 2.0 1.0 -1
GRID 827 -2.0 2.5 1.0 -1
GRID 828 -2.0 1.5 1.0 -1
GRID 829 -2.0 1.0 1.0 -1
GRID 830 -2.0 0.5 1.0 -1
GRID 831 -2.0 -2.0E-181.0 -1
GRID 832 -2.0 -0.5 1.0 -1
GRID 833 -2.0 -1.0 1.0 -1
GRID 834 -2.0 -1.5 1.0 -1
GRID 835 -2.0 -2.0 1.0 -1
GRID 836 -2.0 -2.5 1.0 -1
GRID 837 -2.5 2.0 1.0 -1
GRID 838 -2.5 2.5 1.0 -1
GRID 839 -2.5 1.5 1.0 -1
GRID 840 -2.5 1.0 1.0 -1
GRID 841 -2.5 0.5 1.0 -1
GRID 842 -2.5 -1.0E-181.0 -1
GRID 843 -2.5 -0.5 1.0 -1
GRID 844 -2.5 -1.0 1.0 -1
GRID 845 -2.5 -1.5 1.0 -1
GRID 846 -2.5 -2.0 1.0 -1
GRID 847 -2.5 -2.5 1.0 -1
GRID 848 2.5 2.5 2.0 -1
GRID 849 2.5 2.0 2.0 -1
GRID 850 2.0 2.0 2.0 -1
GRID 851 2.0 2.5 2.0 -1
GRID 852 2.5 1.5 2.0 -1
GRID 853 2.0 1.5 2.0 -1
GRID 854 2.5 1.0 2.0 -1
GRID 855 2.0 1.0 2.0 -1
GRID 856 2.5 0.5 2.0 -1
GRID 857 2.0 0.5 2.0 -1
GRID 858 2.5 -6.0E-192.0 -1
GRID 859 2.0 -1.2E-192.0 -1
GRID 860 2.5 -0.5 2.0 -1
GRID 861 2.0 -0.5 2.0 -1
GRID 862 2.5 -1.0 2.0 -1
GRID 863 2.0 -1.0 2.0 -1
GRID 864 2.5 -1.5 2.0 -1
GRID 865 2.0 -1.5 2.0 -1
GRID 866 2.5 -2.0 2.0 -1
GRID 867 2.0 -2.0 2.0 -1
GRID 868 2.5 -2.5 2.0 -1
GRID 869 2.0 -2.5 2.0 -1
GRID 870 1.5 2.0 2.0 -1
GRID 871 1.5 2.5 2.0 -1
GRID 872 1.5 1.5 2.0 -1
GRID 873 1.5 1.0 2.0 -1
GRID 874 1.5 0.5 2.0 -1
GRID 875 1.5 -2.1E-202.0 -1
GRID 876 1.5 -0.5 2.0 -1
GRID 877 1.5 -1.0 2.0 -1
GRID 878 1.5 -1.5 2.0 -1
GRID 879 1.5 -2.0 2.0 -1
GRID 880 1.5 -2.5 2.0 -1
GRID 881 1.0 2.0 2.0 -1
GRID 882 1.0 2.5 2.0 -1
GRID 883 1.0 1.5 2.0 -1
GRID 884 1.0 1.0 2.0 -1
GRID 885 1.0 0.5 2.0 -1
GRID 886 1.0 -3.8E-212.0 -1
GRID 887 1.0 -0.5 2.0 -1
GRID 888 1.0 -1.0 2.0 -1
GRID 889 1.0 -1.5 2.0 -1
GRID 890 1.0 -2.0 2.0 -1

486 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 891 1.0 -2.5 2.0 -1
GRID 892 0.5 2.0 2.0 -1
GRID 893 0.5 2.5 2.0 -1
GRID 894 0.5 1.5 2.0 -1
GRID 895 0.5 1.0 2.0 -1
GRID 896 0.5 0.5 2.0 -1
GRID 897 0.5 -6.7E-222.0 -1
GRID 898 0.5 -0.5 2.0 -1
GRID 899 0.5 -1.0 2.0 -1
GRID 900 0.5 -1.5 2.0 -1
GRID 901 0.5 -2.0 2.0 -1
GRID 902 0.5 -2.5 2.0 -1
GRID 903 0.0 2.0 2.0 -1
GRID 904 0.0 2.5 2.0 -1
GRID 905 0.0 1.5 2.0 -1
GRID 906 0.0 1.0 2.0 -1
GRID 907 0.0 0.5 2.0 -1
GRID 908 0.0 -1.2E-222.0 -1
GRID 909 0.0 -0.5 2.0 -1
GRID 910 0.0 -1.0 2.0 -1
GRID 911 0.0 -1.5 2.0 -1
GRID 912 0.0 -2.0 2.0 -1
GRID 913 0.0 -2.5 2.0 -1
GRID 914 -0.5 2.0 2.0 -1
GRID 915 -0.5 2.5 2.0 -1
GRID 916 -0.5 1.5 2.0 -1
GRID 917 -0.5 1.0 2.0 -1
GRID 918 -0.5 0.5 2.0 -1
GRID 919 -0.5 -2.0E-232.0 -1
GRID 920 -0.5 -0.5 2.0 -1
GRID 921 -0.5 -1.0 2.0 -1
GRID 922 -0.5 -1.5 2.0 -1
GRID 923 -0.5 -2.0 2.0 -1
GRID 924 -0.5 -2.5 2.0 -1
GRID 925 -1.0 2.0 2.0 -1
GRID 926 -1.0 2.5 2.0 -1
GRID 927 -1.0 1.5 2.0 -1
GRID 928 -1.0 1.0 2.0 -1
GRID 929 -1.0 0.5 2.0 -1
GRID 930 -1.0 -1.4E-182.0 -1
GRID 931 -1.0 -0.5 2.0 -1
GRID 932 -1.0 -1.0 2.0 -1
GRID 933 -1.0 -1.5 2.0 -1
GRID 934 -1.0 -2.0 2.0 -1
GRID 935 -1.0 -2.5 2.0 -1
GRID 936 -1.5 2.0 2.0 -1
GRID 937 -1.5 2.5 2.0 -1
GRID 938 -1.5 1.5 2.0 -1
GRID 939 -1.5 1.0 2.0 -1
GRID 940 -1.5 0.5 2.0 -1
GRID 941 -1.5 -1.3E-172.0 -1
GRID 942 -1.5 -0.5 2.0 -1
GRID 943 -1.5 -1.0 2.0 -1
GRID 944 -1.5 -1.5 2.0 -1
GRID 945 -1.5 -2.0 2.0 -1
GRID 946 -1.5 -2.5 2.0 -1
GRID 947 -2.0 2.0 2.0 -1
GRID 948 -2.0 2.5 2.0 -1
GRID 949 -2.0 1.5 2.0 -1
GRID 950 -2.0 1.0 2.0 -1
GRID 951 -2.0 0.5 2.0 -1
GRID 952 -2.0 -4.1E-182.0 -1
GRID 953 -2.0 -0.5 2.0 -1
GRID 954 -2.0 -1.0 2.0 -1
GRID 955 -2.0 -1.5 2.0 -1
GRID 956 -2.0 -2.0 2.0 -1
GRID 957 -2.0 -2.5 2.0 -1
GRID 958 -2.5 2.0 2.0 -1
GRID 959 -2.5 2.5 2.0 -1

Altair Engineering OptiStruct 13.0 Reference Guide 487

Proprietary Information of Altair Engineering


GRID 960 -2.5 1.5 2.0 -1
GRID 961 -2.5 1.0 2.0 -1
GRID 962 -2.5 0.5 2.0 -1
GRID 963 -2.5 -2.5E-182.0 -1
GRID 964 -2.5 -0.5 2.0 -1
GRID 965 -2.5 -1.0 2.0 -1
GRID 966 -2.5 -1.5 2.0 -1
GRID 967 -2.5 -2.0 2.0 -1
GRID 968 -2.5 -2.5 2.0 -1
GRID 969 2.5 2.5 3.0 -1
GRID 970 2.5 2.0 3.0 -1
GRID 971 2.0 2.0 3.0 -1
GRID 972 2.0 2.5 3.0 -1
GRID 973 2.5 1.5 3.0 -1
GRID 974 2.0 1.5 3.0 -1
GRID 975 2.5 1.0 3.0 -1
GRID 976 2.0 1.0 3.0 -1
GRID 977 2.5 0.5 3.0 -1
GRID 978 2.0 0.5 3.0 -1
GRID 979 2.5 -6.7E-193.0 -1
GRID 980 2.0 -1.5E-193.0 -1
GRID 981 2.5 -0.5 3.0 -1
GRID 982 2.0 -0.5 3.0 -1
GRID 983 2.5 -1.0 3.0 -1
GRID 984 2.0 -1.0 3.0 -1
GRID 985 2.5 -1.5 3.0 -1
GRID 986 2.0 -1.5 3.0 -1
GRID 987 2.5 -2.0 3.0 -1
GRID 988 2.0 -2.0 3.0 -1
GRID 989 2.5 -2.5 3.0 -1
GRID 990 2.0 -2.5 3.0 -1
GRID 991 1.5 2.0 3.0 -1
GRID 992 1.5 2.5 3.0 -1
GRID 993 1.5 1.5 3.0 -1
GRID 994 1.5 1.0 3.0 -1
GRID 995 1.5 0.5 3.0 -1
GRID 996 1.5 -3.1E-203.0 -1
GRID 997 1.5 -0.5 3.0 -1
GRID 998 1.5 -1.0 3.0 -1
GRID 999 1.5 -1.5 3.0 -1
GRID 1000 1.5 -2.0 3.0 -1
GRID 1001 1.5 -2.5 3.0 -1
GRID 1002 1.0 2.0 3.0 -1
GRID 1003 1.0 2.5 3.0 -1
GRID 1004 1.0 1.5 3.0 -1
GRID 1005 1.0 1.0 3.0 -1
GRID 1006 1.0 0.5 3.0 -1
GRID 1007 1.0 -6.2E-213.0 -1
GRID 1008 1.0 -0.5 3.0 -1
GRID 1009 1.0 -1.0 3.0 -1
GRID 1010 1.0 -1.5 3.0 -1
GRID 1011 1.0 -2.0 3.0 -1
GRID 1012 1.0 -2.5 3.0 -1
GRID 1013 0.5 2.0 3.0 -1
GRID 1014 0.5 2.5 3.0 -1
GRID 1015 0.5 1.5 3.0 -1
GRID 1016 0.5 1.0 3.0 -1
GRID 1017 0.5 0.5 3.0 -1
GRID 1018 0.5 -1.2E-213.0 -1
GRID 1019 0.5 -0.5 3.0 -1
GRID 1020 0.5 -1.0 3.0 -1
GRID 1021 0.5 -1.5 3.0 -1
GRID 1022 0.5 -2.0 3.0 -1
GRID 1023 0.5 -2.5 3.0 -1
GRID 1024 1.50E-322.0 3.0 -1
GRID 1025 3.80E-332.5 3.0 -1
GRID 1026 2.67E-331.5 3.0 -1
GRID 1027 4.07E-341.0 3.0 -1
GRID 1028 6.20E-350.5 3.0 -1

488 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1029 6.35E-32-2.3E-223.0 -1
GRID 1030 1.29E-31-0.5 3.0 -1
GRID 1031 -4.0E-32-1.0 3.0 -1
GRID 1032 -5.5E-32-1.5 3.0 -1
GRID 1033 -3.2E-32-2.0 3.0 -1
GRID 1034 -4.8E-33-2.5 3.0 -1
GRID 1035 -0.5 2.0 3.0 -1
GRID 1036 -0.5 2.5 3.0 -1
GRID 1037 -0.5 1.5 3.0 -1
GRID 1038 -0.5 1.0 3.0 -1
GRID 1039 -0.5 0.5 3.0 -1
GRID 1040 -0.5 -2.2E-193.0 -1
GRID 1041 -0.5 -0.5 3.0 -1
GRID 1042 -0.5 -1.0 3.0 -1
GRID 1043 -0.5 -1.5 3.0 -1
GRID 1044 -0.5 -2.0 3.0 -1
GRID 1045 -0.5 -2.5 3.0 -1
GRID 1046 -1.0 2.0 3.0 -1
GRID 1047 -1.0 2.5 3.0 -1
GRID 1048 -1.0 1.5 3.0 -1
GRID 1049 -1.0 1.0 3.0 -1
GRID 1050 -1.0 0.5 3.0 -1
GRID 1051 -1.0 -2.6E-183.0 -1
GRID 1052 -1.0 -0.5 3.0 -1
GRID 1053 -1.0 -1.0 3.0 -1
GRID 1054 -1.0 -1.5 3.0 -1
GRID 1055 -1.0 -2.0 3.0 -1
GRID 1056 -1.0 -2.5 3.0 -1
GRID 1057 -1.5 2.0 3.0 -1
GRID 1058 -1.5 2.5 3.0 -1
GRID 1059 -1.5 1.5 3.0 -1
GRID 1060 -1.5 1.0 3.0 -1
GRID 1061 -1.5 0.5 3.0 -1
GRID 1062 -1.5 -1.5E-173.0 -1
GRID 1063 -1.5 -0.5 3.0 -1
GRID 1064 -1.5 -1.0 3.0 -1
GRID 1065 -1.5 -1.5 3.0 -1
GRID 1066 -1.5 -2.0 3.0 -1
GRID 1067 -1.5 -2.5 3.0 -1
GRID 1068 -2.0 2.0 3.0 -1
GRID 1069 -2.0 2.5 3.0 -1
GRID 1070 -2.0 1.5 3.0 -1
GRID 1071 -2.0 1.0 3.0 -1
GRID 1072 -2.0 0.5 3.0 -1
GRID 1073 -2.0 -5.3E-183.0 -1
GRID 1074 -2.0 -0.5 3.0 -1
GRID 1075 -2.0 -1.0 3.0 -1
GRID 1076 -2.0 -1.5 3.0 -1
GRID 1077 -2.0 -2.0 3.0 -1
GRID 1078 -2.0 -2.5 3.0 -1
GRID 1079 -2.5 2.0 3.0 -1
GRID 1080 -2.5 2.5 3.0 -1
GRID 1081 -2.5 1.5 3.0 -1
GRID 1082 -2.5 1.0 3.0 -1
GRID 1083 -2.5 0.5 3.0 -1
GRID 1084 -2.5 -3.3E-183.0 -1
GRID 1085 -2.5 -0.5 3.0 -1
GRID 1086 -2.5 -1.0 3.0 -1
GRID 1087 -2.5 -1.5 3.0 -1
GRID 1088 -2.5 -2.0 3.0 -1
GRID 1089 -2.5 -2.5 3.0 -1
GRID 1090 2.5 2.5 4.0 -1
GRID 1091 2.5 2.0 4.0 -1
GRID 1092 2.0 2.0 4.0 -1
GRID 1093 2.0 2.5 4.0 -1
GRID 1094 2.5 1.5 4.0 -1
GRID 1095 2.0 1.5 4.0 -1
GRID 1096 2.5 1.0 4.0 -1
GRID 1097 2.0 1.0 4.0 -1

Altair Engineering OptiStruct 13.0 Reference Guide 489

Proprietary Information of Altair Engineering


GRID 1098 2.5 0.5 4.0 -1
GRID 1099 2.0 0.5 4.0 -1
GRID 1100 2.5 -1.0E-164.0 -1
GRID 1101 2.0 -1.8E-164.0 -1
GRID 1102 2.5 -0.5 4.0 -1
GRID 1103 2.0 -0.5 4.0 -1
GRID 1104 2.5 -1.0 4.0 -1
GRID 1105 2.0 -1.0 4.0 -1
GRID 1106 2.5 -1.5 4.0 -1
GRID 1107 2.0 -1.5 4.0 -1
GRID 1108 2.5 -2.0 4.0 -1
GRID 1109 2.0 -2.0 4.0 -1
GRID 1110 2.5 -2.5 4.0 -1
GRID 1111 2.0 -2.5 4.0 -1
GRID 1112 1.5 2.0 4.0 -1
GRID 1113 1.5 2.5 4.0 -1
GRID 1114 1.5 1.5 4.0 -1
GRID 1115 1.5 1.0 4.0 -1
GRID 1116 1.5 0.5 4.0 -1
GRID 1117 1.5 -3.1E-164.0 -1
GRID 1118 1.5 -0.5 4.0 -1
GRID 1119 1.5 -1.0 4.0 -1
GRID 1120 1.5 -1.5 4.0 -1
GRID 1121 1.5 -2.0 4.0 -1
GRID 1122 1.5 -2.5 4.0 -1
GRID 1123 1.0 2.0 4.0 -1
GRID 1124 1.0 2.5 4.0 -1
GRID 1125 1.0 1.5 4.0 -1
GRID 1126 1.0 1.0 4.0 -1
GRID 1127 1.0 0.5 4.0 -1
GRID 1128 1.0 -3.6E-164.0 -1
GRID 1129 1.0 -0.5 4.0 -1
GRID 1130 1.0 -1.0 4.0 -1
GRID 1131 1.0 -1.5 4.0 -1
GRID 1132 1.0 -2.0 4.0 -1
GRID 1133 1.0 -2.5 4.0 -1
GRID 1134 0.5 2.0 4.0 -1
GRID 1135 0.5 2.5 4.0 -1
GRID 1136 0.5 1.5 4.0 -1
GRID 1137 0.5 1.0 4.0 -1
GRID 1138 0.5 0.5 4.0 -1
GRID 1139 0.5 -2.8E-164.0 -1
GRID 1140 0.5 -0.5 4.0 -1
GRID 1141 0.5 -1.0 4.0 -1
GRID 1142 0.5 -1.5 4.0 -1
GRID 1143 0.5 -2.0 4.0 -1
GRID 1144 0.5 -2.5 4.0 -1
GRID 1145 -1.7E-162.0 4.0 -1
GRID 1146 -2.3E-162.5 4.0 -1
GRID 1147 -2.7E-171.5 4.0 -1
GRID 1148 -3.0E-171.0 4.0 -1
GRID 1149 -7.0E-170.5 4.0 -1
GRID 1150 2.16E-17-1.4E-164.0 -1
GRID 1151 1.65E-16-0.5 4.0 -1
GRID 1152 3.53E-16-1.0 4.0 -1
GRID 1153 2.86E-16-1.5 4.0 -1
GRID 1154 -5.5E-17-2.0 4.0 -1
GRID 1155 -2.5E-16-2.5 4.0 -1
GRID 1156 -0.5 2.0 4.0 -1
GRID 1157 -0.5 2.5 4.0 -1
GRID 1158 -0.5 1.5 4.0 -1
GRID 1159 -0.5 1.0 4.0 -1
GRID 1160 -0.5 0.5 4.0 -1
GRID 1161 -0.5 -2.5E-174.0 -1
GRID 1162 -0.5 -0.5 4.0 -1
GRID 1163 -0.5 -1.0 4.0 -1
GRID 1164 -0.5 -1.5 4.0 -1
GRID 1165 -0.5 -2.0 4.0 -1
GRID 1166 -0.5 -2.5 4.0 -1

490 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1167 -1.0 2.0 4.0 -1
GRID 1168 -1.0 2.5 4.0 -1
GRID 1169 -1.0 1.5 4.0 -1
GRID 1170 -1.0 1.0 4.0 -1
GRID 1171 -1.0 0.5 4.0 -1
GRID 1172 -1.0 9.63E-174.0 -1
GRID 1173 -1.0 -0.5 4.0 -1
GRID 1174 -1.0 -1.0 4.0 -1
GRID 1175 -1.0 -1.5 4.0 -1
GRID 1176 -1.0 -2.0 4.0 -1
GRID 1177 -1.0 -2.5 4.0 -1
GRID 1178 -1.5 2.0 4.0 -1
GRID 1179 -1.5 2.5 4.0 -1
GRID 1180 -1.5 1.5 4.0 -1
GRID 1181 -1.5 1.0 4.0 -1
GRID 1182 -1.5 0.5 4.0 -1
GRID 1183 -1.5 2.14E-164.0 -1
GRID 1184 -1.5 -0.5 4.0 -1
GRID 1185 -1.5 -1.0 4.0 -1
GRID 1186 -1.5 -1.5 4.0 -1
GRID 1187 -1.5 -2.0 4.0 -1
GRID 1188 -1.5 -2.5 4.0 -1
GRID 1189 -2.0 2.0 4.0 -1
GRID 1190 -2.0 2.5 4.0 -1
GRID 1191 -2.0 1.5 4.0 -1
GRID 1192 -2.0 1.0 4.0 -1
GRID 1193 -2.0 0.5 4.0 -1
GRID 1194 -2.0 1.84E-164.0 -1
GRID 1195 -2.0 -0.5 4.0 -1
GRID 1196 -2.0 -1.0 4.0 -1
GRID 1197 -2.0 -1.5 4.0 -1
GRID 1198 -2.0 -2.0 4.0 -1
GRID 1199 -2.0 -2.5 4.0 -1
GRID 1200 -2.5 2.0 4.0 -1
GRID 1201 -2.5 2.5 4.0 -1
GRID 1202 -2.5 1.5 4.0 -1
GRID 1203 -2.5 1.0 4.0 -1
GRID 1204 -2.5 0.5 4.0 -1
GRID 1205 -2.5 1.10E-164.0 -1
GRID 1206 -2.5 -0.5 4.0 -1
GRID 1207 -2.5 -1.0 4.0 -1
GRID 1208 -2.5 -1.5 4.0 -1
GRID 1209 -2.5 -2.0 4.0 -1
GRID 1210 -2.5 -2.5 4.0 -1
GRID 1211 2.5 2.5 5.0 -1
GRID 1212 2.5 2.0 5.0 -1
GRID 1213 2.0 2.0 5.0 -1
GRID 1214 2.0 2.5 5.0 -1
GRID 1215 2.5 1.5 5.0 -1
GRID 1216 2.0 1.5 5.0 -1
GRID 1217 2.5 1.0 5.0 -1
GRID 1218 2.0 1.0 5.0 -1
GRID 1219 2.5 0.5 5.0 -1
GRID 1220 2.0 0.5 5.0 -1
GRID 1221 2.5 -1.8E-165.0 -1
GRID 1222 2.0 -2.4E-165.0 -1
GRID 1223 2.5 -0.5 5.0 -1
GRID 1224 2.0 -0.5 5.0 -1
GRID 1225 2.5 -1.0 5.0 -1
GRID 1226 2.0 -1.0 5.0 -1
GRID 1227 2.5 -1.5 5.0 -1
GRID 1228 2.0 -1.5 5.0 -1
GRID 1229 2.5 -2.0 5.0 -1
GRID 1230 2.0 -2.0 5.0 -1
GRID 1231 2.5 -2.5 5.0 -1
GRID 1232 2.0 -2.5 5.0 -1
GRID 1233 1.5 2.0 5.0 -1
GRID 1234 1.5 2.5 5.0 -1
GRID 1235 1.5 1.5 5.0 -1

Altair Engineering OptiStruct 13.0 Reference Guide 491

Proprietary Information of Altair Engineering


GRID 1236 1.5 1.0 5.0 -1
GRID 1237 1.5 0.5 5.0 -1
GRID 1238 1.5 -2.8E-165.0 -1
GRID 1239 1.5 -0.5 5.0 -1
GRID 1240 1.5 -1.0 5.0 -1
GRID 1241 1.5 -1.5 5.0 -1
GRID 1242 1.5 -2.0 5.0 -1
GRID 1243 1.5 -2.5 5.0 -1
GRID 1244 1.0 2.0 5.0 -1
GRID 1245 1.0 2.5 5.0 -1
GRID 1246 1.0 1.5 5.0 -1
GRID 1247 1.0 1.0 5.0 -1
GRID 1248 1.0 0.5 5.0 -1
GRID 1249 1.0 -3.0E-165.0 -1
GRID 1250 1.0 -0.5 5.0 -1
GRID 1251 1.0 -1.0 5.0 -1
GRID 1252 1.0 -1.5 5.0 -1
GRID 1253 1.0 -2.0 5.0 -1
GRID 1254 1.0 -2.5 5.0 -1
GRID 1255 0.5 2.0 5.0 -1
GRID 1256 0.5 2.5 5.0 -1
GRID 1257 0.5 1.5 5.0 -1
GRID 1258 0.5 1.0 5.0 -1
GRID 1259 0.5 0.5 5.0 -1
GRID 1260 0.5 -2.4E-165.0 -1
GRID 1261 0.5 -0.5 5.0 -1
GRID 1262 0.5 -1.0 5.0 -1
GRID 1263 0.5 -1.5 5.0 -1
GRID 1264 0.5 -2.0 5.0 -1
GRID 1265 0.5 -2.5 5.0 -1
GRID 1266 -2.4E-162.0 5.0 -1
GRID 1267 -2.4E-162.5 5.0 -1
GRID 1268 -1.4E-161.5 5.0 -1
GRID 1269 -1.1E-161.0 5.0 -1
GRID 1270 -6.8E-170.5 5.0 -1
GRID 1271 -2.1E-17-1.4E-165.0 -1
GRID 1272 1.13E-16-0.5 5.0 -1
GRID 1273 2.64E-16-1.0 5.0 -1
GRID 1274 2.07E-16-1.5 5.0 -1
GRID 1275 -8.9E-18-2.0 5.0 -1
GRID 1276 -1.0E-16-2.5 5.0 -1
GRID 1277 -0.5 2.0 5.0 -1
GRID 1278 -0.5 2.5 5.0 -1
GRID 1279 -0.5 1.5 5.0 -1
GRID 1280 -0.5 1.0 5.0 -1
GRID 1281 -0.5 0.5 5.0 -1
GRID 1282 -0.5 -2.9E-175.0 -1
GRID 1283 -0.5 -0.5 5.0 -1
GRID 1284 -0.5 -1.0 5.0 -1
GRID 1285 -0.5 -1.5 5.0 -1
GRID 1286 -0.5 -2.0 5.0 -1
GRID 1287 -0.5 -2.5 5.0 -1
GRID 1288 -1.0 2.0 5.0 -1
GRID 1289 -1.0 2.5 5.0 -1
GRID 1290 -1.0 1.5 5.0 -1
GRID 1291 -1.0 1.0 5.0 -1
GRID 1292 -1.0 0.5 5.0 -1
GRID 1293 -1.0 8.84E-175.0 -1
GRID 1294 -1.0 -0.5 5.0 -1
GRID 1295 -1.0 -1.0 5.0 -1
GRID 1296 -1.0 -1.5 5.0 -1
GRID 1297 -1.0 -2.0 5.0 -1
GRID 1298 -1.0 -2.5 5.0 -1
GRID 1299 -1.5 2.0 5.0 -1
GRID 1300 -1.5 2.5 5.0 -1
GRID 1301 -1.5 1.5 5.0 -1
GRID 1302 -1.5 1.0 5.0 -1
GRID 1303 -1.5 0.5 5.0 -1
GRID 1304 -1.5 1.34E-165.0 -1

492 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1305 -1.5 -0.5 5.0 -1
GRID 1306 -1.5 -1.0 5.0 -1
GRID 1307 -1.5 -1.5 5.0 -1
GRID 1308 -1.5 -2.0 5.0 -1
GRID 1309 -1.5 -2.5 5.0 -1
GRID 1310 -2.0 2.0 5.0 -1
GRID 1311 -2.0 2.5 5.0 -1
GRID 1312 -2.0 1.5 5.0 -1
GRID 1313 -2.0 1.0 5.0 -1
GRID 1314 -2.0 0.5 5.0 -1
GRID 1315 -2.0 1.09E-165.0 -1
GRID 1316 -2.0 -0.5 5.0 -1
GRID 1317 -2.0 -1.0 5.0 -1
GRID 1318 -2.0 -1.5 5.0 -1
GRID 1319 -2.0 -2.0 5.0 -1
GRID 1320 -2.0 -2.5 5.0 -1
GRID 1321 -2.5 2.0 5.0 -1
GRID 1322 -2.5 2.5 5.0 -1
GRID 1323 -2.5 1.5 5.0 -1
GRID 1324 -2.5 1.0 5.0 -1
GRID 1325 -2.5 0.5 5.0 -1
GRID 1326 -2.5 5.75E-175.0 -1
GRID 1327 -2.5 -0.5 5.0 -1
GRID 1328 -2.5 -1.0 5.0 -1
GRID 1329 -2.5 -1.5 5.0 -1
GRID 1330 -2.5 -2.0 5.0 -1
GRID 1331 -2.5 -2.5 5.0 -1
GRID 1332 2.0 2.0 0.0
GRID 1333 2.0 1.5 0.0
GRID 1334 2.0 1.0 0.0
GRID 1335 2.0 0.5 0.0
GRID 1336 2.0 -2.2E-180.0
GRID 1337 2.0 -0.5 0.0
GRID 1338 2.0 -1.0 0.0
GRID 1339 2.0 -1.5 0.0
GRID 1340 2.0 -2.0 0.0
GRID 1341 1.5 2.0 0.0
GRID 1342 1.5 1.5 0.0
GRID 1343 1.5 1.0 0.0
GRID 1344 1.5 0.5 0.0
GRID 1345 1.5 -1.9E-180.0
GRID 1346 1.5 -0.5 0.0
GRID 1347 1.5 -1.0 0.0
GRID 1348 1.5 -1.5 0.0
GRID 1349 1.5 -2.0 0.0
GRID 1350 1.0 2.0 0.0
GRID 1351 1.0 1.5 0.0
GRID 1352 1.0 1.0 0.0
GRID 1353 1.0 0.5 0.0
GRID 1354 1.0 -1.9E-180.0
GRID 1355 1.0 -0.5 0.0
GRID 1356 1.0 -1.0 0.0
GRID 1357 1.0 -1.5 0.0
GRID 1358 1.0 -2.0 0.0
GRID 1359 0.5 2.0 0.0
GRID 1360 0.5 1.5 0.0
GRID 1361 0.5 1.0 0.0
GRID 1362 0.5 0.5 0.0
GRID 1363 0.5 -1.9E-180.0
GRID 1364 0.5 -0.5 0.0
GRID 1365 0.5 -1.0 0.0
GRID 1366 0.5 -1.5 0.0
GRID 1367 0.5 -2.0 0.0
GRID 1368 -2.8E-182.0 0.0
GRID 1369 -2.8E-181.5 0.0
GRID 1370 -2.5E-181.0 0.0
GRID 1371 -2.8E-180.5 0.0
GRID 1372 -3.1E-18-1.7E-180.0
GRID 1373 -2.8E-18-0.5 0.0

Altair Engineering OptiStruct 13.0 Reference Guide 493

Proprietary Information of Altair Engineering


GRID 1374 -3.1E-18-1.0 0.0
GRID 1375 -1.9E-18-1.5 0.0
GRID 1376 -2.8E-18-2.0 0.0
GRID 1377 -0.5 2.0 0.0
GRID 1378 -0.5 1.5 0.0
GRID 1379 -0.5 1.0 0.0
GRID 1380 -0.5 0.5 0.0
GRID 1381 -0.5 -1.7E-180.0
GRID 1382 -0.5 -0.5 0.0
GRID 1383 -0.5 -1.0 0.0
GRID 1384 -0.5 -1.5 0.0
GRID 1385 -0.5 -2.0 0.0
GRID 1386 -1.0 2.0 0.0
GRID 1387 -1.0 1.5 0.0
GRID 1388 -1.0 1.0 0.0
GRID 1389 -1.0 0.5 0.0
GRID 1390 -1.0 -1.9E-180.0
GRID 1391 -1.0 -0.5 0.0
GRID 1392 -1.0 -1.0 0.0
GRID 1393 -1.0 -1.5 0.0
GRID 1394 -1.0 -2.0 0.0
GRID 1395 -1.5 2.0 0.0
GRID 1396 -1.5 1.5 0.0
GRID 1397 -1.5 1.0 0.0
GRID 1398 -1.5 0.5 0.0
GRID 1399 -1.5 -1.7E-180.0
GRID 1400 -1.5 -0.5 0.0
GRID 1401 -1.5 -1.0 0.0
GRID 1402 -1.5 -1.5 0.0
GRID 1403 -1.5 -2.0 0.0
GRID 1404 -2.0 2.0 0.0
GRID 1405 -2.0 1.5 0.0
GRID 1406 -2.0 1.0 0.0
GRID 1407 -2.0 0.5 0.0
GRID 1408 -2.0 -2.2E-180.0
GRID 1409 -2.0 -0.5 0.0
GRID 1410 -2.0 -1.0 0.0
GRID 1411 -2.0 -1.5 0.0
GRID 1412 -2.0 -2.0 0.0
GRID 1413 2.4964642.0 0.004472
GRID 1414 2.4964641.5 0.004472
GRID 1415 2.4964641.0 0.004472
GRID 1416 2.4964640.5 0.004472
GRID 1417 2.496464-2.6E-180.004472
GRID 1418 2.496464-0.5 0.004472
GRID 1419 2.496464-1.0 0.004472
GRID 1420 2.496464-1.5 0.004472
GRID 1421 2.496464-2.0 0.004472
GRID 1422 -2.496462.0 0.004472
GRID 1423 -2.496461.5 0.004472
GRID 1424 -2.496461.0 0.004472
GRID 1425 -2.496460.5 0.004472
GRID 1426 -2.49646-2.6E-180.004472
GRID 1427 -2.49646-0.5 0.004472
GRID 1428 -2.49646-1.0 0.004472
GRID 1429 -2.49646-1.5 0.004472
GRID 1430 -2.49646-2.0 0.004472
GRID 1431 2.4961522.4961520.005963
GRID 1432 2.496152-2.496150.005963
GRID 1433 2.0 2.4964640.004472
GRID 1434 2.0 -2.496460.004472
GRID 1435 1.5 2.4964640.004472
GRID 1436 1.5 -2.496460.004472
GRID 1437 1.0 2.4964640.004472
GRID 1438 1.0 -2.496460.004472
GRID 1439 0.5 2.4964640.004472
GRID 1440 0.5 -2.496460.004472
GRID 1441 -2.6E-182.4964640.004472
GRID 1442 -2.6E-18-2.496460.004472

494 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1443 -0.5 2.4964640.004472
GRID 1444 -0.5 -2.496460.004472
GRID 1445 -1.0 2.4964640.004472
GRID 1446 -1.0 -2.496460.004472
GRID 1447 -1.5 2.4964640.004472
GRID 1448 -1.5 -2.496460.004472
GRID 1449 -2.0 2.4964640.004472
GRID 1450 -2.0 -2.496460.004472
GRID 1451 -2.496152.4961520.005963
GRID 1452 -2.49615-2.496150.005963
GRID 1453 -2.49615-2.496154.994037
GRID 1454 -2.49646-2.0 4.995528
GRID 1455 -2.49646-1.5 4.995528
GRID 1456 -2.49646-1.0 4.995528
GRID 1457 -2.49646-0.5 4.995528
GRID 1458 -2.496465.58E-174.995528
GRID 1459 -2.496460.5 4.995528
GRID 1460 -2.496461.0 4.995528
GRID 1461 -2.496461.5 4.995528
GRID 1462 -2.496152.4961524.994037
GRID 1463 -2.496462.0 4.995528
GRID 1464 -2.0 -2.496464.995528
GRID 1465 -2.0 -2.0 5.0
GRID 1466 -2.0 -1.5 5.0
GRID 1467 -2.0 -1.0 5.0
GRID 1468 -2.0 -0.5 5.0
GRID 1469 -2.0 1.05E-165.0
GRID 1470 -2.0 0.5 5.0
GRID 1471 -2.0 1.0 5.0
GRID 1472 -2.0 1.5 5.0
GRID 1473 -2.0 2.4964644.995528
GRID 1474 -2.0 2.0 5.0
GRID 1475 -1.5 -2.496464.995528
GRID 1476 -1.5 -2.0 5.0
GRID 1477 -1.5 -1.5 5.0
GRID 1478 -1.5 -1.0 5.0
GRID 1479 -1.5 -0.5 5.0
GRID 1480 -1.5 1.32E-165.0
GRID 1481 -1.5 0.5 5.0
GRID 1482 -1.5 1.0 5.0
GRID 1483 -1.5 1.5 5.0
GRID 1484 -1.5 2.4964644.995528
GRID 1485 -1.5 2.0 5.0
GRID 1486 -1.0 -2.496464.995528
GRID 1487 -1.0 -2.0 5.0
GRID 1488 -1.0 -1.5 5.0
GRID 1489 -1.0 -1.0 5.0
GRID 1493 -1.0 1.0 5.0
GRID 1494 -1.0 1.5 5.0
GRID 1495 -1.0 2.4964644.995528
GRID 1496 -1.0 2.0 5.0
GRID 1497 -0.5 -2.496464.995528
GRID 1498 -0.5 -2.0 5.0
GRID 1499 -0.5 -1.5 5.0
GRID 1500 -0.5 -1.0 5.0
GRID 1504 -0.5 1.0 5.0
GRID 1505 -0.5 1.5 5.0
GRID 1506 -0.5 2.4964644.995528
GRID 1507 -0.5 2.0 5.0
GRID 1508 -1.0E-16-2.496464.995528
GRID 1509 -1.1E-17-2.0 5.0
GRID 1510 2.04E-16-1.5 5.0
GRID 1511 2.61E-16-1.0 5.0
GRID 1515 -1.2E-161.0 5.0
GRID 1516 -1.4E-161.5 5.0
GRID 1517 -2.4E-162.4964644.995528
GRID 1518 -2.4E-162.0 5.0
GRID 1519 0.5 -2.496464.995528
GRID 1520 0.5 -2.0 5.0

Altair Engineering OptiStruct 13.0 Reference Guide 495

Proprietary Information of Altair Engineering


GRID 1521 0.5 -1.5 5.0
GRID 1522 0.5 -1.0 5.0
GRID 1526 0.5 1.0 5.0
GRID 1527 0.5 1.5 5.0
GRID 1528 0.5 2.4964644.995528
GRID 1529 0.5 2.0 5.0
GRID 1530 1.0 -2.496464.995528
GRID 1531 1.0 -2.0 5.0
GRID 1532 1.0 -1.5 5.0
GRID 1533 1.0 -1.0 5.0
GRID 1534 1.0 -0.5 5.0
GRID 1535 1.0 -3.0E-165.0
GRID 1536 1.0 0.5 5.0
GRID 1537 1.0 1.0 5.0
GRID 1538 1.0 1.5 5.0
GRID 1539 1.0 2.4964644.995528
GRID 1540 1.0 2.0 5.0
GRID 1541 1.5 -2.496464.995528
GRID 1542 1.5 -2.0 5.0
GRID 1543 1.5 -1.5 5.0
GRID 1544 1.5 -1.0 5.0
GRID 1545 1.5 -0.5 5.0
GRID 1546 1.5 -2.8E-165.0
GRID 1547 1.5 0.5 5.0
GRID 1548 1.5 1.0 5.0
GRID 1549 1.5 1.5 5.0
GRID 1550 1.5 2.4964644.995528
GRID 1551 1.5 2.0 5.0
GRID 1552 2.0 -2.496464.995528
GRID 1553 2.496152-2.496154.994037
GRID 1554 2.0 -2.0 5.0
GRID 1555 2.496464-2.0 4.995528
GRID 1556 2.0 -1.5 5.0
GRID 1557 2.496464-1.5 4.995528
GRID 1558 2.0 -1.0 5.0
GRID 1559 2.496464-1.0 4.995528
GRID 1560 2.0 -0.5 5.0
GRID 1561 2.496464-0.5 4.995528
GRID 1562 2.0 -2.4E-165.0
GRID 1563 2.496464-1.8E-164.995528
GRID 1564 2.0 0.5 5.0
GRID 1565 2.4964640.5 4.995528
GRID 1566 2.0 1.0 5.0
GRID 1567 2.4964641.0 4.995528
GRID 1568 2.0 1.5 5.0
GRID 1569 2.4964641.5 4.995528
GRID 1570 2.0 2.4964644.995528
GRID 1571 2.0 2.0 5.0
GRID 1572 2.4964642.0 4.995528
GRID 1573 2.4961522.4961524.994037
GRID 1574 -2.49776-2.497764.0
GRID 1575 -2.5 -2.0 4.0
GRID 1576 -2.5 -1.5 4.0
GRID 1577 -2.5 -1.0 4.0
GRID 1578 -2.5 -0.5 4.0
GRID 1579 -2.5 1.07E-164.0
GRID 1580 -2.5 0.5 4.0
GRID 1581 -2.5 1.0 4.0
GRID 1582 -2.5 1.5 4.0
GRID 1583 -2.497762.4977644.0
GRID 1584 -2.5 2.0 4.0
GRID 1585 -2.0 -2.5 4.0
GRID 1586 -2.0 2.5 4.0
GRID 1587 -1.5 -2.5 4.0
GRID 1588 -1.5 2.5 4.0
GRID 1589 -1.0 -2.5 4.0
GRID 1590 -1.0 2.5 4.0
GRID 1591 -0.5 -2.5 4.0
GRID 1592 -0.5 2.5 4.0

496 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1593 -2.5E-16-2.5 4.0
GRID 1594 -2.3E-162.5 4.0
GRID 1595 0.5 -2.5 4.0
GRID 1596 0.5 2.5 4.0
GRID 1597 1.0 -2.5 4.0
GRID 1598 1.0 2.5 4.0
GRID 1599 1.5 -2.5 4.0
GRID 1600 1.5 2.5 4.0
GRID 1601 2.0 -2.5 4.0
GRID 1602 2.497764-2.497764.0
GRID 1603 2.5 -2.0 4.0
GRID 1604 2.5 -1.5 4.0
GRID 1605 2.5 -1.0 4.0
GRID 1606 2.5 -0.5 4.0
GRID 1607 2.5 -1.0E-164.0
GRID 1608 2.5 0.5 4.0
GRID 1609 2.5 1.0 4.0
GRID 1610 2.5 1.5 4.0
GRID 1611 2.0 2.5 4.0
GRID 1612 2.5 2.0 4.0
GRID 1613 2.4977642.4977644.0
GRID 1614 -2.49776-2.497763.0
GRID 1615 -2.5 -2.0 3.0
GRID 1616 -2.5 -1.5 3.0
GRID 1617 -2.5 -1.0 3.0
GRID 1618 -2.5 -0.5 3.0
GRID 1619 -2.5 -5.4E-183.0
GRID 1620 -2.5 0.5 3.0
GRID 1621 -2.5 1.0 3.0
GRID 1622 -2.5 1.5 3.0
GRID 1623 -2.497762.4977643.0
GRID 1624 -2.5 2.0 3.0
GRID 1625 -2.0 -2.5 3.0
GRID 1626 -2.0 2.5 3.0
GRID 1627 -1.5 -2.5 3.0
GRID 1628 -1.5 2.5 3.0
GRID 1629 -1.0 -2.5 3.0
GRID 1630 -1.0 2.5 3.0
GRID 1631 -0.5 -2.5 3.0
GRID 1632 -0.5 2.5 3.0
GRID 1633 -2.9E-18-2.5 3.0
GRID 1634 -3.1E-182.5 3.0
GRID 1635 0.5 -2.5 3.0
GRID 1636 0.5 2.5 3.0
GRID 1637 1.0 -2.5 3.0
GRID 1638 1.0 2.5 3.0
GRID 1639 1.5 -2.5 3.0
GRID 1640 1.5 2.5 3.0
GRID 1641 2.0 -2.5 3.0
GRID 1642 2.497764-2.497763.0
GRID 1643 2.5 -2.0 3.0
GRID 1644 2.5 -1.5 3.0
GRID 1645 2.5 -1.0 3.0
GRID 1646 2.5 -0.5 3.0
GRID 1647 2.5 -3.4E-183.0
GRID 1648 2.5 0.5 3.0
GRID 1649 2.5 1.0 3.0
GRID 1650 2.5 1.5 3.0
GRID 1651 2.0 2.5 3.0
GRID 1652 2.5 2.0 3.0
GRID 1653 2.4977642.4977643.0
GRID 1654 -2.49776-2.497762.0
GRID 1655 -2.5 -2.0 2.0
GRID 1656 -2.5 -1.5 2.0
GRID 1657 -2.5 -1.0 2.0
GRID 1658 -2.5 -0.5 2.0
GRID 1659 -2.5 -5.0E-182.0
GRID 1660 -2.5 0.5 2.0
GRID 1661 -2.5 1.0 2.0

Altair Engineering OptiStruct 13.0 Reference Guide 497

Proprietary Information of Altair Engineering


GRID 1662 -2.5 1.5 2.0
GRID 1663 -2.497762.4977642.0
GRID 1664 -2.5 2.0 2.0
GRID 1665 -2.0 -2.5 2.0
GRID 1666 -2.0 2.5 2.0
GRID 1667 -1.5 -2.5 2.0
GRID 1668 -1.5 2.5 2.0
GRID 1669 -1.0 -2.5 2.0
GRID 1670 -1.0 2.5 2.0
GRID 1671 -0.5 -2.5 2.0
GRID 1672 -0.5 2.5 2.0
GRID 1673 -2.5E-18-2.5 2.0
GRID 1674 -2.5E-182.5 2.0
GRID 1675 0.5 -2.5 2.0
GRID 1676 0.5 2.5 2.0
GRID 1677 1.0 -2.5 2.0
GRID 1678 1.0 2.5 2.0
GRID 1679 1.5 -2.5 2.0
GRID 1680 1.5 2.5 2.0
GRID 1681 2.0 -2.5 2.0
GRID 1682 2.497764-2.497762.0
GRID 1683 2.5 -2.0 2.0
GRID 1684 2.5 -1.5 2.0
GRID 1685 2.5 -1.0 2.0
GRID 1686 2.5 -0.5 2.0
GRID 1687 2.5 -3.1E-182.0
GRID 1688 2.5 0.5 2.0
GRID 1689 2.5 1.0 2.0
GRID 1690 2.5 1.5 2.0
GRID 1691 2.0 2.5 2.0
GRID 1692 2.5 2.0 2.0
GRID 1693 2.4977642.4977642.0
GRID 1694 -2.49776-2.497761.0
GRID 1695 -2.5 -2.0 1.0
GRID 1696 -2.5 -1.5 1.0
GRID 1697 -2.5 -1.0 1.0
GRID 1698 -2.5 -0.5 1.0
GRID 1699 -2.5 -3.5E-181.0
GRID 1700 -2.5 0.5 1.0
GRID 1701 -2.5 1.0 1.0
GRID 1702 -2.5 1.5 1.0
GRID 1703 -2.497762.4977641.0
GRID 1704 -2.5 2.0 1.0
GRID 1705 -2.0 -2.5 1.0
GRID 1706 -2.0 2.5 1.0
GRID 1707 -1.5 -2.5 1.0
GRID 1708 -1.5 2.5 1.0
GRID 1709 -1.0 -2.5 1.0
GRID 1710 -1.0 2.5 1.0
GRID 1711 -0.5 -2.5 1.0
GRID 1712 -0.5 2.5 1.0
GRID 1713 -2.5E-18-2.5 1.0
GRID 1714 -2.5E-182.5 1.0
GRID 1715 0.5 -2.5 1.0
GRID 1716 0.5 2.5 1.0
GRID 1717 1.0 -2.5 1.0
GRID 1718 1.0 2.5 1.0
GRID 1719 1.5 -2.5 1.0
GRID 1720 1.5 2.5 1.0
GRID 1721 2.0 -2.5 1.0
GRID 1722 2.497764-2.497761.0
GRID 1723 2.5 -2.0 1.0
GRID 1724 2.5 -1.5 1.0
GRID 1725 2.5 -1.0 1.0
GRID 1726 2.5 -0.5 1.0
GRID 1727 2.5 -2.9E-181.0
GRID 1728 2.5 0.5 1.0
GRID 1729 2.5 1.0 1.0
GRID 1730 2.5 1.5 1.0

498 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1731 2.0 2.5 1.0
GRID 1732 2.5 2.0 1.0
GRID 1733 2.4977642.4977641.0
GRID 1734 -0.25 3.33E-165.0
$$
$$ SPOINT Data
$$
$$
$$------------------------------------------------------------------------------$
$$ Group Definitions $
$$------------------------------------------------------------------------------$
$$
$$ RBE2 Elements - Multiple dependent nodes
$$
RBE2 1553 1734 123456 1478 1479 1480 1481 1482+
+ 1489 1493 1500 1504 1511 1515 1522 1526+
+ 1533 1534 1535 1536 1537
$
$HMMOVE 6
$ 1553
$
$ CQUAD4 Elements
$
CQUAD4 1101 4 1332 1341 1342 1333
CQUAD4 1102 4 1333 1342 1343 1334
CQUAD4 1103 4 1334 1343 1344 1335
CQUAD4 1104 4 1335 1344 1345 1336
CQUAD4 1105 4 1336 1345 1346 1337
CQUAD4 1106 4 1337 1346 1347 1338
CQUAD4 1107 4 1338 1347 1348 1339
CQUAD4 1108 4 1339 1348 1349 1340
CQUAD4 1109 4 1341 1350 1351 1342
CQUAD4 1110 4 1342 1351 1352 1343
CQUAD4 1111 4 1343 1352 1353 1344
CQUAD4 1112 4 1344 1353 1354 1345
CQUAD4 1113 4 1345 1354 1355 1346
CQUAD4 1114 4 1346 1355 1356 1347
CQUAD4 1115 4 1347 1356 1357 1348
CQUAD4 1116 4 1348 1357 1358 1349
CQUAD4 1117 4 1350 1359 1360 1351
CQUAD4 1118 4 1351 1360 1361 1352
CQUAD4 1119 4 1352 1361 1362 1353
CQUAD4 1120 4 1353 1362 1363 1354
CQUAD4 1121 4 1354 1363 1364 1355
CQUAD4 1122 4 1355 1364 1365 1356
CQUAD4 1123 4 1356 1365 1366 1357
CQUAD4 1124 4 1357 1366 1367 1358
CQUAD4 1125 4 1359 1368 1369 1360
CQUAD4 1126 4 1360 1369 1370 1361
CQUAD4 1127 4 1361 1370 1371 1362
CQUAD4 1128 4 1362 1371 1372 1363
CQUAD4 1129 4 1363 1372 1373 1364
CQUAD4 1130 4 1364 1373 1374 1365
CQUAD4 1131 4 1365 1374 1375 1366
CQUAD4 1132 4 1366 1375 1376 1367
CQUAD4 1133 4 1368 1377 1378 1369
CQUAD4 1134 4 1369 1378 1379 1370
CQUAD4 1135 4 1370 1379 1380 1371
CQUAD4 1136 4 1371 1380 1381 1372
CQUAD4 1137 4 1372 1381 1382 1373
CQUAD4 1138 4 1373 1382 1383 1374
CQUAD4 1139 4 1374 1383 1384 1375
CQUAD4 1140 4 1375 1384 1385 1376
CQUAD4 1141 4 1377 1386 1387 1378
CQUAD4 1142 4 1378 1387 1388 1379
CQUAD4 1143 4 1379 1388 1389 1380
CQUAD4 1144 4 1380 1389 1390 1381
CQUAD4 1145 4 1381 1390 1391 1382
CQUAD4 1146 4 1382 1391 1392 1383

Altair Engineering OptiStruct 13.0 Reference Guide 499

Proprietary Information of Altair Engineering


CQUAD4 1147 4 1383 1392 1393 1384
CQUAD4 1148 4 1384 1393 1394 1385
CQUAD4 1149 4 1386 1395 1396 1387
CQUAD4 1150 4 1387 1396 1397 1388
CQUAD4 1151 4 1388 1397 1398 1389
CQUAD4 1152 4 1389 1398 1399 1390
CQUAD4 1153 4 1390 1399 1400 1391
CQUAD4 1154 4 1391 1400 1401 1392
CQUAD4 1155 4 1392 1401 1402 1393
CQUAD4 1156 4 1393 1402 1403 1394
CQUAD4 1157 4 1395 1404 1405 1396
CQUAD4 1158 4 1396 1405 1406 1397
CQUAD4 1159 4 1397 1406 1407 1398
CQUAD4 1160 4 1398 1407 1408 1399
CQUAD4 1161 4 1399 1408 1409 1400
CQUAD4 1162 4 1400 1409 1410 1401
CQUAD4 1163 4 1401 1410 1411 1402
CQUAD4 1164 4 1402 1411 1412 1403
CQUAD4 1165 4 1413 1332 1333 1414
CQUAD4 1166 4 1414 1333 1334 1415
CQUAD4 1167 4 1415 1334 1335 1416
CQUAD4 1168 4 1416 1335 1336 1417
CQUAD4 1169 4 1417 1336 1337 1418
CQUAD4 1170 4 1418 1337 1338 1419
CQUAD4 1171 4 1419 1338 1339 1420
CQUAD4 1172 4 1420 1339 1340 1421
CQUAD4 1173 4 1404 1422 1423 1405
CQUAD4 1174 4 1405 1423 1424 1406
CQUAD4 1175 4 1406 1424 1425 1407
CQUAD4 1176 4 1407 1425 1426 1408
CQUAD4 1177 4 1408 1426 1427 1409
CQUAD4 1178 4 1409 1427 1428 1410
CQUAD4 1179 4 1410 1428 1429 1411
CQUAD4 1180 4 1411 1429 1430 1412
CQUAD4 1181 4 1431 1433 1332 1413
CQUAD4 1182 4 1433 1435 1341 1332
CQUAD4 1183 4 1421 1340 1434 1432
CQUAD4 1184 4 1340 1349 1436 1434
CQUAD4 1185 4 1435 1437 1350 1341
CQUAD4 1186 4 1349 1358 1438 1436
CQUAD4 1187 4 1437 1439 1359 1350
CQUAD4 1188 4 1358 1367 1440 1438
CQUAD4 1189 4 1439 1441 1368 1359
CQUAD4 1190 4 1367 1376 1442 1440
CQUAD4 1191 4 1441 1443 1377 1368
CQUAD4 1192 4 1376 1385 1444 1442
CQUAD4 1193 4 1443 1445 1386 1377
CQUAD4 1194 4 1385 1394 1446 1444
CQUAD4 1195 4 1445 1447 1395 1386
CQUAD4 1196 4 1394 1403 1448 1446
CQUAD4 1197 4 1447 1449 1404 1395
CQUAD4 1198 4 1403 1412 1450 1448
CQUAD4 1199 4 1449 1451 1422 1404
CQUAD4 1200 4 1412 1430 1452 1450
CQUAD4 1201 4 1431 1733 1731 1433
CQUAD4 1202 4 1413 1732 1733 1431
CQUAD4 1203 4 1414 1730 1732 1413
CQUAD4 1204 4 1433 1731 1720 1435
CQUAD4 1205 4 1415 1729 1730 1414
CQUAD4 1206 4 1416 1728 1729 1415
CQUAD4 1207 4 1417 1727 1728 1416
CQUAD4 1208 4 1418 1726 1727 1417
CQUAD4 1209 4 1419 1725 1726 1418
CQUAD4 1210 4 1420 1724 1725 1419
CQUAD4 1211 4 1421 1723 1724 1420
CQUAD4 1212 4 1432 1722 1723 1421
CQUAD4 1213 4 1434 1721 1722 1432
CQUAD4 1214 4 1436 1719 1721 1434
CQUAD4 1215 4 1435 1720 1718 1437

500 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CQUAD4 1216 4 1438 1717 1719 1436
CQUAD4 1217 4 1437 1718 1716 1439
CQUAD4 1218 4 1440 1715 1717 1438
CQUAD4 1219 4 1439 1716 1714 1441
CQUAD4 1220 4 1442 1713 1715 1440
CQUAD4 1221 4 1441 1714 1712 1443
CQUAD4 1222 4 1444 1711 1713 1442
CQUAD4 1223 4 1443 1712 1710 1445
CQUAD4 1224 4 1446 1709 1711 1444
CQUAD4 1225 4 1445 1710 1708 1447
CQUAD4 1226 4 1448 1707 1709 1446
CQUAD4 1227 4 1447 1708 1706 1449
CQUAD4 1228 4 1450 1705 1707 1448
CQUAD4 1229 4 1449 1706 1703 1451
CQUAD4 1230 4 1452 1694 1705 1450
CQUAD4 1231 4 1451 1703 1704 1422
CQUAD4 1232 4 1422 1704 1702 1423
CQUAD4 1233 4 1423 1702 1701 1424
CQUAD4 1234 4 1424 1701 1700 1425
CQUAD4 1235 4 1425 1700 1699 1426
CQUAD4 1236 4 1426 1699 1698 1427
CQUAD4 1237 4 1427 1698 1697 1428
CQUAD4 1238 4 1428 1697 1696 1429
CQUAD4 1239 4 1429 1696 1695 1430
CQUAD4 1240 4 1430 1695 1694 1452
CQUAD4 1241 4 1732 1692 1693 1733
CQUAD4 1242 4 1733 1693 1691 1731
CQUAD4 1243 4 1730 1690 1692 1732
CQUAD4 1244 4 1731 1691 1680 1720
CQUAD4 1245 4 1729 1689 1690 1730
CQUAD4 1246 4 1728 1688 1689 1729
CQUAD4 1247 4 1727 1687 1688 1728
CQUAD4 1248 4 1726 1686 1687 1727
CQUAD4 1249 4 1725 1685 1686 1726
CQUAD4 1250 4 1724 1684 1685 1725
CQUAD4 1251 4 1723 1683 1684 1724
CQUAD4 1252 4 1722 1682 1683 1723
CQUAD4 1253 4 1721 1681 1682 1722
CQUAD4 1254 4 1719 1679 1681 1721
CQUAD4 1255 4 1720 1680 1678 1718
CQUAD4 1256 4 1717 1677 1679 1719
CQUAD4 1257 4 1718 1678 1676 1716
CQUAD4 1258 4 1715 1675 1677 1717
CQUAD4 1259 4 1716 1676 1674 1714
CQUAD4 1260 4 1713 1673 1675 1715
CQUAD4 1261 4 1714 1674 1672 1712
CQUAD4 1262 4 1711 1671 1673 1713
CQUAD4 1263 4 1712 1672 1670 1710
CQUAD4 1264 4 1709 1669 1671 1711
CQUAD4 1265 4 1710 1670 1668 1708
CQUAD4 1266 4 1707 1667 1669 1709
CQUAD4 1267 4 1708 1668 1666 1706
CQUAD4 1268 4 1705 1665 1667 1707
CQUAD4 1269 4 1706 1666 1663 1703
CQUAD4 1270 4 1694 1654 1665 1705
CQUAD4 1271 4 1703 1663 1664 1704
CQUAD4 1272 4 1704 1664 1662 1702
CQUAD4 1273 4 1702 1662 1661 1701
CQUAD4 1274 4 1701 1661 1660 1700
CQUAD4 1275 4 1700 1660 1659 1699
CQUAD4 1276 4 1699 1659 1658 1698
CQUAD4 1277 4 1698 1658 1657 1697
CQUAD4 1278 4 1697 1657 1656 1696
CQUAD4 1279 4 1696 1656 1655 1695
CQUAD4 1280 4 1695 1655 1654 1694
CQUAD4 1281 4 1692 1652 1653 1693
CQUAD4 1282 4 1693 1653 1651 1691
CQUAD4 1283 4 1690 1650 1652 1692
CQUAD4 1284 4 1691 1651 1640 1680

Altair Engineering OptiStruct 13.0 Reference Guide 501

Proprietary Information of Altair Engineering


CQUAD4 1285 4 1689 1649 1650 1690
CQUAD4 1286 4 1688 1648 1649 1689
CQUAD4 1287 4 1687 1647 1648 1688
CQUAD4 1288 4 1686 1646 1647 1687
CQUAD4 1289 4 1685 1645 1646 1686
CQUAD4 1290 4 1684 1644 1645 1685
CQUAD4 1291 4 1683 1643 1644 1684
CQUAD4 1292 4 1682 1642 1643 1683
CQUAD4 1293 4 1681 1641 1642 1682
CQUAD4 1294 4 1679 1639 1641 1681
CQUAD4 1295 4 1680 1640 1638 1678
CQUAD4 1296 4 1677 1637 1639 1679
CQUAD4 1297 4 1678 1638 1636 1676
CQUAD4 1298 4 1675 1635 1637 1677
CQUAD4 1299 4 1676 1636 1634 1674
CQUAD4 1300 4 1673 1633 1635 1675
CQUAD4 1301 4 1674 1634 1632 1672
CQUAD4 1302 4 1671 1631 1633 1673
CQUAD4 1303 4 1672 1632 1630 1670
CQUAD4 1304 4 1669 1629 1631 1671
CQUAD4 1305 4 1670 1630 1628 1668
CQUAD4 1306 4 1667 1627 1629 1669
CQUAD4 1307 4 1668 1628 1626 1666
CQUAD4 1308 4 1665 1625 1627 1667
CQUAD4 1309 4 1666 1626 1623 1663
CQUAD4 1310 4 1654 1614 1625 1665
CQUAD4 1311 4 1663 1623 1624 1664
CQUAD4 1312 4 1664 1624 1622 1662
CQUAD4 1313 4 1662 1622 1621 1661
CQUAD4 1314 4 1661 1621 1620 1660
CQUAD4 1315 4 1660 1620 1619 1659
CQUAD4 1316 4 1659 1619 1618 1658
CQUAD4 1317 4 1658 1618 1617 1657
CQUAD4 1318 4 1657 1617 1616 1656
CQUAD4 1319 4 1656 1616 1615 1655
CQUAD4 1320 4 1655 1615 1614 1654
CQUAD4 1321 4 1652 1612 1613 1653
CQUAD4 1322 4 1653 1613 1611 1651
CQUAD4 1323 4 1650 1610 1612 1652
CQUAD4 1324 4 1651 1611 1600 1640
CQUAD4 1325 4 1649 1609 1610 1650
CQUAD4 1326 4 1648 1608 1609 1649
CQUAD4 1327 4 1647 1607 1608 1648
CQUAD4 1328 4 1646 1606 1607 1647
CQUAD4 1329 4 1645 1605 1606 1646
CQUAD4 1330 4 1644 1604 1605 1645
CQUAD4 1331 4 1643 1603 1604 1644
CQUAD4 1332 4 1642 1602 1603 1643
CQUAD4 1333 4 1641 1601 1602 1642
CQUAD4 1334 4 1639 1599 1601 1641
CQUAD4 1335 4 1640 1600 1598 1638
CQUAD4 1336 4 1637 1597 1599 1639
CQUAD4 1337 4 1638 1598 1596 1636
CQUAD4 1338 4 1635 1595 1597 1637
CQUAD4 1339 4 1636 1596 1594 1634
CQUAD4 1340 4 1633 1593 1595 1635
CQUAD4 1341 4 1634 1594 1592 1632
CQUAD4 1342 4 1631 1591 1593 1633
CQUAD4 1343 4 1632 1592 1590 1630
CQUAD4 1344 4 1629 1589 1591 1631
CQUAD4 1345 4 1630 1590 1588 1628
CQUAD4 1346 4 1627 1587 1589 1629
CQUAD4 1347 4 1628 1588 1586 1626
CQUAD4 1348 4 1625 1585 1587 1627
CQUAD4 1349 4 1626 1586 1583 1623
CQUAD4 1350 4 1614 1574 1585 1625
CQUAD4 1351 4 1623 1583 1584 1624
CQUAD4 1352 4 1624 1584 1582 1622
CQUAD4 1353 4 1622 1582 1581 1621

502 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CQUAD4 1354 4 1621 1581 1580 1620
CQUAD4 1355 4 1620 1580 1579 1619
CQUAD4 1356 4 1619 1579 1578 1618
CQUAD4 1357 4 1618 1578 1577 1617
CQUAD4 1358 4 1617 1577 1576 1616
CQUAD4 1359 4 1616 1576 1575 1615
CQUAD4 1360 4 1615 1575 1574 1614
CQUAD4 1361 4 1612 1572 1573 1613
CQUAD4 1362 4 1613 1573 1570 1611
CQUAD4 1363 4 1610 1569 1572 1612
CQUAD4 1364 4 1572 1571 1570 1573
CQUAD4 1365 4 1611 1570 1550 1600
CQUAD4 1366 4 1569 1568 1571 1572
CQUAD4 1367 4 1609 1567 1569 1610
CQUAD4 1368 4 1567 1566 1568 1569
CQUAD4 1369 4 1608 1565 1567 1609
CQUAD4 1370 4 1565 1564 1566 1567
CQUAD4 1371 4 1607 1563 1565 1608
CQUAD4 1372 4 1563 1562 1564 1565
CQUAD4 1373 4 1606 1561 1563 1607
CQUAD4 1374 4 1561 1560 1562 1563
CQUAD4 1375 4 1605 1559 1561 1606
CQUAD4 1376 4 1559 1558 1560 1561
CQUAD4 1377 4 1604 1557 1559 1605
CQUAD4 1378 4 1557 1556 1558 1559
CQUAD4 1379 4 1603 1555 1557 1604
CQUAD4 1380 4 1555 1554 1556 1557
CQUAD4 1381 4 1602 1553 1555 1603
CQUAD4 1382 4 1601 1552 1553 1602
CQUAD4 1383 4 1553 1552 1554 1555
CQUAD4 1384 4 1599 1541 1552 1601
CQUAD4 1385 4 1571 1551 1550 1570
CQUAD4 1386 4 1568 1549 1551 1571
CQUAD4 1387 4 1600 1550 1539 1598
CQUAD4 1388 4 1566 1548 1549 1568
CQUAD4 1389 4 1564 1547 1548 1566
CQUAD4 1390 4 1562 1546 1547 1564
CQUAD4 1391 4 1560 1545 1546 1562
CQUAD4 1392 4 1558 1544 1545 1560
CQUAD4 1393 4 1556 1543 1544 1558
CQUAD4 1394 4 1554 1542 1543 1556
CQUAD4 1395 4 1552 1541 1542 1554
CQUAD4 1396 4 1597 1530 1541 1599
CQUAD4 1397 4 1551 1540 1539 1550
CQUAD4 1398 4 1549 1538 1540 1551
CQUAD4 1399 4 1598 1539 1528 1596
CQUAD4 1400 4 1548 1537 1538 1549
CQUAD4 1401 4 1547 1536 1537 1548
CQUAD4 1402 4 1546 1535 1536 1547
CQUAD4 1403 4 1545 1534 1535 1546
CQUAD4 1404 4 1544 1533 1534 1545
CQUAD4 1405 4 1543 1532 1533 1544
CQUAD4 1406 4 1542 1531 1532 1543
CQUAD4 1407 4 1541 1530 1531 1542
CQUAD4 1408 4 1595 1519 1530 1597
CQUAD4 1409 4 1540 1529 1528 1539
CQUAD4 1410 4 1538 1527 1529 1540
CQUAD4 1411 4 1596 1528 1517 1594
CQUAD4 1412 4 1537 1526 1527 1538
CQUAD4 1417 4 1532 1521 1522 1533
CQUAD4 1418 4 1531 1520 1521 1532
CQUAD4 1419 4 1530 1519 1520 1531
CQUAD4 1420 4 1593 1508 1519 1595
CQUAD4 1421 4 1529 1518 1517 1528
CQUAD4 1422 4 1527 1516 1518 1529
CQUAD4 1423 4 1594 1517 1506 1592
CQUAD4 1424 4 1526 1515 1516 1527
CQUAD4 1429 4 1521 1510 1511 1522
CQUAD4 1430 4 1520 1509 1510 1521

Altair Engineering OptiStruct 13.0 Reference Guide 503

Proprietary Information of Altair Engineering


CQUAD4 1431 4 1519 1508 1509 1520
CQUAD4 1432 4 1591 1497 1508 1593
CQUAD4 1433 4 1518 1507 1506 1517
CQUAD4 1434 4 1516 1505 1507 1518
CQUAD4 1435 4 1592 1506 1495 1590
CQUAD4 1436 4 1515 1504 1505 1516
CQUAD4 1441 4 1510 1499 1500 1511
CQUAD4 1442 4 1509 1498 1499 1510
CQUAD4 1443 4 1508 1497 1498 1509
CQUAD4 1444 4 1589 1486 1497 1591
CQUAD4 1445 4 1507 1496 1495 1506
CQUAD4 1446 4 1505 1494 1496 1507
CQUAD4 1447 4 1590 1495 1484 1588
CQUAD4 1448 4 1504 1493 1494 1505
CQUAD4 1453 4 1499 1488 1489 1500
CQUAD4 1454 4 1498 1487 1488 1499
CQUAD4 1455 4 1497 1486 1487 1498
CQUAD4 1456 4 1587 1475 1486 1589
CQUAD4 1457 4 1496 1485 1484 1495
CQUAD4 1458 4 1494 1483 1485 1496
CQUAD4 1459 4 1588 1484 1473 1586
CQUAD4 1460 4 1493 1482 1483 1494
CQUAD4 1465 4 1488 1477 1478 1489
CQUAD4 1466 4 1487 1476 1477 1488
CQUAD4 1467 4 1486 1475 1476 1487
CQUAD4 1468 4 1585 1464 1475 1587
CQUAD4 1469 4 1485 1474 1473 1484
CQUAD4 1470 4 1483 1472 1474 1485
CQUAD4 1471 4 1586 1473 1462 1583
CQUAD4 1472 4 1482 1471 1472 1483
CQUAD4 1473 4 1481 1470 1471 1482
CQUAD4 1474 4 1480 1469 1470 1481
CQUAD4 1475 4 1479 1468 1469 1480
CQUAD4 1476 4 1478 1467 1468 1479
CQUAD4 1477 4 1477 1466 1467 1478
CQUAD4 1478 4 1476 1465 1466 1477
CQUAD4 1479 4 1475 1464 1465 1476
CQUAD4 1480 4 1574 1453 1464 1585
CQUAD4 1481 4 1583 1462 1463 1584
CQUAD4 1482 4 1474 1463 1462 1473
CQUAD4 1483 4 1584 1463 1461 1582
CQUAD4 1484 4 1472 1461 1463 1474
CQUAD4 1485 4 1582 1461 1460 1581
CQUAD4 1486 4 1471 1460 1461 1472
CQUAD4 1487 4 1581 1460 1459 1580
CQUAD4 1488 4 1470 1459 1460 1471
CQUAD4 1489 4 1580 1459 1458 1579
CQUAD4 1490 4 1469 1458 1459 1470
CQUAD4 1491 4 1579 1458 1457 1578
CQUAD4 1492 4 1468 1457 1458 1469
CQUAD4 1493 4 1578 1457 1456 1577
CQUAD4 1494 4 1467 1456 1457 1468
CQUAD4 1495 4 1577 1456 1455 1576
CQUAD4 1496 4 1466 1455 1456 1467
CQUAD4 1497 4 1576 1455 1454 1575
CQUAD4 1498 4 1465 1454 1455 1466
CQUAD4 1499 4 1575 1454 1453 1574
CQUAD4 1500 4 1464 1453 1454 1465
$
$ CHEXA Elements: First Order
$
CHEXA 601 1 100 102 1 82 727 730+
+ 729 728
CHEXA 602 1 82 1 2 83 728 729+
+ 732 731
CHEXA 603 1 83 2 3 84 731 732+
+ 734 733
CHEXA 604 1 84 3 4 85 733 734+
+ 736 735

504 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 605 1 85 4 5 86 735 736+
+ 738 737
CHEXA 606 1 86 5 6 87 737 738+
+ 740 739
CHEXA 607 1 87 6 7 88 739 740+
+ 742 741
CHEXA 608 1 88 7 8 89 741 742+
+ 744 743
CHEXA 609 1 89 8 9 90 743 744+
+ 746 745
CHEXA 610 1 90 9 103 101 745 746+
+ 748 747
CHEXA 611 1 102 104 10 1 730 750+
+ 749 729
CHEXA 612 1 1 10 11 2 729 749+
+ 751 732
CHEXA 613 1 2 11 12 3 732 751+
+ 752 734
CHEXA 614 1 3 12 13 4 734 752+
+ 753 736
CHEXA 615 1 4 13 14 5 736 753+
+ 754 738
CHEXA 616 1 5 14 15 6 738 754+
+ 755 740
CHEXA 617 1 6 15 16 7 740 755+
+ 756 742
CHEXA 618 1 7 16 17 8 742 756+
+ 757 744
CHEXA 619 1 8 17 18 9 744 757+
+ 758 746
CHEXA 620 1 9 18 105 103 746 758+
+ 759 748
CHEXA 621 1 104 106 19 10 750 761+
+ 760 749
CHEXA 622 1 10 19 20 11 749 760+
+ 762 751
CHEXA 623 1 11 20 21 12 751 762+
+ 763 752
CHEXA 624 1 12 21 22 13 752 763+
+ 764 753
CHEXA 625 1 13 22 23 14 753 764+
+ 765 754
CHEXA 626 1 14 23 24 15 754 765+
+ 766 755
CHEXA 627 1 15 24 25 16 755 766+
+ 767 756
CHEXA 628 1 16 25 26 17 756 767+
+ 768 757
CHEXA 629 1 17 26 27 18 757 768+
+ 769 758
CHEXA 630 1 18 27 107 105 758 769+
+ 770 759
CHEXA 631 1 106 108 28 19 761 772+
+ 771 760
CHEXA 632 1 19 28 29 20 760 771+
+ 773 762
CHEXA 633 1 20 29 30 21 762 773+
+ 774 763
CHEXA 634 1 21 30 31 22 763 774+
+ 775 764
CHEXA 635 1 22 31 32 23 764 775+
+ 776 765
CHEXA 636 1 23 32 33 24 765 776+
+ 777 766
CHEXA 637 1 24 33 34 25 766 777+
+ 778 767
CHEXA 638 1 25 34 35 26 767 778+
+ 779 768
CHEXA 639 1 26 35 36 27 768 779+

Altair Engineering OptiStruct 13.0 Reference Guide 505

Proprietary Information of Altair Engineering


+ 780 769
CHEXA 640 1 27 36 109 107 769 780+
+ 781 770
CHEXA 641 1 108 110 37 28 772 783+
+ 782 771
CHEXA 642 1 28 37 38 29 771 782+
+ 784 773
CHEXA 643 1 29 38 39 30 773 784+
+ 785 774
CHEXA 644 1 30 39 40 31 774 785+
+ 786 775
CHEXA 645 1 31 40 41 32 775 786+
+ 787 776
CHEXA 646 1 32 41 42 33 776 787+
+ 788 777
CHEXA 647 1 33 42 43 34 777 788+
+ 789 778
CHEXA 648 1 34 43 44 35 778 789+
+ 790 779
CHEXA 649 1 35 44 45 36 779 790+
+ 791 780
CHEXA 650 1 36 45 111 109 780 791+
+ 792 781
CHEXA 651 1 110 112 46 37 783 794+
+ 793 782
CHEXA 652 1 37 46 47 38 782 793+
+ 795 784
CHEXA 653 1 38 47 48 39 784 795+
+ 796 785
CHEXA 654 1 39 48 49 40 785 796+
+ 797 786
CHEXA 655 1 40 49 50 41 786 797+
+ 798 787
CHEXA 656 1 41 50 51 42 787 798+
+ 799 788
CHEXA 657 1 42 51 52 43 788 799+
+ 800 789
CHEXA 658 1 43 52 53 44 789 800+
+ 801 790
CHEXA 659 1 44 53 54 45 790 801+
+ 802 791
CHEXA 660 1 45 54 113 111 791 802+
+ 803 792
CHEXA 661 1 112 114 55 46 794 805+
+ 804 793
CHEXA 662 1 46 55 56 47 793 804+
+ 806 795
CHEXA 663 1 47 56 57 48 795 806+
+ 807 796
CHEXA 664 1 48 57 58 49 796 807+
+ 808 797
CHEXA 665 1 49 58 59 50 797 808+
+ 809 798
CHEXA 666 1 50 59 60 51 798 809+
+ 810 799
CHEXA 667 1 51 60 61 52 799 810+
+ 811 800
CHEXA 668 1 52 61 62 53 800 811+
+ 812 801
CHEXA 669 1 53 62 63 54 801 812+
+ 813 802
CHEXA 670 1 54 63 115 113 802 813+
+ 814 803
CHEXA 671 1 114 116 64 55 805 816+
+ 815 804
CHEXA 672 1 55 64 65 56 804 815+
+ 817 806
CHEXA 673 1 56 65 66 57 806 817+
+ 818 807

506 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 674 1 57 66 67 58 807 818+
+ 819 808
CHEXA 675 1 58 67 68 59 808 819+
+ 820 809
CHEXA 676 1 59 68 69 60 809 820+
+ 821 810
CHEXA 677 1 60 69 70 61 810 821+
+ 822 811
CHEXA 678 1 61 70 71 62 811 822+
+ 823 812
CHEXA 679 1 62 71 72 63 812 823+
+ 824 813
CHEXA 680 1 63 72 117 115 813 824+
+ 825 814
CHEXA 681 1 116 118 73 64 816 827+
+ 826 815
CHEXA 682 1 64 73 74 65 815 826+
+ 828 817
CHEXA 683 1 65 74 75 66 817 828+
+ 829 818
CHEXA 684 1 66 75 76 67 818 829+
+ 830 819
CHEXA 685 1 67 76 77 68 819 830+
+ 831 820
CHEXA 686 1 68 77 78 69 820 831+
+ 832 821
CHEXA 687 1 69 78 79 70 821 832+
+ 833 822
CHEXA 688 1 70 79 80 71 822 833+
+ 834 823
CHEXA 689 1 71 80 81 72 823 834+
+ 835 824
CHEXA 690 1 72 81 119 117 824 835+
+ 836 825
CHEXA 691 1 118 120 91 73 827 838+
+ 837 826
CHEXA 692 1 73 91 92 74 826 837+
+ 839 828
CHEXA 693 1 74 92 93 75 828 839+
+ 840 829
CHEXA 694 1 75 93 94 76 829 840+
+ 841 830
CHEXA 695 1 76 94 95 77 830 841+
+ 842 831
CHEXA 696 1 77 95 96 78 831 842+
+ 843 832
CHEXA 697 1 78 96 97 79 832 843+
+ 844 833
CHEXA 698 1 79 97 98 80 833 844+
+ 845 834
CHEXA 699 1 80 98 99 81 834 845+
+ 846 835
CHEXA 700 1 81 99 121 119 835 846+
+ 847 836
CHEXA 701 1 727 730 729 728 848 851+
+ 850 849
CHEXA 702 1 728 729 732 731 849 850+
+ 853 852
CHEXA 703 1 731 732 734 733 852 853+
+ 855 854
CHEXA 704 1 733 734 736 735 854 855+
+ 857 856
CHEXA 705 1 735 736 738 737 856 857+
+ 859 858
CHEXA 706 1 737 738 740 739 858 859+
+ 861 860
CHEXA 707 1 739 740 742 741 860 861+
+ 863 862
CHEXA 708 1 741 742 744 743 862 863+

Altair Engineering OptiStruct 13.0 Reference Guide 507

Proprietary Information of Altair Engineering


+ 865 864
CHEXA 709 1 743 744 746 745 864 865+
+ 867 866
CHEXA 710 1 745 746 748 747 866 867+
+ 869 868
CHEXA 711 1 730 750 749 729 851 871+
+ 870 850
CHEXA 712 1 729 749 751 732 850 870+
+ 872 853
CHEXA 713 1 732 751 752 734 853 872+
+ 873 855
CHEXA 714 1 734 752 753 736 855 873+
+ 874 857
CHEXA 715 1 736 753 754 738 857 874+
+ 875 859
CHEXA 716 1 738 754 755 740 859 875+
+ 876 861
CHEXA 717 1 740 755 756 742 861 876+
+ 877 863
CHEXA 718 1 742 756 757 744 863 877+
+ 878 865
CHEXA 719 1 744 757 758 746 865 878+
+ 879 867
CHEXA 720 1 746 758 759 748 867 879+
+ 880 869
CHEXA 721 1 750 761 760 749 871 882+
+ 881 870
CHEXA 722 1 749 760 762 751 870 881+
+ 883 872
CHEXA 723 1 751 762 763 752 872 883+
+ 884 873
CHEXA 724 1 752 763 764 753 873 884+
+ 885 874
CHEXA 725 1 753 764 765 754 874 885+
+ 886 875
CHEXA 726 1 754 765 766 755 875 886+
+ 887 876
CHEXA 727 1 755 766 767 756 876 887+
+ 888 877
CHEXA 728 1 756 767 768 757 877 888+
+ 889 878
CHEXA 729 1 757 768 769 758 878 889+
+ 890 879
CHEXA 730 1 758 769 770 759 879 890+
+ 891 880
CHEXA 731 1 761 772 771 760 882 893+
+ 892 881
CHEXA 732 1 760 771 773 762 881 892+
+ 894 883
CHEXA 733 1 762 773 774 763 883 894+
+ 895 884
CHEXA 734 1 763 774 775 764 884 895+
+ 896 885
CHEXA 735 1 764 775 776 765 885 896+
+ 897 886
CHEXA 736 1 765 776 777 766 886 897+
+ 898 887
CHEXA 737 1 766 777 778 767 887 898+
+ 899 888
CHEXA 738 1 767 778 779 768 888 899+
+ 900 889
CHEXA 739 1 768 779 780 769 889 900+
+ 901 890
CHEXA 740 1 769 780 781 770 890 901+
+ 902 891
CHEXA 741 1 772 783 782 771 893 904+
+ 903 892
CHEXA 742 1 771 782 784 773 892 903+
+ 905 894

508 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 743 1 773 784 785 774 894 905+
+ 906 895
CHEXA 744 1 774 785 786 775 895 906+
+ 907 896
CHEXA 745 1 775 786 787 776 896 907+
+ 908 897
CHEXA 746 1 776 787 788 777 897 908+
+ 909 898
CHEXA 747 1 777 788 789 778 898 909+
+ 910 899
CHEXA 748 1 778 789 790 779 899 910+
+ 911 900
CHEXA 749 1 779 790 791 780 900 911+
+ 912 901
CHEXA 750 1 780 791 792 781 901 912+
+ 913 902
CHEXA 751 1 783 794 793 782 904 915+
+ 914 903
CHEXA 752 1 782 793 795 784 903 914+
+ 916 905
CHEXA 753 1 784 795 796 785 905 916+
+ 917 906
CHEXA 754 1 785 796 797 786 906 917+
+ 918 907
CHEXA 755 1 786 797 798 787 907 918+
+ 919 908
CHEXA 756 1 787 798 799 788 908 919+
+ 920 909
CHEXA 757 1 788 799 800 789 909 920+
+ 921 910
CHEXA 758 1 789 800 801 790 910 921+
+ 922 911
CHEXA 759 1 790 801 802 791 911 922+
+ 923 912
CHEXA 760 1 791 802 803 792 912 923+
+ 924 913
CHEXA 761 1 794 805 804 793 915 926+
+ 925 914
CHEXA 762 1 793 804 806 795 914 925+
+ 927 916
CHEXA 763 1 795 806 807 796 916 927+
+ 928 917
CHEXA 764 1 796 807 808 797 917 928+
+ 929 918
CHEXA 765 1 797 808 809 798 918 929+
+ 930 919
CHEXA 766 1 798 809 810 799 919 930+
+ 931 920
CHEXA 767 1 799 810 811 800 920 931+
+ 932 921
CHEXA 768 1 800 811 812 801 921 932+
+ 933 922
CHEXA 769 1 801 812 813 802 922 933+
+ 934 923
CHEXA 770 1 802 813 814 803 923 934+
+ 935 924
CHEXA 771 1 805 816 815 804 926 937+
+ 936 925
CHEXA 772 1 804 815 817 806 925 936+
+ 938 927
CHEXA 773 1 806 817 818 807 927 938+
+ 939 928
CHEXA 774 1 807 818 819 808 928 939+
+ 940 929
CHEXA 775 1 808 819 820 809 929 940+
+ 941 930
CHEXA 776 1 809 820 821 810 930 941+
+ 942 931
CHEXA 777 1 810 821 822 811 931 942+

Altair Engineering OptiStruct 13.0 Reference Guide 509

Proprietary Information of Altair Engineering


+ 943 932
CHEXA 778 1 811 822 823 812 932 943+
+ 944 933
CHEXA 779 1 812 823 824 813 933 944+
+ 945 934
CHEXA 780 1 813 824 825 814 934 945+
+ 946 935
CHEXA 781 1 816 827 826 815 937 948+
+ 947 936
CHEXA 782 1 815 826 828 817 936 947+
+ 949 938
CHEXA 783 1 817 828 829 818 938 949+
+ 950 939
CHEXA 784 1 818 829 830 819 939 950+
+ 951 940
CHEXA 785 1 819 830 831 820 940 951+
+ 952 941
CHEXA 786 1 820 831 832 821 941 952+
+ 953 942
CHEXA 787 1 821 832 833 822 942 953+
+ 954 943
CHEXA 788 1 822 833 834 823 943 954+
+ 955 944
CHEXA 789 1 823 834 835 824 944 955+
+ 956 945
CHEXA 790 1 824 835 836 825 945 956+
+ 957 946
CHEXA 791 1 827 838 837 826 948 959+
+ 958 947
CHEXA 792 1 826 837 839 828 947 958+
+ 960 949
CHEXA 793 1 828 839 840 829 949 960+
+ 961 950
CHEXA 794 1 829 840 841 830 950 961+
+ 962 951
CHEXA 795 1 830 841 842 831 951 962+
+ 963 952
CHEXA 796 1 831 842 843 832 952 963+
+ 964 953
CHEXA 797 1 832 843 844 833 953 964+
+ 965 954
CHEXA 798 1 833 844 845 834 954 965+
+ 966 955
CHEXA 799 1 834 845 846 835 955 966+
+ 967 956
CHEXA 800 1 835 846 847 836 956 967+
+ 968 957
CHEXA 801 1 848 851 850 849 969 972+
+ 971 970
CHEXA 802 1 849 850 853 852 970 971+
+ 974 973
CHEXA 803 1 852 853 855 854 973 974+
+ 976 975
CHEXA 804 1 854 855 857 856 975 976+
+ 978 977
CHEXA 805 1 856 857 859 858 977 978+
+ 980 979
CHEXA 806 1 858 859 861 860 979 980+
+ 982 981
CHEXA 807 1 860 861 863 862 981 982+
+ 984 983
CHEXA 808 1 862 863 865 864 983 984+
+ 986 985
CHEXA 809 1 864 865 867 866 985 986+
+ 988 987
CHEXA 810 1 866 867 869 868 987 988+
+ 990 989
CHEXA 811 1 851 871 870 850 972 992+
+ 991 971

510 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 812 1 850 870 872 853 971 991+
+ 993 974
CHEXA 813 1 853 872 873 855 974 993+
+ 994 976
CHEXA 814 1 855 873 874 857 976 994+
+ 995 978
CHEXA 815 1 857 874 875 859 978 995+
+ 996 980
CHEXA 816 1 859 875 876 861 980 996+
+ 997 982
CHEXA 817 1 861 876 877 863 982 997+
+ 998 984
CHEXA 818 1 863 877 878 865 984 998+
+ 999 986
CHEXA 819 1 865 878 879 867 986 999+
+ 1000 988
CHEXA 820 1 867 879 880 869 988 1000+
+ 1001 990
CHEXA 821 1 871 882 881 870 992 1003+
+ 1002 991
CHEXA 822 1 870 881 883 872 991 1002+
+ 1004 993
CHEXA 823 1 872 883 884 873 993 1004+
+ 1005 994
CHEXA 824 1 873 884 885 874 994 1005+
+ 1006 995
CHEXA 825 1 874 885 886 875 995 1006+
+ 1007 996
CHEXA 826 1 875 886 887 876 996 1007+
+ 1008 997
CHEXA 827 1 876 887 888 877 997 1008+
+ 1009 998
CHEXA 828 1 877 888 889 878 998 1009+
+ 1010 999
CHEXA 829 1 878 889 890 879 999 1010+
+ 1011 1000
CHEXA 830 1 879 890 891 880 1000 1011+
+ 1012 1001
CHEXA 831 1 882 893 892 881 1003 1014+
+ 1013 1002
CHEXA 832 1 881 892 894 883 1002 1013+
+ 1015 1004
CHEXA 833 1 883 894 895 884 1004 1015+
+ 1016 1005
CHEXA 834 1 884 895 896 885 1005 1016+
+ 1017 1006
CHEXA 835 1 885 896 897 886 1006 1017+
+ 1018 1007
CHEXA 836 1 886 897 898 887 1007 1018+
+ 1019 1008
CHEXA 837 1 887 898 899 888 1008 1019+
+ 1020 1009
CHEXA 838 1 888 899 900 889 1009 1020+
+ 1021 1010
CHEXA 839 1 889 900 901 890 1010 1021+
+ 1022 1011
CHEXA 840 1 890 901 902 891 1011 1022+
+ 1023 1012
CHEXA 841 1 893 904 903 892 1014 1025+
+ 1024 1013
CHEXA 842 1 892 903 905 894 1013 1024+
+ 1026 1015
CHEXA 843 1 894 905 906 895 1015 1026+
+ 1027 1016
CHEXA 844 1 895 906 907 896 1016 1027+
+ 1028 1017
CHEXA 845 1 896 907 908 897 1017 1028+
+ 1029 1018
CHEXA 846 1 897 908 909 898 1018 1029+

Altair Engineering OptiStruct 13.0 Reference Guide 511

Proprietary Information of Altair Engineering


+ 1030 1019
CHEXA 847 1 898 909 910 899 1019 1030+
+ 1031 1020
CHEXA 848 1 899 910 911 900 1020 1031+
+ 1032 1021
CHEXA 849 1 900 911 912 901 1021 1032+
+ 1033 1022
CHEXA 850 1 901 912 913 902 1022 1033+
+ 1034 1023
CHEXA 851 1 904 915 914 903 1025 1036+
+ 1035 1024
CHEXA 852 1 903 914 916 905 1024 1035+
+ 1037 1026
CHEXA 853 1 905 916 917 906 1026 1037+
+ 1038 1027
CHEXA 854 1 906 917 918 907 1027 1038+
+ 1039 1028
CHEXA 855 1 907 918 919 908 1028 1039+
+ 1040 1029
CHEXA 856 1 908 919 920 909 1029 1040+
+ 1041 1030
CHEXA 857 1 909 920 921 910 1030 1041+
+ 1042 1031
CHEXA 858 1 910 921 922 911 1031 1042+
+ 1043 1032
CHEXA 859 1 911 922 923 912 1032 1043+
+ 1044 1033
CHEXA 860 1 912 923 924 913 1033 1044+
+ 1045 1034
CHEXA 861 1 915 926 925 914 1036 1047+
+ 1046 1035
CHEXA 862 1 914 925 927 916 1035 1046+
+ 1048 1037
CHEXA 863 1 916 927 928 917 1037 1048+
+ 1049 1038
CHEXA 864 1 917 928 929 918 1038 1049+
+ 1050 1039
CHEXA 865 1 918 929 930 919 1039 1050+
+ 1051 1040
CHEXA 866 1 919 930 931 920 1040 1051+
+ 1052 1041
CHEXA 867 1 920 931 932 921 1041 1052+
+ 1053 1042
CHEXA 868 1 921 932 933 922 1042 1053+
+ 1054 1043
CHEXA 869 1 922 933 934 923 1043 1054+
+ 1055 1044
CHEXA 870 1 923 934 935 924 1044 1055+
+ 1056 1045
CHEXA 871 1 926 937 936 925 1047 1058+
+ 1057 1046
CHEXA 872 1 925 936 938 927 1046 1057+
+ 1059 1048
CHEXA 873 1 927 938 939 928 1048 1059+
+ 1060 1049
CHEXA 874 1 928 939 940 929 1049 1060+
+ 1061 1050
CHEXA 875 1 929 940 941 930 1050 1061+
+ 1062 1051
CHEXA 876 1 930 941 942 931 1051 1062+
+ 1063 1052
CHEXA 877 1 931 942 943 932 1052 1063+
+ 1064 1053
CHEXA 878 1 932 943 944 933 1053 1064+
+ 1065 1054
CHEXA 879 1 933 944 945 934 1054 1065+
+ 1066 1055
CHEXA 880 1 934 945 946 935 1055 1066+
+ 1067 1056

512 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 881 1 937 948 947 936 1058 1069+
+ 1068 1057
CHEXA 882 1 936 947 949 938 1057 1068+
+ 1070 1059
CHEXA 883 1 938 949 950 939 1059 1070+
+ 1071 1060
CHEXA 884 1 939 950 951 940 1060 1071+
+ 1072 1061
CHEXA 885 1 940 951 952 941 1061 1072+
+ 1073 1062
CHEXA 886 1 941 952 953 942 1062 1073+
+ 1074 1063
CHEXA 887 1 942 953 954 943 1063 1074+
+ 1075 1064
CHEXA 888 1 943 954 955 944 1064 1075+
+ 1076 1065
CHEXA 889 1 944 955 956 945 1065 1076+
+ 1077 1066
CHEXA 890 1 945 956 957 946 1066 1077+
+ 1078 1067
CHEXA 891 1 948 959 958 947 1069 1080+
+ 1079 1068
CHEXA 892 1 947 958 960 949 1068 1079+
+ 1081 1070
CHEXA 893 1 949 960 961 950 1070 1081+
+ 1082 1071
CHEXA 894 1 950 961 962 951 1071 1082+
+ 1083 1072
CHEXA 895 1 951 962 963 952 1072 1083+
+ 1084 1073
CHEXA 896 1 952 963 964 953 1073 1084+
+ 1085 1074
CHEXA 897 1 953 964 965 954 1074 1085+
+ 1086 1075
CHEXA 898 1 954 965 966 955 1075 1086+
+ 1087 1076
CHEXA 899 1 955 966 967 956 1076 1087+
+ 1088 1077
CHEXA 900 1 956 967 968 957 1077 1088+
+ 1089 1078
CHEXA 901 1 969 972 971 970 1090 1093+
+ 1092 1091
CHEXA 902 1 970 971 974 973 1091 1092+
+ 1095 1094
CHEXA 903 1 973 974 976 975 1094 1095+
+ 1097 1096
CHEXA 904 1 975 976 978 977 1096 1097+
+ 1099 1098
CHEXA 905 1 977 978 980 979 1098 1099+
+ 1101 1100
CHEXA 906 1 979 980 982 981 1100 1101+
+ 1103 1102
CHEXA 907 1 981 982 984 983 1102 1103+
+ 1105 1104
CHEXA 908 1 983 984 986 985 1104 1105+
+ 1107 1106
CHEXA 909 1 985 986 988 987 1106 1107+
+ 1109 1108
CHEXA 910 1 987 988 990 989 1108 1109+
+ 1111 1110
CHEXA 911 1 972 992 991 971 1093 1113+
+ 1112 1092
CHEXA 912 1 971 991 993 974 1092 1112+
+ 1114 1095
CHEXA 913 1 974 993 994 976 1095 1114+
+ 1115 1097
CHEXA 914 1 976 994 995 978 1097 1115+
+ 1116 1099
CHEXA 915 1 978 995 996 980 1099 1116+

Altair Engineering OptiStruct 13.0 Reference Guide 513

Proprietary Information of Altair Engineering


+ 1117 1101
CHEXA 916 1 980 996 997 982 1101 1117+
+ 1118 1103
CHEXA 917 1 982 997 998 984 1103 1118+
+ 1119 1105
CHEXA 918 1 984 998 999 986 1105 1119+
+ 1120 1107
CHEXA 919 1 986 999 1000 988 1107 1120+
+ 1121 1109
CHEXA 920 1 988 1000 1001 990 1109 1121+
+ 1122 1111
CHEXA 921 1 992 1003 1002 991 1113 1124+
+ 1123 1112
CHEXA 922 1 991 1002 1004 993 1112 1123+
+ 1125 1114
CHEXA 923 1 993 1004 1005 994 1114 1125+
+ 1126 1115
CHEXA 924 1 994 1005 1006 995 1115 1126+
+ 1127 1116
CHEXA 925 1 995 1006 1007 996 1116 1127+
+ 1128 1117
CHEXA 926 1 996 1007 1008 997 1117 1128+
+ 1129 1118
CHEXA 927 1 997 1008 1009 998 1118 1129+
+ 1130 1119
CHEXA 928 1 998 1009 1010 999 1119 1130+
+ 1131 1120
CHEXA 929 1 999 1010 1011 1000 1120 1131+
+ 1132 1121
CHEXA 930 1 1000 1011 1012 1001 1121 1132+
+ 1133 1122
CHEXA 931 1 1003 1014 1013 1002 1124 1135+
+ 1134 1123
CHEXA 932 1 1002 1013 1015 1004 1123 1134+
+ 1136 1125
CHEXA 933 1 1004 1015 1016 1005 1125 1136+
+ 1137 1126
CHEXA 934 1 1005 1016 1017 1006 1126 1137+
+ 1138 1127
CHEXA 935 1 1006 1017 1018 1007 1127 1138+
+ 1139 1128
CHEXA 936 1 1007 1018 1019 1008 1128 1139+
+ 1140 1129
CHEXA 937 1 1008 1019 1020 1009 1129 1140+
+ 1141 1130
CHEXA 938 1 1009 1020 1021 1010 1130 1141+
+ 1142 1131
CHEXA 939 1 1010 1021 1022 1011 1131 1142+
+ 1143 1132
CHEXA 940 1 1011 1022 1023 1012 1132 1143+
+ 1144 1133
CHEXA 941 1 1014 1025 1024 1013 1135 1146+
+ 1145 1134
CHEXA 942 1 1013 1024 1026 1015 1134 1145+
+ 1147 1136
CHEXA 943 1 1015 1026 1027 1016 1136 1147+
+ 1148 1137
CHEXA 944 1 1016 1027 1028 1017 1137 1148+
+ 1149 1138
CHEXA 945 1 1017 1028 1029 1018 1138 1149+
+ 1150 1139
CHEXA 946 1 1018 1029 1030 1019 1139 1150+
+ 1151 1140
CHEXA 947 1 1019 1030 1031 1020 1140 1151+
+ 1152 1141
CHEXA 948 1 1020 1031 1032 1021 1141 1152+
+ 1153 1142
CHEXA 949 1 1021 1032 1033 1022 1142 1153+
+ 1154 1143

514 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 950 1 1022 1033 1034 1023 1143 1154+
+ 1155 1144
CHEXA 951 1 1025 1036 1035 1024 1146 1157+
+ 1156 1145
CHEXA 952 1 1024 1035 1037 1026 1145 1156+
+ 1158 1147
CHEXA 953 1 1026 1037 1038 1027 1147 1158+
+ 1159 1148
CHEXA 954 1 1027 1038 1039 1028 1148 1159+
+ 1160 1149
CHEXA 955 1 1028 1039 1040 1029 1149 1160+
+ 1161 1150
CHEXA 956 1 1029 1040 1041 1030 1150 1161+
+ 1162 1151
CHEXA 957 1 1030 1041 1042 1031 1151 1162+
+ 1163 1152
CHEXA 958 1 1031 1042 1043 1032 1152 1163+
+ 1164 1153
CHEXA 959 1 1032 1043 1044 1033 1153 1164+
+ 1165 1154
CHEXA 960 1 1033 1044 1045 1034 1154 1165+
+ 1166 1155
CHEXA 961 1 1036 1047 1046 1035 1157 1168+
+ 1167 1156
CHEXA 962 1 1035 1046 1048 1037 1156 1167+
+ 1169 1158
CHEXA 963 1 1037 1048 1049 1038 1158 1169+
+ 1170 1159
CHEXA 964 1 1038 1049 1050 1039 1159 1170+
+ 1171 1160
CHEXA 965 1 1039 1050 1051 1040 1160 1171+
+ 1172 1161
CHEXA 966 1 1040 1051 1052 1041 1161 1172+
+ 1173 1162
CHEXA 967 1 1041 1052 1053 1042 1162 1173+
+ 1174 1163
CHEXA 968 1 1042 1053 1054 1043 1163 1174+
+ 1175 1164
CHEXA 969 1 1043 1054 1055 1044 1164 1175+
+ 1176 1165
CHEXA 970 1 1044 1055 1056 1045 1165 1176+
+ 1177 1166
CHEXA 971 1 1047 1058 1057 1046 1168 1179+
+ 1178 1167
CHEXA 972 1 1046 1057 1059 1048 1167 1178+
+ 1180 1169
CHEXA 973 1 1048 1059 1060 1049 1169 1180+
+ 1181 1170
CHEXA 974 1 1049 1060 1061 1050 1170 1181+
+ 1182 1171
CHEXA 975 1 1050 1061 1062 1051 1171 1182+
+ 1183 1172
CHEXA 976 1 1051 1062 1063 1052 1172 1183+
+ 1184 1173
CHEXA 977 1 1052 1063 1064 1053 1173 1184+
+ 1185 1174
CHEXA 978 1 1053 1064 1065 1054 1174 1185+
+ 1186 1175
CHEXA 979 1 1054 1065 1066 1055 1175 1186+
+ 1187 1176
CHEXA 980 1 1055 1066 1067 1056 1176 1187+
+ 1188 1177
CHEXA 981 1 1058 1069 1068 1057 1179 1190+
+ 1189 1178
CHEXA 982 1 1057 1068 1070 1059 1178 1189+
+ 1191 1180
CHEXA 983 1 1059 1070 1071 1060 1180 1191+
+ 1192 1181
CHEXA 984 1 1060 1071 1072 1061 1181 1192+

Altair Engineering OptiStruct 13.0 Reference Guide 515

Proprietary Information of Altair Engineering


+ 1193 1182
CHEXA 985 1 1061 1072 1073 1062 1182 1193+
+ 1194 1183
CHEXA 986 1 1062 1073 1074 1063 1183 1194+
+ 1195 1184
CHEXA 987 1 1063 1074 1075 1064 1184 1195+
+ 1196 1185
CHEXA 988 1 1064 1075 1076 1065 1185 1196+
+ 1197 1186
CHEXA 989 1 1065 1076 1077 1066 1186 1197+
+ 1198 1187
CHEXA 990 1 1066 1077 1078 1067 1187 1198+
+ 1199 1188
CHEXA 991 1 1069 1080 1079 1068 1190 1201+
+ 1200 1189
CHEXA 992 1 1068 1079 1081 1070 1189 1200+
+ 1202 1191
CHEXA 993 1 1070 1081 1082 1071 1191 1202+
+ 1203 1192
CHEXA 994 1 1071 1082 1083 1072 1192 1203+
+ 1204 1193
CHEXA 995 1 1072 1083 1084 1073 1193 1204+
+ 1205 1194
CHEXA 996 1 1073 1084 1085 1074 1194 1205+
+ 1206 1195
CHEXA 997 1 1074 1085 1086 1075 1195 1206+
+ 1207 1196
CHEXA 998 1 1075 1086 1087 1076 1196 1207+
+ 1208 1197
CHEXA 999 1 1076 1087 1088 1077 1197 1208+
+ 1209 1198
CHEXA 1000 1 1077 1088 1089 1078 1198 1209+
+ 1210 1199
CHEXA 1001 1 1090 1093 1092 1091 1211 1214+
+ 1213 1212
CHEXA 1002 1 1091 1092 1095 1094 1212 1213+
+ 1216 1215
CHEXA 1003 1 1094 1095 1097 1096 1215 1216+
+ 1218 1217
CHEXA 1004 1 1096 1097 1099 1098 1217 1218+
+ 1220 1219
CHEXA 1005 1 1098 1099 1101 1100 1219 1220+
+ 1222 1221
CHEXA 1006 1 1100 1101 1103 1102 1221 1222+
+ 1224 1223
CHEXA 1007 1 1102 1103 1105 1104 1223 1224+
+ 1226 1225
CHEXA 1008 1 1104 1105 1107 1106 1225 1226+
+ 1228 1227
CHEXA 1009 1 1106 1107 1109 1108 1227 1228+
+ 1230 1229
CHEXA 1010 1 1108 1109 1111 1110 1229 1230+
+ 1232 1231
CHEXA 1011 1 1093 1113 1112 1092 1214 1234+
+ 1233 1213
CHEXA 1012 1 1092 1112 1114 1095 1213 1233+
+ 1235 1216
CHEXA 1013 1 1095 1114 1115 1097 1216 1235+
+ 1236 1218
CHEXA 1014 1 1097 1115 1116 1099 1218 1236+
+ 1237 1220
CHEXA 1015 1 1099 1116 1117 1101 1220 1237+
+ 1238 1222
CHEXA 1016 1 1101 1117 1118 1103 1222 1238+
+ 1239 1224
CHEXA 1017 1 1103 1118 1119 1105 1224 1239+
+ 1240 1226
CHEXA 1018 1 1105 1119 1120 1107 1226 1240+
+ 1241 1228

516 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 1019 1 1107 1120 1121 1109 1228 1241+
+ 1242 1230
CHEXA 1020 1 1109 1121 1122 1111 1230 1242+
+ 1243 1232
CHEXA 1021 1 1113 1124 1123 1112 1234 1245+
+ 1244 1233
CHEXA 1022 1 1112 1123 1125 1114 1233 1244+
+ 1246 1235
CHEXA 1023 1 1114 1125 1126 1115 1235 1246+
+ 1247 1236
CHEXA 1024 1 1115 1126 1127 1116 1236 1247+
+ 1248 1237
CHEXA 1025 1 1116 1127 1128 1117 1237 1248+
+ 1249 1238
CHEXA 1026 1 1117 1128 1129 1118 1238 1249+
+ 1250 1239
CHEXA 1027 1 1118 1129 1130 1119 1239 1250+
+ 1251 1240
CHEXA 1028 1 1119 1130 1131 1120 1240 1251+
+ 1252 1241
CHEXA 1029 1 1120 1131 1132 1121 1241 1252+
+ 1253 1242
CHEXA 1030 1 1121 1132 1133 1122 1242 1253+
+ 1254 1243
CHEXA 1031 1 1124 1135 1134 1123 1245 1256+
+ 1255 1244
CHEXA 1032 1 1123 1134 1136 1125 1244 1255+
+ 1257 1246
CHEXA 1033 1 1125 1136 1137 1126 1246 1257+
+ 1258 1247
CHEXA 1034 1 1126 1137 1138 1127 1247 1258+
+ 1259 1248
CHEXA 1035 1 1127 1138 1139 1128 1248 1259+
+ 1260 1249
CHEXA 1036 1 1128 1139 1140 1129 1249 1260+
+ 1261 1250
CHEXA 1037 1 1129 1140 1141 1130 1250 1261+
+ 1262 1251
CHEXA 1038 1 1130 1141 1142 1131 1251 1262+
+ 1263 1252
CHEXA 1039 1 1131 1142 1143 1132 1252 1263+
+ 1264 1253
CHEXA 1040 1 1132 1143 1144 1133 1253 1264+
+ 1265 1254
CHEXA 1041 1 1135 1146 1145 1134 1256 1267+
+ 1266 1255
CHEXA 1042 1 1134 1145 1147 1136 1255 1266+
+ 1268 1257
CHEXA 1043 1 1136 1147 1148 1137 1257 1268+
+ 1269 1258
CHEXA 1044 1 1137 1148 1149 1138 1258 1269+
+ 1270 1259
CHEXA 1045 1 1138 1149 1150 1139 1259 1270+
+ 1271 1260
CHEXA 1046 1 1139 1150 1151 1140 1260 1271+
+ 1272 1261
CHEXA 1047 1 1140 1151 1152 1141 1261 1272+
+ 1273 1262
CHEXA 1048 1 1141 1152 1153 1142 1262 1273+
+ 1274 1263
CHEXA 1049 1 1142 1153 1154 1143 1263 1274+
+ 1275 1264
CHEXA 1050 1 1143 1154 1155 1144 1264 1275+
+ 1276 1265
CHEXA 1051 1 1146 1157 1156 1145 1267 1278+
+ 1277 1266
CHEXA 1052 1 1145 1156 1158 1147 1266 1277+
+ 1279 1268
CHEXA 1053 1 1147 1158 1159 1148 1268 1279+

Altair Engineering OptiStruct 13.0 Reference Guide 517

Proprietary Information of Altair Engineering


+ 1280 1269
CHEXA 1054 1 1148 1159 1160 1149 1269 1280+
+ 1281 1270
CHEXA 1055 1 1149 1160 1161 1150 1270 1281+
+ 1282 1271

CHEXA 1057 1 1151 1162 1163 1152 1272 1283+


+ 1284 1273
CHEXA 1058 1 1152 1163 1164 1153 1273 1284+
+ 1285 1274
CHEXA 1059 1 1153 1164 1165 1154 1274 1285+
+ 1286 1275
CHEXA 1060 1 1154 1165 1166 1155 1275 1286+
+ 1287 1276
CHEXA 1061 1 1157 1168 1167 1156 1278 1289+
+ 1288 1277
CHEXA 1062 1 1156 1167 1169 1158 1277 1288+
+ 1290 1279
CHEXA 1063 1 1158 1169 1170 1159 1279 1290+
+ 1291 1280
CHEXA 1064 1 1159 1170 1171 1160 1280 1291+
+ 1292 1281
CHEXA 1065 1 1160 1171 1172 1161 1281 1292+
+ 1293 1282
CHEXA 1066 1 1161 1172 1173 1162 1282 1293+
+ 1294 1283
CHEXA 1067 1 1162 1173 1174 1163 1283 1294+
+ 1295 1284
CHEXA 1068 1 1163 1174 1175 1164 1284 1295+
+ 1296 1285
CHEXA 1069 1 1164 1175 1176 1165 1285 1296+
+ 1297 1286
CHEXA 1070 1 1165 1176 1177 1166 1286 1297+
+ 1298 1287
CHEXA 1071 1 1168 1179 1178 1167 1289 1300+
+ 1299 1288
CHEXA 1072 1 1167 1178 1180 1169 1288 1299+
+ 1301 1290
CHEXA 1073 1 1169 1180 1181 1170 1290 1301+
+ 1302 1291
CHEXA 1074 1 1170 1181 1182 1171 1291 1302+
+ 1303 1292
CHEXA 1075 1 1171 1182 1183 1172 1292 1303+
+ 1304 1293
CHEXA 1076 1 1172 1183 1184 1173 1293 1304+
+ 1305 1294
CHEXA 1077 1 1173 1184 1185 1174 1294 1305+
+ 1306 1295
CHEXA 1078 1 1174 1185 1186 1175 1295 1306+
+ 1307 1296
CHEXA 1079 1 1175 1186 1187 1176 1296 1307+
+ 1308 1297
CHEXA 1080 1 1176 1187 1188 1177 1297 1308+
+ 1309 1298
CHEXA 1081 1 1179 1190 1189 1178 1300 1311+
+ 1310 1299
CHEXA 1082 1 1178 1189 1191 1180 1299 1310+
+ 1312 1301
CHEXA 1083 1 1180 1191 1192 1181 1301 1312+
+ 1313 1302
CHEXA 1084 1 1181 1192 1193 1182 1302 1313+
+ 1314 1303
CHEXA 1085 1 1182 1193 1194 1183 1303 1314+
+ 1315 1304
CHEXA 1086 1 1183 1194 1195 1184 1304 1315+
+ 1316 1305
CHEXA 1087 1 1184 1195 1196 1185 1305 1316+
+ 1317 1306
CHEXA 1088 1 1185 1196 1197 1186 1306 1317+

518 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 1318 1307
CHEXA 1089 1 1186 1197 1198 1187 1307 1318+
+ 1319 1308
CHEXA 1090 1 1187 1198 1199 1188 1308 1319+
+ 1320 1309
CHEXA 1091 1 1190 1201 1200 1189 1311 1322+
+ 1321 1310
CHEXA 1092 1 1189 1200 1202 1191 1310 1321+
+ 1323 1312
CHEXA 1093 1 1191 1202 1203 1192 1312 1323+
+ 1324 1313
CHEXA 1094 1 1192 1203 1204 1193 1313 1324+
+ 1325 1314
CHEXA 1095 1 1193 1204 1205 1194 1314 1325+
+ 1326 1315
CHEXA 1096 1 1194 1205 1206 1195 1315 1326+
+ 1327 1316
CHEXA 1097 1 1195 1206 1207 1196 1316 1327+
+ 1328 1317
CHEXA 1098 1 1196 1207 1208 1197 1317 1328+
+ 1329 1318
CHEXA 1099 1 1197 1208 1209 1198 1318 1329+
+ 1330 1319
CHEXA 1100 1 1198 1209 1210 1199 1319 1330+
+ 1331 1320
$$
$$------------------------------------------------------------------------------$
$$ HyperMesh name information for generic property collectors $
$$------------------------------------------------------------------------------$
$$
$$------------------------------------------------------------------------------$
$$ Property Definition for 1-D Elements $
$$------------------------------------------------------------------------------$
$$
$$------------------------------------------------------------------------------$
$$ HyperMesh name and color information for generic components $
$$------------------------------------------------------------------------------$
$HMNAME COMP 6"auto1"
$HWCOLOR COMP 6 3
$
$$
$$------------------------------------------------------------------------------$
$$ Property Definition for Surface and Volume Elements $
$$------------------------------------------------------------------------------$
$$
$$ PSHELL Data
$
$HMNAME COMP 4"shells"
$HWCOLOR COMP 4 7
PSHELL 4 20.2 2 2
$$
$$ PSOLID Data
$
$HMNAME COMP 1"solids"
$HWCOLOR COMP 1 26
PSOLID 1 1 PFLUID
PSOLID 2 2
$$
$$------------------------------------------------------------------------------$
$$ Material Definition Cards $
$$------------------------------------------------------------------------------$
$$--------------------------------------------------------------
$$ HYPERMESH TAGS
$$--------------------------------------------------------------
$$BEGIN TAGS
$$END TAGS
$$
$$ MAT1 Data
$

Altair Engineering OptiStruct 13.0 Reference Guide 519

Proprietary Information of Altair Engineering


$HMNAME MAT 2"MAT1"
$HWCOLOR MAT 2 18
MAT1 2200000.0 0.3 0.9e-5
$$
$$
$$ MAT10 Data
$HMNAME MAT 1"MAT10_1"
$HWCOLOR MAT 1 3
MAT10 11.0 0.01
$$
$$
$$------------------------------------------------------------------------------$
$$ HyperMesh name information for generic materials $
$$------------------------------------------------------------------------------$
$$
$$------------------------------------------------------------------------------$
$$ Material Definition Cards $
$$------------------------------------------------------------------------------$
$$
$$------------------------------------------------------------------------------$
$$ Loads and Boundary Conditions $
$$------------------------------------------------------------------------------$
$$
$$HyperMesh name and color information for generic loadcollectors
$$
$HMNAME LOADCOL 4"SPC"
$HWCOLOR LOADCOL 4 3
$
$HMNAME LOADCOL 6"spcd"
$HWCOLOR LOADCOL 6 4
$
$$
$$
$$
$$
$$ FREQ1 cards
$$
$HMNAME LOADCOL 5"freq"
$HWCOLOR LOADCOL 5 4
FREQ1 50.1 10.0 5
$$
$$
$$
$$
$$
$$ RLOAD2 cards
$$
$HMNAME LOADCOL 2"rload2"
$HWCOLOR LOADCOL 2 5
RLOAD2 2 6 1 0 ACCE
$$
$HMNAME LOADCOL 3"darea"
$HWCOLOR LOADCOL 3 5
RLOAD2 3 3 1 0 LOAD
$$
$$
$$
$$ TABLED1 cards
$$
$HMNAME LOADCOL 1"tab"
$HWCOLOR LOADCOL 1 41
TABLED1 1 LINEAR LINEAR
+ 0.0 0.0 1000.0 1.0ENDT
$$
TABLED1 2 LINEAR LINEAR
+ 0.0 0.0 1000.0 1.0ENDT
$$
TABLED1 3 LINEAR LINEAR
+ 0.0 5.0 1000.0 5.0ENDT

520 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


$$ DLOAD cards
$$
$HMNAME LOADCOL 11"DLOAD11"
$HWCOLOR LOADCOL 11 3
DLOAD 111.0 1.0 2 1.0 3
$$
$$
$$
$$
$$
$$
$$
$$ SPC Data
$$
SPC 4 1431 1234560.0
SPC 4 1432 1234560.0
SPC 4 1451 1234560.0
SPC 4 1452 1234560.0
SPC 4 1734 3 0.0
$$
$$ SPCD Data
$$
SPCD 6 1734 3 3.0
$
$ DAREA Data
$
$$
$$ DAREA Data
$$
DAREA 3 1734 3-10.0
ENDDATA

ALTDOCTAG "HqTD_ARNMI\S\pMpN13G;5oANN]l[enE7fmSbTJro20LOpNriZFOQfUk]
_`5hfS5ATf6pT7RXMjA3e@k_r^K?GP;?OeEbD0"
ADI0.1.0 2011-05-13T19:57:45 0of1 OSQA
ENDDOCTAG

Comments

1. Element identification numbers should be unique with respect to all other element
identification numbers.

2. Grid points G1 through G4 must be given in consecutive order about one quadrilateral
face. G5 through G8 must be on the opposite face with G5 opposite G1, G6 opposite G2,
and so on.

3. The edge points, G9 to G20 are optional. All or none of them may exist. The corner grid
points cannot be deleted. The edge points should be in the middle third of the edges.

4. The second continuation is optional.

5. The face consisting of grid points G1 through G4 and G9 through G12 is assumed to be in
contact with the structure.

6. The mass is lumped to the face formed by grid points G5 through G8 and G17 through G20
and defined to be in contact with the fluid. The opposite face has no mass contribution
due to the absorber element. Also, the face in contact with the fluid has only

Altair Engineering OptiStruct 13.0 Reference Guide 521

Proprietary Information of Altair Engineering


translational stiffness in the direction normal to the face.

7. This card is represented as a CHACAB8 or CHACAB20 element in HyperMesh.

522 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHBDYE

Bulk Data Entry

CHBDYE – Thermal Surface Element (Element Form)

Description

Defines a surface element for application of thermal boundary condition.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C HBDYE EID EID2 SIDE

Field Contents

EID Unique surface element identification number. See comments.

No default (Integer > 0)

EID2 A heat conduction element identification number. See comments.

No default (Integer > 0)

SIDE Element side identification number.

No default (1 < Integer < 6)

Comments

1. EID is unique with respect to other surface element IDs.

2. EID2 identifies the heat conduction element associated with this surface element.

1D 2D 3D
CBAR CQUAD4 CHEXA
CBEAM CQUAD8 CPENTA
CONROD CTRIA3 CPYRA
CROD CTIRA6 CTETRA
C onduction elements for heat transfer analysis

3. All conduction elements that are to have a boundary condition applied must be individually
identified with the application of a surface element entry CHBDYE.

Altair Engineering OptiStruct 13.0 Reference Guide 523

Proprietary Information of Altair Engineering


4. Side conventions for 3D elements:

Sides are numbered consecutively according to the order of the grid point numbers on the
3D element entry. The sides of 3D elements are either quadrilaterals or triangles. For
each element type, the side numbers are shown here:

Side convention for C HEXA element (1st or 2nd order)

Side convention for C PENTA element (1st or 2nd order)

524 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Side convention for C PYRA element (1st or 2nd order)

Side convention for C TETRA element (1st or 2nd order)

5. Side conventions for 2D elements.

2D elements have one side of type AREA (this is Side 1) and 3 or 4 sides of type LINE.

AREA type: Side 1 is that given by the right hand rule on the shell’s gird points.

LINE type: The second side (first line) is from grid point 1 to grid point 2, and the
remaining lines are numbered consecutively. The thickness of the line is that of the shell,
and the normal to the line is outward from the shell in the plane of the shell. Note that
midside nodes are ignored in the specification.

6. Side conventions for 1D elements.

1D elements have one linear side (Side 1) with geometry that is the same as that of the
element and two POINT type sides, corresponding to the two points bounding the linear
element (first grid point side 2; second grid point side 3).

Altair Engineering OptiStruct 13.0 Reference Guide 525

Proprietary Information of Altair Engineering


POINT type: Point sides may be used with any linear element. The direction of the
outward normals of these points is in line with the element axis, but pointing away from
the element. The area assigned to these POINT type sides is consistent with the element
geometry.

Boundary conditions (QBDY1) are applied to CHBDYE through reference of the EID.

7. This card is represented as slave3 and slave4 element in HyperMesh.

526 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA

Bulk Data Entry

CHEXA – Six-sided Solid Element with Eight or Twenty Grid Points

Description

Defines the connections of the HEXA solid element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C HEXA EID PID G1 G2 G3 G4 G5 G6

G7 G8 G9 G10 G11 G12 G13 G14

G15 G16 G17 G18 G19 G20

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C HEXA 71 4 3 4 5 6 7 8

9 10

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PSOLID property entry.

Default = EID (Integer > 0)

G# Grid point identification numbers of connection points.

Default = blank (Integer > 0 or blank)

Altair Engineering OptiStruct 13.0 Reference Guide 527

Proprietary Information of Altair Engineering


Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. Grid points G1,…,G4 must be given in consecutive order about one quadrilateral face.
G5,…,G8 must be on the opposite face with G5 opposite G1, G6 opposite G2, and so on.

The edge points, G9 through G20, are optional. If any of the edge points are present,
they all must be used. The second continuation must not be present for the 8-noded
version of this element.

It is recommended that the edge points be placed near the middle of the edge.

C HEXA definition

3. If the user-prescribed node numbering on the bottom and top faces is reversed as
compared to the sequence shown above, then the nodes are renumbered to produce
right-handed orientation of numbering. This is accomplished by swapping nodes G1 with
G3 and G5 with G7. For 20-noded CHEXA, appropriate changes to mid-side node
numbering are also performed. In such cases, the element coordinate system will be built
on the renumbered node sequence.

4. Stresses are output in the material coordinate system. The material coordinate system is
defined on the referenced PSOLID entry. It may be defined as the basic coordinate
system (CORDM = 0), a defined system (CORDM = Integer > 0), or the element coordinate
system (CORDM = -1).

5. The element coordinate system for the CHEXA element is defined as follows:

Three intermediate vectors R, S, and T are chosen by the following rules:

R Joins the centroids of the faces described by the grid points G4, G1, G5, G8
and the grid points G3, G2, G6, G7.

S Joins the centroids of the faces described by the grid points G1, G2, G6, G5
and the grid points G4, G3, G7, G8

T Joins the centroids of the faces described by the grid points G1, G2, G3, G4
and the grid pints G5, G6, G7, G8.

528 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


C HEXA element coordinate systems

The origin of the element coordinate system is at the intersection of these three vectors.
If the vectors do not all intersect at one point, then the average location of the
intersection points is used.

The element z-axis corresponds to the T vector.

The element y-axis is the cross product of the T and R vectors.

The element x-axis is the cross product of the element y-axis and the element z-axis.

6. This card is represented as a hexa8 or hex20 element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 529

Proprietary Information of Altair Engineering


CMASS1

Bulk Data Entry

CMASS1 – Scalar Mass Connection

Description

Defines a scalar mass element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MASS1 EID PID G1 C1 G2 C2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MASS1 45 4 653 2

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Property identification number of a PMASS entry.

Default = EID (Integer > 0)

G1, G2 Geometric grid point or scalar point identification number.

Default = 0 (Integer > 0)

C1, C2 Component number in the displacement coordinate system specified by the


CD entry of the GRID data.

No default (0 < Integer < 6)

530 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. Zero or blank may be used to indicate a grounded terminal G1 or G2 with a corresponding


blank or zero C1 or C2. A grounded terminal is a point with a displacement that is
constrained to zero.

2. Scalar points may be used for G1 and/or G2, (with a corresponding C1 and/or C2 of zero
or blank). If only scalar points and/or grounded terminals are involved, it is more efficient
to use the CMASS3 entry.

3. Element identification numbers should be unique with respect to all other element
identification numbers.

4. The two connection points (G1, C1) and (G2, C2) must not be coincident. Except in
unusual circumstances, one of them will be a grounded terminal with blank entries for Gi
and Ci.

5. A scalar point specified on this entry need not be defined on an SPOINT entry.

6. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).

7. Scalar mass elements are ignored in heat transfer analysis.

8. This card is represented as a spring or mass element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 531

Proprietary Information of Altair Engineering


CMASS2

Bulk Data Entry

CMASS2 – Scalar Mass Property and Connection

Description

Defines a scalar mass element without reference to a property entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MASS2 EID M G1 C1 G2 C2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MASS2 2 1.1 56 3

Field Contents

EID Unique element identification number.

No default (Integer > 0)

M Value of the scalar mass.

No default (Real)

G1, G2 Geometric grid or identification number.

No default (Integer > 0)

C1, C2 Component number in the displacement coordinate system specified by


the CD entry of the GRID data.

No default (0 < Integer < 6)

532 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. Zero or blank may be used to indicate a grounded terminal G1 or G2 with a corresponding


blank or zero C1 or C2. A grounded terminal is a point with a displacement that is
constrained to zero.

2. Scalar points may be used for G1 and/or G2, (with a corresponding C1 and/or C2 of zero
or blank). If only scalar points and/or grounded terminals are involved, it is more efficient
to use the CMASS4 entry.

3. Element identification numbers should be unique with respect to all other element
identification numbers.

4. This single entry completely defines the element since no material or geometric properties
are required.

5. The two connection points (G1, C1) and (G2, C2) must be distinct. Except in unusual
circumstances, one of them will be a grounded terminal with blank entries for Gi and Ci.

6. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).

7. Scalar mass elements are ignored in heat transfer analysis.

8. This card is represented as a spring or mass element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 533

Proprietary Information of Altair Engineering


CMASS3

Bulk Data Entry

CMASS3 – Scalar Mass Connection to Scalar Points Only

Description

Defines a scalar mass element that is connected only to scalar points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MASS3 EID PID S1 S2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MASS3 13 42 62

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Property identification number of a PMASS entry.

Default = EID (Integer > 0)

S1, S2 Scalar point identification numbers.

Default = 0 (Integer >

Comments

1. S1 or S2, but not both, may be blank or zero, indicating a constrained coordinate.

2. Element identification numbers should be unique with respect to all other element
identification numbers.

534 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. Only one scalar mass element may be defined on a single entry.

4. A scalar point specified on this entry need not be defined on an SPOINT entry.

5. Scalar mass elements are ignored in heat transfer analysis.

6. This card is represented as a spring or mass element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 535

Proprietary Information of Altair Engineering


CMASS4

Bulk Data Entry

CMASS4 – Scalar Mass Property and Connection to Scalar Points Only

Description

Defines a scalar mass element that is connected only to scalar points, without reference to a
property entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MASS4 EID M S1 S2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MASS4 23 14.92 23

Field Contents

EID Unique element identification number.

No default (Integer > 0)

M Scalar mass value.

No default (Real)

S1, S2 Scalar point identification numbers.

Default = 0 (Integer >

Comments

1. S1 or S2, but not both, may be blank or zero, indicating a constrained coordinate. This is
the usual case.

536 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


2. Element identification numbers should be unique with respect to all other element
identification numbers.

3. Only one scalar mass element may be defined on a single entry.

4. A scalar point specified on this entry need not be defined on an SPOINT entry.

5. This single entry completely defines the element since no material or geometric properties
are required.

6. Scalar mass elements are ignored in heat transfer analysis.

7. This card is represented as a spring or mass element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 537

Proprietary Information of Altair Engineering


CMBEAM

Bulk Data Entry

CMBEAM – Beam Element for MBD

Description

Defines a beam element for multi-body dynamics solution sequence without reference to a
property entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MBEAM EID MID GA GB X1, G0 Y1 Z1 L

A I1 I2 J K1 K2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MBEAM 1 2 123 125 0.0 0.0 1.0 5.0

100.0 833.3 833.3 1485.3

Field Contents

EID Element identification number.

(Integer > 0)

MID Material identification number. See comment 5.

(Integer > 0)

GA, GB Grid point identification number of connection points.

538 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

X1, Y1, Z1 Components of vector v at end A, measured at end A, parallel to the


components of the displacement coordinate system for GA, to
determine (with the vector from end A to end B) the orientation of the
element coordinate system for the BEAM element.

(Real)

G0 Grid point identification number to optionally supply X1, X2, and X3


(Integer > 0). Direction of orientation vector is GA to G0.

(Integer > 0)

L Undeformed length along the X-axis of the beam.

(Real)

A Area of the beam cross-section.

No default (Real > 0.0)

I1 Area moment inertia in plane 1 about the neutral axis.

No default (Real > 0.0)

I2 Area moment inertia in plane 2 about the neutral axis.

No default (Real > 0.0)

J Torsional constant.

(Real > 0.0)

K1, K2 Area factor for shear.

Default = 0.0 (Real)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. The X-axis of the beam is always along the line connecting G1 and G2. The Z-axis of the
beam is determined based on the X-axis and the Y-axis provided by G3/X1, Y1, and Z1.

Altair Engineering OptiStruct 13.0 Reference Guide 539

Proprietary Information of Altair Engineering


3. The moments of inertia are defined as follows:

The beam coordinates must be aligned with the principal axes of the cross-section.

4. The transverse shear stiffness in planes 1 and 2 are (K1)AG and (K2)AG, respectively. If
a value of 0.0 is used for K1 and K2, the transverse shear flexibilities are set to 0.0 (K1
and K2 are interpreted as infinite).

5. Only MAT1 material definitions may be referenced by this element.

6. This card is represented as a bar2 element in HyperMesh.

540 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CMBEAMM

Bulk Data Entry

CMBEAMM – Beam Element for MBD based on Markers

Description

Defines a beam element for multi-body dynamic solution sequence without reference to a
property entry based on markers.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MBEAMM EID MID M1 M2 L

A I1 I2 J K1 K2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MBEAMM 1 2 123 125 0.0 0.0 1.0 5.0

100.0 833.3 833.3 1485.3

Field Contents

EID Element identification number.

(Integer > 0)

MID Material identification number.

(Integer > 0)

M1 Marker identification number.

(Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 541

Proprietary Information of Altair Engineering


Field Contents

M2 Marker identification number.

(Integer > 0)

L Undeformed length along the X-axis of the beam.

(Real)

A Area of the beam cross-section.

(Real)

I1 Area moment inertia in plane 1 about the neutral axis.

No default (Real > 0.0)

I2 Area moment inertia in plane 2 about the neutral axis.

No default (Real > 0.0)

J Torsional constant.

(Real > 0.0)

K1, K2 Area factor for shear.

Default = 0.0 (Real)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. The X-axis of the markers M1 and M2 should always be along the axis of the beam.

3. The moments of inertia are defined as follows:

The beam coordinates must be aligned with the principal axes of the cross-section.

4. The transverse shear stiffness in planes 1 and 2 are (K1)AG and (K2)AG, respectively. If
a value of 0.0 is used for K1 and K2, the transverse shear flexibilities are set to 0.0 (K1
and K2 are interpreted as infinite).

5. This card is represented as a bar element in HyperMesh.

542 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CMBUSH

Bulk Data Entry

CMBUSH – Bushing Element for MBD

Description

Defines a bushing element without reference to a property entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MBUSH EID G1 G2 X1, G3 Y1 Z1

"K" K1 K2 K3 K4 K5 K6

"B" B1 B2 B3 B4 B5 B6

"P" P1 P2 P3 P4 P5 P6

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MBUSH 4 1 2 1.0 0.0 0.0

K 100 100 100 1 1 1

B 1 1 1 0.1 0.1 0.1

P 0 0 0 0 0 0

Field Contents

EID Element identification number.

(Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 543

Proprietary Information of Altair Engineering


Field Contents

G1 Grid point identification number.

(Integer > 0)

G2 Grid point identification number.

(Integer > 0)

G3 Grid point identification number to optionally supply X1, Y1, and Z1 in


conjunction with G1.

(Integer > 0)

X1, Y1, Z1 Orientation vector of the bushing.

(Real)

K Stiffness specifier.

K1, K2, K3 Translational stiffness.

K4, K5, K6 Rotational stiffness.

B Damping specifier.

B1, B2, B3 Translational damping.

B4, B5, B6 Rotational damping.

P Preload specifier.

P1, P2, P3 Translational preload.

P4, P5, P6 Rotational preload.

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

544 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CMBUSHC

Bulk Data Entry

CMBUSHC – Nonlinear Bushing Element for MBD using Curve

Description

Defines a bushing element without reference to a property entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MBUSHC EID G1 G2 X1, G3 Y1 Z1

"K" K1C ID K2C ID K3C ID K4C ID K5C ID K6C ID

"B" B1C ID B2C ID B3C ID B4C ID B5C ID B6C ID

"P" P1 P2 P3 P4 P5 P6

”KE” K1EID K2EID K3EID K4EID K5EID K6EID

“BE” B1EID B2EID B3EID B4EID B5EID B6EID

KINT BINT

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MBUSHC 4 1 2 1.0 0.0 0.0

K 100 100 100 1 1 1

B 1 1 1 1 1 1

P 0 0 0 0 0 0

Altair Engineering OptiStruct 13.0 Reference Guide 545

Proprietary Information of Altair Engineering


AKIMA AKIMA

Field Contents

EID Element identification number

(Integer > 0)

G1 Grid point identification number.

(Integer > 0)

G2 Grid point identification number.

(Integer > 0)

G3 Grid point identification number to optionally supply X1, Y1, and Z1 in


conjunction with G1.

(Integer > 0)

X1, Y1, Orientation vector of the bushing.


Z1
(Real)

K Stiffness specifier.

K1CID, Translational stiffness curve ID.


K2CID,
K3CID Default = 0 (Integer > 0 or blank)

K4CID, Rotational stiffness curve ID.


K5CID,
K6CID Default = 0 (Integer > 0 or blank)

B Damping specifier.

B1CID, Translational damping curve ID.


B2CID,
B3CID Default = 0 (Integer > 0 or blank)

B4CID, Rotational damping curve ID.


B5CID,

546 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

B6CID Default = 0 (Integer > 0 or blank)

P Preload specifier.

P1, P2, P3 Translational preload.

P4, P5, P6 Rotational preload.

K1EID, Translational stiffness independent variable expression ID.


K2EID,
K3EID Default = 0 (Integer > 0 or blank) implies deflection as the independent
variable

K4EID, Rotational stiffness independent variable expression ID.


K5EID,
K6EID Default = 0 (Integer > 0 or blank) implies deflection as the independent
variable

B1EID, Translational damping independent variable expression ID.


B2EID,
B3EID Default = 0 (Integer > 0 or blank) implies velocity as the independent
variable

B4EID, Rotational damping independent variable expression ID.


B5EID,
B6EID Default = 0 (Integer > 0 or blank) implies velocity as the independent
variable

KINT Stiffness interpolation type (Character: LINEAR, CUBIC, AKIMA).

Default = AKIMA

BINT Damping interpolation type (Character: LINEAR, CUBIC, AKIMA).

Default = AKIMA

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. This card is represented as a spring element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 547

Proprietary Information of Altair Engineering


CMBUSHE

Bulk Data Entry

CMBUSHE – Nonlinear Bushing Element for MBD using Expression Defined in MBVAR

Description

Defines a bushing element without reference to a property entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MBUSHE EID G1 G2 X1, G3 Y1 Z1

"K" K1EID K2EID K3EID K4EID K5EID K6EID

"B" B1EID B2EID B3EID B4EID B5EID B6EID

"P" P1 P2 P3 P4 P5 P6

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MBUSHE 4 1 2 1.0 0.0 0.0

K 100 100 100 1 1 1

B 1 1 1 1 1 1

P 0 0 0 0 0 0

Field Contents

EID Element identification number.

(Integer > 0)

548 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

G1 Grid point identification number.

(Integer > 0)

G2 Grid point identification number.

(Integer > 0)

G3 Grid point identification number to optionally supply X1, Y1, and Z1 in


conjunction with G1.

(Integer > 0)

X1, Y1, Z1 Orientation vector of the bushing.

(Real)

K Stiffness specifier.

K1EID, K2EID, Translational stiffness MBVAR ID.


K3EID
Default = 0 (Integer > 0 or blank)

K4EID, K5EID, Rotational stiffness MBVAR ID.


K6EID
Default = 0 (Integer > 0 or blank)

B Damping specifier.

B1EID, B2EID, Translational damping MBVAR ID.


B3EID
Default = 0 (Integer > 0 or blank)

B4EID, B5EID, Rotational damping MBVAR ID.


B6EID
Default = 0 (Integer > 0 or blank)

P Preload specifier.

P1, P2, P3 Translational preload.

P4, P5, P6 Rotational preload.

Altair Engineering OptiStruct 13.0 Reference Guide 549

Proprietary Information of Altair Engineering


Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. This card is represented as a spring element in HyperMesh.

550 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CMBUSHM

Bulk Data Entry

CMBUSHM – Bushing Element for MBD based on Markers

Description

Defines a bushing element without reference to a property entry based on markers.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MBUSHM EID M1 M2

"K" K1 K2 K3 K4 K5 K6

"B" B1 B2 B3 B4 B5 B6

"P" P1 P2 P3 P4 P5 P6

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MBUSHM 1 12 13

K 100 100 100 1 1 1

B 1 1 1 0.1 0.1 0.1

P 0 0 0 0 0 0

Field Contents

EID Element identification number.

(Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 551

Proprietary Information of Altair Engineering


Field Contents

M1 Marker identification number.

(Integer > 0)

M2 Marker identification number.

(Integer > 0)

K Stiffness specifier.

K1, K2, K3 Translational stiffness.

(Real)

K4, K5, K6 Rotational stiffness.

(Real)

B Damping specifier.

B1, B2, B3 Translational damping.

(Real)

B4, B5, B6 Rotational damping.

(Real)

P Preload specifier.

P1, P2, P3 Translational preload.

(Real)

P4, P5, P6 Rotational preload.

(Real)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

552 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CMBUSHT

Bulk Data Entry

CMBUSHT – Nonlinear Bushing Element for MBD using Table

Description

Defines a bushing element without reference to a property entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MBUSHT EID G1 G2 X1, G3 Y1 Z1

"K" K1TID K2TID K3TID K4TID K5TID K6TID

"B" B1TID B2TID B3TID B4TID B5TID B6TID

"P" P1 P2 P3 P4 P5 P6

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MBUSHT 4 1 2 1.0 0.0 0.0

K 100 100 100 1 1 1

B 1 1 1 1 1 1

P 0 0 0 0 0 0

Field Contents

EID Element identification number.

(Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 553

Proprietary Information of Altair Engineering


Field Contents

G1 Grid point identification number.

(Integer > 0)

G2 Grid point identification number.

(Integer > 0)

G3 Grid point identification number to optionally supply X1, Y1, and Z1 in


conjunction with G1.

(Integer > 0)

X1, Y1, Z1 Orientation vector of the bushing.

(Real)

K Stiffness specifier.

K1TID, K2TID, Translational stiffness TABLEDi ID.


K3TID
Default = 0 (Integer > 0 or blank)

K4TID, K5TID, Rotational stiffness TABLEDi ID.


K6TID
Default = 0 (Integer > 0 or blank)

B Damping specifier.

B1TID, B2TID, Translational damping TABLEDi ID.


B3TID
Default = 0 (Integer > 0 or blank)

B4TID, B5TID, Rotational damping TABLEDi ID.


B6TID
Default = 0 (Integer > 0 or blank)

P Preload specifier.

P1, P2, P3 Translational preload.

P4, P5, P6 Rotational preload.

554 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. This card is represented as a spring element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 555

Proprietary Information of Altair Engineering


CMSMETH

Bulk Data Entry

CMSMETH – Component Mode Synthesis Method Definition

Description

CMSMETH defines the CMS method, frequency upper limit, number of modes, and starting
SPOINT ID to be used in a component mode synthesis solution. The eigenvalue solver is also
specified. In addition, preload as well as loads for reduction and residual vector generation
can be defined. Also, an ASCII file containing CELAS4 and CDAMP3 element data and/or their
corresponding design variable definitions can be generated for DMIG to allow the use of the
component modes in optimization runs.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MSMETH C MSID METHOD UB_FRE NMODES SPID SOLVER AMPFFA SHFSC L


Q CT

UB_FRE NMODES SPID_F GPRC


Q_F _F

Optional continuation lines for preload definition

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PRELOAD SPC ID PLSID

Optional continuation lines for LOAD SET definition

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

LOADSET USETYPE LSID1 LSID2 LSID3

Optional continuation lines for DMIGDV definition

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DMIGDV S/F OUTOPT NMODE DVKUPFAC DVGEUP DVBUP

556 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MSMETH 5 C BN 1000 200 100000

600 100 200000

Field Contents

CMSID CMSMETH identification number.

(Integer > 0)

METHOD Component mode synthesis method to be employed. See comment 2.

No default (Character = CB, CC, CBN, GM, or GUYAN)

UB_FREQ Upper bound frequency for the eigenvalue analysis for the structural part.
If 0.0 or blank, no upper bound is used. See comments 3 and 4.

Default = blank (Real > 0.0, or blank)

NMODES Number of modes to be extracted from structural eigenvalue analysis. If


set to -1 or blank, number of modes is limitless. See comments 3 and 4.

Default = blank (Integer > -1, or blank)

SPID The starting SPOINT ID to be used in DMIG matrix output for the
structural eigenmodes.

No default. See comment 6.

SOLVER The eigenvalue solver. Either blank or LAN for Lanzos. AMSES for
AMSES.

Default = LAN (Character = LAN or AMSES, or blank)

AMPFFACT AMSES Amplification Factor. The substructure modes are solved up to


the frequency of AMPFFACT*V2. Higher values of AMPFFACT will lead to
more accurate results and longer running times. See comment 9.

Default = 5.0 (Real or blank)

SHFSCL For vibration analysis, it is the estimate of the frequency of the first
flexible mode. See comment 12.

Altair Engineering OptiStruct 13.0 Reference Guide 557

Proprietary Information of Altair Engineering


Field Contents

Default = blank (Real or blank)

UB_FREQ_F Upper bound frequency for the eigenvalue analysis for the fluid part. If
0.0 or blank, no upper bound is used. See comments 3 and 4.

Default = blank (Real > 0.0, or blank)

NMODES_F Number of modes to be extracted from fluid eigenvalue analysis. If set to


-1 or blank, number of modes is limitless. See comments 3 and 4.

Default = blank (Integer > -1, or blank)

SPID_F The starting SPOINT ID to be used in DMIG matrix output for the fluid
eigenmodes.

No default. See comment 6.

GPRC Grid participation recovery control.

Allows fluid-structure interface grid shape data (that is the modes


associated with the fluid-structure interface) to be calculated and stored
with the external superelement.

Only applicable when GM (general modal formulation) is input in the


METHOD field and when all boundary degrees of freedom are free
(BNDFREE).

If any boundary degrees of freedom are fixed and GPRC is set to YES, the
program will be terminated with an error.

Default = NO (YES, NO)

PRELOAD PRELOAD flag indicates that a preload will be used in the CMS analysis

SPCID SPC SET ID for the preload

PLSID LOAD SET ID for defining the preload.

LOADSET LOADSET flag indicates that static load sets will be used in CMS analysis.

USETYPE RESVEC/REDLOAD/BOTH defines the use type for the load sets

RESVEC – the load set is used for generating residual vectors to improve
the modal space

REDLOAD – the load set is used for generating reduced loads

BOTH – both RESVEC and REDLOAD options are selected

Default = BOTH (see comment 11)

558 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

LSIDi The load set IDs for generating residual vectors and/or reduced loads.

S/F S – Selects the structural part of the model.

Default = S

DMIGDV DMIGDV flag indicates that an ASCII file containing CELAS4 and CDAMP3
element data and/or their corresponding design variable definitions is
generated for DMIG (see comment 13).

OUTOPT OUTOPT defines how design variable definitions are written for DMIG.
(see comments 13 to 17) If OUTOPT is:

1 – Only CELAS4 and CDAMP3 element data and PDAMP properties (if
any) are written. Design variable definitions are not written.

2 – All data from Option-1 and design variable definitions are written
(Default, see comment 14).

3 – All data from Option-2 and constraint (f1<f2) creation data are
written (see comment 15).

If OUTOPT field is blank then Option-2 is the default.

NMODE NMODE defines the number of design variables for ∆K/∆GE and ∆B in
CELAS4 and CDAMP3 (see comment 18).

If NMODE > 0 then “NMODE” number of design variables will be written to


control the first “NMODE” eigenvalue changes (∆K), damping coefficient
changes (∆GE) and scalar damping value changes (∆B).

If NMODE is not specified (the NMODE field is blank) then as many design
variables as the total number of modes are written.

DVKUPFAC DVKUPFAC is used to determine the upper bound of ∆K (which is


(maximum eigenvalue)*DVKUPFAC). If DVKUPFAC is not specified
(DVKUPFAC field is blank) then it is set to 0.1 by default (See comment
16).

Default: DVKUPFAC=0.1

DVGEUP Upper bound of ∆GE. This applies to all the design variables for ∆GE. If
DVGEUP is not specified (DVGEUP field is blank) then it is set to 2*DVBUP
by default (See comment 16).

Default: DVGEUP=2*DVBUP

DVBUP Upper bound of ∆B. This applies to all the design variables for ∆B. If
DVBUP is not specified (DVBUP field is blank) then it is set to 0.4 by

Altair Engineering OptiStruct 13.0 Reference Guide 559

Proprietary Information of Altair Engineering


Field Contents

default (See comment 16).

Default: DVBUP=0.4

Comments

1. This definition will be ignored unless referenced in the I/O Options section by a CMSMETH
run control.

2. Several methods are available for Component Mode Synthesis, these are: CB, CC, CBN,
GM and GUYAN (see descriptions below).

The first two methods (CB and CC) are used for generating flexible bodies for use with
multi-body dynamics analysis software, such as Altair’s MotionSolve.

The remaining methods (CBN, GM and GUYAN) are used primarily to generate external
superelements (stored in DMIG format) for use in subsequent finite element analyses.

Flexible body methods:

CB – Craig-Bampton formulation

CC – Craig-Chang formulation

External superelement methods:

CBN – Craig-Bampton Nodal formulation

GM – General Modal formulation

GUYAN – GUYAN reduction:

GUYAN is the same as CBN without including structural eigenmodes; when GUYAN is used,
UB_FREQ & NMODES are ignored.

3. UB_FREQ, NMODES, UB_FREQ_F and NMODES_F cannot all be blank. Additionally, when
structural elements are present in the model, UB_FREQ and NMODES cannot both be
blank, and when fluid elements are present in the model, UB_FREQ_F and NMODES_F
cannot both be blank.

4. When UB_FREQ = 0.0 and NMODES = 0, this is a special case where no structural
eigenmodes will be included in CMS mode generation. If both UB_FREQ and NMODES are
specified, lowest NMODES below UB_FREQ will be accepted as structural SPOINTs.
Similarly things are applied to fluid part.

5. If PARAM, EXTOUT, DMIGPCH (or DMGBIN) is defined when using the CB method, then a
DMIG matrix corresponding to the reduced stiffness and mass matrices will be output.
The stiffness and mass corresponding to the eigenmodes will be assigned to the
generated SPOINTs.

6. The SPOINT IDs of the structure and fluid should have distinct IDs. Any fluid SPOINT ID
cannot be in between structural SPOINT IDs.

7. When PARAM,EXTOUT is used to output DMIG matrices, then it is possible to disable the

560 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


output of a flexh3d file by specifying “OUTPUT,H3D,NONE” in the input file.

8. The nodal flexh3d file output from the CBN method can be used as the DMIG input (using
ASSIGN,H3DDMIG). In this way, the model set output in flexh3d file will be recovered as
the interior points of the DMIG matrix in the residual structure run. The displacements of
these interior points will be included in the output.

9. AMPFFACT is used to increase the accuracy of the eigenvalue and eigenvectors at the
expense of slightly longer run times. It is recommended to use higher values of
AMPFFACT for solid structures like engine blocks and suspension components. If
AMPFFACT is not specified by you and the model contains a large number of solid
elements, then the value of AMPFFACT is automatically reset to 10.

10. The mass properties of the super element (Mass, Center of Gravity, and Moments of
Inertia) are written to the H3D file. In the residual run, these mass properties are
included in the mass properties of the structure printed in the .out file.

11. The USETYPE field should always be set to BOTH or blank for flexible body generation
(METHOD=CB or CC, see comment 2).

12. A specification of SHFSCL may improve the performance of a vibration analysis.

13. If you define the DMIGDV optional continuation card, a text file (ASCII)
filename_dmig_dv.inc is created after the run. You can include this file in the original
input deck to study how changes in the eigenvalues/damping of superelements affect the
performance of the residual structure.

14. In addition to the data included in option 1, the ASCII file now also contains design
variable definitions. These design variables can control available eigenvalues, structural
damping, and viscous damping of the superelement. You can set up an optimization
problem by including this file in the original input deck.

15. In addition to the data included in option 2, the ASCII file now includes data required for
the creation of constraints. These constraints ensure that the eigenvalue of the nth
mode is less than the eigenvalue of the (n+1)th mode during optimization.

16. The lower bound of ∆K, ∆B and ∆GE is set such that K, B and GE are always greater than
or equal to zero.

17. The DMIGDV continuation line works only for METHOD = GM (General Modal formulation) in
field 3 of CMSMETH (See comment 2).

18. Where, ∆K, ∆GE and ∆B represent increments/decrements to the eigenvalues (K), damping
coefficients (GE) and scalar damping values (B) respectively. You are required to include
the .h3d file containing the values of K, GE and B using ASSIGN, H3DDMIG.

19. For further information on creating flex bodies for third party software, refer to Coupling
OptiStruct with Third Party Software in the User’s Guide.

20. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 561

Proprietary Information of Altair Engineering


CMSPDP

Bulk Data Entry

CMSPDP – Multi-body Spring Damper Element

Description

Defines a spring damper element without reference to a property entry for multi-body solution
sequence.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MSPDP EID K G1 G2 B L PF TYPE

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MSPDP 3 34.5 223 324 0.0 1.0 TRANS

Field Contents

EID Element identification number.

(Integer > 0)

K Stiffness value.

Default = 0.0 (Real or blank)

G1 Grid point identification number.

(Integer > 0)

G2 Grid point identification number.

(Integer > 0)

562 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

B Damping value.

Default = 0.0 (Real or blank)

L Unstretched length/angle of spring damper. See comment 4.

Default = 0 (Real > 0.0 or blank)

PF Preload force.

Default = 0 (Real or blank)

TYPE Type

(TRANS or ROT; if blank, default: TRANS)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. The spring damper force is along the line segment connecting the grids G1 and G2.

3. The positive preload force is a stretching force.

4. If the unstretched length/angle of spring damper field (L) is blank:

(a) For a translational spring, OptiStruct calculates the length between the two grid
points (G1, G2) of the spring damper for the value of L.

(b) For a rotational spring, L is set to 0.0.

5. This card is represented as a spring element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 563

Proprietary Information of Altair Engineering


CMSPDPC

Bulk Data Entry

CMSPDPC – Nonlinear Multi-body Spring Damper Element using Curve

Description

Defines a spring damper element without reference to a property entry for multi-body solution
sequence.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MSPDPC EID KC ID G1 G2 BC ID L PF TYPE

KINT KEID BINT BEID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MSPDPC 3 34 223 324 0 1.0 TRANS

AKIMA 1

Field Contents

EID Element identification number.

(Integer > 0)

KCID Stiffness curve ID.

Default = 0 (Integer > 0 or blank)

G1 Grid point identification number.

(Integer > 0)

564 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

G2 Grid point identification number.

(Integer > 0)

B Damping Curve ID.

Default = 0 (Integer > 0 or blank)

L Unstretched length of spring damper.

Default = 0 (Real > 0.0 or blank)

PF Preload force.

Default = 0 (Real or blank)

TYPE Type.

(TRANS or ROT; if blank, default: TRANS)

KINT Stiffness Interpolation type (Character: LINEAR, CUBIC, AKIMA).

Default = AKIMA

KEID MBVAR ID for independent variable ID for stiffness.

Default = Deflection (Integer > 0 or blank)

BINT Damping Interpolation type (Character: LINEAR, CUBIC, AKIMA).

Default = AKIMA

BEID MBVAR ID for independent variable ID for damping.

Default = Velocity (Integer > 0 or blank)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. The spring damper force is along the line segment connecting the grids, G1 and G2.

3. The positive preload force is a stretching force.

4. This card is represented as a spring element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 565

Proprietary Information of Altair Engineering


CMSPDPE

Bulk Data Entry

CMSPDPE – Nonlinear Multi-body Spring Damper Element using Expression defined in MBVAR

Description

Defines a spring damper element without reference to a property entry for multi-body solution
sequence.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MSPDPE EID KEID G1 G2 BEID L PF TYPE

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MSPDPE 3 3 223 324 4 1.0 TRANS

Field Contents

EID Element identification number.

(Integer > 0)

KEID MBVAR ID for stiffness expression.

Default = 0 (Integer > 0 or blank)

G1 Grid point identification number.

(Integer > 0)

G2 Grid point identification number.

(Integer > 0)

566 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

BEID MBVAR ID for Damping expression.

Default = 0 (Integer > 0 or blank)

L Unstretched length of spring damper.

Default = 0 (Real > 0.0 or blank)

PF Preload force.

Default = 0 (Real or blank)

TYPE Type.

(TRANS or ROT; if blank, default: TRANS)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. The spring damper force is along the line segment connecting the grids G1 and G2.

3. The positive preload force is a stretching force.

4. This card is represented as a spring element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 567

Proprietary Information of Altair Engineering


CMSPDPM

Bulk Data Entry

CMSPDPM – Multi-body Spring Damper Element based on Marker

Description

Defines a spring damper element without reference to a property entry for multi-body solution
sequence based on marker.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MSPDPM EID K M1 M2 B L PF TYPE

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MSPDPM 3 34.5 223 324 0.0 1.0 TRANS

Field Contents

EID Element identification number.

(Integer > 0)

K Stiffness value.

Default = 0.0 (Real or blank)

M1 Marker identification number.

(Integer > 0)

M2 Marker identification number.

(Integer > 0)

568 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

B Damping value.

Default = 0.0 (Real or blank)

L Unstretched length of spring damper.

Default = 0 (Real > 0.0 or blank)

PF Preload force.

Default = 0 (Real or blank)

TYPE Type.

(TRANS or ROT; if blank, default: TRANS)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. The spring damper force is along the line segment connecting the marker M1 and M2.

3. The positive preload force is a stretching force.

4. This card is represented as a spring element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 569

Proprietary Information of Altair Engineering


CMSPDPT

Bulk Data Entry

CMSPDPT – Nonlinear Multi-body Spring Damper Element using Table

Description

Defines a spring damper element without reference to a property entry for multi-body solution
sequence.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MSPDPT EID KTID G1 G2 BTID L PF TYPE

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C MSPDPT 3 3 223 324 4 1.0 TRANS

Field Contents

EID Element identification number.

(Integer > 0)

KTID TABLEDi ID for stiffness.

Default = 0 (Integer > 0 or blank)

G1 Grid point identification number.

(Integer > 0)

G2 Grid point identification number.

(Integer > 0)

570 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

BTID TABLEDi ID for Damping.

Default = 0 (Integer > 0 or blank)

L Unstretched length of spring damper.

Default = 0 (Real > 0.0 or blank)

PF Preload force.

Default = 0 (Real or blank)

TYPE Type.

(TRANS or ROT; if blank, default: TRANS)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. The spring damper force is along the line segment connecting the grids G1 and G2.

3. The positive preload force is a stretching force.

4. This card is represented as a spring element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 571

Proprietary Information of Altair Engineering


CONM1

Bulk Data Entry

CONM1 – Concentrated Mass Element Connection, General Form

Description

Defines a 6x6 mass matrix at a geometric grid point.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ONM1 EID G C ID M11 M21 M22 M31 M32

M33 M41 M42 M43 M44 M51 M52 M53

M54 M55 M61 M62 M63 M64 M65 M66

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ONM1 2 22 2 2.9 6.3

4.8 28.6

28.6 28.6

Field Contents

EID Unique element identification number.

(Integer > 0)

G Grid point identification number.

(Integer > 0)

572 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

CID Coordinate system identification number for the mass matrix.

(Integer > 0)

Mij Mass matrix values.

(Real)

Comments

1. This card is represented as a mass element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 573

Proprietary Information of Altair Engineering


CONM2

Bulk Data Entry

CONM2 – Concentrated Mass Element Connection, Rigid Body Form

Description

Defines a concentrated mass at a grid point of the structural model.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ONM2 EID G C ID M X1 X2 X3

I11 I21 I22 I31 I32 I33

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ONM2 2 15 49.7

16.2 16.2 7.8

Field Contents

EID Unique element identification number.

No default (Integer > 0)

G Grid point identification number.

No default (Integer > 0)

CID Coordinate system identification number.

Default = 0 (Integer > -1)

574 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

M Mass value.

No default (Real)

X1, X2, X3 Offset distance from the grid point to the center of gravity of the mass
in the coordinate system defined by CID, unless CID = -1, in which case
X1, X2, and X3 are the coordinates (not offsets) of the center of gravity
of the mass in the basic coordinate system.

Iij Mass moments of inertia measured at the mass c.g.

If CID is zero, then Iij is defined in the basic coordinate system.

If CID > 1, then Iij refers to the local coordinate system.

If CID is -1, then Iij refers to the basic coordinate system.

Default = 0.0 (Real)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. If the continuation is omitted, all rotary inertia is assigned zero values.

3. The form of the inertia matrix about its c.g. is taken as:

where M =

Altair Engineering OptiStruct 13.0 Reference Guide 575

Proprietary Information of Altair Engineering


and X1, X2, and X3 are components of distance from the c.g. The negative signs for the
off-diagonal terms are supplied by the program.

4. If CID = -1, then the offsets are computed internally as the difference between the grid
point location and X1, X2, and X3. The grid points may be defined in a local coordinate
system, in which case the values of must be in a coordinate system that parallels the
basic coordinate system.

5. If CID > 0, then X1, X2, and X3 are defined by a local Cartesian system, even if CID
references a spherical or cylindrical coordinate system.

6. This card is represented as a mass element in HyperMesh.

576 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CONNECT

Bulk Data Entry

CONNECT – Connects two parts

Description

The CONNECT bulk data entry can be used to define equivalence for all degrees of freedom of
grid points of two different parts within a specified tolerance. The tolerance is defined as the
maximum distance between two grid points within which equivalence is allowed. Two formats
can be used to either select all grid points or a few grid points for equivalence.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ONNEC T name_a name_b tol

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ONNEC T C yl_Head Gaskt 0.01

Alternate Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ONNEC T name_a name_b tol

GRID GID1 GID2 GID3 ... GIDn

Alternate Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ONNEC T C yl_Head Gaskt 0.01

Altair Engineering OptiStruct 13.0 Reference Guide 577

Proprietary Information of Altair Engineering


GRID 1201 1212 192 115

Field Contents

name_a Name of a part selected for equivalencing. Part “name_a” is the reference
part. All grid points in part “name_a” are considered during the search; if
OptiStruct finds grid points in part “name_b” within the specified maximum
distance (tol), then such grid point pairs are equivalent.

(Character String)

name_b Name of a part selected for equivalencing. All grid points in part “name_a” are
considered during the search; if OptiStruct finds grid points in part “name_b”
within the specified maximum distance (tol), then such grid point pairs are
equivalent.

(Character String)

tol Specifies the numeric value defining the maximum distance between two grid
points to allow equivalence. All grid points in part “name_a” are considered
during the search; if OptiStruct finds grid points in part “name_b” within the
specified maximum distance (tol), then such grid point pairs are equivalent.

(Real > 0.0)

GRID GRID flag indicating that a list of grid point ID’s is to follow. These grid point
locations are used to define locations to search for matching nodes.

GID# Identification numbers of grid points that define locations at which a search
for matching nodes is conducted. GID# do not need to belong to either part
“name_a” or part “name_b”.

(Integer > 0)

Comments

1. Parts can be connected in two different ways, using the CONNECT entry or by using rigid
elements. The RELOC and INSTNCE entries can be used to position the part appropriately
within the full model and the CONNECT entry or rigid elements can be used to connect the
requisite number of grid points of one part to the other.

2. In an alternate form, grid point ID’s can be specified anywhere in the model, it is not
mandatory for a grid point ID to belong to a part. Equivalencing takes place between any
matching grids in both parts if they coincide with the location of any grid in the list.

3. Searches defined by this entry are performed after all parts are located at their final
positions.

578 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CONROD

Bulk Data Entry

CONROD – Rod Element Property and Connection

Description

Defines a rod element without reference to a property entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ONROD EID G1 G2 MID A J C NSM

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ONROD 2 16 17 4 269

Field Contents

EID Unique element identification number.

(Integer > 0)

G1,G2 Grid point identification numbers of connection points.

MID Material identification number. See comment 1.

(Integer > 0)

A Area of the rod.

(Real)

Altair Engineering OptiStruct 13.0 Reference Guide 579

Proprietary Information of Altair Engineering


Field Contents

J Torsional constant.

(Real)

C Coefficient for torsional stress determination.

(Real)

NSM Nonstructural mass per unit length.

(Real)

Comments

1. For structural problems, MID may reference only a MAT1 material entry. For heat transfer
problems, MID may reference only a MAT4 material entry.

C ONROD Element Forces and Moments

2. This card is represented as a rod element in HyperMesh.

580 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CONTACT

Bulk Data Entry

CONTACT – Contact Interface Definition

Description

Defines a contact interface.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ONTAC C TID PID/ SSID MSID MORIENT SRC HDI ADJUST C LEARANC E
T TYPE/ S
MU1

DISC RET

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ONTAC T 5 SLIDE 7 8

N25

Field Contents

CTID Contact interface identification number.

(Integer > 0)

PID Property identification number of a PCONT, PCONTX entry.

(Integer > 0)

TYPE Choose type of contact without pointing to contact property –


respective default property settings will be used. Default settings can be
changed using CONTPRM.

SLIDE – Sliding contact.

Altair Engineering OptiStruct 13.0 Reference Guide 581

Proprietary Information of Altair Engineering


Field Contents

STICK – Contact with stick condition (stick applies to closed contacts


only).

FREEZE – Enforced zero relative displacements on the contact interface


(applies to both closed and open contacts). See comments 5 and 15.

Default = SLIDE (SLIDE, STICK, FREEZE)

MU1 Coefficient of static friction (µs). See comment 6.

(0.0 < Real < 1.0)

SSID Identification number of slave entity. See comments 2 and 14.

(Integer > 0)

MSID Identification number of master entity. See comments 3 and 15.

(Integer > 0)

MORIENT Orientation of contact “pushout” force from master surface. This only
applies to masters that consist of shell elements or patches of grids.
Masters defined on solid elements always push outwards irrespective of
this flag.

OPENGAP – The contact interface is assumed open.

OVERLAP – Slave and master bodies overlap.

NORM – Contact force is oriented along the vector normal to the master
surface.

REVNORM – Contact force is oriented opposite to the default vector


normal to the master surface.

Default = OPENGAP (OPENGAP, OVERLAP, NORM or REVNORM). See


comments 7, 8, and 17.

SRCHDIS Search distance criterion for creating contact condition. When specified,
only slave nodes that are within SRCHDIS distance from master surface
will have contact condition checked.

Default = twice the average edge length on the master surface. For
FREEZE contact, half the average edge length. (Real > 0 or blank)

ADJUST Adjustment of slave nodes onto the master surface at the start of a
simulation.

<NO, AUTO, Real > 0.0, or Integer > 0>

582 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Default = NO.

NO – no adjustment.
AUTO – A real value equal to 5% of the average edge length on the
master surface is internally assigned as the depth criterion (see comment
10).

Real > 0.0 – value of the depth criterion which defines the zone in
which a search is conducted for slave nodes (for which contact elements
have been created). These slave nodes (with created contact elements)
are then adjusted onto the master surface. The assigned depth criterion
is used to define the searching zone in the pushout direction (see
comment 10).
Integer > 0 – identification number of a SET entry with TYPE = “GRID”.
Only the nodes on the slave entity which also belong to this SET will be
selected for adjustment.
Note: See comment 10 for more information.

CLEARANCE Prescribed initial gap opening between master and slave, irrespective of
the actual distance between the nodes (see comment 11).

Default = blank (Real or blank)

DISCRET Discretization approach type for the construction of contact elements.


<N2S, S2S>
Default = N2S.
N2S – node-to-surface discretization
S2S – surface-to-surface discretization

Comments for nonlinear quasi-static analysis

1. If the node-to-surface (DISCRET=N2S) discretization approach is selected, the CONTACT


interface is constructed by searching, for each slave node, a respective facet of the
master surface, which contains the normal projection of the slave and is within SRCHDIS
distance from the slave node. If no master segment with normal projection is found, then
the nearest segment is picked if the direction from slave to master is within a certain
angle (30 degrees) relative to the normal to the master segment. Having found a feasible
master segment for the slave node, a contact element is created of a similar structure as
the CGAPG element (Figure 1).

Altair Engineering OptiStruct 13.0 Reference Guide 583

Proprietary Information of Altair Engineering


Figure 1: C reation of a contact element

If the surface-to-surface (DISCRET=S2S) discretization approach is selected, the


CONTACT interface is constructed by searching, for each facet of the slave surface,
respective facets of the master surface which contain the normal projection of sample
points on the slave facet and is within SRCHDIS distance from the sample points. For a
slave node, a contact element is created with the surrounding slave facets and the
master facets found by projection of the sample points on the slave facets (Figure 2).

Figure 2: C reation of a contact element (surface-to-surface discretization)

2. The slave entity (SSID) always consists of grid nodes. It may be specified as:

a set of grid nodes defined using SET(GRID,..) command.


a surface defined using SURF command (the slave nodes are picked from the
respective nodes of the SURF faces).
a set of elements (shells or solids) defined using SET(ELEM,..) command. Slave nodes
are picked from the respective nodes of the elements in the set. For 3D solids, only
nodes on the surface of the solid body are selected; internal nodes are not considered.

DISCRET = N2S is recommended if the slave entity is a set of grids (nodes) or a set of
solid elements.

3. The master entity (MSID) may be defined as:

a surface defined using SURF command.

584 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


a set of elements (shells or solids) defined using SET(ELEM,..) command. For sets of
3D solids, element faces on the surface are automatically found and selected as
master surface.
4. Prescribing TYPE=STICK is interpreted in OptiStruct as an enforced stick condition - such
contact interfaces will not enter the sliding phase. Of course, the enforced stick only
applies to contacts that are closed. Note that, in order to effectively enforce the stick
condition, frictional offset may need to be turned off (See comment 8 on PCONT).

5. Prescribing TYPE=FREEZE enforces zero relative motion on the contact surface – the
contact gap opening remains fixed at the original value and the sliding distance is forced
to be zero. Also, rotations at the slave node are matched to the rotations of the master
patch. The FREEZE condition applies to all respective contact elements, no matter
whether open or closed.

6. Prescribing MU1 directly on the CONTACT card allows for simplified specification of
frictional contacts. Note that this implies MU2=MU1, unless MU2 is specified explicitly on
the CONTPRM card. Also note that the value of MU1 prescribed on the CONTACT card
must be less than 1.0 – to specify higher values of static coefficient of friction, PCONT
card must be used.

If FRIC is not explicitly defined on the PCONTX/PCNTX# entries, the MU1 value on the
CONTACT or PCONT entry is used for FRIC in the /INTER entries for Geometric Nonlinear
Analysis. Otherwise, FRIC on PCONTX/PCNTX# overwrites the MU1 value on CONTACT/
PCONT.

7. MORIENT defines the master pushout direction, which is the direction of contact force
that master surface exerts on slave nodes.

It is important to note that, in most practical applications, leaving this field blank will
provide correct resolution of contact, irrespective of the orientation of surface normals.
Only in cases of master surfaces defined as shells or patches of grids, and combined with
initial pre-penetration, is MORIENT needed.

By default, MORIENT is ignored for solid elements – it applies only to master surfaces that
consist of shell elements or patches of grids. (Master surfaces defined as faces of solid
elements always push outwards, irrespective of the surface normals, or whether the
contact gap is initially open or closed. See comment 7 for additional options).

a) In default behavior (OPENGAP), the pushout direction is defined using the assumption
that the gap between slave and master is initially open, and the contact condition
should prevent their contact (gap “padding” GPAD from the PCONT card is ignored in
defining the pushout direction – this direction is based strictly on the positions of
master and slave nodes).

The following example shows a typical use of OPENGAP:

Figure 3: Example for the use of OPENGAP

Altair Engineering OptiStruct 13.0 Reference Guide 585

Proprietary Information of Altair Engineering


b) OVERLAP assumes the reverse, namely that the slave and master bodies are already
overlapping and the contact condition should push them apart (this is useful in case of
pre-penetrating models when the entire slave set is pre-penetrating into the master
object).

The following example shows a typical use of OVERLAP:

Figure 4: Example for the use of OVERLAP

c) With the NORM option, the pushout force is oriented along the normal vector to the
master surface. (Note that the surface normal may be reversed relative to the default
normal to a shell element if a FLIP flag is present on the master SURF definition. This
behavior corresponds to that of the reverse normals checkbox on the contactsurfs
panel in HyperMesh). In cases when the slave node does not have a direct normal
projection onto the master surface, and the "shortest distance" projection is used
(GAPGPRJ set to SHORT on the GAPPRM card), the pushout force is oriented along the
shortest distance line, yet with the orientation aligned with the normal vector.

The following example shows a typical use of NORM:

Figure 5: Example for the use of NORM

d) REVNORM creates pushout force reversed relative to the NORM option.

8. By default, MORIENT does not apply to masters that are defined on solid elements – such
masters always push outwards. This can be changed by choosing
CONTPRM,CORIENT,ONALL which extends the meaning of MORIENT to all contact
surfaces. In which case, it should be noted that the default normal is pointing inwards
unless a FLIP flag appears on the master SURF definition for surfaces on solid elements,
making the surface normal point outwards. (When creating contact surfaces in
HyperMesh, this behavior corresponds to that of the reverse normals checkbox on the
contactsurfs panel).

9. Presently one CONTACT element is created for each slave node. This assures reasonably
efficient numerical computations without creating an excessive number of contact
elements. However, this may require special handling in some cases, such as when a
master surface wraps around the slave set. In such cases, switching the role of slave
and master may be recommended. Alternatively, multiple CONTACT interfaces can be

586 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


created in order to cover all possible directions of relative motion (a simplified illustration
is shown in the figure below). Additionally, individual GAP(G) elements can be used to
handle such special situations.

Figure 6: Special case - Master surface wraps around a slave node set

10. The adjustment of slave nodes doesn’t create any strain in the model. If DISCRET=N2S is
selected, it is treated as a change in the initial model geometry. If DISCRET=S2S is
selected, it is treated as a change in the initial contact opening/penetration.

If a node on the slave entity lies outside the projection zone of the master surface, it will
always be skipped during adjustment since no contact element has been constructed for
it.

Contact interface padding will be accounted for during the nodal adjustment. If the
MORIENT field is “OPENGAP” or “OVERLAP” while the GPAD field in the referred PCONT
entry is “NONE” or zero, the nodal adjustment will be skipped, since for “OPENGAP” or
“OVERLAP” there is no way to decide the master pushout direction if slave nodes are
adjusted to be exactly on the master face.

If different contact interfaces involve the same nodes, nodal adjustment definitions are
processed sequentially in the order of identification numbers of the contact interfaces.
Care must be taken to avoid conflicts between the nodal adjustments; otherwise, contact
element errors or lack of compliance may occur.

a) The ADJUST field must be set to “NO” for self-contact.


b) If a real value (the searching depth criterion for adjustment) is input for the ADJUST
field, a searching zone for adjustment is defined. The slave nodes in this searching zone,
for which contact elements have been created, will be adjusted. If ADJUST is larger
than or equal to SRCHDIS, all the slave nodes for which contact elements have been
created, will be adjusted.

Altair Engineering OptiStruct 13.0 Reference Guide 587

Proprietary Information of Altair Engineering


Figure 7: An illustration depicting how ADJUST works.

Depth Criterion

The depth criterion (A non-negative real value for ADJUST) is used to define the searching
zone for adjustment, as shown in Figure 7. This searching zone is created in the pushout
direction up to a distance equal to the value of the ADJUST field. The slave nodes within
the searching zone (with defined contact elements) are then considered for adjustment
based on the rules specified within this comment (Comment 10).

c) If the ADJUST field is set to an integer value (the identification number of a grid SET
entry), the nodes shared by the slave entity and the grid SET will be checked for
contact creation, that is, SRCHDIS will be ignored for these nodes, and then adjusted if
a projection is found. The nodes belonging to the grid SET but not to the slave entity
will be simply ignored.

11. Using CLEARANCE overrides the default contact behavior of calculating initial gap opening
from the actual distance between Slave and Master. CLEARANCE is now equal to the
distance that Slave and Master have to move towards each other in order to close the
contact. Negative value of CLEARANCE indicates that the bodies have initial pre-
penetration.

Warning: If CLEARANCE is used, it is important to correctly restrict the contact zones


and pick search distance SRCHDIS so that only desired Slave-Master pairs are
involved. Using CLEARANCE, all contact elements created on a given
interface, even those where Slaves are geometrically distant from the

588 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


respective Master surface, will be considered to be at given initial gap and
participate in resolving the contact condition.

Note:

1. CLEARANCE cannot be used in conjunction with PID of PCONT entry. In such a case,
clearance must be specified on the PCONT entry.

2. The CLEARANCE field value on the CONTACT entry will be ignored for
ANALYSIS=NLGEOM subcases

Comments for geometric nonlinear analysis (ANALYSIS = NLGEOM subcases)

12. CONTACT models an interface between a master surface and a set of slave grid points. A
grid point can be at the same time as a slave and a master node. Each slave grid point
can impact each master segment; except if it is connected to the impacted master
segment. A grid point can impact on more than one segment. A grid point can impact on
the two sides, on the edges, and on the corners of each segment. The contact uses a
fast search algorithm without limitations.

The main limitations of this interface follow: a) the time step in an explicit analysis is
reduced in case of high impact speed or contacts with small gap; b) the contact may not
work properly if used with a rigid body at high impact speed or rigid body with small gap;
c) the contact does not solve edge to edge contact.

13. Additional control can be applied to the CONTACT definition in geometric nonlinear
subcases through CONTPRM and PCONTX. These definitions are ignored in all other
subcases. A geometric nonlinear subcase is one that has an ANALYSIS = NLGEOM entry
in the subcase definition.

14. The slave entity (SSID) always consists of grid nodes. It may be specified as:

a set of grid nodes defined using SET(GRID,..) command.


a surface defined using SURF command (the slave nodes are picked from the
respective nodes of the SURF faces).
a set of elements (shells or solids) defined using SET(ELEM,..) command. Slave nodes
are picked from the respective nodes of the elements in the set. For 3D solids, only
nodes on the surface of the solid body are selected; internal nodes are not considered.

15. The master entity (MSID) may be defined as:

a surface defined using SURF command.


a set of elements (shells or solids), TYPE = FREEZE is implemented as a TIE kinematic
condition for large deformation subcases.
16. For implicit analysis, modified settings that improve the contact convergence are
recommended. See CONTPRM and PCONTX.

17. This card defined using SET(ELEM,..) command.

Altair Engineering OptiStruct 13.0 Reference Guide 589

Proprietary Information of Altair Engineering


Comment for Contact-based Thermal Analysis

18. Thermal-structural analysis problems involving contact are fully coupled since contact
status changes thermal conductivity. Refer to Contact-based Thermal Analysis in the
User’s Guide for more information.

19. This card is represented as a group in HyperMesh.

590 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CONTPRM

Bulk Data Entry

CONTPRM – Default Contact Properties

Description

Defines the default properties of all contacts and sets parameters that affect all contacts.
The default values set here can be overridden by values explicitly specified on PCONT,
PCONTX, and CONTACT cards.

Note: These defaults do not apply to properties of individual


gap elements that are specified on PGAP cards.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ONTPRM PARAM1 VALUE1 PARAM2 VALUE2 PARAM3 VALUE3 PARAM4 VALUE4

PARAM5 VALUE5

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ONTPR GPAD 0.5 STIFF AUTO MU1 0.3


M

Field Contents

PARAMi Name of parameter.

VALi Value of parameter.

Altair Engineering OptiStruct 13.0 Reference Guide 591

Proprietary Information of Altair Engineering


Parameters for nonlinear quasi-static analysis

Name Values

GPAD “Padding” of master or slave objects to account for additional layers, such
as shell thickness, and so on. This value is subtracted from contact gap
opening as calculated from location of nodes. See comment 1.

Default = THICK (Real or NONE or THICK)

STIFF Relative stiffness of gap. See comment 2.

Default = AUTO (AUTO, SOFT, HARD or Real > 0.0)

MU1 Coefficient of static friction ( s). See comments 3 and 4.

Default = 0.0 (Real > 0.0 or STICK or FREEZE)

MU2 Coefficient of kinetic friction ( k ).

Default = MU1 (0.0 < Real < MU1)

CONTGAP Create a bulk data file that contains internally created node-to-surface
contact elements represented as CGAPG elements. The file name is:
filename_root.contgap.fem. See comment 6.

Default = NO (YES or NO)

CORIENT Indicates whether the master orientation field MORIENT on the CONTACT
card applies to all surfaces or if it excludes solid elements.

Default = ONSHELL (ONSHELL or ONALL)

ONSHELL – MORIENT applies only to contact masters that consist of shell


elements or patches of grids. Master surfaces defined as faces of solid
elements always push outwards, irrespective of initially open or pre-
penetrating contact.

ONALL – MORIENT applies to all contact masters including, in particular,


solid elements.

SFPRPEN Indicates whether initial pre-penetrations are recognized and resolved in


self-contact areas. (This only affects self-contact areas, wherein Master
and Slave belong to the same set or surface).

Default = YES (YES or NO)

YES – Initial self-penetrations are recognized and resolved in self-contact


areas. There is some danger of finding false self-penetrations across
solids thinner than SRCHDIS (See comment 7).

NO – There are no pre-penetrations to be resolved in self-contact areas,

592 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


except maybe minimal intrusions due to meshing, and so on. Any self-
penetrations larger than minimum element size will be ignored in those
areas (See comment 7).

FRICESL Frictional elastic slip – distance of sliding up to which the frictional


transverse force increases linearly with slip distance. Specified in physical
distance units (similar to U0 and GPAD). See comment 8.

• Non-zero value or blank activates respective friction model based


on Elastic Slip Distance.
• Zero value activates friction model based on fixed transverse
stiffness KT.
Default = AUTO (Real > 0.0 or AUTO)

Parameters for geometric nonlinear analysis (ANALYSIS = NLGEOM / IMPDYN /


EXPDYN in subcase)

Name Values

STFAC Interface stiffness scale factor.

Default = 1.0 in implicit analysis

Default = 0.1 in explicit analysis

(Real > 0)

FRIC Coulomb friction.

Default = 0.0 (Real > 0)

GAP Gap for impact activation (See comments 10 and 11).

(Real > 0)

IDEL Flag for node and segment deletion.

Default = 0 (Integer = 0, …, 2)

0 - No deletion.
1 - When all of the elements (shells, solids) associated to one segment are
deleted, the segment is removed from the master side of the interface.
Additionally, non-connected nodes are removed from the slave side of the
interface.
2 - When a shell or a solid element is deleted, the corresponding segment
is removed from the master side of the interface. Additionally, non-
connected nodes are removed from the slave side of the interface.

Altair Engineering OptiStruct 13.0 Reference Guide 593

Proprietary Information of Altair Engineering


INACTI Flag for handling of initial penetrations (See comment 13).

Default as defined by CONTPRM (Integer = 0, …, 5)

0 - No action.
1 - Deactivation of stiffness on nodes.
2 - Deactivation of stiffness on elements.
3 - Change slave node coordinates to avoid small initial penetrations.
4 - Change master node coordinates to avoid small initial penetrations.
5 - Gap is variable with time but initial gap is slightly de-penetrated as
follows:

gap0 = gap - P0 – 0.05*(gap - P0)

Valid in explicit analysis: 0, 1, 2, 3 and 5.

Valid in implicit analysis: 0, 3 and 4.

Invalid entries are ignored.

CORIENT Indicates whether the master orientation field MORIENT on the CONTACT
card applies to all surfaces, or if it excludes solid elements.

Default = ONSHELL (ONSHELL or ONALL)

ONSHELL – MORIENT applies only to contact masters that consist of shell


elements or patches of grids. Master surfaces defined as faces of solid
elements always push outwards, irrespective of initially open or pre-
penetrating contact.

ONALL – MORIENT applies to all contact masters including, in particular,


solid elements.

IFRIC Friction formulation flag (See comment 15).

Default = COUL (Character = COUL, GEN, DARM, REN)

COUL - Static Coulomb friction law.


GEN - Generalized viscous friction law.
DARM - Darmstad friction law.
REN - Renard friction law.

In implicit computation, only IFRIC = COUL is implemented.

IFILT Friction filtering flag (See comment 14).

Default = NO (Character = NO, SIMP, PER, CUTF)

NO - No filter is used.
SIMP - Simple numerical filter.
PER - Standard -3dB filter with filtering period.
CUTF - Standard -3dB filter with cutting frequency.

FFAC

594 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


(0.0 < Real < 1.0)

IFORM Type of friction penalty formulation (See comments 16 and 17).

Default = VISC (Character = VISC, STIFF)

VISC - Viscous (total) formulation.


STIFF - Stiffness (incremental) formulation.

C1, C2, C3, Friction law coefficients.


C4, C5, C6
(Real > 0)

IGNORE Flag to ignore slave nodes if no master segment is found for TIE contact
(See comment 18).

Default = 1 (Integer = 0, 1, 2)

0 - No deletion of slave nodes;


1 - Slave nodes with no master segment found are deleted from the
interface;
2 - Slave nodes with no master segment found are deleted from the
interface; if SRCHDIS is blank, then it would be newly calculated internally.

MTET10 Flag for second order CTETRA as contact master surface.

Default = 0 (Integer = 0, 1)

0 - TETRA 10 is degenerated on the surface (middle nodes are removed


from contact);
1 - Four triangular segments are used on each tetra face.

The following entries are relevant for explicit analysis only.

ISYM Flag for symmetric contact.

Default = SYM (Character = SYM, UNSYM)

SYM – Symmetric contact.

UNSYM – Master-slave contact.

If SSID defines a grid set, the contact is always a master-slave contact.

IEDGE Flag for edge generation from slave and master surfaces.

Default = NO (Character = NO, ALL, BORD, FEAT)

NO – No edge generation.

ALL – All segment edges are included.

BORD – External border of slave and master surface is used.

Altair Engineering OptiStruct 13.0 Reference Guide 595

Proprietary Information of Altair Engineering


FEAT – External border as well as features defined by FANG are used.

FANG Feature angle for edge generation in degrees (Only with IEDGE = FEAT).

Default = 91.0 (Real > 0)

IGAP Flag for gap definition.

Default = CONST (Character = CONST, VAR)

CONST - Gap is constant and equal to GAP (See comments 11 and 12).

VAR - Gap is variable (in space, not in time) according to the


characteristics of the impacting surfaces and nodes (See comment 11).

ISTF Flag for stiffness definition (See comment 9).

Default = 0 (Integer = 0, …, 5)

0 - The stiffness is computed according to the master side characteristics.

1 - STIF1 is used as interface stiffness.

2, 3, 4 and 5 - The interface stiffness is computed from both master and


slave characteristics.

STIF1 Interface stiffness (Only with ISTF = 1).

Default = 0.0 (Real > 0)

STMIN Minimum interface stiffness (Only with ISTF > 1).

(Real > 0)

STMAX Maximum interface stiffness (Only with ISTF > 1).

Default = 1030 (Real > 0)

IBC Flag for deactivation of boundary conditions at impact.

(Character = X, Y, Z, XY, XZ, YZ, XYZ)

VISS Critical damping coefficient on interface stiffness.

Default = 0.05 (Real > 0)

VISF Critical damping coefficient on interface friction.

Default = 1.0 (Real > 0)

BMULT Sorting factor.

Default = 0.20 (Real > 0)

596 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments for quasi-static analysis

1. The initial gap opening is calculated automatically based on the relative location of slave
and master nodes (in the original, undeformed mesh). To account for additional material
layers covering master or slave objects (such as half of shell thickness), the GPAD entry
can be used. GPAD option THICK automatically accounts for shell thickness on both sides
of the contact interface (this also includes the effects of shell element offset ZOFFS or
composite offset Z0).

2. Option STIFF=AUTO determines the value of normal stiffness for each contact element
using the stiffness of surrounding elements. Additional options SOFT and HARD create
respectively softer or harder penalties. SOFT can be used in cases of convergence
difficulties and HARD can be used if undesirable penetration is detected in the solution.

3. Prescribing MU1=STICK is interpreted in OptiStruct as an enforced stick condition - such


contact interfaces will not enter the sliding phase. Of course, the enforced stick only
applies to contacts that are closed.

4. Prescribing MU1=FREEZE enforces zero relative displacements on the contact surface –


the contact gap opening remains fixed at the original value and the sliding distance is
zero. The FREEZE condition applies to all slave nodes, no matter whether their initial gap
is open or closed.

5. This card is represented as a control card in HyperMesh.

6. The file filename_root.contgap.fem, produced using the CONTGAP parameter, can be


imported into HyperMesh in order to visualize internally created node-to-surface contact
elements (now converted to GAPG entities). Note that during optimization, this file shows
node-to-surface contact elements for the latest optimization iteration. In order to
correctly visualize this configuration in HyperMesh for shape optimization problems, the
FEA mesh shape needs to be updated by applying "Shape change" results.

Furthermore, if GAPPRM,HMGAPST,YES is activated together with


CONTPRM,CONTGAP,YES, then the gap status command file,
filename_root.HM.gapstat.cmf, will also include the open/closed status of these
additional GAPG’s that represent node-to-surface contact elements. For correct
visualization of their status in HyperMesh, file filename_root.contgap.fem needs to be
imported before running the gap status command file.

7. The CONTACT capability in NLSTAT solution is designed to correctly resolve initial pre-
penetration, such as happens in press fit, and so on. This usually works reliably with
correct identification of Master and Slave surfaces. However, in some cases users create
contact surfaces by property for convenience, which results in contact surfaces
enveloping the entire solid bodies. Also, sometimes the Slave and Master receive the
same ID, which is known as self-contact (and is not a recommended practice, in spite of
the convenience factor). In such cases, it is possible to encounter false self-
penetrations, as illustrated below:

Altair Engineering OptiStruct 13.0 Reference Guide 597

Proprietary Information of Altair Engineering


In the case above, the Slave node will be identified as if pre-penetrating the Master face,
while in reality it is on the other side of the same solid body. The result from nonlinear
CONTACT solution will be such that this portion of the body will be “squeezed” to have
practically zero thickness, with very high stresses obviously resulting.

Apart from correctly identifying potential Slave and Master sets, a possible remedy to
avoid such situations is to make sure that SRCHDIS is smaller than minimum thickness of
the solid bodies which are enveloped by self-contacting surfaces.

An alternative, viable when there are no actual pre-penetrations in the problem, is to


choose SFPRPEN = NO, which will ignore initial pre-penetrations on self-contacting
surfaces (some minor pre-penetrations due to variations of nodal positions will still be
correctly resolved – up to the minimum element size on the respective contact surfaces).

Note that SFPRPEN affects only surfaces that actually have self-penetration, as in a case
where the Slave Node and Master Face belong to the same contact set or surface. On
properly defined, disjoint Slave and Master surfaces, the initial pre-penetrations will be
resolved irrespective of this parameter.

8. Effective in Release 12.0, two models of friction are available in nonlinear analysis:

(a) Model based on fixed slope KT (previously existing),


(b) Model based on Elastic Slip Distance FRICESL (introduced in v12.0 and current default).

This latter model typically shows better performance in solution of frictional problems
thanks to more stable handling of transitions from stick to slip. Key differences between
the two available models are illustrated in the figure below (F 1 and F 2 represent two
different values of normal force F x ):

598 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


C omparison of the two available friction models for contact elements.

Model (a), based on fixed stiffness KT, is relatively simple, yet has certain drawback in
modeling nonlinear friction. Namely, in Coulomb friction the frictional resistance depends
upon normal force. Using fixed KT will predict different range of stick/slip boundary for
different normal forces, and thus may qualify the same configuration as stick or slip,
depending on normal force.
Model (b), based on Elastic Slip Distance, provides unique identification of stick or slip
and generally performs better in solution of problems with friction. This model does
require prescribing elastic slip distance FRICESL – for contact interfaces this value is
determined automatically as 0.5% of typical element size on all Master contact
surfaces.
The model (b), which is currently the default, is recommended for solution of nonlinear
problems with friction. For backwards compatibility, the model based on fixed KT can be
activated by prescribing FRICESL=0 on PCONT or CONTPRM card.

Comments for geometric nonlinear analysis (ANALYSIS = NLGEOM / IMPDYN / EXPDYN


in subcase)

9.
and/or the slave segment stiffness Ks.

The master stiffness is computed from Km = STFAC * B * S * S/V for solids, Km = 0.5 *
STFAC * E * t for shells as well as when the master segment is shared by a shell and
solid.

The slave stiffness is an equivalent nodal stiffness computed as Ks = STFAC * B * V-3 for
solids, Ks = 0.5 * STFAC * E * t for shells.

In these equations, B is the Bulk Modulus, S is the segment area, E is the modulus of
elasticity, t is shell thickness, and V is the volume of a solid. There is no limitation to the
value of stiffness factor (but a value larger than 1.0 can reduce the initial time step).

ISTF = 0, the interface stiffness K = Km

ISTF > 1, the interface stiffness is then K = max (STMIN, min (STMAX, K1)) with

ISTF = 2, K1 = 0.5 * (Km + Ks)

Altair Engineering OptiStruct 13.0 Reference Guide 599

Proprietary Information of Altair Engineering


ISTF = 3, K1 = max (Km, Ks)

ISTF = 4, K1 = min (Km, Ks)

ISTF = 5, K1 = Km * Ks / (Km + Ks)

10. In an implicit analysis, the contact stiffness plays a very important role in convergence.
ISTF = 4 (which takes the minimum of master and slave stiffness’s for contact) is
recommended. This is because the penalty contact force will be balanced with the
internal force of the deformable impacted part. That means the stiffness near the
effective stiffness one will converge easier than a higher one.

For small initial gaps in implicit analysis, the convergence will be more stable if a GAP is
defined that is larger than the initial gap.

In implicit analysis, sometimes a stiffness with scaling factor reduction (for example:
STFAC = 0.01) or reduction in impacted thickness (if rigid one) might reduce unbalanced
forces and improve convergence, particularly in shell structures under bending where the
effective stiffness is much lower than membrane stiffness; but it should be noted that too
low of a value could also lead to divergence.

11. The default for the constant gap (IGAP = CONST) is the minimum of

t, average thickness of the master shell elements;


l/10, l – average side length of the master solid elements;
lmin/2, lmin – smallest side length of all master segments (shell or solid).
12. The variable gap (IGAP = VAR) is computed as gs + gm

with:

gm - master element gap with


gm = t/2, t: thickness of the master element for shell elements.

gm = 0 for solid elements.

gs - slave node gap:

gs = 0 if the slave node is not connected to any element or is only connected to solid or
spring elements.

gs = t/2, t - largest thickness of the shell elements connected to the slave node.

and beam elements, with S being the cross-section of the element.

If the slave node is connected to multiple shells and/or beams or trusses, the largest
computed slave gap is used.

The variable gap is always at least equal to GAPMIN.

13. INACTI = 3, 4 are only recommended for small initial penetrations and should be used with
caution because:

the coordinate change is irreversible.


it may create other initial penetrations if several surface layers are defined in the
interfaces.

600 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


it may create initial energy if the node belongs to a spring element.

INACTI = 5 works as follows:

14.
the tangential friction forces are smoothed using a filter:

F T = α * F'T + (1 - α) * F'T -1

where,

F T - Tangential force

F'T - Tangential force at time t

F'T - 1 - Tangential force at time t-1

α - filtering coefficient

IFILT = SIMP – α = FFAC

IFILT = PER – α = 2π dt/FFAC, where dt/T = FFAC, T is the filtering period

IFILT = CUTF – α = 2π * FFAC * dt, where FFAC is the cutting frequency

15. IFRIC defines the friction model.

IFRIC = COUL – Coulomb friction with F T < * F N with = FRIC

For IFRIC is not COUL, the friction coefficient is set by a function ( = (p, V)), where p is
the pressure of the normal force on the master segment and V is the tangential velocity
of the slave node.

The following formulations are available:

IFRIC = GEN - Generalized viscous friction law

= Fric + C1 * p + C2 * V + C3 * p * V + C4 * p2 + C5 * V2

IFRIC = DARM - Darmstad law

= C1 e(C 2 V ) p2 + C3 e(C 4 V ) p + C5 e(C 6 V )

Altair Engineering OptiStruct 13.0 Reference Guide 601

Proprietary Information of Altair Engineering


IFRIC = REN - Renard law

The first critical velocity Vcr1


than the second critical velocity Vcr2 (C5 < C6).

The static friction coefficient C1 and the dynamic friction coefficient C2 must be lower
than the maximum friction C3 (C1 < C3 ) and C2 < C3 ).

The minimum friction coefficient C4 , must be lower than the static friction coefficient
C1 and the dynamic friction coefficient C2 (C4 < C1 and C4 < C2 ).

16. IFROM selects two types of contact friction penalty formulation.

The viscous (total) formulation (IFORM = VISC) computes an adhesive force as

F adh = VISF * Sqrt(2Km) * VTF T = min (µF N, F adh)

The stiffness (incremental) formulation (IFORM = STIFF) computes an adhesive force as

F adh = F Told + ∆F T

∆F T = K * VT * dt

602 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


F Tnew = min (µF N, F adh )

17. For nonlinear implicit contact with friction, the stiffness formulation (IFORM = STIFF) is
recommended.

18. If IGNORE = 1 or 2, the slave nodes without a master segment found during the searching
are deleted from the interface.

If IGNORE = 1 and SRCHDIS is blank, then the default value of the distance for searching
closest master segment is the average size of the master segments.

If IGNORE = 2 and SRCHDIS is blank, then the distance for searching closest master
segment is computed as follows for each slave node:

d1 = 0.6 * (T s + T m)

d2 = 0.05 * T md

SRCHDIS = max(d1, d2 )

where,

T s is the thickness of the element connected to the slave node, for solids T s = 0.0

T m is the thickness of master segment, for solids T m = Element volume / Segment area

T md is the master segment diagonal

19. This card is represented as a control card in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 603

Proprietary Information of Altair Engineering


CONTX11

Bulk Data Entry

CONTX11 – Edge to Edge or Line to Line Contact Interface Definition for Geometric Nonlinear
Analysis

Description

Defines a edge to edge or line to line contact interface.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ONTX11 C TID PID SLID MLID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ONTX11 5 10 7 8

Field Contents

CTID Contact interface identification number.

(Integer > 0)

PID Property identification number of a PCONT entry. See comment 2.

(Integer > 0)

SLID Identification number of slave LINE entity. See comments 3 and 4.

(Integer > 0)

MLID Identification number of master LINE entity. See comments 3 and 4.

(Integer > 0)

604 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. CONTX11 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

2. The property of CONTX11(PID) only can be defined by PCONT and its extended card
PCNTX11.

3. CONTX11 defines contact interface type 11, it describes the edge to edge or line to line
interface. This interface simulates impact between lines, a line can be a beam or truss
element or a shell edge or spring elements. The interface properties are:

impacts occur between a master and a slave line;


a slave line can impact on one or more master lines;
a line can belong to the master and the slave side. This allows self impact;
this interface can be used in addition to the interface type 7 PCNTX7 to solve the
edge to edge limitation of interface type 7.
4. The slave line entity SLID and master line set entity MLID must be defined via LINE:

a set of edges or lines of 1-D, 2-D or 3-D elements;


a set of elements (bars, beams, springs or shells), defined using SET(ELEM,...)
command;
5. This card is represented as a group in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 605

Proprietary Information of Altair Engineering


CONV

Bulk Data Entry

CONV – Free Convection

Description

Defines a free convection boundary condition for heat transfer analysis through connection to
a surface element (CHBDYE card).

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ONV EID PC ONID TA

Field Contents

EID CHBDYE surface element identification number.


No default (Integer > 0)

PCONID Convection property identification number of a PCONV card.


No default (Integer > 0)

TA Ambient points used to specify ambient temperature.


No default (Integer > 0)

Comments

1. The basic exchange relationship is expressed as:

q = H * (T - TAMB)
Where, H is the free convection heat transfer coefficient specified on a MAT4 card
referred by a PCONV card, T is the grid temperature, and TAMB is the ambient
temperature.

2. CONV is used with a CHBDYE card having the same EID.

3. In linear steady-state heat transfer analysis, ambient temperature is specified by SPC of


the TA point.

4. This card is represented as a slave element in HyperMesh.

606 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CORD1C

Bulk Data Entry

CORD1C – Cylindrical Coordinate System Definition, Form 1

Description

This entry defines a cylindrical coordinate system using three grid points. The first point is
the origin, the second lies on the Z-axis, and the third lies in the X-Z plane (see Figure 1).

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ORD1C C ID G1 G2 G3 C ID G1 G2 G3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ORD1C 3 16 32 19

Field Contents

CID Unique coordinate system identification number.

(Integer > 0)

G1, G2, G3 Grid point identification numbers of points used to uniquely define the
cylindrical coordinate system (see Figure 1).

Altair Engineering OptiStruct 13.0 Reference Guide 607

Proprietary Information of Altair Engineering


Figure 1: Defining a C ylindrical C oordinate System (C ID) using grid points G1, G2 and G3.

Comments

1. Coordinate system identification numbers (CID) on all CORD1R, CORD1C, CORD1S,


CORD2R, CORD2C, CORD2S, CORD3R, and CORD4R entries must all be unique.

2. A duplicate identification number is allowed if the CID and GID are identical and the
coordinates are within the value set by PARAM, DUPTOL (see Guidelines for Bulk Data
Entries for further information).

3. The three points G1, G2, G3 must be non-collinear. Non-collinearity is checked by the
geometry processor.

4. The location of a grid point (P in Figure 1) in this cylindrical coordinate system is given by
(R, θ, and Z) where, θ is measured in degrees.

5. The displacement coordinate directions at P are dependent on the location of P (ur, uθ,
and uz) as shown in Figure 1. The displacements in all three of these directions at the
grid point are specified in units of length.

In OptiStruct, the cylindrical and spherical coordinate systems are internally resolved to
entity-position-dependent (example: GRID) rectangular systems. Therefore, when a grid
point is located in a cylindrical system, OptiStruct constructs a rectangular system at
that location for the grid point. The R-direction corresponds to the X-axis, the Z-axis is
the same, and the θ axis is tangential to the X (or R) axis. Now the various degrees of
freedom can be resolved (vis-à-vis constraints) similar to a general rectangular system.
Care must be taken to observe that the internally generated rectangular systems are
dependent on the grid point location in the cylindrical system. So they may be different
for different grid point locations within the same cylindrical system.

608 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


6. Points on the Z-axis should not have their displacement directions defined in this
coordinate system due to ambiguity. In this case, the defining rectangular system is used.

7. A maximum of two coordinate systems may be defined on a single entry.

8. This card is represented as a system in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 609

Proprietary Information of Altair Engineering


CORD1R

Bulk Data Entry

CORD1R – Rectangular Coordinate System Definition, Form 1

Description

This entry defines a rectangular coordinate system using three grid points. The first point is
the origin, the second lies on the Z-axis, and the third lies on the X-Z plane (see Figure 1).

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ORD1R C ID G1 G2 G3 C ID G1 G2 G3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ORD1R 3 16 32 19

Field Contents

CID Unique coordinate system identification number.

(Integer > 0)

G1, G2, G3 Grid point identification numbers of points used to uniquely define the
rectangular coordinate system (see Figure 1).

610 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Figure 1: Defining a Rectangular C oordinate System (C ID) using grid points G1, G2 and G3.

Comments

1. Coordinate system identification numbers on all CORD1R, CORD1C, CORD1S, CORD2R,


CORD2C, CORD2S, CORD3R, and CORD4R entries must all be unique.

2. A duplicate identification number is allowed if the CID and GID are identical and the
coordinates are within the value set by PARAM, DUPTOL (see Guidelines for Bulk Data
Entries for further information).

3. The three points G1, G2, and G3 must be non-collinear. Non-collinearity is checked by
the geometry processor.

4. The location of a grid point (P in Figure 1) in this rectangular coordinate system is given
by (X, Y, and Z).

5. The displacement coordinate directions at P are (Ux , Uv , and Uz) as shown in Figure 1.

6. A maximum of two coordinate systems may be defined on a single entry.

7. In geometric nonlinear analysis, CORD1R is a moving coordinate system. It moves with


GRID points defining the system.

8. This card is represented as a system in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 611

Proprietary Information of Altair Engineering


CORD1S

Bulk Data Entry

CORD1S – Spherical Coordinate System Definition, Form 1

Description

This entry defines a spherical coordinate system using three grid points. The first point is the
origin, the second lies on the polar (Z) axis, and the third lies in the X-Z plane (see Figure 1).

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ORD1S C ID G1 G2 G3 C ID G1 G2 G3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ORD1S 3 16 32 19

Field Contents

CID Unique coordinate system identification number.

(Integer > 0)

G1, G2, G3 Grid point identification number.

612 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Figure 1: Defining a Spherical C oordinate System (C ID) using grid points G1, G2 and G3.

Comments

1. Coordinate system identification numbers on all CORD1R, CORD1C, CORD1S, CORD2R,


CORD2C, CORD2S, CORD3R, and CORD4R entries must all be unique.

2. A duplicate identification number is allowed if the CID and GID are identical and the
coordinates are within the value set by PARAM, DUPTOL (see Guidelines for Bulk Data
Entries for further information).

3. The three points G1, G2, and G3 must be non-collinear. Non-collinearity is checked by
the geometry processor.

4. The location of a grid point (P in Figure 1) in this spherical coordinate system is given by
(R, θ, and ). Where, θ and are measured in degrees.

5. The displacement coordinate directions at P are dependent on the location of P (ur, uθ,
and u ) as shown in Figure 1. The displacements in all three of these directions at the
grid point are specified in units of length.

6. Points on the polar axis may not have their displacement directions defined in this
coordinate system due to ambiguity. In this case, the defining rectangular system is
used.

7. A maximum of two coordinate systems may be defined on a single entry.

8. This card is represented as a system in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 613

Proprietary Information of Altair Engineering


CORD2C

Bulk Data Entry

CORD2C – Cylindrical Coordinate System Definition, Form 2

Description

This entry defines a cylindrical coordinate system using three grid points specified with
respect to a reference coordinate system. The coordinates of the three non-collinear grid
points are used to uniquely define the coordinate system. The first point defines the origin.
The second point defines the direction of the Z-axis. The third lies in the X-Z plane (see
Figure 1).

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ORD2C C ID RID A1 A2 A3 B1 B2 B3

C1 C2 C3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ORD2C 3 -2.9 1.0 0.0 3.6 0.0 1.0

5.2 1.0 -2.9

Field Contents

CID Unique coordinate system identification number.

(Integer > 0)

RID Identification number of a reference coordinate system that is defined


independently from this coordinate system (see comment 7).

Default = 0 (Integer > 0)

614 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

A1,A2,A3 Coordinates of three points in the reference coordinate system (RID). If


B1,B2,B3 RID is blank or 0, then the reference coordinate system is the default
C1,C2,C3 basic coordinate system.

(Real)

Figure 1: Defining a C ylindrical C oordinate System (C ID) using points A, B and C with reference to another
coordinate system (RID).

Comments

1. The three points (A1, A2, A3), (B1, B2, B3), (C1, C2, C3) must be unique and non-
collinear. Non-collinearity is checked by the geometry processor.

2. Coordinate system identification numbers (CID) on all CORD1R, CORD1C, CORD1S,


CORD2R, CORD2C, CORD2S, CORD3R, and CORD4R entries must be unique.

3. A duplicate identification number is allowed if the CID and GID are identical and the
coordinates are within the value set by PARAM, DUPTOL (see Guidelines for Bulk Data
Entries for further information).

4. The location of a grid point (P in Figure 1) in this cylindrical coordinate system is given by
(R, θ, and Z). Where, θ is measured in degrees.

5. The displacement coordinate directions at P are dependent on the location of P (Ur, Uθ,
and Uz) as shown in Figure 1. The displacements in these three directions at the grid
point are specified in units of length.

Altair Engineering OptiStruct 13.0 Reference Guide 615

Proprietary Information of Altair Engineering


In OptiStruct, the cylindrical and spherical coordinate systems are internally resolved to
entity-position-dependent (example: GRID) rectangular systems. Therefore, when a grid
point is located in a cylindrical system, OptiStruct constructs a rectangular system at
that location for the grid point. The R-direction corresponds to the X-axis, the Z-axis is
the same, and the θ axis is tangential to the X (or R) axis. Now the various degrees of
freedom can be resolved (vis-à-vis constraints) similar to a general rectangular system.
Care must be taken to observe that the internally generated rectangular systems are
dependent on the grid point location in the cylindrical system. So they may be different
for different grid point locations within the same cylindrical system.

6. Points on the Z-axis should not have their displacement directions defined in this
coordinate system due to ambiguity.

7. The reference coordinate system (RID) should be independently defined or left blank. If
blank (or 0), the reference coordinate system is the default basic coordinate system. In
such cases, A, B and C are defined with respect to the basic coordinate system.

8. This card is represented as a system in HyperMesh.

616 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CORD2R

Bulk Data Entry

CORD2R – Rectangular Coordinate System Definition, Form 2

Description

The entry defines a rectangular coordinate system by using three grid points. The coordinates
of the three non-collinear grid points are used to uniquely define the coordinate system. The
first point defines the origin. The second defines the direction of the Z-axis. The third point
defines a vector, which, with the Z-axis, defines the X-Z plane (see Figure 1).

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ORD2R C ID RID A1 A2 A3 B1 B2 B3

C1 C2 C3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ORD2R 3 -2.9 1.0 0.0 3.6 0.0 1.0

5.2 1.0 -2.9

Field Contents

CID Unique coordinate system identification number.

(Integer > 0)

RID Identification number of a coordinate system that is defined independently


from this coordinate system (see comment 6).

Default = 0 (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 617

Proprietary Information of Altair Engineering


Field Contents

A1,A2,A3 Coordinates of three points in the reference coordinate system (RID). If


B1,B2,B3 RID is blank or 0, then the reference coordinate system is the default
C1,C2,C3 basic coordinate system.

(Real)

Figure 1: Defining a Rectangular C oordinate System (C ID) using points A, B and C with reference to another
coordinate system (RID).

Comments

1. The three points (A1, A2, and A3), (B1, B2, and B3), and (C1, C2, and C3) must be
unique and non-collinear. Non-collinearity is checked by the geometry processor.

2. Coordinate system identification numbers on all CORD1R, CORD1C, CORD1S, CORD2R,


CORD2C, CORD2S, CORD3R, and CORD4R entries must all be unique.

3. A duplicate identification number is allowed if the CID and GID are identical and the
coordinates are within the value set by PARAM, DUPTOL (see Guidelines for Bulk Data
Entries for further information).

4. The location of a grid point (P in Figure 1) in this rectangular coordinate system is given
by (X, Y, and Z).

5. The displacement coordinate directions at P are (Ux , Uv , and Uz) as shown in Figure 1.

618 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


6. The reference coordinate system (RID) should be independently defined or left blank. If
blank (or 0), the reference coordinate system is the default basic coordinate system. In
such cases, A, B and C are defined with respect to the basic coordinate system.

7. This card is represented as a system in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 619

Proprietary Information of Altair Engineering


CORD2S

Bulk Data Entry

CORD2S – Spherical Coordinate System Definition, Form 2

Description

This entry defines a spherical coordinate system three grid points. The coordinates of the
three non-collinear grid points are used to uniquely define the coordinate system. The first
point defines the origin. The second point defines the direction of the Z-axis. The third lies in
the X-Z plane (see Figure 1).

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ORD2S C ID RID A1 A2 A3 B1 B2 B3

C1 C2 C3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ORD2S 3 -2.9 1.0 0.0 3.6 0.0 1.0

5.2 1.0 -2.9

Field Contents

CID Unique coordinate system identification number.

(Integer > 0)

RID Identification number of a coordinate system that is defined


independently from this coordinate system (see comment 7).

Default = 0 (Integer > 0)

A1,A2,A3 Coordinates of three points in the reference coordinate system (RID). If

620 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

B1,B2,B3 RID is blank or 0, then the reference coordinate system is the default
C1,C2,C3 basic coordinate system.

(Real)

Figure 1: Defining a Spherical C oordinate System (C ID) using grid points A, B and C .

Comments

1. The three points (A1, A2, and A3), (B1, B2, and B3), and (C1, C2, and C3) must be
unique and non-collinear. Non-collinearity is checked by the geometry processor.

2. Coordinate system identification numbers on all CORD1R, CORD1C, CORD1S, CORD2R,


CORD2C, CORD2S, CORD3R, and CORD4R entries must all be unique.

3. A duplicate identification number is allowed if the CID and GID are identical and the
coordinates are within the value set by PARAM, DUPTOL (see Guidelines for Bulk Data
Entries for further information).

4. The location of a grid point (P in Figure 1) in this spherical coordinate system is given by
(R, θ, and ). Where, θ and are measured in degrees.

5. The displacement coordinate directions at P are (ur, uθ, and u ) as shown in Figure 1.
The displacements in all three of these directions at the grid point are specified in units of
length.

Altair Engineering OptiStruct 13.0 Reference Guide 621

Proprietary Information of Altair Engineering


6. Points on the polar axis may not have their displacement directions defined in this
coordinate system due to ambiguity.

7. The reference coordinate system (RID) should be independently defined or left blank. If
blank (or 0), the reference coordinate system is the default basic coordinate system. In
such cases, A, B and C are defined with respect to the basic coordinate system.

8. This card is represented as a system in HyperMesh.

622 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CORD3R

Bulk Data Entry

CORD3R – Rectangular Coordinate System Definition, Form 3

Description

The entry defines a rectangular coordinate system using three grid points. The first point is
the origin, the second lies on the X-axis, and the third lies on the X-Y plane (see Figure 1).

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ORD3R C ID G1 G2 G3 C ID G1 G2 G3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ORD3R 3 16 32 19

Field Contents

CID Unique coordinate system identification number.

(Integer > 0)

G1, G2, G3 Grid point identification numbers of points used to uniquely define the
rectangular coordinate system (see Figure 1).

Altair Engineering OptiStruct 13.0 Reference Guide 623

Proprietary Information of Altair Engineering


Figure 1: Defining a Rectangular C oordinate System (C ID) using grid points G1, G2 and G3.

Comments

1. Coordinate system identification numbers on all CORD1R, CORD1C, CORD1S, CORD2R,


CORD2C, CORD2S, CORD3R, and CORD4R entries must all be unique.

2. A duplicate identification number is allowed if the CID and GID are identical and the
coordinates are within the value set by PARAM, DUPTOL. Refer to Guidelines for Bulk Data
Entries.

3. The three points G1, G2, and G3 must be non-collinear. Non-collinearity is checked by
the geometry processor.

4. The location of a grid point (P in Figure 1) in this rectangular coordinate system is given
by (X, Y, and Z).

5. The displacement coordinate directions at P are (Ux , Uv , and Uz) as shown in Figure 1.

6. A maximum of two coordinate systems may be defined on a single entry.

7. In geometric nonlinear analysis, CORD3R is a moving coordinate system. It moves with


grid points defining the system.

8. The implementation of CORD3R in OptiStruct is different from that of NASTRAN. A CORD3R


coordinate system in OptiStruct can be defined by specifying grid point identification
numbers for the Origin, X-axis and the XY plane, whereas CORD3R in NASTRAN is specified
with reference to the Origin, Z-axis and the XZ plane.

9. This card is represented as a system in HyperMesh.

624 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CORD4R

Bulk Data Entry

CORD4R – Rectangular Coordinate System Definition, Form 4

Description

This entry defines a rectangular coordinate system using three grid points specified with
respect to the basic coordinate system. The coordinates of the three non-collinear grid points
are used to uniquely define the coordinate system. The first point is the origin, the second lies
on the X-axis, and the third lies on the X-Y plane (see Figure 1).

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ORD4R C ID A1 A2 A3 B1 B2 B3

C1 C2 C3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ORD4R 3 -2.9 1.0 0.0 3.6 0.0 1.0

5.2 1.0 -2.9

Field Contents

CID Unique coordinate system identification number.

(Integer > 0)

A1,A2,A3 Coordinates of three points in the basic coordinate system.


B1,B2,B3
C1,C2,C3 (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 625

Proprietary Information of Altair Engineering


Figure 1: C ORD4R definition.

Comments

1. Coordinate system identification numbers on all CORD1R, CORD1C, CORD1S, CORD2R,


CORD2C, CORD2S, CORD3R, and CORD4R entries must all be unique.

2. A duplicate identification number is allowed if the CID and GID are identical and the
coordinates are within the value set by PARAM, DUPTOL (see Guidelines for Bulk Data
Entries for further information).

3. The three points (A1, A2, and A3), (B1, B2, and B3), and (C1, C2, and C3) must be
unique and non-collinear. Non-collinearity is checked by the geometry processor.

4. The location of a grid point (P in Figure 1) in this rectangular coordinate system is given
by (X, Y, and Z).

5. The displacement coordinate directions at P are (Ux , Uv , and Uz) as shown in Figure 1.

6. A maximum of two coordinate systems may be defined on a single entry.

7. This card is represented as a system in HyperMesh.

626 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


COUPLER

Bulk Data Entry

COUPLER – Coupler Definition for Multi-body Solution Sequence

Description

Defines a coupler connecting two or three joints.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C OUPLER C OID JID1 TYPE1 RATIO1 JID2 TYPE2 RATIO2

JID3 TYPE3 RATIO3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C OUPLER 3 1 T 2.0 4 R 1.0

Field Contents

COID Unique coupler identification number.

(Integer > 0)

JIDi Joint identification numbers.

No default (Integer > 0)

TYPEi Type.

No default (TRA or ROT) – See comment 3.

RATIOi Coefficients of the coupler constraint equation.

(Real; Default = 1.0)

Altair Engineering OptiStruct 13.0 Reference Guide 627

Proprietary Information of Altair Engineering


Comments

1. COUPLERs are only valid in a multi-body solution sequence.

2. At least JID1 and JID2 need to be defined.

3. The type is optional if the Joint is revolute or translation. But if the joint is cylindrical,
the type should be set to TRA to denote that the translational motion is coupled or ROT
to specify that the rotational motion is coupled.

628 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CPENTA

Bulk Data Entry

CPENTA – Five-sided Solid Element with six or fifteen grid points

Description

Defines the connections of the CPENTA element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C PENTA EID PID G1 G2 G3 G4 G5 G6

G7 G8 G9 G10 G11 G12 G13 G14

G15

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C PENTA 112 2 3 15 14 4 103 115

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PSOLID property entry.

Default = EID (Integer > 0)

G# Identification numbers of connected grid points.

Default = blank (Integer > 0 or blank)

Altair Engineering OptiStruct 13.0 Reference Guide 629

Proprietary Information of Altair Engineering


Comments

1. Element ID numbers must be unique with respect to all other element ID numbers.

2. The topology of the diagram must be preserved, that is, G1, G2, and G3 define a
triangular face, G1-G4, G2-G5, and G3-G6 each form one edge.

The edge points, G7-G15, are optional. If any of the edge points are present, they all
must be used. The second and third continuation is not needed for the six node version
of this element.

It is recommended that the edge points be placed near the middle of the edge.

C PENTA definition

3. If the user-prescribed node numbering on the bottom and top faces is reversed as
compared to the sequence shown above, then the nodes are renumbered to produce
right-handed orientation of numbering. This is accomplished by swapping nodes G1 with
G3 and G4 with G6. For 15-noded CPENTA, appropriate changes to mid-side node
numbering are also performed. In such cases, the element coordinate system will be built
on the renumbered node sequence.

4. Stresses are output in the material coordinate system. The material coordinate system is
defined on the referenced PSOLID entry. It may be defined as the basic coordinate
system (CORDM = 0), a defined system (CORDM = Integer > 0), or the element coordinate
system (CORDM = -1).

5. The element coordinate system for the CPENTA element is defined as follows:

630 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


C PENTA element coordinate system

The origin of the element coordinate system is located at the mid-point of a straight line
from G1 to G4.

The element z-axis corresponds to the average of the vector connecting the centroid of
triangular face G1-G2-G3 to the centroid of the triangular face G4-G5-G6 and the normal
vector of the mid-plane (the plane on which the mid-points of the straight lines G1-G4,
G2-G5, and G3-G6 lie). The positive sense of the z-axis is toward the triangular face G4-
G5-G6.

The element y-axis is perpendicular to the element z-axis and lies on the plane created by
the element z-axis and the line connecting the origin and the mid-point of a straight line
from G3 to G6. The positive sense of the y-axis is toward the straight line from G3 to G6.

The element x-axis is the cross product of the element y-axis and the element z-axis.

6. This card is represented as a penta6 or penta15 element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 631

Proprietary Information of Altair Engineering


CPYRA

Bulk Data Entry

CPYRA – Five-sided Solid Element with five or thirteen grid points

Description

Defines the connections of the PYRA solid element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C PYRA EID PID G1 G2 G3 G4 G5 G6

G7 G8 G9 G10 G11 G12 G13

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C PYRA 71 4 3 4 5 6 7

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PSOLID property entry.

Default = EID (Integer > 0)

G# Grid point identification numbers of connection points.

Default = blank (Integer > 0 or blank)

632 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. Grid points G1,…,G4 must be given in consecutive order about the quadrilateral face.

The edge points, G6 through G13, are optional. If any of the edge points are present,
they all must be used. The continuation must not be present for the 5-noded version of
this element.

It is recommended that the edge points be placed near the middle of the edge.

C PYRA definition

3. Stresses are output in the material coordinate system. The material coordinate system is
defined on the referenced PSOLID entry. It may be defined as the basic coordinate
system (CORDM = 0), a defined system (CORDM = Integer > 0), or the element coordinate
system (CORDM = -1).

4. The element coordinate system for the CPYRA element is defined as follows:

Three intermediate vectors R, S, and T are chosen by the following rules:

R Joins the midpoints of the edges from G1 to G4 and G2 to G3.

S Joins the midpoints of the edges from G1 to G2 and G3 to G4.

T Joins the intersection of R and S to G5.

Altair Engineering OptiStruct 13.0 Reference Guide 633

Proprietary Information of Altair Engineering


C PYRA element coordinate system

The origin of the element coordinate system is located at the intersection of the vectors
R and S.

The element z-axis corresponds to the T vector.

The element y-axis is the cross product of the T and R vectors.

The element x-axis is the cross product of the element y-axis and the element z-axis.

5. This card is represented as a pyra5 or pyra13 element in HyperMesh.

634 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CQUAD4

Bulk Data Entry

CQUAD4 – Quadrilateral Element Connection

Description

Defines a quadrilateral plate element (QUAD4) of the structural model. This element uses a 6
degree-of-freedom per node formulation.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C QUAD4 EID PID G1 G2 G3 G4 Theta ZOFFS


or
MC ID

T1 T2 T3 T4

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C QUAD4 111 203 31 74 75 32

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PSHELL, PCOMP, PCOMPP or PHFSHL property


entry.

Default = EID (Integer > 0)

G1,G2,G3,G4 Grid point identification numbers of connection points.

No default (Integers > 0, all unique)

Altair Engineering OptiStruct 13.0 Reference Guide 635

Proprietary Information of Altair Engineering


Field Contents

Theta Material orientation angle in degrees.

Default = 0.0 (Real)

MCID Material coordinate system identification number. The x-axis of this


coordinate system is projected onto the element to define the x-axis of
the material coordinate system. If MCID = 0, it specifies the basic
coordinate system. MCID must be an integer > 0. If blank, Theta =
0.0 is used, unless the material referenced by the element is isotropic
(MAT1) – then MCID = 0 is used. See comments 4, 5, and 6.

Default is Theta = 0.0 (Integer > 0)

ZOFFS Offset from the plane defined by element grid points to the shell
reference plane. See comment 10. Overrides the ZOFFS specified on
the PSHELL entry.

Default = 0.0 (Real or blank)

Ti Thickness of the element at the grid points. Overrides the thickness


specified on the PSHELL entry. If Ti is specified, the average of all four
thicknesses is used as the element thickness.

For defaults: See comments 7 and 9.

(Real > 0.0 or blank)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. Grid points G1 through G4 must be ordered consecutively around the perimeter of the
element.

3. All of the interior angles must be less than 180 degrees.

4. The elemental coordinate system is a bisection definition as depicted in the following


figure:

636 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Elemental coordinate system

5. For H3D and OUTPUT2 output formats, stresses and strains are always output in the
elemental system.

6. For HM, PUNCH and OPTI output formats, stresses and strains are output by default in
the material coordinate system. PARAM, OMID can be set to NO to output results in the
elemental system. For elements with blank Theta/MCID, THETA = 0.0 is assumed, and
the material coordinate system is aligned with side G1-G2 of the shell element. For
elements with prescribed THETA, the material x-axis is rotated from side G1-G2 by angle
THETA. For elements with prescribed MCID, the material system is constructed by
projecting the prescribed MCID onto the plane of the element.

Orientation when Theta (real value) is entered in 8th field

Altair Engineering OptiStruct 13.0 Reference Guide 637

Proprietary Information of Altair Engineering


Orientation when MC ID (integer value) is entered in 8th field

7. If any of the Ti fields are blank, the thickness specified on the PSHELL data will be used
for that node’s thickness. If 0.0 is specified for Ti, then the thickness at that node is
zero.

8. If the property referenced by PID is selected as a region for free-size or size optimization,
then any Ti values defined here are ignored. If you input Ti for elements in the design
space for Topology or Free-Size optimization, the run will error out.

9. If Ti is present, the PID cannot reference PCOMP or PCOMPP data.

10. The shell reference plane can be offset from the plane defined by element nodes by
means of ZOFFS. In this case all other information, such as material matrices or fiber
locations for the calculation of stresses, is given relative to the offset reference plane.
Similarly, shell results, such as shell element forces, are output on the offset reference
plane.

ZOFFS can be input in two different formats:

1. Real:

A positive or a negative value of ZOFFS is specified in this format. A positive value of


ZOFFS implies that the reference plane of each shell element is offset a distance of
ZOFFS along the positive z-axis of its element coordinate system.

2. Surface:

This format allows you to select either “Top” or “Bottom” option to specify the offset
value.

Top:

The top surface of the shell element and the plane defined by the element nodes are
coincident.

This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
property entry referenced by this element. (The sign of the ZOFFS value would depend on
the direction of the offset relative to the positive z-axis of the element coordinate

638 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


system, as defined in the Real section). See Figure 1.

Figure 1: Top option in ZOFFS

Bottom:

The bottom surface of the shell element and the plane defined by the element nodes are
coincident.

This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
property entry referenced by this element. (The sign of the ZOFFS value would depend on
the direction of the offset relative to the positive z-axis of the element coordinate
system, as defined in the Real section). See Figure 2.

Figure 2: Bottom option in ZOFFS

Note that when ZOFFS is used, both MID1 and MID2 must be specified on the PSHELL
entry referenced by this element (otherwise, singular matrices would result).

Offset is applied to all element matrices (stiffness, mass, and geometric stiffness), and to
respective element loads (such as gravity). Hence, ZOFFS can be used in all types of
analysis and optimization. Note, however, that for first order shell elements (CQUAD4 and
CTRIA3), the offset operation does not correct for secondary effects, such as change of
shell area when offset is applied on curved surfaces. Hence, the value of ZOFFS should
be kept within a reasonable percentage (10% - 15%) of the local radius of curvature.
Automatic offset control is available in composite free-size and sizing optimization where
the specified offset values are automatically updated based on thickness changes.

Moreover, while offset is correctly applied in geometric stiffness matrix and hence can be
used in linear buckling analysis, caution is advised in interpreting the results. Without
offset, a typical simple structure will bifurcate and loose stability “instantly” at the critical

Altair Engineering OptiStruct 13.0 Reference Guide 639

Proprietary Information of Altair Engineering


load. With offset, though, the loss of stability is gradual and asymptotically reaches a
limit load, as shown below in figure (b):

Hence, the structure with offset can reach excessive deformation before the limit load is
reached. Note that the above illustrations apply to linear buckling – in a fully nonlinear
limit load simulation, additional instability points may be present on the load path.

11. PHFSHL properties are only valid with an @HYPERFORM statement in the first line of the
input file.

12. This card is represented as a quad4 element in HyperMesh.

640 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CQUAD8

Bulk Data Entry

CQUAD8 – Curved Quadrilateral Shell Element Connection

Description

Defines a curved quadrilateral shell element with eight grid points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C QUAD8 EID PID G1 G2 G3 G4 G5 G6

G7 G8 T1 T2 T3 T4 Theta ZOFFS
or
MC ID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C QUAD8 111 203 20 21 50 51 26 94

95 23 0.125 0.025 0.030 .025 30. .03

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PSHELL, PCOMP or PCOMPP property entry.

Default = EID (Integer > 0)

G1,G2,G3,G4 Grid point identification numbers of connected corner points. Required


data for all four grid points.

No default (Integers > 0, all unique)

Altair Engineering OptiStruct 13.0 Reference Guide 641

Proprietary Information of Altair Engineering


Field Contents

G5,G6,G7,G8 Grid point identification numbers of connected edge points. Cannot be


omitted.

No default (Integer > 0 or blank)

Ti Thickness of the element at the corner grid points G1 through G4. The
thickness of the element with Ti specified will be constant and equal to
an average of T1, T2, T3 and T4.

For defaults: see comment 5.

(Real > 0.0 or blank)

THETA Material orientation angle in degrees. See comment 4.

Default = 0,0 (Real)

MCID Material coordinate system identification number. The x-axis of this


coordinate system is projected onto the element to define the x-axis
of the material coordinate system. If MCID = 0, it specifies the basic
coordinate system. If blank, Theta = 0.0 is used, (See comments 3
and 4).

Default is THETA = 0.0 (Integer > 0)

ZOFFS Offset from the surface of grid points to the element reference plane.
See comment 7. Overrides the ZOFFS specified on the PSHELL entry.

Default = 0.0 (Real or blank)

Comments

1. Element identification numbers should be unique with respect to all other element IDs.

2. Grid points G1 through G8 must be numbered as shown here:

642 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. The element coordinate system is a Cartesian system defined locally for each point ( , ).

It is based on the following rules:


- The plane containing and is tangent to the surface of the element.
- and are obtained by doubly bisecting the lines of constant and .
increases in the general direction of increasing and of .

Altair Engineering OptiStruct 13.0 Reference Guide 643

Proprietary Information of Altair Engineering


4. The orientation of the material coordinate system is defined locally at each interior
integration point by THETA, which is the angle from the line of constant (essentially the
same as the -axis) to the material x-direction (Xmaterial).

If MCID is used in place of THETA, then the local material x-direction (Xmaterial) is
obtained at any point in the element by projection of the x-axis of the prescribed MCID
coordinate system onto the surface of the element at this point. The local z-direction is
aligned with the normal to the surface and the material y-direction (Y material) is
constructed accordingly to produce right-handed local material system X-Y-Zmaterial.

644 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Note that since changes directions throughout the element based on element shape,
the material coordinate system varies similarly. Because of this, an orthotropic or
anisotropic material will cause the CQUAD8's stiffness to be biased by both its shape and
grid ordering. Use the CQUAD4 element if a constant material coordinate system direction
is desired with orthotropic and anisotropic materials.

5. T1, T2, T3, and T4 are optional. If they are not supplied, then the element thickness will
be set equal to the value of T on the PSHELL entry. If 0.0 is specified for Ti, then the
thickness at that node is zero. If Ti’s are supplied, PID cannot reference PCOMP or
PCOMPP data. If the property referenced by PID is selected as a region for Size
optimization, then any Ti values defined here are ignored. If you input Ti for elements in
the design space for Topology or Free-Size optimization, the run will error out.

6. It is required that the midside grid points be located within the middle third of the edge;
that is the interval (0.25, 0.75) excluding the quarter points 0.25 and 0.75. If the edge
point is located at the quarter point, the program may fail with an error or the calculated
stresses will be meaningless.

7. The shell reference plane can be offset from the plane defined by element nodes by
means of ZOFFS. In this case all other information, such as material matrices or fiber
locations for the calculation of stresses, is given relative to the offset reference plane.
Similarly, shell results, such as shell element forces, are output on the offset reference
plane.

ZOFFS can be input in two different formats:

1. Real:

A positive or a negative value of ZOFFS is specified in this format. A positive value of


ZOFFS implies that the reference plane of each shell element is offset a distance of
ZOFFS along the positive z-axis of its element coordinate system.

Altair Engineering OptiStruct 13.0 Reference Guide 645

Proprietary Information of Altair Engineering


2. Surface:

This format allows you to select either “Top” or “Bottom” option to specify the offset
value.

Top:

The top surface of the shell element and the plane defined by the element nodes are
coincident.

This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
property entry referenced by this element. (The sign of the ZOFFS value would depend on
the direction of the offset relative to the positive z-axis of the element coordinate
system, as defined in the Real section). See Figure 1.

Figure 1: Top option in ZOFFS

Bottom:

The bottom surface of the shell element and the plane defined by the element nodes are
coincident.

This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
property entry referenced by this element. (The sign of the ZOFFS value would depend on
the direction of the offset relative to the positive z-axis of the element coordinate
system, as defined in the Real section). See Figure 2.

Figure 2: Bottom option in ZOFFS

Note that when ZOFFS is used, both MID1 and MID2 must be specified on the PSHELL
entry referenced by this element (otherwise, singular matrices would result).

646 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Offset is applied to all element matrices (stiffness, mass and geometric stiffness) and to
respective element loads (such as gravity). Hence, ZOFFS can be used in all types of
analysis and optimization in OptiStruct. Automatic offset control is available in composite
free-size and sizing optimization where the specified offset values are automatically
updated based on thickness changes.

However, while offset is correctly applied in geometric stiffness matrix and hence can be
used in linear buckling analysis, caution is advised in interpreting the results. Without
offset, a typical simple structure will bifurcate and loose stability “instantly” at the critical
load. With offset, though, the loss of stability is gradual and asymptotically reaches a
limit load, as shown below in figure (b):

Hence, the structure with offset can reach excessive deformation before the limit load is
reached. Note that the above illustrations apply to linear buckling – in a fully nonlinear
limit load simulation, additional instability points may be present on the load path.

8. Stresses and strains are output in the local coordinate system identified by and
above.

9. Size optimization of the property referenced by PID is not possible if Ti values are defined
here. If the property referenced by PID is selected as a region for free-size optimization,
then any Ti values defined here are ignored.

10. These 2nd order shell elements do not have normal rotational degrees-of-freedom (often
referred to as "drilling stiffness"). No mass is associated with these degrees-of-freedom.
If unconstrained, massless mechanisms may occur. It is therefore advisable to use
PARAM,AUTOSPC,YES when working with these elements.

11. This card is represented as a quad8 element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 647

Proprietary Information of Altair Engineering


CQUADR

Bulk Data Entry

CQUADR – Quadrilateral Element Connection

Description

CQUADR entry is equivalent to CQUAD4. Unlike other Nastran codes, a 6 degree-of-freedom


per node formulation is used for all shell elements.

Refer to the documentation for the CQUAD4 Bulk Data Entry.

648 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CROD

Bulk Data Entry

CROD – Rod Element Connection

Description

Defines a tension-compression-torsion element (ROD) of the structural model.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ROD EID PID G1 G2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C ROD 12 13 21 23

Field Contents

EID Unique element identification number.

(Integer > 0)

PID Identification number of a PROD property entry.

(Integer > 0; If blank defaults to EID)

G1,G2 Grid point identification numbers of connection points.

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. Only one ROD element may be defined on a single entry.

3. This card is represented as a rod element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 649

Proprietary Information of Altair Engineering


CSEAM

Bulk Data Entry

CSEAM – Seam Weld Element Connection

Description

Define a seam weld connecting two shell surfaces.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SEAM EID PID SMLN C TYPE IDAS IDBS IDAE IDBE

GS GE

Examples

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SEAM 22 3 SEAM1 PSHELL 1 2

7 8

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SEAM 22 3 ELEM 11 12 21 22

7 8

Alternate Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SEAM EID PID SMLN C TYPE IDAS IDBS IDAE IDBE

650 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


XS YS ZS XE YE ZE

Alternate Format Examples

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SEAM 22 3 SEAM1 PSHELL 1 2

0.3 0.4 0.25 0.6 0.4 0.25

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SEAM 22 3 ELEM 11 12 21 22

0.3 0.4 0.25 0.6 0.4 0.25

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PSEAM entry.

No default (Integer > 0)

SMLN Identification of a seam line (See comment 2).

No default (Maximum eight characters)

CTYPE Character string indicating how the connection is defined. Either format
connects up to 3 x 3 quadrilateral shell elements per patch (possibly more
for triangular elements).

For PSHELL type, the connection of surface patch to surface patch is


defined by specifying the property identification numbers.

For ELEM type, the connection of surface patch to surface patch is


defined by specifying element identification numbers.

Altair Engineering OptiStruct 13.0 Reference Guide 651

Proprietary Information of Altair Engineering


Field Contents

IDAS, Used to define the two connecting patches or the start parts of patch A
IDBS and patch B.

If CTYPE="PSHELL", then IDAS and IDBS refer to the property identification


numbers of patch A and patch B.

If CTYPE="ELEM", then IDAS and IDBS refer to the element identification


numbers of patch A and B.

IDAE, Used to define the end parts of patch A and patch B.


IDBE
If CTYPE="PSHELL", IDAE and IDBE could be zero. If they are not zero,
then IDAE and IDBE refer to the property identification numbers of the end
parts of patch A and patch B. They could be used to define a tailored
blank model.

If CTYPE="ELEM", IDAS and IDBS refer to the element identification


numbers of the end parts of patch A and B.

For PSHELL type, Integer >

GS Identification number of a grid point which defines the start location of the
connector.

No default (Integer > 0)

GE Identification number of a grid point which defines the end location of the
connector.

No default (Integer > 0)

XS, YS, Coordinates of point that defines the start location (GS) of the seam weld
ZS in the basic coordinate system.

(Real)

XE, YE, Coordinates of point that defines the end location (GE) of the seam weld in
ZE the basic coordinate system.

(Real)

652 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. CSEAM defines a flexible connection between two surface patches. With all of the
information provided, a fictitious 8-node CHEXA will be generated internally for a CSEAM,
and the eight corner nodes are all constrained by the grids of corresponding shell
elements. Then the element stiffness of this fictitious CHEXA will be transferred to the
corresponding shell grids. The CSEAM element itself does not hold any independent DOF.
See the figure below:

A CSEAM element connects Shell A and Shell B. A fictitious hexa is generated for the
CSEAM, and the corner nodes of the hexa are all constrained by corresponding shell grids.
To have a clear view, only one of this kind of constraint relationship is shown with dotted
lines.

2. In the SMLN entry, a name can be given for the CSEAM element. If one CSEAM's GS or
GE is common to the GS or GE of the other CSEAM and they have the same SMLN, the
two CSEAM elements are regarded as neighbors. For two neighboring CSEAM elements,
the faces of the internally generated CHEXAs will be adjusted to form a single common
face.

A seam line does not have a branch with the same SMLN,

3. The distance between GS and GE is the length of the element. The width of the seam
weld is defined in the PSEAM card as W. It is measured perpendicular to the length and
lies in the plane of Shell A or B.

Altair Engineering OptiStruct 13.0 Reference Guide 653

Proprietary Information of Altair Engineering


4. Building the connectivity for CSEAM.

Since the geometry for finding the correct projection could be various and complicated,
many geometry related checks will be implemented in the following procedure. The
default projection algorithm and checking rules can be modified to some extent via
changing the default value defined in the SWLDPRM card.

To build the connectivity, at first, project GS on Shell A and B; the projection points are
denoted as SA and SB respectively. This is also true for GE, and the projection points are
denoted as EA and EB. SA, SB, EA and EB are also called piercing points. Meanwhile, the
shell elements supporting these piercing points are denoted as EIDSA, EIDSB, EIDEA and
EIDEB.

Take SA as an example. For ELEM type, the program will try to project GS on the user
specified element; if the piercing point falls inside the element, the program will accept it
and move to find the next piercing point. If the piercing point falls outside the element
but within the tolerance defined by PROJTOL in the SWLDPRM card, the program will still
accept it. Otherwise, an error will be issued for this CSEAM element, and the program
continues to process other CSEAM elements. For PSHELL type, the case could be much
more complicated. First, a bunch of shell elements which are the closest ones to GS and
have the user-specified shell property will be selected as candidates. Then project GS on
each of the candidates. If the piercing point falls inside one of the candidates, the
program will accept it and move to find the next one. After looping all the candidates, if
there is no appropriate one to support the piercing point, the tolerance defined by
PROJTOL will be used and all candidates will be searched again. At last, if still no element
is found to support the piercing point, an error will be issued for this CSEAM, and the
program continues to process other CSEAM elements. In this way, all the four piercing
points and elements supporting them are found, or an error is issued.

If GMCHK > 0 (be defined in the SWLDPRM card), various geometry checks will be
implemented at specific steps.

If GMCHK > 0 and GSPROJ > 0.0 (be defined in the SWLDPRM card), the program will
check the angle between the normal vectors of EIDSA and EIDSB, and the angle between
the normal vectors of EIDEA and EIDEB. If the angle is larger than GSPROJ, an error will
be issued for this CSEAM. If GSTOL > 0.0 (be defined in the SWLDPRM card) and one of
the lengths of GS-SA, GS-SB, GE-EA and GE-EB is larger than GSTOL, an error will be
issued. Besides these basic checks, a group of cutout and span checks will be performed
if GMCHK>0.

After the four piercing points are found, the auxiliary points will then need to be located
with the definition of the seam width. Take SA as an example, with the coordinates of
the piercing point, the supporting element EIDSA and the seam weld width W, you can
define the following vector n × GS-GE where n is the normal vector of EIDSA. Through
SA, two points SA1 ' and SA2 ' can be defined along this vector and |SA1 '-SA2 '| = W. SA1 '
and SA2 ' are called the preliminary auxiliary points. For a curved or folded shell patch, the
preliminary points may not lie on the shell surface. Therefore, a second projection is
needed to find the final auxiliary points. Take SA1 ' as an example. First, a group of
candidate elements needs to be collected. They are composed of shell elements
surrounding EIDSA. SA1 ' will be projected on each of the candidates to find the best one
to support the projection point. If no element with the user specified shell property is
found with/without tolerance, elements with different shell property will be supplemented
to the candidate list. After projecting all the eight preliminary auxiliary points on the shell

654 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


surfaces, the number of good auxiliary points will be counted. If all of the eight auxiliary
points and corresponding shell elements are successfully located, the building of the
connectivity for this CSEAM succeeds. Otherwise, GSMOVE defined in the SWLDPRM card
will be implemented to avoid the failure if GSMOVE > 0.

When collecting candidate shell elements which will be used to support the auxiliary
points, the angle between the normal vector of the shell element and the thickness
direction of the fictitious CHEXA will be checked. If the angle is larger than GSPORJ, this
shell element will not be considered as a candidate. If EIDSA, EIDSB, EIDEA or EIDEB fails
the check, a warning message will be issued. For curved or folded shell surface, shell
elements on it have more chances to be eliminated from the candidate list, thus may
possibly induce the failure of locating all auxiliary points. One remedy to this problem is to
increase the value of GSPORJ to include more shell elements into the candidate list.

Various projection points generated in building the connectivity for a CSEAM element.

5. When building the connectivity for CSEAM, if not all eight auxiliary points can be found
and GSMOVE > 0, GS or/and GE will be moved by W/2 and re-projected to avoid the
failure. This often happens near the mesh boundary.

Altair Engineering OptiStruct 13.0 Reference Guide 655

Proprietary Information of Altair Engineering


Both GS and GE are moved by W/2 to find correct projection.

6. For PSHELL type CSEAM, when the GS or GE is close to a folded or curved part of a shell
surface, the program has more chances to fail in locating the correct element to support
the piercing points because of multiple possible choices. In this case, using ELEM type to
directly specify the elements for projection would be a wise alternative.

7. Check whether the CSEAM spans a cutout or spans more than three shell elements on
each shell surface when GMCHK > 0.

Take EIDSA and EIDEA as an example.

If EIDSA = EIDEA, the seam lies on the same element on this surface. This case is
accepted.
EIDEA and they share at least one common grid, it is necessary to do some
checks.
(In the following check, an element called EIDMA is used to assist the check. EIDMA is
located on the same shell surface where EIDSA and EIDEA are located. It shares one of
the common grids shared by EIDSA and EIDEA. EIDMA could be multiple.)

a)If EIDSA and EIDEA share only one common grid but no EIDMA is found, then this case
is rejected.

656 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


This case is rejected.

b)If EIDSA and EIDEA share only one common grid and at least one EIDMA is found, the
number of free edges will be counted. The following cases are considered.

If there are three or more free edges (bold lines), this case is rejected.

Angle check.

Altair Engineering OptiStruct 13.0 Reference Guide 657

Proprietary Information of Altair Engineering


Projection check. M is the middle point of the two free edges' ends.

If there are two free edges, the angle (α) between the free edges will be calculated. If
the angle is larger than CNRAGLI (be defined in the SWLDPRM card), this case is
accepted. If the angle is smaller than CNRAGLI, then you project the mid-point M to
EIDSA, EIDEA and EIDMA, if the projection point falls inside, this case is still accepted. Or
it will be rejected.

If there is only one free edge, this case is accepted.

If there is no free edge, this case is accepted.

658 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


c)If EIDSA and EIDEA share two common grids, that means EIDSA and EIDEA share a
common edge. Before accepting this case, it is still necessary to check the angle or
project the middle point M.

Angle check.

Projection check. M is the middle point of the two free edges' ends.

Compare the angle (α) with CNRAGLO even EIDSA and EIDEA share an edge. If the angle
is larger than CNRAGLI, this case is accepted. If the angle is smaller than CNRAGLI, then
you project the mid-point M to EIDSA and EIDEA, if the projection point falls inside, this
case is still accepted. Or it will be rejected.

elements around them and check how these elements are connected with EIDSA and
EIDEA.
(In the following check, EIDMA is re-defined as an element which shares at least one grid
respectively with EIDSA and EIDEA)

a) If there is no EIDMA, this means the CSEAM element spans more than three elements
in the current shell surface, and this case is rejected.

Altair Engineering OptiStruct 13.0 Reference Guide 659

Proprietary Information of Altair Engineering


This case is rejected.

b) If there are three EIDMA which share edges with both EIDSA and EIDEA, this case is
accepted.

This case is accepted.


c) If there are two EIDMA which share edges with both EIDSA and EIDEA, it is necessary
to check whether the two EIDMA share a common edge or not. If the two EIDMA do
not share a common edge, there is a cutout and this case is rejected.

660 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


If the two EIDMA do not share a common If the two EIDMA share a common edge, this
edge, there is a cutout and this case is case is accepted.
rejected.

Two different cases when there are two EIDMA who share edges with both EIDSA and
EIDEA.

d) If there is only one EIDMA which shares edges with both EIDSA and EIDEA. The check
presented in the following figure needs to be implemented.

Point M is the average of the two piercing points, that is SA and EA. If the projection
from point M on EIDMA falls inside this element, this case is accepted, or it will be
rejected.

e) If there is only one EIDMA which shares one edge with EIDSA and shares a corner with
EIDEA (or shares one corner with EIDSA and shares one edge with EIDEA), the same
check implemented for the last case will be adopted.

Altair Engineering OptiStruct 13.0 Reference Guide 661

Proprietary Information of Altair Engineering


f) If the projection from point M on EIDMA falls inside this element, this case is accepted,
or it will be rejected.

g) If there are two EIDMA and each of them shares an edge with EIDSA or EIDEA and
shares a corner with EIDEA or EIDSA, this case is accepted.

This case is accepted.

h) If there is only EIDMA which shares only corners but no edge with EIDSA or EIDEA, this
case is rejected.

These two cases are rejected. For the one on the right, although there is no cutout on
the surface, but EIDMA is not fully constrained (only two corners are constrained) by the
CSEAM. Therefore, this case is still rejected.

For EIDSB and EIDEB, the same cutout/span check applies.

All the cutout/span checks introduced here still cannot cover 100% cases, but they can
spot most of the bad cases that will lead to unreal modeling of the seam weld. Thus, it is
recommended to turn on the cutout/span check (GMCHK > 0) to exam the seam weld
model in the first round. After all possible problems are resolved, then start the final run.

8. Check whether the CSEAM spans a corner on each shell surface when GMCHK > 0.

662 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Take EIDSA and EIDEA as an example. The angle between the normal vectors of the two
elements should not larger than the value of CNRAGLO (be defined in the SWLDPRM card)
as shown in the following figure. The same check applies to EIDSB and EIDEB. This
prevents generating single CSEAM element across a very curved shell configuration.

If α > CNRAGLO, this CSEAM element is rejected.

9. Diagnostic print outs, checkout runs and non-default setting of search and projection
parameters are requested on the SWLDPRM bulk data entry.

10. It is possible to visualize the fictitious CHEXA via setting SHOWAUX = 1 in the SWLDPRM
card. To have the fictitious CHEXA and corresponding results output into the H3D file,
one also needs to set SHOWAUX = 1.

11. It is recommended to start with default settings and turn on the full geometry check by
setting GMCHK=1 or 2. With the full geometry check, most of the unexpected cases
which may possibly induce unreasonable projections can be spotted. If the switch for
outputting diagnostic info, that is PRTSW, is turned on, the connectivity detail of each
CSEAM element will be printed in the .out file. Also, a summary of various geometry data
will be printed after all CSEAM elements are gone through by the program. They will be
very useful for debugging the seam weld model.

12. Seam weld elements are ignored in heat transfer analysis.

Altair Engineering OptiStruct 13.0 Reference Guide 663

Proprietary Information of Altair Engineering


CSEC2

Bulk Data Entry

CSEC2 – 1D Section Element

Description

Defines a two-noded element used in the definition of arbitrary beam cross-sections.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SEC 2 EID PID G1 G2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SEC 2 71 4 3 4

Field Contents

EID Element identification number.

No default (Integer > 0)

PID Identification number of a PSEC section property entry.

Default = EID (Integer > 0)

G# Identification number of GRIDS section grid points.

No default (Integer > 0)

Comments

1. Element identification numbers within a section definition must be unique with respect to
all other element identification numbers within the same section definition.

2. This entry is only valid when it appears between the BEGIN and END statements.

664 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CSEC3

Bulk Data Entry

CSEC3 – Triangular Section Element

Description

Defines a 1st order three-noded element used in the definition of arbitrary beam cross-
sections.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SEC 3 EID PID G1 G2 G3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SEC 3 10 100 3 4 5

Field Contents

EID Element identification number.

No default (Integer > 0)

PID Identification number of a PSEC section property entry.

Default = EID (Integer > 0)

G# Identification number of GRIDS section grid points.

No default (Integer > 0)

Comments

1. Element identification numbers within a section definition must be unique with respect to
all other element identification numbers within the same section definition.

2. This entry is only valid when it appears between the BEGIN and END statements.

Altair Engineering OptiStruct 13.0 Reference Guide 665

Proprietary Information of Altair Engineering


CSEC4

Bulk Data Entry

CSEC4 – Quadrilateral Section Element

Description

Defines a 1st order four-noded element used in the definition of arbitrary beam cross-sections.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SEC 4 EID PID G1 G2 G3 G4

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SEC 4 10 100 3 4 5 6

Field Contents

EID Element identification number.

No default (Integer > 0)

PID Identification number of a PSEC section property entry.

Default = EID (Integer > 0)

G# Identification number of GRIDS section grid points.

No default (Integer > 0)

Comments

1. Element identification numbers within a section definition must be unique with respect to
all other element identification numbers within the same section definition.

2. This entry is only valid when it appears between the BEGIN and END statements.

666 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CSEC6

Bulk Data Entry

CSEC6 – Curved Triangular Section Element

Description

Defines a planar, 2nd order, six-noded element used in the definition of arbitrary beam cross-
sections.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SEC 6 EID PID G1 G2 G3 G4 G5 G6

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SEC 6 10 100 3 4 5 6 7 8

Field Contents

EID Element identification number.

No default (Integer > 0)

PID Identification number of a PSEC section property entry.

Default = EID (Integer > 0)

G# Identification number of GRIDS section grid points.

No default (Integer > 0)

Comments

1. Element identification numbers within a section definition must be unique with respect to
all other element identification numbers within the same section definition.

Altair Engineering OptiStruct 13.0 Reference Guide 667

Proprietary Information of Altair Engineering


2. Grid points G1 through G6 must be numbered as shown here:

3. This entry is only valid when it appears between the BEGIN and END statements.

668 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CSEC8

Bulk Data Entry

CSEC8 – Curved Quadrilateral Section Element

Description

Defines a planar 2nd order eight-noded element used in the definition of arbitrary beam cross-
sections.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SEC 8 EID PID G1 G2 G3 G4 G5 G6

G7 G8

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SEC 8 10 100 3 4 5 6 13 14

15 16

Field Contents

EID Element identification number.

No default (Integer > 0)

PID Identification number of a PSEC section property entry.

Default = EID (Integer > 0)

G# Identification number of GRIDS section grid points.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 669

Proprietary Information of Altair Engineering


Comments

1. Element identification numbers within a section definition must be unique with respect to
all other element identification numbers within the same section definition.

2. Grid points G1 through G8 must be numbered as shown here:

3. This entry is only valid when it appears between the BEGIN and END statements.

670 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CSET

Bulk Data Entry

CSET – Boundary Degrees-of-Freedom of a Superelement Assembly

Description

CSET entry is equivalent to BNDFREE.

Refer to the documentation for the BNDFREE Bulk Data Entry.

Altair Engineering OptiStruct 13.0 Reference Guide 671

Proprietary Information of Altair Engineering


CSET1

Bulk Data Entry

CSET1 – Boundary Degrees-of-Freedom of a Superelement Assembly

Description

CSET1 entry is equivalent to BNDFRE1.

Refer to the documentation for the BNDFRE1 Bulk Data Entry.

672 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CSHEAR

Bulk Data Entry

CSHEAR – Shear Panel Element Connection

Description

Defines a shear panel element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SHEAR EID PID G1 G2 G3 G4

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C SHEAR 111 67 89 123 124 56

Field Contents

EID Unique element identification number.

(Integer > 0)

PID Identification number of a PSHEAR property entry.

(Integer > 0; If blank, defaults to EID)

G1, G2, G3, G4 Grid point identification numbers of connection points.

(Integer > 0; all unique)

Comments

1. Element identification numbers should be unique with respect to all other element
identification numbers.

Altair Engineering OptiStruct 13.0 Reference Guide 673

Proprietary Information of Altair Engineering


2. Grid points G1 through G4 must be ordered consecutively around the perimeter of the
element.

3. All interior angles must be less than 180 degrees.

C SHEAR definition

C SHEAR Element C orner Forces and Shear Flows

4. Shear panel elements are ignored in heat transfer analysis.

5. This card is represented as a quad4 element in HyperMesh.

674 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CTAXI

Bulk Data Entry

CTAXI – Axisymmetric Triangular Element Connection

Description

Defines an axisymmetric triangular cross-section ring element for use in linear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C TAXI EID PID G1 G2 G3 G4 G5 G6

Theta

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C TAXI 111 2 31 74 75 32 51 52

15.0

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PAXI entry.

Default = EID (Integer > 0)

G1,G3,G5 Identification numbers of connected corner grid points. Cannot be


omitted.

No default (Integers > 0, all unique)

Altair Engineering OptiStruct 13.0 Reference Guide 675

Proprietary Information of Altair Engineering


Field Contents

G2,G4,G6 Identification numbers of connected edge grid points. Cannot be


omitted.

No default (Integers > 0, all unique)

Theta Material orientation angle in degrees.

Default = 0.0 (Real)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. All the grid points must be located in the x-z plane of the basic coordinate system with x
= r > 0, and ordered consecutively starting at a corner grid point and proceeding around
the perimeter in either direction.

Corner grid points G1, G3 and G5 must be present. The edge points G2, G4 and G6 are
optional. If any of the edge points are present, they all must be used.

C TAXI definition

676 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. The continuation is optional.

4. If the PAXI entry referenced in field 3 references a MAT3 entry, material properties and
stresses are always given in the (xm, zm) coordinate system shown in the figure above.

5. A concentrated load (for example, the load specified on a FORCE entry) at a grid Gi of this
element denotes that applied onto the circumference with radius of Gi. For example, in
order to apply a load of 200N/m on the circumference at Gi which is located at a radius of
0.4m, the magnitude of the load specified on the static load entry must be:

(200 N/m) * 2 * (0.4m) = 502.655N

6. CTAXI and CTRIAX6 elements cannot be used simultaneously in an input model.

7. This card is represented as an element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 677

Proprietary Information of Altair Engineering


CTETRA

Bulk Data Entry

CTETRA – Four-sided Solid Element with four or ten grid points

Description

Defines the connections of the CTETRA element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C TETRA EID PID G1 G2 G3 G4 G5 G6

G7 G8 G9 G10

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C TETRA 112 2 3 15 14 4

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PSOLID property entry.

Default = EID (Integer > 0)

G# Identification numbers of connected grid points.

Default = blank (Integer > 0)

Comments

1. Element ID numbers must be unique with respect to all other element ID numbers.

678 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


2. The grid points G1, G2, G3, and G4 must describe the vertices and the remaining grid
points describe mid side nodes in the order shown here:

The edge points G5 to G10 are optional. All or none of the edge points can be specified.

It is recommended that the edge points be located within the middle third of the edge.

C TETRA definition

3. If the user-prescribed node numbering on the bottom face is reversed as compared to the
sequence shown above, then the nodes are renumbered to produce right-handed
orientation of numbering. This is accomplished by swapping node G2 with G3. For 10-
noded CTETRA, appropriate changes to mid-side node numbering are also performed. In
such cases, the element coordinate system will be built on the renumbered node
sequence.

4. Stresses are output in the material coordinate system. The material coordinate system is
defined on the referenced PSOLID entry. It may be defined as the basic coordinate
system (CORDM = 0), a defined system (CORDM = Integer > 0), or the element coordinate
system (CORDM = -1).

5. The element coordinate system for the CTETRA element is defined as follows:

Three intermediate vectors R, S, and T are chosen by the following rules:

R Joins the midpoints of the edges from G1 to G2 and G3 to G4.

S Joins the midpoints of the edges from G1 to G3 and G2 to G4.

T Joins the midpoints of the edges from G1 to G4 and G2 to G3

Altair Engineering OptiStruct 13.0 Reference Guide 679

Proprietary Information of Altair Engineering


C TETRA element coordinate system

The origin of the element coordinate system is located at G1.

The element z-axis corresponds to the T vector.

The element y-axis is the cross product of the T and R vectors.

The element x-axis is the cross product of the element y-axis and the element z-axis.

6. This card is represented as a tetra4 or tetra10 element in HyperMesh.

680 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CTRIA3

Bulk Data Entry

CTRIA3 – Triangular Element Connection

Description

Defines a triangular plate element (TRIA3) of the structural model. This element uses a 6
degree-of-freedom per node formulation.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C TRIA3 EID PID G1 G2 G3 Theta ZOFFS


or
MC ID

T1 T2 T3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C TRIA3 111 203 31 74 75

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PSHELL, PCOMP, PCOMPP or PHFSHL property


entry.

Default = EID (Integer > 0)

G1,G2,G3 Grid point identification numbers of connection points.

No default (Integers > 0, all unique)

Altair Engineering OptiStruct 13.0 Reference Guide 681

Proprietary Information of Altair Engineering


Field Contents

Theta Material orientation angle in degrees.

Default = 0.0 (Real)

MCID Material coordinate system identification number. The x-axis of this


coordinate system is projected onto the element to define the x-axis of
the material coordinate system. If MCID = 0, it specifies the basic
coordinate system. MCID must be an integer > 0. If blank, Theta = 0.0 is
used (See comments 2, 3, and 4).

Default is Theta = 0.0 (Integer > 0)

ZOFFS Offset from the plane defined by element grid points to the shell reference
plane. See comment 8. Overrides the ZOFFS specified on the PSHELL
entry.

Default = 0.0 (Real or blank)

Ti Thickness of the element at the grid points. Overrides the thickness


specified on the PSHELL entry. If Ti is specified, the average of all three
thicknesses is used as the element thickness.

For defaults: see comments 5 and 7.

(Real > 0.0 or blank)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. The x-axis of the element coordinate system is aligned with side 1-2 of the shell element.

3. For H3D and OUTPUT2 output formats, stresses and strains are always output in the
elemental system.

4. For HM, PUNCH, and OPTI output formats, stresses and strains are output by default in
the material coordinate system. PARAM,OMID can be set to NO to output results in the
elemental system. For elements with blank Theta/MCID, the material coordinate system is
aligned with elemental coordinate system. For elements with prescribed THETA, the
material x-axis is rotated from side G1-G2 by angle THETA. For elements with prescribed
MCID, the material system is constructed by projecting the prescribed MCID onto the
plane of the element.

682 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Orientation when Theta (real value) is entered in 8th field

Orientation when MC ID (integer value) is entered in 8th field

5. If any of the Ti fields are blank, the thickness specified on the PSHELL data will be used
for that node’s thickness. If 0.0 is specified for Ti, then the thickness at that node is
zero.

6. If the property referenced by PID is selected as a region for free-size or size optimization,
then any Ti values defined here are ignored. If you input Ti for elements in the design
space for Topology or Free-Size optimization, the run will error out.

7. If Ti is present, the PID cannot reference PCOMP or PCOMPP data.

8. The shell reference plane can be offset from the plane defined by element nodes by
means of ZOFFS. In this case all other information, such as material matrices or fiber
locations for the calculation of stresses, is given relative to the offset reference plane.
Similarly, shell results, such as shell element forces, are output on the offset reference
plane.

ZOFFS can be input in two different formats:

1. Real:

A positive or a negative value of ZOFFS is specified in this format. A positive value of


ZOFFS implies that the reference plane of each shell element is offset a distance of
ZOFFS along the positive z-axis of its element coordinate system.

Altair Engineering OptiStruct 13.0 Reference Guide 683

Proprietary Information of Altair Engineering


2. Surface:

This format allows you to select either “Top” or “Bottom” option to specify the offset
value.

Top:

The top surface of the shell element and the plane defined by the element nodes are
coincident.

This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
property entry referenced by this element. (The sign of the ZOFFS value would depend on
the direction of the offset relative to the positive z-axis of the element coordinate
system, as defined in the Real section). See Figure 1.

Figure 1: Top option in ZOFFS

Bottom:

The bottom surface of the shell element and the plane defined by the element nodes are
coincident.

This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
property entry referenced by this element. (The sign of the ZOFFS value would depend on
the direction of the offset relative to the positive z-axis of the element coordinate
system, as defined in the Real section). See Figure 2.

Figure 2: Bottom option in ZOFFS

Note that when ZOFFS is used, both MID1 and MID2 must be specified on the PSHELL
entry referenced by this element (otherwise, singular matrices would result).

684 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Offset is applied to all element matrices (stiffness, mass, and geometric stiffness), and to
respective element loads (such as gravity). Hence, ZOFFS can be used in all types of
analysis and optimization. Note, however, that for first order shell elements (CQUAD4 and
CTRIA3), the offset operation does not correct for secondary effects, such as change of
shell area when offset is applied on curved surfaces. Hence, the value of ZOFFS should
be kept within a reasonable percentage (10% - 15%) of the local radius of curvature.
Automatic offset control is available in composite free-size and sizing optimization where
the specified offset values are automatically updated based on thickness changes.

Moreover, while offset is correctly applied in geometric stiffness matrix and hence can be
used in linear buckling analysis, caution is advised in interpreting the results. Without
offset, a typical simple structure will bifurcate and loose stability “instantly” at the critical
load. With offset, though, the loss of stability is gradual and asymptotically reaches a
limit load, as shown below in figure (b):

Hence, the structure with offset can reach excessive deformation before the limit load is
reached. Note that the above illustrations apply to linear buckling – in a fully nonlinear
limit load simulation, additional instability points may be present on the load path.

9. PHFSHL properties are only valid with an @HYPERFORM statement in the first line of the
input file.

10. This card is represented as a tria3 element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 685

Proprietary Information of Altair Engineering


CTRIA6

Bulk Data Entry

CTRIA6 – Curved Triangular Shell Element Connection

Description

Defines a curved triangular shell element with six grid points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C TRIA6 EID PID G1 G2 G3 G4 G5 G6

THETA ZOFFS T1 T2 T3
or
MC ID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C TRIA6 302 3 31 33 71 32 51 52

45 .03 .020 .025 .025

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PSHELL, PCOMP or PCOMPP entry.

Default = EID (Integer > 0)

G1,G2,G3 Grid point identification numbers of connected corner points.

No default (Integers > 0, all unique)

686 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

G4,G5,G6 Grid point identification number of connected edge points. Cannot be


omitted.

No default (Integer > 0 or blank)

THETA Material orientation angle in degrees.

Default = 0.0 (Real)

MCID Material coordinate system identification number. The x-axis of this


material coordinate system is determined by projecting the x-axis of
the MCID coordinate system (defined by the CORDij entry or zero for
the basic coordinate system) onto the surface of the element.

Default is THETA = 0.0 (Integer > 0)

ZOFFS Offset from the surface of grid points to the element reference plane;
see Comment 7. Overrides the ZOFFS specified on the PSHELL entry.

Default = 0.0 (Real or blank)

Ti Membrane thickness of element at grid points G1 through G3. The


thickness of the element with Ti specified will be constant and equal to
an average of T1, T2, and T3.

For defaults: see comment 5.

(Real > 0.0 or blank)

Comments

1. Element identification numbers should be unique with respect to all other element IDs.

2. Grid points G1 through G6 must be numbered as shown here:

Altair Engineering OptiStruct 13.0 Reference Guide 687

Proprietary Information of Altair Engineering


3. The element coordinate system is a Cartesian system defined locally for each point ( ,
).

It is based on the following rules:

- The plane containing and is tangent to the surface of the element.

- is tangent to the line of constant .

- increases in the general direction of increasing and of .

688 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


4. The orientation of the material coordinate system is defined locally at each interior
integration point by THETA, which is the angle from the line of constant (essentially the
same as the -axis) to the material x-direction (Xmaterial).

If MCID is used in place of THETA, then the local material x-direction (Xmaterial) is
obtained at any point in the element by projection of the x-axis of the prescribed MCID
coordinate system onto the surface of the element at this point. The local z-direction is
aligned with the normal to the surface and the material y-direction (Y material) is
constructed accordingly to produce right-handed local material system X-Y-Zmaterial.

Altair Engineering OptiStruct 13.0 Reference Guide 689

Proprietary Information of Altair Engineering


5. T1, T2, and T3 are optional. If they are not supplied, then the element thickness will be
set equal to the value of T on the PSHELL entry. If 0.0 is specified for Ti, then the
thickness at that node is zero. If Ti is supplied, PID cannot reference PCOMP or PCOMPP
data. If the property referenced by PID is selected as a region for Size optimization, then
any Ti values defined here are ignored. If you input Ti for elements in the design space for
Topology or Free-Size optimization, the run will error out.

6. It is required that the midside grid points be located within the middle third of the edge.
That is the interval (0.25, 0.75) excluding the quarter points 0.25 and 0.75. If the edge
point is located at the quarter point, the program may fail with an error or the calculated
stresses will be meaningless.

7. The shell reference plane can be offset from the plane defined by element nodes by
means of ZOFFS. In this case all other information, such as material matrices or fiber
locations for the calculation of stresses, is given relative to the offset reference plane.
Similarly, shell results, such as shell element forces, are output on the offset reference
plane.

ZOFFS can be input in two different formats:

1. Real:

A positive or a negative value of ZOFFS is specified in this format. A positive value of


ZOFFS implies that the reference plane of each shell element is offset a distance of
ZOFFS along the positive z-axis of its element coordinate system.

2. Surface:

This format allows you to select either “Top” or “Bottom” option to specify the offset
value.

690 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Top:

The top surface of the shell element and the plane defined by the element nodes are
coincident.

This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
property entry referenced by this element. (The sign of the ZOFFS value would depend on
the direction of the offset relative to the positive z-axis of the element coordinate
system, as defined in the Real section). See Figure 1.

Figure 1: Top option in ZOFFS

Bottom:

The bottom surface of the shell element and the plane defined by the element nodes are
coincident.

This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
property entry referenced by this element. (The sign of the ZOFFS value would depend on
the direction of the offset relative to the positive z-axis of the element coordinate
system, as defined in the Real section). See Figure 2.

Figure 2: Bottom option in ZOFFS

Note that when ZOFFS is used, both MID1 and MID2 must be specified on the PSHELL
entry referenced by this element (otherwise, singular matrices would result).

Offset is applied to all element matrices (stiffness, mass and geometric stiffness) and to
respective element loads (such as gravity). Hence, ZOFFS can be used in all types of
analysis and optimization. Automatic offset control is available in composite free-size and
sizing optimization where the specified offset values are automatically updated based on
thickness changes.

Altair Engineering OptiStruct 13.0 Reference Guide 691

Proprietary Information of Altair Engineering


However, while offset is correctly applied in geometric stiffness matrix and hence can be
used in linear buckling analysis, caution is advised in interpreting the results. Without
offset, a typical simple structure will bifurcate and loose stability “instantly” at the critical
load. With offset, though, the loss of stability is gradual and asymptotically reaches a
limit load, as shown below in figure (b):

Hence, the structure with offset can reach excessive deformation before the limit load is
reached. Note that the above illustrations apply to linear buckling – in a fully nonlinear
limit load simulation, additional instability points may be present on the load path.

8. Stresses and strains are output in the local coordinate system identified by and
above.

9. Size optimization of the property referenced by PID is not possible if Ti values are defined
here. If the property referenced by PID is selected as a region for free-size optimization,
then any Ti values defined here are ignored.

10. These 2nd order shell elements do not have normal rotational degrees-of-freedom (often
referred to as "drilling stiffness"). No mass is associated with these degrees-of-freedom.
If unconstrained, massless mechanisms may occur. It is therefore advisable to use
PARAM,AUTOSPC,YES when working with these elements.

11. This card is represented as a tria6 element in HyperMesh.

692 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CTRIAR

Bulk Data Entry

CTRIAR – Triangular Element Connection

Description

CTRIAR entry is equivalent to CTRIA3. Unlike other Nastran codes, a 6 degrees-of-freedom


per node formulation is used for all shell elements.

Refer to the documentation for the CTRIA3 Bulk Data Entry.

Altair Engineering OptiStruct 13.0 Reference Guide 693

Proprietary Information of Altair Engineering


CTRIAX6

Bulk Data Entry

CTRIAX6 – Axisymmetric Triangular Element Connection

Description

Defines an axisymmetric triangular cross-section ring element for use in linear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C TRIAX6 EID MID G1 G2 G3 G4 G5 G6

Theta

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C TRIAX6 111 203 31 74 75 32 51 52

15.0

Field Contents

EID Unique element identification number.

No default (Integer > 0)

MID Identification number of a MAT1 or MAT3 entry.

No default (Integer > 0)

G1,G3,G5 Identification numbers of connected corner grid points. Cannot be


omitted.

No default (Integers > 0, all unique)

694 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

G2,G4,G6 Identification numbers of connected edge grid points. Cannot be


omitted.

No default (Integers > 0, all unique)

Theta Material orientation angle in degrees.

Default = 0.0 (Real or blank)

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. All the grid points must be located in the x-z plane of the basic coordinate system with x
= r > 0, and ordered consecutively starting at a corner grid point and proceeding around
the perimeter in either direction.

Corner grid points G1, G3 and G5 must be present. The edge points G2, G4 and G6 are
optional. If any of the edge points are present, they all must be used.

C TRIAX6 definition

Altair Engineering OptiStruct 13.0 Reference Guide 695

Proprietary Information of Altair Engineering


3. The continuation is optional.

4. If MID is defined on a MAT3 entry, material properties and stresses are always given in
the (xm, zm) coordinate system shown in the figure above.

5. A concentrated load (for example, the load specified on a FORCE entry) at a grid Gi of this
element denotes that applied onto the circumference with radius of Gi. For example, in
order to apply a load of 200N/m on the circumference at Gi which is located at a radius of
0.4m, the magnitude of the load specified on the static load entry must be:

(200 N/m) * 2 * (0.4m) = 502.655N

6. CTRIAX6 and CTAXI elements cannot be used simultaneously in an input model.

7. This card is represented as an element in HyperMesh.

696 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CTUBE

Bulk Data Entry

CTUBE – Tube Element Connection

Description

Defines a tension-compression-torsion element (TUBE) of the structural model.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C TUBE EID PID G1 G2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C TUBE 12 13 21 23

Field Contents

EID Element identification number.

(Integer > 0)

PID Identification number of a PTUBE property entry.

(Default = EID, Integer > 0)

G1,G2 Grid point identification numbers of connection points.

Comments

1. Element identification numbers must be unique with respect to all other element
identification numbers.

2. Only one TUBE element may be defined on a single entry.

Altair Engineering OptiStruct 13.0 Reference Guide 697

Proprietary Information of Altair Engineering


3. CTUBE data is converted to CROD data as it is read. PTUBE data is converted into PROD
data.

4. This card is represented as a rod element in HyperMesh.

698 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CVISC

Bulk Data Entry

CVISC – Viscous Damper Connection

Description

Defines a viscous damper element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C VISC EID PID G1 G2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C VISC 2 64 12 63

Field Contents

EID Unique element identification number.

No default (Integer > 0)

PID Identification number of a PVISC entry.

Default = EID (Integer > 0)

G1, G2 Geometric grid point identification numbers of connection points.

No default (Integer > 0)

Comments

1.

2. Element identification numbers must be unique with respect to all other element
identification numbers.

Altair Engineering OptiStruct 13.0 Reference Guide 699

Proprietary Information of Altair Engineering


3. Only one viscous damper element may be defined on a single entry.

4. Viscous damper elements are ignored in heat transfer analysis.

5. This card is represented as a spring element in HyperMesh.

700 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CWELD

Bulk Data Entry

CWELD – Weld or Fastener Element Connection

Description

Defines a weld or fastener connecting two surface patches or points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C WELD EWID PWID GS TYP GA GB SPTYP

GA1/SHIDA GA2/ GA3 GA4 GA5 GA6 GA7 GA8


SHIDB

GB1 GB2 GB3 GB4 GB5 GB6 GB7 GB8

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C WELD 7 34 233 GRIDID QT

55 56 21 22

101 102 378

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C WELD 7 34 233 ELEMID

15 16

Altair Engineering OptiStruct 13.0 Reference Guide 701

Proprietary Information of Altair Engineering


Example 3

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C WELD 7 34 ALIGN 103 259

Alternate Formats of CWELD Card – PARTPAT/ELPAT

The alternative formats of CWELD listed below are useful in cases when the weld diameter
extends beyond a single shell element. These options connect up to 3x3 shell elements per
patch (possibly more for triangular elements) on each side of weld element.

Format (Alternate)

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C WELD EWID PWID GS PATC HTYP GA GB

PIDA/ PIDB/
SHIDA SHIDB

XS YS ZS

Example 1 (Alternate)

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C WELD 10 20 PARTPAT

33 34

5.0 5.0 0.0

Example 2 (Alternate)

702 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

C WELD 10 20 345 ELPAT

1034 2035

Field Contents

EWID Unique element identification number.

No default (Integer > 0)

PWID Identification number of a PWELD entry.

Default = EWID (Integer > 0)

GS Identification number of a grid point which defines the location of the


connector. Required when TYP is GRIDID or ELEMID and GA and GB
are unspecified (See comments 2 and 4).

No default (Integer > 0)

TYP Character string indicating how the connection is defined.

GRIDID indicates that the connection is defined with grid


identification numbers GA# and GB#, respectively (See comment 3).

ELEMID indicates that the connection is defined with shell element


identification numbers SHIDA and SHIDB (See comment 7).

ALIGN indicates that the connection is defined between two shell


vertex grid points (See comment 8).

No default (GRIDID, ELEMID or ALIGN)

GA, GB When TYP is GRIDID or ELEMID, these represent grid identification


numbers of piercing points on surface A and surface B respectively
(See comment 4).

When TYPE is ALIGN, these represent vertex grid identification


numbers of the first and second shells respectively.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 703

Proprietary Information of Altair Engineering


Field Contents

SPTYP String indicating types of surface patches A and B. Q indicates


quadrilateral surface patch, and T indicates triangular surface patch.
Required when TYP is GRIDID (See comment 5).

No default (QQ, TT, QT, TQ, Q or T)

GA# Grid identification numbers of the first surface patch. GA1 to GA3 are
required (See comment 6).

No default (Integer > 0)

GB# Grid identification numbers of the second surface patch (See


comment 6).

PATCHTYP The type of connection between the patches. Either format


connects up to 3x3 elements per patch (possibly more for triangular
elements). See comment 12.

For PARTPAT, the connection of surface patch to surface patch is


defined by specifying the property numbers of shells on side A and B,
PIDA and PIDB, respectively.

For ELPAT, the connection of surface patch to surface patch is


defined by specifying IDs of shells SHIDA and SHIDB, respectively.

PIDA,PIDB Property identification numbers of PSHELL entries defining surface A


and B, respectively. Required for PARTPAT.

SHIDA, SHIDB Element identification numbers of shells defining weld ends A and B,
respectively. Required for ELPAT.

XS, YS, ZS Coordinates of point that defines the location of the weld in the basic
coordinate system. It is an alternate way of specifying the location
of GS. Available with PARTPAT/ELPAT options only.

Real

Comments

1. CWELD defines a flexible connection between two surface patches, between a point and
a surface patch, or between two shell vertex grid points. See figure below:

704 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


C onnection between two surface patches

C onnection between a point and a surface patch

Altair Engineering OptiStruct 13.0 Reference Guide 705

Proprietary Information of Altair Engineering


C onnection between two shell vertex grid points

2. GS is ignored if TYP is ALIGN.

3. If TYP is GRIDID, either a point to patch (GS to GA#) or a patch to patch (GA# to GB#)
connection is defined. For the patch to patch connection, GA# describes the first
surface patch and GB# describes the second surface patch.

4. The input of the piercing points GA and GB is optional when TYP is GRIDID and ELEMID. If
GA or GB are not specified, they are generated from the normal projection of GS onto the
surface patches. If GA and/or GB are specified, they take precedence over GS in defining
the respective end points. Also, their locations will be corrected so that they lie on
surface patch A and B, respectively. If GS is not specified, both GA and GB are required.
The length of the connector is the distance from GA to GB.

5. SPTYP defines the type of surface patches to be connected. SPTYP is required when TYP
is GRIDID to identify quadrilateral or triangular patches. Allowable combinations are:

SPTYP Description

QQ Connects a quadrilateral surface patch A (QUAD4 or QUAD8) with a


quadrilateral surface patch B (QUAD4 or QUAD8).

QT Connects a quadrilateral surface patch A (QUAD4 or QUAD8) with a


triangular surface patch B (TRIA3 or TRIA6).

TT Connects a triangular surface patch A (TRIA3 or TRIA6) with a


triangular surface patch B (TRIA3 or TRIA6).

TQ Connects a triangular surface patch A (TRIA3 or TRIA6) with a


quadrilateral surface patch B (QUAD4 or QUAD8).

Q Connects a grid point GB (or GS if GB not provided) with a quadrilateral


surface patch A (QUAD4 or QUAD8). Surface patch B should not be
specified.

706 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SPTYP Description

T Connects a grid point GB (or GS if GB not provided) with a triangular


surface patch A (TRIA3 or TRIA6). Surface patch B should not be
specified.

6. GA# are required when TYP is GRIDID. At least 3, and at most 8, grid IDs may be
specified for GA#. Triangular and quadrilateral element definition sequences apply for the
order of GA# and GB#, see below. Missing mid-side nodes are allowed.

Quadrilateral and Triangular Surface Patches as defined when TYP is GRIDID

7. When TYP is ELEMID, a point to patch connection is defined, GS to SHIDA or a patch to


patch connection, SHIDA to SHIDB. SHIDA and SHIDB must be valid shell element
identification numbers.

8. When TYP is ALIGN, a point to point connection is defined. GA and GB are required. GA
and GB are not required when TYP is GRIDID or ELEMID.

9. Forces and moments are output in the element coordinate system (shown in comment 10
below).

The element x-axis points from GA to GB. The element y-axis lies on the plane created by
the element x-axis and the smallest component of the element x-axis is the basic
coordinate system, and is orthogonal to the element x-axis. The element z-axis is the
cross-product of the element x-axis and the element y-axis.

10. The output format of the forces and moments, including the sign convention, is identical
to the CBAR element.

Altair Engineering OptiStruct 13.0 Reference Guide 707

Proprietary Information of Altair Engineering


Element coordinate system and sign convention of element forces

11. Diagnostic print outs, checkout runs and non-default setting of search and projection
parameters are requested on the SWLDPRM bulk data entry. It is recommended to start
with default settings.

12. The formats PARTPAT and ELPAT connect shell element patches on side A and B. The
patches are identified by specifying SHIDA and SHIDB (for ELPAT connection) and by
specifying property IDs PIDA and PIDB for PARTPAT connection (wherein SHIDA and SHIDB
are found by appropriate search of best projections of GS (or GA) onto the surfaces A
and B, respectivel)y. The piercing points GA and GB are found by appropriate projections
onto SHIDA and SHIDB. Then the axis GA-GB is used to define four pairs of auxiliary
points GAHi, GBHi, i=1,4 that are located on patches A and B, respectively. The cross-
section area of the resulting hexahedral is equivalent to the area of the weld. The weld
stiffness matrix is first built using the auxiliary points and then constrained to supporting
shell nodes using respective shape functions.

708 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


13. Fastener elements are ignored in heat transfer analysis.

14. This card is represented as a rod element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 709

Proprietary Information of Altair Engineering


DAREA

Bulk Data Entry

DAREA – Dynamic Load Scale Factor

Description

Defines scale (area) factors for dynamic loads. DAREA is used in conjunction with RLOAD1,
RLOAD2, TLOAD1, and TLOAD2 entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DAREA SID P1 C1 A1 P2 C2 A2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DAREA 3 64 2 5.7 65 2 5.7

Field Contents

SID Identification number.

No default (Integer > 0)

P1, P2# Grid or scalar point identification number.

No default (Integer > 0)

C1, C2# Component number.

No default (Integer 1 through 6, or 0 for scalar points)

A1, A2# Scale (area) factor.

No default (Real)

710 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. One or two scale factors may be defined on a single entry.

2. Refer to RLOAD1, RLOAD2, TLOAD1, or TLOAD2 entries for the formula that define the
scale factor A#.

3. Component numbers refer to the displacement coordinate system.

4. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).

5. This card is represented as a constraint load in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 711

Proprietary Information of Altair Engineering


DCOMP

Bulk Data Entry

DCOMP – Manufacturing Constraints for Composite Sizing Optimization

Description

Defines manufacturing constraints for composite sizing optimization.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DC OMP ID ETYPE EID1 EID2 EID3 EID4 EID5 EID6

+ EID7 …

+ LAMTHK LTMIN LTMAX LTSET LTEXC

+ PLYTHK PTGRP PTMIN PTMAX PTOPT PTSET PTEXC

+ PLYPC T PPGRP PPMIN PPMAX PPOPT PPSET PPEXC

+ BALANC E BGRP1 BGRP2 BOPT

+ C ONST C GRP C THIC K C OPT

+ PLYDRP PDGRIP PDTYP PDMAX PDOPT PDSET PDEXC

Field Contents

ID Unique identification number.

No default (Integer > 0)

ETYPE Entity type for which this DCOMP card is defined.

No default (PCOMP or STACK)

EID# Entity identification numbers. List of entities of type ETYPE for which this
DCOMP card is defined.

No default (Integer > 0)

LAMTHK LAMTHK flag indicating that laminate thickness constraints are applied.

712 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Multiple LAMTHK constraints are allowed.

LTMIN Minimum laminate thickness for the LAMTHK constraint.

Default = blank (Real > 0.0)

LTMAX Maximum laminate thickness for the LAMTHK constraint.

Default = blank (Real > 0.0 and > LTMIN)

LTSET Set ID of elements to which the LAMTHK constraint is applied.

LTEXC Exclusion flag indicates that certain plies are excluded from the LAMTHK
constraint. The following options are supported:

NONE: Plies are not excluded.


CORE: The core is excluded. (Default)
CONST: Plies defined in the CONST constraint are excluded.
BOTH: CORE and CONST are considered.

PLYTHK PLYTHK flag indicating that ply thickness constraints are applied. Multiple
PLYTHK constraints are allowed.

PTGRP Ply orientation in degrees, ply sets or ply IDs, to which the PLYTHK
constraint is applied, depending on the PTOPT selection.

No default (Real or Integer)

PTMIN Minimum thickness for the PLYTHK constraint.

Default = blank (Real > 0.0)

PTMAX Maximum thickness for the PLYTHK constraint.

Default = blank (Real > 0.0 and > PTMIN)

PTOPT Ply selection options for the PLYTHK constraint. Plies can be selected based
on the following:

BYANG: Orientation (Default)


BYSET: Ply sets
BYPLY: Ply IDs

PTSET Set ID of elements to which the PLYTHK constraint is applied.

PTEXC Exclusion flag indicates that certain plies are excluded from the PLYTHK
constraint. The following options are supported:

NONE: Plies are not excluded.

Altair Engineering OptiStruct 13.0 Reference Guide 713

Proprietary Information of Altair Engineering


Field Contents

CORE: The core is excluded. (Default)


CONST: Plies defined in the CONST constraint are excluded.
BOTH: CORE and CONST are considered.

PLYPCT PLYPCT flag indicating that ply thickness percentage constraints are applied.
Multiple PLYPCT constraints are allowed.

PPGRP Ply orientation in degrees, ply sets or ply IDs, to which the PLYPCT
constraint is applied, depending on the PPOPT selection.

No default (Real or Integer)

PPMIN Minimum percentage thickness for the PLYPCT constraint.

Default = blank (Real > 0.0 and < 1.0)

PPMAX Maximum percentage thickness for the PLYPCT constraint.

Default = blank (Real > 0.0, < 1.0 and > PPMIN)

PPOPT Ply selection options for the PLYPCT constraint. Plies can be selected based
on the following:

BYANG: Orientation (Default)


BYSET: Ply sets
BYPLY: Ply IDs

PPSET Set ID of elements to which the PLYPCT constraint is applied.

PPEXC Exclusion flag indicates that certain plies are excluded from the PLYPCT
constraint. The following options are supported:

NONE: Plies are not excluded.


CORE: The core is excluded. (Default)
CONST: Plies defined in the CONST constraint are excluded.
BOTH: CORE and CONST are considered.

BALANCE BALANCE flag indicating that a balancing constraint is applied. Multiple


BALANCE constraints are allowed.

BGRP1 First ply orientation in degrees, ply sets or ply IDs, to which the BALANCE
constraint is applied, depending on the BOPT selection.

No default (Real or Integer)

BGRP2 Second ply orientation in degrees, ply sets or ply IDs, to which the BALANCE
constraint is applied, depending on the BOPT selection.

No default (Real or Integer)

714 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

BOPT Ply selection options for the BALANCE constraint. Plies can be selected
based on the following:

BYANG: Orientation (Default)


BYSET: Ply sets
BYPLY: Ply IDs

CONST CONST flag indicating that a constant thickness constraint is applied.


Multiple CONST constraints are allowed.

CGRP Ply orientation in degrees, ply sets or ply IDs, to which the CONST constraint
is applied, depending on the COPT selection.

No default (Real or Integer)

CTHICK Constant ply thickness for the CONST constraint.

No default (Real > 0.0)

COPT Ply selection options for the CONST constraint. Plies can be selected based
on the following:

BYANG: Orientation (Default)


BYSET: Ply sets
BYPLY: Ply IDs

PLYDRP Indicates that ply drop-off constraints are applied. Multiple PLYDRP
constraints are allowed.

PDGRIP Ply orientation in degrees, ply sets or ply IDs, to which the PLYDRP
constraint is applied, depending on the PDOPT selection.

No default. (Real or Integer)

PDTYP Specifies the type of the drop-off constraint as: TOTDRP (see comment 5).

PDMAX Maximum allowed drop-off for the PLYDRP constraint.

No default (Real > 0)

PDOPT Ply selection options for the PLYDRP constraint. Plies can be selected based
on the following:

BYANG: Orientation (Default)


BYSET: Ply sets
BYPLY: Ply IDs

PDSET Set IDs of elements to which the PLYDRP constraint is applied.

Altair Engineering OptiStruct 13.0 Reference Guide 715

Proprietary Information of Altair Engineering


Field Contents

PDEXC Exclusion flag indicates certain plies are excluded from the PLYDRP
constraint. The following options are supported:

NONE: Plies are not excluded.


CORE: The core is excluded. (Default).
CONST: Plies defined in the CONST constraint are excluded.
BOTH: CORE and CONST are considered.

Comments

1. The following manufacturing constraints are available for ply-based composite sizing
optimization:

Lower and upper bounds on the total thickness of the laminate (LAMTHK)
Lower and upper bounds on the thickness of a given orientation (PLYTHK)
Lower and upper bounds on the thickness percentage of a given orientation (PLYPCT)
Manufacturable ply thickness (PLYMAN)
Linking between the thicknesses of two given orientations (BALANCE)
Constant (non-designable) thickness of a given orientation (CONST)
LAMTHK, PLYTHK and PLYPCT can be applied locally to sets of elements. There can be
elements that do not belong to any set.
2. These constraints are automatically created after performing free-sizing optimization
when the OUTPUT,FSTOSZ control card is activated.

3. For a more detailed description and an example, refer to the User’s Guide section,
Optimization of Composite Structures.

4. Older versions of the DCOMP card (OptiStruct version 11.0 and prior) are supported and
handled appropriately.

5. The option for selecting the type of drop-off constraints for PDTYP is defined for a set of
plies, as shown in the figure below:

The option for PDTYP in DCOMP is: TOTDRP.

716 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Assuming that the plies are stacked as shown above, you have the following definition:

6. This card is represented as an optimization designvariable in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 717

Proprietary Information of Altair Engineering


DCONADD

Bulk Data Entry

DCONADD – Design Constraint Addition

Description

Creates a combination of several DCONSTR sets that can be referenced by a subcase.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DC ONADD DC ID DC 1 DC 2 DC 3 DC 4 DC 5 DC 6 DC 7

DC 8 etc.

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DC ONADD 101 10 20 30

Field Contents

DCID DCONADD identification number.

(Integer > 0)

DCi DCONSTR identification number.

(Integer > 0)

Comments

1. The DCONADD entry is selected by a DESSUB or DESGLB in the Subcase Information


section.

2. All DCi must be unique.

3. All DCID must be unique with respect to all Dci (DCONSTR IDs).

4. This card is represented as an optimizationconstraint in HyperMesh.

718 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DCONSTR

Bulk Data Entry

DCONSTR – Design Constraints

Description

Defines design constraint upper and lower bounds where response is defined by DRESP1,
DRESP2, and DRESP3 cards.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DC ONSTR DC ID RID LBOUND/ UBOUND/ LFREQ UFREQ PROB


LTID UTID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DC ONSTR 1 9 0.5 10.0

Associated Cards

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DRESP1 9 TOPN DISP 3 4668

Field Contents

DCID Design constraint identification number.

(Integer > 0)

RID DRESP1, DRESP2, or DRESP3 identification number.

(Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 719

Proprietary Information of Altair Engineering


Field Contents

LBOUND/LTID Lower bound on response or table identification number of a TABLEDi


entry that specifies the lower bound as function of a loading
frequency.

(Real, Integer, or blank)

UBOUND/UTID Upper bound on response or table identification number of a TABLEDi


entry that specifies the upper bound as function of a loading
frequency.

(Real, Integer, or blank)

LFREQ Lower bound on a loading frequency range.

Default = 0.0 (Real > 0.0)

UFREQ Upper bound on a loading frequency range.

Default = 1.0E+20 (Real > LFREQ)

PROB Probability value for Reliability based Design Optimization runs.

(50.0 < Real < 100.0)

Comments

1. The DCONSTR DCID is selected in the Subcase Information section by the DESSUB or
DESGLB cards and/or referenced by the DCONADD card.

2. For any DCID, the associated RID can be referenced only once.

3. If LBOUND or UBOUND are blank, no constraint will be generated for the bound.

4. Constraint bounds of zero should be avoided. Unnecessary bounds should be left blank.
For example, lower bounds on von Mises stress should be blank, not zero. If a bound of
zero is input, the bound will be changed to 1.0E-7 for lower bounds and –1.0E-7 for upper
bounds. This will remove numerical difficulties and cause the constraints to be ignored
unless the response is actually very near zero.

5. LFREQ, UFREQ apply only to response types related to a frequency response subcase
(DRESPi, RTYPE = FRDISP, FRVELO, FRACCL, FRSTRS, FRSTRN, FRFORC, and FRERP). The
constraint bounds LBOUND and UBOUND are applied only if the loading frequency falls
between LFREQ and UFREQ. If ATTB of DRESP1 specifies a frequency value, LFREQ and
UFREQ are ignored.

6. LTID, UTID identify a loading frequency dependent tabular input using TABLEDi. They are
applied analogous to LFREQ, UFREQ detailed in comment 5.

7. This card is represented as an optimizationconstraint in HyperMesh.

720 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DDVAL

Bulk Data Entry

DDVAL – Discrete Design Variable Values

Description

This bulk data entry can be used to define real, discrete design variable values for discrete
variable optimization or to define relative rotor spin rates in rotor dynamics.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DDVAL ID DVAL1 DVAL2 DVAL3 DVAL4 DVAL5 DVAL6 DVAL7

Alternate Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DDVAL ID DVAL1 "THRU" DVAL "BY" INC

The continuation entry formats (shown below) may be used more than once, and in any order.
They may also be used with either format above.

Continuation Entry Format 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVAL8 DVAL9 DVAL10 DVAL11 -etc.-

Continuation Entry Format 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVAL8 "THRU" DVAL9 "BY" INC

Example

Altair Engineering OptiStruct 13.0 Reference Guide 721

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DDVAL 110 0.1 0.2 0.3 0.5 0.6 0.4

.7 thru 1.0 by 0.05

1.5 20

Field Contents

ID Unique discrete value set identification number.

(Integer > 0)

DVALi Discrete values.

(Real or "THRU" or "BY")

INC Discrete value increment.

(Real)

Comments

1. DDVAL entries must be referenced by

a) The DDVAL field of a DESVAR bulk data entry.

b) The SPTID field of a RSPINR bulk data entry.

2. Trailing fields on a DDVAL record can be left blank if the next record is of type DVALi
"THRU" DVALj "BY" INC. Also, fields 7 though 9 must be blank when the type DVALi "THRU"
DVALj "BY" INC is used in fields 2 through 6. Fields 8 through 9 must be blank when the
type DVALi "THRU" DVALj "BY" INC is used in fields 3 through 7 for the first record.
Embedded blanks are not permitted in other cases.

3. The DVALi sequence can be random.

4. The format DVALi "THRU" DVALj "BY" INC defines a list of discrete values, for example,
DVALi, DVALi+INC, DVALi+2.0*INC, …, DVALj. The last discrete DVALj is always included,
even if the range is not evenly divisible by INC.

5. This card is represented as a discretedesignvariable in HyperMesh.

722 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DEFORM

Bulk Data Entry

DEFORM – Static Element Deformation

Description

Defines enforced axial deformation for one-dimensional elements for use in statics problems.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DEFORM SID EID1 D1 EID2 D2 EID3 D3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DEFORM 21 157 -0.2 111 1.4

Field Contents

SID Identification number of a deformation set.

No default (Integer > 0)

EID# Element Identification Number. See comment 1.

No default (Integer > 0)

D# Deformation. (Positive value represents elongation).

No default (Real)

Comments

1. Only CBAR, CBEAM, CROD, CONROD, and CTUBE elements are valid.

2. To be used in an analysis, deformation sets must be referenced by a DEFORM Subcase


Information entry.

Altair Engineering OptiStruct 13.0 Reference Guide 723

Proprietary Information of Altair Engineering


3. DEFORM does not enforce an actual extension of the length of the element; it applies an
internal strain within the element, which produces the specified extension if the element is
free to expand (similar to the effect of thermal expansion).

Since most elements in an FEA model are not free to expand, the specified extension
value may not be achieved because elastic compression of the element will partially or
completely offset the effect of the prescribed strain. To precisely enforce a prescribed
increase in length, MPC equations are more appropriate. Alternatively, giving the DEFORM
element a very high axial stiffness can approximate such conditions.

724 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DELAY

Bulk Data Entry

DELAY – Dynamic Load Time Delay

Description

Defines the time delay term in the equations of the dynamic loading function. DELAY is
used in conjunction with RLOAD1, RLOAD2, TLOAD1, and TLOAD2 entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DELAY SID P1 C1 T1 P2 C2 T2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DELAY 3 64 2 5.7 65 2 5.7

Field Contents

SID Identification number.

No default (Integer > 0)

P1, P2 Grid or scalar point identification number.

No default (Integer > 0)

C1, C2 Component number.

No default (Integer 1 through 6, or 0 for scalar points)

T1, T2 time delay term, , for designated point and component.

No default (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 725

Proprietary Information of Altair Engineering


Comments

1. One or two dynamic load time delays may be defined on a single entry.

2. SID must also be specified on a RLOAD1, RLOAD2, TLOAD1, or TLOAD2 entry. See those
entry descriptions for the formulae that define the manner in which the time delay term,
, is used.

3. A DAREA entry should be used to define a load at P# and C#.

4. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).

5. This card is represented as a constraint load in HyperMesh.

726 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DEQATN

Bulk Data Entry

DEQATN – Design Equation Definition

Description

Specifies one or more equations for use in optimization.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DEQATN EQUID EQN1; EQN2; EQN3;

…; …; EQNn-1; EQNn

Example 1

DEQATN 3 y(x1, x2) = x1 + x2**-3.0*(2-1)+5.0;

z = -y*1.3E-2

Example 2

DEQATN 104 z(x1, x2) = min(sin(x1), x2);

y = max(0.3, -2.0, z) + 4.0

Field Contents

EQUID Unique equation identification number.

(Integer > 0)

EQNi i-th equation.

Altair Engineering OptiStruct 13.0 Reference Guide 727

Proprietary Information of Altair Engineering


(Character string)

Comments

1. All equation identification numbers must be unique.

2. Each equation card is specified in a fixed format, without the limitation of data field
boundaries. Equations are located in columns 17-72 on the first card, and in columns 9-
72 on each continuation card. There is no limit on the total length of any equation.

3. Large field format is not allowed.

4. Free field format is allowed, but only the same number of characters as in the fixed format
(56 on the first line and 64 on the continuation lines) and will be accepted. Characters
after the 72nd column will not be accepted. Excess characters are silently disregarded,
which may result in DEQATN error or in a valid expression different from that intended. On
the continuation card in free format, the comma must be present within the first 8
columns; otherwise, the card will be interpreted in a fixed field format.

5. Blank characters in the equation have no effect, even within a constant, variable or
function name. Lower and upper case letters are equivalent.

6. There must be only one variable at the left-hand side of each equation in any equation
card. The variable of the first equation must be followed by an argument list in the
following format:
v1(x1,x2,…,xn) = expression(x1,x2,…,xn);

v2 = expression(x1,x2,…,xn,v1);

vi = expression(x1,x2,…,xn,v1,v2,…,vi-1);

vn = expression(x1,x2,…,xn,v1,v2,…,vn-1);

where, vi is the variable of equation i. (x1, x2, …, xn) is the argument list for variable v1.
(v1,v2,…,vi-1) is the variable list which corresponds to the result of equation 1 through
equation i-1.

Only the value of the last expression is returned to the bulk data card referencing EQUID
(DRESP2).

7. Constants can be specified in a format of either integer or floating point. A floating point
number can be in a format of either normal decimal-point format ("3.90") or scientific
notation ("-2.0E-3"), which means -2x10-3.

The list of supported mathematical functions is as follows:

728 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


One-argument functions

abs(x) absolute value

acos(x) arccosine

acosh(x) hyperbolic arccosine

asin(x) arcsine

asinh(x) hyperbolic arcsine

atan(x) arctangent

atanh(x) hyperbolic arctangent

cos(x) cosine

cosh(x) hyperbolic cosine

exp(x) exponential

log(x) natural logarithm

log10(x) common logarithm

pi(x) multiples of

sin(x) sine

sinh(x) hyperbolic sine

int (x) real to integer conversion

sqrt(x) square root

Two-argument functions

Altair Engineering OptiStruct 13.0 Reference Guide 729

Proprietary Information of Altair Engineering


Multi-argument functions

8. The supported operators are listed below:

Symbol Meaning Example

+ binary + x+y

- binary - x-y

* multiplication, x*y

/ division x/y

** power x**y

+ unary + +1.0

730 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Symbol Meaning Example

- unary - -1.0

9. The precedence of mathematical calculations follows the rules of Fortran language.


Parenthesis has a higher priority in the order of precedence than the operators listed in 8.
Two consecutive operators are allowed only if the second one is unary plus or minus.

Examples of operator precedence:

Expression Result

2**-3 0.128

1 / 2 +3 3.5

2*3-4 2.0

-2**3**2 -512.0

2 + -5 -3.0

2 * -5 -10.0

2 - -5 7.0

2/3/4 0.16666666…

2/(3/4) 2.6666666…

10. Functions can be defined in a layered format, for example, min(sin(x1), x2). There is no
limit on the number of layers.

11. The DEQATN entry is referenced by DRESP2 and/or DVPREL2 bulk data cards.

DRESP2 card, the variable identified by DVIDi, LABj, NRk, Gr and DPIP correspond to
variable arguments listed in the left-hand side of the first equation of a DEQATN card
identified by EQUID. The variable arguments x1 through xN (where N = n + m + p + q + s)
are assigned in the order DVID1, DVID2, …, DVIDn, LAB1, LAB2, …, LABm, NR1,NR2, …,
NRp, G1, …, Gq, DPIP1,…,DPIPS. In a DVPREL2 card, the variables identified by DVIDi and
LABj correspond to variable arguments listed in the left-hand side of the first equation of
a DEQATN card identified by EQUID. The variable arguments x1 through xN (where N = n
+ m) are assigned in the order DVID1, DVID2, …, DVIDn, LAB1, LAB2, …, LABm.

Only the computed value of the last expression (vn) is used by DRESP2 and/or DVPREL2
entry.

12. This card is represented as an optimizationfunction in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 731

Proprietary Information of Altair Engineering


Restrictions

Variable names longer than 8 characters are truncated, which may create an error in
equation if two names are identical after such truncation.
All trigonometric arguments are in radians.
Only alphanumeric characters may be used in variable names (that is do not use
underscores, monetary symbols, punctuation symbols, mathematical operators, letters
from non-English alphabet, and so on).

Mathematical function names (such as those listed in comment 7 above) should not be
used as variable names.
The following functions are not accepted:
DB()
DBA()
INVDB()
INVDBA()

Possible Errors

An informative error message with the DEQATN ID will be displayed if the parsing of the
equation fails. However, in certain cases, the following generic message will be provided:

Error 1690: This equation could not be parsed. See the DEQATN entry in the
OptiStruct manual.

This error message means that it was not possible to clearly identify the reason for the failure.
If this happens, check for the following possible causes, and contact ossupport@altair.com:

The length of the equation exceeds the 72 character per line limitation.
The last character of the equation is an operator.

There are two adjacent operators in the equation.


There are non-alphanumeric characters (besides operators) in the equation.

732 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DESVAR

Bulk Data Entry

DESVAR – Design Variable

Description

Defines a design variable.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DESVAR ID LABEL XINIT XLB XUB DELXV DDVAL

+ RAND ITYPE P1 P2 P3

+ RANP ITYPE P1 P2 P3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DESVAR 1 DV001 0.0 -1.0 1.0

Field Contents

ID Unique design variable identification number.

(Integer > 0)

LABEL User-defined name for the variable.

(Character)

XINIT Initial value for variable.

(Real between XLB and XUB)

Altair Engineering OptiStruct 13.0 Reference Guide 733

Proprietary Information of Altair Engineering


Field Contents

XLB Design variable lower bound.

(Real)

XUB Design variable upper bound.

(Real)

DELXV Initial move limit for each design variable.

(Real > 0.0 or blank)


Size: fraction of the variable itself.
(Default = value of DOPTPRM parameter DELSIZ)
Shape: fraction of the range (XUB – XLB) of the variable.
(Default = value of DOPTPRM parameter DELSHP)

DDVAL ID of DDVAL entry that provides a set of discrete values.

(Blank or Integer > 0; Default = blank for continuous design variables)

RAND Random Design Variable

RAND flag indicating that the random design variable distribution parameters
for Reliability-based Design Optimization (RBDO).

ITYPE Type of Random Distribution (see comment 5):

(Character string)

NORM – Normal distribution

LOG – Logarithmic normal distribution

UNIF – Uniform distribution

TRIA – Triangular distribution

EXPO – Exponential distribution

WEIB – Weibull distribution

GUMB – Gumbel distribution

P1 The first distribution parameter (see comment 5)

(Real > 0.0)

P2 The second distribution parameter (see comment 5)

734 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

(Real > 0.0)

P3 The third distribution parameter (see comment 5)

(Real > 0.0)

Set it to zero, if this parameter does not exist

RANP Random Parameter

RANP flag indicating that the random parameter distribution parameters for
Reliability-based Design Optimization (RBDO).

Comments

1. Only the initial value of the move limits can be set. Move limits are automatically
adjusted to enhance iterative stability and convergence speed.

2. LABEL must begin with an alphabetical character, and cannot have embedded blanks.

3. If the design variable is discrete (Integer > 0 in DDVAL field), and if either XLB and/or XUB
bounds are wider than those given by the discrete list of values on the corresponding
DDVAL entry, XLB and/or XUB will be replaced by the minimum and maximum discrete
values.

4. Setting XINIT=XLB=XUB freezes the design variable.

5. The various distribution types are as follows:

Normal Distribution (NORM)

Log-normal Distribution (LOG)

Altair Engineering OptiStruct 13.0 Reference Guide 735

Proprietary Information of Altair Engineering


Uniform distribution (UNIF)

Triangular distribution (TRIA)

Exponential distribution (EXPO)

736 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Weibull distribution (WEIB)

Gumbel distribution (GUMB)

6. This card is represented as an optimization designvariable in HyperMesh

Altair Engineering OptiStruct 13.0 Reference Guide 737

Proprietary Information of Altair Engineering


DESVARG

Bulk Data Entry

DESVARG – Design Variable Group Override

Description
Defines an override for design variable settings.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DESVARG ID INIT LB UB SET

Field Contents

ID Identification Number.

No default (Integer > 0)

INIT Overrides the initial value setting for affected design variables. See
comment 1.

Default = blank (UB, LB, blank, Real or ANALYSIS)

LB Overrides the lower bound setting for affected design variables.

Default = blank (blank or Real)

UB Overrides the upper bound setting for affected design variables.

Default = blank (blank or Real)

SET Defines the design variables that are affected by this DESVARG entry. Can
either be the keyword ALL or the SID of a SET of type DESVAR.

Default = ALL (ALL or Integer)

Comments

1. If any of INIT, LB or UB are left blank, then no override is applied to the corresponding
field on affected DESVARs.

738 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


2. If INIT is defined as LB, then for all affected DESVAR entries the initial value is set to the
lower bound setting.

Likewise if INIT is defined as UB, then for all affected DESVAR entries the initial value is
set to the upper bound setting.

If, INIT is defined as ANALYSIS, then for all affected DESVAR entries the initialization is
accomplished based on the corresponding analysis properties.

Limitations for the ANALYSIS mode of initialization in the INIT field:

When a Design Variable is associated with multiple properties that have different
values.
When a Design Variable is associated with a property through DVPREL2

When a Design Variable is associated with a property through DVPREL1 with multiple
design variables.
When one of the three limitations occurs, a warning is issued and the Design Variable is
initialized based on the DESVAR card.

3. Multiple DESVARGs are allowed (DESVARGs are processed in the order of input).

4. If the bounds are invalid after DESVARG is applied, then an error will occur.

5. This card is represented as a control card in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 739

Proprietary Information of Altair Engineering


DGLOBAL

Bulk Data Entry

DGLOBAL – Input Data for Selecting the Global Search Option

Description

Defines input parameters required for the Global Search Option (GSO).

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DGLOBA ID NGROU NPOINT SPMETH NOUTDE DESTOL


L P S

+ MAXSP MAXSUC MAXWAL MAXC PU


C L

+ GROUP SID1 NPOINT1 SPMETH1

+ GROUP SID2 NPOINT2 SPMETH2

+ … …

Field Contents

ID Each DGLOBAL card must have a unique ID.

No default (Integer > 0)

NGROUP Number of groups of design variables. See comment 1.

Default = AUTO (Integer > 0, AUTO or blank)

NPOINT Number of starting points for each group of design variables. See
comment 1.

Default = AUTO (Integer > 0, AUTO or blank)

SPMETH Method used to generate the starting points. See comment 2.

740 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Default = OFFSET (EXTREME, OFFSET or blank)

NOUTDES Number of unique designs to be saved. See comment 4.

Default = ALL (Integer > 0, ALL or blank)

DESTOL Unique design tolerance. See comment 4.

Default = 1% (Real > 0.0 or blank)

MAXSP Maximum number of starting points. See comment 5.

Default = 20 (Integer > 0 or blank)

MAXSUCC Maximum number of consecutive starting points without finding a unique


design. See comment 5.

Default = 10 (Integer > 0 or blank)

MAXWALL Maximum amount of WALL time (in hours). See comment 5.

Default = infinite (Real > 0.0 or blank)

MAXCPU Maximum amount of CPU time (in hours). See comment 5.

Default = infinite (Real > 0.0 or blank)

GROUP GROUP flag indicating that design variables grouping information is to


follow. See comment 3.

SID# Design variables SET identification number.

No default (Integer > 0)

NPOINT# Number of starting points for the current group of design variables.

Default = AUTO (Integer > 0, AUTO or blank)

SPMETH# Method used to generate the starting points for the current group of
design variables.

Default = AUTO (EXTREME, OFFSET, AUTO or blank)

Altair Engineering OptiStruct 13.0 Reference Guide 741

Proprietary Information of Altair Engineering


Comments

1. Design variables are automatically organized in groups, and design variables within a given
group are assigned the same relative starting points, such as their lower or upper bound.
With the AUTO option, OptiStruct determines NGROUP and NPOINT so as to generate a
reasonable and manageable number of starting points. Note that for small optimization
problems, each design variable might be assigned its own group. By default, the number
of groups is equal to the number of independent design variables with an upper limit of 10.
For larger optimization problems, design variables are grouped together in order to
consolidate the potential starting points.

2. With the EXTREME option, the lower and upper bounds are included in the list of starting
points; whereas with the OFFSET option, the lower and upper bounds are not considered
as starting points. In both cases, the starting points are distributed evenly.

3. In situations where finer control is required, design variables can be grouped manually by
creating DESVAR SETs. NPOINT# and SPMETH# can also be defined for individual groups.
If those parameters are not defined for a specific group, they inherit their value from the
generic NPOINT and SPMETH parameters.

4. The unique design tolerance DESTOL provides the threshold under which two designs are
considered identical. It is measured as the average of the relative differences between
the design variables at the last iteration. If such identical designs are found, the best
occurrence is preserved and other results are discarded. Up to NOUTDES unique designs
are saved in subdirectories named <filename_#s_#u>, where #s is the starting point and
#u is the rank of the unique design.

5. The global search option stops searching for optimal designs when any of the following
criteria has been met:

the maximum number of starting points (MAXSP) has been reached


the maximum number of consecutive starting points without finding a unique design
(MAXSUCC) has been reached
the maximum amount of WALL time (MAXWALL) has been reached or exceeded
the maximum amount of CPU time (MAXCPU) has been reached or exceeded

all possible starting points have been explored


6. In general, it is recommended to run the global search option with the default parameters,
except for the termination criteria.

7. The DGLOBAL bulk data entry is referenced by the DGLOBAL command in the I/O section
of the input data.

742 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DIM

Bulk Data Entry

DIM – Dimension Definition

Description

Defines a link between a DIM# field on a PBARL or PBEAML property and either the thickness
on a PSEC definition or the y or z coordinate on a GRIDS definition; it is used in the definition
of arbitrary beam cross-sections.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DIM DIMID T PID

Alternate Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DIM DIMID G GID C OORD

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DIM 1 T 10

Field Contents

DIMID Dimension identification number. The number of a cross-section dimension


field on a PBARL, or PBEAML property definition.

No default (Integer > 0)

T Thickness flag. Indicates that the dimension definition is related to a PSEC


thickness.

Altair Engineering OptiStruct 13.0 Reference Guide 743

Proprietary Information of Altair Engineering


Field Contents

PID Identification number of a PSEC definition.

No default (Integer > 0)

G Grid flag. Indicates that the dimension definition is related to a GRIDS


coordinate.

GID Identification number of a GRIDS definition.

No default (Integer > 0)

COORD Coordinate.

No default (Y or Z)

Comments

1. DIMID may be repeated in a section definition, but a PSEC thickness or a GRIDS


coordinate must not be mentioned on more than one DIM entry within a section definition.

2. This entry is only valid when it appears between the BEGIN and END statements.

744 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DLINK

Bulk Data Entry

DLINK – Design Variable Link

Description

The DLINK bulk data entry defines a link between one design variable and one or more other
design variables.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DLINK ID DDVID C0 C MULT IDV1 C1 IDV2 C2

IDV3 C3 etc.

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DLINK 55 3 0.2 0.45 5 2.0 10 5.5

15 -3.0

Field Contents

ID Unique DLINK identification number.

(Integer > 0)

DDVID Identification number of the Dependent Design Variable.

(Integer > 0)

C0 Constant.

Default = 0.0 (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 745

Proprietary Information of Altair Engineering


Field Contents

CMULT Constant multiplier.

Default = 1.0 (Real)

IDVi Identification number of the Independent Design Variable.

(Integer > 0)

Ci Coefficient multiplier for IDVi.

(Real)

Comments

1. DLINK defines the relationship.

This capability allows physical and non-physical design variables to be related such as
shell thickness and interpolating functions.

2. Independent IDVi’s can occur on the same DLINK entry only once.

3. CMULT and Ci can be used together to provide a simple means of scaling.

4. This card is represented as an optimization designvariablelink in HyperMesh.

746 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DLINK2

Bulk Data Entry

DLINK2 – Design Variable Link Defined by User-supplied Equation

Description

Defines a link of one design variable to one or more other design variables defined by a
DEQATN card. The equation inputs come from the referenced DESVAR values and the
constants defined on the DTABLE card.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DLINK2 ID DDVID EQUID


or FUNC

DESVAR DVID1 DVID2 DVID3 DVID4 DVID5 DVID6 DVID7

DVID8 DVID9 etc.

DTABLE LABL1 LABL2 LABL3 LABL4 LABL5 LABL6 LABL7

LABL8 etc.

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DLINK2 201 7 101

DESVAR 5 6

Altair Engineering OptiStruct 13.0 Reference Guide 747

Proprietary Information of Altair Engineering


Associated Cards

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DESVAR 5 X 0.0 -1.0 1.0

DESVAR 6 Y 0.0 -1.0 1.0

DESVAR 7 R 0.0 -1.0 1.0

DEQATN 101 RADIUS(X,Y) = SQRT(X**2+Y**2)

Field Contents

ID Relationship identity. Each DVPREL2 card must have a unique ID.

No default (Integer > 0)

DDVID Identification number of Dependent Design Variable.

(Integer > 0)

EQID Equation ID of DEQATN data.

No default (Integer > 0)

FUNC Function to be applied to the arguments. See comment 2.

(Character)

DESVAR DESVAR flag indicating DESVAR ID numbers follow.

DVIDi DESVAR ID.

No default (Integer > 0)

DTABLE DTABLE flag indicating DTABLE labels follow.

LABLi Constant label on DTABLE card.

No default (Character)

748 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. The main application for this entity is to link shape design variables with each other
through equations. DVPREL2 should be used for linking sizing design variables with each
other through equations.

2. The following functions can be used instead of an EQUID. If FUNC is used, the DEQATN
entry is no longer needed. The functions are applied to all arguments on the DLINK2
regardless of their type.

Function Description Formula

SUM Sum of arguments

AVG Average of arguments

SSQ Sum of square of arguments

Square root of sum of squares of


RSS
arguments

MAX Maximum of arguments

MIN Minimum of arguments

SUMABS Sum of absolute value of arguments

Average of absolute value of


AVGABS
arguments

MAXABS Maximum of absolute arguments

Minimum of absolute value of


MINABS
arguments

3. This card is represented as an optimization designvariablelink in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 749

Proprietary Information of Altair Engineering


DLOAD

Bulk Data Entry

DLOAD – Dynamic Load Combination or Superposition

Description

Defines a dynamic loading condition for frequency response problems as a linear combination
of load sets defined via RLOAD1 and RLOAD2 entries, or for transient problems as a linear
combination of load sets defined via TLOAD1 and TLOAD2 entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DLOAD SID S S1 L1 S2 L2 S3 L3

S4 L4 … … … … … …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DLOAD 5 1.0 2.0 101 2.0 102 2.0 103

-2.0 201

Field Contents

SID Load set identification number.

No default (Integer > 0)

S Scale factor.

No default (Real)

S# Scale factors.

No default (Real)

750 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

L# Load set identification numbers of RLOAD1 and RLOAD2 or TLOAD1 and


TLOAD2 entries.

No default (Integer > 0)

Comments

1. Dynamic load sets must be selected in the I/O Options or Subcase Information sections
with DLOAD=SID. (See I/O Options and Subcase Information DLOAD entry).

2. The load vector being defined by this entry is given by:

3. Each L# must be unique from any other L# on the same entry.

4. SID must be unique from all RLOAD1 and RLOAD2 or TLOAD1 and TLOAD2 entries.

5. A DLOAD entry may not reference a set identification number defined by another DLOAD
entry.

6. RLOAD1 and RLOAD2 loads and TLOAD1 and TLOAD2 loads may be combined only through
the use of the DLOAD entry.

7. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 751

Proprietary Information of Altair Engineering


DMIG

Bulk Data Entry

DMIG – Direct Matrix Input at Points

Description

Defines direct input matrices related to grid points. The matrix is defined by a single header
entry and one or more column entries. A column entry is required for each column with non-
zero elements.

Header Entry Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DMIG NAME "0" IFO TIN TOUT NC OL

Column Entry Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DMIG NAME GJ CJ G1 C1 A1

G2 C2 A2 G3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DMIG STIF 0 9 1 0 2

DMIG STIF 27 1 120 3 3.+5

120 4 2.5+10

DMIG STIF 28 1 123 3 6.+7

123 4 4.1+8

752 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

NAME Name of the matrix -- See comment 1.

No default (One to eight alphanumeric characters, the first must be


alphabetic)

IFO Form of matrix input.

No default (6 = Symmetric, 9 = rectangular)

TIN Type of matrix being input. (Ignored)

All data is read in as double precision. The number of significant digits is


equal to the number of digits in the input. The input can be free, short fixed
field, or long fixed field data.

TOUT Type of matrix that will be created. (Ignored)

All data is stored internally as double precision.

NCOL Number of columns in a rectangular matrix. Must be used when IFO = 9. Not
used when IFO = 6.

Default = blank (Integer > 0, or blank)

GJ Grid point identification number for column index.

No default (Integer > 0)

CJ Component number for grid point GJ.

No default (0 < Integer < 6)

Gi Grid point identification number for row index.

No default (Integer > 0)

Ci Component number for Gi for a grid point.

No default (0 < CJ < 6)

Ai Real value of a matrix element.

No default (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 753

Proprietary Information of Altair Engineering


Comments

1. Matrices may be selected for all solution sequences by the structural matrices before
constraints are applied.

2. The header entry containing IFO is required. Each no-null column is started with a GJ, CJ
pair. The entries for each row of that column follow. Only non-zero terms need be
entered. The terms may be input in arbitrary order. A GJ, CJ pair may be entered more
than once, but input of an element of the matrix more than once will produce a fatal
message.

3. Field 3 of the header entry must contain an integer 0.

4. A given off-diagonal element may be input either below or above the diagonal. While
upper and lower triangle terms may be mixed, a fatal message will be issued if an element
is input both below and above the diagonal.

5. The matrix names must be unique among all DMIGs.

6. The recommended format for rectangular matrices requires the use of NCOL and IFO = 9.
The number of columns in the matrix is NCOL. (The number of rows in all DMIG matrices is
always g-set size). The GJ term is used for the column index. The CJ term is ignored.

7. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).

8. The DMIG matrices can be multiplied by real numbers and combined when referenced by
the K2GG, M2GG, K42GG, K2PP, B2GG, and A2GG data.

9. The DMIG matrices can be multiplied by real numbers as they are assembled into the
global matrices using the PARAM data C2K, CP2, CB2, and CM2 for K2GG, K2PP, B2GG, and
M2GG data respectively.

754 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DMIGMOD

Bulk Data Entry

DMIGMOD – H3DDMIG Modification

Description

Defines changes in the contents of a super element from H3DDMIG input.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DMIGMO MTXNAM SHFGID SHFSPI SHFSPID_ SHFC ID SHFEID SHFRID


D E D F

HYBDAM METHOD SDAMP KDAMP METHOD_ SDAMP_ KDAMP_


P F F F

ORIGIN A1 A2 A3

GIDMAP GID1 GID1A GID2 GID2A GID3 GID3A

C IDMAP C ID1 C ID1A C ID2 C ID2A C ID3 C ID3A

RELOC PA1 PA2 PA3 PB1 PB2 PB3

Field Contents

MTXNAME Matrix name defined on ASSIGN,H3DDMIG.

No default (1 to 6 characters)

SHFGID All Grid identification numbers in the superelement are shifted by the
specified value. If this field is left blank, then a shift does not occur (see
comment 2).

Default = blank (Integer, or blank)

SHFSPID All SPOINT identification numbers in the superelement are shifted by the
specified value. If this field is left blank, then a shift does not occur (see

Altair Engineering OptiStruct 13.0 Reference Guide 755

Proprietary Information of Altair Engineering


Field Contents

comment 2).

Default = blank (Integer, or blank)

SHFSPID_F All Fluid SPOINT identification numbers in the superelement are shifted by the
specified value. If this field is left blank, then a shift does not occur (see
comment 2).

Default = blank (Integer, or blank)

SHFCID All Coordinate System identification numbers in the superelement are shifted
by the specified value. If this field is left blank, then a shift does not occur
(see comment 2).

Default = blank (Integer, or blank)

SHFEID All Element identification numbers in the superelement are shifted by the
specified value. If this field is left blank, then a shift does not occur (see
comment 2).

Default = blank (Integer, or blank)

SHFRID All Rigid Element identification numbers in the superelement are shifted by
the specified value. If this field is left blank, then a shift does not occur (see
comment 2).

Default = blank (Integer, or blank)

HYBDAMP Keyword for the remaining data for superelement damping.

METHOD Identification number of EIGRL card. Hybrid damping would be applied on the
superelements for the modes referred by EIGRL card. If blank, then applied
damping on all the modes.

Default = blank (Integer > 0, or blank)

SDAMP Identification number of TABDMP1 entry for modal damping.

No default (Integer > 0)

KDAMP If KDAMP is set to -1, viscous modal damping is entered into the complex
stiffness matrix as structural damping instead of viscous damping.

Default = 1 (Integer)

756 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

METHOD_F Identification number of EIGRL card. Hybrid damping would be applied on the
fluid part of superelement for the modes referred by the EIGRL card. If
blank, then modal damping is applied damping to all the fluid modes.

SDAMP_F Identification number of TABDMP1 entry for fluid modal damping of the
superelement.

No default (Integer > 0)

KDAMP_F If KDAMP_F is set to -1, viscous modal damping is entered into the complex
stiffness matrix as structural damping instead of viscous damping.

Default = 1 (Integer)

ORIGIN Keyword for defining the new ORIGIN for DMIG.

A1,A2,A3 Defines the new location of the origin of the DMIG.

Default = 0.0 (Real)

GIDMAP Keyword for defining mapped grid ID pairs.

GIDn,GIDnA Mapped grid ID pairs.

CIDMAP Keyword for defining mapped coordinate system ID pairs.

CIDn,CIDnA Mapped coordinate system ID pairs.

RELOC Keyword indicating that matching grid point ID pairs in the residual structure
and superelement are to follow (see comment 1).

PA1, PA2, ID’s of three non-collinear grid points in the residual structure.
PA3

PB1, PB2, ID’s of three non-collinear grid points in the superelement that will be
PB3 matched to corresponding grid points in the residual structure (defined by
PA1, PA2 and PA3).

Comments

1. The RELOC entry and its related fields define three matching grid point pairs on the
residual structure and the superelement. The superelement defined using ASSIGN,
H3DDMIG is relocated (translated and rotated, as required) such that the three non-

Altair Engineering OptiStruct 13.0 Reference Guide 757

Proprietary Information of Altair Engineering


collinear grids PB1, PB2, and PB3 coincide with PA1, PA2, and PA3, respectively on the
residual structure.

Figure 1: Matching three grids on the superelement with grids on the residual structure

2. Identification numbers of certain entities in a superelement can be modified during


H3DDMIG input. Negative integers can be input in the shift fields on this entry (see fields
beginning with ‘SHF’ above), however, care should be taken to ensure that the
identification numbers are not shifted to negative values. The values of identification
numbers after shifting should always be greater than zero, otherwise, the run will error
out.

758 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DOBJREF

Bulk Data Entry

DOBJREF – Design Objective for Minmax Problems

Description

Defines a response and its reference values for a minmax (maxmin) optimization problem.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DOBJREF DOID RID SID NEGREF POSREF LOWFQ HIGHFQ


/ LID / UID

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DOBJREF 22 3 ALL -1.0 1.0

DOBJREF 22 5 ALL -1.0 1.0

Associated Cards

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DRESP1 3 TOP DISP 3 488

DRESP1 5 BOTTOM DISP 3 601

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DOBJREF 23 14 ALL -1.0 1.0

Altair Engineering OptiStruct 13.0 Reference Guide 759

Proprietary Information of Altair Engineering


Associated Cards

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DRESP1 3 TOP DISP 3 488

DRESP1 5 BOTTOM DISP 3 601

Field Contents

DOID Design objective identification number.

(Integer > 0)

RID DRESP1 or DRESP2 identification number.

(Integer > 0)

SID Subcase identification number - use ALL if it applies to all subcases.

Default = ALL (Integer > 0, blank or ALL)

NEGREF/ LID NEGREF Reference value for a negative


response (should always be a
(Real < 0.0) negative real number or blank). See
Default = -1 comments 2, 3 and 5.

LID Table identification number of a


TABLEDi entry that specifies the
<Integer> negative reference as a function of
No default loading frequency. See comments
2, 3 and 5.

POSREF/ UID POSREF Reference value for a positive


response (should always be a
(Real > 0.0) positive real number or blank). See
Default = 1.0 comments 2, 3 and 5.

UID Table identification number of a


TABLEDi entry that specifies the
<Integer> positive reference as a function of
No default loading frequency. See comments
2, 3 and 5.

760 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

LOWFQ Lower bound on a loading frequency range.

Default = 0.0 (Real > 0.0)

HIGHFQ Upper bound on a loading frequency range.

Default = 1.0E+20 (Real > LOWFQ)

Comments

1. The same DOID can be used for multiple DOBJREF entries. If only one DOID is used, only
one MINMAX=DOID entry is needed in the Subcase Information section.

2. The use of reference values allows users to set up general minmax problems involving
different responses with different magnitudes. For these problems, the objective can be
defined as:

Minimize max(W1 ( x)/r1, W2 (x)/r 2 , ... Wk ( x)/ rk )

Or, alternatively:

Maximimze max(W1 ( x)/r 1, W2 ( x)/ r2 ,...Wk ( x)/ rk )

where, Wk are response values, and rk are corresponding reference values, which can
take different values depending on whether the response is positive or negative.

3. Typically, the target value or constraint value of a response can be used as its reference
value. So, instead of the traditional optimization problem where there is a single objective
and multiple constraints, the problem may be formulated as a minmax (maxmin)
optimization, where all the responses which were previously constrained are defined as
objectives and their bounds are used as reference values. This works toward pushing the
maximum ratio of response versus bound value as low as possible, thus increasing the
safety of the structure.

4. LOWFQ and HIGHFQ apply only to response types related to a frequency response
subcase (DRESPi, RTYPE = FRDISP, FRVELO, FRACCL, FRSTRS, FRSTRN, FRFORC, FRPRES
and FRERP). The reference values NEGREF and POSREF are applied only if the loading
frequency falls between LOWFQ and HIGHFQ. If ATTB of DRESP1 specifies a frequency
value, LOWFQ and HIGHFQ are ignored.

5. LID and UID identify a loading frequency dependent tabular input using TABLEDi. They are
applied analogous to LOWFQ, HIGHFQ detailed in comment 4.

6. This card is represented as a designobjectivereference in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 761

Proprietary Information of Altair Engineering


DOPTPRM

Bulk Data Entry

DOPTPRM – Design Optimization Parameters

Description

Defines design optimization parameters by overriding the defaults.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DOPTPRM PARAM1 VAL1 PARAM2 VAL2 PARAM3 VAL3 PARAM4 VAL4

PARM5 VAL5 Etc …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DOPTPRM MINDIM 10.0 OBJTOL 0.01

Field Contents

PARAMi Parameter name. See below for allowable names.

VALi Parameter value.

(Real or Integer)

The available parameters and their values are listed below (click the parameter name for
detailed parameter descriptions).

Parameter Brief Description Value

APPROX Switch to select the approximation FULL or REDUCED


type for stress/strain responses of Default = FULL
shells, composites and 1-D elements.

762 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Parameter Brief Description Value

CHECKER This option controls the 0 or 1


checkerboard-like element wise Default = 0
density distribution.

DDVOPT Control options for discrete design 1, 2, or 3


optimization. Default = 1

DELSHP The initial fractional move limit for Real > 0.0
topography/shape design variables Default = 0.2
(fractional difference between the
upper and lower bounds).

DELSIZ The initial fractional move limit for Real > 0


size design variables. Default = 0.5

DELTOP The initial fractional move limit for Real > 0


topology and free-size design Default = 0.5
variables.

DESMAX or Defines the maximum number of Integer > 0


MAXITER design iterations. Default = 30, or if MINDIM is
defined, default = 80

DISCRETE Discreteness parameter. Influences Real > 0.0


the tendency for elements in a
topology optimization to converge to Defaults
a material density of 0 or 1. 1.0 – general default.

2.0 - for solid dominant


structures with member size
control and no manufacturing
constraints.

DISCRT1D Discreteness parameter for 1-D Real > 0.0


elements. Default = DISCRETE

ESLMAX Maximum number of outer design Integer > 0


loops in the design of Multi-body Default = 30
dynamic systems and for nonlinear
optimization using ESLM.

ESLSOPT Controls the time step screen <0, 1>


strategy in the design of multi-body Default = 1
dynamic systems.

Altair Engineering OptiStruct 13.0 Reference Guide 763

Proprietary Information of Altair Engineering


Parameter Brief Description Value

ESLSTOL Controls the tolerance for screening 0.0 < Real < 1.0
out time steps in the design of multi- Default = 0.3
body dynamic systems.

GBUCK Controls the global buckling YES, NO, 1 or 0


constraint. Default = 0

MATINIT Defines the initial material fraction. Real between 0.0 and 1.0

MAX_BUCK Controls the maximum number of Integer > 0


buckling eigenvalues to be considered Default = 15
for each buckling subcase in an
optimization problem.

MINDENS Sets the minimum element material Real > 0.0


density. Default = 0.01

MINDIM Specifies the minimum diameter of Real > 0.0


members formed in a topology Default = no minimum member
optimization. size control

MMCHECK Parameter to ensure a checkerboard- Integer = 0,1


free solution. Default = 0

NESLEXPD Specifies the number of time steps Integer > 0


retained for optimization from each Default = 20
EXPDYN subcase. At each time step,
one ESL is generated.

NESLIMPD Specifies the number of time steps Integer > 0


retained for optimization from each Default = 20
IMPDYN subcase. At each time step,
one ESL is generated.

NESLNLGM Specifies the number of time steps Integer > 0


retained for optimization from each Default = 1
NLGEOM subcase. At each time step,
one ESL is generated.

OBJTOL Relative convergence criterion. Real > 0.0


Default = 0.005

OPTMETH Options to choose the optimization MFD, SQP, DUAL, BIGOPT

764 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Parameter Brief Description Value

algorithm. Default = See descriptions

REMESH Parameter to activate the remeshing Integer = 0,1


process. Default = 0

SHAPEOPT Optional parameter to select an <1, 2>


alternative shape optimization Default = 1
algorithm.

TMINPLY Defines the minimum ply thickness 0.0 < Real < min(Ti)
allowed for all plies of PCOMP’s
selected by DSIZE or DTPL design
variable definitions.

Comments

1. Some of the parameters may also be defined as separate entities in the I/O section of the
deck, using the previous (OS3.5) input format. Only one definition is allowed.

2. This card is represented as an opticontrols in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 765

Proprietary Information of Altair Engineering


DOPTPRM, APPROX

Parameter Values Description

APPROX < FULL or Approximation type switch for stress/strain responses for
REDUCED > shells, composites and 1D elements.
Default =
FULL When REDUCED is chosen, some stress/strain responses will
use the constant force approximation. This method has the
benefit of reducing the memory requirement for large
optimization problems (many stress/strain responses for
many size design variables). Another benefit is the reduction
in runtime if the bottleneck occurs due to sensitivity
analysis. You are encouraged to try the REDUCED option for
the large size optimization model, and, if the FULL option
results in the error 832 (Optimization problem is too big to be
solved by OptiStruct).

766 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DOPTPRM, CHECKER

Parameter Values Description

CHECKER < 0 or 1 > Checkerboard control option.


Default = 0
Use 0 for no checkerboard control.

Use 1 for global checkerboard control.

This option controls checkerboard-like element wise density


distribution.

The undesired side effect is that a layer of semi-dense


elements will remain at the transition from solid (fully dense
domain) to void. To reduce this side effect, you can
activate minimum member size control (MEMBSIZ on DTPL)
which has built-in checkerboard control.

MINDIM can be smaller than the mesh size if a large member


size is not desired. Minimum member size control has a 3-
phase iterative process in which the final phase targets the
removal of the semi-dense element layer. If manufacturing
constraints are applied, minimum member size control is
always activated. However, the final iterative phase will not
target the removal of semi-dense elements, as this may
have an adverse effect on manufacturing constraint
preservation.

Altair Engineering OptiStruct 13.0 Reference Guide 767

Proprietary Information of Altair Engineering


DOPTPRM, DDVOPT

Parameter Values Description

DDVOPT < 1, 2, 3 > Discrete Design Variable Option.


Default = 1
Use 1 for full discrete design optimization.

Use 2 for two-phased approach, a continuous


optimization phase followed by a discrete optimization
phase (starting from the continuous optimum).

Use 3 for a continuous optimization regardless of DDVAL


definitions. The bounds will be affected by DDVAL if
DDVAL bounds are more restrictive than those defined
on DESVAR.

768 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DOPTPRM, DELSHP

Parameter Values Description

DELSHP Real > 0.0 Initial fractional move limit for topography/shape design
Default = 0.2 variables. Defined as the fractional difference between
the upper and lower bounds.

Only the initial value of the move limits can be set.


Move limits are automatically adjusted to enhance
iterative stability and convergence speed.

The move limits for subsequent iterations may not be


greater than this initial move limit.

Altair Engineering OptiStruct 13.0 Reference Guide 769

Proprietary Information of Altair Engineering


DOPTPRM, DELSIZ

Parameter Values Description

DELSIZ Real > 0 Initial fractional move limit for size design variables.
Default = 0.5
Only the initial value of the move limits can be set.
Move limits are automatically adjusted to enhance
iterative stability and convergence speed.

The move limits for subsequent iterations may not be


greater than this initial move limit.

770 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DOPTPRM, DELTOP

Parameter Values Description

DELTOP Real > 0 Initial fractional move limit for topology and free-size
Default = 0.5 design variables.

Only the initial value of the move limits can be set.


Move limits are automatically adjusted to enhance
iterative stability and convergence speed.

The move limits for subsequent iterations may not be


greater than this initial move limit.

Altair Engineering OptiStruct 13.0 Reference Guide 771

Proprietary Information of Altair Engineering


DOPTPRM, DESMAX or MAXITER

Parameter Values Description

DESMAX or Integer > 0 Maximum number of design iterations.


Default = 30
MAXITER
or if MINDIM is
defined, Default =
80

772 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DOPTPRM, DISCRETE

Parameter Values Description

DISCRETE Real > 0.0 Discreteness parameter. Influences the tendency for
elements in a topology optimization to converge to a
Defaults material density of 0 or 1. Higher values decrease the
1.0 – general number of elements that remain between 0 and 1.
default.
Note: Recommended bounds are 0.0 and 2.0 for shells,
2.0 - for solid or 3.0 for solids.
dominant
structures with
member size
control and no
manufacturing
constraints.

Altair Engineering OptiStruct 13.0 Reference Guide 773

Proprietary Information of Altair Engineering


DOPTPRM, DISCRT1D

Parameter Values Description

DISCRT1D Real > 0.0 Discreteness parameter for 1D elements. Same


Default = DISCRETE effect as DISCRETE, but applies only to 1D
elements. It is often desirable to have a higher
discreteness for 1D elements than for 2D or 3D
elements.

774 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DOPTPRM, ESLMAX

Parameter Values Description

ESLMAX Integer > 0 Maximum number of outer design loops in the design
Default = 30 of multi-body dynamics systems, and for nonlinear
optimization using the equivalent static load
method.

If 0, then the optimization process is not activated.

Altair Engineering OptiStruct 13.0 Reference Guide 775

Proprietary Information of Altair Engineering


DOPTPRM, ESLSOPT

Parameter Values Description

ESLSOPT < 0, 1 > Controls the time step screen strategy in the design
Default = 1 of multi-body dynamics systems.

1 – Screens out time steps that do not play an


important role in the design of multi-body dynamics
systems.

0 – Does not screen out time steps. All of the steps


in the multi-body dynamics analysis are involved in
the design process. Refer to Equivalent Static Load
Method (ESLM) for more information.

776 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DOPTPRM, ESLSTOL

Parameter Values Description

ESLSTOL 0.0 < Real < 1.0 Controls the tolerance for screening out time steps
Default = 0.3 in the design of multi-body dynamic systems. Valid
only when DOPTPRM, ESLSOPT is 1.

The smaller value it has, the smaller number of time


steps the design process handles, which makes the
design process even faster. Too small a value may
cause the design process to diverge though.
Therefore, if the number of time steps retained by
ESLSTOL is less than 10, the 10 most dominant time
steps will be involved in the optimization process. If
the value is 1.0, this is equivalent to DOPTPRM,
ESLSOPT, 0. That is, all of the steps in the multi-
body dynamic analysis are involved in the design
process, which causes more CPU time to be used.

Altair Engineering OptiStruct 13.0 Reference Guide 777

Proprietary Information of Altair Engineering


DOPTPRM, GBUCK

Parameter Values Description

GBUCK YES, NO, 1 or 0 Controls global buckling constraint.


Default = 0
Use 0, NO, or omit this parameter for no global buckling
constraint.

Use 1 or YES to activate global buckling constraint.

When activated, the global buckling constraint affects


those subcases in which buckling eigenvalues (LAMA) are
constrained. For these subcases, when this parameter is
activated, only a single buckling mode needs to be
constrained with a lower bound. The GBUCK parameter
will then ensure that all buckling eigenvalues that are
less than or equal to the lower bound defined in this
constraint will be considered within the optimization
problem.

More than one buckling eigenvalue constraint (or if the


single constraint is not a lower bound) in any buckling
subcase will cause termination with an error.

The MAX_BUCK parameter on the DOPTPRM card controls


the maximum number of buckling modes for each subcase
that are considered in the optimization. The EIGRL card
referenced in the buckling subcase controls the number
of modes calculated at each iteration.

778 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DOPTPRM, MATINIT

Parameter Values Description

MATINIT Real between This parameter declares the initial material fraction. For
0.0 and 1.0 topology optimization runs with mass as the objective,
default is 0.9. For runs with constrained mass, the
default is reset to the constraint value. If mass is not
the objective function and is not constrained, the
default is 0.6.

Altair Engineering OptiStruct 13.0 Reference Guide 779

Proprietary Information of Altair Engineering


DOPTPRM, MAX_BUCK

Parameter Values Description

MAX_BUCK Integer > 0 Controls maximum number of buckling eigenvalues to be


Default = 15 considered for each buckling subcase in the optimization
problem.

Can only exist if GBUCK exists.

Only up to MAX_BUCK eigenvalues are considered for


each buckling subcase.

If the user-defined MAX_BUCK is less than 15 when auto


screening is turned on, MAX_BUCK will be reset to 15.
If more buckling modes need to be involved for a
problem, explicitly specify MAX_BUCK (MAX_BUCK>15).
To reduce the computational cost, OptiStruct
automatically and dynamically adjusts the upper bound
of the eigenvalue range on the EIGRL card for each
buckling subcase at each iteration and only the
eigenvalues that are possibly retained in the
optimization would be calculated.

780 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DOPTPRM, MINDENS

Parameter Values Description

MINDENS Real > 0.0 Minimum element material density. Sets a lower limit
Default = 0.01 on the amount of material that can be assigned to any
design element. Extremely low values for this
parameter can result in an ill-conditioned stiffness
matrix.

Altair Engineering OptiStruct 13.0 Reference Guide 781

Proprietary Information of Altair Engineering


DOPTPRM, MINDIM

Parameter Values Description

MINDIM Real > 0.0 Specifies the minimum diameter of members formed
Default = no in a topology optimization. This command is used to
minimum member eliminate small members.
size control

782 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DOPTPRM, MMCHECK

Parameter Values Description

MMCHECK Integer = 0,1 The use of this parameter, in conjunction with MINDIM,
Default = 0 will ensure a checkerboard-free solution, although with
the undesired side effect of achieving a solution that
involves a large number of semi-dense elements, similar
to the result of using CHECKER=1. Therefore, use this
parameter only when it is necessary.

Altair Engineering OptiStruct 13.0 Reference Guide 783

Proprietary Information of Altair Engineering


DOPTPRM, NESLEXPD

Parameter Values Description

NESLEXPD Integer > 0 This parameter specifies the number of time steps
Default = 20 retained for optimization from each EXPDYN subcase.
At each time step, one ESL (equivalent static load) is
generated.

The termination time (TTERM) of the subcase is always


retained.

If 0, all of the time steps are retained.

The total number of time steps is determined by the


duration of the subcase (difference in TTERM between
current and previous subcases) and animation output
control (TA0 and DTA on XSTEP card).

While retaining fewer time steps will result in less


computational time in the inner loop of the ESL method,
very low number of retained time steps could result in
many outer loops required or even divergence of the
solution in the outer loop.

784 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DOPTPRM, NESLIMPD

Parameter Values Description

NESLIMPD Integer > 0 This parameter specifies the number of time steps
Default = 20 retained for optimization from each IMPDYN subcase.
At each time step, one ESL (equivalent static load) is
generated.

The termination time (TTERM) of the subcase is always


retained.

If 0, all of the time steps are retained.

The total number of time steps is determined by the


duration of the subcase (difference in TTERM between
current and previous subcases) and animation output
control (TA0 and DTA on TSTEPNX card).

While retaining fewer time steps will result in less


computational time in the inner loop of the ESL method,
a very low number of retained time steps could result in
many outer loops required or even divergence of the
solution in the outer loop.

Altair Engineering OptiStruct 13.0 Reference Guide 785

Proprietary Information of Altair Engineering


DOPTPRM, NESLNLGM

Parameter Values Description

NESLNLGM Integer > 0 This parameter specifies the number of time steps
Default = 1 retained for optimization from each NLGEOM subcase.
At each time step, one ESL (equivalent static load) is
generated.

The termination time (TTERM) of the subcase is always


retained.

If 0, all of the time steps are retained.

The total number of time steps is determined by the


duration of the subcase (difference in TTERM between
current and previous subcases) and animation output
control (TA0 and DTA on NLPARMX card).

While retaining fewer time steps will result in less


computational time in the inner loop of the ESL method,
a very low number of retained time steps could result in
many outer loops required or even divergence of the
solution in the outer loop.

786 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DOPTPRM, OBJTOL

Parameter Values Description

OBJTOL Real > 0.0 Relative convergence criterion. If relative change in


Default = 0.005 the objective function between two design iterations is
less than OBJTOL, then optimization stops.

A relative change in the objective function of 0.005 is


the same as a 0.5% change in the objective function.

Altair Engineering OptiStruct 13.0 Reference Guide 787

Proprietary Information of Altair Engineering


DOPTPRM, OPTMETH

Parameter Values Description

OPTMETH < MFD, SQP, Options to choose the optimization algorithm:


DUAL, BIGOPT >
Default = See MFD = Method of feasible directions
description and SQP = Sequential Quadratic Programming
Note DUAL = Dual Optimizer based on separable convex
approximation.
BIGOPT = Large scale optimization algorithm.

The DUAL algorithm should be used for concept level


optimization (Topology, free-size and Topography) since
such problems typically involve a very large number of
design variables.

For size and shape optimization, primal methods (MFD


and SQP) and BIGOPT are more suitable since the
approximate problem typically involves coupled terms due
to advanced approximation formulation utilizing
intermediate variables and responses. MFD has been and
remains the default optimizer.

Note:

During a run, the corresponding optimization algorithms


are automatically selected by OptiStruct based on the
optimization type. The use of this parameter will override
the defaults.

788 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DOPTPRM, REMESH

Parameter Values Description

REMESH Integer = 0, 1 This parameter specifies if the remeshing process will


Default = 0 be activated when the optimization runs into element
quality error.

1 – Yes. When optimization runs into element quality


error, the remeshing process will be activated to
improve element quality. After remeshing is completed,
the optimization process will then continue based on
the remeshed model.

0 – No. The remeshing process will not be activated


regardless of whether element quality error occurs.

Note:

1. When an optimization run results in element quality


error (usually during Shape, Free-shape or
Topography optimization), OptiStruct calls
HyperMesh in batch mode. The model from the
latest optimization iteration is automatically loaded
into HyperMesh and remeshing is performed to
improve element quality.

HyperMesh, then automatically exports a new input


deck named *_rmsh###.fem (### = 001, 002, 003,
represents the remeshing round number) that is
loaded into OptiStruct to continue the optimization
run with the remeshed model.

2. When an element quality error occurs, OptiStruct


12.0.210 will automatically check the HyperMesh
version.

If HyperMesh version 12.0.110 or later is installed,


the new function *remesh_optistruct will be
called to accomplish the remeshing process. For all
other versions (HyperMesh 12.0 or earlier) an old
function, previously used in 12.0, is called.

3. Installing the latest version of HyperMesh


(12.0.110 or later) is recommended to access all
the latest improvements in the
*remesh_optistruct function.

Altair Engineering OptiStruct 13.0 Reference Guide 789

Proprietary Information of Altair Engineering


DOPTPRM, SHAPEOPT

Parameter Values Description

SHAPEOPT Integer = 1, 2 Defines an optional parameter to select an alternative


Default = 1 shape optimization algorithm. This algorithm can be
selected when non-moving shapes are encountered in
the optimization.

1 – Default algorithm for shape optimization.

2 – Selects the alternate algorithm for shape


optimization.

If discrete design variables are present, it is


recommended to use this parameter along with design
optimization parameter, DDVOPT=2.

790 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DOPTPRM, TMINPLY

Parameter Values Description

TMINPLY 0.0 < Real < min(Ti) Defines the minimum ply thickness allowed for all
plies of PCOMPs selected by DSIZE or DTPL design
variable definitions. Should be smaller than the
minimum of all relevant Ti on the selected PCOMPs.
Check its compatibility with volume constraint if
applied. Note also that for volume fraction
calculation, TMINPLY is not treated as none design
volume in the same way as T0 for regular PSHELLs.

Buckling responses for composite structures may be


considered for free-size and topology optimization
when this parameter is non-zero.

Altair Engineering OptiStruct 13.0 Reference Guide 791

Proprietary Information of Altair Engineering


DPHASE

Bulk Data Entry

DPHASE – Dynamic Load Phase Lead

Description

Defines the phase lead term in the equation of the dynamic loading function. DPHASE is
used in conjunction with RLOAD1 and RLOAD2 entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DPHASE SID P1 C1 TH1 P2 C2 TH2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DPHASE 5 33 1 3.4 34 1 3.4

Field Contents

SID Identification number.

No default (Integer > 0)

P1, P2 Grid or scalar point identification number.

No default (Integer > 0)

C1, C2 Component number.

No default (Integers 1 through 6, or 0 for scalar points)

TH1, TH2 Phase lead in degrees.

No default (Real)

792 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. One or two dynamic load phase lead terms may be defined on a single entry.

2. SID must be referenced on a RLOAD1 or RLOAD2 entry for the formulae that define how
the phase lead is used.

3. A DAREA entry should be used to define a load at P# and C#.

4. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).

5. This card is represented as a constraint load in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 793

Proprietary Information of Altair Engineering


DRAPE

Bulk Data Entry

DRAPE – Draping Information for Ply-based Composite Definition

Description

Defines the draping data for plies used in ply-based composite definition.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DRAPE ID

DTYPE1 DID1 T1 THETA1

DTYPE2 DID2 T2 THETA2

...

Field Contents

ID Unique draping identification number.

No default (Integer > 0)

DTYPE# Entity type.

No default (ELEM, SET, or ALL)

DID# Entity number. Must refer to an element (for ELEM) or SET (for
SET) bulk data entry. Must be blank for ALL.

No default (Integer > 0 or blank)

T# Thinning factor.

Default = 1.0 (Real or blank)

THETA# Angle variation.

Default = 0.0 (Real or blank)

794 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DREPADD

Bulk Data Entry

DREPADD – Addition of Response Selection to be Reported without being Constrained

Description

Creates a combination of several DREPORT sets that can be referenced by a subcase.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DREPAD DRID DR1 DR2 DR3 Dr4 DR5 DR6 DR7


D

DR8 etc.

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DREPAD 101 10 20 30
D

Field Contents

DRID DREPADD identification number.

(Integer > 0)

DRi DREPORT ID number.

(Integer > 0)

Comments

1. The DREPADD entry is selected by a REPSUB or REPGLB in the Subcase Information


section.

2. All DRi must be unique.

3. All DRID must be unique with respect to all DRi (DREPORT IDs).

Altair Engineering OptiStruct 13.0 Reference Guide 795

Proprietary Information of Altair Engineering


DREPORT

Bulk Data Entry

DREPORT – Report Unconstrained Responses

Description

The DREPORT card is used in the bulk data section to report responses, defined by DRESP1,
DRESP2 and DRESP3 cards, to the output file, which are not constrained or used as the
objective function, as defined by the optimization problem.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DREPOR DRID RID LALLOW UALLOW NL NU


T

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DREPOR 1 1 1.0 5.0 2 5


T

Associated Cards

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DRESP1 1 TOPN DISP 3 4668

Field Contents

DRID Report identification number.

(Integer > 0)

RID DRESP1, DRESP2, or DRESP3 identification number.

(Integer > 0)

796 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

LALLOW Optional lower bound on response for reporting purposes.

(Real or blank)

UALLOW Optional upper bound on response for reporting purposes.

(Real or blank)

NL Optional number of lowest responses to report. See comment 3.

(Integer or blank)

NU Optional number of highest response to report. See comment 3.

(Integer or blank)

Comments

1. The DREPORT DRID is selected in the Subcase Information section by the REPSUB or
REPGLB cards and/or referenced by the DREPADD card.

2. For any DRID, the associated RID can be referenced only once.

3. If NL=1, only the lowest response in the range [LALLOW, UALLOW] (if specified) is
reported. If NU=1, only the highest response in the range [LALLOW, UALLOW] (if
specified) is reported.

Altair Engineering OptiStruct 13.0 Reference Guide 797

Proprietary Information of Altair Engineering


DRESP1

Bulk Data Entry

DRESP1 – Optimization Design Response

Description

A response, or set of responses, that are the result of a design analysis iteration. These
responses can be used as a design objective or as design constraints.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DRESP1 ID LABEL RTYPE PTYPE REGION ATTA ATTB ATT1

ATT2 … … … … … … …

EXC L EID1 EID2 EID3 EID4 EID5 EID6 EID7

EID8 … … …

EXTN RANDID

Examples

The maximum principal stress in PSHELL PID 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DRESP1 99 SS11 STRESS PSHELL 7 1

or

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DRESP1 99 SS11 STRESS PSHELL SMP1 1

798 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


The maximum principal stress in elements 2001-2004

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DRESP1 88 SS11 STRESS ELEM 7 2001

2002 2003 2004

The combined mass of PSHELL PID 2, 4, 7

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DRESP1 77 TMASS MASS PSHELL SUM 2

4 7

Field Contents

ID Response identification number. Each DRESP1 card must have a unique ID.

No default (Integer > 0)

LABEL User-defined name for the response.

No default (Character)

RTYPE Type of response that is defined – mass, volume, freq, disp, stress, etc.

No default (See Responses and attributes for DRESP1 card for full list of
response types)

PTYPE If a property response, then PTYPE is the property type, for example,
PSHELL. It is used in conjunction with ATT1 to identify the unique
property. If an element response, then PTYPE = ELEM. It is used in
conjunction with ATTi to identify the element IDs. For material responses,
PTYPE is MAT and ATTi are material IDs. For grid responses, PTYPE is blank
and ATTi are grid IDs. (See Responses and attributes for DRESP1 card for
further information).

No default (ELEM, MAT, PSHELL, PCOMP, PCOMPG, PLY, PROD, PSOLID,


PELAS, PBAR, PBARL, PBEAM, PBEAML, PFBODY, MBREQM, MBREQE, or
blank)

Altair Engineering OptiStruct 13.0 Reference Guide 799

Proprietary Information of Altair Engineering


Field Contents

REGION Region identifier.

Default = blank (Integer > 0 or blank, See comment 2)

ATTA, The attributes of a response where further definition is required.


ATTB
No default (See Responses and attributes for DRESP1 card for further
information)

ATTi PID, MID, EID, MBREQM ID, MBREQE ID, PFBODY ID or Grid ID as referenced
by PTYPE and RTYPE. (See Responses and attributes for DRESP1 card for
further information).

No default (Integer > 0)

EXCL EXCL flag indicating that IDs of elements excluded from the response
follow.

EIDi Element ID. For these elements, no response will be generated.

No default (Integer > 0)

EXTN EXTN flag indicating that extended attribute definition follows. RANDID is
currently supported as an extended attribute definition and is the RANDPS
ID to which the response applies. See comments 30 and 31.

Responses and Attributes


Center of Gravity and Moment of Inertia Item Codes
Static Stress/Strain Item Codes
Static Stress Item Codes for Bar Elements using PBARL, PBEAML Properties
Static Stress/Strain Item Codes for Composites
Static Failure Item Codes for Composites
Static Force Item Codes
Frequency Response Displacement, Velocity, and Acceleration Item Codes
Frequency Response Pressure Item Codes
Frequency Response Stress/Strain Item Codes
Frequency Response Force Item Codes
PSD/RMS Displacement, Velocity, and Acceleration Item Codes
PSD/RMS Pressure Item Codes
PSD/RMS Stress/Strain Item Codes
MBD Displacement Item Codes

800 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MBD Velocity/Acceleration Item Codes
MBD Force Item Codes

Comments

1. VOLFRAC is equivalent to MATFRAC in previous versions of OptiStruct. MATFRAC is still


supported.

2. Responses of the same RTYPE with the same region identifier are grouped together into
the same region. If the region identifier is blank, elements identified by an ATTi field
(when PTYPE = ELEM) are grouped together into the same region, but for properties or
materials, each property or material identified by an ATTi field will form its own region.
Refer to the User's Guide section Constraint Screening for a more detailed explanation.

For composite responses (RTYPE = CSTRESS, CSTRAIN, CFAILURE; PTYPE = PCOMP,


PCOMPG), each ply is given its own region. However, if a region identifier is defined
explicitly for the entire lay-up (ATTB=ALL), this region identifier applies to all plies. It is
not recommended to do this.

3. DRESP1 entries must have unique identification numbers with respect to DRESP2 and
DRESP3 entries.

4. In normal modes analysis, the frequencies are in Hz (cycles/time).

5. The total displacement can be requested using ATTA=7; the total rotation using ATTA=8.

6. PTYPE = PCOMP, PCOMPG can be selected for RTYPE = STRESS or RTYPE = STRAIN, in
which case homogenized stresses or strains are used. RTYPE = CSTRESS or RTYPE =
CSTRAIN should be used instead for composite responses.

7. Stresses are element stresses. For CBAR, CBEAM, stresses are normal (axial) stresses for
the element.

8. VOLFRAC and MASSFRAC can only be applied to topology design domains. OptiStruct will
terminate with an error if this is not the case.

9. MASS, MASSFRAC, COG and INERTIA responses are not available for PBUSH, PDAMP,
PELAS, PGAP, PVISC, and PWELD.

10. VOLUME and VOLFRAC responses are not available for CONM2, PDAMP, PELAS, PGAP,
PMASS, and PVISC.

11. The VOLUME of a single CWELD element is 1.0. The response then is the number of
welds.

12. WCOMP, WFREQ, COMB require the definition of WEIGHT and/or MODEWEIGHT subcase
commands. If WEIGHT or MODEWEIGHT are not defined, the following defaults apply:

RTYPE Applicable subcase commands Default

WCOMP WEIGHT in static subcases WEIGHT = 1.0 for all static subcases.

WFREQ MODEWEIGHT in normal modes MODEWEIGHT (1) = 1.0 in most cases for
subcase topology optimization.

Altair Engineering OptiStruct 13.0 Reference Guide 801

Proprietary Information of Altair Engineering


RTYPE Applicable subcase commands Default

MODEWEIGHT (7) = 1.0 if no SPC is


defined for the subcase, EIGRL does not
define a V1 > 0.0, and it is solving for
more than 6 modes or all modes below an
upper bound.

COMB WEIGHT in static subcases WEIGHT = 1.0 for all static subcases.

MODEWEIGHT in normal modes


subcase

13. CSTRESS, CSTRAIN, and CFAILURE are only available for PCOMP, PCOMPG.
ATTB = # refers to a ply on a PCOMP.
Example: DRESP1, 12, PLY23, CSTRESS, PCOMP, SMAP, 23, 43.
ATTB = G# refers to a global ply on a PCOMPG.
Example: DRESP1, 12, GLOBAL11, CFAILURE, PCOMPG, HILL, G11, 17.
ATTB must be blank for PLY response type.

14. STRAIN responses not applicable for CELAS.

15. Composite Stress/Strain item codes S1Z and S2Z for Shear-1Z and Shear-2Z are for
CSTRESS only, these are not available for CSTRAIN.

16. Lower bound constraints are not allowed on von Mises stress.

17. LABEL must begin with an alphabetical character.

18. Responses that do not exist are ignored, and a warning is issued.

19. EXCL only applies to RTYPE = STRESS, STRAIN, FORCE, CSTRESS, CSTRAIN, CFAILURE,
FRSTRS, FRSTRN, and FRFORC response types.

20. For RTYPE = MASS, MASSFRAC, VOLUME, VOLFRAC, COG, INERTIA, BEADFRAC, and
COMP; ATTi can only be blank if PTYPE is also blank. ATTi blank means that all relevant
entities are included. They all belong to the same region for constraint screening.

21. For RTYPE=STRESS, STRAIN, FORCE, FRSTRS, FRSTRN, FRFORC, CSTRESS, CSTRAIN, and
CFAILURE; ATTi can only be blank if PTYPE is a property type (not allowed when PTYPE is
"ELEM"). ATTi blank means that all entities of the defined PTYPE are selected.

22. For RTYPE = MASS, MASSFRAC, MBMASS, VOLUME, VOLFRAC, COG, MBCOG, INERTIA,
MBINER, COMP, and BEADFRAC; ATTB = COMB results in the creation of a single response
for the combination of all ATTi entities.

23. For RTYPE=MASS, MBMASS, VOLUME, MBCOG, MBINER, COMP, MASSFRAC, and VOLFRAC;
ATTB=SUM is the same as ATTB=COMB.

24. For RTYPE = FRDISP, FRVELO, FRACCL, FRSTRS, FRSTRN, FRFORC, FRERP, PSDDISP,
PSDVELO, PSDACCL, and PSDPRES the following functions can be applied through the
character input on ATTB. The formulas are applied across all loading frequencies. The
use of MAX can be very inefficient computationally and it is better to leave ATTB blank
and let constraint screening take care of it.

802 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Function Description Formula

SUM Sum of arguments

AVG Average of arguments

SSQ Sum of square of arguments

Square root of sum of squares of


RSS
arguments

MAX Maximum of arguments

MIN Minimum of arguments

Sum of absolute value of


SUMABS
arguments

Average of absolute value of


AVGABS
arguments

MAXABS Maximum of absolute arguments

Minimum of absolute value of


MINABS
arguments

25. For RTYPE = INERTIA, the Moment of Inertia is with reference to the center of gravity.
The Moment of Inertia of the whole model is referred to the center of gravity of the whole
model. The Moment of Inertia of each property or material is referred to the center of
gravity of that property or material.

26. For acoustic optimization, pressure responses are defined using RTYPE=FRPRES; however,
it is acceptable to define a pressure response on a fluid grid as RTYPE=FRDISP with ATTA
as one of M-TX, R-TX or I-TX, internally it will be converted to FRPRES (with M-TX/R-TX/
I-TX interpreted as M-PRES/R-PRES/I-PRES). Likewise, RTYPE=PSDDISP or RMSDISP are
accepted in place of PSDPRES or RMSPRES, respectively.

27. For RTYPE = MBDIS, MBVEL, MBACC, or MBFRC, the PTYPE must be MBREQM. These four
response types must be defined using MARKERs, and requested by MBREQM. For RTYPE =
MBEXPR, the PTYPE must be MBREQE. The response must be requested by MBREQE. For

Altair Engineering OptiStruct 13.0 Reference Guide 803

Proprietary Information of Altair Engineering


RTYPE = MBMASS, MBCOG, or MBINER, the PTYPE must be PFBODY.

28. MBREQE referenced in DRESP1 must have single expression although MBREQE allows up to
6 expressions for analysis output.

29. MBD system level responses must be scalar quantities. Thus, THE ATTB field must have
one of the following - MAX, MIN, MAXABS, or MINABS so that time dependent vectors can
be converted to scalar quantities.

30. Legacy data with RANDPS ID defined on the PTYPE or ATTB entry is also supported.

31. A blank field for RANDID on the EXTN extended attributes entry indicates that all RANDPS
cards in the input file will be used.

32. “Cluster Size” represents the number of elements around the specified element whose
stress contributions are included in the calculation of the individual element’s stress
contribution. The contributions of the elements in the cluster are weighted based on their
distance to the center of the cluster (Available for Shell and Solid elements). Weighting
element stress contributions using “Cluster Size” is generally useful in models with stress
gradients or stress concentrations in the design space. If the stress distribution within
the selected element cluster is uniform, there may not be any significant difference in the
stress response. A separate result type “Element Stress Cluster” is available in the
_s#.h3d file and stress results based on element cluster response(s) can be viewed in
HyperView by selecting Element Stresses Cluster in the Result type: drop-down menu.

33. This card is represented as an optimization response in HyperMesh.

804 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DRESP1 - Responses and Attributes

Response
RTYPE PTYPE ATTA ATTB ATTi EXTN
s

Mass MASS PTYPE, - COMB**, SUM PID, MID or -


"MAT", or or blank blank*
blank

Fraction of MASSFR PTYPE, - COMB**, SUM, PID, MID or -


mass AC "MAT", or or blank blank*
blank

Volume VOLUME PTYPE, - COMB**, SUM PID, MID or -


"MAT", or or blank blank*
blank

Fraction of VOLFRA PTYPE, - COMB**, SUM, PID, MID or -


design C "MAT", or or blank blank*
volume blank

Center of COG PTYPE, Center of COMB** PID, MID or -


Gravity "MAT", or Gravity item or blank blank*
blank code

Moment of INERTIA PTYPE, Moment of COMB** PID, MID or -


Inertia "MAT", or Inertia item or blank blank*
blank code

Complianc COMP PTYPE, - COMB**, SUM PID, MID or -


e of a "MAT", or or blank blank*
static blank
subcase

Static DISP - Static - Grid ID -


displaceme displacement
nt Component

Mode DISP - Component Mode # Grid ID -


shape

Frequency FREQ - Normal mode # - - -


of a
normal
mode

Altair Engineering OptiStruct 13.0 Reference Guide 805

Proprietary Information of Altair Engineering


Response
RTYPE PTYPE ATTA ATTB ATTi EXTN
s

Eigenvalue LAMA - Buckling mode - - -


of a #
buckling
mode

Static STRESS PTYPE or Static stress Cluster Size PID, EID -


stress of "ELEM" item code ****** or or blank***
homogeno blank
us material

Static STRAIN PTYPE or Static strain - PID, EID -


strain of "ELEM" item code or blank***
homogeno
us material

Static CSTRES "PCOMP", Composite ALL, Ply No. PID, EID, Ply -
stress in a S "PCOMPG" Stress item or ‘G#**** ID,
composite , "PLY", code (Default = 1) or blank***
or blank*****
lay-up or "ELEM"

Static CSTRAI "PCOMP", Composite ALL, Ply No. PID, EID, Ply -
strain in a N "PCOMPG" Strain item or ‘G#**** ID,
composite , "PLY", code (Default = 1) or blank***
or blank*****
lay-up or "ELEM"

Static CFAILU "PCOMP", Composite ALL, Ply No. PID, EID, Ply -
failure in a RE "PCOMPG" Failure item or ‘G#**** ID,
composite , "PLY", code (Default = 1) or blank***
or blank*****
lay-up or "ELEM"

Static FORCE PTYPE or Static force - PID, EID -


force "ELEM" item code or blank***

Frequency FRDISP - Frequency Frequency Value. Grid ID -


response Response (Blank, Real >
displacement 0.0 or Character)
displaceme component
nt

Frequency FRVELO - Frequency Frequency Value Grid ID -


response Response (Blank, Real >
velocity velocity 0.0 or Character)
component

806 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Response
RTYPE PTYPE ATTA ATTB ATTi EXTN
s

Frequency FRACCL - Frequency Frequency Value Grid ID -


response Response (Blank, Real >
acceleratio acceleration 0.0 or Character)
component
n

Frequency FRSTRS PTYPE Frequency Frequency Value PID, EID -


response or Response (Blank, Real > or blank***
stress "ELEM" Stress item 0.0 or Character)
code

Frequency FRSTRN PTYPE Frequency Frequency Value PID, EID -


response or Response (Blank, Real > or blank***
strain "ELEM" Strain item 0.0 or
code Character)

Frequency FRFORC PTYPE Frequency Frequency Value PID, EID -


response or Response (Blank, Real > or blank***
force "ELEM" Force item 0.0 or Character)
code

Frequency FRERP - - Frequency Value Panel ID


response (Blank, Real >
equivalent 0.0 or Character)
radiated
power

Acoustic FRPRES - M-PRES, R- Frequency Value. Grid ID -


pressure PRES or I- (Blank, Real >
PRES 0.0 or Character)

PSD PSDDIS - PSD/RMS item Frequency Value. GRID ID RANDPS


displaceme P code (Blank, Real > ID
nt 0.0 or Character)

Frequency Value.
PSD PSDVEL - PSD/RMS item (Blank, Real > GRID ID RANDPS
velocity O code 0.0 or Character) ID

PSD PSDACC - PSD/RMS item Frequency Value. GRID ID RANDPS


acceleratio L code (Blank, Real > ID
n 0.0 or Character)

PSD stress PSDSTR PTYPE PSD/RMS item Frequency PID, EID RANDPS
S or code Value or blank*** ID

Altair Engineering OptiStruct 13.0 Reference Guide 807

Proprietary Information of Altair Engineering


Response
RTYPE PTYPE ATTA ATTB ATTi EXTN
s

"ELEM" (Blank, Real >


0.0 or
Character)

PSD strain PSDSTR PTYPE PSD/RMS item Frequency PID, EID RANDPS
N or code Value or blank*** ID
"ELEM" (Blank, Real >
0.0 or
Character)

PSD PSDPRE - PRES Frequency GRID ID RANDPS


pressure S Value. ID
(Blank, Real >
0.0 or
Character)

RMS RMSDIS - PSD/RMS item - GRID ID RANDPS


displaceme P code ID
nt

RMS RMSVEL - PSD/RMS item - GRID ID RANDPS


velocity O code ID

RMS RMSAC - PSD/RMS item - GRID ID RANDPS


acceleratio CL code ID
n

RMS stress RMSSTR PTYPE PSD/RMS item - PID, EID RANDPS


S or code or blank*** ID
"ELEM"

RMS strain RMSSTR PTYPE PSD/RMS item - PID, EID RANDPS


N or code or blank*** ID
"ELEM"

RMS RMSPRE - PRES - GRID ID RANDPS


pressure S ID

Static WCOMP - - - - -
compliance
weighted
across all

808 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Response
RTYPE PTYPE ATTA ATTB ATTi EXTN
s

subcases

Frequency WFREQ - - - - -
weighted
across
reciprocal
eigenvalue
s

Combined COMB - - - - -
static
compliance
and
frequency
index
(Combined
Complianc
e Index)

Bead BEADFR - - COMB** or DTPGID -


discretene AC blank or blank*
ss fraction
for
topograph
y design
space
(0.0 <
BEADFRAC
< 1.0)

MBD MBDIS MBREQM MBD MAX, MIN, MBREQM ID -


displaceme Displacement MAXABS,
nt item code MINABS

MBD MBVEL MBREQM MBD Velocity MAX, MIN, MBREQM ID -


velocity item code MAXABS,
MINABS

MBD MBACC MBREQM MBD MAX, MIN, MBREQM ID -


acceleratio Acceleration MAXABS,
n item code MINABS

MBD force MBFRC MBREQM MBD Force MAX, MIN, MBREQM ID -

Altair Engineering OptiStruct 13.0 Reference Guide 809

Proprietary Information of Altair Engineering


Response
RTYPE PTYPE ATTA ATTB ATTi EXTN
s

item code MAXABS,


MINABS

MBD MBEXPR MBREQE - - MBREQE ID -


expression

Mass of MBMAS PFBODY - COMB, SUM or PFBODY ID -


flexible S blank
body

Center of MBCOG PFBODY Center of COMB, SUM or PFBODY ID -


gravity of Gravity item blank
flexible code
body

Moment of MBINER PFBODY Moment of COMB, SUM or PFBODY ID -


inertia of Inertia item blank
flexible code
body

Fatigue FATIGU PTYPE or LIFE, DAMAGE - PID, EID or -


results E "ELEM" or FOS blank***

Temperatu TEMP - - - Grid ID -


re

SPC Component ID
SPCFOR - - Grid ID -
Forces CE (1-6) –
(Reaction Degrees of
forces/ Freedom
moments)

Grid point Component ID


GPFORC Grid ID - EID -
force E (1-6) –
balance Degrees of
results Freedom

* ATTi can only be blank when PTYPE is also blank, and means that all relevant
entities will be included. See comment 20 on the DRESP1 page.

** ATTB = COMB – Response represents a single response for the combination of all

810 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Response
RTYPE PTYPE ATTA ATTB ATTi EXTN
s

ATTi entities. See comment 22 on the DRESP1 page.

*** ATTi can only be blank when a property type is defined in the PTYPE field (not
allowed for "ELEM"), and means that all entities of the defined property type will
be selected. See comment 21 on the DRESP1 page.

**** ATTB = G# – # is the number of the global ply defined on a PCOMPG. See
comment 13 on the DRESP1 page.

***** ATTB must be Blank for PLY response type. See comment 13 on the DRESP1
page.

****** ATTB = Cluster Size represents the number of elements in a cluster for which
Stress Constraints need to be defined. See comment 32 on the DRESP1 page.

Altair Engineering OptiStruct 13.0 Reference Guide 811

Proprietary Information of Altair Engineering


DRESP1 - Static Stress/Strain Item Codes

Element Stress/Strain Item ASCII Code Number Code *

CELAS Stress/Strain S 2

CROD Both ends SAB -

End A SA 2

End B SB 2

CBAR** All stresses/strains SALL -

End A pt. C SAC 2

End A pt. D SAD 3

End A pt. E SAE 4

End A pt. F SAF 5

End B pt. C SBC 10

End B pt. D SBD 11

End B pt. E SBE 12

End B pt. F SBF 13

Max end A SAMAX 7

Max end B SBMAX 14

812 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CBEAM** All stresses/strains SALL -

End A pt. C SAC 4

End A pt. D SAD 5

End A pt. E SAE 6

End A pt. F SAF 7

End B pt. C SBC 104

End B pt. D SBD 105

End B pt. E SBE 106

End B pt. F SBF 107

Max end A SAMAX 8

Max end B SBMAX 108

CSHEAR Maximum Shear SHMAX 2

Average Shear SHAVG 3

Safety Margin SHMRG 4

All Solid von Mises SVM 13


elements

Max Principal Stress SMP

Major Principal SMAP 8

Mid Principal SMDP 16

Altair Engineering OptiStruct 13.0 Reference Guide 813

Proprietary Information of Altair Engineering


Minor Principal SMIP 22

Normal X SXX 6

Normal Y SYY 14

Normal Z SZZ 20

Shear XY SXY 7

Shear YZ SYZ 15

Shear XZ SXZ 21

Equivalent Plastic Strain PLAS -

All Shell von Mises both surfaces SVMB -


elements

Major Principal both SMPB -


surfaces

von Mises 1 SVM1 9

von Mises 2 SVM2 17

Major Principal 1 SMP1 7

Major Principal 2 SMP2 15

Minor Principal both SMIPB -


surfaces

Minor Principal 1 SMIP1 8

Minor Principal 2 SMIP2 16

Normal X both surfaces SXB -

814 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Normal X 1 SX1 3

Normal X 2 SX2 11

Normal Y both surfaces SYB -

Normal Y 1 SY1 4

Normal Y 2 SY2 12

Shear XY both surfaces SXYB -

Shear XY 1 SXY1 5

Shear XY 2 SXY2 13

Equivalent Plastic Strain PLASB -


both surfaces

Equivalent Plastic Strain 1 PLAS1 -

Equivalent Plastic Strain 2 PLAS2 -

*OptiStruct provides partial support for Nastran item codes. Since Nastran response items
are not fully compatible with those used in OptiStruct, it is recommended that the OptiStruct
ASCII item codes be used.

**For Bar elements that reference PBARL, PBEAML, it is recommended that the special stress
item codes listed under Stress Item Codes for Bar Elements using PBARL, PBEAML Properties be
used. Stress/strain items listed here for CBAR, CBEAM elements using PBAR, PBEAM, PBARL, or
PBEAML properties include only normal stress/strain.

Altair Engineering OptiStruct 13.0 Reference Guide 815

Proprietary Information of Altair Engineering


DRESP1 - Static Stress Item Codes for Bar Elements using
PBARL, PBEAML Properties
The evaluation stresses (normal, shear, and von Mises) for each bar element are listed in the
links provided below. The shear stress includes torsion and shear.

Bar Element Types

BAR element type

C ross-sectional dimensions and stress constraint evaluation points

Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N

S2N

S3N

S4N

S5S S5V

S6S S6V

S7S S7V

816 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


S8S S8V

SNMAX SSMAX SVMAX

BOX element type

C ross-sectional dimensions and stress constraint evaluation points

Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N S1S S1V

S2N S2S S2V

S3N S3S S3V

S4N S4S S4V

S5S S5V

S6S S6V

S7S S7V

Altair Engineering OptiStruct 13.0 Reference Guide 817

Proprietary Information of Altair Engineering


Normal Stress Shear Stress von Mises Stress

S8S S8V

S9S S9V

S10S S10V

S11S S11V

S12S S12V

SNMAX SSMAX SVMAX

Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.

BOX1 element type

C ross-sectional dimensions and stress constraint evaluation points

818 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N S1S S1V

S2N S2S S2V

S3N S3S S3V

S4N S4S S4V

S5S S5V

S6S S6V

S7S S7V

S8S S8V

S9S S9V

S10S S10V

S11S S11V

S12S S12V

SNMAX SSMAX SVMAX

Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.

CHAN element type

Altair Engineering OptiStruct 13.0 Reference Guide 819

Proprietary Information of Altair Engineering


C ross-sectional dimensions and stress constraint evaluation points

Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N

S2N

S3N

S4N

S5S S5V

S6S S6V

S7S S7V

S8S S8V

S9S S9V

SNMAX SSMAX SVMAX

Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number

820 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


refers to stress recovered in the xz plane.

CHAN1 element type

C ross-sectional dimensions and stress constraint evaluation points

Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N

S2N

S3N

S4N

S5S S5V

S6S S6V

S7S S7V

S8S S8V

S9S S9V

SNMAX SSMAX SVMAX

Altair Engineering OptiStruct 13.0 Reference Guide 821

Proprietary Information of Altair Engineering


Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.

CHAN2 element type

C ross-sectional dimensions and stress constraint evaluation points

Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N

S2N

S3N

S4N

S5S S5V

S6S S6V

S7S S7V

S8S S8V

S9S S9V

822 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SNMAX SSMAX SVMAX

Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.

CROSS element type

C ross-sectional dimensions and stress constraint evaluation points

Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N S1V

S2N S2V

S3N S3V

S4N S4V

S5S S5V

S6S S6V

Altair Engineering OptiStruct 13.0 Reference Guide 823

Proprietary Information of Altair Engineering


S7S S7V

S8S S8V

SNMAX SSMAX SVMAX

Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.

H element type

C ross-sectional dimensions and stress constraint evaluation points

Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N

S2N

S3N

S4N

824 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


S5S S5V

S6S S6V

S7S S7V

S8S S8V

S9S S9V

SNMAX SSMAX SVMAX

Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.

HAT element type

C ross-sectional dimensions and stress constraint evaluation points

Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N

S2N

S3N

S4N

Altair Engineering OptiStruct 13.0 Reference Guide 825

Proprietary Information of Altair Engineering


S5S S5V

S6S S6V

S7S S7V

S8S S8V

S9S S9V

S10S S10V

S11S S11V

S12S S12V

S13S S13V

S14S S14V

S15S S15V

SNMAX SSMAX SVMAX

Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.

I element type

826 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


C ross-sectional dimensions and stress constraint evaluation points

Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N

S2N

S3N

S4N

S5S S5V

S6S S6V

S7S S7V

S8S S8V

S9S S9V

SNMAX SSMAX SVMAX

Altair Engineering OptiStruct 13.0 Reference Guide 827

Proprietary Information of Altair Engineering


Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.

I1 element type

C ross-sectional dimensions and stress constraint evaluation points

Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N

S2N

S3N

S4N

S5S S5V

S6S S6V

S7S S7V

S8S S8V

S9S S9V

828 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SNMAX SSMAX SVMAX

Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.

L element type

C ross-sectional dimensions and stress constraint evaluation points

Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N

S2N

S3N

S4N

S5S S5V

S6S S6V

S7S S7V

S8S S8V

Altair Engineering OptiStruct 13.0 Reference Guide 829

Proprietary Information of Altair Engineering


SNMAX SSMAX SVMAX

Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.

ROD element type

C ross-sectional dimensions and stress constraint evaluation points

Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N S1S

S2N S2S

S3N S3S

S4N S4S

S5V

The location of point 5 will be determined by varying the from 0 to 360 degrees to find
the maximum von Mises stress.

830 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


T element type

C ross-sectional dimensions and stress constraint evaluation points

Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N

S2N

S3N

S4N

S5S S5V

S6S S6V

S7S S7V

SNMAX SSMAX SVMAX

Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.

T1 element type

Altair Engineering OptiStruct 13.0 Reference Guide 831

Proprietary Information of Altair Engineering


C ross-sectional dimensions and stress constraint evaluation points

Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N

S2N

S3N

S4N

S5S S5V

S6S S6V

S7S S7V

SNMAX SSMAX SVMAX

Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.

T2 element type

832 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


C ross-sectional dimensions and stress constraint evaluation points

Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N

S2N

S3N

S4N

S5S S5V

S6S S6V

S7S S7V

SNMAX SSMAX SVMAX

Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these
cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.

TUBE element type

Altair Engineering OptiStruct 13.0 Reference Guide 833

Proprietary Information of Altair Engineering


C ross-sectional dimensions and stress constraint evaluation points

Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N S1S

S2N S2S

S3N S3S

S4N S4S

S5V

The location of point 5 will be determined by varying the from 0 to 360 degrees to find
the maximum von Mises stress.

Z element type

834 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


C ross-sectional dimensions and stress constraint evaluation points

Evaluation Stresses

Normal Stress Shear Stress von Mises Stress

S1N

S2N

S3N

S4N

S5S S5V

S6S S6V

S7S S7V

S8S S8V

S9S S9V

SNMAX SSMAX SVMAX

Several stress recovery points are coincident (for example, 1 and 5, 2 and 6). In these

Altair Engineering OptiStruct 13.0 Reference Guide 835

Proprietary Information of Altair Engineering


cases, the lower number refers to stress recovered in the xy plane and the higher number
refers to stress recovered in the xz plane.

836 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DRESP1 - Frequency Response Force Item Codes

Element Response Component ASCII code Number code*

CELAS Force Real R-F 2

Imaginary I-F 3

Magnitude M-F 2

Phase P-F 3

CDAMP Force Real R-FA 2

Imaginary I-FA 3

Magnitude M-FA 2

Phase P-FA 3

CVISC Axial force Real R-FA 2

Imaginary I-FA 3

Magnitude M-FA 2

Phase P-FA 3

Torque Real R-FB 4

Imaginary I-FB 5

Magnitude M-FB 4

Phase P-FB 5

CROD Force at end A Real R-FA 2

Imaginary I-FA 3

Altair Engineering OptiStruct 13.0 Reference Guide 837

Proprietary Information of Altair Engineering


Magnitude M-FA 2

Phase P-FA 3

Force at end B Real R-FB

Imaginary I-FB

Magnitude M-FB

Phase P-FB

CBAR/ Bending at end A Real R-MA1 2


CBEAM plane 1
Imaginary I-MA1 10

Magnitude M-MA1 2

Phase P-MA1 10

Bending at end A Real R-MA2 3


plane 2
Imaginary I-MA2 11

Magnitude M-MA2 3

Phase P-MA2 11

Bending at end B Real R-MB1 4


plane 1
Imaginary I-MB1 12

Magnitude M-MB1 4

Phase P-MB1 12

Bending at end B Real R-MB2 5


plane 2
Imaginary I-MB2 13

Magnitude M-MB2 5

Phase P-MB2 13

838 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Shear at end A Real R-SA1 6
plane 1
Imaginary I-SA1 14

Magnitude M-SA1 6

Phase P-SA1 14

Shear at end A Real R-SA2 7


plane 2
Imaginary I-SA2 15

Magnitude M-SA2 7

Phase P-SA2 15

Axial force at end A Real R-FA 8

Imaginary I-FA 16

Magnitude M-FA 8

Phase P-FA 16

Torque at end A Real R-TA 9

Imaginary I-TA 17

Magnitude M-TA 9

Phase P-TA 17

Shear at end B Real R-SB1


plane 1
Imaginary I-SB1

Magnitude M-SB1

Phase P-SB1

Shear at end B Real R-SB2


plane 2
Imaginary I-SB2

Altair Engineering OptiStruct 13.0 Reference Guide 839

Proprietary Information of Altair Engineering


Magnitude M-SB2

Phase P-SB2

Axial force at end B Real R-FB

Imaginary I-FB

Magnitude M-FB

Phase P-FB

Torque at end B Real R-TB

Imaginary I-TB

Magnitude M-TB

Phase P-TB

CBUSH Force X Real R-FX 2

Imaginary I-FX 8

Magnitude M-FX 2

Phase P-FX 8

Force Y Real R-FY 3

Imaginary I-FY 9

Magnitude M-FY 3

Phase P-FY 9

Force Z Real R-FZ 4

Imaginary I-FZ 10

Magnitude M-FZ 4

Phase P-FZ 10

840 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Moment X Real R-MX 5

Imaginary I-MX 11

Magnitude M-MX 5

Phase P-MX 11

Moment Y Real R-MY 6

Imaginary I-MY 12

Magnitude M-MY 6

Phase P-MY 12

Moment Z Real R-MZ 7

Imaginary I-MZ 13

Magnitude M-MZ 7

Phase P-MZ 13

CSHEAR Force 4 to 1 Real R-F41 2

Imaginary I-F41 10

Magnitude M-F41 2

Phase P-F41 10

Force 2 to 1 Real R-F21 3

Imaginary I-F21 11

Magnitude M-F21 3

Phase R-F21 11

Force 1 to 2 Real R-F12 4

Imaginary I-F12 12

Altair Engineering OptiStruct 13.0 Reference Guide 841

Proprietary Information of Altair Engineering


Magnitude M-F12 4

Phase P-F12 12

Force 3 to 2 Real I-F32 5

Imaginary I-F32 13

Magnitude M-F32 5

Phase P-F32 13

Force 2 to 3 Real R-F23 6

Imaginary I-F23 14

Magnitude M-F23 6

Phase P-F23 14

Force 4 to 3 Real R-F43 7

Imaginary I-F43 15

Magnitude M-F43 7

Phase P-F43 15

Force 3 to 4 Real R-F34 8

Imaginary I-F34 16

Magnitude M-F34 8

Phase P-F34 16

Force 1 to 4 Real R-F14 9

Imaginary I-F14 17

Magnitude M-F14 9

Phase P-F14 17

Kick Force on 1 Real R-KF1 18

842 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Imaginary I-KF1 26

Magnitude M-KF1 18

Phase P-KF1 26

Shear Flow 12 Real R-SH12 19

Imaginary I-SH12 27

Magnitude M-SH12 19

Phase P-SH12 27

Kick Force on 2 Real R-KF2 20

Imaginary I-KF2 28

Magnitude M-KF2 20

Phase P-KF2 28

All Shell Membrane force X Real R-NX 2


Elements
Imaginary I-NX 10

Magnitude M-NX 2

Phase P-NX 10

Membrane force Y Real R-NY 3

Imaginary I-NY 11

Magnitude M-NY 3

Phase P-NY 11

Membrane shear Real R-NXY 4


force XY
Imaginary I-NXY 12

Magnitude M-NXY 4

Altair Engineering OptiStruct 13.0 Reference Guide 843

Proprietary Information of Altair Engineering


Phase P-NXY 12

Bending Moment X Real R-MX 5

Imaginary I-MX 13

Magnitude M-MX 5

Phase P-MX 13

Bending Moment Y Real R-MY 6

Imaginary I-MY 14

Magnitude M-MY 6

Phase P-MY 14

Twisting moment Real R-MXY 7


XY
Imaginary I-MXY 15

Magnitude M-MXY 7

Phase P-MXY 15

Transverse shear Real R-SXZ 8


XZ
Imaginary I-SXZ 16

Magnitude M-SXZ 8

Phase P-SXZ 16

Transverse shear Real R-SYZ 9


YZ
Imaginary I-SYZ 17

Magnitude M-SYZ 9

Phase P-SYZ 17

*OptiStruct provides partial support for Nastran item codes. Since Nastran response items
are not fully compatible with those used in OptiStruct, it is recommended that the OptiStruct
ASCII item codes be used.

844 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DRESP1 - Frequency Response Stress/Strain Item Codes

Element Stress/Strain Component ASCII code Number code*


Item

CELAS Stress/Strain Real R-S 2

Imaginary I-S 3

Magnitude M-S 2

Phase P-S 3

CROD Both ends Real R-SAB

Imaginary I-SAB

Magnitude M-SAB

Phase P-SAB

End A Real R-SA 2

Imaginary I-SA 3

Magnitude M-SA 2

Phase P-SA 3

End B Real R-SB

Imaginary I-SB

Magnitude M-SB

Phase P-SB

CBAR All Stresses/ Real R-SALL


Strains
Imaginary I-SALL

Magnitude M-SALL

Phase P-SALL

Altair Engineering OptiStruct 13.0 Reference Guide 845

Proprietary Information of Altair Engineering


Element Stress/Strain Component ASCII code Number code*
Item

End A point C Real R-SAC 2

Imaginary I-SAC 7

Magnitude M-SAC 2

Phase P-SAC 7

End A point D Real R-SAD 3

Imaginary I-SAD 8

Magnitude M-SAD 3

Phase P-SAD 8

End A point E Real R-SAE 4

Imaginary I-SAE 9

Magnitude M-SAE 4

Phase P-SAE 9

End A point F Real R-SAF 5

Imaginary I-SAF 10

Magnitude M-SAF 5

Phase P-SAF 10

End B point C Real R-SBC 12

Imaginary I-SBC 16

Magnitude M-SBC 12

Phase P-SBC 16

End B point D Real R-SBD 13

846 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Element Stress/Strain Component ASCII code Number code*
Item

Imaginary I-SBD 17

Magnitude M-SBD 13

Phase P-SBD 17

End B point E Real R-SBE 14

Imaginary I-SBE 18

Magnitude M-SBE 14

Phase P-SBE 18

End B point F Real R-SBF 15

Imaginary I-SBF 19

Magnitude M-SBF 15

Phase P-SBF 19

Maximum at end Real R-SAMAX


A
Imaginary I-SAMAX

Magnitude M-SAMAX

Phase P-SAMAX

Maximum at end Real R-SBMAX


B
Imaginary I-SBMAS

Magnitude M-SBMAX

Phase P-SBMAX

CBEAM All Stresses/ Real R-SALL


Strains
Imaginary I-SALL

Altair Engineering OptiStruct 13.0 Reference Guide 847

Proprietary Information of Altair Engineering


Element Stress/Strain Component ASCII code Number code*
Item

Magnitude M-SALL

Phase P-SALL

End A point C Real R-SAC 4

Imaginary I-SAC 8

Magnitude M-SAC 4

Phase P-SAC 8

End A point D Real R-SAD 5

Imaginary I-SAD 9

Magnitude M-SAD 5

Phase P-SAD 9

End A point E Real R-SAE 6

Imaginary I-SAE 10

Magnitude M-SAE 6

Phase P-SAE 10

End A point F Real R-SAF 7

Imaginary I-SAF 11

Magnitude M-SAF 7

Phase P-SAF 11

End B point C Real R-SBC 104

Imaginary I-SBC 108

Magnitude M-SBC 104

848 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Element Stress/Strain Component ASCII code Number code*
Item

Phase P-SBC 108

End B point D Real R-SBD 105

Imaginary I-SBD 109

Magnitude M-SBD 105

Phase P-SBD 109

End B point E Real R-SBE 106

Imaginary I-SBE 110

Magnitude M-SBE 106

Phase P-SBE 110

End B point F Real R-SBF 107

Imaginary I-SBF 111

Magnitude M-SBF 107

Phase P-SBF 111

Maximum at end Real R-SAMAX


A
Imaginary I-SAMAX

Magnitude M-SAMAX

Phase P-SAMAX

Maximum at end Real R-SBMAX


B
Imaginary I-SBMAX

Magnitude M-SBMAX

Phase P-SBMAX

Altair Engineering OptiStruct 13.0 Reference Guide 849

Proprietary Information of Altair Engineering


Element Stress/Strain Component ASCII code Number code*
Item

CSHEAR Maximum Shear Real R-SHMAX 2

Imaginary I-SHMAX 3

Magnitude M-SHMAX 2

Phase P-SHMAX 3

Average Shear Real R-SHAVG 4

Imaginary I-SHAVG 5

Magnitude M-SHAVG 4

Phase P-SHAVG 5

All Solid Normal X Real R-SXX 6


Elements
Imaginary I-SXX 12

Magnitude M-SXX 6

Phase P-SXX 12

Normal Y Real R-SYY 7

Imaginary I-SYY 13

Magnitude M-SYY 7

Phase P-SYY 13

Normal Z Real R-SZZ 8

Imaginary I-SZZ 14

Magnitude M-SZZ 8

Phase P-SZZ 14

850 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Element Stress/Strain Component ASCII code Number code*
Item

Shear XY Real R-SXY 9

Imaginary I-SXY 15

Magnitude M-SXY 9

Phase P-SXY 15

Shear YZ Real R-SYZ 10

Imaginary I-SYZ 16

Magnitude M-SYZ 10

Phase P-SYZ 16

Shear XZ Real R-SXZ 11

Imaginary I-SXZ 17

Magnitude M-SXZ 11

Phase P-SXZ 17

von Mises - SVM -

All Shell Normal X at both Real R-SXB


Elements surfaces
Imaginary I-SXB

Magnitude M-SXB

Phase P-SXB

Normal X at Z1 Real R-SX1 3

Imaginary I-SX1 4

Magnitude M-SX1 3

Phase P-SX1 4

Altair Engineering OptiStruct 13.0 Reference Guide 851

Proprietary Information of Altair Engineering


Element Stress/Strain Component ASCII code Number code*
Item

Normal X at Z2 Real R-SX2 10

Imaginary I-SX2 11

Magnitude M-SX2 10

Phase P-SX2 11

Normal Y at both Real R-SYB


surfaces
Imaginary I-SYB

Magnitude M-SYB

Phase P-SYB

Normal Y at Z1 Real R-SY1 5

Imaginary I-SY1 6

Magnitude M-SY1 5

Phase P-SY1 6

Normal Y at Z2 Real R-SY2 12

Imaginary I-SY2 13

Magnitude M-SY2 12

Phase P-SY2 13

Shear XY at both Real R-SXYB


surfaces
Imaginary I-SXYB

Magnitude M-SXYB

Phase P-SXYB

Shear XY at Z1 Real R-SXY1 7

852 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Element Stress/Strain Component ASCII code Number code*
Item

Imaginary I-SXY1 8

Magnitude M-SXY1 7

Phase P-SXY1 8

Shear XY at Z2 Real R-SXY2 14

Imaginary I-SXY2 15

Magnitude M-SXY2 14

Phase P-SXY2 15

von Mises at Z1 - SVM1 -

von Mises at Z2 - SVM2 -

von Mises - SVMB -

* OptiStruct provides partial support for Nastran item codes. Since Nastran response items
are not fully compatible with those used in OptiStruct, it is recommended that the OptiStruct
ASCII item codes be used.

Altair Engineering OptiStruct 13.0 Reference Guide 853

Proprietary Information of Altair Engineering


DRESP1 - Frequency Response Displacement, Velocity,
and Acceleration Item Codes

Response Component ASCII code Number code*

Translation X Real R-TX 1

Imaginary I-TX 7

Magnitude M-TX 1

Phase P-TX 7

Translation Y Real R-TY 2

Imaginary I-TY 8

Magnitude M-TY 2

Phase P-TY 8

Translation Z Real R-TZ 3

Imaginary I-TZ 9

Magnitude M-TZ 3

Phase P-TZ 9

Rotation X Real R-RX 4

Imaginary I-RX 10

Magnitude M-RX 4

Phase P-RX 10

Rotation Y Real R-RY 5

Imaginary I-RY 11

Magnitude M-RY 5

Phase P-RY 11

854 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Response Component ASCII code Number code*

Rotation Z Real R-RZ 6

Imaginary I-RZ 12

Magnitude M-RZ 6

Phase P-RZ 12

Normal Real R-NORM -

Imaginary I-NORM -

Magnitude M-NORM -

Phase P-NORM -

*OptiStruct provides partial support for Nastran item codes. Since Nastran response items
are not fully compatible with those used in OptiStruct, it is recommended that the OptiStruct
ASCII item codes be used.

Altair Engineering OptiStruct 13.0 Reference Guide 855

Proprietary Information of Altair Engineering


DRESP1 - Frequency Response Pressure Item Codes

Response Component ASCII code Number code*

Pressure Real R-PRES 1

Imaginary I-PRES 7

Magnitude M-PRES 1

Phase P-PRES 7

*OptiStruct provides partial support for Nastran item codes. Since Nastran response items
are not fully compatible with those used in OptiStruct, it is recommended that the OptiStruct
ASCII item codes be used.

856 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DRESP1 - Center of Gravity and Moments of Inertia Item
Codes

Center of Gravity

Component ASCII Code

x-coordinate X

y-coordinate Y

z-coordinate Z

Moments of Inertia

Component ASCII Code

lxx XX

lyy YY

lzz ZZ

lxy XY

lxz XZ

lyz YZ

Altair Engineering OptiStruct 13.0 Reference Guide 857

Proprietary Information of Altair Engineering


DRESP1 - Static Force Item Codes

Element Force Item ASCII Code Number Code *

CELAS Force F 2

CROD Force End A FA 2

Force End B FB -

CBAR Bending End A Plane 1 MA1 2

Bending End A Plane 2 MA2 3

Bending End B Plane 1 MB1 4

Bending End B Plane 2 MB2 5

Shear End A Plane 1 SA1 6

Shear End A Plane 2 SA2 7

Axial Force End A FA 8

Torque End A TA 9

Shear End B Plane 1 SB1 -

Shear End B Plane 2 SB2 -

Axial Force End B FB -

Torque End B TB -

CBEAM Bending End A Plane 1 MA1 4

Bending End A Plane 2 MA2 5

Bending End B Plane 1 MB1 94

Bending End B Plane 2 MB2 95

858 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Element Force Item ASCII Code Number Code *

Shear End A Plane 1 SA1 6

Shear End A Plane 2 SA2 7

Axial Force End A FA 8

Torque End A TA 9

Shear End B Plane 1 SB1 96

Shear End B Plane 2 SB2 97

Axial Force End B FB 98

Torque End B TB 99

CBUSH Force-X FX 2

Force-Y FY 3

Force-Z FZ 4

Moment-X MX 5

Moment-Y MY 6

Moment-Z MZ 7

All Shell Membrane Force X NX 2


Elements
Membrane Force Y NY 3

Membrane Shear Force XY NXY 4

Bending Moment X MX 5

Bending Moment Y MY 6

Altair Engineering OptiStruct 13.0 Reference Guide 859

Proprietary Information of Altair Engineering


Element Force Item ASCII Code Number Code *

Twisting Moment XY MXY 7

Transverse Shear XZ SXZ 8

Transverse Shear YZ SYZ 9

CSHEAR Force 4 to 1 F41 2

Force 2 to 1 F21 3

Force 1 to 2 F12 4

Force 3 to 2 F32 5

Force 2 to 3 F23 6

Force 4 to 3 F43 7

Force 3 to 4 F34 8

Force 1 to 4 F14 9

Kick Force on 1 KF1 10

Shear Flow 12 SH12 11

Kick Force on 2 KF2 12

Shear Flow 23 SH23 13

Kick Force on 3 KF3 14

Shear Flow 34 SH34 15

Kick Force on 4 KF4 16

Shear Flow 41 SH41 17

*OptiStruct provides partial support for Nastran item codes. Since Nastran response items

860 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


are not fully compatible with those used in OptiStruct, it is recommended that the OptiStruct
ASCII item codes be used.

Altair Engineering OptiStruct 13.0 Reference Guide 861

Proprietary Information of Altair Engineering


DRESP1 - Static Failure Item Codes for Composites

Theory ASCII code

Hill HILL

Hoffman HOFF

Tsai-Wu TSAI

Maximum Strain STRN

862 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DRESP1 - Static Stress/Strain Item Codes for Composites

Stress Item ASCII Code Number code*

Normal - 1 S1 3

Normal - 2 S2 4

Shear - 12 S12 5

Shear - 1Z S1Z 6

Shear - 2Z S2Z 7

Maj. Principal SMAP 9

Min. Principal SMIP 10

* OptiStruct provides partial support for Nastran item codes. Since Nastran response
items are not fully compatible with those used in OptiStruct, it is recommended to use
the OptiStruct ASCII item codes.

Strain Item ASCII Code Number Code*

Normal - 1 S1 3

Normal - 2 S2 4

Shear - 12 S12 5

Maj. Principal SMAP 9

Min. Principal SMIP 10

* OptiStruct provides partial support for Nastran item codes. Since Nastran response
items are not fully compatible with those used in OptiStruct, it is recommended to use
the OptiStruct ASCII item codes.

Altair Engineering OptiStruct 13.0 Reference Guide 863

Proprietary Information of Altair Engineering


Thermal Strain Item ASCII Code Number Code*

Normal - 1 TS1 -

Normal - 2 TS2 -

Shear - 12 TS12 -

Maj. Principal TSMAP -

Min. Principal TSMIP -

* OptiStruct provides partial support for Nastran item codes. Since Nastran response
items are not fully compatible with those used in OptiStruct, it is recommended to use
the OptiStruct ASCII item codes.

Mechanical Strain Item ASCII Code Number Code*

Normal - 1 MS1 -

Normal - 2 MS2 -

Shear - 12 MS12 -

Maj. Principal MSMAP -

Min. Principal MSMIP -

* OptiStruct provides partial support for Nastran item codes. Since Nastran response
items are not fully compatible with those used in OptiStruct, it is recommended to use
the OptiStruct ASCII item codes.

864 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DRESP1 - MBD Displacement Item Codes

Displacement ASCII code

Translational X TX

Translational Y TY

Translational Z TZ

Rotational X RX

Rotational Y RY

Rotational Z RZ

Translational TXYZ
resultant

Altair Engineering OptiStruct 13.0 Reference Guide 865

Proprietary Information of Altair Engineering


DRESP1 - MBD Velocity/Acceleration Item Codes

Vel/Acc ASCII code

Translational X TX

Translational Y TY

Translational Z TZ

Rotational X RX

Rotational Y RY

Rotational Z RZ

Translational TXYZ
resultant

Rotational RXYZ
resultant

866 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DRESP1 - MBD Force Item Codes

Force ASCII code

Translational X FX

Translational Y FY

Translational Z FZ

Rotational X MX

Rotational Y MY

Rotational Z MZ

Translational FXYZ
resultant

Rotational MXYZ
resultant

Altair Engineering OptiStruct 13.0 Reference Guide 867

Proprietary Information of Altair Engineering


DRESP1 – PSD/RMS Displacement, Velocity, and
Acceleration Item Codes

Response ASCII code Number code*

Translation X TX 1

Translation Y TY 2

Translation Z TZ 3

Rotation X RX 4

Rotation Y RY 5

Rotation Z RZ 6

*OptiStruct provides partial support for Nastran item codes. Since Nastran response items
are not fully compatible with those used in OptiStruct, it is recommended that the OptiStruct
ASCII item codes be used.

868 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DRESP1 – PSD/RMS Pressure Item Codes

Response ASCII code

Pressure PRES

Altair Engineering OptiStruct 13.0 Reference Guide 869

Proprietary Information of Altair Engineering


DRESP1 - PSD/RMS Stress/Strain Item Codes

All Solid elements Stress/Strain Item ASCII code

Normal X SXX

Normal Y SYY

Normal Z SZZ

Shear XY SXY

Shear YZ SYZ

Shear XZ SXZ

All Shell elements Stress/Strain Item ASCII code

Normal X both surfaces SXB

Normal X 1 SX1

Normal X 2 SX2

Normal Y both surfaces SYB

Normal Y 1 SY1

Normal Y 2 SY2

Shear XY both surfaces SXYB

Shear XY 1 SXY1

Shear XY 2 SXY2

870 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DRESP2

Bulk Data Entry

DRESP2 – Design Response via Equations for Design Optimization

Description

When a desired response is not directly available from OptiStruct, it may be calculated using
DRESP2. This response can be a functional combination of any set of responses resulting from
the design analysis iteration. Responses defined in this manner can be used as design
objectives or constraints. The DRESP2 card identifies the equation to use for the response
relationship and the input values to evaluate the response function.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DRESP2 ID LABEL EQID REGION


or
FUNC

DRESPM RID1 MODEL RID2 MODEL ... ...


NAME1 NAME2

VARTYPE1 ID1 ID2 ID3 ID4 ID5 ID6 ID7

ID8 ... ...

VARTYPE2 ID1 ID2 ID3 ID4 ID5 ID6 ID7

ID8 ... ...

... ... ... ... ... ... ... ...

Example 1

Define a response labeled FUNC1 that references equation #999, where DESVAR #11 is the
first variable, the DTABLE entry PI is the second variable, DRESP1 #1 is the third variable,
the Y location of grid #11 is the forth variable and the DVPREL1 #22 is the fifth variable.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

Altair Engineering OptiStruct 13.0 Reference Guide 871

Proprietary Information of Altair Engineering


DRESP2 10 FUNC 1 999

DESVAR 11

DTABLE PI

DRESP1 1

DGRID 11 2

DVPREL1 22

Example 2

Define a response that is the weighted average of 2 displacements

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DRESP2 3 AVDIS 7 2

DRESP1 9 2

Associated Cards

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DRESP1 9 TOPN DISP 1 3 4668

DRESP1 2 BOTN DISP 1 3 5432

DEQATN 7 y(x1, x2) = (x1*1.5+ x2*4.0)/2

Field Contents

ID Response identification number. Each DRESP2 card must have a unique

872 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

ID with respect to all other DRESP# cards.

No default (Integer > 0)

LABEL User defined name for the response.

No default (Character)

EQID DEQATN identifier that defines the response relationship.

No default (Integer > 0)

FUNC Function to be applied to the arguments (see comment 14).

No default (Character)

REGION Region identifier (see comment 4).

Default = blank (Integer > 0 or blank)

DRESPM Indicates the beginning of a continuation line, which defines model-


specific response ID and Model Name pairs to be used in a Multi-Model
Optimization run.

RID# Identification numbers of model-specific responses (see comment 15).

MODEL User-defined model names defined on the ASSIGN, MMO entry (see
NAME# comment 15).

VARTYPE# Indicates the type of variables to follow. Can be one of: DESVAR,
DTABLE, DGRID, DGRIDB, DRESP1, DRESP1L, DRESP2, DRESP2L, DVPREL1,
DVPREL2, DVCREL1, DVCREL2, DVMREL1, DVMREL2, DVMBRL1, or
DVMBRL2 (see comments 5, 13 and 16).

No default (Character)

ID# When VARTYPE is DESVAR, DTABLE, DRESP1, DRESP2, DVPREL1,


DVPREL2, DVCREL1, DVCREL2, DVMREL1, DVMREL2, DVMBRL1, or
DVMBRL2 this list of IDs reference entities of the defined VARTYPE.

When VARTYPE is DGRID or DGRIDB, the list is a list of GRID/ID


Component pairs, where every second value is a component (1, 2, or 3).
For example, DGRID, 11, 2 indicates the Y component of grid 11 (see

Altair Engineering OptiStruct 13.0 Reference Guide 873

Proprietary Information of Altair Engineering


Field Contents

comment 13).

When VARTYPE is DRESP1L or DRESP2L, the list is a list of response/


subcase pairs, where every second value is a subcase ID, for example,
DRESP1L, 9, 1, 9, 3 indicates response 9 calculated for subcase 1 and
response 9 calculated for subcase 3.

No default (Integer > 0)

Comments

1. DRESP2 entries are referenced from the subcase through one of DESOBJ, DESSUB, or
DESGBL.

2. DRESP2 entries must have unique identification numbers with respect to DRESP1 and
DRESP3 entries.

3. DRESP1L, DRESP2L define a response defined with a DRESP1 or DRESP2, respectively, and
a SUBCASE. The SUBCASE number 0 should be used for global responses.

4. Responses with the same region identifier are grouped together into the same region. If
the region identifier is blank, then a separate region is formed for each DRESP2 definition.
The RTYPE EQUA on the DSCREEN definition refers to DRESP2 responses. It is important
to ensure that responses with the same region identifier reference similar equations. For
further information, refer to Constraint Screening in the User's Guide.

5. Any number of VARTYPE# continuation lines can be defined. The order in which the
VARTYPE# continuation lines are listed on the DRESP2 card is not prescribed. The same
VARTYPE# can be repeated any number of times, in any position, on the card. However,
the order in which the VARTYPE# continuation lines are listed will affect the solution as
the values are passed to the equation (or function) in the listed sequence.

6. The entries on the DRESP2 cards are assigned to the variable on the DEQATN card in the
order that they occur. For example 2 above x1 is the displacement response defined by
the DRESP1 card with ID=9 and x2 is the displacement response defined by the DRESP1
card with ID=2.

7. DRESPi and DRESPiL cards cannot be mixed on the same DRESP2 definition.

8. If DRESP1L, DRESP2L are used for a constrained DRESP2, DESGLB must be used to identify
the DRESP2.

9. If DRESP1L, DRESP2L are used in a DRESP2 objective function, then the DESOBJ that
references the DRESP2 must be defined before the first Subcase.

10. If the DRESP2 data is referenced by DESOBJ data, the DESOBJ data must be above the
first SUBCASE if:

The DRESP2 contains DRESP1L, DRESP2L data.


The DRESP2 contains no DRESP1DRESP2, DRESP1L, or DRESP2L data.

874 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


The DRESP2 contains DRESP1, DRESP2 global responses.

The DESOBJ data must be in the correct SUBCASE if the DRESP2 contains subcase
dependent DRESP1 responses.

11. LABEL must begin with an alphabetical character.

12. DRESP2 cannot reference itself directly or recursively, but multiple levels of referencing
are allowed.

13. The DGRID and DGRIDB VARTYPE’s can be used to select grid point locations as variables
to be passed to the specified equation or function. The grid point locations are specified
as a list of Grid point ID/Component pairs where every second value is a component. The
Grid point ID’s are unique grid point identification numbers (ID) and Components are the
grid point locations X1, X2, and X3 fields on the GRID bulk data entry.

Examples:

DGRIDB:

The VARTYPE DGRIDB can be used to select grid point locations in the basic coordinate
system. The basic coordinate system is the default rectangular coordinate system in
OptiStruct.

DGRID:

The VARTYPE DGRID can be used to select the grid point locations in the local coordinate
system of each grid point. This local coordinate system may be specified by the CP field
of the GRID bulk data entry for a particular grid point of interest. All local (or user defined)
coordinate systems are directly or indirectly based on the default basic coordinate
system.

14. The following functions can be used instead of an EQID. If FUNC is used, the DEQATN
entry is no longer needed. The functions are applied to all arguments on the DRESP2
regardless of their type.

Function Description Formula

SUM Sum of arguments

AVG Average of arguments

Altair Engineering OptiStruct 13.0 Reference Guide 875

Proprietary Information of Altair Engineering


Function Description Formula

SSQ Sum of square of arguments

Square root of sum of squares of


RSS
arguments

MAX Maximum of arguments

MIN Minimum of arguments

SUMABS Sum of absolute value of arguments

Average of absolute value of


AVGABS
arguments

MAXABS Maximum of absolute arguments

Minimum of absolute value of


MINABS
arguments

15. Multiple RID-Model Name pairs can be specified on a single DRESPM continuation line.
These responses can be used similar to responses defined via the VARTYPE# -ID# entries.
ASSIGN, MMO can be used to identify the filename of the model and the user-defined
Model Name that contains the referenced response definition.

16. An inconsistent number of responses can be referenced via multiple DRESP#L VARTYPE’s.
The following requirements should be met for such entries:

1. A minimum of one DRESP# entry listed on a corresponding DRESP#L VARTYPE should


reference only a single response value, (and)

2. DRESP# entries listed on other DRESP#L VARTYPE’s should reference the same number
of responses.

3. If requirement (1) above is not met, then the number of responses referenced by all
the DRESP# entries (listed on all the DRESP#L VARTYPE’s) should be equal.

Example

Allowed

DRESP1 1 R1 STRESS ELEM SVM3 1


2
DRESP1 2 R2 STRESS PSHELL SVM4 1

876 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DRESP2 3 MA 1
+ DRESP1L 4 0
+ DRESP1L 2 2
DRESP1 4 vol VOLUME
DEQATN 1 f(a,b)=a+b

Not Allowed
DRESP1 1 R1 STRESS ELEM SVM1 1
2
DRESP1 2 R2 STRESS PSHELL SVM2 1
DRESP2 3 MNA 1
+ DRESP1L 4 0
+ DRESP1L 1 2
+ DRESP1L 2 2
DRESP1 4 vol VOLUME
DEQATN 1 f(a,b,c)=a+b+c

In the above example (Allowed), the number of responses referenced by DRESP1L=4 is


one. Also, DRESP1L=2 references multiple responses, this is allowed as there are no other
DRESP#L that reference more than one response. However, in the “Not Allowed” example,
DRESP1L=1 references two responses and DRESP1L=2 references multiple responses (this
violates requirement 2 above).

17. This card is represented as optimization responses in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 877

Proprietary Information of Altair Engineering


DRESP3

Bulk Data Entry

DRESP3 – Design Response via External User-supplied Functions

Description

When a desired response is not available from OptiStruct, either directly or via equations, it
may be calculated through external user-supplied functions implemented in shared/dynamic
libraries or external files (see External Reponses). The DRESP3 card identifies the external
function to be called and defines the parameters to be transferred to that function.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DRESP3 ID LABEL GROUP FUNC REGION RESP MAXRESP

DRESPM RID1 MODEL RID2 MODEL ... ...


NAME1 NAME2

VARTYPE1 ID1 ID2 ID3 ID4 ID5 ID6 ID7

ID8 ... ...

VARTYPE2 ID1 ID2 ID3 ID4 ID5 ID6 ID7

ID8 ... ...

...

VARTYPEn ID1 ID2 ID3 ID4 ID5 ID6 ID7

ID8

C ELLIN C I1 C I2 C I3 ... C In

C ELLOUT CO

SENSOPT METHOD

878 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Alternate format for CELLIN (cell input) specifications

C ELLIN C I1 thru C In

Alternate format when VARTYPE is DEIGV

DEIGV EIGV1 LID1 G1 C1

EIGV2 LID2 G2 C2

... ... ... ...

Alternate format when VARTYPE is USRDATA

USRDATA STRNG

...

Field Contents

ID Response identification number. Each DRESP3 must have a unique ID with


respect to all other DRESP# cards.

No default (Integer > 0)

LABEL User-defined name for the response.

No default (Character)

GROUP GROUP identifier that defines the shared/dynamic library or external


Microsoft Excel workbook to be used (see comment 19). It references an
existing LOADLIB entry in the input deck.

No default (Character)

FUNC FUNC identifier that defines the external function to be used.

No default (Character)

Altair Engineering OptiStruct 13.0 Reference Guide 879

Proprietary Information of Altair Engineering


Field Contents

REGION Region identifier (see comment 4).

Default = blank (Integer > 0 or blank)

DRESPM Indicates the beginning of a continuation line, which defines model-


specific response ID and Model Name pairs to be used in a Multi-Model
Optimization run.

RID# Identification numbers of model-specific responses (see comment 21)

MODEL User-defined model names defined on the ASSIGN, MMO entry (see
NAME# comment 21).

RESP RESP identifier that defines the response to be returned by the external
function.

No default (Integer > 0)

MAXRESP MAXRESP identifier that defines the number of responses available in the
external function.

No default (Integer > 0)

VARTYPE# Indicates the type of variables to follow. Can be one of: DESVAR,
DTABLE, DGRID, DGRIDB, DEIGV, DRESP1, DRESP1L, DRESP2, DRESP2L,
DVPREL1, DVPREL2, DVCREL1, DVCREL2, DVMREL1, DVMREL2, DVMBRL1,
DVMBRL2, USRDATA or SLAVE (see comment 18).

No default (Character)

ID# When VARTYPE is DESVAR, DTABLE, DRESP1, DRESP2, DVPREL1, DVPREL2,


DVCREL1, DVCREL2, DVMREL1, DVMREL2, DVMBRL1, or DVMBRL2 this list of
IDs reference entities of the defined VARTYPE.

When VARTYPE is DGRID or DGRIDB, the list is a list of GRID/Component


pairs, where every second value is a component (1, 2, or 3). For example,
DGRID, 11, 2 indicates the Y component of grid 11.

When VARTYPE is DEIGV, the ID# list is replaced by a list of eigenvectors,


with each line defining an eigenvector ID, a subcase ID, and a grid/
component pair (where the component is one of 1, 2, 3, 4, 5 or 6).

When VARTYPE is DRESP1L or DRESP2L, the list is a list of response/


subcase pairs, where every second value is a subcase ID, for example,

880 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

DRESP1L, 9, 1, 9, 3 indicates response 9 calculated for subcase 1 and


response 9 calculated for subcase 3.

When VARTYPE is USRDATA, the list is replaced by a user-defined


character string, which is passed to the external function. This character
string must be less than 32000 characters.

When VARTYPE is SLAVE, only a single ID should follow. This is the ID of


another DRESP3 entry from which data should be copied.

No default (Integer > 0, or Character)

CELLIN CELLIN flag indicates that a list of Microsoft Excel worksheet cell
references are to follow, that define response input values (see comments
19 and 20).

CI# A list of Microsoft Excel worksheet cell references that define response
input values (see comments 19 and 20).

No default (Alphanumeric)

CELLOUT CELLIN flag indicates that a Microsoft Excel Worksheet cell reference is to
follow that defines the response output value (see comments 19 and 20).

CO A Microsoft Excel worksheet cell reference that defines the response


output value (see comments 19 and 20).

No default (Alphanumeric)

SENSOPT Indicates that the sensitivities evaluation method follows.

METHOD Method to be used for sensitivities evaluation (see comment 17).

NONE (or blank): Sensitivities are not provided. Full evaluations are
performed at every step of the approximation process.

AUTO: Sensitivities are automatically evaluated by finite differences at


the beginning of the iteration, and subsequently used in the approximation
process.

USER: Sensitivities are provided by the external function at the beginning


of the iteration, and subsequently used in the approximation process.

Default = NONE (or blank)

EIGVi Eigenvector numbers.

Altair Engineering OptiStruct 13.0 Reference Guide 881

Proprietary Information of Altair Engineering


Field Contents

No default (Integer > 0)

LIDi Subcase IDs.

No default (Integer > 0)

Gi Grid IDs.

No default (Integer > 0)

Ci Component IDs.

No default (1, 2, 3, 4, 5, or 6)

STRNG User-defined string to be passed to the external function.

No default (Character string < 32000 characters)

Comments

1. DRESP3 entries are referenced from the subcases through one of DESOBJ, DESSUB, or
DESGBL.

2. DRESP3 entries must have unique identification numbers with respect to DRESP2 and
DRESP1 entries.

3. DRESP1L, DRESP2L define a response defined with a DRESP1 or DRESP2, respectively, and
a SUBCASE. The SUBCASE number 0 should be used for global responses.

4. Responses with the same region identifier are grouped together into the same region. If
the region identifier is blank, then a separate region is formed for each DRESP3 definition.
The RTYPE EXTERNAL on the DSCREEN definition refers to DRESP3 responses. It is
important to ensure that responses with the same region identifier reference similar
external responses. For further information, refer to Constraint Screening in the User's
Guide.

5. Any number of VARTYPE# continuation lines can be defined. The order in which the
VARTYPE# continuation lines are listed on the DRESP2 card is not prescribed. The same
VARTYPE# can be repeated any number of times, in any position, on the card.

6. The entries on the DRESP3 card are assigned to the parameters passed to the external
function in the order that they occur.

7. DRESPi and DRESPiL cards cannot be mixed on one DRESP3 definition.

8. If DRESP1L, DRESP2L is used for a constrained DRESP3, DESGLB must be used to identify
the DRESP3.

882 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


9. If DRESP1L, DRESP2L is used in a DRESP3 objective function, then the DESOBJ that
references the DRESP3 must be defined before the first subcase.

10. If the DRESP3 data is referenced by DESOBJ data, the DESOBJ data must be above the
first SUBCASE if:

DRESP3 contains DRESP1L, DRESP2L data.


DRESP3 contains no DRESP1, DRESP2 or DRESP1L, DRESP2L data.
DRESP3 contains DRESP1, DRESP2 global responses.

The DESOBJ data must be in the correct static or eigenvalue SUBCASE if the DRESP3
contains static or eigenvalue DRESP1 responses.

11. DRESP1 of RTYPE = WCOMB, WFREQ, and COMP cannot be referenced by DRESP3 data.

12. LABEL must begin with an alphabetical character.

13. The RESP field may be used to request a specific response from the external function,
while MAXRESP defines the maximum number of responses available in that function.
External functions can be implemented to compute any number of responses and to return
any subset of these responses. This approach has two main benefits:

There is no need to write a specific external function for each response that you want
computed. One general function may be written instead. In many cases, this allows
for easier code maintenance and better code reusability.
OptiStruct will automatically group responses which point to the same external
function, and which use the same set of input data. The external function will only be
called once for that group of responses, which may save computational time in the
library.
14. The SLAVE continuation line indicates that the input data (DESVAR, and so on) for the
current DRESP3 card is identical to the input data of the master DRESP3 card. There
cannot be any other continuation line when SLAVE is used.

This simplifies the DRESP3 definition and reduces potential errors when modifying input
decks, either via the HyperMesh interface or manually. Also, as explained above,
OptiStruct will group responses that share the same input data.

15. The data in the STRNG field is character string based. It provides a convenient way to
pass constants to the external response server routines. The maximum number of
characters allowed in 32000.

16. The eigenvector values provided on the DEIGV continuation are normalized against the
mass matrix. No sensitivities are calculated for these values.

17. Performance of the sensitivity evaluation method is problem dependent, and selection of a
method depends on the number of arguments and the cost of each evaluation. The
default method works best for most problems. However, if the approximation module is
observed to be very slow with the default, AUTO or USER can be tried.

USER: This setup is more complex as it requires user-calculated gradients. However,


since finite differences are not used, it can improve the quality of those gradients and
may also increase the speed at which those gradients are calculated.

18. The DGRID and DGRIDB VARTYPE’s can be used to select grid point locations as variables

Altair Engineering OptiStruct 13.0 Reference Guide 883

Proprietary Information of Altair Engineering


to be passed to the specified equation or function. The grid point locations are specified
as a list of Grid point ID/Component pairs where every second value is a component. The
Grid point ID’s are unique grid point identification numbers (ID) and Components are the
grid point locations X1, X2, and X3 fields on the GRID Bulk Data Entries.

Examples:

DGRIDB:

The VARTYPE DGRIDB can be used to select grid point locations in the basic coordinate
system. The basic coordinate system is the default rectangular coordinate system in
OptiStruct.

DGRID:

The VARTYPE DGRID can be used to select the grid point locations in the local coordinate
system of each grid point. This local coordinate system may be specified by the CP field
of the GRID Bulk Data Entry for a particular grid point of interest. All local (or user
defined) coordinate systems are directly or indirectly based on the default basic
coordinate system.

19. An external Microsoft Excel workbook can be referenced on the GROUP field via the
LOADLIB I/O Options Entry.

20. Multiple CELLIN continuation lines can be specified; each CI# entry on the CELLIN
continuation lines corresponds to responses (ID#) defined on the VARTYPE# continuation
lines. See External Responses in the User’s Guide for further information.

21. Multiple RID-Model Name pairs can be specified on a single DRESPM continuation line.
These responses can be used similar to responses defined via the VARTYPE# -ID# entries.
ASSIGN, MMO can be used to identify the filename of the model and the user-defined
Model Name that contains the referenced response definition.

884 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DSCREEN

Bulk Data Entry

DSCREEN – Design Constraint Screening

Description

Defines design constraint screening data. Refer to Constraint Screening in the User's Guide
section.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DSC REEN RTYPE THOLD MAXC

Alternate Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DSC REEN AUTO LEVEL

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DSC REEN STRESS -0.6 4

Associated Cards

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DRESP1 98 SS11 STRESS PSHELL 1 7 1

DRESP1 99 SS11 STRESS PSHELL 2 7 3

DRESP1 100 SS11 STRESS PSHELL 2 7 5

Altair Engineering OptiStruct 13.0 Reference Guide 885

Proprietary Information of Altair Engineering


Field Contents

RTYPE Response type affected by the constraint screening settings on this


definition.

No default (Character; See comment 1)

THOLD Normalized threshold value – constraint will not be retained during the
current iteration if its normalized value is below THOLD.

Default = -0.5 (Real < 0.0)

MAXC Maximum number of constraints to be retained for each region definition and
each load case.

Default = 20 (Integer > 0)

AUTO Automatic adjustment of screening criteria.

When this is activated, the screening algorithm will seek to retain the least
number of responses that are necessary for stable convergence.

Automatic constraint screening is active by default. It is disabled by the


presence of any DSCREEN definition in the input data.

LEVEL The automatic constraint screening has levels 1 through 5, with 1 being the
least aggressive (more responses retained) and 5 being the most aggressive
(less responses retained). Level 3 is the default.

The automatic constraint screening can also be disabled by setting it to


OFF.

Default = 3 (1, 2, 3, 4, 5 or OFF)

Comments

1. RTYPE may be any of the RTYPEs allowed on the DRESP1 entry, or EQUA or EXTERNAL or
AUTO.

2. RTYPE EQUA refers to DRESP2 definitions. If DRESP2 definitions are given the same region
identifier, they should reference similar equations.

3. RTYPE EXTERNAL refers to DRESP3 definitions. If DRESP3 definitions are given the same
region identifier, they should reference similar equations.

4. F is the normalized constraint. If F> THOLD, then the constraint will be retained. F is
calculated with respect to the upper and lower bounds of the constraint as follows:

886 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


5. The THOLD and MAXC defaults do not apply for MASS, MASSFRAC, VOLUME,
VOLUMEFRAC, or FREQ. Constraint screening is not active for these responses by default.

6. When no DSCREEN definitions are present in the input data, automatic constraint
screening is active for all responses. The presence of any DSCREEN definition disables
the automatic screening for all response types.

7. With automatic screening, the upper bound on the EIGRL card for buckling analysis will be
adjusted in order to calculate only the necessary buckling eigenvalues (responses) that
are potentially retained in the optimization.

8. This card is represented as an optidscreens in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 887

Proprietary Information of Altair Engineering


DSHAPE

Bulk Data Entry

DSHAPE – Design Variable for Free-Shape Optimization

Description

Defines parameters for the generation of free-shape design variables.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DSHAPE ID

PERT DTYPE MVFAC TO NSMOOT MXSHRK MXGROW SMETHO NTRANS


R H D

GRID GMETH GSETID / GID2 GID3 GID4 GID5 GID6


GID1

GID7 GID8 … …

PATRN PATYP AID/XA YA ZA FID/VXF VYF VZF

DRAW DTYP DAID/ YDA ZDA DFID/ YDF ZDF


XDA XDF

DRAFT

EXTR EC ID XE YE ZE

GRIDC O GC METH GC SETID C TYPE1 C ID1 X1 Y1 Z1


N 1/
GDID1

GC METH GC SETID C TYPE2 C ID2 X2 Y2 Z2


2/
GDID2

… …

SDC ON SDC ID1 XL1 XU1 YL1 YU1 ZL1 ZU1

SDC ID2 XL2 XU2 YL2 YU2 ZL2 ZU2

… …

BMESH BMID

888 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

ID Each DSHAPE card must have a unique ID.

No default (Integer > 0)

PERT PERT flag indicating perturbation information is to follow.

DTYPE Specifies the direction type for the free-shape variation (Comment 1).

Default = BOTH (GROW, SHRINK, or BOTH)

MVFACTOR Initial limit on the movement factor of the design grids. The unit of
MVFACTOR is the average mesh size of meshes adjacent to grids defined
after GRID.

Only the initial value of this limit can be set. The values in subsequent
optimization iterations are automatically adjusted to enhance to enhance
iterative stability and convergence speed; however, they will never be
greater than the initial limit.

Default = 0.5 (Real > 0.0)

NSMOOTH Number of grids layers NSMOOTH.

Default = 10 (Integer)

MXSHRK Maximum shrinking distance.

No default

MXGROW Maximum growing distance.

No default

SMETHOD Mesh smoothing method.

Default = 1 (1 or 2)

Method 1 is faster than method 2, but method 2 is more robust in avoiding


mesh distortion.

NTRANS Number of design grid layers in the transition zone to non-design area,
where additional treatment will be applied to produce smooth transition
(Comment 4).

Default = 0 (Integer > 0)

GRID GRID flag indicating that a list of grid IDs is to follow. These grids are
design variables for the free-shape optimization.

Altair Engineering OptiStruct 13.0 Reference Guide 889

Proprietary Information of Altair Engineering


Field Contents

GMETH Flag indicating that a list of grids is to be defined by a list of grid IDs or a
single SET reference.

Default = ID (SET or ID)

GID# Grid identification numbers. List of grids for which this DSHAPE card is
defined.

No default (Integer > 0)

GSETID Grid SET identification number. A grid set containing design grids for free-
shape optimization.

No default (Integer > 0)

PATRN PATRN flag indicating that variable pattern grouping is active. Indicates
that information about the pattern group will follow.

PATYP Type of variable pattern grouping. Required if any symmetry or variable


pattern grouping is desired. Only 1-plane symmetry (TYP=10) is currently
supported.

Default = 0 (0 or 10)

AID/XA, YA, ZA Variable pattern grouping anchor point. These fields define a point that
determines how grids are grouped into variables (See comment 3). The X,
Y, and Z values are in the global coordinate system. You may put a grid
ID in the AID/XA field to define the anchor point.

Default = origin (Real in all three fields or Integer in AID/XA field)

FID/VXF, VYF, Direction of first vector for variable pattern grouping. These fields define
VZF an xyz vector which determines how grids are grouped into variables
(Comment 3). The X, Y, and Z values are in the global coordinate system.

If FID is defined, it defines a vector pointing from grid AID or point (XA,
YA, and ZA) to grid FID.

If VXF, VYF, VZF are defined, it defines a vector pointing from point (XA,
YA, and ZA) to point (XA+VXF,YA+VYF,ZA+VZF). (XA, YA, and ZA) are
coordinates of the anchor point defined by AID or XA, YA, and ZA.

If all fields are blank and the PATYP field is not blank or zero, OptiStruct
gives an error.

No default

DRAW DRAW flag indicating that casting constraints are being applied. Indicates
that draw direction information is to follow. Only valid for design grids on
solid elements.

890 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

DTYP Type of draw direction constraint to be used. SINGLE indicates that a


single die will be used, the die being withdrawn in the given draw
direction. Only SINGLE is available in 9.0.

DAID/XDA, YDA, Draw direction anchor point. These fields define the anchor point for draw
ZDA direction of the casting. The point may be defined by entering a grid ID in
the DAID field or by entering X, Y, and Z coordinates in the XDA, YDA, and
ZDA fields, these coordinates will be in the basic coordinate system.

Default = origin (Real in all three fields or Integer in first field)

DFID/XDF, YDF, Direction of vector for draw direction definition. These fields define a
ZDF point. The vector goes from the anchor point to this point. The point
may be defined by entering a grid ID in the DFID field or by entering X, Y,
and Z coordinates in the XDF, YDF, and ZDF fields, these coordinates will
be in the basic coordinate system.

No default (Real in all three fields or Integer in first field)

DRAFT Draft angle in degrees. See comment 5.

Default = 0.0 (0.0 < Real < 90.0)

SDCON# SDCON# flag indicating that side constraints are being applied.

SDCID# The ID of a coordinate system which the following XL#, XU#, YL#, YU#,
ZL#, or ZU# components are resolved in.

XL#, XU#, YL#, Side constraints defined by lower and upper bounds of coordinates, which
YU#, ZL#, ZU# restrict the moving space of the design grids. Any of the six fields could
be blank, which means the corresponding coordinate is not constrained.

EXTR EXTR flag indicating that extrusion constraints are being applied.
Indicates that extrusion information is to follow. Only valid for design
grids on solid elements.

ECID The ID of a coordinate system which the following X, Y, and Z


components are resolved in.

Default = 0 (Integer > 0)

For Free-Shape 9.0, only consider two simple extrusion paths: Line and
Circle.

Line - ECID is a rectangular system.

Circle - ECID is a cylindrical system.

XE, YE, ZE When ECID is a rectangular system ID, X, Y, and Z are components of a
vector under system EID, which define the extrusion path.

Altair Engineering OptiStruct 13.0 Reference Guide 891

Proprietary Information of Altair Engineering


Field Contents

GRIDCON GRIDCON flag indicating that a list of grids with associated constraints are
to follow.

Note: Grids within the smoothing zone (defined by NSMOOTH) will move
during Free-shape optimization to avoid mesh distortion without
changing the shape of the model. Users can also constrain the
movement of these grids by GRIDCON even if they are not defined
after GRID.

GCMETH Flag indicating that a list of grids is to be defined by a list of grid IDs or a
single SET reference.

Default = ID (SET or ID)

GCSETID# Grid SET identification numbers. IDs of certain grid SETs which are
constrained to move in a predefined manner.

No default (Integer > 0)

GDID# IDs of certain grids which are constrained to move in a predefined manner.

No default (Integer > 0, ID must also be present in the list following the
GRID flag)

CTYPE# Specifies the type of constraint applied to the grid GDID# (Comment 2).

No default (FIXED, DIR, or NORM)

CID# The ID of a coordinate system which the following X, Y, and Z


components are resolved in.

Default = 0 (Integer > 0)

X#, Y#, Z# X, Y, and Z components of a vector, which either defines the direction in
which the grid GDID# is constrained to move, or the normal of a plane on
which the grid GDID# is constrained to remain.

Default = 0.0 (Real)

BMESH BMESH flag indicating that a BMFACE ID is to follow.

BMID The BMFACE ID which defines a list of QUADs and/or TRIAs which define a
barrier that the design surface will not penetrate during shape
optimization.

Comments

1. DTYPE has three distinct options:

a) GROW – grids cannot move inside of the initial part boundary.

892 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


b) SHRINK – grids cannot move outside of the initial part boundary.

c) BOTH – grids are unconstrained.

For a more detailed description, refer to Free-shape Optimization in the User’s Guide.

2. CTYPE has three distinct options:

a) FIXED – grid cannot move due to free-shape optimization.

b) DIR – grid is forced to move along the vector defined by the following fields.

c) NORM – grid is forced to remain on a plane for which the following fields define the
normal direction.

For a more detailed description, refer to Free-shape Optimization in the User’s Guide.

3. For a single plane of symmetry (TYP = 10), the plane is defined normal to the first vector
and is located at the anchor node.

4. The NTRANS option allows you to achieve a smooth transition between design and non-
design regions. This additional smoothness, however, comes with an inherent cost of a
reduction in design flexibility. NTRANS improves design smoothness across the transition
zone between design and non-design regions at the expense of design flexibility.

For detailed information illustrating the working mechanism of NTRANS, refer to Defining
Free-shape Design Regions in the User’s Guide.

5. The draft angle can be specified in degrees via the DRAFT field, as illustrated in the figure
below. Geometric constraints (GRIDCON and SDCON) may not be satisfied when the draft
angle is activated:

6. This card is represented as an optimization design variable in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 893

Proprietary Information of Altair Engineering


DSHUFFLE

Bulk Data Entry

DSHUFFLE – Design Variable for Composite Shuffling Optimization

Description

Defines parameters for the generation of composite shuffling design variables.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DSHUFFL ID ETYPE EID1 EID2 EID3 EID4 EID5 EID6


E

+ EID7 …

+ MAXSUC MANGLE MSUC C VSUC C


C

+ PAIR PANGLE PANGLE2 POPT


1

+ C ORE C REP C ANG1 C ANG2 C ANG3 C ANG4 C ANG5 C ANG6

+ C ANG7 …

+ C OVER VREP VANG1 VANG2 VANG3 VANG4 VANG5 VANG6

+ VANG7 …

+ RANGE PIDSTA PIDEND

Field Contents

ID Unique identification number.

No default (Integer > 0)

ETYPE Entity type for which this DSHUFFLE card is defined.

No default (STACK, PCOMP, or PCOMPG)

894 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

EID# Entity identification numbers. List of entities of type ETYPE for which this
DSHUFFLE card is defined.

No default (Integer > 0)

MAXSUCC MAXSUCC flag indicating that the "maximum number of successive plies"
constraint is applied. Multiple MAXSUCC constraints are allowed (see
Comment 1).

MANGLE Ply orientation, in degrees, to which the MAXSUCC constraint is applied.

No default (Real or ALL)

MSUCC Maximum number of successive plies for the MAXSUCC constraint.

No default (Integer > 0)

VSUCC Allowable percentage violation for the MAXSUCC constraint. 0.0 indicates
that this constraint cannot be violated.

Default = 0.0 (Real)

PAIR PAIR flag indicating that a pairing constraint is applied (see Comment 2).

PANGLE1 First ply orientation, in degrees, to which the PAIR constraint is applied.

No default (Real, only 45.0 allowed at this time)

PANGLE2 Second ply orientation, in degrees, to which the PAIR constraint is applied.

No default (Real, only -45.0 allowed at this time)

POPT Pairing option. SAME indicates that the stacking sequence should remain
the same for consecutive pairs. REVERSE indicates that the stacking
sequence should be reversed for alternate pairs.

Default = blank (SAME, REVERSE or BLANK)

CORE CORE flag indicating that a ply sequence for the core layer is defined.
Only one CORE sequence is allowed (see Comment 3).

CREP Number of times the core ply sequence should be repeated.

Default = 1 (Integer > 0)

CANG# Ply orientations, in degrees, defining the core.

No default (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 895

Proprietary Information of Altair Engineering


Field Contents

COVER COVER flag indicating that a ply sequence for the cover layer is defined.
Only one COVER sequence is allowed (see Comment 3).

VREP Number of times the cover ply sequence should be repeated.

Default = 1 (Integer > 0)

VANG# Ply orientations, in degrees, defining the cover.

No default (Real)

RANGE Indicates that starting and ending ply identification numbers are defined in
the following fields to specify the range of plies to be shuffled. OptiStruct
will only shuffle plies between PIDSTA and PIDEND. Multiple DSHUFFLE
entries can be created to define different ply ranges.

PIDSTA The ply identification number (starting ply) that defines the first ply in the
range to be shuffled.

No default (Integer > 0)

PIDEND The ply identification number (ending ply) that defines the last ply in the
range to be shuffled.

No default (Integer > 0)

Comments

1. The MAXSUCC constraint indicates that the stacking sequence should contain no sections
with more than a given number of successive plies with the same orientation. In the case
of symmetrical laminates, this constraint accounts for the mirrored successive plies on
both sides of the symmetry plane. In the image below, (a) shows invalid and valid
sequences for a non-symmetrical stack, and (b) shows invalid and valid sequences for a
symmetrical stack, both for MAXSUCC=3.

896 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


2. The PAIR constraint indicates that 45° and -45° plies should be paired together. The
POPT option specifies how the pairing should be accomplished, as illustrated on the figure
below.

3. The CORE and COVER constraints specify stacking sequences for the core and cover
layers respectively. Plies are listed from the bottom surface upward, in respect to the
element’s normal direction. In the example below, the sequence for the core is (0°, 0°,
90°, 90°) while the sequence for the cover is defined as (90°, 90°, 0°, 0°).

Note that, for non-symmetrical laminates, COVER actually corresponds to the bottom
cover, whereas CORE corresponds to the upper cover. At this point, it is not possible to
create an actual core for non-symmetrical stacks.

4. For a more detailed description and an example, refer to Optimization of Composite


Structures in the User’s Guide.

5. This card is represented as an optimization design variable in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 897

Proprietary Information of Altair Engineering


DSIZE

Bulk Data Entry

DSIZE – Design Variable for Free-Size Optimization

Description

DSIZE defines parameters for the generation of free-size design variables.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DSIZE ID PTYPE PID1 PID2 PID3 PID4 PID5 PID6

PID7 … … … … … …

Optional continuation lines for thickness definition:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

THIC K T0 T1

Optional continuation lines for stress constraint definition:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

STRESS UBOUND

Optional continuation lines for member size constraint definition:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MEMBSIZ MINDIM

Optional continuation lines for composite manufacturing constraints definition:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

+ C OMP LAMTHK LTMIN LTMAX LTSET LTEXC

898 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

+ C OMP PLYTHK PTGRP PTMIN PTMAX PTOPT PTSET PTEXC

+ C OMP PLYPC T PPGRP PPMIN PPMAX PPOPT PPSET PPEXC

+ C OMP PLYMAN PMGRP PMMAN PMOPT PMSET PMEXC

+ C OMP BALANC E BGRP1 BGRP2 BOPT

+ C OMP C ONST C GRP C THIC K C OPT

+ C OMP PLYDRP PDGRIP PDTYP PDMAX PDOPT PDSET PDEXC

+ PDDEF PDX PDY PDZ

Optional continuation lines for pattern grouping constraint definition:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PATRN TYP AID/XA YA ZA FID/XF YF ZF

UC YC SID/XS YS ZS

Optional continuation lines for "Master" definition for pattern repetition constraint:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MASTER

C AID/
C OORD C ID YC A ZC A C FID/XC F YC F ZC F
XC A

C SID/
YC S ZC S C TID/XC T YC T ZC T
XC S

Optional continuation lines for "Slave" definition for pattern repetition constraint:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SLAVE DSIZE_ID SX SY SZ

C OORD C ID C AID/ YC A ZC A C FID/XC F YC F ZC F

Altair Engineering OptiStruct 13.0 Reference Guide 899

Proprietary Information of Altair Engineering


XC A

C SID/
YC S ZC S C TID/XC T YC T ZC T
XC S

Optional continuation lines for fatigue constraint definition:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FATIGUE FTYPE FBOUND

Optional continuation lines for zone based free-sizing definition:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GROUP EG1 EG2 EG3 EG4 EG5 EG6

EG7 EG8 EG9 … … … …

Alternate continuation line for zone based free-sizing definition (Alternate Format):

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GROUP EG1 THRU EG2

Field Contents

ID Each DSIZE card must have a unique ID.

No default (Integer > 0)

PTYPE Property type for which DSIZE card is defined.

No default (PCOMP, PCOMPG, PSHELL, or STACK)

PID# Property identification numbers. List of properties of type


PTYPE for which this DSIZE card is defined. Use ALL in PID1
field if it applies to all properties of type PTYPE in the model.

No default (Integer > 0, or ALL)

900 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

THICK THICK flag indicating that minimum and possibly maximum


thickness value are to follow.

T0 Minimum thickness.

For PTYPE = PSHELL, this refers to the minimum thickness of the


shell. If no value is entered for T0, the T0 value on the PSHELL
card is used. If T0 is not defined on the PSHELL card, then
T0=0.0 is assumed.

This option does not apply for PTYPE = PCOMP, PCOMPG, or


STACK.

Default = blank (Real > 0.0)

T1 Maximum thickness.

For PTYPE = PSHELL, this refers to the maximum thickness of


the shell. If no value is entered for T1, the T value on the
PSHELL card is used.

This option does not apply for PTYPE = PCOMP, PCOMPG, or


STACK.

Default = blank (Real > T0)

STRESS STRESS flag indicating that von Mises stress constraints are
active and that an upper bound value for the stress is to follow.
See comment 4.

UBOUND Upper bound constraint on von Mises stress.

No default (Real > 0.0)

MEMBSIZ MEMBSIZ flag indicating that member size control is active for
the properties listed. Indicates that MINDIM is to follow.

MINDIM Specifies the minimum diameter of members formed. This


command is used to eliminate small members. It also eliminates
checkerboard results. See comment 3.

Default = No minimum member size control (Real > 0.0)

COMP COMP flag indicating that composite manufacturing constraints


are applied. Indicates that information about manufacturing
constraints is to follow. See comment 5.

Altair Engineering OptiStruct 13.0 Reference Guide 901

Proprietary Information of Altair Engineering


Field Contents

LAMTHK LAMTHK flag indicating that laminate thickness constraints are


applied. Multiple LAMTHK constraints are allowed. See
comment 5.

LTMIN Minimum laminate thickness for the LAMTHK constraint.

Default = blank (Real > 0.0)

LTMAX Maximum laminate thickness for the LAMTHK constraint.

Default = blank (Real > 0.0 and > LTMIN)

LTSET Set ID of elements to which the LAMTHK constraint is applied.

LTEXC Exclusion flag indicating that certain plies are excluded from the
LAMTHK constraint. The following options are supported:

NONE: Plies are not excluded.


CORE: The core is excluded. (Default)
CONST: Plies defined in the CONST constraint are excluded.
BOTH: CORE and CONST are considered.

PLYTHK PLYTHK flag indicating that ply thickness constraints are


applied. Multiple PLYTHK constraints are allowed.

PTGRP Ply orientation in degrees, ply sets or ply IDs, to which the
PLYTHK constraint is applied, depending on the PTOPT
selection.

No default (Real or Integer)

PTMIN Minimum thickness for the PLYTHK constraint.

Default = blank (Real > 0.0)

PTMAX Maximum thickness for the PLYTHK constraint.

Default = blank (Real > 0.0 and > PTMIN)

PTOPT Ply selection options for the PLYTHK constraint. Plies can be
selected based on the following:

BYANG: Orientation (Default)

902 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

BYSET: Ply sets


BYPLY: Ply IDs

PTSET Set ID of elements to which the PLYTHK constraint is applied.

PTEXC Exclusion flag indicating that certain plies are excluded from the
PLYTHK constraint. The following options are supported:

NONE: Plies are not excluded.


CORE: The core is excluded. (Default)
CONST: Plies defined in the CONST constraint are excluded.
BOTH: CORE and CONST are considered.

PLYPCT PLYPCT flag indicating that ply thickness percentage constraints


are applied. Multiple PLYPCT constraints are allowed.

PPGRP Ply orientation in degrees, ply sets or ply IDs, to which the
PLYPCT constraint is applied, depending on the PPOPT selection.

No default (Real or Integer)

PPMIN Minimum percentage thickness for the PLYPCT constraint.

Default = blank (Real > 0.0 and < 1.0)

PPMAX Maximum percentage thickness for the PLYPCT constraint.

Default = blank (Real > 0.0, < 1.0 and > PPMIN)

PPOPT Ply selection options for the PLYPCT constraint. Plies can be
selected based on the following:

BYANG: Orientation (Default)


BYSET: Ply sets
BYPLY: Ply IDs

PPSET Set ID of elements to which the PLYPCT constraint is applied.

PPEXC Exclusion flag indicating that certain plies are excluded from the
PLYPCT constraint. The following options are supported:

NONE: Plies are not excluded.


CORE: The core is excluded. (Default)

Altair Engineering OptiStruct 13.0 Reference Guide 903

Proprietary Information of Altair Engineering


Field Contents

CONST: Plies defined in the CONST constraint are excluded.


BOTH: CORE and CONST are considered.

PLYMAN PLYMAN flag indicating that manufacturable ply thickness


constraints are applied. Multiple PLYMAN constraints are
allowed.

PMGRP Ply orientation in degrees, ply sets or ply IDs, to which the
PLYMAN constraint is applied, depending on the PMOPT
selection.

No default (Real or Integer)

PMMAN Manufacturable ply thickness. See comment 6.

Default = blank (Real > 0.0)

PMOPT Ply selection options for the PLYMAN constraint. Plies can be
selected based on the following:

BYANG: Orientation (Default)


BYSET: Ply sets
BYPLY: Ply IDs

PMSET Set ID of elements to which the PLYMAN constraint is applied.

PMEXC Exclusion flag indicating that certain plies are excluded from the
PLYMAN constraint. The following options are supported:

NONE: Plies are not excluded.


CORE: The core is excluded. (Default)
CONST: Plies defined in the CONST constraint are excluded.
BOTH: CORE and CONST are considered.

BALANCE BALANCE flag indicating that a balancing constraint is applied.


Multiple BALANCE constraints are allowed.

BGRP1 First ply orientation in degrees, ply sets or ply IDs, to which the
BALANCE constraint is applied, depending on the BOPT
selection.

No default (Real or Integer)

904 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

BGRP2 Second ply orientation in degrees, ply sets or ply IDs, to which
the BALANCE constraint is applied, depending on the BOPT
selection.

No default (Real or Integer)

BOPT Ply selection options for the BALANCE constraint. Plies can be
selected based on the following:

BYANG: Orientation (Default)


BYSET: Ply sets
BYPLY: Ply IDs

CONST CONST flag indicating that a constant thickness constraint is


applied. Multiple CONST constraints are allowed.

CGRP Ply orientation in degrees, ply sets or ply IDs, to which the
CONST constraint is applied, depending on the COPT selection.

No default (Real or Integer)

CTHICK Constant ply thickness for the CONST constraint.

No default (Real > 0.0)

COPT Ply selection options for the CONST constraint. Plies can be
selected based on the following:

BYANG: Orientation (Default)


BYSET: Ply sets
BYPLY: Ply IDs

PLYDRP Indicates that ply drop-off constraints are applied. Multiple


PLYDRP constraints are allowed.

PDGRP Ply orientation in degrees, ply sets or ply IDs, to which the
PLYDRP constraint is applied, depending on the PDOPT selection.

No default. (Real or Integer)

PDTYP PDTYP specifies the type of the drop-off constraint as:

PLYSLP (Default)
PLYDRP
TOTSLP

Altair Engineering OptiStruct 13.0 Reference Guide 905

Proprietary Information of Altair Engineering


Field Contents

TOTDRP

(see Comment 11)

PDMAX Maximum allowed drop-off for the PLYDRP constraint.

No default (Real > 0)

PDOPT Ply selection options for the PLYDRP constraint. Plies can be
selected based on the following:

BYANG: Orientation (Default)


BYSET: Ply sets
BYPLY: Ply IDs

PDSET Set IDs of elements to which the PLYDRP constraint is applied.

PDEXC Exclusion flag indicates that certain plies are excluded from the
PLYDRP constraint. The following options are supported:

NONE: Plies are not excluded.


CORE: The core is excluded. (Default).
CONST: Plies defined in the CONST constraint are excluded.
BOTH: CORE and CONST are considered.

PDDEF Optional definition to fine-tune the drop-off constraint.


Currently only DIRECT is available to request directional drop-
off, in which case PDX, PDY and PDZ specify the drop-off
direction. See comment 12.

PDX, PDY, PDZ Used to specify the drop-off direction when DIRECT is input in
the PDDEF field. See comment 12.

PATRN PATRN flag indicating that pattern grouping is active for the
properties listed. Indicates that information for pattern
grouping is to follow.

TYP Indicates the type of pattern grouping requested. See


comment 1.

Default = No pattern grouping (1, 2, 3, 9, or 10)

AID/XA, YA, ZA Anchor point for pattern grouping. The point may be defined by
entering a grid ID in the AID field or by entering X, Y, and Z
coordinates in the XA, YA, and ZA fields. These coordinates will
be in the basic coordinate system. See comment 1.

906 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Default = origin (Real in all three fields or Integer in first field)

FID/XF, YF, ZF First point for pattern grouping. The point may be defined by
entering a grid ID in the FID field or by entering X, Y, and Z
coordinates in the XF, YF, and ZF fields. These coordinates will
be in the basic coordinate system. See comment 1.

No default (Real in all three fields or Integer in the first field)

UCYC Number of cyclical repetitions for cyclical symmetry. This field


defines the number of radial "wedges" for cyclical symmetry.
The angle of each wedge is computed as 360.0/UCYC. See
comment 1.

Default = blank (Integer > 0 or blank)

SID/XS, YS, ZS Second point for pattern grouping. The point may be defined by
entering a grid ID in the SID field or by entering X, Y, and Z
coordinates in the XS, YS, and ZS fields. These coordinates will
be in the basic coordinate system. See comment 1.

No default (Real in all three fields or Integer in first field)

MASTER MASTER flag indicating that this design variable may be used as
a master pattern for pattern repetition. See comment 2.

SLAVE SLAVE flag indicating that this design variable is slave to the
master pattern definition referenced by the following DSIZE_ID
entry. See comment 2.

DSIZE_ID DSIZE identification number for a master pattern definition.

No default (Integer > 0)

SX, SY, SZ Scale factors for pattern repetition, in X, Y, and Z directions


respectively. See comment 2.

Default = 1.0 (Real > 0.0)

COORD COORD flag indicating information regarding the coordinate


system for pattern repetition is to follow. This is required if
either MASTER or SLAVE flags are present.

CID Coordinate system ID for a rectangular coordinate system that


may be used as the pattern repetition coordinate system. See
comment 2.

Altair Engineering OptiStruct 13.0 Reference Guide 907

Proprietary Information of Altair Engineering


Field Contents

Default = 0 (Integer > 0)

CAID/XCA, YCA, ZCA Anchor point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CAID field or
by entering X, Y, and Z coordinates in the XCA, YCA, and ZCA
fields. These coordinates will be in the basic coordinate
system. See comment 2.

No default (Real in all three fields or Integer in the first field)

CFID/XCF, YCF, ZCF First point for pattern repetition coordinate system. The point
may be defined by entering a grid ID in the CFID field or by
entering X, Y, and Z coordinates in the XCF, YCF, and ZCF
fields. These coordinates will be in the basic coordinate
system. See comment 2.

No default (Real in all three fields or Integer in the first field)

CSID/XCS, YCS, ZCS Second point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CSID field or
by entering X, Y, and Z coordinates in the XCS, YCS, and ZCS
fields. These coordinates will be in the basic coordinate
system. See comment 2.

No default (Real in all three fields or Integer in the first field)

CTID/XCT, YCT, ZCT Third point for pattern repetition coordinate system. The point
may be defined by entering a grid ID in the CTID field or by
entering X, Y, and Z coordinates in the XCT, YCT, and ZCT
fields. These coordinates will be in the basic coordinate
system. See comment 2.

No default (Real in all three fields or Integer in the first field)

FATIGUE FATIGUE flag indicating that fatigue constraints are active and
their definition is to follow.

FTYPE Specifies the type of fatigue constraint; it can be DAMAGE, LIFE


or FOS.

FBOUND Specifies the bound value. If FTYPE is DAMAGE, FBOUND will be


the upper bound of fatigue damage. If FTYPE is LIFE or FOS,
FBOUND will be the lower bound of fatigue life (LIFE) or Factor
of Safety (FOS), respectively.

No default (Real)

908 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

GROUP Specifies the definition of zone based free-sizing optimization.


Indicates that element group IDs will follow.

EG# Element group numbers. Element groups are created through


element sets. See comment 7.

No default (Integer > 0)

THRU This keyword can be used in the optional alternate format to


define zone based free-sizing optimization.

This keyword is used for ID range definition to indicate that all


ID’s between the preceding ID (EG1) and the following ID (EG2)
are to be included in the set.

Comments

1. There are currently five pattern grouping options for free-size optimization:

1-plane symmetry (TYP = 1)

This type of pattern grouping requires that the anchor point and the first point be defined.
A vector from the anchor point to the first point is normal to the plane of symmetry.

2-plane symmetry (TYP = 2)

This type of pattern grouping requires that the anchor point, first point, and second point
be defined. A vector from the anchor point to the first point is normal to the first plane of
symmetry. The second point is projected normally onto the first plane of symmetry. A
vector from the anchor point to this projected point is normal to the second plane of
symmetry.

3-plane symmetry (TYP = 3)

This type of pattern grouping requires that the anchor point, first point, and second point
be defined. A vector from the anchor point to the first point is normal to the first plane of
symmetry. The second point is projected normally onto the first plane of symmetry. A
vector from the anchor point to this projected point is normal to the second plane of
symmetry. The third plane of symmetry is orthogonal to both the first and second planes
of symmetry, passing through the anchor point.

Cyclic (TYP = 10)

This type of pattern grouping requires that the anchor point, first point, and number of
cyclical repetitions be defined. A vector from the anchor point to the first point defines
the axis of symmetry.

Cyclic with symmetry (TYP = 11)

This type of pattern grouping requires that the anchor point, first point, second point,
and number of cyclical repetitions be defined. A vector from the anchor point to the first

Altair Engineering OptiStruct 13.0 Reference Guide 909

Proprietary Information of Altair Engineering


point defines the axis of symmetry. The anchor point, first point, and second point all lay
on a plane of symmetry. A plane of symmetry lies at the center of each cyclical
repetition.

For a more detailed description, refer to the Pattern Grouping for Free-Size Optimization
page contained within the User’s Guide section Manufacturability for Free-Size
Optimization.

2. Pattern repetition allows similar regions of the design domain to be linked together so as
to produce similar topological layouts. This is facilitated through the definition of "Master"
and "Slave" regions. A DSIZE card may only contain one MASTER or SLAVE flag. For both
"Master" and "Slave" regions, a pattern repetition coordinate system is required and is
described following the COORD flag. In order to facilitate reflection, the coordinate
system may be a left-handed or right-handed Cartesian system. The coordinate system
may be defined in one of two ways, listed here in order of precedence:

Four points are defined and these are utilized as follows to define the coordinate
system (this is the only way to define a left-handed system):
- A vector from the anchor point to the first point defines the x-axis.

- The second point lies on the x-y plane, indicating the positive sense of the y-axis.

- The third point indicates the positive sense of the z-axis.

A rectangular coordinate system and an anchor point are defined. If only an anchor
point is defined, it is assumed that the basic coordinate system is to be used.
Multiple "Slaves" may reference the same "Master."

Scale factors may be defined for "Slave" regions, allowing the "Master" layout to be
adjusted.

For a more detailed description, refer to the Pattern Repetition for Free-Size Optimization
contained within the User’s Guide section Manufacturability for Free-Size Optimization.

3. It is recommended that a MINDIM value be chosen which allows for the formation of
members that are at least three elements thick. When pattern grouping constraints are
active, a MINDIM value of three times the average element edge length is enforced, and
user-defined values (which are smaller than this value) will be replaced by this value.

4. Von Mises stress constraints may be defined for topology and free-size optimization
through the STRESS optional continuation line on the DTPL or the DSIZE card. There are
a number of restrictions with this constraint:

The definition of stress constraints is limited to a single von Mises permissible stress.
The phenomenon of singular topology is pronounced when different materials with
different permissible stresses exist in a structure. Singular topology refers to the
problem associated with the conditional nature of stress constraints that is the stress
constraint of an element disappears when the element vanishes. This creates another
problem in that a huge number of reduced problems exist with solutions that cannot
usually be found by a gradient-based optimizer in the full design space.
Stress constraints for a partial domain of the structure are not allowed because they
often create an ill-posed optimization problem since elimination of the partial domain
would remove all stress constraints. Consequently, the stress constraint applies to the

910 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


entire model when active, including both design and non-design regions, and stress
constraint settings must be identical for all DSIZE and DTPL cards.

The capability has built-in intelligence to filter out artificial stress concentrations
around point loads and point boundary conditions. Stress concentrations due to
boundary geometry are also filtered to some extent as they can be improved more
effectively with local shape optimization.
Due to the large number of elements with active stress constraints, no element stress
report is given in the table of retained constraints in the .out file. The iterative
history of the stress state of the model can be viewed in HyperView or HyperMesh.

Stress constraints do not apply to 1D elements.


Stress constraints may not be used when enforced displacements are present in the
model.
5. The following manufacturing constraints are available for composite free-sizing
optimization:

Lower and upper bounds on the total thickness of the laminate (LAMTHK).
Lower and upper bounds on the thickness of a given orientation (PLYTHK).
Lower and upper bounds on the thickness percentage of a given orientation (PLYPCT).
Linking between the thicknesses of two given orientations (BALANCE).
Constant (non-designable) thickness of a given orientation (CONST).
LAMTHK, PLYTHK, PLYPCT, and PLYMAN can be applied locally to sets of elements.
There can be elements that do not belong to any set.
For a more detailed description and an example, refer to Optimization of Composite
Structures in the User’s Guide.

6. PLYMAN has no influence on the free-size phase, but this information will be translated
into the TMANUF entry on the PLY card for the sizing phase.

7. Elements within each group will have uniform ply thicknesses.

8. The core is designable by default. It can be made non-designable through the CONST
manufacturing constraint. To facilitate this, the keyword CORE can be used instead of a
ply ID when BYPLY is activated.

9. The core is excluded from the LAMTHK, PLYTHK, PLYPCT and PLYMAN manufacturing
constraints by default.

10. Legacy data field PTMAN (for manufacturable ply thickness) defined on the PLYTHK and
PLYPCT entries is supported. However, it is now recommended to define the
manufacturable ply thickness in the PMMAN field through the PLYMAN continuation line as
this offers more control.

11. The options for selecting the type of drop-off constraints for PDTYP are defined for a set
of plies, as shown in the figures below:

The options for PDTYP are:

PLYSLP

Altair Engineering OptiStruct 13.0 Reference Guide 911

Proprietary Information of Altair Engineering


PLYDRP

TOTSLP
TOTDRP

Assuming that the plies are stacked as shown above, you have the following definitions:

912 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Altair Engineering OptiStruct 13.0 Reference Guide 913

Proprietary Information of Altair Engineering


12. The optional PDDEF definition is used to fine-tune the drop-off constraint. Currently, only
the DIRECT option is available for the PDDEF field.

Field Value

PDDEF DIRECT – This option allows you to fine-tune the drop-off


constraint by requesting directional drop-off. The direction of
drop-off can be specified by defining a directional vector with
respect to the basic coordinate system. The directional vector
is defined using the PDX, PDY and PDZ values.

PDX, PDY, PDZ PDX, PDY and PDZ are real numbers.

These values are used to specify the drop-off direction when


DIRECT is input in the PDDEF field. They specify the three
components of a directional vector defined with respect to the
basic coordinate system.
Example:
If drop-off control is required in the X-direction, then 1,0,0
can be defined in the PDX, PDY, PDZ fields respectively. 0,1,0
can be defined for Y-direction drop-off control.

13. This card is represented as an optimization design variable in HyperMesh.

914 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DSYSID

Bulk Data Entry

DSYSID – Design Objective for System Identification

Description

Defines responses and their target values for a system identification problem.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DSYSID DOID LABEL RID1 SID1 T1 W1

+ RID2 SID2 T2 W2

+ ...

+ RIDn SIDn Tn Wn

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DSYSID 22 SYS 3 4 0.002

+ 5 5 0.05

Associated Cards

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DRESP1 3 TZ488 DISP 3 488

DRESP1 5 TZ601 DISP 3 601

Altair Engineering OptiStruct 13.0 Reference Guide 915

Proprietary Information of Altair Engineering


Field Contents

DOID Design objective identification number.

(Integer > 0)

LABEL User-defined name for the response.

No default (Character)

RIDi DRESP1, DRESP2, or DRESP3 identification number.

(Integer > 0)

SIDi Subcase identification number; use ALL if it applies to all subcases.

Default = ALL (Integer > 0, blank or ALL)

Ti Target value.

No default (Real)

Wi Weighting factor.

Default = 1.0 (Real or blank)

Comments

1. If the DSYSID entry is referenced by a DESOBJ subcase entry, a least squares objective
function is used in the optimization. The objective function is the sum of the squared,
weighted, normalized differences between the target responses and those calculated by
the finite element analysis:

If the DSYSID entry is referenced by a MINMAX or MAXMIN subcase entry, the beta
method is applied in the optimization as follows:

2. DSYSID entries must have unique identification numbers with respect to DRESP1, DRESP2,
and DRESP3 entries.

916 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. DRESP1, DRESP2, and DRESP3 entries referenced by the DSYSID entry can define only a
single response per subcase when the DESOBJ formulation is used. There is no such
limitation with the MINMAX or MAXMIN formulations.

4. In order to use DSCREEN to control the number of retained responses when performing a
system identification, RTYPE=EQUA needs to be used on the DSCREEN entry.

Altair Engineering OptiStruct 13.0 Reference Guide 917

Proprietary Information of Altair Engineering


DTABLE

Bulk Data Entry

DTABLE – Table of Constants

Description

List of constants to be used in functions defined by DEQATN.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DTABLE LABL1 VAL1 LABL2 VAL2 LABL3 VAL3 LABL4 VAL4

LABL5 VAL5 Etc…

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DTABLE W 123.00 H 321.00 B 55.55 AGE 21

C 36.0 WST 24.0 HPS 35.0

Field Contents

LABLi Constant Label.

(Character)

VALi Constant value.

(Real)

Comments

1. If a DTABLE entry has a pair of blank fields, they are ignored. If there are other
constants after the blank fields, they are read in.

2. If fields are full of zeros, the constant label is "0", and the value is 0.0.

3. This card is represented as an optimization table entry in HyperMesh.

918 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DTI,SPECSEL

Bulk Data Entry

DTI,SPECSEL – Response Spectra Input Correlation Table

Description

Correlates spectra lines specified on TABLED1 entries with damping values.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DTI SPEC SEL ID TYPE TID1 DAMP1 TID2 DAMP2

TID3 DAMP3 … … … … … …

… …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DTI SPEC SEL 99 A 2 0.0 3 0.02

4 0.04

Field Contents

ID DTI,SPECSEL identification number.

No default (Integer > 0)

TYPE Type of spectrum. Can be either acceleration (A), velocity (V) or


displacement (D).

No default (A, V, D)

Altair Engineering OptiStruct 13.0 Reference Guide 919

Proprietary Information of Altair Engineering


Field Contents

TID# Identification number of a TABLED1 entry that defines a line of the


spectrum.

No default (Integer > 0)

DAMP# Damping value assigned to TID#.

No default (Real)

Comments

1. All DTI,SPECSEL cards must have unique ID numbers.

2. The TID#, DAMP# pairs list the TABLED1 entry, which defines a line of the spectrum and
the damping value assigned to it. The damping value is in the units of fraction of critical
damping.

3. Refer to Response Spectrum Analysis in the User’s Guide for more details.

920 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DTI,UNITS

Bulk Data Entry

DTI,UNITS – Units Definition

Description

Defines units for multi-body, component mode synthesis (flexible-body preparation), and
geometric nonlinear solution sequences.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DTI UNITS 1 MASS FORC E LENGTH TIME

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DTI UNITS 1 KG N M S

Field Contents

MASS Units of mass. See comment 1.

Default = KG (KG, LBM, SLUG, GRAM, OZM, KLBM, MGG, SLINCH, UG, NG,
USTON, or MG)

FORCE Units of force. See comment 2.

Default = N (N, LBF, KGF, OZF, DYNE, KN, KLBF, MN, UN, or NN)

LENGTH Units of length. See comment 3.

Default = MM (MM, KM, M, CM, MI, FT, IN, UM, NM, ANG, YD, MIL, or
UIN)

TIME Units of time. See comment 4.

Default = S (S, H, MIN, MS, US, NANOSEC, or D)

Altair Engineering OptiStruct 13.0 Reference Guide 921

Proprietary Information of Altair Engineering


Comments

1. The following options are available for input for MASS:

kg kilogram

lbm pound-mass

slug slug

gram gram

ozm ounce-mass

klbm kilo pound-mass (1000.lbm)

mgg megagram

slinch 12 slugs

ug Microgram

ng Nanogram

uston US ton

mg Milligram

2. The following options are available for input for FORCE:

n newton

lbf pounds-force

kgf kilograms-force

ozf ounce-force

dyne dyne

kn kilonewton

klbf kilo pound-force (1000.lbf)

mn Millinewton

922 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


un Micronewton

nn Nanonewton

3. The following options are available for input for LENGTH:

km kilometer

m meter

cm centimeter

mm millimeter

mi mile

ft foot

in inch

um Micrometer

nm Nanometer

ang Angstrom

yd Yard

mil Milli-inch

uin Micro-inch

4. The following options are available for input for TIME:

s seconds

h hours

min minutes

ms milliseconds

us Microsecond

Altair Engineering OptiStruct 13.0 Reference Guide 923

Proprietary Information of Altair Engineering


nanosec Nanosecond

d day

5. PARAM, WTMASS is ignored for the multi-body and component mode synthesis (flexible-
body preparation) solution sequences. Unit data for these solution sequences is supplied
on the DTI,UNITS bulk data entry.

6. This DTI, UNITS data entry is the same as the UNITS entry.

7. This card is represented as a control card in HyperMesh.

924 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DTPG

Bulk Data Entry

DTPG – Design Variable for Topography Optimization

Description

Defines parameters for the generation of topography design variables.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DTPG ID TYPE PID1/DVID PID2 PID3 PID4 PID5 PID6

PID7 … … … … … …

MW ANG BF HGT Norm/XD YD ZD SKIP

PATRN TYP AID/XA YA ZA FID/XF YF ZF

PATRN2 UC YC SID/XS YS ZS

BOUNDS LB UB INIT

Optional continuation lines for "Master" definition for pattern repetition constraint:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MASTER

C OORD C ID C AID/ YC A ZC A C FID/XC F YC F ZC F


XC A

C SID/ YC S ZC S C TID/ YC T ZC T
XC S XC T

Altair Engineering OptiStruct 13.0 Reference Guide 925

Proprietary Information of Altair Engineering


Optional continuation lines for "Slave" definition for pattern repetition constraint:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SLAVE DTPL_ID SX SY SZ

C OORD C ID C AID/ YC A ZC A C FID/XC F YC F ZC F


XC A

C SID/ YC S ZC S C TID/ YC T ZC T
XC S XC T

Example 1

This example defines a topography design variable which allows for swages to be created in
components referencing the PSHELL properties 1, 9, and 23. The swages will have a
minimum width of 3 units, a draw angle of 600, and a maximum height of 5 units. The draw
direction will be in the element’s normal direction, but the swages may grow in either the
positive or negative direction. The swages should be grouped such that they form a
cyclical pattern of 1200 intervals about the z-axis, through the point (0,25,0), and they
also should be symmetrical about the xy plane.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DTPG 1 PSHELL 1 9 23

3.0 60.0 Yes 5.0 Norm both

PATRN 50 0.0 25.0 0.0 0.0 1.0 0.0

PATRN2 3 1.0 0.0 0.0

BOUNDS -1.0 1.0

Example 2

This example defines a topography design variable that references the shape variables
defined by the DVGRIDs with ID 1. The swages will have a minimum width of 5 units and a
draw angle of 750. The height and draw direction of the swages is defined by the DVGRID
cards. Also ensure that the swages can only grow in the positive direction as defined by
the DVGRID cards.

926 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DTPG 1 DVGRID 1

5.0 75.0 YES

BOUNDS 0.0 1.0

Field Contents

ID Each DTPG card must have a unique ID.

No default (Integer > 0)

TYPE Indicate whether DTPG card is defined for PSHELL, PCOMP, or


DVGRID.

No default (PSHELL, PCOMP, or DVGRID)

PID/DVID If TYPE is PSHELL or PCOMP, then this entry is a Property


identification number. Use ALL if it applies to all properties of type
PTYPE in the model. Numerous PIDs may be given.

If TYPE is DVGRID, then this entry is the Design Variable Number for a
set of DVGRIDs. Only one DVID may be given.

Default = ALL (Integer > 0, blank or ALL)

MW Bead minimum width. This parameter controls the width of the beads
in the model [recommended value between 1.5 and 2.5 times the
average element width]. See comment 1.

No default (Real > 0.0)

ANG Draw angle in degrees. This parameter controls the angle of the
sides of the beads (recommended value between 60 and 75 degrees).
See comment 1.

No default (1.0 < Real < 89.0)

BF Buffer zone. This parameter will establish a buffer zone between


elements in the design domain and elements outside the design
domain. See comment 2.

Altair Engineering OptiStruct 13.0 Reference Guide 927

Proprietary Information of Altair Engineering


Field Contents

Default = YES (YES, or NO)

HGT Draw height. This parameter sets the maximum height of the beads
to be drawn. This field is only valid if TYPE is PSHELL or PCOMP.

No default (Real > 0.0)

norm/XD,YD,ZD Draw direction. If norm/XD field is ‘norm’, the shape variables will be
created in the normal directions of the elements. If all the fields are
real, the shape variable will be created in the direction specified by
the xyz vector defined by the three fields. The X, Y, and Z values
are in the global coordinate system. This field is only valid if TYPE is
PSHELL or PCOMP.

Default = NORM (NORM in norm/XD field or Real in all three fields)

SKIP Boundary skip. This parameter tells OptiStruct to leave certain nodes
out of the design domain. If ‘none’, all nodes attached to elements
whose PIDs are specified will be a part of the shape variables. If ‘bc’
or ‘spc’, any nodes which have SPC or SPC1 declarations are omitted
from the design domain. If ‘load’, any nodes which have FORCE,
FORCE1, MOMENT, MOMENT1, or SPCD declarations are omitted from
the design domain. If ‘both’, nodes with either ‘spc’ or ‘load’
declarations are omitted from the design domain. This field is only
valid if TYPE is PSHELL or PCOMP.

Default = BOTH (BOTH, BC, SPC, LOAD, or NONE)

PATRN PATRN flag indicating that variable pattern grouping is active.


Indicates that information about the pattern group will follow.

TYP Type of variable grouping pattern. Required if any symmetry or


variable pattern grouping is desired. If zero or blank, anchor node,
first vector, and second vector definitions are ignored. If less than
20, second vector definition is ignored. See comment 4.

Default = 0 (Integer > 0)

AID/XA,YA,ZA Variable grouping pattern anchor point. These fields define a point
that determines how grids are grouped into variables. See comment
3. The X, Y, and Z values are in the global coordinate system. You
may put a grid ID in the AID/XA field to define the anchor point.

Default = origin (Real in all three fields or Integer in AID/XA field)

928 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

FID/XF,YF,ZF Direction of first vector for variable pattern grouping. These fields
define an xyz vector which determines how grids are grouped into
variables (See comment 3). The X, Y, and Z values are in the global
coordinate system. You may put a grid ID in the FID/XF field to
define the first vector. This vector goes from the anchor point to
this grid. If all fields are blank and the TYP field is not blank or zero,
OptiStruct gives an error.

No default

PATRN2 PATRN2 flag indicating variable pattern grouping continuation card.


This card is only required when a second vector is needed to define
the pattern grouping.

UCYC Number of cyclical repetitions for cyclical symmetry. This field


defines the number of radial "wedges" for cyclical symmetry. The
angle of each wedge is computed as 360.0 / UCYC. See comment 4.

Default = 0 (Integer > 0 or blank)

SID/XS,YS,ZS Direction used to determine second vector for variable pattern


grouping. These fields define an xyz vector which, when combined
with the first vector, form a plane. The second vector is calculated
to lie in that plane and is perpendicular to the first vector. The
second vector is sometimes required to determine how grids are
grouped into variables (See comment 3). The X, Y, and Z values are
in the global coordinate system. You may put a grid ID in the SID/XS
field to define the second vector. This vector goes from the anchor
point to this grid. If all fields are blank and the TYP field contains a
value of 20 or higher, OptiStruct gives an error.

No default

BOUNDS BOUNDS flag indicating that information on upper and lower limits and
the initial value for grid movement are to follow.

LB Lower bound on variables controlling grid movement. This sets the


lower bound on grid movement equal to LB*HGT.

Default = 0.0 (Real < UB)

UB Upper bound on variables controlling grid movement. This sets the


upper bound on grid movement equal to UB*HGT.

Default = 1.0 (Real > LB)

Altair Engineering OptiStruct 13.0 Reference Guide 929

Proprietary Information of Altair Engineering


Field Contents

INIT The initial value of the variables controlling grid movement. This sets
the initial value on grid movement equal to INIT*HGT.

Default = LB + factor*(UB-LB), if LB > 0.0 and UB > 0.0

Default = UB - factor*(UB-LB), if LB < 0.0 and UB < 0.0

Default = factor*max(abs(LB),UB), if LB < 0.0 and UB > 0.0

where:

factor = 0.0 if this DTPG is not used in a BEADFRAC response or is


used in a BEADFRAC response that is neither chosen as the
objective nor constrained.

factor = 0.9 if this DTPG is used in a BEADFRAC response that is


chosen as the objective.

factor = constraint_value if this DTPG is used in a BEADFRAC


response that is constrained.

(LB < Real < UB)

MASTER MASTER flag indicating that this design variable may be used as a
master pattern for pattern repetition.

COORD COORD flag indicating information regarding the coordinate system for
pattern repetition is to follow. This is required if either MASTER or
SLAVE flags are present.

CID Coordinate system ID for a rectangular coordinate system that may


be used as the pattern repetition coordinate system. See comment
6.

Default = 0 (Integer > 0)

CAID/XCA, Anchor point for pattern repetition coordinate system. The point
YCA, ZCA may be defined by entering a grid ID in the CAID field or by entering
X, Y, and Z coordinates in the XCA, YCA, and ZCA fields. These
coordinates will be in the basic coordinate system. See comment 6.

No default (Real in all three fields or Integer in the first field)

CFID/XCF, YCF, First point for pattern repetition coordinate system. The point may
ZCF be defined by entering a grid ID in the CFID field or by entering X, Y,

930 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

and Z coordinates in the XCF, YCF, and ZCF fields. These


coordinates will be in the basic coordinate system. See comment 6.

No default (Real in all three fields or Integer in the first field)

CSID/XCS, Second point for pattern repetition coordinate system. The point
YCS, ZCS may be defined by entering a grid ID in the CSID field or by entering
X, Y, and Z coordinates in the XCS, YCS, and ZCS fields. These
coordinates will be in the basic coordinate system. See comment 6.

No default (Real in all three fields or Integer in the first field)

CTID/XCT, Third point for pattern repetition coordinate system. The point may
YCT, ZCT be defined by entering a grid ID in the CTID field or by entering X, Y,
and Z coordinates in the XCT, YCT, and ZCT fields. These
coordinates will be in the basic coordinate system. See comment 6.

No default (Real in all three fields or Integer in the first field)

SLAVE SLAVE flag indicating that this design variable is slaved to the master
pattern definition referenced by the following DTPL_ID entry. See
comment 6.

DTPL_ID DTPL identification number for a master pattern definition.

No default (Integer > 0)

SX, SY, SZ Scale factors for pattern repetition in X, Y, and Z directions


respectively. See comment 6.

Default = 1.0 (Real > 0.0)

Comments

1. The bead minimum width and draw angles are used to determine the geometry of the
shape variables. The figure below shows a cross-section of a single shape variable fully
extended normal to the plane of the design elements. The top of the bead is flat across
the circular area with a diameter equal to the minimum bead width parameter. The sides
of the bead taper down at an angle equal to the draw angle parameter.

Altair Engineering OptiStruct 13.0 Reference Guide 931

Proprietary Information of Altair Engineering


Bead width and draw angle definitions

2. The buffer zone is a parameter that controls how the interfaces between design and non-
design elements are treated. If active, OptiStruct will place the shape variables far
enough away from the non-design elements so that the proper bead widths and draw
angles are maintained. If inactive, the boundary between the beads and non-design
elements will have an abrupt transition. Any nodes that were skipped due to the
boundary skip parameter (field 10) will also have a buffer zone created around them.

Transitions between design and non-design elements with and without buffer zone

3. Symmetry of topography optimization can be enforced across one, two, or three planes.
Defining symmetry planes for symmetric model and loading conditions is recommended
because automatic variable generation may not be symmetric if it is not enforced. A
symmetric mesh is not necessary, OptiStruct will create variables that are very close to
identical across the plane(s) of symmetry. If the mesh is larger on one side of the
plane(s) of symmetry than the other, OptiStruct will reflect variables created on the
‘positive’ side of the plane(s) of symmetry to the other side(s) but will not create
variables on the ‘negative’ side(s) of the plane(s) of symmetry that do not overlap with
the positive side. The positive side of the plane(s) of symmetry is the one in which the
first vector, second vector, and cross product thereof are pointing toward.

4. Variable pattern grouping may be defined for a DTPG card. OptiStruct will generate shape
variables based on the type of pattern selected in field 20. For variable grouping pattern
types 1 through 14, only the first vector and anchor node need to be defined. For
variable pattern grouping types 20 or higher, the first and second vectors need to be
defined as well as the anchor node. If a grid is used to define the first vector, the normal
vector will begin at the anchor point and extend towards the given grid (see below).
Grids or xyz data may be used for either the first vector, second vector, or anchor point
and can be a mixture, (that is the anchor point may be determined by a grid and the first
vector determined by xyz data or vice-versa).

One very useful feature for topography optimization in OptiStruct is the automatic
generation of shape variables in simple patterns. In many cases, due to manufacturing
constraints or the risk of elements being collapsed upon them during shape optimization, it

932 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


is required to create shape variables in patterns that conform to the desired shape of the
part. In basic topography optimization (TYP = 0), OptiStruct creates shape variables that
are circular. OptiStruct contains a library of different shape variable patterns which can
be accessed using the TYP parameter on the DTPG card.

Defining the first vector using a grid point

The second vector is calculated by taking the grid point or vector defined in fields 22, 23,
and 24 and projecting it onto plane 1. If a grid point was used to define the second
vector, the second vector is a vector running from the anchor node to the projected grid
point. If a vector was used to define the second vector, the base of the projected
vector is placed at the anchor point. The second vector is normal to plane 2 (see
below).

Plane 3 is determined to be normal to both plane 1 and plane 2 (see below).

5. For a list of patterns supported by OptiStruct, refer to Pattern Grouping Options.

6. Pattern repetition allows similar regions of the design domain to be linked together so as

Altair Engineering OptiStruct 13.0 Reference Guide 933

Proprietary Information of Altair Engineering


to produce similar topographical layouts. This is facilitated through the definition of
"Master" and "Slave" regions. A DTPG card may only contain one MASTER or SLAVE flag.
Bead parameters will not be exported for any DTPG cards containing the SLAVE flag. For
both "Master" and "Slave" regions, a pattern repetition coordinate system is required and
is described following the COORD flag. In order to facilitate reflection, the coordinate
system may be a left-handed or right-handed Cartesian system. The coordinate system
may be defined in one of two ways, listed here in order of precedence:

Four points are defined and these are utilized as follows to the define the coordinate
system (this is the only way to define a left-handed system):
- A vector from the anchor point to the first point defines the x-axis.
- The second point lies on the x-y plane, indicating the positive sense of the y-axis.
- The third point indicates the positive sense of the z-axis.
A rectangular coordinate system and an anchor point are defined. If only an anchor
point is defined, it is assumed that the basic coordinate system is to be used.
Multiple "Slaves" may reference the same "Master."

Scale factors may be defined for "Slave" regions, allowing the "Master" layout to be
adjusted.

For a more detailed description, refer to the Pattern Repetition page contained within the
User's Guide section Manufacturability for Topography Optimization.

7. This card is represented as an optimization design variable in HyperMesh.

934 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DTPL

Bulk Data Entry

DTPL – Design Variable for Topology Optimization

Description

Defines parameters for the generation of topology design variables.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DTPL ID PTYPE PID1 PID2 PID3 PID4 PID5 PID6

PID7 … … … … … …

… …

Optional continuation lines for minimum thickness definition:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TMIN T0

Optional continuation lines for stress constraint definition:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

STRESS UBOUND

Optional continuation lines for member size constraint definition:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MEMBSIZ MINDIM MAXDIM MINGAP

Altair Engineering OptiStruct 13.0 Reference Guide 935

Proprietary Information of Altair Engineering


Optional continuation lines for mesh type definition:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MESH MTYP

Optional continuation lines for draw direction constraint definition:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DRAW DTYP DAID/ YDA ZDA DFID/ YDF ZDF


XDA XDF

OBST OPID1 OPID2 OPID3 OPID4 OPID5 OPID6 OPID7

OPID8 … … … … … …

NOHOLE

STAMP TSTAMP

Optional continuation lines for extrusion constraint definition:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

EXTR ETYP

EPATH1 EP1_ID1 EP1_ID2 EP1_ID3 EP1_ID4 EP1_ID5 EP1_ID6 EP1_ID7

EP1_ID8 … … … … … …

… …

EPATH2 EP2_ID1 EP2_ID2 EP2_ID3 EP2_ID4 EP2_ID5 EP2_ID6 EP2_ID7

EP2_ID8 … … … … … …

… …

Optional continuation lines for "Master" definition for pattern repetition constraint:

936 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MASTER

C OORD C ID C AID/ YC A ZC A C FID/ YC F ZC F


XC A XC F

C SID/ YC S ZC S C TID/ YC T ZC T
XC S XC T

Optional continuation lines for "Slave" definition for pattern repetition constraint:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SLAVE DTPL_ID SX SY SZ

C OORD C ID C AID/ YC A ZC A C FID/ YC F ZC F


XC A XC F

C SID/ YC S ZC S C TID/ YC T ZC T
XC S XC T

Optional continuation lines for pattern grouping constraint definition:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PATRN TYP AID/XA YA ZA FID/XF YF ZF

UC YC SID/XS YS ZS

Optional continuation lines for material definition if PTYPE=COMP:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT MATOPT

Optional continuation lines for fatigue constraint definition:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FATIGUE FTYPE FBOUND

Altair Engineering OptiStruct 13.0 Reference Guide 937

Proprietary Information of Altair Engineering


Optional continuation lines for Level Set Method (Topology Optimization) activation:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

LEVELSE HOLEIN HOLERA NHOLES NHOLES NHOLES


T ST D X Y Z

Example 1

Define a topology design variable that allows the thickness of components referencing the
PSHELL properties 7, 8, and 17 to vary between 1.0 and 5.0 (the thickness defined on
PSHELL definitions with PID 7, 8, and 17 is 5.0). The optimized design should contain
members whose width is no less than 60.0 units.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DTPL 1 PSHELL 7 8 17

MEMBSIZ 60.0

TMIN 1.0

Example 2

Define a topology design variable for components referencing the PSOLID properties 4, 5,
and 6. The optimized design should contain members whose diameter is no less than 60.0
units. The final design will be manufactured using a casting process, where the draw
direction lies along the x-axis. The components referencing PSOLID properties 10, 11, and
12 are non-designable, but will form part of the same casting as the designable
components.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DTPL 1 PSOLID 4 5 6

MEMBSIZ 60.0

DRAW SPLIT 0.0 0.0 0.0 1.0 0.0 0.0

938 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


OBST 10 11 12

Field Contents

ID Each DTPL card must have a unique ID.

No default (Integer > 0)

PTYPE Property type for which DTPL card is defined, PBAR, PBARL,
PBEAM, PBEAML, PBUSH, PROD, PWELD, PSHELL, PCOMP, or
PSOLID.

No default (PBAR, PBARL, PBEAM, PBEAML, PBUSH, PROD,


PWELD, PSHELL, PCOMP, or PSOLID)

PID# Property identification numbers. List of properties of type


PTYPE for which this DTPL card is defined. Use ALL in PID1
field, if it applies to all properties of type PTYPE in the
model.

If no PIDs are listed, OptiStruct will check all properties of


type PTYPE to see if they are to be included in the design
space (see help section for PCOMP, PSHELL, and PSOLID).
If any properties satisfy this search, then they will be
affected by entries on this card. In this situation (where no
PIDs are defined), only one DTPL card can be defined for the
given PTYPE.

Default = blank (Integer > 0, blank or ALL)

TMIN TMIN flag indicating that minimum thickness value will follow.
Only valid when PTYPE = PSHELL.

If not present when PTYPE = PSHELL, then minimum


thickness will default to the T0 value defined on the PSHELL
card. If no T0 value is defined on the PSHELL card, the
minimum thickness will default to 0.0.

T0 Minimum thickness for PSHELL properties when the


referenced material is of type MAT1.

If PSHELL references a material which is not of type MAT1,


this value is ignored and T0 = 0.0 is used.

If no value is entered for T0, the T0 value on the PSHELL


card is used. If T0 is not defined on the PSHELL card, then
T0=0.0 is assumed.

Default = blank (Real > 0.0)

Altair Engineering OptiStruct 13.0 Reference Guide 939

Proprietary Information of Altair Engineering


Field Contents

STRESS STRESS flag indicating that stress constraints are active


and that an upper bound value for stress is to follow. See
comment 1.

UBOUND Upper bound constraint on stress.

No default (Real > 0.0)

MEMBSIZ MEMBSIZ flag indicating that member size control is active


for the properties listed. Indicates that MINDIM and possibly
MAXDIM are to follow.

MINDIM Specifies the minimum diameter of members formed. This


command is used to eliminate small members. It also
eliminates checkerboard results. See comment 2.

Default = No Minimum Member Size Control (Real > 0.0)

MAXDIM Specifies the maximum diameter of members formed. This


command is used to prevent the formation of large members.
It can only be used in combination with MINDIM. See
comment 3.

Default = No Maximum Member Size Control (Real > 0.0)

MINGAP Defines the minimum spacing between structural members


formed. This command can only be used in conjunction with
MAXDIM. See comment 3.

Default = blank (Real > MAXDIM)

MESH MESH flag indicating that mesh type information is to follow.

MTYP Indicates that the mesh conforms to certain rules for which
the optimizer is tuned. Currently, only the ALIGN option is
available. ALIGN indicates that when manufacturing
constraints are active, the mesh is aligned with the draw
direction or extrusion path. See comment 4.

Default = blank (ALIGN or blank)

DRAW DRAW flag indicating that casting constraints are being


applied. Indicates that draw direction information is to
follow.

Only valid for PTYPE = PSOLID. OptiStruct will terminate


with an error if present for other PTYPEs.

940 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

DTYP Type of draw direction constraint to be used. Can choose


between SINGLE, SPLIT, SPLIT2, or SPLIT3.

SINGLE indicates that a single die will be used, the die being
withdrawn in the given draw direction.

SPLIT allows the optimization of the splitting surface of two


dies, with both dies moving apart in the given draw
direction.

SPLIT2 and SPLIT3 provide alternative methods to optimize


the splitting surface. These should only be used in the case
where SPLIT creates non-castable cavities.

Default = SPLIT (SINGLE, SPLIT, SPLIT2, or SPLIT3)

DAID/XDA, YDA, ZDA Draw direction anchor point. These fields define the anchor
point for draw direction of the casting. The point may be
defined by entering a grid ID in the DAID field or by entering
X, Y, and Z coordinates in the XDA, YDA, and ZDA fields,
these coordinates will be in the basic coordinate system.

Default = origin (Real in all three fields or Integer in first


field)

DFID/XDF, YDF, ZDF Direction of vector for draw direction definition. These fields
define a point. The vector goes from the anchor point to
this point. The point may be defined by entering a grid ID in
the DFID field or by entering X, Y, and Z coordinates in the
XDF, YDF, and ZDF fields, these coordinates will be in the
basic coordinate system.

No default (Real in all three fields or Integer in first field)

OBST OBST flag indicating that a list of PIDs will follow which are
non-designable, but their interaction with designable parts
needs to be considered with regard to the defined draw
direction. OBST stands for obstacle.

Only recognized if DRAW flag is also present on same DTPL


card. OptiStruct will terminate with an error if OBST flag is
present without DRAW flag.

OPID# Obstacle property identification number. List of non-


designable properties that are to be considered with regard
to the defined draw direction. These must be PSOLID.

No default (Integer > 0, blank or ALL)

Altair Engineering OptiStruct 13.0 Reference Guide 941

Proprietary Information of Altair Engineering


Field Contents

NOHOLE Prevents the formation of through-holes in the draw


direction. Note that it does not prevent holes perpendicular
to the draw direction. The assumed minimum thickness in
the draw direction is twice the average mesh size.

STAMP STAMP flag forcing the design to evolve into a 3D shell


structure. Indicates that thickness, TSTAMP, is to follow.
See comment 5.

TSTAMP Defines the thickness of the 3D shell structure that is


evolved with the STAMP option. The recommended minimum
thickness is three times the average mesh size. See
comment 5.

No default (Real > 0.0)

EXTR EXTR flag indicating that extrusion constraints are being


applied. Indicates that extrusion information is to follow.

Only valid for PTYPE = PSOLID. OptiStruct will terminate


with an error if present for other PTYPEs.

ETYP Type of extrusion constraint to be used. Can choose


between NOTWIST or TWIST.

NOTWIST indicates that the cross-section cannot twist


about the neutral axis, in which case only one path needs to
be defined.

TWIST indicates that the cross-section can twist about the


neutral axis, in which case two paths need to be defined.

Default = NOTWIST (NOTWIST or TWIST)

EPATH1 EPATH1 flag indicating that a list of grid IDs will follow to
define the primary extrusion path.

Only recognized if EXTR flag is also present on same DTPL


card. OptiStruct will terminate with an error if EPATH1 flag
is present without EXTR flag.

EP1_ID# Primary extrusion path identification numbers. List of grid


IDs that define the primary extrusion path.

No default (Integer > 0 or blank)

942 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

EPATH2 EPATH2 flag indicating that a list of grid IDs will follow to
define the secondary extrusion path. This is only required
when ETYP has been set to TWIST.

Only recognized if EXTR flag is also present on same DTPL


card. OptiStruct will terminate with an error if EPATH2 flag
is present without EXTR flag.

EP2_ID# Secondary extrusion path identification numbers. List of grid


IDs that define the secondary extrusion path.

No default (Integer > 0 or blank)

MASTER MASTER flag indicating that this design variable may be used
as a master pattern for pattern repetition. See comment 7.

COORD COORD flag indicating information regarding the coordinate


system for pattern repetition is to follow. This is required if
either MASTER or SLAVE flags are present.

CID Coordinate system ID for a rectangular coordinate system


that may be used as the pattern repetition coordinate
system. See comment 7.

Default = 0 (Integer > 0)

CAID/XCA, YCA, ZCA Anchor point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CAID field
or by entering X, Y, and Z coordinates in the XCA, YCA, and
ZCA fields. These coordinates will be in the basic coordinate
system. See comment 7.

No default (Real in all three fields or Integer in first field)

CFID/XCF, YCF, ZCF First point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CFID field
or by entering X, Y, and Z coordinates in the XCF, YCF, and
ZCF fields. These coordinates will be in the basic coordinate
system. See comment 7.

No default (Real in all three fields or Integer in first field)

CSID/XCS, YCS, ZCS Second point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CSID field

Altair Engineering OptiStruct 13.0 Reference Guide 943

Proprietary Information of Altair Engineering


Field Contents

or by entering X, Y, and Z coordinates in the XCS, YCS, and


ZCS fields. These coordinates will be in the basic coordinate
system. See comment 7.

No default (Real in all three fields or Integer in first field)

CTID/XCT, YCT, ZCT Third point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CTID field
or by entering X, Y, and Z coordinates in the XCT, YCT, and
ZCT fields. These coordinates will be in the basic coordinate
system. See comment 7.

No default (Real in all three fields or Integer in first field)

SLAVE SLAVE flag indicating that this design variable is slaved to


the master pattern definition referenced by the following
DTPL_ID entry. See comment 7.

DTPL_ID DTPL identification number for a master pattern definition.

No default (Integer > 0)

SX, SY, SZ Scale factors for pattern repetition in X, Y, and Z directions


respectively. See comment 7.

Default = 1.0 (Real > 0.0)

COORD COORD flag indicating information regarding the coordinate


system for pattern repetition is to follow. This is required if
either MASTER or SLAVE flags are present.

CID Coordinate system ID for a rectangular coordinate system


that may be used as the pattern repetition coordinate
system. See comment 7.

Default = 0 (Integer > 0)

CAID/XCA, YCA, ZCA Anchor point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CAID field
or by entering X, Y, and Z coordinates in the XCA, YCA, and
ZCA fields. These coordinates will be in the basic coordinate
system. See comment 7.

No default (Real in all three fields or Integer in first field)

CFID/XCF, YCF, ZCF First point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CFID field
or by entering X, Y, and Z coordinates in the XCF, YCF, and

944 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

ZCF fields. These coordinates will be in the basic coordinate


system. See comment 7.

No default (Real in all three fields or Integer in first field)

CSID/XCS, YCS, ZCS Second point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CSID field
or by entering X, Y, and Z coordinates in the XCS, YCS, and
ZCS fields. These coordinates will be in the basic coordinate
system. See comment 7.

No default (Real in all three fields or Integer in first field)

CTID/XCT, YCT, ZCT Third point for pattern repetition coordinate system. The
point may be defined by entering a grid ID in the CTID field
or by entering X, Y, and Z coordinates in the XCT, YCT, and
ZCT fields. These coordinates will be in the basic coordinate
system. See comment 7.

No default (Real in all three fields or Integer in first field)

PATRN PATRN flag indicating that pattern grouping is active for the
properties listed. Indicates that information for pattern
grouping is to follow.

Only valid for PTYPE = PCOMP, PSHELL, and PSOLID.


OptiStruct will terminate with an error if present for other
PTYPEs.

TYP Indicates the type of pattern grouping requested. See


comment 10.

Default = No Pattern Grouping (1, 2, 3, 9, 10, or 11)

AID/XA, YA, ZA Anchor point for pattern grouping. The point may be defined
by entering a grid ID in the AID field or by entering X, Y, and
Z coordinates in the XA, YA, and ZA fields. These
coordinates will be in the basic coordinate system. See
comment 10.

Default = origin (Real in all three fields or Integer in first


field)

FID/XF, YF, ZF First point for pattern grouping. The point may be defined
by entering a grid ID in the FID field or by entering X, Y, and
Z coordinates in the XF, YF, and ZF fields. These
coordinates will be in the basic coordinate system. See
comment 10.

Altair Engineering OptiStruct 13.0 Reference Guide 945

Proprietary Information of Altair Engineering


Field Contents

No default (Real in all three fields or Integer in first field)

UCYC Number of cyclical repetitions for cyclical symmetry. This


field defines the number of radial "wedges" for cyclical
symmetry. The angle of each wedge is computed as 360.0 /
UCYC. See comment 10.

Default = blank (Integer > 0 or blank)

SID/XS, YS, ZS Second point for pattern grouping. The point may be
defined by entering a grid ID in the SID field or by entering
X, Y, and Z coordinates in the XS, YS, and ZS fields. These
coordinates will be in the basic coordinate system. See
comment 10.

No default (Real in all three fields or Integer in first field)

MAT Indicates the type of composite topology optimization. Only


considered for PTYPE=PCOMP.

MATOPT PLY: Indicates that the optimization should be performed at


the ply level. Topology design variables are applied to each
ply individually. This method allows the optimization process
to determine which orientation is preferred for each
element.

HOMO: Indicates that the optimization should be performed


on the homogenized shell. This is the method which was
used in previous versions of OptiStruct.

Default = PLY

FATIGUE FATIGUE flag indicating that fatigue constraints are active


and their definitions are to follow.

FTYPE Specifies the type of fatigue constraint; it can be DAMAGE,


LIFE or FOS.

FBOUND Specifies the bound value. If FTYPE is DAMAGE, FBOUND will


be the upper bound of fatigue damage. If FTYPE is LIFE or
FOS, FBOUND will be the lower bound of fatigue life (LIFE) or
Factor of Safety (FOS), respectively.

No default (Real)

LEVELSET LEVELSET flag indicating that the Level Set method (for
topology optimization) is activated and the definitions of the
required parameters follow.

946 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

HOLEINST Defines the method used to insert holes into the design.

NONE/ADAPT/ALIGN/TOPDER

DEFAULT = ADAPT

NONE: Indicates that there are no holes in the initial design,


and it will work similar to shape optimization.

ADAPT: Indicates that the optimization will start with a


cheese-like initial design, where the holes are adaptively
inserted into the design domain, as illustrated in Figure 2.
This works well with irregular design domains.

ALIGN: Indicates that the optimization will start with evenly


distributed holes aligned with axes X and Y (and Z for 3D) of
the basic coordinate system, as illustrated in Figure 3. This
option is specially developed for regular design domains.

TOPDER: Indicates that OptiStruct will automatically identify


locations for the insertion of holes during the optimization
process.

If the HOLEINST Field is blank, it is set to ADAPT by default

HOLERAD <REAL NUMBER>

DEFAULT = 4 times the average mesh size

A real number that specifies the initial radius of the holes.

If the field HOLERAD is blank, the radius will be set to 4


times the average mesh size.

NHOLESX / NHOLESY / <POSITIVE INTEGER>


NHOLESZ
A positive integer that specifies the number of holes in X
direction (when HOLEINST= ALIGN).

If the field NHOLESX is blank, OptiStruct will automatically


assign a number based on HOLERAD and the dimensions of
the domain.

NHOLESY and NHOLESZ can be inferred by analogy.

Comments

1. Von Mises stress constraints may be defined for topology and free-size optimization
through the STRESS optional continuation line on the DTPL or the DSIZE card. There are
a number of restrictions with this constraint:

The definition of stress constraints is limited to a single von Mises permissible stress.
The phenomenon of singular topology is pronounced when different materials with

Altair Engineering OptiStruct 13.0 Reference Guide 947

Proprietary Information of Altair Engineering


different permissible stresses exist in a structure. Singular topology refers to the
problem associated with the conditional nature of stress constraints, that is, the stress
constraint of an element disappears when the element vanishes. This creates another
problem in that a huge number of reduced problems exist with solutions that cannot
usually be found by a gradient-based optimizer in the full design space.
Stress constraints for a partial domain of the structure are not allowed because they
often create an ill-posed optimization problem since elimination of the partial domain
would remove all stress constraints. Consequently, the stress constraint applies to the
entire model when active, including both design and non-design regions, and stress
constraint settings must be identical for all DSIZE and DTPL cards.
The capability has built-in intelligence to filter out artificial stress concentrations
around point loads and point boundary conditions. Stress concentrations due to
boundary geometry are also filtered to some extent as they can be improved more
effectively with local shape optimization.
Due to the large number of elements with active stress constraints, no element stress
report is given in the table of retained constraints in the .out file. The iterative
history of the stress state of the model can be viewed in HyperView or HyperMesh.
Stress constraints do not apply to 1D elements.
Stress constraints may not be used when enforced displacements are present in the
model.
2. It is recommended that a MINDIM value be chosen such that it is at least 3 times, and no
greater than 12 times, the average element size. When pattern grouping, draw direction,
or extrusion constraints are active, a MINDIM value of 3 times the average element size is
enforced, and user-defined values (which are smaller than this value) will be replaced by
this value. However, in cases where a MINDIM greater than 12 times the average
element size is defined, irrespective of whether or not other manufacturing constraints
are defined, the value is reset to be equal to 12 times the average element size.

If MINDIM is defined, but no other manufacturing constraint exists, MINDIM will not be
reset to the recommended lower bound value for PTYPE = PSHELL or PSOLID, if the
defined value is less than the recommended value. For PTYPE = PCOMP, MINDIM will be
reset in the absence of manufacturing constraints.

3. MAXDIM should at least be twice the value of MINDIM. If the input value of MAXDIM is
too small, OptiStruct automatically resets the value and an INFORMATION message is
printed.

The MAXDIM constraint introduces significant restriction to the design problem.


Therefore, it should only be used when it is a necessary design requirement. A study
without MAXDIM should always be carried out in order to compare the impact of this
additional constraint.

MAXDIM implies the application of a MINGAP constraint of the same value as MAXDIM, as
well. Therefore, for MINGAP to be effective, it should be greater than MAXDIM.

It is important to pay attention to volume fraction as the achievable volume is below 50%
when MAXDIM is defined, and further decreases as MINGAP increases.

4. MTYP "ALIGN" may be used in conjunction with draw direction or extrusion manufacturing
constraints to indicate that a mesh is aligned with a draw direction or extrusion path.

948 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Figure 1: Draw direction

Mesh 1 is "aligned" for draw direction 1 in the example shown, but not for draw direction
2.

MTYP "ALIGN" may also be used in conjunction with manufacturing constraints (minimum
member, maximum member, pattern grouping, and pattern repetition) other than draw
direction and extrusion, and Mesh 1 is considered "aligned" for those manufacturing
constraints, too.

In both cases, this will enable OptiStruct to use a smaller minimum member size and
smaller maximum member sizes. The default minimum member size is three times the
average element edge length; with an "aligned" mesh, the default size can be two times
the average element edge length.

Mesh 2 in the example shown is not "aligned" in any case.

5. The stamping constraint is available for only one sheet, which is defined by the
combination of STAMP and DTYP as SINGLE.

It is recommended that the stamping thickness, TSTAMP, be chosen such that it is at


least 3 times the average element size. If TSTAMP is defined less than the minimum
recommended value, TSTAMP will be reset to the minimum recommended value.

STAMP and NOHOLE can be a good combination as this helps to produce a continuous/
spread shell structure.

Note that attention should be paid to the compatibility between thickness and target
volume.

6. Extrusion constraints cannot be combined with draw direction constraints.

Altair Engineering OptiStruct 13.0 Reference Guide 949

Proprietary Information of Altair Engineering


7. Pattern repetition allows similar regions of the design domain to be linked together so as
to produce similar topological layouts. This is facilitated through the definition of "Master"
and "Slave" regions. A DTPL card may only contain one MASTER or SLAVE flag.
Parameters will not be exported for any DTPL cards containing the SLAVE flag. For both
"Master" and "Slave" regions, a pattern repetition coordinate system is required and is
described following the COORD flag. In order to facilitate reflection, the coordinate
system may be a left-handed or right-handed Cartesian system. The coordinate system
may be defined in one of two ways, listed here in order of precedence:

Four points are defined and these are utilized as follows to define the coordinate
system (this is the only way to define a left-handed system):
- A vector from the anchor point to the first point defines the x-axis.
- The second point lies on the x-y plane, indicating the positive sense of the y-axis.
- The third point indicates the positive sense of the z-axis.
A rectangular coordinate system and an anchor point are defined. If only an anchor
point is defined, it is assumed that the basic coordinate system is to be used.
Multiple "Slaves" may reference the same "Master."

Scale factors may be defined for "Slave" regions, allowing the "Master" layout to be
adjusted.

For a more detailed description, refer to the Pattern Repetition page contained within the
User's Guide section Manufacturability for Topology Optimization.

8. Pattern grouping is applicable for PCOMP, PSHELL, and PSOLID components only.

9. For historic reasons, the SYMM flag may be used in place of the PATRN flag.

10. Currently there are six pattern grouping options:

1-plane symmetry (TYP = 1)

This type of pattern grouping requires the anchor point and first point to be defined. A
vector from the anchor point to the first point is normal to the plane of symmetry.

2-plane symmetry (TYP = 2)

This type of pattern grouping requires the anchor point, first point, and second point to
be defined. A vector from the anchor point to the first point is normal to the first plane
of symmetry. The second point is projected normally onto the first plane of symmetry. A
vector from the anchor point to this projected point is normal to the second plane of
symmetry.

3-plane symmetry (TYP = 3)

This type of pattern grouping requires the anchor point, first point, and second point to
be defined. A vector from the anchor point to the first point is normal to the first plane
of symmetry. The second point is projected normally onto the first plane of symmetry. A
vector from the anchor point to this projected point is normal to the second plane of
symmetry. The third plane of symmetry is orthogonal to both the first and second planes
of symmetry, passing through the anchor point.

Uniform (TYP = 9)

This type of pattern grouping does not require any additional input.

950 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Cyclic (TYP = 10)

This type of pattern grouping requires the anchor point, first point, and number of cyclical
repetitions to be defined. A vector from the anchor point to the first point defines the
axis of symmetry.

Cyclic with symmetry (TYP = 11)

This type of pattern grouping requires the anchor point, first point, second point, and
number of cyclical repetitions to be defined. A vector from the anchor point to the first
point defines the axis of symmetry. The anchor point, first point, and second point all lay
on a plane of symmetry. A plane of symmetry lies at the center of each cyclical
repetition.

For a more detailed description, refer to the Pattern Grouping page contained within the
User's Guide section Manufacturability for Topology Optimization.

11. The level set method can merge existing holes but cannot nucleate new holes in the
design domain. Therefore, creating an initial design with holes is necessary, especially for
2D design problems (For 3D design problems, new holes can be “tunneled” when two
surfaces merged).

12. By default, OptiStruct will automatically create a Cheese-Like initial design with holes
adaptively distributed over the design domain, as shown in Figure 2. The default hole
radius is 4.0 times the average mesh size.

Figure 2: A C heese-Like Initial design generated with (left) the default setting, and (right) double hole
radius.

13. Changing the value of HOLERAD can result in different initial designs. Figure 2 (Right)
shows an initial design filled with holes possessing a doubled hole radius when compared
to Figure 2 (Left). If the you wish to create an initial design with evenly distributed and
well aligned holes (this may be preferable for regular design domains), HOLEINST can be
set to ALIGN. The number of holes in each direction can be further specified by using
NHOLESX, NHOLESY and NHOLESZ as shown in Figure 3.

Altair Engineering OptiStruct 13.0 Reference Guide 951

Proprietary Information of Altair Engineering


Figure 3: A C heese-Like initial design with 3-by-5 evenly distributed holes generated using the following
settings: HOLEINST=ALIGN, NHOLESX=5 and NHOLESY=3.

14. Currently, level set supports both SINGLE and SPLIT draw direction constraints. When
multiple DTPL cards are involved, the draw directions need to be the same. The
information needed for draw direction constraint is read from the DTPL cards and thus no
extra settings are required.

15. This card is represented as an optimization design variable in HyperMesh.

952 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DVCREL1

Bulk Data Entry

DVCREL1 – Relates Design Variables to Analysis Model Element Properties

Description

Linearly relates a design variable to an analysis model element property using the equation:

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVC REL1 ID TYPE EID EPNAME/FID C0

DVID1 C OEF1 DVID2 C OEF2 etc.

Field Contents

ID Relationship identification number. ID must be unique with respect to


other DVCREL1 cards.

No default (Integer > 0)

TYPE Element type to be related (See DVCREL - Types)

No default (Character)

EID Element Identification Number.

No default (Integer > 0)

EPNAME/FID Element property name, such as "K" or “ZOFFS" (as in the documentation
of the element bulk data entries), or field number on an element bulk
data entry.

No default (Character or Integer > 0)

C0 Constant in relationship equation.

Altair Engineering OptiStruct 13.0 Reference Guide 953

Proprietary Information of Altair Engineering


Field Contents

Default = 0.0 (Real)

DVIDi DESVAR ID.

No default (Integer > 0)

COEFi Coefficient in relationship equation.

Default = 1.0 (Real)

Comments

1. This card is represented as an optimization design variable property relationship in


HyperMesh.

954 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DVCREL2

Bulk Data Entry

DVCREL2 – Relates Design Variables to Analysis Model Element Properties via Relationship
Defined by User-supplied Equation

Description

Relates design variables to an analysis model element property using a relationship defined by
a DEQATN card. The equation inputs come from the referenced DESVAR values and constants
defined on a DTABLE card.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVC REL2 ID TYPE EID EPNAME/ EQID


FID

DESVAR DVID1 DVID2 DVID3 DVID4 DVID5 DVID6 DVID7

DVID8 DVID9 etc.

DTABLE LABL1 LABL2 LABL3 LABL4 LABL5 LABL6 LABL7

LABL8 etc.

Field Contents

ID Relationship identification number. ID must be unique with respect to


other DVCREL2 cards.

No default (Integer > 0)

TYPE Element type to be related (See DVCREL - Types)

No default (Character)

EID Element Identification Number.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 955

Proprietary Information of Altair Engineering


Field Contents

EPNAME/FID Element property name, such as "K" or “ZOFFS" (as in the documentation
of the element bulk data entries), or field number on an element bulk
data entry.

No default (Character or Integer > 0)

EQID Equation ID of DEQATN data.

No default (Integer > 0)

DESVAR DESVAR flag indicating DESVAR ID numbers follow.

DVID# DESVAR ID.

No default (Integer > 0)

DTABLE DTABLE flag indicating DTABLE labels follow.

LABL# Constant label. Must match with a constant label of a DTABLE entry.

No default (Character)

Comments

1. This card is represented as an optimization design variable property relationship in


HyperMesh.

956 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DVCREL - Types

Types

Depending on the TYPE entry, the FID of the appropriate design parameter can be determined
from the table below.

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

CONM1 M11 M21 M22 M31 M32

FID 11-20 M33 M41 M42 M43 M44 M51 M52 M53

FID 21-30 M54 M55 M61 M62 M63 M64 M65 M66

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

CONM2 M X1 X2 X3

FID 11- I11 I21 I22 I31 I32 I33


20

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

CMASS2 M

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

CMASS4 M

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

CDAMP2 B

Altair Engineering OptiStruct 13.0 Reference Guide 957

Proprietary Information of Altair Engineering


Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

CDAMP4 B

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

CBAR X1 X2 X3

FID 11- W1A W2A W3A W1B W2B W3B


20

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

CBEAM X1 X2 X3

FID 11- W1A W2A W3A W1B W2B W3B


20

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

CONROD A J C NSM

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

CELAS2 K GE S

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

CELAS4 K GE S

958 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

CTRIA3 ZOFFS

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

CTRIA6

FID 11-20 ZOFFS

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

CQUAD4 ZOFFS

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

CQUAD8

FID 11-20 ZOFFS

Altair Engineering OptiStruct 13.0 Reference Guide 959

Proprietary Information of Altair Engineering


DVGRID

Bulk Data Entry

DVGRID – Relationship between Design Variable and Grid Point Location

Description

Defines the relationship between a design variable and a grid point location.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVGRID DVID GID C ID C OEFF X Y Z

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVGRID 1 1032 0 1.0 1.0 0.0 0.0

Field Contents

DVID DESVAR identification number.

(Integer > 0)

GID GRID identification number.

(Integer > 0)

CID Coordinate system identification number.

Default = 0 (Integer > 0)

COEFF Multiplier to the vector defined in fields 6, 7, and 8.

X, Y, Z Components of the vector defining the perturbation of the grid in the


coordinate system defined by CID.

960 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. A CID of zero or blank references the basic coordinate system.

2. Multiple references to the same grid ID will yield a summation of perturbation vectors for
the given grid.

3. The DVGRID data defines perturbations in the locations of the grids. The updated
location of the grid is:

where, DVj is the value of design variable j and [N]T is the coordinate transformation
matrix based on the CID and the GRID location.

4. This card is represented as an optimization design variable in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 961

Proprietary Information of Altair Engineering


DVMBRL1

Bulk Data Entry

DVMBRL1 – Relates Design Variables to Properties of MBD Entities

Description

Linearly relates a design variable to properties of an MBD entity using the equation:

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVMBRL1 ID TYPE BID/EID PNAME C0

DVID1 C OEF1 DVID2 C OEF2 etc.

Example 1

To relate the translational x component of stiffness value (K1) on a CMBUSH whose ID is 22


to Design Variable 5.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVMBRL1 88 C MBUSH 22 K1 0.0

5 1.

DESVAR 5 5.00 1.50 9.90

Example 2

To relate the mass of a rigid boy whose ID is 3 to design variable 5.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

962 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DVMBRL1 88 PRBODY 3 M 0.0

5 1.

DESVAR 5 5.00 1.50 9.90

Field Contents

ID Response identity. ID must be unique with respect to other DVMBRL1 and


DVMBRL2 cards.

No default (Integer > 0)

TYPE MBD entity type to be related (see table below).

No default (Character)

BID/EID Body ID or Element ID number. When TYPE is PRBODY, this field is the ID
number of a rigid body. When TYPE is CMBUSH(M), CMBEAM(M), or
CMSPDP(m), this field is the ID number of a corresponding element.

No default (Integer > 0)

PNAME Property name, such as "A" or "L" (as in the documentation of the
PRBODY, CMBEAM(M), CMBUSH(M), and CMSPDP(M) cards).

No default (Character or Integer > 0)

C0 Constant in relationship equation.

Default = 0.0 (Real)

DVIDi DESVAR ID.

No default (Integer > 0)

COEFi Coefficient in relationship equation.

Default = 1.0 (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 963

Proprietary Information of Altair Engineering


Comments

1. Available TYPEs are PRBODY, CMBUSH, CMBUSHM, CMBEAM, CMBEAMM, CMSPDP, and
CMSPDPM.

2. MBD entity type information:

TYPE Available PNAME

PRBODY IXX

IYY

IZZ

IXY

IXZ

IYZ

X X component of center of gravity.

Y Y component of center of gravity.

Z Z component of center of gravity.

CMBEAM/CMBEAMM L Undeformed length along the X–axis of


the beam.

A Area of the beam cross-section.

I1 Area moment of inertia in plane 1


about the neutral axis.

I2 Area moment of inertia in plane 1


about the neutral axis.

J Torsional constant.

K1 ~ K2 Area factor for shear.

CMBUSH/CMBUSHM K1 ~ K3 Translational stiffness.

964 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


TYPE Available PNAME

K4 ~ K6 Rotational stiffness.

B1 ~ B3 Translational damping.

B4 ~ B6 Rotational damping.

P1 ~ P3 Translational preload.

P4 ~ P6 Rotational preload.

CMSPDP/CMSPDPM K Stiffness

B Damping

L Unstretched length of spring damper.

PF Preload force.

3. This card is represented as an optimization design variable property relationship in


HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 965

Proprietary Information of Altair Engineering


DVMBRL2

Bulk Data Entry

DVMBREL2 – Relates Design Variables to Properties of MBD Entities via Relationship Defined
by User-supplied Equation

Description

Relates a design variable to properties of MBD entities using a relationship defined by a


DEQATN card. The equation inputs come from the referenced DESVAR values and the
constants defined on the DTABLE card.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVMBRL2 ID PTYPE BID/EID PNAME EQID

DESVAR DVID1 DVID2 DVID3 DVID4 DVID5 DVID6 DVID7

DVID8 DVID9 etc.

DTABLE LABL1 LABL2 LABL3 LABL4 LABL5 LABL6 LABL7

LABL8 etc.

Field Contents

ID Relationship identity. ID must be unique with respect to other DVMBRL1 and


DVMBRL2 cards.

No default (Integer > 0)

TYPE Property type to be related (see table below).

No default (Character)

BID/EID Body ID or Element ID number. When TYPE is PRBODY, this field is ID


number of a rigid body. When TYPE is CMBUSH(M), CMBEAM(M), or
CMSPDP(m), this field is ID number of a corresponding element.

No default (Integer > 0)

966 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

PNAME Property name, such as "A" or "L" (as in the documentation of the PRBODY,
CMBEAM(M), CMBUSH(M), and CMSPDP(M) cards).

No default (Character or Integer > 0)

EQID Equation ID of DEQATN data.

No default (Integer > 0)

DESVAR DESVAR flag indicating DESVAR ID numbers follow.

DVIDi DESVAR ID.

No default (Integer > 0)

DTABLE DTABLE flag indicating DTABLE labels follow.

LABLi Constant label on DTABLE card.

No default (Character)

Comments

1. Available TYPE are PRBODY, CMBUSH, CMBUSHM, CMBEAM, CMBEAMM, CMSPDP, and
CMSPDPM.

2. Property type table:

TYPE Available PNAME

PRBODY IXX

IYY

IZZ

IXY

IXZ

IYZ

Altair Engineering OptiStruct 13.0 Reference Guide 967

Proprietary Information of Altair Engineering


TYPE Available PNAME

X X component of center of gravity.

Y Y component of center of gravity.

Z Z component of center of gravity.

CMBEAM/CMBEAMM L Undeformed length along the X–axis of


the beam.

A Area of the beam cross-section.

I1 Area moment of inertia in plane 1


about the neutral axis.

I2 Area moment of inertia in plane 1


about the neutral axis.

J Torsional constant.

K1 ~ K2 Area factor for shear.

CMBUSH/CMBUSHM K1 ~ K3 Translational stiffness.

K4 ~ K6 Rotational stiffness.

B1 ~ B3 Translational damping.

B4 ~ B6 Rotational damping.

P1 ~ P3 Translational preload.

P4 ~ P6 Rotational preload.

CMSPDP/CMSPDPM K Stiffness

B Damping

L Unstretched length of spring damper.

968 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


TYPE Available PNAME

PF Preload force

3. This card is represented as an optimization design variable property relationship in


HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 969

Proprietary Information of Altair Engineering


DVMREL1

Bulk Data Entry

DVMREL1 – Relates Design Variables to Analysis Model Material Properties

Description

Linearly relates a design variable to an analysis model material property using the equation:

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVMREL1 ID TYPE MID MPNAME/ C0


FID

DVID1 C OEF1 DVID2 C OEF2 etc.

Example 1

To relate the Damping Coefficient value on a MAT1 card (field 9) to Design Variable 5.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVMREL 17 MAT1 22 9 0.0


1

5 1.0

Example 2

This example is the same as example 1 (above), except that it defines MPNAME in place of
FID.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVMREL 17 MAT1 22 GE 0.0

970 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

5 1.0

Associated Cards

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DESVAR 5 GE 1.0 2.0 0.5

MAT1 22 2.1e5 0.3 7.85e-9 1.0

Field Contents

ID Relationship identification number. ID must be unique with respect to


other DVMREL1 cards.

No default (Integer > 0)

TYPE Material type to be related (MAT1, MAT2, MAT4, MAT5, MAT8, and
MAT9).

No default (Character)

MID Material identification number.

No default (Integer > 0)

MPNAME/FID Material property name, such as "E" or “RHO" (as in the documentation of
the material bulk data entries), or field number on a material bulk data
entry.

No default (Character or Integer > 0)

C0 Constant in relationship equation.

Default = 0.0 (Real)

DVIDi DESVAR ID.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 971

Proprietary Information of Altair Engineering


COEFi Coefficient in relationship equation.

Default = 1.0 (Real)

Comments

1. See the DVMREL - Types section for details on the supported material fields and the
MPNAME/FID entries.

972 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DVMREL2

Bulk Data Entry

DVMREL2 – Relates Design Variables to Analysis Model Material Property

Description

Relates design variables to an analysis model material property using a relationship defined by
a DEQATN card. The equation inputs come from the referenced DESVAR values and constants
defined on a DTABLE card.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVMREL2 ID TYPE MID MPNAME/ EQID


FID

DESVAR DVID1 DVID2 DVID3 DVID4 DVID5 DVID6 DVID7

DVID8 DVID9 etc.

DTABLE LABL1 LABL2 LABL3 LABL4 LABL5 LABL6 LABL7

LABL8 etc.

Example 1

To relate the Damping Coefficient value on a MAT1 card (field 9) to some user-defined
relationship of design variables 5 and 6 and the table entry GE0.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVMREL 17 MAT1 22 9 1
2

DESVAR 5 6

DTABLE GE0

Example 2

Altair Engineering OptiStruct 13.0 Reference Guide 973

Proprietary Information of Altair Engineering


This example is the same as example 1 (above), except that it defines MPNAME in place of
FID.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVMREL 17 MAT1 22 GE 1
2

DESVAR 5 6

DTABLE GE0

Associated Cards

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DESVAR 5 GE1 1.0 2.0 0.5

DESVAR 6 GE2 1.0 1.0 0.01

DTABLE GE0 0.01

DEQATN 1 GE(GE1, GE2, GE0) = GE0+(GE1*GE2)

MAT1 22 2.1e5 0.3 7.85e-9 1.0

Field Contents

ID Relationship identification number. ID must be unique with respect to


other DVMREL2 cards.

No default (Integer > 0)

TYPE Material type to be related (MAT1, MAT2, MAT4, MAT5, MAT8, and
MAT9).

No default (Character)

MID Material identification number.

No default (Integer > 0)

974 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

MPNAME/FID Material property name, such as "E" or “RHO" (as in the documentation
of the material bulk data entries), or field number on a material bulk data
entry.

No default (Character or Integer > 0)

EQID Equation ID of DEQATN data.

No default (Integer > 0)

DESVAR DESVAR flag indicating DESVAR ID numbers follow.

DVID# DESVAR ID.

No default (Integer > 0)

DTABLE DTABLE flag indicating DTABLE labels follow.

LABL# Constant label. Must match with a constant label of a DTABLE entry.

No default (Character)

Comments

1. See the DVMREL - Types section for details on the supported material fields and the
MPNAME/FID entries.

Altair Engineering OptiStruct 13.0 Reference Guide 975

Proprietary Information of Altair Engineering


DVMREL - Types

Types

Depending on the TYPE entry, the FID of the appropriate design parameter can be determined
from the table below.

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

MAT1 E G NU RHO A TREF GE

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

MAT2 G11 G12 G13 G22 G23 G33 RHO

FID 11- A1 A2 A12 TREF GE


20

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

MAT4 K RHO H HGEN

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

MAT5 KXX KXY KXZ KYY KYZ KZZ

FID 11-20 RHO HGEN

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

MAT8 E1 E2 NU12 G12 G1,Z G2,Z RHO

FID 11- A1 A2 TREF


20

FID 21- GE

976 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


30

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

MAT9 G11 G12 G13 G14 G15 G16 G22

FID 11-20 G23 G24 G25 G26 G33 G34 G35 G36

FID 21-30 G44 G45 G46 G55 G56 G66 RHO A1

FID 31-40 A2 A3 A4 A5 A6 TREF GE

Altair Engineering OptiStruct 13.0 Reference Guide 977

Proprietary Information of Altair Engineering


DVPREL1

Bulk Data Entry

DVPREL1 – Relates Design Variables to Analysis Model Properties

Description

Linearly relates a design variable to an analysis model property using the equation:

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVPREL1 ID TYPE PID PNAME/ C0


FID

DVID1 C OEF1 DVID2 C OEF2 etc.

Example 1

To relate the thickness value on a PSHELL card (field 4) to Design Variable 5.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVPREL1 88 PSHELL 1 4 0.0

5 1.

DESVAR 5 5.00 1.50 9.90

Example 2

This example is the same as example 1 (above), except that it defines PNAME.

978 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVPREL1 88 PSHELL 1 T 0.0

5 1.

DESVAR 5 5.00 1.50 9.90

Field Contents

ID Relationship identification number. ID must be unique with respect to


other DVPREL1 cards.

No default (Integer > 0)

TYPE Property type to be related (see DVPREL - Types).

No default (Character)

PID Property identification number. When PTYPE is PCOMPG, G# may be


used where # is the GPLYID. When PTYPE is PCOMPP, P# may be used
where # is the PLY ID. See comment 2.

No default (Integer > 0)

PNAME/FID Property name, such as "A" or "T" (as in the documentation of the
property cards), or field number in property card (see table below). For
the PSHELL property 12I/T3, only the filed number (6) is allowed. For
PBARL and PBEAML only property names are allowed, as different
sections use different fields.

No default (Character or Integer > 0)

C0 Constant in relationship equation.

Default = 0.0 (Real)

DVIDi DESVAR ID.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 979

Proprietary Information of Altair Engineering


Field Contents

COEFi Coefficient in relationship equation.

Default = 1.0 (Real)

Comments

1. TYPE cannot be PSOLID.

a) The DDVAL field of a DESVAR bulk data entry.

b) The SPTID field of a RSPINR bulk data entry.

2. When TYPE is PCOMPG, either global plies or property specific plies may be selected.

To select property specific plies, the format is similar to that used for other property
types where the property identification number of the PCOMPG is entered in the PID field
and then either PNAME or FID is used to identify the value to be related. In this scenario,
only the property with an ID given in the PID field is affected.

To select global plies, G# is entered in the PID field where, # is the GPLYID of a global
ply. In this instance, FID is not applicable so T or THETA is used in the PNAME field to
relate either the thickness or orientation respectively. In this scenario, all plies that use
the given GPLYID are affected.

When TYPE is PCOMPP, P# is entered in the PID field where # is the ID of a PLY entity.
In this instance, FID is not applicable so T or THETA is used in the PNAME field to relate
either the thickness or orientation respectively.

3. PBEAML definitions with more than one section definition may not be referenced by a
DVPREL1.

4. Properties of PBARL/PBEAML have to be controlled through DIMs (cannot be controlled


directly), with the exception of NSM.

5. When TYPE is PBARL or PBEAML, users should pay close attention to the variable ranges
to avoid invalid dimensions. For example, the inner radius of a tube cross-section cannot
exceed the outer radius. It is necessary to prevent combinations of dimensions from
taking on values that are physically meaningless. Some constraints are applied
automatically on section dimensions. The table below summarizes these constraints.
Constraints are satisfied when they are < 0.0.

Section Type Constraint

TUBE DIM2 – DIM1

I DIM4 – DIM2

DIM4 – DIM3

980 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Section Type Constraint

DIM5 + DIM6 – DIM1

CHAN 2 * DIM4 – DIM2

DIM3 – DIM1

T DIM3 – DIM2

DIM4 – DIM1

BOX DIM4 – DIM1

DIM3 – DIM2

CROSS DIM4 – DIM3

H DIM4 – DIM3

T1 DIM4 – DIM1

I1 DIM3 – DIM4

CHAN1 DIM3 – DIM4

Z DIM3 – DIM4

CHAN2 DIM2 – DIM3

2 • DIM1 – DIM4

T2 DIM4 – DIM1

DIM3 – DIM2

BOX1 DIM4 + DIM3 – DIM2

DIM5 + DIM6 – DIM1

Altair Engineering OptiStruct 13.0 Reference Guide 981

Proprietary Information of Altair Engineering


Section Type Constraint

HEXA 2 * DIM1 – DIM2

HAT 2 * DIM2 – DIM1

2 * DIM2 – DIM3

L DIM3 – DIM2

DIM4 – DIM1

HAT1 DIM3 – DIM1

2 * DIM4 – DIM2

2 * DIM4 + DIM5 – DIM2

6. This card is represented as an optimization design variable in HyperMesh.

982 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DVPREL2

Bulk Data Entry

DVPREL2 – Relates Design Variables to Analysis Model Properties via Relationship Defined by
User-supplied Equation

Description

Relates a design variable to an analysis model property using a relationship defined by a


DEQATN card. The equation inputs come from the referenced DESVAR values and the
constants defined on the DTABLE card.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVPREL2 ID TYPE PID PNAME/ EQID


FID

DESVAR DVID1 DVID2 DVID3 DVID4 DVID5 DVID6 DVID7

DVID8 DVID9 etc.

DTABLE LABL1 LABL2 LABL3 LABL4 LABL5 LABL6 LABL7

LABL8 etc.

Example 1

A rectangular bar of width W and depth D is defined using the PBAR card. The required
fields on the PBAR for Area, I1 and I2 are all related to the width and depth, which are the
design variables, by the referenced equations.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVPREL2 201 PBAR 1 4 101

DESVAR 5 6

DVPREL2 203 PBAR 1 5 102

Altair Engineering OptiStruct 13.0 Reference Guide 983

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DESVAR 5 6

DVPREL2 204 PBAR 1 6 103

DESVAR 5 6

Example 2

This example is the same as example 1 (above), except that it defines PNAME.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DVPREL2 201 PBAR 1 A 101

DESVAR 5 6

DVPREL2 203 PBAR 1 I1 102

DESVAR 5 6

DVPREL2 204 PBAR 1 I2 103

DESVAR 5 6

Associated Cards

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DESVAR 5 W 6.0 1.0 10.0

DESVAR 6 D 5.0 1.0 20.0

DEQATN 101 AREA(W,D) = W*D

DEQATN 102 I1(W,D) = (W*D**3)/12

984 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

DEQATN 103 I2(W,D) = (D*W**3)/12

PBAR 1 222 0.1 19e-4 1e-3

Field Contents

ID Relationship identification number. ID must be unique with respect to other


DVPREL1 cards.

No default (Integer > 0)

TYPE Property type to be related (see DVPREL - Types).

No default (Character)

PID Property identification number. When PTYPE is PCOMPG, G# may be used


where # is the GPLYID. When PTYPE is PCOMPP, P# may be used where #
is the PLY ID. See comment 5.

No default (Integer > 0)

PNAME/ Property name, such as "A" or "T" (as in the documentation of the property
FID cards), or field number in property card (see table below). For the PSHELL
property 12I/T3, only the filed number (6) is allowed. For PBARL and
PBEAML only property names are allowed, as different sections use different
fields.

No default (Character or Integer > 0)

EQID Equation ID of DEQATN data.

No default (Integer > 0)

DESVAR DESVAR flag indicating DESVAR ID numbers follow.

DVIDi DESVAR ID.

No default (Integer > 0)

DTABLE DTABLE flag indicating DTABLE labels follow.

Altair Engineering OptiStruct 13.0 Reference Guide 985

Proprietary Information of Altair Engineering


Field Contents

LABLi Constant label on DTABLE card.

No default (Character)

Comments

1. Type cannot be PSOLID.

2. When Type is PBARL or PBEAML, users should pay close attention to the variable ranges
to avoid invalid dimensions.

3. PBEAML definitions with more than one section definition may not be referenced by a
DVPREL1.

4. Properties of PBARL/PBEAML have to be controlled through DIMs (cannot be controlled


directly), with the exception of NSM.

5. When TYPE is PCOMPG, either global plies or property specific plies may be selected.

To select property specific plies, the format is similar to that used for other property
types where the property identification number of the PCOMPG is entered in the PID field
and then either PNAME or FID is used to identify the value to be related. In this scenario,
only the property with an ID given in the PID field is affected.

To select global plies, G# is entered in the PID field where # is the GPLYID of a global ply.
In this instance, FID is not applicable so T or THETA is used in the PNAME field to relate
either the thickness or orientation respectively. In this scenario, all plies that use the
given GPLYID are affected.

When TYPE is PCOMPP, P# is entered in the PID field where # is the ID of a PLY entity.
In this instance, FID is not applicable so T or THETA is used in the PNAME field to relate
either the thickness or orientation respectively.

6. This card is represented as an optimization design variable in HyperMesh.

986 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DVPREL - Types

Types

Depending on the TYPE entry, the FID of the appropriate design parameter can be determined
from the table below.

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

CONM2 M X1 X2 X3

FID 11-20 I11 I12 I22 I13 I23 I33

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

PBAR A I1 I2 J NSM

FID 11-20 C1 C2 D1 D2 E1 E2 F1 F2

FID 21-30 K1 K2 I12

Type Field numbers are not allowed for PBARL.

PBARL DIMi NSM

Type Field Field Field Field Field Field Field Field Field Field
1 2 3 4 5 6 7 8 9 10

PBEAM A(A) I1(A) I2(A) I12(A) J(A) NSM(A)

FID 11-20 C 1(A) C 2(A) D1(A) D2(A) E1(A) E2(A) F1(A) F2(A)

FID 21-30

FID 31-40 K1(A) K2(A) NSI(A) NSI(B)

Altair Engineering OptiStruct 13.0 Reference Guide 987

Proprietary Information of Altair Engineering


FID 41-50 M1(A) M2(A) M1(B) M2(B) N1(A) N2(A) N1(B) N2(B)

Type Field numbers are not allowed for PBEAML.

PBEAML DIMi NSM

Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6

PBUSH K1 K2 K3 K4 K5 K6

B1 B2 B3 B4 B5 B6

GE1 GE2 GE3 GE4 GE5 GE6

Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6

PCOMP Z0 NSM

FID 11-20 T1 THETA1 T2 THETA4

FID 21-30 T3 THETA3 … …

… … … … …

Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6

PCOMPG Z0 NSM

FID 11-20 T1 THETA1

988 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


FID 21-20 T2 THETA2

… … …

Type Field numbers do not apply for PCOMPG when referencing global plies. See
comment 2 (DVPREL1).

PCOMPG T THETA

Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6

PCOMPP Z0 NSM

Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6

PDAMP B B B B

Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6

PELAS K S K S

Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6

PMASS M M M M

Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10

Altair Engineering OptiStruct 13.0 Reference Guide 989

Proprietary Information of Altair Engineering


6

PROD A NSM

Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6

PSHELL T 12* TS/T NSM


I/T3

FID 11-20 Z1 Z2 ZOF


FS

Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6

PSHEAR T NSM F1 F2

Type Field Field Field Field Field Fiel Field Field Field Field
1 2 3 4 5 d 7 8 9 10
6

PVISC CE CR CE CR

990 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


EDGEBH

Bulk Data Entry

EDGEBH – Edge Blank Holder Definition for One-Step Stamping Simulation

Description

Defines geometry and restraining force per unit length for an edge blank holder in a one-step
stamping simulation.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

EDGEBH EID S1 T2 S2 T2 BFORC E BSID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

EDGEBH 6 -1.0 1.0 1.0 1.0 100.0 5

Field Contents

EID Element identification number.

No default (Integer > 0)

S1, T1 Parametric entry points for the line.

No default (Real; | S1, T1 | < 1.0)

S2, T2 Parametric exit points for the line.

No default (Real; | S2, T2 | < 1.0)

BFORCE Blank holder restraining force.

No default (Real)

BSID Blank holder set identifier for retrieving the input file back to HyperForm.
Not used by the solver.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 991

Proprietary Information of Altair Engineering


Comments

1. This entry is only valid with an @HyperForm statement in the first line of the input file.

992 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


EDRAWB

Bulk Data Entry

EDRAWB – Draw Bead Definition for One-Step Stamping Simulation

Description

Defines location and restraining force per unit length for a draw bead in a one-step stamping
simulation.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

EDRAWB EID S1 T2 S2 T2 DFORC E DSID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

EDRAW 13 -1.0 1.0 1.0 -1.0 100.0 2


B

Field Contents

EID Element identification number.

No default (Integer > 0)

S1, T1 Parametric entry points for the line.

No default (Real; | S1, T1 | < 1.0)

S2, T2 Parametric exit points for the line.

No default (Real; | S2, T2 | < 1.0)

DFORCE Draw bead restraining force per unit length.

No default (Real)

DSID Draw bead set identifier for retrieving the input file back to HyperForm. Not
used by the solver.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 993

Proprietary Information of Altair Engineering


Comments

1. This entry is only valid with an @HyperForm statement in the first line of the input file.

994 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


EIGC

Bulk Data Entry

EIGC – Complex Eigenvalue Extraction Data

Description

Defines data required to perform complex eigenvalue analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

EIGC SID NORM G C ND0

Continuation for EIGC

ALPHAAJ OMEGAAJ ND1

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

EIC G 4 MAX 15

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

EIGC 4 MAX

15

Example 3

Altair Engineering OptiStruct 13.0 Reference Guide 995

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

EIGC 4 MAX

1000.0 1000.0 15

Field Contents

SID Unique set identification number.

No default (Integer > 0)

NORM Indicates the option for normalizing eigenvectors.

MAX - Normalize the component having the largest magnitude to a


unit value for the real part and a zero value for the imaginary part.

POINT - Normalize the component defined in fields 5 and 6 to a unit


value for the real part and a zero value for the imaginary part. The
value for NORM defaults to MAX if the magnitude of the defined
component is zero.

Default = MAX

G Grid or scalar point identification number. Required if and only if NORM


= POINT.

No default (Integer > 0)

C Component number. Required if and only if NORM = POINT and G is a


geometric grid point.

No default (0 < Integer < 6)

ND0 Desired number of roots and eigenvectors to be extracted.

No default (Integer > 0)

ND1 Desired number of roots and eigenvectors to be extracted.

No default (Integer > 0)

ALPHAAJ Real part of the shift point.

Default = 0.0 (Real)

996 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

OMEGAAJ Imaginary part of the shift point.

Default = 0.0 (Real)

Comments

1. ND0 is required if there is no continuation, and it must be empty if there is a continuation


line.

2. ALPHAAJ and OMEGAAJ are only useful for direct complex eigenvalue analysis. If there is
no METHOD command present in the subcase control area, the direct method is
considered for the complex eigenvalue analysis. Otherwise, modal method is used.

3. The 3rd field is reserved for a numerical complex eigensolution (METHOD). Currently, this
field should be left blank;however, certain method types (INV, HESS and CLAN) will be
accepted, but there will be no effect on the analysis.

Altair Engineering OptiStruct 13.0 Reference Guide 997

Proprietary Information of Altair Engineering


EIGRA

Bulk Data Entry

EIGRA – Real Eigenvalue Extraction Data using Automated Multi-Level Sub-structuring

Description

Defines the data required to perform real eigenvalue analysis with the Automated Multi-Level
Sub-structuring technique.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

EIGRA SID V1 V2 ND AMPFFAC T NORM

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

EIGRA 0.1 3.2 10

Field Contents

SID Unique set identification number.

No default (Integer > 0)

V1,V2 Frequency range of interest in cycles per unit time.

V2 must be present.

Default = 0.0 for V1 (V1 < V2, Real, or blank for V1)

ND Number of roots desired. See comment 3.

No default (Integer > 0 or blank)

AMPFFACT Amplification Factor. The substructure modes are solved up to the


frequency of AMPFFACT*V2. Higher values of AMPFFACT will lead to

998 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

more accurate results and longer running times. See comments 6 and
9.

Default = 5.0 (Real or blank)

NORM Method used for eigenvector normalization. If MASS, then eigenvectors


are normalized to the unit value of the generalized mass. If MAX, then
eigenvectors are normalized to the unit value of the largest
displacement in the analysis set.

Default = MASS for normal modes analysis.

Comments

1. The units of V1 and V2 are cycles per unit time.

2. The eigenvectors are normalized with respect to the mass matrix by default.

3. The roots are found in order of increasing magnitude; those closest to zero are found
first. The number and type of roots to be found can be determined from the following
table.

V1 V2 ND Number and Type of Roots Found

V1 V2 ND Lowest ND or all in range, whichever is smaller.

V1 V2 blank All in range.

blank V2 ND Lowest ND roots below V2.

blank V2 blank All below V2.

4. Eigenvalues are sorted in the order of magnitude for output.

5. In vibration analysis, small negative roots are usually computational zeros, indicating rigid
body modes. Finite negative roots are an indication of modeling problems. If V1 is set to
zero explicitly, V1 is ignored.

6. AMPFFACT is used to increase the accuracy of the eigenvalue and eigenvectors at the
expense of slightly longer run times. It is recommended to use higher values of
AMPFFACT, between [5.0, 15.0], for solid structures like engine blocks and suspension
components.

7. EIGRA data can be referenced by multiple normal modes subcases with different MPC set
SID’s in each subcase. However, only one can be used for modal frequency response or
modal transient analysis.

Altair Engineering OptiStruct 13.0 Reference Guide 999

Proprietary Information of Altair Engineering


8. EIGRA data can be referenced by multiple modal dynamic subcases, if the MPC set SID is
the same in each SUBCASE and the set of SPCD DOF is the same in each SUBCASE.
Additionally, multiple eigenvalue analysis subcases can be used with AMSES, however,
only one can be used for modal frequency response or modal transient analysis.

9. If AMPFFACT is not specified by you and the model contains a large number of solid
elements, then the value of AMPFFACT is automatically reset to 10.

10. This card is represented as a loadcollector in HyperMesh.

1000 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


EIGRL

Bulk Data Entry

EIGRL – Real Eigenvalue Extraction Data, Lanczos Method

Description

Defines data required to perform real eigenvalue analysis (vibration or buckling) with the
Lanczos Method.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

EIGRL SID V1 V2 ND MSGLVL MAXSET SHFSC L NORM

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

EIGRL 0.1 3.2 10

Field Contents

SID Unique set identification number.

No default (Integer > 0)

V1,V2 For vibration analysis: Frequency range of interest


For buckling analysis: Eigenvalue range of interest. See comments 3, 4,
and 10.

Default = blank (V1 < V2, Real, or blank)

ND Number of roots desired. See comments 3 and 4.

No default (Integer > 0 or blank)

MSGLVL Diagnostic level.

Altair Engineering OptiStruct 13.0 Reference Guide 1001

Proprietary Information of Altair Engineering


Field Contents

Default = 0 (Integer 0 through 4 or blank)

MAXSET Number of vectors in block or set.

Default = 8 (Integer 1 through 16 or blank)

SHFSCL For vibration analysis: Estimate of the frequency of the first flexible
mode.

For buckling analysis: Estimate of the first eigenvalue. See comment 9.

Default = blank (Real or blank)

NORM Method used for eigenvector normalization. If MASS, then eigenvectors


are normalized to the unit value of the generalized mass (this is not a
valid option for linear buckling analysis). If MAX, then eigenvectors are
normalized to the unit value of the largest displacement in the analysis
set.

Default = MASS for normal modes analysis; Default = MAX for linear
buckling analysis (MASS or MAX)

Comments

1. In vibration analysis, the units of V1 and V2 are cycles per unit time. In buckling analysis,
V1 and V2 are eigenvalues. Each buckling eigenvalue is the factor by which the
prebuckling state of stress is multiplied to produce buckling in the shape defined by the
corresponding eigenvector.

2. In vibration analysis, eigenvectors are normalized with respect to the mass matrix by
default. In buckling analysis, eigenvectors are normalized to have unit value. NORM =
MASS is not a valid option for linear buckling analysis.

3. The roots are found in order of increasing magnitude: that is, those closest to zero are
found first. The number and type of roots to be found can be determined from the
following table. In vibration analysis, blank V1 defaults to -10.

V1 V2 ND Number and Type of Roots Found

V1 V2 ND Lowest ND or all in range, whichever is smaller.

V1 V2 blank All in range

V1 blank ND Lowest ND in range [V1, + ¥]

1002 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


V1 V2 ND Number and Type of Roots Found

V1 blank blank Lowest root in range [V1, + ¥]

blank blank ND Lowest ND roots in [-¥,+¥]

blank blank blank Lowest root.

blank V2 ND Lowest ND roots below V2

blank V2 blank All below V2

4. The Lanczos eigensolver provides two different ways of solving the problem. If the
eigenvalue range is defined with no upper bound (V2 blank) and less than 50 modes (ND <
50), the faster method is applied.

5. Eigenvalues are sorted in the order of magnitude for output. An eigenvector is found for
each eigenvalue.

6. In vibration analysis, small negative roots are usually computational zeros, indicating rigid
body modes. Finite negative roots are an indication of modeling problems. If V1 is set to
zero explicitly, V1 is ignored. It is recommended that V1 not be set to zero when
extracting rigid body modes.

7. MSGLVL controls the amount of diagnostic output during the eigenvalue extraction. The
default value of zero suppresses all diagnostic output. A value of one prints eigenvalues
accepted at each shift. Higher values result in increasing levels of diagnostic output.

8. MAXSET is used to limit the maximum block size in the Lanczos solver. It may be reduced
if there is insufficient memory available. The default value is recommended.

9. A specification of SHFSCL may improve the performance of a vibration analysis. It may


also be used to improve the performance of a buckling analysis, especially when the
applied load differs from the first buckling load by orders of magnitude.

10. AMLS and AMSES eigensolvers require that V2 be specified.

11. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1003

Proprietary Information of Altair Engineering


ELEMQUAL

Bulk Data Entry

ELEMQUAL – Resets the Default Bound Values for Element Quality Check

Description

Resets the default values of the warning and error bound limits for element quality check.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ELEMQUAL ETYPE PTYPE LTYPE V1 V2

Example 1

For CTRIA3 elements, change the upper limit of aspect ratio for error message to 300.0
(default is 500).

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ELEMQUAL TRIA3 ARATIO ERROR 300.0

Example 2

For CTETRA elements, change the bound limits of collapse for warning message to 0.01 and
10.0 (default lower and upper limits are 0.001 and 100.0).

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ELEMQUAL TETRA C OLLAPSE WARNING 0.01 10.

1004 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

ETYPE Element type. Allowable entries are: TRIA3 (CTRIA3), QUAD4 (CQUAD4),
TETRA (1st-order CTETRA), TET10 (2nd-order CTETRA), PENTA (1st-order
CPENTA), PENT15 (2nd-order CPENTA), HEXA (1st-order CHEXA), HEX20
(2nd-order CHEXA), PYRA (1st-order CPYRA), PYRA13 (2nd-order CPYRA),
TAXI3 (1st-order CTAXI or CTRIAX6), TAXI6 (2nd-order CTAXI or
CTRIAX6), GASK8 (CGASK8), GASK16 (CGASK16), GASK6 (CGASK6), and
GASK12 (CGASK12).

No default (TRIA3, QUAD4, TETRA, TET10, PENTA, PENT15, HEXA, HEX20,


PYRA, PYRA13, TAXI3, TAXI6, GASK8, GASK16, GASK6, or GASK12).

PTYPE Geometric property type. Allowable entries are: ARATIO (Aspect Ratio),
SKEW (Skew Angle), TAPER (Face Taper), WARP (Warp Angle), TWIST
(Twist Angle), EDGE (Edge Angle), COLLAPSE, ANGLE (Vertex Angle),
HOENOR (Hoe Normal Offset), HOETAN (Hoe Tangent Offset).

No default (ARATIO, SKEW, TAPER, WARP, TWIST, EDGE, COLLAPSE,


ANGLE, HOENOR, or HOETAN).

LTYPE Type of bound limits.

No default (WARNING or ERROR)

V1 Lower bound value.

No default (Real)

V2 Upper bound value.

No default (Real)

Comments

1. Element quality checks and their default settings are described in the Element Quality
Check section.

2. All specified values (V1 and V2) are checked against the corresponding limits used for
validity check. Data outside the validity range is ignored.

Altair Engineering OptiStruct 13.0 Reference Guide 1005

Proprietary Information of Altair Engineering


ELIST

Bulk Data Entry

ELIST – Damp Shell Elements for a Fluid Volume

Description

Specifies damp shell elements for a fluid volume. ELIST entries are referenced by the MFLUID
entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ELIST LID EID1 EID2 EID3 EID4 EID5 EID6 EID7

EID8 EID9 EID10 - etc -

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ELIST 25 47 22 THRU 35 -56 -57

Field Contents

LID List of identification number.

No default (Integer > 0)

EID Element identification number of CQUAD4, CTRIA3, CQUADR, and


CTRIAR elements that are damp in the fluid volume.

Comments

1. By default, for elements only damp on one side (see WSURF1 on MFLUID entry), the damp
side of an element is on the same side of the element’s normal. But a negative EIDi
indicates that the fluid is opposite to the normal. If there are negative EIDi’s specified in
a "THRU" range, then both EIDi’s in the range must be negative.

1006 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


2. Alternatively, the SURF and SET entries may be used to define damp elements but the
SURF and SET entries may not be combined in the single with ELIST entries to define
damp elements. For example, if any MFLUID references a missing ELIST,25, then the
program will not search for a SET,25 if a ELIST card exists in the deck.

3. ELIST entries are internally converted to SET entries. The continuation is optional.

Altair Engineering OptiStruct 13.0 Reference Guide 1007

Proprietary Information of Altair Engineering


ENDMETADATA

Bulk Data Entry

ENDMETADATA – Indicates the end of metadata that is to be passed to the metadata output
file.

Description

ENDMETADATA indicates the end of metadata that is to be passed to the metadata output file.
Metadata between the METADATA and ENDMETADATA commands is passed to the
<filename>_metadata.xml file.

Example

METADATA
This line will be passed to the filename_metadata.xml file.
So will this information: Color=blue
ENDMETADATA

Comments

1. There can be two sections of metadata; one in the Solution Control section and one in
the Bulk Data section.

2. Metadata can be used to pass information from the pre-processor seamlessly through the
solver to a post-processing program.

1008 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


END

Bulk Data Entry

END – Indicates the end of data input for a specific entity

Description

The END bulk data entry indicates the end of data that is used to describe a specific entity
(or entities) for inclusion in a model. The END entry is used in conjunction with the BEGIN
entry to define the data required for a specific entity.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

END TYPE NAME

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

END FEMODE Bumper


L

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

END HYPRBEAM Square

Field Contents

TYPE Specifies the entity type that will be defined by the END data entry (see
comment 2).

(HYPRBEAM or FEMODEL)

NAME This field specifies the name of the entity that is defined by the END entry
(see comment 2).

(Character String)

Altair Engineering OptiStruct 13.0 Reference Guide 1009

Proprietary Information of Altair Engineering


Comments

1. The BEGIN and END bulk data entries can be used in conjunction to define a part within
the full model (for TYPE = FEMODEL).

2. TYPE = HYPRBEAM:

Data required for the definition of an arbitrary beam section will be specified between the
BEGIN and END data entries.

TYPE = FEMODEL:

In a model containing multiple parts, the parts are included within the full model specifying
part data between the BEGIN and END bulk data entries (the INCLUDE entry can also be
used for part data referencing). The name of the included part should be specified in the
NAME field.

3. The INCLUDE entry, similar to almost any other bulk data entry, is allowed between BEGIN
and END entries. However, BEGIN and END should exist in the same file.

4. Models are often defined in separate files, and the block (BEGIN – END) contains only
INCLUDE entries. It is possible to duplicate a single part by including the same file(s) in
different BEGIN-END blocks.

5. There can be multiple sections of arbitrary beam data; one for each beam section.

6. An example set of data for the definition of an arbitrary beam section is as follows:
BEGIN,HYPRBEAM,SQUARE
$
GRIDS,1,0.0,0.0
GRIDS,2,1.0,0.0
GRIDS,3,1.0,1.0
GRIDS,4,0.0,1.0
$
CSEC2,10,100,1,2
CSEC2,20,100,2,3
CSEC2,30,100,3,4
CSEC2,40,100,4,1
$
PSEC,100,1000,0.1
$
END,HYPRBEAM

1010 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


ERPPNL

Bulk Data Entry

ERPPNL – Panel Definition for Equivalent Radiated Power Output

Description

Defines one or more sets of elements as panels for equivalent radiated power output for a
frequency response analysis of a coupled fluid-structural model.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ERPPNL NAME1 SID1 NAME2 SID2 NAME3 SID3 NAME4 SID4

NAME5 SID5 …

Field Contents

NAME# Panel label.

No default (Character string)

SID# Set identification number for a set of elements.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1011

Proprietary Information of Altair Engineering


ESLTADD

Bulk Data Entry

ESLTADD – Combination of selected time steps for Geometric Nonlinear ESLM Optimization or a
Multi-body Dynamics ESLM Optimization

Description

Defines a combined time step selection set as a union of selected time steps defined via
ESLTIME entries for Geometric Nonlinear ESLM optimization or a Multi-body Dynamics ESLM
optimization.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ESLTADD SID S1 S2 S3 S4 S5 S6 S7

S8 S9 etc.

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ESLTADD 101 9 11 13

Field Contents

SID Set identification number.

(Integer > 0)

Si Set identification numbers of time step selections defined via ESLTIME bulk
data entries.

(Integer > 0)

Comments

1. ESLTADD can be selected within the subcase information section using the command
ESLTIME=SID.

2. Si should be unique and may not be the identification number of a set defined by another
ESLTADD entry.

1012 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. ESLTADD entries take precedence over ESLTIME entries. If both entries have the same
SID, only the ESLTADD entry will be used.

4. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1013

Proprietary Information of Altair Engineering


ESLTIME

Bulk Data Entry

ESLTIME – Time Step selection control for Geometric Nonlinear Response ESLM Optimization
and Multi-body Dynamics ESLM Optimization

Description

Defines time step selection control for geometric nonlinear response ESL Optimization and
Multi-body dynamics ESLM optimization.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ESLTIME SID TLB TUB

RID1 LB1 UB1 TYPE1

RID2 LB2 UB2 TYPE2

RID3 LB3 UB3 TYPE3

...

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ESLTIME 100

11 -19.9 99.9

12 1

13

1014 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

SID Set identification number.

(Integer > 0)

RID Identification number of a DRESP1, DRESP2, or DRESP3 bulk data


entry.

(Integer > 0)

TLB Lower bound of time.

No default (Real > 0.0, or blank)

TUB Upper bound of time.

No default (Real > 0.0, or blank)

LB# Lower bound on response.

(Real, or blank)

UB# Upper bound on response.

(Real, or blank)

TYPE# Flag to select the time steps at which the highest or lowest
response values or peaks or troughs of the response, occur.

= 1, select the highest response value

= -1, select the lowest response value

= 2, select the response peaks

= -2, select the response troughs

(Integer = -2, -1, 1, 2, or blank)

Comments

1. ESLTIME should be selected by the Subcase Information command ESLTIME = SID or in


the bulk data section by the ESLTADD entry. It can only be selected in geometric
nonlinear analysis subcases which are defined by an ANALYSIS = NLGEOM, IMPDYN or
EXPDYN subcase entry, and for geometric nonlinear response ESL Optimization.

2. The SID and RID fields cannot be left blank. Other fields, if blank, will be ignored.

3. Lower bounds TLB and LB must be smaller than upper bounds TUB and UB respectively.

Altair Engineering OptiStruct 13.0 Reference Guide 1015

Proprietary Information of Altair Engineering


4. The TLB and TUB fields can be used to define the range of time. OptiStruct will then
select the most critical time steps in the time range with higher priority for ESL generation
(Figure 1). If more time steps are required, then the critical time steps outside the time
range will be taken into account.

5. Using fields LB and UB, the user can define the range of a specific response. OptiStruct
will then select the time steps with response values in this range for ESL generation
(Figure 1).

Figure 1: Time step selection based on time and response range.

6. If TYPE = 1, time steps which have the highest response values will be selected.

If TYPE = -1, time steps which have the lowest response values will be selected.

Figure 2: Example illustration depicting TYPE=1 and TYPE=-1 response selection

7. If TYPE = 2, time steps at which response peaks occur will be selected.

If TYPE = -2, time steps at which response troughs occur will be selected.

1016 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Figure 3: Example illustration depicting TYPE=2 and TYPE=-2 response selection.

8. If a NLGEOM, IMPDYN or EXPDYN subcase is referenced by a DRESP2 entry with DRESP1L


or DRESP2L definition, the generated ESL subcase at the most critical time step will be
used for this DRESP2(DRESP1L/DRESP2L) entry.

9. All continuation lines on the ESLTIME entry are ignored in Multi-body dynamics ESLM
optimization. Only the first line (ESLTIME, SID, TLB, TUB) is considered.

10. DOPTPRM, ESLSTOL is ignored, if ESLTIME is defined in the model.

Altair Engineering OptiStruct 13.0 Reference Guide 1017

Proprietary Information of Altair Engineering


FATDEF

Bulk Data Entry

FATDEF – Elements for Fatigue Analysis

Description

Defines elements, and associated fatigue properties, for consideration in a fatigue analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FATDEF ID TOPSTR

Optional continuation lines for selecting elements, and associated fatigue properties, using
element sets (ELSET)

ELSET ELSID1 PFATID1 ELSID2 PFATID2 ELSID3 PFATID3

ELSID4 PFATID4 … … … …

… …

Optional continuation lines for selecting elements and associated fatigue properties through
referenced properties (PSHELL)

PSHELL PID1 PFATID1 PID2 PFATID2 PID3 PFATID3

PID4 PFATID4 … … … …

… …

Optional continuation lines for selecting elements and associated fatigue properties through
referenced properties (PSOLID)

PSOLID PID1 PFATID1 PID2 PFATID2 PID3 PFATID3

PID4 PFATID4 … … … …

… …

1018 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Optional continuation lines for excluding elements using element sets (ELSET)

XELSET XELSID1 XELSID2 XELSID3 XELSID4 XELSID5 XELSID6 XELSID7

XELSID8 … … … … … …

… …

Optional continuation lines for excluding individual elements

XELEM XEID1 XEID2 XEID3 XEID4 XEID5 XEID6 XEID7

XEID8 … … … … … …

… …

Field Contents

ID Each FATDEF card must have a unique ID. FATDEF Subcase Information entry
may reference this ID.

No default (Integer > 0)

TOPSTR Top stress fraction. Elements with combined stress not in this top fraction of
each MATFAT group will be screened out and have no results. This field is
ignored in fatigue analysis on a transient subcase.

Default = blank (100% will be used internally), (0.0 < Real < 1.0)

ELSET ELSET flag indicating that a list of pairs of ELSET and PFAT IDs will follow,
defining elements, and their associated fatigue properties, for consideration in
fatigue analyses where this FATDEF is selected.

ELSID# Element Set ID. Elements in this set will be considered in fatigue analyses
where this FATDEF is selected.

No default (Integer > 0)

PFATID# Fatigue property ID. This is identification number of a PFAT entry, which
indicates the fatigue property used by the preceding elements defined by
ELSID# or PID#.

PSHELL PSHELL flag indicating that a list of pairs of PSHELL property IDs and PFAT
IDs will follow; defining elements and their associated fatigue properties for
consideration in fatigue analyses where this FATDEF is selected.

Altair Engineering OptiStruct 13.0 Reference Guide 1019

Proprietary Information of Altair Engineering


Field Contents

PSOLID PSOLID flag indicating that a list of pairs of PSOLID property IDs and PFAT
IDs will follow; defining elements and their associated fatigue properties for
consideration in fatigue analyses where this FATDEF is selected.

PID# Property ID. This is identification number of a PSHELL or PSOLID entry.


Elements referencing any property with this ID will be considered in fatigue
analyses where this FATDEF is selected.

No default (Integer > 0)

XELSET XELSET flag indicating that IDs of elements sets excluded from fatigue
analysis follow.

XELSID# Element set ID. Elements in these sets will be excluded from fatigue analyses
where this FATDEF is selected.

No default (Integer > 0)

XELEM XELEM flag indicating that IDs of elements excluded from fatigue analysis
follow.

XEID# Element ID. These elements will be excluded from fatigue analyses where this
FATDEF is selected.

No default (Integer > 0)

Comments

1. At least one of the optional continuation lines ELSET or PROP must be present.

2. This card is represented as a loadcollector in HyperMesh.

1020 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


FATEVNT

Bulk Data Entry

FATEVNT – Loading Event Definition for Fatigue Analysis

Description

Defines loading events for fatigue analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FATEVNT ID FLOAD1 FLOAD2 FLOAD3 FLOAD4 FLOAD5 FLOAD6 FLOAD7

FLOAD8 ... ...

Field Contents

ID Each FATEVNT card must have a unique ID. This identifier may be referenced
by a FATSEQ definition.

No default (Integer > 0)

FLOAD# Identification number of a FATLOAD entry (see comments 1, 3 and 4).

No default (Integer > 0)

Comments

1. FATLOAD entries referenced on this bulk data entry may reference different subcases.

2. Identification numbers of FATSEQ and FATEVNT share the same ID pool.

3. These FATLOAD entries should reference the subcase types. For example, either static
subcases or transient subcases can be referenced, but not both. Referencing a
combination of subcase types via FATLOAD entries on the same FATEVNT entry is not
allowed.

4. If a specified FATLOAD entry references a transient subcase, only one FATLOAD entry is
allowed.

5. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1021

Proprietary Information of Altair Engineering


FATLOAD

Bulk Data Entry

FATLOAD - Fatigue Load

Description

Defines fatigue loading parameters.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FATLOAD ID TID LC ID LDM Scale Offset

Field Contents

ID Each FATLOAD card must have a unique ID. This identifier may be
referenced by a FATEVNT definition.

No default (Integer > 0)

TID Identification number of TABFAT entry.

(Integer > 0 or blank)

If LCID references a linear-static subcase, TID should be a positive integer


(Integer > 0).

If LCID references transient subcase, TID should be blank.

LCID Subcase identification number of a linear-static or transient analysis


subcase.

No default (Integer > 0)

LDM The magnitude of the FEA load in the same units as those for the time
history. It is ignored in fatigue analyses based on a transient analysis
subcase (see comment 2).

Default = 1.0 (Real)

Scale Scale factor applied to the load or time history. It is ignored in fatigue
analyses based on a transient analysis subcase.

Default = 1.0 (Real)

1022 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Offset Offset applied to the load or time history. It is ignored in fatigue analyses
based on a transient analysis subcase.

Default = 0.0 (Real)

Comments

1. This magnitude is used as a scale factor to normalize the finite element stresses/strains
to obtain the stress/strain distribution due to a unit loading.

2. The sequence below depicts how LDM, Scale and Offset values work together to scale
the FEA stress tensor at time t:

ij . FEA
ij (t ) ( P (t ) Scale Offset )
LDM

Where, is the result stress tensor at time t.

is the stress tensor from static analysis.

P(t) is the y point value of load-time history at time t.


3. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1023

Proprietary Information of Altair Engineering


FATPARM

Bulk Data Entry

FATPARM - Fatigue Analysis Parameters

Description

This bulk data entry can be used to define parameters required for a Fatigue Analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FATPARM ID Type

STRESS C ombinatio C orrectio StressUni Plasticit


n n t y

RAINFLO RType GateRel


W

C ERTNTY SurvC ert

FOS FOSType

Field Contents

ID Each FATPARM card must have a unique ID. The FATPARM Subcase Information
entry may reference this identifier.

No default (Integer > 0)

Type Type of fatigue analysis that is defined.

Default = SN

(SN = Stress Life, EN = Strain Life, FOS = Factor of Safety Analysis - see
comment 9)

(NSTRESS is also supported for Stress Life for compatibility)

STRESS STRESS flag indicating that parameters are to follow which define how the
stress is used in fatigue calculation. This flag and following parameters will be
used only when the "Type" field is set to SN or EN.

1024 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Combinatio Default = ABSMAXPR


n
(ABSMAXPR = Abs Max Principal MAXPRINC = Max Principal
MINPRINC = Min Principal VONMISES = von Mises
SGVON = Signed von Mises TRESCA = Tresca
SGTRESCA = Signed Tresca SGMAXSHR = Signed Max Shear
XNORMAL = X Normal YNORMAL = Y Normal
ZNORMAL = Z Normal XYSHEAR = X-Y Shear
YZSHEAR = Y-Z Shear ZXSHEAR = Z-X Shear)
The sign on the Signed von Mises, Signed Tresca, Signed Max. Shear is taken
from the sign of the Abs. Max. Principal value.

For Stress Life, combined stress value is used; For Strain Life, combined strain
value is used.

For Strain Life, shear strain components are engineering shear strain (two times
tensor shear strain).

For brittle materials, "Absolute maximum principle" is recommended.

For ductile materials, "Signed von Mises" is recommended.

Correction Mean stress correction method. See comments 5, 6, 7 and 8.

For Type = SN, valid options are:

Default = GOODMAN (NONE, GOODMAN, GERBER, GERBER2, SODERBE)

For Type = EN, valid options are:

Default = SWT (NONE, MORROW, MORROW2, SWT = Smith-Watson-Topper)

StressUnit FE analysis Stress Tensor Unit. The Unit is necessary because the S-N/E-N
curve (MATFAT card) might be defined in different unit, and FEA stress needs
to be converted before looking up the fatigue life for a given stress level on the
S-N curve. See comment 10.

Default = MPA (MPA, PA, PSI, KSI)

Plasticity This parameter is only applicable for Type = EN.

For Type = SN, it is not used.

For Type = EN, valid options are:

Default = NEUBER (NONE, NEUBER)

RAINFLOW The RAINFLOW flag indicates that parameters required for Rainflow counting are
to follow. This flag and its related parameters will be used only when the “Type”
field is set to SN or EN.

Altair Engineering OptiStruct 13.0 Reference Guide 1025

Proprietary Information of Altair Engineering


Field Contents

RType Rainflow data type. See comment 1.

Default = LOAD

(LOAD - Load-time history

STRESS - Stress-time history)

GateRel Relative fraction of maximum gate range. The reference value is the maximum
range multiplied by GateRel, and used for gating out small disturbances or
"noise" in the time series.

CERTNTY The CERTNTY flag indicates that parameters that define certainties in fatigue
analysis are to follow. This flag and the following parameter will be used only
when the “Type” field is set to SN or EN.

SurvCert Certainty of survival based on the scatter of the S-N curve. See comment 4.

Default = 0.5 (0.0 < Real < 1.0)

FOS The FOS flag indicates that the following parameters are for Factor of Safety
analysis (Type = FOS). This flag and following parameter will be used only when
the “Type” field is set to FOS.

FOSType This field can be used to select the Factor of safety analysis type.

Default = DANGVAN

Comments

1. RType = Load is valid when there is only one static load case defined in an event. If the
event contains multiple static load cases, then RType will automatically be set to STRESS
because there will be stress super-positioning among different load cases; doing rainflow
counting on load-time history could not deal with it.

2. When RType = Load, load-time history will be cycle counted using the rainflow cycle
counting method. The cycle counting results (load Ranges and Means) will be scaled by
combined FEA stress. Doing rainflow counting on load-time is much faster than doing it
on stress-time (RType=Stress), especially when the load-time history is complex and
contains a large number of time points, but it is less accurate.

3. When RType = Stress, stress-time history will be cycle counted using the rainflow cycle
counting method. The stress-time history has the same length as load-time, while each
point of the stress time is the combined stress value where the stress tensor is FEA
stress scaled by y point value of the corresponding load-time history.

1026 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


4. Certainty of Survival is based on the scatter of the S-N / E-N curve. It is used to modify
the S-N / E-N curve according to the standard error parameter (SE) defined in fatigue
property of material card (MATFAT card). A higher reliability level requires a larger
certainty of survival.

5. When fatigue optimization is performed, EN method with SWT mean stress correction is
changed to EN method with Morrow mean stress correction automatically.

6. Correction=GERBER2 improves the GERBER method by ignoring the effect of negative mean
stress.

7. Correction=MORROW2 improves the MORROW method by ignoring the effect of negative


mean stress.

8. Correction=SODERBE is slightly different from GOODMAN, the mean stress is normalized by


yield stress instead of ultimate tensile stress.

Se = Sa / (1 - Sm / Sy )

Where, Se is equivalent stress amplitude, Sa is stress amplitude, Sm is mean stress, and


Sy is yield stress.

9. The “STRESS”, “RAINFLOW” and “CERTNTY” continuation lines are ignored in a factor of
safety analysis (Type=FOS).

10. If UNITS=# or DTI UNITS is present, the default value of StressUnit should be determined
by UNITS=# or DTI UNITS. If UNITS=# and DTI UNITS are absent, the default value of
StressUnit is MPA. If UNITS=# or DTI UNITS is present, and StressUnit is also specified,
but they are not consistent, an error will be issued.

11. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1027

Proprietary Information of Altair Engineering


FATSEQ

Bulk Data Entry

FATSEQ – Load Sequence Definition for Fatigue Analysis

Description

This bulk data entry can be used to define a loading sequence for a Fatigue Analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FATSEQ ID

FID1 N1 FID2 N2 FID3 N3 FID4 N4

FID5 N5

Field Contents

ID Each FATSEQ card must have a unique ID. FATSEQ Subcase Information entry
may reference this identifier. Alternatively this ID may be referenced by other
FATSEQ definitions.

No default (Integer > 0)

FID# Identification number of FATSEQ or FATEVNT entry (see Comment 3)

No default (Integer > 0)

N# Number of times this loading sequence or event is repeated (see Comment 4).

Default = 1 (Integer > 0)

Comments

1. Identification numbers of FATSEQ and FATEVNT entries share the same ID pool.

2. Repeat number (N#) has no effect on the results of a Factor of Safety (FOS) analysis.

3. A fatigue subcase should reference the same subcase types through FATSEQ and
FATEVNT entries (for example, either static subcases or transient subcases can be
referenced, but not both). Referencing a combination of subcase types is not allowed.

4. This card is represented as a loadcollector in HyperMesh.

1028 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


FLDATA

Bulk Data Entry

FLDATA – User-defined Forming Limit Curve for One-Step Stamping Simulation

Description

Defines a forming limit curve as a table of minor and major strain values in a one-step
stamping simulation.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FLDATA FLDID Ei1 Ei2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FLDATA 2 -.194 .284

FLDATA 2 -.0.89 .269

FLDATA 2 … …

FLDATA 2 .319 .319

Field Contents

Blank holder identification number.


FLDID
No default (Integer > 0)

Minor strain value.


Ei1
No default (Real)

Major strain value


Ei2
No default (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 1029

Proprietary Information of Altair Engineering


Comments

1. This entry is only valid with an @HyperForm statement in the first line of the input file.

1030 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


FORCE

Bulk Data Entry

FORCE – Point Force

Description

Defines a static force at a grid point by specifying a vector. It can also be used to define the
EXCITEID field (Amplitude “A”) of dynamic loads in RLOAD1, RLOAD2, TLOAD1 and TLOAD2 bulk
data entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FORC E SID G C ID F N1 N2 N3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FORC E 2 5 6 2.9 0.0 1.0 0.0

Field Contents

SID Load set identification number.

(Integer > 0)

G Grid point identification number.

(Integer > 0 or <PartName.number>) See comment 3.

CID Coordinate system identification number.

Default = 0 (Integer > 0, or blank)

F Scale factor.

Altair Engineering OptiStruct 13.0 Reference Guide 1031

Proprietary Information of Altair Engineering


Field Contents

(Real)

N1,N2,N3 Components of vector measured in coordinate system defined by CID.

(Real; must have at least one non-zero component)

Comments

1. The static force applied to grid point G is given by

where, is the vector defined in fields 6, 7, and 8.

2. A CID of zero or blank references the basic coordinate system.

3. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on FORCE entries in the model. A fully qualified reference
(“PartName.number”) is similar to the format of a numeric reference. “PartName” is the
name of the part that contains the referenced local entry (part names are defined on the
BEGIN Bulk Data Entry in the model). “number” is the identification number of a
referenced local entry in the part “PartName”. See Parts and Instances in the User’s
Guide for detailed information on the use of fully qualified references.

4. This card is represented as a force load in HyperMesh.

1032 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


FORCE1

Bulk Data Entry

FORCE1 – Static Force, Alternate Form 1

Description

Used to define a static force by specification of a value and two grid points that determine
the direction. It can also be used to define the EXCITEID field (Amplitude “A”) of dynamic
loads in RLOAD1, RLOAD2, TLOAD1 and TLOAD2 bulk data entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FORC E1 SID G F G1 G2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FORC E1 6 13 -2.93 16 13

Field Contents

SID Load set identification number.

(Integer > 0)

G Grid point identification number.

(Integer > 0)

F Value of force.

(Real)

G1,G2 Grid point identification numbers.

Altair Engineering OptiStruct 13.0 Reference Guide 1033

Proprietary Information of Altair Engineering


Comments

1. The static force applied to grid point G is

where, is a unit vector parallel to a vector from G1 to G2.

2. This card is represented as a force load in HyperMesh

1034 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


FORCE2

Bulk Data Entry

FORCE2 – Static Force, Alternate Form 2

Description

Used to define a static force by specification of a value and four grid points that determine
the direction. It can also be used to define the EXCITEID field (Amplitude “A”) of dynamic
loads in RLOAD1, RLOAD2, TLOAD1 and TLOAD2 bulk data entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FORC E2 SID G F G1 G2 G3 G4

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FORC E2 6 13 -2.93 16 13 18 19

Field Contents

SID Load set identification number.

(Integer > 0)

G Loaded Grid point identification number.

(Integer > 0)

F Value of force.

(Real)

Gi Grid point identification numbers.

(Integer > 0; G1 and G2 may not be coincident; G3 and G4 cannot be


coincident.)

Altair Engineering OptiStruct 13.0 Reference Guide 1035

Proprietary Information of Altair Engineering


Comments

1. The static force applied to grid point G is

where, is a unit vector parallel to a vector calculated by the cross product of vectors
from G1 to G2 and G3 to G4.

2. This card is represented as a force load in HyperMesh

1036 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


FREQ

Bulk Data Entry

FREQ – Frequency List

Description

Defines a set of frequencies to be used in the solution of frequency response problems.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FREQ SID F1 F2 F3 F4 F5 F6 F7

F8 … … … … … … …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FREQ 3 7.0 12.56 13.99 23.4 23.34

Field Contents

SID Identification number.

No default (Integer > 0)

F# Frequency value.

No default (Real > 0.0)

Comments

1. FREQ entries must be selected with the I/O Options or Subcase Information command
FREQUENCY = SID.

2. The units for F# are cycles per unit time.

Altair Engineering OptiStruct 13.0 Reference Guide 1037

Proprietary Information of Altair Engineering


3. All FREQi entries with the same set identification numbers will be used. Duplicate
frequencies will be ignored. and are considered duplicated if:

where, DFREQ is a user parameter with a default of 10 -5 * fMAX , and fMIN are the maximum
and minimum excitation frequencies of the combined FREQi entries.

4. This card is represented as a loadcollector in HyperMesh.

1038 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


FREQ1

Bulk Data Entry

FREQ1 – Frequency List, Alternate Form 1

Description

Defines a set of frequencies to be used in the solution of frequency response problems by


specification of a starting frequency, frequency increment, and the number of increments
desired.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FREQ1 SID F1 DF NDF

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FREQ1 6 2.9 0.5 13

Field Contents

SID Identification number.

No default (Integer > 0)

F1 First frequency in set.

No default (Real > 0)

DF Frequency increment.

No default (Real > 0.0)

NDF Number of frequency increments.

Default = 1 (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1039

Proprietary Information of Altair Engineering


Comments

1. FREQ1 entries must be selected with the I/O Options or Subcase Information command
FREQUENCY = SID.

2. The units for F1 and DF are cycles per unit time.

3. The frequencies defined by this entry are given by

where i = 1 to (NDF + 1).

4. All FREQi entries with the same set identification numbers will be used. Duplicate
frequencies will be ignored. and are considered duplicated if:

where, DFREQ is a user parameter with a default of 10 -5 * fMAX , and are the maximum
and minimum excitation frequencies of the combined FREQi entries.

5. This card is represented as a loadcollector in HyperMesh.

1040 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


FREQ2

Bulk Data Entry

FREQ2 – Frequency List, Alternate Form 2

Description

Defines a set of frequencies to be used in the solution of frequency response problems by


specification of a starting frequency, final frequency, and the number of logarithmic
increments desired.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FREQ2 SID F1 F2 NF

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FREQ2 6 1.0 8.0 6

Field Contents

SID Identification number.

No default (Integer > 0)

F1 First frequency in set.

No default (Real > 0.0)

F2 Last frequency in set.

No default (Real > 0.0, F2 > F1)

NF Number of logarithmic intervals.

Default = 1 (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1041

Proprietary Information of Altair Engineering


Comments

1. FREQ2 entries must be selected with the I/O Options or Subcase Information command
FREQUENCY = SID.

2. The units for F1 and F2 are cycles per unit time.

3. The frequencies defined by this entry are given by

where, and i = 1, 2, …, (NF + 1).

4. All FREQi entries with the same set identification numbers will be used. Duplicate
frequencies will be ignored. and are considered duplicated if:

where, DFREQ is a user parameter with a default of 10 -5 * fMAX , and are the maximum
and minimum excitation frequencies of the combined FREQi entries.

5. This card is represented as a loadcollector in HyperMesh.

1042 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


FREQ3

Bulk Data Entry

FREQ3 – Frequency List, Alternate Form 3

Description

Defines a set of frequencies for the modal method of frequency response analysis by
specifying the number of frequencies between modal frequencies.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FREQ3 SID F1 F2 TYPE NEF C LUSTER

Example

Define a set of frequencies such that there will be 10 frequencies between each mode,
within the frequency range 20 to 200, plus 10 frequencies between 20 and the lowest
mode in the range, plus 10 frequencies between the highest mode in the range and 200.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FREQ3 6 20.0 200.0 LINEAR 10 2.0

Field Contents

SID Set identification number.

No default (Integer > 0)

F1 Lower bound of modal frequency range in cycles per unit time.

No default (Real > 0.0 for TYPE = LINEAR ; Real > 0.0 for TYPE = LOG)

F2 Upper bound of modal frequency range in cycles per unit time.

Default = F1 (Real > 0.0, F2 > F1)

Altair Engineering OptiStruct 13.0 Reference Guide 1043

Proprietary Information of Altair Engineering


Field Contents

TYPE Specifies linear or logarithmic interpolation between frequencies.

Default = "LINEAR" (LINEAR or LOG)

NEF Number of excitation frequencies within each sub range including the end
points. The first sub range is between F1 and the first modal frequency
within the bounds. Intermediate sub ranges exist between each mode
calculated within the bounds. The last sub range is between the last
modal frequency within the bounds and F2.

Default = 10 (Integer > 1)

CLUSTER Specifies cluster of the excitation frequency near the end points of the
range. See comment 5.

Default = 1.0 (Real > 0.0)

Comments

1. FREQ3 applies only to the modal method of frequency response analysis.

2. FREQ3 entries must be selected in the Subcase Information section with FREQUENCY =
SID.

3. Since the forcing frequencies are near structural resonances, it is important that some
amount of damping be specified.

4. All FREQi entries with the same set identification numbers will be used. Duplicate
frequencies will be ignored. and are considered duplicated if:

where, DFREQ is a user parameter, with a default of 10 -5 * fMAX and are the maximum
and minimum excitation frequencies of the combined FREQi entries.

5. CLUSTER is used to obtain better resolution near the modal frequencies where the
response variation is highest, in accordance with:

1044 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


where,

= -1 + 2(k - 1)/(NEF - 1) is a parametric coordinate between -1 and 1.

k = excitation frequency number in the subrange (1,2,3,…,NEF)

= frequency at the lower limit of the sub range. (If TYPE is LOG, then this is
the logarithm of the frequency.)

= frequency at the upper limit of the sub range. (If TYPE is LOG, then this is
the logarithm of the frequency.)

= the k-th excitation frequency. (If TYPE is LOG, then this is the logarithm of
the frequency.)

CLUSTER > 1.0 provides closer spacing of excitation frequency towards the ends of the
frequency range, while values of less than 1.0 provide closer spacing towards the center
of the frequency range.

For example, if the frequency range is between 10 and 20, NEF = 11, TYPE = "LINEAR";
then, the excitation frequencies for various values of CLUSTER would be as shown in the
table below.

CLUSTER
Excitation
Frequency 0.25 0.50 1.0 2.0 4.0
Number
Excitation Frequencies in Hertz

1 -1.0 10.00 10.0 10.0 10.0 10.0

2 -0.8 12.95 11.8 11.0 10.53 10.27

3 -0.6 14.35 13.2 12.0 11.13 10.60

4 -0.4 14.87 14.2 13.0 11.84 11.02

5 -0.2 14.99 14.8 14.0 12.76 11.66

6 0.0 15.00 15.0 15.0 15.00 15.00

7 0.2 15.01 15.2 16.0 17.24 18.34

8 0.4 15.13 15.8 17.0 18.16 18.98

9 0.6 15.65 16.8 18.0 18.87 19.40

Altair Engineering OptiStruct 13.0 Reference Guide 1045

Proprietary Information of Altair Engineering


10 0.8 17.05 18.2 19.0 19.47 19.73

11 1.0 20.00 20.0 20.0 20.00 20.00

6. In design optimization, the excitation frequencies are derived from the modal frequencies
computed at each design iteration.

7. In modal analysis, solutions for modal degrees-of-freedom from rigid body modes at zero
excitation frequencies may be discarded. Solutions for non-zero modes are retained.

8. This card is represented as a loadcollector in HyperMesh.

1046 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


FREQ4

Bulk Data Entry

FREQ4 – Frequency List, Alternate Form 4

Description

Defines a set of frequencies for the modal method of frequency response analysis by
specifying the amount of "spread" around each modal frequency and the number of equally
spaced frequencies within the spread.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FREQ4 SID F1 F2 FSPD NFM

Example

Define a set of frequencies such that there will be 21 equally spaced frequencies across a
frequency band of to for each modal frequency that occurs between 20
and 200.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FREQ4 6 20.0 200.0 0.30 21

Field Contents

SID Set identification number.

No default (Integer > 0)

F1 Lower bound of modal frequency range in cycles per unit time.

Default = 0.0 (Real > 0.0)

F2 Upper bound of frequency range in cycles per unit time.

Default = 1.0E20 (Real > 0.0, F2 > F1)

Altair Engineering OptiStruct 13.0 Reference Guide 1047

Proprietary Information of Altair Engineering


Field Contents

FSPD Frequency spread, +/- the fractional amount specified for each mode
which occurs in the frequency range F1 to F2.

Default = 0.10 (1.0 > Real > 0.0)

NFM Number of evenly spaced frequencies per "spread" mode.

Default = 3 (Integer > 0; If NFM is even, NFM + 1 will be used)

Comments

1. FREQ4 applies only to the modal method of frequency response analysis.

2. FREQ4 entries must be selected in the Subcase Information section with FREQUENCY =
SID.

3. There will be NFM excitation frequencies between and , for


each modal frequency in the range F1 to F2. If this computation results in excitation
frequencies less than F1 and greater than F2, those computed excitation frequencies are
ignored.

4. Excitation frequencies may be based on modal frequencies that are not within the range
(F1 and F2) as long as the calculated excitation frequencies are within the range.
Similarly, an excitation frequency calculated based on natural frequencies within the
range (F1 through F2) may be excluded if it falls outside the range.

5. The frequency spread can be used also to define the half-power bandwidth. The half-
power bandwidth is given by , where, is the damping ratio. Therefore, if FSPD
is specified equal to the damping ratio for the mode, NFM specifies the number of
excitation frequencies within the half-power bandwidth.

1048 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


6. Since the forcing frequencies are near structural resonances, it is important that some
amount of damping be specified.

7. All FREQi entries with the same set identification numbers will be used. Duplicate
frequencies will be ignored. and are considered duplicated if:

where, DFREQ is a user parameter, with a default of 10-5. The values and are
the maximum and minimum excitation frequencies of the combined FREQi entries.

8. In design optimization, the excitation frequencies are derived from the modal frequencies
computed at each design iteration.

9. In modal analysis, solutions for modal degrees-of-freedom from rigid body modes at zero
excitation frequencies may be discarded. Solutions for non-zero modes are retained.

10. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1049

Proprietary Information of Altair Engineering


FREQ5

Bulk Data Entry

FREQ5 – Frequency List, Alternate Form 5

Description

Defines a set of frequencies for the modal method of frequency response analysis by
specification of a frequency range and fractions of the natural frequencies within that range.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FREQ5 SID F1 F2 FR1 FR2 FR3 FR4 FR5

FR6 FR7 etc.

Example

Define a set of frequencies such that the list of frequencies will be 0.6, 0.8, 0.9, 0.95, 1.0,
1.05, 1.1, and 1.2 times each modal frequency between 20 and 200.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FREQ5 6 20.0 200.0 1.0 0.6 0.8 0.9 0.95

1.05 1.1 1.2

Field Contents

SID Set identification number.

No default (Integer > 0)

F1 Lower bound of modal frequency range in cycles per unit time.

Default = 0.0 (Real > 0.0)

1050 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

F2 Upper bound of frequency range in cycles per unit time.

Default = 1.0E20 (Real > 0.0, F2 > F1)

FRi Fractions of the natural frequencies in the range F1 to F2.

No default (Real > 0.0)

Comments

1. FREQ5 applies only to the modal method frequency response analysis.

2. FREQ5 entries must be selected in the Subcase Information section with FREQUENCY =
SID.

3. The frequencies defined by this entry are given by

where, are the modal frequencies in the range F1 through F2.

If this computation results in excitation frequencies less than F1 and greater than F2,
those computed excitation frequencies are ignored.

4. Excitation frequencies may be based on natural frequencies that are not within the range
(F1 and F2) as long as the calculated excitation frequencies are within the range.

5. Since the forcing frequencies are near structural resonances, it is important that some
amount of damping be specified.

6. All FREQi entries with the same set identification numbers will be used. Duplicate
frequencies will be ignored. and are considered duplicated if:

where, DFREQ is a user parameter, with a default of 10-5. The values and are
the maximum and minimum excitation frequencies of the combined FREQi entries.

7. In design optimization, the excitation frequencies are derived from the modal frequencies
computed at each design iteration.

8. In modal analysis, solutions for modal degrees-of-freedom from rigid body modes at zero
excitation frequencies may be discarded. Solutions for non-zero modes are retained.

9. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1051

Proprietary Information of Altair Engineering


GAPPRM

Bulk Data Entry

GAPPRM – Parameters for Gap Element Connectivity and Configuration Checks

Description

Defines parameters that control connectivity and configuration checks for gap elements (CGAP
and CGAPG). Most of these parameters also affect contact elements that are automatically
created on CONTACT interfaces – see individual descriptions for details.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GAPPRM PARAM1 VAL1 PARAM2 VAL2 PARAM3 VAL3 PARAM4 VAL4

PARAM5 VAL5 etc.

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GAPPRM C KGPDIR -1 PRTSW 1 C HKRUN 1

Field Contents

PARAM# Name of parameter.

VAL# Value of parameter.

While textual values are recommended for clarity, their integer equivalents will also be read.
The available parameters and their values are listed below (click the parameter name for
parameter descriptions).

Parameter Value

1052 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHKRN NO, 0, YES, or 1
Default = NO

CKGPDIR ERR, 2, WARN, 1, NO, 0, REV, or 3


Default = ERR

ERRMSG SHORT, 1, FULL, or 2


Default = SHORT

GAPCMPL NO, 0, YES, 1


Default = YES

GAPGPRJ NORM, 1, SHORT, or 2


Default = SHORT

GAPOFFS YES, NO
Default = YES

GPCOINC <Real>
Defaults
For GAP elements: 1.0e-04
For CONTACT elements: Calculated
automatically based on element size on the
master face.

HMGAPST NO, 0 YES, 1


Default = NO

PRTSW NO, 0, YES, 1


Default = NO

Comments

1. The GAPPRM entry changes the default settings of control parameters for the gap
elements connectivity and checks for configuration errors. None of the parameters of this
entry are required.

2. The gap alignment check controlled by the default value of CKGPDIR = ERR applies
correctly to the most typical situations wherein there is an initial opening between bodies
A and B, and the gap element is used to enforce non-penetration condition. For cases of
overlapping meshes (combined with a prescribed coordinate system), the REV value is
appropriate – it allows both aligned and reversed gap directions (respective to the gap
axis defined by the prescribed system).

3. This card is represented as a control card in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1053

Proprietary Information of Altair Engineering


GAPPRM, CHKRN

Parameter Values Description

CHKRN NO, 0, YES, or 1 Stop the run after the gap element checks are
completed.
Default = NO
If NO or 0, OptiStruct will run to completion unless
other errors are present.

If YES or 1, OptiStruct will stop after gap and


contact elements have been checked.

1054 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GAPPRM, CKGPDIR

Parameter Values Description

CKGPDIR ERR, 2, WARN, 1, Controls the checking of gap element alignment in


NO, 0, REV, or 3 case of prescribed coordinate system CID.

Default = ERR If ERR or 2, then all non-zero length gap elements


that have a prescribed coordinate system are
checked for misalignment of the gap prescribed axis
(x-axis of the prescribed coordinate system) with
the vector GA->B. Angles larger than 30 degrees
produce warnings, angles larger than 60 degrees
produce errors.

If WARN or 1, same as ERR or 2 with the exception


that only warnings are issued.

If NO or 0, then no gap CID direction checks are


performed.

If REV or 3, then orientations of the vector GA->B


that are generally opposite to the prescribed axis
are also accepted. The tolerance levels are the
same as for the default case, except that they are
measured from either 0 or 180 degrees reference
angle.

Altair Engineering OptiStruct 13.0 Reference Guide 1055

Proprietary Information of Altair Engineering


GAPPRM, ERRMSG

Parameter Values Description

ERRMSG SHORT, 1, Defines the maximum number of error messages printed


FULL, or 2 for gap and contact elements.

Default = SHORT If SHORT or 1, then up to 10 error messages are printed


along with a summary of the total number of errors.

If FULL or 2, then all gap and contact element error


messages are printed. Additional diagnostic information
for elements with errors is also printed to the .out file.

1056 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GAPPRM, GAPCMPL

Parameter Values Description

GAPCMPL NO, 0, YES, or 1 This parameter can be used to allow/disallow the


inclusion of gap and contact compliance in the
Default = YES calculation of global compliance.

If YES or 1, then gap/contact compliances will be


included in the calculation of global compliance.

If NO or 0, then gap/contact compliances will not be


included in the calculation of global compliance.

Note:

An example situation where the GAPCMPL parameter may


be used is described as follows:

In some cases, gap/contact elements may exist with


initial penetration (U0<0), these elements may produce
negative contributions to the global compliance. While
this is a legitimate situation (the gap/contact is releasing
elastic energy, rather than accumulating it) it may cause
the global compliance to be negative and thus make
optimization impossible. In such cases, the GAPCMPL
parameter can be used to turn off the contributions of
gap/contact elements to the compliance calculation.

Altair Engineering OptiStruct 13.0 Reference Guide 1057

Proprietary Information of Altair Engineering


GAPPRM, GAPGPRJ

Parameter Values Description

GAPGPRJ NORM, 1, SHORT, or 2 For CGAPG and contact elements, controls how
the projection onto the obstacle element (or
Default = SHORT node patch) is performed.

If NORM or 1, the projection of node GA (or


slave node for CONTACT) to the obstacle B is
performed along the normal to the surface of
the obstacle (a patch of nodes or an element
face). If such normal projection falls outside
the patch of nodes or element face (within 5%
tolerance), an error message is issued for GAPG
elements, while no contact element is created
on the CONTACT interface.

If SHORT or 2, the node GA (or slave node for


CONTACT) is projected onto the obstacle B
along the shortest distance. For cases where
the normal projection falls within the bounds of
the obstacle, this coincides with the NORM
option. For cases where the normal projection
falls outside the obstacle, this option will
choose the point on the obstacle that is
nearest to GA or slave node.

1058 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GAPPRM, GAPOFFS

Parameter Values Description

GAPOFFS YES, NO, AUTO If YES, frictional offset for gap and contact analysis is
active.
Default = AUTO
If NO, frictional offset for gap and contact analysis in
inactive.

If AUTO, frictional offset is turned off when the deck


contains gaps, contact with friction or stick conditions
and at least one nonlinear subcase. This affects both
linear and nonlinear subcases.

For more details, refer to the PGAP and PCONT


descriptions.

Altair Engineering OptiStruct 13.0 Reference Guide 1059

Proprietary Information of Altair Engineering


GAPPRM, GPCOINC

Parameter Values Description

GPCOINC <Real> This parameter defines the distance below which the end
points of gap/contact elements (for example, the GA, GB
See the Note fields of the CGAP bulk data entry) are considered
for defaults coincident (as they may be too close to define the gap
direction accurately).

Note:

1. Currently, for CGAP and CGAPG elements, the default


minimum distance is set at an absolute value of
1.0e-4. For CONTACT, it is calculated automatically
according to element size on the master face, in
which case it is automatically scaled if there is a
change in units.

2. This parameter is automatically included in the


<filename>.contgap.fem file, which is an ASCII
format file generated when CONTPRM,CONTGAP,YES is
used.

1060 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GAPPRM, HMGAPST

Parameter Values Description

HMGAPST NO, 0, YES, or 1 Create HyperMesh command file that defines sets
containing open and closed gaps for the initial set up and
Default = NO for each nonlinear subcase. The file name is
<my_job>.hm.gapstat.cmf.

If NO or 0, then no file is produced.

GAPPRM,HMGAPST,YES can also be used to visualize the


status of internally created CONTACT elements. This
requires the additional command CONTPRM,CONTGAP,YES
– it will create a file, <my_job>.contgap.fem, that
contains contact elements converted to CGAPG entities.
For correct visualization of their open/closed status in
HyperMesh, this file needs to be imported before running
the gap status command file,
<my_job>.HM.gapstat.cmf.

Altair Engineering OptiStruct 13.0 Reference Guide 1061

Proprietary Information of Altair Engineering


GAPPRM, PRTSW

Parameter Values Description

PRTSW NO, 0, YES, or 1 Print diagnostic output for gap elements.

Default = NO If NO or 0, OptiStruct will not output diagnostic


information.

If YES or 1, OptiStruct will print diagnostic information to


the .out file.

1062 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GENEL

Bulk Data Entry

GENEL – General Finite Element

Description

Defines the stiffness or flexibility of a general element connected to an arbitrary number of


grids.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GENEL EID GI1 C I1 GI2 C I2 GI3 C I3

GI4 C I4 GI5 C I5 -etc.-

“UD” GD1 C D1 GD2 C D2 GD3 C D3

GD4 C D4 GD5 C D5 -etc.-

“K” or KZ11 KZ12 KZ13 -etc.- KZ21 KZ22 -etc.-


“Z”

KZ31 KZ32 -etc.-

“S” S11 S12 S13 -etc.- S21 S22 -etc.-

S31 S32 -etc.-

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GENEL 537 1001 1 1001 2 1001 3

1002 1 1002 2 1002 3

Altair Engineering OptiStruct 13.0 Reference Guide 1063

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

K 5757. -816.6 -43.1 -5757. 816.6 43.1 35479.3

-1151. 816.6 - 1151. 6538.6 43.1 1151. -6538.6


35479.3

5757. -816.6 -43.1 35479.3 -1151. 6538.6

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GENEL 4001 1073 1 1073 2 1073 3

1073 4 1073 5 1073 6

UD 1074 1 1074 2 1074 3

1074 4 1074 5 1074 6

Z .592-6 .39-6 .592-6

-.39-6 .1-9

.319-6 .319-6 .1-9

Example 3

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GENEL 435 11 1 23 4 72 0

17 2

1064 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

S 1.7 2.3 3.6 4.4 5.2 6.8 7.1

8.9

K .1 .2 .3 .4 .5 .6 .7

.8

UD 12 2 47 0

Field Contents

EID Unique element identification number.

No default (Integer > 0)

GIi/CIi Grid (or scalar point) and component identification numbers ordered
according to stiffness or flexibility values specified after KZmn. For scalar
points, CIi is zero.

No default (GIi is integer > 0 and CIi is integer > 0).

UD Flag indicating that the subsequent fields and continuation entries contain
values for GDj/CDj until “K”, “Z”, or “S” is specified in field 2 or it is the
end of the entry.

No default (Character)

GDj/CDj Grid (or scalar point) and component identification numbers ordered
according to the columns in the “S” matrix.

No default (GDj is integer > 0 and CDj is integer > 0).

K or Z Flag indicating that the next fields and continuation entries contain
stiffness values until “UD” or “S” is specified in field 2 or it is the end of
the entry.

No default (Character)

KZmn Stiffness or flexibility matrix for degrees-of-freedom in GIi/CIi where “m” is

Altair Engineering OptiStruct 13.0 Reference Guide 1065

Proprietary Information of Altair Engineering


Field Contents

the row number and “n” is the column number. Only the lower triangular
terms in the matrix need to be specified. Zero values must be specified
as blank or 0.0.

Default = 0.0 (Real)

S Flag indicating that the subsequent fields and continuation entries contain
values for the S matrix.

No default (Character)

Sij “S” matrix values where “i” corresponds to GIi/CIi list and “j” corresponds
to GDj/CDj list until “K”, “Z”, or “UD” is specified in field 2 or it is the end
of the entry. All the terms in the matrix must be specified and zero
values must be specified as blank or 0.0.

Default = 0.0 (Real)

Comments

1. GIi/CIi and KZmn are required inputs. Either “K” or “Z” must be specified, but not both.

2. “UD”, “K”, “Z”, and “S”, may be specified in any order as demonstrated in the third
example.

3. “UD” and “S” are optional inputs. “S” defines the motion between the GIi/CIi and GDj/CDj
degrees-of-freedom according to:

But if “S” is specified then GDj/CDj must also be specified. If “S” is not specified then
GDj/CDj may contain six and only six degrees of freedom and they cannot refer to
SPOINTs.

4. If only “K” or “Z” is input without “UD” then it is recommended that the resulting stiffness
represents the unsupported element, containing all of the rigid body modes. If not, then
the “UD” option allows for the reintroduction of the rigid body modes with “S” which is
provided by you or computed internally.

a) If “K” and “UD” are specified then the program will form the complete stiffness as
defined by the following equation:

Where the K matrix is formed from the KZmn values and the S matrix is formed from the
Sij values or computed automatically.

1066 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


b) If “Z” and “UD” are specified then the program will form the complete stiffness as
defined by the following equation:

Where the Z matrix is formed from the KZmn values and the S matrix is formed from the
Sij values or computed automatically. Z must be nonsingular.

5. PARAM,CK3 may be used to scale the stiffness produced by all GENEL elements.

6. All lower triangular values in K and Z and all values in S have to be accounted for in the
input. Zero values may be specified as 0.0 or be left blank, however if all entries in any
continuation line are zero, then at least one visible character must appear on this line (it
can be 0.0 in any field or the plus sign (+) in the first column) because blank lines are
treated as comment. Unused fields (after the last matrix entry) must be blank.

7. General elements are ignored in heat transfer analysis.

Altair Engineering OptiStruct 13.0 Reference Guide 1067

Proprietary Information of Altair Engineering


GRAV

Bulk Data Entry

GRAV – Gravity Vector

Description

Defines the gravity vectors for use in determining gravity loading for the structural model. It
can also be used to define the EXCITEID field (Amplitude “A”) of dynamic loads in RLOAD1,
RLOAD2, TLOAD1 and TLOAD2 bulk data entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GRAV SID C ID G N1 N2 N3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GRAV 3 32.2 0.0 0.0 -1.0

Field Contents

SID Set identification number.

(Integer > 0)

CID Coordinate system identification number.

(Integer > 0)

G Gravity vector scale factor.

N1,N2, N3 Gravity vector components.

(Real; at least one non-zero component)

1068 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. The gravity vector is defined by g = G(N1, N2, N3). The direction of G is the direction of
free fall. N1, N2, and N3 are in coordinate system CID.

2. A CID of zero references the basic coordinate system.

3. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1069

Proprietary Information of Altair Engineering


GRDSET

Bulk Data Entry

GRDSET – Grid Point Default

Description

Defines default options for fields 3, 7, and 8 of all GRID entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GRDSET blank CP blank blank blank CD PS blank

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GRDSET 16 32 3456

Field Contents

CP Identification number of coordinate system in which the location of the grid


point is defined.

(Integer > 0 or blank)

CD Identification number of coordinate system in which displacements are


measured at grid point.

(Integer > 0 or blank)

PS Permanent single-point constraints associated with grid point (any of the


digits 1-6 with no embedded blanks).

(Integer > 0 or blank)

1070 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. The contents of fields 3, 7, or 8 of this entry are assumed for the corresponding fields of
any GRID entry whose field 3, 7, and 8 are blank. If any of these fields on the GRID entry
are blank, the default option defined by this entry occurs for that field. If no permanent
single-point constraints are desired or one of the coordinate systems is basic, the default
may be overridden on the GRID entry by entering zero in the corresponding field. Only
one GRDSET entry may appear in the bulk data section.

2. The primary purpose of this entry is to minimize the burden of preparing data for problems
with a large amount of repetition (for example, two-dimensional pinned-joint problems).

3. At least one of the entries CP, CD, or PS must be non-zero.

4. This card is represented as a control card in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1071

Proprietary Information of Altair Engineering


GRID

Bulk Data Entry

GRID – Grid Point

Description

Defines the location of a geometric grid point of the structural model, the directions of its
displacement, and its permanent single-point constraints.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GRID ID CP X1 X2 X3 CD PS

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GRID 2 3 1.0 -2.0 3.0 316

Field Contents

ID Unique grid point identification number.

(Integer > 0)

CP Identification number of coordinate system in which the location of the grid


point is defined.

(Integer > 0 or blank)

X1,X2,X3 Location of the grid point in coordinate system CP.

(Real)

CD Identification number of coordinate system in which the displacements,


degrees-of-freedom, constraints, and solution vectors are defined at grid
point.

1072 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

(Integer > -1 or blank)

PS Permanent single-point constraints associated with grid point. Up to six


unique digits may be placed in the field with no imbedded blanks.

(Integer > 0 or blank)

See the GRDSET entry for default options for fields 3, 7, and 8.

Comments

1. All grid point identification numbers must be unique with respect to all other structural grid
and scalar points. A duplicate identification number is only allowed if all fields on the
duplicated entries are exactly the same, unless PARAM,DUPTOL is used. PARAM,DUPTOL
can be used to set a tolerance that will allow a GRID with same ID, CP, CD, and PS to
have slightly different coordinates. Refer to Guidelines for Bulk Data Entries.

2. The meaning of X1, X2, and X3 depends on the type of coordinate system, CP, as
follows: (see CORDI entry descriptions).

Type X1 X2 X3

Rectangular X Y Z

Cylindrical R q(degrees) Z

Spherical R q(degrees) f(degrees)

3. The collection of all CD coordinate systems defined on all GRID entries is called the Global
Coordinate System. All degrees-of-freedom, constraints, and solution vectors are
expressed in the Global Coordinate System.

4. If CD = -1, then this defines a fluid grid point in the coupled fluid-structural analysis. This
type of point may only connect the CHEXA, CPENTA, and CTETRA elements to defined
fluid elements.

5. If CP, PS, or CD is blank, information from the GRDSET data will be used. If CP or CD
contains a zero, the basic coordinate system will be used. If PS contains a zero, single
point constraints on the GRDSET data are ignored.

6. Input data replication is available for the GRID data. This can be used to generate
additional GRID data, based on incrementing the GRID ID and coordinate locations.

7. This card is represented as a node in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1073

Proprietary Information of Altair Engineering


GRIDS

Bulk Data Entry

GRIDS – Section Grid Point

Description

Defines a grid point on the y-z plane, using cartesian coordinates, for use in the definition of
arbitrary beam cross-sections.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GRIDS ID Y Z

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GRIDS 101 1.1 2.1

Field Contents

ID Identification number.

No default (Integer > 0)

Y Y location of the grid point.

No default (Real)

Z Z location of the grid point.

No default (Real)

Comments

1. All grid point identification numbers within a section definition must be unique with respect
to all other grid point identification numbers within the same section definition.

2. This entry is only valid when it appears between the BEGIN and END statements.

1074 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GROUND

Bulk Data Entry

GROUND – Ground Body Definition for Multi-body Simulation

Description

Defines a ground body out of a list of finite element properties, elements, and grid points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GROUND BID BODY_NAME

TYPE1 ID1 ID2 ID3 ID4 ID5 ID6 ID7

ID8 …

TYPE2 ID1 ID2 …

TYPE# …

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GROUND 3 SUPPORTING_BEAM

PSHELL 23 21

PBEAM 9 59 48

C ONM2 2345

GRID 400 401 402

Altair Engineering OptiStruct 13.0 Reference Guide 1075

Proprietary Information of Altair Engineering


Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

GROUND 4 ANC HOR

PBAR 10 11 13 15 22 99 88

44

Field Contents

BID Unique body identification number.

No default (Integer > 0)

BODY_NAME Unique body name. The body name for this PRBODY.

Default = OUTFILE_body_<BID> (Character string)

TYPE# Flag indicating that the following list of IDs refer to entities of this
type. All property definitions; CELAS2, CONM2, PLTOEL, RBE2, RBE3,
RBAR, RROD, and GRID are valid types for this field.

No default (PBAR, PBARL, PBEAM, PBEAML, PBUSH, PCOMP, PDAMP,


PELAS, PGAP, PROD, PSHEAR, PSHELL, PSOLID, PVISC, PWELD,
CELAS2, CONM2, PLOTEL, RBE2, RBE3, RBAR, RROD, GRID)

ID# Identification numbers of entities of the preceding TYPE flag.

No default (Integer > 0)

Comments

1. Any number of property definitions; CELAS2, CONM2, PLOTEL, RBAR, RBE2, RBE3, or RROD
elements or grid points can be given.

2. At least one property definition, element, or grid point must be given.

3. A property definition, CELAS2, CONM2, PLOTEL, RBE2, REB3, RBAR, or RROD element or
grid point can only belong to one ground or rigid or flexible body.

4. The grid ID provided in the ground card is considered grounded.

5. This card is represented as a group in HyperMesh.

1076 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


HYBDAMP

Bulk Data Entry

HYBDAMP – Apply Hybrid Damping to the Residual Structure in a Direct or Transient


Frequency Response Analysis

Description

This bulk data entry defines the application of modal damping to the residual structure in a
direct or transient frequency response analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

HYBDAMP SID METHOD SDAMP KDAMP

Field Contents

HYBDAMP Keyword for applying modal damping on a direct analysis

SID Unique hybrid damping SID (Referred to by the HYBDAMP I/O section
data).

METHOD Identification number of EIGRL/EIGRA data. Hybrid damping is applied on


the modes determined by the eigenvalue analysis.

No default (Integer > 0)

SDAMP Identification number of TABDMP1 entry for modal damping.

No default (Integer > 0)

KDAMP If KDAMP is set to -1/YES, modal damping is entered into the complex
stiffness matrix as material damping, instead of viscous damping. The
default is 1/NO to enter the damping as viscous damping.

Default = 1 (Integer)

Comments

1. HYBDAMP SID can be set by the HYBDAMP I/O Options Entry in the I/O section of the input
data.

Altair Engineering OptiStruct 13.0 Reference Guide 1077

Proprietary Information of Altair Engineering


2. Hybrid damping can be defined as shown below:

If KDAMP is set to 1/NO (Default), then:

If KDAMP is set to -1/YES, then:

Where,

are the modes of the structure

[M] is the structural mass matrix

b( ) are the modal damping values

g( ) are equal to twice the critical damping ratios calculated from the TABDMP1 entry

is the natural frequency of mode

mi is the generalized mass of mode

1078 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


INCLUDE

I/O Options and Bulk Data Entry

This bulk data card is identical to the I/O options entry, INCLUDE.

Altair Engineering OptiStruct 13.0 Reference Guide 1079

Proprietary Information of Altair Engineering


INSTNCE

Bulk Data Entry

INSTNCE – Defines part location within the global part

Description

The INSTNCE bulk data entry can be used to define the location of a part in the global
structure. Each INSTNCE entry should reference a unique part name.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

INSTNC E ID name NN

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

INSTNC E 2 C rankShaft 32

Field Contents

ID Set identification number.

(Integer > 0)

name This field specifies the unique name of a part that is to be attached to the
global part (see comment 2). It should match the name of one of the parts
defined using the BEGIN, FEMODEL, name entry.

(Character String)

NN ID of a RELOC bulk data entry. This field defines the actual location of the part
in the final model via the RELOC entry.

Default = Blank (Integer > 0)

1080 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. The full model consists of several parts, one part is designated as global and the rest of
the parts are attached to the global part using INSTNCE entries. The global part can have
an arbitrary name (it is identified by the presence of INSTNCE entries). A minimum of one
INSTNCE entry should always be present in the model.

2. All INSTNCE entries should exist within a global part and no INSTNCE entry can reference
the name of a global part on the “name” field.

3. Each INSTNCE entry should reference a different part name. However, not every part has
to be defined using an INSTNCE entry. Such parts are still contained within the full model
without any relocation.

4. A global part can be moved to a different location, however, this is not recommended as
it may lead to inaccuracies in locating other parts.

Altair Engineering OptiStruct 13.0 Reference Guide 1081

Proprietary Information of Altair Engineering


INVELB

Bulk Data Entry

INVELB – Initial Velocity of a Body

Description

Defines initial velocity in a multi-body situation.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

INVELB SID BID C ID

VX VY VZ WX WY WZ

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

INVELB 1 3

1000.0

Field Contents

SID Load set identification number.

(Integer > 0)

BID Body identification number.

(Integer > 0)

CID Reference coordinate system.

(Integer > 0)

1082 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

VX, VY, VZ Translational velocities.

(Blank or Real)

WX, WY, WZ Rotational velocities.

(Blank or Real)

Comments

1. Only one initial velocity per body can be defined in a load set.

2. A CID of zero or blank references the basic coordinate system.

3. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1083

Proprietary Information of Altair Engineering


INVELJ

Bulk Data Entry

INVELJ – Initial Velocity of a Joint

Description

Defines initial velocity of a joint in a multi-body situation.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

INVELJ SID JID JTYPE VT VR

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

INVELJ 1 3 REV 10.0

Field Contents

SID Load set identification number.

(Integer > 0)

JID Joint identification number.

(Integer > 0)

JTYPE Joint type.

Options = ("REV", "CYL", or "TRANS")

No default

VT Translational velocity

If JTYPE = TRANS, VT must be real.

1084 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

VR Rotational velocity

If JTYPE = REV, VR must be real.

Comments

1. Only one initial velocity per joint can be defined in a load set.

2. Initial velocities of joints defined by INVELJ will be overwritten by MOTNJ, MOTNJE, or


MOTNJC.

Altair Engineering OptiStruct 13.0 Reference Guide 1085

Proprietary Information of Altair Engineering


JOINT

Bulk Data Entry

JOINT – Joint Definition for Multi-body Solution Sequence

Description

Defines a joint.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

JOINT JID JTYPE G1 G2 X3, G3 Y3 Z3 blank

X4, G4 Y4 Z4

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

JOINT 3 BALL 345 231

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

JOINT 4 UNIV 456 899 0.0 0.0 1.0

399

Field Contents

JID Unique joint identification number.

(Integer > 0)

1086 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

JTYPE Joint type

(BALL, FIX, REV, TRANS, CYL, UNIV, CV, PLANAR, INLINE, PERP, PARA,
INPLANE, or ORIENT).

G1, G2 Geometric grid point identification number. Used to identify the bodies
to be connected and, for many JTYPEs, the location of the joint.

(Integer > 0)

X3, Y3, Z3 First orientation vector of the joint.

(Real)

G3 Grid point identification number to optionally supply X3, Y3, Z3 in


conjunction with either G1 or G2 (depending on the JTYPE).

(Integer > 0)

X4, Y4, Z4 Second orientation vector of the joint.

(Real)

G4 Grid point identification number to optionally supply X4, Y4, Z4 in


conjunction with G2.

(Integer > 0)

Comments

1. Joints are only valid in a multi-body solution sequence.

2. G1 and G2 identify the bodies being joined and must, therefore, belong to different bodies.

3. Definition of the different joint types:

Joint Type Description JTYPE Required Joint Orientation


Fields

Ball All translations are BALL G1, G2 · G1 and G2 must


fixed; all rotations coincide.
are free.

Fixed All translations FIX G1, G2 · G1 and G2 must

Altair Engineering OptiStruct 13.0 Reference Guide 1087

Proprietary Information of Altair Engineering


Joint Type Description JTYPE Required Joint Orientation
Fields

and rotations are coincide.


fixed.

Revolute Rotation about a REV G1, G2, · G1 and G2 must


single selected and either coincide.
axis is free; other X3, Y3, · The selected axis is
rotations and Z3 or G3 defined by the vector
translations are X3, Y3, Z3 or
fixed. alternatively the vector
from G1 to G3.

Translational Translation along TRANS G1, G2, · G1 and G2 must be along


a single selected and either the joint axis.
axis is free; other X3, Y3, · The selected axis is
translations and Z3 or G3 defined by the vector
rotations are X3, Y3, Z3 or
fixed. alternatively the vector
from G1 to G3.

Cylindrical Translation along CYL G1, G2, · G1 and G2 must be along


and rotation and either the joint axis.
about a single X3, Y3, · The selected axis is
selected axis is Z3 or G3 defined by the vector
free; other X3, Y3, Z3 or
translations and alternatively the vector
rotations are from G1 to G3.
fixed.

Universal Rotations about UNIV G1, G2, · G1 and G2 must


two selected and either coincide.
perpendicular axes X3, Y3, Z3 · The first selected (cross
are free; or G3 and pin) axis is defined by
translations and either X4, the vector X3, Y3, Z3 or
other rotations Y4, Z4 or alternatively the vector
are fixed. G4 from G1 to G3.
· The second selected
(cross pin) axis is defined
by the vector X4, Y4, Z4
or alternatively the
vector from G2 to G4.
· The selected axes must
be perpendicular.

Constant Vel Rotations about CV G1, G2, · G1 and G2 must coincide.


two selected axes and either · The first selected axis is
are equal and X3, Y3, Z3 defined by the vector
opposite; or G3 and X3, Y3, Z3 or

1088 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Joint Type Description JTYPE Required Joint Orientation
Fields

alternatively the vector


translations and either X4,
from G1 to G3.
other rotations Y4, Z4 or
· The second selected axis
are fixed. G4
is defined by the vector
X4, Y4, Z4 or
alternatively the vector
from G2 to G4.

Planar Translations on a PLANAR G1, G2, · G1 and G2 must be in the


plane defined by a and either joint plane.
selected normal X3, Y3, · The vector X3, Y3, Z3 or
vector and the Z3 or G3 the vector from G1 to G3
rotation about will define the normal to
that normal the plane.
vector are free,
out-of-plane
translations and
rotations are
fixed.

Inline Translation along INLINE G1, G2, · G1 and G2 must be along


a single selected and either the joint axis.
axis and all X3, Y3, · The selected axis is
rotations are free; Z3 or G3 defined by the vector
other translations X3, Y3, Z3 or
are fixed. alternatively the vector
from G2 to G3.

Perpendicular Two perpendicular PERP G1,G2 and · The first selected axis is
axes are selected either X3, defined by the vector
that are always to Y3, Z3 or X3, Y3, Z3 or
remain G3 and alternatively the vector
perpendicular. either X4, from G1 to G3.
Therefore, Y4, Z4 or · The second selected axis
rotations about G4 is defined by the vector
both selected X4, Y4, Z4 or
axes and all alternatively the vector
translations are from G2 to G4.
free. Rotation · The selected vectors
about the cross- must be perpendicular to
product of the one another.
two selected
vectors is fixed.

Parallel Axes Two parallel axes PARA G1,G2 · The first selected axis is
are selected that and either defined by the vector X3,
are always to X3, Y3, Y3, Z3 or alternatively
the vector from G1 to

Altair Engineering OptiStruct 13.0 Reference Guide 1089

Proprietary Information of Altair Engineering


Joint Type Description JTYPE Required Joint Orientation
Fields

remain parallel. Z3 or G3 G3.


Therefore, and either · The second selected axis
rotations about X4, Y4, is defined by the vector
the selected Z4 or G4 X4, Y4, Z4 or
parallel axes and alternatively the vector
all translations are from G2 to G4.
free; other · The selected vectors
rotations are must be parallel to one
fixed. another.

Inplane Two perpendicular INPLANE G1,G2 · The first selected vector


vectors are and either is defined by X3, Y3, Z3
selected that X3, Y3, or alternatively the
describe a plane. Z3 or G3 vector from G2 to G3.
Out-of-plane and either · The second selected
translations are X4, Y4, vector is defined by X4,
fixed; all other Z4 or G4 Y4, Z4 or alternatively
translations and the vector from G2 to
rotations are free. G4.
· The selected vectors
must be perpendicular to
one another.

Orient All rotations are ORIENT G1,G2


fixed; all
translations are
free.

4. This card is represented as a joint element in HyperMesh.

1090 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


JOINTM

Bulk Data Entry

JOINTM – Joint Definition for Multi-body Solution Sequence using Marker

Description

Defines a joint using two grids which have a marker card associated with them.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

JOINTM JID JTYPE M1 M2

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

JOINTM 3 BALL 345 231

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

JOINTM 4 UNIV 456 899

Field Contents

JID Unique joint identification number.

(Integer > 0)

JTYPE Joint type

(BALL, FIX, REV, TRANS, CYL, UNIV, CV, PLANAR, INLINE, PERP, PARA,
INPLANE, or ORIENT)

Altair Engineering OptiStruct 13.0 Reference Guide 1091

Proprietary Information of Altair Engineering


Field Contents

M1, M2 Marker identification numbers.

(Integer > 0)

Comments

1. Joints are only valid in a multi-body solution sequence.

2. M1 and M2 must belong to different bodies and must have a marker card associated with
them.

3. Definition of the different joint types:

Joint Type JTYPE Definition Joint Orientation

Ball BALL M1, M2 · M1, M2 must coincide.

Fixed FIX M1, M2 · M1, M2 must coincide.

Revolute REV M1, M2 · M1, M2 must coincide.


· The joint axis will be along the
Z-axis of marker M1.

Translational TRANS M1, M2 · M1, M2 must be along the joint


axis.
· The joint axis will be along the
Z-axis of marker M1.

Cylindrical CYL M1, M2 · M1, M2 must be along the joint


axis.

Universal UNIV M1, M2 · M1, M2 must coincide.

Constant CV M1, M2 · M1, M2 must coincide.


Velocity

Planar PLANAR M1, M2 · M1, M2 must be in the joint


plane.

Inline INLINE M1, M2

Perpendicular PERP M1, M2

Parallel Axes PARA M1, M2

Inplane INPLANE M1, M2

1092 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Joint Type JTYPE Definition Joint Orientation

Orient ORIENT M1, M2 No relative rotation.

Altair Engineering OptiStruct 13.0 Reference Guide 1093

Proprietary Information of Altair Engineering


LINE

Bulk Data Entry

LINE – Line Definition

Description

Definition of a line.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

LINE LINEID EDGE

GA1 GB1

GA2 GB2

GA3 GB3

... ...

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

LINE 100 EDGE

33 34

34 35

35 36

1094 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Alternate Format

In this format, line is represented as collection of 1-D, 2-D or 3-D elements.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

LINE LINEID ELEDGE

EID1 EID2 EID3 EID4 EID5 EID6 EID7 EID8

EID9 -etc-

Alternate Format (SET)

In this format, a line is defined by a SET of elements. With this approach, the line is composed
of all the edges of all selected 1-D, 2-D or 3-D elements in the SET.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

LINE LINEID SET SID

Field Contents

LINEID Non-unique identification number of LINE.

No default (Integer > 0)

EDGE Flag indicating that a line is defined by two grids.

GA# Grid point identification number of first grid A.

No default (Integer > 0)

GB# Grid point identification number of second grid B.

No default (Integer > 0)

ELEDGE Flag indicating that the line is composed of elements.

EID# Element identification number.

No default (Integer > 0)

SET Flag indicating that the line is defined by a SET of elements.

Altair Engineering OptiStruct 13.0 Reference Guide 1095

Proprietary Information of Altair Engineering


Field Contents

SID Set identification number.

No default (Integer > 0)

Comments

1. LINEID is not unique, multiple LINE cards with the same LINEID compose a line group.

2. GA and GB should be two different grids.

3. All nodes must belong to a shell, solid, truss or beam element.

4. This card is represented as a contactsurf in HyperMesh.

1096 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


LOAD

Bulk Data Entry

LOAD – Static Load Combination (Superposition)

Description

Defines a static load as a linear combination of load sets defined via FORCE, MOMENT,
FORCE1, MOMENT1, PLOAD, PLOAD1, PLOAD2, PLOAD4, RFORCE, DAREA and GRAV entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

LOAD SID S S1 L1 S2 L2 S3 L3

S4 L4 -etc-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

LOAD 101 -0.5 1.0 3 6.2 4

Field Contents

SID Load set identification number.

(Integer > 0)

S Scale factor.

(Real)

Si Scale factors.

(Real)

Li Load set identification numbers defined via entry typed enumerated above.

(Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1097

Proprietary Information of Altair Engineering


Comments

1. The load vector defined is given by

2. The Li must be unique.

3. All data after the first blank field is ignored.

4. Load sets must be selected in the Subcase Information section (LOAD=SID) if they are to
be applied to the structural model.

5. A LOAD entry may not reference a set identification number defined by another LOAD
entry.

6. SPCD load SIDs cannot be referenced by LOAD data.

7. This card is represented as a loadcollector in HyperMesh.

1098 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


LOADADD

Bulk Data Entry

LOADADD – Static Load Combination (Superposition)

Description

Defines a static load as a linear combination of load sets defined via FORCE, MOMENT,
FORCE1, MOMENT1, PLOAD, PLOAD1, PLOAD2, PLOAD4, RFORCE, DAREA, and GRAV entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

LOADADD SID S S1 L1 S2 L2 S3 L3

S4 L4 -etc-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

LOADADD 101 -0.5 1.0 3 6.2 4

Field Contents

SID Load set identification number.

(Integer > 0)

S Scale factor (See comment 1).

(Real)

Si Scale factors (See comment 1).

(Real)

Li Load set identification numbers defined via entry typed enumerated above

Altair Engineering OptiStruct 13.0 Reference Guide 1099

Proprietary Information of Altair Engineering


Field Contents

(See comment 1).

(Integer > 0)

Comments

1. The load vector defined is given by:


r r
P S i
Si PLi

Where,
r
P is the static load as a linear combination of the defined load sets.

S is the scale factor defined in Field 3.

Si
are the scale factors defined in the S1, S2,…, Sn fields.
r
PLi
are the loads, whose id’s, are referenced by the L1, L2,…, Ln fields.

2. The Load Set identification numbers (Li) must be unique.

3. All data after the first blank field is ignored.

4. Load sets must be selected in the Subcase Information section (LOAD=SID) if they are to
be applied to the structural model.

5. A LOADADD entry may not reference a set identification number defined by another
LOADADD entry.

6. Only a single thermal load can be referenced by the LOADADD data.

7. SPCD load SIDs cannot be referenced by LOADADD data.

8. This card is represented as a loadcollector in HyperMesh.

1100 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MARKER

Bulk Data Entry

MARKER – Define a Marker by Associating a Grid and a Coordinate System

Description

Define a marker by associating a grid and a coordinate system.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MARKER MID1 GID1 C ID1 MID2 GID2 C ID2

MID3 GID3 C ID3 … … …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MARKER 3 345 123

Field Contents

MIDi Marker identification number.

(Integer > 0)

GIDi Grid identification number.

(Integer > 0)

CIDi Coordinate system identification number.

(Integer > 0 or blank)


Default (Blank, defaults to basic coordinate system)

Altair Engineering OptiStruct 13.0 Reference Guide 1101

Proprietary Information of Altair Engineering


Comments

1. Each marker has a unique ID. The marker gets its location from the grid corresponding to
the GID and the orientation from the coordinate system (CID).

2. Multiple markers can be located at the same grid with the same or with a different CID.

3. This card is represented as a sensor in HyperMesh.

1102 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MAT1

Bulk Data Entry

MAT1 – Material Property Definition, Form 1

Description

Defines the material properties for linear, temperature-independent, and isotropic materials.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT1 MID E G NU RHO A TREF GE

ST SC SS

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT1 17 3.+7 0.33 4.28

Field Contents

MID Unique material identification number.

No default (Integer > 0)

E Young’s Modulus.

Default = blank (Real or blank)

G Shear Modulus.

Default = blank (Real or blank)

NU Poisson’s Ratio.

Default = blank (-1.0 < Real < 0.5 or blank)

Altair Engineering OptiStruct 13.0 Reference Guide 1103

Proprietary Information of Altair Engineering


Field Contents

RHO Mass density.

No default (Real)

A Thermal expansion coefficient.

No default (Real)

TREF Reference temperature for thermal loading.

Default = 0.0 (Real)

GE Structural Element Damping coefficient. See comments 11 and 12.

No default (Real)

ST, SC, SS Stress limits in tension, compression and shear. Used for composite ply
failure calculations

No default (Real)

Comments

1. The material identification number must be unique for all MAT1, MAT2, MAT8 and MAT9
entries.

2. The mass density, RHO, is used to automatically compute mass for all structural elements.

3. Either E or G must be specified (that is, nonblank).

4. If any one of E, G, or NU is blank, it is computed to satisfy the identity

E = 2(1+NU)G; otherwise, values supplied by you are used.

5. If E and NU are both blank, they are both given the value 0.0.

6. If G and NU are both blank, they are both given the value 0.0.

7. Implausible data on one or more MAT1 entries result in a warning message. Implausible
data is defined as:

E < 0.0 or

G < 0.0 or

NU > 0.5 or

NU < -1.0 or

1104 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


except for cases covered by comments 5 and 6.

8. It is strongly recommended that only two of the three values E, G, and NU be input.

9. A warning is issued if NU < 0.0.

10. The large field format may also be used.

11. To obtain the damping coefficient GE, multiply the critical damping ratio, C/C0 by 2.0.

12. TREF and GE are ignored if a MAT1 entry is referenced by a PCOMP entry.

13. This card is represented as a material in HyperMesh.

Element Type E NU G

CROD, CBAR, CBEAM, Axial and N/A Transverse Shear


and CWELD Bending and Torsion

CSHEAR N/A N/A Shear

Membrane Membrane
CQUAD and CTRIA Transverse Shear
and Bending and Bending

CHEX, CTETRA,
CPENTA, CPRYRA and Deformation N/A
CSEAM

Altair Engineering OptiStruct 13.0 Reference Guide 1105

Proprietary Information of Altair Engineering


MAT2

Bulk Data Entry

MAT2 – Material Property Definition, Form 2

Description

Defines the material properties for linear, temperature-independent, anisotropic materials for
two-dimensional elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT2 MID G11 G12 G13 G22 G23 G33 RHO

A1 A2 A12 TREF GE ST SC SS

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT2 13 6.2+3 6.2+3 5.1+3 0.056

6.5-6 6.5-6 -500.0

Field Contents

MID Unique material identification number.

No default (Integer > 0)

Gij The material property matrix.

No default (Real)

RHO Mass density.

No default (Real)

1106 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Ai Thermal expansion coefficient vector.

No default (Real)

TREF Reference temperature for the calculation of thermal loads. See comment
6.

Default = blank (Real or blank)

GE Structural Element Damping Coefficient. See comments 7 and 8.

No default (Real)

ST, SC, SS Stress limits in tension, compression and shear. Used for composite ply
failure calculations.

No default (Real)

Comments

1. The material identification number must be unique for all MAT1, MAT2, MAT8 and MAT9
entries.

2. The mass density, RHO, is used to automatically compute mass for all structural elements.

3. The convention for the Gij in fields 3 through 8 are represented by the matrix relationship:

4. If this entry is referenced by the MID3 field (transverse shear) on the PSHELL, G13, G23,
and G33 must be blank.

5. Unlike the MAT1 entry, data from the MAT2 entry is used directly, without adjustment of
equivalent E, G, or NU values.

6. TREF is used as the reference temperature for the calculation of thermal loads.

7. The long field format may be used.

8. To obtain the damping coefficient GE, multiply the critical damping ratio, C/C0, by 2.0.

9. TREF and GE are ignored if a MAT 2 entry is referenced by a PCOMP entry.

Altair Engineering OptiStruct 13.0 Reference Guide 1107

Proprietary Information of Altair Engineering


10. If a MAT2 card is pointed to by a MID4 on PSHELL, and has a material ID greater than
400,000,000, then the thermal membrane-bending coefficients A1, A2, and A12 have a
modified interpretation, and represent [G]*[alpha] rather then [alpha]. Here, [G] is a
matrix composed of G11, G22 …G33. This is to maintain consistency with respective
terms generated internally by the PCOMP card.

11. This card is represented as a material in HyperMesh.

1108 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MAT3

Bulk Data Entry

MAT3 – Material Property Definition, Form 3

Description

Defines the material properties for linear, temperature-independent, and orthotropic materials
used by the CTAXI and CTRIAX6 axisymmetric elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT3 MID EX ETH EZ NUXTH NUTHZ NUZX RHO

GZX AX ATH AZ TREF GE

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT3 17 3.0+7 3.1+7 3.2+7 0.33 0.28 0.30 2.0e-5

7.0+6 1.1e-4 1.1e-4 1.2e-4 35.5 0.19

Field Contents

MID Unique material identification number.

No default (Integer > 0)

EX, ETH, Young’s Moduli in the x, θ and z directions, respectively.


EZ
No default (Real > 0.0)

NUXTH, Poisson’s Ratios:


NUTHZ,
NUZX NUXTH = Poisson’s Ratio for strain in the θ direction when stress in the x

Altair Engineering OptiStruct 13.0 Reference Guide 1109

Proprietary Information of Altair Engineering


Field Contents

direction.
NUTHZ = Poisson’s Ratio for strain in the z direction when stress in the θ
direction.
NUZX = Poisson’s Ratio for strain in the x direction when stress in the z
direction.
No default (Real)

RHO Mass density.

No default (Real)

GZX Shear Modulus in the x-z plane.

No default (Real > 0.0)

AX, ATH, Thermal expansion coefficient in the x, θ, and z directions, respectively.


AZ
No default (Real)

TREF Reference temperature for thermal loading.

Default = blank (Real or blank)

GE Structural Element Damping coefficient. See comment 6.

No default (Real)

Comments

1. The material identification number must be unique for all MAT1, MAT2, MAT8 and MAT9
entries.

2. Values of all seven elastic constants, EX, ETH, EZ, NUXTH, NUTHZ, NUZX and GZX must
be present.

3. A warning is issued if absolute value of NUXTH or NUTHZ is greater than 1.0.

4. The x, θ and z directions are principal material directions of the material coordinate
system. Each element (that is a CTAXI or CTRIAX6 element) supporting the use of MAT3
contains a “Theta” field to relate the principal material directions to the basic coordinate
system.

5. The strain-stress relationship is:

1110 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Note that the strain and stress here are both defined in the material coordinate system.

6. To obtain the damping coefficient GE, multiply the critical damping ratio, C/C0, by 2.0.

7. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1111

Proprietary Information of Altair Engineering


MAT4

Bulk Data Entry

MAT4 – Material Property Definition, Form 4

Description

Defines constant thermal material properties for conductivity, density, and heat generation.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT4 MID K CP RHO H HGEN

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT4 24 200 2e5

Field Contents

MID Material identification number.

No default (Integer > 0)

K Thermal conductivity.

Default = 0.0 (Real > 0.0)

CP Heat capacity per unit mass (specific heat).

(Real > 0.0 or blank)

RHO Density.

Default = 1.0 (Real > 0.0)

H Free convection heat transfer coefficient.

Default = 0.0 (Real)

1112 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

HGEN Heat generation capability used with QVOL entries. HGEN is the scale factor
used with QVOL (See comment 3).

Default = 1.0 (Real > 0.0)

Comments

1. The material identification number may be the shared with structural material property
definitions (MAT1, MAT2, MAT8, MAT9 or MGASK) but must be unique with respect to
other thermal material property definitions (MAT4 or MAT5).

2. MAT4 may specify material properties for any conduction elements. MAT4 also provides
the heat transfer coefficient for free convection (see CONV).

3. HGEN is the scale factor and QVOL is the power generated per unit volume, Pin = volume *
HGEN * QVOL.
4. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1113

Proprietary Information of Altair Engineering


MAT5

Bulk Data Entry

MAT5 – Material Property Definition, Form 5

Description

Defines the thermal material properties for anisotropic materials.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT5 MID KXX KXY KXZ KYY KYZ KZZ CP

RHO HGEN

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT5 2 .300 100 200

2e5

Field Contents

MID Material identification number.

No default (Integer > 0)

Kij Thermal conductivity.

Default = 0.0 (Real)

CP Heat capacity per unit mass (specific heat).

(Real > 0.0 or blank)

RHO Density.

Default = 1.0 (Real > 0.0)

1114 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

HGEN Heat generation capability used with QVOL entries. HGEN is the scale factor
used with QVOL (See comment 3).

Default = 1.0 (Real > 0.0)

Comments

1. The material identification number may be the shared with structural material property
definitions (MAT1, MAT2, MAT8, MAT9 or MGASK), but must be unique with respect to
other thermal material property definitions (MAT4 or MAT5).

2. The thermal conductivity matrix has the following form:

3. HGEN is the scale factor and QVOL is the power generated per unit volume, Pin = volume *
HGEN * QVOL.
4. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1115

Proprietary Information of Altair Engineering


MAT8

Bulk Data Entry

MAT8 – Material Property Definition, Form 8

Description

Defines the material properties for linear temperature-independent orthotropic material for
two-dimensional elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT8 MID E1 E2 NU12 G12 G1,Z G2,Z RHO

A1 A2 TREF Xt Xc Yt Yc S

GE F12 STRN

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT8 171 30.+6 1.+6 0.3 2.+6 3.+6 1.5+6 0.056

28.-6 1.5-6 155.0

Field Contents

MID Material ID.

No default (Integer > 0)

E1 Modulus of elasticity in longitudinal direction (also defined as fibre direction or 1-


direction) (See comment 8)

1116 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

E2 Modulus of elasticity in lateral direction (also defined as matrix direction or 2-


direction) (See comment 8).

NU12
Poisson’s ratio ( for uniaxial loading in 1-direction). Note that for
uniaxial loading in 2-direction is related to by the relation
.

No default (Real)

G12 Inplane shear modulus.

No default (Real > 0.0)

G1,Z Transverse shear modulus for shear in 1-Z plane.

Default = blank (Real > 0.0 or blank)

G2,Z Transverse shear modulus for shear in 2-Z plane.

Default = blank (Real > 0.0 or blank)

RHO Mass density.

No default (Real)

A1 Thermal expansion coefficient in 1-direction.

No default (Real)

A2 Thermal expansion coefficient in 2-direction.

No default (Real)

TREF Reference temperature for the calculation of thermal loads. See comment 3.

Default = blank (Real or blank)

Xt, Xc, Allowable stresses or strains in the longitudinal and lateral directions. Used for
Yt, Yc composite ply failure calculations.

Altair Engineering OptiStruct 13.0 Reference Guide 1117

Proprietary Information of Altair Engineering


Field Contents

No default (Real > 0.0)

S Allowable for in-plane shear for composite ply failure calculations.

No default (Real > 0.0)

GE Structural Element Damping Coefficient. See comment 6.

No default (Real)

F12 Tsai-Wu interaction term for composite failure.

No default (Real)

STRN Indicates whether Xt, Xc, Yt, or Yc are stress or strain allowables.

Default = blank (Real = 1.0 for strain allowables, blank for stress allowables)

Comments

1. The material identification number must be unique for all MAT1, MAT2, MAT8 and MAT9
entries.

2. If G1, Z and G2, Z values are specified as zero or are not supplied, a penalty term is used
to enforce very high transverse shear stiffness.

3. An approximate value for G1, Z and G2, Z is the inplane shear modulus G12. If test data
not available to accurately determine G1, Z and G2, Z for the material and transverse
shear calculations, the value of G12 may be supplied for G1, Z and G2, Z.

4. TREF is used as the reference temperature for calculations of thermal loads.

5. Long field format can be used.

6. TREF and GE are ignored if a MAT8 entry is referenced by a PCOMP entry.

7. The option of interpreting Xt, Xc, Yt, and Yc as strains is only available for composite
definitions (PCOMP or PCOMPG) using the STRN failure criterion. In this case, the STRN
flag indicates whether Xt, Xc, Yt, and Yc are stress or strain allowables.

For all other failure criteria Xt, Xc, Yt, and Yc are always interpreted as stresses,
regardless of the value of the STRN flag.

8. The value of E1 should be greater than that of E2 for the material to be stable. If E1 <
E2, then the material matrix becomes indefinite leading to an unstable material.

9. This card is represented as a material in HyperMesh.

1118 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MAT9

Bulk Data Entry

MAT9 – Material Property Definition, Form 9

Description

Defines the material properties for linear, temperature-independent, and anisotropic materials
for solid elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT9 MID G11 G12 G13 G14 G15 G16 G22

G23 G24 G25 G26 G33 G34 G35 G36

G44 G45 G46 G55 G56 G66 RHO A1

A2 A3 A4 A5 A6 TREF GE

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT9 17 6.2+3 6.2+3

6.2+3

5.1+3 5.1+3 5.1 + 3 3.2 6.5 - 6

6.5-6 125.

Field Contents

MID Unique material identification number.

Altair Engineering OptiStruct 13.0 Reference Guide 1119

Proprietary Information of Altair Engineering


Field Contents

No default (Integer > 0)

Gij The material property matrix.

No default (Real)

RHO Mass density.

No default (Real)

Ai Thermal expansion coefficient vector.

No default (Real)

TREF Reference temperature for the calculation of thermal loads. See comment 6.

Default = blank (Real or blank)

GE Structural Element Damping Coefficient. See comment 9.

No default (Real)

Comments

1. The material identification number must be unique for all MAT1, MAT2, MAT8, MAT9ORT
and MAT9 entries.

2. The mass density, RHO, is used to automatically compute mass for all structural elements.

3. The convention for the Gij in fields 3 through 8 are represented by the matrix relationship.

The subscripts 1 to 6 refer to x, y, z, xy, yz, and zx of the material coordinate system
defined by the CORDM field on the PSOLID entry.

4. Unlike the MAT1 entry, data from the MAT9 entry is used directly, without adjustment of
equivalent E, G, or NU values.

1120 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


5. If material data is to specified with the Engineering Constants E1, E2, E3, NU12, NU13,
NU23, G12, G23, and G13, then use the MAT9ORT data.

6. TREF is used as the reference temperature for the calculation of thermal loads.

7. The last continuation is optional.

8. Long field format can be used.

9. To obtain the damping coefficient GE, multiply the critical damping ratio, C/C0, by 2.0.

10. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1121

Proprietary Information of Altair Engineering


MAT9ORT

Bulk Data Entry

MAT9ORT – Material Property Definition, Form 9-Orthotropic

Description

Defines the material properties for linear, temperature-independent, and orthotropic materials
for solid elements in terms of engineering constants.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT9ORT MID E1 E2 E3 NU12 NU23 NU31 RHO

G12 G23 G31 A1 A2 A3 TREF GE

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT9ORT 21 1e6 1e3 1e3 0.1 0.1 1e5

1e3 1e3 1e-6 1e-6 1e-6

Field Contents

MID Material identification number. Must be unique with respect to other MAT1,
MAT2, MAT8, MAT9, and MAT9ORT definitions

No default (Integer > 0)

E1 Elastic modulus in 1-direction.

No default (Real)

E2 Elastic modulus in 2-direction.

No default (Real)

1122 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

E3 Elastic modulus in 3-direction.

No default (Real)

NU12 Poisson’s ratio for uniaxial loading in 1-direction. See comment 3.

No default (Real)

NU23 Poisson’s ratio for uniaxial loading in 2-direction. See comment 3.

No default (Real)

NU31 Poisson’s ratio for uniaxial loading in 3-direction. See comment 3.

Default = NU23 (Real)

RHO Mass density.

No default (Real)

G12 Shear modulus on plane 1-2.

G23 Shear modulus on plane 2-3.

G31 Shear modulus on plane 3-1.

Ai Coefficient of thermal expansion in the i-direction

Default =0.0 (Real)

TREF Reference temperature for the calculation of thermal loads. See comment 5.

Default = blank (Real or blank)

GE Structural Element Damping Coefficient. See comment 6.

Default = 0.0 (Real)

Comments

1. This input definition is internally converted to an equivalent MAT9 definition on reading


(See comment 7). This is reflected in echoed (ECHO) input data and all messaging.

Altair Engineering OptiStruct 13.0 Reference Guide 1123

Proprietary Information of Altair Engineering


2. The material identification number must be unique for all MAT1, MAT2, MAT8, MAT9 and
MAT9ORT entries.

3. In general, is not the same as , but they are related by .

Furthermore, material stability requires that:

and

4. It may be difficult to find all nine orthotropic constants. In some practical problems, the
material properties may be reduced to normal anisotropy in which the material is isotropic
in a plane (for example, plane 1-2), and has different properties in the direction normal to
this plane.

In the plane of isotropy, the properties are reduced to:

with and

There are five independent material constants for normal anisotropy


.

In case the material has a planar anisotropy, in which the material is orthotropic only in a
plane, the elastic constants are reduced to seven .

5. TREF is used as the reference temperature for the calculation of thermal loads.

6. To obtain the damping coefficient GE, multiply the critical damping ratio, C/C0 by 2.0.

7. Internal conversion from MAT9ORT to MAT9. The material property fields of the MAT9
entry are calculated internally from the MAT9ORT entry using the following formula:

1124 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Where,

The values of , E and G for the expressions in the above equations in comment 7 are
taken from the NUij , Ei and Gij fields respectively of this MAT9ORT entry where i, j €
{1,2,3} and the values of (see above equations
in comment 7) are used to populate the G11, G22, G33, G44, G55, G66, G12, G13, and G23
fields (G12=G21, G13=G31 and G23=G32 due to symmetry) of the MAT9 entry. The
remaining elements of the MAT9 entry (that is G14, G15, G24, and so on) are equal to
zero.

Altair Engineering OptiStruct 13.0 Reference Guide 1125

Proprietary Information of Altair Engineering


MAT10

Bulk Data Entry

MAT10 – Material Property Definition, Form 10

Description

Defines material properties for fluid elements in coupled fluid-structural analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT10 MID BULK RHO C GE ALPHA

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT10 2 0.5 22.1

Field Contents

MID Material identification number.

No default (Integer > 0)

BULK Bulk modulus.

No default (Real > 0.0)

RHO Mass density.

No default (Real > 0.0)

C Speed of sound.

No default (Real > 0.0)

GE Fluid element damping coefficient.

No default (Real)

1126 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

ALPHA
Normalized porous material damping coefficient. See comment 6.

No default (Real)

Comments

1. MAT10 may be referenced by PSOLID entries with FCTN=’PFLUID’.

2. The material identification number must be unique with respect to MAT1, MAT2, MAT3,
MAT9, and MAT10 entries, but may be shared with MAT4, MAT5 or MATFAT.

3. The mass density RHO will be used to compute the mass automatically.

4. BULK, RHO, and C are related by BULK = C2 * RHO.

Two out of the three must be specified, and the other will be calculated according to this
equation.

5. To obtain the damping coefficient GE, multiply the critical damping ratio C/C0 by 2.0.

6. Since the admittance is a function of frequency, the value of ALPHA should be chosen for
the frequency range of interest for the analysis.

7. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1127

Proprietary Information of Altair Engineering


MATFAT

Bulk Data Entry

MATFAT - Fatigue Material Data

Description

Defines material properties for fatigue analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATFAT MID UNIT

STATIC YS UTS

Optional continuation lines for SN fatigue properties:

SN SR1 b1 Nc1 b2 FL SE

Optional continuation lines for EN fatigue properties:

EN Sf b c Ef np Kp Nc

SEe SEp

Optional continuation lines for factor of safety (FOS) analysis:

FOS Tfl Hss

Field Contents

MID Material identification number that matches the identification number on a


MAT1 bulk data entry.

No default (Integer > 0)

UNIT Defines the units of stress values specified on the YS, UTS, SRI1, FL, Sf, and
Kp fields

Default = MPa (MPa, PA, PSI, or KSI)

1128 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

STATIC STATIC flag indicates that static material properties are defined in the following
fields.

YS Yield strength. See comment 1.

(Real > 0.0, or blank)

UTS Ultimate tensile strength. See comment 1.

(Real > 0.0, or blank)

SN SN flag indicating that fatigue material properties for SN analysis are following.

SRI1 Fatigue strength coefficient. It is the stress range intercept of SN curve at 1


cycle in log-log scale.

No default (Real > 0.0)

b1 The first fatigue strength exponent. It is the slope of the first segment of SN
curve in log-log scale.

No default (Real < 0.0)

Nc1 In one-segment S-N curve, this is the cycle limit of endurance (see NC1 in
Figure 1).

In two-segment S-N curve, this is the transition point (see NC1 in Figure 2).

No default (Real > 1000.0)

b2 The second fatigue strength exponent. It is the slope of the second segment
of SN curve in log-log scale.

Default = 0.0 (Real < 0.0)

FL Fatigue Limit; No damage occurs if the stress range is less than FL (see FL in
Figures 1 and 2). See comment 6.

(Real > 0.0, or blank)

SE Standard Error of Log(N).

Default = 0.0 (Real > 0.0)

EN EN flag indicating that fatigue material properties for EN analysis are following.

Sf Fatigue strength coefficient.

No default (Real > 0.0)

Altair Engineering OptiStruct 13.0 Reference Guide 1129

Proprietary Information of Altair Engineering


Field Contents

b Fatigue strength exponent.

No default (Real < 0.0)

c Fatigue ductility exponent.

No default (Real < 0.0)

Ef Fatigue ductility coefficient.

No default (Real > 0.0)

np Cyclic strain-hardening exponent.

No default (Real > 0.0)

Kp Cyclic Strength coefficient.

No default (Real > 0.0)

Nc Reversal limit of endurance. One cycle contains two reversals. See comment
6.

Default = 2.0E8 (Real > 1.0E5)

SEe Standard Error of Log(N) from elastic strain.

Default = 0.0 (Real > 0.0)

SEp Standard Error of Log(N) from plastic strain.

Default = 0.0 (Real > 0.0)

FOS The FOS flag indicates that material properties for factor of safety analysis are
defined in the following fields.

Tfl Torsion fatigue limit.

No default (Real > 0.0)

Hss Hydrostatic stress sensitivity.

No default (Real > 0.0)

1130 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Figures

Figure 1a: One-segment S-N curve in log-log scale Figure 1b: One-segment S-N curve in log-log scale
(b2=0) (b2=0)
(Nc1 is not defined or less conservative than FL) (FL is not defined or less conservative than Nc1)

Figure 2: Two-segment S-N curve in log-log scale

Altair Engineering OptiStruct 13.0 Reference Guide 1131

Proprietary Information of Altair Engineering


Figure 3: E-N curve in log-log scale

Comments

1. UTS or YS is used in mean stress correction (SN) and surface finish correction (SN and
EN). If both UTS and YS are defined, UTS will be used. It is not allowed that both UTS
and YS are blanks.

2. S-N data defined in the MATFAT card is expected to be obtained from standard
experiments that are fully reversed bending on mirror-polished specimens.

3. S-N curves are defined in Stress range – Cycle form. Stress range is the algebraic
difference between the maximum and minimum stress in a cycle. SN curve is expressed
as:

Where S r is the stress range, SRI1 is the fatigue strength coefficient, is the cycle
number, is the fatigue strength exponent.

4. E-N curves are defined in Strain amplitude - Reversal form. Strain amplitude is half of the
algebraic difference between the maximum and minimum strain in a cycle, and one strain
cycle contains two reversals. EN curve is expressed as:

Where, is the strain amplitude, is the fatigue strength coefficient, E is the Young's

modulus, is the cycle number, is the fatigue strength exponent, is the fatigue

1132 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


ductility coefficient, and is the fatigue ductility exponent.

5. Empirical formula can be used to estimate SN/EN data from ultimate tensile strength
(UTS) and Young’s modulus (E):

Table 1* Estimated S-N data from empirical formula


(* Source: Yung-Li Lee, Jwo. Pan, Richard B. Hathaway and Mark E. Barekey. Fatigue testing and
analysis: Theory and practice, Elsevier, 2005)

Table 2**. Estimate E-N data from UTS and E


(** Source: Anton Baumel and T. Seeger, Materials Data for C yclic Loading, Elsevier, 1990)

6. For one-segment SN curve (b2=0.0), if FL is blank, the fatigue limit is the stress range at
Nc1. If both Nc1 and FL are defined, the more conservative value (larger damage) will be
used (Figure 1).

For two-segment SN curve, if FL is blank, the fatigue limit is 0.0.

When fatigue optimization is performed, fatigue limit FL of S-N data and reversal limit Nc
of E-N data will be ignored in order to get continuous changes in fatigue results when
stress/strain changes.

7. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1133

Proprietary Information of Altair Engineering


MATF1

Bulk Data Entry

MATF1 – Isotropic Material Frequency Dependence

Description

Specifies frequency-dependent material properties on MAT1 entry fields via TABLEDi entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATF1 MID T(E) T(G) T(NU) T(RHO) T(A) T(GE)

T(ST) T(SC ) T(SS)

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATF1 17 32 17 53

Field Contents

MID Material property identification number that matches the identification


number on the MAT1 entry.

(Integer > 0)

T(E) Identification number of a TABLEDi entry for the Young’s modulus.

(Integer > 0 or blank)

T(G) Identification number of a TABLEDi entry for the shear modulus.

(Integer > 0 or blank)

T(NU) Identification number of a TABLEDi entry for the Poisson’s ratio.

(Integer > 0 or blank)

1134 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

T(RHO) Identification number of a TABLEDi entry for the mass density.

(Integer > 0 or blank)

T(A) Identification number of a TABLEDi entry for the thermal expansion


coefficient.

(Integer or blank)

T(GE) Identification number of a TABLEDi entry for the damping coefficient.

(Integer > 0 or blank)

T(ST) Identification number of a TABLEDi entry for the tension stress limit.

(Integer > 0 or blank)

T(SC) Identification number of a TABLEDi entry for the compression limit.

(Integer > 0 or blank)

T(SS) Identification number of a TABLEDi entry for the shear limit.

(Integer > 0 or blank)

Comments

1. Fields 3, 4, and so on of this entry correspond, field-by-field, to fields 3, 4, and so on of


the MAT1 entry referenced in field 2. The value in a particular field of the MAT1 entry is
replaced or modified by the table referenced in the corresponding field of this entry. In
the example shown, E is modified by TABLEDi 32, RHO is modified by TABLEDi 17 and GE is
modified by TABLEDi 53. Blank or zero entries mean that there is no frequency
dependence of the field on the MAT1 entry.

2. The MATF1 entries may refer to blank entries on the respective MAT1 card. In this case,
they will be applied to default values of respective parameters. Initial values of E, G, or
NU will be supplied according to comment 4 on the MAT1 entry.

3. Table references must be present for each item that is frequency dependent. For
example, it is not sufficient to only give table references for fields 3 and 4 (Young’s
modulus and shear modulus) if density is also frequency dependent.

4. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1135

Proprietary Information of Altair Engineering


MATF2

Bulk Data Entry

MATF2 – Anisotropic Material Frequency Dependence

Description

Specifies frequency-dependent material properties on MAT2 entry fields via TABLEDi entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATF2 MID T(G11) T(G12) T(G13) T(G22) T(G23) T(G33) T(RHO)

T(A1) T(A2) T(A3) T(GE) T(ST) T(SC ) T(SS)

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATF2 17 32 15 44

62

Field Contents

MID Material property identification number that matches the identification


number on the MAT2 entry.

(Integer > 0)

T(Gij) Identification number of a TABLEDi entry for the shear modulus.

(Integer > 0 or blank)

T(RHO) Identification number of a TABLEDi entry for the mass density.

(Integer > 0 or blank)

T(Ai) Identification number of a TABLEDi entry for the thermal expansion

1136 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

coefficient.

(Integer or blank)

T(GE) Identification number of a TABLEDi entry for the damping coefficient.

(Integer > 0 or blank)

T(ST) Identification number of a TABLEDi entry for the tension stress limit.

(Integer > 0 or blank)

T(SC) Identification number of a TABLEDi entry for the compression limit.

(Integer > 0 or blank)

T(SS) Identification number of a TABLEDi entry for the shear limit.

(Integer > 0 or blank)

Comments

1. Fields 3, 4, and so on of this entry correspond, field-by-field, to fields 3, 4, and so on of


the MAT2 entry referenced in field 2. The value in a particular field of the MAT2 entry is
replaced or modified by the table referenced in the corresponding field of this entry. In
the example shown, G11 is modified by TABLEDi 32; G33 is modified by TABLEDi 15; RHO is
modified by TABLEDi 44 and GE is modified by TABLEDi 62. Blank or zero entries mean that
there is no frequency dependence of the field on the MAT2 entry.

2. The MATF2 entries may refer to blank entries on the respective MAT2 card. In this case,
they will be applied to default values of respective parameters.

3. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1137

Proprietary Information of Altair Engineering


MATF3

Bulk Data Entry

MATF3 – Orthotropic Material Frequency Dependence

Description

Specifies frequency-dependent material properties on MAT3 data entry fields via TABLEDi
entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATF3 MID T(EX) T(ETH) T(EZ) T(NUXTH) T(NUTHZ) T(NUZX) T(RHO)

T(GZX) T(AX) T(ATH) T(AZ) T(GE)

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATF3 17 32 19

52

Field Contents

MID Material property identification number that matches the identification


number on the MAT3 entry.

(Integer > 0)

T(EX) Identification numbers of TABLEDi entries for Young’s moduli in the x, θ and z
T(ETH) directions.
T(EZ)
Default = blank (Integer > 0 or blank)

T(EX) Identification numbers of TABLEDi entries for Poisson’s ratios in the xθ, θz
T(ETH) and zx directions.

1138 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

T(EZ) Default = blank (Integer > 0 or blank)

T(RHO) Identification number of a TABLEDi entry for the mass density.

Default = blank (Integer > 0 or blank)

T(GZX) Identification number of a TABLEDi entry for the shear modulus.

Default = blank (Integer > 0 or blank)

T(AX) Identification numbers of TABLEDi entries for thermal expansion coefficients in


T(ATH) the x, θ and z directions.
T(AZ)
Default = blank (Integer or blank)

T(GE) Identification number of a TABLEDi entry for the damping coefficient.

Default = blank (Integer > 0 or blank)

Comments

1. Fields 3, 4, and so on of this entry correspond, field-by-field, to fields 3, 4, and so on of


the MAT3 entry referenced in field 2. The value in a particular field of the MAT3 entry is
replaced or modified by the table referenced in the corresponding field of this entry. In
the example shown, EX is modified; TABLEDi 32, RHO is modified by TABLEDi 19; and GE is
modified by TABLEDi 52.

2. Blank or zero entries mean that there is no frequency dependence of the field on the
MAT3 entry. Any quantity modified by this entry must have a value on the MAT3 entry.

3. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1139

Proprietary Information of Altair Engineering


MATF8

Bulk Data Entry

MATF8 – Shell Orthotropic Material Frequency Dependence

Description

Specifies frequency-dependent material properties on MAT8 entry fields via TABLEDi entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATF8 MID T(E1) T(E2) T(NU12) T(G12) T(G1Z) T(G2Z) T(RHO)

T(A1) T(A2) T(Xt) T(Xc) T(Yt) T(Yc) T(S)

T(GE) T(F12)

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATF8 17 32 15

52

Field Contents

MID Material property identification number that matches the identification


number on the MAT1 entry.

(Integer > 0)

T(E1) Identification number of a TABLEDi entry for the Young’s modulus 1.

(Integer > 0 or blank)

1140 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

T(E2) Identification number of a TABLEDi entry for the Young’s modulus 2.

(Integer > 0 or blank)

T(NU12) Identification number of a TABLEDi entry for the Poisson’s ratio 12.

(Integer > 0 or blank)

T(G12) Identification number of a TABLEDi entry for shear modulus 12.

(Integer > 0 or blank)

T(G1Z) Identification number of a TABLEDi entry for transverse shear modulus 1Z.

(Integer > 0 or blank)

T(G2Z) Identification number of a TABLEDi entry for transverse shear modulus 2Z.

(Integer > 0 or blank)

T(RHO) Identification number of a TABLEDi entry for mass density.

(Integer > 0 or blank)

T(A1) Identification number of a TABLEDi entry for the thermal expansion coefficient
1. See comment 3.

(Integer or blank)

T(A2) Identification number of a TABLEDi entry for the thermal expansion coefficient
2.

(Integer or blank)

T(Xt) Identification number of a TABLEDi entry for the tension stress/strain limit 1.

(Integer > 0 or blank)

T(Xc) Identification number of a TABLEDi entry for compression stress/strain limit 1.

(Integer > 0 or blank)

T(Yt) Identification number of a TABLEDi entry for tension stress/strain limit 2.

(Integer > 0 or blank)

T(Yc) Identification number of a TABLEDi entry for compression stress/strain limit 2.

(Integer > 0 or blank)

Altair Engineering OptiStruct 13.0 Reference Guide 1141

Proprietary Information of Altair Engineering


Field Contents

T(S) Identification number of a TABLEDi entry for shear stress/strain limit.

(Integer > 0 or blank)

T(GE) Identification number of a TABLEDi entry for structural damping coefficient.

(Integer > 0 or blank)

T(F12) Identification number of a TABLEDi entry for Tsai-Wu interaction term.

(Integer > 0 or blank)

Comments

1. Fields 3, 4, and so on of this entry correspond, field-by-field, to fields 3, 4, and so on of


the MAT8 entry referenced in field 2. The value in a particular field of the MAT8 entry is
replaced or modified by the table referenced in the corresponding field of this entry. In
the example shown, E1 is modified by TABLEDi 32; RHO is modified by TABLEDi 15; and GE
is modified by TABLEDi 52.

2. Blank or zero entries mean that there is no frequency dependence of the fields on the
MAT8 entry. The MATF8 entries may refer to blank entries on the respective MAT8 card.
In which case, they will be applied to default values of the respective parameters.

3. This card is represented as a material in HyperMesh.

1142 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATF9

Bulk Data Entry

MATF9 – Solid Element Anisotropic Material Frequency Dependence

Description

Specifies frequency-dependent material properties on MAT9 entry fields via TABLEDi entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATF9 MID T(G11) T(G12) T(G13) T(G14) T(G15) T(G16) T(G22)

T(G23) T(G24) T(G25) T(G26) T(G33) T(G34) T(G35) T(G36)

T(G44) T(G45) T(G46) T(G55) T(G56) T(G66) T(RHO) T(A1)

T(A2) T(A3) T(A4) T(A5) T(A6) T(GE)

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATF9 17 32 18 17

12 5

10

Field Contents

MID Material property identification number that matches the identification


number on the MAT9 entry.

(Integer > 0)

T(Gij) Identification number of a TABLEDi entry for the terms in the material

Altair Engineering OptiStruct 13.0 Reference Guide 1143

Proprietary Information of Altair Engineering


Field Contents

property matrix.

(Integer > 0 or blank)

T(RHO) Identification number of a TABLEDi entry for the mass density.

(Integer > 0 or blank)

T(Ai) Identification number of a TABLEDi entry for the thermal expansion


coefficient.

(Integer or blank)

T(GE) Identification number of a TABLEDi entry for the damping coefficient.

(Integer > 0 or blank)

Comments

1. Fields 3, 4, and so on of this entry correspond, field-by-field, to fields 3, 4, and so on of


the MAT9 entry referenced in field 2. The value recorded in a particular field of the MAT9
entry is replaced or modified by the table referenced in the corresponding field of this
entry. In the example shown, G11 is modified by TABLEDj 32; G14 is modified by TABLEDj
18; G22 is modified by TABLEDi 17; G26 is modified by TABLEDi 12; RHO is modified by
TABLEDi 5 and GE is modified by TABLEDi 10.

2. If the fields are zero or blank, there is no frequency dependence of the field on the MAT9
entry. The MATF9 entries may refer to blank entries on the respective MAT9 card. In
which case, they will be applied to default values of respective parameters.

3. The continuation entries are optional.

4. This card is represented as a material in HyperMesh.

1144 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATF10

Bulk Data Entry

MATF10 – Isotropic Material Frequency Dependence

Description

Specifies frequency-dependent material properties on MAT10 entry fields via TABLEDi entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATF10 MID T(BULK) T(RHO) T(GE) T(ALPHA)

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATF10 2 10 13 17 19

Field Contents

MID Material property identification number that matches the identification


number on the MAT10 entry.

(Integer > 0)

T(BULK) Identification number of a TABLEDi entry for the bulk modulus.

(Integer > 0 or blank)

T(RHO) Identification number of a TABLEDi entry for the mass density.

(Integer > 0 or blank)

T(GE) Identification number of a TABLEDi entry for fluid material damping


coefficient.

(Integer > 0 or blank)

T(ALPHA) Identification number of a TABLEDi entry for normalized porous material

Altair Engineering OptiStruct 13.0 Reference Guide 1145

Proprietary Information of Altair Engineering


Field Contents

damping coefficient.

(Integer > 0 or blank)

Comments

1. Fields 3, 4, and so on of this entry correspond, field-by-field, to fields 3, 4, and so on of


the MAT10 entry referenced in field 2. The value recorded in a particular field of the
MAT10 entry is replaced or modified by the table referenced in the corresponding field of
this entry. In the example shown, BULK modulus is modified by TABLEDj 10; RHO is
modified by TABLEDj 18; G22 is modified by TABLEDi 17; G26 is modified by TABLEDi 12;
RHO is modified by TABLEDi 13; GE is modified by TABLEDi 17 and ALPHA is modified by
TABLEDi 19.

2. If the fields are zero or blank, there is no frequency dependence of the field on the
MAT10 entry. The MATF10 entries may refer to blank entries on the respective MAT10
card. In which case, they will be applied to default values of respective parameters.

3. The continuation entries are optional.

4. This card is represented as a material in HyperMesh.

1146 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATHE

Bulk Data Entry

MATHE – Nonlinear Hyperelastic Material Property Definition

Description

The MATHE bulk data entry defines material properties for nonlinear hyperelastic materials. The
Polynomial form is available and various material types (comment 3) can be defined by
specifying the corresponding coefficients.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATHE MID Model

C 10 C 01 D1 TAB1 TAB2 TAB4

C 20 C 11 C 02 D2 NA ND

C 30 C 21 C 12 C 03 D3

C 40 C 31 C 22 C 13 C 04 D4

C 50 C 41 C 32 C 23 C 14 C 05 D5

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATHE 2 MOONEY

80 20 0.001

Field Contents

MID Unique material identification number.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1147

Proprietary Information of Altair Engineering


Field Contents

Model Specifies the type of hyperelastic material model

MOONEY – Selects the generalized Mooney-Rivlin hyperelastic model

Default = MOONEY (Character, <MOONEY, blank>)

NA Order of the distortional strain energy polynomial function

No default (0 < Integer < 5)

ND Order of the volumetric strain energy polynomial function (see comment 2).

Default = 1 (Integer)

Cpq Material constants related to distortional deformation (Model = MOONEY).

Default = 0.0 (Real)

Dp Material constants related to volumetric deformation (Model = MOONEY).

Default = 0.0 (Real > 0.0)

TAB1 Table identification number of a TABLES1 entry that contains simple tension-
compression data to be used in the estimation of the material constants,
Cpq, related to distortional deformation. The x-values in the TABLES1 entry
should be the stretch ratios and y-values should be values of the engineering
stress.

(Integer > 0 or blank)

TAB2 Table identification number of a TABLES1 entry that contains equi-biaxial


tension data to be used in the estimation of the material constants, Cpq,
related to distortional deformation. The x-values in the TABLES1 entry should
be the stretch ratios and y-values should be values of the engineering stress.

(Integer > 0 or blank)

TAB4 Table identification number of a TABLES1 entry that contains pure shear data
to be used in the estimation of the material constants, Cpq, related to
distortional deformation. The x-values in the TABLES1 entry should be the
stretch ratios and y-values should be values of the nominal stress.

(Integer > 0 or blank)

Comments

1.
curve fit values based on the corresponding TAB# tables. However, any Cpq values set to
0.0 are not overwritten.

1148 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


2. The polynomial form of the Hyperelastic material model is written as a combination of the
deviatoric and volumetric strain energy of the material. The potential (U) is written in
polynomial form, as follows:

Where,

N1 is the order of the distortional strain energy polynomial function (NA)

N2 is the order of the volumetric strain energy polynomial function (ND). Currently only
first order volumetric strain energy functions are supported (ND=1).

Cpq are the material constants related to distortional deformation (Cpq)

, are invariants internally calculated by OptiStruct

Dp are material constants related to volumetric deformation (Dp). These values define the
compressibility of the material.

Jelas is the elastic volume strain calculated internally by OptiStruct

3. The polynomial form can be used to model the following material types by specifying the
corresponding coefficients (Cpq, Dp) on the MATHE entry:

Mooney-Rivlin Material:

N1 = N2 =1

1 2
U C10 I1 3 C01 I 2 3 J elas 1
D1

Reduced Polynomial:

q=0
N1 N2
p 1 2p
U C p 0 I1 3 J elas 1
p 1 p 1 Dp

Neo-Hooken Material
N1= N2 =1, q=0

1 2
U C10 I1 3 J elas 1
D1

Altair Engineering OptiStruct 13.0 Reference Guide 1149

Proprietary Information of Altair Engineering


Yeoh Material

N1 = N2 =3, q=0

1 2 2 1 4 3 1 6
U C10 I1 3 J elas 1 C20 I1 3 J elas 1 C30 I1 3 J elas 1
D1 D2 D3

Three term Mooney-Rivlin Material:

U C10 I1 3 C01 I 2 3 C11 I1 3 I2 3

Signiorini Material:
2
U C10 I1 3 C01 I 2 3 C20 I1 3

Third Order Invariant Material:


2
U C10 I1 3 C01 I 2 3 C11 I1 3 I2 3 C20 I1 3

Third Order Deformation Material (James-Green-Simpson):


2 3
U C10 I1 3 C01 I 2 3 C11 I1 3 I2 3 C20 I1 3 C30 I1 3

4. The MATHE hyperelastic material supports CTETRA (4, 10), CPENTA (6, 15), and CHEXA
(8, 20) element types.

5. This card is represented as a material in HyperMesh.

1150 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATHF

Bulk Data Entry

MATHF – Material Property Definition for One-step Stamping Simulation

Description

Defines the material properties in a one-step stamping simulation.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATHF MID E NU Y K n EPS0

R0 R45 R90 TABLEID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATHF 17 21.0E4 0.3 184.297 549.03 0.22 0.007

1.6 1.6 1.6

Field Contents

MID Unique material identification number.

No default (Integer > 0)

E Young’s Modulus.

No default (Real)

NU Poisson’s Ratio.

Default = blank (-1.0 < Real < 0.5 or blank)

Y Yield stress.

No default (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 1151

Proprietary Information of Altair Engineering


Field Contents

K Strength coefficient.

No default (Real or blank)

n Strain hardening component.

No default (Real or blank)

EPS0 Pre-strain coefficient.

No default (Real or blank)

R0, R45, R90 Lankford coefficients.

No default (Real)

TABLEID Table ID for stress-strain curve using a TABLES1 entry.

No default (Integer > 0)

Comments

1. This entry is only valid with a @HyperForm statement in the first line of the input file.

2. The TABLEID and the corresponding curve are required only when material data is
specified with a stress-strain curve. For such case, material parameter such as K, n and
EPS0 are extracted from the stress strain curve.

1152 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATPE1

Bulk Data Entry

MATPE1 – Material Property Definition

Description

Defines the material properties for poro-elastic materials.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATPE1 MID MAT1 MAT10 BIOT

VISC GAMMA PRANDTL POR TOR AFR VLE TLE

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATPE1 17 1 10 1.0

1.8-8 1.41 7.0-1 8.0-1 1.2 2.-5 1.0-1 9.3-2

Field Contents

MID Unique material identification number.

No default (Integer > 0)

MAT1 Material identification number of the MAT1 bulk data entry (or MATF1 if it is
frequency-dependent) for the skeleton.

No default (Integer > 0)

MAT10 Identification number of MAT10 bulk data entry for the porous material.

No default (Integer > 0)

BIOT BIOT factor

Altair Engineering OptiStruct 13.0 Reference Guide 1153

Proprietary Information of Altair Engineering


Field Contents

Default = 1.0 (Real > 0.0)

VISC Fluid dynamic viscosity

No default (Real > 0.0)

GAMMA Fluid ratio of specific heats.

Default = 1.402 (Real > 0.0)

PRANDTL Fluid Prandtl number.

Default = 0.71 (Real > 0.0)

POR Porosity of the porous material.

No default (Real > 0.0)

TOR Tortuosity of the porous material.

Default = 1.0 (Real > 0.0)

AFR Air flow resistivity.

No default (Real > 0.0)

VLE Viscous characteristic length.

No default (Real > 0.0)

TLE Thermal characteristic length.

No default (Real > 0.0)

Comments

1. This entry is represented as a material in HyperMesh.

1154 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATS1

Bulk Data Entry

MATS1 – Stress-dependent and Temperature-dependent Material Definition

Description

Specifies stress-dependent and temperature-dependent material properties for use in


applications involving nonlinear materials. This entry is used if a MAT1 entry is specified with
the same MID in a nonlinear subcase.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATS1 MID TID TYPE H YF HR LIMIT1

TYPSTRN

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATS1 17 28 PLASTIC 0.0 1 1 2. + 4

Field Contents

MID Identification number of a MAT1 entry.

(Integer > 0)

TID Identification number of a TABLES1 or TABLEST entry. If H is given, then


this field must be blank. See comment 3.

(Integer > 0 or blank)

TYPE Type of material nonlinearity. See comments.

PLASTIC – Elastoplastic material

Altair Engineering OptiStruct 13.0 Reference Guide 1155

Proprietary Information of Altair Engineering


Field Contents

NLELAST – Nonlinear elastic material

Default = NLELAST (PLATIC, NLELAST)

H Work hardening slope (slope of stress versus plastic strain) in units of stress.
For elastic-perfectly plastic cases, H = 0.0. For more than a single slope in
the plastic range, the stress-strain data must be supplied on a TABLES1
entry referenced by TID, and this field must be blank. See comment 2.

(Real > 0)

YF Yield function criterion, selected by the following value (Integer):

1 = von Mises (Default)

(Integer > 0 or blank)

HR Hardening Rule, selected by the following value (Integer):

1 = Isotropic Hardening (Default)

2 = Kinematic Hardening

3 = Mixed Hardening with 30% contribution of the Kinematic Hardening and


70% contribution of the Isotropic Hardening

Adjustable Mixed Hardening is selected by choosing (Real) value for HR:

0 < HR < 1 indicates a mixed combination of Isotropic and Kinematic


Hardening. The contribution of the Kinematic Hardening is HR whereas the
contribution of the Isotropic Hardening is 1 – HR.

See comment 4.

(Integer 0, 1, 2, 3 or blank, or Real > 0 and < 1)

LIMIT1 Initial yield point. See comment 6.

(Real > 0 or Blank)

TYPSTRN Specifies the type of strain used on the x-axis of the table pointed to by
TID. The strain type is selected by one of the following values. See
comment 5.

0 - total strain is used on the x-axis.

1 - plastic strain is used on the x-axis.

Default = 0 (Integer, 0, or 1)

1156 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. For nonlinear elastic material, the stress-strain data given in the TABLES1 entry will be
used to determine the stress for a given value of strain. The values H, YF, HR, and
LIMIT1 will not be used in this case. Nonlinear elastic material is only available in NLGEOM
subcases.

2. For elastoplastic materials, the elastic stress-strain matrix is computed from a MAT1
entry, and the isotropic plasticity theory is used to perform the plastic analysis. In this
case, either the table identification TID or the work hardening slope H may be specified,
but not both. If the TID is omitted, the work hardening slope H must be specified unless
the material is perfectly plastic. The plasticity modulus (H) is related to the tangential
modulus (ET ) by

where, E is the elastic modulus and is the slope of the uniaxial stress-strain
curve in the plastic region.

Stress-strain curve definition when H is specified in field 5.

3. If TID is given, TABLES1 entries (Xi,Yi) of stress-strain data ( ) must conform to the
following rules:

If TYPE = "PLASTIC", the curve must be defined in the first quadrant. The data points
must be in ascending order. If the table is defined in terms of total strain (TYPSTRN = 0),
the first point must be at the origin (X1 = 0, Y1 = 0) and the second point (X2, Y2) must
be at the initial yield point (Y 1) specified on the MATS1 entry. The slope of the line
joining the origin to the yield stress must be equal to the value of E. If the table is
defined in terms of plastic strain (TYPSTRN = 1), the first point (X1, Y1), corresponding to
yield point (Y 1), must be at X1=0. TID may reference a TABLEST entry. In this case, the
above rules apply to all TABLES1 tables pointed to by TABLEST.

If TYPE = “NLELAST”, the full stress-strain curve may be defined in the first and third
quadrants to accommodate different uniaxial compression data. If the curve is defined
only in the first quadrant, then the curve must start at the origin (X1 = 0.0, Y1 = 0.0).

For analyses where small deformations are assumed, there should be little or no difference

Altair Engineering OptiStruct 13.0 Reference Guide 1157

Proprietary Information of Altair Engineering


between the true stress-strain curve and the engineering stress-strain curve, so either of
them may be used in the TABLES1 definition. For analyses where small deformations are
not assumed, the true stress-strain curve should be used.

If the deformations go past the values defined in the table, the curve is extrapolated
linearly.

4. Kinematic hardening and Mixed hardening are supported only for solids.

5. The conversion of the relation stress vs. total strain (TYPSTRN=0) into stress vs. plastic
strain (TYPSTRN=1) is illustrated below. This is clearly different than simply shifting the
entire table along the epsilon-axis.

1158 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


6. The LIMIT1 field can be blank if the initial yield point value is defined via a referenced
TABLES1 entry on the TID field. OptiStruct will error out if LIMIT1 is blank and TID does
not reference a TABLES1 entry.

Altair Engineering OptiStruct 13.0 Reference Guide 1159

Proprietary Information of Altair Engineering


7. The temperature-dependence of the MATS1 material is defined by referencing a TABLEST
entry via the TID field.

8. Large strain elasto-plasticity can be activated using MATS1 (TYPE=PLASTIC) in


conjunction with PARAM, LGDISP, 1.

9. Linear Buckling Analysis and Preloaded Analysis are not supported with models containing
nonlinear (MATS1) material entries. However, you can use PARAM,PRESUBNL,YES to force
OptiStruct to run in such models. Linear Buckling Analysis or Preloaded Analysis is not
recommended in models with nonlinear materials or in large displacement nonlinear
analysis. It is the user’s responsibility to interpret the results with caution.

1160 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATT1

Bulk Data Entry

MATT1 – Isotropic Material Temperature Dependence

Description

Specifies temperature-dependent material properties on MAT1 entry fields via TABLEMi entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATT1 MID T(E) T(G) T(NU) T(RHO) T(A) T(GE)

T(ST) T(SC ) T(SS)

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATT1 17 32 15

52

Field Contents

MID Material property identification number that matches the identification number
on MAT1 entry.

(Integer > 0)

T(E) Identification number of a TABLEMi entry for the Young’s modulus.

(Integer > 0 or blank)

T(G) Identification number of a TABLEMi entry for the shear modulus.

(Integer > 0 or blank)

Altair Engineering OptiStruct 13.0 Reference Guide 1161

Proprietary Information of Altair Engineering


Field Contents

T(NU) Identification number of a TABLEMi entry for the Poisson’s ratio.

(Integer > 0 or blank)

T(RHO) Identification number of a TABLEMi entry for the mass density.

(Integer > 0 or blank)

T(A) Identification number of a TABLEMi entry for the thermal expansion


coefficient.

(Integer or blank)

T(GE) Identification number of a TABLEMi entry for the damping coefficient.

(Integer > 0 or blank)

T(ST) Identification number of a TABLEMi entry for the tension stress limit.

(Integer > 0 or blank)

T(SC) Identification number of a TABLEMi entry for the compression limit.

(Integer > 0 or blank)

T(SS) Identification number of a TABLEMi entry for the shear limit.

(Integer > 0 or blank)

Comments

1. Fields 3, 4, and so on, of this entry correspond, field-by-field, to fields 3, 4, and so on, of
the MAT1 entry referenced in field 2. The value in a particular field of the MAT1 entry is
replaced or modified by the table referenced in the corresponding field of this entry. In
the example shown, E is modified; TABLEMi 32, A is modified by TABLEMi 15; and ST is
modified by TABLEMi 52. Blank or zero entries mean that there is no temperature
dependence of the field on the MAT1 entry.

2. The MATT1 entries may refer to blank entries on the respective MAT1 card. In this case,
they will be applied to default values of respective parameters. Initial values of E, G, or
NU will be supplied according to comment 4 on the MAT1 entry.

3. Table references must be present for each item that is temperature dependent. For
example, it is not sufficient to only give table references for fields 3 and 4 (Young’s
modulus and shear modulus) if Poisson’s ratio is temperature dependent.

4. The TEMPERATURE subcase information entry (with type = MATERIAL) is required to

1162 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


activate temperature-dependent material behavior and to define the temperature field
(option = SID of TEMP, TEMPD or the SUBCASE ID of a thermal analysis subcase).

5. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1163

Proprietary Information of Altair Engineering


MATT2

Bulk Data Entry

MATT2 – Anisotropic Material Temperature Dependence

Description

Specifies temperature-dependent material properties on MAT2 entry fields via TABLEMj


entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATT2 MID T(G11) T(G12) T(G13) T(G22) T(G23) T(G33) T(RHO)

T(A1) T(A2) T(A3) T(GE) T(ST) T(SC ) T(SS)

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATT2 17 32 15

62

Field Contents

MID Material property identification number that matches the identification number
on a MAT2 entry.

(Integer > 0)

T(Gij) Identification number of a TABLEMk entry for the terms in the material
property matrix.

(Integer > 0 or blank)

T(RHO) Identification number of a TABLEMk entry for the mass density.

1164 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

(Integer > 0 or blank)

T(Ai) Identification number of a TABLEMk entry for the thermal expansion


coefficient.

(Integer or blank)

T(GE) Identification number of a TABLEMk entry for the damping coefficient.

(Integer > 0 or blank)

T(ST) Identification number of a TABLEMk entry for the tension stress limit.

(Integer > 0 or blank)

T(SC) Identification number of a TABLEMk entry for the compression limit.

(Integer > 0 or blank)

T(SS) Identification number of a TABLEMk entry for the shear limit.

(Integer > 0 or blank)

Comments

1. Fields 3, 4, and so on of this entry correspond, field-by-field, to fields 3, 4, and so on of


the MAT2 entry referenced in field 2. The value in a particular field of the MAT2 entry is
replaced or modified by the table referenced in the corresponding field of this entry. In
the example shown, G11 is modified by TABLEMk 32; G33 is modified by TABLEMk 15; and
A1 is modified by TABLEMk 62. If Ri is zero or blank, there is no temperature dependence
of the field on the MAT2 entry.

2. The MATT2 entries may refer to blank entries on the respective MAT2 card. In which
case, they will be applied to default values of respective parameters.

3. The TEMPERATURE subcase information entry (with type = MATERIAL) is required to


activate temperature-dependent material behavior and to define the temperature field
(option = SID of TEMP, TEMPD or the SUBCASE ID of a thermal analysis subcase).

4. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1165

Proprietary Information of Altair Engineering


MATT3

Bulk Data Entry

MATT3 – MAT3 Material Temperature Dependence

Description

Specifies temperature-dependent material properties on MAT3 entry fields via TABLEMi entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATT3 MID T(EX) T(ETH) T(EZ) T(NUXTH) T(NUTHZ) T(NUZX) T(RHO)

T(GZX) T(AX) T(ATH) T(AZ) T(GE)

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATT3 17 32 19

52

Field Contents

MID Material property identification number that matches the identification


number on MAT3 entry.

(Integer > 0)

T(EX), Identification number of a TABLEMi entry for the Young’s moduli in the x, θ
T(ETH), and z directions.
T(EZ)
Default = blank (Integer > 0 or blank)

T(NUXTH), Identification number of a TABLEMi entry for the Poisson’s ratios in the xθ, θz

1166 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

T(NUTHZ), and zx directions.


T(NUZX)
Default = blank (Integer > 0 or blank)

T(RHO) Identification number of a TABLEMi entry for the mass density.

Default = blank (Integer > 0 or blank)

T(GZX) Identification number of a TABLEMi entry for the shear modulus.

Default = blank (Integer > 0 or blank)

T(AX), Identification number of a TABLEMi entry for the thermal expansion


T(ATH), coefficients in the x, θ and z directions.
T(AZ)
Default = blank (Integer or blank)

T(GE) Identification number of a TABLEMi entry for the damping coefficient.

Default = blank (Integer > 0 or blank)

Comments

1. Fields 3, 4, and so on, of this entry correspond, field-by-field, to fields 3, 4, and so on, of
the MAT3 entry referenced in field 2. The value in a particular field of the MAT3 entry is
replaced or modified by the table referenced in the corresponding field of this entry. In
the example shown, EX is modified; TABLEMi 32, EZ is modified by TABLEMi 19; and GZX is
modified by TABLEMi 52. Blank or zero entries mean that there is no temperature
dependence of the field on the MAT3 entry.

2. Any quantity modified by this entry must have a value on the MAT3 entry.

3. The TEMPERATURE subcase information entry (with type = MATERIAL) is required to


activate temperature-dependent material behavior and to define the temperature field
(option = SID of TEMP, TEMPD or the SUBCASE ID of a thermal analysis subcase).

4. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1167

Proprietary Information of Altair Engineering


MATT4

Bulk Data Entry

MATT4 – Temperature-Dependent Material Property Definition, Form 4

Description

Defines temperature-dependent material properties for the corresponding MAT4 bulk data
entry fields via TABLEMi entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATT4 MID T(K)

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATT4 24 200

Field Contents

MID Material identification number of a MAT4 bulk data entry that is temperature
dependent.

No default (Integer > 0)

T(K) Identification number of a TABLEMi entry that defines temperature-dependent


thermal conductivity.

Default = 0 (Integer > 0)

Comments

1. The quantities defined on the MAT4 bulk data entry are multiplied by the tabular function
referenced by the MATT4 bulk data card to generate the corresponding material
properties.

2. If the fields are blank or zero, then constant properties defined on the MAT4 bulk data
card are used.

1168 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATT8

Bulk Data Entry

MATT8 – Shell Orthotropic Material Temperature Dependence

Description

Specifies temperature-dependent material properties on MAT8 entry fields via TABLEMi entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATT8 MID T(E1) T(E2) T(NU12) T(G12) T(G1Z) T(G2Z) T(RHO)

T(A1) T(A2) T(Xt) T(Xc) T(Yt) T(Yc) T(S)

T(GE) T(F12)

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATT8 17 32 15

15 52

Field Contents

MID Material property identification number that matches the identification


number on MAT1 entry.

(Integer > 0)

T(E1) Identification number of a TABLEMi entry for the Young’s modulus 1.

(Integer > 0 or blank)

Altair Engineering OptiStruct 13.0 Reference Guide 1169

Proprietary Information of Altair Engineering


Field Contents

T(E2) Identification number of a TABLEMi entry for the Young’s modulus 2.

(Integer > 0 or blank)

T(NU12) Identification number of a TABLEMi entry for the Poisson’s ratio 12.

(Integer > 0 or blank)

T(G12) Identification number of a TABLEMi entry for shear modulus 12.

(Integer > 0 or blank)

T(G1Z) Identification number of a TABLEMi entry for transverse shear modulus 1Z.

(Integer > 0 or blank)

T(G2Z) Identification number of a TABLEMi entry for transverse shear modulus 2Z.

(Integer > 0 or blank)

T(RHO) Identification number of a TABLEMi entry for mass density.

(Integer > 0 or blank)

T(A1) Identification number of a TABLEMi entry for the thermal expansion


coefficient 1. See comment 3.

(Integer or blank)

T(A2) Identification number of a TABLEMi entry for the thermal expansion


coefficient 2.

(Integer or blank)

T(Xt) Identification number of a TABLEMi entry for the tension stress/strain limit 1.

(Integer > 0 or blank)

T(Xc) Identification number of a TABLEMi entry for compression stress/strain limit


1.

(Integer > 0 or blank)

1170 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

T(Yt) Identification number of a TABLEMi entry for tension stress/strain limit 2.

(Integer > 0 or blank)

T(Yc) Identification number of a TABLEMi entry for compression stress/strain limit


2.

(Integer > 0 or blank)

T(S) Identification number of a TABLEMi entry for shear stress/strain limit.

(Integer > 0 or blank)

T(GE) Identification number of a TABLEMi entry for structural damping coefficient.

(Integer > 0 or blank)

T(F12) Identification number of a TABLEMi entry for Tsai-Wu interaction term.

(Integer > 0 or blank)

Comments

1. Fields 3, 4, and so on of this entry correspond, field-by-field, to fields 3, 4, and so on of


the MAT8 entry referenced in field 2. The value in a particular field of the MAT8 entry is
replaced or modified by the table referenced in the corresponding field of this entry. In
the example shown, E1 is modified by TABLEMi 32; A1 is modified by TABLEMi 15; and Xt
is modified by TABLEMi 52. Blank or zero entries mean that there is no temperature
dependence of the fields on the MAT8 entry.

2. The MATT8 entries may refer to blank entries on the respective MAT8 card. In which
case, they will be applied to default values of respective parameters.

3. The TEMPERATURE subcase information entry (with type = MATERIAL) is required to


activate temperature-dependent material behavior and to define the temperature field
(option = SID of TEMP, TEMPD or the SUBCASE ID of a thermal analysis subcase).

4. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1171

Proprietary Information of Altair Engineering


MATT9

Bulk Data Entry

MATT9 – Solid Element Anisotropic Material Temperature Dependence

Description

Specifies temperature-dependent material properties on MAT9 entry fields via TABLEMk


entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATT9 MID T(G11) T(G12) T(G13) T(G14) T(G15) T(G16) T(G22)

T(G23) T(G24) T(G25) T(G26) T(G33) T(G34) T(G35) T(G36)

T(G44) T(G45) T(G46) T(G55) T(G56) T(G66) T(RHO) T(A1)

T(A2) T(A3) T(A4) T(A5) T(A6) T(GE)

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATT9 17 32 18 17

12

5 10

Field Contents

MID Material property identification number that matches the identification number
on a MAT9 entry.

(Integer > 0)

1172 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

T(Gij) Identification number of a TABLEMk entry for the terms in the material
property matrix.

(Integer > 0 or blank)

T(RHO) Identification number of a TABLEMk entry for the mass density.

(Integer > 0 or blank)

T(Ai) Identification number of a TABLEMk entry for the thermal expansion


coefficients.

(Integer > 0 or blank)

T(GE) Identification number of a TABLEMk entry for the damping coefficient.

(Integer > 0 or blank)

Comments

1. Fields 3, 4, and so on of this entry correspond, field-by-field, to fields 3, 4, and so on of


the MAT9 entry referenced in field 2. The value recorded in a particular field of the MAT9
entry is replaced or modified by the table referenced in the corresponding field of this
entry. In the example shown, G11 is modified by TABLEMj 32; G14 is modified by TABLEMj
18, and so on. If the fields are zero or blank, there is no temperature dependence of the
field on the MAT9 entry.

2. The MATT9 entries may refer to blank entries on the respective MAT9 card. In which
case, they will be applied to default values of respective parameters.

3. The continuation entries are optional.

4. The TEMPERATURE subcase information entry (with type = MATERIAL) is required to


activate temperature-dependent material behavior and to define the temperature field
(option = SID of TEMP, TEMPD or the SUBCASE ID of a thermal analysis subcase).

5. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1173

Proprietary Information of Altair Engineering


MATX0

Bulk Data Entry

MATX0 – Material Property Extension for Void Material for Geometric Nonlinear Analysis

Description

Defines void material for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX0 MID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT1 102 10.0 0.495 6.0E-10

MATX0 102

Field Contents

MID Material ID of the associated MAT1. See comment 1.

No default (Integer > 0)

Comments

1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATX0 material extension can be associated with a particular MAT1.

2. MATX0 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN subcase entry. For all other subcases, it is
treated as an elastic material defined by the associated MAT1.

3. This card is represented as an extension to a MAT1 material in HyperMesh.

1174 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATX02

Bulk Data Entry

MATX02 – Material Property Extension for Johnson-Cooke Elastic-plastic Material for


Geometric Nonlinear Analysis

Description

Defines additional material properties for Johnson-Cooke elastic-plastic material for geometric
nonlinear analysis. This is an elasto-plastic law with strain rate and temperature effects.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX02 MID A B N EPSMAX SIGMAX C DEPS0

IC C FSMOOTH FC UT M TMELT RC P

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT1 102 60.4 0.33 2.70E-06

MATX02 102 0.09026 0.22313 0.374618 100.0 0.175

Field Contents

MID Material ID of the associated MAT1. See comment 1.

No default (Integer > 0)

A Plasticity yield stress.

(Real > 0)

B Plasticity hardening parameter.

(Real > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1175

Proprietary Information of Altair Engineering


Field Contents

N Plasticity hardening exponent.

Default = 1.0 (Real < 1.0)

EPSMAX Failure plastic strain εmax

Default = 1030 (Real > 0)

SIGMAX Maximum plastic stress σmax0

Default = 1030 (Real > 0)

C Strain rate coefficient. If zero, there is no strain rate effect.

Default = 0.0 (Real)

DEPS0 Reference strain rate .

Default = 0.0 (Real)

If DESPS < DESPS0, no strain rate effect.

ICC Flag for strain rate dependency of σmax (See comment 5).

Default = ON (ON or OFF)

FSMOOTH Flag for strain rate smoothing.

Default = OFF (ON or OFF)

FCUT Cutoff frequency for strain rate filtering. Only for shell and solid elements.

Default = 1030 (Real > 0)

M Temperature exponent.

Default = 0.0 (Real)

TMELT Melting temperature.

Default = 1030 (Real > 0)

1176 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

RCP Specific heat per unit of volume.

Default = 0.0 (Real > 0)

Comments

1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.

2. MATX02 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. This is an elastic-plastic law with strain rate and thermal effects. It follows:

with:

= plastic strain

= strain rate

T = Temperature (in Kelvin)

4. If the plastic strain reaches EPSMAX, shell elements are deleted. Solid elements are not
deleted, but the deviatoric stress is set to zero.

5. ICC controls the strain rate effect.

Altair Engineering OptiStruct 13.0 Reference Guide 1177

Proprietary Information of Altair Engineering


6. No strain rate effects are considered in rod elements.

7. Strain rate filtering is used to smooth strain rates. The input FCUT is available only for
shell and solid elements.

8. To take into account the temperature effect, strain rate dependence must be activated.
If the temperature exponent M = 0; there is no temperature effect. No temperature
effect is considered on rod, bar, and beam elements.

9. The temperature is computed assuming adiabatic conditions:

where, Eint is the internal energy.

If ρCp = 0, the temperature is constant: T = T i

10. This card is represented as an extension to a MAT1 material in HyperMesh.

1178 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATX13

Bulk Data Entry

MATX13 – Material Property Extension for Rigid Material for Geometric Nonlinear Analysis

Description

Defines rigid material for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX13 MID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT1 102 10.0 0.495 6.0E-10

MATX13 102

Field Contents

MID Material ID of the associated MAT1. See comment 1.

No default (Integer > 0)

Comments

1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.

2. MATX13 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1179

Proprietary Information of Altair Engineering


MATX21

Bulk Data Entry

MATX21 – Material Property Extension for Rock-Concrete Material for Geometric Nonlinear
Analysis

Description

Defines additional material properties for Rock-Concrete material for geometric nonlinear
analysis. This law is based on the Drücker-Prager yield criteria and is used to model materials
with internal friction such as rock-concrete. The plastic behavior of these materials is
dependent on the pressure in the material. This law is only applicable to solid elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX21 MID A0 A1 A2 AMAX

TPID KT FSC AL PMIN B MUMAX PEXT

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT1 102 3.1E10 0.33 1000.0

MATX21 102 3

1 1E10

Field Contents

MID Material ID of the associated MAT1. See comment 1.

No default (Integer > 0)

A0 Coefficient.

(Real)

1180 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

A1 Coefficient.

(Real)

A2 Coefficient.

(Real)

AMAX Von Mises limit.

Default = 1030 (Real > 0)

TPID Identification number of a TABLES1 that defines the volumetric strain vs.
pressure function.

No default (Integer > 0)

KT Tensile bulk modulus.

(Real > 0.0)

FSCAL Scale factor for pressure function.

Default = 1.0 (Real)

PMIN Minimum pressure.

Default = -1030 (Real)

B Unloading bulk modulus.

(Real > 0.0)

MUMAX Maximum compression volumetric strain.

(Real)

PEXT External pressure (see comment 6).

Default = 0.0 (Real)

Comments

1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATX21 material extension can be associated with a particular MAT1.

2. MATX21 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

Altair Engineering OptiStruct 13.0 Reference Guide 1181

Proprietary Information of Altair Engineering


3. Hydrodynamic behavior is given by a user-defined function P = f(µ)

where, P is the pressure in the material, and µ is the volumetric strain.

4. Drücker-Prager yield criteria uses a modified von Mises yield criteria to incorporate the
effects of pressure for massive structures:

F = J2 - (A0 + A1P + A2P2)

where,

J2: second invariant of deviatoric stress.

P: pressure.

A0, A1, A2: material coefficients.

vm 3 A0
A1 = A2 = 0 means that the yield criteria is von Mises ( )

1182 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


5. It is recommended to set unloading bulk modulus, B equal to the initial slope of function
describing P(µ) and tensile bulk modulus KT equal to 1/100 of unloading bulk modulus. B
and KT must be positive.

6. External pressure is required if relative pressure formulation is used. In this specific case,
yield criteria and energy integration require the value of total pressure.

7. This card is represented as an extension to a MAT1 material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1183

Proprietary Information of Altair Engineering


MATX25

Bulk Data Entry

MATX25 – Material Property Extension for Tsai-Wu and CRASURVT Materials for Geometric
Nonlinear Analysis

Description

Defines an elasto-plastic orthotropic material with Tsai-Wu and CRASURVT yield criteria for
composite shell materials.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX25 MID EPSF1 EPSF2 EPST1 EPSM1 EPST2 EPSM2 DTENDS

WPMAX WPREF IOFF GAMINI GAMMAX DMAX RATIO

FSMOOTH FC UT IFORM

Continuation line for IFORM = TSAI

B N FMAX

SY1T SY2T SY1C SY2C ALFA

SY12C SY12T C 12 EPSR0 IC C

Continuation line for IFORM = CRAS

C EPSR0 ALFA IC C G

SY1T B1T N1T SMAX1T C 1T

EPS1T1 EPS2T1 SRST1 WMPT1

SY2T B2T N2T SMAX2T C 2T

EPS1T2 EPS2T2 SRST2 WMPT2

1184 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SY1C B1C N1C SMAX1C C 1C

EPS1C 1 EPS2C 1 SRSC 1 WMPC 1

SY2C B2C N2C SMAX2C C 2C

EPS1C 2 EPS2C 2 SRSC 2 WMPC 2

SY12T B12T N12T SMAX12 C 12T


T

EPS1T12 EPS2T12 SRST12 WMPT12

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT8 102 70000 70000 0.3 26923.1 26923.1 26923.1

MATX25 102 0.15 0.2 0.95

0.2 1.0 2.0

1E10 1E10 1E10 1E10

1E10 1E10

Field Contents

MID Material ID of the associated MAT8. See comment 1.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1185

Proprietary Information of Altair Engineering


Field Contents

EPSF1 Total tensile failure in direction 1.

Default = 1E30 (Real)

EPSF2 Total tensile failure in direction 2.

Default = 1E30 (Real)

EPST1 Tensile failure strain in direction 1.

(Real)

EPSM1 Maximum strain in direction 1.

(Real)

EPST2 Tensile failure strain in direction 2.

(Real)

EPSM2 Maximum strain in direction 2.

(Real)

DTENDS Maximum damage of composite tensile strength.

Default = 0.999 (Real < 1.0)

WPMAX Maximum plastic work.

Default = 1E30 (Real)

WPREF Reference plastic work.

Default = 1.0 (Real)

IOFF Total element failure criteria.

Default = 0 (Integer)

= 0: shell is deleted if Wp* > Wp*max for 1 layer


= 1: shell is deleted if Wp* > Wp*max for all layers
= 2: if for each layer, Wp* > Wp*max or tensile failure in direction 1(t1)

1186 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

= 3: if for each layer, Wp* > Wp*max or tensile failure in direction 2(t2)
= 4: if for each layer, Wp* > Wp*max or tensile failure in directions 1(t1) and
2(t2)
= 5: if for all layers: Wp* > Wp*max or tensile failure in direction 1(t1)
or if for all layers: Wp* > Wp*max or tensile failure in direction 2(t2)
= 6: if for each layer, Wp* > Wp*max or tensile failure in direction 1(t1) or
2(t2)

GAMINI Delamination shear strain. See comment 11.

Default = 1E30 (Real)

GAMMAX Maximum shear strain.

Default = 1.1E30 (Real)

DMAX Maximum damage.

Default = 1.0 (Real)

RATIO Ratio parameter control to delete shell elements

Default = 1.0 (Real)

< 0.0: the element will be deleted if all of the layers but one fail (the number
of layers that did not fail is equal to 1).

> 0.0: the element will be deleted if:

FSMOOTH Flag for strain rate smoothing.

Default = OFF (ON or OFF)

FCUT Cutoff frequency for strain rate filtering.

Default = 1E30 (Real)

IFORM Formulation flag.

Default = TSAI (TSAI, CRAS)

IFORM = TSAI

Altair Engineering OptiStruct 13.0 Reference Guide 1187

Proprietary Information of Altair Engineering


Field Contents

B Hardening parameter.

(Real)

N Hardening exponent.

Default = 1.0 (Real)

FMAX Maximum value of yield function.

Default = 1E30 (Real)

SY1T Tension in direction 1.

(Real > 0)

SY2T Tension in direction 2.

(Real > 0)

SY1C Compression yield stress in direction 1.

(Real > 0)

SY2C Compression yield stress in direction 2.

(Real > 0)

ALFA F12 reduction factor.

Default = 1.0 (Real)

SY12C Compression yield stress in direction 12.

(Real > 0)

SY12T Tension yield stress in direction 12.

(Real > 0)

C12 Strain rate coefficient.

(Real)

1188 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

= 0.0: no strain rate dependency.

EPSR0 Reference strain rate.

(Real)

ICC Flag for yield stress in shear and strain rate (See comment 9).

(Integer)

= 0: Default set to 1
= 1: Strain rate effect on FMAX no effect on WPMAX
= 2: No strain rate effect on FMAX and WPMAX
= 3: Strain rate effect on FMAX and WPMAX
= 4: No strain rate effect on FMAX effect on WPMAX

IFORM = CRAS

C Global strain rate coefficient for plastic work criteria.

(Real)

EPSR0 Reference strain rate.

(Real)

ALFA F12 reduction factor.

Default= 1.0 (Real)

ICCG Global composite plasticity parameters flag for strain rate computation: (See
comment 9).

= 1: Strain rate effect on SMAX1T, SMAX2T, SMAX1C, SMAX2C, SMAX12T;


no strain rate effect on WPMAX.

= 2: No strain rate effect on SMAX1T, SMAX2T, SMAX1C, SMAX2C,


SMAX12T; no strain rate effect on WPMAX.

= 3: Strain rate effect on SMAX1T, SMAX2T, SMAX1C, SMAX2C, SMAX12T


and strain rate effect on WPMAX.

= 4: No strain rate effect on SMAX1T, SMAX2T, SMAX1C, SMAX2C, SMAX12T


and strain rate effect on WPMAX.

Default = 1 (Integer)

Altair Engineering OptiStruct 13.0 Reference Guide 1189

Proprietary Information of Altair Engineering


Field Contents

SY1T Tension yield stress in direction 1.

(Real > 0)

B1T Hardening parameter in direction 1.

(Real)

N1T Hardening exponent in direction 1.

Default = 1.0 (Real)

SMAX1T Maximum stress in direction 1.

Default = 1E30 (Real)

C1T Strain rate coefficient in direction 1.

0: no strain rate dependency.

Default = C (Real)

EPS1T1 Initial softening strain in direction 1.

Default = 1E30 (Real)

EPS2T1 Maximum softening strain in direction 1.

Default = 1.2 * EPS1T1 (Real)

SRST1 Residual stress in direction 1.

Default = 10E-3*SY1T (Real)

WMPT1 Maximum plastic work in tension direction 1.

Default = 1E30 (Real)

SY2T Tension yield stress in direction 2.

(Real > 0)

B2T Hardening parameter in direction 2.

1190 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Default = B1T (Real)

N2T Hardening exponent in direction 2.

Default = N1T (Real)

SMAX2T Maximum stress in direction 2.

Default = 1E30 (Real)

C2T Strain rate coefficient in direction 2.

0: no strain rate dependency

Default = C (Real)

EPS1T2 Initial softening strain in direction 2.

Default = 1E30 (Real)

EPS2T2 Maximum softening strain in direction 2.

Default = 1.2*EPS1T1 (Real)

SRST2 Residual stress in direction 2.

Default = 10E-3 * SY2T (Real)

WMPT2 Maximum plastic work in tension direction 2.

Default = 1E30 (Real)

SY1C Compression yield stress in direction 1.

(Real > 0)

B1C Hardening parameter in direction 1.

Default = B2T (Real)

N1C Hardening exponent in direction 1.

Default = N2T (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 1191

Proprietary Information of Altair Engineering


Field Contents

SMAX1C Maximum stress in direction 1.

Default = 1E30 (Real)

C1C Strain rate coefficient in direction 1.

= 0.0: no strain rate dependency.

Default = C (Real)

EPS1C1 Initial softening strain in direction 1.

Default = 1E30 (Real)

ESP2C1 Maximum softening strain in direction 1.

Default = 1.2*EPS1C1 (Real)

SRSC1 Residual stress in direction 1.

Default = 10E-3*S1YC (Real)

WMPC1 Maximum plastic work in compression direction 1.

Default = 1E30 (Real)

SY2C Compression yield stress in direction 2.

(Real > 0)

B2C Hardening parameter in direction 2.

Default = B1C (Real)

N2C Hardening exponent in direction 2

Default = N1C (Real)

SMAX2C Maximum stress in direction 2.

Default = 1E30 (Real)

C2C Strain rate coefficient in direction 2.

1192 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

= 0.0: no strain rate dependency.

Default = C (Real)

EPS1C2 Initial softening strain in direction 2.

Default = 1E30 (Real)

EPS2C2 Maximum softening strain in direction 2.

Default = 1.2*EPS1C2 (Real)

SRSC2 Residual stress in direction 2.

Default = 10E-3*S2YC (Real)

WMPC2 Maximum plastic work in compression direction 2.

Default = 1E30 (Real)

SY12T Tension yield stress in direction 12.

(Real > 0)

B12T Hardening parameter in direction 12.

Default = B2C (Real)

N12T Hardening exponent in direction 12.

Default = 1.0 (Real)

SMAX12T Maximum stress in direction 12.

Default = 1E30 (Real)

C12T Strain rate coefficient in direction 12.

= 0.0: no strain rate dependency.

Default = C (Real)

EPS1T12 Initial softening strain in direction 12.

Altair Engineering OptiStruct 13.0 Reference Guide 1193

Proprietary Information of Altair Engineering


Field Contents

Default = 1E30 (Real)

EPS2T12 Maximum softening strain in direction 12.

Default = 1.2*EPS1T12 (Real)

SRST12 Residual stress in direction 12.

Default = 10E-3*SY12T (Real)

WMPT12 Maximum plastic work in shear.

Default = 1E30 (Real)

Comments

1. The material identification number must be that of an existing MAT8 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT8.

2. MATX25 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. Tsai-Wu formula (IFORM=TSAI) is not available with QEPH (ISHELL=24 on PCOMPX) shell
elements, it is only available with Q4 (ISHELL=1,2,3,4 on PCOMPX) and QBAT(ISHELL=12
on PCOMPX) shell elements.

4. The Lamina yield surface for Tsai-Wu criteria(IFORM=TSAI) is:

with:

Wp is the plastic work

is the reference plastic work

is the yield envelope evolution:

where,

b = Hardening parameter for plastic work

n = Hardening exponent

1194 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


5. The CRASURV model is an improved version of the former law based on the standard Tsai-
Wu criteria. The main changes concern the expression of the yield surface before
plastification and during work hardening. Firstly, in a CRASURV model, the coefficient F 44
depends only on one input parameter:

Another modification concerns the parameters F ij which are expressed now in function of
plastic work and plastic work rate as below:

6. If the total tensile failure value EPSF1 is reached in the direction 1 and respectively ε
EPSF2 in the direction 2, the stresses tensor in the layer is permanently reset to 0.

Altair Engineering OptiStruct 13.0 Reference Guide 1195

Proprietary Information of Altair Engineering


7. If a shell has several layers with one material per layer (different materials, different
IOFF), the IOFF used is the one that is associated to the shell in the shell element
definition.

8. Both Wp* and Wp*max are defined as follows:

9. The plastic work criteria is:

When ICC=2,3,4 for Tsai-Wu formula, when ICCG=3,4 for CRASURV formula.

10. Delamination is a global model:

with applies to the all shell and not independently per each layer.

11. Thereby, the coefficients GAMINI, GAMMAX, and DMAX considered, are the coefficients
which are defined in the global material associated to the shell equivalent out-of-plane
shear strain.

12. The IOFF and RATIO field values are utilized only if they are defined in the material
assigned to a part, these fields are not considered if they are only defined in material
used for a layer in the property entry. This option is not available for solid elements.

13. This card is represented as extension to a MAT8 material in HyperMesh.

1196 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATX27

Bulk Data Entry

MATX27 – Material Property Extension for Elastic-Plastic Brittle Material for Geometric
Nonlinear Analysis

Description

Defines additional material properties for elastic-plastic brittle material for geometric nonlinear
analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX27 MID A B N EPSMAX SIGMAX C DEPS0

IC C

EPS1 EPS1MAX D1MAX EPSD1 EPS2 EPS2MAX D2MAX ESPD2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT1 127 60.4 0.33 2.70E-06

MATX27 127 0.09026 0.22313 0.374618 100.0 0.175

Field Contents

MID Material ID of the associated MAT1. See comment 1.

No default (Integer > 0)

A Plasticity yield stress.

(Real > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1197

Proprietary Information of Altair Engineering


Field Contents

B Plasticity hardening parameter.

(Real > 0)

N Plasticity hardening exponent.

Default = 1.0 (Real < 1.0)

EPSMAX Failure plastic strain εmax

Default = 1030 (Real > 0)

SIGMAX Maximum plastic stress σmax0

Default = 1030 (Real > 0)

C Strain rate coefficient.

Default = 0.0 (Real)

DEPS0 Reference strain rate .

Default = 0.0 (Real)

If DESPS < DESPS0, no strain rate effect.

ICC Flag for strain rate dependency of σmax . See comment 4.

Default = ON (ON or OFF)

EPS1 Tensile failure strain in principal strain direction 1.

Default = 1.0*1030 (Real > 0)

EPS1MAX Maximum tensile failure strain in principal strain direction 1.

Default = 1.1*1030 (Real > 0)

DMAX1 Maximum tensile failure damage in principal strain direction 1.

Default = 0.999 (Real > 0)

1198 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

EPSD1 Tensile strain for element deletion in principal strain direction 2.

Default = 1.2*1030 (Real > 0)

EPS2 Tensile failure strain in principal strain direction 2.

Default = 1.0*1030 (Real > 0)

EPS2MAX Maximum tensile failure strain in principal strain direction 2.

Default = 1.1*1030 (Real > 0)

DMAX2 Maximum tensile failure damage in principal strain direction 2.

Default = 0.999 (Real > 0)

EPSD2 Tensile strain for element deletion in principal strain direction 2.

Default = 1.2*1030 (Real > 0)

Comments

1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.

2. MATX27 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. This law is only applicable with shell elements. The isotropic elasto-plastic model is the
same as with MATX02. However, MATX27 allows material damage and brittle failure to be
modeled.

4. ICC controls the strain rate effect.

Altair Engineering OptiStruct 13.0 Reference Guide 1199

Proprietary Information of Altair Engineering


5. The failure plastic strain EPSMAX has no effect if the second continuation is defined.

6. An element is removed if one layer reaches the tensile failure strain EPS1.

7. This card is represented as an extension to a MAT1 material in HyperMesh.

1200 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATX28

Bulk Data Entry

MATX28 – Material Property Extension for Honeycomb Material for Geometric Nonlinear
Analysis

Description

Defines additional material properties for Honeycomb material for geometric nonlinear analysis.
This law is only applicable to solid elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX28 MID

TIID11 TIID22 TIID33 IFLAG1 FSC AI11 FSC AI22 FSC AI33

EPSFI11 EPSFI22 EPSFI33

TIID12 TIID23 TIID31 IFLAG2 FSC AI12 FSC AI23 FSC AI31

EPSFI12 EPSFI23 EPSFI31

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT9ORT 102 0.2 0.02 0.02 0.33 0.33 0.33 0.286E-7

0.1 0.01 0.1

102
MATX28

11 22 33 NEGSTR 1.0 1.0 1.0

0 0 0

12 23 31 NEGSTR 1.0 1.0 1.0

Altair Engineering OptiStruct 13.0 Reference Guide 1201

Proprietary Information of Altair Engineering


0.0 0.0 0.0

Field Contents

MID Material ID of the associated MAT9ORT. See comment 1.

No default (Integer > 0)

TIID11 Identification number of a TABLES1 that defines the initial yield stress function
in direction 11.

No default (Integer > 0)

TIID22 Identification number of a TABLES1 that defines the initial yield stress function
in direction 22.

No default (Integer > 0)

TIID33 Identification number of a TABLES1 that defines the initial yield stress function
in direction 33.

No default (Integer > 0)

IFLAG1 Strain formulation for yield functions 11, 22, and 33. See comment 4.

Default = VOLSTR (VOLSTR, STR, or NEGSTR)

VOLSTR - Yield stress is a function of volumetric strains.

STR - Yield stress is a function of strains.

NEGSTR - Yield stress is a function of negative strains.

FSCAI11 Scale factor on initial yield stress function in direction 11.

Default = 1.0 (Real)

FSCAI22 Scale factor on initial yield stress function in direction 22.

Default = 1.0 (Real)

FSCAI33 Scale factor on initial yield stress function in direction 33.

Default = 1.0 (Real)

EPSFI11 Initial failure strain under tension or compression in direction 11.

(Real)

EPSFI22 Initial failure strain under tension or compression in direction 22.

1202 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

(Real)

EPSFI33 Initial failure strain under tension or compression in direction 33.

(Real)

TIID12 Identification number of a TABLES1 that defines the initial shear yield stress
function in direction 12.

No default (Integer > 0)

TIID23 Identification number of a TABLES1 that defines the initial shear yield stress
function in direction 23.

No default (Integer > 0)

TIID31 Identification number of a TABLES1 that defines the initial shear yield stress
function in direction 31.

No default (Integer > 0)

IFLAG2 Strain formulation for yield functions 12, 23, and 31.

Default = VOLSTR (VOLSTR, STR, or NEGSTR)

VOLSTR - Yield stress is a function of volumetric strains.

STR - Yield stress is a function of strains.

NEGSTR - Yield stress is a function of negative strains.

FSCAI12 Scale factor on initial shear yield stress function in direction 12.

Default = 1.0 (Real)

FSCAI23 Scale factor on initial shear yield stress function in direction 23.

Default = 1.0 (Real)

FSCAI31 Scale factor on initial shear yield stress function in direction 31.

Default = 1.0 (Real)

EPSFI12 Initial failure strain under tension or compression in direction 12.

(Real)

EPSFI23 Initial failure strain under tension or compression in direction 23.

(Real)

Altair Engineering OptiStruct 13.0 Reference Guide 1203

Proprietary Information of Altair Engineering


Field Contents

EPSFI31 Initial failure strain under tension or compression in direction 31.

(Real)

Comments

1. The material identification number must be that of an existing MAT9ORT bulk data entry.
Only one MATX28 material extension can be associated with a particular MAT9ORT.

2. MATX28 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. This law is compatible with 10 node tetrahedron elements, and it is compatible with
ISOLID = 1, 2, or 12 on PSOLIDX card.

4. This law is not compatible with IFRAME = OFF, if it is referenced by the PSOLIDX card.

5. When switching from a volumetric strain formulation to a strain formulation, IFLAGi =


NEGSTR allows the same function definition to be retained.

6. If one of the failure or shear failure strains is reached, the element is deleted.

7. Transition strains define transition from initial yield stress function to residual yield stress
function.

8. If one of the transition or shear transition strains is reached, the element has yield stress
described by residual functions in each direction. Transition is applied to the neighboring
elements.

9. This card is represented as an extension to a MAT9ORT material in HyperMesh.

1204 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATX33

Bulk Data Entry

MATX33 – Material Property Extension for Visco-Elastic Plastic Foam Material for Geometric
Nonlinear Analysis

Description

Defines additional material properties for visco-elastic plastic foam material for geometric
nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX33 MID KA TID FSC ALE P0 PHI EPSV0

A B C E1 E2 ET ETAC ETAS

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT1 133 0.11 0.11 9.92E-07

MATX33 133 0

Field Contents

MID Material ID of the associated MAT1 (See comment 1).

No default (Integer > 0)

KA Flag for analysis type.

Default = ELAST (Character = ELAST, VISCO)

ELAST: the skeletal behavior before yield is elastic.

VISCO: the skeletal behavior before yield is visco-elastic.

Altair Engineering OptiStruct 13.0 Reference Guide 1205

Proprietary Information of Altair Engineering


Field Contents

TID Identification number of TABLES1 entry that defines the yield stress vs.
volumetric strain curve.

No default (Integer > 0)

FSCALE Scale factor for stress in yield curve.

Default = 1.0 (Real)

P0 Initial air pressure (See comment 4).

Default = 0.0 (Real)

PHI Ratio of foam to polymer density.

Default = 0.0 (Real)

EPSV0 Initial volumetric strain.

Default = 0.0 (Real)

A Yield parameter.

Default = 0.0 (Real)

B Yield parameter.

Default = 1.0 (Real)

C Yield parameter.

Default = 1.0 (Real)

E1 Coefficient for Young's modulus update.

No default (Real)

E2 Coefficient for Young's modulus update.

No default (Real)

ET Tangent modulus.

1206 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

No default (Real > 0)

ETAC Viscosity coefficient in pure compression.

Default = 1.0 (Real > 0)

ETAS Viscosity coefficient in pure shear.

Default = 1.0 (Real > 0)

Comments

1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.

2. MATX33 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. This material can be used only with solid elements, typically used to model low density,
closed cell polyurethane foams such as impact limiters.

4. The air pressure is computed as

Pair = P0 * / (1+ - Φ), with = 0 + V/V0 - 1

where, is the volumetric strain, Φ is the porosity, P0 is the initial air pressure, 0 is the
initial volumetric strain. The volumetric strain < 0 in compression.

5. If TID is blank or zero, then

σy = A + B(1+ Cγ ), with = V/V0 - 1 = ρ/ρ0 - 1 = -µ/(1+µ)

6. If TID is defined, σy vs. is read from input of the curve.

7. The Young’s modulus used in the calculation is

E = max(E, E1 + E2)

Altair Engineering OptiStruct 13.0 Reference Guide 1207

Proprietary Information of Altair Engineering


This material assumes NU = 0 no matter what is defined on the corresponding MAT1.
Hence, G = 0.5 * E.

8. This card is represented as an extension to a MAT1 material in HyperMesh.

1208 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATX36

Bulk Data Entry

MATX36 – Material Property Extension for Piece-wise Linear Elastic-plastic Material for
Geometric Nonlinear Analysis

Description

Defines additional material properties for piece-wise linear elastic-plastic material for geometric
nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX36 MID EPSMAX EPST1 EPST2 EPSF FSMOOTH FC UT IC H

TPID PSC A

TID1 FSC A1 EPSR1

... ... ...

TIDi FSC Ai EPSRI

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT1 102 60.4 0.33 2.70E-06

MATX36 102

10 1.0

7 1.0 0.0

Altair Engineering OptiStruct 13.0 Reference Guide 1209

Proprietary Information of Altair Engineering


Field Contents

MID Material identifier of the associated MAT1 (See comment 1).

No default (Integer > 0)

EPSMAX Failure plastic strain εmax

Default = 1030 (Real > 0)

EPST1 Maximum tensile failure strain (See comment 5).

Default = 1030 (Real > 0)

EPST2 Maximum tensile failure damage (See comment 6).

Default = 2.0*1030 (Real > 0)

EPSF Tensile strain for element deletion.

Default = 3.0*1030 (Real > 0)

FSMOOTH Flag for strain rate smoothing.

Default = OFF (ON or OFF)

FCUT Cutoff frequency for strain rate filtering. Only for shell and solid elements.

Default = 1030 (Real > 0)

ICH Hardening coefficient.

Default = 0.0 (Real > 0)

0.0 - The hardening is a full isotropic model.

1.0 - Hardening uses the kinematic Prager-Ziegler model.

Between 0.0 and 1.0 - Hardening is interpolated between the two models.

TPID Identification number of a TABLES1 that defines pressure dependent yield


stress function.

No default (Integer > 0)

PSCA Scale factor for stress in pressure dependent function.

1210 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Default = 1.0 (Real)

TIDi Identification number of a TABLES1 that defines the yield stress vs. plastic
strain function corresponding to EPSRi. Separate functions must be defined
for different strain rates.

No default (Integer > 0)

FSCAi Scale factor for TIDi.

Default = 1.0 (Real)

EPSRi Strain rate. Strain rate values must be given strictly in ascending order.

(Real)

Comments

1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.

2. MATX36 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. The first point of yield stress functions (plastic strain vs. stress) should have a plastic
strain value of zero. If the last point of the first (static) function equals 0 in stress, the
default value of EPSMAX is set to the value of the corresponding plastic strain.

4. When the plastic strain reaches EPSMAX, the element is deleted.

5. If the first principal strain ε1 reaches εt1 = EPST1, the stress σ is reduced by

with εt2 = EPST2.

6. If the first principal strain ε1 reaches εt2 = EPST2, the stress is reduced to 0 (but the
element is not deleted).

7. If the first principal strain ε1 reaches εf = EPSF, the element is deleted.

8. Strain rate filtering is used to smooth strain rates. The input FCUT is available only for
shell and solid elements.

9. Hardening is defined by ICH.

ICH = 0 – Fully isotropic hardening


ICH = 1 – Prager-Ziegler kinematic hardening

Altair Engineering OptiStruct 13.0 Reference Guide 1211

Proprietary Information of Altair Engineering


0 < ICH < 1 – Interpolation between the two models

10. The kinematic hardening model is not available with global formulation (NIP = 0 on
PSHELX), that is hardening is fully isotropic.

11. In case of kinematic hardening and strain rate dependency, the yield stress depends on
the strain rate.

12. TPID is used to distinguish the behavior in tension and compression for certain materials
(that is pressure dependent yield). This is available for both shell and solid elements.
The effective yield stress is then obtained by multiplying the nominal yield stress by the
yield factor PSCA corresponding to the actual pressure.

13. The first function TID1 is used for strain rate values from 0 to the corresponding strain
rate EPSR1. However, the last function used in the model does not extend to the
maximum strain rate; for higher strain rates, a linear extrapolation will be applied. Hence,
if < EPSRi, the yield stress is interpolated between TIDi and TIDi-1. If < EPSR1, TID1
is used. Above EPSRmax the yield stress is extrapolated.

14. Strain rate values must be given strictly in ascending order. Separate functions must be
defined for different strain rates.

15. At least one strain rate is needed under which the yield stress vs. plastic strain function
is defined.

16. This card is represented as a material in HyperMesh.

1212 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATX42

Bulk Data Entry

MATX42 – Material Property Extension for Ogden, Mooney-Rivlin Material for Geometric
Nonlinear Analysis

Description

Defines additional material properties for Ogden, Mooney-Rivlin material for geometric nonlinear
analysis. This material is used to model rubber, polymers, and elastomers.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX42 MID SC UT TBID FBULK

LAW MU1 ALFA1 MU2 ALFA2 MU3 ALFA3

MU4 ALFA4 MU5 ALFA5

Optional continuation lines for prony value:

PRONY G1 T1 G2 T2 G3 T3

G4 T4 G5 T5 ...

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT1 102 10.0 0.495 6.0E-10

MATX42 102

LAW 0.10 2.0 -0.010 -2.0

Altair Engineering OptiStruct 13.0 Reference Guide 1213

Proprietary Information of Altair Engineering


Field Contents

MID Material ID of the associated MAT1 (See comment 1).

No default (Integer > 0)

SCUT Cut-off stress in tension.

Default = 103 0 (Real > 0)

TBID Identification number of a TABLES1 to define the bulk function f(J) that scales
the bulk modulus vs. relative volume. If TBID = 0, f(J) = const. = 1.0.

Default = 0 (Integer > 0)

FBULK Scale factor for bulk function.

Default = 1.0 (Real > 0)

LAW Indicates that material parameters MUi and ALFAi follow.

MUi Parameter µi

(Real)

ALFAi Parameter αi

(Real)

PRONY Indicates that prony model parameters Gi and Ti follow.

Gi Parameter G for prony model.

(Real)

Ti Parameter T for prony model.

(Real)

Comments

1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.

2. MATX42 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

1214 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. Up to five pairs MUi, ALFAi are permitted.

4. The recommended Poisson’s ratio for incompressible material is NU = 0.495. NU is defined


on the corresponding MAT1.

5. The strain energy density W is computed using the following equation

with λi being the ith principal stretch (λi = 1 + ε i


, ε i
is the ith principal engineering
strain). The Cauchy stress is computed as follows:

with J = λ1 * λ2 * λ3 being the relative volume:

The quantity P is the pressure:

P = K * FBULK * f (J) * (J - 1)

The Bulk Modulus K is:

with the ground shear modulus µ:

6. An incompressible Mooney-Rivlin material is governed by

W = C1 0 (I1 - 3) + C0 1 (I2 - 3)

where, Ii is ith invariant of the right-hand Cauchy-Green Tensor. It can be modeled using
the following parameters:

µ1 = 2 * C1 0

Altair Engineering OptiStruct 13.0 Reference Guide 1215

Proprietary Information of Altair Engineering


µ2 = -2 * C0 1

α1 = 2.0

α2 = -2.0

7. The Kirchhoff viscous stress is given by the convolution integral:

and

8. This card is represented as a material in HyperMesh.

1216 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATX43

Bulk Data Entry

MATX43 – Material Property Extension for Hill Orthotropic Material for Geometric Nonlinear
Analysis

Description

Defines additional material properties for Hill Orthotropic material for geometric nonlinear
analysis. This law is only applicable to two-dimensional elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX43 MID R00 R45 R90 C HARD EPSPF EPST1 EPST2

If strain rate dependent material, at least 1 time, at most 10 times

TID1 FSC A1 EPSR1

TID2 FSC A2 EPSR2

… … …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT8 102 0.7173 0.7173 0.3 0.4 2.7

MATX43 102 1.0 1.0 2.0

1 1.0 0.1

2 1.0 0.05

Altair Engineering OptiStruct 13.0 Reference Guide 1217

Proprietary Information of Altair Engineering


Field Contents

MID Material ID of the associated MAT8. See comment 1.

No default (Integer > 0)

R00 Lankford parameter at 0 degree.

Default = 1.0 (Real)

R45 Lankford parameter at 45 degrees.

Default = 1.0 (Real)

R90 Lankford parameter at 90 degrees.

Default = 1.0 (Real)

CHARD Hardening coefficient.

0.0 - The hardening is a full isotropic model.


1.0 - Hardening uses the kinematic Prager-Ziegler model.
Between 0.0 and 1.0 - Hardening is interpolated between the two models.

Default = 0.0 (1.0 > Real > 0.0)

EPSPF Failure plastic strain.

Default = 1030 (Real)

EPST1 Tensile failure strain.

Default = 1030 (Real)

EPST2 Tensile failure strain.

Default = 2.0*1030 (Real)

TIDi Identification number of a TABLES1 that defines the yield stress vs. plastic
strain function corresponding to EPSRi. Separate functions must be defined
for different strain rates.

Integer > 0

1218 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

FSCAi Scale factor for ith function.

Default= 1.0 (Real)

EPSRi Strain rate for ith function.

(Real)

Comments

1. The material identification number must be that of an existing MAT8 bulk data entry. Only
one MATX43 material extension can be associated with a particular MAT8. E1 must be
equal to E2 on MAT8 that is extended by MATX43.

2. MATX43 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. The yield stress is defined by a user function and the yield stress is compared to
equivalent stress.

4. Angles for Lankford parameters are defined with respect to orthotropic direction 1.

5. The Lankford parameters rα are determined from a simple tensile test at an angle α to the
orthotropic direction 1.

6. The hardening coefficient is used to describe the hardening model. Its value must be
between 0 and 1:

if set to 0, the hardening is full isotropic.


if set to 1, the hardening uses the kinematic Prager-Ziegler model.

Altair Engineering OptiStruct 13.0 Reference Guide 1219

Proprietary Information of Altair Engineering


for any value between 0 and 1, the hardening is interpolated between the two models.

7. If the last point of the first (static) function equals 0 in stress, default value of failure
plastic strain EPSPF is set to the corresponding value of plastic strain, p.

8. If plastic strain εp reaches failure plastic strain εpmax , the element is deleted.

9. If ε1 (largest principal strain) > εt1(EPST1), stress is reduced according to the following
relation:

10. If ε1 (largest principal strain) > εt2(EPST2), the stress is reduced to be 0 (but the
element is not deleted). If (EPSRn), yield is interpolated between ƒn and ƒn-1. If

(EPSR1), function ƒ1 is used. Above , yield is extrapolated.

11. This card is represented as extension to a MAT8 material in HyperMesh.

1220 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATX44

Bulk Data Entry

MATX44 – Material Property Extension for Cowper-Symonds Elastic-plastic Material for


Geometric Nonlinear Analysis

Description

Defines additional material properties for Cowper-Symonds elastic-plastic material for


geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX44 MID A B N IC H SIGMAX C P

IC C FSMOOTH FC UT EPSMAX EPST1 EPST2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT1 144 0.11 0.11 9.92E-07

MATX44 144

Field Contents

MID Material ID of the associated MAT1.

No default (Integer > 0)

A Plasticity yield stress.

(Real > 0)

B Plasticity hardening parameter.

(Real > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1221

Proprietary Information of Altair Engineering


Field Contents

N Plasticity hardening exponent.

Default = 1.0 (Real)

ICH Hardening coefficient.

0.0: The hardening is a full isotropic model.


1.0: Hardening uses the kinematic Prager-Ziegler model.
Between 0.0 and 1.0: Hardening is interpolated between the two models.

Default = 0.0 (Real > 0)

SIGMAX Maximum plastic stress σmax0

Default = 1030 (Real > 0)

C Strain rate coefficient.

Default = 0.0 (Real)

P Strain rate exponent.

Default = 1.0 (Real)

ICC Flag for strain rate dependency of σmax (See comment 5).

Default = ON (ON or OFF)

FSMOOTH Flag for strain rate smoothing.

Default = OFF (ON or OFF)

FCUT Cutoff frequency for strain rate filtering.

Default = 1030 (Real > 0)

EPSMAX Failure plastic strain.

Default = 1030 (Real > 0)

EPST1 Tensile rupture strain 1.

1222 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Default = 1030 (Real > 0)

EPST2 Tensile rupture strain 2.

Default = 2.0 * 1030 (Real > 0)

Comments

1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.

2. MATX44 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. The Cowper-Symonds models an elastic-plastic material, only for solids and shells. The
basic principle is the same as the standard Johnson-Cook model; the only difference
between the two lies in the expression for strain rate effect on flow stress

with εp being plastic strain, and being the strain rate.

4. Hardening is defined by ICH.

ICH = 0 – Fully isotropic hardening.


ICH = 1 – Prager-Ziegler kinematic hardening.
0 < ICH < 1 – Interpolation between the two models.

5. ICC controls the strain rate effect.

Altair Engineering OptiStruct 13.0 Reference Guide 1223

Proprietary Information of Altair Engineering


6. No strain rate effects are considered in rod elements.

7. Strain rate filtering is used to smooth strain rates. The input FCUT is available only for
shell and solid elements.

8. When the plastic strain reaches EPSMAX, the element is deleted.

9. If the first principal strain ε1 reaches εt1 = EPST1, the stress σ is reduced by

with εt2 = EPST2.

10. If the first principal strain ε1 reaches εt2 = EPST2, the stress is reduced to 0 (but the
element is not deleted).

11. If the first principal strain ε1 reaches εf = EPSF, the element is deleted.

12. This card is represented as an extension to a MAT1 material in HyperMesh.

1224 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATX60

Bulk Data Entry

MATX60 – Material Property Extension for Piece-wise Nonlinear Elastic-plastic Material for
Geometric Nonlinear Analysis

Description

Defines additional material properties for piece-wise nonlinear elastic-plastic material for
geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX60 MID EPSPF EPST1 EPST2 FSMOOTH C HARD FC UT EPSF

TPID PSC A

Strain rate dependent material, at least 4 times, at most 10 times:

TID1 FSC A1 EPSR1

TID2 FSC A2 EPSR2

... ... ...

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT1 102 900 0.33 1E1

MATX60 102

101 1.0 4.2E-7

102 1.0 4.2e6

Altair Engineering OptiStruct 13.0 Reference Guide 1225

Proprietary Information of Altair Engineering


Field Contents

MID Material ID of the associated MAT1 (See comment 1).

No default (Integer > 0)

EPSPF Failure plastic strain.

Default = 1030 (Real > 0)

EPST1 Maximum tensile failure strain (See comment 5).

Default = 1030 (Real > 0)

EPST2 Maximum tensile failure damage (See comment 6).

Default = 2.0*1030 (Real > 0)

FSMOOTH Flag for strain rate smoothing.

Default = OFF (ON or OFF)

CHARD Hardening coefficient.

0.0: The hardening is a full isotropic model.


1.0: Hardening uses the kinematic Prager-Ziegler model.
Between 0.0 and 1.0: Hardening is interpolated between the two models.

Default = 0.0 (1.0 > Real > 0)

FCUT Cutoff frequency for strain rate filtering. Only for shell and solid elements.

Default = 1030 (Real > 0)

EPSF Tensile strain for element deletion.

Default = 3.0*1030 (Real > 0)

TPID Identification number of a TABLES1 that defines pressure dependent yield


stress function.

No default (Integer > 0)

PSCA Scale factor for stress in pressure dependent function.

1226 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Default = 1.0 (Real)

TIDi Identification number of a TABLES1 that defines the yield stress vs. plastic
strain rate function corresponding to EPSRi. Separate functions must be
defined for different strain rates.

No default (Integer > 0)

FSCAi Scale factor for TIDi.

Default = 1.0 (Real)

EPSRi Strain rate. Strain rate values must be given strictly in ascending order.

(Real)

Comments

1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATX60 material extension can be associated with a particular MAT1.

2. MATX60 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. The first point of yield stress functions (plastic strain vs. stress) should have a plastic
strain value of zero. If the last point of the first (static) function equals 0 in stress, the
default value of EPSMAX is set to the value of the corresponding plastic strain.

4. When the plastic strain reaches EPSMAX, the element is deleted.

5. If the first principal strain ε1 reaches εt1 (EPST1), the stress σ is reduced by

with εt2 = EPST2.

6. If the first principal strain ε1 reaches εt2 (EPST2), the stress is reduced to 0 (but the
element is not deleted).

7. If the first principal strain ε1 reaches εf (EPSF), the element is deleted.

8. Strain rate filtering is used to smooth strain rates. The input FCUT is available only for
shell and solid elements.

9. Hardening is defined by ICH.

Altair Engineering OptiStruct 13.0 Reference Guide 1227

Proprietary Information of Altair Engineering


ICH = 0 – Fully isotropic hardening

ICH = 1 – Prager-Ziegler kinematic hardening

0 < ICH < 1 – Interpolation between the two models

Isotropic Hardening Prager-Ziegler Kinematic Hardening

10. The kinematic hardening model is not available with global formulation (NIP = 0 on
PSHELX), that is hardening is fully isotropic.

11. In case of kinematic hardening and strain rate dependency, the yield stress depends on
the strain rate.

12. TPID is used to distinguish the behavior in tension and compression for certain materials
(that is pressure dependent yield). This is available for solid elements only. The effective
yield stress is then obtained by multiplying the nominal yield stress by the yield factor
PSCA corresponding to the actual pressure.

13. If ( =EPSRn) , yield stress is a cubic interpolation between functions f n-


1, f n, f n+1 and f n+2.

If , yield stress is interpolated between functions f 1, f 2, and f 3.

If , where Nfunc is the function number for strain rate, yield is


extrapolated between functions f Nfunc-3, f Nfunc-2, f Nfunc-1 and f Nfunc.

If , yield is extrapolated between functions f Nfunc-2, f Nfunc-1, and f Nfunc.

14. Strain rate values must be given strictly in ascending order. Separate functions must be
defined for different strain rates.

15. This card is represented as an extension to a MAT1 material in HyperMesh.

1228 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATX62

Bulk Data Entry

MATX62 – Material Property Extension for Hyper-visco-elastic Material for Geometric Nonlinear
Analysis

Description

Defines additional material properties for Hyper-visco-elastic material for geometric nonlinear
analysis. This material is used to model rubber, polymers, and elastomers.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX62 MID MUMAX

LAW MU1 ALFA1 MU2 ALFA2 MU3 ALFA3

MU4 ALFA4 MU5 ALFA5 ...

Optional continuation lines for Maxwell value:

MAXWELL GAM1 T1 GAM2 T2 GAM3 T3

GAM4 T4 GAM5 T5 ...

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT1 102 10.0 0.495 6.0E-10

MATX62 102

LAW 0.10 2.0 -0.010 -2.0

Altair Engineering OptiStruct 13.0 Reference Guide 1229

Proprietary Information of Altair Engineering


Field Contents

MID Material ID of the associated MAT1 (See comment 1).

No default (Integer > 0)

MUMAX Maximum viscosity.

Default = 1030 (Real)

LAW Indicates that material parameters MUi and ALFAi follow.

MUi Parameter µi

(Real)

ALFAi Parameter αi

(Real)

MAXWELL Indicates that MAXWELL model parameter pairs GAMi and Ti follow.

GAMi Stiffness ratio γ i.

(Real)

Ti Time relaxation τi.

(Real)

Comments

1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.

2. MATX62 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. This material is compatible with solid and shell elements.

4. NU is defined on the corresponding MAT1.

5. If no pair GAM1, T1 is given the law is hyper-elastic.

1230 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


6. The strain energy density W is computed using the following equation:

with λi being the ith principal stretch, J = λ1 * λ2 * λ3 being the relative volume and

. O < NU < 0.5

The ground shear modulus is:

7. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1231

Proprietary Information of Altair Engineering


MATX65

Bulk Data Entry

MATX65 – Material Property Extension for Tabulated Strain Rate Dependent Elastic-Plastic
Material for Geometric Nonlinear Analysis

Description

Defines additional material properties for tabulated strain rate dependent elastic-plastic
material for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX65 MID EPSMAX FSMOOTH FC UT NLOAD

If NLOAD > 1, NLOAD times

TIDL TIDU EPSR FSC AL

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT1 91 60.4 0.33 2.70E-06

MATX65 91 2.70E-06 1

1 2

Field Contents

MID Material ID of the associated MAT1 (See comment 1).

No default (Integer > 0)

1232 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

EPSMAX Failure plastic strain εmax

(Real > 0)

FSMOOTH Strain rate filtering flag.

Default = OFF (ON or OFF)

FCUT Cutoff frequency for strain rate filtering.

Default = 1.E30 (Real > 0)

NLOAD Number of loading/unloading stress-strain function pairs.

Default = 0 (Integer > 0)

TIDL Identification number of TABLES1 entry that defines the loading stress-strain
function.

(Integer > 0)

TIDU Identification number of TABLES1 entry that defines the unloading stress-
strain function.

(Integer > 0)

EPSR Strain rate.

Default = 1.0 (Real)

FSCAL Scale factor for stress.

Default = 1.0 (Real)

Comments

1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.

2. MATX65 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. The material law is defined by pairs of stress functions for loading and unloading at a
constant strain rate. For each strain rate, the yield stress is defined by the intersection
between loading and unloading curves. Unloading follows unloading curve shifted by
plastic strain value. Strain rates are interpolated using input values. In the elastic range,
stress smaller than the yield value, the material behavior is elastic with hysteresis. It is

Altair Engineering OptiStruct 13.0 Reference Guide 1233

Proprietary Information of Altair Engineering


limited by loading and unloading curves.

Loading and unloading function sets for constant strain rates.

The Young's modulus must be greater than the maximum function slopes, and is used to
follow loading and unloading paths between limiting curves.

For a constant strain rate, user defined functions set the limits for the cycling loading.

1234 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


4. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1235

Proprietary Information of Altair Engineering


MATX68

Bulk Data Entry

MATX68 – Material Property Extension for Honeycomb Material for Geometric Nonlinear
Analysis

Description

Defines additional material properties for Honeycomb material for geometric nonlinear analysis.
This law is only applicable to solid elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX68 MID

TIID11 TIID22 TIID33 IFLAG1 FSC AI11 FSC AI22 FSC AI33

EPSFI11 EPSFI22 EPSFI33

TIID12 TIID23 TIID31 IFLAG2 FSC AI12 FSC AI23 FSC AI31

EPSFI12 EPSFI23 EPSFI31

TIID21 TIID32 TIID13 FSC AI21 FSC AI32 FSC AI13

TRID11 TRID22 TRID33 FSC AR11 FSC AR22 FSC AR33

EPST11 EPST22 EPST33

TRID12 TRID23 TRID31 FSC AR12 FSC AR23 FSC AR31

EPST12 EPST23 EPST31

TRID21 TRID32 TRID13 FSC AR21 FSC AR32 FSC AR13

Example

1236 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT9ORT 102 0.2 0.02 0.02 0.33 0.33 0.33 0.286E-7

0.1 0.01 0.1

102
MATX68

11 22 33 NEGSTR 1.0 1.0 1.0

0 0 0

12 23 31 NEGSTR 1.0 1.0 1.0

0.0 0.0 0.0

21 32 13 1.0 1.0 1.0

11 22 33 1.0 1.0 1.0

0.8 0.0 0.0

12 23 31 1.0 1.0 1.0

0.0 0.0 0.0

21 32 13 1.0 1.0 1.0

Field Contents

MID Material ID of the associated MAT9ORT. See comment 1.

No default (Integer > 0)

TIID11 Identification number of a TABLES1 that defines initial yield stress function in
direction 11.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1237

Proprietary Information of Altair Engineering


Field Contents

TIID22 Identification number of a TABLES1 that defines initial yield stress function in
direction 22.

No default (Integer > 0)

TIID33 Identification number of a TABLES1 that defines initial yield stress function in
direction 33.

No default (Integer > 0)

IFLAG1 Strain formulation for yield functions 11, 22, and 33. See comment 4.

VOLSTR - Yield stress is a function of volumetric strains.


STR - Yield stress is a function of strains.
NEGSTR - Yield stress is a function of negative strains.

Default = VOLSTR (VOLSTR, STR, NEGSTR)

FSCAI11 Scale factor on initial yield stress function in direction 11.

Default = 1.0 (Real)

FSCAI22 Scale factor on initial yield stress function in direction 22.

Default = 1.0 (Real)

FSCAI33 Scale factor on initial yield stress function in direction 33.

Default = 1.0 (Real)

EPSFI11 Initial failure strain under tension or compression in direction 11.

(Real)

EPSFI22 Initial failure strain under tension or compression in direction 22.

(Real)

EPSFI33 Initial failure strain under tension or compression in direction 33.

(Real)

TIID12 Identification number of a TABLES1 that defines initial shear yield stress

1238 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

function in direction 12.

No default (Integer > 0)

TIID23 Identification number of a TABLES1 that defines Initial shear yield stress
function in direction 23.

No default (Integer > 0)

TIID31 Identification number of a TABLES1 that defines Initial shear yield stress
function in direction 31.

No default (Integer > 0)

IFLAG2 Strain formulation for yield functions 12, 23, and 31.

VOLSTR - Yield stress is a function of volumetric strains.


STR - Yield stress is a function of strains.
NEGSTR - Yield stress is a function of negative strains.

Default = VOLSTR (VOLSTR, STR, NEGSTR)

FSCAI12 Scale factor on initial shear yield stress function in direction 12.

Default = 1.0 (Real)

FSCAI23 Scale factor on initial shear yield stress function in direction 23.

Default = 1.0 (Real)

FSCAI31 Scale factor on initial shear yield stress function in direction 31.

Default = 1.0 (Real)

EPSFI12 Initial failure strain under tension or compression in direction 12.

(Real)

EPSFI23 Initial failure strain under tension or compression in direction 23.

(Real)

EPSFI31 Initial failure strain under tension or compression in direction 31.

Altair Engineering OptiStruct 13.0 Reference Guide 1239

Proprietary Information of Altair Engineering


Field Contents

(Real)

TIID21 Identification number of a TABLES1 that defines Initial shear yield stress
function in direction 21.

No default (Integer > 0)

TIID32 Identification number of a TABLES1 that defines Initial shear yield stress
function in direction 32.

No default (Integer > 0)

TIID13 Identification number of a TABLES1 that defines Initial shear yield stress
function in direction 13.

No default (Integer > 0)

FSCAI21 Scale factor on initial shear yield stress function in direction 21.

Default = 1.0 (Real)

FSCAI32 Scale factor on initial shear yield stress function in direction 32.

Default = 1.0 (Real)

FSCAI13 Scale factor on initial shear yield stress function in direction 13.

Default = 1.0 (Real)

TRID11 Identification number of a TABLES1 that defines residual yield stress function
in direction 11.

No default (Integer > 0)

TRID22 Identification number of a TABLES1 that defines residual yield stress function
in direction 22.

No default (Integer > 0)

TRID33 Identification number of a TABLES1 that defines residual yield stress function
in direction 33.

No default (Integer > 0)

1240 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

FSCAR11 Scale factor on residual yield stress function in direction 11.

Default = 1.0 (Real)

FSCAR22 Scale factor on residual yield stress function in direction 22.

Default = 1.0 (Real)

FSCAR33 Scale factor on residual yield stress function in direction 33.

Default = 1.0 (Real)

EPST11 Transition strain in direction 11.

(Real)

EPST22 Transition strain in direction 22.

(Real)

EPST33 Transition strain in direction 33.

(Real)

TRID12 Identification number of a TABLES1 that defines residual shear yield stress
function in direction 12.

No default (Integer > 0)

TRID23 Identification number of a TABLES1 that defines residual shear yield stress
function in direction 23.

No default (Integer > 0)

TRID31 Identification number of a TABLES1 that defines residual shear yield stress
function in direction 31.

No default (Integer > 0)

FSCAR12 Scale factor on residual shear yield stress function in direction 12.

Default = 1.0 (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 1241

Proprietary Information of Altair Engineering


Field Contents

FSCAR23 Scale factor on residual shear yield stress function in direction 23.

Default = 1.0 (Real)

FSCAR31 Scale factor on residual shear yield stress function in direction 31.

Default = 1.0 (Real)

EPST12 Transition strain in direction 12.

(Real)

EPST23 Transition strain in direction 23.

(Real)

EPST31 Transition strain in direction 31.

(Real)

TRID21 Identification number of a TABLES1 that defines residual shear yield stress
function in direction 21.

No default (Integer > 0)

TRID32 Identification number of a TABLES1 that defines residual shear yield stress
function in direction 32.

No default (Integer > 0)

TRID13 Identification number of a TABLES1 that defines residual shear yield stress
function in direction 13.

No default (Integer > 0)

FSCAR21 Scale factor on residual shear yield stress function in direction 21.

Default = 1.0 (Real)

FSCAR32 Scale factor on residual shear yield stress function in direction 32.

Default = 1.0 (Real)

1242 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

FSCAR13 Scale factor on residual shear yield stress function in direction 13.

Default = 1.0 (Real)

Comments

1. The material identification number must be that of an existing MAT9ORT bulk data entry.
Only one MATX68 material extension can be associated with a particular MAT9ORT.

2. MATX68 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. This law is compatible with 8 node brick elements with ISOLID =1 or ISOLID =2 on
PSOLIDX only.

4. When switching from a volumetric strain formulation to a strain formulation, IFLAGi =


NEGSTR allows the same function definition to be retained.

5. If one of the failure or shear failure strains is reached, the element is deleted.

6. Transition strains define transition from initial yield stress function to residual yield stress
function.

7. If one of the transition or shear transition strains is reached, the element has yield stress
described by residual functions in each direction, Transition is applied to the neighbor
elements.

8. This card is represented as extension to a MAT9ORT material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1243

Proprietary Information of Altair Engineering


MATX70

Bulk Data Entry

MATX70 – Material Property Extension for Tabulated Visco-elastic Foam Material for
Geometric Nonlinear Analysis

Description

Defines additional material properties for tabulated visco-elastic foam material for geometric
nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX70 MID EMAX EPSMAX FSMOOTH FC UT NLOAD NULOAD IFLAG

SHAPE HYS

If NLOAD > 1, NLOAD times

TIDL EPSRL FSC ALL

If NULOAD > 0, NULOAD times

TIDU EPSRU FSC ALU

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT1 170 0.1 0.1 9.9E-07

MATX70 170 1.0 0.8 1 4

1244 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

MID Material ID of the associated MAT1 (See comment 1).

No default (Integer > 0)

EMAX Maximum young modulus .

(Real > 0)

EPSMAX Maximum plastic (failure) strain.

(Real > 0)

FSMOOTH Strain rate smoothing flag.

Default = OFF (ON or OFF)

FCUT Cutoff frequency for strain rate filtering.

Default = 1.E30 (Real > 0)

NLOAD Number of loading stress-strain function.

Default = 1 (Integer > 1)

NULOAD Number of unloading stress-strain function. If FLAG in this card is 1, 2, 3, or


4, NULOAD must be zero.

Default = 1, if FLAG = 0
Default = 0, if FLAG = 1, 2, 3, or 4

(Integer > 0)

IFLAG Flag to control the loading/unloading behavior (See comment 5).

Default = 0 (Integer)

0 – Behavior follows the loading and unloading curves respectively.

1 – Behavior follows the loading/unloading curves. For unloading, the


deviatoric stress is modified.

2 – Behavior follows the loading/unloading curves. For unloading, the stress


tensor is modified.

Altair Engineering OptiStruct 13.0 Reference Guide 1245

Proprietary Information of Altair Engineering


Field Contents

3 – The loading curve is used for both loading and unloading. For unloading,
the deviatoric stress is modified. The unloading curves are ignored.

4 - The loading curve is used for both loading and unloading. For unloading,
the stress tensor is modified. The unloading curves are ignored.

SHAPE Shape factor.

Default = 1.0 (Real)

HYS Hysteresis unloading factor.

Default = 1.0 (Real)

TIDL Identification number of TABLES1 entry that defines the loading function.

(Integer > 0)

EPSRL Strain rate for loading function.

Default = 0.0 (Real)

FSCALL Scale factor for loading function.

Default = 1.0 (Real)

TIDU Identification number of TABLES1 entry that defines the unloading function.

No default (Integer > 0)

EPSRU Strain rate for unloading function.

Default = 0.0 (Real)

FSCALU Scale factor for unloading function.

Default = 1.0 (Real)

Comments

1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.

2. MATX70 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

1246 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. This material law can be used only with solid elements. The corresponding PSOLIDX
property must define ISOLID = 1 (Belytschko element), ISMSTR = 1 (small strain), and
IFRAME = OFF (not co-rotational).

4. The loading and unloading functions use engineering stress-strain curve.

Loading and unloading stress-strain curves

5. The loading and unloading behavior is determined by IFLAG.

IFLAG = 0 - The material behavior follows the defined curves for loading and unloading.
NLOAD and NULOAD must be greater than 0.
IFLAG = 1 - Both loading curves are used respectively. For unloading, the deviatoric
stress is modified by using the quasi-static unloading curve

σ = (1 - D)(σ + p*I) – p*I

where, D is calculated from the quasi-static unloading curve,

are the current stresses computed respectively from the unloading and quasi-static
curves.

The pressure is:

p = -(σxx + σyy + σzz) / 3

IFLAG = 2 - Both loading and unloading curves are used respectively. For unloading,
the stress tensor is modified using the quasi-static unloading curve σ = (1 - D)σ, where
D is calculated from the quasi-static unloading curve,

are the current stresses computed respectively from the unloading and quasi-static
curves.

Altair Engineering OptiStruct 13.0 Reference Guide 1247

Proprietary Information of Altair Engineering


IFLAG = 3 - The loading curves are used for both loading and unloading behavior. The
unloading curve is ignored. The deviatoric unloading stress is modified using

σ = (1 - D)(σ + p*I) – p*I

where, Wcur and Wmax are the current and maximum energy, respectively.

IFLAG = 4 - The loading curves are used for both loading and unloading behavior. The
unloading curve is ignored. The unloading stress tensor is modified using σ = (1 - D)σ.

where, Wcur and Wmax are the current and maximum energy, respectively.

For IFLAG = 3, 4 the unloading curves are not used.

6. For stresses above the last load function, the behavior is extrapolated by using the two
last load functions. In order to avoid huge stress values, it is recommended to repeat the
last load function.

7. When maximum plastic strain EPSMAX is reached, EMAX is used whatever the curve
definition is.

8. If EMAX is blank, EMAX is set and equal to Young modulus on MAT1 card.

9. If EPSMAX is blank, it will be calculated automatically if EMAX is less than the maximum
tangent according to the input stress-strain curves.

10. Young's modulus E on MAT1 card would be modified automatically if it is less than the
initial value according to the input stress-strain curves' tangents.

11. This card is represented as a material in HyperMesh.

1248 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MATX82

Bulk Data Entry

MATX82 – Material Property Extension for Ogden Material for Geometric Nonlinear Analysis

Description

Defines additional material properties for Ogden material for geometric nonlinear analysis. This
material is used to model rubber, polymers, and elastomers.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MATX82 MID

LAW MU1 ALFA1 D1 MU2 ALFA2 D2

MU3 ALFA3 D3 MU4 ALFA4 D4

...

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MAT1 102 10.0 0.495 6.0E-10

MATX82 102

LAW 0.10 2.0 -0.010 -2.0

Field Contents

MID Material ID of the associated MAT1 (See comment 1).

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1249

Proprietary Information of Altair Engineering


Field Contents

LAW Indicates that material parameters MUi, ALFAi, and Di follow.

MUi Parameter µi

(Real)

ALFAi Parameter αi

(Real)

Di Parameter Di

(Real)

Comments

1. The material identification number must be that of an existing MAT1 bulk data entry. Only
one MATXi material extension can be associated with a particular MAT1.

2. MATX82 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. NU is defined on the corresponding MAT1. For material without Poisson effect, a small NU
(for example, =1.E-10) should be defined.

4. The strain energy density W is computed using the following equation

with λi being the ith principal stretch, J = λ1 * λ2 * λ3 being the relative volume and

5. The Bulk Modulus K is:

If NU = 0, then

1250 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


1
is modified to respect

If NU = 0 and D1 = 0, then u = 0.475.


6. The ground shear modulus is

7. This card is represented as a material in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1251

Proprietary Information of Altair Engineering


MBACT

Bulk Data Entry

MBACT – Activate an Entity/set in the Multi-body System

Description

Defines the entity/set that needs to be activated in the multi-body system for the
subsequent simulation.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBAC T ID ETYPE ID1 ID2 ID3 …

or

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBAC T ID ETYPE IDST THRU IDEND

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBAC T ID MOTION 92

Field Contents

ID Unique identification number.

(Integer > 0)

ETYPE Entity type that needs to be activated.

(Option – "CMBEAM", "CMBUSH", "CMSPDP", "JOINT", "MLOAD", or "MOTION")

1252 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

ID1, ID2, … Entity/Set IDs that need to be activated.

(Integer > 0)

IDST Entity/Set ID range start.

(Integer > 0)

THRU Keyword to indicate entity/set ID range is specified.

IDEND Entity/Set ID range end.

(Integer > IDST)

Comments

1. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1253

Proprietary Information of Altair Engineering


MBCNTDS

Bulk Data Entry

MBCNTDS – Multi-body Contact with Deformable Surface

Description

Defines a Multi-body Contact between a set of nodes and a deformable surface.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBC NTDS C ID SID SRFID C NFTYPE STIFF DAMP RADIUS

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBC NTD 2 21 4 LINEAR 1E6 10 .1


S

Field Contents

CID Contact identification number.

No default (Integer > 0)

SID1 Set identification number of a set of nodes.

No default (Integer > 0)

SRFID Multi-body deformable surface (MBDSRF) identification number.

No default (Integer > 0)

CNFTYPE Contact Normal Force Type. Select from LINEAR and POISSON.

No default (CHARACTER: LINEAR, POISSON)

STIFF For CNFTYPE=LINEAR, this parameter specifies the interface stiffness


coefficient.

For CNFTYPE=POISSON, this parameter specifies the penalty parameter

1254 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

which is related to the stiffness RJTODO.

Default = 0.0 (Real > 0.0)

DAMP For CNFTYPE=LINEAR, this parameter specifies the interface damping.

Default = 0.0 (Real > 0)

For CNFTYPE=POISSON, this parameter specifies the coefficient of restitution


value for the contact.

Default = 1.0 (0.0 < Real < 1.0)

RADIUS Radius of the sphere geometry centered at the origin of the I marker.

Default = 0.0 (Real > 0)

Comments

1. This card is represented as a group in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1255

Proprietary Information of Altair Engineering


MBCNTR

Bulk Data Entry

MBCNTR – Multi-body Contact of Type Rigid to Rigid

Description

Defines a Multi-body Contact between rigid bodies.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBC NTR C ID SID1 SID2 C NFTYPE PENAL C OR MUSTAT MUDYN

C FFTYPE STVEL FTVEL

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBC NTR 2 4 7 POISSON 1E6 .5 .7 .3

C OUL .1 .8

Field Contents

CID Contact identification number.

No default (Integer > 0)

SID1 Set identification number for a set of elements.

No default (Integer > 0)

SID2 Set identification number for a set of elements.

CNFTYPE Contact normal force type.

Default = POISSON

PENAL Penalty factor.

1256 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Default = 1.0 (Real > 0.0)

COR Coefficient of restitution.

Default = 1.0 (0.0 < Real < 1.0)

MUSTAT Coefficient of static friction.

Default = 0.0 (Real > 0.0)

MUDYN Coefficient of dynamic friction.

Default = 0.0 (Real > 0.0)

CFFTYPE Contact friction force type

Default = (COUL, NONE, DYNA)

STVEL Stiction transition velocity. Defines the slip velocity at which the static
coefficient of friction MUSTAT is applied.

Default = 0.0 (Real > 0.0)

FTVEL Friction transition velocity. Defines the slip velocity at which the
dynamic coefficient of friction MUDYN is applied.

Default = 0.0 (Real > 0.0)

Comments

1. This card is represented as a group in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1257

Proprietary Information of Altair Engineering


MBCRV

Bulk Data Entry

MBCRV – XY Curve Definition

Description

Specifies the data used to define a curve.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBC RV C VID LINEAR

X1 Y1 X2 Y2 … … Xn Yn

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBC RV 399

1.0 1.1 2.0 0.0 3.0 14.2 4.0 19.9

5.0 12.1

Field Contents

CVID Curve identification number.

No default (Integer > 0)

LINEAR If the LINEAR keyword is specified, linear extrapolation is used to


determine the curve data when the independent coordinate goes out of
the range specified on the Xi fields.

If this field is blank, no extrapolation is applied and an ERROR is output


when the independent coordinate goes out of range.

1258 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Default = blank

X1, X2, X3, …, Independent curve data.


Xn
No default (Real, X1 < X2 < X3 < …)

Y1, Y2, Y3, …, Dependent curve data.


Yn
No default (Real)

Comments

1. This card is represented as a curve in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1259

Proprietary Information of Altair Engineering


MBCVCV

Bulk Data Entry

MBCVCV – Multi-body Curve to Curve Constraint

Description

Defines a Curve to Curve Constraint.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBC VC V JID blank PC ID1 G3 V1

blank blank PC ID2 G4 V2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBC VC V 1 1 0 0

2 0 1

Field Contents

JID Joint identification number.

No default (Integer > 0)

PCID1 Parametric curve (MBPCRV) identification number.

No default (Integer > 0)

PCID2 Parametric curve (MBPCRV) identification number.

No default (Integer > 0)

G3 This grid specifies the guess for the initial contact point on the first
curve.

1260 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Although this parameter is optional, specifying it helps the solver in


determining the initial contact point.

V1 Specifies the sliding velocity of the contact point relative to the part on
which the curve is etched. V1 is positive when contact point is moving
toward the start of the curve and vice-versa.

Default = 0.0 (Real)

G4 This grid specifies the guess for the initial contact point on the second
curve.

Although this parameter is optional, specifying it helps the solver in


determining the initial contact point.

V2 Specifies the sliding velocity of the contact point relative to the part on
which the curve is etched. V2 is positive when contact point is moving
toward the start of the curve and vice-versa.

Default = 0.0 (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 1261

Proprietary Information of Altair Engineering


MBDCRV

Bulk Data Entry

MBDCRV – Multi-body Deformable Curve

Description

Defines an ordered list of grids as a Multi-body Deformable Curve.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBDC RV ENDTYPE ENDTYPE LAMBDA


DC ID LAMBDAL NSEG
L R R

G1 G2 G3 …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBDC RV NATURA C ANTILEVE


1 0.5 100 5
L R

201 202 203 204 205

Field Contents

DCID Curve identification number.

No default (Integer > 0)

ENDTYPEL Select from NATURAL, PARABOLIC, PERIODIC and CANTILEVER. See comment
1.

Default = NATURAL

LAMBDAL This parameter is only applicable for CANTILEVER type end condition. It should
be left blank for other end conditions.

A real valued parameter in the interval [0,1] that controls the left end
condition for CUBIC spline interpolation. A value of 0 implies NATURAL end
condition while a value of 1 implies PARABOLIC end condition.

1262 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Default = 0.0 (0.0 < Real < 1.0)

ENDTYPER Select from: NATURAL, PARABOLIC, PERIODIC and CANTILEVER. See comment
1.

Default = NATURAL

LAMBDAR This parameter is only applicable for CANTILEVER type end condition. It should
be left blank for other end conditions.

A real valued parameter in the interval [0,1] that controls the left end
condition for CUBIC spline interpolation. A value of 0 implies NATURAL end
condition while a value of 1 implies PARABOLIC end condition.

Default = 0.0 (0.0 < Real < 1.0)

NSEG Number of segments used to visualize the deformable curve in animation.

No default (Integer > 0)

G1, G2, G3, Ordered list of grid IDs defining the curve.

Comments

1. The deformable curve is generated using the CUBIC spline interpolation which requires
assumptions on the second derivative of the interpolating function at either end of the
curve. The keywords NATURAL, PARABOLIC, PERIODIC and CANTILEVER represent the
four standard assumptions defined as follows:

Note that λ =0.0 implies NATURAL (or free) end conditions and λ =1.0 implies PARABOLIC
end conditions.

2. This card is represented as a set in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1263

Proprietary Information of Altair Engineering


MBDEACT

Bulk Data Entry

MBDEACT – Deactivate an Entity/set in the Multi-body System

Description

Defines the entity/set that needs to be deactivated in the multi-body system for the
subsequent simulation.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBDEAC T ID ETYPE ID1 ID2 ID3 …

or

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBDEAC T ID ETYPE IDST THRU IDEND

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBDEAC T ID MOTION 92 94 199

Field Contents

ID Unique identification number.

(Integer > 0)

ETYPE Entity type that needs to be deactivated.

(Option – "CMBEAM", "CMBUSH", "CMSPDP2", "JOINT", "MLOAD", or


"MOTION")

1264 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

ID1, ID2, … Entity/Set ID that needs to be deactivated.

(Integer > 0)

IDST Entity/Set ID range start.

(Integer > 0)

THRU Keyword to indicate entity/set ID range is specified.

IDEND Entity/Set ID range end.

(Integer > IDST)

Comments

1. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1265

Proprietary Information of Altair Engineering


MBDSRF

Bulk Data Entry

MBDSRF – Multi-body Deformable Surface

Description

Defines a multi-body deformable surface.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBDSRF SRFID NROW NC OL ENDTYPE NSEGU NSEGV

G1 G2 G3 G4 G5 G6 …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBDSRF 1 3 6 NATURAL 100 100

201 202 203 204 205 206 207 206

209 210 211 212 213 214 215 216

217 218

Field Contents

SRFID Surface identification number.

No default (Integer > 0)

NROW Number of rows of nodes.

NCOL Number of columns of nodes.

ENDTYPE Select from: NATURAL, PARABOLIC and PERIODIC. See comment 1.

1266 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Default = NATURAL

NSEGU, NSEGV Number of segments along the U and V coordinates used to discretize the
deformable surface for animation purposes.

No default (Integer > 0)

G1, G2, … Row-wise list of nodes. The first NROW IDs form the first row; the second
NROW IDs form the second row, and so on. The list must contain a total of
NROW*NCOL grid IDs.

Comments

1. The deformable surface is generated using the CUBIC spline interpolation which requires
assumptions on the second derivative of the interpolating function at the end of the
surface. The keywords NATURAL, PARABOLIC and PERIODIC represent assumptions defined
as follows:

2. The MBDSRF element is not supported by the Force Imbalance method of static
equilibrium.

3. The MBDSRF element does not possess any inherent inertia, stiffness or damping.

4. This card is represented as a set in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1267

Proprietary Information of Altair Engineering


MBFRC

Bulk Data Entry

MBFRC – Force for Multi-body Solution Sequence

Description

Defines a constant force at a grid point by specifying a vector.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBFRC SID G1 C ID F G3/N1 N2 N3 G2

G4

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBFRC 3 345 100.0 0.0 1.0 0.0

201

Field Contents

SID Load set identification number.

No default (Integer > 0)

G1 Grid point identification number where the action force is applied.

No default (Integer > 0)

CID Coordinate system identification number. Blank or 0 infer the basic


coordinate system.

Default = 0 (Integer > 0 or blank)

1268 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

F Force magnitude.

No default (Real)

G3 Grid point identification number to optionally supply N1, N2, N3 in


conjunction with G1.

(Integer > 0)

N1, N2, N3 Defines the direction of the force vector. At least one of the vector
components must be non-zero.

Default = 0.0 (Real)

G2 Grid point identification number where the reaction force is applied. If


blank, then the force is an action-only force.

Default = blank (Integer > 0 or blank)

G4 Grid point identification number whose parent body hosts the coordinate
system with respect to which the force is defined. The force vector
changes direction with the orientation of the body. See comment 1.

Default = blank (Integer > 0 or blank)

Comments

1. If G4 is not specified, the force is defined with respect to the ground body (that is the
basic coordinate systems).

2. This card is represented as a force load in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1269

Proprietary Information of Altair Engineering


MBFRCC

Bulk Data Entry

MBFRCC – Curve Force for Multi-body Solution Sequence

Description

Defines a curve force at a grid point by specifying a vector.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBFRC C SID G1 C ID C VID G3/N1 N2 N3 G2

INT EID G4

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBFRC C 3 345 9 0.0 1.0 0.0

AKIMA 41 201

Field Contents

SID Load set identification number.

No default (Integer > 0)

G1 Grid point identification number where the action force is applied.

No default (Integer > 0)

CID Coordinate system identification number. Blank or 0 infer the basic


coordinate system.

Default = 0 (Integer > 0, or blank)

1270 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

CVID Set identification number of the MBCRV entry that gives the load vs.
independent variable measured in the coordinate system defined by
CID.

(Integer > 0)

G3 Grid point identification number to optionally supply N1, N2, N3 in


conjunction with G1.

(Integer > 0)

N1, N2, N3 Defines the direction of the force vector. At least one of the vector
components must be non-zero.

Default = 0.0 (Real)

G2 Grid point identification number where the reaction force is applied. If


blank or zero, then the force is an action-only force.

Default = 0 (Integer > 0)

INT Interpolation type (Character: LINEAR, CUBIC, AKIMA).

Default = AKIMA

EID Set identification number of the MBVAR for the independent variable
expression.

Default = TIME (Integer > 0 or blank)

G4 Grid point identification number whose parent body hosts the coordinate
system with respect to which the force is defined. The force vector
changes direction with the orientation of the body. See comment 1.

Default = blank (Integer > 0 or blank)

Comments

1. If G4 is undefined, the force is defined with respect to the ground body (that is the basic
coordinate systems).

2. This card is represented as a force load in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1271

Proprietary Information of Altair Engineering


MBFRCE

Bulk Data Entry

MBFRCE – Expression Force for Multi-body Solution Sequence

Description

Defines an expression force at a grid point by specifying a vector.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBFRC E SID G1 C ID EID G3/N1 N2 N3 G2

G4

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBFRC E 3 345 49 0.0 1.0 0.0

201

Field Contents

SID Load set identification number.

No default (Integer > 0)

G1 Grid point identification number where the action force is applied.

No default (Integer > 0)

CID Coordinate system identification number. Blank or 0 infer the basic


coordinate system.

Default = 0 (Integer > 0, or blank)

1272 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

EID Expression identification number of the MBVAR entry that gives the load
measured in the coordinate system defined by CID.

No default (Integer > 0)

G3 Grid point identification number to optionally supply N1, N2, N3 in


conjunction with G1.

(Integer > 0)

N1, N2, N3 Defines the direction of the force vector. At least one of the vector
components must be non-zero.

Default = 0.0 (Real)

G2 Grid point identification number where the reaction force is applied. If


blank or zero, then the force is an action-only force.

Default = 0 (Integer > 0)

G4 Grid point identification number whose parent body hosts the coordinate
system with respect to which the force is defined. The force vector
changes direction with the orientation of the body. See comment 1.

Default = blank (Integer > 0 or blank)

Comments

1. If G4 is undefined, the force is defined with respect to the ground body (that is the basic
coordinate systems).

Altair Engineering OptiStruct 13.0 Reference Guide 1273

Proprietary Information of Altair Engineering


MBLIN

Bulk Data Entry

MBLIN – Parameters for Multi-body System Linear Analysis

Description

Defines the parameters for a multi-body system linear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBLIN ID TYPE ASC ALE

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBLIN 99 EIGEN 1.0

Field Contents

ID Unique identification number.

(Integer > 0)

TYPE Type of linear analysis.

(Option – "EIGEN", "STMAT")

ASCALE Animation scale.

Default = 1.0 (Real > 0.0)

Comments

1. This card is represented as a loadcollector in HyperMesh.

1274 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MBMNT

Bulk Data Entry

MBMNT – Moment for Multi-body Solution Sequence

Description

Defines a constant moment at a grid point by specifying a vector.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBMNT SID G1 C ID M G3/N1 N2 N3 G2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBMNT 3 345 100.0 0.0 1.0 0.0

Field Contents

SID Load set identification number.

No default (Integer > 0)

G1 Grid point identification number where the action force is applied.

No default (Integer > 0)

CID Coordinate system identification number. Blank or 0 infer the basic


coordinate system.

Default = 0 (Integer > 0, or blank)

M Moment magnitude.

No default (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 1275

Proprietary Information of Altair Engineering


Field Contents

G3 Grid point identification number to optionally supply N1, N2, N3 in


conjunction with G1.

(Integer > 0)

N1,N2,N3 Defines the direction of the force vector. At least one of the vector
components must be non-zero.

Default = 0.0 (Real)

G2 Grid point identification number where the reaction force is applied. If


blank or zero, then the force is an action-only force.

Default = 0 (Integer > 0)

Comments

1. This card is represented as a moment load in HyperMesh.

1276 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MBMNTC

Bulk Data Entry

MBMNTC – Curve moment for Multi-body Solution Sequence

Description

Defines a curve moment at a grid point by specifying a vector.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBMNTC SID G1 C ID C VID G3/N1 N2 N3 G2

INT EID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBMNTC 3 345 4 0.0 1.0 0.0

AKIMA 42

Field Contents

SID Load set identification number.

No default (Integer > 0)

G1 Grid point identification number where the action force is applied.

No default (Integer > 0)

CID Coordinate system identification number. Blank or 0 infer the basic


coordinate system.

Default = 0 (Integer > 0, or blank)

Altair Engineering OptiStruct 13.0 Reference Guide 1277

Proprietary Information of Altair Engineering


Field Contents

CVID Set identification number of the MBCRV entry that gives the load vs.
independent variable measured in the coordinate system defined by
CID.

(Integer > 0)

G3 Grid point identification number to optionally supply N1, N2, N3 in


conjunction with G1.

(Integer > 0)

N1,N2,N3 Defines the direction of the force vector. At least one of the vector
components must be non-zero.

Default = 0.0 (Real)

G2 Grid point identification number where the reaction force is applied. If


blank or zero, then the force is an action-only force.

Default = 0 (Integer > 0)

INT Interpolation type (Character: LINEAR, CUBIC, AKIMA)

Default = AKIMA

EID Set identification number of the MBVAR for the independent variable
expression.

Default = TIME (Integer > 0 or blank)

Comments

1. This card is represented as a moment load in HyperMesh.

1278 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MBMNTE

Bulk Data Entry

MBMNTE – Expression Moment for Multi-body Solution Sequence

Description

Defines an expression moment at a grid point by specifying a vector.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBMNTE SID G1 C ID EID G3/N1 N2 N3 G2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBMNT 3 345 4 0.0 1.0 0.0

Field Contents

SID Load set identification number.

No default (Integer > 0)

G1 Grid point identification number where the action force is applied.

No default (Integer > 0)

CID Coordinate system identification number. Blank or 0 infer the basic


coordinate system.

Default = 0 (Integer > 0, or blank)

EID Expression identification number of the MBVAR entry that gives the load
measured in the coordinate system defined by CID.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1279

Proprietary Information of Altair Engineering


Field Contents

G3 Grid point identification number to optionally supply N1, N2, N3 in


conjunction with G1.

(Integer > 0)

N1, N2, N3 Defines the direction of the force vector. At least one of the vector
components must be non-zero.

Default = 0.0 (Real)

G2 Grid point identification number where the reaction force is applied. If


blank or zero, then the force is an action-only force.

Default = 0 (Integer > 0)

1280 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MBPCRV

Bulk Data Entry

MBPCRV – Multi-body Parametric Curve

Description

Defines a Multi-body Parametric Curve using node sets.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBPC RV PC ID UC LOSE C RVPTS


D

G1 G2 G3 G4 G5

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBPC RV 1 1 0 1 5

201 202 203 204 205

Field Contents

PCID Parametric curve identification number.

No default (Integer > 0)

UCLOSED Specify 1 for closed and 0 for open curves.

CRVPTS Curve points. Specify 1 if the curve must pass through the nodes, and 0 if
the B-spline curve does not pass through the nodes, but stays close.

Default = 0 (BOOLEAN: 0,1)

G1,G2,… Ordered list of grids defining the curve.

Comments

Altair Engineering OptiStruct 13.0 Reference Guide 1281

Proprietary Information of Altair Engineering


1. This card is represented as a set in HyperMesh.

1282 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MBPTCV

Bulk Data Entry

MBPTCV – Multi-body Point to Curve Constraint

Description

Defines a Point to Parametric Curve Constraint.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBPTC V JID GID PC ID G3 V0

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBPTC V 1 21 2 25 0

Field Contents

JID Joint identification number.

No default (Integer > 0)

GID Grid identification number corresponding to the point which is sliding on


a curve.

No default (Integer > 0)

PCID Parametric curve (MBPCRV) identification number.

No default (Integer > 0)

G3 This grid specifies the guess for the initial contact point on the curve.

Default is GID (Integer > 0)

V0 Specifies the initial sliding velocity of the contact point, as measured by


an observer on the curve, placed at the contact point.

Default = 0.0 (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 1283

Proprietary Information of Altair Engineering


MBPTDCV

Bulk Data Entry

MBPTDCV – Multi-body Point to Deformable Curve Constraint

Description

Defines a Point to Deformable Curve Constraint.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBPTDC V JID GID DC ID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBPTDC V 1 21 2

Field Contents

JID Joint identification number.

No default (Integer > 0)

GID Grid identification number corresponding to the point which is sliding on


the deformable curve.

No default (Integer > 0)

DCID Deformable curve (MBDCRV) identification number.

No default (Integer > 0)

Comments

1. The deformable curve is generated using the CUBIC spline interpolation which requires
assumptions on the second derivative of the interpolating function at either end of the
curve. The keywords NATURAL, PARABOLIC, PERIODIC and CANTILEVER represent the
four standard assumptions defined as follows:

1284 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Note that λ =0.0 implies NATURAL (or free) end conditions and λ =1.0 implies PARABOLIC
end conditions.

2. The MBPTDCV element is not supported by the Force Imbalance method of static
equilibrium.

3. In most cases, the interpolation produces a smooth curve but in some cases, it produces
a curve that wiggles too much. In those cases, the TENSION parameter may be specified
to smooth out the wiggles in the curve. A TENSION value of unity is a good first guess.
After that, higher values of TENSION may be tried if necessary.

4. The deformable element itself does not possess any inherent inertia, stiffness or damping
properties. You must include other modeling elements to capture those effects.

Altair Engineering OptiStruct 13.0 Reference Guide 1285

Proprietary Information of Altair Engineering


MBPTDSF

Bulk Data Entry

MBPTDSF – Multi-body Dynamics Point to Deformable Surface Constraint

Description

Defines a Point to Deformable Surface Constraint.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBPTDSF JID GID SRFID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBPTDSF 1 21 2

Field Contents

JID Joint identification number.

No default (Integer > 0)

GID Grid identification number corresponding to the point which is sliding on


a curve.

No default (Integer > 0)

SRFID Deformable surface identification number

No default (Integer > 0)

Comments

1. The deformable curve is generated using the CUBIC spline interpolation which requires
assumptions on the second derivative of the interpolating function at either end of the
curve. The keywords NATURAL, PARABOLIC, PERIODIC and CANTILEVER represent the four
standard assumptions defined as follows:

1286 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Note that λ =0.0 implies NATURAL (or free) end conditions and λ =1.0 implies PARABOLIC
end conditions.

2. The MBPTDCV element is not supported by the Force Imbalance method of static
equilibrium.

3. In most cases, the interpolation produces a smooth curve but in some cases, it produces
a curve that wiggles too much. In those cases, the UTENSION and VTENSION parameters
may be specified to smooth out the wiggles in the curve. A value of unity is a good first
guess. After that, higher values may be tried if necessary.

4. The deformable surface itself does not possess any inherent inertia, stiffness or damping
properties. You must include other modeling elements to capture those effects. For
example, you may use a deformable surface in conjunction with a flexible body to simulate
contact with a rigid body.

Altair Engineering OptiStruct 13.0 Reference Guide 1287

Proprietary Information of Altair Engineering


MBREQ

Bulk Data Entry

MBREQ – Multi-body Request Combination

Description

Defines a multi-body as a combination of request sets defined via MBREQE and MBREQM.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBREQ SID R1 R2 R3 R4 R5 R6 R7

R8 R9 …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBREQ 3 31 34 35

Field Contents

SID Request set identification number.

(Integer > 0)

Ri Request set identification numbers defined via entry typed


enumerated above.

(Integer > 0)

Comments

1. The Ri must be unique.

2. Request sets must be selected in the Subcase Information section (REQUEST = SID) if
they are to be applied.

1288 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MBREQE

Bulk Data Entry

MBREQE – Multi-body Expression Output Request

Description

Defines a multi-body solver output request to output the results of a set of expressions.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBREQE RSID RID E1 E2 E3 E4 E5 E6

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBREQE 235 10 20 30 40

Field Contents

RSID Request set identification number.

(Integer > 0)

RID Request identification number.

(Integer > 0)

E1 ID of MBVAR.

(Integer > 0)

E2 … E6 Additional MBVAR IDs.

Default = blank (blank or Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1289

Proprietary Information of Altair Engineering


Comments

1. The request evaluates the expression at every output step.

2. The values are always set to 0 if the expression is not specified.

3. Request set will be specified in the subcase definition.

4. Request ID must be unique with respect to all other MBREQM and MBREQE cards.

1290 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MBREQM

Bulk Data Entry

MBREQM – Multi-body Output Request based on Markers

Description

Defines a multi-body solver output request to output displacement, velocity, acceleration, or


force with respect to markers.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBREQM RSID RID TYPE IMARK JMARK RMARK

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBREQM 20 234 DISP 20 30 10

Field Contents

RSID Request set identification number.

(Integer > 0)

RID Request identification number.

(Integer > 0)

TYPE Output type

DIS - Displacement request


VEL - Velocity request
ACC - Acceleration request
FRC - Force request

No default

Altair Engineering OptiStruct 13.0 Reference Guide 1291

Proprietary Information of Altair Engineering


Field Contents

IMARK Marker ID.

(Integer > 0) – See comment 1

JMARK Marker ID.

Default = blank; (blank or Integer > 0) – See comments 1 and 2

RMARK Reference marker ID.

Default = blank; (blank or Integer > 0) – See comment 3

Comments

1. The output request is usually of IMARK with respect to JMARK resolved in RMARK.

2. If the JMARK is not specified, the results are with respect to global frame.

3. If the RMARK is not specified, the results are resolved in the global frame.

4. Request set will be specified in the subcase definition.

5. Request ID must be unique with respect to all other MBREQM and MBREQE cards.

1292 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MBSEQ

Bulk Data Entry

MBSEQ – Multi-body System Simulation Sequence

Description

Defines the simulation sequence for the multi-body solver.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSEQ ID SID1 SID2 SID3 … …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSEQ 9 99 12 43

Field Contents

ID Unique identification number.

(Integer > 0)

SID1, SID2, … IDs of the simulation sequence.

(Integer > 0) (Valid IDs are: MBSIM, MBLIN, MBSIMP, MBACT, or


MBDEACT)

Comments

1. Every time an MBSIM card is encountered, a simulation is performed on the multi-body


model. The initial condition for the next MBSIM will be the ending condition of the current
simulation.

2. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1293

Proprietary Information of Altair Engineering


MBSFRC

Bulk Data Entry

MBSFRC – Scalar Load for Multi-body Solution Sequence

Description

Defines a constant scalar load on two grid points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSFRC SID G1 G2 F

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSFRC 3 345 346 1.0

Field Contents

SID Load set identification number.

No default (Integer > 0)

G1 Grid point identification number.

No default (Integer > 0)

G2 Grid point identification number.

No default (Integer > 0)

F Value of load

(Real)

1294 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. MBSFRC applies a translational action-reaction force along the line of action defined by
the line segment connecting G1 and G2.

2. The action force is applied to G1 and the reaction force is applied to G2.

3. Tensile force is positive.

Altair Engineering OptiStruct 13.0 Reference Guide 1295

Proprietary Information of Altair Engineering


MBSFRCC

Bulk Data Entry

MBSFRCC – Curve Scalar Load for Multi-body Solution Sequence

Description

Defines a curve scalar load on two grid points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSFRC C SID G1 G2 C VID INT EID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSFRC C 3 345 346 1 AKIMA 1

Field Contents

SID Load set identification number.

No default (Integer > 0)

G1 Grid point identification number.

No default (Integer > 0)

G2 Grid point identification number.

No default (Integer > 0)

CVID Set identification number of the MBCRV entry that gives the load vs.
independent variable measured in the coordinate system defined by
CID.

(Integer > 0)

1296 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

INT Interpolation type (Character: LINEAR, CUBIC, AKIMA).

Default = AKIMA

EID Set identification number of the MBVAR for the independent variable
expression.

Default = TIME (Integer > 0 or blank)

Comments

1. MBSFRCC applies a translational action-reaction force along the line of action defined by
the line segment connecting G1 and G2.

2. The action force is applied to G1 and the reaction force is applied to G2.

3. Tensile force is positive.

Altair Engineering OptiStruct 13.0 Reference Guide 1297

Proprietary Information of Altair Engineering


MBSFRCE

Bulk Data Entry

MBSFRCE – Expression Scalar Load for Multi-body Solution Sequence

Description

Defines an expression scalar load on two grid points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSFRC E SID G1 G2 EID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSFRC E 3 345 346 1

Field Contents

SID Load set identification number.

No default (Integer > 0)

G1 Grid point identification number.

No default (Integer > 0)

G2 Grid point identification number.

No default (Integer > 0

EID Expression identification number of the MBVAR entry.

No default (Integer > 0)

1298 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. MBSFRCE applies a translational action-reaction force along the line of action defined by
the line segment connecting G1 and G2.

2. The action force is applied to G1 and the reaction force is applied to G2.

3. Tensile force is positive.

Altair Engineering OptiStruct 13.0 Reference Guide 1299

Proprietary Information of Altair Engineering


MBSIM

Bulk Data Entry

MBSIM – Parameters for Multi-body Simulation

Description

Defines the parameters for a multi-body simulation.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSIM ID TYPE TTYPE TIME STYPE DELTA/


NSTEP/
PRINC R

ITYPE DTOL H0 HMAX HMIN VTOLFAC MAXODR

DAEIDX DC NTOL DC RMXI DC RMNI DVC TRL DJAC EVL DEVLEXP


T T

or

KETOL/ DQTOL/ NITER TLIMIT ALIMIT STTYPE


RESTOL FITOL

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSIM 99 TRAN END 5.0 NSTEPS 250

VSTIFF 0.001 0.001 0.01 1000.0 5

Example 2

1300 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSIM 99 TRAN END 5.0 NSTEPS 250

DSTIFF 0.001 0.001 1000.0 9

3 4 TRUE

Example 3

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSIM 91 STAT

1.0e-6 0.0001 100

Field Contents

ID Unique identification number.

(Integer > 0)

TYPE Simulation type.

Options = ("TRANS", "STATIC")

No default

TTYPE Termination type.

Options = ("END", "DUR") – See comment 2.

No default

TIME Termination time or duration based on TTYPE.

(Real > 0.0) – See comment 2.

STYPE Output step type.

Altair Engineering OptiStruct 13.0 Reference Guide 1301

Proprietary Information of Altair Engineering


Field Contents

Options = ("DELTA", "NSTEPS", "PRINCR") – See comments 2 and 3.

No default

DELTA Output time step.

(Real > 0.0) – See comments 2 and 3.

NSTEPS Maximum number of time steps.

(Integer > 0) – See comments 2 and 3.

ITYPE Integrator type.

Options = ("ABAM", "VSTIFF", "MSTIFF", "DSTIFF") – See comment 4.

Default = DSTIFF

DTOL Integrator tolerance.

Default = 0.001 (Real > 0.0) – See comment 4.

H0 Initial time step for the integrator.

Default = 1e-8 (Real > 0.0) – See comment 4.

HMAX Max step size the integrator is allowed to take.

Default = 0.01 (Real > 0.0) – See comment 4.

HMIN Min step size the integrator is allowed to take.

Default = 1.0e-6 (Real > 0.0) – See comment 4.

VTOLFAC A factor that multiplies DTOL to yield the error tolerance for velocity
states.

Default = 1000 (Real > 0.0) – See comment 4.

MAXODR The maximum order that the integrator is to take.

Default depends on ITYPE (Integer > 0) – See comment 4.

1302 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

DAEIDX The index of the DAE formulation.

Default = 3 (Integer > 0) – See comment 4.

DCNTOL A tolerance on all algebraic constraint equations that the corrector


must satisfy at convergence.

Default = 0.001 (Real > 0.0) – See comment 4.

DCRMXIT The maximum number of iterations that the corrector is allowed to


take to achieve convergence.

Default = 4 (Integer > 0) – See comment 4.

DCRMNIT The minimum number of iterations that the corrector is allowed to take
before it checks for corrector divergence.

Default = 1 (Integer > 0) – See comment 4.

DVCTRL A logical flag that controls whether the velocity states are checked
for local integration error at each step.

(True or False, Default = True if DAEIDX is 3, otherwise False) – See


comment 4.

DJCEVL An attribute to control the frequency of evaluation of the Jacobian


matrix during corrector iterations.

Default is determined by MotionSolve (Integer > 0) – See comment 4.

DEVLXP The number of integration steps after which the evaluation pattern
defined by DJCEVL is ignored, and the default evaluation pattern is to
be used.

Default = 0 (Integer > 0) – See comment 4.

KETOL Maximum residual kinetic energy tolerance.

Default = 1.0e-5 (Real > 0.0) – See comment 5.

RESTOL Maximum residual tolerance for force imbalance method.

Default = 1.0e-4 (Real > 0.0) – See comment 6.

Altair Engineering OptiStruct 13.0 Reference Guide 1303

Proprietary Information of Altair Engineering


Field Contents

DQTOL Maximum coordinate difference tolerance.

Default = 0.001 (Real > 0.0) – See comment 5.

FITOL Maximum force imbalance tolerance.

Default = 0.001 (Real > 0.0) – See comment 6.

NITER Max number of iterations for static solution to converge.

Default = 50 (Integer > 1) – See comment 5.

TLIMIT Max translational limit for force imbalance static solution.

Default = 10000 (Real > 1) – See comment 6.

ALIMIT Max angular limit for force imbalance static solution.

Default = 30 (Real > 1) – See comment 6.

STTYPE Static solver type

Options = ("FIM", "MKM") – See comments 7 and 8.

Default = MKM

Comments

1. The continuation card is used to distinguish between either a TRANS or STAT simulation
type. The reader will look for appropriate options based on the type of simulation
specified.

2. When the simulation type is static (STAT), the solver will perform a static simulation if the
termination type, termination time/duration, step type, delta/nsteps are not provided. A
quasi-static simulation will be performed if that information is provided.

3. If the output step type is DELTA, then the next argument is expected to be a positive
real value, and it is the output step time during the simulation run. If the step type is
NSTEPS, then the next argument is expected to be a positive integer value which will be
the number of output steps during the simulation. If the step type is PRINCR, then the
next argument is expected to be a positive integer value which will be print increment.
Solver will output at every intermediate print increment value. If the PRINCR is set to 1,
then the solver will output intermediate results at every integrator step.

4. ITYPE, DTOL, H0, HMAX, HMIN, VTOLFAC, MAXODR, DAEIDX, DCNTOL, DCRMXIT,
DCRMNIT, DVCTRL, DJACEVL, and DEVLEXP are only applicable for TRANS simulation types.
The 2nd continuation card (DAEIDX, DCNTOL, DCRMXIT, DCRMNIT, DVCTRL, DJACEVL,

1304 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


and DEVLEXP) are available when ITYPE = DSTIFF. See the comments in the
Param_Transient in the online help for more details.

5. KETOL, DQTOL, NITER are only applicable for STATIC simulation type.

6. RESTOL, FITOL, NITER, TLIMIT, ALIMIT are applicable for the force imbalance static
method used for quasi-static solutions.

7. Static solver type is used to select from the two static solution types currently offered.
FIM represents the Force Imbalance Method and MKM represents the Maximum Kinetic
Energy Attrition Method.

8. Note that when quasi-static simulation is requested (STAT with termination time), then
the STTYPE option is ignored and the quasi-static simulation will be performed using the
force imbalance method.

9. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1305

Proprietary Information of Altair Engineering


MBSIMP

Bulk Data Entry

MBSIMP – Simulation Parameters for Subsequent Multi-body Simulation

Description

Defines the simulation parameters for subsequent multi-body simulation.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSIMP ID C TOL IDTOL

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSIMP 99 0.001 1.0E-8

Field Contents

ID Unique identification number.

(Integer > 0)

CTOL Constraint tolerance.

Default = 1.0E-10 (Real > 0.0)

IDTOL Implicit differentiation tolerance.

Default = 1.0E-6 (Real > 0.0)

Comments

1. This card is represented as a loadcollector in HyperMesh.

1306 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MBSMNT

Bulk Data Entry

MBSMNT – Scalar Moment for Multi-body Solution Sequence

Description

Defines a constant scalar moment on two gird points along the specified vector.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSMNT SID G1 G2 T G3/Vx Vy Vz

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSMNT 3 345 346 1.0 0 1.0 1.0

Field Contents

SID Load set identification number.

No default (Integer > 0)

G1 Grid point identification number.

No default (Integer > 0)

G2 Grid point identification number.

No default (Integer > 0)

T Value of moment.

(Real)

Altair Engineering OptiStruct 13.0 Reference Guide 1307

Proprietary Information of Altair Engineering


Field Contents

G3 Grid point identification number to optionally supply Vx, Vy, and Vz in


conjunction with G1.

(Integer > 0)

Vx X component of vector V.

Vy Y component of vector V.

Vz Z component of vector V.

Comments

1. MBSMNT applies a scalar action-reaction moment on G1 and G2 along the vector defined
by Vx, Vy, and Vz.

2. The action moment is applied to G1 and the reaction moment is applied to G2.

3. Right hand rule defines the positive moment.

1308 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MBSMNTC

Bulk Data Entry

MBSMNTC – Curve Scalar Moment for Multi-body Solution Sequence

Description

Defines a curve scalar moment on two grid points along the specified vector.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSMNTC SID G1 G2 C VID G3/Vx Vy Vz

INT EID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSMNTC 3 345 346 2 0 1.0 1.0

AKIMA 1

Field Contents

SID Load set identification number.

No default (Integer > 0)

G1 Grid point identification number.

No default (Integer > 0)

G2 Grid point identification number.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1309

Proprietary Information of Altair Engineering


Field Contents

CVID Set identification number of the MBCRV entry that gives the load vs.
independent variable measured in the coordinate system defined by CID.

(Integer > 0)

G3 Grid point identification number to optionally supply Vx, Vy, and Vz in


conjunction with G1.

(Integer > 0)

Vx X component of vector V.

Vy Y component of vector V.

Vz Z component of vector V.

INT Interpolation type (Character: LINEAR, CUBIC, AKIMA)

Default = AKIMA

EID Set identification number of the MBVAR for the independent variable
expression.

Default = TIME (Integer > 0 or blank)

Comments

1. MBSCMTC applies a scalar action-reaction moment on G1 and G2 along the vector defined
by Vx, Vy, and Vz.

2. The action moment is applied to G1 and the reaction moment is applied to G2.

3. Right hand rule defines the positive moment.

1310 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MBSMNTE

Bulk Data Entry

MBSMNTE– Expression Moment for a Multi-body Solution Sequence

Description

Defines an expression scalar moment on two grid points along the specified vector

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSMNTE SID G1 G2 EID Vx Vy Vz

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBSMNTE 3 345 346 2 0 1.0 1.0

Field Contents

SID Load set identification number.

No default (Integer > 0)

G1 Grid point identification number.

No default (Integer > 0)

G2 Grid point identification number.

No default (Integer > 0)

EID Expression identification number of the MBVAR entry.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1311

Proprietary Information of Altair Engineering


Field Contents

G3 Grid point identification number to optionally supply Vx, Vy, and Vz in


conjunction with G1.

(Integer > 0)

Vx X component of Vector V.

Vy Y component of Vector V.

Vz Z component of Vector V.

Comments

1. MBSMNTE applies a scalar action-reaction moment on G1 and G2 along the vector defined
by Vx, Vy, and Vz.

2. The action moment is applied to G1 and the reaction moment is applied to G2.

3. Right hand rule defines the positive moment.

1312 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MBVAR

Bulk Data Entry

MBVAR– Multi-body Solver Variable

Description

Defines a multi-body solver variable which can be referred to by multiple Expressions.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBVAR VID EXPR

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MBVAR 3 IMPAC T(Dz(30301020,30302040),VZ(30301020,30302040),0.0,4

00,1.0,0.5,0.000)

Field Contents

VID Variable identification number.

(Integer > 0)

EXPR Character string expression. The expression can spawn multiple lines. The
continuation lines will start from the second column. Refer to Function
Expressions.

Comments

1. The variable ID can be referenced by VARVAL(VID) in multiple expressions in the model.

Altair Engineering OptiStruct 13.0 Reference Guide 1313

Proprietary Information of Altair Engineering


METADATA

Bulk Data Entry

METADATA – Indicates the beginning of metadata that is to be passed to the metadata


output file.

Description

METADATA indicates the beginning of metadata that is to be passed to the metadata output
file. Metadata between the METADATA and ENDMETADATA commands is passed to the
<filename>_metadata.xml file.

Example

METADATA
This line will be passed to the filename_metadata.xml file.
So will this information: Color=blue
ENDMETADATA

Comments

1. There can be two sections of metadata; one in the Solution Control section and one in
the Bulk Data section.

2. Metadata can be used to pass information from the pre-processor seamlessly through the
solver to a post-processing program.

1314 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MFLUID

Bulk Data Entry

MFLUID – Fluid Volume

Description

Defines the parameters and damp shell elements for a fluid volume.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MFLUID SID C ID ZFS RHO WSURF1 WSURF2 PLANE1 PLANE2

RMAX

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MFLUID 25 32.0 42.0 45

Field Contents

SID Unique set of identification numbers.

No default (Integer > 0)

CID Coordinate system identification number in which its z-axis is assumed to


be normal to the free surface.

Default = 0 (Integer > 0, or blank)

ZFS Location of the free surface on the z-axis of the CID coordinate system.

Default = 1030 (Real)

RHO Fluid density.

Altair Engineering OptiStruct 13.0 Reference Guide 1315

Proprietary Information of Altair Engineering


Field Contents

No default (Real > 0.0)

WSURF1 Set identification number of a SURF or SET bulk data entry. This list
identifies shell elements that are damp on only one side of the element or
an exterior face of solid elements (see SURF,ELFACE).

Default = 0 (Integer > 0, or blank)

WSURF2 Set identification number of a SURF or SET bulk data entry. This list
identifies shell elements that are damp on both sides of the element.

Default = 0 (Integer > 0, or blank)

PLANE1 Type of symmetry on x-z plane of fluid coordinate system (CID).

N - no symmetry
S - symmetric
A - antisymmetric

Default = N (Character = N, S, A)

PLANE2 Type of symmetry on y-z plane of fluid coordinate system (CID).

N - no symmetry
S - symmetric
A - antisymmetric

Default = N (Character = N, S, A)

RMAX Interaction between two elements is ignored, if the distance between


them is greater than RMAX.

Default = 1010 (Real > 0.0)

Comments

1. An MFLUID entry must be selected by the MFLUID = SID command in the Subcase
Information section.

2. More than one MFLUID entry may be specified to define multiple fluid volumes.

3. Either WSURF1 or WSURF2, or both must be specified and non-zero. In other words,
WSURF1 and WSURF2 cannot be both blank or zero.

4. An element with all its vertices located on or above the free surface will be ignored in the
fluid volume’s mass calculation. An element vertex is considered to be located on the free

surface, if the vertex is located within a distance that is

1316 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


from the free surface.

5. By default for elements referenced by WSURF1, the damp side of the element is assumed
to be on the same side as the element’s normal. If this condition is not true for a given
element, then the standard SURF entry format with “ELFACE” (not the alternative SET
format) must be used to redefine the normal into the fluid by setting NORMAL=1 on SURF
entry.

6. ELIST is an alternative to SET and SURF, but ELIST is intended only to provide
compatibility with Nastran decks and therefore is considered deprecated. Also,

The SURF and SET entries may not be combined with ELIST entries to define damp
elements.
ELIST entries are internally converted to SET entries. If ELIST is used, then all MFLUID
entries must reference ELIST entries. This means that if an MFLUID references a
missing ELIST,25, then the program will not search for a SET,25.
7. Planes of symmetry may be defined with PLANE1 and PLANE2.

"S” means zero displacement normal to the plane.


“A” means zero pressure normal to the plane.
Consistent structural boundary conditions should be applied to grids located on the
planes of symmetry.
If PLANE1 is “S” or “A”, then all damp elements must not cross the X-Z plane and be
on the same side of the X-Z plane as all other damp elements.
If PLANE2 is “S” or “A”, then all damp elements must not cross the Y-Z plane and be
on the same side of the Y-Z plane as all other damp elements.
8. Dry mode output in the .out file is available only when PARAM,VMOPT,2 is specified.

Altair Engineering OptiStruct 13.0 Reference Guide 1317

Proprietary Information of Altair Engineering


MGASK

Bulk Data Entry

MGASK – Gasket Material Property Definition

Description

Defining the material properties for gasket-like materials.

Format 1 (no temperature dependency)

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MGASK MID BEHAV YPRS EPL GPL ALPHA EPLTYPE GPLUNIT

TABLD TABLU1 TABLU2 TABLU3 TABLU4 TABLU5 TABLU6 TABLU7

TABLU8

Format 2 (temperature dependency defined)

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MGASK MID BEHAV YPRS EPL GPL ALPHA EPLTYPE GPLUNIT

TABLD TABLU1 TABLU2 TABLU3 TABLU4 TABLU5 TABLU6 TABLU7

TABLU8 TABLU9 -etc.-

"T" TEMP1

"PLUS" YPRS EPL GPL ALPHA

TABLD TABLU1 TABLU2 TABLU3 TABLU4 TABLU5 TABLU6 TABLU7

TABLU8 TABLU9 -etc.-

"T" TEMP2

-etc.-

1318 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MGASK 2 1 1.0e-3 200.0 1.0e-5

1001 1002 1003 1004

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MGASK 2 1 1.0e-3 200.0 1.0e-5

1001 1002 1003 1004

T 20.0

PLUS

2001 2002 2003 2004 2005

T 100.0

PLUS

3001 3002 3003

T 300.0

Field Contents

MID Material identification number.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1319

Proprietary Information of Altair Engineering


Field Contents

BEHAV Behavior type. See comment 12.

Default = 0 (Integer (0 or 1 only))

0 – elasto-plastic material
1 – elastic material with damage

YPRS Initial yield pressure for the thickness direction of the gasket material.
Applies only to elasto-plastic behavior (BEHAV=0).

If blank, it is determined automatically.

For the groups of data starting with “PLUS”, default is the corresponding
field value defined at the first line.

EPL Tension stabilization coefficient or direct tensile modulus (depends on the


value of the EPLTYPE field) for the thickness direction of the gasket
material. See comment 5.

Default = 0.0 (Real > 0.0)

For the groups of data starting with “PLUS”, default is the corresponding
field value defined at the first line.

GPL Transverse shear modulus of the gasket material (the unit of measure
depends on the value of the GPLUNIT field).

Default = 0.0 (Real > 0.0)

For the groups of data starting with “PLUS”, default is the corresponding
field value defined at the first line.

ALPHA Coefficient of thermal expansion in the normal direction.

Default = 0.0 (Real > 0.0)

For the groups of data starting with “PLUS”, default is the corresponding
field value defined at the first line.

EPLTYPE Type of definition of EPL. See comment 12.

Default = 0 (Integer (0 or 1 only))

0 – EPL is defined as a tension stabilization coefficient


1 – EPL is defined as a direct tensile modulus

GPLUNIT Type of the unit of measure of GPL. See comment 12.

Default = 0 (Integer (0 or 1 only))

1320 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

0 – stress per unit displacement


1 – force per unit area

TABLD Identifier of a TABLES1 table providing loading path of the gasket material
(pressure vs. closure).

No default (Integer > 0)

TABLUi Identifier of TABLES1 table providing unloading/reloading path of the


gasket material (pressure vs. closure). If there is no unloading, leave the
fields blank.

Default = blank (Integer > 0 or blank)

T Temperature flag indicating that a temperature value will be defined in the


next field.

TEMPj Temperature for the group of data above. See comment 11.

No default (Real)

PLUS Keyword indicating that the following is a group of data defined at another
temperature. See comment 12.

Comments

1. The material identification number must be unique for all MAT1, MAT2, MAT3, MAT8,
MAT9 and MGASK entries.

2. MGASK mainly defines nonlinear properties in the thickness direction for gasket-like
materials under compression. MGASK has anisotropy only in the thickness direction, which
is called normal anisotropy. For linear analysis, the thickness-direction modulus (stress
per unit displacement) is defined by the slope of the first segment of the loading
pressure-closure curve TABLD.

3. MGASK also defines the transverse shear and thickness-direction tension behaviors with
linear properties. (The membrane properties of the gasket are defined by a MAT1,
referenced from the PGASK property.)

4. The thickness direction of gasket material is the principal direction (local 3-direction) in
3D solids.

5. If EPL is defined as a tension stabilization coefficient (EPLTYPE = 0), the tensile modulus
will be calculated as the initial slope of the first segment of the loading curve TABLD
multiplied by EPL. If EPL is defined as a direct tensile modulus (EPLTYPE = 1), its unit of
measure is stress per unit displacement. If EPL is zero, a small tensile modulus will be used
automatically for stabilization (no matter EPLTYPE is 0 or 1).

6. All the data points in tables TABLD and TABLUi are specified in the first quadrant. Points

Altair Engineering OptiStruct 13.0 Reference Guide 1321

Proprietary Information of Altair Engineering


on loading (TABLD) and unloading/reloading (TABLUi) paths must be defined in order of
increasing pressure and distance.

7. For elasto-plastic material (BEHAV = 0),

The initial yield pressure should match a point in table TABLD. If the initial yield
pressure is not specified, it will be determined automatically by finding the first point on
the TABLD curve where the slope changes by more than 10%.
The loading path starts from the origin to initial yield pressure (nonlinear elastic range)
and continues with strain hardening slope into the plastic region.

All unloading/reloading paths must start with zero pressure and positive closure
distance, and end at the loading path in the plastic region. Subsequent unloading/
reloading curves must start with larger closure distances (when pressure is zero) and
end with larger closure distances than previous unloading/reloading curves.
8. For elastic material with damage (BEHAV = 1),

All loading and unloading/reloading curves must start at the origin of the coordinate
system (0, 0).
All unloading/reloading paths must end at the loading path. Subsequent unloading/
reloading curves must end with larger closure distances than previous unloading/
reloading curves.
9. Unloading/reloading behavior at undefined paths will be interpolated between two
adjacent unloading/reloading paths.

10. For closures larger than the last user-specified closure, the pressure-closure relationship
is calculated as follows:

For elasto-plastic material (BEHAV = 0), it follows the last segment of the furthest
unloading/reloading curve. This behavior is fully elastic and represents crushed gasket.
For elastic material with damage (BEHAV = 1), it follows last slope computed from the
user-specified data.

1322 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Elasto-plastic gasket material

Elastic gasket material with damage

11. If temperature dependency is defined, TEMPj should be provided in ascending order and
the loading path (and unloading/reloading paths, if required) should be provided for each

Altair Engineering OptiStruct 13.0 Reference Guide 1323

Proprietary Information of Altair Engineering


temperature. If temperature dependency is defined but the temperature field for material
property is not provided, the first group of data will be used to calculate the material
property. TEMPj are defined for all MGASK data fields (data groups) that lie between the
respective TEMPj and its previous PLUS field. TEMP1 is an exception to this rule as it is
defined for all data fields that lie between itself and MID.

Example

12. BEHAV, EPLTYPE and GPLUNIT fields after any “PLUS” field should remain blank because
their values are always the same as those of the first-group data.

1324 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MLOAD

Bulk Data Entry

MLOAD – Multi-body Load Combination

Description

Defines a multi-body as a linear combination of load sets defined via GRAV, MBFRC, MBFRCC,
MBFRCE, MBMNT, MBMNTC, MBMNTE, MBSFRC, MBSFRCC, MBSFRCE, MBSMNT, MBSMNTC, and
MBSMNTE.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MLOAD SID L1 L2 L3 L4 L5 L6 L7

L8 L9 …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MLOAD 3 31 34 35

Field Contents

SID Load set identification number.

(Integer > 0)

Li Load set identification numbers defined via entry typed enumerated above.

(Integer > 0)

Comments

1. The Li must be unique.

2. Load sets must be selected in the Subcase Information section (MLOAD = SID) if they are
to be applied.

Altair Engineering OptiStruct 13.0 Reference Guide 1325

Proprietary Information of Altair Engineering


3. An MLOAD entry may not reference a set identification number defined by another MLOAD
entry.

4. This card is represented as a loadcollector in HyperMesh.

1326 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MOMENT

Bulk Data Entry

MOMENT – Static Moment

Description

Defines a static moment at a grid point by specifying a vector. It can also be used to define
the EXCITEID field (Amplitude “A”) of dynamic loads in RLOAD1, RLOAD2, TLOAD1 and TLOAD2
bulk data entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOMENT SID G C ID M N1 N2 N3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOMENT 2 5 6 2.9 0.0 1.0 0.0

Field Contents

SID Load set identification number.

(Integer > 0)

G Grid point identification number.

(Integer > 0 or <PartName.number>) See comment 3.

CID Coordinate system identification number.

(Integer > 0 or blank)

M Scale factor.

Altair Engineering OptiStruct 13.0 Reference Guide 1327

Proprietary Information of Altair Engineering


Field Contents

(Real)

N1,N2,N3 Components of vector measured in coordinate system defined by CID.

(Real; at least one non-zero component)

Comments

1. The static moment applied to grid point G is given by

where, is the vector defined in fields 6, 7, and 8.

2. A CID of zero or blank references the basic coordinate system.

3. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on MOMENT entries in the model. A fully qualified reference
(“PartName.number”) is similar to the format of a numeric reference. “PartName” is the
name of the part that contains the referenced local entry (part names are defined on the
BEGIN Bulk Data Entry in the model). “number” is the identification number of a
referenced local entry in the part “PartName”. See Parts and Instances in the User’s
Guide for detailed information on the use of fully qualified references.

4. This card is represented as a moment load in HyperMesh.

1328 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MOMENT1

Bulk Data Entry

MOMENT1 – Static Moment, Alternate Form 1

Description

Defines a static moment by specification of a value and two grid points, which determine the
direction. It can also be used to define the EXCITEID field (Amplitude “A”) of dynamic loads in
RLOAD1, RLOAD2, TLOAD1 and TLOAD2 bulk data entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOMENT1 SID G M G1 G2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOMENT1 6 13 -2.93 16 13

Field Contents

SID Load set identification number.

(Integer > 0)

G Grid point identification number.

(Integer > 0)

M Value of moment.

(Real)

G1,G2 Grid point identification numbers.

Altair Engineering OptiStruct 13.0 Reference Guide 1329

Proprietary Information of Altair Engineering


Comments

1. The static moment applied to grid point G is

where, is a unit vector parallel to a vector from G1 to G2.

2. This card is represented as a moment load in HyperMesh.

1330 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MOMENT2

Bulk Data Entry

MOMENT2 – Static Moment, Alternate Form 2

Description

Defines a static moment by specification of a value and four grid points, which determine the
direction. It can also be used to define the EXCITEID field (Amplitude “A”) of dynamic loads in
RLOAD1, RLOAD2, TLOAD1 and TLOAD2 bulk data entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOMENT2 SID G M G1 G2 G3 G4

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOMENT2 6 13 -2.93 16 13 18 19

Field Contents

SID Load set identification number.

(Integer > 0)

G Loaded grid point identification number.

(Integer > 0)

M Value of moment.

(Real)

G1,G2 Grid point identification numbers.

(Integer > 0; G1 and G2 cannot coincident; G3 and G4 cannot be


coincident)

Altair Engineering OptiStruct 13.0 Reference Guide 1331

Proprietary Information of Altair Engineering


Comments

1. The static moment applied to grid point G is

where, is a unit vector parallel to a vector calculated from the cross product of the
vectors from G1 to G2 and G3 to G4.

2. This card is represented as a moment load in HyperMesh.

1332 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MOTION

Bulk Data Entry

MOTION – Multi-body Motion Combination

Description

Defines a multi-body as a combination of motion sets defined via MOTNJ, MOTNJC, MOTNJE,
MOTNG, MOTNGC, and MOTNGE.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOTION SID M1 M2 M3 M4 M5 M6 M7

M8 M9 …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOTION 3 31 34 35

Field Contents

SID Motion set identification number.

(Integer > 0)

Mi Motion set identification numbers defined via entry typed enumerated


above.

(Integer > 0)

Comments

1. The Mi must be unique.

2. Motion sets must be selected in the Subcase Information section (MOTION=SID) if they
are to be applied.

Altair Engineering OptiStruct 13.0 Reference Guide 1333

Proprietary Information of Altair Engineering


3. This card is represented as a loadcollector in HyperMesh.

1334 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MOTNG

Bulk Data Entry

MOTNG – Constant Grid Point Motion for Multi-body Solution Sequence

Description

Defines a constant grid point motion.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOTNG SID G1 C1 G2 D D0 V0

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOTNG 3 345 3 1.0

Field Contents

SID Load set identification number.

(Integer > 0)

G1 Grid point identification number.

(Integer > 0)

C1 Component number (Integer 1 through 18). The component refers to the


direction and type of motion of the grid point G1 in the Basic Coordinate
System (not the Local Coordinate System).

G2 Grid point identification number to define relative motion.

(Integer > 0 or blank)

D Scale factor.

Altair Engineering OptiStruct 13.0 Reference Guide 1335

Proprietary Information of Altair Engineering


(Real)

D0 Initial displacement if motion data is of type velocity or acceleration,


ignored otherwise.

V0 Initial velocity if motion data type is acceleration, ignored otherwise.

Comments

1. If G1 and G2 are defined, the motion is a relative motion between the two grid points; if
G2 is blank, absolute motion of G1 is defined.

2. The types and directions of motion for the component numbers are given in the following
table.

Component Number(s) Type of Motion Direction(s) of Motion

1, 2, and 3 Displacement X, Y, Z

4, 5, and 6 Rotation X, Y, Z

7, 8, and 9 Translational Velocity X, Y, Z

10, 11, and 12 Angular Velocity X, Y, Z

13, 14, and 15 Translational Acceleration X, Y, Z

16, 17, and 18 Angular Acceleration X, Y, Z

The component numbers and directions of motion are in the format: 1->X, 2->Y and 3->Z
for Displacement and this format is followed for all the types in the table.

3. This card is represented as a constraint load in HyperMesh.

1336 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MOTNGC

Bulk Data Entry

MOTNGC – Grid Point Motion vs. Time Curve for Multi-body Solution Sequence

Description

Defines a grid point motion vs. time by specifying a curve.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOTNGC SID G1 C1 G2 C VID INT EID

D0 V0

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOTNGC 3 345 3 1 AKIMA 2

Field Contents

SID Load set identification number.

(Integer > 0)

G1 Grid point identification number.

(Integer > 0)

C1 Component number (Integer 1 through 18). The component refers to the


direction and type of motion of the grid point G1 in the Basic Coordinate
System (not the Local Coordinate System).

G2 Grid point identification number to define relative motion.

(Integer > 0 or blank)

Altair Engineering OptiStruct 13.0 Reference Guide 1337

Proprietary Information of Altair Engineering


Field Contents

CVID Set identification number of the MBCRV entry that gives the motion vs.
time.

(Integer > 0)

INT Interpolation type (Character: LINEAR, CUBIC, AKIMA).

Default = AKIMA

EID Set identification number of the MBVAR for the independent variable
expression.

Default = TIME (Integer > 0 or blank)

D0 Initial displacement if motion data is of type velocity or acceleration,


ignored otherwise.

V0 Initial velocity if motion data type is acceleration, ignored otherwise.

Comments

1. If G1 and G2 are defined, the motion is a relative motion between the two grid points; if
G2 is blank, absolute motion of G1 is defined.

2. The types and directions of motion for the component numbers are given in the following
table.

Component Number(s) Type of Motion Direction(s) of Motion

1, 2, and 3 Displacement X, Y, Z

4, 5, and 6 Rotation X, Y, Z

7, 8, and 9 Translational Velocity X, Y, Z

10, 11, and 12 Angular Velocity X, Y, Z

13, 14, and 15 Translational Acceleration X, Y, Z

16, 17, and 18 Angular Acceleration X, Y, Z

The component numbers and directions of motion are in the format: 1->X, 2->Y and 3->Z
for Displacement and this format is followed for all the types in the table.

3. This card is represented as a constraint load in HyperMesh.

1338 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MOTNGE

Bulk Data Entry

MOTNGE – Expression Grid Point Motion for Multi-body Solution Sequence

Description

Defines a grid point motion through an expression.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOTNGE SID G1 C1 G2 EID D0 V0

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOTNGE 3 345 3 4

Field Contents

SID Load set identification number.

(Integer > 0)

G1 Grid point identification number.

(Integer > 0)

C1 Component number (Integer 1 through 18). The component refers to the


direction and type of motion of the grid point G1 in the Basic Coordinate
System (not the Local Coordinate System).

G2 Grid point identification number to define relative motion.

(Integer > 0 or blank)

Altair Engineering OptiStruct 13.0 Reference Guide 1339

Proprietary Information of Altair Engineering


Field Contents

EID Expression identification number of the MBVAR entry that gives the motion
vs. time.

(Integer > 0)

D0 Initial displacement if motion data is of type velocity or acceleration,


ignored otherwise.

V0 Initial velocity if motion data type is acceleration, ignored otherwise.

Comments

1. A CID of zero or blank references the basic coordinate system.

2. The types and directions of motion for the component numbers are given in the following
table.

Component Number(s) Type of Motion Direction(s) of Motion

1, 2, and 3 Displacement X, Y, Z

4, 5, and 6 Rotation X, Y, Z

7, 8, and 9 Translational Velocity X, Y, Z

10, 11, and 12 Angular Velocity X, Y, Z

13, 14, and 15 Translational Acceleration X, Y, Z

16, 17, and 18 Angular Acceleration X, Y, Z

The component numbers and directions of motion are in the format: 1->X, 2->Y and 3->Z
for Displacement and this format is followed for all the types in the table.

1340 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MOTNJ

Bulk Data Entry

MOTNJ – Constant Joint Motion for Multi-body Solution Sequence

Description

Defines a constant joint motion.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOTNJ SID JID MTYPE D DTYPE D0 V0

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOTNJ 3 345 TRANS 1.0 DIS

Field Contents

SID Load set identification number.

(Integer > 0)

JID Joint identification number.

(Integer > 0)

MTYPE TRANS or ROT, ignored for revolute and translational joints.

D Value of motion.

(Real)

DTYPE Motion data type (DIS or VEL or ACC), blank means displacement
motion.

Altair Engineering OptiStruct 13.0 Reference Guide 1341

Proprietary Information of Altair Engineering


Field Contents

D0 Initial displacement if motion data is of type velocity or acceleration,


ignored otherwise.

V0 Initial velocity if motion data type is acceleration, ignored otherwise.

Comments

1. Joint motion can only be applied to cylindrical joints (MTYPE = TRANS or ROT), revolute
joints (MTYPE = ROT), and translational joints (MTYPE = TRANS).

1342 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MOTNJC

Bulk Data Entry

MOTNJC – Joint Motion vs. Time Curve for Multi-body Solution Sequence

Description

Defines a joint motion vs. time by specifying a curve.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOTNJC SID JID MTYPE C VID INT EID DTYPE

D0 V0

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOTNJC 3 345 ROT 2 AKIMA 99

Field Contents

SID Load set identification number.

(Integer > 0)

JID Grid point identification number.

(Integer > 0)

MTYPE TRANS or ROT, ignored for revolute and translational joints.

CVID Set identification number of the MBCRV entry that gives the motion vs.
time.

(Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1343

Proprietary Information of Altair Engineering


Field Contents

INT Interpolation type (Character: LINEAR, CUBIC, AKIMA).

Default = AKIMA

EID Set identification number of the MBVAR for the independent variable
expression.

Default = TIME (Integer > 0 or blank)

DTYPE Motion data type (DIS or VEL or ACC), blank means displacement motion.

D0 Initial displacement if motion data is of type velocity or acceleration,


ignored otherwise.

V0 Initial velocity if motion data type is acceleration, ignored otherwise.

Comments

1. Joint motion can only be applied to cylindrical joints (MTYPE = TRANS or ROT), revolute
joints (MTYPE = ROT), and translational joints (MTYPE = TRANS).

1344 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MOTNJE

Bulk Data Entry

MOTNJE – Expression Joint Motion for Multi-body Solution Sequence

Description

Defines a joint motion through an expression.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOTNJE SID JID MTYPE EID DTYPE D0 V0

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MOTNJE 3 345 3 1

Field Contents

SID Load set identification number.

(Integer > 0)

JID Joint identification number.

(Integer > 0)

MTYPE TRANS or ROT, ignored for revolute and translational joints.

EID Expression identification number of the MBVAR entry that gives the
motion vs. time. If blank or zero, a constant motion of D is applied.

Default = constant motion D (Integer > 0 or blank)

DTYPE Motion data type (DIS or VEL or ACC), blank means displacement

Altair Engineering OptiStruct 13.0 Reference Guide 1345

Proprietary Information of Altair Engineering


Field Contents

motion.

D0 Initial displacement if motion data is of type velocity or acceleration,


ignored otherwise.

V0 Initial velocity if motion data type is acceleration, ignored otherwise.

Comments

1. Joint motion can only be applied to cylindrical joints (MTYPE = TRANS or ROT), revolute
joints (MTYPE = ROT), and translational joints (MTYPE = TRANS).

1346 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MPC

Bulk Data Entry

MPC – Multipoint Constraint

Description

The MPC bulk data entry defines a multipoint constraint equation of the form.

Aj u j 0
j

Where,
Aj
is the coefficient that can be used to define the relationship between the degrees of
freedom associated with grid points (or a scalar point) in the model.
uj
is the degree of freedom associated with a grid point (or a scalar point).

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MPC SID G C A G C A blank

blank G C A -etc.- blank

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MPC 3 28 3 6.2 2 2 4.29

1 4 -2.91

Field Contents

SID Set identification number.

Altair Engineering OptiStruct 13.0 Reference Guide 1347

Proprietary Information of Altair Engineering


Field Contents

(Integer > 0)

G Identification number of a grid point or a scalar point.

(Integer > 0 or <PartName.number>) See comment 5.

C Component number. See comment 3.

(Integer zero or blank for scalar points, or any one of the digits 1-6 for grid
points)

A Coefficient that can be used to define the relationship between the degrees of
freedom associated with grid points (or a scalar point).

(Real; the first A must be non-zero)

Comments

1. The first coordinate in the sequence is assumed to be the dependent coordinate. A


dependent degree-of-freedom assigned by one MPC entry cannot be assigned dependent
by another MPC entry or by a rigid element.

2. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).

3. The component refers to the coordinate system referenced by the grid point.

4. Illustrative Example:

Figure 1 can be used to illustrate an MPC application. Independent grid points G1 and G2
of a 2D quad element are connected with the help of an MPC; where Gd is the dependent
grid point. The objective of this example is to force the displacement of Gd to be equal to
the sum of the displacements of grid points G1 and G2 in the X (1) direction using an
MPC.

1348 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Figure : MPC Example Illustration

Rewriting the MPC equation for three grid points:

A1u1 A2 u2 A3 u3 0

Substituting A1 = 1.0, A2 = -1.0 and A3 = -1.0 in the equation above:

(1.0)ud ( 1.0)u1 ( 1.0)u2 0

Rearranging equation terms:

ud u1 u2

Where,

ud
is the displacement of grid point Gd in X direction

u1
is the displacement of grid point G1 in X direction

u2
is the displacement of grid point G2 in X direction

5. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on MPC entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry
in the model). “number” is the identification number of a referenced local entry in the part
“PartName”. See Parts and Instances in the User’s Guide for detailed information on the
use of fully qualified references.

6. This card is represented as an equation in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1349

Proprietary Information of Altair Engineering


MPCADD

Bulk Data Entry

MPCADD – Multipoint Constraint Set Combination

Description

Defines a multipoint constraint set as a union of multipoint constraint sets defined via MPC
entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MPC ADD SID S1 S2 S3 S4 S5 S6 S7

S8 S9 etc.

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

MPC ADD 101 2 3 1 6 4

Field Contents

SID Set identification number.

(Integer > 0)

Sj Set identification numbers of multipoint constraint sets defined via MPC


entries.

(Integer > 0 or <PartName.number>) See comment 5.

Comments

1. Multipoint constraint sets must be selected with the Subcase Information command
MPC=SID.

2. The Sj field should not reference the identification number of a multipoint constraint set

1350 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


defined by another MPCADD entry.

3. MPCADD entries take precedence over MPC entries. If both have the same SID, only the
MPCADD entry will be used.

4. If all Si are non-existent, the solver will exit with an error termination.

5. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on MPCADD entries in the model. A fully qualified reference
(“PartName.number”) is similar to the format of a numeric reference. “PartName” is the
name of the part that contains the referenced local entry (part names are defined on the
BEGIN Bulk Data Entry in the model). “number” is the identification number of a
referenced local entry in the part “PartName”. See Parts and Instances in the User’s
Guide for detailed information on the use of fully qualified references.

6. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1351

Proprietary Information of Altair Engineering


NLOAD

Bulk Data Entry

NLOAD – Nonlinear Load Combination or Superposition

Description

Defines a loading condition for nonlinear problems as a linear combination of load sets defined
via NLOAD1.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NLOAD SID S S1 L1 S2 L2 S3 L3

S4 L4 ... ... ... ... ... ...

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NLOAD 5 1.0 2.0 101 2.0 102 2.0 103

-2.0 201

Field Contents

SID Load set identification number.

No default (Integer > 0)

S Scale factor.

No default (Real)

Si Scale factors.

No default (Real)

1352 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Li Load set identification numbers of NLOAD1.

No default (Integer > 0)

Comments

1. Dynamic load sets must be selected in the I/O Options or Subcase Information sections
with NLOAD=SID.

2. The load vector being defined by this entry is given by:

3. Each Li must be unique from any other Li on the same entry.

4. SID must be unique from all NLOAD1 entries.

5. An NLOAD entry may not reference a set identification number defined by another NLOAD
entry.

6. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1353

Proprietary Information of Altair Engineering


NLOAD1

Bulk Data Entry

NLOAD1 – Time Dependent Load or Motion for Geometric Nonlinear Analysis

Description

Defines a time-dependent load or enforced motion for use in geometric nonlinear analysis.

f(t) = A * C * F(t/B)

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NLOAD1 SID EXC ITEID SENSID TYPE TID B C C ID

TSTART TEND

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NLOAD1 5 7 LOAD 13

Field Contents

SID Load set identification number.

(Integer > 0)

EXCITEID SID number of DAREA, SPCD or static load set that defines A. See
comments 2 and 3.

(Integer > 0)

SENSID Identification number of a sensor. Load application is activated once the


referenced sensor is activated.

1354 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

(Integer > 0)

TYPE Defines the type of the dynamic excitation. See comments 2 and 3.

Default = 0 (Integer, character or blank)

TID Identification number of TABLEDi entry defining the load history F(t).

(Integer > 0)

TID=0 implies F(t) is a linear function passing through (TTERM-TTERMS, 0)


and (TTERM, 1). TTERMS is the duration of each subcase. TTERM is the
termination time. TID = 0 is only for geometric nonlinear implicit (quasi-)
static analysis (NLGEOM).

B Scale factor of the time in f(t).

Default = 1.0 (Real > 0)

C Scale factor for the function value in f(t).

Default = 1.0 (Real)

CID Identification number of coordinate system defining a frame in which the


imposed velocity is defined. Applies only for TYPE = 2, V, VE, VEL, or VELO.
Only CORD1R and CORD2R systems are allowed.

(Integer > 0 or blank)

TSTART Start time. See comment 4.

Default = 0.0 (Real > 0.0)

TEND End time.

Default = 1030 (Real > TSTART)

Comments

1. Time-dependent load sets must be selected with the Subcase Information command
NLOAD = SID. It can only be selected in geometric nonlinear analysis subcases which are
defined by an ANALYSIS = NLGEOM, IMPDYN or EXPDYN subcase entry.

2. The type of the dynamic excitation is specified by TYPE (field 5) according to the
following table:

Altair Engineering OptiStruct 13.0 Reference Guide 1355

Proprietary Information of Altair Engineering


TYPE TYPE of Dynamic Excitation

O, L, LO, LOA, or LOAD Applied load (force, moment, pressure).

(Default)

1, D, DI, DIS, or DISP Enforced displacement using SPC/SPCD data.

2, V, VE, VEL, or VELO Enforced velocity using SPC/SPCD data.

3, A, AC, ACC, or ACCE Enforced acceleration using SPC/SPCD data

3. TYPE (field 5) also determines the manner in which EXCITEID (field 3) is used by the
program as described below.

Excitation specified by TYPE is applied load. The EXCITEID may reference DAREA, or
(and) static load set entries. If EXCITEID references both DAREA and static load set,
the two loads will be super-imposed.
Excitation specified by TYPE is enforced motion. The EXCITEID must reference SPCD
entries.
4. TSTART and TEND are only considered for enforced displacement, velocity, and
acceleration. The continuation line is optional.

5. This card is represented as a loadcollector in HyperMesh.

1356 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


NLPARM

Bulk Data Entry

NLPARM – Parameters for Nonlinear Static Analysis or Heat Transfer Analysis

Description

The NLPARM bulk data entry defines parameters for nonlinear static analysis or heat transfer
analysis solution control.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NLPARM ID NINC KSTEP MAXITER C ONV

EPSU EPSP EPSW MAXLS LSTOL

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NLPARM 99 5

Field Contents

ID Each NLPARM bulk data card must have a unique ID.

No default (Integer > 0)

NINC Number of implicit load sub-increments (see comments 2 and 3).

Default = 1 (no increments) for ANALYSIS = NLSTAT and ANALYSIS=NLHEAT

Default = 10 for ANALYSIS = NLGEOM

(Integer > 0)

KSTEP Number of iterations before stiffness update (see comment 3).

Default = 6 for ANALYSIS = NLGEOM and BCS solver

Altair Engineering OptiStruct 13.0 Reference Guide 1357

Proprietary Information of Altair Engineering


Field Contents

Default = 3 for ANALYSIS = NLGEOM and PCG solver

(Integer > 0)

MAXITER Limit on number of implicit iterations for each load increment. If reached, the
solution is terminated (ANALYSIS = NLSTAT and ANALYSIS=NLHEAT).

Default = 25 (Integer > 0)

CONV Flags to select implicit convergence criteria.

Default = UPW for ANALYSIS = NLSTAT

Default = PW for ANALYSIS = NLGEOM

(Any combination of U, P and W)

EPSU Error tolerance for displacement (U) criterion.

Default = 1.0E-3 for ANALYSIS = NLSTAT

Default = 1.0E-2 for ANALYSIS = NLGEOM

(Real > 0.0)

EPSP Error tolerance for load (P) criterion.

Default = 1.0E-3 for ANALYSIS = NLSTAT and ANALYSIS=NLHEAT

Default = 1.0E-2 for ANALYSIS = NLGEOM

(Real > 0.0)

EPSW Error tolerance for work (W) criterion.

Default = 1.0E-7 for ANALYSIS = NLSTAT and ANALYSIS=NLHEAT

Default = 1.0E-3 for ANALYSIS = NLGEOM

(Real > 0.0)

MAXLS Maximum number of line searches allowed for each iteration.

Default = 20 (Integer > 0)

1358 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

LSTOL Line search tolerance.

Default = 1.0E-3 (Real > 0.0)

Comments

1. The NLPARM bulk data entry is selected by the Subcase Information command
NLPARM=option. Each subcase for which nonlinear analysis is desired requires an NLPARM
command.

2. The solution method for quasi-static nonlinear analysis (ANALYSIS = NLSTAT) is full
Newton. The stiffness matrix is updated at each iteration. NINC > 0 represents the
number of equal subdivisions that the total load in a given subcase will be divided into. If
NINC is blank, the entire load for a given subcase is applied at once. The Newton method
will be applied to consecutive load levels until the final load is reached.

3. Additional control for geometric nonlinear implicit static solution schemes (ANALYSIS =
NLGEOM) can be defined using the NLPARMX bulk data entry. Defaults will be used if
NLPARMX is not present.

4. The solution method for geometric nonlinear implicit analysis (ANALYSIS = NLGEOM) is
modified or Quasi-Newton. The frequency of stiffness matrix updates is controlled by
KSTEP. For highly nonlinear problems, it is recommended to reduce KSTEP for better
performance. KSTEP = 1 means full Newton.

If the loading is defined using NLOAD, the termination time TTERM must defined by a
TTERM subcase entry. The initial implicit time step is TTERMS/NINC with TTERMS =
TTERM – T0. All subsequent time steps will be determined automatically. In a simulation
with multiple nonlinear subcases, T0 is the end time of the previous load step. If there is
only a single nonlinear subcase, T0 = 0.0.

If the loading is defined using LOAD, TTERM is not mandatory. These loads are treated as
linear ramp-up. If TTERM is defined, the load ramps up from the end time of the previous
subcase to TTERM. If TTERM is absent, it will be determined from the subcase sequence
such that the duration of each subcase TTERMS = 1.0. In this case, the initial time step
is 1.0/NINC.

5. For Nastran compatibility, NLPCI is imported if present. Only the fields ID, TYPE are
interpreted. With NLPCI present, the default for NLPARMX, SACC will be reset to RIKS.
TYPE will be translated into CTYPE; all other entries are set to default. A warning will be
issued. NLPCI and NLPARMX cannot be used simultaneously. It is recommended to remove
NLPCI and use NLPARMX with the appropriate definitions.

6. For more information about nonlinear quasi-static analysis, see the Nonlinear Quasi-static
Analysis section.

7. For more information about geometric nonlinear analysis, see the Geometric Nonlinear
Analysis section.

8. For more information about nonlinear steady-state heat transfer analysis, see the
Nonlinear Steady-State Heat Transfer Analysis section.

Altair Engineering OptiStruct 13.0 Reference Guide 1359

Proprietary Information of Altair Engineering


9. This card is represented as a loadcollector in HyperMesh.

1360 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


NLPARMX

Bulk Data Entry

NLPARMX – Optional Parameters for Geometric Nonlinear Implicit Static Analysis Control

Description

Defines additional parameters for geometric nonlinear implicit static analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NLPARMX ID TA0 DTA DTTH NPRINT RFILE

SOLV TSC TRL DTMIN DTMAX LSMETH RREFIF NC YC LE FIXTID/


TOUT

KINER DTSC Q ILIN SMDISP SPRBK

ITW DTSC I LDTN DTSC D LARC C TYP WSC AL

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NLPARM 99

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NLPARM 99

NLPARMX 99 0.1

NEWT ARC 1.e-4 0.1

Altair Engineering OptiStruct 13.0 Reference Guide 1361

Proprietary Information of Altair Engineering


Example 3

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NLPARM 99 3 PW

0.01 0.01 0.01

NLPARMX 99 0.1

NEWT ARC 1.e-4 0.1

NEWM 0.25 0.5

Field Contents

ID Identification number of an associated NLPARM entry.

No default (Integer > 0)

TA0 Start time for writing animation files.

Default = 0.0 (Real > 0)

DTA Output time step for animation files. If zero, no output (See comment 3).

Default = DTINI (Real > 0)

DTTH Output time step for time history files. If zero, no output (See comment 3).

Default = 0.1*DTINI (Real > 0)

NPRINT Print every NPRINT iterations. If negative, to .out and standard output; if
positive, only to .out file.

Default = -1 (Integer)

RFILE Cycle frequency to write restart file for nonlinear iteration.

Default = 5000 (Integer > 0)

1362 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

SOLV Geometric nonlinear implicit solution method.

NEWT – Modified Newton

BFGS – BFGS quasi-Newton method

Default = NEWT (Character = NEWT or BFGS)

TSCTRL Time step control.

ARC – Arc-length is used to accelerate and control the convergence. The


time step is determined by displacement norm control (arc-length).

SIMP – Simple time step control.

RIKS – Riks method for post-buckling analysis (only with SOLV = NEWT).

NONE – No time step control. A warning will be issued. In the case of


divergence the time step will be repeated with half the step size. The run
will be terminated according to DTMIN and NCYCLE.

Default = ARC (Character)

DTMIN Minimum implicit time step. If DTMIN is reached, simulation will be terminated
(See comment 3).

Default = 1e-4*DTINI (Real > 0)

DTMAX Maximum implicit time step from which time step is set constant (See
comment 3).

Default = 3*DTINI (Real > 0)

LSMETH Line search method.

Default = ENERGY (Character = NONE, FORCE, ENERGY, or AUTO)

RREFIF Special residual force computation with contact interfaces present.

Default = no special treatment (Integer = 0, …, 5)

0 – Aggressive (modified entirely by the out-of-balance value)


1 – Average (modified each time with 200% maximum)
2 – Light (modified each time with 20% maximum)
3 – No modification

Altair Engineering OptiStruct 13.0 Reference Guide 1363

Proprietary Information of Altair Engineering


Field Contents

4 – No modification; except for the first contact.


5 – Modified automatically (for imposed displacement only)

NCYCLE Maximum number of time steps. If reached, solution will be terminated.


NCYCLE = 0 means no limit.

Default = no limit (Integer > 0)

FIXTID Identification number of a TABLEDi entry. The x values of the table define
fixed time points that the automatic time step control will adhere to.

(Integer > 0)

TOUT The method to determine the fixed time point.

AUTO – Fully automatic time step control.


NLOAD - The time points in all TABLEDi that are referenced by NLOAD1 in one
subcase.

Default = AUTO (AUTO or NLOAD)

KINER Inertia Stiffness for handling models that are not sufficiently constrained.
May require definition of DTSCQ (See comment 4).

Default = OFF (Character = ON, OFF)

DTSCQ Scale factor for inertia stiffness matrix used in quasi-static analysis (KINER =
ON, See comment 4).

Default = 1.0 (Real > 0)

ILIN Perform linear instead of nonlinear analysis. For debugging purposes.


(ANALYSIS = NLGEOM, See comment 5).

LIN – Linear analysis without contact.

LINC – Linear analysis with contact.

Default is nonlinear analysis (Character = LIN, LINC)

SMDISP Perform small displacement and rotation analysis instead of geometric


nonlinear analysis. PARAM, SMDISP, 1 overwrites this definition.

OFF – Geometric nonlinear analysis.

1364 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

ON – Small displacements and small rotations analysis.

Default = OFF (Character = ON, OFF)

SPRBK Perform spring back analysis. Equilibrium is reached when the internal forces
are less or equal to the tolerances given on NLPARM.

OFF – Regular analysis.

ON – Spring back analysis.

Default = OFF (Character = ON, OFF)

ITW If the solution of a time step converges within ITW iterations the next time
step will be increased by a factor controlled by DTSCI.

Default = 6 for TSCTRL = ARC

Default = 2 for TSCTRL = SIMP

Default = 12 for TSCTRL = RIKS

Default = 6 (Integer > 0)

DTSCI Maximum scale factor for increasing the time step (TSCTRL = ARC, RIKS).
Scale factor for TSCTRL = SIMP.

Default = 1.1 (Real > 0)

LDTN Maximum number of iterations before resetting and decreasing the time step
by a factor of DTSCD.

Default = 20 for TSCTRL = ARC

Default = 15 for TSCTRL = SIMP

Default = 25 for TSCTRL = RIKS

(Integer > 0)

DTSCD Scale factor for decreasing the time step (TSCTRL = ARC, SIMP, RIKS).

Default = 0.67 (Real > 0)

LARC Input arc-length for TSCTRL = ARC, RIKS

Altair Engineering OptiStruct 13.0 Reference Guide 1365

Proprietary Information of Altair Engineering


Field Contents

Default = automatic computation (Real)

CTYP Constraint type (See comment 6).

CRIS – Crisfield constraint equation.

MFSRIKS –- Modified Forde & Stiemer equation.

Default = CRIS (CRIS or MFSRIKS)

WSCAL Scale factor for controlling the loading contribution in the constraint
equation.

Default = 0.0 (Real > 0.0)

Comments

1. The NLPARMX bulk data entry is selected by the Subcase Information command NLPARM =
option. There must also be an NLPARM bulk data entry with the same ID. It is only used
in geometric nonlinear implicit static analysis (ANALYSIS = NLGEOM); it is ignored in other
analyses.

2. The solution method for geometric nonlinear implicit analysis is selected by SOLV. The
frequency of stiffness matrix updates is controlled by KSTEP. For highly nonlinear
problems, it is recommended to reduce KSTEP for better performance. KSTEP = 1 means
full Newton.

3. If the loading is defined using NLOAD, the termination time TTERM must be defined by a
TTERM subcase entry. The initial implicit time step is DTINI = TTERMS/NINC with TTERMS
= TTERM – T0. All subsequent time steps will be determined automatically. In a
simulation with multiple nonlinear subcases, T0 is the end time of the previous load step.
If there is only a single nonlinear subcase, T0 = 0.0.

If the loading is defined using LOAD, TTERM is not mandatory. These loads are treated as
linear ramp-up. If TTERM is defined, the load ramps up from the end time of the previous
subcase to TTERM. If TTERM is absent, it will be determined from the subcase sequence
such that the duration of each subcase TTERMS = 1.0. In this case, the initial time step
is DTINI = 1.0/NINC.

4. For models that are not sufficiently constrained, inertia stiffness can be used to overcome
a singular stiffness matrix. The inertia stiffness [K]inertia = 1/(DTSCQ*dt)^2[M] is added
to the stiffness matrix [K]. Care needs to be taken in the selection of DTSCQ. Too large
of an added mass may lead to wrong results.

5. Linear static and normal modes analysis within geometric nonlinear analysis (ILIN = LIN,
LINC) are provided for debugging purposes. They may help detecting modeling errors. All
materials are linearized, and linear displacements are assumed as well. The load is taken
at the termination time. To run normal modes analysis, a METHOD subcase entry that
refers to an EIGL bulk data entry must be provided.

1366 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


6. The constraint equation for CTYP = CRIS is:

Where, u is displacement, j the scale factor (WSCAL) , l a load factor, and r the arc-
length.

The constraint equation for CTYP = MFSRIKS is:

Where, is the displacement, due to a unit load factor, and is the displacement
increment from the conventional Newton type method. The meaning of u, j, l, and r are
the same as those above.

7. For Nastran compatibility, NLPCI is imported if present. Only the fields ID, TYPE are
interpreted. With NLPCI present, the default for TSCTRL will be reset to RIKS. TYPE will
be translated into CTYP; all other entries are set to default. A warning will be issued.
NLPCI and NLPARMX cannot be used simultaneously. It is recommended to remove NLPCI
and use NLPARMX with the appropriate definitions

8. For more information about geometric nonlinear analysis, see the Geometric Nonlinear
Analysis section.

9. This card is represented as an extension to an NLPARMX loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1367

Proprietary Information of Altair Engineering


NLPCI

Bulk Data Entry

NLPCI – Implicit Time Step Control for Riks Type Arc-Length Method

Description

Define implicit automatic time step control with Riks type arc-length method.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NLPC I ID TYPE

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NLPC I 5 C RIS

Field Contents

ID Identification number of an associated NLPARM entry.

No default (Integer > 0)

TYPE Constraint type

Default = CRIS (CRIS, RIKS, or MRIKS)

Comments

1. The NLPCI bulk data entry is selected by the Subcase Information command NLPARM =
option. There must also be an NLPARM entry with the same ID. It is only used in
geometric nonlinear (quasi-)static analysis (ANALYSIS = NLGEOM).

2. NLPCI is implemented for Nastran compatibility and imported if present. Only the fields ID,
TYPE are interpreted. With NLPCI present, the default for NLPARMX, SACC will be reset
to RIKS. TYPE will be translated into CTYPE; all other entries are set to default. A
warning will be issued. NLPCI and NLPARMX cannot be used simultaneously. It is

1368 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


recommended to remove NLPCI and use NLPARMX with the appropriate definitions.

3. This card is an unsupported bulk data entry in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1369

Proprietary Information of Altair Engineering


NLRGAP

Bulk Data Entry

NLRGAP – Nonlinear Load Proportional to Gap

Description

Defines a nonlinear radial (circular) gap for direct transient response analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NLRGAP SID GA GB PLANE TABK TABG TABU RADIUS

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NOLIN1 21 3 4 XY 3 10 6 1.6

Field Contents

SID Nonlinear load set identification number.

No default (Integer > 0)

GA Inner grid for radial gap (shaft).

No default (Integer > 0)

GB Outer grid for radial gap (housing).

No default (Integer > 0)

PLANE Radial gap orientation plane.

Default = XY (XY, YZ or ZX)

TABK Table ID defining either (See comment 11):

Gap stiffness vs. time

1370 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Gap force vs. penetration


No default (Integer > 0)

TABG Table ID for radial gap clearance as a function of time.

No default (Integer > 0)

TABU Table ID for radial coefficient of friction as a function of time.

No default (Integer > 0)

RADIUS Shaft radius.

Default = 0.0 (Real > 0.0)

Comments

1. Nonlinear radial gap must be selected by the Subcase Information data selector
NONLINEAR.

2. Multiple NLRGAP entries with the same SID are allowed.

3. The NLRGAP is not an element, but a nonlinear load similar to the NOLIN1, NOLIN2, NOLIN3
and NOLIN4 entries. It computes the relative displacements of GA and GB in the selected
plane and applies appropriate nonlinear loads to simulate the radial contact.

4. The degrees of freedom in the XY, YZ and ZX planes (depending on the PLANE defined) of
GA and GB must be members of the solution set. This means that they must not be
dependent degrees of freedom and the must not have SPCs applied to them. If RADIUS is
> 0.0, then the in-plane rotation degree of freedom must also be in the solution set.

5. The NLRGAP is limited to use in direct transient response analysis.

6. The XY, YZ and ZX planes are relative to the displacement coordinate systems of GA and
GB.

7. GA and GB must both be grid points, they must both be coincident, and they must have
parallel displacement coordinate systems. If any of these conditions are not met, an error
termination will occur.

8. The shaft radius is used only for the computation of friction induced torque.

9. A positive coefficient of friction is consistent with a counter-clockwise shaft rotation.

Altair Engineering OptiStruct 13.0 Reference Guide 1371

Proprietary Information of Altair Engineering


10. The time step algorithm in transient solution sequences may loose unconditional stability
when this load entry is used. In most practical cases, the time step size chosen to reach
a certain accuracy is below the stability limit. It is recommended to decrease the time
step if results diverge.

11. If the integer entered in the TABK field is positive, it is the ID of a TABLED1 entry defining
time vs. gap stiffness. If the integer is negative, then the absolute value of the integer is
the ID of a TABLED1 entry defining gap penetration vs. gap force.

12. Forces due to TABK and TABU at GA and GB are only present when the gap is closed. A
moment is applied only when the gap is closed and RADIUS > 0.0.

1372 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


NOLIN1

Bulk Data Entry

NOLIN1 – Nonlinear Transient Load as a Tabular Function

Description

Defines nonlinear transient forcing functions of the form

Function of displacement:

Function of velocity:

where, and are the displacement and velocity at point GJ in the direction of CJ.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NOLIN1 SID GI CI S GJ CJ TID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NOLIN1 21 3 4 2.1 3 10 6

Field Contents

SID Nonlinear load set identification number.

No default (Integer > 0)

GI Grid or scalar point identification number at which nonlinear load is to be


applied.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1373

Proprietary Information of Altair Engineering


Field Contents

CI Component number for GI.

No default (1 < Integer < 6; blank or 0 if GI is a scalar point)

S Scale factor.

No default (Real)

GJ Grid or scalar point identification number.

No default (Integer > 0)

CJ Component number for GJ, according to the following table:

Type Displacement Velocity

Grid 1 < Integer < 6 11 < Integer < 16

Scalar Blank or 0 Integer = 10

TID Identification number of a TABLED1, TABLED2, TABLED3, or TABLED4 entry.

No default (Integer > 0)

Comments

1. Nonlinear loads must be selected by the Subcase Information data selector NONLINEAR.

2. Nonlinear loads may not be referenced on a DLOAD entry.

3. All degrees-of-freedom referenced on NOLIN1 entries must be members of the solution


set.

4. Nonlinear loads as a function of velocity are denoted by components ten greater than the
actual component number; that is the component 11 indicates velocity in the 1
component direction. The velocity is determined by:

where, is the time step interval and is the displacement of GJ-CJ for the
previous time step.

5. The time step algorithm in transient solution sequences may loose unconditional stability

1374 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


when this load entry is used. In most practical cases, the time step size chosen to reach
a certain accuracy is below the stability limit. It is recommended to decrease the time
step if results diverge.

Altair Engineering OptiStruct 13.0 Reference Guide 1375

Proprietary Information of Altair Engineering


NOLIN2

Bulk Data Entry

NOLIN1 – Nonlinear Transient Load as the Product of Two Variables

Description

Defines nonlinear transient forcing functions of the form

where, and can be either displacement or velocity at points GJ and GK,


respectively, in the directions of CJ and CK, respectively.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NOLIN2 SID GI CI S GJ CJ GK CK

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NOLIN2 14 2 1 2.9 2 1 2

Field Contents

SID Nonlinear load set identification number.

No default (Integer > 0)

GI Grid or scalar point identification number at which nonlinear load is to be


applied.

No default (Integer > 0)

CI Component number for GI.

1376 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

No default (1 < Integer < 6; blank or 0 if GI is a scalar point)

S Scale factor.

No default (Real)

GJ, GK Grid or scalar point identification number.

No default (Integer > 0)

CJ, CK Component number for GJ, GK according to the following table:

Displacement Velocity
Type

Grid 1 < Integer < 6 11 < Integer < 16

Scalar Blank or 0 Integer = 10

Comments

1. Nonlinear loads must be selected by the Subcase Information data selector NONLINEAR.

2. Nonlinear loads may not be referenced on a DLOAD entry.

3. All degrees-of-freedom referenced on NOLIN2 entries must be members of the solution


set.

4. GI-CI, GJ-CJ and GK-CK may be the same degree-of-freedom.

5. Nonlinear loads may be a function of displacement or velocity .


Velocities are denoted by a component number ten greater than the actual component
number; that is the component 11 indicates velocity in the 1 component direction. The
velocity is determined by:

where, is the time step interval and is the displacement of GJ-CJ or GK-CK for the
previous time step.

6. The time step algorithm in transient solution sequences may loose unconditional stability
when this load entry is used. In most practical cases, the time step size chosen to reach
a certain accuracy is below the stability limit. It is recommended to decrease the time
step if results diverge.

Altair Engineering OptiStruct 13.0 Reference Guide 1377

Proprietary Information of Altair Engineering


NOLIN3

Bulk Data Entry

NOLIN1 – Nonlinear Transient Load as a Positive Variable Raised to a Power

Description

Defines nonlinear transient forcing functions of the form

where, may be a displacement or a velocity at point GJ in the direction of CJ.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NOLIN3 SID GI CI S GJ CJ A

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NOLIN3 4 102 -6.1 2 15 -3.5

Field Contents

SID Nonlinear load set identification number.

No default (Integer > 0)

GI Grid or scalar point identification number at which nonlinear load is to be


applied.

No default (Integer > 0)

CI Component number for GI.

1378 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

No default (1 < Integer < 6; blank or 0 if GI is a scalar point)

S Scale factor.

No default (Real)

GJ Grid or scalar point identification number.

No default (Integer > 0)

CJ Component number for GJ, GK according to the following table:

Type Displacement Velocity

Grid 1 < Integer < 6 11 < Integer < 16

Scalar Blank or 0 Integer = 10

A Exponent of the forcing function.

No default (Real)

Comments

1. Nonlinear loads must be selected by the Subcase Information data selector NONLINEAR.

2. Nonlinear loads may not be referenced on a DLOAD entry.

3. All degrees-of-freedom referenced on NOLIN3 entries must be members of the solution


set.

4. Nonlinear loads may be a function of displacement or velocity .


Velocities are denoted by components ten greater than the actual component number;
that is the component 11 indicates velocity in the 1 component direction. The velocity is
determined by:

where, is the time step interval and is the displacement of GJ-CJ for the
previous time step.

Altair Engineering OptiStruct 13.0 Reference Guide 1379

Proprietary Information of Altair Engineering


5. Use a NOLIN4 entry for the negative range of .

6. The time step algorithm in transient solution sequences may loose unconditional stability
when this load entry is used. In most practical cases, the time step size chosen to reach
a certain accuracy is below the stability limit. It is recommended to decrease the time
step if results diverge.

1380 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


NOLIN4

Bulk Data Entry

NOLIN1 – Nonlinear Transient Load as a Negative Variable Raised to a Power

Description

Defines nonlinear transient forcing functions of the form

where, may be a displacement or a velocity at point GJ in the direction of CJ.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NOLIN4 SID GI CI S GJ CJ A

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NOLIN4 2 4 6 2.0 101 16.3

Field Contents

SID Nonlinear load set identification number.

No default (Integer > 0)

GI Grid or scalar point identification number at which nonlinear load is to be


applied.

No default (Integer > 0)

CI Component number for GI.

Altair Engineering OptiStruct 13.0 Reference Guide 1381

Proprietary Information of Altair Engineering


Field Contents

No default (1 < Integer < 6; blank or 0 if GI is a scalar point)

S Scale factor.

No default (Real)

GJ Grid or scalar point identification number.

No default (Integer > 0)

CJ Component number for GJ, GK according to the following table:

Type Displacement Velocity

Grid 1 < Integer < 6 11 < Integer < 16

Scalar Blank or 0 Integer = 10

A Exponent of the forcing function.

No default (Real)

Comments

1. Nonlinear loads must be selected by the Subcase Information data selector NONLINEAR.

2. Nonlinear loads may not be referenced on a DLOAD entry.

3. All degrees-of-freedom referenced on NOLIN4 entries must be members of the solution


set.

4. Nonlinear loads may be a function of displacement or velocity .


Velocities are denoted by components ten greater than the actual component number;
that is the component 11 indicates velocity in the 1 component direction. The velocity is
determined by

where, is the time step interval and is the displacement of GJ-CJ for the
previous time step.

1382 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


5. Use a NOLIN3 entry for the positive range of .

6. The time step algorithm in transient solution sequences may loose unconditional stability
when this load entry is used. In most practical cases, the time step size chosen to reach
a certain accuracy is below the stability limit. It is recommended to decrease the time
step if results diverge.

Altair Engineering OptiStruct 13.0 Reference Guide 1383

Proprietary Information of Altair Engineering


NSM

Bulk Data Entry

NSM – Non-structural Mass per Unit Area or per Unit Length

Description

Defines non-structural mass per unit area or per unit length for a list of elements or
properties.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NSM SID TYPE ID VALUE ID VALUE ID VALUE

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NSM 4 PSHELL 155 0.06

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NSM 6 ELEMENT 12 0.03 13 0.03 14 0.03

Field Contents

SID Identification number of non-structural mass set.

No default (Integer > 0)

TYPE This can be one of the properties PSHELL, PCOMP, PBAR, PBARL, PBEAM,
PBEAML, PROD, CONROD, PSHEAR, or PTUBE, in which case the list of IDs will

1384 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

refer to properties of the stated type, or it can be ELEMENT, in which case the
list is of individual element IDs of elements that can have NSM.

No default (PSHELL, PCOMP, PBAR, PBARL, PBEAM, PBEAML, PROD, CONROD,


PSHEAR, PTUBE, or ELEMENT).

ID Property or Element ID, depending on the TYPE definition

No default (Integer > 0)

VALUE Non-structural mass per unit area or per unit length

No default (Real)

Comments

1. Refer to the User's Guide section on Non-structural Mass for more information on the use
of this card.

2. Non-structural mass in this format must be selected by the NSM Subcase Information
selector.

Altair Engineering OptiStruct 13.0 Reference Guide 1385

Proprietary Information of Altair Engineering


NSM1

Bulk Data Entry

NSM1 – Non-structural Mass per Unit Area or per Unit Length, Alternate Form 1

Description

Defines non-structural mass per unit area or per unit length for a list of elements or
properties.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NSM1 SID TYPE VALUE ID ID ID ID ID

ID ID ID -etc.-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NSM1 2 ELEMENT 0.063 1 8

Alternate Format and Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NSM1 SID TYPE VALUE ID THRU ID

NSM1 3 PSHELL 0.03 9 THRU 12

Field Contents

SID Identification number of non-structural mass set.

1386 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


No default (Integer > 0)

TYPE This can be one of the properties PSHELL, PCOMP, PBAR, PBARL, PBEAM, PBEAML,
PROD, CONROD, PSHEAR, or PTUBE, in which case the list of IDs will refer to
properties of the stated type, or it can be ELEMENT, in which case the list is of
individual element IDs of elements that can have NSM.

No default (PSHELL, PCOMP, PBAR, PBARL, PBEAM, PBEAML, PROD, CONROD,


PSHEAR, PTUBE, or ELEMENT).

VALUE Non-structural mass per unit area or per unit length

No default (Real)

ID Property or Element ID, depending on the TYPE definition

No default (Integer > 0, or "THRU")

Comments

1. Refer to the User's Guide section on Non-structural Mass for more information on the use
of this card.

2. Non-structural mass in this format must be selected by the NSM Subcase Information
selector.

Altair Engineering OptiStruct 13.0 Reference Guide 1387

Proprietary Information of Altair Engineering


NSMADD

Bulk Data Entry

NSMADD – Non-structural Mass Set Combination

Description

Defines non-structural mass as the sum of the sets listed.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NSMADD SID S1 S2 S3 S4 S5 S6 S7

S8 S9 S10 -etc.-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NSMADD 4 100 200

Field Contents

SID Identification number of non-structural mass set.

No default (Integer > 0)

S# Identification number of nonstructural mass sets defined via NSM, NSM1, NSML,
and NSML1 entries.

VALUE A lumped mass value to be distributed over all the listed elements and elements
referencing listed properties.

No default (Real)

1388 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

ID Property or Element ID, depending on the TYPE definition

No default (Integer > 0, or "THRU")

Comments

1. Refer to the User's Guide section on Non-structural Mass for more information on the use
of this card.

2. Non-structural mass in this format must be selected by the NSM Subcase Information
selector.

3. No S# may be the identification number of a non-structural mass set defined by another


NSMADD entry.

4. NSMADD entries take precedence over NSM, NSML, NSM1 or NSML1 entries. If both have
the same SID, only the NSMADD entry will be used.

Altair Engineering OptiStruct 13.0 Reference Guide 1389

Proprietary Information of Altair Engineering


NSML

Bulk Data Entry

NSML – Lumped Non-structural Mass

Description

Defines lumped non-structural mass for a list of elements or properties.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NSML SID TYPE ID VALUE ID VALUE ID VALUE

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NSML 6 PSHELL 16 0.29

Field Contents

SID Identification number of non-structural mass set.

No default (Integer > 0)

TYPE This can be one of the properties PSHELL, PCOMP, PBAR, PBARL, PBEAM,
PBEAML, PROD, CONROD, PSHEAR, or PTUBE, in which case the list of IDs will
refer to properties of the stated type, or it can be ELEMENT, in which case the
list is of individual element IDs of elements that can have NSM.

No default (PSHELL, PCOMP, PBAR, PBARL, PBEAM, PBEAML, PROD, CONROD,


PSHEAR, PTUBE, or ELEMENT).

ID Property or Element ID, depending on the TYPE definition

No default (Integer > 0)

1390 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

VALUE A lumped mass value to be distributed over all the listed elements and elements
referencing listed properties.

No default (Real)

Comments

1. Refer to the User's Guide section on Non-structural Mass for more information on the use
of this card.

2. Non-structural mass in this format must be selected by the NSM Subcase Information
selector.

3. This entry will calculated an equivalent non-structural mass per unit area or per unit
length using the lumped mass values provided.

For "area" elements, the calculation is:

and for "line" elements, the calculation is:

4. You cannot mix "area" and "line" elements on the same entry. The "area" elements are:
CQUAD4, CQUAD8, CTRIA3, CTRIA6, and CSHEAR; and the "line" elements are: CBAR,
CBEAM, CTUBE, CROD, and CONROD.

Altair Engineering OptiStruct 13.0 Reference Guide 1391

Proprietary Information of Altair Engineering


NSML1

Bulk Data Entry

NSML1 – Lumped Non-structural Mass, Alternate Form 1

Description

Defines lumped non-structural mass for a list of elements or properties.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NSML SID TYPE VALUE ID ID ID ID ID

ID ID ID -etc.-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NSML 3 ELEMENT 0.06 1 2 3 4

Alternate Format and Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

NSML SID TYPE VALUE ID THRU ID

NSML 3 ELEMENT 0.06 1 THRU 4

Field Contents

SID Identification number of non-structural mass set.

No default (Integer > 0)

1392 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

TYPE This can be one of the properties PSHELL, PCOMP, PBAR, PBARL, PBEAM, PBEAML,
PROD, CONROD, PSHEAR, or PTUBE, in which case the list of IDs will refer to
properties of the stated type, or it can be ELEMENT, in which case the list is of
individual element IDs of elements that can have NSM.

No default (PSHELL, PCOMP, PBAR, PBARL, PBEAM, PBEAML, PROD, CONROD,


PSHEAR, PTUBE, or ELEMENT).

VALUE A lumped mass value to be distributed over all the listed elements and elements
referencing listed properties.

No default (Real)

ID Property or Element ID, depending on the TYPE definition

No default (Integer > 0, or "THRU")

Comments

1. Refer to the User's Guide section on Non-structural Mass for more information on the use
of this card.

2. Non-structural mass in this format must be selected by the NSM Subcase Information
selector.

3. This entry will calculated an equivalent non-structural mass per unit area or per unit
length using the lumped mass values provided.

For "area" elements, the calculation is:

and for "line" elements, the calculation is:

4. You cannot mix "area" and "line" elements on the same entry. The "area" elements are:
CQUAD4, CQUAD8, CTRIA3, CTRIA6, and CSHEAR; and the "line" elements are: CBAR,
CBEAM, CTUBE, CROD, and CONROD.

Altair Engineering OptiStruct 13.0 Reference Guide 1393

Proprietary Information of Altair Engineering


PAABSF

Bulk Data Entry

PAABSF – Frequency-Dependant Fluid Acoustic Absorber Property

Description

Defines the properties of the fluid acoustic absorber element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PAABSF PID TZREID TSIMID S A B K RHOC

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PAABSF 4 3 4 1.0 0.5

Field Contents

PID Property identification number.

(Integer > 0)

TZREID Identification of the TABLEDi entry that defines the resistance as a function of
frequency. The real part of the impedance.

(Integer > 0 or Blank)

TZIMID Identification of the TABLEDi entry that defines the reactance as a function of
frequency. The imaginary part of impedance.

(Integer > 0 or Blank)

S Impedance scale factor.

Default = 1.0 (Real)

1394 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

A Area factor when 1 or 2 grid points are specified in the CAABSF entry.

Default = 1.0 (Real > 0.0)

B Equivalent damping coefficient.

Default = 0.0 (Real)

K Equivalent stiffness coefficient.

Default = 0.0 (Real)

RHOC Constant used in data recovery for calculating an absorption coefficient. RHO is
the media density and C is the speed of sound in the media.

Default = 1.0; current unused (Real)

Input File - mdcaabsf.parm

$$
$$ Optistruct Input Deck Generated by HyperMesh Version : 10.0build60
$$ Generated using HyperMesh-Optistruct Template Version : 10.0-SA1-120
$$
$$ Template: optistruct
$$
$$
$
DISPLACEMENT(PHASE) = 1
OUTPUT,HGFREQ,ALL
OUTPUT,OPTI,ALL
OUTPUT,H3D,ALL
OUTPUT,PUNCH,ALL
$$------------------------------------------------------------------------------$
$$ Case Control Cards $
$$------------------------------------------------------------------------------$
$
$HMNAME LOADSTEP 1"Piston_Load" 6
$
SUBCASE 1
LABEL Piston_Load
SPC = 12
METHOD(STRUCTURE) = 4
METHOD(FLUID) = 5
FREQUENCY = 3
DLOAD = 9
XYPUNCH DISP 1/ 11(T1)
XYPUNCH DISP 1/ 43(T1)
XYPUNCH DISP 1/ 55(T1)
XYPUNCH DISP 1/ 67(T1)
XYPUNCH DISP 1/ 79(T1)
XYPUNCH DISP 1/ 91(T1)
XYPUNCH DISP 1/ 103(T1)
XYPUNCH DISP 1/ 115(T1)

Altair Engineering OptiStruct 13.0 Reference Guide 1395

Proprietary Information of Altair Engineering


XYPUNCH DISP 1/ 127(T1)
XYPUNCH DISP 1/ 139(T1)
XYPUNCH DISP 1/ 151(T1)
XYPUNCH DISP 1/ 163(T1)
XYPUNCH DISP 1/ 175(T1)
XYPUNCH DISP 1/ 187(T1)
XYPUNCH DISP 1/ 199(T1)
XYPUNCH DISP 1/ 531(T1)
XYPUNCH DISP 1/ 543(T1)
XYPUNCH DISP 1/ 555(T1)
XYPUNCH DISP 1/ 567(T1)
XYPUNCH DISP 1/ 579(T1)
XYPUNCH DISP 1/ 591(T1)
XYPUNCH DISP 1/ 603(T1)
XYPUNCH DISP 1/ 615(T1)
XYPUNCH DISP 1/ 627(T1)
XYPUNCH DISP 1/ 639(T1)
XYPUNCH DISP 1/ 651(T1)
XYPUNCH DISP 1/ 663(T1)
XYPUNCH DISP 1/ 675(T1)
XYPUNCH DISP 1/ 687(T1)
$
$HMSET 1 1 "pressure"
SET 1 = 43,55,67,79,91,103,115,
127,139,151,163,175,187,199,
531,543,555,567,579,591,603,
615,627,639,651,663,675,687,
6798

$
$$--------------------------------------------------------------
$$ HYPERMESH TAGS
$$--------------------------------------------------------------
$$BEGIN TAGS
$$END TAGS
$
BEGIN BULK
ACMODL
$$
$$ Stacking Information for Ply-Based Composite Definition
$$

PARAM,AUTOSPC,YES
PARAM,POST,-1
$$
$$ DESVARG Data
$$
$$
$$ GRID Data
$$
GRID 9 0.492 0.0 -1.72-15 -1
GRID 10 0.246 0.0 -8.59-16 -1
GRID 11 0.0 0.0 0.0 -1
GRID 12 -0.246 0.0 8.589-16 -1
GRID 13 -0.492 0.0 1.718-15 -1
GRID 14 -0.492 0.246 1.718-15 -1
GRID 15 -0.492 0.492 1.718-15 -1
GRID 16 -0.246 0.492 8.589-16 -1
GRID 17 0.0 0.492 0.0 -1
GRID 18 0.246 0.492 -8.59-16 -1
GRID 19 0.492 0.492 -1.72-15 -1
GRID 20 0.492 0.246 -1.72-15 -1
GRID 21 0.0 0.246 0.0 -1
GRID 22 -0.246 0.246 8.589-16 -1
GRID 23 0.246 0.246 -8.59-16 -1
GRID 24 0.492 -0.246 -1.72-15 -1
GRID 25 0.492 -0.492 -1.72-15 -1
GRID 26 0.246 -0.492 -8.59-16 -1

1396 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 27 0.0 -0.492 0.0 -1
GRID 28 -0.246 -0.492 8.589-16 -1
GRID 29 -0.492 -0.492 1.718-15 -1
GRID 30 -0.492 -0.246 1.718-15 -1
GRID 31 0.0 -0.246 0.0 -1
GRID 32 0.246 -0.246 -8.59-16 -1
GRID 33 -0.246 -0.246 8.589-16 -1
GRID 34 0.246 5.049-29-.300073 -1
GRID 35 -5.99-130.0 -.300073 -1
GRID 36 -5.62-130.246 -.300073 -1
GRID 37 0.246 0.246 -.300073 -1
GRID 38 0.246 2.524-29-.600146 -1
GRID 39 -1.2-12 0.0 -.600146 -1
GRID 40 -1.12-120.246 -.600146 -1
GRID 41 0.246 0.246 -.600146 -1
GRID 42 0.246 2.919-29-0.90022 -1
GRID 43 -1.79-120.0 -.900219 -1
GRID 44 -1.68-120.246 -.900219 -1
GRID 45 0.246 0.246 -0.90022 -1
GRID 46 0.246 3.787-29-1.20029 -1
GRID 47 -2.39-120.0 -1.20029 -1
GRID 48 -2.24-120.246 -1.20029 -1
GRID 49 0.246 0.246 -1.20029 -1
GRID 50 0.246 4.733-29-1.50037 -1
GRID 51 -3.0-12 0.0 -1.50037 -1
GRID 52 -2.81-120.246 -1.50037 -1
GRID 53 0.246 0.246 -1.50037 -1
GRID 54 0.246 5.364-29-1.80044 -1
GRID 55 -3.6-12 0.0 -1.80044 -1
GRID 56 -3.37-120.246 -1.80044 -1
GRID 57 0.246 0.246 -1.80044 -1
GRID 58 0.246 6.311-29-2.10051 -1
GRID 59 -4.2-12 0.0 -2.10051 -1
GRID 60 -3.93-120.246 -2.10051 -1
GRID 61 0.246 0.246 -2.10051 -1
GRID 62 0.246 7.258-29-2.40059 -1
GRID 63 -4.79-120.0 -2.40059 -1
GRID 64 -4.49-120.246 -2.40059 -1
GRID 65 0.246 0.246 -2.40059 -1
GRID 66 0.246 8.204-29-2.70066 -1
GRID 67 -5.39-120.0 -2.70066 -1
GRID 68 -5.06-120.246 -2.70066 -1
GRID 69 0.246 0.246 -2.70066 -1
GRID 70 0.246 8.835-29-3.00073 -1
GRID 71 -5.99-120.0 -3.00073 -1
GRID 72 -5.62-120.246 -3.00073 -1
GRID 73 0.246 0.246 -3.00073 -1
GRID 74 0.246 9.782-29-3.30081 -1
GRID 75 -6.59-120.0 -3.30081 -1
GRID 76 -6.18-120.246 -3.30081 -1
GRID 77 0.246 0.246 -3.30081 -1
GRID 78 0.246 1.073-28-3.60088 -1
GRID 79 -7.19-120.0 -3.60088 -1
GRID 80 -6.74-120.246 -3.60088 -1
GRID 81 0.246 0.246 -3.60088 -1
GRID 82 0.246 1.136-28-3.90095 -1
GRID 83 -7.78-120.0 -3.90095 -1
GRID 84 -7.3-12 0.246 -3.90095 -1
GRID 85 0.246 0.246 -3.90095 -1
GRID 86 0.246 1.231-28-4.20102 -1
GRID 87 -8.38-120.0 -4.20102 -1
GRID 88 -7.86-120.246 -4.20102 -1
GRID 89 0.246 0.246 -4.20102 -1
GRID 90 0.246 1.294-28-4.5011 -1
GRID 91 -8.99-120.0 -4.5011 -1
GRID 92 -8.43-120.246 -4.5011 -1
GRID 93 0.246 0.246 -4.5011 -1
GRID 94 0.246 1.388-28-4.80117 -1
GRID 95 -9.59-120.0 -4.80117 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1397

Proprietary Information of Altair Engineering


GRID 96 -8.99-120.246 -4.80117 -1
GRID 97 0.246 0.246 -4.80117 -1
GRID 98 0.246 1.452-28-5.10124 -1
GRID 99 -1.02-110.0 -5.10124 -1
GRID 100 -9.55-120.246 -5.10124 -1
GRID 101 0.246 0.246 -5.10124 -1
GRID 102 0.246 1.515-28-5.40132 -1
GRID 103 -1.08-110.0 -5.40132 -1
GRID 104 -1.01-110.246 -5.40132 -1
GRID 105 0.246 0.246 -5.40132 -1
GRID 106 0.246 1.609-28-5.70139 -1
GRID 107 -1.14-110.0 -5.70139 -1
GRID 108 -1.07-110.246 -5.70139 -1
GRID 109 0.246 0.246 -5.70139 -1
GRID 110 0.246 1.672-28-6.00146 -1
GRID 111 -1.2-11 0.0 -6.00146 -1
GRID 112 -1.12-110.246 -6.00146 -1
GRID 113 0.246 0.246 -6.00146 -1
GRID 114 0.246 1.735-28-6.30154 -1
GRID 115 -1.26-110.0 -6.30154 -1
GRID 116 -1.18-110.246 -6.30154 -1
GRID 117 0.246 0.246 -6.30154 -1
GRID 118 0.246 1.83-28 -6.60161 -1
GRID 119 -1.32-110.0 -6.60161 -1
GRID 120 -1.23-110.246 -6.60161 -1
GRID 121 0.246 0.246 -6.60161 -1
GRID 122 0.246 1.893-28-6.90168 -1
GRID 123 -1.38-110.0 -6.90168 -1
GRID 124 -1.29-110.246 -6.90168 -1
GRID 125 0.246 0.246 -6.90168 -1
GRID 126 0.246 1.956-28-7.20176 -1
GRID 127 -1.44-110.0 -7.20176 -1
GRID 128 -1.35-110.246 -7.20176 -1
GRID 129 0.246 0.246 -7.20176 -1
GRID 130 0.246 2.019-28-7.50183 -1
GRID 131 -1.5-11 0.0 -7.50183 -1
GRID 132 -1.4-11 0.246 -7.50183 -1
GRID 133 0.246 0.246 -7.50183 -1
GRID 134 0.246 2.083-28-7.8019 -1
GRID 135 -1.55-110.0 -7.8019 -1
GRID 136 -1.46-110.246 -7.8019 -1
GRID 137 0.246 0.246 -7.8019 -1
GRID 138 0.246 2.146-28-8.10198 -1
GRID 139 -1.61-110.0 -8.10198 -1
GRID 140 -1.51-110.246 -8.10198 -1
GRID 141 0.246 0.246 -8.10198 -1
GRID 142 0.246 2.209-28-8.40205 -1
GRID 143 -1.67-110.0 -8.40205 -1
GRID 144 -1.57-110.246 -8.40205 -1
GRID 145 0.246 0.246 -8.40205 -1
GRID 146 0.246 2.272-28-8.70212 -1
GRID 147 -1.73-110.0 -8.70212 -1
GRID 148 -1.63-110.246 -8.70212 -1
GRID 149 0.246 0.246 -8.70212 -1
GRID 150 0.246 2.335-28-9.0022 -1
GRID 151 -1.79-110.0 -9.0022 -1
GRID 152 -1.68-110.246 -9.0022 -1
GRID 153 0.246 0.246 -9.0022 -1
GRID 154 0.246 2.398-28-9.30227 -1
GRID 155 -1.85-110.0 -9.30227 -1
GRID 156 -1.74-110.246 -9.30227 -1
GRID 157 0.246 0.246 -9.30227 -1
GRID 158 0.246 2.461-28-9.60234 -1
GRID 159 -1.91-110.0 -9.60234 -1
GRID 160 -1.79-110.246 -9.60234 -1
GRID 161 0.246 0.246 -9.60234 -1
GRID 162 0.246 2.524-28-9.90241 -1
GRID 163 -1.97-110.0 -9.90241 -1
GRID 164 -1.85-110.246 -9.90241 -1

1398 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 165 0.246 0.246 -9.90241 -1
GRID 166 0.246 2.556-28-10.2025 -1
GRID 167 -2.03-110.0 -10.2025 -1
GRID 168 -1.91-110.246 -10.2025 -1
GRID 169 0.246 0.246 -10.2025 -1
GRID 170 0.246 2.619-28-10.5026 -1
GRID 171 -2.09-110.0 -10.5026 -1
GRID 172 -1.96-110.246 -10.5026 -1
GRID 173 0.246 0.246 -10.5026 -1
GRID 174 0.246 2.682-28-10.8026 -1
GRID 175 -2.15-110.0 -10.8026 -1
GRID 176 -2.02-110.246 -10.8026 -1
GRID 177 0.246 0.246 -10.8026 -1
GRID 178 0.246 2.745-28-11.1027 -1
GRID 179 -2.21-110.0 -11.1027 -1
GRID 180 -2.07-110.246 -11.1027 -1
GRID 181 0.246 0.246 -11.1027 -1
GRID 182 0.246 2.777-28-11.4028 -1
GRID 183 -2.27-110.0 -11.4028 -1
GRID 184 -2.13-110.246 -11.4028 -1
GRID 185 0.246 0.246 -11.4028 -1
GRID 186 0.246 2.84-28 -11.7029 -1
GRID 187 -2.33-110.0 -11.7029 -1
GRID 188 -2.19-110.246 -11.7029 -1
GRID 189 0.246 0.246 -11.7029 -1
GRID 190 0.246 2.871-28-12.0029 -1
GRID 191 -2.39-110.0 -12.0029 -1
GRID 192 -2.24-110.246 -12.0029 -1
GRID 193 0.246 0.246 -12.0029 -1
GRID 194 0.246 2.935-28-12.303 -1
GRID 195 -2.45-110.0 -12.303 -1
GRID 196 -2.3-11 0.246 -12.303 -1
GRID 197 0.246 0.246 -12.303 -1
GRID 198 0.246 2.966-28-12.6031 -1
GRID 199 -2.51-110.0 -12.6031 -1
GRID 200 -2.35-110.246 -12.6031 -1
GRID 201 0.246 0.246 -12.6031 -1
GRID 522 0.246 2.935-28-12.903 -1
GRID 523 -7.36-110.0 -12.903 -1
GRID 524 -6.9-11 0.246 -12.903 -1
GRID 525 0.246 0.246 -12.903 -1
GRID 526 0.246 2.903-28-13.2031 -1
GRID 527 -7.42-110.0 -13.2031 -1
GRID 528 -6.95-110.246 -13.2031 -1
GRID 529 0.246 0.246 -13.2031 -1
GRID 530 0.246 2.84-28 -13.5032 -1
GRID 531 -7.48-110.0 -13.5032 -1
GRID 532 -7.01-110.246 -13.5032 -1
GRID 533 0.246 0.246 -13.5032 -1
GRID 534 0.246 2.777-28-13.8032 -1
GRID 535 -7.54-110.0 -13.8032 -1
GRID 536 -7.06-110.246 -13.8032 -1
GRID 537 0.246 0.246 -13.8032 -1
GRID 538 0.246 2.745-28-14.1033 -1
GRID 539 -7.6-11 0.0 -14.1033 -1
GRID 540 -7.12-110.246 -14.1033 -1
GRID 541 0.246 0.246 -14.1033 -1
GRID 542 0.246 2.682-28-14.4034 -1
GRID 543 -7.67-110.0 -14.4034 -1
GRID 544 -7.19-110.246 -14.4034 -1
GRID 545 0.246 0.246 -14.4034 -1
GRID 546 0.246 2.619-28-14.7034 -1
GRID 547 -7.73-110.0 -14.7034 -1
GRID 548 -7.24-110.246 -14.7034 -1
GRID 549 0.246 0.246 -14.7034 -1
GRID 550 0.246 2.587-28-15.0035 -1
GRID 551 -7.78-110.0 -15.0035 -1
GRID 552 -7.3-11 0.246 -15.0035 -1
GRID 553 0.246 0.246 -15.0035 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1399

Proprietary Information of Altair Engineering


GRID 554 0.246 2.524-28-15.3036 -1
GRID 555 -7.84-110.0 -15.3036 -1
GRID 556 -7.35-110.246 -15.3036 -1
GRID 557 0.246 0.246 -15.3036 -1
GRID 558 0.246 2.461-28-15.6037 -1
GRID 559 -7.9-11 0.0 -15.6037 -1
GRID 560 -7.41-110.246 -15.6037 -1
GRID 561 0.246 0.246 -15.6037 -1
GRID 562 0.246 2.398-28-15.9037 -1
GRID 563 -7.96-110.0 -15.9037 -1
GRID 564 -7.47-110.246 -15.9037 -1
GRID 565 0.246 0.246 -15.9037 -1
GRID 566 0.246 2.335-28-16.2038 -1
GRID 567 -8.02-110.0 -16.2038 -1
GRID 568 -7.52-110.246 -16.2038 -1
GRID 569 0.246 0.246 -16.2038 -1
GRID 570 0.246 2.272-28-16.5039 -1
GRID 571 -8.08-110.0 -16.5039 -1
GRID 572 -7.58-110.246 -16.5039 -1
GRID 573 0.246 0.246 -16.5039 -1
GRID 574 0.246 2.209-28-16.804 -1
GRID 575 -8.14-110.0 -16.804 -1
GRID 576 -7.63-110.246 -16.804 -1
GRID 577 0.246 0.246 -16.804 -1
GRID 578 0.246 2.146-28-17.104 -1
GRID 579 -8.2-11 0.0 -17.104 -1
GRID 580 -7.69-110.246 -17.104 -1
GRID 581 0.246 0.246 -17.104 -1
GRID 582 0.246 2.083-28-17.4041 -1
GRID 583 -8.26-110.0 -17.4041 -1
GRID 584 -7.75-110.246 -17.4041 -1
GRID 585 0.246 0.246 -17.4041 -1
GRID 586 0.246 2.019-28-17.7042 -1
GRID 587 -8.32-110.0 -17.7042 -1
GRID 588 -7.8-11 0.246 -17.7042 -1
GRID 589 0.246 0.246 -17.7042 -1
GRID 590 0.246 1.956-28-18.0042 -1
GRID 591 -8.38-110.0 -18.0042 -1
GRID 592 -7.86-110.246 -18.0042 -1
GRID 593 0.246 0.246 -18.0042 -1
GRID 594 0.246 1.893-28-18.3043 -1
GRID 595 -8.44-110.0 -18.3043 -1
GRID 596 -7.91-110.246 -18.3043 -1
GRID 597 0.246 0.246 -18.3043 -1
GRID 598 0.246 1.83-28 -18.6044 -1
GRID 599 -8.5-11 0.0 -18.6044 -1
GRID 600 -7.97-110.246 -18.6044 -1
GRID 601 0.246 0.246 -18.6044 -1
GRID 602 0.246 1.735-28-18.9045 -1
GRID 603 -8.56-110.0 -18.9045 -1
GRID 604 -8.03-110.246 -18.9045 -1
GRID 605 0.246 0.246 -18.9045 -1
GRID 606 0.246 1.672-28-19.2045 -1
GRID 607 -8.62-110.0 -19.2045 -1
GRID 608 -8.08-110.246 -19.2045 -1
GRID 609 0.246 0.246 -19.2045 -1
GRID 610 0.246 1.609-28-19.5046 -1
GRID 611 -8.68-110.0 -19.5046 -1
GRID 612 -8.14-110.246 -19.5046 -1
GRID 613 0.246 0.246 -19.5046 -1
GRID 614 0.246 1.515-28-19.8047 -1
GRID 615 -8.74-110.0 -19.8047 -1
GRID 616 -8.19-110.246 -19.8047 -1
GRID 617 0.246 0.246 -19.8047 -1
GRID 618 0.246 1.452-28-20.1048 -1
GRID 619 -8.8-11 0.0 -20.1048 -1
GRID 620 -8.25-110.246 -20.1048 -1
GRID 621 0.246 0.246 -20.1048 -1
GRID 622 0.246 1.388-28-20.4048 -1

1400 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 623 -8.86-110.0 -20.4048 -1
GRID 624 -8.31-110.246 -20.4048 -1
GRID 625 0.246 0.246 -20.4048 -1
GRID 626 0.246 1.294-28-20.7049 -1
GRID 627 -8.92-110.0 -20.7049 -1
GRID 628 -8.36-110.246 -20.7049 -1
GRID 629 0.246 0.246 -20.7049 -1
GRID 630 0.246 1.231-28-21.005 -1
GRID 631 -8.98-110.0 -21.005 -1
GRID 632 -8.42-110.246 -21.005 -1
GRID 633 0.246 0.246 -21.005 -1
GRID 634 0.246 1.136-28-21.3051 -1
GRID 635 -9.04-110.0 -21.3051 -1
GRID 636 -8.47-110.246 -21.3051 -1
GRID 637 0.246 0.246 -21.3051 -1
GRID 638 0.246 1.073-28-21.6051 -1
GRID 639 -9.1-11 0.0 -21.6051 -1
GRID 640 -8.53-110.246 -21.6051 -1
GRID 641 0.246 0.246 -21.6051 -1
GRID 642 0.246 9.782-29-21.9052 -1
GRID 643 -9.16-110.0 -21.9052 -1
GRID 644 -8.59-110.246 -21.9052 -1
GRID 645 0.246 0.246 -21.9052 -1
GRID 646 0.246 8.835-29-22.2053 -1
GRID 647 -9.22-110.0 -22.2053 -1
GRID 648 -8.64-110.246 -22.2053 -1
GRID 649 0.246 0.246 -22.2053 -1
GRID 650 0.246 8.204-29-22.5053 -1
GRID 651 -9.28-110.0 -22.5053 -1
GRID 652 -8.7-11 0.246 -22.5053 -1
GRID 653 0.246 0.246 -22.5053 -1
GRID 654 0.246 7.258-29-22.8054 -1
GRID 655 -9.34-110.0 -22.8054 -1
GRID 656 -8.75-110.246 -22.8054 -1
GRID 657 0.246 0.246 -22.8054 -1
GRID 658 0.246 6.311-29-23.1055 -1
GRID 659 -9.4-11 0.0 -23.1055 -1
GRID 660 -8.81-110.246 -23.1055 -1
GRID 661 0.246 0.246 -23.1055 -1
GRID 662 0.246 5.364-29-23.4056 -1
GRID 663 -9.46-110.0 -23.4056 -1
GRID 664 -8.87-110.246 -23.4056 -1
GRID 665 0.246 0.246 -23.4056 -1
GRID 666 0.246 4.733-29-23.7056 -1
GRID 667 -9.52-110.0 -23.7056 -1
GRID 668 -8.92-110.246 -23.7056 -1
GRID 669 0.246 0.246 -23.7056 -1
GRID 670 0.246 3.787-29-24.0057 -1
GRID 671 -9.58-110.0 -24.0057 -1
GRID 672 -8.98-110.246 -24.0057 -1
GRID 673 0.246 0.246 -24.0057 -1
GRID 674 0.246 2.84-29 -24.3058 -1
GRID 675 -9.64-110.0 -24.3058 -1
GRID 676 -9.04-110.246 -24.3058 -1
GRID 677 0.246 0.246 -24.3058 -1
GRID 678 0.246 1.893-29-24.6059 -1
GRID 679 -9.7-11 0.0 -24.6059 -1
GRID 680 -9.09-110.246 -24.6059 -1
GRID 681 0.246 0.246 -24.6059 -1
GRID 682 0.246 9.466-30-24.9059 -1
GRID 683 -9.76-110.0 -24.9059 -1
GRID 684 -9.15-110.246 -24.9059 -1
GRID 685 0.246 0.246 -24.9059 -1
GRID 686 0.246 4.151-12-25.206 -1
GRID 687 -9.82-112.767-12-25.206 -1
GRID 688 -9.16-110.246 -25.206 -1
GRID 689 0.246 0.246 -25.206 -1
GRID 690 0.492 4.323-13-.300073 -1
GRID 691 0.492 0.246 -.300073 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1401

Proprietary Information of Altair Engineering


GRID 692 0.492 1.621-13-.600146 -1
GRID 693 0.492 0.246 -.600146 -1
GRID 694 0.492 1.592-13-0.90022 -1
GRID 695 0.492 0.246 -0.90022 -1
GRID 696 0.492 2.009-13-1.20029 -1
GRID 697 0.492 0.246 -1.20029 -1
GRID 698 0.492 2.5-13 -1.50037 -1
GRID 699 0.492 0.246 -1.50037 -1
GRID 700 0.492 3.004-13-1.80044 -1
GRID 701 0.492 0.246 -1.80044 -1
GRID 702 0.492 3.51-13 -2.10051 -1
GRID 703 0.492 0.246 -2.10051 -1
GRID 704 0.492 4.016-13-2.40059 -1
GRID 705 0.492 0.246 -2.40059 -1
GRID 706 0.492 4.522-13-2.70066 -1
GRID 707 0.492 0.246 -2.70066 -1
GRID 708 0.492 5.028-13-3.00073 -1
GRID 709 0.492 0.246 -3.00073 -1
GRID 710 0.492 5.534-13-3.30081 -1
GRID 711 0.492 0.246 -3.30081 -1
GRID 712 0.492 6.041-13-3.60088 -1
GRID 713 0.492 0.246 -3.60088 -1
GRID 714 0.492 6.547-13-3.90095 -1
GRID 715 0.492 0.246 -3.90095 -1
GRID 716 0.492 7.053-13-4.20102 -1
GRID 717 0.492 0.246 -4.20102 -1
GRID 718 0.492 7.559-13-4.5011 -1
GRID 719 0.492 0.246 -4.5011 -1
GRID 720 0.492 8.066-13-4.80117 -1
GRID 721 0.492 0.246 -4.80117 -1
GRID 722 0.492 8.572-13-5.10124 -1
GRID 723 0.492 0.246 -5.10124 -1
GRID 724 0.492 9.078-13-5.40132 -1
GRID 725 0.492 0.246 -5.40132 -1
GRID 726 0.492 9.584-13-5.70139 -1
GRID 727 0.492 0.246 -5.70139 -1
GRID 728 0.492 1.009-12-6.00146 -1
GRID 729 0.492 0.246 -6.00146 -1
GRID 730 0.492 1.06-12 -6.30154 -1
GRID 731 0.492 0.246 -6.30154 -1
GRID 732 0.492 1.11-12 -6.60161 -1
GRID 733 0.492 0.246 -6.60161 -1
GRID 734 0.492 1.161-12-6.90168 -1
GRID 735 0.492 0.246 -6.90168 -1
GRID 736 0.492 1.212-12-7.20176 -1
GRID 737 0.492 0.246 -7.20176 -1
GRID 738 0.492 1.262-12-7.50183 -1
GRID 739 0.492 0.246 -7.50183 -1
GRID 740 0.492 1.313-12-7.8019 -1
GRID 741 0.492 0.246 -7.8019 -1
GRID 742 0.492 1.363-12-8.10198 -1
GRID 743 0.492 0.246 -8.10198 -1
GRID 744 0.492 1.414-12-8.40205 -1
GRID 745 0.492 0.246 -8.40205 -1
GRID 746 0.492 1.465-12-8.70212 -1
GRID 747 0.492 0.246 -8.70212 -1
GRID 748 0.492 1.515-12-9.0022 -1
GRID 749 0.492 0.246 -9.0022 -1
GRID 750 0.492 1.566-12-9.30227 -1
GRID 751 0.492 0.246 -9.30227 -1
GRID 752 0.492 1.616-12-9.60234 -1
GRID 753 0.492 0.246 -9.60234 -1
GRID 754 0.492 1.667-12-9.90242 -1
GRID 755 0.492 0.246 -9.90242 -1
GRID 756 0.492 1.718-12-10.2025 -1
GRID 757 0.492 0.246 -10.2025 -1
GRID 758 0.492 1.768-12-10.5026 -1
GRID 759 0.492 0.246 -10.5026 -1
GRID 760 0.492 1.819-12-10.8026 -1

1402 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 761 0.492 0.246 -10.8026 -1
GRID 762 0.492 1.87-12 -11.1027 -1
GRID 763 0.492 0.246 -11.1027 -1
GRID 764 0.492 1.92-12 -11.4028 -1
GRID 765 0.492 0.246 -11.4028 -1
GRID 766 0.492 1.971-12-11.7029 -1
GRID 767 0.492 0.246 -11.7029 -1
GRID 768 0.492 2.021-12-12.0029 -1
GRID 769 0.492 0.246 -12.0029 -1
GRID 770 0.492 2.072-12-12.303 -1
GRID 771 0.492 0.246 -12.303 -1
GRID 772 0.492 2.123-12-12.6031 -1
GRID 773 0.492 0.246 -12.6031 -1
GRID 934 0.492 6.223-12-12.903 -1
GRID 935 0.492 0.246 -12.903 -1
GRID 936 0.492 6.274-12-13.2031 -1
GRID 937 0.492 0.246 -13.2031 -1
GRID 938 0.492 6.324-12-13.5032 -1
GRID 939 0.492 0.246 -13.5032 -1
GRID 940 0.492 6.375-12-13.8032 -1
GRID 941 0.492 0.246 -13.8032 -1
GRID 942 0.492 6.425-12-14.1033 -1
GRID 943 0.492 0.246 -14.1033 -1
GRID 944 0.492 6.476-12-14.4034 -1
GRID 945 0.492 0.246 -14.4034 -1
GRID 946 0.492 6.527-12-14.7034 -1
GRID 947 0.492 0.246 -14.7034 -1
GRID 948 0.492 6.577-12-15.0035 -1
GRID 949 0.492 0.246 -15.0035 -1
GRID 950 0.492 6.628-12-15.3036 -1
GRID 951 0.492 0.246 -15.3036 -1
GRID 952 0.492 6.679-12-15.6037 -1
GRID 953 0.492 0.246 -15.6037 -1
GRID 954 0.492 6.729-12-15.9037 -1
GRID 955 0.492 0.246 -15.9037 -1
GRID 956 0.492 6.78-12 -16.2038 -1
GRID 957 0.492 0.246 -16.2038 -1
GRID 958 0.492 6.83-12 -16.5039 -1
GRID 959 0.492 0.246 -16.5039 -1
GRID 960 0.492 6.881-12-16.804 -1
GRID 961 0.492 0.246 -16.804 -1
GRID 962 0.492 6.932-12-17.104 -1
GRID 963 0.492 0.246 -17.104 -1
GRID 964 0.492 6.982-12-17.4041 -1
GRID 965 0.492 0.246 -17.4041 -1
GRID 966 0.492 7.033-12-17.7042 -1
GRID 967 0.492 0.246 -17.7042 -1
GRID 968 0.492 7.083-12-18.0042 -1
GRID 969 0.492 0.246 -18.0042 -1
GRID 970 0.492 7.134-12-18.3043 -1
GRID 971 0.492 0.246 -18.3043 -1
GRID 972 0.492 7.185-12-18.6044 -1
GRID 973 0.492 0.246 -18.6044 -1
GRID 974 0.492 7.235-12-18.9045 -1
GRID 975 0.492 0.246 -18.9045 -1
GRID 976 0.492 7.286-12-19.2045 -1
GRID 977 0.492 0.246 -19.2045 -1
GRID 978 0.492 7.337-12-19.5046 -1
GRID 979 0.492 0.246 -19.5046 -1
GRID 980 0.492 7.387-12-19.8047 -1
GRID 981 0.492 0.246 -19.8047 -1
GRID 982 0.492 7.438-12-20.1048 -1
GRID 983 0.492 0.246 -20.1048 -1
GRID 984 0.492 7.488-12-20.4048 -1
GRID 985 0.492 0.246 -20.4048 -1
GRID 986 0.492 7.539-12-20.7049 -1
GRID 987 0.492 0.246 -20.7049 -1
GRID 988 0.492 7.59-12 -21.005 -1
GRID 989 0.492 0.246 -21.005 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1403

Proprietary Information of Altair Engineering


GRID 990 0.492 7.64-12 -21.3051 -1
GRID 991 0.492 0.246 -21.3051 -1
GRID 992 0.492 7.691-12-21.6051 -1
GRID 993 0.492 0.246 -21.6051 -1
GRID 994 0.492 7.742-12-21.9052 -1
GRID 995 0.492 0.246 -21.9052 -1
GRID 996 0.492 7.792-12-22.2053 -1
GRID 997 0.492 0.246 -22.2053 -1
GRID 998 0.492 7.843-12-22.5053 -1
GRID 999 0.492 0.246 -22.5053 -1
GRID 1000 0.492 7.893-12-22.8054 -1
GRID 1001 0.492 0.246 -22.8054 -1
GRID 1002 0.492 7.944-12-23.1055 -1
GRID 1003 0.492 0.246 -23.1055 -1
GRID 1004 0.492 7.995-12-23.4056 -1
GRID 1005 0.492 0.246 -23.4056 -1
GRID 1006 0.492 8.045-12-23.7056 -1
GRID 1007 0.492 0.246 -23.7056 -1
GRID 1008 0.492 8.096-12-24.0057 -1
GRID 1009 0.492 0.246 -24.0057 -1
GRID 1010 0.492 8.146-12-24.3058 -1
GRID 1011 0.492 0.246 -24.3058 -1
GRID 1012 0.492 8.197-12-24.6059 -1
GRID 1013 0.492 0.246 -24.6059 -1
GRID 1014 0.492 8.248-12-24.9059 -1
GRID 1015 0.492 0.246 -24.9059 -1
GRID 1016 0.492 5.534-12-25.206 -1
GRID 1017 0.492 0.246 -25.206 -1
GRID 1018 -5.24-130.492 -.300073 -1
GRID 1019 0.246 0.492 -.300073 -1
GRID 1020 -1.05-120.492 -.600146 -1
GRID 1021 0.246 0.492 -.600146 -1
GRID 1022 -1.57-120.492 -.900219 -1
GRID 1023 0.246 0.492 -0.90022 -1
GRID 1024 -2.09-120.492 -1.20029 -1
GRID 1025 0.246 0.492 -1.20029 -1
GRID 1026 -2.63-120.492 -1.50037 -1
GRID 1027 0.246 0.492 -1.50037 -1
GRID 1028 -3.15-120.492 -1.80044 -1
GRID 1029 0.246 0.492 -1.80044 -1
GRID 1030 -3.67-120.492 -2.10051 -1
GRID 1031 0.246 0.492 -2.10051 -1
GRID 1032 -4.19-120.492 -2.40059 -1
GRID 1033 0.246 0.492 -2.40059 -1
GRID 1034 -4.72-120.492 -2.70066 -1
GRID 1035 0.246 0.492 -2.70066 -1
GRID 1036 -5.24-120.492 -3.00073 -1
GRID 1037 0.246 0.492 -3.00073 -1
GRID 1038 -5.76-120.492 -3.30081 -1
GRID 1039 0.246 0.492 -3.30081 -1
GRID 1040 -6.29-120.492 -3.60088 -1
GRID 1041 0.246 0.492 -3.60088 -1
GRID 1042 -6.81-120.492 -3.90095 -1
GRID 1043 0.246 0.492 -3.90095 -1
GRID 1044 -7.33-120.492 -4.20102 -1
GRID 1045 0.246 0.492 -4.20102 -1
GRID 1046 -7.87-120.492 -4.5011 -1
GRID 1047 0.246 0.492 -4.5011 -1
GRID 1048 -8.39-120.492 -4.80117 -1
GRID 1049 0.246 0.492 -4.80117 -1
GRID 1050 -8.91-120.492 -5.10124 -1
GRID 1051 0.246 0.492 -5.10124 -1
GRID 1052 -9.44-120.492 -5.40132 -1
GRID 1053 0.246 0.492 -5.40132 -1
GRID 1054 -9.96-120.492 -5.70139 -1
GRID 1055 0.246 0.492 -5.70139 -1
GRID 1056 -1.05-110.492 -6.00146 -1
GRID 1057 0.246 0.492 -6.00146 -1
GRID 1058 -1.1-11 0.492 -6.30154 -1

1404 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1059 0.246 0.492 -6.30154 -1
GRID 1060 -1.15-110.492 -6.60161 -1
GRID 1061 0.246 0.492 -6.60161 -1
GRID 1062 -1.2-11 0.492 -6.90168 -1
GRID 1063 0.246 0.492 -6.90168 -1
GRID 1064 -1.26-110.492 -7.20176 -1
GRID 1065 0.246 0.492 -7.20176 -1
GRID 1066 -1.31-110.492 -7.50183 -1
GRID 1067 0.246 0.492 -7.50183 -1
GRID 1068 -1.36-110.492 -7.8019 -1
GRID 1069 0.246 0.492 -7.8019 -1
GRID 1070 -1.41-110.492 -8.10198 -1
GRID 1071 0.246 0.492 -8.10198 -1
GRID 1072 -1.46-110.492 -8.40205 -1
GRID 1073 0.246 0.492 -8.40205 -1
GRID 1074 -1.52-110.492 -8.70212 -1
GRID 1075 0.246 0.492 -8.70212 -1
GRID 1076 -1.57-110.492 -9.0022 -1
GRID 1077 0.246 0.492 -9.0022 -1
GRID 1078 -1.62-110.492 -9.30227 -1
GRID 1079 0.246 0.492 -9.30227 -1
GRID 1080 -1.67-110.492 -9.60234 -1
GRID 1081 0.246 0.492 -9.60234 -1
GRID 1082 -1.73-110.492 -9.90241 -1
GRID 1083 0.246 0.492 -9.90241 -1
GRID 1084 -1.78-110.492 -10.2025 -1
GRID 1085 0.246 0.492 -10.2025 -1
GRID 1086 -1.83-110.492 -10.5026 -1
GRID 1087 0.246 0.492 -10.5026 -1
GRID 1088 -1.88-110.492 -10.8026 -1
GRID 1089 0.246 0.492 -10.8026 -1
GRID 1090 -1.94-110.492 -11.1027 -1
GRID 1091 0.246 0.492 -11.1027 -1
GRID 1092 -1.99-110.492 -11.4028 -1
GRID 1093 0.246 0.492 -11.4028 -1
GRID 1094 -2.04-110.492 -11.7029 -1
GRID 1095 0.246 0.492 -11.7029 -1
GRID 1096 -2.09-110.492 -12.0029 -1
GRID 1097 0.246 0.492 -12.0029 -1
GRID 1098 -2.14-110.492 -12.303 -1
GRID 1099 0.246 0.492 -12.303 -1
GRID 1100 -2.2-11 0.492 -12.6031 -1
GRID 1101 0.246 0.492 -12.6031 -1
GRID 1262 -6.43-110.492 -12.903 -1
GRID 1263 0.246 0.492 -12.903 -1
GRID 1264 -6.49-110.492 -13.2031 -1
GRID 1265 0.246 0.492 -13.2031 -1
GRID 1266 -6.54-110.492 -13.5032 -1
GRID 1267 0.246 0.492 -13.5032 -1
GRID 1268 -6.59-110.492 -13.8032 -1
GRID 1269 0.246 0.492 -13.8032 -1
GRID 1270 -6.64-110.492 -14.1033 -1
GRID 1271 0.246 0.492 -14.1033 -1
GRID 1272 -6.71-110.492 -14.4034 -1
GRID 1273 0.246 0.492 -14.4034 -1
GRID 1274 -6.76-110.492 -14.7034 -1
GRID 1275 0.246 0.492 -14.7034 -1
GRID 1276 -6.81-110.492 -15.0035 -1
GRID 1277 0.246 0.492 -15.0035 -1
GRID 1278 -6.86-110.492 -15.3036 -1
GRID 1279 0.246 0.492 -15.3036 -1
GRID 1280 -6.91-110.492 -15.6037 -1
GRID 1281 0.246 0.492 -15.6037 -1
GRID 1282 -6.97-110.492 -15.9037 -1
GRID 1283 0.246 0.492 -15.9037 -1
GRID 1284 -7.02-110.492 -16.2038 -1
GRID 1285 0.246 0.492 -16.2038 -1
GRID 1286 -7.07-110.492 -16.5039 -1
GRID 1287 0.246 0.492 -16.5039 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1405

Proprietary Information of Altair Engineering


GRID 1288 -7.12-110.492 -16.804 -1
GRID 1289 0.246 0.492 -16.804 -1
GRID 1290 -7.18-110.492 -17.104 -1
GRID 1291 0.246 0.492 -17.104 -1
GRID 1292 -7.23-110.492 -17.4041 -1
GRID 1293 0.246 0.492 -17.4041 -1
GRID 1294 -7.28-110.492 -17.7042 -1
GRID 1295 0.246 0.492 -17.7042 -1
GRID 1296 -7.33-110.492 -18.0042 -1
GRID 1297 0.246 0.492 -18.0042 -1
GRID 1298 -7.39-110.492 -18.3043 -1
GRID 1299 0.246 0.492 -18.3043 -1
GRID 1300 -7.44-110.492 -18.6044 -1
GRID 1301 0.246 0.492 -18.6044 -1
GRID 1302 -7.49-110.492 -18.9045 -1
GRID 1303 0.246 0.492 -18.9045 -1
GRID 1304 -7.54-110.492 -19.2045 -1
GRID 1305 0.246 0.492 -19.2045 -1
GRID 1306 -7.59-110.492 -19.5046 -1
GRID 1307 0.246 0.492 -19.5046 -1
GRID 1308 -7.65-110.492 -19.8047 -1
GRID 1309 0.246 0.492 -19.8047 -1
GRID 1310 -7.7-11 0.492 -20.1048 -1
GRID 1311 0.246 0.492 -20.1048 -1
GRID 1312 -7.75-110.492 -20.4048 -1
GRID 1313 0.246 0.492 -20.4048 -1
GRID 1314 -7.8-11 0.492 -20.7049 -1
GRID 1315 0.246 0.492 -20.7049 -1
GRID 1316 -7.86-110.492 -21.005 -1
GRID 1317 0.246 0.492 -21.005 -1
GRID 1318 -7.91-110.492 -21.3051 -1
GRID 1319 0.246 0.492 -21.3051 -1
GRID 1320 -7.96-110.492 -21.6051 -1
GRID 1321 0.246 0.492 -21.6051 -1
GRID 1322 -8.01-110.492 -21.9052 -1
GRID 1323 0.246 0.492 -21.9052 -1
GRID 1324 -8.07-110.492 -22.2053 -1
GRID 1325 0.246 0.492 -22.2053 -1
GRID 1326 -8.12-110.492 -22.5053 -1
GRID 1327 0.246 0.492 -22.5053 -1
GRID 1328 -8.17-110.492 -22.8054 -1
GRID 1329 0.246 0.492 -22.8054 -1
GRID 1330 -8.22-110.492 -23.1055 -1
GRID 1331 0.246 0.492 -23.1055 -1
GRID 1332 -8.27-110.492 -23.4056 -1
GRID 1333 0.246 0.492 -23.4056 -1
GRID 1334 -8.33-110.492 -23.7056 -1
GRID 1335 0.246 0.492 -23.7056 -1
GRID 1336 -8.38-110.492 -24.0057 -1
GRID 1337 0.246 0.492 -24.0057 -1
GRID 1338 -8.43-110.492 -24.3058 -1
GRID 1339 0.246 0.492 -24.3058 -1
GRID 1340 -8.48-110.492 -24.6059 -1
GRID 1341 0.246 0.492 -24.6059 -1
GRID 1342 -8.54-110.492 -24.9059 -1
GRID 1343 0.246 0.492 -24.9059 -1
GRID 1344 -8.59-110.492 -25.206 -1
GRID 1345 0.246 0.492 -25.206 -1
GRID 1346 0.492 0.492 -.300073 -1
GRID 1347 0.492 0.492 -.600146 -1
GRID 1348 0.492 0.492 -0.90022 -1
GRID 1349 0.492 0.492 -1.20029 -1
GRID 1350 0.492 0.492 -1.50037 -1
GRID 1351 0.492 0.492 -1.80044 -1
GRID 1352 0.492 0.492 -2.10051 -1
GRID 1353 0.492 0.492 -2.40059 -1
GRID 1354 0.492 0.492 -2.70066 -1
GRID 1355 0.492 0.492 -3.00073 -1
GRID 1356 0.492 0.492 -3.30081 -1

1406 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1357 0.492 0.492 -3.60088 -1
GRID 1358 0.492 0.492 -3.90095 -1
GRID 1359 0.492 0.492 -4.20102 -1
GRID 1360 0.492 0.492 -4.5011 -1
GRID 1361 0.492 0.492 -4.80117 -1
GRID 1362 0.492 0.492 -5.10124 -1
GRID 1363 0.492 0.492 -5.40132 -1
GRID 1364 0.492 0.492 -5.70139 -1
GRID 1365 0.492 0.492 -6.00146 -1
GRID 1366 0.492 0.492 -6.30154 -1
GRID 1367 0.492 0.492 -6.60161 -1
GRID 1368 0.492 0.492 -6.90168 -1
GRID 1369 0.492 0.492 -7.20176 -1
GRID 1370 0.492 0.492 -7.50183 -1
GRID 1371 0.492 0.492 -7.8019 -1
GRID 1372 0.492 0.492 -8.10198 -1
GRID 1373 0.492 0.492 -8.40205 -1
GRID 1374 0.492 0.492 -8.70212 -1
GRID 1375 0.492 0.492 -9.0022 -1
GRID 1376 0.492 0.492 -9.30227 -1
GRID 1377 0.492 0.492 -9.60234 -1
GRID 1378 0.492 0.492 -9.90242 -1
GRID 1379 0.492 0.492 -10.2025 -1
GRID 1380 0.492 0.492 -10.5026 -1
GRID 1381 0.492 0.492 -10.8026 -1
GRID 1382 0.492 0.492 -11.1027 -1
GRID 1383 0.492 0.492 -11.4028 -1
GRID 1384 0.492 0.492 -11.7029 -1
GRID 1385 0.492 0.492 -12.0029 -1
GRID 1386 0.492 0.492 -12.303 -1
GRID 1387 0.492 0.492 -12.6031 -1
GRID 1468 0.492 0.492 -12.903 -1
GRID 1469 0.492 0.492 -13.2031 -1
GRID 1470 0.492 0.492 -13.5032 -1
GRID 1471 0.492 0.492 -13.8032 -1
GRID 1472 0.492 0.492 -14.1033 -1
GRID 1473 0.492 0.492 -14.4034 -1
GRID 1474 0.492 0.492 -14.7034 -1
GRID 1475 0.492 0.492 -15.0035 -1
GRID 1476 0.492 0.492 -15.3036 -1
GRID 1477 0.492 0.492 -15.6037 -1
GRID 1478 0.492 0.492 -15.9037 -1
GRID 1479 0.492 0.492 -16.2038 -1
GRID 1480 0.492 0.492 -16.5039 -1
GRID 1481 0.492 0.492 -16.804 -1
GRID 1482 0.492 0.492 -17.104 -1
GRID 1483 0.492 0.492 -17.4041 -1
GRID 1484 0.492 0.492 -17.7042 -1
GRID 1485 0.492 0.492 -18.0042 -1
GRID 1486 0.492 0.492 -18.3043 -1
GRID 1487 0.492 0.492 -18.6044 -1
GRID 1488 0.492 0.492 -18.9045 -1
GRID 1489 0.492 0.492 -19.2045 -1
GRID 1490 0.492 0.492 -19.5046 -1
GRID 1491 0.492 0.492 -19.8047 -1
GRID 1492 0.492 0.492 -20.1048 -1
GRID 1493 0.492 0.492 -20.4048 -1
GRID 1494 0.492 0.492 -20.7049 -1
GRID 1495 0.492 0.492 -21.005 -1
GRID 1496 0.492 0.492 -21.3051 -1
GRID 1497 0.492 0.492 -21.6051 -1
GRID 1498 0.492 0.492 -21.9052 -1
GRID 1499 0.492 0.492 -22.2053 -1
GRID 1500 0.492 0.492 -22.5053 -1
GRID 1501 0.492 0.492 -22.8054 -1
GRID 1502 0.492 0.492 -23.1055 -1
GRID 1503 0.492 0.492 -23.4056 -1
GRID 1504 0.492 0.492 -23.7056 -1
GRID 1505 0.492 0.492 -24.0057 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1407

Proprietary Information of Altair Engineering


GRID 1506 0.492 0.492 -24.3058 -1
GRID 1507 0.492 0.492 -24.6059 -1
GRID 1508 0.492 0.492 -24.9059 -1
GRID 1509 0.492 0.492 -25.206 -1
GRID 1510 -0.246 0.0 -.300073 -1
GRID 1511 -0.492 8.522-26-.300073 -1
GRID 1512 -0.492 0.246 -.300073 -1
GRID 1513 -0.246 0.246 -.300073 -1
GRID 1514 -0.246 0.0 -.600146 -1
GRID 1515 -0.492 1.441-26-.600146 -1
GRID 1516 -0.492 0.246 -.600146 -1
GRID 1517 -0.246 0.246 -.600146 -1
GRID 1518 -0.246 0.0 -.900219 -1
GRID 1519 -0.492 2.685-27-.900219 -1
GRID 1520 -0.492 0.246 -.900219 -1
GRID 1521 -0.246 0.246 -.900219 -1
GRID 1522 -0.246 0.0 -1.20029 -1
GRID 1523 -0.492 8.709-28-1.20029 -1
GRID 1524 -0.492 0.246 -1.20029 -1
GRID 1525 -0.246 0.246 -1.20029 -1
GRID 1526 -0.246 0.0 -1.50037 -1
GRID 1527 -0.492 6.595-28-1.50037 -1
GRID 1528 -0.492 0.246 -1.50037 -1
GRID 1529 -0.246 0.246 -1.50037 -1
GRID 1530 -0.246 0.0 -1.80044 -1
GRID 1531 -0.492 7.258-28-1.80044 -1
GRID 1532 -0.492 0.246 -1.80044 -1
GRID 1533 -0.246 0.246 -1.80044 -1
GRID 1534 -0.246 0.0 -2.10051 -1
GRID 1535 -0.492 7.936-28-2.10051 -1
GRID 1536 -0.492 0.246 -2.10051 -1
GRID 1537 -0.246 0.246 -2.10051 -1
GRID 1538 -0.246 0.0 -2.40058 -1
GRID 1539 -0.492 8.993-28-2.40058 -1
GRID 1540 -0.492 0.246 -2.40058 -1
GRID 1541 -0.246 0.246 -2.40058 -1
GRID 1542 -0.246 0.0 -2.70066 -1
GRID 1543 -0.492 1.01-27 -2.70066 -1
GRID 1544 -0.492 0.246 -2.70066 -1
GRID 1545 -0.246 0.246 -2.70066 -1
GRID 1546 -0.246 0.0 -3.00073 -1
GRID 1547 -0.492 1.185-27-3.00073 -1
GRID 1548 -0.492 0.246 -3.00073 -1
GRID 1549 -0.246 0.246 -3.00073 -1
GRID 1550 -0.246 0.0 -3.3008 -1
GRID 1551 -0.492 1.313-27-3.3008 -1
GRID 1552 -0.492 0.246 -3.3008 -1
GRID 1553 -0.246 0.246 -3.3008 -1
GRID 1554 -0.246 0.0 -3.60088 -1
GRID 1555 -0.492 1.341-27-3.60088 -1
GRID 1556 -0.492 0.246 -3.60088 -1
GRID 1557 -0.246 0.246 -3.60088 -1
GRID 1558 -0.246 0.0 -3.90095 -1
GRID 1559 -0.492 1.36-27 -3.90095 -1
GRID 1560 -0.492 0.246 -3.90095 -1
GRID 1561 -0.246 0.246 -3.90095 -1
GRID 1562 -0.246 0.0 -4.20102 -1
GRID 1563 -0.492 1.447-27-4.20102 -1
GRID 1564 -0.492 0.246 -4.20102 -1
GRID 1565 -0.246 0.246 -4.20102 -1
GRID 1566 -0.246 0.0 -4.5011 -1
GRID 1567 -0.492 1.549-27-4.5011 -1
GRID 1568 -0.492 0.246 -4.5011 -1
GRID 1569 -0.246 0.246 -4.5011 -1
GRID 1570 -0.246 0.0 -4.80117 -1
GRID 1571 -0.492 1.775-27-4.80117 -1
GRID 1572 -0.492 0.246 -4.80117 -1
GRID 1573 -0.246 0.246 -4.80117 -1
GRID 1574 -0.246 0.0 -5.10124 -1

1408 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1575 -0.492 1.907-27-5.10124 -1
GRID 1576 -0.492 0.246 -5.10124 -1
GRID 1577 -0.246 0.246 -5.10124 -1
GRID 1578 -0.246 0.0 -5.40132 -1
GRID 1579 -0.492 2.023-27-5.40132 -1
GRID 1580 -0.492 0.246 -5.40132 -1
GRID 1581 -0.246 0.246 -5.40132 -1
GRID 1582 -0.246 0.0 -5.70139 -1
GRID 1583 -0.492 2.136-27-5.70139 -1
GRID 1584 -0.492 0.246 -5.70139 -1
GRID 1585 -0.246 0.246 -5.70139 -1
GRID 1586 -0.246 0.0 -6.00146 -1
GRID 1587 -0.492 2.248-27-6.00146 -1
GRID 1588 -0.492 0.246 -6.00146 -1
GRID 1589 -0.246 0.246 -6.00146 -1
GRID 1590 -0.246 0.0 -6.30154 -1
GRID 1591 -0.492 2.36-27 -6.30154 -1
GRID 1592 -0.492 0.246 -6.30154 -1
GRID 1593 -0.246 0.246 -6.30154 -1
GRID 1594 -0.246 0.0 -6.60161 -1
GRID 1595 -0.492 2.474-27-6.60161 -1
GRID 1596 -0.492 0.246 -6.60161 -1
GRID 1597 -0.246 0.246 -6.60161 -1
GRID 1598 -0.246 0.0 -6.90168 -1
GRID 1599 -0.492 2.551-27-6.90168 -1
GRID 1600 -0.492 0.246 -6.90168 -1
GRID 1601 -0.246 0.246 -6.90168 -1
GRID 1602 -0.246 0.0 -7.20176 -1
GRID 1603 -0.492 2.693-27-7.20176 -1
GRID 1604 -0.492 0.246 -7.20176 -1
GRID 1605 -0.246 0.246 -7.20176 -1
GRID 1606 -0.246 0.0 -7.50183 -1
GRID 1607 -0.492 2.965-27-7.50183 -1
GRID 1608 -0.492 0.246 -7.50183 -1
GRID 1609 -0.246 0.246 -7.50183 -1
GRID 1610 -0.246 0.0 -7.8019 -1
GRID 1611 -0.492 3.113-27-7.8019 -1
GRID 1612 -0.492 0.246 -7.8019 -1
GRID 1613 -0.246 0.246 -7.8019 -1
GRID 1614 -0.246 0.0 -8.10198 -1
GRID 1615 -0.492 3.067-27-8.10198 -1
GRID 1616 -0.492 0.246 -8.10198 -1
GRID 1617 -0.246 0.246 -8.10198 -1
GRID 1618 -0.246 0.0 -8.40205 -1
GRID 1619 -0.492 2.979-27-8.40205 -1
GRID 1620 -0.492 0.246 -8.40205 -1
GRID 1621 -0.246 0.246 -8.40205 -1
GRID 1622 -0.246 0.0 -8.70212 -1
GRID 1623 -0.492 3.233-27-8.70212 -1
GRID 1624 -0.492 0.246 -8.70212 -1
GRID 1625 -0.246 0.246 -8.70212 -1
GRID 1626 -0.246 0.0 -9.0022 -1
GRID 1627 -0.492 3.323-27-9.00219 -1
GRID 1628 -0.492 0.246 -9.00219 -1
GRID 1629 -0.246 0.246 -9.0022 -1
GRID 1630 -0.246 0.0 -9.30227 -1
GRID 1631 -0.492 3.67-27 -9.30227 -1
GRID 1632 -0.492 0.246 -9.30227 -1
GRID 1633 -0.246 0.246 -9.30227 -1
GRID 1634 -0.246 0.0 -9.60234 -1
GRID 1635 -0.492 3.58-27 -9.60234 -1
GRID 1636 -0.492 0.246 -9.60234 -1
GRID 1637 -0.246 0.246 -9.60234 -1
GRID 1638 -0.246 0.0 -9.90241 -1
GRID 1639 -0.492 3.454-27-9.90241 -1
GRID 1640 -0.492 0.246 -9.90241 -1
GRID 1641 -0.246 0.246 -9.90241 -1
GRID 1642 -0.246 0.0 -10.2025 -1
GRID 1643 -0.492 3.782-27-10.2025 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1409

Proprietary Information of Altair Engineering


GRID 1644 -0.492 0.246 -10.2025 -1
GRID 1645 -0.246 0.246 -10.2025 -1
GRID 1646 -0.246 0.0 -10.5026 -1
GRID 1647 -0.492 3.659-27-10.5026 -1
GRID 1648 -0.492 0.246 -10.5026 -1
GRID 1649 -0.246 0.246 -10.5026 -1
GRID 1650 -0.246 0.0 -10.8026 -1
GRID 1651 -0.492 4.003-27-10.8026 -1
GRID 1652 -0.492 0.246 -10.8026 -1
GRID 1653 -0.246 0.246 -10.8026 -1
GRID 1654 -0.246 0.0 -11.1027 -1
GRID 1655 -0.492 4.154-27-11.1027 -1
GRID 1656 -0.492 0.246 -11.1027 -1
GRID 1657 -0.246 0.246 -11.1027 -1
GRID 1658 -0.246 0.0 -11.4028 -1
GRID 1659 -0.492 4.274-27-11.4028 -1
GRID 1660 -0.492 0.246 -11.4028 -1
GRID 1661 -0.246 0.246 -11.4028 -1
GRID 1662 -0.246 0.0 -11.7029 -1
GRID 1663 -0.492 4.388-27-11.7028 -1
GRID 1664 -0.492 0.246 -11.7028 -1
GRID 1665 -0.246 0.246 -11.7029 -1
GRID 1666 -0.246 0.0 -12.0029 -1
GRID 1667 -0.492 4.5-27 -12.0029 -1
GRID 1668 -0.492 0.246 -12.0029 -1
GRID 1669 -0.246 0.246 -12.0029 -1
GRID 1670 -0.246 0.0 -12.303 -1
GRID 1671 -0.492 4.358-27-12.303 -1
GRID 1672 -0.492 0.246 -12.303 -1
GRID 1673 -0.246 0.246 -12.303 -1
GRID 1674 -0.246 0.0 -12.6031 -1
GRID 1675 -0.492 4.424-27-12.6031 -1
GRID 1676 -0.492 0.246 -12.6031 -1
GRID 1677 -0.246 0.246 -12.6031 -1
GRID 1998 -0.246 0.0 -12.903 -1
GRID 1999 -0.492 1.381-26-12.903 -1
GRID 2000 -0.492 0.246 -12.903 -1
GRID 2001 -0.246 0.246 -12.903 -1
GRID 2002 -0.246 0.0 -13.2031 -1
GRID 2003 -0.492 1.395-26-13.2031 -1
GRID 2004 -0.492 0.246 -13.2031 -1
GRID 2005 -0.246 0.246 -13.2031 -1
GRID 2006 -0.246 0.0 -13.5032 -1
GRID 2007 -0.492 1.407-26-13.5031 -1
GRID 2008 -0.492 0.246 -13.5031 -1
GRID 2009 -0.246 0.246 -13.5032 -1
GRID 2010 -0.246 0.0 -13.8032 -1
GRID 2011 -0.492 1.418-26-13.8032 -1
GRID 2012 -0.492 0.246 -13.8032 -1
GRID 2013 -0.246 0.246 -13.8032 -1
GRID 2014 -0.246 0.0 -14.1033 -1
GRID 2015 -0.492 1.429-26-14.1033 -1
GRID 2016 -0.492 0.246 -14.1033 -1
GRID 2017 -0.246 0.246 -14.1033 -1
GRID 2018 -0.246 0.0 -14.4034 -1
GRID 2019 -0.492 1.441-26-14.4034 -1
GRID 2020 -0.492 0.246 -14.4034 -1
GRID 2021 -0.246 0.246 -14.4034 -1
GRID 2022 -0.246 0.0 -14.7034 -1
GRID 2023 -0.492 1.452-26-14.7034 -1
GRID 2024 -0.492 0.246 -14.7034 -1
GRID 2025 -0.246 0.246 -14.7034 -1
GRID 2026 -0.246 0.0 -15.0035 -1
GRID 2027 -0.492 1.463-26-15.0035 -1
GRID 2028 -0.492 0.246 -15.0035 -1
GRID 2029 -0.246 0.246 -15.0035 -1
GRID 2030 -0.246 0.0 -15.3036 -1
GRID 2031 -0.492 1.454-26-15.3036 -1
GRID 2032 -0.492 0.246 -15.3036 -1

1410 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 2033 -0.246 0.246 -15.3036 -1
GRID 2034 -0.246 0.0 -15.6037 -1
GRID 2035 -0.492 1.38-26 -15.6037 -1
GRID 2036 -0.492 0.246 -15.6037 -1
GRID 2037 -0.246 0.246 -15.6037 -1
GRID 2038 -0.246 0.0 -15.9037 -1
GRID 2039 -0.492 1.479-26-15.9037 -1
GRID 2040 -0.492 0.246 -15.9037 -1
GRID 2041 -0.246 0.246 -15.9037 -1
GRID 2042 -0.246 0.0 -16.2038 -1
GRID 2043 -0.492 1.505-26-16.2038 -1
GRID 2044 -0.492 0.246 -16.2038 -1
GRID 2045 -0.246 0.246 -16.2038 -1
GRID 2046 -0.246 0.0 -16.5039 -1
GRID 2047 -0.492 1.519-26-16.5039 -1
GRID 2048 -0.492 0.246 -16.5039 -1
GRID 2049 -0.246 0.246 -16.5039 -1
GRID 2050 -0.246 0.0 -16.804 -1
GRID 2051 -0.492 1.531-26-16.804 -1
GRID 2052 -0.492 0.246 -16.804 -1
GRID 2053 -0.246 0.246 -16.804 -1
GRID 2054 -0.246 0.0 -17.104 -1
GRID 2055 -0.492 1.542-26-17.104 -1
GRID 2056 -0.492 0.246 -17.104 -1
GRID 2057 -0.246 0.246 -17.104 -1
GRID 2058 -0.246 0.0 -17.4041 -1
GRID 2059 -0.492 1.553-26-17.4041 -1
GRID 2060 -0.492 0.246 -17.4041 -1
GRID 2061 -0.246 0.246 -17.4041 -1
GRID 2062 -0.246 0.0 -17.7042 -1
GRID 2063 -0.492 1.564-26-17.7042 -1
GRID 2064 -0.492 0.246 -17.7042 -1
GRID 2065 -0.246 0.246 -17.7042 -1
GRID 2066 -0.246 0.0 -18.0042 -1
GRID 2067 -0.492 1.576-26-18.0042 -1
GRID 2068 -0.492 0.246 -18.0042 -1
GRID 2069 -0.246 0.246 -18.0042 -1
GRID 2070 -0.246 0.0 -18.3043 -1
GRID 2071 -0.492 1.477-26-18.3043 -1
GRID 2072 -0.492 0.246 -18.3043 -1
GRID 2073 -0.246 0.246 -18.3043 -1
GRID 2074 -0.246 0.0 -18.6044 -1
GRID 2075 -0.492 1.58-26 -18.6044 -1
GRID 2076 -0.492 0.246 -18.6044 -1
GRID 2077 -0.246 0.246 -18.6044 -1
GRID 2078 -0.246 0.0 -18.9045 -1
GRID 2079 -0.492 1.606-26-18.9045 -1
GRID 2080 -0.492 0.246 -18.9045 -1
GRID 2081 -0.246 0.246 -18.9045 -1
GRID 2082 -0.246 0.0 -19.2045 -1
GRID 2083 -0.492 1.62-26 -19.2045 -1
GRID 2084 -0.492 0.246 -19.2045 -1
GRID 2085 -0.246 0.246 -19.2045 -1
GRID 2086 -0.246 0.0 -19.5046 -1
GRID 2087 -0.492 1.632-26-19.5046 -1
GRID 2088 -0.492 0.246 -19.5046 -1
GRID 2089 -0.246 0.246 -19.5046 -1
GRID 2090 -0.246 0.0 -19.8047 -1
GRID 2091 -0.492 1.643-26-19.8047 -1
GRID 2092 -0.492 0.246 -19.8047 -1
GRID 2093 -0.246 0.246 -19.8047 -1
GRID 2094 -0.246 0.0 -20.1048 -1
GRID 2095 -0.492 1.655-26-20.1048 -1
GRID 2096 -0.492 0.246 -20.1048 -1
GRID 2097 -0.246 0.246 -20.1048 -1
GRID 2098 -0.246 0.0 -20.4048 -1
GRID 2099 -0.492 1.666-26-20.4048 -1
GRID 2100 -0.492 0.246 -20.4048 -1
GRID 2101 -0.246 0.246 -20.4048 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1411

Proprietary Information of Altair Engineering


GRID 2102 -0.246 0.0 -20.7049 -1
GRID 2103 -0.492 1.677-26-20.7049 -1
GRID 2104 -0.492 0.246 -20.7049 -1
GRID 2105 -0.246 0.246 -20.7049 -1
GRID 2106 -0.246 0.0 -21.005 -1
GRID 2107 -0.492 1.572-26-21.005 -1
GRID 2108 -0.492 0.246 -21.005 -1
GRID 2109 -0.246 0.246 -21.005 -1
GRID 2110 -0.246 0.0 -21.3051 -1
GRID 2111 -0.492 1.68-26 -21.3051 -1
GRID 2112 -0.492 0.246 -21.3051 -1
GRID 2113 -0.246 0.246 -21.3051 -1
GRID 2114 -0.246 0.0 -21.6051 -1
GRID 2115 -0.492 1.708-26-21.6051 -1
GRID 2116 -0.492 0.246 -21.6051 -1
GRID 2117 -0.246 0.246 -21.6051 -1
GRID 2118 -0.246 0.0 -21.9052 -1
GRID 2119 -0.492 1.722-26-21.9052 -1
GRID 2120 -0.492 0.246 -21.9052 -1
GRID 2121 -0.246 0.246 -21.9052 -1
GRID 2122 -0.246 0.0 -22.2053 -1
GRID 2123 -0.492 1.733-26-22.2053 -1
GRID 2124 -0.492 0.246 -22.2053 -1
GRID 2125 -0.246 0.246 -22.2053 -1
GRID 2126 -0.246 0.0 -22.5053 -1
GRID 2127 -0.492 1.745-26-22.5053 -1
GRID 2128 -0.492 0.246 -22.5053 -1
GRID 2129 -0.246 0.246 -22.5053 -1
GRID 2130 -0.246 0.0 -22.8054 -1
GRID 2131 -0.492 1.756-26-22.8054 -1
GRID 2132 -0.492 0.246 -22.8054 -1
GRID 2133 -0.246 0.246 -22.8054 -1
GRID 2134 -0.246 0.0 -23.1055 -1
GRID 2135 -0.492 1.767-26-23.1055 -1
GRID 2136 -0.492 0.246 -23.1055 -1
GRID 2137 -0.246 0.246 -23.1055 -1
GRID 2138 -0.246 0.0 -23.4056 -1
GRID 2139 -0.492 1.778-26-23.4056 -1
GRID 2140 -0.492 0.246 -23.4056 -1
GRID 2141 -0.246 0.246 -23.4056 -1
GRID 2142 -0.246 0.0 -23.7056 -1
GRID 2143 -0.492 1.666-26-23.7056 -1
GRID 2144 -0.492 0.246 -23.7056 -1
GRID 2145 -0.246 0.246 -23.7056 -1
GRID 2146 -0.246 0.0 -24.0057 -1
GRID 2147 -0.492 1.78-26 -24.0057 -1
GRID 2148 -0.492 0.246 -24.0057 -1
GRID 2149 -0.246 0.246 -24.0057 -1
GRID 2150 -0.246 0.0 -24.3058 -1
GRID 2151 -0.492 1.809-26-24.3058 -1
GRID 2152 -0.492 0.246 -24.3058 -1
GRID 2153 -0.246 0.246 -24.3058 -1
GRID 2154 -0.246 0.0 -24.6059 -1
GRID 2155 -0.492 1.823-26-24.6059 -1
GRID 2156 -0.492 0.246 -24.6059 -1
GRID 2157 -0.246 0.246 -24.6059 -1
GRID 2158 -0.246 0.0 -24.9059 -1
GRID 2159 -0.492 1.835-26-24.9059 -1
GRID 2160 -0.492 0.246 -24.9059 -1
GRID 2161 -0.246 0.246 -24.9059 -1
GRID 2162 -0.246 1.384-12-25.206 -1
GRID 2163 -0.492 1.272-26-25.206 -1
GRID 2164 -0.492 0.246 -25.206 -1
GRID 2165 -0.246 0.246 -25.206 -1
GRID 2166 -0.492 0.492 -.300073 -1
GRID 2167 -0.246 0.492 -.300073 -1
GRID 2168 -0.492 0.492 -.600146 -1
GRID 2169 -0.246 0.492 -.600146 -1
GRID 2170 -0.492 0.492 -.900219 -1

1412 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 2171 -0.246 0.492 -.900219 -1
GRID 2172 -0.492 0.492 -1.20029 -1
GRID 2173 -0.246 0.492 -1.20029 -1
GRID 2174 -0.492 0.492 -1.50037 -1
GRID 2175 -0.246 0.492 -1.50037 -1
GRID 2176 -0.492 0.492 -1.80044 -1
GRID 2177 -0.246 0.492 -1.80044 -1
GRID 2178 -0.492 0.492 -2.10051 -1
GRID 2179 -0.246 0.492 -2.10051 -1
GRID 2180 -0.492 0.492 -2.40058 -1
GRID 2181 -0.246 0.492 -2.40058 -1
GRID 2182 -0.492 0.492 -2.70066 -1
GRID 2183 -0.246 0.492 -2.70066 -1
GRID 2184 -0.492 0.492 -3.00073 -1
GRID 2185 -0.246 0.492 -3.00073 -1
GRID 2186 -0.492 0.492 -3.3008 -1
GRID 2187 -0.246 0.492 -3.3008 -1
GRID 2188 -0.492 0.492 -3.60088 -1
GRID 2189 -0.246 0.492 -3.60088 -1
GRID 2190 -0.492 0.492 -3.90095 -1
GRID 2191 -0.246 0.492 -3.90095 -1
GRID 2192 -0.492 0.492 -4.20102 -1
GRID 2193 -0.246 0.492 -4.20102 -1
GRID 2194 -0.492 0.492 -4.5011 -1
GRID 2195 -0.246 0.492 -4.5011 -1
GRID 2196 -0.492 0.492 -4.80117 -1
GRID 2197 -0.246 0.492 -4.80117 -1
GRID 2198 -0.492 0.492 -5.10124 -1
GRID 2199 -0.246 0.492 -5.10124 -1
GRID 2200 -0.492 0.492 -5.40132 -1
GRID 2201 -0.246 0.492 -5.40132 -1
GRID 2202 -0.492 0.492 -5.70139 -1
GRID 2203 -0.246 0.492 -5.70139 -1
GRID 2204 -0.492 0.492 -6.00146 -1
GRID 2205 -0.246 0.492 -6.00146 -1
GRID 2206 -0.492 0.492 -6.30154 -1
GRID 2207 -0.246 0.492 -6.30154 -1
GRID 2208 -0.492 0.492 -6.60161 -1
GRID 2209 -0.246 0.492 -6.60161 -1
GRID 2210 -0.492 0.492 -6.90168 -1
GRID 2211 -0.246 0.492 -6.90168 -1
GRID 2212 -0.492 0.492 -7.20176 -1
GRID 2213 -0.246 0.492 -7.20176 -1
GRID 2214 -0.492 0.492 -7.50183 -1
GRID 2215 -0.246 0.492 -7.50183 -1
GRID 2216 -0.492 0.492 -7.8019 -1
GRID 2217 -0.246 0.492 -7.8019 -1
GRID 2218 -0.492 0.492 -8.10198 -1
GRID 2219 -0.246 0.492 -8.10198 -1
GRID 2220 -0.492 0.492 -8.40205 -1
GRID 2221 -0.246 0.492 -8.40205 -1
GRID 2222 -0.492 0.492 -8.70212 -1
GRID 2223 -0.246 0.492 -8.70212 -1
GRID 2224 -0.492 0.492 -9.00219 -1
GRID 2225 -0.246 0.492 -9.0022 -1
GRID 2226 -0.492 0.492 -9.30227 -1
GRID 2227 -0.246 0.492 -9.30227 -1
GRID 2228 -0.492 0.492 -9.60234 -1
GRID 2229 -0.246 0.492 -9.60234 -1
GRID 2230 -0.492 0.492 -9.90241 -1
GRID 2231 -0.246 0.492 -9.90241 -1
GRID 2232 -0.492 0.492 -10.2025 -1
GRID 2233 -0.246 0.492 -10.2025 -1
GRID 2234 -0.492 0.492 -10.5026 -1
GRID 2235 -0.246 0.492 -10.5026 -1
GRID 2236 -0.492 0.492 -10.8026 -1
GRID 2237 -0.246 0.492 -10.8026 -1
GRID 2238 -0.492 0.492 -11.1027 -1
GRID 2239 -0.246 0.492 -11.1027 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1413

Proprietary Information of Altair Engineering


GRID 2240 -0.492 0.492 -11.4028 -1
GRID 2241 -0.246 0.492 -11.4028 -1
GRID 2242 -0.492 0.492 -11.7028 -1
GRID 2243 -0.246 0.492 -11.7029 -1
GRID 2244 -0.492 0.492 -12.0029 -1
GRID 2245 -0.246 0.492 -12.0029 -1
GRID 2246 -0.492 0.492 -12.303 -1
GRID 2247 -0.246 0.492 -12.303 -1
GRID 2248 -0.492 0.492 -12.6031 -1
GRID 2249 -0.246 0.492 -12.6031 -1
GRID 2410 -0.492 0.492 -12.903 -1
GRID 2411 -0.246 0.492 -12.903 -1
GRID 2412 -0.492 0.492 -13.2031 -1
GRID 2413 -0.246 0.492 -13.2031 -1
GRID 2414 -0.492 0.492 -13.5031 -1
GRID 2415 -0.246 0.492 -13.5032 -1
GRID 2416 -0.492 0.492 -13.8032 -1
GRID 2417 -0.246 0.492 -13.8032 -1
GRID 2418 -0.492 0.492 -14.1033 -1
GRID 2419 -0.246 0.492 -14.1033 -1
GRID 2420 -0.492 0.492 -14.4034 -1
GRID 2421 -0.246 0.492 -14.4034 -1
GRID 2422 -0.492 0.492 -14.7034 -1
GRID 2423 -0.246 0.492 -14.7034 -1
GRID 2424 -0.492 0.492 -15.0035 -1
GRID 2425 -0.246 0.492 -15.0035 -1
GRID 2426 -0.492 0.492 -15.3036 -1
GRID 2427 -0.246 0.492 -15.3036 -1
GRID 2428 -0.492 0.492 -15.6037 -1
GRID 2429 -0.246 0.492 -15.6037 -1
GRID 2430 -0.492 0.492 -15.9037 -1
GRID 2431 -0.246 0.492 -15.9037 -1
GRID 2432 -0.492 0.492 -16.2038 -1
GRID 2433 -0.246 0.492 -16.2038 -1
GRID 2434 -0.492 0.492 -16.5039 -1
GRID 2435 -0.246 0.492 -16.5039 -1
GRID 2436 -0.492 0.492 -16.804 -1
GRID 2437 -0.246 0.492 -16.804 -1
GRID 2438 -0.492 0.492 -17.104 -1
GRID 2439 -0.246 0.492 -17.104 -1
GRID 2440 -0.492 0.492 -17.4041 -1
GRID 2441 -0.246 0.492 -17.4041 -1
GRID 2442 -0.492 0.492 -17.7042 -1
GRID 2443 -0.246 0.492 -17.7042 -1
GRID 2444 -0.492 0.492 -18.0042 -1
GRID 2445 -0.246 0.492 -18.0042 -1
GRID 2446 -0.492 0.492 -18.3043 -1
GRID 2447 -0.246 0.492 -18.3043 -1
GRID 2448 -0.492 0.492 -18.6044 -1
GRID 2449 -0.246 0.492 -18.6044 -1
GRID 2450 -0.492 0.492 -18.9045 -1
GRID 2451 -0.246 0.492 -18.9045 -1
GRID 2452 -0.492 0.492 -19.2045 -1
GRID 2453 -0.246 0.492 -19.2045 -1
GRID 2454 -0.492 0.492 -19.5046 -1
GRID 2455 -0.246 0.492 -19.5046 -1
GRID 2456 -0.492 0.492 -19.8047 -1
GRID 2457 -0.246 0.492 -19.8047 -1
GRID 2458 -0.492 0.492 -20.1048 -1
GRID 2459 -0.246 0.492 -20.1048 -1
GRID 2460 -0.492 0.492 -20.4048 -1
GRID 2461 -0.246 0.492 -20.4048 -1
GRID 2462 -0.492 0.492 -20.7049 -1
GRID 2463 -0.246 0.492 -20.7049 -1
GRID 2464 -0.492 0.492 -21.005 -1
GRID 2465 -0.246 0.492 -21.005 -1
GRID 2466 -0.492 0.492 -21.3051 -1
GRID 2467 -0.246 0.492 -21.3051 -1
GRID 2468 -0.492 0.492 -21.6051 -1

1414 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 2469 -0.246 0.492 -21.6051 -1
GRID 2470 -0.492 0.492 -21.9052 -1
GRID 2471 -0.246 0.492 -21.9052 -1
GRID 2472 -0.492 0.492 -22.2053 -1
GRID 2473 -0.246 0.492 -22.2053 -1
GRID 2474 -0.492 0.492 -22.5053 -1
GRID 2475 -0.246 0.492 -22.5053 -1
GRID 2476 -0.492 0.492 -22.8054 -1
GRID 2477 -0.246 0.492 -22.8054 -1
GRID 2478 -0.492 0.492 -23.1055 -1
GRID 2479 -0.246 0.492 -23.1055 -1
GRID 2480 -0.492 0.492 -23.4056 -1
GRID 2481 -0.246 0.492 -23.4056 -1
GRID 2482 -0.492 0.492 -23.7056 -1
GRID 2483 -0.246 0.492 -23.7056 -1
GRID 2484 -0.492 0.492 -24.0057 -1
GRID 2485 -0.246 0.492 -24.0057 -1
GRID 2486 -0.492 0.492 -24.3058 -1
GRID 2487 -0.246 0.492 -24.3058 -1
GRID 2488 -0.492 0.492 -24.6059 -1
GRID 2489 -0.246 0.492 -24.6059 -1
GRID 2490 -0.492 0.492 -24.9059 -1
GRID 2491 -0.246 0.492 -24.9059 -1
GRID 2492 -0.492 0.492 -25.206 -1
GRID 2493 -0.246 0.492 -25.206 -1
GRID 2494 -0.246 -0.246 -.300073 -1
GRID 2495 -5.62-13-0.246 -.300073 -1
GRID 2496 -0.246 -0.246 -.600146 -1
GRID 2497 -1.12-12-0.246 -.600146 -1
GRID 2498 -0.246 -0.246 -.900219 -1
GRID 2499 -1.68-12-0.246 -.900219 -1
GRID 2500 -0.246 -0.246 -1.20029 -1
GRID 2501 -2.24-12-0.246 -1.20029 -1
GRID 2502 -0.246 -0.246 -1.50037 -1
GRID 2503 -2.81-12-0.246 -1.50037 -1
GRID 2504 -0.246 -0.246 -1.80044 -1
GRID 2505 -3.37-12-0.246 -1.80044 -1
GRID 2506 -0.246 -0.246 -2.10051 -1
GRID 2507 -3.93-12-0.246 -2.10051 -1
GRID 2508 -0.246 -0.246 -2.40058 -1
GRID 2509 -4.49-12-0.246 -2.40059 -1
GRID 2510 -0.246 -0.246 -2.70066 -1
GRID 2511 -5.06-12-0.246 -2.70066 -1
GRID 2512 -0.246 -0.246 -3.00073 -1
GRID 2513 -5.62-12-0.246 -3.00073 -1
GRID 2514 -0.246 -0.246 -3.3008 -1
GRID 2515 -6.18-12-0.246 -3.30081 -1
GRID 2516 -0.246 -0.246 -3.60088 -1
GRID 2517 -6.74-12-0.246 -3.60088 -1
GRID 2518 -0.246 -0.246 -3.90095 -1
GRID 2519 -7.3-12 -0.246 -3.90095 -1
GRID 2520 -0.246 -0.246 -4.20102 -1
GRID 2521 -7.86-12-0.246 -4.20102 -1
GRID 2522 -0.246 -0.246 -4.5011 -1
GRID 2523 -8.43-12-0.246 -4.5011 -1
GRID 2524 -0.246 -0.246 -4.80117 -1
GRID 2525 -8.99-12-0.246 -4.80117 -1
GRID 2526 -0.246 -0.246 -5.10124 -1
GRID 2527 -9.55-12-0.246 -5.10124 -1
GRID 2528 -0.246 -0.246 -5.40132 -1
GRID 2529 -1.01-11-0.246 -5.40132 -1
GRID 2530 -0.246 -0.246 -5.70139 -1
GRID 2531 -1.07-11-0.246 -5.70139 -1
GRID 2532 -0.246 -0.246 -6.00146 -1
GRID 2533 -1.12-11-0.246 -6.00146 -1
GRID 2534 -0.246 -0.246 -6.30154 -1
GRID 2535 -1.18-11-0.246 -6.30154 -1
GRID 2536 -0.246 -0.246 -6.60161 -1
GRID 2537 -1.23-11-0.246 -6.60161 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1415

Proprietary Information of Altair Engineering


GRID 2538 -0.246 -0.246 -6.90168 -1
GRID 2539 -1.29-11-0.246 -6.90168 -1
GRID 2540 -0.246 -0.246 -7.20176 -1
GRID 2541 -1.35-11-0.246 -7.20176 -1
GRID 2542 -0.246 -0.246 -7.50183 -1
GRID 2543 -1.4-11 -0.246 -7.50183 -1
GRID 2544 -0.246 -0.246 -7.8019 -1
GRID 2545 -1.46-11-0.246 -7.8019 -1
GRID 2546 -0.246 -0.246 -8.10198 -1
GRID 2547 -1.51-11-0.246 -8.10198 -1
GRID 2548 -0.246 -0.246 -8.40205 -1
GRID 2549 -1.57-11-0.246 -8.40205 -1
GRID 2550 -0.246 -0.246 -8.70212 -1
GRID 2551 -1.63-11-0.246 -8.70212 -1
GRID 2552 -0.246 -0.246 -9.0022 -1
GRID 2553 -1.68-11-0.246 -9.0022 -1
GRID 2554 -0.246 -0.246 -9.30227 -1
GRID 2555 -1.74-11-0.246 -9.30227 -1
GRID 2556 -0.246 -0.246 -9.60234 -1
GRID 2557 -1.79-11-0.246 -9.60234 -1
GRID 2558 -0.246 -0.246 -9.90241 -1
GRID 2559 -1.85-11-0.246 -9.90241 -1
GRID 2560 -0.246 -0.246 -10.2025 -1
GRID 2561 -1.91-11-0.246 -10.2025 -1
GRID 2562 -0.246 -0.246 -10.5026 -1
GRID 2563 -1.96-11-0.246 -10.5026 -1
GRID 2564 -0.246 -0.246 -10.8026 -1
GRID 2565 -2.02-11-0.246 -10.8026 -1
GRID 2566 -0.246 -0.246 -11.1027 -1
GRID 2567 -2.07-11-0.246 -11.1027 -1
GRID 2568 -0.246 -0.246 -11.4028 -1
GRID 2569 -2.13-11-0.246 -11.4028 -1
GRID 2570 -0.246 -0.246 -11.7029 -1
GRID 2571 -2.19-11-0.246 -11.7029 -1
GRID 2572 -0.246 -0.246 -12.0029 -1
GRID 2573 -2.24-11-0.246 -12.0029 -1
GRID 2574 -0.246 -0.246 -12.303 -1
GRID 2575 -2.3-11 -0.246 -12.303 -1
GRID 2576 -0.246 -0.246 -12.6031 -1
GRID 2577 -2.35-11-0.246 -12.6031 -1
GRID 2738 -0.246 -0.246 -12.903 -1
GRID 2739 -6.9-11 -0.246 -12.903 -1
GRID 2740 -0.246 -0.246 -13.2031 -1
GRID 2741 -6.95-11-0.246 -13.2031 -1
GRID 2742 -0.246 -0.246 -13.5032 -1
GRID 2743 -7.01-11-0.246 -13.5032 -1
GRID 2744 -0.246 -0.246 -13.8032 -1
GRID 2745 -7.06-11-0.246 -13.8032 -1
GRID 2746 -0.246 -0.246 -14.1033 -1
GRID 2747 -7.12-11-0.246 -14.1033 -1
GRID 2748 -0.246 -0.246 -14.4034 -1
GRID 2749 -7.19-11-0.246 -14.4034 -1
GRID 2750 -0.246 -0.246 -14.7034 -1
GRID 2751 -7.24-11-0.246 -14.7034 -1
GRID 2752 -0.246 -0.246 -15.0035 -1
GRID 2753 -7.3-11 -0.246 -15.0035 -1
GRID 2754 -0.246 -0.246 -15.3036 -1
GRID 2755 -7.35-11-0.246 -15.3036 -1
GRID 2756 -0.246 -0.246 -15.6037 -1
GRID 2757 -7.41-11-0.246 -15.6037 -1
GRID 2758 -0.246 -0.246 -15.9037 -1
GRID 2759 -7.47-11-0.246 -15.9037 -1
GRID 2760 -0.246 -0.246 -16.2038 -1
GRID 2761 -7.52-11-0.246 -16.2038 -1
GRID 2762 -0.246 -0.246 -16.5039 -1
GRID 2763 -7.58-11-0.246 -16.5039 -1
GRID 2764 -0.246 -0.246 -16.804 -1
GRID 2765 -7.63-11-0.246 -16.804 -1
GRID 2766 -0.246 -0.246 -17.104 -1

1416 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 2767 -7.69-11-0.246 -17.104 -1
GRID 2768 -0.246 -0.246 -17.4041 -1
GRID 2769 -7.75-11-0.246 -17.4041 -1
GRID 2770 -0.246 -0.246 -17.7042 -1
GRID 2771 -7.8-11 -0.246 -17.7042 -1
GRID 2772 -0.246 -0.246 -18.0042 -1
GRID 2773 -7.86-11-0.246 -18.0042 -1
GRID 2774 -0.246 -0.246 -18.3043 -1
GRID 2775 -7.91-11-0.246 -18.3043 -1
GRID 2776 -0.246 -0.246 -18.6044 -1
GRID 2777 -7.97-11-0.246 -18.6044 -1
GRID 2778 -0.246 -0.246 -18.9045 -1
GRID 2779 -8.03-11-0.246 -18.9045 -1
GRID 2780 -0.246 -0.246 -19.2045 -1
GRID 2781 -8.08-11-0.246 -19.2045 -1
GRID 2782 -0.246 -0.246 -19.5046 -1
GRID 2783 -8.14-11-0.246 -19.5046 -1
GRID 2784 -0.246 -0.246 -19.8047 -1
GRID 2785 -8.19-11-0.246 -19.8047 -1
GRID 2786 -0.246 -0.246 -20.1048 -1
GRID 2787 -8.25-11-0.246 -20.1048 -1
GRID 2788 -0.246 -0.246 -20.4048 -1
GRID 2789 -8.31-11-0.246 -20.4048 -1
GRID 2790 -0.246 -0.246 -20.7049 -1
GRID 2791 -8.36-11-0.246 -20.7049 -1
GRID 2792 -0.246 -0.246 -21.005 -1
GRID 2793 -8.42-11-0.246 -21.005 -1
GRID 2794 -0.246 -0.246 -21.3051 -1
GRID 2795 -8.47-11-0.246 -21.3051 -1
GRID 2796 -0.246 -0.246 -21.6051 -1
GRID 2797 -8.53-11-0.246 -21.6051 -1
GRID 2798 -0.246 -0.246 -21.9052 -1
GRID 2799 -8.59-11-0.246 -21.9052 -1
GRID 2800 -0.246 -0.246 -22.2053 -1
GRID 2801 -8.64-11-0.246 -22.2053 -1
GRID 2802 -0.246 -0.246 -22.5053 -1
GRID 2803 -8.7-11 -0.246 -22.5053 -1
GRID 2804 -0.246 -0.246 -22.8054 -1
GRID 2805 -8.75-11-0.246 -22.8054 -1
GRID 2806 -0.246 -0.246 -23.1055 -1
GRID 2807 -8.81-11-0.246 -23.1055 -1
GRID 2808 -0.246 -0.246 -23.4056 -1
GRID 2809 -8.87-11-0.246 -23.4056 -1
GRID 2810 -0.246 -0.246 -23.7056 -1
GRID 2811 -8.92-11-0.246 -23.7056 -1
GRID 2812 -0.246 -0.246 -24.0057 -1
GRID 2813 -8.98-11-0.246 -24.0057 -1
GRID 2814 -0.246 -0.246 -24.3058 -1
GRID 2815 -9.04-11-0.246 -24.3058 -1
GRID 2816 -0.246 -0.246 -24.6059 -1
GRID 2817 -9.09-11-0.246 -24.6059 -1
GRID 2818 -0.246 -0.246 -24.9059 -1
GRID 2819 -9.15-11-0.246 -24.9059 -1
GRID 2820 -0.246 -0.246 -25.206 -1
GRID 2821 -9.16-11-0.246 -25.206 -1
GRID 2822 -0.492 -0.246 -.300074 -1
GRID 2823 -0.492 -0.246 -.600146 -1
GRID 2824 -0.492 -0.246 -.900219 -1
GRID 2825 -0.492 -0.246 -1.20029 -1
GRID 2826 -0.492 -0.246 -1.50037 -1
GRID 2827 -0.492 -0.246 -1.80044 -1
GRID 2828 -0.492 -0.246 -2.10051 -1
GRID 2829 -0.492 -0.246 -2.40058 -1
GRID 2830 -0.492 -0.246 -2.70066 -1
GRID 2831 -0.492 -0.246 -3.00073 -1
GRID 2832 -0.492 -0.246 -3.3008 -1
GRID 2833 -0.492 -0.246 -3.60088 -1
GRID 2834 -0.492 -0.246 -3.90095 -1
GRID 2835 -0.492 -0.246 -4.20102 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1417

Proprietary Information of Altair Engineering


GRID 2836 -0.492 -0.246 -4.5011 -1
GRID 2837 -0.492 -0.246 -4.80117 -1
GRID 2838 -0.492 -0.246 -5.10124 -1
GRID 2839 -0.492 -0.246 -5.40132 -1
GRID 2840 -0.492 -0.246 -5.70139 -1
GRID 2841 -0.492 -0.246 -6.00146 -1
GRID 2842 -0.492 -0.246 -6.30154 -1
GRID 2843 -0.492 -0.246 -6.60161 -1
GRID 2844 -0.492 -0.246 -6.90168 -1
GRID 2845 -0.492 -0.246 -7.20176 -1
GRID 2846 -0.492 -0.246 -7.50183 -1
GRID 2847 -0.492 -0.246 -7.8019 -1
GRID 2848 -0.492 -0.246 -8.10198 -1
GRID 2849 -0.492 -0.246 -8.40205 -1
GRID 2850 -0.492 -0.246 -8.70212 -1
GRID 2851 -0.492 -0.246 -9.00219 -1
GRID 2852 -0.492 -0.246 -9.30227 -1
GRID 2853 -0.492 -0.246 -9.60234 -1
GRID 2854 -0.492 -0.246 -9.90241 -1
GRID 2855 -0.492 -0.246 -10.2025 -1
GRID 2856 -0.492 -0.246 -10.5026 -1
GRID 2857 -0.492 -0.246 -10.8026 -1
GRID 2858 -0.492 -0.246 -11.1027 -1
GRID 2859 -0.492 -0.246 -11.4028 -1
GRID 2860 -0.492 -0.246 -11.7028 -1
GRID 2861 -0.492 -0.246 -12.0029 -1
GRID 2862 -0.492 -0.246 -12.303 -1
GRID 2863 -0.492 -0.246 -12.6031 -1
GRID 2944 -0.492 -0.246 -12.903 -1
GRID 2945 -0.492 -0.246 -13.2031 -1
GRID 2946 -0.492 -0.246 -13.5031 -1
GRID 2947 -0.492 -0.246 -13.8032 -1
GRID 2948 -0.492 -0.246 -14.1033 -1
GRID 2949 -0.492 -0.246 -14.4034 -1
GRID 2950 -0.492 -0.246 -14.7034 -1
GRID 2951 -0.492 -0.246 -15.0035 -1
GRID 2952 -0.492 -0.246 -15.3036 -1
GRID 2953 -0.492 -0.246 -15.6037 -1
GRID 2954 -0.492 -0.246 -15.9037 -1
GRID 2955 -0.492 -0.246 -16.2038 -1
GRID 2956 -0.492 -0.246 -16.5039 -1
GRID 2957 -0.492 -0.246 -16.804 -1
GRID 2958 -0.492 -0.246 -17.104 -1
GRID 2959 -0.492 -0.246 -17.4041 -1
GRID 2960 -0.492 -0.246 -17.7042 -1
GRID 2961 -0.492 -0.246 -18.0042 -1
GRID 2962 -0.492 -0.246 -18.3043 -1
GRID 2963 -0.492 -0.246 -18.6044 -1
GRID 2964 -0.492 -0.246 -18.9045 -1
GRID 2965 -0.492 -0.246 -19.2045 -1
GRID 2966 -0.492 -0.246 -19.5046 -1
GRID 2967 -0.492 -0.246 -19.8047 -1
GRID 2968 -0.492 -0.246 -20.1048 -1
GRID 2969 -0.492 -0.246 -20.4048 -1
GRID 2970 -0.492 -0.246 -20.7049 -1
GRID 2971 -0.492 -0.246 -21.005 -1
GRID 2972 -0.492 -0.246 -21.3051 -1
GRID 2973 -0.492 -0.246 -21.6051 -1
GRID 2974 -0.492 -0.246 -21.9052 -1
GRID 2975 -0.492 -0.246 -22.2053 -1
GRID 2976 -0.492 -0.246 -22.5053 -1
GRID 2977 -0.492 -0.246 -22.8054 -1
GRID 2978 -0.492 -0.246 -23.1055 -1
GRID 2979 -0.492 -0.246 -23.4056 -1
GRID 2980 -0.492 -0.246 -23.7056 -1
GRID 2981 -0.492 -0.246 -24.0057 -1
GRID 2982 -0.492 -0.246 -24.3058 -1
GRID 2983 -0.492 -0.246 -24.6059 -1
GRID 2984 -0.492 -0.246 -24.9059 -1

1418 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 2985 -0.492 -0.246 -25.206 -1
GRID 2986 -0.246 -0.492 -.300073 -1
GRID 2987 -5.24-13-0.492 -.300073 -1
GRID 2988 -0.246 -0.492 -.600146 -1
GRID 2989 -1.05-12-0.492 -.600146 -1
GRID 2990 -0.246 -0.492 -.900219 -1
GRID 2991 -1.57-12-0.492 -.900219 -1
GRID 2992 -0.246 -0.492 -1.20029 -1
GRID 2993 -2.09-12-0.492 -1.20029 -1
GRID 2994 -0.246 -0.492 -1.50037 -1
GRID 2995 -2.63-12-0.492 -1.50037 -1
GRID 2996 -0.246 -0.492 -1.80044 -1
GRID 2997 -3.15-12-0.492 -1.80044 -1
GRID 2998 -0.246 -0.492 -2.10051 -1
GRID 2999 -3.67-12-0.492 -2.10051 -1
GRID 3000 -0.246 -0.492 -2.40058 -1
GRID 3001 -4.19-12-0.492 -2.40059 -1
GRID 3002 -0.246 -0.492 -2.70066 -1
GRID 3003 -4.72-12-0.492 -2.70066 -1
GRID 3004 -0.246 -0.492 -3.00073 -1
GRID 3005 -5.24-12-0.492 -3.00073 -1
GRID 3006 -0.246 -0.492 -3.3008 -1
GRID 3007 -5.76-12-0.492 -3.30081 -1
GRID 3008 -0.246 -0.492 -3.60088 -1
GRID 3009 -6.29-12-0.492 -3.60088 -1
GRID 3010 -0.246 -0.492 -3.90095 -1
GRID 3011 -6.81-12-0.492 -3.90095 -1
GRID 3012 -0.246 -0.492 -4.20102 -1
GRID 3013 -7.33-12-0.492 -4.20102 -1
GRID 3014 -0.246 -0.492 -4.5011 -1
GRID 3015 -7.87-12-0.492 -4.5011 -1
GRID 3016 -0.246 -0.492 -4.80117 -1
GRID 3017 -8.39-12-0.492 -4.80117 -1
GRID 3018 -0.246 -0.492 -5.10124 -1
GRID 3019 -8.91-12-0.492 -5.10124 -1
GRID 3020 -0.246 -0.492 -5.40132 -1
GRID 3021 -9.44-12-0.492 -5.40132 -1
GRID 3022 -0.246 -0.492 -5.70139 -1
GRID 3023 -9.96-12-0.492 -5.70139 -1
GRID 3024 -0.246 -0.492 -6.00146 -1
GRID 3025 -1.05-11-0.492 -6.00146 -1
GRID 3026 -0.246 -0.492 -6.30154 -1
GRID 3027 -1.1-11 -0.492 -6.30154 -1
GRID 3028 -0.246 -0.492 -6.60161 -1
GRID 3029 -1.15-11-0.492 -6.60161 -1
GRID 3030 -0.246 -0.492 -6.90168 -1
GRID 3031 -1.2-11 -0.492 -6.90168 -1
GRID 3032 -0.246 -0.492 -7.20176 -1
GRID 3033 -1.26-11-0.492 -7.20176 -1
GRID 3034 -0.246 -0.492 -7.50183 -1
GRID 3035 -1.31-11-0.492 -7.50183 -1
GRID 3036 -0.246 -0.492 -7.8019 -1
GRID 3037 -1.36-11-0.492 -7.8019 -1
GRID 3038 -0.246 -0.492 -8.10198 -1
GRID 3039 -1.41-11-0.492 -8.10198 -1
GRID 3040 -0.246 -0.492 -8.40205 -1
GRID 3041 -1.46-11-0.492 -8.40205 -1
GRID 3042 -0.246 -0.492 -8.70212 -1
GRID 3043 -1.52-11-0.492 -8.70212 -1
GRID 3044 -0.246 -0.492 -9.0022 -1
GRID 3045 -1.57-11-0.492 -9.0022 -1
GRID 3046 -0.246 -0.492 -9.30227 -1
GRID 3047 -1.62-11-0.492 -9.30227 -1
GRID 3048 -0.246 -0.492 -9.60234 -1
GRID 3049 -1.67-11-0.492 -9.60234 -1
GRID 3050 -0.246 -0.492 -9.90241 -1
GRID 3051 -1.73-11-0.492 -9.90241 -1
GRID 3052 -0.246 -0.492 -10.2025 -1
GRID 3053 -1.78-11-0.492 -10.2025 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1419

Proprietary Information of Altair Engineering


GRID 3054 -0.246 -0.492 -10.5026 -1
GRID 3055 -1.83-11-0.492 -10.5026 -1
GRID 3056 -0.246 -0.492 -10.8026 -1
GRID 3057 -1.88-11-0.492 -10.8026 -1
GRID 3058 -0.246 -0.492 -11.1027 -1
GRID 3059 -1.94-11-0.492 -11.1027 -1
GRID 3060 -0.246 -0.492 -11.4028 -1
GRID 3061 -1.99-11-0.492 -11.4028 -1
GRID 3062 -0.246 -0.492 -11.7029 -1
GRID 3063 -2.04-11-0.492 -11.7029 -1
GRID 3064 -0.246 -0.492 -12.0029 -1
GRID 3065 -2.09-11-0.492 -12.0029 -1
GRID 3066 -0.246 -0.492 -12.303 -1
GRID 3067 -2.14-11-0.492 -12.303 -1
GRID 3068 -0.246 -0.492 -12.6031 -1
GRID 3069 -2.2-11 -0.492 -12.6031 -1
GRID 3230 -0.246 -0.492 -12.903 -1
GRID 3231 -6.43-11-0.492 -12.903 -1
GRID 3232 -0.246 -0.492 -13.2031 -1
GRID 3233 -6.49-11-0.492 -13.2031 -1
GRID 3234 -0.246 -0.492 -13.5032 -1
GRID 3235 -6.54-11-0.492 -13.5032 -1
GRID 3236 -0.246 -0.492 -13.8032 -1
GRID 3237 -6.59-11-0.492 -13.8032 -1
GRID 3238 -0.246 -0.492 -14.1033 -1
GRID 3239 -6.64-11-0.492 -14.1033 -1
GRID 3240 -0.246 -0.492 -14.4034 -1
GRID 3241 -6.71-11-0.492 -14.4034 -1
GRID 3242 -0.246 -0.492 -14.7034 -1
GRID 3243 -6.76-11-0.492 -14.7034 -1
GRID 3244 -0.246 -0.492 -15.0035 -1
GRID 3245 -6.81-11-0.492 -15.0035 -1
GRID 3246 -0.246 -0.492 -15.3036 -1
GRID 3247 -6.86-11-0.492 -15.3036 -1
GRID 3248 -0.246 -0.492 -15.6037 -1
GRID 3249 -6.91-11-0.492 -15.6037 -1
GRID 3250 -0.246 -0.492 -15.9037 -1
GRID 3251 -6.97-11-0.492 -15.9037 -1
GRID 3252 -0.246 -0.492 -16.2038 -1
GRID 3253 -7.02-11-0.492 -16.2038 -1
GRID 3254 -0.246 -0.492 -16.5039 -1
GRID 3255 -7.07-11-0.492 -16.5039 -1
GRID 3256 -0.246 -0.492 -16.804 -1
GRID 3257 -7.12-11-0.492 -16.804 -1
GRID 3258 -0.246 -0.492 -17.104 -1
GRID 3259 -7.18-11-0.492 -17.104 -1
GRID 3260 -0.246 -0.492 -17.4041 -1
GRID 3261 -7.23-11-0.492 -17.4041 -1
GRID 3262 -0.246 -0.492 -17.7042 -1
GRID 3263 -7.28-11-0.492 -17.7042 -1
GRID 3264 -0.246 -0.492 -18.0042 -1
GRID 3265 -7.33-11-0.492 -18.0042 -1
GRID 3266 -0.246 -0.492 -18.3043 -1
GRID 3267 -7.39-11-0.492 -18.3043 -1
GRID 3268 -0.246 -0.492 -18.6044 -1
GRID 3269 -7.44-11-0.492 -18.6044 -1
GRID 3270 -0.246 -0.492 -18.9045 -1
GRID 3271 -7.49-11-0.492 -18.9045 -1
GRID 3272 -0.246 -0.492 -19.2045 -1
GRID 3273 -7.54-11-0.492 -19.2045 -1
GRID 3274 -0.246 -0.492 -19.5046 -1
GRID 3275 -7.59-11-0.492 -19.5046 -1
GRID 3276 -0.246 -0.492 -19.8047 -1
GRID 3277 -7.65-11-0.492 -19.8047 -1
GRID 3278 -0.246 -0.492 -20.1048 -1
GRID 3279 -7.7-11 -0.492 -20.1048 -1
GRID 3280 -0.246 -0.492 -20.4048 -1
GRID 3281 -7.75-11-0.492 -20.4048 -1
GRID 3282 -0.246 -0.492 -20.7049 -1

1420 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 3283 -7.8-11 -0.492 -20.7049 -1
GRID 3284 -0.246 -0.492 -21.005 -1
GRID 3285 -7.86-11-0.492 -21.005 -1
GRID 3286 -0.246 -0.492 -21.3051 -1
GRID 3287 -7.91-11-0.492 -21.3051 -1
GRID 3288 -0.246 -0.492 -21.6051 -1
GRID 3289 -7.96-11-0.492 -21.6051 -1
GRID 3290 -0.246 -0.492 -21.9052 -1
GRID 3291 -8.01-11-0.492 -21.9052 -1
GRID 3292 -0.246 -0.492 -22.2053 -1
GRID 3293 -8.07-11-0.492 -22.2053 -1
GRID 3294 -0.246 -0.492 -22.5053 -1
GRID 3295 -8.12-11-0.492 -22.5053 -1
GRID 3296 -0.246 -0.492 -22.8054 -1
GRID 3297 -8.17-11-0.492 -22.8054 -1
GRID 3298 -0.246 -0.492 -23.1055 -1
GRID 3299 -8.22-11-0.492 -23.1055 -1
GRID 3300 -0.246 -0.492 -23.4056 -1
GRID 3301 -8.27-11-0.492 -23.4056 -1
GRID 3302 -0.246 -0.492 -23.7056 -1
GRID 3303 -8.33-11-0.492 -23.7056 -1
GRID 3304 -0.246 -0.492 -24.0057 -1
GRID 3305 -8.38-11-0.492 -24.0057 -1
GRID 3306 -0.246 -0.492 -24.3058 -1
GRID 3307 -8.43-11-0.492 -24.3058 -1
GRID 3308 -0.246 -0.492 -24.6059 -1
GRID 3309 -8.48-11-0.492 -24.6059 -1
GRID 3310 -0.246 -0.492 -24.9059 -1
GRID 3311 -8.54-11-0.492 -24.9059 -1
GRID 3312 -0.246 -0.492 -25.206 -1
GRID 3313 -8.59-11-0.492 -25.206 -1
GRID 3314 -0.492 -0.492 -.300073 -1
GRID 3315 -0.492 -0.492 -.600146 -1
GRID 3316 -0.492 -0.492 -.900219 -1
GRID 3317 -0.492 -0.492 -1.20029 -1
GRID 3318 -0.492 -0.492 -1.50037 -1
GRID 3319 -0.492 -0.492 -1.80044 -1
GRID 3320 -0.492 -0.492 -2.10051 -1
GRID 3321 -0.492 -0.492 -2.40058 -1
GRID 3322 -0.492 -0.492 -2.70066 -1
GRID 3323 -0.492 -0.492 -3.00073 -1
GRID 3324 -0.492 -0.492 -3.3008 -1
GRID 3325 -0.492 -0.492 -3.60088 -1
GRID 3326 -0.492 -0.492 -3.90095 -1
GRID 3327 -0.492 -0.492 -4.20102 -1
GRID 3328 -0.492 -0.492 -4.5011 -1
GRID 3329 -0.492 -0.492 -4.80117 -1
GRID 3330 -0.492 -0.492 -5.10124 -1
GRID 3331 -0.492 -0.492 -5.40132 -1
GRID 3332 -0.492 -0.492 -5.70139 -1
GRID 3333 -0.492 -0.492 -6.00146 -1
GRID 3334 -0.492 -0.492 -6.30154 -1
GRID 3335 -0.492 -0.492 -6.60161 -1
GRID 3336 -0.492 -0.492 -6.90168 -1
GRID 3337 -0.492 -0.492 -7.20176 -1
GRID 3338 -0.492 -0.492 -7.50183 -1
GRID 3339 -0.492 -0.492 -7.8019 -1
GRID 3340 -0.492 -0.492 -8.10198 -1
GRID 3341 -0.492 -0.492 -8.40205 -1
GRID 3342 -0.492 -0.492 -8.70212 -1
GRID 3343 -0.492 -0.492 -9.00219 -1
GRID 3344 -0.492 -0.492 -9.30227 -1
GRID 3345 -0.492 -0.492 -9.60234 -1
GRID 3346 -0.492 -0.492 -9.90241 -1
GRID 3347 -0.492 -0.492 -10.2025 -1
GRID 3348 -0.492 -0.492 -10.5026 -1
GRID 3349 -0.492 -0.492 -10.8026 -1
GRID 3350 -0.492 -0.492 -11.1027 -1
GRID 3351 -0.492 -0.492 -11.4028 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1421

Proprietary Information of Altair Engineering


GRID 3352 -0.492 -0.492 -11.7028 -1
GRID 3353 -0.492 -0.492 -12.0029 -1
GRID 3354 -0.492 -0.492 -12.303 -1
GRID 3355 -0.492 -0.492 -12.6031 -1
GRID 3436 -0.492 -0.492 -12.903 -1
GRID 3437 -0.492 -0.492 -13.2031 -1
GRID 3438 -0.492 -0.492 -13.5031 -1
GRID 3439 -0.492 -0.492 -13.8032 -1
GRID 3440 -0.492 -0.492 -14.1033 -1
GRID 3441 -0.492 -0.492 -14.4034 -1
GRID 3442 -0.492 -0.492 -14.7034 -1
GRID 3443 -0.492 -0.492 -15.0035 -1
GRID 3444 -0.492 -0.492 -15.3036 -1
GRID 3445 -0.492 -0.492 -15.6037 -1
GRID 3446 -0.492 -0.492 -15.9037 -1
GRID 3447 -0.492 -0.492 -16.2038 -1
GRID 3448 -0.492 -0.492 -16.5039 -1
GRID 3449 -0.492 -0.492 -16.804 -1
GRID 3450 -0.492 -0.492 -17.104 -1
GRID 3451 -0.492 -0.492 -17.4041 -1
GRID 3452 -0.492 -0.492 -17.7042 -1
GRID 3453 -0.492 -0.492 -18.0042 -1
GRID 3454 -0.492 -0.492 -18.3043 -1
GRID 3455 -0.492 -0.492 -18.6044 -1
GRID 3456 -0.492 -0.492 -18.9045 -1
GRID 3457 -0.492 -0.492 -19.2045 -1
GRID 3458 -0.492 -0.492 -19.5046 -1
GRID 3459 -0.492 -0.492 -19.8047 -1
GRID 3460 -0.492 -0.492 -20.1048 -1
GRID 3461 -0.492 -0.492 -20.4048 -1
GRID 3462 -0.492 -0.492 -20.7049 -1
GRID 3463 -0.492 -0.492 -21.005 -1
GRID 3464 -0.492 -0.492 -21.3051 -1
GRID 3465 -0.492 -0.492 -21.6051 -1
GRID 3466 -0.492 -0.492 -21.9052 -1
GRID 3467 -0.492 -0.492 -22.2053 -1
GRID 3468 -0.492 -0.492 -22.5053 -1
GRID 3469 -0.492 -0.492 -22.8054 -1
GRID 3470 -0.492 -0.492 -23.1055 -1
GRID 3471 -0.492 -0.492 -23.4056 -1
GRID 3472 -0.492 -0.492 -23.7056 -1
GRID 3473 -0.492 -0.492 -24.0057 -1
GRID 3474 -0.492 -0.492 -24.3058 -1
GRID 3475 -0.492 -0.492 -24.6059 -1
GRID 3476 -0.492 -0.492 -24.9059 -1
GRID 3477 -0.492 -0.492 -25.206 -1
GRID 3478 0.246 -0.246 -.300073 -1
GRID 3479 0.492 -0.246 -.300074 -1
GRID 3480 0.246 -0.246 -.600146 -1
GRID 3481 0.492 -0.246 -.600146 -1
GRID 3482 0.246 -0.246 -0.90022 -1
GRID 3483 0.492 -0.246 -0.90022 -1
GRID 3484 0.246 -0.246 -1.20029 -1
GRID 3485 0.492 -0.246 -1.20029 -1
GRID 3486 0.246 -0.246 -1.50037 -1
GRID 3487 0.492 -0.246 -1.50037 -1
GRID 3488 0.246 -0.246 -1.80044 -1
GRID 3489 0.492 -0.246 -1.80044 -1
GRID 3490 0.246 -0.246 -2.10051 -1
GRID 3491 0.492 -0.246 -2.10051 -1
GRID 3492 0.246 -0.246 -2.40059 -1
GRID 3493 0.492 -0.246 -2.40059 -1
GRID 3494 0.246 -0.246 -2.70066 -1
GRID 3495 0.492 -0.246 -2.70066 -1
GRID 3496 0.246 -0.246 -3.00073 -1
GRID 3497 0.492 -0.246 -3.00073 -1
GRID 3498 0.246 -0.246 -3.30081 -1
GRID 3499 0.492 -0.246 -3.30081 -1
GRID 3500 0.246 -0.246 -3.60088 -1

1422 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 3501 0.492 -0.246 -3.60088 -1
GRID 3502 0.246 -0.246 -3.90095 -1
GRID 3503 0.492 -0.246 -3.90095 -1
GRID 3504 0.246 -0.246 -4.20102 -1
GRID 3505 0.492 -0.246 -4.20102 -1
GRID 3506 0.246 -0.246 -4.5011 -1
GRID 3507 0.492 -0.246 -4.5011 -1
GRID 3508 0.246 -0.246 -4.80117 -1
GRID 3509 0.492 -0.246 -4.80117 -1
GRID 3510 0.246 -0.246 -5.10124 -1
GRID 3511 0.492 -0.246 -5.10124 -1
GRID 3512 0.246 -0.246 -5.40132 -1
GRID 3513 0.492 -0.246 -5.40132 -1
GRID 3514 0.246 -0.246 -5.70139 -1
GRID 3515 0.492 -0.246 -5.70139 -1
GRID 3516 0.246 -0.246 -6.00146 -1
GRID 3517 0.492 -0.246 -6.00146 -1
GRID 3518 0.246 -0.246 -6.30154 -1
GRID 3519 0.492 -0.246 -6.30154 -1
GRID 3520 0.246 -0.246 -6.60161 -1
GRID 3521 0.492 -0.246 -6.60161 -1
GRID 3522 0.246 -0.246 -6.90168 -1
GRID 3523 0.492 -0.246 -6.90168 -1
GRID 3524 0.246 -0.246 -7.20176 -1
GRID 3525 0.492 -0.246 -7.20176 -1
GRID 3526 0.246 -0.246 -7.50183 -1
GRID 3527 0.492 -0.246 -7.50183 -1
GRID 3528 0.246 -0.246 -7.8019 -1
GRID 3529 0.492 -0.246 -7.8019 -1
GRID 3530 0.246 -0.246 -8.10198 -1
GRID 3531 0.492 -0.246 -8.10198 -1
GRID 3532 0.246 -0.246 -8.40205 -1
GRID 3533 0.492 -0.246 -8.40205 -1
GRID 3534 0.246 -0.246 -8.70212 -1
GRID 3535 0.492 -0.246 -8.70212 -1
GRID 3536 0.246 -0.246 -9.0022 -1
GRID 3537 0.492 -0.246 -9.0022 -1
GRID 3538 0.246 -0.246 -9.30227 -1
GRID 3539 0.492 -0.246 -9.30227 -1
GRID 3540 0.246 -0.246 -9.60234 -1
GRID 3541 0.492 -0.246 -9.60234 -1
GRID 3542 0.246 -0.246 -9.90241 -1
GRID 3543 0.492 -0.246 -9.90242 -1
GRID 3544 0.246 -0.246 -10.2025 -1
GRID 3545 0.492 -0.246 -10.2025 -1
GRID 3546 0.246 -0.246 -10.5026 -1
GRID 3547 0.492 -0.246 -10.5026 -1
GRID 3548 0.246 -0.246 -10.8026 -1
GRID 3549 0.492 -0.246 -10.8026 -1
GRID 3550 0.246 -0.246 -11.1027 -1
GRID 3551 0.492 -0.246 -11.1027 -1
GRID 3552 0.246 -0.246 -11.4028 -1
GRID 3553 0.492 -0.246 -11.4028 -1
GRID 3554 0.246 -0.246 -11.7029 -1
GRID 3555 0.492 -0.246 -11.7029 -1
GRID 3556 0.246 -0.246 -12.0029 -1
GRID 3557 0.492 -0.246 -12.0029 -1
GRID 3558 0.246 -0.246 -12.303 -1
GRID 3559 0.492 -0.246 -12.303 -1
GRID 3560 0.246 -0.246 -12.6031 -1
GRID 3561 0.492 -0.246 -12.6031 -1
GRID 3722 0.246 -0.246 -12.903 -1
GRID 3723 0.492 -0.246 -12.903 -1
GRID 3724 0.246 -0.246 -13.2031 -1
GRID 3725 0.492 -0.246 -13.2031 -1
GRID 3726 0.246 -0.246 -13.5032 -1
GRID 3727 0.492 -0.246 -13.5032 -1
GRID 3728 0.246 -0.246 -13.8032 -1
GRID 3729 0.492 -0.246 -13.8032 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1423

Proprietary Information of Altair Engineering


GRID 3730 0.246 -0.246 -14.1033 -1
GRID 3731 0.492 -0.246 -14.1033 -1
GRID 3732 0.246 -0.246 -14.4034 -1
GRID 3733 0.492 -0.246 -14.4034 -1
GRID 3734 0.246 -0.246 -14.7034 -1
GRID 3735 0.492 -0.246 -14.7034 -1
GRID 3736 0.246 -0.246 -15.0035 -1
GRID 3737 0.492 -0.246 -15.0035 -1
GRID 3738 0.246 -0.246 -15.3036 -1
GRID 3739 0.492 -0.246 -15.3036 -1
GRID 3740 0.246 -0.246 -15.6037 -1
GRID 3741 0.492 -0.246 -15.6037 -1
GRID 3742 0.246 -0.246 -15.9037 -1
GRID 3743 0.492 -0.246 -15.9037 -1
GRID 3744 0.246 -0.246 -16.2038 -1
GRID 3745 0.492 -0.246 -16.2038 -1
GRID 3746 0.246 -0.246 -16.5039 -1
GRID 3747 0.492 -0.246 -16.5039 -1
GRID 3748 0.246 -0.246 -16.804 -1
GRID 3749 0.492 -0.246 -16.804 -1
GRID 3750 0.246 -0.246 -17.104 -1
GRID 3751 0.492 -0.246 -17.104 -1
GRID 3752 0.246 -0.246 -17.4041 -1
GRID 3753 0.492 -0.246 -17.4041 -1
GRID 3754 0.246 -0.246 -17.7042 -1
GRID 3755 0.492 -0.246 -17.7042 -1
GRID 3756 0.246 -0.246 -18.0042 -1
GRID 3757 0.492 -0.246 -18.0042 -1
GRID 3758 0.246 -0.246 -18.3043 -1
GRID 3759 0.492 -0.246 -18.3043 -1
GRID 3760 0.246 -0.246 -18.6044 -1
GRID 3761 0.492 -0.246 -18.6044 -1
GRID 3762 0.246 -0.246 -18.9045 -1
GRID 3763 0.492 -0.246 -18.9045 -1
GRID 3764 0.246 -0.246 -19.2045 -1
GRID 3765 0.492 -0.246 -19.2045 -1
GRID 3766 0.246 -0.246 -19.5046 -1
GRID 3767 0.492 -0.246 -19.5046 -1
GRID 3768 0.246 -0.246 -19.8047 -1
GRID 3769 0.492 -0.246 -19.8047 -1
GRID 3770 0.246 -0.246 -20.1048 -1
GRID 3771 0.492 -0.246 -20.1048 -1
GRID 3772 0.246 -0.246 -20.4048 -1
GRID 3773 0.492 -0.246 -20.4048 -1
GRID 3774 0.246 -0.246 -20.7049 -1
GRID 3775 0.492 -0.246 -20.7049 -1
GRID 3776 0.246 -0.246 -21.005 -1
GRID 3777 0.492 -0.246 -21.005 -1
GRID 3778 0.246 -0.246 -21.3051 -1
GRID 3779 0.492 -0.246 -21.3051 -1
GRID 3780 0.246 -0.246 -21.6051 -1
GRID 3781 0.492 -0.246 -21.6051 -1
GRID 3782 0.246 -0.246 -21.9052 -1
GRID 3783 0.492 -0.246 -21.9052 -1
GRID 3784 0.246 -0.246 -22.2053 -1
GRID 3785 0.492 -0.246 -22.2053 -1
GRID 3786 0.246 -0.246 -22.5053 -1
GRID 3787 0.492 -0.246 -22.5053 -1
GRID 3788 0.246 -0.246 -22.8054 -1
GRID 3789 0.492 -0.246 -22.8054 -1
GRID 3790 0.246 -0.246 -23.1055 -1
GRID 3791 0.492 -0.246 -23.1055 -1
GRID 3792 0.246 -0.246 -23.4056 -1
GRID 3793 0.492 -0.246 -23.4056 -1
GRID 3794 0.246 -0.246 -23.7056 -1
GRID 3795 0.492 -0.246 -23.7056 -1
GRID 3796 0.246 -0.246 -24.0057 -1
GRID 3797 0.492 -0.246 -24.0057 -1
GRID 3798 0.246 -0.246 -24.3058 -1

1424 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 3799 0.492 -0.246 -24.3058 -1
GRID 3800 0.246 -0.246 -24.6059 -1
GRID 3801 0.492 -0.246 -24.6059 -1
GRID 3802 0.246 -0.246 -24.9059 -1
GRID 3803 0.492 -0.246 -24.9059 -1
GRID 3804 0.246 -0.246 -25.206 -1
GRID 3805 0.492 -0.246 -25.206 -1
GRID 3806 0.246 -0.492 -.300073 -1
GRID 3807 0.492 -0.492 -.300074 -1
GRID 3808 0.246 -0.492 -.600146 -1
GRID 3809 0.492 -0.492 -.600146 -1
GRID 3810 0.246 -0.492 -0.90022 -1
GRID 3811 0.492 -0.492 -0.90022 -1
GRID 3812 0.246 -0.492 -1.20029 -1
GRID 3813 0.492 -0.492 -1.20029 -1
GRID 3814 0.246 -0.492 -1.50037 -1
GRID 3815 0.492 -0.492 -1.50037 -1
GRID 3816 0.246 -0.492 -1.80044 -1
GRID 3817 0.492 -0.492 -1.80044 -1
GRID 3818 0.246 -0.492 -2.10051 -1
GRID 3819 0.492 -0.492 -2.10051 -1
GRID 3820 0.246 -0.492 -2.40059 -1
GRID 3821 0.492 -0.492 -2.40059 -1
GRID 3822 0.246 -0.492 -2.70066 -1
GRID 3823 0.492 -0.492 -2.70066 -1
GRID 3824 0.246 -0.492 -3.00073 -1
GRID 3825 0.492 -0.492 -3.00073 -1
GRID 3826 0.246 -0.492 -3.30081 -1
GRID 3827 0.492 -0.492 -3.30081 -1
GRID 3828 0.246 -0.492 -3.60088 -1
GRID 3829 0.492 -0.492 -3.60088 -1
GRID 3830 0.246 -0.492 -3.90095 -1
GRID 3831 0.492 -0.492 -3.90095 -1
GRID 3832 0.246 -0.492 -4.20102 -1
GRID 3833 0.492 -0.492 -4.20102 -1
GRID 3834 0.246 -0.492 -4.5011 -1
GRID 3835 0.492 -0.492 -4.5011 -1
GRID 3836 0.246 -0.492 -4.80117 -1
GRID 3837 0.492 -0.492 -4.80117 -1
GRID 3838 0.246 -0.492 -5.10124 -1
GRID 3839 0.492 -0.492 -5.10124 -1
GRID 3840 0.246 -0.492 -5.40132 -1
GRID 3841 0.492 -0.492 -5.40132 -1
GRID 3842 0.246 -0.492 -5.70139 -1
GRID 3843 0.492 -0.492 -5.70139 -1
GRID 3844 0.246 -0.492 -6.00146 -1
GRID 3845 0.492 -0.492 -6.00146 -1
GRID 3846 0.246 -0.492 -6.30154 -1
GRID 3847 0.492 -0.492 -6.30154 -1
GRID 3848 0.246 -0.492 -6.60161 -1
GRID 3849 0.492 -0.492 -6.60161 -1
GRID 3850 0.246 -0.492 -6.90168 -1
GRID 3851 0.492 -0.492 -6.90168 -1
GRID 3852 0.246 -0.492 -7.20176 -1
GRID 3853 0.492 -0.492 -7.20176 -1
GRID 3854 0.246 -0.492 -7.50183 -1
GRID 3855 0.492 -0.492 -7.50183 -1
GRID 3856 0.246 -0.492 -7.8019 -1
GRID 3857 0.492 -0.492 -7.8019 -1
GRID 3858 0.246 -0.492 -8.10198 -1
GRID 3859 0.492 -0.492 -8.10198 -1
GRID 3860 0.246 -0.492 -8.40205 -1
GRID 3861 0.492 -0.492 -8.40205 -1
GRID 3862 0.246 -0.492 -8.70212 -1
GRID 3863 0.492 -0.492 -8.70212 -1
GRID 3864 0.246 -0.492 -9.0022 -1
GRID 3865 0.492 -0.492 -9.0022 -1
GRID 3866 0.246 -0.492 -9.30227 -1
GRID 3867 0.492 -0.492 -9.30227 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1425

Proprietary Information of Altair Engineering


GRID 3868 0.246 -0.492 -9.60234 -1
GRID 3869 0.492 -0.492 -9.60234 -1
GRID 3870 0.246 -0.492 -9.90241 -1
GRID 3871 0.492 -0.492 -9.90242 -1
GRID 3872 0.246 -0.492 -10.2025 -1
GRID 3873 0.492 -0.492 -10.2025 -1
GRID 3874 0.246 -0.492 -10.5026 -1
GRID 3875 0.492 -0.492 -10.5026 -1
GRID 3876 0.246 -0.492 -10.8026 -1
GRID 3877 0.492 -0.492 -10.8026 -1
GRID 3878 0.246 -0.492 -11.1027 -1
GRID 3879 0.492 -0.492 -11.1027 -1
GRID 3880 0.246 -0.492 -11.4028 -1
GRID 3881 0.492 -0.492 -11.4028 -1
GRID 3882 0.246 -0.492 -11.7029 -1
GRID 3883 0.492 -0.492 -11.7029 -1
GRID 3884 0.246 -0.492 -12.0029 -1
GRID 3885 0.492 -0.492 -12.0029 -1
GRID 3886 0.246 -0.492 -12.303 -1
GRID 3887 0.492 -0.492 -12.303 -1
GRID 3888 0.246 -0.492 -12.6031 -1
GRID 3889 0.492 -0.492 -12.6031 -1
GRID 4050 0.246 -0.492 -12.903 -1
GRID 4051 0.492 -0.492 -12.903 -1
GRID 4052 0.246 -0.492 -13.2031 -1
GRID 4053 0.492 -0.492 -13.2031 -1
GRID 4054 0.246 -0.492 -13.5032 -1
GRID 4055 0.492 -0.492 -13.5032 -1
GRID 4056 0.246 -0.492 -13.8032 -1
GRID 4057 0.492 -0.492 -13.8032 -1
GRID 4058 0.246 -0.492 -14.1033 -1
GRID 4059 0.492 -0.492 -14.1033 -1
GRID 4060 0.246 -0.492 -14.4034 -1
GRID 4061 0.492 -0.492 -14.4034 -1
GRID 4062 0.246 -0.492 -14.7034 -1
GRID 4063 0.492 -0.492 -14.7034 -1
GRID 4064 0.246 -0.492 -15.0035 -1
GRID 4065 0.492 -0.492 -15.0035 -1
GRID 4066 0.246 -0.492 -15.3036 -1
GRID 4067 0.492 -0.492 -15.3036 -1
GRID 4068 0.246 -0.492 -15.6037 -1
GRID 4069 0.492 -0.492 -15.6037 -1
GRID 4070 0.246 -0.492 -15.9037 -1
GRID 4071 0.492 -0.492 -15.9037 -1
GRID 4072 0.246 -0.492 -16.2038 -1
GRID 4073 0.492 -0.492 -16.2038 -1
GRID 4074 0.246 -0.492 -16.5039 -1
GRID 4075 0.492 -0.492 -16.5039 -1
GRID 4076 0.246 -0.492 -16.804 -1
GRID 4077 0.492 -0.492 -16.804 -1
GRID 4078 0.246 -0.492 -17.104 -1
GRID 4079 0.492 -0.492 -17.104 -1
GRID 4080 0.246 -0.492 -17.4041 -1
GRID 4081 0.492 -0.492 -17.4041 -1
GRID 4082 0.246 -0.492 -17.7042 -1
GRID 4083 0.492 -0.492 -17.7042 -1
GRID 4084 0.246 -0.492 -18.0042 -1
GRID 4085 0.492 -0.492 -18.0042 -1
GRID 4086 0.246 -0.492 -18.3043 -1
GRID 4087 0.492 -0.492 -18.3043 -1
GRID 4088 0.246 -0.492 -18.6044 -1
GRID 4089 0.492 -0.492 -18.6044 -1
GRID 4090 0.246 -0.492 -18.9045 -1
GRID 4091 0.492 -0.492 -18.9045 -1
GRID 4092 0.246 -0.492 -19.2045 -1
GRID 4093 0.492 -0.492 -19.2045 -1
GRID 4094 0.246 -0.492 -19.5046 -1
GRID 4095 0.492 -0.492 -19.5046 -1
GRID 4096 0.246 -0.492 -19.8047 -1

1426 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 4097 0.492 -0.492 -19.8047 -1
GRID 4098 0.246 -0.492 -20.1048 -1
GRID 4099 0.492 -0.492 -20.1048 -1
GRID 4100 0.246 -0.492 -20.4048 -1
GRID 4101 0.492 -0.492 -20.4048 -1
GRID 4102 0.246 -0.492 -20.7049 -1
GRID 4103 0.492 -0.492 -20.7049 -1
GRID 4104 0.246 -0.492 -21.005 -1
GRID 4105 0.492 -0.492 -21.005 -1
GRID 4106 0.246 -0.492 -21.3051 -1
GRID 4107 0.492 -0.492 -21.3051 -1
GRID 4108 0.246 -0.492 -21.6051 -1
GRID 4109 0.492 -0.492 -21.6051 -1
GRID 4110 0.246 -0.492 -21.9052 -1
GRID 4111 0.492 -0.492 -21.9052 -1
GRID 4112 0.246 -0.492 -22.2053 -1
GRID 4113 0.492 -0.492 -22.2053 -1
GRID 4114 0.246 -0.492 -22.5053 -1
GRID 4115 0.492 -0.492 -22.5053 -1
GRID 4116 0.246 -0.492 -22.8054 -1
GRID 4117 0.492 -0.492 -22.8054 -1
GRID 4118 0.246 -0.492 -23.1055 -1
GRID 4119 0.492 -0.492 -23.1055 -1
GRID 4120 0.246 -0.492 -23.4056 -1
GRID 4121 0.492 -0.492 -23.4056 -1
GRID 4122 0.246 -0.492 -23.7056 -1
GRID 4123 0.492 -0.492 -23.7056 -1
GRID 4124 0.246 -0.492 -24.0057 -1
GRID 4125 0.492 -0.492 -24.0057 -1
GRID 4126 0.246 -0.492 -24.3058 -1
GRID 4127 0.492 -0.492 -24.3058 -1
GRID 4128 0.246 -0.492 -24.6059 -1
GRID 4129 0.492 -0.492 -24.6059 -1
GRID 4130 0.246 -0.492 -24.9059 -1
GRID 4131 0.492 -0.492 -24.9059 -1
GRID 4132 0.246 -0.492 -25.206 -1
GRID 4133 0.492 -0.492 -25.206 -1
GRID 6776 -0.246 -0.246 8.589-16
GRID 6777 0.246 -0.246 -8.59-16
GRID 6778 0.0 -0.246 0.0
GRID 6779 -0.492 -0.246 1.718-15
GRID 6780 -0.492 -0.492 1.718-15
GRID 6781 -0.246 -0.492 8.589-16
GRID 6782 0.0 -0.492 0.0
GRID 6783 0.246 -0.492 -8.59-16
GRID 6784 0.492 -0.492 -1.72-15
GRID 6785 0.492 -0.246 -1.72-15
GRID 6786 0.246 0.246 -8.59-16
GRID 6787 -0.246 0.246 8.589-16
GRID 6788 0.0 0.246 0.0
GRID 6789 0.492 0.246 -1.72-15
GRID 6790 0.492 0.492 -1.72-15
GRID 6791 0.246 0.492 -8.59-16
GRID 6792 0.0 0.492 0.0
GRID 6793 -0.246 0.492 8.589-16
GRID 6794 -0.492 0.492 1.718-15
GRID 6795 -0.492 0.246 1.718-15
GRID 6796 -0.492 0.0 1.718-15
GRID 6797 -0.246 0.0 8.589-16
GRID 6798 0.0 0.0 0.0
GRID 6799 0.246 0.0 -8.59-16
GRID 6800 0.492 0.0 -1.72-15
$$
$$ SPOINT Data
$$
$
$ CQUAD4 Elements
$
CQUAD4 5627 1 6778 6798 6799 6777

Altair Engineering OptiStruct 13.0 Reference Guide 1427

Proprietary Information of Altair Engineering


CQUAD4 5629 1 6782 6778 6777 6783
CQUAD4 6116 1 6777 6799 6800 6785
CQUAD4 6122 1 6783 6777 6785 6784
CQUAD4 6125 1 6799 6798 6788 6786
CQUAD4 6520 1 6779 6796 6797 6776
CQUAD4 6521 1 6776 6797 6798 6778
CQUAD4 6523 1 6780 6779 6776 6781
CQUAD4 6528 1 6781 6776 6778 6782
CQUAD4 6954 1 6797 6796 6795 6787
CQUAD4 7220 1 6788 6787 6793 6792
CQUAD4 7647 1 6787 6795 6794 6793
CQUAD4 7652 1 6798 6797 6787 6788
CQUAD4 7945 1 6786 6788 6792 6791
CQUAD4 7948 1 6789 6786 6791 6790
CQUAD4 7955 1 6800 6799 6786 6789
$
$HMMOVE 5
$ 5627 5629 6116 6122 6125 6520THRU 6521 6523
$ 6528 6954 7220 7647 7652 7945 7948 7955
$
$
$ CHEXA Elements: First Order
$
CHEXA 17 2 10 11 21 23 34 35
+ 36 37
CHEXA 18 2 34 35 36 37 38 39
+ 40 41
CHEXA 19 2 38 39 40 41 42 43
+ 44 45
CHEXA 20 2 42 43 44 45 46 47
+ 48 49
CHEXA 21 2 46 47 48 49 50 51
+ 52 53
CHEXA 22 2 50 51 52 53 54 55
+ 56 57
CHEXA 23 2 54 55 56 57 58 59
+ 60 61
CHEXA 24 2 58 59 60 61 62 63
+ 64 65
CHEXA 25 2 62 63 64 65 66 67
+ 68 69
CHEXA 26 2 66 67 68 69 70 71
+ 72 73
CHEXA 27 2 70 71 72 73 74 75
+ 76 77
CHEXA 28 2 74 75 76 77 78 79
+ 80 81
CHEXA 29 2 78 79 80 81 82 83
+ 84 85
CHEXA 30 2 82 83 84 85 86 87
+ 88 89
CHEXA 31 2 86 87 88 89 90 91
+ 92 93
CHEXA 32 2 90 91 92 93 94 95
+ 96 97
CHEXA 33 2 94 95 96 97 98 99
+ 100 101
CHEXA 34 2 98 99 100 101 102 103
+ 104 105
CHEXA 35 2 102 103 104 105 106 107
+ 108 109
CHEXA 36 2 106 107 108 109 110 111
+ 112 113
CHEXA 37 2 110 111 112 113 114 115
+ 116 117
CHEXA 38 2 114 115 116 117 118 119
+ 120 121
CHEXA 39 2 118 119 120 121 122 123
+ 124 125

1428 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 40 2 122 123 124 125 126 127
+ 128 129
CHEXA 41 2 126 127 128 129 130 131
+ 132 133
CHEXA 42 2 130 131 132 133 134 135
+ 136 137
CHEXA 43 2 134 135 136 137 138 139
+ 140 141
CHEXA 44 2 138 139 140 141 142 143
+ 144 145
CHEXA 45 2 142 143 144 145 146 147
+ 148 149
CHEXA 46 2 146 147 148 149 150 151
+ 152 153
CHEXA 47 2 150 151 152 153 154 155
+ 156 157
CHEXA 48 2 154 155 156 157 158 159
+ 160 161
CHEXA 49 2 158 159 160 161 162 163
+ 164 165
CHEXA 50 2 162 163 164 165 166 167
+ 168 169
CHEXA 51 2 166 167 168 169 170 171
+ 172 173
CHEXA 52 2 170 171 172 173 174 175
+ 176 177
CHEXA 53 2 174 175 176 177 178 179
+ 180 181
CHEXA 54 2 178 179 180 181 182 183
+ 184 185
CHEXA 55 2 182 183 184 185 186 187
+ 188 189
CHEXA 56 2 186 187 188 189 190 191
+ 192 193
CHEXA 57 2 190 191 192 193 194 195
+ 196 197
CHEXA 58 2 194 195 196 197 198 199
+ 200 201
CHEXA 139 2 198 199 200 201 522 523
+ 524 525
CHEXA 140 2 522 523 524 525 526 527
+ 528 529
CHEXA 141 2 526 527 528 529 530 531
+ 532 533
CHEXA 142 2 530 531 532 533 534 535
+ 536 537
CHEXA 143 2 534 535 536 537 538 539
+ 540 541
CHEXA 144 2 538 539 540 541 542 543
+ 544 545
CHEXA 145 2 542 543 544 545 546 547
+ 548 549
CHEXA 146 2 546 547 548 549 550 551
+ 552 553
CHEXA 147 2 550 551 552 553 554 555
+ 556 557
CHEXA 148 2 554 555 556 557 558 559
+ 560 561
CHEXA 149 2 558 559 560 561 562 563
+ 564 565
CHEXA 150 2 562 563 564 565 566 567
+ 568 569
CHEXA 151 2 566 567 568 569 570 571
+ 572 573
CHEXA 152 2 570 571 572 573 574 575
+ 576 577
CHEXA 153 2 574 575 576 577 578 579
+ 580 581
CHEXA 154 2 578 579 580 581 582 583

Altair Engineering OptiStruct 13.0 Reference Guide 1429

Proprietary Information of Altair Engineering


+ 584 585
CHEXA 155 2 582 583 584 585 586 587
+ 588 589
CHEXA 156 2 586 587 588 589 590 591
+ 592 593
CHEXA 157 2 590 591 592 593 594 595
+ 596 597
CHEXA 158 2 594 595 596 597 598 599
+ 600 601
CHEXA 159 2 598 599 600 601 602 603
+ 604 605
CHEXA 160 2 602 603 604 605 606 607
+ 608 609
CHEXA 161 2 606 607 608 609 610 611
+ 612 613
CHEXA 162 2 610 611 612 613 614 615
+ 616 617
CHEXA 163 2 614 615 616 617 618 619
+ 620 621
CHEXA 164 2 618 619 620 621 622 623
+ 624 625
CHEXA 165 2 622 623 624 625 626 627
+ 628 629
CHEXA 166 2 626 627 628 629 630 631
+ 632 633
CHEXA 167 2 630 631 632 633 634 635
+ 636 637
CHEXA 168 2 634 635 636 637 638 639
+ 640 641
CHEXA 169 2 638 639 640 641 642 643
+ 644 645
CHEXA 170 2 642 643 644 645 646 647
+ 648 649
CHEXA 171 2 646 647 648 649 650 651
+ 652 653
CHEXA 172 2 650 651 652 653 654 655
+ 656 657
CHEXA 173 2 654 655 656 657 658 659
+ 660 661
CHEXA 174 2 658 659 660 661 662 663
+ 664 665
CHEXA 175 2 662 663 664 665 666 667
+ 668 669
CHEXA 176 2 666 667 668 669 670 671
+ 672 673
CHEXA 177 2 670 671 672 673 674 675
+ 676 677
CHEXA 178 2 674 675 676 677 678 679
+ 680 681
CHEXA 179 2 678 679 680 681 682 683
+ 684 685
CHEXA 180 2 682 683 684 685 686 687
+ 688 689
CHEXA 181 2 9 10 23 20 690 34
+ 37 691
CHEXA 182 2 690 34 37 691 692 38
+ 41 693
CHEXA 183 2 692 38 41 693 694 42
+ 45 695
CHEXA 184 2 694 42 45 695 696 46
+ 49 697
CHEXA 185 2 696 46 49 697 698 50
+ 53 699
CHEXA 186 2 698 50 53 699 700 54
+ 57 701
CHEXA 187 2 700 54 57 701 702 58
+ 61 703
CHEXA 188 2 702 58 61 703 704 62
+ 65 705

1430 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 189 2 704 62 65 705 706 66
+ 69 707
CHEXA 190 2 706 66 69 707 708 70
+ 73 709
CHEXA 191 2 708 70 73 709 710 74
+ 77 711
CHEXA 192 2 710 74 77 711 712 78
+ 81 713
CHEXA 193 2 712 78 81 713 714 82
+ 85 715
CHEXA 194 2 714 82 85 715 716 86
+ 89 717
CHEXA 195 2 716 86 89 717 718 90
+ 93 719
CHEXA 196 2 718 90 93 719 720 94
+ 97 721
CHEXA 197 2 720 94 97 721 722 98
+ 101 723
CHEXA 198 2 722 98 101 723 724 102
+ 105 725
CHEXA 199 2 724 102 105 725 726 106
+ 109 727
CHEXA 200 2 726 106 109 727 728 110
+ 113 729
CHEXA 201 2 728 110 113 729 730 114
+ 117 731
CHEXA 202 2 730 114 117 731 732 118
+ 121 733
CHEXA 203 2 732 118 121 733 734 122
+ 125 735
CHEXA 204 2 734 122 125 735 736 126
+ 129 737
CHEXA 205 2 736 126 129 737 738 130
+ 133 739
CHEXA 206 2 738 130 133 739 740 134
+ 137 741
CHEXA 207 2 740 134 137 741 742 138
+ 141 743
CHEXA 208 2 742 138 141 743 744 142
+ 145 745
CHEXA 209 2 744 142 145 745 746 146
+ 149 747
CHEXA 210 2 746 146 149 747 748 150
+ 153 749
CHEXA 211 2 748 150 153 749 750 154
+ 157 751
CHEXA 212 2 750 154 157 751 752 158
+ 161 753
CHEXA 213 2 752 158 161 753 754 162
+ 165 755
CHEXA 214 2 754 162 165 755 756 166
+ 169 757
CHEXA 215 2 756 166 169 757 758 170
+ 173 759
CHEXA 216 2 758 170 173 759 760 174
+ 177 761
CHEXA 217 2 760 174 177 761 762 178
+ 181 763
CHEXA 218 2 762 178 181 763 764 182
+ 185 765
CHEXA 219 2 764 182 185 765 766 186
+ 189 767
CHEXA 220 2 766 186 189 767 768 190
+ 193 769
CHEXA 221 2 768 190 193 769 770 194
+ 197 771
CHEXA 222 2 770 194 197 771 772 198
+ 201 773
CHEXA 303 2 772 198 201 773 934 522

Altair Engineering OptiStruct 13.0 Reference Guide 1431

Proprietary Information of Altair Engineering


+ 525 935
CHEXA 304 2 934 522 525 935 936 526
+ 529 937
CHEXA 305 2 936 526 529 937 938 530
+ 533 939
CHEXA 306 2 938 530 533 939 940 534
+ 537 941
CHEXA 307 2 940 534 537 941 942 538
+ 541 943
CHEXA 308 2 942 538 541 943 944 542
+ 545 945
CHEXA 309 2 944 542 545 945 946 546
+ 549 947
CHEXA 310 2 946 546 549 947 948 550
+ 553 949
CHEXA 311 2 948 550 553 949 950 554
+ 557 951
CHEXA 312 2 950 554 557 951 952 558
+ 561 953
CHEXA 313 2 952 558 561 953 954 562
+ 565 955
CHEXA 314 2 954 562 565 955 956 566
+ 569 957
CHEXA 315 2 956 566 569 957 958 570
+ 573 959
CHEXA 316 2 958 570 573 959 960 574
+ 577 961
CHEXA 317 2 960 574 577 961 962 578
+ 581 963
CHEXA 318 2 962 578 581 963 964 582
+ 585 965
CHEXA 319 2 964 582 585 965 966 586
+ 589 967
CHEXA 320 2 966 586 589 967 968 590
+ 593 969
CHEXA 321 2 968 590 593 969 970 594
+ 597 971
CHEXA 322 2 970 594 597 971 972 598
+ 601 973
CHEXA 323 2 972 598 601 973 974 602
+ 605 975
CHEXA 324 2 974 602 605 975 976 606
+ 609 977
CHEXA 325 2 976 606 609 977 978 610
+ 613 979
CHEXA 326 2 978 610 613 979 980 614
+ 617 981
CHEXA 327 2 980 614 617 981 982 618
+ 621 983
CHEXA 328 2 982 618 621 983 984 622
+ 625 985
CHEXA 329 2 984 622 625 985 986 626
+ 629 987
CHEXA 330 2 986 626 629 987 988 630
+ 633 989
CHEXA 331 2 988 630 633 989 990 634
+ 637 991
CHEXA 332 2 990 634 637 991 992 638
+ 641 993
CHEXA 333 2 992 638 641 993 994 642
+ 645 995
CHEXA 334 2 994 642 645 995 996 646
+ 649 997
CHEXA 335 2 996 646 649 997 998 650
+ 653 999
CHEXA 336 2 998 650 653 999 1000 654
+ 657 1001
CHEXA 337 2 1000 654 657 1001 1002 658
+ 661 1003

1432 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 338 2 1002 658 661 1003 1004 662
+ 665 1005
CHEXA 339 2 1004 662 665 1005 1006 666
+ 669 1007
CHEXA 340 2 1006 666 669 1007 1008 670
+ 673 1009
CHEXA 341 2 1008 670 673 1009 1010 674
+ 677 1011
CHEXA 342 2 1010 674 677 1011 1012 678
+ 681 1013
CHEXA 343 2 1012 678 681 1013 1014 682
+ 685 1015
CHEXA 344 2 1014 682 685 1015 1016 686
+ 689 1017
CHEXA 345 2 23 21 17 18 37 36
+ 1018 1019
CHEXA 346 2 37 36 1018 1019 41 40
+ 1020 1021
CHEXA 347 2 41 40 1020 1021 45 44
+ 1022 1023
CHEXA 348 2 45 44 1022 1023 49 48
+ 1024 1025
CHEXA 349 2 49 48 1024 1025 53 52
+ 1026 1027
CHEXA 350 2 53 52 1026 1027 57 56
+ 1028 1029
CHEXA 351 2 57 56 1028 1029 61 60
+ 1030 1031
CHEXA 352 2 61 60 1030 1031 65 64
+ 1032 1033
CHEXA 353 2 65 64 1032 1033 69 68
+ 1034 1035
CHEXA 354 2 69 68 1034 1035 73 72
+ 1036 1037
CHEXA 355 2 73 72 1036 1037 77 76
+ 1038 1039
CHEXA 356 2 77 76 1038 1039 81 80
+ 1040 1041
CHEXA 357 2 81 80 1040 1041 85 84
+ 1042 1043
CHEXA 358 2 85 84 1042 1043 89 88
+ 1044 1045
CHEXA 359 2 89 88 1044 1045 93 92
+ 1046 1047
CHEXA 360 2 93 92 1046 1047 97 96
+ 1048 1049
CHEXA 361 2 97 96 1048 1049 101 100
+ 1050 1051
CHEXA 362 2 101 100 1050 1051 105 104
+ 1052 1053
CHEXA 363 2 105 104 1052 1053 109 108
+ 1054 1055
CHEXA 364 2 109 108 1054 1055 113 112
+ 1056 1057
CHEXA 365 2 113 112 1056 1057 117 116
+ 1058 1059
CHEXA 366 2 117 116 1058 1059 121 120
+ 1060 1061
CHEXA 367 2 121 120 1060 1061 125 124
+ 1062 1063
CHEXA 368 2 125 124 1062 1063 129 128
+ 1064 1065
CHEXA 369 2 129 128 1064 1065 133 132
+ 1066 1067
CHEXA 370 2 133 132 1066 1067 137 136
+ 1068 1069
CHEXA 371 2 137 136 1068 1069 141 140
+ 1070 1071
CHEXA 372 2 141 140 1070 1071 145 144

Altair Engineering OptiStruct 13.0 Reference Guide 1433

Proprietary Information of Altair Engineering


+ 1072 1073
CHEXA 373 2 145 144 1072 1073 149 148
+ 1074 1075
CHEXA 374 2 149 148 1074 1075 153 152
+ 1076 1077
CHEXA 375 2 153 152 1076 1077 157 156
+ 1078 1079
CHEXA 376 2 157 156 1078 1079 161 160
+ 1080 1081
CHEXA 377 2 161 160 1080 1081 165 164
+ 1082 1083
CHEXA 378 2 165 164 1082 1083 169 168
+ 1084 1085
CHEXA 379 2 169 168 1084 1085 173 172
+ 1086 1087
CHEXA 380 2 173 172 1086 1087 177 176
+ 1088 1089
CHEXA 381 2 177 176 1088 1089 181 180
+ 1090 1091
CHEXA 382 2 181 180 1090 1091 185 184
+ 1092 1093
CHEXA 383 2 185 184 1092 1093 189 188
+ 1094 1095
CHEXA 384 2 189 188 1094 1095 193 192
+ 1096 1097
CHEXA 385 2 193 192 1096 1097 197 196
+ 1098 1099
CHEXA 386 2 197 196 1098 1099 201 200
+ 1100 1101
CHEXA 467 2 201 200 1100 1101 525 524
+ 1262 1263
CHEXA 468 2 525 524 1262 1263 529 528
+ 1264 1265
CHEXA 469 2 529 528 1264 1265 533 532
+ 1266 1267
CHEXA 470 2 533 532 1266 1267 537 536
+ 1268 1269
CHEXA 471 2 537 536 1268 1269 541 540
+ 1270 1271
CHEXA 472 2 541 540 1270 1271 545 544
+ 1272 1273
CHEXA 473 2 545 544 1272 1273 549 548
+ 1274 1275
CHEXA 474 2 549 548 1274 1275 553 552
+ 1276 1277
CHEXA 475 2 553 552 1276 1277 557 556
+ 1278 1279
CHEXA 476 2 557 556 1278 1279 561 560
+ 1280 1281
CHEXA 477 2 561 560 1280 1281 565 564
+ 1282 1283
CHEXA 478 2 565 564 1282 1283 569 568
+ 1284 1285
CHEXA 479 2 569 568 1284 1285 573 572
+ 1286 1287
CHEXA 480 2 573 572 1286 1287 577 576
+ 1288 1289
CHEXA 481 2 577 576 1288 1289 581 580
+ 1290 1291
CHEXA 482 2 581 580 1290 1291 585 584
+ 1292 1293
CHEXA 483 2 585 584 1292 1293 589 588
+ 1294 1295
CHEXA 484 2 589 588 1294 1295 593 592
+ 1296 1297
CHEXA 485 2 593 592 1296 1297 597 596
+ 1298 1299
CHEXA 486 2 597 596 1298 1299 601 600
+ 1300 1301

1434 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 487 2 601 600 1300 1301 605 604
+ 1302 1303
CHEXA 488 2 605 604 1302 1303 609 608
+ 1304 1305
CHEXA 489 2 609 608 1304 1305 613 612
+ 1306 1307
CHEXA 490 2 613 612 1306 1307 617 616
+ 1308 1309
CHEXA 491 2 617 616 1308 1309 621 620
+ 1310 1311
CHEXA 492 2 621 620 1310 1311 625 624
+ 1312 1313
CHEXA 493 2 625 624 1312 1313 629 628
+ 1314 1315
CHEXA 494 2 629 628 1314 1315 633 632
+ 1316 1317
CHEXA 495 2 633 632 1316 1317 637 636
+ 1318 1319
CHEXA 496 2 637 636 1318 1319 641 640
+ 1320 1321
CHEXA 497 2 641 640 1320 1321 645 644
+ 1322 1323
CHEXA 498 2 645 644 1322 1323 649 648
+ 1324 1325
CHEXA 499 2 649 648 1324 1325 653 652
+ 1326 1327
CHEXA 500 2 653 652 1326 1327 657 656
+ 1328 1329
CHEXA 501 2 657 656 1328 1329 661 660
+ 1330 1331
CHEXA 502 2 661 660 1330 1331 665 664
+ 1332 1333
CHEXA 503 2 665 664 1332 1333 669 668
+ 1334 1335
CHEXA 504 2 669 668 1334 1335 673 672
+ 1336 1337
CHEXA 505 2 673 672 1336 1337 677 676
+ 1338 1339
CHEXA 506 2 677 676 1338 1339 681 680
+ 1340 1341
CHEXA 507 2 681 680 1340 1341 685 684
+ 1342 1343
CHEXA 508 2 685 684 1342 1343 689 688
+ 1344 1345
CHEXA 509 2 20 23 18 19 691 37
+ 1019 1346
CHEXA 510 2 691 37 1019 1346 693 41
+ 1021 1347
CHEXA 511 2 693 41 1021 1347 695 45
+ 1023 1348
CHEXA 512 2 695 45 1023 1348 697 49
+ 1025 1349
CHEXA 513 2 697 49 1025 1349 699 53
+ 1027 1350
CHEXA 514 2 699 53 1027 1350 701 57
+ 1029 1351
CHEXA 515 2 701 57 1029 1351 703 61
+ 1031 1352
CHEXA 516 2 703 61 1031 1352 705 65
+ 1033 1353
CHEXA 517 2 705 65 1033 1353 707 69
+ 1035 1354
CHEXA 518 2 707 69 1035 1354 709 73
+ 1037 1355
CHEXA 519 2 709 73 1037 1355 711 77
+ 1039 1356
CHEXA 520 2 711 77 1039 1356 713 81
+ 1041 1357
CHEXA 521 2 713 81 1041 1357 715 85

Altair Engineering OptiStruct 13.0 Reference Guide 1435

Proprietary Information of Altair Engineering


+ 1043 1358
CHEXA 522 2 715 85 1043 1358 717 89
+ 1045 1359
CHEXA 523 2 717 89 1045 1359 719 93
+ 1047 1360
CHEXA 524 2 719 93 1047 1360 721 97
+ 1049 1361
CHEXA 525 2 721 97 1049 1361 723 101
+ 1051 1362
CHEXA 526 2 723 101 1051 1362 725 105
+ 1053 1363
CHEXA 527 2 725 105 1053 1363 727 109
+ 1055 1364
CHEXA 528 2 727 109 1055 1364 729 113
+ 1057 1365
CHEXA 529 2 729 113 1057 1365 731 117
+ 1059 1366
CHEXA 530 2 731 117 1059 1366 733 121
+ 1061 1367
CHEXA 531 2 733 121 1061 1367 735 125
+ 1063 1368
CHEXA 532 2 735 125 1063 1368 737 129
+ 1065 1369
CHEXA 533 2 737 129 1065 1369 739 133
+ 1067 1370
CHEXA 534 2 739 133 1067 1370 741 137
+ 1069 1371
CHEXA 535 2 741 137 1069 1371 743 141
+ 1071 1372
CHEXA 536 2 743 141 1071 1372 745 145
+ 1073 1373
CHEXA 537 2 745 145 1073 1373 747 149
+ 1075 1374
CHEXA 538 2 747 149 1075 1374 749 153
+ 1077 1375
CHEXA 539 2 749 153 1077 1375 751 157
+ 1079 1376
CHEXA 540 2 751 157 1079 1376 753 161
+ 1081 1377
CHEXA 541 2 753 161 1081 1377 755 165
+ 1083 1378
CHEXA 542 2 755 165 1083 1378 757 169
+ 1085 1379
CHEXA 543 2 757 169 1085 1379 759 173
+ 1087 1380
CHEXA 544 2 759 173 1087 1380 761 177
+ 1089 1381
CHEXA 545 2 761 177 1089 1381 763 181
+ 1091 1382
CHEXA 546 2 763 181 1091 1382 765 185
+ 1093 1383
CHEXA 547 2 765 185 1093 1383 767 189
+ 1095 1384
CHEXA 548 2 767 189 1095 1384 769 193
+ 1097 1385
CHEXA 549 2 769 193 1097 1385 771 197
+ 1099 1386
CHEXA 550 2 771 197 1099 1386 773 201
+ 1101 1387
CHEXA 631 2 773 201 1101 1387 935 525
+ 1263 1468
CHEXA 632 2 935 525 1263 1468 937 529
+ 1265 1469
CHEXA 633 2 937 529 1265 1469 939 533
+ 1267 1470
CHEXA 634 2 939 533 1267 1470 941 537
+ 1269 1471
CHEXA 635 2 941 537 1269 1471 943 541
+ 1271 1472

1436 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 636 2 943 541 1271 1472 945 545
+ 1273 1473
CHEXA 637 2 945 545 1273 1473 947 549
+ 1275 1474
CHEXA 638 2 947 549 1275 1474 949 553
+ 1277 1475
CHEXA 639 2 949 553 1277 1475 951 557
+ 1279 1476
CHEXA 640 2 951 557 1279 1476 953 561
+ 1281 1477
CHEXA 641 2 953 561 1281 1477 955 565
+ 1283 1478
CHEXA 642 2 955 565 1283 1478 957 569
+ 1285 1479
CHEXA 643 2 957 569 1285 1479 959 573
+ 1287 1480
CHEXA 644 2 959 573 1287 1480 961 577
+ 1289 1481
CHEXA 645 2 961 577 1289 1481 963 581
+ 1291 1482
CHEXA 646 2 963 581 1291 1482 965 585
+ 1293 1483
CHEXA 647 2 965 585 1293 1483 967 589
+ 1295 1484
CHEXA 648 2 967 589 1295 1484 969 593
+ 1297 1485
CHEXA 649 2 969 593 1297 1485 971 597
+ 1299 1486
CHEXA 650 2 971 597 1299 1486 973 601
+ 1301 1487
CHEXA 651 2 973 601 1301 1487 975 605
+ 1303 1488
CHEXA 652 2 975 605 1303 1488 977 609
+ 1305 1489
CHEXA 653 2 977 609 1305 1489 979 613
+ 1307 1490
CHEXA 654 2 979 613 1307 1490 981 617
+ 1309 1491
CHEXA 655 2 981 617 1309 1491 983 621
+ 1311 1492
CHEXA 656 2 983 621 1311 1492 985 625
+ 1313 1493
CHEXA 657 2 985 625 1313 1493 987 629
+ 1315 1494
CHEXA 658 2 987 629 1315 1494 989 633
+ 1317 1495
CHEXA 659 2 989 633 1317 1495 991 637
+ 1319 1496
CHEXA 660 2 991 637 1319 1496 993 641
+ 1321 1497
CHEXA 661 2 993 641 1321 1497 995 645
+ 1323 1498
CHEXA 662 2 995 645 1323 1498 997 649
+ 1325 1499
CHEXA 663 2 997 649 1325 1499 999 653
+ 1327 1500
CHEXA 664 2 999 653 1327 1500 1001 657
+ 1329 1501
CHEXA 665 2 1001 657 1329 1501 1003 661
+ 1331 1502
CHEXA 666 2 1003 661 1331 1502 1005 665
+ 1333 1503
CHEXA 667 2 1005 665 1333 1503 1007 669
+ 1335 1504
CHEXA 668 2 1007 669 1335 1504 1009 673
+ 1337 1505
CHEXA 669 2 1009 673 1337 1505 1011 677
+ 1339 1506
CHEXA 670 2 1011 677 1339 1506 1013 681

Altair Engineering OptiStruct 13.0 Reference Guide 1437

Proprietary Information of Altair Engineering


+ 1341 1507
CHEXA 671 2 1013 681 1341 1507 1015 685
+ 1343 1508
CHEXA 672 2 1015 685 1343 1508 1017 689
+ 1345 1509
CHEXA 673 2 12 13 14 22 1510 1511
+ 1512 1513
CHEXA 674 2 1510 1511 1512 1513 1514 1515
+ 1516 1517
CHEXA 675 2 1514 1515 1516 1517 1518 1519
+ 1520 1521
CHEXA 676 2 1518 1519 1520 1521 1522 1523
+ 1524 1525
CHEXA 677 2 1522 1523 1524 1525 1526 1527
+ 1528 1529
CHEXA 678 2 1526 1527 1528 1529 1530 1531
+ 1532 1533
CHEXA 679 2 1530 1531 1532 1533 1534 1535
+ 1536 1537
CHEXA 680 2 1534 1535 1536 1537 1538 1539
+ 1540 1541
CHEXA 681 2 1538 1539 1540 1541 1542 1543
+ 1544 1545
CHEXA 682 2 1542 1543 1544 1545 1546 1547
+ 1548 1549
CHEXA 683 2 1546 1547 1548 1549 1550 1551
+ 1552 1553
CHEXA 684 2 1550 1551 1552 1553 1554 1555
+ 1556 1557
CHEXA 685 2 1554 1555 1556 1557 1558 1559
+ 1560 1561
CHEXA 686 2 1558 1559 1560 1561 1562 1563
+ 1564 1565
CHEXA 687 2 1562 1563 1564 1565 1566 1567
+ 1568 1569
CHEXA 688 2 1566 1567 1568 1569 1570 1571
+ 1572 1573
CHEXA 689 2 1570 1571 1572 1573 1574 1575
+ 1576 1577
CHEXA 690 2 1574 1575 1576 1577 1578 1579
+ 1580 1581
CHEXA 691 2 1578 1579 1580 1581 1582 1583
+ 1584 1585
CHEXA 692 2 1582 1583 1584 1585 1586 1587
+ 1588 1589
CHEXA 693 2 1586 1587 1588 1589 1590 1591
+ 1592 1593
CHEXA 694 2 1590 1591 1592 1593 1594 1595
+ 1596 1597
CHEXA 695 2 1594 1595 1596 1597 1598 1599
+ 1600 1601
CHEXA 696 2 1598 1599 1600 1601 1602 1603
+ 1604 1605
CHEXA 697 2 1602 1603 1604 1605 1606 1607
+ 1608 1609
CHEXA 698 2 1606 1607 1608 1609 1610 1611
+ 1612 1613
CHEXA 699 2 1610 1611 1612 1613 1614 1615
+ 1616 1617
CHEXA 700 2 1614 1615 1616 1617 1618 1619
+ 1620 1621
CHEXA 701 2 1618 1619 1620 1621 1622 1623
+ 1624 1625
CHEXA 702 2 1622 1623 1624 1625 1626 1627
+ 1628 1629
CHEXA 703 2 1626 1627 1628 1629 1630 1631
+ 1632 1633
CHEXA 704 2 1630 1631 1632 1633 1634 1635
+ 1636 1637

1438 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 705 2 1634 1635 1636 1637 1638 1639
+ 1640 1641
CHEXA 706 2 1638 1639 1640 1641 1642 1643
+ 1644 1645
CHEXA 707 2 1642 1643 1644 1645 1646 1647
+ 1648 1649
CHEXA 708 2 1646 1647 1648 1649 1650 1651
+ 1652 1653
CHEXA 709 2 1650 1651 1652 1653 1654 1655
+ 1656 1657
CHEXA 710 2 1654 1655 1656 1657 1658 1659
+ 1660 1661
CHEXA 711 2 1658 1659 1660 1661 1662 1663
+ 1664 1665
CHEXA 712 2 1662 1663 1664 1665 1666 1667
+ 1668 1669
CHEXA 713 2 1666 1667 1668 1669 1670 1671
+ 1672 1673
CHEXA 714 2 1670 1671 1672 1673 1674 1675
+ 1676 1677
CHEXA 795 2 1674 1675 1676 1677 1998 1999
+ 2000 2001
CHEXA 796 2 1998 1999 2000 2001 2002 2003
+ 2004 2005
CHEXA 797 2 2002 2003 2004 2005 2006 2007
+ 2008 2009
CHEXA 798 2 2006 2007 2008 2009 2010 2011
+ 2012 2013
CHEXA 799 2 2010 2011 2012 2013 2014 2015
+ 2016 2017
CHEXA 800 2 2014 2015 2016 2017 2018 2019
+ 2020 2021
CHEXA 801 2 2018 2019 2020 2021 2022 2023
+ 2024 2025
CHEXA 802 2 2022 2023 2024 2025 2026 2027
+ 2028 2029
CHEXA 803 2 2026 2027 2028 2029 2030 2031
+ 2032 2033
CHEXA 804 2 2030 2031 2032 2033 2034 2035
+ 2036 2037
CHEXA 805 2 2034 2035 2036 2037 2038 2039
+ 2040 2041
CHEXA 806 2 2038 2039 2040 2041 2042 2043
+ 2044 2045
CHEXA 807 2 2042 2043 2044 2045 2046 2047
+ 2048 2049
CHEXA 808 2 2046 2047 2048 2049 2050 2051
+ 2052 2053
CHEXA 809 2 2050 2051 2052 2053 2054 2055
+ 2056 2057
CHEXA 810 2 2054 2055 2056 2057 2058 2059
+ 2060 2061
CHEXA 811 2 2058 2059 2060 2061 2062 2063
+ 2064 2065
CHEXA 812 2 2062 2063 2064 2065 2066 2067
+ 2068 2069
CHEXA 813 2 2066 2067 2068 2069 2070 2071
+ 2072 2073
CHEXA 814 2 2070 2071 2072 2073 2074 2075
+ 2076 2077
CHEXA 815 2 2074 2075 2076 2077 2078 2079
+ 2080 2081
CHEXA 816 2 2078 2079 2080 2081 2082 2083
+ 2084 2085
CHEXA 817 2 2082 2083 2084 2085 2086 2087
+ 2088 2089
CHEXA 818 2 2086 2087 2088 2089 2090 2091
+ 2092 2093
CHEXA 819 2 2090 2091 2092 2093 2094 2095

Altair Engineering OptiStruct 13.0 Reference Guide 1439

Proprietary Information of Altair Engineering


+ 2096 2097
CHEXA 820 2 2094 2095 2096 2097 2098 2099
+ 2100 2101
CHEXA 821 2 2098 2099 2100 2101 2102 2103
+ 2104 2105
CHEXA 822 2 2102 2103 2104 2105 2106 2107
+ 2108 2109
CHEXA 823 2 2106 2107 2108 2109 2110 2111
+ 2112 2113
CHEXA 824 2 2110 2111 2112 2113 2114 2115
+ 2116 2117
CHEXA 825 2 2114 2115 2116 2117 2118 2119
+ 2120 2121
CHEXA 826 2 2118 2119 2120 2121 2122 2123
+ 2124 2125
CHEXA 827 2 2122 2123 2124 2125 2126 2127
+ 2128 2129
CHEXA 828 2 2126 2127 2128 2129 2130 2131
+ 2132 2133
CHEXA 829 2 2130 2131 2132 2133 2134 2135
+ 2136 2137
CHEXA 830 2 2134 2135 2136 2137 2138 2139
+ 2140 2141
CHEXA 831 2 2138 2139 2140 2141 2142 2143
+ 2144 2145
CHEXA 832 2 2142 2143 2144 2145 2146 2147
+ 2148 2149
CHEXA 833 2 2146 2147 2148 2149 2150 2151
+ 2152 2153
CHEXA 834 2 2150 2151 2152 2153 2154 2155
+ 2156 2157
CHEXA 835 2 2154 2155 2156 2157 2158 2159
+ 2160 2161
CHEXA 836 2 2158 2159 2160 2161 2162 2163
+ 2164 2165
CHEXA 837 2 11 12 22 21 35 1510
+ 1513 36
CHEXA 838 2 35 1510 1513 36 39 1514
+ 1517 40
CHEXA 839 2 39 1514 1517 40 43 1518
+ 1521 44
CHEXA 840 2 43 1518 1521 44 47 1522
+ 1525 48
CHEXA 841 2 47 1522 1525 48 51 1526
+ 1529 52
CHEXA 842 2 51 1526 1529 52 55 1530
+ 1533 56
CHEXA 843 2 55 1530 1533 56 59 1534
+ 1537 60
CHEXA 844 2 59 1534 1537 60 63 1538
+ 1541 64
CHEXA 845 2 63 1538 1541 64 67 1542
+ 1545 68
CHEXA 846 2 67 1542 1545 68 71 1546
+ 1549 72
CHEXA 847 2 71 1546 1549 72 75 1550
+ 1553 76
CHEXA 848 2 75 1550 1553 76 79 1554
+ 1557 80
CHEXA 849 2 79 1554 1557 80 83 1558
+ 1561 84
CHEXA 850 2 83 1558 1561 84 87 1562
+ 1565 88
CHEXA 851 2 87 1562 1565 88 91 1566
+ 1569 92
CHEXA 852 2 91 1566 1569 92 95 1570
+ 1573 96
CHEXA 853 2 95 1570 1573 96 99 1574
+ 1577 100

1440 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 854 2 99 1574 1577 100 103 1578
+ 1581 104
CHEXA 855 2 103 1578 1581 104 107 1582
+ 1585 108
CHEXA 856 2 107 1582 1585 108 111 1586
+ 1589 112
CHEXA 857 2 111 1586 1589 112 115 1590
+ 1593 116
CHEXA 858 2 115 1590 1593 116 119 1594
+ 1597 120
CHEXA 859 2 119 1594 1597 120 123 1598
+ 1601 124
CHEXA 860 2 123 1598 1601 124 127 1602
+ 1605 128
CHEXA 861 2 127 1602 1605 128 131 1606
+ 1609 132
CHEXA 862 2 131 1606 1609 132 135 1610
+ 1613 136
CHEXA 863 2 135 1610 1613 136 139 1614
+ 1617 140
CHEXA 864 2 139 1614 1617 140 143 1618
+ 1621 144
CHEXA 865 2 143 1618 1621 144 147 1622
+ 1625 148
CHEXA 866 2 147 1622 1625 148 151 1626
+ 1629 152
CHEXA 867 2 151 1626 1629 152 155 1630
+ 1633 156
CHEXA 868 2 155 1630 1633 156 159 1634
+ 1637 160
CHEXA 869 2 159 1634 1637 160 163 1638
+ 1641 164
CHEXA 870 2 163 1638 1641 164 167 1642
+ 1645 168
CHEXA 871 2 167 1642 1645 168 171 1646
+ 1649 172
CHEXA 872 2 171 1646 1649 172 175 1650
+ 1653 176
CHEXA 873 2 175 1650 1653 176 179 1654
+ 1657 180
CHEXA 874 2 179 1654 1657 180 183 1658
+ 1661 184
CHEXA 875 2 183 1658 1661 184 187 1662
+ 1665 188
CHEXA 876 2 187 1662 1665 188 191 1666
+ 1669 192
CHEXA 877 2 191 1666 1669 192 195 1670
+ 1673 196
CHEXA 878 2 195 1670 1673 196 199 1674
+ 1677 200
CHEXA 959 2 199 1674 1677 200 523 1998
+ 2001 524
CHEXA 960 2 523 1998 2001 524 527 2002
+ 2005 528
CHEXA 961 2 527 2002 2005 528 531 2006
+ 2009 532
CHEXA 962 2 531 2006 2009 532 535 2010
+ 2013 536
CHEXA 963 2 535 2010 2013 536 539 2014
+ 2017 540
CHEXA 964 2 539 2014 2017 540 543 2018
+ 2021 544
CHEXA 965 2 543 2018 2021 544 547 2022
+ 2025 548
CHEXA 966 2 547 2022 2025 548 551 2026
+ 2029 552
CHEXA 967 2 551 2026 2029 552 555 2030
+ 2033 556
CHEXA 968 2 555 2030 2033 556 559 2034

Altair Engineering OptiStruct 13.0 Reference Guide 1441

Proprietary Information of Altair Engineering


+ 2037 560
CHEXA 969 2 559 2034 2037 560 563 2038
+ 2041 564
CHEXA 970 2 563 2038 2041 564 567 2042
+ 2045 568
CHEXA 971 2 567 2042 2045 568 571 2046
+ 2049 572
CHEXA 972 2 571 2046 2049 572 575 2050
+ 2053 576
CHEXA 973 2 575 2050 2053 576 579 2054
+ 2057 580
CHEXA 974 2 579 2054 2057 580 583 2058
+ 2061 584
CHEXA 975 2 583 2058 2061 584 587 2062
+ 2065 588
CHEXA 976 2 587 2062 2065 588 591 2066
+ 2069 592
CHEXA 977 2 591 2066 2069 592 595 2070
+ 2073 596
CHEXA 978 2 595 2070 2073 596 599 2074
+ 2077 600
CHEXA 979 2 599 2074 2077 600 603 2078
+ 2081 604
CHEXA 980 2 603 2078 2081 604 607 2082
+ 2085 608
CHEXA 981 2 607 2082 2085 608 611 2086
+ 2089 612
CHEXA 982 2 611 2086 2089 612 615 2090
+ 2093 616
CHEXA 983 2 615 2090 2093 616 619 2094
+ 2097 620
CHEXA 984 2 619 2094 2097 620 623 2098
+ 2101 624
CHEXA 985 2 623 2098 2101 624 627 2102
+ 2105 628
CHEXA 986 2 627 2102 2105 628 631 2106
+ 2109 632
CHEXA 987 2 631 2106 2109 632 635 2110
+ 2113 636
CHEXA 988 2 635 2110 2113 636 639 2114
+ 2117 640
CHEXA 989 2 639 2114 2117 640 643 2118
+ 2121 644
CHEXA 990 2 643 2118 2121 644 647 2122
+ 2125 648
CHEXA 991 2 647 2122 2125 648 651 2126
+ 2129 652
CHEXA 992 2 651 2126 2129 652 655 2130
+ 2133 656
CHEXA 993 2 655 2130 2133 656 659 2134
+ 2137 660
CHEXA 994 2 659 2134 2137 660 663 2138
+ 2141 664
CHEXA 995 2 663 2138 2141 664 667 2142
+ 2145 668
CHEXA 996 2 667 2142 2145 668 671 2146
+ 2149 672
CHEXA 997 2 671 2146 2149 672 675 2150
+ 2153 676
CHEXA 998 2 675 2150 2153 676 679 2154
+ 2157 680
CHEXA 999 2 679 2154 2157 680 683 2158
+ 2161 684
CHEXA 1000 2 683 2158 2161 684 687 2162
+ 2165 688
CHEXA 1001 2 22 14 15 16 1513 1512
+ 2166 2167
CHEXA 1002 2 1513 1512 2166 2167 1517 1516
+ 2168 2169

1442 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 1003 2 1517 1516 2168 2169 1521 1520
+ 2170 2171
CHEXA 1004 2 1521 1520 2170 2171 1525 1524
+ 2172 2173
CHEXA 1005 2 1525 1524 2172 2173 1529 1528
+ 2174 2175
CHEXA 1006 2 1529 1528 2174 2175 1533 1532
+ 2176 2177
CHEXA 1007 2 1533 1532 2176 2177 1537 1536
+ 2178 2179
CHEXA 1008 2 1537 1536 2178 2179 1541 1540
+ 2180 2181
CHEXA 1009 2 1541 1540 2180 2181 1545 1544
+ 2182 2183
CHEXA 1010 2 1545 1544 2182 2183 1549 1548
+ 2184 2185
CHEXA 1011 2 1549 1548 2184 2185 1553 1552
+ 2186 2187
CHEXA 1012 2 1553 1552 2186 2187 1557 1556
+ 2188 2189
CHEXA 1013 2 1557 1556 2188 2189 1561 1560
+ 2190 2191
CHEXA 1014 2 1561 1560 2190 2191 1565 1564
+ 2192 2193
CHEXA 1015 2 1565 1564 2192 2193 1569 1568
+ 2194 2195
CHEXA 1016 2 1569 1568 2194 2195 1573 1572
+ 2196 2197
CHEXA 1017 2 1573 1572 2196 2197 1577 1576
+ 2198 2199
CHEXA 1018 2 1577 1576 2198 2199 1581 1580
+ 2200 2201
CHEXA 1019 2 1581 1580 2200 2201 1585 1584
+ 2202 2203
CHEXA 1020 2 1585 1584 2202 2203 1589 1588
+ 2204 2205
CHEXA 1021 2 1589 1588 2204 2205 1593 1592
+ 2206 2207
CHEXA 1022 2 1593 1592 2206 2207 1597 1596
+ 2208 2209
CHEXA 1023 2 1597 1596 2208 2209 1601 1600
+ 2210 2211
CHEXA 1024 2 1601 1600 2210 2211 1605 1604
+ 2212 2213
CHEXA 1025 2 1605 1604 2212 2213 1609 1608
+ 2214 2215
CHEXA 1026 2 1609 1608 2214 2215 1613 1612
+ 2216 2217
CHEXA 1027 2 1613 1612 2216 2217 1617 1616
+ 2218 2219
CHEXA 1028 2 1617 1616 2218 2219 1621 1620
+ 2220 2221
CHEXA 1029 2 1621 1620 2220 2221 1625 1624
+ 2222 2223
CHEXA 1030 2 1625 1624 2222 2223 1629 1628
+ 2224 2225
CHEXA 1031 2 1629 1628 2224 2225 1633 1632
+ 2226 2227
CHEXA 1032 2 1633 1632 2226 2227 1637 1636
+ 2228 2229
CHEXA 1033 2 1637 1636 2228 2229 1641 1640
+ 2230 2231
CHEXA 1034 2 1641 1640 2230 2231 1645 1644
+ 2232 2233
CHEXA 1035 2 1645 1644 2232 2233 1649 1648
+ 2234 2235
CHEXA 1036 2 1649 1648 2234 2235 1653 1652
+ 2236 2237
CHEXA 1037 2 1653 1652 2236 2237 1657 1656

Altair Engineering OptiStruct 13.0 Reference Guide 1443

Proprietary Information of Altair Engineering


+ 2238 2239
CHEXA 1038 2 1657 1656 2238 2239 1661 1660
+ 2240 2241
CHEXA 1039 2 1661 1660 2240 2241 1665 1664
+ 2242 2243
CHEXA 1040 2 1665 1664 2242 2243 1669 1668
+ 2244 2245
CHEXA 1041 2 1669 1668 2244 2245 1673 1672
+ 2246 2247
CHEXA 1042 2 1673 1672 2246 2247 1677 1676
+ 2248 2249
CHEXA 1123 2 1677 1676 2248 2249 2001 2000
+ 2410 2411
CHEXA 1124 2 2001 2000 2410 2411 2005 2004
+ 2412 2413
CHEXA 1125 2 2005 2004 2412 2413 2009 2008
+ 2414 2415
CHEXA 1126 2 2009 2008 2414 2415 2013 2012
+ 2416 2417
CHEXA 1127 2 2013 2012 2416 2417 2017 2016
+ 2418 2419
CHEXA 1128 2 2017 2016 2418 2419 2021 2020
+ 2420 2421
CHEXA 1129 2 2021 2020 2420 2421 2025 2024
+ 2422 2423
CHEXA 1130 2 2025 2024 2422 2423 2029 2028
+ 2424 2425
CHEXA 1131 2 2029 2028 2424 2425 2033 2032
+ 2426 2427
CHEXA 1132 2 2033 2032 2426 2427 2037 2036
+ 2428 2429
CHEXA 1133 2 2037 2036 2428 2429 2041 2040
+ 2430 2431
CHEXA 1134 2 2041 2040 2430 2431 2045 2044
+ 2432 2433
CHEXA 1135 2 2045 2044 2432 2433 2049 2048
+ 2434 2435
CHEXA 1136 2 2049 2048 2434 2435 2053 2052
+ 2436 2437
CHEXA 1137 2 2053 2052 2436 2437 2057 2056
+ 2438 2439
CHEXA 1138 2 2057 2056 2438 2439 2061 2060
+ 2440 2441
CHEXA 1139 2 2061 2060 2440 2441 2065 2064
+ 2442 2443
CHEXA 1140 2 2065 2064 2442 2443 2069 2068
+ 2444 2445
CHEXA 1141 2 2069 2068 2444 2445 2073 2072
+ 2446 2447
CHEXA 1142 2 2073 2072 2446 2447 2077 2076
+ 2448 2449
CHEXA 1143 2 2077 2076 2448 2449 2081 2080
+ 2450 2451
CHEXA 1144 2 2081 2080 2450 2451 2085 2084
+ 2452 2453
CHEXA 1145 2 2085 2084 2452 2453 2089 2088
+ 2454 2455
CHEXA 1146 2 2089 2088 2454 2455 2093 2092
+ 2456 2457
CHEXA 1147 2 2093 2092 2456 2457 2097 2096
+ 2458 2459
CHEXA 1148 2 2097 2096 2458 2459 2101 2100
+ 2460 2461
CHEXA 1149 2 2101 2100 2460 2461 2105 2104
+ 2462 2463
CHEXA 1150 2 2105 2104 2462 2463 2109 2108
+ 2464 2465
CHEXA 1151 2 2109 2108 2464 2465 2113 2112
+ 2466 2467

1444 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 1152 2 2113 2112 2466 2467 2117 2116
+ 2468 2469
CHEXA 1153 2 2117 2116 2468 2469 2121 2120
+ 2470 2471
CHEXA 1154 2 2121 2120 2470 2471 2125 2124
+ 2472 2473
CHEXA 1155 2 2125 2124 2472 2473 2129 2128
+ 2474 2475
CHEXA 1156 2 2129 2128 2474 2475 2133 2132
+ 2476 2477
CHEXA 1157 2 2133 2132 2476 2477 2137 2136
+ 2478 2479
CHEXA 1158 2 2137 2136 2478 2479 2141 2140
+ 2480 2481
CHEXA 1159 2 2141 2140 2480 2481 2145 2144
+ 2482 2483
CHEXA 1160 2 2145 2144 2482 2483 2149 2148
+ 2484 2485
CHEXA 1161 2 2149 2148 2484 2485 2153 2152
+ 2486 2487
CHEXA 1162 2 2153 2152 2486 2487 2157 2156
+ 2488 2489
CHEXA 1163 2 2157 2156 2488 2489 2161 2160
+ 2490 2491
CHEXA 1164 2 2161 2160 2490 2491 2165 2164
+ 2492 2493
CHEXA 1165 2 21 22 16 17 36 1513
+ 2167 1018
CHEXA 1166 2 36 1513 2167 1018 40 1517
+ 2169 1020
CHEXA 1167 2 40 1517 2169 1020 44 1521
+ 2171 1022
CHEXA 1168 2 44 1521 2171 1022 48 1525
+ 2173 1024
CHEXA 1169 2 48 1525 2173 1024 52 1529
+ 2175 1026
CHEXA 1170 2 52 1529 2175 1026 56 1533
+ 2177 1028
CHEXA 1171 2 56 1533 2177 1028 60 1537
+ 2179 1030
CHEXA 1172 2 60 1537 2179 1030 64 1541
+ 2181 1032
CHEXA 1173 2 64 1541 2181 1032 68 1545
+ 2183 1034
CHEXA 1174 2 68 1545 2183 1034 72 1549
+ 2185 1036
CHEXA 1175 2 72 1549 2185 1036 76 1553
+ 2187 1038
CHEXA 1176 2 76 1553 2187 1038 80 1557
+ 2189 1040
CHEXA 1177 2 80 1557 2189 1040 84 1561
+ 2191 1042
CHEXA 1178 2 84 1561 2191 1042 88 1565
+ 2193 1044
CHEXA 1179 2 88 1565 2193 1044 92 1569
+ 2195 1046
CHEXA 1180 2 92 1569 2195 1046 96 1573
+ 2197 1048
CHEXA 1181 2 96 1573 2197 1048 100 1577
+ 2199 1050
CHEXA 1182 2 100 1577 2199 1050 104 1581
+ 2201 1052
CHEXA 1183 2 104 1581 2201 1052 108 1585
+ 2203 1054
CHEXA 1184 2 108 1585 2203 1054 112 1589
+ 2205 1056
CHEXA 1185 2 112 1589 2205 1056 116 1593
+ 2207 1058
CHEXA 1186 2 116 1593 2207 1058 120 1597

Altair Engineering OptiStruct 13.0 Reference Guide 1445

Proprietary Information of Altair Engineering


+ 2209 1060
CHEXA 1187 2 120 1597 2209 1060 124 1601
+ 2211 1062
CHEXA 1188 2 124 1601 2211 1062 128 1605
+ 2213 1064
CHEXA 1189 2 128 1605 2213 1064 132 1609
+ 2215 1066
CHEXA 1190 2 132 1609 2215 1066 136 1613
+ 2217 1068
CHEXA 1191 2 136 1613 2217 1068 140 1617
+ 2219 1070
CHEXA 1192 2 140 1617 2219 1070 144 1621
+ 2221 1072
CHEXA 1193 2 144 1621 2221 1072 148 1625
+ 2223 1074
CHEXA 1194 2 148 1625 2223 1074 152 1629
+ 2225 1076
CHEXA 1195 2 152 1629 2225 1076 156 1633
+ 2227 1078
CHEXA 1196 2 156 1633 2227 1078 160 1637
+ 2229 1080
CHEXA 1197 2 160 1637 2229 1080 164 1641
+ 2231 1082
CHEXA 1198 2 164 1641 2231 1082 168 1645
+ 2233 1084
CHEXA 1199 2 168 1645 2233 1084 172 1649
+ 2235 1086
CHEXA 1200 2 172 1649 2235 1086 176 1653
+ 2237 1088
CHEXA 1201 2 176 1653 2237 1088 180 1657
+ 2239 1090
CHEXA 1202 2 180 1657 2239 1090 184 1661
+ 2241 1092
CHEXA 1203 2 184 1661 2241 1092 188 1665
+ 2243 1094
CHEXA 1204 2 188 1665 2243 1094 192 1669
+ 2245 1096
CHEXA 1205 2 192 1669 2245 1096 196 1673
+ 2247 1098
CHEXA 1206 2 196 1673 2247 1098 200 1677
+ 2249 1100
CHEXA 1287 2 200 1677 2249 1100 524 2001
+ 2411 1262
CHEXA 1288 2 524 2001 2411 1262 528 2005
+ 2413 1264
CHEXA 1289 2 528 2005 2413 1264 532 2009
+ 2415 1266
CHEXA 1290 2 532 2009 2415 1266 536 2013
+ 2417 1268
CHEXA 1291 2 536 2013 2417 1268 540 2017
+ 2419 1270
CHEXA 1292 2 540 2017 2419 1270 544 2021
+ 2421 1272
CHEXA 1293 2 544 2021 2421 1272 548 2025
+ 2423 1274
CHEXA 1294 2 548 2025 2423 1274 552 2029
+ 2425 1276
CHEXA 1295 2 552 2029 2425 1276 556 2033
+ 2427 1278
CHEXA 1296 2 556 2033 2427 1278 560 2037
+ 2429 1280
CHEXA 1297 2 560 2037 2429 1280 564 2041
+ 2431 1282
CHEXA 1298 2 564 2041 2431 1282 568 2045
+ 2433 1284
CHEXA 1299 2 568 2045 2433 1284 572 2049
+ 2435 1286
CHEXA 1300 2 572 2049 2435 1286 576 2053
+ 2437 1288

1446 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 1301 2 576 2053 2437 1288 580 2057
+ 2439 1290
CHEXA 1302 2 580 2057 2439 1290 584 2061
+ 2441 1292
CHEXA 1303 2 584 2061 2441 1292 588 2065
+ 2443 1294
CHEXA 1304 2 588 2065 2443 1294 592 2069
+ 2445 1296
CHEXA 1305 2 592 2069 2445 1296 596 2073
+ 2447 1298
CHEXA 1306 2 596 2073 2447 1298 600 2077
+ 2449 1300
CHEXA 1307 2 600 2077 2449 1300 604 2081
+ 2451 1302
CHEXA 1308 2 604 2081 2451 1302 608 2085
+ 2453 1304
CHEXA 1309 2 608 2085 2453 1304 612 2089
+ 2455 1306
CHEXA 1310 2 612 2089 2455 1306 616 2093
+ 2457 1308
CHEXA 1311 2 616 2093 2457 1308 620 2097
+ 2459 1310
CHEXA 1312 2 620 2097 2459 1310 624 2101
+ 2461 1312
CHEXA 1313 2 624 2101 2461 1312 628 2105
+ 2463 1314
CHEXA 1314 2 628 2105 2463 1314 632 2109
+ 2465 1316
CHEXA 1315 2 632 2109 2465 1316 636 2113
+ 2467 1318
CHEXA 1316 2 636 2113 2467 1318 640 2117
+ 2469 1320
CHEXA 1317 2 640 2117 2469 1320 644 2121
+ 2471 1322
CHEXA 1318 2 644 2121 2471 1322 648 2125
+ 2473 1324
CHEXA 1319 2 648 2125 2473 1324 652 2129
+ 2475 1326
CHEXA 1320 2 652 2129 2475 1326 656 2133
+ 2477 1328
CHEXA 1321 2 656 2133 2477 1328 660 2137
+ 2479 1330
CHEXA 1322 2 660 2137 2479 1330 664 2141
+ 2481 1332
CHEXA 1323 2 664 2141 2481 1332 668 2145
+ 2483 1334
CHEXA 1324 2 668 2145 2483 1334 672 2149
+ 2485 1336
CHEXA 1325 2 672 2149 2485 1336 676 2153
+ 2487 1338
CHEXA 1326 2 676 2153 2487 1338 680 2157
+ 2489 1340
CHEXA 1327 2 680 2157 2489 1340 684 2161
+ 2491 1342
CHEXA 1328 2 684 2161 2491 1342 688 2165
+ 2493 1344
CHEXA 1329 2 33 12 11 31 2494 1510
+ 35 2495
CHEXA 1330 2 2494 1510 35 2495 2496 1514
+ 39 2497
CHEXA 1331 2 2496 1514 39 2497 2498 1518
+ 43 2499
CHEXA 1332 2 2498 1518 43 2499 2500 1522
+ 47 2501
CHEXA 1333 2 2500 1522 47 2501 2502 1526
+ 51 2503
CHEXA 1334 2 2502 1526 51 2503 2504 1530
+ 55 2505
CHEXA 1335 2 2504 1530 55 2505 2506 1534

Altair Engineering OptiStruct 13.0 Reference Guide 1447

Proprietary Information of Altair Engineering


+ 59 2507
CHEXA 1336 2 2506 1534 59 2507 2508 1538
+ 63 2509
CHEXA 1337 2 2508 1538 63 2509 2510 1542
+ 67 2511
CHEXA 1338 2 2510 1542 67 2511 2512 1546
+ 71 2513
CHEXA 1339 2 2512 1546 71 2513 2514 1550
+ 75 2515
CHEXA 1340 2 2514 1550 75 2515 2516 1554
+ 79 2517
CHEXA 1341 2 2516 1554 79 2517 2518 1558
+ 83 2519
CHEXA 1342 2 2518 1558 83 2519 2520 1562
+ 87 2521
CHEXA 1343 2 2520 1562 87 2521 2522 1566
+ 91 2523
CHEXA 1344 2 2522 1566 91 2523 2524 1570
+ 95 2525
CHEXA 1345 2 2524 1570 95 2525 2526 1574
+ 99 2527
CHEXA 1346 2 2526 1574 99 2527 2528 1578
+ 103 2529
CHEXA 1347 2 2528 1578 103 2529 2530 1582
+ 107 2531
CHEXA 1348 2 2530 1582 107 2531 2532 1586
+ 111 2533
CHEXA 1349 2 2532 1586 111 2533 2534 1590
+ 115 2535
CHEXA 1350 2 2534 1590 115 2535 2536 1594
+ 119 2537
CHEXA 1351 2 2536 1594 119 2537 2538 1598
+ 123 2539
CHEXA 1352 2 2538 1598 123 2539 2540 1602
+ 127 2541
CHEXA 1353 2 2540 1602 127 2541 2542 1606
+ 131 2543
CHEXA 1354 2 2542 1606 131 2543 2544 1610
+ 135 2545
CHEXA 1355 2 2544 1610 135 2545 2546 1614
+ 139 2547
CHEXA 1356 2 2546 1614 139 2547 2548 1618
+ 143 2549
CHEXA 1357 2 2548 1618 143 2549 2550 1622
+ 147 2551
CHEXA 1358 2 2550 1622 147 2551 2552 1626
+ 151 2553
CHEXA 1359 2 2552 1626 151 2553 2554 1630
+ 155 2555
CHEXA 1360 2 2554 1630 155 2555 2556 1634
+ 159 2557
CHEXA 1361 2 2556 1634 159 2557 2558 1638
+ 163 2559
CHEXA 1362 2 2558 1638 163 2559 2560 1642
+ 167 2561
CHEXA 1363 2 2560 1642 167 2561 2562 1646
+ 171 2563
CHEXA 1364 2 2562 1646 171 2563 2564 1650
+ 175 2565
CHEXA 1365 2 2564 1650 175 2565 2566 1654
+ 179 2567
CHEXA 1366 2 2566 1654 179 2567 2568 1658
+ 183 2569
CHEXA 1367 2 2568 1658 183 2569 2570 1662
+ 187 2571
CHEXA 1368 2 2570 1662 187 2571 2572 1666
+ 191 2573
CHEXA 1369 2 2572 1666 191 2573 2574 1670
+ 195 2575

1448 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 1370 2 2574 1670 195 2575 2576 1674
+ 199 2577
CHEXA 1451 2 2576 1674 199 2577 2738 1998
+ 523 2739
CHEXA 1452 2 2738 1998 523 2739 2740 2002
+ 527 2741
CHEXA 1453 2 2740 2002 527 2741 2742 2006
+ 531 2743
CHEXA 1454 2 2742 2006 531 2743 2744 2010
+ 535 2745
CHEXA 1455 2 2744 2010 535 2745 2746 2014
+ 539 2747
CHEXA 1456 2 2746 2014 539 2747 2748 2018
+ 543 2749
CHEXA 1457 2 2748 2018 543 2749 2750 2022
+ 547 2751
CHEXA 1458 2 2750 2022 547 2751 2752 2026
+ 551 2753
CHEXA 1459 2 2752 2026 551 2753 2754 2030
+ 555 2755
CHEXA 1460 2 2754 2030 555 2755 2756 2034
+ 559 2757
CHEXA 1461 2 2756 2034 559 2757 2758 2038
+ 563 2759
CHEXA 1462 2 2758 2038 563 2759 2760 2042
+ 567 2761
CHEXA 1463 2 2760 2042 567 2761 2762 2046
+ 571 2763
CHEXA 1464 2 2762 2046 571 2763 2764 2050
+ 575 2765
CHEXA 1465 2 2764 2050 575 2765 2766 2054
+ 579 2767
CHEXA 1466 2 2766 2054 579 2767 2768 2058
+ 583 2769
CHEXA 1467 2 2768 2058 583 2769 2770 2062
+ 587 2771
CHEXA 1468 2 2770 2062 587 2771 2772 2066
+ 591 2773
CHEXA 1469 2 2772 2066 591 2773 2774 2070
+ 595 2775
CHEXA 1470 2 2774 2070 595 2775 2776 2074
+ 599 2777
CHEXA 1471 2 2776 2074 599 2777 2778 2078
+ 603 2779
CHEXA 1472 2 2778 2078 603 2779 2780 2082
+ 607 2781
CHEXA 1473 2 2780 2082 607 2781 2782 2086
+ 611 2783
CHEXA 1474 2 2782 2086 611 2783 2784 2090
+ 615 2785
CHEXA 1475 2 2784 2090 615 2785 2786 2094
+ 619 2787
CHEXA 1476 2 2786 2094 619 2787 2788 2098
+ 623 2789
CHEXA 1477 2 2788 2098 623 2789 2790 2102
+ 627 2791
CHEXA 1478 2 2790 2102 627 2791 2792 2106
+ 631 2793
CHEXA 1479 2 2792 2106 631 2793 2794 2110
+ 635 2795
CHEXA 1480 2 2794 2110 635 2795 2796 2114
+ 639 2797
CHEXA 1481 2 2796 2114 639 2797 2798 2118
+ 643 2799
CHEXA 1482 2 2798 2118 643 2799 2800 2122
+ 647 2801
CHEXA 1483 2 2800 2122 647 2801 2802 2126
+ 651 2803
CHEXA 1484 2 2802 2126 651 2803 2804 2130

Altair Engineering OptiStruct 13.0 Reference Guide 1449

Proprietary Information of Altair Engineering


+ 655 2805
CHEXA 1485 2 2804 2130 655 2805 2806 2134
+ 659 2807
CHEXA 1486 2 2806 2134 659 2807 2808 2138
+ 663 2809
CHEXA 1487 2 2808 2138 663 2809 2810 2142
+ 667 2811
CHEXA 1488 2 2810 2142 667 2811 2812 2146
+ 671 2813
CHEXA 1489 2 2812 2146 671 2813 2814 2150
+ 675 2815
CHEXA 1490 2 2814 2150 675 2815 2816 2154
+ 679 2817
CHEXA 1491 2 2816 2154 679 2817 2818 2158
+ 683 2819
CHEXA 1492 2 2818 2158 683 2819 2820 2162
+ 687 2821
CHEXA 1493 2 30 13 12 33 2822 1511
+ 1510 2494
CHEXA 1494 2 2822 1511 1510 2494 2823 1515
+ 1514 2496
CHEXA 1495 2 2823 1515 1514 2496 2824 1519
+ 1518 2498
CHEXA 1496 2 2824 1519 1518 2498 2825 1523
+ 1522 2500
CHEXA 1497 2 2825 1523 1522 2500 2826 1527
+ 1526 2502
CHEXA 1498 2 2826 1527 1526 2502 2827 1531
+ 1530 2504
CHEXA 1499 2 2827 1531 1530 2504 2828 1535
+ 1534 2506
CHEXA 1500 2 2828 1535 1534 2506 2829 1539
+ 1538 2508
CHEXA 1501 2 2829 1539 1538 2508 2830 1543
+ 1542 2510
CHEXA 1502 2 2830 1543 1542 2510 2831 1547
+ 1546 2512
CHEXA 1503 2 2831 1547 1546 2512 2832 1551
+ 1550 2514
CHEXA 1504 2 2832 1551 1550 2514 2833 1555
+ 1554 2516
CHEXA 1505 2 2833 1555 1554 2516 2834 1559
+ 1558 2518
CHEXA 1506 2 2834 1559 1558 2518 2835 1563
+ 1562 2520
CHEXA 1507 2 2835 1563 1562 2520 2836 1567
+ 1566 2522
CHEXA 1508 2 2836 1567 1566 2522 2837 1571
+ 1570 2524
CHEXA 1509 2 2837 1571 1570 2524 2838 1575
+ 1574 2526
CHEXA 1510 2 2838 1575 1574 2526 2839 1579
+ 1578 2528
CHEXA 1511 2 2839 1579 1578 2528 2840 1583
+ 1582 2530
CHEXA 1512 2 2840 1583 1582 2530 2841 1587
+ 1586 2532
CHEXA 1513 2 2841 1587 1586 2532 2842 1591
+ 1590 2534
CHEXA 1514 2 2842 1591 1590 2534 2843 1595
+ 1594 2536
CHEXA 1515 2 2843 1595 1594 2536 2844 1599
+ 1598 2538
CHEXA 1516 2 2844 1599 1598 2538 2845 1603
+ 1602 2540
CHEXA 1517 2 2845 1603 1602 2540 2846 1607
+ 1606 2542
CHEXA 1518 2 2846 1607 1606 2542 2847 1611
+ 1610 2544

1450 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 1519 2 2847 1611 1610 2544 2848 1615
+ 1614 2546
CHEXA 1520 2 2848 1615 1614 2546 2849 1619
+ 1618 2548
CHEXA 1521 2 2849 1619 1618 2548 2850 1623
+ 1622 2550
CHEXA 1522 2 2850 1623 1622 2550 2851 1627
+ 1626 2552
CHEXA 1523 2 2851 1627 1626 2552 2852 1631
+ 1630 2554
CHEXA 1524 2 2852 1631 1630 2554 2853 1635
+ 1634 2556
CHEXA 1525 2 2853 1635 1634 2556 2854 1639
+ 1638 2558
CHEXA 1526 2 2854 1639 1638 2558 2855 1643
+ 1642 2560
CHEXA 1527 2 2855 1643 1642 2560 2856 1647
+ 1646 2562
CHEXA 1528 2 2856 1647 1646 2562 2857 1651
+ 1650 2564
CHEXA 1529 2 2857 1651 1650 2564 2858 1655
+ 1654 2566
CHEXA 1530 2 2858 1655 1654 2566 2859 1659
+ 1658 2568
CHEXA 1531 2 2859 1659 1658 2568 2860 1663
+ 1662 2570
CHEXA 1532 2 2860 1663 1662 2570 2861 1667
+ 1666 2572
CHEXA 1533 2 2861 1667 1666 2572 2862 1671
+ 1670 2574
CHEXA 1534 2 2862 1671 1670 2574 2863 1675
+ 1674 2576
CHEXA 1615 2 2863 1675 1674 2576 2944 1999
+ 1998 2738
CHEXA 1616 2 2944 1999 1998 2738 2945 2003
+ 2002 2740
CHEXA 1617 2 2945 2003 2002 2740 2946 2007
+ 2006 2742
CHEXA 1618 2 2946 2007 2006 2742 2947 2011
+ 2010 2744
CHEXA 1619 2 2947 2011 2010 2744 2948 2015
+ 2014 2746
CHEXA 1620 2 2948 2015 2014 2746 2949 2019
+ 2018 2748
CHEXA 1621 2 2949 2019 2018 2748 2950 2023
+ 2022 2750
CHEXA 1622 2 2950 2023 2022 2750 2951 2027
+ 2026 2752
CHEXA 1623 2 2951 2027 2026 2752 2952 2031
+ 2030 2754
CHEXA 1624 2 2952 2031 2030 2754 2953 2035
+ 2034 2756
CHEXA 1625 2 2953 2035 2034 2756 2954 2039
+ 2038 2758
CHEXA 1626 2 2954 2039 2038 2758 2955 2043
+ 2042 2760
CHEXA 1627 2 2955 2043 2042 2760 2956 2047
+ 2046 2762
CHEXA 1628 2 2956 2047 2046 2762 2957 2051
+ 2050 2764
CHEXA 1629 2 2957 2051 2050 2764 2958 2055
+ 2054 2766
CHEXA 1630 2 2958 2055 2054 2766 2959 2059
+ 2058 2768
CHEXA 1631 2 2959 2059 2058 2768 2960 2063
+ 2062 2770
CHEXA 1632 2 2960 2063 2062 2770 2961 2067
+ 2066 2772
CHEXA 1633 2 2961 2067 2066 2772 2962 2071

Altair Engineering OptiStruct 13.0 Reference Guide 1451

Proprietary Information of Altair Engineering


+ 2070 2774
CHEXA 1634 2 2962 2071 2070 2774 2963 2075
+ 2074 2776
CHEXA 1635 2 2963 2075 2074 2776 2964 2079
+ 2078 2778
CHEXA 1636 2 2964 2079 2078 2778 2965 2083
+ 2082 2780
CHEXA 1637 2 2965 2083 2082 2780 2966 2087
+ 2086 2782
CHEXA 1638 2 2966 2087 2086 2782 2967 2091
+ 2090 2784
CHEXA 1639 2 2967 2091 2090 2784 2968 2095
+ 2094 2786
CHEXA 1640 2 2968 2095 2094 2786 2969 2099
+ 2098 2788
CHEXA 1641 2 2969 2099 2098 2788 2970 2103
+ 2102 2790
CHEXA 1642 2 2970 2103 2102 2790 2971 2107
+ 2106 2792
CHEXA 1643 2 2971 2107 2106 2792 2972 2111
+ 2110 2794
CHEXA 1644 2 2972 2111 2110 2794 2973 2115
+ 2114 2796
CHEXA 1645 2 2973 2115 2114 2796 2974 2119
+ 2118 2798
CHEXA 1646 2 2974 2119 2118 2798 2975 2123
+ 2122 2800
CHEXA 1647 2 2975 2123 2122 2800 2976 2127
+ 2126 2802
CHEXA 1648 2 2976 2127 2126 2802 2977 2131
+ 2130 2804
CHEXA 1649 2 2977 2131 2130 2804 2978 2135
+ 2134 2806
CHEXA 1650 2 2978 2135 2134 2806 2979 2139
+ 2138 2808
CHEXA 1651 2 2979 2139 2138 2808 2980 2143
+ 2142 2810
CHEXA 1652 2 2980 2143 2142 2810 2981 2147
+ 2146 2812
CHEXA 1653 2 2981 2147 2146 2812 2982 2151
+ 2150 2814
CHEXA 1654 2 2982 2151 2150 2814 2983 2155
+ 2154 2816
CHEXA 1655 2 2983 2155 2154 2816 2984 2159
+ 2158 2818
CHEXA 1656 2 2984 2159 2158 2818 2985 2163
+ 2162 2820
CHEXA 1657 2 28 33 31 27 2986 2494
+ 2495 2987
CHEXA 1658 2 2986 2494 2495 2987 2988 2496
+ 2497 2989
CHEXA 1659 2 2988 2496 2497 2989 2990 2498
+ 2499 2991
CHEXA 1660 2 2990 2498 2499 2991 2992 2500
+ 2501 2993
CHEXA 1661 2 2992 2500 2501 2993 2994 2502
+ 2503 2995
CHEXA 1662 2 2994 2502 2503 2995 2996 2504
+ 2505 2997
CHEXA 1663 2 2996 2504 2505 2997 2998 2506
+ 2507 2999
CHEXA 1664 2 2998 2506 2507 2999 3000 2508
+ 2509 3001
CHEXA 1665 2 3000 2508 2509 3001 3002 2510
+ 2511 3003
CHEXA 1666 2 3002 2510 2511 3003 3004 2512
+ 2513 3005
CHEXA 1667 2 3004 2512 2513 3005 3006 2514
+ 2515 3007

1452 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 1668 2 3006 2514 2515 3007 3008 2516
+ 2517 3009
CHEXA 1669 2 3008 2516 2517 3009 3010 2518
+ 2519 3011
CHEXA 1670 2 3010 2518 2519 3011 3012 2520
+ 2521 3013
CHEXA 1671 2 3012 2520 2521 3013 3014 2522
+ 2523 3015
CHEXA 1672 2 3014 2522 2523 3015 3016 2524
+ 2525 3017
CHEXA 1673 2 3016 2524 2525 3017 3018 2526
+ 2527 3019
CHEXA 1674 2 3018 2526 2527 3019 3020 2528
+ 2529 3021
CHEXA 1675 2 3020 2528 2529 3021 3022 2530
+ 2531 3023
CHEXA 1676 2 3022 2530 2531 3023 3024 2532
+ 2533 3025
CHEXA 1677 2 3024 2532 2533 3025 3026 2534
+ 2535 3027
CHEXA 1678 2 3026 2534 2535 3027 3028 2536
+ 2537 3029
CHEXA 1679 2 3028 2536 2537 3029 3030 2538
+ 2539 3031
CHEXA 1680 2 3030 2538 2539 3031 3032 2540
+ 2541 3033
CHEXA 1681 2 3032 2540 2541 3033 3034 2542
+ 2543 3035
CHEXA 1682 2 3034 2542 2543 3035 3036 2544
+ 2545 3037
CHEXA 1683 2 3036 2544 2545 3037 3038 2546
+ 2547 3039
CHEXA 1684 2 3038 2546 2547 3039 3040 2548
+ 2549 3041
CHEXA 1685 2 3040 2548 2549 3041 3042 2550
+ 2551 3043
CHEXA 1686 2 3042 2550 2551 3043 3044 2552
+ 2553 3045
CHEXA 1687 2 3044 2552 2553 3045 3046 2554
+ 2555 3047
CHEXA 1688 2 3046 2554 2555 3047 3048 2556
+ 2557 3049
CHEXA 1689 2 3048 2556 2557 3049 3050 2558
+ 2559 3051
CHEXA 1690 2 3050 2558 2559 3051 3052 2560
+ 2561 3053
CHEXA 1691 2 3052 2560 2561 3053 3054 2562
+ 2563 3055
CHEXA 1692 2 3054 2562 2563 3055 3056 2564
+ 2565 3057
CHEXA 1693 2 3056 2564 2565 3057 3058 2566
+ 2567 3059
CHEXA 1694 2 3058 2566 2567 3059 3060 2568
+ 2569 3061
CHEXA 1695 2 3060 2568 2569 3061 3062 2570
+ 2571 3063
CHEXA 1696 2 3062 2570 2571 3063 3064 2572
+ 2573 3065
CHEXA 1697 2 3064 2572 2573 3065 3066 2574
+ 2575 3067
CHEXA 1698 2 3066 2574 2575 3067 3068 2576
+ 2577 3069
CHEXA 1779 2 3068 2576 2577 3069 3230 2738
+ 2739 3231
CHEXA 1780 2 3230 2738 2739 3231 3232 2740
+ 2741 3233
CHEXA 1781 2 3232 2740 2741 3233 3234 2742
+ 2743 3235
CHEXA 1782 2 3234 2742 2743 3235 3236 2744

Altair Engineering OptiStruct 13.0 Reference Guide 1453

Proprietary Information of Altair Engineering


+ 2745 3237
CHEXA 1783 2 3236 2744 2745 3237 3238 2746
+ 2747 3239
CHEXA 1784 2 3238 2746 2747 3239 3240 2748
+ 2749 3241
CHEXA 1785 2 3240 2748 2749 3241 3242 2750
+ 2751 3243
CHEXA 1786 2 3242 2750 2751 3243 3244 2752
+ 2753 3245
CHEXA 1787 2 3244 2752 2753 3245 3246 2754
+ 2755 3247
CHEXA 1788 2 3246 2754 2755 3247 3248 2756
+ 2757 3249
CHEXA 1789 2 3248 2756 2757 3249 3250 2758
+ 2759 3251
CHEXA 1790 2 3250 2758 2759 3251 3252 2760
+ 2761 3253
CHEXA 1791 2 3252 2760 2761 3253 3254 2762
+ 2763 3255
CHEXA 1792 2 3254 2762 2763 3255 3256 2764
+ 2765 3257
CHEXA 1793 2 3256 2764 2765 3257 3258 2766
+ 2767 3259
CHEXA 1794 2 3258 2766 2767 3259 3260 2768
+ 2769 3261
CHEXA 1795 2 3260 2768 2769 3261 3262 2770
+ 2771 3263
CHEXA 1796 2 3262 2770 2771 3263 3264 2772
+ 2773 3265
CHEXA 1797 2 3264 2772 2773 3265 3266 2774
+ 2775 3267
CHEXA 1798 2 3266 2774 2775 3267 3268 2776
+ 2777 3269
CHEXA 1799 2 3268 2776 2777 3269 3270 2778
+ 2779 3271
CHEXA 1800 2 3270 2778 2779 3271 3272 2780
+ 2781 3273
CHEXA 1801 2 3272 2780 2781 3273 3274 2782
+ 2783 3275
CHEXA 1802 2 3274 2782 2783 3275 3276 2784
+ 2785 3277
CHEXA 1803 2 3276 2784 2785 3277 3278 2786
+ 2787 3279
CHEXA 1804 2 3278 2786 2787 3279 3280 2788
+ 2789 3281
CHEXA 1805 2 3280 2788 2789 3281 3282 2790
+ 2791 3283
CHEXA 1806 2 3282 2790 2791 3283 3284 2792
+ 2793 3285
CHEXA 1807 2 3284 2792 2793 3285 3286 2794
+ 2795 3287
CHEXA 1808 2 3286 2794 2795 3287 3288 2796
+ 2797 3289
CHEXA 1809 2 3288 2796 2797 3289 3290 2798
+ 2799 3291
CHEXA 1810 2 3290 2798 2799 3291 3292 2800
+ 2801 3293
CHEXA 1811 2 3292 2800 2801 3293 3294 2802
+ 2803 3295
CHEXA 1812 2 3294 2802 2803 3295 3296 2804
+ 2805 3297
CHEXA 1813 2 3296 2804 2805 3297 3298 2806
+ 2807 3299
CHEXA 1814 2 3298 2806 2807 3299 3300 2808
+ 2809 3301
CHEXA 1815 2 3300 2808 2809 3301 3302 2810
+ 2811 3303
CHEXA 1816 2 3302 2810 2811 3303 3304 2812
+ 2813 3305

1454 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 1817 2 3304 2812 2813 3305 3306 2814
+ 2815 3307
CHEXA 1818 2 3306 2814 2815 3307 3308 2816
+ 2817 3309
CHEXA 1819 2 3308 2816 2817 3309 3310 2818
+ 2819 3311
CHEXA 1820 2 3310 2818 2819 3311 3312 2820
+ 2821 3313
CHEXA 1821 2 29 30 33 28 3314 2822
+ 2494 2986
CHEXA 1822 2 3314 2822 2494 2986 3315 2823
+ 2496 2988
CHEXA 1823 2 3315 2823 2496 2988 3316 2824
+ 2498 2990
CHEXA 1824 2 3316 2824 2498 2990 3317 2825
+ 2500 2992
CHEXA 1825 2 3317 2825 2500 2992 3318 2826
+ 2502 2994
CHEXA 1826 2 3318 2826 2502 2994 3319 2827
+ 2504 2996
CHEXA 1827 2 3319 2827 2504 2996 3320 2828
+ 2506 2998
CHEXA 1828 2 3320 2828 2506 2998 3321 2829
+ 2508 3000
CHEXA 1829 2 3321 2829 2508 3000 3322 2830
+ 2510 3002
CHEXA 1830 2 3322 2830 2510 3002 3323 2831
+ 2512 3004
CHEXA 1831 2 3323 2831 2512 3004 3324 2832
+ 2514 3006
CHEXA 1832 2 3324 2832 2514 3006 3325 2833
+ 2516 3008
CHEXA 1833 2 3325 2833 2516 3008 3326 2834
+ 2518 3010
CHEXA 1834 2 3326 2834 2518 3010 3327 2835
+ 2520 3012
CHEXA 1835 2 3327 2835 2520 3012 3328 2836
+ 2522 3014
CHEXA 1836 2 3328 2836 2522 3014 3329 2837
+ 2524 3016
CHEXA 1837 2 3329 2837 2524 3016 3330 2838
+ 2526 3018
CHEXA 1838 2 3330 2838 2526 3018 3331 2839
+ 2528 3020
CHEXA 1839 2 3331 2839 2528 3020 3332 2840
+ 2530 3022
CHEXA 1840 2 3332 2840 2530 3022 3333 2841
+ 2532 3024
CHEXA 1841 2 3333 2841 2532 3024 3334 2842
+ 2534 3026
CHEXA 1842 2 3334 2842 2534 3026 3335 2843
+ 2536 3028
CHEXA 1843 2 3335 2843 2536 3028 3336 2844
+ 2538 3030
CHEXA 1844 2 3336 2844 2538 3030 3337 2845
+ 2540 3032
CHEXA 1845 2 3337 2845 2540 3032 3338 2846
+ 2542 3034
CHEXA 1846 2 3338 2846 2542 3034 3339 2847
+ 2544 3036
CHEXA 1847 2 3339 2847 2544 3036 3340 2848
+ 2546 3038
CHEXA 1848 2 3340 2848 2546 3038 3341 2849
+ 2548 3040
CHEXA 1849 2 3341 2849 2548 3040 3342 2850
+ 2550 3042
CHEXA 1850 2 3342 2850 2550 3042 3343 2851
+ 2552 3044
CHEXA 1851 2 3343 2851 2552 3044 3344 2852

Altair Engineering OptiStruct 13.0 Reference Guide 1455

Proprietary Information of Altair Engineering


+ 2554 3046
CHEXA 1852 2 3344 2852 2554 3046 3345 2853
+ 2556 3048
CHEXA 1853 2 3345 2853 2556 3048 3346 2854
+ 2558 3050
CHEXA 1854 2 3346 2854 2558 3050 3347 2855
+ 2560 3052
CHEXA 1855 2 3347 2855 2560 3052 3348 2856
+ 2562 3054
CHEXA 1856 2 3348 2856 2562 3054 3349 2857
+ 2564 3056
CHEXA 1857 2 3349 2857 2564 3056 3350 2858
+ 2566 3058
CHEXA 1858 2 3350 2858 2566 3058 3351 2859
+ 2568 3060
CHEXA 1859 2 3351 2859 2568 3060 3352 2860
+ 2570 3062
CHEXA 1860 2 3352 2860 2570 3062 3353 2861
+ 2572 3064
CHEXA 1861 2 3353 2861 2572 3064 3354 2862
+ 2574 3066
CHEXA 1862 2 3354 2862 2574 3066 3355 2863
+ 2576 3068
CHEXA 1943 2 3355 2863 2576 3068 3436 2944
+ 2738 3230
CHEXA 1944 2 3436 2944 2738 3230 3437 2945
+ 2740 3232
CHEXA 1945 2 3437 2945 2740 3232 3438 2946
+ 2742 3234
CHEXA 1946 2 3438 2946 2742 3234 3439 2947
+ 2744 3236
CHEXA 1947 2 3439 2947 2744 3236 3440 2948
+ 2746 3238
CHEXA 1948 2 3440 2948 2746 3238 3441 2949
+ 2748 3240
CHEXA 1949 2 3441 2949 2748 3240 3442 2950
+ 2750 3242
CHEXA 1950 2 3442 2950 2750 3242 3443 2951
+ 2752 3244
CHEXA 1951 2 3443 2951 2752 3244 3444 2952
+ 2754 3246
CHEXA 1952 2 3444 2952 2754 3246 3445 2953
+ 2756 3248
CHEXA 1953 2 3445 2953 2756 3248 3446 2954
+ 2758 3250
CHEXA 1954 2 3446 2954 2758 3250 3447 2955
+ 2760 3252
CHEXA 1955 2 3447 2955 2760 3252 3448 2956
+ 2762 3254
CHEXA 1956 2 3448 2956 2762 3254 3449 2957
+ 2764 3256
CHEXA 1957 2 3449 2957 2764 3256 3450 2958
+ 2766 3258
CHEXA 1958 2 3450 2958 2766 3258 3451 2959
+ 2768 3260
CHEXA 1959 2 3451 2959 2768 3260 3452 2960
+ 2770 3262
CHEXA 1960 2 3452 2960 2770 3262 3453 2961
+ 2772 3264
CHEXA 1961 2 3453 2961 2772 3264 3454 2962
+ 2774 3266
CHEXA 1962 2 3454 2962 2774 3266 3455 2963
+ 2776 3268
CHEXA 1963 2 3455 2963 2776 3268 3456 2964
+ 2778 3270
CHEXA 1964 2 3456 2964 2778 3270 3457 2965
+ 2780 3272
CHEXA 1965 2 3457 2965 2780 3272 3458 2966
+ 2782 3274

1456 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 1966 2 3458 2966 2782 3274 3459 2967
+ 2784 3276
CHEXA 1967 2 3459 2967 2784 3276 3460 2968
+ 2786 3278
CHEXA 1968 2 3460 2968 2786 3278 3461 2969
+ 2788 3280
CHEXA 1969 2 3461 2969 2788 3280 3462 2970
+ 2790 3282
CHEXA 1970 2 3462 2970 2790 3282 3463 2971
+ 2792 3284
CHEXA 1971 2 3463 2971 2792 3284 3464 2972
+ 2794 3286
CHEXA 1972 2 3464 2972 2794 3286 3465 2973
+ 2796 3288
CHEXA 1973 2 3465 2973 2796 3288 3466 2974
+ 2798 3290
CHEXA 1974 2 3466 2974 2798 3290 3467 2975
+ 2800 3292
CHEXA 1975 2 3467 2975 2800 3292 3468 2976
+ 2802 3294
CHEXA 1976 2 3468 2976 2802 3294 3469 2977
+ 2804 3296
CHEXA 1977 2 3469 2977 2804 3296 3470 2978
+ 2806 3298
CHEXA 1978 2 3470 2978 2806 3298 3471 2979
+ 2808 3300
CHEXA 1979 2 3471 2979 2808 3300 3472 2980
+ 2810 3302
CHEXA 1980 2 3472 2980 2810 3302 3473 2981
+ 2812 3304
CHEXA 1981 2 3473 2981 2812 3304 3474 2982
+ 2814 3306
CHEXA 1982 2 3474 2982 2814 3306 3475 2983
+ 2816 3308
CHEXA 1983 2 3475 2983 2816 3308 3476 2984
+ 2818 3310
CHEXA 1984 2 3476 2984 2818 3310 3477 2985
+ 2820 3312
CHEXA 1985 2 32 10 9 24 3478 34
+ 690 3479
CHEXA 1986 2 3478 34 690 3479 3480 38
+ 692 3481
CHEXA 1987 2 3480 38 692 3481 3482 42
+ 694 3483
CHEXA 1988 2 3482 42 694 3483 3484 46
+ 696 3485
CHEXA 1989 2 3484 46 696 3485 3486 50
+ 698 3487
CHEXA 1990 2 3486 50 698 3487 3488 54
+ 700 3489
CHEXA 1991 2 3488 54 700 3489 3490 58
+ 702 3491
CHEXA 1992 2 3490 58 702 3491 3492 62
+ 704 3493
CHEXA 1993 2 3492 62 704 3493 3494 66
+ 706 3495
CHEXA 1994 2 3494 66 706 3495 3496 70
+ 708 3497
CHEXA 1995 2 3496 70 708 3497 3498 74
+ 710 3499
CHEXA 1996 2 3498 74 710 3499 3500 78
+ 712 3501
CHEXA 1997 2 3500 78 712 3501 3502 82
+ 714 3503
CHEXA 1998 2 3502 82 714 3503 3504 86
+ 716 3505
CHEXA 1999 2 3504 86 716 3505 3506 90
+ 718 3507
CHEXA 2000 2 3506 90 718 3507 3508 94

Altair Engineering OptiStruct 13.0 Reference Guide 1457

Proprietary Information of Altair Engineering


+ 720 3509
CHEXA 2001 2 3508 94 720 3509 3510 98
+ 722 3511
CHEXA 2002 2 3510 98 722 3511 3512 102
+ 724 3513
CHEXA 2003 2 3512 102 724 3513 3514 106
+ 726 3515
CHEXA 2004 2 3514 106 726 3515 3516 110
+ 728 3517
CHEXA 2005 2 3516 110 728 3517 3518 114
+ 730 3519
CHEXA 2006 2 3518 114 730 3519 3520 118
+ 732 3521
CHEXA 2007 2 3520 118 732 3521 3522 122
+ 734 3523
CHEXA 2008 2 3522 122 734 3523 3524 126
+ 736 3525
CHEXA 2009 2 3524 126 736 3525 3526 130
+ 738 3527
CHEXA 2010 2 3526 130 738 3527 3528 134
+ 740 3529
CHEXA 2011 2 3528 134 740 3529 3530 138
+ 742 3531
CHEXA 2012 2 3530 138 742 3531 3532 142
+ 744 3533
CHEXA 2013 2 3532 142 744 3533 3534 146
+ 746 3535
CHEXA 2014 2 3534 146 746 3535 3536 150
+ 748 3537
CHEXA 2015 2 3536 150 748 3537 3538 154
+ 750 3539
CHEXA 2016 2 3538 154 750 3539 3540 158
+ 752 3541
CHEXA 2017 2 3540 158 752 3541 3542 162
+ 754 3543
CHEXA 2018 2 3542 162 754 3543 3544 166
+ 756 3545
CHEXA 2019 2 3544 166 756 3545 3546 170
+ 758 3547
CHEXA 2020 2 3546 170 758 3547 3548 174
+ 760 3549
CHEXA 2021 2 3548 174 760 3549 3550 178
+ 762 3551
CHEXA 2022 2 3550 178 762 3551 3552 182
+ 764 3553
CHEXA 2023 2 3552 182 764 3553 3554 186
+ 766 3555
CHEXA 2024 2 3554 186 766 3555 3556 190
+ 768 3557
CHEXA 2025 2 3556 190 768 3557 3558 194
+ 770 3559
CHEXA 2026 2 3558 194 770 3559 3560 198
+ 772 3561
CHEXA 2107 2 3560 198 772 3561 3722 522
+ 934 3723
CHEXA 2108 2 3722 522 934 3723 3724 526
+ 936 3725
CHEXA 2109 2 3724 526 936 3725 3726 530
+ 938 3727
CHEXA 2110 2 3726 530 938 3727 3728 534
+ 940 3729
CHEXA 2111 2 3728 534 940 3729 3730 538
+ 942 3731
CHEXA 2112 2 3730 538 942 3731 3732 542
+ 944 3733
CHEXA 2113 2 3732 542 944 3733 3734 546
+ 946 3735
CHEXA 2114 2 3734 546 946 3735 3736 550
+ 948 3737

1458 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 2115 2 3736 550 948 3737 3738 554
+ 950 3739
CHEXA 2116 2 3738 554 950 3739 3740 558
+ 952 3741
CHEXA 2117 2 3740 558 952 3741 3742 562
+ 954 3743
CHEXA 2118 2 3742 562 954 3743 3744 566
+ 956 3745
CHEXA 2119 2 3744 566 956 3745 3746 570
+ 958 3747
CHEXA 2120 2 3746 570 958 3747 3748 574
+ 960 3749
CHEXA 2121 2 3748 574 960 3749 3750 578
+ 962 3751
CHEXA 2122 2 3750 578 962 3751 3752 582
+ 964 3753
CHEXA 2123 2 3752 582 964 3753 3754 586
+ 966 3755
CHEXA 2124 2 3754 586 966 3755 3756 590
+ 968 3757
CHEXA 2125 2 3756 590 968 3757 3758 594
+ 970 3759
CHEXA 2126 2 3758 594 970 3759 3760 598
+ 972 3761
CHEXA 2127 2 3760 598 972 3761 3762 602
+ 974 3763
CHEXA 2128 2 3762 602 974 3763 3764 606
+ 976 3765
CHEXA 2129 2 3764 606 976 3765 3766 610
+ 978 3767
CHEXA 2130 2 3766 610 978 3767 3768 614
+ 980 3769
CHEXA 2131 2 3768 614 980 3769 3770 618
+ 982 3771
CHEXA 2132 2 3770 618 982 3771 3772 622
+ 984 3773
CHEXA 2133 2 3772 622 984 3773 3774 626
+ 986 3775
CHEXA 2134 2 3774 626 986 3775 3776 630
+ 988 3777
CHEXA 2135 2 3776 630 988 3777 3778 634
+ 990 3779
CHEXA 2136 2 3778 634 990 3779 3780 638
+ 992 3781
CHEXA 2137 2 3780 638 992 3781 3782 642
+ 994 3783
CHEXA 2138 2 3782 642 994 3783 3784 646
+ 996 3785
CHEXA 2139 2 3784 646 996 3785 3786 650
+ 998 3787
CHEXA 2140 2 3786 650 998 3787 3788 654
+ 1000 3789
CHEXA 2141 2 3788 654 1000 3789 3790 658
+ 1002 3791
CHEXA 2142 2 3790 658 1002 3791 3792 662
+ 1004 3793
CHEXA 2143 2 3792 662 1004 3793 3794 666
+ 1006 3795
CHEXA 2144 2 3794 666 1006 3795 3796 670
+ 1008 3797
CHEXA 2145 2 3796 670 1008 3797 3798 674
+ 1010 3799
CHEXA 2146 2 3798 674 1010 3799 3800 678
+ 1012 3801
CHEXA 2147 2 3800 678 1012 3801 3802 682
+ 1014 3803
CHEXA 2148 2 3802 682 1014 3803 3804 686
+ 1016 3805
CHEXA 2149 2 31 11 10 32 2495 35

Altair Engineering OptiStruct 13.0 Reference Guide 1459

Proprietary Information of Altair Engineering


+ 34 3478
CHEXA 2150 2 2495 35 34 3478 2497 39
+ 38 3480
CHEXA 2151 2 2497 39 38 3480 2499 43
+ 42 3482
CHEXA 2152 2 2499 43 42 3482 2501 47
+ 46 3484
CHEXA 2153 2 2501 47 46 3484 2503 51
+ 50 3486
CHEXA 2154 2 2503 51 50 3486 2505 55
+ 54 3488
CHEXA 2155 2 2505 55 54 3488 2507 59
+ 58 3490
CHEXA 2156 2 2507 59 58 3490 2509 63
+ 62 3492
CHEXA 2157 2 2509 63 62 3492 2511 67
+ 66 3494
CHEXA 2158 2 2511 67 66 3494 2513 71
+ 70 3496
CHEXA 2159 2 2513 71 70 3496 2515 75
+ 74 3498
CHEXA 2160 2 2515 75 74 3498 2517 79
+ 78 3500
CHEXA 2161 2 2517 79 78 3500 2519 83
+ 82 3502
CHEXA 2162 2 2519 83 82 3502 2521 87
+ 86 3504
CHEXA 2163 2 2521 87 86 3504 2523 91
+ 90 3506
CHEXA 2164 2 2523 91 90 3506 2525 95
+ 94 3508
CHEXA 2165 2 2525 95 94 3508 2527 99
+ 98 3510
CHEXA 2166 2 2527 99 98 3510 2529 103
+ 102 3512
CHEXA 2167 2 2529 103 102 3512 2531 107
+ 106 3514
CHEXA 2168 2 2531 107 106 3514 2533 111
+ 110 3516
CHEXA 2169 2 2533 111 110 3516 2535 115
+ 114 3518
CHEXA 2170 2 2535 115 114 3518 2537 119
+ 118 3520
CHEXA 2171 2 2537 119 118 3520 2539 123
+ 122 3522
CHEXA 2172 2 2539 123 122 3522 2541 127
+ 126 3524
CHEXA 2173 2 2541 127 126 3524 2543 131
+ 130 3526
CHEXA 2174 2 2543 131 130 3526 2545 135
+ 134 3528
CHEXA 2175 2 2545 135 134 3528 2547 139
+ 138 3530
CHEXA 2176 2 2547 139 138 3530 2549 143
+ 142 3532
CHEXA 2177 2 2549 143 142 3532 2551 147
+ 146 3534
CHEXA 2178 2 2551 147 146 3534 2553 151
+ 150 3536
CHEXA 2179 2 2553 151 150 3536 2555 155
+ 154 3538
CHEXA 2180 2 2555 155 154 3538 2557 159
+ 158 3540
CHEXA 2181 2 2557 159 158 3540 2559 163
+ 162 3542
CHEXA 2182 2 2559 163 162 3542 2561 167
+ 166 3544
CHEXA 2183 2 2561 167 166 3544 2563 171
+ 170 3546

1460 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 2184 2 2563 171 170 3546 2565 175
+ 174 3548
CHEXA 2185 2 2565 175 174 3548 2567 179
+ 178 3550
CHEXA 2186 2 2567 179 178 3550 2569 183
+ 182 3552
CHEXA 2187 2 2569 183 182 3552 2571 187
+ 186 3554
CHEXA 2188 2 2571 187 186 3554 2573 191
+ 190 3556
CHEXA 2189 2 2573 191 190 3556 2575 195
+ 194 3558
CHEXA 2190 2 2575 195 194 3558 2577 199
+ 198 3560
CHEXA 2271 2 2577 199 198 3560 2739 523
+ 522 3722
CHEXA 2272 2 2739 523 522 3722 2741 527
+ 526 3724
CHEXA 2273 2 2741 527 526 3724 2743 531
+ 530 3726
CHEXA 2274 2 2743 531 530 3726 2745 535
+ 534 3728
CHEXA 2275 2 2745 535 534 3728 2747 539
+ 538 3730
CHEXA 2276 2 2747 539 538 3730 2749 543
+ 542 3732
CHEXA 2277 2 2749 543 542 3732 2751 547
+ 546 3734
CHEXA 2278 2 2751 547 546 3734 2753 551
+ 550 3736
CHEXA 2279 2 2753 551 550 3736 2755 555
+ 554 3738
CHEXA 2280 2 2755 555 554 3738 2757 559
+ 558 3740
CHEXA 2281 2 2757 559 558 3740 2759 563
+ 562 3742
CHEXA 2282 2 2759 563 562 3742 2761 567
+ 566 3744
CHEXA 2283 2 2761 567 566 3744 2763 571
+ 570 3746
CHEXA 2284 2 2763 571 570 3746 2765 575
+ 574 3748
CHEXA 2285 2 2765 575 574 3748 2767 579
+ 578 3750
CHEXA 2286 2 2767 579 578 3750 2769 583
+ 582 3752
CHEXA 2287 2 2769 583 582 3752 2771 587
+ 586 3754
CHEXA 2288 2 2771 587 586 3754 2773 591
+ 590 3756
CHEXA 2289 2 2773 591 590 3756 2775 595
+ 594 3758
CHEXA 2290 2 2775 595 594 3758 2777 599
+ 598 3760
CHEXA 2291 2 2777 599 598 3760 2779 603
+ 602 3762
CHEXA 2292 2 2779 603 602 3762 2781 607
+ 606 3764
CHEXA 2293 2 2781 607 606 3764 2783 611
+ 610 3766
CHEXA 2294 2 2783 611 610 3766 2785 615
+ 614 3768
CHEXA 2295 2 2785 615 614 3768 2787 619
+ 618 3770
CHEXA 2296 2 2787 619 618 3770 2789 623
+ 622 3772
CHEXA 2297 2 2789 623 622 3772 2791 627
+ 626 3774
CHEXA 2298 2 2791 627 626 3774 2793 631

Altair Engineering OptiStruct 13.0 Reference Guide 1461

Proprietary Information of Altair Engineering


+ 630 3776
CHEXA 2299 2 2793 631 630 3776 2795 635
+ 634 3778
CHEXA 2300 2 2795 635 634 3778 2797 639
+ 638 3780
CHEXA 2301 2 2797 639 638 3780 2799 643
+ 642 3782
CHEXA 2302 2 2799 643 642 3782 2801 647
+ 646 3784
CHEXA 2303 2 2801 647 646 3784 2803 651
+ 650 3786
CHEXA 2304 2 2803 651 650 3786 2805 655
+ 654 3788
CHEXA 2305 2 2805 655 654 3788 2807 659
+ 658 3790
CHEXA 2306 2 2807 659 658 3790 2809 663
+ 662 3792
CHEXA 2307 2 2809 663 662 3792 2811 667
+ 666 3794
CHEXA 2308 2 2811 667 666 3794 2813 671
+ 670 3796
CHEXA 2309 2 2813 671 670 3796 2815 675
+ 674 3798
CHEXA 2310 2 2815 675 674 3798 2817 679
+ 678 3800
CHEXA 2311 2 2817 679 678 3800 2819 683
+ 682 3802
CHEXA 2312 2 2819 683 682 3802 2821 687
+ 686 3804
CHEXA 2313 2 26 32 24 25 3806 3478
+ 3479 3807
CHEXA 2314 2 3806 3478 3479 3807 3808 3480
+ 3481 3809
CHEXA 2315 2 3808 3480 3481 3809 3810 3482
+ 3483 3811
CHEXA 2316 2 3810 3482 3483 3811 3812 3484
+ 3485 3813
CHEXA 2317 2 3812 3484 3485 3813 3814 3486
+ 3487 3815
CHEXA 2318 2 3814 3486 3487 3815 3816 3488
+ 3489 3817
CHEXA 2319 2 3816 3488 3489 3817 3818 3490
+ 3491 3819
CHEXA 2320 2 3818 3490 3491 3819 3820 3492
+ 3493 3821
CHEXA 2321 2 3820 3492 3493 3821 3822 3494
+ 3495 3823
CHEXA 2322 2 3822 3494 3495 3823 3824 3496
+ 3497 3825
CHEXA 2323 2 3824 3496 3497 3825 3826 3498
+ 3499 3827
CHEXA 2324 2 3826 3498 3499 3827 3828 3500
+ 3501 3829
CHEXA 2325 2 3828 3500 3501 3829 3830 3502
+ 3503 3831
CHEXA 2326 2 3830 3502 3503 3831 3832 3504
+ 3505 3833
CHEXA 2327 2 3832 3504 3505 3833 3834 3506
+ 3507 3835
CHEXA 2328 2 3834 3506 3507 3835 3836 3508
+ 3509 3837
CHEXA 2329 2 3836 3508 3509 3837 3838 3510
+ 3511 3839
CHEXA 2330 2 3838 3510 3511 3839 3840 3512
+ 3513 3841
CHEXA 2331 2 3840 3512 3513 3841 3842 3514
+ 3515 3843
CHEXA 2332 2 3842 3514 3515 3843 3844 3516
+ 3517 3845

1462 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 2333 2 3844 3516 3517 3845 3846 3518
+ 3519 3847
CHEXA 2334 2 3846 3518 3519 3847 3848 3520
+ 3521 3849
CHEXA 2335 2 3848 3520 3521 3849 3850 3522
+ 3523 3851
CHEXA 2336 2 3850 3522 3523 3851 3852 3524
+ 3525 3853
CHEXA 2337 2 3852 3524 3525 3853 3854 3526
+ 3527 3855
CHEXA 2338 2 3854 3526 3527 3855 3856 3528
+ 3529 3857
CHEXA 2339 2 3856 3528 3529 3857 3858 3530
+ 3531 3859
CHEXA 2340 2 3858 3530 3531 3859 3860 3532
+ 3533 3861
CHEXA 2341 2 3860 3532 3533 3861 3862 3534
+ 3535 3863
CHEXA 2342 2 3862 3534 3535 3863 3864 3536
+ 3537 3865
CHEXA 2343 2 3864 3536 3537 3865 3866 3538
+ 3539 3867
CHEXA 2344 2 3866 3538 3539 3867 3868 3540
+ 3541 3869
CHEXA 2345 2 3868 3540 3541 3869 3870 3542
+ 3543 3871
CHEXA 2346 2 3870 3542 3543 3871 3872 3544
+ 3545 3873
CHEXA 2347 2 3872 3544 3545 3873 3874 3546
+ 3547 3875
CHEXA 2348 2 3874 3546 3547 3875 3876 3548
+ 3549 3877
CHEXA 2349 2 3876 3548 3549 3877 3878 3550
+ 3551 3879
CHEXA 2350 2 3878 3550 3551 3879 3880 3552
+ 3553 3881
CHEXA 2351 2 3880 3552 3553 3881 3882 3554
+ 3555 3883
CHEXA 2352 2 3882 3554 3555 3883 3884 3556
+ 3557 3885
CHEXA 2353 2 3884 3556 3557 3885 3886 3558
+ 3559 3887
CHEXA 2354 2 3886 3558 3559 3887 3888 3560
+ 3561 3889
CHEXA 2435 2 3888 3560 3561 3889 4050 3722
+ 3723 4051
CHEXA 2436 2 4050 3722 3723 4051 4052 3724
+ 3725 4053
CHEXA 2437 2 4052 3724 3725 4053 4054 3726
+ 3727 4055
CHEXA 2438 2 4054 3726 3727 4055 4056 3728
+ 3729 4057
CHEXA 2439 2 4056 3728 3729 4057 4058 3730
+ 3731 4059
CHEXA 2440 2 4058 3730 3731 4059 4060 3732
+ 3733 4061
CHEXA 2441 2 4060 3732 3733 4061 4062 3734
+ 3735 4063
CHEXA 2442 2 4062 3734 3735 4063 4064 3736
+ 3737 4065
CHEXA 2443 2 4064 3736 3737 4065 4066 3738
+ 3739 4067
CHEXA 2444 2 4066 3738 3739 4067 4068 3740
+ 3741 4069
CHEXA 2445 2 4068 3740 3741 4069 4070 3742
+ 3743 4071
CHEXA 2446 2 4070 3742 3743 4071 4072 3744
+ 3745 4073
CHEXA 2447 2 4072 3744 3745 4073 4074 3746

Altair Engineering OptiStruct 13.0 Reference Guide 1463

Proprietary Information of Altair Engineering


+ 3747 4075
CHEXA 2448 2 4074 3746 3747 4075 4076 3748
+ 3749 4077
CHEXA 2449 2 4076 3748 3749 4077 4078 3750
+ 3751 4079
CHEXA 2450 2 4078 3750 3751 4079 4080 3752
+ 3753 4081
CHEXA 2451 2 4080 3752 3753 4081 4082 3754
+ 3755 4083
CHEXA 2452 2 4082 3754 3755 4083 4084 3756
+ 3757 4085
CHEXA 2453 2 4084 3756 3757 4085 4086 3758
+ 3759 4087
CHEXA 2454 2 4086 3758 3759 4087 4088 3760
+ 3761 4089
CHEXA 2455 2 4088 3760 3761 4089 4090 3762
+ 3763 4091
CHEXA 2456 2 4090 3762 3763 4091 4092 3764
+ 3765 4093
CHEXA 2457 2 4092 3764 3765 4093 4094 3766
+ 3767 4095
CHEXA 2458 2 4094 3766 3767 4095 4096 3768
+ 3769 4097
CHEXA 2459 2 4096 3768 3769 4097 4098 3770
+ 3771 4099
CHEXA 2460 2 4098 3770 3771 4099 4100 3772
+ 3773 4101
CHEXA 2461 2 4100 3772 3773 4101 4102 3774
+ 3775 4103
CHEXA 2462 2 4102 3774 3775 4103 4104 3776
+ 3777 4105
CHEXA 2463 2 4104 3776 3777 4105 4106 3778
+ 3779 4107
CHEXA 2464 2 4106 3778 3779 4107 4108 3780
+ 3781 4109
CHEXA 2465 2 4108 3780 3781 4109 4110 3782
+ 3783 4111
CHEXA 2466 2 4110 3782 3783 4111 4112 3784
+ 3785 4113
CHEXA 2467 2 4112 3784 3785 4113 4114 3786
+ 3787 4115
CHEXA 2468 2 4114 3786 3787 4115 4116 3788
+ 3789 4117
CHEXA 2469 2 4116 3788 3789 4117 4118 3790
+ 3791 4119
CHEXA 2470 2 4118 3790 3791 4119 4120 3792
+ 3793 4121
CHEXA 2471 2 4120 3792 3793 4121 4122 3794
+ 3795 4123
CHEXA 2472 2 4122 3794 3795 4123 4124 3796
+ 3797 4125
CHEXA 2473 2 4124 3796 3797 4125 4126 3798
+ 3799 4127
CHEXA 2474 2 4126 3798 3799 4127 4128 3800
+ 3801 4129
CHEXA 2475 2 4128 3800 3801 4129 4130 3802
+ 3803 4131
CHEXA 2476 2 4130 3802 3803 4131 4132 3804
+ 3805 4133
CHEXA 2477 2 27 31 32 26 2987 2495
+ 3478 3806
CHEXA 2478 2 2987 2495 3478 3806 2989 2497
+ 3480 3808
CHEXA 2479 2 2989 2497 3480 3808 2991 2499
+ 3482 3810
CHEXA 2480 2 2991 2499 3482 3810 2993 2501
+ 3484 3812
CHEXA 2481 2 2993 2501 3484 3812 2995 2503
+ 3486 3814

1464 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 2482 2 2995 2503 3486 3814 2997 2505
+ 3488 3816
CHEXA 2483 2 2997 2505 3488 3816 2999 2507
+ 3490 3818
CHEXA 2484 2 2999 2507 3490 3818 3001 2509
+ 3492 3820
CHEXA 2485 2 3001 2509 3492 3820 3003 2511
+ 3494 3822
CHEXA 2486 2 3003 2511 3494 3822 3005 2513
+ 3496 3824
CHEXA 2487 2 3005 2513 3496 3824 3007 2515
+ 3498 3826
CHEXA 2488 2 3007 2515 3498 3826 3009 2517
+ 3500 3828
CHEXA 2489 2 3009 2517 3500 3828 3011 2519
+ 3502 3830
CHEXA 2490 2 3011 2519 3502 3830 3013 2521
+ 3504 3832
CHEXA 2491 2 3013 2521 3504 3832 3015 2523
+ 3506 3834
CHEXA 2492 2 3015 2523 3506 3834 3017 2525
+ 3508 3836
CHEXA 2493 2 3017 2525 3508 3836 3019 2527
+ 3510 3838
CHEXA 2494 2 3019 2527 3510 3838 3021 2529
+ 3512 3840
CHEXA 2495 2 3021 2529 3512 3840 3023 2531
+ 3514 3842
CHEXA 2496 2 3023 2531 3514 3842 3025 2533
+ 3516 3844
CHEXA 2497 2 3025 2533 3516 3844 3027 2535
+ 3518 3846
CHEXA 2498 2 3027 2535 3518 3846 3029 2537
+ 3520 3848
CHEXA 2499 2 3029 2537 3520 3848 3031 2539
+ 3522 3850
CHEXA 2500 2 3031 2539 3522 3850 3033 2541
+ 3524 3852
CHEXA 2501 2 3033 2541 3524 3852 3035 2543
+ 3526 3854
CHEXA 2502 2 3035 2543 3526 3854 3037 2545
+ 3528 3856
CHEXA 2503 2 3037 2545 3528 3856 3039 2547
+ 3530 3858
CHEXA 2504 2 3039 2547 3530 3858 3041 2549
+ 3532 3860
CHEXA 2505 2 3041 2549 3532 3860 3043 2551
+ 3534 3862
CHEXA 2506 2 3043 2551 3534 3862 3045 2553
+ 3536 3864
CHEXA 2507 2 3045 2553 3536 3864 3047 2555
+ 3538 3866
CHEXA 2508 2 3047 2555 3538 3866 3049 2557
+ 3540 3868
CHEXA 2509 2 3049 2557 3540 3868 3051 2559
+ 3542 3870
CHEXA 2510 2 3051 2559 3542 3870 3053 2561
+ 3544 3872
CHEXA 2511 2 3053 2561 3544 3872 3055 2563
+ 3546 3874
CHEXA 2512 2 3055 2563 3546 3874 3057 2565
+ 3548 3876
CHEXA 2513 2 3057 2565 3548 3876 3059 2567
+ 3550 3878
CHEXA 2514 2 3059 2567 3550 3878 3061 2569
+ 3552 3880
CHEXA 2515 2 3061 2569 3552 3880 3063 2571
+ 3554 3882
CHEXA 2516 2 3063 2571 3554 3882 3065 2573

Altair Engineering OptiStruct 13.0 Reference Guide 1465

Proprietary Information of Altair Engineering


+ 3556 3884
CHEXA 2517 2 3065 2573 3556 3884 3067 2575
+ 3558 3886
CHEXA 2518 2 3067 2575 3558 3886 3069 2577
+ 3560 3888
CHEXA 2599 2 3069 2577 3560 3888 3231 2739
+ 3722 4050
CHEXA 2600 2 3231 2739 3722 4050 3233 2741
+ 3724 4052
CHEXA 2601 2 3233 2741 3724 4052 3235 2743
+ 3726 4054
CHEXA 2602 2 3235 2743 3726 4054 3237 2745
+ 3728 4056
CHEXA 2603 2 3237 2745 3728 4056 3239 2747
+ 3730 4058
CHEXA 2604 2 3239 2747 3730 4058 3241 2749
+ 3732 4060
CHEXA 2605 2 3241 2749 3732 4060 3243 2751
+ 3734 4062
CHEXA 2606 2 3243 2751 3734 4062 3245 2753
+ 3736 4064
CHEXA 2607 2 3245 2753 3736 4064 3247 2755
+ 3738 4066
CHEXA 2608 2 3247 2755 3738 4066 3249 2757
+ 3740 4068
CHEXA 2609 2 3249 2757 3740 4068 3251 2759
+ 3742 4070
CHEXA 2610 2 3251 2759 3742 4070 3253 2761
+ 3744 4072
CHEXA 2611 2 3253 2761 3744 4072 3255 2763
+ 3746 4074
CHEXA 2612 2 3255 2763 3746 4074 3257 2765
+ 3748 4076
CHEXA 2613 2 3257 2765 3748 4076 3259 2767
+ 3750 4078
CHEXA 2614 2 3259 2767 3750 4078 3261 2769
+ 3752 4080
CHEXA 2615 2 3261 2769 3752 4080 3263 2771
+ 3754 4082
CHEXA 2616 2 3263 2771 3754 4082 3265 2773
+ 3756 4084
CHEXA 2617 2 3265 2773 3756 4084 3267 2775
+ 3758 4086
CHEXA 2618 2 3267 2775 3758 4086 3269 2777
+ 3760 4088
CHEXA 2619 2 3269 2777 3760 4088 3271 2779
+ 3762 4090
CHEXA 2620 2 3271 2779 3762 4090 3273 2781
+ 3764 4092
CHEXA 2621 2 3273 2781 3764 4092 3275 2783
+ 3766 4094
CHEXA 2622 2 3275 2783 3766 4094 3277 2785
+ 3768 4096
CHEXA 2623 2 3277 2785 3768 4096 3279 2787
+ 3770 4098
CHEXA 2624 2 3279 2787 3770 4098 3281 2789
+ 3772 4100
CHEXA 2625 2 3281 2789 3772 4100 3283 2791
+ 3774 4102
CHEXA 2626 2 3283 2791 3774 4102 3285 2793
+ 3776 4104
CHEXA 2627 2 3285 2793 3776 4104 3287 2795
+ 3778 4106
CHEXA 2628 2 3287 2795 3778 4106 3289 2797
+ 3780 4108
CHEXA 2629 2 3289 2797 3780 4108 3291 2799
+ 3782 4110
CHEXA 2630 2 3291 2799 3782 4110 3293 2801
+ 3784 4112

1466 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 2631 2 3293 2801 3784 4112 3295 2803
+ 3786 4114
CHEXA 2632 2 3295 2803 3786 4114 3297 2805
+ 3788 4116
CHEXA 2633 2 3297 2805 3788 4116 3299 2807
+ 3790 4118
CHEXA 2634 2 3299 2807 3790 4118 3301 2809
+ 3792 4120
CHEXA 2635 2 3301 2809 3792 4120 3303 2811
+ 3794 4122
CHEXA 2636 2 3303 2811 3794 4122 3305 2813
+ 3796 4124
CHEXA 2637 2 3305 2813 3796 4124 3307 2815
+ 3798 4126
CHEXA 2638 2 3307 2815 3798 4126 3309 2817
+ 3800 4128
CHEXA 2639 2 3309 2817 3800 4128 3311 2819
+ 3802 4130
CHEXA 2640 2 3311 2819 3802 4130 3313 2821
+ 3804 4132
$
$HMMOVE 2
$ 17THRU 58 139THRU 222 303THRU 386
$ 467THRU 550 631THRU 714 795THRU 878
$ 959THRU 1042 1123THRU 1206 1287THRU 1370
$ 1451THRU 1534 1615THRU 1698 1779THRU 1862
$ 1943THRU 2026 2107THRU 2190 2271THRU 2354
$ 2435THRU 2518 2599THRU 2640
$
$$
$$------------------------------------------------------------------------------$
$$ HyperMesh name and color information for generic components $
$$------------------------------------------------------------------------------$
$HMNAME COMP 2"Air" 2 "Air" 5
$HWCOLOR COMP 2 5
$
$HMNAME COMP 5"Piston"
$HWCOLOR COMP 5 8
$
$HMNAME COMP 6"absorber"
$HWCOLOR COMP 6 3
$
$
$HMDPRP
$ 17THRU 58 139THRU 222 303THRU 386
$ 467THRU 550 631THRU 714 795THRU 878
$ 959THRU 1042 1123THRU 1206 1287THRU 1370
$ 1451THRU 1534 1615THRU 1698 1779THRU 1862
$ 1943THRU 2026 2107THRU 2190 2271THRU 2354
$ 2435THRU 2518 2599THRU 2640 5627 5629 6116
$ 6122 6125 6520THRU 6521 6523 6528 6954 7220
$ 7647 7652 7945 7948 7955
$

$
$$
$$ PSHELL Data
$$
$
$
$
$
$
$
$
$HMNAME PROP 1"tube" 4
$HWCOLOR PROP 1 52
PSHELL 1 20.1 2 2 0.0
$$

Altair Engineering OptiStruct 13.0 Reference Guide 1467

Proprietary Information of Altair Engineering


$$ PSOLID Data
$$
$HMNAME PROP 2"Air" 5
$HWCOLOR PROP 2 4
PSOLID 2 1 PFLUID
$$
$$ MAT1 Data
$$
$HMNAME MAT 2"alum" "MAT1"
$HWCOLOR MAT 2 3
MAT1 21.0+7 0.3 0.000254
$$
$$ MAT10 Data
$HMNAME MAT 1"Air" "MAT10"
$HWCOLOR MAT 1 3
MAT10 1 1.21-7 13000.0
$$
$$------------------------------------------------------------------------------$
$$ HyperMesh Commands for loadcollectors name and color information $
$$------------------------------------------------------------------------------$
$HMNAME LOADCOL 2"spc"
$HWCOLOR LOADCOL 2 6
$$
$HMNAME LOADCOL 8"Force"
$HWCOLOR LOADCOL 8 7
$$
$HMNAME LOADCOL 12"SPC"
$HWCOLOR LOADCOL 12 5
$$
$$
$$ FREQi cards
$$
$HMNAME LOADCOL 3"Freq"
$HWCOLOR LOADCOL 3 6
$FREQ1 3 0.0 5.0 600
FREQ 3480.
$
$$
$$ RLOAD1 cards
$$
$HMNAME LOADCOL 6"Rload"
$HWCOLOR LOADCOL 6 6
RLOAD1 6 8 7 0 VELO
$$
$$
$$ TABLED1 cards
$$
$HMNAME LOADCOL 7"Table"
$HWCOLOR LOADCOL 7 6
TABLED1 7 LINEAR LINEAR
+ 0.0 1.0 3000.0 1.0ENDT
$$
$HMNAME LOADCOL 10"reactance"
$HWCOLOR LOADCOL 10 5
TABLED1 10 LINEAR LINEAR
+ 0.0 0.00154 3000.0 0.00154ENDT
$$
$HMNAME LOADCOL 11"Impedance"
$HWCOLOR LOADCOL 11 5
TABLED1 11 LINEAR LINEAR
+ 0.0 0.0 3000.0 0.0ENDT
$$
$$
$$ DLOAD cards
$$
$HMNAME LOADCOL 9"Dload"
$HWCOLOR LOADCOL 9 6
DLOAD 91.0 1.0 6
$$

1468 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


$$ EIGRL cards
$$
$HMNAME LOADCOL 4"EigrlTube"
$HWCOLOR LOADCOL 4 6
EIGRL 4 5 MASS
$HMNAME LOADCOL 5"EigrlAir"
$HWCOLOR LOADCOL 5 6
EIGRL 5 30 MASS
$$
$$ SPC Data
$$
SPC1 12123456 6776 thru 6800
spcd 86776 3 1.0
spcd 86777 3 1.0
spcd 86778 3 1.0
spcd 86779 3 1.0
spcd 86780 3 1.0
spcd 86781 3 1.0
spcd 86782 3 1.0
spcd 86783 3 1.0
spcd 86784 3 1.0
spcd 86785 3 1.0
spcd 86786 3 1.0
spcd 86788 3 1.0
spcd 86789 3 1.0
spcd 86790 3 1.0
spcd 86791 3 1.0
spcd 86792 3 1.0
spcd 86793 3 1.0
spcd 86794 3 1.0
spcd 86795 3 1.0
spcd 86796 3 1.0
spcd 86797 3 1.0
spcd 86798 3 1.0
spcd 86799 3 1.0
spcd 86800 3 1.0
$
$ DAREA Data
$
$$
$$ DAREA Data
$$
DAREA 8 6798 3-15.0
$$
$$
CAABSF 7957 5 689 688 687 686
CAABSF 7960 5 1017 689 686 1016
CAABSF 7964 5 1345 1344 688 689
CAABSF 7969 5 1509 1345 689 1017
CAABSF 7972 5 2165 2164 2163 2162
CAABSF 7977 5 688 2165 2162 687
CAABSF 7978 5 4133 3805 3804 4132
CAABSF 7980 5 2493 2492 2164 2165
CAABSF 7984 5 1344 2493 2165 688
CAABSF 7985 5 2821 687 2162 2820
CAABSF 7988 5 2820 2162 2163 2985
CAABSF 7990 5 3313 2821 2820 3312
CAABSF 7994 5 3312 2820 2985 3477
CAABSF 7996 5 3805 1016 686 3804
CAABSF 7998 5 3804 686 687 2821
CAABSF 8003 5 4132 3804 2821 3313
PAABSF 5 11 10
ENDDATA
$$
$$------------------------------------------------------------------------------$$
$$ Data Definition for AutoDV $$
$$------------------------------------------------------------------------------$$
$$
$$-----------------------------------------------------------------------------$$

Altair Engineering OptiStruct 13.0 Reference Guide 1469

Proprietary Information of Altair Engineering


$$ Design Variables Card for Control Perturbations $$
$$-----------------------------------------------------------------------------$$
$
$------------------------------------------------------------------------------$
$ Domain Element Definitions $
$------------------------------------------------------------------------------$
$$
$$------------------------------------------------------------------------------$$
$$ Nodeset Definitions $$
$$------------------------------------------------------------------------------$$
$$ Design domain node sets
$$
$$------------------------------------------------------------------------------$$
$$ Control Perturbation $$
$$------------------------------------------------------------------------------$$
$$
$$
$$ CONTROL PERTURBATION Data
$$

ALTDOCTAG "0mjpRI@DXd^3_0ASnbi`;l;q6A23R@9_67hgW8R?OiZ]
Eq:PeN``A;WXh3ITgJeq5NZRd5jSHQK3X@:`a12;n4qD_I^RYMo"
ADI0.1.0 2011-02-11T20:16:20 0of1 OSQA
ENDDOCTAG

Comments

1. PAABSF is referenced by a CAABSF entry only.

2. If only one grid point is specified on the CAABSF entry, then the impedance Z(f) = ZR +
iZi is the total impedance at the point. If two grids are specified, then the impedance is
the impedance per unit length. If three or four points are specified, then the impedance
is the impedance per unit area. ZR(f) = TZREID(f) + B and Zi(f) = TZIMID(f) – K/(ω).

3. The resistance represents a damper quantity B. The reactance represents a quantity of


the type (ωM – K/ω). The impedance is defined as: Z = p/u where, p is the pressure and
u is the velocity.

4. The impedance scale factor S is used in computing element stiffness and damping terms
as:

5. To create a non-reflecting boundary, set the values of the TABLEDi entry referenced by

the TZREID field (Resistance-real part of Impedance) to be equal to


for all frequencies. This will allow the acoustic wave to propagate normally through the
boundary, without reflection. This condition is called the Sommerfeld boundary condition.

Where, is the density of the fluid and, is the speed of sound in the fluid.

6. This card is represented as a property in HyperMesh.

1470 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PACABS

Bulk Data Entry

PACABS – Frequency-Dependant Structural Acoustic Absorber Property

Description

Defines the properties of the structural acoustic absorber element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PAC ABS PID SYNTH TID1 TID2 TID3 TESTAR C UTFR B

K M

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PAC ABS 4 YES 3 4 5 1. 200.

Field Contents

PID Property identification number.

(Integer > 0)

SYNTH Request the calculation of B, K, and M from the specified tables TIDi.

Default = “YES” (Character = “YES” or “NO”)

TID1 Identification of the TABLEDi entry that defines the resistance.

(Integer > 0 or Blank)

TID2 Identification of the TABLEDi entry that defines the reactance.

Altair Engineering OptiStruct 13.0 Reference Guide 1471

Proprietary Information of Altair Engineering


Field Contents

(Integer > 0 or Blank)

TID3 Identification of the TABLEDi entry that defines the weighting function.

(Integer > 0 or Blank)

TESTAR Area of the test specimen.

Default = 1.0 (Real > 0.0)

CUTFR Cutoff frequency for tables referenced above.

(Real > 0.0)

B, K, M Equivalent damping, stiffness and mass values per unit area.

K and M (Real > 0.0), B (Real)

Input File - chacab.fem

$$------------------------------------------------------------------------------$
$$ $
$$ NASTRAN Input Deck Generated by HyperMesh Version : 8.0SR1 $
$$ Generated using HyperMesh-Nastran Template Version : 8.0sr1
$$ $
$$ Template: general $
$$ $
$$------------------------------------------------------------------------------$
$$------------------------------------------------------------------------------$
$$ Executive Control Cards $
$$------------------------------------------------------------------------------$
SOL 111
CEND
$$------------------------------------------------------------------------------$
$$ Case Control Cards $
$$------------------------------------------------------------------------------$
SET 1 = 1734
DISPLACEMENT = 1
$
$HMNAME LOADSTEP 1"Load2"
SUBCASE 1
LABEL= Load2
SPC = 4
FREQUENCY = 5
DLOAD = 2
$$------------------------------------------------------------------------------$
$$ Bulk Data Cards $
$$------------------------------------------------------------------------------$
BEGIN BULK

$CHEXA 1056 2 1650 1661 1662 1651 1671 1682+


$+ 1683 1672

1472 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHACAB 1056 100 1650 1645 1657 1658 1676 1675+
+ 1671 1672
PACABS,100,YES,1,2,3,1.5,10.0,2.0
PARAM,G,0.001
PARAM,COUPMASS,-1
PARAM,POST,-1
$ACMODL DIFF 0.1
$$
EIGRL,20,,,300
EIGRL,21,,,300
$$ GRID Data
$$
GRID 1 2.0 2.0 0.0 -1
GRID 2 2.0 1.5 0.0 -1
GRID 3 2.0 1.0 0.0 -1
GRID 4 2.0 0.5 0.0 -1
GRID 5 2.0 0.0 0.0 -1
GRID 6 2.0 -0.5 0.0 -1
GRID 7 2.0 -1.0 0.0 -1
GRID 8 2.0 -1.5 0.0 -1
GRID 9 2.0 -2.0 0.0 -1
GRID 10 1.5 2.0 0.0 -1
GRID 11 1.5 1.5 0.0 -1
GRID 12 1.5 1.0 0.0 -1
GRID 13 1.5 0.5 0.0 -1
GRID 14 1.5 0.0 0.0 -1
GRID 15 1.5 -0.5 0.0 -1
GRID 16 1.5 -1.0 0.0 -1
GRID 17 1.5 -1.5 0.0 -1
GRID 18 1.5 -2.0 0.0 -1
GRID 19 1.0 2.0 0.0 -1
GRID 20 1.0 1.5 0.0 -1
GRID 21 1.0 1.0 0.0 -1
GRID 22 1.0 0.5 0.0 -1
GRID 23 1.0 0.0 0.0 -1
GRID 24 1.0 -0.5 0.0 -1
GRID 25 1.0 -1.0 0.0 -1
GRID 26 1.0 -1.5 0.0 -1
GRID 27 1.0 -2.0 0.0 -1
GRID 28 0.5 2.0 0.0 -1
GRID 29 0.5 1.5 0.0 -1
GRID 30 0.5 1.0 0.0 -1
GRID 31 0.5 0.5 0.0 -1
GRID 32 0.5 0.0 0.0 -1
GRID 33 0.5 -0.5 0.0 -1
GRID 34 0.5 -1.0 0.0 -1
GRID 35 0.5 -1.5 0.0 -1
GRID 36 0.5 -2.0 0.0 -1
GRID 37 0.0 2.0 0.0 -1
GRID 38 0.0 1.5 0.0 -1
GRID 39 0.0 1.0 0.0 -1
GRID 40 0.0 0.5 0.0 -1
GRID 41 0.0 0.0 0.0 -1
GRID 42 0.0 -0.5 0.0 -1
GRID 43 0.0 -1.0 0.0 -1
GRID 44 0.0 -1.5 0.0 -1
GRID 45 0.0 -2.0 0.0 -1
GRID 46 -0.5 2.0 0.0 -1
GRID 47 -0.5 1.5 0.0 -1
GRID 48 -0.5 1.0 0.0 -1
GRID 49 -0.5 0.5 0.0 -1
GRID 50 -0.5 0.0 0.0 -1
GRID 51 -0.5 -0.5 0.0 -1
GRID 52 -0.5 -1.0 0.0 -1
GRID 53 -0.5 -1.5 0.0 -1
GRID 54 -0.5 -2.0 0.0 -1
GRID 55 -1.0 2.0 0.0 -1
GRID 56 -1.0 1.5 0.0 -1
GRID 57 -1.0 1.0 0.0 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1473

Proprietary Information of Altair Engineering


GRID 58 -1.0 0.5 0.0 -1
GRID 59 -1.0 0.0 0.0 -1
GRID 60 -1.0 -0.5 0.0 -1
GRID 61 -1.0 -1.0 0.0 -1
GRID 62 -1.0 -1.5 0.0 -1
GRID 63 -1.0 -2.0 0.0 -1
GRID 64 -1.5 2.0 0.0 -1
GRID 65 -1.5 1.5 0.0 -1
GRID 66 -1.5 1.0 0.0 -1
GRID 67 -1.5 0.5 0.0 -1
GRID 68 -1.5 0.0 0.0 -1
GRID 69 -1.5 -0.5 0.0 -1
GRID 70 -1.5 -1.0 0.0 -1
GRID 71 -1.5 -1.5 0.0 -1
GRID 72 -1.5 -2.0 0.0 -1
GRID 73 -2.0 2.0 0.0 -1
GRID 74 -2.0 1.5 0.0 -1
GRID 75 -2.0 1.0 0.0 -1
GRID 76 -2.0 0.5 0.0 -1
GRID 77 -2.0 0.0 0.0 -1
GRID 78 -2.0 -0.5 0.0 -1
GRID 79 -2.0 -1.0 0.0 -1
GRID 80 -2.0 -1.5 0.0 -1
GRID 81 -2.0 -2.0 0.0 -1
GRID 82 2.5 2.0 0.0 -1
GRID 83 2.5 1.5 0.0 -1
GRID 84 2.5 1.0 0.0 -1
GRID 85 2.5 0.5 0.0 -1
GRID 86 2.5 0.0 0.0 -1
GRID 87 2.5 -0.5 0.0 -1
GRID 88 2.5 -1.0 0.0 -1
GRID 89 2.5 -1.5 0.0 -1
GRID 90 2.5 -2.0 0.0 -1
GRID 91 -2.5 2.0 0.0 -1
GRID 92 -2.5 1.5 0.0 -1
GRID 93 -2.5 1.0 0.0 -1
GRID 94 -2.5 0.5 0.0 -1
GRID 95 -2.5 0.0 0.0 -1
GRID 96 -2.5 -0.5 0.0 -1
GRID 97 -2.5 -1.0 0.0 -1
GRID 98 -2.5 -1.5 0.0 -1
GRID 99 -2.5 -2.0 0.0 -1
GRID 100 2.5 2.5 0.0 -1
GRID 101 2.5 -2.5 0.0 -1
GRID 102 2.0 2.5 0.0 -1
GRID 103 2.0 -2.5 0.0 -1
GRID 104 1.5 2.5 0.0 -1
GRID 105 1.5 -2.5 0.0 -1
GRID 106 1.0 2.5 0.0 -1
GRID 107 1.0 -2.5 0.0 -1
GRID 108 0.5 2.5 0.0 -1
GRID 109 0.5 -2.5 0.0 -1
GRID 110 0.0 2.5 0.0 -1
GRID 111 0.0 -2.5 0.0 -1
GRID 112 -0.5 2.5 0.0 -1
GRID 113 -0.5 -2.5 0.0 -1
GRID 114 -1.0 2.5 0.0 -1
GRID 115 -1.0 -2.5 0.0 -1
GRID 116 -1.5 2.5 0.0 -1
GRID 117 -1.5 -2.5 0.0 -1
GRID 118 -2.0 2.5 0.0 -1
GRID 119 -2.0 -2.5 0.0 -1
GRID 120 -2.5 2.5 0.0 -1
GRID 121 -2.5 -2.5 0.0 -1
GRID 727 2.5 2.5 1.0 -1
GRID 728 2.5 2.0 1.0 -1
GRID 729 2.0 2.0 1.0 -1
GRID 730 2.0 2.5 1.0 -1
GRID 731 2.5 1.5 1.0 -1

1474 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 732 2.0 1.5 1.0 -1
GRID 733 2.5 1.0 1.0 -1
GRID 734 2.0 1.0 1.0 -1
GRID 735 2.5 0.5 1.0 -1
GRID 736 2.0 0.5 1.0 -1
GRID 737 2.5 -4.2E-191.0 -1
GRID 738 2.0 -6.5E-201.0 -1
GRID 739 2.5 -0.5 1.0 -1
GRID 740 2.0 -0.5 1.0 -1
GRID 741 2.5 -1.0 1.0 -1
GRID 742 2.0 -1.0 1.0 -1
GRID 743 2.5 -1.5 1.0 -1
GRID 744 2.0 -1.5 1.0 -1
GRID 745 2.5 -2.0 1.0 -1
GRID 746 2.0 -2.0 1.0 -1
GRID 747 2.5 -2.5 1.0 -1
GRID 748 2.0 -2.5 1.0 -1
GRID 749 1.5 2.0 1.0 -1
GRID 750 1.5 2.5 1.0 -1
GRID 751 1.5 1.5 1.0 -1
GRID 752 1.5 1.0 1.0 -1
GRID 753 1.5 0.5 1.0 -1
GRID 754 1.5 -9.8E-211.0 -1
GRID 755 1.5 -0.5 1.0 -1
GRID 756 1.5 -1.0 1.0 -1
GRID 757 1.5 -1.5 1.0 -1
GRID 758 1.5 -2.0 1.0 -1
GRID 759 1.5 -2.5 1.0 -1
GRID 760 1.0 2.0 1.0 -1
GRID 761 1.0 2.5 1.0 -1
GRID 762 1.0 1.5 1.0 -1
GRID 763 1.0 1.0 1.0 -1
GRID 764 1.0 0.5 1.0 -1
GRID 765 1.0 -1.5E-211.0 -1
GRID 766 1.0 -0.5 1.0 -1
GRID 767 1.0 -1.0 1.0 -1
GRID 768 1.0 -1.5 1.0 -1
GRID 769 1.0 -2.0 1.0 -1
GRID 770 1.0 -2.5 1.0 -1
GRID 771 0.5 2.0 1.0 -1
GRID 772 0.5 2.5 1.0 -1
GRID 773 0.5 1.5 1.0 -1
GRID 774 0.5 1.0 1.0 -1
GRID 775 0.5 0.5 1.0 -1
GRID 776 0.5 -2.3E-221.0 -1
GRID 777 0.5 -0.5 1.0 -1
GRID 778 0.5 -1.0 1.0 -1
GRID 779 0.5 -1.5 1.0 -1
GRID 780 0.5 -2.0 1.0 -1
GRID 781 0.5 -2.5 1.0 -1
GRID 782 0.0 2.0 1.0 -1
GRID 783 0.0 2.5 1.0 -1
GRID 784 0.0 1.5 1.0 -1
GRID 785 0.0 1.0 1.0 -1
GRID 786 0.0 0.5 1.0 -1
GRID 787 0.0 -3.5E-231.0 -1
GRID 788 0.0 -0.5 1.0 -1
GRID 789 0.0 -1.0 1.0 -1
GRID 790 0.0 -1.5 1.0 -1
GRID 791 0.0 -2.0 1.0 -1
GRID 792 0.0 -2.5 1.0 -1
GRID 793 -0.5 2.0 1.0 -1
GRID 794 -0.5 2.5 1.0 -1
GRID 795 -0.5 1.5 1.0 -1
GRID 796 -0.5 1.0 1.0 -1
GRID 797 -0.5 0.5 1.0 -1
GRID 798 -0.5 -5.3E-241.0 -1
GRID 799 -0.5 -0.5 1.0 -1
GRID 800 -0.5 -1.0 1.0 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1475

Proprietary Information of Altair Engineering


GRID 801 -0.5 -1.5 1.0 -1
GRID 802 -0.5 -2.0 1.0 -1
GRID 803 -0.5 -2.5 1.0 -1
GRID 804 -1.0 2.0 1.0 -1
GRID 805 -1.0 2.5 1.0 -1
GRID 806 -1.0 1.5 1.0 -1
GRID 807 -1.0 1.0 1.0 -1
GRID 808 -1.0 0.5 1.0 -1
GRID 809 -1.0 -8.1E-251.0 -1
GRID 810 -1.0 -0.5 1.0 -1
GRID 811 -1.0 -1.0 1.0 -1
GRID 812 -1.0 -1.5 1.0 -1
GRID 813 -1.0 -2.0 1.0 -1
GRID 814 -1.0 -2.5 1.0 -1
GRID 815 -1.5 2.0 1.0 -1
GRID 816 -1.5 2.5 1.0 -1
GRID 817 -1.5 1.5 1.0 -1
GRID 818 -1.5 1.0 1.0 -1
GRID 819 -1.5 0.5 1.0 -1
GRID 820 -1.5 -9.3E-181.0 -1
GRID 821 -1.5 -0.5 1.0 -1
GRID 822 -1.5 -1.0 1.0 -1
GRID 823 -1.5 -1.5 1.0 -1
GRID 824 -1.5 -2.0 1.0 -1
GRID 825 -1.5 -2.5 1.0 -1
GRID 826 -2.0 2.0 1.0 -1
GRID 827 -2.0 2.5 1.0 -1
GRID 828 -2.0 1.5 1.0 -1
GRID 829 -2.0 1.0 1.0 -1
GRID 830 -2.0 0.5 1.0 -1
GRID 831 -2.0 -2.0E-181.0 -1
GRID 832 -2.0 -0.5 1.0 -1
GRID 833 -2.0 -1.0 1.0 -1
GRID 834 -2.0 -1.5 1.0 -1
GRID 835 -2.0 -2.0 1.0 -1
GRID 836 -2.0 -2.5 1.0 -1
GRID 837 -2.5 2.0 1.0 -1
GRID 838 -2.5 2.5 1.0 -1
GRID 839 -2.5 1.5 1.0 -1
GRID 840 -2.5 1.0 1.0 -1
GRID 841 -2.5 0.5 1.0 -1
GRID 842 -2.5 -1.0E-181.0 -1
GRID 843 -2.5 -0.5 1.0 -1
GRID 844 -2.5 -1.0 1.0 -1
GRID 845 -2.5 -1.5 1.0 -1
GRID 846 -2.5 -2.0 1.0 -1
GRID 847 -2.5 -2.5 1.0 -1
GRID 848 2.5 2.5 2.0 -1
GRID 849 2.5 2.0 2.0 -1
GRID 850 2.0 2.0 2.0 -1
GRID 851 2.0 2.5 2.0 -1
GRID 852 2.5 1.5 2.0 -1
GRID 853 2.0 1.5 2.0 -1
GRID 854 2.5 1.0 2.0 -1
GRID 855 2.0 1.0 2.0 -1
GRID 856 2.5 0.5 2.0 -1
GRID 857 2.0 0.5 2.0 -1
GRID 858 2.5 -6.0E-192.0 -1
GRID 859 2.0 -1.2E-192.0 -1
GRID 860 2.5 -0.5 2.0 -1
GRID 861 2.0 -0.5 2.0 -1
GRID 862 2.5 -1.0 2.0 -1
GRID 863 2.0 -1.0 2.0 -1
GRID 864 2.5 -1.5 2.0 -1
GRID 865 2.0 -1.5 2.0 -1
GRID 866 2.5 -2.0 2.0 -1
GRID 867 2.0 -2.0 2.0 -1
GRID 868 2.5 -2.5 2.0 -1
GRID 869 2.0 -2.5 2.0 -1

1476 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 870 1.5 2.0 2.0 -1
GRID 871 1.5 2.5 2.0 -1
GRID 872 1.5 1.5 2.0 -1
GRID 873 1.5 1.0 2.0 -1
GRID 874 1.5 0.5 2.0 -1
GRID 875 1.5 -2.1E-202.0 -1
GRID 876 1.5 -0.5 2.0 -1
GRID 877 1.5 -1.0 2.0 -1
GRID 878 1.5 -1.5 2.0 -1
GRID 879 1.5 -2.0 2.0 -1
GRID 880 1.5 -2.5 2.0 -1
GRID 881 1.0 2.0 2.0 -1
GRID 882 1.0 2.5 2.0 -1
GRID 883 1.0 1.5 2.0 -1
GRID 884 1.0 1.0 2.0 -1
GRID 885 1.0 0.5 2.0 -1
GRID 886 1.0 -3.8E-212.0 -1
GRID 887 1.0 -0.5 2.0 -1
GRID 888 1.0 -1.0 2.0 -1
GRID 889 1.0 -1.5 2.0 -1
GRID 890 1.0 -2.0 2.0 -1
GRID 891 1.0 -2.5 2.0 -1
GRID 892 0.5 2.0 2.0 -1
GRID 893 0.5 2.5 2.0 -1
GRID 894 0.5 1.5 2.0 -1
GRID 895 0.5 1.0 2.0 -1
GRID 896 0.5 0.5 2.0 -1
GRID 897 0.5 -6.7E-222.0 -1
GRID 898 0.5 -0.5 2.0 -1
GRID 899 0.5 -1.0 2.0 -1
GRID 900 0.5 -1.5 2.0 -1
GRID 901 0.5 -2.0 2.0 -1
GRID 902 0.5 -2.5 2.0 -1
GRID 903 0.0 2.0 2.0 -1
GRID 904 0.0 2.5 2.0 -1
GRID 905 0.0 1.5 2.0 -1
GRID 906 0.0 1.0 2.0 -1
GRID 907 0.0 0.5 2.0 -1
GRID 908 0.0 -1.2E-222.0 -1
GRID 909 0.0 -0.5 2.0 -1
GRID 910 0.0 -1.0 2.0 -1
GRID 911 0.0 -1.5 2.0 -1
GRID 912 0.0 -2.0 2.0 -1
GRID 913 0.0 -2.5 2.0 -1
GRID 914 -0.5 2.0 2.0 -1
GRID 915 -0.5 2.5 2.0 -1
GRID 916 -0.5 1.5 2.0 -1
GRID 917 -0.5 1.0 2.0 -1
GRID 918 -0.5 0.5 2.0 -1
GRID 919 -0.5 -2.0E-232.0 -1
GRID 920 -0.5 -0.5 2.0 -1
GRID 921 -0.5 -1.0 2.0 -1
GRID 922 -0.5 -1.5 2.0 -1
GRID 923 -0.5 -2.0 2.0 -1
GRID 924 -0.5 -2.5 2.0 -1
GRID 925 -1.0 2.0 2.0 -1
GRID 926 -1.0 2.5 2.0 -1
GRID 927 -1.0 1.5 2.0 -1
GRID 928 -1.0 1.0 2.0 -1
GRID 929 -1.0 0.5 2.0 -1
GRID 930 -1.0 -1.4E-182.0 -1
GRID 931 -1.0 -0.5 2.0 -1
GRID 932 -1.0 -1.0 2.0 -1
GRID 933 -1.0 -1.5 2.0 -1
GRID 934 -1.0 -2.0 2.0 -1
GRID 935 -1.0 -2.5 2.0 -1
GRID 936 -1.5 2.0 2.0 -1
GRID 937 -1.5 2.5 2.0 -1
GRID 938 -1.5 1.5 2.0 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1477

Proprietary Information of Altair Engineering


GRID 939 -1.5 1.0 2.0 -1
GRID 940 -1.5 0.5 2.0 -1
GRID 941 -1.5 -1.3E-172.0 -1
GRID 942 -1.5 -0.5 2.0 -1
GRID 943 -1.5 -1.0 2.0 -1
GRID 944 -1.5 -1.5 2.0 -1
GRID 945 -1.5 -2.0 2.0 -1
GRID 946 -1.5 -2.5 2.0 -1
GRID 947 -2.0 2.0 2.0 -1
GRID 948 -2.0 2.5 2.0 -1
GRID 949 -2.0 1.5 2.0 -1
GRID 950 -2.0 1.0 2.0 -1
GRID 951 -2.0 0.5 2.0 -1
GRID 952 -2.0 -4.1E-182.0 -1
GRID 953 -2.0 -0.5 2.0 -1
GRID 954 -2.0 -1.0 2.0 -1
GRID 955 -2.0 -1.5 2.0 -1
GRID 956 -2.0 -2.0 2.0 -1
GRID 957 -2.0 -2.5 2.0 -1
GRID 958 -2.5 2.0 2.0 -1
GRID 959 -2.5 2.5 2.0 -1
GRID 960 -2.5 1.5 2.0 -1
GRID 961 -2.5 1.0 2.0 -1
GRID 962 -2.5 0.5 2.0 -1
GRID 963 -2.5 -2.5E-182.0 -1
GRID 964 -2.5 -0.5 2.0 -1
GRID 965 -2.5 -1.0 2.0 -1
GRID 966 -2.5 -1.5 2.0 -1
GRID 967 -2.5 -2.0 2.0 -1
GRID 968 -2.5 -2.5 2.0 -1
GRID 969 2.5 2.5 3.0 -1
GRID 970 2.5 2.0 3.0 -1
GRID 971 2.0 2.0 3.0 -1
GRID 972 2.0 2.5 3.0 -1
GRID 973 2.5 1.5 3.0 -1
GRID 974 2.0 1.5 3.0 -1
GRID 975 2.5 1.0 3.0 -1
GRID 976 2.0 1.0 3.0 -1
GRID 977 2.5 0.5 3.0 -1
GRID 978 2.0 0.5 3.0 -1
GRID 979 2.5 -6.7E-193.0 -1
GRID 980 2.0 -1.5E-193.0 -1
GRID 981 2.5 -0.5 3.0 -1
GRID 982 2.0 -0.5 3.0 -1
GRID 983 2.5 -1.0 3.0 -1
GRID 984 2.0 -1.0 3.0 -1
GRID 985 2.5 -1.5 3.0 -1
GRID 986 2.0 -1.5 3.0 -1
GRID 987 2.5 -2.0 3.0 -1
GRID 988 2.0 -2.0 3.0 -1
GRID 989 2.5 -2.5 3.0 -1
GRID 990 2.0 -2.5 3.0 -1
GRID 991 1.5 2.0 3.0 -1
GRID 992 1.5 2.5 3.0 -1
GRID 993 1.5 1.5 3.0 -1
GRID 994 1.5 1.0 3.0 -1
GRID 995 1.5 0.5 3.0 -1
GRID 996 1.5 -3.1E-203.0 -1
GRID 997 1.5 -0.5 3.0 -1
GRID 998 1.5 -1.0 3.0 -1
GRID 999 1.5 -1.5 3.0 -1
GRID 1000 1.5 -2.0 3.0 -1
GRID 1001 1.5 -2.5 3.0 -1
GRID 1002 1.0 2.0 3.0 -1
GRID 1003 1.0 2.5 3.0 -1
GRID 1004 1.0 1.5 3.0 -1
GRID 1005 1.0 1.0 3.0 -1
GRID 1006 1.0 0.5 3.0 -1
GRID 1007 1.0 -6.2E-213.0 -1

1478 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1008 1.0 -0.5 3.0 -1
GRID 1009 1.0 -1.0 3.0 -1
GRID 1010 1.0 -1.5 3.0 -1
GRID 1011 1.0 -2.0 3.0 -1
GRID 1012 1.0 -2.5 3.0 -1
GRID 1013 0.5 2.0 3.0 -1
GRID 1014 0.5 2.5 3.0 -1
GRID 1015 0.5 1.5 3.0 -1
GRID 1016 0.5 1.0 3.0 -1
GRID 1017 0.5 0.5 3.0 -1
GRID 1018 0.5 -1.2E-213.0 -1
GRID 1019 0.5 -0.5 3.0 -1
GRID 1020 0.5 -1.0 3.0 -1
GRID 1021 0.5 -1.5 3.0 -1
GRID 1022 0.5 -2.0 3.0 -1
GRID 1023 0.5 -2.5 3.0 -1
GRID 1024 1.50E-322.0 3.0 -1
GRID 1025 3.80E-332.5 3.0 -1
GRID 1026 2.67E-331.5 3.0 -1
GRID 1027 4.07E-341.0 3.0 -1
GRID 1028 6.20E-350.5 3.0 -1
GRID 1029 6.35E-32-2.3E-223.0 -1
GRID 1030 1.29E-31-0.5 3.0 -1
GRID 1031 -4.0E-32-1.0 3.0 -1
GRID 1032 -5.5E-32-1.5 3.0 -1
GRID 1033 -3.2E-32-2.0 3.0 -1
GRID 1034 -4.8E-33-2.5 3.0 -1
GRID 1035 -0.5 2.0 3.0 -1
GRID 1036 -0.5 2.5 3.0 -1
GRID 1037 -0.5 1.5 3.0 -1
GRID 1038 -0.5 1.0 3.0 -1
GRID 1039 -0.5 0.5 3.0 -1
GRID 1040 -0.5 -2.2E-193.0 -1
GRID 1041 -0.5 -0.5 3.0 -1
GRID 1042 -0.5 -1.0 3.0 -1
GRID 1043 -0.5 -1.5 3.0 -1
GRID 1044 -0.5 -2.0 3.0 -1
GRID 1045 -0.5 -2.5 3.0 -1
GRID 1046 -1.0 2.0 3.0 -1
GRID 1047 -1.0 2.5 3.0 -1
GRID 1048 -1.0 1.5 3.0 -1
GRID 1049 -1.0 1.0 3.0 -1
GRID 1050 -1.0 0.5 3.0 -1
GRID 1051 -1.0 -2.6E-183.0 -1
GRID 1052 -1.0 -0.5 3.0 -1
GRID 1053 -1.0 -1.0 3.0 -1
GRID 1054 -1.0 -1.5 3.0 -1
GRID 1055 -1.0 -2.0 3.0 -1
GRID 1056 -1.0 -2.5 3.0 -1
GRID 1057 -1.5 2.0 3.0 -1
GRID 1058 -1.5 2.5 3.0 -1
GRID 1059 -1.5 1.5 3.0 -1
GRID 1060 -1.5 1.0 3.0 -1
GRID 1061 -1.5 0.5 3.0 -1
GRID 1062 -1.5 -1.5E-173.0 -1
GRID 1063 -1.5 -0.5 3.0 -1
GRID 1064 -1.5 -1.0 3.0 -1
GRID 1065 -1.5 -1.5 3.0 -1
GRID 1066 -1.5 -2.0 3.0 -1
GRID 1067 -1.5 -2.5 3.0 -1
GRID 1068 -2.0 2.0 3.0 -1
GRID 1069 -2.0 2.5 3.0 -1
GRID 1070 -2.0 1.5 3.0 -1
GRID 1071 -2.0 1.0 3.0 -1
GRID 1072 -2.0 0.5 3.0 -1
GRID 1073 -2.0 -5.3E-183.0 -1
GRID 1074 -2.0 -0.5 3.0 -1
GRID 1075 -2.0 -1.0 3.0 -1
GRID 1076 -2.0 -1.5 3.0 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1479

Proprietary Information of Altair Engineering


GRID 1077 -2.0 -2.0 3.0 -1
GRID 1078 -2.0 -2.5 3.0 -1
GRID 1079 -2.5 2.0 3.0 -1
GRID 1080 -2.5 2.5 3.0 -1
GRID 1081 -2.5 1.5 3.0 -1
GRID 1082 -2.5 1.0 3.0 -1
GRID 1083 -2.5 0.5 3.0 -1
GRID 1084 -2.5 -3.3E-183.0 -1
GRID 1085 -2.5 -0.5 3.0 -1
GRID 1086 -2.5 -1.0 3.0 -1
GRID 1087 -2.5 -1.5 3.0 -1
GRID 1088 -2.5 -2.0 3.0 -1
GRID 1089 -2.5 -2.5 3.0 -1
GRID 1090 2.5 2.5 4.0 -1
GRID 1091 2.5 2.0 4.0 -1
GRID 1092 2.0 2.0 4.0 -1
GRID 1093 2.0 2.5 4.0 -1
GRID 1094 2.5 1.5 4.0 -1
GRID 1095 2.0 1.5 4.0 -1
GRID 1096 2.5 1.0 4.0 -1
GRID 1097 2.0 1.0 4.0 -1
GRID 1098 2.5 0.5 4.0 -1
GRID 1099 2.0 0.5 4.0 -1
GRID 1100 2.5 -1.0E-164.0 -1
GRID 1101 2.0 -1.8E-164.0 -1
GRID 1102 2.5 -0.5 4.0 -1
GRID 1103 2.0 -0.5 4.0 -1
GRID 1104 2.5 -1.0 4.0 -1
GRID 1105 2.0 -1.0 4.0 -1
GRID 1106 2.5 -1.5 4.0 -1
GRID 1107 2.0 -1.5 4.0 -1
GRID 1108 2.5 -2.0 4.0 -1
GRID 1109 2.0 -2.0 4.0 -1
GRID 1110 2.5 -2.5 4.0 -1
GRID 1111 2.0 -2.5 4.0 -1
GRID 1112 1.5 2.0 4.0 -1
GRID 1113 1.5 2.5 4.0 -1
GRID 1114 1.5 1.5 4.0 -1
GRID 1115 1.5 1.0 4.0 -1
GRID 1116 1.5 0.5 4.0 -1
GRID 1117 1.5 -3.1E-164.0 -1
GRID 1118 1.5 -0.5 4.0 -1
GRID 1119 1.5 -1.0 4.0 -1
GRID 1120 1.5 -1.5 4.0 -1
GRID 1121 1.5 -2.0 4.0 -1
GRID 1122 1.5 -2.5 4.0 -1
GRID 1123 1.0 2.0 4.0 -1
GRID 1124 1.0 2.5 4.0 -1
GRID 1125 1.0 1.5 4.0 -1
GRID 1126 1.0 1.0 4.0 -1
GRID 1127 1.0 0.5 4.0 -1
GRID 1128 1.0 -3.6E-164.0 -1
GRID 1129 1.0 -0.5 4.0 -1
GRID 1130 1.0 -1.0 4.0 -1
GRID 1131 1.0 -1.5 4.0 -1
GRID 1132 1.0 -2.0 4.0 -1
GRID 1133 1.0 -2.5 4.0 -1
GRID 1134 0.5 2.0 4.0 -1
GRID 1135 0.5 2.5 4.0 -1
GRID 1136 0.5 1.5 4.0 -1
GRID 1137 0.5 1.0 4.0 -1
GRID 1138 0.5 0.5 4.0 -1
GRID 1139 0.5 -2.8E-164.0 -1
GRID 1140 0.5 -0.5 4.0 -1
GRID 1141 0.5 -1.0 4.0 -1
GRID 1142 0.5 -1.5 4.0 -1
GRID 1143 0.5 -2.0 4.0 -1
GRID 1144 0.5 -2.5 4.0 -1
GRID 1145 -1.7E-162.0 4.0 -1

1480 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1146 -2.3E-162.5 4.0 -1
GRID 1147 -2.7E-171.5 4.0 -1
GRID 1148 -3.0E-171.0 4.0 -1
GRID 1149 -7.0E-170.5 4.0 -1
GRID 1150 2.16E-17-1.4E-164.0 -1
GRID 1151 1.65E-16-0.5 4.0 -1
GRID 1152 3.53E-16-1.0 4.0 -1
GRID 1153 2.86E-16-1.5 4.0 -1
GRID 1154 -5.5E-17-2.0 4.0 -1
GRID 1155 -2.5E-16-2.5 4.0 -1
GRID 1156 -0.5 2.0 4.0 -1
GRID 1157 -0.5 2.5 4.0 -1
GRID 1158 -0.5 1.5 4.0 -1
GRID 1159 -0.5 1.0 4.0 -1
GRID 1160 -0.5 0.5 4.0 -1
GRID 1161 -0.5 -2.5E-174.0 -1
GRID 1162 -0.5 -0.5 4.0 -1
GRID 1163 -0.5 -1.0 4.0 -1
GRID 1164 -0.5 -1.5 4.0 -1
GRID 1165 -0.5 -2.0 4.0 -1
GRID 1166 -0.5 -2.5 4.0 -1
GRID 1167 -1.0 2.0 4.0 -1
GRID 1168 -1.0 2.5 4.0 -1
GRID 1169 -1.0 1.5 4.0 -1
GRID 1170 -1.0 1.0 4.0 -1
GRID 1171 -1.0 0.5 4.0 -1
GRID 1172 -1.0 9.63E-174.0 -1
GRID 1173 -1.0 -0.5 4.0 -1
GRID 1174 -1.0 -1.0 4.0 -1
GRID 1175 -1.0 -1.5 4.0 -1
GRID 1176 -1.0 -2.0 4.0 -1
GRID 1177 -1.0 -2.5 4.0 -1
GRID 1178 -1.5 2.0 4.0 -1
GRID 1179 -1.5 2.5 4.0 -1
GRID 1180 -1.5 1.5 4.0 -1
GRID 1181 -1.5 1.0 4.0 -1
GRID 1182 -1.5 0.5 4.0 -1
GRID 1183 -1.5 2.14E-164.0 -1
GRID 1184 -1.5 -0.5 4.0 -1
GRID 1185 -1.5 -1.0 4.0 -1
GRID 1186 -1.5 -1.5 4.0 -1
GRID 1187 -1.5 -2.0 4.0 -1
GRID 1188 -1.5 -2.5 4.0 -1
GRID 1189 -2.0 2.0 4.0 -1
GRID 1190 -2.0 2.5 4.0 -1
GRID 1191 -2.0 1.5 4.0 -1
GRID 1192 -2.0 1.0 4.0 -1
GRID 1193 -2.0 0.5 4.0 -1
GRID 1194 -2.0 1.84E-164.0 -1
GRID 1195 -2.0 -0.5 4.0 -1
GRID 1196 -2.0 -1.0 4.0 -1
GRID 1197 -2.0 -1.5 4.0 -1
GRID 1198 -2.0 -2.0 4.0 -1
GRID 1199 -2.0 -2.5 4.0 -1
GRID 1200 -2.5 2.0 4.0 -1
GRID 1201 -2.5 2.5 4.0 -1
GRID 1202 -2.5 1.5 4.0 -1
GRID 1203 -2.5 1.0 4.0 -1
GRID 1204 -2.5 0.5 4.0 -1
GRID 1205 -2.5 1.10E-164.0 -1
GRID 1206 -2.5 -0.5 4.0 -1
GRID 1207 -2.5 -1.0 4.0 -1
GRID 1208 -2.5 -1.5 4.0 -1
GRID 1209 -2.5 -2.0 4.0 -1
GRID 1210 -2.5 -2.5 4.0 -1
GRID 1211 2.5 2.5 5.0 -1
GRID 1212 2.5 2.0 5.0 -1
GRID 1213 2.0 2.0 5.0 -1
GRID 1214 2.0 2.5 5.0 -1

Altair Engineering OptiStruct 13.0 Reference Guide 1481

Proprietary Information of Altair Engineering


GRID 1215 2.5 1.5 5.0 -1
GRID 1216 2.0 1.5 5.0 -1
GRID 1217 2.5 1.0 5.0 -1
GRID 1218 2.0 1.0 5.0 -1
GRID 1219 2.5 0.5 5.0 -1
GRID 1220 2.0 0.5 5.0 -1
GRID 1221 2.5 -1.8E-165.0 -1
GRID 1222 2.0 -2.4E-165.0 -1
GRID 1223 2.5 -0.5 5.0 -1
GRID 1224 2.0 -0.5 5.0 -1
GRID 1225 2.5 -1.0 5.0 -1
GRID 1226 2.0 -1.0 5.0 -1
GRID 1227 2.5 -1.5 5.0 -1
GRID 1228 2.0 -1.5 5.0 -1
GRID 1229 2.5 -2.0 5.0 -1
GRID 1230 2.0 -2.0 5.0 -1
GRID 1231 2.5 -2.5 5.0 -1
GRID 1232 2.0 -2.5 5.0 -1
GRID 1233 1.5 2.0 5.0 -1
GRID 1234 1.5 2.5 5.0 -1
GRID 1235 1.5 1.5 5.0 -1
GRID 1236 1.5 1.0 5.0 -1
GRID 1237 1.5 0.5 5.0 -1
GRID 1238 1.5 -2.8E-165.0 -1
GRID 1239 1.5 -0.5 5.0 -1
GRID 1240 1.5 -1.0 5.0 -1
GRID 1241 1.5 -1.5 5.0 -1
GRID 1242 1.5 -2.0 5.0 -1
GRID 1243 1.5 -2.5 5.0 -1
GRID 1244 1.0 2.0 5.0 -1
GRID 1245 1.0 2.5 5.0 -1
GRID 1246 1.0 1.5 5.0 -1
GRID 1247 1.0 1.0 5.0 -1
GRID 1248 1.0 0.5 5.0 -1
GRID 1249 1.0 -3.0E-165.0 -1
GRID 1250 1.0 -0.5 5.0 -1
GRID 1251 1.0 -1.0 5.0 -1
GRID 1252 1.0 -1.5 5.0 -1
GRID 1253 1.0 -2.0 5.0 -1
GRID 1254 1.0 -2.5 5.0 -1
GRID 1255 0.5 2.0 5.0 -1
GRID 1256 0.5 2.5 5.0 -1
GRID 1257 0.5 1.5 5.0 -1
GRID 1258 0.5 1.0 5.0 -1
GRID 1259 0.5 0.5 5.0 -1
GRID 1260 0.5 -2.4E-165.0 -1
GRID 1261 0.5 -0.5 5.0 -1
GRID 1262 0.5 -1.0 5.0 -1
GRID 1263 0.5 -1.5 5.0 -1
GRID 1264 0.5 -2.0 5.0 -1
GRID 1265 0.5 -2.5 5.0 -1
GRID 1266 -2.4E-162.0 5.0 -1
GRID 1267 -2.4E-162.5 5.0 -1
GRID 1268 -1.4E-161.5 5.0 -1
GRID 1269 -1.1E-161.0 5.0 -1
GRID 1270 -6.8E-170.5 5.0 -1
GRID 1271 -2.1E-17-1.4E-165.0 -1
GRID 1272 1.13E-16-0.5 5.0 -1
GRID 1273 2.64E-16-1.0 5.0 -1
GRID 1274 2.07E-16-1.5 5.0 -1
GRID 1275 -8.9E-18-2.0 5.0 -1
GRID 1276 -1.0E-16-2.5 5.0 -1
GRID 1277 -0.5 2.0 5.0 -1
GRID 1278 -0.5 2.5 5.0 -1
GRID 1279 -0.5 1.5 5.0 -1
GRID 1280 -0.5 1.0 5.0 -1
GRID 1281 -0.5 0.5 5.0 -1
GRID 1282 -0.5 -2.9E-175.0 -1
GRID 1283 -0.5 -0.5 5.0 -1

1482 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1284 -0.5 -1.0 5.0 -1
GRID 1285 -0.5 -1.5 5.0 -1
GRID 1286 -0.5 -2.0 5.0 -1
GRID 1287 -0.5 -2.5 5.0 -1
GRID 1288 -1.0 2.0 5.0 -1
GRID 1289 -1.0 2.5 5.0 -1
GRID 1290 -1.0 1.5 5.0 -1
GRID 1291 -1.0 1.0 5.0 -1
GRID 1292 -1.0 0.5 5.0 -1
GRID 1293 -1.0 8.84E-175.0 -1
GRID 1294 -1.0 -0.5 5.0 -1
GRID 1295 -1.0 -1.0 5.0 -1
GRID 1296 -1.0 -1.5 5.0 -1
GRID 1297 -1.0 -2.0 5.0 -1
GRID 1298 -1.0 -2.5 5.0 -1
GRID 1299 -1.5 2.0 5.0 -1
GRID 1300 -1.5 2.5 5.0 -1
GRID 1301 -1.5 1.5 5.0 -1
GRID 1302 -1.5 1.0 5.0 -1
GRID 1303 -1.5 0.5 5.0 -1
GRID 1304 -1.5 1.34E-165.0 -1
GRID 1305 -1.5 -0.5 5.0 -1
GRID 1306 -1.5 -1.0 5.0 -1
GRID 1307 -1.5 -1.5 5.0 -1
GRID 1308 -1.5 -2.0 5.0 -1
GRID 1309 -1.5 -2.5 5.0 -1
GRID 1310 -2.0 2.0 5.0 -1
GRID 1311 -2.0 2.5 5.0 -1
GRID 1312 -2.0 1.5 5.0 -1
GRID 1313 -2.0 1.0 5.0 -1
GRID 1314 -2.0 0.5 5.0 -1
GRID 1315 -2.0 1.09E-165.0 -1
GRID 1316 -2.0 -0.5 5.0 -1
GRID 1317 -2.0 -1.0 5.0 -1
GRID 1318 -2.0 -1.5 5.0 -1
GRID 1319 -2.0 -2.0 5.0 -1
GRID 1320 -2.0 -2.5 5.0 -1
GRID 1321 -2.5 2.0 5.0 -1
GRID 1322 -2.5 2.5 5.0 -1
GRID 1323 -2.5 1.5 5.0 -1
GRID 1324 -2.5 1.0 5.0 -1
GRID 1325 -2.5 0.5 5.0 -1
GRID 1326 -2.5 5.75E-175.0 -1
GRID 1327 -2.5 -0.5 5.0 -1
GRID 1328 -2.5 -1.0 5.0 -1
GRID 1329 -2.5 -1.5 5.0 -1
GRID 1330 -2.5 -2.0 5.0 -1
GRID 1331 -2.5 -2.5 5.0 -1
GRID 1332 2.0 2.0 0.0
GRID 1333 2.0 1.5 0.0
GRID 1334 2.0 1.0 0.0
GRID 1335 2.0 0.5 0.0
GRID 1336 2.0 -2.2E-180.0
GRID 1337 2.0 -0.5 0.0
GRID 1338 2.0 -1.0 0.0
GRID 1339 2.0 -1.5 0.0
GRID 1340 2.0 -2.0 0.0
GRID 1341 1.5 2.0 0.0
GRID 1342 1.5 1.5 0.0
GRID 1343 1.5 1.0 0.0
GRID 1344 1.5 0.5 0.0
GRID 1345 1.5 -1.9E-180.0
GRID 1346 1.5 -0.5 0.0
GRID 1347 1.5 -1.0 0.0
GRID 1348 1.5 -1.5 0.0
GRID 1349 1.5 -2.0 0.0
GRID 1350 1.0 2.0 0.0
GRID 1351 1.0 1.5 0.0
GRID 1352 1.0 1.0 0.0

Altair Engineering OptiStruct 13.0 Reference Guide 1483

Proprietary Information of Altair Engineering


GRID 1353 1.0 0.5 0.0
GRID 1354 1.0 -1.9E-180.0
GRID 1355 1.0 -0.5 0.0
GRID 1356 1.0 -1.0 0.0
GRID 1357 1.0 -1.5 0.0
GRID 1358 1.0 -2.0 0.0
GRID 1359 0.5 2.0 0.0
GRID 1360 0.5 1.5 0.0
GRID 1361 0.5 1.0 0.0
GRID 1362 0.5 0.5 0.0
GRID 1363 0.5 -1.9E-180.0
GRID 1364 0.5 -0.5 0.0
GRID 1365 0.5 -1.0 0.0
GRID 1366 0.5 -1.5 0.0
GRID 1367 0.5 -2.0 0.0
GRID 1368 -2.8E-182.0 0.0
GRID 1369 -2.8E-181.5 0.0
GRID 1370 -2.5E-181.0 0.0
GRID 1371 -2.8E-180.5 0.0
GRID 1372 -3.1E-18-1.7E-180.0
GRID 1373 -2.8E-18-0.5 0.0
GRID 1374 -3.1E-18-1.0 0.0
GRID 1375 -1.9E-18-1.5 0.0
GRID 1376 -2.8E-18-2.0 0.0
GRID 1377 -0.5 2.0 0.0
GRID 1378 -0.5 1.5 0.0
GRID 1379 -0.5 1.0 0.0
GRID 1380 -0.5 0.5 0.0
GRID 1381 -0.5 -1.7E-180.0
GRID 1382 -0.5 -0.5 0.0
GRID 1383 -0.5 -1.0 0.0
GRID 1384 -0.5 -1.5 0.0
GRID 1385 -0.5 -2.0 0.0
GRID 1386 -1.0 2.0 0.0
GRID 1387 -1.0 1.5 0.0
GRID 1388 -1.0 1.0 0.0
GRID 1389 -1.0 0.5 0.0
GRID 1390 -1.0 -1.9E-180.0
GRID 1391 -1.0 -0.5 0.0
GRID 1392 -1.0 -1.0 0.0
GRID 1393 -1.0 -1.5 0.0
GRID 1394 -1.0 -2.0 0.0
GRID 1395 -1.5 2.0 0.0
GRID 1396 -1.5 1.5 0.0
GRID 1397 -1.5 1.0 0.0
GRID 1398 -1.5 0.5 0.0
GRID 1399 -1.5 -1.7E-180.0
GRID 1400 -1.5 -0.5 0.0
GRID 1401 -1.5 -1.0 0.0
GRID 1402 -1.5 -1.5 0.0
GRID 1403 -1.5 -2.0 0.0
GRID 1404 -2.0 2.0 0.0
GRID 1405 -2.0 1.5 0.0
GRID 1406 -2.0 1.0 0.0
GRID 1407 -2.0 0.5 0.0
GRID 1408 -2.0 -2.2E-180.0
GRID 1409 -2.0 -0.5 0.0
GRID 1410 -2.0 -1.0 0.0
GRID 1411 -2.0 -1.5 0.0
GRID 1412 -2.0 -2.0 0.0
GRID 1413 2.4964642.0 0.004472
GRID 1414 2.4964641.5 0.004472
GRID 1415 2.4964641.0 0.004472
GRID 1416 2.4964640.5 0.004472
GRID 1417 2.496464-2.6E-180.004472
GRID 1418 2.496464-0.5 0.004472
GRID 1419 2.496464-1.0 0.004472
GRID 1420 2.496464-1.5 0.004472
GRID 1421 2.496464-2.0 0.004472

1484 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1422 -2.496462.0 0.004472
GRID 1423 -2.496461.5 0.004472
GRID 1424 -2.496461.0 0.004472
GRID 1425 -2.496460.5 0.004472
GRID 1426 -2.49646-2.6E-180.004472
GRID 1427 -2.49646-0.5 0.004472
GRID 1428 -2.49646-1.0 0.004472
GRID 1429 -2.49646-1.5 0.004472
GRID 1430 -2.49646-2.0 0.004472
GRID 1431 2.4961522.4961520.005963
GRID 1432 2.496152-2.496150.005963
GRID 1433 2.0 2.4964640.004472
GRID 1434 2.0 -2.496460.004472
GRID 1435 1.5 2.4964640.004472
GRID 1436 1.5 -2.496460.004472
GRID 1437 1.0 2.4964640.004472
GRID 1438 1.0 -2.496460.004472
GRID 1439 0.5 2.4964640.004472
GRID 1440 0.5 -2.496460.004472
GRID 1441 -2.6E-182.4964640.004472
GRID 1442 -2.6E-18-2.496460.004472
GRID 1443 -0.5 2.4964640.004472
GRID 1444 -0.5 -2.496460.004472
GRID 1445 -1.0 2.4964640.004472
GRID 1446 -1.0 -2.496460.004472
GRID 1447 -1.5 2.4964640.004472
GRID 1448 -1.5 -2.496460.004472
GRID 1449 -2.0 2.4964640.004472
GRID 1450 -2.0 -2.496460.004472
GRID 1451 -2.496152.4961520.005963
GRID 1452 -2.49615-2.496150.005963
GRID 1453 -2.49615-2.496154.994037
GRID 1454 -2.49646-2.0 4.995528
GRID 1455 -2.49646-1.5 4.995528
GRID 1456 -2.49646-1.0 4.995528
GRID 1457 -2.49646-0.5 4.995528
GRID 1458 -2.496465.58E-174.995528
GRID 1459 -2.496460.5 4.995528
GRID 1460 -2.496461.0 4.995528
GRID 1461 -2.496461.5 4.995528
GRID 1462 -2.496152.4961524.994037
GRID 1463 -2.496462.0 4.995528
GRID 1464 -2.0 -2.496464.995528
GRID 1465 -2.0 -2.0 5.0
GRID 1466 -2.0 -1.5 5.0
GRID 1467 -2.0 -1.0 5.0
GRID 1468 -2.0 -0.5 5.0
GRID 1469 -2.0 1.05E-165.0
GRID 1470 -2.0 0.5 5.0
GRID 1471 -2.0 1.0 5.0
GRID 1472 -2.0 1.5 5.0
GRID 1473 -2.0 2.4964644.995528
GRID 1474 -2.0 2.0 5.0
GRID 1475 -1.5 -2.496464.995528
GRID 1476 -1.5 -2.0 5.0
GRID 1477 -1.5 -1.5 5.0
GRID 1478 -1.5 -1.0 5.0
GRID 1479 -1.5 -0.5 5.0
GRID 1480 -1.5 1.32E-165.0
GRID 1481 -1.5 0.5 5.0
GRID 1482 -1.5 1.0 5.0
GRID 1483 -1.5 1.5 5.0
GRID 1484 -1.5 2.4964644.995528
GRID 1485 -1.5 2.0 5.0
GRID 1486 -1.0 -2.496464.995528
GRID 1487 -1.0 -2.0 5.0
GRID 1488 -1.0 -1.5 5.0
GRID 1489 -1.0 -1.0 5.0
GRID 1493 -1.0 1.0 5.0

Altair Engineering OptiStruct 13.0 Reference Guide 1485

Proprietary Information of Altair Engineering


GRID 1494 -1.0 1.5 5.0
GRID 1495 -1.0 2.4964644.995528
GRID 1496 -1.0 2.0 5.0
GRID 1497 -0.5 -2.496464.995528
GRID 1498 -0.5 -2.0 5.0
GRID 1499 -0.5 -1.5 5.0
GRID 1500 -0.5 -1.0 5.0
GRID 1504 -0.5 1.0 5.0
GRID 1505 -0.5 1.5 5.0
GRID 1506 -0.5 2.4964644.995528
GRID 1507 -0.5 2.0 5.0
GRID 1508 -1.0E-16-2.496464.995528
GRID 1509 -1.1E-17-2.0 5.0
GRID 1510 2.04E-16-1.5 5.0
GRID 1511 2.61E-16-1.0 5.0
GRID 1515 -1.2E-161.0 5.0
GRID 1516 -1.4E-161.5 5.0
GRID 1517 -2.4E-162.4964644.995528
GRID 1518 -2.4E-162.0 5.0
GRID 1519 0.5 -2.496464.995528
GRID 1520 0.5 -2.0 5.0
GRID 1521 0.5 -1.5 5.0
GRID 1522 0.5 -1.0 5.0
GRID 1526 0.5 1.0 5.0
GRID 1527 0.5 1.5 5.0
GRID 1528 0.5 2.4964644.995528
GRID 1529 0.5 2.0 5.0
GRID 1530 1.0 -2.496464.995528
GRID 1531 1.0 -2.0 5.0
GRID 1532 1.0 -1.5 5.0
GRID 1533 1.0 -1.0 5.0
GRID 1534 1.0 -0.5 5.0
GRID 1535 1.0 -3.0E-165.0
GRID 1536 1.0 0.5 5.0
GRID 1537 1.0 1.0 5.0
GRID 1538 1.0 1.5 5.0
GRID 1539 1.0 2.4964644.995528
GRID 1540 1.0 2.0 5.0
GRID 1541 1.5 -2.496464.995528
GRID 1542 1.5 -2.0 5.0
GRID 1543 1.5 -1.5 5.0
GRID 1544 1.5 -1.0 5.0
GRID 1545 1.5 -0.5 5.0
GRID 1546 1.5 -2.8E-165.0
GRID 1547 1.5 0.5 5.0
GRID 1548 1.5 1.0 5.0
GRID 1549 1.5 1.5 5.0
GRID 1550 1.5 2.4964644.995528
GRID 1551 1.5 2.0 5.0
GRID 1552 2.0 -2.496464.995528
GRID 1553 2.496152-2.496154.994037
GRID 1554 2.0 -2.0 5.0
GRID 1555 2.496464-2.0 4.995528
GRID 1556 2.0 -1.5 5.0
GRID 1557 2.496464-1.5 4.995528
GRID 1558 2.0 -1.0 5.0
GRID 1559 2.496464-1.0 4.995528
GRID 1560 2.0 -0.5 5.0
GRID 1561 2.496464-0.5 4.995528
GRID 1562 2.0 -2.4E-165.0
GRID 1563 2.496464-1.8E-164.995528
GRID 1564 2.0 0.5 5.0
GRID 1565 2.4964640.5 4.995528
GRID 1566 2.0 1.0 5.0
GRID 1567 2.4964641.0 4.995528
GRID 1568 2.0 1.5 5.0
GRID 1569 2.4964641.5 4.995528
GRID 1570 2.0 2.4964644.995528
GRID 1571 2.0 2.0 5.0

1486 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1572 2.4964642.0 4.995528
GRID 1573 2.4961522.4961524.994037
GRID 1574 -2.49776-2.497764.0
GRID 1575 -2.5 -2.0 4.0
GRID 1576 -2.5 -1.5 4.0
GRID 1577 -2.5 -1.0 4.0
GRID 1578 -2.5 -0.5 4.0
GRID 1579 -2.5 1.07E-164.0
GRID 1580 -2.5 0.5 4.0
GRID 1581 -2.5 1.0 4.0
GRID 1582 -2.5 1.5 4.0
GRID 1583 -2.497762.4977644.0
GRID 1584 -2.5 2.0 4.0
GRID 1585 -2.0 -2.5 4.0
GRID 1586 -2.0 2.5 4.0
GRID 1587 -1.5 -2.5 4.0
GRID 1588 -1.5 2.5 4.0
GRID 1589 -1.0 -2.5 4.0
GRID 1590 -1.0 2.5 4.0
GRID 1591 -0.5 -2.5 4.0
GRID 1592 -0.5 2.5 4.0
GRID 1593 -2.5E-16-2.5 4.0
GRID 1594 -2.3E-162.5 4.0
GRID 1595 0.5 -2.5 4.0
GRID 1596 0.5 2.5 4.0
GRID 1597 1.0 -2.5 4.0
GRID 1598 1.0 2.5 4.0
GRID 1599 1.5 -2.5 4.0
GRID 1600 1.5 2.5 4.0
GRID 1601 2.0 -2.5 4.0
GRID 1602 2.497764-2.497764.0
GRID 1603 2.5 -2.0 4.0
GRID 1604 2.5 -1.5 4.0
GRID 1605 2.5 -1.0 4.0
GRID 1606 2.5 -0.5 4.0
GRID 1607 2.5 -1.0E-164.0
GRID 1608 2.5 0.5 4.0
GRID 1609 2.5 1.0 4.0
GRID 1610 2.5 1.5 4.0
GRID 1611 2.0 2.5 4.0
GRID 1612 2.5 2.0 4.0
GRID 1613 2.4977642.4977644.0
GRID 1614 -2.49776-2.497763.0
GRID 1615 -2.5 -2.0 3.0
GRID 1616 -2.5 -1.5 3.0
GRID 1617 -2.5 -1.0 3.0
GRID 1618 -2.5 -0.5 3.0
GRID 1619 -2.5 -5.4E-183.0
GRID 1620 -2.5 0.5 3.0
GRID 1621 -2.5 1.0 3.0
GRID 1622 -2.5 1.5 3.0
GRID 1623 -2.497762.4977643.0
GRID 1624 -2.5 2.0 3.0
GRID 1625 -2.0 -2.5 3.0
GRID 1626 -2.0 2.5 3.0
GRID 1627 -1.5 -2.5 3.0
GRID 1628 -1.5 2.5 3.0
GRID 1629 -1.0 -2.5 3.0
GRID 1630 -1.0 2.5 3.0
GRID 1631 -0.5 -2.5 3.0
GRID 1632 -0.5 2.5 3.0
GRID 1633 -2.9E-18-2.5 3.0
GRID 1634 -3.1E-182.5 3.0
GRID 1635 0.5 -2.5 3.0
GRID 1636 0.5 2.5 3.0
GRID 1637 1.0 -2.5 3.0
GRID 1638 1.0 2.5 3.0
GRID 1639 1.5 -2.5 3.0
GRID 1640 1.5 2.5 3.0

Altair Engineering OptiStruct 13.0 Reference Guide 1487

Proprietary Information of Altair Engineering


GRID 1641 2.0 -2.5 3.0
GRID 1642 2.497764-2.497763.0
GRID 1643 2.5 -2.0 3.0
GRID 1644 2.5 -1.5 3.0
GRID 1645 2.5 -1.0 3.0
GRID 1646 2.5 -0.5 3.0
GRID 1647 2.5 -3.4E-183.0
GRID 1648 2.5 0.5 3.0
GRID 1649 2.5 1.0 3.0
GRID 1650 2.5 1.5 3.0
GRID 1651 2.0 2.5 3.0
GRID 1652 2.5 2.0 3.0
GRID 1653 2.4977642.4977643.0
GRID 1654 -2.49776-2.497762.0
GRID 1655 -2.5 -2.0 2.0
GRID 1656 -2.5 -1.5 2.0
GRID 1657 -2.5 -1.0 2.0
GRID 1658 -2.5 -0.5 2.0
GRID 1659 -2.5 -5.0E-182.0
GRID 1660 -2.5 0.5 2.0
GRID 1661 -2.5 1.0 2.0
GRID 1662 -2.5 1.5 2.0
GRID 1663 -2.497762.4977642.0
GRID 1664 -2.5 2.0 2.0
GRID 1665 -2.0 -2.5 2.0
GRID 1666 -2.0 2.5 2.0
GRID 1667 -1.5 -2.5 2.0
GRID 1668 -1.5 2.5 2.0
GRID 1669 -1.0 -2.5 2.0
GRID 1670 -1.0 2.5 2.0
GRID 1671 -0.5 -2.5 2.0
GRID 1672 -0.5 2.5 2.0
GRID 1673 -2.5E-18-2.5 2.0
GRID 1674 -2.5E-182.5 2.0
GRID 1675 0.5 -2.5 2.0
GRID 1676 0.5 2.5 2.0
GRID 1677 1.0 -2.5 2.0
GRID 1678 1.0 2.5 2.0
GRID 1679 1.5 -2.5 2.0
GRID 1680 1.5 2.5 2.0
GRID 1681 2.0 -2.5 2.0
GRID 1682 2.497764-2.497762.0
GRID 1683 2.5 -2.0 2.0
GRID 1684 2.5 -1.5 2.0
GRID 1685 2.5 -1.0 2.0
GRID 1686 2.5 -0.5 2.0
GRID 1687 2.5 -3.1E-182.0
GRID 1688 2.5 0.5 2.0
GRID 1689 2.5 1.0 2.0
GRID 1690 2.5 1.5 2.0
GRID 1691 2.0 2.5 2.0
GRID 1692 2.5 2.0 2.0
GRID 1693 2.4977642.4977642.0
GRID 1694 -2.49776-2.497761.0
GRID 1695 -2.5 -2.0 1.0
GRID 1696 -2.5 -1.5 1.0
GRID 1697 -2.5 -1.0 1.0
GRID 1698 -2.5 -0.5 1.0
GRID 1699 -2.5 -3.5E-181.0
GRID 1700 -2.5 0.5 1.0
GRID 1701 -2.5 1.0 1.0
GRID 1702 -2.5 1.5 1.0
GRID 1703 -2.497762.4977641.0
GRID 1704 -2.5 2.0 1.0
GRID 1705 -2.0 -2.5 1.0
GRID 1706 -2.0 2.5 1.0
GRID 1707 -1.5 -2.5 1.0
GRID 1708 -1.5 2.5 1.0
GRID 1709 -1.0 -2.5 1.0

1488 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


GRID 1710 -1.0 2.5 1.0
GRID 1711 -0.5 -2.5 1.0
GRID 1712 -0.5 2.5 1.0
GRID 1713 -2.5E-18-2.5 1.0
GRID 1714 -2.5E-182.5 1.0
GRID 1715 0.5 -2.5 1.0
GRID 1716 0.5 2.5 1.0
GRID 1717 1.0 -2.5 1.0
GRID 1718 1.0 2.5 1.0
GRID 1719 1.5 -2.5 1.0
GRID 1720 1.5 2.5 1.0
GRID 1721 2.0 -2.5 1.0
GRID 1722 2.497764-2.497761.0
GRID 1723 2.5 -2.0 1.0
GRID 1724 2.5 -1.5 1.0
GRID 1725 2.5 -1.0 1.0
GRID 1726 2.5 -0.5 1.0
GRID 1727 2.5 -2.9E-181.0
GRID 1728 2.5 0.5 1.0
GRID 1729 2.5 1.0 1.0
GRID 1730 2.5 1.5 1.0
GRID 1731 2.0 2.5 1.0
GRID 1732 2.5 2.0 1.0
GRID 1733 2.4977642.4977641.0
GRID 1734 -0.25 3.33E-165.0
$$
$$ SPOINT Data
$$
$$
$$------------------------------------------------------------------------------$
$$ Group Definitions $
$$------------------------------------------------------------------------------$
$$
$$ RBE2 Elements - Multiple dependent nodes
$$
RBE2 1553 1734 123456 1478 1479 1480 1481 1482+
+ 1489 1493 1500 1504 1511 1515 1522 1526+
+ 1533 1534 1535 1536 1537
$
$HMMOVE 6
$ 1553
$
$ CQUAD4 Elements
$
CQUAD4 1101 4 1332 1341 1342 1333
CQUAD4 1102 4 1333 1342 1343 1334
CQUAD4 1103 4 1334 1343 1344 1335
CQUAD4 1104 4 1335 1344 1345 1336
CQUAD4 1105 4 1336 1345 1346 1337
CQUAD4 1106 4 1337 1346 1347 1338
CQUAD4 1107 4 1338 1347 1348 1339
CQUAD4 1108 4 1339 1348 1349 1340
CQUAD4 1109 4 1341 1350 1351 1342
CQUAD4 1110 4 1342 1351 1352 1343
CQUAD4 1111 4 1343 1352 1353 1344
CQUAD4 1112 4 1344 1353 1354 1345
CQUAD4 1113 4 1345 1354 1355 1346
CQUAD4 1114 4 1346 1355 1356 1347
CQUAD4 1115 4 1347 1356 1357 1348
CQUAD4 1116 4 1348 1357 1358 1349
CQUAD4 1117 4 1350 1359 1360 1351
CQUAD4 1118 4 1351 1360 1361 1352
CQUAD4 1119 4 1352 1361 1362 1353
CQUAD4 1120 4 1353 1362 1363 1354
CQUAD4 1121 4 1354 1363 1364 1355
CQUAD4 1122 4 1355 1364 1365 1356
CQUAD4 1123 4 1356 1365 1366 1357
CQUAD4 1124 4 1357 1366 1367 1358
CQUAD4 1125 4 1359 1368 1369 1360

Altair Engineering OptiStruct 13.0 Reference Guide 1489

Proprietary Information of Altair Engineering


CQUAD4 1126 4 1360 1369 1370 1361
CQUAD4 1127 4 1361 1370 1371 1362
CQUAD4 1128 4 1362 1371 1372 1363
CQUAD4 1129 4 1363 1372 1373 1364
CQUAD4 1130 4 1364 1373 1374 1365
CQUAD4 1131 4 1365 1374 1375 1366
CQUAD4 1132 4 1366 1375 1376 1367
CQUAD4 1133 4 1368 1377 1378 1369
CQUAD4 1134 4 1369 1378 1379 1370
CQUAD4 1135 4 1370 1379 1380 1371
CQUAD4 1136 4 1371 1380 1381 1372
CQUAD4 1137 4 1372 1381 1382 1373
CQUAD4 1138 4 1373 1382 1383 1374
CQUAD4 1139 4 1374 1383 1384 1375
CQUAD4 1140 4 1375 1384 1385 1376
CQUAD4 1141 4 1377 1386 1387 1378
CQUAD4 1142 4 1378 1387 1388 1379
CQUAD4 1143 4 1379 1388 1389 1380
CQUAD4 1144 4 1380 1389 1390 1381
CQUAD4 1145 4 1381 1390 1391 1382
CQUAD4 1146 4 1382 1391 1392 1383
CQUAD4 1147 4 1383 1392 1393 1384
CQUAD4 1148 4 1384 1393 1394 1385
CQUAD4 1149 4 1386 1395 1396 1387
CQUAD4 1150 4 1387 1396 1397 1388
CQUAD4 1151 4 1388 1397 1398 1389
CQUAD4 1152 4 1389 1398 1399 1390
CQUAD4 1153 4 1390 1399 1400 1391
CQUAD4 1154 4 1391 1400 1401 1392
CQUAD4 1155 4 1392 1401 1402 1393
CQUAD4 1156 4 1393 1402 1403 1394
CQUAD4 1157 4 1395 1404 1405 1396
CQUAD4 1158 4 1396 1405 1406 1397
CQUAD4 1159 4 1397 1406 1407 1398
CQUAD4 1160 4 1398 1407 1408 1399
CQUAD4 1161 4 1399 1408 1409 1400
CQUAD4 1162 4 1400 1409 1410 1401
CQUAD4 1163 4 1401 1410 1411 1402
CQUAD4 1164 4 1402 1411 1412 1403
CQUAD4 1165 4 1413 1332 1333 1414
CQUAD4 1166 4 1414 1333 1334 1415
CQUAD4 1167 4 1415 1334 1335 1416
CQUAD4 1168 4 1416 1335 1336 1417
CQUAD4 1169 4 1417 1336 1337 1418
CQUAD4 1170 4 1418 1337 1338 1419
CQUAD4 1171 4 1419 1338 1339 1420
CQUAD4 1172 4 1420 1339 1340 1421
CQUAD4 1173 4 1404 1422 1423 1405
CQUAD4 1174 4 1405 1423 1424 1406
CQUAD4 1175 4 1406 1424 1425 1407
CQUAD4 1176 4 1407 1425 1426 1408
CQUAD4 1177 4 1408 1426 1427 1409
CQUAD4 1178 4 1409 1427 1428 1410
CQUAD4 1179 4 1410 1428 1429 1411
CQUAD4 1180 4 1411 1429 1430 1412
CQUAD4 1181 4 1431 1433 1332 1413
CQUAD4 1182 4 1433 1435 1341 1332
CQUAD4 1183 4 1421 1340 1434 1432
CQUAD4 1184 4 1340 1349 1436 1434
CQUAD4 1185 4 1435 1437 1350 1341
CQUAD4 1186 4 1349 1358 1438 1436
CQUAD4 1187 4 1437 1439 1359 1350
CQUAD4 1188 4 1358 1367 1440 1438
CQUAD4 1189 4 1439 1441 1368 1359
CQUAD4 1190 4 1367 1376 1442 1440
CQUAD4 1191 4 1441 1443 1377 1368
CQUAD4 1192 4 1376 1385 1444 1442
CQUAD4 1193 4 1443 1445 1386 1377
CQUAD4 1194 4 1385 1394 1446 1444

1490 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CQUAD4 1195 4 1445 1447 1395 1386
CQUAD4 1196 4 1394 1403 1448 1446
CQUAD4 1197 4 1447 1449 1404 1395
CQUAD4 1198 4 1403 1412 1450 1448
CQUAD4 1199 4 1449 1451 1422 1404
CQUAD4 1200 4 1412 1430 1452 1450
CQUAD4 1201 4 1431 1733 1731 1433
CQUAD4 1202 4 1413 1732 1733 1431
CQUAD4 1203 4 1414 1730 1732 1413
CQUAD4 1204 4 1433 1731 1720 1435
CQUAD4 1205 4 1415 1729 1730 1414
CQUAD4 1206 4 1416 1728 1729 1415
CQUAD4 1207 4 1417 1727 1728 1416
CQUAD4 1208 4 1418 1726 1727 1417
CQUAD4 1209 4 1419 1725 1726 1418
CQUAD4 1210 4 1420 1724 1725 1419
CQUAD4 1211 4 1421 1723 1724 1420
CQUAD4 1212 4 1432 1722 1723 1421
CQUAD4 1213 4 1434 1721 1722 1432
CQUAD4 1214 4 1436 1719 1721 1434
CQUAD4 1215 4 1435 1720 1718 1437
CQUAD4 1216 4 1438 1717 1719 1436
CQUAD4 1217 4 1437 1718 1716 1439
CQUAD4 1218 4 1440 1715 1717 1438
CQUAD4 1219 4 1439 1716 1714 1441
CQUAD4 1220 4 1442 1713 1715 1440
CQUAD4 1221 4 1441 1714 1712 1443
CQUAD4 1222 4 1444 1711 1713 1442
CQUAD4 1223 4 1443 1712 1710 1445
CQUAD4 1224 4 1446 1709 1711 1444
CQUAD4 1225 4 1445 1710 1708 1447
CQUAD4 1226 4 1448 1707 1709 1446
CQUAD4 1227 4 1447 1708 1706 1449
CQUAD4 1228 4 1450 1705 1707 1448
CQUAD4 1229 4 1449 1706 1703 1451
CQUAD4 1230 4 1452 1694 1705 1450
CQUAD4 1231 4 1451 1703 1704 1422
CQUAD4 1232 4 1422 1704 1702 1423
CQUAD4 1233 4 1423 1702 1701 1424
CQUAD4 1234 4 1424 1701 1700 1425
CQUAD4 1235 4 1425 1700 1699 1426
CQUAD4 1236 4 1426 1699 1698 1427
CQUAD4 1237 4 1427 1698 1697 1428
CQUAD4 1238 4 1428 1697 1696 1429
CQUAD4 1239 4 1429 1696 1695 1430
CQUAD4 1240 4 1430 1695 1694 1452
CQUAD4 1241 4 1732 1692 1693 1733
CQUAD4 1242 4 1733 1693 1691 1731
CQUAD4 1243 4 1730 1690 1692 1732
CQUAD4 1244 4 1731 1691 1680 1720
CQUAD4 1245 4 1729 1689 1690 1730
CQUAD4 1246 4 1728 1688 1689 1729
CQUAD4 1247 4 1727 1687 1688 1728
CQUAD4 1248 4 1726 1686 1687 1727
CQUAD4 1249 4 1725 1685 1686 1726
CQUAD4 1250 4 1724 1684 1685 1725
CQUAD4 1251 4 1723 1683 1684 1724
CQUAD4 1252 4 1722 1682 1683 1723
CQUAD4 1253 4 1721 1681 1682 1722
CQUAD4 1254 4 1719 1679 1681 1721
CQUAD4 1255 4 1720 1680 1678 1718
CQUAD4 1256 4 1717 1677 1679 1719
CQUAD4 1257 4 1718 1678 1676 1716
CQUAD4 1258 4 1715 1675 1677 1717
CQUAD4 1259 4 1716 1676 1674 1714
CQUAD4 1260 4 1713 1673 1675 1715
CQUAD4 1261 4 1714 1674 1672 1712
CQUAD4 1262 4 1711 1671 1673 1713
CQUAD4 1263 4 1712 1672 1670 1710

Altair Engineering OptiStruct 13.0 Reference Guide 1491

Proprietary Information of Altair Engineering


CQUAD4 1264 4 1709 1669 1671 1711
CQUAD4 1265 4 1710 1670 1668 1708
CQUAD4 1266 4 1707 1667 1669 1709
CQUAD4 1267 4 1708 1668 1666 1706
CQUAD4 1268 4 1705 1665 1667 1707
CQUAD4 1269 4 1706 1666 1663 1703
CQUAD4 1270 4 1694 1654 1665 1705
CQUAD4 1271 4 1703 1663 1664 1704
CQUAD4 1272 4 1704 1664 1662 1702
CQUAD4 1273 4 1702 1662 1661 1701
CQUAD4 1274 4 1701 1661 1660 1700
CQUAD4 1275 4 1700 1660 1659 1699
CQUAD4 1276 4 1699 1659 1658 1698
CQUAD4 1277 4 1698 1658 1657 1697
CQUAD4 1278 4 1697 1657 1656 1696
CQUAD4 1279 4 1696 1656 1655 1695
CQUAD4 1280 4 1695 1655 1654 1694
CQUAD4 1281 4 1692 1652 1653 1693
CQUAD4 1282 4 1693 1653 1651 1691
CQUAD4 1283 4 1690 1650 1652 1692
CQUAD4 1284 4 1691 1651 1640 1680
CQUAD4 1285 4 1689 1649 1650 1690
CQUAD4 1286 4 1688 1648 1649 1689
CQUAD4 1287 4 1687 1647 1648 1688
CQUAD4 1288 4 1686 1646 1647 1687
CQUAD4 1289 4 1685 1645 1646 1686
CQUAD4 1290 4 1684 1644 1645 1685
CQUAD4 1291 4 1683 1643 1644 1684
CQUAD4 1292 4 1682 1642 1643 1683
CQUAD4 1293 4 1681 1641 1642 1682
CQUAD4 1294 4 1679 1639 1641 1681
CQUAD4 1295 4 1680 1640 1638 1678
CQUAD4 1296 4 1677 1637 1639 1679
CQUAD4 1297 4 1678 1638 1636 1676
CQUAD4 1298 4 1675 1635 1637 1677
CQUAD4 1299 4 1676 1636 1634 1674
CQUAD4 1300 4 1673 1633 1635 1675
CQUAD4 1301 4 1674 1634 1632 1672
CQUAD4 1302 4 1671 1631 1633 1673
CQUAD4 1303 4 1672 1632 1630 1670
CQUAD4 1304 4 1669 1629 1631 1671
CQUAD4 1305 4 1670 1630 1628 1668
CQUAD4 1306 4 1667 1627 1629 1669
CQUAD4 1307 4 1668 1628 1626 1666
CQUAD4 1308 4 1665 1625 1627 1667
CQUAD4 1309 4 1666 1626 1623 1663
CQUAD4 1310 4 1654 1614 1625 1665
CQUAD4 1311 4 1663 1623 1624 1664
CQUAD4 1312 4 1664 1624 1622 1662
CQUAD4 1313 4 1662 1622 1621 1661
CQUAD4 1314 4 1661 1621 1620 1660
CQUAD4 1315 4 1660 1620 1619 1659
CQUAD4 1316 4 1659 1619 1618 1658
CQUAD4 1317 4 1658 1618 1617 1657
CQUAD4 1318 4 1657 1617 1616 1656
CQUAD4 1319 4 1656 1616 1615 1655
CQUAD4 1320 4 1655 1615 1614 1654
CQUAD4 1321 4 1652 1612 1613 1653
CQUAD4 1322 4 1653 1613 1611 1651
CQUAD4 1323 4 1650 1610 1612 1652
CQUAD4 1324 4 1651 1611 1600 1640
CQUAD4 1325 4 1649 1609 1610 1650
CQUAD4 1326 4 1648 1608 1609 1649
CQUAD4 1327 4 1647 1607 1608 1648
CQUAD4 1328 4 1646 1606 1607 1647
CQUAD4 1329 4 1645 1605 1606 1646
CQUAD4 1330 4 1644 1604 1605 1645
CQUAD4 1331 4 1643 1603 1604 1644
CQUAD4 1332 4 1642 1602 1603 1643

1492 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CQUAD4 1333 4 1641 1601 1602 1642
CQUAD4 1334 4 1639 1599 1601 1641
CQUAD4 1335 4 1640 1600 1598 1638
CQUAD4 1336 4 1637 1597 1599 1639
CQUAD4 1337 4 1638 1598 1596 1636
CQUAD4 1338 4 1635 1595 1597 1637
CQUAD4 1339 4 1636 1596 1594 1634
CQUAD4 1340 4 1633 1593 1595 1635
CQUAD4 1341 4 1634 1594 1592 1632
CQUAD4 1342 4 1631 1591 1593 1633
CQUAD4 1343 4 1632 1592 1590 1630
CQUAD4 1344 4 1629 1589 1591 1631
CQUAD4 1345 4 1630 1590 1588 1628
CQUAD4 1346 4 1627 1587 1589 1629
CQUAD4 1347 4 1628 1588 1586 1626
CQUAD4 1348 4 1625 1585 1587 1627
CQUAD4 1349 4 1626 1586 1583 1623
CQUAD4 1350 4 1614 1574 1585 1625
CQUAD4 1351 4 1623 1583 1584 1624
CQUAD4 1352 4 1624 1584 1582 1622
CQUAD4 1353 4 1622 1582 1581 1621
CQUAD4 1354 4 1621 1581 1580 1620
CQUAD4 1355 4 1620 1580 1579 1619
CQUAD4 1356 4 1619 1579 1578 1618
CQUAD4 1357 4 1618 1578 1577 1617
CQUAD4 1358 4 1617 1577 1576 1616
CQUAD4 1359 4 1616 1576 1575 1615
CQUAD4 1360 4 1615 1575 1574 1614
CQUAD4 1361 4 1612 1572 1573 1613
CQUAD4 1362 4 1613 1573 1570 1611
CQUAD4 1363 4 1610 1569 1572 1612
CQUAD4 1364 4 1572 1571 1570 1573
CQUAD4 1365 4 1611 1570 1550 1600
CQUAD4 1366 4 1569 1568 1571 1572
CQUAD4 1367 4 1609 1567 1569 1610
CQUAD4 1368 4 1567 1566 1568 1569
CQUAD4 1369 4 1608 1565 1567 1609
CQUAD4 1370 4 1565 1564 1566 1567
CQUAD4 1371 4 1607 1563 1565 1608
CQUAD4 1372 4 1563 1562 1564 1565
CQUAD4 1373 4 1606 1561 1563 1607
CQUAD4 1374 4 1561 1560 1562 1563
CQUAD4 1375 4 1605 1559 1561 1606
CQUAD4 1376 4 1559 1558 1560 1561
CQUAD4 1377 4 1604 1557 1559 1605
CQUAD4 1378 4 1557 1556 1558 1559
CQUAD4 1379 4 1603 1555 1557 1604
CQUAD4 1380 4 1555 1554 1556 1557
CQUAD4 1381 4 1602 1553 1555 1603
CQUAD4 1382 4 1601 1552 1553 1602
CQUAD4 1383 4 1553 1552 1554 1555
CQUAD4 1384 4 1599 1541 1552 1601
CQUAD4 1385 4 1571 1551 1550 1570
CQUAD4 1386 4 1568 1549 1551 1571
CQUAD4 1387 4 1600 1550 1539 1598
CQUAD4 1388 4 1566 1548 1549 1568
CQUAD4 1389 4 1564 1547 1548 1566
CQUAD4 1390 4 1562 1546 1547 1564
CQUAD4 1391 4 1560 1545 1546 1562
CQUAD4 1392 4 1558 1544 1545 1560
CQUAD4 1393 4 1556 1543 1544 1558
CQUAD4 1394 4 1554 1542 1543 1556
CQUAD4 1395 4 1552 1541 1542 1554
CQUAD4 1396 4 1597 1530 1541 1599
CQUAD4 1397 4 1551 1540 1539 1550
CQUAD4 1398 4 1549 1538 1540 1551
CQUAD4 1399 4 1598 1539 1528 1596
CQUAD4 1400 4 1548 1537 1538 1549
CQUAD4 1401 4 1547 1536 1537 1548

Altair Engineering OptiStruct 13.0 Reference Guide 1493

Proprietary Information of Altair Engineering


CQUAD4 1402 4 1546 1535 1536 1547
CQUAD4 1403 4 1545 1534 1535 1546
CQUAD4 1404 4 1544 1533 1534 1545
CQUAD4 1405 4 1543 1532 1533 1544
CQUAD4 1406 4 1542 1531 1532 1543
CQUAD4 1407 4 1541 1530 1531 1542
CQUAD4 1408 4 1595 1519 1530 1597
CQUAD4 1409 4 1540 1529 1528 1539
CQUAD4 1410 4 1538 1527 1529 1540
CQUAD4 1411 4 1596 1528 1517 1594
CQUAD4 1412 4 1537 1526 1527 1538
CQUAD4 1417 4 1532 1521 1522 1533
CQUAD4 1418 4 1531 1520 1521 1532
CQUAD4 1419 4 1530 1519 1520 1531
CQUAD4 1420 4 1593 1508 1519 1595
CQUAD4 1421 4 1529 1518 1517 1528
CQUAD4 1422 4 1527 1516 1518 1529
CQUAD4 1423 4 1594 1517 1506 1592
CQUAD4 1424 4 1526 1515 1516 1527
CQUAD4 1429 4 1521 1510 1511 1522
CQUAD4 1430 4 1520 1509 1510 1521
CQUAD4 1431 4 1519 1508 1509 1520
CQUAD4 1432 4 1591 1497 1508 1593
CQUAD4 1433 4 1518 1507 1506 1517
CQUAD4 1434 4 1516 1505 1507 1518
CQUAD4 1435 4 1592 1506 1495 1590
CQUAD4 1436 4 1515 1504 1505 1516
CQUAD4 1441 4 1510 1499 1500 1511
CQUAD4 1442 4 1509 1498 1499 1510
CQUAD4 1443 4 1508 1497 1498 1509
CQUAD4 1444 4 1589 1486 1497 1591
CQUAD4 1445 4 1507 1496 1495 1506
CQUAD4 1446 4 1505 1494 1496 1507
CQUAD4 1447 4 1590 1495 1484 1588
CQUAD4 1448 4 1504 1493 1494 1505
CQUAD4 1453 4 1499 1488 1489 1500
CQUAD4 1454 4 1498 1487 1488 1499
CQUAD4 1455 4 1497 1486 1487 1498
CQUAD4 1456 4 1587 1475 1486 1589
CQUAD4 1457 4 1496 1485 1484 1495
CQUAD4 1458 4 1494 1483 1485 1496
CQUAD4 1459 4 1588 1484 1473 1586
CQUAD4 1460 4 1493 1482 1483 1494
CQUAD4 1465 4 1488 1477 1478 1489
CQUAD4 1466 4 1487 1476 1477 1488
CQUAD4 1467 4 1486 1475 1476 1487
CQUAD4 1468 4 1585 1464 1475 1587
CQUAD4 1469 4 1485 1474 1473 1484
CQUAD4 1470 4 1483 1472 1474 1485
CQUAD4 1471 4 1586 1473 1462 1583
CQUAD4 1472 4 1482 1471 1472 1483
CQUAD4 1473 4 1481 1470 1471 1482
CQUAD4 1474 4 1480 1469 1470 1481
CQUAD4 1475 4 1479 1468 1469 1480
CQUAD4 1476 4 1478 1467 1468 1479
CQUAD4 1477 4 1477 1466 1467 1478
CQUAD4 1478 4 1476 1465 1466 1477
CQUAD4 1479 4 1475 1464 1465 1476
CQUAD4 1480 4 1574 1453 1464 1585
CQUAD4 1481 4 1583 1462 1463 1584
CQUAD4 1482 4 1474 1463 1462 1473
CQUAD4 1483 4 1584 1463 1461 1582
CQUAD4 1484 4 1472 1461 1463 1474
CQUAD4 1485 4 1582 1461 1460 1581
CQUAD4 1486 4 1471 1460 1461 1472
CQUAD4 1487 4 1581 1460 1459 1580
CQUAD4 1488 4 1470 1459 1460 1471
CQUAD4 1489 4 1580 1459 1458 1579
CQUAD4 1490 4 1469 1458 1459 1470

1494 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CQUAD4 1491 4 1579 1458 1457 1578
CQUAD4 1492 4 1468 1457 1458 1469
CQUAD4 1493 4 1578 1457 1456 1577
CQUAD4 1494 4 1467 1456 1457 1468
CQUAD4 1495 4 1577 1456 1455 1576
CQUAD4 1496 4 1466 1455 1456 1467
CQUAD4 1497 4 1576 1455 1454 1575
CQUAD4 1498 4 1465 1454 1455 1466
CQUAD4 1499 4 1575 1454 1453 1574
CQUAD4 1500 4 1464 1453 1454 1465
$
$ CHEXA Elements: First Order
$
CHEXA 601 1 100 102 1 82 727 730+
+ 729 728
CHEXA 602 1 82 1 2 83 728 729+
+ 732 731
CHEXA 603 1 83 2 3 84 731 732+
+ 734 733
CHEXA 604 1 84 3 4 85 733 734+
+ 736 735
CHEXA 605 1 85 4 5 86 735 736+
+ 738 737
CHEXA 606 1 86 5 6 87 737 738+
+ 740 739
CHEXA 607 1 87 6 7 88 739 740+
+ 742 741
CHEXA 608 1 88 7 8 89 741 742+
+ 744 743
CHEXA 609 1 89 8 9 90 743 744+
+ 746 745
CHEXA 610 1 90 9 103 101 745 746+
+ 748 747
CHEXA 611 1 102 104 10 1 730 750+
+ 749 729
CHEXA 612 1 1 10 11 2 729 749+
+ 751 732
CHEXA 613 1 2 11 12 3 732 751+
+ 752 734
CHEXA 614 1 3 12 13 4 734 752+
+ 753 736
CHEXA 615 1 4 13 14 5 736 753+
+ 754 738
CHEXA 616 1 5 14 15 6 738 754+
+ 755 740
CHEXA 617 1 6 15 16 7 740 755+
+ 756 742
CHEXA 618 1 7 16 17 8 742 756+
+ 757 744
CHEXA 619 1 8 17 18 9 744 757+
+ 758 746
CHEXA 620 1 9 18 105 103 746 758+
+ 759 748
CHEXA 621 1 104 106 19 10 750 761+
+ 760 749
CHEXA 622 1 10 19 20 11 749 760+
+ 762 751
CHEXA 623 1 11 20 21 12 751 762+
+ 763 752
CHEXA 624 1 12 21 22 13 752 763+
+ 764 753
CHEXA 625 1 13 22 23 14 753 764+
+ 765 754
CHEXA 626 1 14 23 24 15 754 765+
+ 766 755
CHEXA 627 1 15 24 25 16 755 766+
+ 767 756
CHEXA 628 1 16 25 26 17 756 767+
+ 768 757

Altair Engineering OptiStruct 13.0 Reference Guide 1495

Proprietary Information of Altair Engineering


CHEXA 629 1 17 26 27 18 757 768+
+ 769 758
CHEXA 630 1 18 27 107 105 758 769+
+ 770 759
CHEXA 631 1 106 108 28 19 761 772+
+ 771 760
CHEXA 632 1 19 28 29 20 760 771+
+ 773 762
CHEXA 633 1 20 29 30 21 762 773+
+ 774 763
CHEXA 634 1 21 30 31 22 763 774+
+ 775 764
CHEXA 635 1 22 31 32 23 764 775+
+ 776 765
CHEXA 636 1 23 32 33 24 765 776+
+ 777 766
CHEXA 637 1 24 33 34 25 766 777+
+ 778 767
CHEXA 638 1 25 34 35 26 767 778+
+ 779 768
CHEXA 639 1 26 35 36 27 768 779+
+ 780 769
CHEXA 640 1 27 36 109 107 769 780+
+ 781 770
CHEXA 641 1 108 110 37 28 772 783+
+ 782 771
CHEXA 642 1 28 37 38 29 771 782+
+ 784 773
CHEXA 643 1 29 38 39 30 773 784+
+ 785 774
CHEXA 644 1 30 39 40 31 774 785+
+ 786 775
CHEXA 645 1 31 40 41 32 775 786+
+ 787 776
CHEXA 646 1 32 41 42 33 776 787+
+ 788 777
CHEXA 647 1 33 42 43 34 777 788+
+ 789 778
CHEXA 648 1 34 43 44 35 778 789+
+ 790 779
CHEXA 649 1 35 44 45 36 779 790+
+ 791 780
CHEXA 650 1 36 45 111 109 780 791+
+ 792 781
CHEXA 651 1 110 112 46 37 783 794+
+ 793 782
CHEXA 652 1 37 46 47 38 782 793+
+ 795 784
CHEXA 653 1 38 47 48 39 784 795+
+ 796 785
CHEXA 654 1 39 48 49 40 785 796+
+ 797 786
CHEXA 655 1 40 49 50 41 786 797+
+ 798 787
CHEXA 656 1 41 50 51 42 787 798+
+ 799 788
CHEXA 657 1 42 51 52 43 788 799+
+ 800 789
CHEXA 658 1 43 52 53 44 789 800+
+ 801 790
CHEXA 659 1 44 53 54 45 790 801+
+ 802 791
CHEXA 660 1 45 54 113 111 791 802+
+ 803 792
CHEXA 661 1 112 114 55 46 794 805+
+ 804 793
CHEXA 662 1 46 55 56 47 793 804+
+ 806 795
CHEXA 663 1 47 56 57 48 795 806+

1496 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 807 796
CHEXA 664 1 48 57 58 49 796 807+
+ 808 797
CHEXA 665 1 49 58 59 50 797 808+
+ 809 798
CHEXA 666 1 50 59 60 51 798 809+
+ 810 799
CHEXA 667 1 51 60 61 52 799 810+
+ 811 800
CHEXA 668 1 52 61 62 53 800 811+
+ 812 801
CHEXA 669 1 53 62 63 54 801 812+
+ 813 802
CHEXA 670 1 54 63 115 113 802 813+
+ 814 803
CHEXA 671 1 114 116 64 55 805 816+
+ 815 804
CHEXA 672 1 55 64 65 56 804 815+
+ 817 806
CHEXA 673 1 56 65 66 57 806 817+
+ 818 807
CHEXA 674 1 57 66 67 58 807 818+
+ 819 808
CHEXA 675 1 58 67 68 59 808 819+
+ 820 809
CHEXA 676 1 59 68 69 60 809 820+
+ 821 810
CHEXA 677 1 60 69 70 61 810 821+
+ 822 811
CHEXA 678 1 61 70 71 62 811 822+
+ 823 812
CHEXA 679 1 62 71 72 63 812 823+
+ 824 813
CHEXA 680 1 63 72 117 115 813 824+
+ 825 814
CHEXA 681 1 116 118 73 64 816 827+
+ 826 815
CHEXA 682 1 64 73 74 65 815 826+
+ 828 817
CHEXA 683 1 65 74 75 66 817 828+
+ 829 818
CHEXA 684 1 66 75 76 67 818 829+
+ 830 819
CHEXA 685 1 67 76 77 68 819 830+
+ 831 820
CHEXA 686 1 68 77 78 69 820 831+
+ 832 821
CHEXA 687 1 69 78 79 70 821 832+
+ 833 822
CHEXA 688 1 70 79 80 71 822 833+
+ 834 823
CHEXA 689 1 71 80 81 72 823 834+
+ 835 824
CHEXA 690 1 72 81 119 117 824 835+
+ 836 825
CHEXA 691 1 118 120 91 73 827 838+
+ 837 826
CHEXA 692 1 73 91 92 74 826 837+
+ 839 828
CHEXA 693 1 74 92 93 75 828 839+
+ 840 829
CHEXA 694 1 75 93 94 76 829 840+
+ 841 830
CHEXA 695 1 76 94 95 77 830 841+
+ 842 831
CHEXA 696 1 77 95 96 78 831 842+
+ 843 832
CHEXA 697 1 78 96 97 79 832 843+
+ 844 833

Altair Engineering OptiStruct 13.0 Reference Guide 1497

Proprietary Information of Altair Engineering


CHEXA 698 1 79 97 98 80 833 844+
+ 845 834
CHEXA 699 1 80 98 99 81 834 845+
+ 846 835
CHEXA 700 1 81 99 121 119 835 846+
+ 847 836
CHEXA 701 1 727 730 729 728 848 851+
+ 850 849
CHEXA 702 1 728 729 732 731 849 850+
+ 853 852
CHEXA 703 1 731 732 734 733 852 853+
+ 855 854
CHEXA 704 1 733 734 736 735 854 855+
+ 857 856
CHEXA 705 1 735 736 738 737 856 857+
+ 859 858
CHEXA 706 1 737 738 740 739 858 859+
+ 861 860
CHEXA 707 1 739 740 742 741 860 861+
+ 863 862
CHEXA 708 1 741 742 744 743 862 863+
+ 865 864
CHEXA 709 1 743 744 746 745 864 865+
+ 867 866
CHEXA 710 1 745 746 748 747 866 867+
+ 869 868
CHEXA 711 1 730 750 749 729 851 871+
+ 870 850
CHEXA 712 1 729 749 751 732 850 870+
+ 872 853
CHEXA 713 1 732 751 752 734 853 872+
+ 873 855
CHEXA 714 1 734 752 753 736 855 873+
+ 874 857
CHEXA 715 1 736 753 754 738 857 874+
+ 875 859
CHEXA 716 1 738 754 755 740 859 875+
+ 876 861
CHEXA 717 1 740 755 756 742 861 876+
+ 877 863
CHEXA 718 1 742 756 757 744 863 877+
+ 878 865
CHEXA 719 1 744 757 758 746 865 878+
+ 879 867
CHEXA 720 1 746 758 759 748 867 879+
+ 880 869
CHEXA 721 1 750 761 760 749 871 882+
+ 881 870
CHEXA 722 1 749 760 762 751 870 881+
+ 883 872
CHEXA 723 1 751 762 763 752 872 883+
+ 884 873
CHEXA 724 1 752 763 764 753 873 884+
+ 885 874
CHEXA 725 1 753 764 765 754 874 885+
+ 886 875
CHEXA 726 1 754 765 766 755 875 886+
+ 887 876
CHEXA 727 1 755 766 767 756 876 887+
+ 888 877
CHEXA 728 1 756 767 768 757 877 888+
+ 889 878
CHEXA 729 1 757 768 769 758 878 889+
+ 890 879
CHEXA 730 1 758 769 770 759 879 890+
+ 891 880
CHEXA 731 1 761 772 771 760 882 893+
+ 892 881
CHEXA 732 1 760 771 773 762 881 892+

1498 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 894 883
CHEXA 733 1 762 773 774 763 883 894+
+ 895 884
CHEXA 734 1 763 774 775 764 884 895+
+ 896 885
CHEXA 735 1 764 775 776 765 885 896+
+ 897 886
CHEXA 736 1 765 776 777 766 886 897+
+ 898 887
CHEXA 737 1 766 777 778 767 887 898+
+ 899 888
CHEXA 738 1 767 778 779 768 888 899+
+ 900 889
CHEXA 739 1 768 779 780 769 889 900+
+ 901 890
CHEXA 740 1 769 780 781 770 890 901+
+ 902 891
CHEXA 741 1 772 783 782 771 893 904+
+ 903 892
CHEXA 742 1 771 782 784 773 892 903+
+ 905 894
CHEXA 743 1 773 784 785 774 894 905+
+ 906 895
CHEXA 744 1 774 785 786 775 895 906+
+ 907 896
CHEXA 745 1 775 786 787 776 896 907+
+ 908 897
CHEXA 746 1 776 787 788 777 897 908+
+ 909 898
CHEXA 747 1 777 788 789 778 898 909+
+ 910 899
CHEXA 748 1 778 789 790 779 899 910+
+ 911 900
CHEXA 749 1 779 790 791 780 900 911+
+ 912 901
CHEXA 750 1 780 791 792 781 901 912+
+ 913 902
CHEXA 751 1 783 794 793 782 904 915+
+ 914 903
CHEXA 752 1 782 793 795 784 903 914+
+ 916 905
CHEXA 753 1 784 795 796 785 905 916+
+ 917 906
CHEXA 754 1 785 796 797 786 906 917+
+ 918 907
CHEXA 755 1 786 797 798 787 907 918+
+ 919 908
CHEXA 756 1 787 798 799 788 908 919+
+ 920 909
CHEXA 757 1 788 799 800 789 909 920+
+ 921 910
CHEXA 758 1 789 800 801 790 910 921+
+ 922 911
CHEXA 759 1 790 801 802 791 911 922+
+ 923 912
CHEXA 760 1 791 802 803 792 912 923+
+ 924 913
CHEXA 761 1 794 805 804 793 915 926+
+ 925 914
CHEXA 762 1 793 804 806 795 914 925+
+ 927 916
CHEXA 763 1 795 806 807 796 916 927+
+ 928 917
CHEXA 764 1 796 807 808 797 917 928+
+ 929 918
CHEXA 765 1 797 808 809 798 918 929+
+ 930 919
CHEXA 766 1 798 809 810 799 919 930+
+ 931 920

Altair Engineering OptiStruct 13.0 Reference Guide 1499

Proprietary Information of Altair Engineering


CHEXA 767 1 799 810 811 800 920 931+
+ 932 921
CHEXA 768 1 800 811 812 801 921 932+
+ 933 922
CHEXA 769 1 801 812 813 802 922 933+
+ 934 923
CHEXA 770 1 802 813 814 803 923 934+
+ 935 924
CHEXA 771 1 805 816 815 804 926 937+
+ 936 925
CHEXA 772 1 804 815 817 806 925 936+
+ 938 927
CHEXA 773 1 806 817 818 807 927 938+
+ 939 928
CHEXA 774 1 807 818 819 808 928 939+
+ 940 929
CHEXA 775 1 808 819 820 809 929 940+
+ 941 930
CHEXA 776 1 809 820 821 810 930 941+
+ 942 931
CHEXA 777 1 810 821 822 811 931 942+
+ 943 932
CHEXA 778 1 811 822 823 812 932 943+
+ 944 933
CHEXA 779 1 812 823 824 813 933 944+
+ 945 934
CHEXA 780 1 813 824 825 814 934 945+
+ 946 935
CHEXA 781 1 816 827 826 815 937 948+
+ 947 936
CHEXA 782 1 815 826 828 817 936 947+
+ 949 938
CHEXA 783 1 817 828 829 818 938 949+
+ 950 939
CHEXA 784 1 818 829 830 819 939 950+
+ 951 940
CHEXA 785 1 819 830 831 820 940 951+
+ 952 941
CHEXA 786 1 820 831 832 821 941 952+
+ 953 942
CHEXA 787 1 821 832 833 822 942 953+
+ 954 943
CHEXA 788 1 822 833 834 823 943 954+
+ 955 944
CHEXA 789 1 823 834 835 824 944 955+
+ 956 945
CHEXA 790 1 824 835 836 825 945 956+
+ 957 946
CHEXA 791 1 827 838 837 826 948 959+
+ 958 947
CHEXA 792 1 826 837 839 828 947 958+
+ 960 949
CHEXA 793 1 828 839 840 829 949 960+
+ 961 950
CHEXA 794 1 829 840 841 830 950 961+
+ 962 951
CHEXA 795 1 830 841 842 831 951 962+
+ 963 952
CHEXA 796 1 831 842 843 832 952 963+
+ 964 953
CHEXA 797 1 832 843 844 833 953 964+
+ 965 954
CHEXA 798 1 833 844 845 834 954 965+
+ 966 955
CHEXA 799 1 834 845 846 835 955 966+
+ 967 956
CHEXA 800 1 835 846 847 836 956 967+
+ 968 957
CHEXA 801 1 848 851 850 849 969 972+

1500 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 971 970
CHEXA 802 1 849 850 853 852 970 971+
+ 974 973
CHEXA 803 1 852 853 855 854 973 974+
+ 976 975
CHEXA 804 1 854 855 857 856 975 976+
+ 978 977
CHEXA 805 1 856 857 859 858 977 978+
+ 980 979
CHEXA 806 1 858 859 861 860 979 980+
+ 982 981
CHEXA 807 1 860 861 863 862 981 982+
+ 984 983
CHEXA 808 1 862 863 865 864 983 984+
+ 986 985
CHEXA 809 1 864 865 867 866 985 986+
+ 988 987
CHEXA 810 1 866 867 869 868 987 988+
+ 990 989
CHEXA 811 1 851 871 870 850 972 992+
+ 991 971
CHEXA 812 1 850 870 872 853 971 991+
+ 993 974
CHEXA 813 1 853 872 873 855 974 993+
+ 994 976
CHEXA 814 1 855 873 874 857 976 994+
+ 995 978
CHEXA 815 1 857 874 875 859 978 995+
+ 996 980
CHEXA 816 1 859 875 876 861 980 996+
+ 997 982
CHEXA 817 1 861 876 877 863 982 997+
+ 998 984
CHEXA 818 1 863 877 878 865 984 998+
+ 999 986
CHEXA 819 1 865 878 879 867 986 999+
+ 1000 988
CHEXA 820 1 867 879 880 869 988 1000+
+ 1001 990
CHEXA 821 1 871 882 881 870 992 1003+
+ 1002 991
CHEXA 822 1 870 881 883 872 991 1002+
+ 1004 993
CHEXA 823 1 872 883 884 873 993 1004+
+ 1005 994
CHEXA 824 1 873 884 885 874 994 1005+
+ 1006 995
CHEXA 825 1 874 885 886 875 995 1006+
+ 1007 996
CHEXA 826 1 875 886 887 876 996 1007+
+ 1008 997
CHEXA 827 1 876 887 888 877 997 1008+
+ 1009 998
CHEXA 828 1 877 888 889 878 998 1009+
+ 1010 999
CHEXA 829 1 878 889 890 879 999 1010+
+ 1011 1000
CHEXA 830 1 879 890 891 880 1000 1011+
+ 1012 1001
CHEXA 831 1 882 893 892 881 1003 1014+
+ 1013 1002
CHEXA 832 1 881 892 894 883 1002 1013+
+ 1015 1004
CHEXA 833 1 883 894 895 884 1004 1015+
+ 1016 1005
CHEXA 834 1 884 895 896 885 1005 1016+
+ 1017 1006
CHEXA 835 1 885 896 897 886 1006 1017+
+ 1018 1007

Altair Engineering OptiStruct 13.0 Reference Guide 1501

Proprietary Information of Altair Engineering


CHEXA 836 1 886 897 898 887 1007 1018+
+ 1019 1008
CHEXA 837 1 887 898 899 888 1008 1019+
+ 1020 1009
CHEXA 838 1 888 899 900 889 1009 1020+
+ 1021 1010
CHEXA 839 1 889 900 901 890 1010 1021+
+ 1022 1011
CHEXA 840 1 890 901 902 891 1011 1022+
+ 1023 1012
CHEXA 841 1 893 904 903 892 1014 1025+
+ 1024 1013
CHEXA 842 1 892 903 905 894 1013 1024+
+ 1026 1015
CHEXA 843 1 894 905 906 895 1015 1026+
+ 1027 1016
CHEXA 844 1 895 906 907 896 1016 1027+
+ 1028 1017
CHEXA 845 1 896 907 908 897 1017 1028+
+ 1029 1018
CHEXA 846 1 897 908 909 898 1018 1029+
+ 1030 1019
CHEXA 847 1 898 909 910 899 1019 1030+
+ 1031 1020
CHEXA 848 1 899 910 911 900 1020 1031+
+ 1032 1021
CHEXA 849 1 900 911 912 901 1021 1032+
+ 1033 1022
CHEXA 850 1 901 912 913 902 1022 1033+
+ 1034 1023
CHEXA 851 1 904 915 914 903 1025 1036+
+ 1035 1024
CHEXA 852 1 903 914 916 905 1024 1035+
+ 1037 1026
CHEXA 853 1 905 916 917 906 1026 1037+
+ 1038 1027
CHEXA 854 1 906 917 918 907 1027 1038+
+ 1039 1028
CHEXA 855 1 907 918 919 908 1028 1039+
+ 1040 1029
CHEXA 856 1 908 919 920 909 1029 1040+
+ 1041 1030
CHEXA 857 1 909 920 921 910 1030 1041+
+ 1042 1031
CHEXA 858 1 910 921 922 911 1031 1042+
+ 1043 1032
CHEXA 859 1 911 922 923 912 1032 1043+
+ 1044 1033
CHEXA 860 1 912 923 924 913 1033 1044+
+ 1045 1034
CHEXA 861 1 915 926 925 914 1036 1047+
+ 1046 1035
CHEXA 862 1 914 925 927 916 1035 1046+
+ 1048 1037
CHEXA 863 1 916 927 928 917 1037 1048+
+ 1049 1038
CHEXA 864 1 917 928 929 918 1038 1049+
+ 1050 1039
CHEXA 865 1 918 929 930 919 1039 1050+
+ 1051 1040
CHEXA 866 1 919 930 931 920 1040 1051+
+ 1052 1041
CHEXA 867 1 920 931 932 921 1041 1052+
+ 1053 1042
CHEXA 868 1 921 932 933 922 1042 1053+
+ 1054 1043
CHEXA 869 1 922 933 934 923 1043 1054+
+ 1055 1044
CHEXA 870 1 923 934 935 924 1044 1055+

1502 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 1056 1045
CHEXA 871 1 926 937 936 925 1047 1058+
+ 1057 1046
CHEXA 872 1 925 936 938 927 1046 1057+
+ 1059 1048
CHEXA 873 1 927 938 939 928 1048 1059+
+ 1060 1049
CHEXA 874 1 928 939 940 929 1049 1060+
+ 1061 1050
CHEXA 875 1 929 940 941 930 1050 1061+
+ 1062 1051
CHEXA 876 1 930 941 942 931 1051 1062+
+ 1063 1052
CHEXA 877 1 931 942 943 932 1052 1063+
+ 1064 1053
CHEXA 878 1 932 943 944 933 1053 1064+
+ 1065 1054
CHEXA 879 1 933 944 945 934 1054 1065+
+ 1066 1055
CHEXA 880 1 934 945 946 935 1055 1066+
+ 1067 1056
CHEXA 881 1 937 948 947 936 1058 1069+
+ 1068 1057
CHEXA 882 1 936 947 949 938 1057 1068+
+ 1070 1059
CHEXA 883 1 938 949 950 939 1059 1070+
+ 1071 1060
CHEXA 884 1 939 950 951 940 1060 1071+
+ 1072 1061
CHEXA 885 1 940 951 952 941 1061 1072+
+ 1073 1062
CHEXA 886 1 941 952 953 942 1062 1073+
+ 1074 1063
CHEXA 887 1 942 953 954 943 1063 1074+
+ 1075 1064
CHEXA 888 1 943 954 955 944 1064 1075+
+ 1076 1065
CHEXA 889 1 944 955 956 945 1065 1076+
+ 1077 1066
CHEXA 890 1 945 956 957 946 1066 1077+
+ 1078 1067
CHEXA 891 1 948 959 958 947 1069 1080+
+ 1079 1068
CHEXA 892 1 947 958 960 949 1068 1079+
+ 1081 1070
CHEXA 893 1 949 960 961 950 1070 1081+
+ 1082 1071
CHEXA 894 1 950 961 962 951 1071 1082+
+ 1083 1072
CHEXA 895 1 951 962 963 952 1072 1083+
+ 1084 1073
CHEXA 896 1 952 963 964 953 1073 1084+
+ 1085 1074
CHEXA 897 1 953 964 965 954 1074 1085+
+ 1086 1075
CHEXA 898 1 954 965 966 955 1075 1086+
+ 1087 1076
CHEXA 899 1 955 966 967 956 1076 1087+
+ 1088 1077
CHEXA 900 1 956 967 968 957 1077 1088+
+ 1089 1078
CHEXA 901 1 969 972 971 970 1090 1093+
+ 1092 1091
CHEXA 902 1 970 971 974 973 1091 1092+
+ 1095 1094
CHEXA 903 1 973 974 976 975 1094 1095+
+ 1097 1096
CHEXA 904 1 975 976 978 977 1096 1097+
+ 1099 1098

Altair Engineering OptiStruct 13.0 Reference Guide 1503

Proprietary Information of Altair Engineering


CHEXA 905 1 977 978 980 979 1098 1099+
+ 1101 1100
CHEXA 906 1 979 980 982 981 1100 1101+
+ 1103 1102
CHEXA 907 1 981 982 984 983 1102 1103+
+ 1105 1104
CHEXA 908 1 983 984 986 985 1104 1105+
+ 1107 1106
CHEXA 909 1 985 986 988 987 1106 1107+
+ 1109 1108
CHEXA 910 1 987 988 990 989 1108 1109+
+ 1111 1110
CHEXA 911 1 972 992 991 971 1093 1113+
+ 1112 1092
CHEXA 912 1 971 991 993 974 1092 1112+
+ 1114 1095
CHEXA 913 1 974 993 994 976 1095 1114+
+ 1115 1097
CHEXA 914 1 976 994 995 978 1097 1115+
+ 1116 1099
CHEXA 915 1 978 995 996 980 1099 1116+
+ 1117 1101
CHEXA 916 1 980 996 997 982 1101 1117+
+ 1118 1103
CHEXA 917 1 982 997 998 984 1103 1118+
+ 1119 1105
CHEXA 918 1 984 998 999 986 1105 1119+
+ 1120 1107
CHEXA 919 1 986 999 1000 988 1107 1120+
+ 1121 1109
CHEXA 920 1 988 1000 1001 990 1109 1121+
+ 1122 1111
CHEXA 921 1 992 1003 1002 991 1113 1124+
+ 1123 1112
CHEXA 922 1 991 1002 1004 993 1112 1123+
+ 1125 1114
CHEXA 923 1 993 1004 1005 994 1114 1125+
+ 1126 1115
CHEXA 924 1 994 1005 1006 995 1115 1126+
+ 1127 1116
CHEXA 925 1 995 1006 1007 996 1116 1127+
+ 1128 1117
CHEXA 926 1 996 1007 1008 997 1117 1128+
+ 1129 1118
CHEXA 927 1 997 1008 1009 998 1118 1129+
+ 1130 1119
CHEXA 928 1 998 1009 1010 999 1119 1130+
+ 1131 1120
CHEXA 929 1 999 1010 1011 1000 1120 1131+
+ 1132 1121
CHEXA 930 1 1000 1011 1012 1001 1121 1132+
+ 1133 1122
CHEXA 931 1 1003 1014 1013 1002 1124 1135+
+ 1134 1123
CHEXA 932 1 1002 1013 1015 1004 1123 1134+
+ 1136 1125
CHEXA 933 1 1004 1015 1016 1005 1125 1136+
+ 1137 1126
CHEXA 934 1 1005 1016 1017 1006 1126 1137+
+ 1138 1127
CHEXA 935 1 1006 1017 1018 1007 1127 1138+
+ 1139 1128
CHEXA 936 1 1007 1018 1019 1008 1128 1139+
+ 1140 1129
CHEXA 937 1 1008 1019 1020 1009 1129 1140+
+ 1141 1130
CHEXA 938 1 1009 1020 1021 1010 1130 1141+
+ 1142 1131
CHEXA 939 1 1010 1021 1022 1011 1131 1142+

1504 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 1143 1132
CHEXA 940 1 1011 1022 1023 1012 1132 1143+
+ 1144 1133
CHEXA 941 1 1014 1025 1024 1013 1135 1146+
+ 1145 1134
CHEXA 942 1 1013 1024 1026 1015 1134 1145+
+ 1147 1136
CHEXA 943 1 1015 1026 1027 1016 1136 1147+
+ 1148 1137
CHEXA 944 1 1016 1027 1028 1017 1137 1148+
+ 1149 1138
CHEXA 945 1 1017 1028 1029 1018 1138 1149+
+ 1150 1139
CHEXA 946 1 1018 1029 1030 1019 1139 1150+
+ 1151 1140
CHEXA 947 1 1019 1030 1031 1020 1140 1151+
+ 1152 1141
CHEXA 948 1 1020 1031 1032 1021 1141 1152+
+ 1153 1142
CHEXA 949 1 1021 1032 1033 1022 1142 1153+
+ 1154 1143
CHEXA 950 1 1022 1033 1034 1023 1143 1154+
+ 1155 1144
CHEXA 951 1 1025 1036 1035 1024 1146 1157+
+ 1156 1145
CHEXA 952 1 1024 1035 1037 1026 1145 1156+
+ 1158 1147
CHEXA 953 1 1026 1037 1038 1027 1147 1158+
+ 1159 1148
CHEXA 954 1 1027 1038 1039 1028 1148 1159+
+ 1160 1149
CHEXA 955 1 1028 1039 1040 1029 1149 1160+
+ 1161 1150
CHEXA 956 1 1029 1040 1041 1030 1150 1161+
+ 1162 1151
CHEXA 957 1 1030 1041 1042 1031 1151 1162+
+ 1163 1152
CHEXA 958 1 1031 1042 1043 1032 1152 1163+
+ 1164 1153
CHEXA 959 1 1032 1043 1044 1033 1153 1164+
+ 1165 1154
CHEXA 960 1 1033 1044 1045 1034 1154 1165+
+ 1166 1155
CHEXA 961 1 1036 1047 1046 1035 1157 1168+
+ 1167 1156
CHEXA 962 1 1035 1046 1048 1037 1156 1167+
+ 1169 1158
CHEXA 963 1 1037 1048 1049 1038 1158 1169+
+ 1170 1159
CHEXA 964 1 1038 1049 1050 1039 1159 1170+
+ 1171 1160
CHEXA 965 1 1039 1050 1051 1040 1160 1171+
+ 1172 1161
CHEXA 966 1 1040 1051 1052 1041 1161 1172+
+ 1173 1162
CHEXA 967 1 1041 1052 1053 1042 1162 1173+
+ 1174 1163
CHEXA 968 1 1042 1053 1054 1043 1163 1174+
+ 1175 1164
CHEXA 969 1 1043 1054 1055 1044 1164 1175+
+ 1176 1165
CHEXA 970 1 1044 1055 1056 1045 1165 1176+
+ 1177 1166
CHEXA 971 1 1047 1058 1057 1046 1168 1179+
+ 1178 1167
CHEXA 972 1 1046 1057 1059 1048 1167 1178+
+ 1180 1169
CHEXA 973 1 1048 1059 1060 1049 1169 1180+
+ 1181 1170

Altair Engineering OptiStruct 13.0 Reference Guide 1505

Proprietary Information of Altair Engineering


CHEXA 974 1 1049 1060 1061 1050 1170 1181+
+ 1182 1171
CHEXA 975 1 1050 1061 1062 1051 1171 1182+
+ 1183 1172
CHEXA 976 1 1051 1062 1063 1052 1172 1183+
+ 1184 1173
CHEXA 977 1 1052 1063 1064 1053 1173 1184+
+ 1185 1174
CHEXA 978 1 1053 1064 1065 1054 1174 1185+
+ 1186 1175
CHEXA 979 1 1054 1065 1066 1055 1175 1186+
+ 1187 1176
CHEXA 980 1 1055 1066 1067 1056 1176 1187+
+ 1188 1177
CHEXA 981 1 1058 1069 1068 1057 1179 1190+
+ 1189 1178
CHEXA 982 1 1057 1068 1070 1059 1178 1189+
+ 1191 1180
CHEXA 983 1 1059 1070 1071 1060 1180 1191+
+ 1192 1181
CHEXA 984 1 1060 1071 1072 1061 1181 1192+
+ 1193 1182
CHEXA 985 1 1061 1072 1073 1062 1182 1193+
+ 1194 1183
CHEXA 986 1 1062 1073 1074 1063 1183 1194+
+ 1195 1184
CHEXA 987 1 1063 1074 1075 1064 1184 1195+
+ 1196 1185
CHEXA 988 1 1064 1075 1076 1065 1185 1196+
+ 1197 1186
CHEXA 989 1 1065 1076 1077 1066 1186 1197+
+ 1198 1187
CHEXA 990 1 1066 1077 1078 1067 1187 1198+
+ 1199 1188
CHEXA 991 1 1069 1080 1079 1068 1190 1201+
+ 1200 1189
CHEXA 992 1 1068 1079 1081 1070 1189 1200+
+ 1202 1191
CHEXA 993 1 1070 1081 1082 1071 1191 1202+
+ 1203 1192
CHEXA 994 1 1071 1082 1083 1072 1192 1203+
+ 1204 1193
CHEXA 995 1 1072 1083 1084 1073 1193 1204+
+ 1205 1194
CHEXA 996 1 1073 1084 1085 1074 1194 1205+
+ 1206 1195
CHEXA 997 1 1074 1085 1086 1075 1195 1206+
+ 1207 1196
CHEXA 998 1 1075 1086 1087 1076 1196 1207+
+ 1208 1197
CHEXA 999 1 1076 1087 1088 1077 1197 1208+
+ 1209 1198
CHEXA 1000 1 1077 1088 1089 1078 1198 1209+
+ 1210 1199
CHEXA 1001 1 1090 1093 1092 1091 1211 1214+
+ 1213 1212
CHEXA 1002 1 1091 1092 1095 1094 1212 1213+
+ 1216 1215
CHEXA 1003 1 1094 1095 1097 1096 1215 1216+
+ 1218 1217
CHEXA 1004 1 1096 1097 1099 1098 1217 1218+
+ 1220 1219
CHEXA 1005 1 1098 1099 1101 1100 1219 1220+
+ 1222 1221
CHEXA 1006 1 1100 1101 1103 1102 1221 1222+
+ 1224 1223
CHEXA 1007 1 1102 1103 1105 1104 1223 1224+
+ 1226 1225
CHEXA 1008 1 1104 1105 1107 1106 1225 1226+

1506 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


+ 1228 1227
CHEXA 1009 1 1106 1107 1109 1108 1227 1228+
+ 1230 1229
CHEXA 1010 1 1108 1109 1111 1110 1229 1230+
+ 1232 1231
CHEXA 1011 1 1093 1113 1112 1092 1214 1234+
+ 1233 1213
CHEXA 1012 1 1092 1112 1114 1095 1213 1233+
+ 1235 1216
CHEXA 1013 1 1095 1114 1115 1097 1216 1235+
+ 1236 1218
CHEXA 1014 1 1097 1115 1116 1099 1218 1236+
+ 1237 1220
CHEXA 1015 1 1099 1116 1117 1101 1220 1237+
+ 1238 1222
CHEXA 1016 1 1101 1117 1118 1103 1222 1238+
+ 1239 1224
CHEXA 1017 1 1103 1118 1119 1105 1224 1239+
+ 1240 1226
CHEXA 1018 1 1105 1119 1120 1107 1226 1240+
+ 1241 1228
CHEXA 1019 1 1107 1120 1121 1109 1228 1241+
+ 1242 1230
CHEXA 1020 1 1109 1121 1122 1111 1230 1242+
+ 1243 1232
CHEXA 1021 1 1113 1124 1123 1112 1234 1245+
+ 1244 1233
CHEXA 1022 1 1112 1123 1125 1114 1233 1244+
+ 1246 1235
CHEXA 1023 1 1114 1125 1126 1115 1235 1246+
+ 1247 1236
CHEXA 1024 1 1115 1126 1127 1116 1236 1247+
+ 1248 1237
CHEXA 1025 1 1116 1127 1128 1117 1237 1248+
+ 1249 1238
CHEXA 1026 1 1117 1128 1129 1118 1238 1249+
+ 1250 1239
CHEXA 1027 1 1118 1129 1130 1119 1239 1250+
+ 1251 1240
CHEXA 1028 1 1119 1130 1131 1120 1240 1251+
+ 1252 1241
CHEXA 1029 1 1120 1131 1132 1121 1241 1252+
+ 1253 1242
CHEXA 1030 1 1121 1132 1133 1122 1242 1253+
+ 1254 1243
CHEXA 1031 1 1124 1135 1134 1123 1245 1256+
+ 1255 1244
CHEXA 1032 1 1123 1134 1136 1125 1244 1255+
+ 1257 1246
CHEXA 1033 1 1125 1136 1137 1126 1246 1257+
+ 1258 1247
CHEXA 1034 1 1126 1137 1138 1127 1247 1258+
+ 1259 1248
CHEXA 1035 1 1127 1138 1139 1128 1248 1259+
+ 1260 1249
CHEXA 1036 1 1128 1139 1140 1129 1249 1260+
+ 1261 1250
CHEXA 1037 1 1129 1140 1141 1130 1250 1261+
+ 1262 1251
CHEXA 1038 1 1130 1141 1142 1131 1251 1262+
+ 1263 1252
CHEXA 1039 1 1131 1142 1143 1132 1252 1263+
+ 1264 1253
CHEXA 1040 1 1132 1143 1144 1133 1253 1264+
+ 1265 1254
CHEXA 1041 1 1135 1146 1145 1134 1256 1267+
+ 1266 1255
CHEXA 1042 1 1134 1145 1147 1136 1255 1266+
+ 1268 1257

Altair Engineering OptiStruct 13.0 Reference Guide 1507

Proprietary Information of Altair Engineering


CHEXA 1043 1 1136 1147 1148 1137 1257 1268+
+ 1269 1258
CHEXA 1044 1 1137 1148 1149 1138 1258 1269+
+ 1270 1259
CHEXA 1045 1 1138 1149 1150 1139 1259 1270+
+ 1271 1260
CHEXA 1046 1 1139 1150 1151 1140 1260 1271+
+ 1272 1261
CHEXA 1047 1 1140 1151 1152 1141 1261 1272+
+ 1273 1262
CHEXA 1048 1 1141 1152 1153 1142 1262 1273+
+ 1274 1263
CHEXA 1049 1 1142 1153 1154 1143 1263 1274+
+ 1275 1264
CHEXA 1050 1 1143 1154 1155 1144 1264 1275+
+ 1276 1265
CHEXA 1051 1 1146 1157 1156 1145 1267 1278+
+ 1277 1266
CHEXA 1052 1 1145 1156 1158 1147 1266 1277+
+ 1279 1268
CHEXA 1053 1 1147 1158 1159 1148 1268 1279+
+ 1280 1269
CHEXA 1054 1 1148 1159 1160 1149 1269 1280+
+ 1281 1270
CHEXA 1055 1 1149 1160 1161 1150 1270 1281+
+ 1282 1271

CHEXA 1057 1 1151 1162 1163 1152 1272 1283+


+ 1284 1273
CHEXA 1058 1 1152 1163 1164 1153 1273 1284+
+ 1285 1274
CHEXA 1059 1 1153 1164 1165 1154 1274 1285+
+ 1286 1275
CHEXA 1060 1 1154 1165 1166 1155 1275 1286+
+ 1287 1276
CHEXA 1061 1 1157 1168 1167 1156 1278 1289+
+ 1288 1277
CHEXA 1062 1 1156 1167 1169 1158 1277 1288+
+ 1290 1279
CHEXA 1063 1 1158 1169 1170 1159 1279 1290+
+ 1291 1280
CHEXA 1064 1 1159 1170 1171 1160 1280 1291+
+ 1292 1281
CHEXA 1065 1 1160 1171 1172 1161 1281 1292+
+ 1293 1282
CHEXA 1066 1 1161 1172 1173 1162 1282 1293+
+ 1294 1283
CHEXA 1067 1 1162 1173 1174 1163 1283 1294+
+ 1295 1284
CHEXA 1068 1 1163 1174 1175 1164 1284 1295+
+ 1296 1285
CHEXA 1069 1 1164 1175 1176 1165 1285 1296+
+ 1297 1286
CHEXA 1070 1 1165 1176 1177 1166 1286 1297+
+ 1298 1287
CHEXA 1071 1 1168 1179 1178 1167 1289 1300+
+ 1299 1288
CHEXA 1072 1 1167 1178 1180 1169 1288 1299+
+ 1301 1290
CHEXA 1073 1 1169 1180 1181 1170 1290 1301+
+ 1302 1291
CHEXA 1074 1 1170 1181 1182 1171 1291 1302+
+ 1303 1292
CHEXA 1075 1 1171 1182 1183 1172 1292 1303+
+ 1304 1293
CHEXA 1076 1 1172 1183 1184 1173 1293 1304+
+ 1305 1294
CHEXA 1077 1 1173 1184 1185 1174 1294 1305+
+ 1306 1295

1508 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA 1078 1 1174 1185 1186 1175 1295 1306+
+ 1307 1296
CHEXA 1079 1 1175 1186 1187 1176 1296 1307+
+ 1308 1297
CHEXA 1080 1 1176 1187 1188 1177 1297 1308+
+ 1309 1298
CHEXA 1081 1 1179 1190 1189 1178 1300 1311+
+ 1310 1299
CHEXA 1082 1 1178 1189 1191 1180 1299 1310+
+ 1312 1301
CHEXA 1083 1 1180 1191 1192 1181 1301 1312+
+ 1313 1302
CHEXA 1084 1 1181 1192 1193 1182 1302 1313+
+ 1314 1303
CHEXA 1085 1 1182 1193 1194 1183 1303 1314+
+ 1315 1304
CHEXA 1086 1 1183 1194 1195 1184 1304 1315+
+ 1316 1305
CHEXA 1087 1 1184 1195 1196 1185 1305 1316+
+ 1317 1306
CHEXA 1088 1 1185 1196 1197 1186 1306 1317+
+ 1318 1307
CHEXA 1089 1 1186 1197 1198 1187 1307 1318+
+ 1319 1308
CHEXA 1090 1 1187 1198 1199 1188 1308 1319+
+ 1320 1309
CHEXA 1091 1 1190 1201 1200 1189 1311 1322+
+ 1321 1310
CHEXA 1092 1 1189 1200 1202 1191 1310 1321+
+ 1323 1312
CHEXA 1093 1 1191 1202 1203 1192 1312 1323+
+ 1324 1313
CHEXA 1094 1 1192 1203 1204 1193 1313 1324+
+ 1325 1314
CHEXA 1095 1 1193 1204 1205 1194 1314 1325+
+ 1326 1315
CHEXA 1096 1 1194 1205 1206 1195 1315 1326+
+ 1327 1316
CHEXA 1097 1 1195 1206 1207 1196 1316 1327+
+ 1328 1317
CHEXA 1098 1 1196 1207 1208 1197 1317 1328+
+ 1329 1318
CHEXA 1099 1 1197 1208 1209 1198 1318 1329+
+ 1330 1319
CHEXA 1100 1 1198 1209 1210 1199 1319 1330+
+ 1331 1320
$$
$$------------------------------------------------------------------------------$
$$ HyperMesh name information for generic property collectors $
$$------------------------------------------------------------------------------$
$$
$$------------------------------------------------------------------------------$
$$ Property Definition for 1-D Elements $
$$------------------------------------------------------------------------------$
$$
$$------------------------------------------------------------------------------$
$$ HyperMesh name and color information for generic components $
$$------------------------------------------------------------------------------$
$HMNAME COMP 6"auto1"
$HWCOLOR COMP 6 3
$
$$
$$------------------------------------------------------------------------------$
$$ Property Definition for Surface and Volume Elements $
$$------------------------------------------------------------------------------$
$$
$$ PSHELL Data
$
$HMNAME COMP 4"shells"

Altair Engineering OptiStruct 13.0 Reference Guide 1509

Proprietary Information of Altair Engineering


$HWCOLOR COMP 4 7
PSHELL 4 20.2 2 2
$$
$$ PSOLID Data
$
$HMNAME COMP 1"solids"
$HWCOLOR COMP 1 26
PSOLID 1 1 PFLUID
PSOLID 2 2
$$
$$------------------------------------------------------------------------------$
$$ Material Definition Cards $
$$------------------------------------------------------------------------------$
$$--------------------------------------------------------------
$$ HYPERMESH TAGS
$$--------------------------------------------------------------
$$BEGIN TAGS
$$END TAGS
$$
$$ MAT1 Data
$
$HMNAME MAT 2"MAT1"
$HWCOLOR MAT 2 18
MAT1 2200000.0 0.3 0.9e-5
$$
$$
$$ MAT10 Data
$HMNAME MAT 1"MAT10_1"
$HWCOLOR MAT 1 3
MAT10 11.0 0.01
$$
$$
$$------------------------------------------------------------------------------$
$$ HyperMesh name information for generic materials $
$$------------------------------------------------------------------------------$
$$
$$------------------------------------------------------------------------------$
$$ Material Definition Cards $
$$------------------------------------------------------------------------------$
$$
$$------------------------------------------------------------------------------$
$$ Loads and Boundary Conditions $
$$------------------------------------------------------------------------------$
$$
$$HyperMesh name and color information for generic loadcollectors
$$
$HMNAME LOADCOL 4"SPC"
$HWCOLOR LOADCOL 4 3
$
$HMNAME LOADCOL 6"spcd"
$HWCOLOR LOADCOL 6 4
$
$$
$$
$$
$$
$$ FREQ1 cards
$$
$HMNAME LOADCOL 5"freq"
$HWCOLOR LOADCOL 5 4
FREQ1 50.1 10.0 5
$$
$$
$$
$$
$$
$$ RLOAD2 cards
$$
$HMNAME LOADCOL 2"rload2"

1510 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


$HWCOLOR LOADCOL 2 5
RLOAD2 2 6 1 0 ACCE
$$
$HMNAME LOADCOL 3"darea"
$HWCOLOR LOADCOL 3 5
RLOAD2 3 3 1 0 LOAD
$$
$$
$$
$$ TABLED1 cards
$$
$HMNAME LOADCOL 1"tab"
$HWCOLOR LOADCOL 1 41
TABLED1 1 LINEAR LINEAR
+ 0.0 0.0 1000.0 1.0ENDT
$$
TABLED1 2 LINEAR LINEAR
+ 0.0 0.0 1000.0 1.0ENDT
$$
TABLED1 3 LINEAR LINEAR
+ 0.0 5.0 1000.0 5.0ENDT
$$ DLOAD cards
$$
$HMNAME LOADCOL 11"DLOAD11"
$HWCOLOR LOADCOL 11 3
DLOAD 111.0 1.0 2 1.0 3
$$
$$
$$
$$
$$
$$
$$
$$ SPC Data
$$
SPC 4 1431 1234560.0
SPC 4 1432 1234560.0
SPC 4 1451 1234560.0
SPC 4 1452 1234560.0
SPC 4 1734 3 0.0
$$
$$ SPCD Data
$$
SPCD 6 1734 3 3.0
$
$ DAREA Data
$
$$
$$ DAREA Data
$$
DAREA 3 1734 3-10.0
ENDDATA

ALTDOCTAG "HqTD_ARNMI\S\pMpN13G;5oANN]l[enE7fmSbTJro20LOpNriZFOQfUk]
_`5hfS5ATf6pT7RXMjA3e@k_r^K?GP;?OeEbD0"
ADI0.1.0 2011-05-13T19:57:45 0of1 OSQA
ENDDOCTAG

Altair Engineering OptiStruct 13.0 Reference Guide 1511

Proprietary Information of Altair Engineering


Comments

1. PACABS is referenced by a CHACAB entry only.

2. If SYNTH = “YES”, then TID1 and TID2 must be supplied (TID3 is optional) and the
equivalent structural model will be derived from tables TIDi. If TID3 is blank, then the
weighting function defaults to 1.0.

3. If SYNTH=”NO”, then the equivalent structural model will be derived from B, K and M.

4. This card is represented as a property in HyperMesh.

1512 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PANEL

Bulk Data Entry

PANEL – Panel Definition for Panel Participation Output

Description

Defines up to four sets of grid points or elements as panels for panel participation output for a
frequency response analysis of a coupled fluid-structural model.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PANEL NAME1 SID1 NAME2 SID2 NAME3 SID3 NAME4 SID4

Field Contents

NAME# Panel label.

No default (Character string)

SID# Set identification number for a set of grids or elements.

No default (Integer > 0)

Comments

1. If a set of elements is defined, the panel will consist of all grid points connected to these
elements.

Altair Engineering OptiStruct 13.0 Reference Guide 1513

Proprietary Information of Altair Engineering


PANELG

Bulk Data Entry

PANELG – Generic Panel Definition

Description

Defines a set of grid points and/or elements as generic panel.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PANELG ID NAME TYPE ESID GSID

Field Contents

ID Unique panel identification number.

No default (Integer > 0)

NAME Panel label.

No default (Character string)

TYPE Panel type.

Default = blank (PFP, ERP, SOUND, or blank, See comment 1)

ESID Set identification number for a set of elements.

No default (Integer > 0 or blank)

GSID Set identification number for a set of grids.

No default (Integer > 0 or blank)

Comments

1. The panel type indicates the context in which the panel should be used. PFP indicates
that the panel should be considered for panel participation output (similar to PANEL). ERP
indicates that the panel should be considered for equivalent radiated power output

1514 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


(similar to ERPPNL). SOUND indicates that the panel should be considered for radiated
sound output. Blank indicates that the panel should be considered in any context
involving panels.

2. Panels of type ERP/SOUND (or blank) may be defined as a set of elements, a set of grid
points, or both. If a set of elements is defined, the panel will consist of all grid points
connected to these elements. If both sets are defined, the panel will consist of the
intersection of those sets.

3. Panels of type PFP must be defined as a set of grid points exclusively.

4. The element set can also consist of solid elements. In such cases, grids on the wetted
surface are automatically detected to define the panel.

Altair Engineering OptiStruct 13.0 Reference Guide 1515

Proprietary Information of Altair Engineering


PARAM

Bulk Data Entry

PARAM – Solution Control Parameter

Description

Defines values for parameters used during analysis and optimization.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PARAM N V

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PARAM C OUPMASS YES

Field Contents

N Name of Parameter.

V Value of Parameter.

The available parameters and their values are listed below (click the parameter name for
parameter descriptions).

Parameter Description Values

ACMODL12 Used to restore the ACMODL formulation used in YES, NO


version 12.0 and earlier for the Fluid-Structure Default = NO
Interface.

AGGPCH To support output of the fluid-structure coupling YES, NO


matrix to the Punch (.pch) file as a matrix defined

1516 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Parameter Description Values

using DMIG data entry. Default = NO

AKUSMOD Use external fluid-structure coupling matrix YES, NO


generated by AKUSMOD. Default = NO

ALPHA1 Adds Rayleigh damping to viscous damping for <REAL>


structural mesh. Default = 0.0

ALPHA2 Adds Rayleigh damping to viscous damping for <REAL>


structural mesh. Default = 0.0

ALPHA1FL Adds Rayleigh damping to viscous damping for fluid <REAL>


mesh. Default = 0.0

ALPHA2FL Adds Rayleigh damping to viscous damping for fluid <REAL>


mesh. Default = 0.0

AMLS Use external AMLS eigenvalue solver. YES, NO


Default = NO

AMLSMAXR Used to determine singularities in the stiffness matrix <REAL>


for AMLS eigenvalue solver. Default = 1.0e-8

AMLSMEM Defines the amount of memory in Gigabytes to be <REAL>


used by the external AMLS eigenvalue solver. No default

AMLSNCPU Identify number of cpu's to be used by AMLS 1, 2, 4


eigenvalue solver. Default = no. of cpu’s
used by the solver

AMLSUCON Constrain unconnected grids for AMLS eigenvalue 1, 0


solver. Default = 0

AMSESLM Indicate if the AMSES numerical mode for enforced <YES, NO>
motion based modal dynamic analysis with large Default = NO
mass method will be activated or not.

ASCOUP Generates the fluid-structure coupling (area) matrix <YES, NO>


for use in the solution. Default = YES

AUTOMSET Automatically convert dependent degrees-of- <YES, NO>

Altair Engineering OptiStruct 13.0 Reference Guide 1517

Proprietary Information of Altair Engineering


Parameter Description Values

freedom of rigid elements to independent degrees- Default = YES


of-freedom.

AUTOSPC Automatically constrain degrees-of-freedom with no YES, NO


stiffness. Default = YES

AUTOSPRT Activate inertia relief and auto-support degree-of- 1, 0


freedom generation. Default = 1

BUSHRLMT Issues a WARNING when the stiffness value for <Real Number > 0.0>
rotational components on the PBUSH entry exceeds
Default = 1.0E+09
the specified limit (BUSHRLMT).

BUSHSTIF Specifies a value to replace large stiffness values <Real Number > 0.0>
(>1.0E+07) input in field K of the PBUSH data entry. No default

BUSHTLMT Issues a WARNING when the stiffness value for <Real Number > 0.0>
translational components on the PBUSH entry
Default = 1E+07
exceeds the specified limit (BUSHTLMT).

CB2 Scale factor for direct input damping matrices. Real


Default = 1.0

CHECKEL Activate element quality checking. NO, YES, FULL


Default = YES

CHECKMAT Activate material property checking. YES, NO, FULL


Default = YES

CHKGPDIR Activate gap direction alignment checking. YES, NO, WARN,


FULL, REVERSE
Default = YES

CK2 Scale factor for direct input stiffness matrices. Real


Default = 1.0

CK3 Specifies factors for the stiffness matrix produced Real


by GENEL cards. Default = 1.0

CM2 Scale factor for direct input mass matrices. Real


Default = 1.0

1518 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Parameter Description Values

CMFTINIT Defines lower threshold for *.HM.comp.cmf and 0.0 < REAL < 1.0
*.HM.ent.cmf HyperMesh command files. Default = 0.0

CMFTSTEP Defines step or interval value for *.HM.comp.cmf 0.0 < REAL < 1.0
and *.HM.ent.cmf HyperMesh command. Default = 0.1

CMSALOD Controls the inclusion of mass contribution from the <YES, NO>
mass matrix stored in the PUNCH DMIG or the H3D Default = YES
DMIG files for the generation of RFORCE and Gravity
Loads.

CMSDIRM Allows flexible body generation when directional YES, NO


masses are defined in the input file. Default = NO

CMSOFST Consider shell offsets for flexbody generation. <YES, NO>


Default - NO

COEFFC Friction coefficient on curvatures for one-step Real > 0.0


stamping simulation.

YES, NO,
COMP2SHL Results of homogenization of composite properties.
BULK
Default = NO

CONTFEL Activates Contact-friendly elements. This is <YES, NO>


recommended when second order solids/gaskets are Default = NO
used with contact analysis in OptiStruct.

COUPMASS Use coupled mass matrix approach for eigenvalue -1, 0, 1, YES, NO
analysis. Default = NO

CP2 Scale factor for direct input load matrices. Real


Default = 1.0

CSTEVAL Use wall time based cost evaluation for Lanczos <YES, NO>
steps. Default = YES

CSTOL Specifies how many decimal digits may be lost to Real


cancellation in one operation during the Default = 3.5
eigensolution process.

DFREQ Used to determine duplicate frequencies. Real

Altair Engineering OptiStruct 13.0 Reference Guide 1519

Proprietary Information of Altair Engineering


Parameter Description Values

Default = 10-5

DISIFMCK Skip indefinite mass matrix check. <YES, NO>


Default = NO

DISJOINT Used to allow AMLS to handle disconnected parts. Integer


This can also be accomplished with Default = NONE
PARAM,AMLSUCON.

DUPTOL Level of accuracy used in determining duplicate <0, 1, 2, 3, 4, 5>


grids. Default = 0

EFFMAS Output modal participation factors and effective YES, NO, Integer
mass for normal modes analyses. Default = NO

EHD Prints the inverse of the stiffness matrix created by <YES,NO>


static reduction to FORTRAN unit 3 Default = NO

ELASRLMT Issues a WARNING when the stiffness value for <Real Number > 0.0>
rotational components on the CELAS2/4 or PELAS
Default = 1.0E + 09
entry exceeds the specified limit (ELASRLMT).

ELASSTIF Specifies a value to replace large stiffness values <Real Number > 0.0>
(>1.0E+07) input in field K of the PELAS data entry. No default

ELASTLMT Issues a WARNING when the stiffness value for <Real Number > 0.0>
translational components on the CELAS2/4 or PELAS
Default = 1E+07
entry exceeds the specified limit (ELASTLMT).

ENFMOTN Switch between relative and absolute displacement <REL, ABS>


output in Modal Frequency Response Analysis with Default = ABS
enforced motion.

ERPC The speed of sound used in the ERP calculation Real > 0.0
Default = 1.0

ERPREFDB The reference value in decibels (dB) used in ERP Real > 0.0
calculations. Default = 1.0

ERPRHO The fluid density used in ERP calculations. Real > 0.0
Default = 1.0

1520 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Parameter Description Values

ERPRLF The Radiation Loss Factor used in ERP calculation. Real > 0.0
Default = 1.0

EXCEXB Controls the output of the AVL/EXCITE .exb file <YES, BOTH, NO>
directly from OptiStruct. Default = BOTH

EXCOUT Outputs of condensed superelement information for <-1, 0, 1, 3, 4, 5, 6>


AVL/EXCITE. Default = 0

EXPERTNL Activates nonlinear expert system to aid in the YES, NO


convergence of small displacement nonlinear Default = NO
problems.

EXTOUT Output reduced matrices to .pch or .dmg file. <DMIGPCH, DMIGBIN>


No default

FASTFR Controls the activation of a faster, alternative <YES, NO>


method (FASTFR) for Modal Frequency Response Default = AUTO
Analysis.

FFRS Used to invoke the external FastFRS (Fast <YES, NO>


Frequency Response Solver). Default = NO

FFRSLFREQ Defines a frequency cut-off value in Hertz used to Real


partition the structural system into low frequency Default = 1.0
and high frequency parts.

FFRSMEM Defines the amount of memory in Gigabytes to be <Real>


used by the external FastFRS modal equation solver. Default = 2.0 (GB)

FFRSNCPU Defines the number of cpu’s to be used by the <INTEGER>


external FastFRS solver. Default = number of
cpu's used by
OptiStruct.

FLEXH3D Generate flexh3d files for flexible bodies in an MBD <AUTO, YES, NO>
analysis. Default = AUTO

FLIPOK Allows tetrahedral elements to invert during shape NO, YES


optimization. Default = NO

Altair Engineering OptiStruct 13.0 Reference Guide 1521

Proprietary Information of Altair Engineering


Parameter Description Values

FRIC Define multiplier for K2PP reference. <REAL>


Default = 1.0

FZERO Identify the maximum frequency of a rigid body <REAL>


mode. Default = 0.1

G Specifies the uniform structural damping coefficient <REAL>


for dynamic analyses. Default = 0.0

GE_MOD Modifies specified GE values. <REAL> or NO_GE>


No default

GFL Specifies the uniform fluid damping coefficient for <REAL>


dynamic analyses. Default = 0.0

GMAR Controls the accuracy of the external AMLS <REAL>


eigenvalue solution. Default = 1.1

GMAR1 Controls the accuracy of the external AMLS <REAL>


eigenvalue solution. Default = 1.7

GPSLOC Controls where the grid point stresses are calculated Z1, Z2 and MID
for output to the .mnf file. Default = Z1

GRDPNT Obsolete NASTRAN parameter that will give <-1, 0>


information about the mass properties of the Default = -1
structure.

GRIDFORM This parameter controls the output format of the <LONG, SHORT>
.grid file. Default = SHORT

GYROAVG Used to select the frequency response analysis <0, -1>


formulation type for rotor dynamics analysis. Default = 0

HASHASSM Enable hash-table based assembly. <YES, NO>


Default = NO

HFREQ Specifies the upper bound of the frequency range of <REAL>


interest for modal combination. Default = None

HFREQFL Excludes modes with frequencies greater than <REAL>

1522 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Parameter Description Values

HFREQFL in Coupled Modal Frequency Response (Hertz)


Analysis (Acoustic Analysis).
Default = None

I64SLV Enforces the activation of internal long (64-bit) <YES, NO>


integer sparse direct solver. Default = NO

INREL Controls the calculation of inertia relief. 0, -1, -2


Default = 0, for static
subcases
Default = -2, for modal
frequency response
subcases

ITAPE Writes the ‘Tape Label’ at the beginning of the -1, 0


OUTPUT2 results file. Default = -1

INTRFACE Generates the .interface file to verify if proper YES, NO


connection has been established between the Fluid Default = YES
and Structure meshes at the interface.

K4CUTOFF Sets cut-off value if the low rank representation for <REAL>
the structural damping matrix is selected. Default = 0.1

KDAMP Enter viscous modal damping into the stiffness 1, -1


matrix as structural damping. Default = 1

KGRGD Include contributions from rigid elements in the YES, NO


geometric stiffness matrix. Default = NO

LFREQ Can be used to remove the Rigid Body Modes from <REAL>
the Modal Space. Default = None

LFREQFL Excludes modes with frequencies lower than <REAL> (Hertz)


LFREQFL in Coupled Modal Frequency Response
Analysis (Acoustic Analysis). Default = None

LGDISP Activates Large Displacement Nonlinear Analysis. <1, 0, -1>


Default = 0

LMSOUT Output the condensed Flex Body Modes, full Diagonal YES, NO, STRESS
Mass Matrix, and modal stresses to the .op2 file. Default = NO

Altair Engineering OptiStruct 13.0 Reference Guide 1523

Proprietary Information of Altair Engineering


Parameter Description Values

LOWRANK Indicates to FastFRS which solution strategy to use <0, -1, 1>
to handle the modal structural damping matrix. Default = 0

MASSDMIG For static condensation with ASET of a static <YES, NO>


loadcase, the reduced stiffness matrix [k] and load Default = NO
vector {p} are created.

MAXDAMP Identify the maximum number of residual vectors to <INTEGER>


be calculated. Default = 400

MBDH3D Choose the type of the results output to the .h3d NODAL, MODAL, BOTH,
file for MBD analyses. NONE
Default = BOTH

MBDREC Create a small and large flexible body files during YES, NO
Component Mode Synthesis (CMS). Default = NO

MEMTRIM Activate/deactivate the memory-trim feature when <YES, NO>


using AMLS eigensolver. Default = YES

MFILTER Defines a threshold for the mode tracking matrix to <0.0 < real number <
check eigenvector correspondence. 1.0>

MODETRAK Track mode numbers by comparing eigenvectors -1, 0, 1, YES, NO


between iterations. Default = NO

NEGMASS Allows run to proceed with negative diagonal mass <0, 1>
terms. Default = 0

NLAFILE Controls the output of animation files (A-File) in <YES, NO>


geometric nonlinear analysis. Default = NO

NLFAT Forces OptiStruct to run models in which fatigue <YES, NO>


solutions reference nonlinear quasi-static analysis Default = NO
(NLSTAT) subcases.

This is not recommended; refer to the complete


PARAM, NLFAT documentation for details.

NLRFILE Controls the output of restart files (R-File) in <YES, NO>


geometric nonlinear analysis. Default = NO

1524 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Parameter Description Values

NLRUN Controls the run of geometric nonlinear analysis after <YES, NO>
bulk to block conversion. Default = YES

NPRBAR Controls the number of the output INFORMATION <INTEGER>


#741 for RBAR element. Default = 3

NPRBE2 Controls the number of the output INFORMATION <INTEGER>


#741 for RBE2 element. Default = 3

NPRGDE Controls the number of the output INFORMATION <INTEGER>


#742. Default = 3

NUMEG Specifies the anticipated number of modes to be <INTEGER>


calculated in order to estimate disk space usage. 1000

OGEOM Output model data to the OUTPUT2 results file. <YES, NO>
Default = YES

OMACHPR Select newer version of certain OUTPUT2 <YES, NO>


datablocks. Default = NO

OMID Output stress and strain results for shell and <YES, NO>
membrane elements with reference to the material Default = NO
coordinate system.

OP2GM34 Controls the output of GEOM3 and GEOM4 data <TRUE, FALSE>
blocks to the .op2 file. Default = TRUE

PLIGEXT Print the applied load vector in DMIG form to the <YES,NO>
.pligext file. Default = NO

POST Generate an OUTPUT2 results file. 0, -1, -2, -5


Default = 0

POSTEXT Output the modal complex stiffness matrix and modal YES, NO
viscous damping matrix to the OUTPUT2 results file. Default = NO

PRESUBNL Forces OptiStruct to run models in which Linear YES, NO


Buckling Analysis or Preloaded Analysis is defined, in Default = NO
conjunction with nonlinear materials (MATS1,
MATHE, or MGASK) or Large Displacement Nonlinear

Altair Engineering OptiStruct 13.0 Reference Guide 1525

Proprietary Information of Altair Engineering


Parameter Description Values

Analysis.

This is not recommended. Refer to the complete


PARAM, PRESUBNL documentation for details.

PRGPST Output AutoSPC information to the .out file. <YES, NO>


Default = YES

PRINFACC Controls the output of inertial relief rigid body forces <1, 0>
and accelerations.

RBE2FREE Used to convert ERROR 725 into WARNING 825 when <YES, NO>
singular RBE2 elements are present in the model. Default = NO

RBE3FREE Used to convert ERROR 772 into WARNING 824 when <YES, NO>
free spiders on RBE3 elements are present in the Default = NO
model. These free spiders may contain singular
degrees of freedom.

RBMEIG Defines the cut-off eigenvalue for determining rigid <REAL>


body modes calculated by AMLS. Default = 0.1

REANAL Reanalyze the final iteration of a topology 0.0 < REAL < 1.0
optimization without penalization. No default

RECOVER Allows you to request full-structure mode shape <LB, UB>


output instead of the modes of the condensed Default for LB = 0.0,
system generated during Component Mode Synthesis and UB must be
(CMS) within the specified range of frequencies. specified

RENUMOK Allows you to correctly renumber the reversed (but <YES, NO, BLANK>
acceptable) sequence of element grids without Default = NO
having to run (import and re-export) the model
through HyperMesh.

RFIOUT This parameter controls the output of modal super <YES, NO>
element for use in the RecurDyn multibody dynamics Default = NO
software from FunctionBay.

RHOCP The scale factor used to calculate ERP in decibels Real > 0.0
(dB). Default = 1.0

RSPLICOR RSPLINE end rotation correction. 0, 1, REAL > 1.0


Default = 0

1526 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Parameter Description Values

SEP1XOVR The old and new location of moved shell grid points 0, 16
are printed if SEP1XOVR = 16. Default = 0

SEPLOT Output display model to .seplot file, from a CMS <YES, NO>
run. Default = YES

SH4NRP Controls the full projection of 4-node shell elements 0, 1, 2


in NLGEOM implicit analysis. Default = 0 in NLGEOM
subcases
Default = 1 in IMPDYN
subcases

SHELOS11 Allows you to revert to the first order shell element <YES, NO>
formulation (for CQUAD4 and CTRIA3) used in version Default = NO
11.0.240 and earlier.

SHL2MEM A shell property (defined by the PSHELL bulk data <Real Number > 0.0>
entry) is automatically converted into a membrane No default
property if the membrane thickness (field T) of the
PSHELL bulk data entry is less than the value
specified using PARAM, SHL2MEM.

SHPBCKOR Defines the type and order of approximation used in 1, 2


plate bending geometric stiffness for linear shell Default = 1
elements (CQUAD4, CTRIA3).

SIMPACK Requests generation of the SIMPACK .fbi file 0, 1, 2, 3, 4, 5


containing flexible body information for SIMPACK Default =0
analysis.

SMDISP Controls if small displacement formulation or large 0, 1


displacement formulation is used. Default = 0

SNAPTHRU Controls the output of the force-deflection curve in <YES,NO>


geometric nonlinear analysis. Default = NO

SORTCON Controls the output of violated constraints to the <INTEGER>


.out file from an optimization. Default = 20

SPLC Specifies the speed of sound used in the wave Real > 0.0
number and the complex particle velocity vector Default = 1.0
calculations.

Altair Engineering OptiStruct 13.0 Reference Guide 1527

Proprietary Information of Altair Engineering


Parameter Description Values

SPLFAC Specifies the scale factor (q ) used to calculate the Real > 0.0
Sound Pressure Level in Radiated Sound Analysis. Default = 1.0

SPLREFDB Specifies the reference sound pressure value used Real > 0.0
to calculate the Sound Pressure Level (SPL) in Default = 1.0
decibels (dB).

SPLRHO Specifies the density of the acoustic medium in the Real > 0.0
calculation of the complex acoustic sound pressure Default = 1.0
and the complex particle velocity vector.

SRCOMPS Outputs the strength ratios for composite elements <YES, NO>
that have failure indices requested. Default = NO

SS2GCR Controls the accuracy of the external AMLS <REAL>


eigenvalue solution. Default = 5.0

STRTHR Specifies the von Mises stress threshold value above


which the stress results are output for a model. Default = 0.0

THCNTPEN Controls the penalty factor used in thermal contact AUTO, LOW, HIGH
analysis. Default = AUTO

TOLRSC Connecting grid points of the shell element are <REAL>


moved onto the solid face. Default = 0.05

TRAKMETH Used to select the criterion employed for mode <0, 1, 2>
tracking. Default = 0

TRAKMTX Controls output of the mode tracking matrix during <0, 1>
optimization. Default = 0

TPS Activate fast transient response analysis (only shell <YES, NO>
stress results output). Default = YES

UCORD Specifies the coordinate system in which the mass <CID>


moment of inertia is output. It also can be used to
control the point about which the mass moment of Default = -1
inertia is calculated.

VMOPT Allows you to prevent the inclusion of the Virtual <Integer = 0, 1, 2>

1528 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Parameter Description Values

Mass Matrix in the Regular Mass Matrix for Modal Default = 0


Dynamic Subcases. In such cases, the virtual mass
is added after the eigen solution and modes are
modified based on the virtual mass matrix.

W3 Convert structural damping to equivalent viscous <REAL>


damping for transient analysis. Default = 0.0

W4 Convert structural damping to equivalent viscous <REAL>


damping for transient analysis. Default = 0.0

WR3 Used to include or exclude frequency dependent <REAL>


damping in rotor dynamics analysis. Default = 0.0

WR4 Used to include or exclude frequency dependent <REAL>


damping in rotor dynamics analysis. Default = 0.0

WTMASS Convert weights to masses using this multiplier. REAL > 0.0
Default = 1.0

Comments

1. This card is represented as a control card in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1529

Proprietary Information of Altair Engineering


PARAM, ACMODL12

Parameter Values Description

ACMODL <YES, NO> PARAM, ACMODL12, YES can be used to restore the
ACMODL formulation used in version 12.0 and earlier for the
Default = NO
Fluid-Structure Interface.

Note

In OptiStruct 13.0 the new and improved ACMODL


formulation will couple the fluid grids at the interface to only
a single layer of structural grids. This parameter can be
used to restore the formulation used prior to 13.0. The old
formulation coupled the fluid face to every structural grid in
the search box.

1530 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, AGGPCH

Parameter Values Description

AGGPCH <YES, NO> If YES, OptiStruct will output the Fluid-Structure


Default = NO coupling matrix to the Punch file (.pch) as a matrix
defined using the DMIG data entry, with the name
AGGAX. This DMIG can be used in a subsequent
OptiStruct run using the A2GG Solution Control
Command.

If NO, the Fluid-Structure coupling matrix will not be


output to the Punch file (.pch).

Altair Engineering OptiStruct 13.0 Reference Guide 1531

Proprietary Information of Altair Engineering


PARAM, AKUSMOD

Parameter Values Description

AKUSMOD <YES, NO> If YES, this indicates that OptiStruct should use a fluid-
Default = NO structure coupling matrix generated by AKUSMOD. In this
case, the ACMODL data is ignored.

By default 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“. However an alternate
file name and location may be assigned via the
ASSIGN,AKUSMOD command.

1532 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, ALPHA1

Parameter Values Description

ALPHA1 <REAL> PARAM, ALPHA1 is used in frequency response,


Default = 0.0 transient response and modal complex eigenvalue
analyses.

If PARAM, ALPHA1 and/or PARAM, ALPHA2 are not equal


to zero, then Rayleigh damping is added to the viscous
damping. ALPHA1 is the scale factor applied to the
mass matrix and ALPHA2 to the structural stiffness
matrix as in:

Altair Engineering OptiStruct 13.0 Reference Guide 1533

Proprietary Information of Altair Engineering


PARAM, ALPHA2

Parameter Values Description

ALPHA2 <REAL> PARAM, ALPHA2 is used in frequency response, transient


Default = 0.0 response and modal complex eigenvalue analyses.

If PARAM, ALPHA1 and/or PARAM, ALPHA2 are not equal to


zero, then Rayleigh damping is added to the viscous
damping. ALPHA1 is the scale factor applied to the mass
matrix and ALPHA2 to the structural stiffness matrix as in:

1534 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, ALPHA1FL

Parameter Values Description

ALPHA1FL <REAL> PARAM, ALPHA1FL is used in frequency and transient


Default = 0.0 response analysis.

If PARAM, ALPHA1FL and/or PARAM, ALPHA2FL are not equal


to zero, then Rayleigh damping is added to the viscous
damping. ALPHA1FL is the scale factor applied to the mass
matrix and ALPHA2FL to the fluid stiffness matrix as in:

Altair Engineering OptiStruct 13.0 Reference Guide 1535

Proprietary Information of Altair Engineering


PARAM, ALPHA2FL

Parameter Values Description

ALPHA2FL <REAL> PARAM, ALPHA2FL is used in frequency and transient


Default = 0.0 response analysis.

If PARAM, ALPHA1FL and/or PARAM, ALPHA2FL are not equal


to zero, then Rayleigh damping is added to the viscous
damping. ALPHA1FL is the scale factor applied to the mass
matrix and ALPHA2FL to the fluid stiffness matrix as in:

1536 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, AMLS

Parameter Values Description

AMLS YES, NO This parameter is used to invoke the external AMLS


Default = NO eigenvalue solver. This solver is faster than the Lanczos
solver for large eigenvalue problems. Note that AMLS must
be installed on the system and the environment variable
AMLS_EXE must point to the AMLS executable for this
setting to work.

If YES, then the external AMLS eigenvalue solver is used.

If NO, then the internal Lanczos eigenvlaue solver is used.

Refer to the User’s Guide section, Using the AMLS


(Automatic Multi-Level Sub-structuring) Eigensolver for
more details.

Altair Engineering OptiStruct 13.0 Reference Guide 1537

Proprietary Information of Altair Engineering


PARAM, AMLSMAXR

Parameter Values Description

AMLSMAXR <REAL> PARAM, AMLSMAXR is used to determine singularities in


Default = 1.0e-8 the stiffness matrix.

If the value of AMLSMAXR is exceeded in the process of


factoring a stiffness matrix, this indicates a singularity in
K. If the mass of this degree-of-freedom is zero, there
is a "massless mechanism"; an SPC is applied and a
message is written to the .out file. If there is mass,
then this is a mechanism which is treated as a rigid body
mode and a message is written to the .out file.

Refer to the User’s Guide section, Using the AMLS


(Automatic Multi-Level Sub-structuring) Eigensolver for
more details.

1538 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, AMLSMEM

Parameter Values Description

AMLSMEM <REAL> This parameter is used to define the amount of memory


in Gigabytes to be used by the external AMLS eigenvalue
Default = solver. This parameter is only valid for AMLS versions 5
Memory used by and higher.
OptiStruct for a
particular run. Note

1. If this parameter is not set, AMLS will use the


amount of memory that OptiStruct is using for the
run.

2. OptiStruct and AMLS can be run with different


allocations of memory. For example, OptiStruct can
be run with 10.0 Gigabytes and AMLS with 20.0
Gigabytes in the same run.

3. If the environment variable AMLS_MEM is set, it will


override the value set using PARAM,AMLSMEM.

4. This parameter can be used only if PARAM, AMLS is


set to YES.

Refer to the User’s Guide section, Using the AMLS


(Automatic Multi-Level Sub-structuring) Eigensolver for
more details.

Altair Engineering OptiStruct 13.0 Reference Guide 1539

Proprietary Information of Altair Engineering


PARAM, AMLSNCPU

Parameter Values Description

AMLSNCPU 1, 2, 4 This parameter is used to define the number of cpu’s


Default = no. of to be used by the external AMLS eigenvalue solver.
cpu’s This parameter will set the environment variable
used by the solver OMP_NUM_THREADS.

The default value is the current value of


OMP_NUM_THREADS. Note that this value can be set
through the command line arguments –nproc or –
ncpu.

OptiStruct and AMLS can be run with different


allocations of processors. For example, OptiStruct
can be run with 1 processor and AMLS with 4
processors in the same run.

Only valid when PARAM, AMLS is set to YES.

Refer to the User’s Guide section, Using the AMLS


(Automatic Multi-Level Sub-structuring) Eigensolver
for more details.

1540 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, AMLSUCON

Parameter Values Description

AMLSUCON 0, 1 This parameter is used to indicate whether or not


Default = 0 unconnected grids are to be constrained for AMLS run.

If 0, then unconnected grids are not constrained.

If 1, then unconnected grids are to be constrained.

Refer to the User’s Guide section, Using the AMLS


(Automatic Multi-Level Sub-structuring) Eigensolver for
more details.

Altair Engineering OptiStruct 13.0 Reference Guide 1541

Proprietary Information of Altair Engineering


PARAM, AMSESLM

Parameter Values Description

AMSESLM <YES, NO> YES: The EIGRA (AMSES) numerical method for enforced
Default = NO motion based modal dynamic analysis with large mass
method will be activated.

NO: The EIGRA (AMSES) numerical method for enforced


motion based modal dynamic analysis with large mass
method will not be activated.

1542 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, ASCOUP

Parameter Values Description

ASCOUP <YES, NO> If YES, the fluid-structure coupling (area) matrix will
Default = YES be calculated and used in the solution.

If NO, the fluid-structure (area) matrix is not


calculated.

Note: PARAM,AGGPCH,YES should be used to output


the matrix to the Punch (.pch) file.

PARAM,ASCOUP,NO is required when the fluid-


structure coupling (area) matrix is read in from
the Punch (.pch) file.

Altair Engineering OptiStruct 13.0 Reference Guide 1543

Proprietary Information of Altair Engineering


PARAM, AUTOMSET

Parameter Values Description

AUTOMSET <YES, NO> If YES, the dependent degrees-of-freedom of rigid


elements may be converted to independent degrees-
Default = YES of-freedom when conversion is necessary for the
model to run.
Defaults
If NO, the above conversion will not be performed.
1. The default is NO
when the The model may not run when multiple constraint
parameter is not equations reference the same dependent degree-of-
present in the freedom more than once.
deck. Note:
2. The default is YES 1. This parameter can be used if the dependent
when PARAM, degree-of-freedom (DOF) of a rigid element is
AUTOMSET is SPC’ed, part of the ASET, or if it is a dependent
input without DOF of another constraint equation (MPC
specifying a equation or another rigid element).
value.
2. PARAM, AUTOMSET, YES can be used in models
with SPC’ed dependent rigid element grids, only
if multiple SPC sets are present in multiple
subcases.

3. AUTOMSET cannot be used to convert the


dependent degrees of freedom (DOF’s) of a rigid
element constrained by global SPC’s to
independent DOF’s. In such situations, it is
recommended to create another subcase with a
different SPC set.

4. AUTOMSET cannot be used if Direct Matrix Input


(DMIG) generation is performed using the Static
Condensation method (Component Mode
Synthesis (CMSMETH entry) is not used).

1544 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, AUTOSPC

Parameter Values Description

AUTOSPC YES, NO If YES, the global stiffness matrix is checked for


Default = YES degrees-of-freedom with no stiffness. If found, these
degrees-of-freedom are automatically constrained.

If NO, the degrees of freedom with no stiffness are not


automatically constrained.

Altair Engineering OptiStruct 13.0 Reference Guide 1545

Proprietary Information of Altair Engineering


PARAM, AUTOSPRT

Parameter Values Description

AUTOSPRT <1, 0> This parameter applies to residual vector calculation in


Default = 1 inertia relief analysis.

If 1, rigid body modes from the eigenvalue analysis


(PARAM,FZERO defines cut-off for determination of rigid
body modes) are used to automatically generate
SUPORT dofs.

If 0, SUPORT dofs are automatically generated using the


6 geometric rigid body modes.

1546 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, BUSHRLMT

Parameter Values Description

BUSHRLMT <Real Number > This parameter is used to issue a WARNING when the
0.0> stiffness value for rotational components on the PBUSH
entry exceeds the specified limit (BUSHRLMT).
Default = 1.0E +
09 Note: This check is overridden when PARAM, BUSHSTIF
is used to control the maximum stiffness value.

Altair Engineering OptiStruct 13.0 Reference Guide 1547

Proprietary Information of Altair Engineering


PARAM, BUSHSTIF
Description

This parameter can accept two arguments. If only one argument is specified, the same value
is used for the second argument.

Format
PARAM, BUSHSTIF, <BUSHSTIFT>, <BUSHSTIFR>

Parameter Values Description

BUSHSTIFT <Real Number > This parameter controls the value of field “K” in the
0.0> PBUSH property entries.
No default BUSHSTIFT:
This value applies to translational stiffness fields on the
property entry (first three values).
BUSHSTIFR <Real Number >
0.0> BUSHSTIFR:
This value applies to rotational stiffness values on the
Default = property entry.
<BUSHSTIFT>
Note:

1. Any value on the field “K” on the PBUSH entry which


exceeds BUSHSTIFT or BUSHSTIFR, respectively will
be replaced by BUSHSTIFT or BUSHSTIFR.

2. Either BUSHSTIFT or BUSHSTIFR (or both) can be


set to 0.0. This will disable stiffness control for the
corresponding translational or rotational stiffnesses.

3. Defaults:

a. If BUSHSTIFT is input without specifying a value,


then OptiStruct will error out (no default). The
default for BUSHSTIFR is BUSHSTIFT.

b. If PARAM, BUSHSTIF is not included in the deck,


the stiffness value (Field K) is not replaced
regardless of its value (no stiffness control).

4. This parameter applies, in a similar fashion, to the


PBUSH1D Rod-type Spring-and-Damper Property as
well (using BUSHSTIFT).

1548 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, BUSHTLMT

Parameter Values Description

BUSHTLMT <Real Number > This parameter is used to issue a WARNING when the
0.0> stiffness value for translational components on the
PBUSH entry exceeds the specified limit (BUSHTLMT).
Default = 1E+07
Note: This check is overridden when PARAM, BUSHSTIF
is used to control the maximum stiffness value.

Altair Engineering OptiStruct 13.0 Reference Guide 1549

Proprietary Information of Altair Engineering


PARAM, CB2

Parameter Values Description

CB2 Real CB2 specified factors for the direct input damping matrix.
Default = 1.0 The total damping matrix is:

where is selected via the subcase information

command B2GG, and comes from CDAMP1, CDAMP2,


CDAMP3, CDAMP4, or CVISC element bulk data entries.

1550 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, CHECKEL

Parameter Values Description

CHECKEL NO, YES, FULL If NO, element quality checks are not performed, but
Default = YES mathematical validity checks are performed.

If YES, the geometric quality of each element is


checked. Any violation of the error limits is counted as a
fatal error and the run will stop. Any violation of warning
limits is non-fatal. Error or warning messages are printed
for elements violating the limits along with the offending
property values. The amount of output is limited to the
first 3 occurrences for each individual case, plus a
summary table of all errors.

If FULL, the same checks are performed as for YES, but


the error or warning messages are printed for all of the
elements violating the error or warning limits.

See Element Quality Check for an overview of the


element quality checking performed by the solver.

The ELEMQUAL bulk data entry may be used to control


the values for warning and error limits for each quality
check, but validity limits cannot be altered by the user.

Altair Engineering OptiStruct 13.0 Reference Guide 1551

Proprietary Information of Altair Engineering


PARAM, CHECKMAT

Parameter Values Description

CHECKMAT YES, NO, FULL If YES, the material properties for all referenced material
Default = YES definitions are checked for adherence to the default
material requirements as described on the Material
Property Check page. The amount of output is limited.

If NO, mathematical requirement checks only are


performed for all referenced material definitions.

If FULL, material property checks are performed as when


the value is YES, but all violations are output.

1552 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, CHKGPDIR

Parameter Values Description

CHKGPDIR YES, NO, WARN, If YES, all gap elements of non-zero length (distance
FULL, REVERSE between GA-GB) that have a prescribed coordinate
Default = YES system CID are checked for misalignment of gap
prescribed axis (x-axis of CID) with the vector GA->GB
(angles larger than 30 degrees produce errors). The
amount of output is limited to the first ten occurrences.
Note that this check applies correctly to the most
typical situations where in there is an initial opening
between bodies A and B, and the gap element is used
to enforce non-penetration condition (for other cases,
see the REVERSE option below).

If NO, no gap CID direction checks are performed.

If WARN, only warnings are issued.

If FULL, the error or warning messages are printed for


all gap elements violating this check.

If REVERSE, orientations of vector GA->GB generally


opposite to the prescribed x-axis of CID system are also
accepted (this can be used in cases when gap is used
to model rope behavior or when there is initial
penetration, rather than gap, between bodies A and B).
The tolerance levels are the same as for YES, except
that they are measured from either 0 or 180 degrees
reference angle.

For more details, refer to the CGAP description.

PARAM, CHKGPDIR is superseded by the CKGAPDIR


parameter on the GAPPRM bulk data entry if present.

Altair Engineering OptiStruct 13.0 Reference Guide 1553

Proprietary Information of Altair Engineering


PARAM, CK2

Parameter Values Description

CK2 Real CK2 specifies factors for the direct input stiffness matrix.
Default = 1.0 The total stiffness matrix is:

where is selected via the subcase information

command K2GG, and is generated from structural


element entries in the bulk data section.

1554 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, CK3

Parameter Values Description

CK3 Real CK3 specifies factors for the stiffness matrix produced by
Default = 1.0 GENEL cards. The total stiffness matrix is:

where is the stiffness generated by all GENEL cards

and is the combination of the stiffness generated


from structural element entries in the bulk data section and
the stiffness generated by the subcase information
command K2GG and scaled by PARAM,CK2.

Altair Engineering OptiStruct 13.0 Reference Guide 1555

Proprietary Information of Altair Engineering


PARAM, CM2

Parameter Values Description

CM2 Real CM2 specifies factors for the direct input mass matrix. The
Default = 1.0 total mass matrix is:

where is selected via the subcase information

command M2GG, and is generated from the mass


element entries in the bulk data section.

1556 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, CMFTINIT

Parameter Values Description

CMFTINIT 0.0 < REAL < 1.0 PARAM, CMFTINIT defines the lower threshold value used
Default = 0.0 for the HyperMesh command files *.HM.comp.cmf and
*.HM.ent.cmf.

These command files are used to organize elements,


which formed a topology or free-size design space, into
components (.comp.cmf) or sets (.ent.cmf), based on
their optimized densities/thicknesses.

Altair Engineering OptiStruct 13.0 Reference Guide 1557

Proprietary Information of Altair Engineering


PARAM, CMFTSTEP

Parameter Values Description

CMFTSTEP 0.0 < REAL < 1.0 PARAM, CMFTSTEP defines the step or interval value
Default = 0.1 used for the HyperMesh command files *.HM.comp.cmf
and *.HM.ent.cmf.

These command files are used to organize elements,


which formed a topology or free-size design space, into
components (.comp.cmf) or sets (.ent.cmf), based on
their optimized densities/thicknesses.

1558 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, CMSALOD

Parameter Values Description

CMSALOD <YES, NO> PARAM, CMSALOD controls the generation of RFORCE and
Default = YES Gravity loads from the mass matrix stored in the PUNCH
DMIG or H3DDMIG file.

If YES, the RFORCE and Gravity loads include the


contribution from the mass matrix stored in the PUNCH
DMIG or H3DDMIG file.

If NO, the DMIG mass contribution is ignored when


generating the RFORCE and Gravity loads.

Refer to Direct Matrix Input and DMIG.

Altair Engineering OptiStruct 13.0 Reference Guide 1559

Proprietary Information of Altair Engineering


PARAM, CMSDIRM

Parameter Values Description

CMSDIRM YES, NO PARAM, CMSDIRM allows flexible body generation when


Default = NO directional masses are defined in the input file.

If YES, the existence of directional mass will be allowed


for flexbody generation runs. A warning will be issued for
the ignored or approximated CMASS1, CMASS2, and
CONM1.

If NO, the run will be terminated with an ERROR if the


input file contains directional mass definitions and flexible
body generation is requested.

See the User’s Guide entry on Flexible Body Generation.

1560 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, CMSOFST

Parameter Values Description

CMSOFST <YES, NO> PARAM, CMSOFST applies to Component Mode Synthesis


Default = NO (CMS) runs for flexbody generation.

While element offsets are valid for DMIG generation, that


is performing CMS with METHOD = CBN or GUYAN, they
are undesirable for flexbody generation, that is
performing CMS with METHOD = CC or CB, as it may
introduce approximation error into the generated
flexh3d file, and so in general, you will not solve these
problems.

However, the approximation error for plates offset by


half of their thickness, such that the grids can be
aligned on one side of the plate surface, is tolerable.
Setting this parameter to YES will allow problems with
this kind of offset to be solved.

Altair Engineering OptiStruct 13.0 Reference Guide 1561

Proprietary Information of Altair Engineering


PARAM, COEFFC

Parameter Values Description

COEFFC Real > 0.0 Value of the friction coefficient on curvatures for one-
step stamping simulation.

1562 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, COMP2SHL

Parameter Values Description

COMP2SHL YES, NO, If YES or blank, results of homogenization of composite


BULK properties (equivalent shell and material, PSHELL and
Default = NO MAT2) will be printed in a descriptive form in the
“.out” file.

If NO, echo of composite homogenization will not be


printed.

If BULK, then results of composite homogenization


(equivalent PSHELL and MAT2) will be printed in a
version corresponding to bulk data input in large field
(long) format. This version can be cut and pasted
directly into an OptiStruct input deck.

Note: The equivalent shell and materials represent


composite properties as they are defined in the
input deck. In optimization runs involving
composites, OptiStruct internally adjusts and
changes the composite properties. Such
changes are not reflected in the equivalent
shell results printed by this command.

Altair Engineering OptiStruct 13.0 Reference Guide 1563

Proprietary Information of Altair Engineering


PARAM, CONTFEL

Parameter Values Description

CONTFEL <YES, NO> If YES, Contact-friendly elements are activated.


Default = NO PARAM, CONTFEL, YES is recommended when second
order solids/gaskets are used with contact analysis in
OptiStruct.

If NO, Contact-friendly elements are not activated.

1564 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, COUPMASS

Parameter Values Description

COUPMASS -1, 0, 1, YES, If -1, 0 or NO, the lumped mass matrix approach is used
NO for eigenvalue analysis.
Default = NO
If 1 or YES, the coupled mass matrix approach is used
for eigenvalue analysis.

Altair Engineering OptiStruct 13.0 Reference Guide 1565

Proprietary Information of Altair Engineering


PARAM, CP2

Parameter Values Description

CP2 Real CP2 specifies factors for the direct input load matrix.
Default = 1.0 The total load matrix is:

where is selected via the subcase information

command P2G, and is generated from the static


load entries in the bulk data section.

1566 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, CSTEVAL

Parameter Values Description

CSTEVAL YES, NO This parameter controls whether to use wall time based
Default = YES cost evaluation to provide the optimal performance in
running Lanczos steps.

The wall time based cost evaluation is a function of


system performance, hence it could be influenced by the
system load. Although it rarely happens, this influence
could result in a different number of Lanczos steps,
which could cause the resulting eigenvalues having a
round off difference. In most cases, this small difference
in solution is completely negligible for analysis. However,
it can produce visible differences in optimization runs or
in any solution that is sensitive to the small difference of
the obtained eigenvalues and eigenvectors.

If Yes, the wall time based cost evaluation is performed.

If NO, the wall time based cost evaluation is not


performed.

Altair Engineering OptiStruct 13.0 Reference Guide 1567

Proprietary Information of Altair Engineering


PARAM, CSTOL

Parameter Values Description

CSTOL <Real> PARAM, CSTOL relates to the FastFRS interface.


Default = 3.5
If the low rank representation is not selected, then a
cancellation tolerance must be provided. The CSTOL
value specifies how many decimal digits may be lost to
cancellation in one operation during the eigensolution
process. Since double precision arithmetic maintains
nearly 16 digits of precision, the recommended limit of
3.5 on the number of digits lost leaves more than 12
digits, which is quite conservative for maintaining
adequate accuracy for engineering purposes. You may
choose to increase this value to speed computation, at
the risk of introducing inaccuracy from uncorrected
cancellation error. Setting it to 16 turns off the
capability to address cancellation error in the
eigensolution, and this has consistently been found to
give very satisfactory results when the number of modes
is under three thousand.

Refer to the User’s Guide section, FastFRS Usage (Fast


Frequency Response Solver) for more details.

1568 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, DFREQ

Parameter Values Description

DFREQ Real DFREQ specified the threshold for the elimination of


Default = 10-5 duplicate frequencies on all FREQi bulk data entries.
and are considered duplicated if

where and are the maximum and minimum


excitation frequencies of the combined FREQi entries.

Altair Engineering OptiStruct 13.0 Reference Guide 1569

Proprietary Information of Altair Engineering


PARAM, DISIFMCK

Parameter Values Description

DISIFMCK <YES, NO> For vibrational eigenvalue analysis, the mass matrix must be
Default = NO positive semi-definite. However, if this is simply caused by
numerical ill-conditioning, then PARAM,DISIFMCK may be used
to skip the indefinite mass matrix check.

YES Skip indefinite mass matrix checking.

NO Perform indefinite mass matrix checking.

1570 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, DISJOINT

Parameter Values Description

DISJOINT <Integer> DISJOINT is used to allow AMLS to handle disconnected


Default = NONE parts. This can also be accomplished with
PARAM,AMLSUCON.

PARAM, DISJOINT should be set to one larger than the


number of disconnected parts as determined by AMLS.
PARAM, DISJOINT causes the environment variable
AMLS_NPART to be set to the value of PARAM, DISJOINT.
AMLS will read the value of AMLS_NPART and handle the
disconnected structure.

PARAM, DISJOINT can be set to a real value for


compatibility, but it is recommended to use an integer
value.

Altair Engineering OptiStruct 13.0 Reference Guide 1571

Proprietary Information of Altair Engineering


PARAM, DUPTOL

Parameter Values Description

DUPTOL <0, 1, 2, 3, 4, 5> PARAM, DUPTOL controls how many decimal places
Default = 0 can differ when comparing X, Y, and Z coordinates on
GRID and CORDxx cards with identical ID. Obsolete,
use SYSSETTINGS,DUPTOL command.

1572 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, EFFMAS

Param Values Description


eter

EFFMA <YES, When EFFMAS < 0 or NO, the modal participation factors, modal
S NO, participation factor ratio, and modal effective mass are not output for
Integer> normal modes analysis.
Default =
NO When EFFMAS > 0 or YES, the modal participation factors, modal
participation factor ratio, and modal effective mass will be computed and
output to the .out and .pch files for normal modes analysis. They are
computed as follows:

Modal Participation Factor =

The Modal Participation Factor is a measure of how close each mode is


to a rigid body mode.

The Modal Participation Factor Ratio is the Modal Participation Factor for
each rotational and translational direction divided by the maximum Modal
Participation Factor of all the modes for that direction. So, each of the
six directions will have a value of 1.0 for the mode that has the
maximum Modal Participation Factor and the other modes will have a
value less than 1.0.

Modal Effective Mass =

The Modal Effective Mass is a measure of how much mass is associated


with each mode.

whe is the matrix of eigenvectors.


re
[m] is the system mass matrix.

[V] is the objective function matrix. Six rigid body modes are
used as objective function in normal modes analysis to
obtain [PF] and [EFFMAS].

[M] is the diagonal modal mass matrix.

Altair Engineering OptiStruct 13.0 Reference Guide 1573

Proprietary Information of Altair Engineering


PARAM, EHD

Parameter Values Description

EHD <YES, NO> This parameter is used to print the inverse of the
Default = NO stiffness matrix created by static reduction to FORTRAN
unit 3. The inverse reduced stiffness matrix is written in
NASTRAN MATPRN format.

To perform static reduction there must be ASET data


and PARAM,EXTOUT,DMIGPCH in the input data. After
the stiffness matrix is reduced to the ASET DOF, its
inverse is calculated and written using NASTRAN
MATPRN format to FORTRAN unit 3.

PARAM,EXTOUT,DMIGPCH must also be specified when


this parameter is used in order to trigger the static
reduction.

1574 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, ELASRLMT

Parameter Values Description

ELASRLMT <Real Number > This parameter is used to issue a WARNING when the
0.0> stiffness value for rotational components on the
CELAS2/4 or PELAS entry exceeds the specified limit
Default = 1.0E +
(ELASRLMT).
09
Note: This check is overridden when PARAM, ELASSTIF
is used to control the maximum stiffness value.

Altair Engineering OptiStruct 13.0 Reference Guide 1575

Proprietary Information of Altair Engineering


PARAM, ELASSTIF
Description

This parameter can accept two arguments. If only one argument is specified, the same value
is used for the second argument.

Format
PARAM, ELASSTIF, <ELASSTIFT>, <ELASSTIFR>

Parameter Values Description

ELASSTIFT <Real Number > This parameter controls the value of field “K” in the
0.0> PELAS scalar elastic property entry and the CELAS2/
CELAS4 scalar spring property and connection entries.
No default
ELASSTIFT:
This value applies to translational stiffness fields on the
PELAS scalar elastic property entry and the CELAS2/
CELAS4 scalar spring property and connection entries.

ELASSTIFR:
This value applies to rotational stiffness values on the
ELASSTIFR <Real Number > PELAS scalar elastic property entry and the CELAS2/
0.0> CELAS4 scalar spring property and connection entries.
Default =
Note:
<ELASSTIFT>
1. Any value on the field “K” on the PELAS or CELAS2/
CELAS4 entry which exceeds ELASSTIFT or
ELASSTIFR, respectively will be replaced by
ELASSTIFT or ELASSTIFR.

2. Either ELASSTIFT or ELASSTIFR (or both) can be set


to 0.0. This will disable stiffness control for the
corresponding translational or rotational stiffnesses.

3. Defaults:

a. If ELASSTIFT is input without specifying a value,


then OptiStruct will error out (no default). The
default for ELASSTIFR is ELASSTIFT.

b. If PARAM, BUSHSTIF is not included in the deck,


the elastic property value (Field K) is not replaced
regardless of its value (no stiffness control).

1576 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, ELASTLMT

Parameter Values Description

ELASTLMT <Real Number > This parameter is used to issue a WARNING when the
0.0> stiffness value for translational components on the
CELAS2/4 or PELAS entry exceeds the specified limit
Default = 1E+07
(ELASTLMT).

Note: This check is overridden when PARAM, ELASSTIF


is used to control the maximum stiffness value.

Altair Engineering OptiStruct 13.0 Reference Guide 1577

Proprietary Information of Altair Engineering


PARAM, ENFMOTN

Parameter Values Description

ENFMOTN <REL, ABS, If ABS, TOTAL or blank, the displacements/velocities/


TOTAL> accelerations output during Modal Frequency Response
Default = ABS Analysis and Modal Transient Response Analysis are the
total/absolute displacements/velocities/accelerations
that include the specified enforced motion. Stresses/
forces will be calculated (if requested) based on the
total displacements/velocities/accelerations.

If REL, the displacements/velocities/accelerations output


during Modal Frequency Response Analysis and Modal
Transient Response Analysis are relative to the enforced
motion specified in the model. Stresses/forces will be
calculated (if requested) based on the relative
displacements/velocities/accelerations.

1578 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, ERPC

Parameter Values Description

ERPC Real > 0.0 The speed of sound used in the ERP calculation:
Default = 1.0

Altair Engineering OptiStruct 13.0 Reference Guide 1579

Proprietary Information of Altair Engineering


PARAM, ERPREFDB

Parameter Values Description

ERPREFDB Real > 0.0 This parameter can be used to specify the reference
Default = 1.0 power value used to calculate Equivalent Radiated Power
(ERP) in decibels (dB).

Note:

The Equivalent Radiated Power (ERP) in decibels can be


calculated using the following equation:

Where,

ERPdB is the Equivalent Radiated Power in decibels.

RHOCP is the value of the scale factor specified using


the parameter PARAM, RHOCP.

ERPREFDB is the reference power value specified using


this parameter.

1580 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, ERPRHO

Parameter Values Description

ERPRHO Real > 0.0 The fluid density used in ERP calculations:
Default = 1.0

Altair Engineering OptiStruct 13.0 Reference Guide 1581

Proprietary Information of Altair Engineering


PARAM, ERPRLF

Parameter Values Description

ERPRLF Real > 0.0 The Radiation Loss Factor used in the ERP calculation:
Default = 1.0

1582 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, EXCEXB

Parameter Values Description

EXCEXB <YES, BOTH, NO> This parameter controls the output of the AVL/EXCITE
.exb file directly from OptiStruct.
Defaults
If this parameter If YES, the AVL/EXCITE .exb file is output.
is included in the
If BOTH, the AVL/EXCITE .exb file and the old files
input file, but, no
(.doft, .geom, _mff.out4, _x2oa.out4, and .out4)
value is provided,
then the default are output.
value is YES. If NO, the AVL EXCITE interface output files are not
If this parameter output.
is not included in Note: PARAM, EXCEXB, YES/BOTH should be used in
the input file (and conjunction with PARAM, EXCOUT. OptiStruct will
PARAM, EXCOUT error out if PARAM, EXCEXB, YES/BOTH is
is present), then specified without PARAM, EXCOUT in the model.
the default value
is BOTH.

Altair Engineering OptiStruct 13.0 Reference Guide 1583

Proprietary Information of Altair Engineering


PARAM, EXCOUT

Parameter Values Description

EXCOUT <-1, 0, 1, 3, 4, 5, Output of condensed superelement information for AVL/


6> EXCITE.
Default = 0
-1 No output.

0 All output.

1 DOF, geometry, and elements tables (GEOM1,


GEOM2, EQEXIN, and USET), as well as the
reduced mass and stiffness matrices (MAA and
KMAA).

3 1 + eigenvectors of the full system (GOA


transpose).

4 3 + unreduced mass matrix (MFF).

5 1 + eigenvectors of condensed system (PHA) and


the grid point stress table (OGS1).

6 4 + eigenvectors of condensed system (PHA) and


the grid point stress table (OGS1).

1. When PARAM,EXCOUT,1 is defined, only the ASET


dofs are output when the MODEL card is not
present. Otherwise, the entire model is output when
the MODEL card is not present.

2. PARAM, EXCEXB, BOTH is automatically activated if


PARAM, EXCOUT is present in the input deck.

1584 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, EXPERTNL

Parameter Values Description

EXPERTNL YES, NO, YES activates a nonlinear "expert system" that aids in the
CNTSTB, convergence of small displacement nonlinear problems
AUTO (NLSTAT). This version is designed to facilitate obtaining
converged, high accuracy solutions without much concern
Default = for computational time. The system monitors the
AUTO convergence of nonlinear processes and, if needed,
implements measures designed to improve convergence for
poorly converging cases. These measures include:
performing additional iterations, under-relaxation, automatic
adjustment of the load increment, as well as backing off to
the last convergent solution and retrying. This may lead to
a large number of nonlinear iterations for poorly converging
problems.

CNTSTB additionally introduces temporary stabilization on


contact interfaces (CONTACT or GAP(G) elements) that may
improve nonlinear convergence, especially in cases where
individual parts lack full support and are supported only by
contact. The stabilization is applied only during incremental
loading and is not present in the final solution for the
respective nonlinear subcase.

AUTO activates a “light” version of the expert system, which


is designed to facilitate converging nonlinear process in
reasonably close to minimum number of iterations. In
particular, this version may adjust the time step, including
increasing the time step beyond that prescribed on the
NLPARM card.

This parameter does not apply to geometric nonlinear


solution sequences (NLGEOM, IMPDYN or EXPDYN).

Altair Engineering OptiStruct 13.0 Reference Guide 1585

Proprietary Information of Altair Engineering


PARAM, EXTOUT

Parameter Values Description

EXTOUT DMIGPCH, EXTOUT controls the output of reduced matrices to


DMIGBIN external data files for use in subsequent analyses.
No default
If DMIGPCH, the matrices are written to an ASCII .pch
file.

If DMIGBIN, the matrices are written to a binary .dmg


file.

See the User's Guide section The Direct Matrix Approach


for more detailed information.

1586 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, FASTFR

Parameter Values Description

FASTFR <YES, NO> If, AUTO (Default), the faster method is automatically
Default = AUTO chosen by the program for Modal Frequency Response
Analysis. If the FASTFR method is not activated, the
standard method is used (see comments).

If YES, and if FASTFR is allowed (see comments), it


activates an alternative method to run Modal Frequency
Response Analysis that enhances the performance.

If NO, the FASTFR method is deselected and the program


is run using the standard solution method.

Comments:
The FASTFR method will be ignored for Modal Frequency
Response Analysis, if:

1. Multiple modal spaces exist in the model.

2. Single Program, Multiple Data (SPMD) parallelization


has been requested.

3. Viscous degrees of freedom are significantly large.

The FASTFR method will be allowed, if Shared Memory


Parallelism (SMP) parallelization has been requested by
specifying the number of processors using the –nproc run
option.

Altair Engineering OptiStruct 13.0 Reference Guide 1587

Proprietary Information of Altair Engineering


PARAM, FFRS

Parameter Values Description

FFRS <YES, NO> This parameter is used to invoke the external FastFRS
Default = NO (Fast Frequency Response Solver). This solver is very
efficient for a certain class of large modal frequency
response problems, such as those common in automotive
NVH analysis. Note that FastFRS must be installed on the
system and the environment variable FASTFRS_EXE must
point to the FastFRS executable for this setting to work.

If YES, then the external FastFRS solver is used.

If NO, then the internal solver is used.

Refer to the User’s Guide section, FastFRS Usage (Fast


Frequency Response Solver) for more details.

1588 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, FFRSLFREQ

Parameter Values Description

FFRSLFREQ <Real> PARAM, FFRSLFREQ relates to the FastFRS interface.


Default = 1.0
It defines a frequency cut-off value in Hertz used to
partition the structural system into low frequency and
high frequency parts, to improve matrix condition
numbers and solution accuracy at a very small
computational cost.

If the value is defined as 0.0, then FastFRS will set


FFRSLFREQ to 1.0.

Refer to the User’s Guide section, FastFRS Usage (Fast


Frequency Response Solver) for more details.

Altair Engineering OptiStruct 13.0 Reference Guide 1589

Proprietary Information of Altair Engineering


PARAM, FFRSMEM

Parameter Values Description

FFRSMEM <Real> This parameter is used to define the amount of memory in


Gigabytes to be used by the external FastFRS modal
Default = equation solver. This parameter is only valid for FastFRS
Memory used versions 2 and higher.
by OptiStruct
for a particular Note:
run. 1. If this parameter is not set, FastFRS will use the
amount of memory that OptiStruct is using for the
run.

2. If the environment variable FFRS_MEM is set, it will


override the value set using PARAM, FFRSMEM.

3. OptiStruct and FastFRS can be run with different


allocations of memory. For example, OptiStruct can
be run with 10.0 Gigabytes and FastFRS with 20.0
Gigabytes in the same run.

4. This parameter is only valid when PARAM, FFRS is set


to YES.

Refer to the User’s Guide section, FastFRS Usage (Fast


Frequency Response Solver) for more details.

1590 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, FFRSNCPU

Parameter Values Description

FFRSNCPU <Integer> PARAM, FFRSNCPU relates to the FastFRS interface.


Default =
number of cpu's This parameter is used to define the number of cpu’s to
used by be used by the external FastFRS solver. This parameter
OptiStruct. will set the environment variable OMP_NUM_THREADS.
The default value is the current value of
OMP_NUM_THREADS.

Note

1. If FFRSNCPU is not set, but AMLSNCPU is set, the


FastFRS will use the number of cpu’s specified by
AMLSNCPU.

2. OptiStruct and FastFRS can be run with different


allocations of processors. For example, OptiStruct
can be run with one processor and FastFRS with four
processors in the same run.

3. This parameter is only valid when PARAM, FFRS or


the run option –ffrs is set to YES.

Refer to the User’s Guide section, FastFRS Usage (Fast


Frequency Response Solver) for more details.

Altair Engineering OptiStruct 13.0 Reference Guide 1591

Proprietary Information of Altair Engineering


PARAM, FLEXH3D

Parameter Values Description

FLEXH3D AUTO, YES, NO This parameter controls the generation of flexh3d files
Default = AUTO for flexible bodies in an MBD analysis.

If AUTO, flexh3d files are generated only for those


flexible bodies for which no previously generated
flexh3d file exists. Previously generated flexh3d files
are checked for validity; if the file is valid for the
corresponding flex-body definition, the run will
continue using the existing flexh3d file. If the file is
found to be invalid (has a different mass or the wrong
number of grids), an error termination will occur.

If YES, flexh3d files are generated for all flexible


bodies, overwriting existing files (if present).

If NO, flexh3d files are not generated. The run makes


use of previously generated files. An error termination
will occur if no such files exist.

1592 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, FLIPOK

Parameter Values Description

FLIPOK NO, YES If YES, severely distorted and possibly inverted elements
Default = NO will be accepted by the solver. This is limited to first
order tetra (CTETRA) and tria (CTRIA3) elements.

If NO, severely distorted elements will not be accepted


by the solver, and the solution will be terminated with an
error to avoid inaccurate results.

Altair Engineering OptiStruct 13.0 Reference Guide 1593

Proprietary Information of Altair Engineering


PARAM, FRIC

Parameter Values Description

FRIC <REAL> PARAM, FRIC defines a multiplier for matrices (DMIG)


Default = 1.0 referenced by K2PP.

1594 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, FZERO

Parameter Values Description

FZERO <Real> This parameter defines the maximum frequency for a rigid
Default = 0.1 body mode for the Lanczos eigensolver. That is all
eigenmodes with frequency at or below this cutoff will be
regarded as rigid body modes in the inertia relief
analysis.

Note:

To set the rigid body mode cutoff eigenvalue for the


AMSES and AMLS eigensolvers, use PARAM, RBMEIG.

Altair Engineering OptiStruct 13.0 Reference Guide 1595

Proprietary Information of Altair Engineering


PARAM, G

Parameter Values Description

G <Real> G specifies the uniform structural damping coefficient in


Default = 0.0 the formulation of dynamics problems.

To obtain the value for the parameter G, multiply the


critical damping ratio, C/C0 by 2.0.

Note:

To achieve identical displacements in Modal frequency


response or Modal transient analyses when the SDAMPING
bulk data entry is used instead of PARAM, G, the steps
described here can be followed:

1. The TYPE field in the TABDMP1 bulk data entry should


be set to CRIT. This TABDMP1 bulk data entry is
referenced by the SDAMPING subcase information
entry.

2. Set the damping value (field gi) in the TABDMP1 bulk


data entry equal to half of the value of PARAM, G
(that is set the constant value to C/C0).

3. Set PARAM, KDAMP,-1.

1596 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, GE_MOD

Parameter Values Description

GE_MOD <Real or The real value of GE_MOD overrides the value of GE


NO_GE> specified in all MATx material data, sets the table ID for
No default GE on the MATTx material data to zero, and overrides the
value of GE specified on the PCOMP, PCOMPP, and
PCOMPG data. GE_MOD can be set to 0.0 to remove all
material-based structural damping from the model. The
damping from PARAM, G will also be applied when GE_MOD
is present.

The GE_MOD setting of NO_GE is used to remove all


structural damping from the model. When NO_GE is
specified, the value of GE will be set to zero on all MATx
material data and the GE values specified in the CELAS2,
PELAS, PELAST, PBUSH, PBUSHT, PCOMP, PCOMPP, and
PCOMPG data will also be set to zero. In addition, the
table ID for GE on MATTx material data will be set to
zero. PARAM, G can be used to set the value to a
constant value for the entire structure.

Altair Engineering OptiStruct 13.0 Reference Guide 1597

Proprietary Information of Altair Engineering


PARAM, GFL

Parameter Values Description

GFL <Real> GFL specifies the uniform fluid damping coefficient in the
Default = 0.0 formulation of dynamics problems. To obtain the value
for the parameter GFL, multiply the critical damping
ration, C/C0, by 2.0.

In coupled fluid-structure models, PARAM, G is applied to


structural portion and PARAM, GFL to the fluid portion.

1598 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, GMAR

Parameter Values Description

GMAR <REAL> PARAM, GMAR is used to control the accuracy of the


Default = 1.1 AMLS solution.

Refer to the User’s Guide section, Using the AMLS


(Automatic Multi-Level Sub-structuring) Eigensolver for
more details.

Altair Engineering OptiStruct 13.0 Reference Guide 1599

Proprietary Information of Altair Engineering


PARAM, GMAR1

Parameter Values Description

GMAR1 <REAL> PARAM, GMAR1 is used to control the accuracy of the


Default = 1.7 AMLS solution.

Refer to the User’s Guide section, Using the AMLS


(Automatic Multi-Level Sub-structuring) Eigensolver for
more details.

1600 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, GPSLOC

Parameter Values Description

GPSLOC Z1, Z2 and MID Used to control the where grid point stresses are
calculated for output to the .mnf file.
Default = Z1
The highest stresses are at the bottom (Z1) or top (Z2)
surface of the shell. For pure bending, they have the
same magnitude.

GPSLOC is used to specify the location of the calculation


of the grid point stresses. They can be calculated at the
bottom surface (Z1), top surface (Z2), or at the mid-
plane (MID).

Altair Engineering OptiStruct 13.0 Reference Guide 1601

Proprietary Information of Altair Engineering


PARAM, GRDPNT

Parameter Values Description

GRDPNT <GID> If = -1, no output from grid point weight generator.

If = 0, the center of gravity coordinates are relative to


the origin of the basic coordinate system and are
Default = -1 expressed in the coordinate system CID.

If > 0, the center of gravity coordinates are relative to


GID and are expressed in the coordinate system CID.

Note:

1. The coordinate system CID is defined by PARAM,


UCORD.

2. If PARAM, UCORD is not specified, CID = -1, or CID


given is not found, all values are calculated relative
to the basic coordinate system.

3. If PARAM, GRDPNT is not specified in the input deck,


then the center of gravity and moment of inertia are
not output regardless of the value of PARAM, UCORD.

1602 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, GRIDFORM

Parameter Values Description

GRODFORM < LONG, SHORT > This parameter controls the output format of the
Default = SHORT .grid file.

If LONG, the Large Field Fixed Format is used to


output the .grid file.

If SHORT (Default), the Fixed Format is used to


output the .grid file.

Altair Engineering OptiStruct 13.0 Reference Guide 1603

Proprietary Information of Altair Engineering


PARAM, GYROAVG

Parameter Values Description

GYROAVG <0, -1> This parameter is used to select the frequency


Default = 0 response analysis formulation type for rotor dynamics
analysis.
PARAM, GYROAVG, 0

If this formulation is selected, the frequency-


dependent rotor dynamics terms are calculated for
each frequency. A frequency-dependent looping
option is activated, however, the run time is higher
compared to PARAM, GYROAVG, -1 as the calculation
process has to be repeated for each frequency in
the specified range.
PARAM, GYROAVG, -1

If this formulation is selected, frequency-dependent


looping does not occur and an average frequency
method is used to calculate the rotor dynamic terms.
The run time is lower compared to PARAM, GYROAVG,
0 as this option avoids intensive calculations for
each frequency. PARAM, WR3 and PARAM, WR4 must
be specified for this formulation to include rotor
damping.

Refer to the User’s Guide section, Rotor Dynamics


for more details.

1604 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, HASHASSM

Parameter Values Description

HASHASSM YES, NO This parameter is used to enable the hash-table based


Default = NO assembly method.

The hash-table based assembly method reduces the


memory requirement of the assembly module by about a
factor of 3 for linear static analyses, by about a factor of
5 for eigenvalue analyses, and by about a factor of 7 for
frequency response analyses involving material damping.

The reduction in the overall memory requirement is


problem-dependant. For problems where modules other
than the assembly module are dictating the overall
memory requirement, using this alternative assembly
method will not result in a reduction in the overall memory
requirement.

Using the hash-table based assembly method while


possibly reducing memory requirements may result in
longer run times.

If YES, hash-table based assembly method is used.

If NO, hash-table based assembly method is not used.

Altair Engineering OptiStruct 13.0 Reference Guide 1605

Proprietary Information of Altair Engineering


PARAM, HFREQ

Parameter Values Description

HFREQ Real> Modes with frequencies higher than HFREQ are not used
(Hertz) in Modal Frequency Response and Modal Transient
Analysis.
Default = None
HFREQ is used in Response Spectrum Analysis to specify
Defaults the upper bound of the frequency range of interest for
modal combination.
If PARAM,
HFREQ is input Note:
without
specifying a 1. The Residual Vector (RESVEC) calculation still
value, then the includes the modes above HFREQ so that they are
solution runs normalized correctly.
into an error 2. Modes that are eliminated by PARAM, HFREQ will
display:

a) an “S” next to the mode number if the mode is


eliminated by MODESELECT in one subcase and
PARAM, HFREQ in another subcase, or

b) an “H” next to the mode number if the mode is


eliminated only by PARAM, HFREQ.

1606 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, HFREQFL

Parameter Values Description

HFREQFL Real> Modes with frequencies greater than HFREQFL are not
(Hertz) used in Coupled Modal Frequency Response Analysis.
HFREQFL can be used to remove Rigid Body Modes from
Default = None the Modal Space.

Defaults Note: Modes that are eliminated by PARAM, HFREQFL will


If PARAM, display an “H” next to the mode number.
HFREQFL is
input without
specifying a
value, then the
solution runs
into an error

Altair Engineering OptiStruct 13.0 Reference Guide 1607

Proprietary Information of Altair Engineering


PARAM, I64SLV

Parameter Values Description

I64SLV YES, NO This parameter is used to enforce the activation of


Default = NO internal long (64-bit) integer sparse direct solver. With
automatic memory allocation mode, the solver
automatically decides whether or not to switch the 64-bit
integer solver on. However, even if the 64-bit integer
solver is not the preferred choice in certain scenarios,
this parameter can still be used to enforce activation.

YES: the long (64-bit) integer sparse direct solver is


used.

NO: the short (32-bit) integer sparse direct solver is


used.

1608 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, INREL

Parameter Values Description

INREL < 0, -1, -2 > INREL controls the calculation of inertia relief.

Default = 0, for -2 requests inertia relief analysis without the need


static subcases for a SUPORT/SUPORT1 entry.

Default = -2, for -1 requests that inertia relief be performed.


modal frequency SUPORT or SUPORT1 cards are required in the bulk
response subcases data section to restrain rigid body motion. The total
number of degrees-of-freedom specified on SUPORT
and SUPORT1 cards must be less than or equal to
six.

0 requests that constrained analysis be performed.


SUPORT and SUPORT1 cards are treated like SPC in
this case.

Altair Engineering OptiStruct 13.0 Reference Guide 1609

Proprietary Information of Altair Engineering


PARAM, ITAPE

Parameter Values Description

ITAPE -1, 0 If ITAPE = -1, then the ‘Tape Label’ is written at the
Default = -1 beginning of the OUTPUT2 results file.

1610 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, INTRFACE

Parameter Values Description

INTRFACE YES, NO If YES, OptiStruct generates the .interface file which


Default = YES contains data about the Fluid-Structure Coupling. The
.interface file can then be loaded into HyperMesh to
verify if the Fluid and Structure meshes are properly
connected at the interface. The parameters that
determine the Fluid-Structure coupling are set in the
ACMODL Data.

If NO, the .interface file is not generated.

Comments

1. When the fluid domain is represented by an MFLUID card, and PARAM, INTRFACE, YES is
specified, OptiStruct generates the .wetel file which contains data about the wet
elements resulting from MFLUID cards. The .wetel file can then be loaded into HyperMesh
to visualize the locations of submerged/damp elements in the model.

Altair Engineering OptiStruct 13.0 Reference Guide 1611

Proprietary Information of Altair Engineering


PARAM, K4CUTOFF

Parameter Values Description

K4CUTOFF <Real> PARAM, K4CUTOFF relates to the FastFRS interface.


Default = 0.1
If the low rank representation for the structural damping
matrix is selected, a cut-off value must be set. The
value is set using K4CUTOFF.

Refer to the User’s Guide section, FastFRS Usage (Fast


Frequency Response Solver) for more details.

1612 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, KDAMP

Parameter Values Description

KDAMP < 1, -1 > If KDAMP is set to –1, modal damping is entered into the
Default = 1 complex stiffness matrix as material damping.

If KDAMP is set to 1, modal damping is entered into the


complex stiffness matrix as viscous damping.

Note:

To achieve identical displacements in Modal frequency


response or Modal transient analyses when the SDAMPING
subcase information entry is used instead of PARAM, G, the
steps described here can be followed:

1. The TYPE field in the TABDMP1 bulk data entry should


be set to CRIT. This TABDMP1 bulk data entry is
referenced by the SDAMPING subcase information entry.

2. Set the damping value (field gi) in the TABDMP1 bulk


data entry equal to half of the value of PARAM, G (that
is set the constant value to C/C0).

3. Set PARAM, KDAMP,-1 (See description above).

Altair Engineering OptiStruct 13.0 Reference Guide 1613

Proprietary Information of Altair Engineering


PARAM, KGRGD

Parameter Values Description

KGRGD YES, NO If YES, the rigid elements contribution to the geometric


Default = NO stiffness matrix is included. This may result in missing
buckling modes that are found in other codes.

If NO, the rigid elements contribution to the geometric


stiffness matrix is omitted. This is the default.

1614 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, LFREQ

Parameter Values Description

LFREQ <Real> Modes with frequencies less than LFREQ are not used in
(Hertz) Modal Frequency Response and Modal Transient Analysis.
LFREQ can be used to remove Rigid Body Modes from the
Default = None Modal Space.

Defaults LFREQ is used in Response Spectrum Analysis to specify


If PARAM, the lower bound of the frequency range of interest for
LFREQ is input modal combination.
without
specifying a Note:
value, then the 1. The Residual Vector (RESVEC) calculation still includes
solution runs the modes below LFREQ so that they are normalized
into an error. correctly.

2. Modes that are eliminated by PARAM, LFREQ will


display:

a) an “S” next to the mode number, if the mode is


eliminated by MODESELECT in one subcase and
PARAM, LFREQ in another subcase, or

b) an “L” next to the mode number, if the mode is


eliminated only by PARAM, LFREQ.

Altair Engineering OptiStruct 13.0 Reference Guide 1615

Proprietary Information of Altair Engineering


PARAM, LFREQFL

Parameter Values Description

LFREQFL Real> Modes with frequencies less than LFREQFL are not used
(Hertz) in Coupled Modal Frequency Response Analysis. LFREQFL
can be used to remove Rigid Body Modes from the Modal
Default = None Space.

Defaults Note: Modes that are eliminated by PARAM, LFREQFL will


If PARAM, display an “L” next to the mode number.
LFREQFL is
input without
specifying a
value, then the
solution runs
into an error

1616 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, LGDISP

Parameter Values Description

LGDISP <0, 1, -1> If LGDISP = 1, Large displacement nonlinear static analysis


Default = 0 is activated. The corresponding nonlinear solution
parameters should be specified in the NLPARM bulk data
entry.

If LGDISP = 0 or -1, Large displacement nonlinear static


analysis is deactivated (Small displacement nonlinear static
analysis is the default). The corresponding nonlinear
solution parameters should be specified in the NLPARM bulk
data entry.

Altair Engineering OptiStruct 13.0 Reference Guide 1617

Proprietary Information of Altair Engineering


PARAM, LMSOUT

Parameter Values Description

LMSOUT <YES, NO, This parameter controls the output of the condensed flex
STRESS> body modes, full diagonal mass matrix, and modal stresses
Default = NO to the .op2 file.

If YES, the condensed flex body modes and the full diagonal
mass matrix are output to the .op2 file.

If STRESS, the modal stresses are also output to the .op2


file.

If NO, the condensed flex body modes, full diagonal mass


matrix and the modal stresses are not output to the .op2
file.

1618 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, LOWRANK

Parameter Values Description

LOWRANK <0,-1 or 1> PARAM, LOWRANK relates to the FastFRS interface.


Default = 0
It indicates to FastFRS which solution strategy to use to
handle the modal structural damping matrix.

If the value is 0, then FastFRS computes a full eigensolution


using the data found in either the optimization FSPSD data
block or the diagonal stiffness and structural damping data
blocks.

If the value is -1, a low rank representation of the matrix


found in structural damping is used.

A special case of this option occurs when acoustic fluid is


present in the model and the matrices found in the fluid
mass matrix, fluid stiffness matrix, and fluid viscous damping
matrix data blocks are all diagonal. FastFRS takes
advantage of this special case when the value of LOWRANK
is set to 1 by treating the matrix found in the structural
damping data block and the fluid matrices as low rank
representations. Note that for optimization problems, the
mass and stiffness matrices are full and a low rank
representation cannot be used.

Refer to the User’s Guide section, FastFRS Usage (Fast


Frequency Response Solver) for more details.

Altair Engineering OptiStruct 13.0 Reference Guide 1619

Proprietary Information of Altair Engineering


PARAM, MASSDMIG

Parameter Values Description

MASSDMIG YES, NO For static condensation with ASET of a static loadcase,


Default = NO the reduced stiffness matrix [k] and load vector {p} are
created. If the reduced mass matrix is also desired,
then set PARAM, MASSDMIG to YES.

1620 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, MAXDAMP

Parameter Values Description

MAXDAMP <Integer> Identifies the maximum number of viscous residual vectors


Default = 400 that are to be calculated. If MAXDAMP is exceeded, a
WARNING message is issued and no viscous residual
vectors are calculated.

Solution times can be greatly extended due to the


calculation of large numbers of viscous residual vectors, if
this is not intended by the user.

Altair Engineering OptiStruct 13.0 Reference Guide 1621

Proprietary Information of Altair Engineering


PARAM, MBDH3D

Parameter Values Description

MBDH3D NODAL, MODAL, This parameter controls the type of results output
BOTH, NONE to the .h3d results format for MBD analyses.
Default = BOTH
If NODAL, nodal based results are output to the
.h3d results file.

If MODAL, modal based results are output to the


_mbd.h3d results file.

If BOTH, nodal results are output to the .h3d


results file and modal results are output to the
_mbd.h3d file.

If NONE, MBD results are not output to either the


.h3d or _mbd.h3d results file.

Note: If the HyperMesh output format is requested,


nodal based results will be output to the
.res file, regardless of this parameter
setting.

1622 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, MBDREC

Parameter Values Description

MBDREC YES, NO PARAM, MBDREC creates two flexible body files


Default = NO during Component Mode Synthesis (CMS).

A small *.h3d is generated that contains the


minimum amount of information required for MBD
simulation in MotionSolve.

A larger file *_recov.h3d will also be generated that


contains the information from the small file as well as
recovery information for displacement, velocity,
acceleration, stress, and strain.

The large file is used along with the MotionSolve


calculated result (.mrf) file specified with the
ASSIGN, MBDINP data in an OptiStruct transient
analysis to recover displacement, velocity,
acceleration, stress, and strain results of the flex
body. These results can be output in the .op2 and
.h3d files.

See the User’s Guide entry on Flexible Body


Generation.

Altair Engineering OptiStruct 13.0 Reference Guide 1623

Proprietary Information of Altair Engineering


PARAM, MEMTRIM

Parameter Values Description

MEMTRIM YES, NO This parameter is used to activate/deactivate the memory


Default = YES trim feature for AMLS runs.

AMLS is an external program that requires its own memory


and disk space to perform eigenvalue analysis. Without
memory trim, the total memory requirement (T) to perform
eigenvalue analysis using AMLS was the sum of the memory
required by OptiStruct (O), the memory exclusively
allocated for AMLS (A), and other miscellaneous memory
requirements; for example, MIO library requirement, (M).
Thus:

T = O + A + M.

With memory trim enabled, the total memory requirement is


reduced to:

T = max(O,A) + M.

If YES, memory trim is active.

If NO, memory trim is inactive.

1624 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, MFILTER

Parameter Values Description

MFILTER <0.0 < real This parameter defines a threshold for the mode tracking
number < 1.0> matrix to check eigenvector correspondence.

Defaults: If an entry of the mode tracking matrix is greater than


the specified threshold, the eigenvectors of previous and
-If this current iterations (corresponding to the row number and
parameter is column number of the entry) are assumed to have
included in the correspondence.
input file, but, no
value is If PARAM, TRAKMETH is set to 0, the mass matrix based
provided, then cross-orthogonality criterion (CORC) is used to check for
running the
program will eigenvector correspondence, and PARAM, MFILTER is set
result in an to 0.7.
error. In such
cases a real If PARAM, TRAKMETH is set to 1, the modal assurance
value between criterion square root (MACSR) is used, and PARAM,
0.0 and 1.0 must MFILTER is set to 0.7.
be specified.
If PARAM, TRAKMETH is set to 2, the modal assurance
- If this criterion (MAC) is used and PARAM, MFILTER is set to be
parameter is not 0.5.
included in the
input file, then:

The value of
PARAM,
MFILTER is
equal to 0.7 if
PARAM,
TRAKMETH is
set to 0 or 1.

The value of
PARAM,
MFILTER is
equal to 0.5 if
PARAM,
TRAKMETH is
set to 2.

Altair Engineering OptiStruct 13.0 Reference Guide 1625

Proprietary Information of Altair Engineering


PARAM, MODETRAK

Parameter Values Description

MODETRAK -1, 0, 1, YES, If -1, 0 or NO, mode tracking is not used. Mode numbers
NO are determined by frequency.
Default = NO
If 1 or YES, mode tracking is used. Mode numbers are
tracked by comparing eigenvectors between iterations.

Concerning mode tracking, the following symbols are used


in the output format:

* Indicates that the tracked mode was not found in


the modes retrieved for that iteration. If this mode
is not a part of the objective, optimization will
continue and mode will be tracked if found in later
iterations, otherwise optimization will stop. If
optimization is halted for this reason, increase the
number of modes or range of modes being retrieved.

~ Indicates that the tracked mode was found but


does not correlate well with the original mode.
Optimization will continue.

Note: In topology optimization, mode shapes can


change greatly due to the reorganization of
material within the design domain. For some
models, mode tracking may be of limited
effectiveness. Also, the values of optimized
modes may increase substantially during the
optimization process. You are advised to provide
a wide range or large number of modes in the
EIGRL card to protect against optimized modes
being lost.

Note: This parameter is ignored if a MODTRAK subcase


information entry is present in the input.

1626 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, NEGMASS

Parameter Values Description

NEGMASS 0, 1 This parameter is used to check for negative


Default = 0 diagonal mass.

If 0, an error termination will occur if negative


diagonal mass is discovered.

If 1, negative diagonal mass or inertia from CONM2 is


allowed.

Altair Engineering OptiStruct 13.0 Reference Guide 1627

Proprietary Information of Altair Engineering


PARAM, NLAFILE

Parameter Values Description

NLAFILE <YES, NO> This parameter controls the output of animation files (A-File)
Default = NO in geometric nonlinear analysis.

If YES, the animation files are retained after geometric


nonlinear analysis;

If NO, the animation files are removed after geometric


nonlinear analysis.

1628 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, NLFAT

Parameter Values Description

NLFAT <YES, NO> PARAM, NLFAT, YES, forces OptiStruct to run models in which
Default = NO fatigue solutions (using the FATLOAD entry) reference
nonlinear quasi-static analysis (NLSTAT) subcases.
Defaults:
PARAM, NLFAT, NO, does not allow NLSTAT subcases to be
1. If this referenced by the FATLOAD data entry and the solution
parameter errors out if such models are run.
does not
exist in the Note:
deck, the
default PARAM, NLFAT, YES can be introduced to force OptiStruct to
behavior is run fatigue analysis based on a nonlinear subcase
NO. (ANALYSIS=NLSTAT). Nonlinear analysis results are not
recommended for use in a fatigue analysis because
2. If this nonlinear stresses and strains cannot be scaled and
parameter superimposed, however, acceptable results may be generated
exists in the in the following cases:
deck,
however, no During a nonlinear run (ANALYSIS=NLSTAT),
value (YES/ acceptable results may be generated if a model uses
NO) is elasto-plastic material and NEUBER correction is turned
specified, OFF (Plasticity field on FATPARM bulk data entry). This
then the statement is based on the assumption that nonlinear
default analysis is run until shakedown is achieved. If strain
behavior is results from the nonlinear analysis are used prior to
NO. shakedown, the fatigue results will most likely be
incorrect since the magnitude of plastic strain may not
be close to the steady state strain value.
Additionally, acceptable results may be generated if
contact based nonlinearity exists in the model
(ANALYSIS=NLSTAT) and the contact area is not
expected to change appreciably as the load increases
(for example, surfaces that match from the beginning).
In both cases, the Scale and Offset fields on the FATLOAD
entry should be left blank as the stresses and strains cannot
be scaled and superimposed.

Regardless of the model type, fatigue results based on


nonlinear results using PARAM, NLFAT, YES should always be
interpreted with caution.

Altair Engineering OptiStruct 13.0 Reference Guide 1629

Proprietary Information of Altair Engineering


PARAM, NLRFILE

Parameter Values Description

NLRFILE <YES, NO> This parameter controls the output of restart files (R-File) in
Default = NO geometric nonlinear analysis.

If YES, the restart files are retained after geometric


nonlinear analysis;

If NO, the restart files are removed after geometric


nonlinear analysis.

1630 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, NLRUN

Parameter Values Description

NLRUN <YES, NO> The parameter controls if geometric nonlinear analysis


Default = YES subcases run automatically after these subcases in bulk
format are converted into block format.

If YES, geometric nonlinear analysis subcases run


automatically after conversion.

If NO, geometric nonlinear analysis subcases do not run


automatically after conversion.

Altair Engineering OptiStruct 13.0 Reference Guide 1631

Proprietary Information of Altair Engineering


PARAM, NPRBAR

Parameter Values Description

NPRBAR <INTEGER> Controls the number of the output INFORMATION #741 for
Default = 3 RBAR elements.

Example of INFORMATION #741,

*** INFORMATION # 741


No need to constrain the rotational dof of this dependent
grid.
RBAR element id = 20436260
independent grid id = 20374048
dependent grid id = 20367448
This is because there isn't any stiffness and load on the
rotational dof of the dependent grid.

1632 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, NPRBE2

Parameter Values Description

NPRBE2 <INTEGER> Controls the number of the output INFORMATION #741 for
Default = 3 RBE2 elements.

Example of INFORMATION #741,

*** INFORMATION # 741


No need to constrain the rotational dof of this dependent
grid.
RBE2 element id = 20436260
independent grid id = 20374048
dependent grid id = 20367448
This is because there isn't any stiffness and load on the
rotational dof of the dependent grid.

Altair Engineering OptiStruct 13.0 Reference Guide 1633

Proprietary Information of Altair Engineering


PARAM, NPRGDE

Parameter Values Description

NPRGDE <INTEGER> Controls the number of the output INFORMATION #742.


Default = 3
Example of INFORMATION #742,

*** INFORMATION # 742


The dependent rotational dof of this rigid element is
removed.
RBE2 element id = 20436262
independent grid id = 20374050
a dependent grid id = 20367345
This is because there is no need to constrain the rotational
dof of any of the dependent grids.

1634 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, NUMEG

Parameter Values Description

NUMEG <Integer> When ND on the EIGRL/EIGRA data is blank, the disk space
1000 estimate in the .out file for modal frequency response and
the transient analysis is based on the number of modes
specified by PARAM,NUMEG. When Lanczos is used, the disk
space estimate is based on this value plus the number of the
potential residual vectors. When AMLS/AMSES is used, the
disk space estimate is based only on the value of
PARAM,NUMEG. In this case, it is assumed that
PARAM,NUMEG includes the number of potential residual
vectors.

Altair Engineering OptiStruct 13.0 Reference Guide 1635

Proprietary Information of Altair Engineering


PARAM, OGEOM

Parameter Values Description

OGEOM <YES, NO> PARAM, OGEOM controls the output of model (geometry)
Default = YES data to the .op2 file. This functionality is also
controlled by the MODEL/NOMODEL option on the
OUTPUT, OP2 I/O option, but this parameter setting will
override the OUTPUT, OP2 setting.

PARAM, OGEOM, YES will output model data to the .op2


file.

PARAM, OGEOM, NO will not output model data to the


.op2 file.

1636 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, OMACHPR

Parameter Values Description

OMACHPR <YES, NO> PARAM, OMACHPR controls the Nastran version for some
Default = NO OP2 datablocks.

YES means that the new Nastran version should be used.

NO means that the old Nastran version should be used.

Altair Engineering OptiStruct 13.0 Reference Guide 1637

Proprietary Information of Altair Engineering


PARAM, OMID

Parameter Values Description

OMID <YES, NO> Controls the coordinate system used by shell and
Default = YES membrane elements for stress and strain results.

This affects the recovery of optimization responses as


well as results output to the HM, PUNCH, and OPTI
output formats.

Stress and strain results are always output to OUTPUT2


and H3D output formats with reference to the elemental
system.

YES indicates that shell and membrane stresses/strains


are with reference to the material coordinate system, as
defined by the MID/THETA field of the element card.

NO indicates that shell and membrane stresses/strains are


with reference to the elemental coordinate system,
regardless of what is defined on the MID/THETA field of
the element card.

1638 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, OP2GM34

Parameter Values Description

OP2GM34 <TRUE, FALSE> PARAM, OP2GM34 controls the output of GEOM3 and
Default = TRUE GEOM4 data blocks to the .op2 file if PARAM, POST, -1 is
specified.

PARAM, OP2GM34, TRUE will output GEOM3 and GEOM4


data blocks to the .op2 file if PARAM, POST, -1 is
specified.

PARAM, OP2GM34, FALSE will not output GEOM3 and


GEOM4 data blocks to the .op2 file.

Altair Engineering OptiStruct 13.0 Reference Guide 1639

Proprietary Information of Altair Engineering


PARAM, PLIGEXT

Parameter Values Description

PLIGEXT <YES, NO> This parameter is used to print the applied load vector in
Default = NO DMIG form to the .pligext file. The DMIG NAME is
PLIGEXT.

To generate the .pligext file the oload(opti)=all


command must also be requested.

1640 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, POST

Parameter Values Description

POST <0, -1, -2, -5> Adding PARAM, POST to the bulk data section of the
Default = 0 input deck will activate the creation of the .op2 file.

PARAM, POST, -1 will create the .op2 file with


displacement results output in the analysis system
and PARAM, ITAPE set to -1.

PARAM, POST, -2 will create the .op2 file with


displacement results output in the basic coordinate
system and PARAM, ITAPE set to 0. The GEOM3,
GPDT and GPL data blocks are also included in the
.op2 file when PARAM, POST, -2 is used.

PARAM, POST, -5 will write the stiffness and mass


matrices to the .k.op2 and the .m.op2 files,
respectively, in addition to creating the .op2 file with
displacement results output in the analysis system
and PARAM, ITAPE set to -1.

Altair Engineering OptiStruct 13.0 Reference Guide 1641

Proprietary Information of Altair Engineering


PARAM, POSTEXT

Parameter Values Description

POSTEXT YES, NO If PARAM,POSTEXT,YES, the modal complex stiffness matrix


Default = NO (KHH) and, if it exists, the modal viscous damping matrix
(BHH) are written to the .op2 file when frequency
response analysis is performed.

The modal complex stiffness matrix is:

Where G is the PARAM,G structural damping value and


[Kge] is the structural damping matrix based on the
structural damping values on the MATi data.

The modal viscous damping matrix is:

1642 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, PRESUBNL

Parameter Values Description

PRESUBNL YES, NO PARAM, PRESUBNL, YES forces OptiStruct to run models, in


which Linear Buckling Analysis or Preloaded Analysis is
Default = NO defined, in conjunction with nonlinear materials (MATS1,
MATHE, or MGASK) or large displacement nonlinear
Defaults:
analysis.
If this
PARAM, PRESUBNL, NO does not allow Linear Buckling
parameter
Analysis or Preloaded Analysis with nonlinear materials or
does not exist
large displacement nonlinear analysis to be defined and the
in the deck,
solution errors out if such models are run.
the default
behavior is NO. Note: Linear Buckling Analysis or Preloaded Analysis is not
recommended in models with nonlinear materials or
If this
large displacement nonlinear analysis. It is the user’s
parameter
responsibility to interpret such results with caution.
exists in the
deck,
however, no
value (YES/
NO) is
specified,
then the
default
behavior is NO.

Altair Engineering OptiStruct 13.0 Reference Guide 1643

Proprietary Information of Altair Engineering


PARAM, PRGPST

Parameter Values Description

PRGPST < YES, NO, ALL, PRGPST controls the printing of AUTOSPC information
NONE,< number of to the .out file.
DOFs> >
PARAM, PRGPST, YES
Default = YES
A maximum of 100 degrees of freedom (DOF) of
AUTOSPC data will be printed in the .out file.

PARAM, PRGPST, NO

No AUTOSPC data will be printed.


PARAM, PRGPST, NONE

Works exactly like PARAM, PRGPST, NO - No AUTOSPC


data will be printed.

PARAM, PRGPST, ALL

All AUTOSPC data will be printed in the .out file.

PARAM, PRGPST, <number of DOF>

A maximum of <number of DOF> degrees of freedom


(DOF) of AUTOSPC data will be printed in the .out file.

1644 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, PRINFACC

Parameter Values Description

PRINFACC <1, 0> If 1, the inertia relief rigid body forces and
accelerations are printed to the .out file.
Defaults
If 0, the inertia relief rigid body forces and
1. The default is
accelerations are NOT printed to the .out file.
0, when the
parameter is
not present in
the deck.

2. The default is
1, when
PARAM,
PRINFACC is
input without
specifying a
value.

Altair Engineering OptiStruct 13.0 Reference Guide 1645

Proprietary Information of Altair Engineering


PARAM, RBE2FREE

Parameter Values Description

RBE2FREE <YES, NO> Modeling errors can result in the creation of RBE2 elements
with rigid body rotations. This parameter can be used to
Default = NO convert ERROR 725 into WARNING 825 when singular RBE2
elements, with rotational rigid body modes in all three
directions, are present in the model.
YES

If PARAM, RBE2FREE, YES is specified, ERROR 725 is


converted into WARNING 825. For AMSES/AMLS SUBCASEs
the free rotational degrees of freedom are AUTOSPC’ed.
For static analysis and Lanczos eigenvalue analysis, the
run may fail due to singularities and ERROR 153 or 155 will
be issued.
NO

If PARAM, RBE2FREE, NO is specified, ERROR 725 is not


converted into WARNING 825 and models containing
singular RBE2 elements will error out.

Note:

To solve a problem with Lanczos or static analysis, AMSES


can used first to determine which RBE2 degrees of freedom
are AUTOSPC’ed. Single point constraints (SPC) can be
added to manually constrain such degrees of freedom in
subsequent static analysis or Lanczos eigenvalue analysis.

1646 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, RBE3FREE

Parameter Values Description

RBE3FREE <YES, NO> Modeling errors can result in the creation of RBE3 elements
with free spiders. This parameter can be used to convert
Default = NO ERROR 772 into WARNING 824 when free spiders on RBE3
elements are present in the model. These free spiders may
contain singular degrees of freedom.
YES

If PARAM, RBE3FREE, YES is specified, ERROR 772 is


converted into WARNING 824.

For AMSES/AMLS runs the free spiders will be AUTOSPC’ed


if they are singular. This will cause invalid results as the
RBE3 will be constrained to ground. Check the AUTOSPC
output to make sure the free spiders are not AUTOSPC’ed.

If the free spiders are singular, Lanczos eigenvalue


solutions and static analysis runs will fail with ERROR’s 155
or 153.
NO

If PARAM, RBE3FREE, NO is specified, ERROR 772 is not


converted into WARNING. Models containing RBE3 elements
with free spiders will error out.

Altair Engineering OptiStruct 13.0 Reference Guide 1647

Proprietary Information of Altair Engineering


PARAM, RBMEIG

Parameter Values Description

RBMEIG <REAL> PARAM, RBMEIG defines the cutoff eigenvalue for


Default = 1.0 determination of rigid body modes calculated by the AMLS
and AMSES eigensolvers.
Default
Note:
The default
cutoff 1. PARAM, RBMEIG functions in a similar manner to
eigenvalue PARAM, FZERO, which is used in models solved by the
(AMSES and Lanczos eigensolver.
AMLS) is 1.0, if 2. The default cutoff eigenvalue of 1.0 is equivalent to a
this parameter natural frequency of 0.16 Hz.
is not present
in the deck. 3. For the Lanczos eigensolver, use PARAM,FZERO to set
the cutoff frequency for rigid body modes.

1648 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, REANAL

Parameter Values Description

REANAL 0.0 < Real < 1.0 This parameter is for restart runs of topology
No default optimizations only.

Inclusion of this parameter on a restart run will cause


the last iteration to be reanalyzed without penalization.

If the value given is less than the value of MINDENS


(default = 0.01) used in the optimization, all elements
will be assigned the densities they had during the final
iteration of the optimization. As there is no
penalization, stiffness will now be proportional to
density.

If the value given is greater than the value of MINDENS,


those elements whose density is less than the given
value will have density equal to MINDENS, all others will
have a density of 1.0.

Altair Engineering OptiStruct 13.0 Reference Guide 1649

Proprietary Information of Altair Engineering


PARAM, RECOVER

Param Value Description


eter s

RECOVE <LB, <LB, UB>:


R UB>
They represent the Lower Bound (LB) and the Upper Bound (UB) of
the frequencies between which the full-structure mode shapes are
requested instead of the modes of the condensed system generated
during Component Mode Synthesis (CMS).

LB (real > 0.0, optional):

Mode shapes of the full-structure, at frequencies greater than “LB”,


will be output to the .op2 file.

UB (real > 0.0, mandatory):

Mode shapes of the full-structure, at frequencies lower than “UB”, will


be output to the .op2 file.

Note:

1. The following example implementations are incorrect and will


result in an ERROR:

PARAM, RECOVER, 30.0, 20.0 (as UB < LB)


PARAM, RECOVER, ,0.0 (as UB 0)

Defaults

1. The mode shapes of the condensed system (only) generated during CMS are output when
this parameter is not present in the deck.

2. If PARAM, RECOVER is input without specifying a value, the program results in an ERROR.

3. LB is optional and the default for LB is 0.0, if it is left blank.

1650 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, RENUMOK

Parameter Values Description

RENUMOK <YES, NO, If YES or BLANK, when the solid element grids are listed
BLANK> in the order that would make the element inside out,
Default = NO they are automatically re-ordered. In this way, running
(importing and exporting) the model through HyperMesh
to get the corrected element grid sequence can be
avoided.

If NO, when the element grids are input in reverse


order, they are not re-sequenced to the correct order.
OptiStruct will error out if such element grid ordering
exists.

Note:

1. If the element grids are input in a random order,


then PARAM, RENUMOK will not be able to correct
the sequence. OptiStruct will error out in such
cases.

2. If PARAM, RENUMOK is not specified (default), then


the default is NO. This is different from specifying
PARAM, RENUMOK and leaving the value field blank,
which implies YES.

3. If PARAM,RENUMOK is used and the .fem file is used


for the model information file in HyperView, then
corner stresses for the solid elements will be wrong
when the .h3d or .op2 files are used for the results
file. So, if PARAM,RENUMOK is used, HyperView
should use the .op2 or .h3d file for the model
information file.

Altair Engineering OptiStruct 13.0 Reference Guide 1651

Proprietary Information of Altair Engineering


PARAM, RFIOUT

Parameter Values Description

RFIOUT <YES, NO> This parameter controls the output of modal super
Default = NO element for use in the RecurDyn multibody dynamics
software from FunctionBay. This information is written
to the .rfi file. This should be used with CMSMETH
CBN and ASET DOF for the connection points.

If YES, the modal super element is output to the .rfi


file.

If NO, the .rfi file is not created.

Note:

This .rfi file can be created only by OptiStruct


executables running on 64-bit Windows machines. This
file cannot be created while using OptiStruct on Linux or
Mac OS X machines.

1652 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, RHOCP

Parameter Values Description

RHOCP Real > 0.0 The scale factor used to calculate ERP in decibels (dB).
Default = 1.0 The calculation is:

Altair Engineering OptiStruct 13.0 Reference Guide 1653

Proprietary Information of Altair Engineering


PARAM, RSPLICOR

Parameter Values Description

RSPLICOR 0, 1, REAL > 1.0 RSPLINE end rotation correction.


Default = 0
0: No correction

1: two RSPLINE ends have rotation correction

>1: Defines cut-off angle. Two RSPLINE ends have


rotation correction. If two consecutive RSPLINE
sections have an angle larger then the cut-off angle,
rotation correction is applied to the shared RESPLINE
node.

1654 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, SEP1XOVR

Parameter Values Description

SEP1XOVR 0, 16 The old and new location of moved shell grid points are
Default = 0 printed if SEP1XOVR = 16. When the RSSCON shell-to-
solid element connector is used. By default, the moved
shell grid points are not printed, SEP1XOVR = 0.

See the description of PARAM,TOLRSC for more details.

Altair Engineering OptiStruct 13.0 Reference Guide 1655

Proprietary Information of Altair Engineering


PARAM, SEPLOT

Parameter Values Description

SEPLOT <YES, NO> PARAM, SEPLOT can be used during CMS analysis (only
Default = YES with the CBN method) to create a .seplot file that
contains the ASET grid data as well as the GRID and
Defaults: PLOTEL data defined using the MODEL I/O Option. The
data is written to the .seplot file in OptiStruct.
The value of this
parameter is YES,
YES: The .seplot file is created.
if it is included in
the input file, but
NO: The .seplot file is not created.
no value is
provided.

The value of this


parameter is NO,
if it is not
included in input
file.

1656 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, SH4NRP

Parameter Values Description

SH4NRP 0, 1, 2 This parameter controls the full projection of 4-node shell


elements in NLGEOM implicit analysis.
Default = 0 in
NLGEOM If 0, the full projection for warped QEPH shell elements will
subcase be deactivated. This option may improve the implicit
nonlinear analysis with QEPH warped shell elements if the
Default = 1 in rigid rotation of warped elements is small enough.
IMPDYN
subcase If 1, the full projection for warped elements will be applied
only for internal force calculation; the option gives
accurate results if it converges successfully, but
convergence issue could be encountered with very warped
elements.

If 2, the full projection for warped QEPH shell elements will


be activated for the stiffness matrix to stay consistent
with the internal force calculation. This option can
improve the convergence of implicit nonlinear analysis with
QEPH warped shell elements at the cost of some additional
calculations.

In the case of finite rigid rotations with warped shell


elements, PARAM, SH4NRP, 1 gives accurate results. If
convergence difficulties are encountered, PARAM, SH4NRP,
2 should be used.

If PARAM SMDISP 1 is present, SH4NRP is always set as 0


internally.

Altair Engineering OptiStruct 13.0 Reference Guide 1657

Proprietary Information of Altair Engineering


PARAM, SHELOS11

Parameter Values Description

SHELOS11 YES, NO YES can be used to restore the formulation used in version
11.0.240 and earlier for first-order shell elements (CQUAD4
Default = NO and CTRIA3).

Note: In Release 12.0 the first order shell elements have


been improved to:

Eliminate inaccuracies in transverse shear and


inter-laminar stress calculation that could occur for
cases with membrane-bending coupling, especially
composites.
Improve robustness and stability of buckling
formulation by changing the default order for plate
buckling to first order.

The behavior of shells from earlier releases can be


recovered using this parameter.

1658 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, SHL2MEM

Parameter Values Description

SHL2MEM <Real Number > A shell property (defined by the PSHELL bulk data
0.0> entry) is automatically converted into a membrane
property if the membrane thickness (field T) of the
No default
PSHELL bulk data entry is less than or equal to the
(see note 6) value specified using PARAM, SHL2MEM. This is done by
setting MID2 and MID3 to blank for the PSHELL.

Note:

1. With regard to determining the conversion from a


PSHELL shell to membrane property, the nodal
thicknesses defined using the Ti fields of the
CTRIA3/6 or the CQUAD4/8 bulk data entries are
ignored.

2. If the value of the field T in the referenced PSHELL


entry is less than or equal to the value of
PARAM,SHL2MEM then the shell property is
converted to a membrane property regardless of
the Ti field values.

3. PARAM, SHL2MEM should be used with caution in


optimization runs, as this parameter will also apply
to design properties. If the shell thickness on such
design properties (in PSHELL) is lower than the
value specified with PARAM, SHL2MEM, they will
automatically be converted to membrane properties
(regardless of the value of their corresponding
design variables).

4. If PARAM, SHL2MEM is used in optimization runs


with the shell thickness (T) of the PSHELL design
property equal to zero or blank, then the shell
property is automatically converted into a
membrane property.

5. PARAM, SHL2MEM is intended for use with ‘skin’


elements, which are useful for stress calculation on
the surface of solid (3D) elements.

6. Defaults:

If PARAM,SHL2MEM is input without specifying a


value, then the code will error out (no default).
If PARAM,SHL2MEM is not used, the conversion
from shell property to a membrane property will
not occur.

Altair Engineering OptiStruct 13.0 Reference Guide 1659

Proprietary Information of Altair Engineering


PARAM, SHPBCKOR

Parameter Values Description

SHPBCKOR 1, 2 PARAM,SHPBCKOR defines the type and order of


Default = 1 approximation used in plate bending geometric stiffness for
linear shell elements (CQUAD4 and CTRIA3).

1: First order approximation, expressed using displacement


degrees of freedom in the geometric stiffness matrix. It is
more numerically stable and includes both bending and
transverse shear contributions. Being first order, this
option may over-estimate buckling loads, especially when
the mesh is coarse relative to the buckling wavelength
(only a few elements per wave length).

2: Second order approximation, expressed using rotational


degrees of freedom in the geometric stiffness matrix. This
option ignores contributions of transverse shear to
buckling.

Note:
Second order approximation is appropriate and provides
better accuracy for buckling of thin shells, which is
dominated by bending.

For thick shells or for composites with soft cores (where


transverse shear contributions are significant), it is
advisable to use PARAM,SHPBCKOR,1, which captures both
bending and transverse shear effects. Since
PARAM,SHPBCKOR,1 is more numerically stable, it can also
help if there are difficulties in the eigensolver.

1660 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, SIMPACK

Parameter Values Description

SIMPACK 0, 1, 2, 3, 4 Requests generation of the SIMPACK .fbi file containing


Default = 0 flexible body information for SIMPACK analysis.

PARAM,SIMPACK,1
Writes CMS Matrices [k] and [m] to the SIMPACK
.fbi file.
Writes modes and eigenvectors of the SE to the
SIMPACK .fbi file.

PARAM,SIMPACK,2
This option writes out all the information specified in
PARAM, SIMPACK,1 (above) and additionally writes
model information to the SIMPACK .fbi file. See
Comment 2 about MODEL data.
PARAM,SIMPACK,3
This option writes out all the information specified in
PARAM, SIMPACK, 2 (above) to the SIMPACK .fbi
file and additionally includes the following:

Writes the Interior point recovery GRID SET to the


SIMPACK .fbi file.
Writes the Interior point recovery matrix to the to
the SIMPACK .fbi file.

PARAM,SIMPACK,4
This option writes out all the information specified in
PARAM, SIMPACK, 3 (above) to the SIMPACK .fbi
file and additionally includes the following:

Writes rotational forces to the SIMPACK .fbi file.

Comments

1. Refer to the SIMPACK section of “Coupling OptiStruct with Third Party Software” in the
User’s Guide for more information.

2. If PARAM, SIMPACK, 2 is specified, the MODEL I/O Options Entry does not have any effect
on the output. The entire model is written to the SIMPACK .fbi file.

Altair Engineering OptiStruct 13.0 Reference Guide 1661

Proprietary Information of Altair Engineering


PARAM, SMDISP

Parameter Values Description

SMDISP < 0, 1 > This parameter is used to specify that small displacement
Default = 0 formulation or large displacement formulation is used. It
affects Geometric Nonlinear Implicit Static Analysis
(ANALYSIS = NLGEOM) and Geometric Nonlinear Implicit
Dynamic Analysis (ANALYSIS = IMPDYN).

When large displacement effects are negligible, “PARAM,


SMDISP, 1” could be used to improve the convergence and
performance.

If 0, use large displacement formulation.

If 1, use small displacement formulation.

1662 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, SNAPTHRU

Parameter Values Description

SNAPTHRU YES, NO PARAM, SNAPTHRU controls the output of the force-


Default = NO deflection curve in geometric nonlinear analysis.

If YES, the converter will generate rigid bodies internally


and output the time history for rigid body forces in the
Time-History (TH) file. This is valid only when grids are
defined on XHIST bulk data entry with TYPE = GRID and
ENTRY=DEF simultaneously. The force-deflection curve
can be cross plotted with the grid displacements and
corresponding rigid body forces in HyperGraph.

If NO, output of the force-deflection curve is not


requested and the internal rigid bodies are not generated.

Altair Engineering OptiStruct 13.0 Reference Guide 1663

Proprietary Information of Altair Engineering


PARAM, SORTCON

Parameter Values Description

SORTCON <Integer> This parameter controls the output of violated constraints


Default = 20 to the .out file (and to screen).

By default, the 20 most violated constraints are printed in


a separate table and sorted by percentage violation. This
behavior can be modified with PARAM, SORTCON, N; where
N is the number of constraints to be printed. (N = 0
disables this feature).

1664 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, SPLC

Parameter Values Description

SPLC Real > 0.0 This parameter is used to specify the speed of sound used
Default = 1.0 in the wave number and the complex particle velocity
vector calculations, as shown below (see the Radiated
Sound Analysis section in the User’s Guide for further
information):

Wave Number

The wave number k is defined as follows:


2 f
k
c
Where,
c is the speed of sound defined by PARAM, SPLC.
f is the frequency of the sound wave in the medium.

Complex Particle Velocity Vector

The complex particle velocity vector is defined for each


frequency as follows:
uuur ˆ
pj ( f ) X j i
( pv) j ( f ) 1
c krj

Where,

pj ( f )
is the complex acoustic pressure due to source grid
j at the microphone location.

X̂ j
is the unit vector from the source grid j to the
microphone grid
r r
Xj Xj
X̂ j r
Xj rj
(see Figure 1)

is the density of the acoustic medium defined by


PARAM, SPLRHO.

c is the speed of sound defined by PARAM, SPLC.


k is the wave number defined above under Wave Number.

rj
is the distance from the acoustic source grid j on the

Altair Engineering OptiStruct 13.0 Reference Guide 1665

Proprietary Information of Altair Engineering


Parameter Values Description

panel to the microphone grid (see Figure 1).

i is the square root of -1


Note:

1. This parameter is used to specify the speed of sound


used in Radiated Sound Analysis. The same value is
used in the Equivalent Radiated Power (ERP)
calculations (See PARAM, ERPC).

2. If both PARAM, SPLC and PARAM, ERPC are specified in


the same input deck, then the last instance
dominates.

1666 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, SPLFAC

Parameter Values Description

SPLFAC Real > 0.0 This parameter specifies the scale factor (q ) used to
Default = 1.0 calculate the Sound Pressure Level in Radiated Sound
Analysis. The equation used for the calculation is:

Sound Pressure

Total Complex Acoustic Sound Pressure requested by SPL


is:
np
f q ikr j
ptotal f V flux f ie
j 1 rj j

Where,
f is the frequency of the sound wave in the medium.
is the density of the acoustic medium defined by
PARAM, SPLRHO.
rj
is the distance from the acoustic source grid j on the
panel to the microphone location grid (see Figure 1).

V flux f
j
is the velocity flux of the source grid j .

k is the wave number as defined in Wave Number.


i is the square root of -1
np is the number of source grids (see Figure 1).
q is the value of the scale factor specified using the
parameter PARAM, SPLFAC.

Altair Engineering OptiStruct 13.0 Reference Guide 1667

Proprietary Information of Altair Engineering


PARAM, SPLREFDB

Parameter Values Description

SPLREFDB Real > 0.0 This parameter can be used to specify the reference sound
Default = 1.0 pressure value used to calculate the Sound Pressure Level
(SPL) in decibels (dB).

Note:

The Sound Pressure Level (SPL) in decibels can be


calculated using the following equation:
SPL
SPLdB 20.0 * log10 ( )
SPLREFDB
Where,
SPLdB
is the Sound Pressure Level in decibels.
SPL
is the magnitude of the acoustic sound pressure
specified in the Radiated Sound Analysis section of the
User’s Guide.
SPLREFDB is the reference sound pressure value specified
using this parameter.

1668 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, SPLRHO

Parameter Values Description

SPLRHO Real > 0.0 This parameter is used to specify the density of the
Default = 1.0 acoustic medium in the calculation of the complex acoustic
sound pressure and the complex particle velocity vector,
as shown below (see the Radiated Sound Analysis section
of the User’s Guide for further information):

Sound Pressure Level

Total Complex Acoustic Sound Pressure requested by SPL


is:
np
f q ikr j
ptotal f V flux f ie
j 1 rj j

Where,

f is the frequency of the sound wave in the medium.

is the density of the acoustic medium defined by


PARAM, SPLRHO.

rj
is the distance from the acoustic source grid j on the
panel to the microphone location grid (see Figure 1).

V flux f
j
is the velocity flux of the source grid j .

k is the wave number as defined in Wave Number.


i is the square root of -1
np is the number of source grids (see Figure 1).
q is the value of the scale factor specified using the
parameter PARAM, SPLFAC.

Complex Particle Velocity Vector

The complex particle velocity vector is defined for each


frequency as follows:
uuur ˆ
pj ( f ) X j i
( pv) j ( f ) 1
c krj

Where,

pj ( f )
is the complex acoustic pressure due to source

Altair Engineering OptiStruct 13.0 Reference Guide 1669

Proprietary Information of Altair Engineering


Parameter Values Description

grid j at the microphone location.

X̂ j
is the unit vector from the source grid j to the
microphone grid
r r
Xj Xj
X̂ j r
Xj rj
(see Figure 1)

is the density of the acoustic medium defined by


PARAM, SPLRHO.

c is the speed of sound defined by PARAM, SPLC.


k is the wave number defined above under Wave Number.

rj
is the distance from the acoustic source grid j on the
panel to the microphone grid (see Figure 1).

i is the square root of -1


Note:

1. This parameter is used to specify the acoustic medium


density used in Radiated Sound Analysis. The same
value is used in the Equivalent Radiated Power (ERP)
calculations (See PARAM, ERPRHO).

2. If both PARAM, SPLRHO and PARAM, ERPRHO are


specified in the same input deck, then the last
instance dominates.

1670 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, SRCOMPS

Parameter Values Description

SRCOMPS <YES, NO> If YES, the strength ratios are output for composite
Default = NO elements that have failure indices requested. (The
Output formats currently supported are: H3D, HM, OP2,
PCH and OPT)

If NO or blank, the strength ratio will not be output.

Note:

The Strength Ratios that are output as a result of


PARAM, SRCOMPS, YES depend on the Failure Theory
specified by the user. The following equations show the
relationship between the Failure Index and the Strength
Ratio for different Failure Theories.

Hill Failure Theory:

1
Strength Ratio
Failure Index

Hoffman Failure Theory: There is no direct relationship


between the Strength Ratio and Failure Index. (refer to
the Composite Laminates section of the User’s Guide for
more information).

Tsai-Wu Failure Theory: There is no direct relationship


between the Strength Ratio and Failure Index. (refer to
the Composite Laminates section of the User’s Guide for
more information).

Maximum Stress (Strain) Failure Theory:

1
Strength Ratio
Failure Index

For the Transverse Shear Failure Theory:

1
Strength Ratio
Failure Index

Altair Engineering OptiStruct 13.0 Reference Guide 1671

Proprietary Information of Altair Engineering


PARAM, SS2GCR

Parameter Values Description

SS2GCR <REAL> PARAM, SS2GCR is used to control the accuracy of the


Default = 5.0 AMLS solution.

Refer to the User’s Guide section, Using the AMLS


(Automatic Multi-Level Sub-structuring) Eigensolver for
more details.

1672 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, STRTHR

Parameter Values Description

STRTHR This parameter can be used to specify the von Mises


Default = 0.0 stress threshold above which the stress results are output
for a model.

Note

1. PARAM, STRTHR applies to all static subcases defined


within a model. The stress results for a particular
element are not output ONLY if its von Mises stress
value falls below STRTHR for ALL static subcases.

For example, if the von Mises stress results for


elements ID=1 and ID=2 fall below the threshold for
subcase 1, but are above the threshold for subcase 2;
then the stress results for both elements (ID=1 and
ID=2) are output for both subcases.

2. PARAM, STRTHR applies to stress results output in all


active formats.

3. PARAM, STRTHR is supported for static analysis only.

4. If PARAM, STRTHR is defined in a model, then 1D


element stresses are not output, regardless of their
stress level or the specified threshold.

Altair Engineering OptiStruct 13.0 Reference Guide 1673

Proprietary Information of Altair Engineering


PARAM, THCNTPEN

Parameter Values Description

THCNTPEN AUTO, LOW, PARAM, THCNTPEN controls the penalty factor used in
HIGH thermal contact analysis.
Default = AUTO
AUTO:
Determines the value of conductivity for each contact/
gap element based on the conductivity of surrounding
elements.

LOW:
Imposes a lower penalty factor that reduces the
conductivity of each contact/gap element compared to
the conductivities of the surrounding elements. It can be
used when the program runs into convergence
difficulties.

HIGH:
Imposes a higher penalty factor that increases the
conductivity of each contact/gap element compared to
the conductivities of the surrounding elements. It can be
used to enforce stronger conduction.

Note:

1. Theoretically, while higher conductivity values


enforce a perfect conductor, excessively high values
may result in poor conditioning of the conductivity
matrix. In such cases, it may be beneficial to reduce
the value of conductivity, or use conductivity based
contact clearance and pressure.

2. This parameter influences the KC field of the


PCONTHT bulk data entry and the KAHT field of the
PGAPHT bulk data entry.

1674 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, TOLRSC

Parameter Values Description

TOLRSC Real When the RSSCON shell-to-solid element connector is


Default = 0.05 used, the connecting grid points of the shell element
are moved onto the solid face if the grid points are
close enough. The tolerable distance of the shell grid
point to the solid edge or face is where h is the
height of the solid edge. Rigid body invariance is
satisfied with double-precision accuracy if the shell grid
points are adjusted.

Altair Engineering OptiStruct 13.0 Reference Guide 1675

Proprietary Information of Altair Engineering


PARAM, TRAKMETH

Parameter Values Description

TRAKMETH <0, 1, 2> TRAKMETH is a parameter that can be used to select


the criterion employed for mode tracking.
Default = 0
There are three tracking criteria available for selection
Defaults: in the current implementation:

-The value of Mass cross-orthogonality check (CORC)


this parameter is
Modal assurance criterion (MAC)
0 if it is not
included in input Modal assurance criterion square root (MACSR).
file.
If TRAKMETH = 0
-If this parameter
is included in the The Mass cross-orthogonality check (CORC) criterion is
input file, but no used for mode tracking. This performs a mass
value is provided, orthogonality check of the current and previous
eigenvectors after reanalysis. CORC is implemented as
then running the
follows:
program will
result in an error.
If TRAKMETH = 1

The Modal assurance criterion square root (MACSR)


criterion is used for mode tracking. This criterion
essentially calculates the dot product of the two unit
vectors associated with the current and previous
eigenvectors. MACSR is implemented as follows:

If TRAKMETH = 2

The standard modal assurance criterion (MAC) is used


for mode tracking. MAC is implemented as follows:

Where,
is the current eigenvector.
is the previous eigenvector.
is the mass matrix.

1676 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, TRAKMTX

Parameter Values Description

TRAKMTX <0, 1> TRAKMTX is a parameter that controls the output of the
Default = 0 mode tracking matrix during optimization.

Defaults: If TRAKMTX = 1
The mode tracking matrix will be printed to the output file
-The value of this at each iteration.
parameter is 0 if
it is not included If TRAKMTX = 0
in input file. The mode tracking matrix will not be printed to the
output file.
-If this parameter
is included in the Note:
input file, but no Each element of the mode tracking matrix stores the
value is provided, correlation value of two eigenvectors which is calculated
then running the using certain mode tracking criteria (see PARAM,
program will result TRAKMETH).
in an error.
Example

The following is an example of the mode tracking matrix.


For this example, assume that:

1. The first 5 modes are being tracked.

2. 10 modes are calculated for each analysis

3. PARAM, MFILTER is set to 0.7.

Mode Tracking Matrix

Based on the above matrix, mode 1 (of the previous


iteration) will get tracked to mode 1 (of current
iteration). Mode 2 will get tracked to mode 2. Mode 3 will
get tracked to mode 4. Mode 4 will get tracked to mode
3. And mode 5 could not be tracked to any of the 10
modes in the current iteration (out of bounds).

Altair Engineering OptiStruct 13.0 Reference Guide 1677

Proprietary Information of Altair Engineering


PARAM, TPS

Parameter Values Description

TPS <YES, NO> PARAM, TPS may be used with transient response
Default = YES analysis. When only shell stress results are required from
a transient response analysis, significant speed
improvements in run time can be obtained with the use of
this parameter.

YES: fast transient response analysis is activated – only


shell stress results output may be requested in this case.
that is, no displacement results are output.

NO: normal transient response analysis is performed.

1678 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, UCORD

Parameter Values Description

UCORD <CID> If = -1, the mass moment of inertia is calculated about the
center of gravity and is output in the basic coordinate
system.
Default = -1 If = 0, the mass moment of inertia is calculated about the
origin of the basic coordinate system. The output values
are expressed in the basic coordinate system.

the center of gravity coordinates are expressed in


the coordinate system CID. The mass moment of inertia is
calculated about the center of gravity and expressed in
the coordinate system CID.

Note:

1. If PARAM, UCORD is not specified, CID = -1, or CID


given is not found, all values in PARAM, GRDPNT are
calculated relative to the basic coordinate system.

2. If PARAM, GRDPNT is not specified in the input deck,


then the center of gravity and moment of inertia are
not output regardless of the value of PARAM, UCORD.

Altair Engineering OptiStruct 13.0 Reference Guide 1679

Proprietary Information of Altair Engineering


PARAM, VMOPT

Parameter Values Description

VMOPT <Integer = 0, 1, If PARAM,VMOPT is set to 0 or 1, then the virtual mass


2> of the fluid is included in the mass matrix for all
Default = 0 calculations. This can increase the calculation time
because of the dense mass matrix on the damp surface
of the structure.

If “PARAM,VMOPT,2” is specified, the eigenvalue solution


is performed without adding the mass contribution from
MFLUID, so that dry modes are calculated. A second
eigenvalue analysis is performed to get the damp modes,
which are used in modal dynamic solution. This solution
is much faster with only a slight loss of accuracy.

Note: Dry mode output in the .out file is available only


when PARAM,VMOPT,2 is specified.

1680 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, W3

Parameter Values Description

W3 <Real> Used in transient analyses to convert structural damping to


Default = 0.0 equivalent viscous damping.

The damping matrix [B] for transient analysis is assembled


from:

where:

is the contribution from damping elements (CDAMP#,


CVSIC) and B2GG.

is the overall structural damping coefficient (PARAM,


G).

is the frequency of interest in radians per unit time


(PARAM, W3) for the conversion of overall structural
damping into equivalent viscous damping.

[K] is the global stiffness matrix.

is the element structural damping coefficient (GE on


the MAT# entry).

is the frequency of interest in radians per unit time


(PARAM, W4) for the conversion of element structural
damping into equivalent viscous damping.

is the element stiffness matrix.

Altair Engineering OptiStruct 13.0 Reference Guide 1681

Proprietary Information of Altair Engineering


PARAM, W4

Parameter Values Description

W4 <Real> Used in transient analyses to convert structural damping to


Default = 0.0 equivalent viscous damping.

The damping matrix [B] for transient analysis is assembled


from:

where:

is the contribution from damping elements (CDAMP#,


CVSIC) and B2GG.

is the overall structural damping coefficient (PARAM,


G).

is the frequency of interest in radians per unit time


(PARAM, W3) for the conversion of overall structural
damping into equivalent viscous damping.

[K] is the global stiffness matrix.

is the element structural damping coefficient (GE on


the MAT# entry).

is the frequency of interest in radians per unit time


(PARAM, W4) for the conversion of element structural
damping into equivalent viscous damping.

is the element stiffness matrix.

1682 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, WR3

Parameter Values Description

WR3 <Real> This parameter is used to include or exclude frequency


Default = 0.0 dependent damping in rotor dynamics analysis.
PARAM, WR3, <Real>

If any real value except 0.0 (default) is specified, then it


is included in the rotor dynamics equation as the
“average” excitation frequency. PARAM, WR3, <Real>
should be specified to activate frequency dependent
damping if PARAM, GYROAVG is set to -1.

PARAM, WR3, 0

If 0.0 is specified, then frequency dependent damping


terms are not included in rotor dynamics analysis.

Refer to the User’s Guide section, Rotor Dynamics for more


details.

Altair Engineering OptiStruct 13.0 Reference Guide 1683

Proprietary Information of Altair Engineering


PARAM, WR4

Parameter Values Description

WR4 <Real> This parameter is used to include or exclude frequency


Default = 0.0 dependent damping in rotor dynamics analysis.
PARAM, WR4, <Real>

If any real value except 0.0 (default) is specified, then it


is included in the rotor dynamics equation as the
“average” excitation frequency. PARAM, WR4, <Real>
should be specified to activate frequency dependent
damping if PARAM, GYROAVG is set to -1.

PARAM, WR4, 0

If 0.0 is specified, then frequency dependent damping


terms are not included in rotor dynamics analysis.

Refer to the User’s Guide section, Rotor Dynamics for more


details.

1684 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, WTMASS

Parameter Values Description

WTMASS Real > 0.0 The WTMASS (Weight-To-MASS) parameter is used as a


Default = 1.0 multiplier for the terms of the structural mass matrix.

Note

PARAM, WTMASS cannot be applied to superelements


(.h3d or .pch) that are read into the model. If the unit of
mass is incorrect on the MAT# entries and PARAM,
WTMASS is required to update the structural mass
matrix; then this should be done in the creation run.

Altair Engineering OptiStruct 13.0 Reference Guide 1685

Proprietary Information of Altair Engineering


PAXI

Bulk Data Entry

PAXI – Axisymmetric Element Property

Description

Defines the properties of axisymmetric elements. Referenced by CTAXI entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PAXI PID MID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PAXI 2 203

Field Contents

PID Unique axisymmetric element property identification number.

No default (Integer > 0)

MID Identification number of a MAT1 or MAT3 entry.

No default (Integer > 0)

Comments

1. All axisymmetric element property entries must have unique ID numbers.

2. This card is represented as a property in HyperMesh.

1686 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PBAR

Bulk Data Entry

PBAR – Simple Beam Property

Description

The PBAR bulk data entry defines the properties of a simple beam (bar), which is used to
create bar elements via the CBAR entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBAR PID MID A I1 I2 J NSM

C1 C2 D1 D2 E1 E2 F1 F2

K1 K2 I12

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBAR 39 6 2.9 8.4 5.97 1.1

2.0 4.0

Field Contents

PID Unique simple beam property identification number.

No default (Integer > 0)

MID Material identification number. See comment 1.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1687

Proprietary Information of Altair Engineering


Field Contents

A Area of bar cross-section.

No default (Real > 0.0)

I1 Area moment inertia in plane 1 about the neutral axis.

No default (Real > 0.0)

I2 Area moment inertia in plane 2 about the neutral axis.

No default (Real > 0.0)

I12 Area product of inertia.

Default = 0.0 (Real) ( )

J Torsional constant.

Default = 0.0 (Real > 0.0)

NSM Nonstructural mass per unit length.

Default = 0.0 (Real)

K1, K2 Area factor for shear.

Default = 0.0 (Real)

Ci, Di, Stress recovery coefficients.


Ei, Fi
Default = 0.0 (Real)

Comments

1. For structural problems, MID may reference only a MAT1 material entry. For heat transfer
problems, MID may reference only a MAT4 material entry.

2. The transverse shear stiffness in planes 1 and 2 are (K1)AG and (K2)AG, respectively.
The default values for K1 and K2 are infinite; in other words, the transverse shear

used for K1 and K2, the transverse shear flexibilities are set to 0.0 (K1 and K2 are
interpreted as infinite).

1688 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. The stress recovery coefficients C1 and C2, and so on, are the y and z coordinates in the
BAR element coordinate system of a point at which stresses are computed. Stresses are
computed at both ends of the BAR.

Fig 1: C oordinate System for Bar Element (PBAR).

4. The moments of inertia are defined as follows:

5. This card is represented as a property in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1689

Proprietary Information of Altair Engineering


PBARL

Bulk Data Entry

PBARL – Simple Beam Property

Description

Defines the properties of a simple beam (bar) by cross-sectional dimensions, which is used to
create bar elements via the CBAR entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBARL PID MID GROUP TYPE/ ND


NAME

DIM1 DIM2 DIM3 DIM4 DIM5 DIM6 DIM7 DIM8

DIM9 … NSM

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBARL 12 7 BOX

10. 6. .5 .5

Field Contents

PID Unique simple beam property identification number.

No default (Integer > 0)

MID Material identification number. See comment 1.

No default (Integer > 0)

1690 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

GROUP Indicates if an arbitrary beam section definition is to be used. Refer to


Arbitrary Beam Section Definition in the User’s Guide. If the value of this field is
HYPRBEAM, the following field is NAME; otherwise it is TYPE.

Default = blank (blank or HYPRBEAM)

TYPE Cross-section type. When GROUP field is blank, this field is TYPE.

No default ("BAR", "BOX", "BOX1", "CHAN", "CHAN1", "CHAN2", "CROSS", "H",


"HAT", "I", "I1", "ROD", "T", "T1", "T2", "TUBE", "Z")

NAME Name of arbitrary beam section definition. Refer to Arbitrary Beam Section
Definition in the User’s Guide. When the value of GROUP is HYPRBEAM, this field
is NAME.

No default (Character string)

ND Number of dimensions used to specify the Cross-section shape. This is required


when the value of the GROUP field is HYPRBEAM. ND represents the total number
of dimensions used to define an Arbitrary Beam Section.

Default = blank

DIMi Cross-sectional dimensions.

No default (Real > 0.0)

NSM Nonstructural mass per unit length. NSM is specified after the last DIMi.

Default 0.0 (Real)

Comments

1. For structural problems, MID may reference only a MAT1 material entry. For heat transfer
problems, MID may reference only a MAT4 material entry.

2. The cross-sectional properties, shear flexibility factors, and stress recovery points (C, D,
E, and F) are computed using the TYPE and DIMi as shown below. The origin of the
element coordinate system is centered at the shear center of the cross-section oriented
as shown. The PBARL does not account for offsets between the neutral axis and the
shear center. Therefore, the CHAN cross-sections may produce incorrect results. The
PBEAML entry is recommended.

Altair Engineering OptiStruct 13.0 Reference Guide 1691

Proprietary Information of Altair Engineering


Type = BAR Type = BOX

Type = BOX1 Type = CHAN

1692 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Type = CHAN1 Type = CHAN2

Type = CROSS Type = H

Altair Engineering OptiStruct 13.0 Reference Guide 1693

Proprietary Information of Altair Engineering


Type = HAT Type = I

Type = I1 Type = ROD

1694 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Type = T Type = T1

Type = T2 Type = TUBE

Altair Engineering OptiStruct 13.0 Reference Guide 1695

Proprietary Information of Altair Engineering


Type = Z

3. This card is represented as a property in HyperMesh.

1696 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PBARX

Bulk Data Entry

PBARX – Optional BAR Property Extension for Geometric Nonlinear Analysis

Description

Defines additional BAR properties for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBARX PID ISMSTR ISTRAIN DM DB

Field Contents

PID Property identification number of the associated PBAR or PBARL card. See
comment 1.

No default (Integer > 0)

ISMSTR Flag for small strain formulation.

Default = 2 (Integer = 1, 2)

1 - Small strain from time =0

2 - Full geometric nonlinearity

ISTRAIN Flag for shear in beam formulation.

Default = ON (ON or OFF)

DM Beam membrane damping.

Default = 0.0 (Real > 0)

DB Beam bending damping.

Default = 0.01 (Real > 0)

Comments

1. The property identification number must be that of an existing PBAR bulk data entry. Only
one PBARX property extension can be associated with a particular PBAR.

Altair Engineering OptiStruct 13.0 Reference Guide 1697

Proprietary Information of Altair Engineering


2. PBARX is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. If the small strain option is activated (ISMSTR = 1), the strain and stress are engineering
strain and stress; otherwise they are true strain and stress.

4. This card is represented as an extension to a PBAR property in HyperMesh.

1698 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PBEAM

Bulk Data Entry

PBEAM – Beam Property

Description

The PBEAM bulk data entry defines the properties of beam elements defined via the CBEAM
entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBEAM PID MID A(A) I1(A) I2(A) I12(A) J(A) NSM(A)

C 1(A) C 2(A) D1(A) D2(A) E1(A) E2(A) F1(A) F2(A)

The following two continuation lines may be repeated up to ten times. They are used to
define stations along the beam element.

SO X/XB A I1 I2 I12 J NSM

C1 C2 D1 D2 E1 E2 F1 F2

The last two continuation lines are:

K1 K2 NSIA NSIB

M1A M2A M1B M2B N1A N2A N1B N2B

Altair Engineering OptiStruct 13.0 Reference Guide 1699

Proprietary Information of Altair Engineering


Fig 1: Beam Element C oordinate System (for PBEAM entry)

Example 1

This example represents a straight beam with stress recovery, only at end A.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBEAM 9 7 9.5 18.073 98.792 0.813

0.0 2.0 0.0 -2.0

NO 1.0

2.1

0.5

Example 2

This example represents a tapered beam with an intermediate section defined halfway
along its length and stress recovery at both end A and end B.

1700 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Note that the blank line after YES is entered for Stress Output (SO) at end B.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBEAM 9 7 9.5 18.073 98.792 0.813

0.0 2.0 0.0 -2.0

NO 0.5 6.5 5.385 35.542 0.563

YES 1.0 3.5 0.698 7.292 0.313

2.1

0.5

Field Contents

PID Property identification number.

No default (Integer > 0)

MID Material identification number. See comment 1.

No default (Integer > 0)

A(A) Area of beam cross-section at end A.

No default (Real > 0.0)

I1(A) Area moment inertia in plane 1 about the neutral axis at end A.

No default (Real > 0.0)

I2(A) Area moment inertia in plane 2 about the neutral axis at end A.

No default (Real > 0.0)

I12(A) Area product inertia at end A ( ).

Default = 0.0 (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 1701

Proprietary Information of Altair Engineering


Field Contents

J(A) Torsional stiffness parameter at end A.

Default = 0.0 (Real > 0.0)

NSM(A) Nonstructural mass per unit length at end A.

Default = 0.0 (Real)

Ci(A), Di(A), The y and z locations in element coordinates for stress data recovery at
Ei(A), Fi(A) end A. (i=1 is y and i=2 is z)

Default = 0.0 for all entries (Real)

SO Stress output request option for intermediate stations and end B. See
comments 5 through 8.

If set to NO, the following continuation line (containing fields C1 through


F2) must be omitted for that intermediate station, and no stresses are
recovered for that intermediate station.

If set to YESA, the following continuation line (containing fields C1


through F2) must be omitted for that intermediate station, and stresses,
for that intermediate station, are recovered at the stress recovery
locations identified for end A.

If set to YES, the following continuation line (containing fields C1 through


F2) must contain the same stress recovery locations as the first
continuation line (containing fields C1(A) through F2(A)) or must be
entirely blank.

Default = YES (YES, YESA, or NO)

X/XB Fractional distance of the intermediate station from end A.

Default = 1.0 (Real > 0.0)

A Area of beam cross-section for intermediate stations.

Default = A(A) (Real > 0.0)

I1 Area moment inertia in plane 1 about the neutral axis for intermediate
stations.

Default = I1(A) (Real > 0.0)

1702 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

I2 Area moment inertia in plane 2 about the neutral axis for intermediate
stations.

Default = I2(A) (Real > 0.0)

I12 Area product inertia for intermediate stations ( ).

Default = I12(A) (Real)

J Torsional stiffness parameter for intermediate stations.

Default = J(A) (Real > 0.0)

NSM Nonstructural mass per unit length for intermediate stations.

Default = NSM(A) (Real)

Ci, Di, Ei, Fi The y and z locations in element coordinates for stress data recovery for
intermediate stations. (i=1 is y and i=2 is z). See comments 5 through 8.

Default = 0.0 for all entries. (Real)

K1,K2 Shear stiffness factor K in K*A*G for plane 1 and plane 2.

Default = 1.0 for both (Real)

NSIA Nonstructural mass moment of inertia per unit length about nonstructural
mass center of gravity at end A.

Default = 0.0 (Real)

NSIB Nonstructural mass moment of inertia per unit length about nonstructural
mass center of gravity at end B.

Default = NSIA (Real)

M1A, M2A (y,z) coordinates of center of gravity of nonstructural mass at end A.

Default = 0.0, 0.0 (Real)

M1B, M2B (y,z) coordinates of center of gravity of nonstructural mass at end B.

Default = M1A, M2A (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 1703

Proprietary Information of Altair Engineering


Field Contents

N1A, N2A (y,z) coordinates of neutral axis at end A.

Default = 0.0, 0.0 (Real)

N1B, N2B (y,z) coordinates of neutral axis at end B.

Default = N1A, N2A (Real)

Comments

1. For structural problems, MID may reference only a MAT1 material entry. For heat transfer
problems, MID may reference only a MAT4 material entry.

2. Blank fields for K1 and K2 are defaulted to 1.0. If a value of 0.0 is used for K1 and K2,
the transverse shear flexibilities are set to 0.0.

3. One value for X/XB must be 1.0.

4. The moments of inertia are defined as follows:

5. Stress recovery is only allowed at end A and end B. Stress recovery at intermediate
stations is not supported.

6. If no stress data at end A is to be recovered, but a stress recovery location is defined for
end B, then the first continuation entry, which contains the fields C1(A) through F2(A),
may be omitted.

7. If the continuation line containing values C1 through F2 is entirely blank for end B, then
the stress recovery locations defined for end A are used. However, if any entry is defined
on this line, then all blank entries will default to 0.0 and not the corresponding entry for
end A.

8. Stress recovery locations must be the same for end A and end B.

9. OSDIAG, 166, 1 may be input in the I/O options section of the input deck to bypass error
terminations caused by PBEAM definitions which violate the rules outlined in comments 5
and 8. In such instances, the following occurs:

Warning messages regarding the violations are echoed to the .out file.

Stress is not recovered at intermediate stations.


Recovery locations defined for end A are also used for end B.
10. For tapered beams, a single prismatic beam is created with properties obtained by
weighted averaging of all station properties.

1704 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


11. The cross-sectional properties have to be specified fully for end A. For end B, blank fields
mean that the properties are the same as for end A. For intermediate stations, blank
fields result in a linear interpolation between the property value at end A and end B being
used.

12. The NSM specified at end A is the default value for NSM at end B. The default for all
other stations is a linear interpolation between end A and end B. So, for a constant NSM
over the length of the beam, only NSM at end A is required.

The mass of the element is calculated as:

Mass = density * beam_area * beam_length + NSM * beam_length

If the NSM value is different in different stations, it is averaged over all the stations and
the average is used in the element calculation.

13. This card is represented as a property in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1705

Proprietary Information of Altair Engineering


PBEAML

Bulk Data Entry

PBEAML – Beam Property

Description

Defines the properties of a beam element by cross-sectional dimensions that are used to
create beam elements via the CBEAM entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBEAML PID MID GROUP TYPE/ ND


NAME

DIM1(A) DIM2(A) … NSM(A) SO(1) X(1)/XB DIM1(1) DIM2(1)

… NSM(1) … SO(B) X(B)/XB DIM1(B) DIM2(B) …

NSM(B)

* The format of this bulk data


entry is somewhat unusual as
the field locations can vary
depending on the number of
dimensions used to define the
cross-section.

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBEAML 99 21 T

12. 14.8 2.5 26. NO 0.4 6.

7. 1.2 2.6 YES 0.6 6. 7.8

5.6. 2.3 YES

1706 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

PID Property identification number.

No default (Integer > 0)

MID Material identification number. See comment 1.

No default (Integer > 0)

GROUP Indicates if an arbitrary beam section definition is to be used. Refer to


Arbitrary Beam Section Definition in the User’s Guide. If the value of
this field is HYPRBEAM, the following field is NAME; otherwise it is TYPE.

Default = blank (blank or HYPRBEAM)

TYPE Cross-section shape. When GROUP field is blank, this field is TYPE.

No default ("BAR", "BOX", "BOX1", "CHAN", "CHAN1", "CHAN2", "CROSS",


"H", "HAT", "I", "I1", "L", "ROD", "T", "T1", "T2", "TUBE", "Z")

NAME Name of arbitrary beam section definition. Refer to Arbitrary Beam


Section Definition in the User’s Guide. When the value of GROUP is
HYPRBEAM, this field is NAME.

No default (Character string)

ND Number of dimensions used to specify the Cross-section shape. This is


required when the value of the GROUP field is HYPRBEAM. ND represents
the total number of dimensions used to define an Arbitrary Beam
Section.

Default = blank

DIMi(A) Cross-section dimensions at end A.

No default (Real > 0.0)

NSM(A) Nonstructural mass per unit length at end A.

Default = 0.0 (Real)

SO(#) Stress output request option for intermediate station #.


Stress output is not supported for intermediate stations so this field
must be set to NO.

X(#)/XB Distance from end A to intermediate station # in the element coordinate

Altair Engineering OptiStruct 13.0 Reference Guide 1707

Proprietary Information of Altair Engineering


Field Contents

system, divided by the length of the element.

Default = 1.0 (Real > 0.0)

DIMi(#) Cross-section dimensions at intermediate station #.

(Real > 0.0)

NSM(#) Nonstructural mass per unit length at intermediate station #.

Default = 0.0 (Real)

SO(B) Stress output request option for end B.

Default = YES (YES or NO)

X(B)/XB Distance form end A to end B in the element coordinate system, divided
by the length of the element.

This must be 1.0

DIMi(B) Cross-section dimensions at end B

(Real > 0.0)

NSM(B) Nonstructural mass per unit length at end B.

Default = 0.0 (Real)

Comments

1. For structural problems, MID may reference only a MAT1 material entry. For heat transfer
problems, MID may reference only a MAT4 material entry.

2. Up to eleven stations are allowed (end A and B, and nine intermediate stations #).

3. The cross-sectional properties, shear flexibility factors, and stress recovery points (C, D,
E, and F) are computed using the TYPE and DIMi as shown below. The element
coordinate system is located at the shear center.

1708 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Type = BAR Type = BOX

Type = BOX1 Type = CHAN

Altair Engineering OptiStruct 13.0 Reference Guide 1709

Proprietary Information of Altair Engineering


Type = CHAN1 Type = CHAN2

Type = CROSS Type = H

1710 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Type = HAT Type = I

Type = I1 Type = L

Altair Engineering OptiStruct 13.0 Reference Guide 1711

Proprietary Information of Altair Engineering


Type = ROD Type = T

Type = T1 Type = T2

1712 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Type = TUBE Type = Z

4. For PBEAML entries with more than one section, an equivalent PBEAM entry is derived. An
echo request will cause a printout of the derived PBEAM.

5. Stress recovery is only allowed at end A and end B. Stress recovery at intermediate
stations is not supported.

6. For tapered beams, a single prismatic beam is created with dimensions obtained by
weighted averaging of all station dimensions.

7. DIMi and NSM have to be specified fully on station A. On station B, blank means that the
dimensions are the same as at A. On other stations, it is a linear interpolation between A
and B.

8. The NSM specified at end A is the default value for NSM at end B. The default for all
other stations is a linear interpolation between end A and end B. So, for a constant NSM
over the length of the beam, only NSM at end A is required.

The mass of the element is calculated as:

Mass = density * beam_area * beam_length + NSM * beam_length

If the NSM value is different in different stations, it is averaged over all the stations and
the average is used in the element calculation.

9. This card is represented as a property in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1713

Proprietary Information of Altair Engineering


PBEAMX

Bulk Data Entry

PBEAMX – Optional BEAM Property Extension for Geometric Nonlinear Analysis

Description

Defines additional BEAM properties for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBEAMX PID ISMSTR ISTRAIN DM DB

Field Contents

PID Property identification number of the associated PBEAM, PBEAML. See


comment 1.

No default (Integer > 0)

ISMSTR Flag for small strain formulation.

Default = 2 (Integer = 1, 2)

1 - Small strain from time =0

2 - Full geometric non-linearity

ISTRAIN Flag for shear in beam formulation.

Default = ON (ON or OFF)

DM Beam membrane damping.

Default = 0.0 (Real > 0.0)

DB Beam bending damping.

Default = 0.01 (Real > 0.0)

Comments

1. The property identification number must be that of an existing PBEAM bulk data entry.
Only one PBEAMX property extension can be associated with a particular PBEAM.

1714 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


2. PBEAMX is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. If the small strain option is activated (ISMSTR = 1), the strain and stress are engineering
strain and stress; otherwise they are true strain and stress.

4. This card is represented as an extension to a PSOLID property in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1715

Proprietary Information of Altair Engineering


PBUSH

Bulk Data Entry

PBUSH – Generalized Spring-Damper-Mass Property

Description

Defines the nominal property values for a generalized spring-damper-mass structural element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBUSH PID K K1 K2 K3 K4 K5 K6

B B1 B2 B3 B4 B5 B6

GE GE1 GE2 GE3 GE4 GE5 GE6

M M1 M2 M3 M4 M5 M6

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBUSH 35 K 4.35 2.4 RIGID 3.1

GE 0.02

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBUSH 35 B 4.35

M 1.2 7.1

1716 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

PID Property identification number.

No default (Integer > 0)

K Flag indicating that the next 1 to 6 fields are stiffness values.

No default (Character)

Ki Nominal stiffness values in directions 1 through 6. See comments 3, 6, and


8.

Default = 0.0 (Real or RIGID)

B Flag indicating that the next 1 to 6 fields are force-per-velocity damping.

No default (Character)

Bi Nominal damping coefficients in directions 1 through 6 in units of force per


unit velocity.

Default = 0.0 (Real)

GE Flag indicating that the next 1 to 6 fields are the structural damping
constants.

No default (Character)

GEi Nominal structural damping constants in directions 1 through 6. See


comments 3, 5, and 6.

Default = 0.0 (Real)

M Flag indicating that the next 1 to 6 fields are directional masses.

Mi Nominal mass values in directions 1 through 6. See comment 7.

Default = 0.0 (Real)

Comments

1. All generalized spring-damper-mass property entries must have unique ID numbers.

2. The K, B, GE, and M lines may be specified in any order.

Altair Engineering OptiStruct 13.0 Reference Guide 1717

Proprietary Information of Altair Engineering


3. Ki, Bi, GEi, or Mi may be made frequency dependent for both direct and modal frequency
response by use of the PBUSHT entry.

The nominal values are used for all analysis types except frequency response. For modal
frequency response, the normal modes are computed using the nominal Ki values. The
frequency-dependent values are used at every excitation frequency.

4. To obtain the damping coefficient GE, multiply the critical damping ratio C/C0 by 2.0.

5. If PARAM, W4 is not specified, GEi is ignored in transient analysis.

6. For upward compatibility, if ONLY GE1 is specified on a PBUSH entry and GEi, i = 2 to 6 are
blank on that PBUSH entry, then a single structural damping is assumed and applied to all
Ki of that PBUSH. If a PBUSH entry has a GEi, i = 2 to 6 specified, then the GEi fields are
considered variable for that PBUSH entry.

7. The Mi fields do not contribute to mass and inertia properties. Their contributions to
gravity and/or centrifugal loading are also not included.

8. The keyword RIGID may be used in place of a stiffness value for Ki entries. When RIGID is
defined, a very high relative stiffness (relative to the surrounding structure) is selected
for that degree-of-freedom simulating a rigid connection.

9. This card is represented as a property in HyperMesh.

1718 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PBUSH1D

Bulk Data Entry

PBUSH1D – Rod-type Spring-and-Damper Property

Description

Defines the linear and nonlinear properties for a one-dimensional spring-and-damper structural
element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBUSH1D PID K B M

SPRING TYPE IDT

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBUSH1D 35 4.35 0.5

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBUSH1D 35 4.35

SPRING TABLE 43

Field Contents

PID Property identification number.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1719

Proprietary Information of Altair Engineering


Field Contents

K Stiffness.

Default = 0.0 (Real > 0)

B Viscous damping.

Default = 0.0 (Real > 0)

M Total mass.

Default = 0.0 (Real > 0)

SPRING String indicating that a function defining the spring characteristics follows.

TYPE Type of input definition.

Default = TABLE (Character = TABLE)

IDT Identification number of a TABLEDi table entry.

No default (Integer > 0)

Comments

1. Either the stiffness K, or the damping B, or the mass M must be specified. B and M are
ignored in static subcases.

2. The SPRING continuation line is used in nonlinear analysis solution sequences only. The
table input supersedes the stiffness K.

3. PBUSH1D may only be referenced by CBUSH1D elements.

4. In all linear subcases, as well as small displacement nonlinear quasi-static


(ANALYSIS=NLSTAT) subcases, PBUSH1D and CBUSH1D are converted internally to the
equivalent PBUSH (with PBUSHT, if necessary) and CBUSH.

5. This card is represented as a property in HyperMesh.

1720 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PBUSHT

Bulk Data Entry

PBUSHT – Generalized Spring and Damper Property

Description

Defines property values for a generalized spring and damper structural element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBUSHT PID TYPE TID1 TID2 TID3 TID4 TID5 TID6

TYPE TID1 TID2 TID3 TID4 TID5 TID6

TYPE TID1 TID2 TID3 TID4 TID5 TID6

TYPE TID1 TID2

... ...

Field Contents

PID Property identification number. Must match with a PID of a PBUSH Bulk
Data Entry.

No default (Integer > 0)

TYPE Identifies what the following six fields reference.

If TYPE is K, then the following six fields are stiffness vs. frequency table
references for dofs 1 through 6, respectively.

If TYPE is B, then the following six fields are viscous damping vs. frequency
table references for dofs 1 through 6, respectively.

If TYPE is GE, then the following six fields are structural damping vs.
frequency table references for dofs 1 through 6, respectively.

Altair Engineering OptiStruct 13.0 Reference Guide 1721

Proprietary Information of Altair Engineering


Field Contents

If TYPE is M, then the following six fields are directional mass vs. frequency
table references for dofs 1 through 6, respectively.

If TYPE is KN, then the following six fields are force vs. deflection table
references for dofs 1 through 6, respectively.

See comment 4.

No default (K, B, GE, M, or KN)

TID# Identification number of a TABLED# entry. The type of the referenced


table is defined by the TYPE keyword given on the same line. The six
references on each line represent the 6 degrees-of-freedom in sequence
from 1 through 6.

Default = 0 (Integer > 0)

Comments

1. The K, B, GE, and M fields are associated with the same entries on the PBUSH entry

2. PBUSHT may only be referenced by CBUSH elements in the residual structure which do not
attach to any omitted degrees-of-freedom.

3. The TYPEs can be defined in any order, but may only appear once per PBUSH definition.

4. TYPE=K, B, GE and M are allowed for frequency response analysis only, while TYPE=KN is
allowed only for nonlinear analysis.

5. For upward computability, if ONLY the dof1 field for the GE line (line where TYPE=GE) is
specified on ALL PBUSHT entries and the other dofs for the GE line are blank on ALL
PBUSH entries, then a single structural damping table for each PBUSHT applied to all
defined dofs on the K line for each PBUSH is assumed. If ANY PBUSHT entry has a dof
field other than dof1 for the GE line specified, then the GE fields are considered variable
on ALL PBUSH and PBUSHT entries.

6. This card is represented as a property in HyperMesh.

1722 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PCNTX2

Bulk Data Entry

PCNTX2 – Extended CONTACT Property type 2 for Geometric Nonlinear Analysis

Description

Defines properties TYPE2 tied CONTACT interface for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC NTX2 PID

IGNROE FSPOT LEVEL ISRC H IDELG

If FSPOT = 20, 21, or 22, two continuation lines

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RUPT IFILT SRTID SNTID STTID MAXND MAXTD

FSTR FSTRATE FDIST ALPHA

If FSPOT = 25, one continuation line

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

STFAC VISC

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC ONT 34

PC NTX2 34

Altair Engineering OptiStruct 13.0 Reference Guide 1723

Proprietary Information of Altair Engineering


Field Contents

PID Property identification number of the associated PCONT.

No default (Integer > 0)

IGNORE Flag to ignore slave nodes if no master segment found for TIE contact
(See comment 7).

Default as defined by CONTPRM (Integer = 0, 1, or 2)

0 - No deletion of slave nodes;


1 - Slave nodes with no master segment found are deleted from the
interface;
2 - Slave nodes with no master segment found are deleted from the
interface, if SRCHDIS is blank, then it would be new calculated internally.

FSPOT Flag for spotweld formulation. (Integer).

Default = 5.

1 - Formulation is optimized for spotweld or rivets.


2 - Same formulation as standard formulation. Required when using
hierarchy levels. Not compatible with nodal time step (TSTYP= GRID, TSC
= CST).
4 - Rotational degrees of freedom are not transmitted (if shells are
used).
5 - Standard formulation.

20, 21, 22 - formulation with failure. Not compatible with nodal time step
GRID(CST) on XSTEP card. The stress is computed for each slave node
according to the "equivalent" surface around the node. The equivalent
surface is defined accordingly:

20 - Surface computed using shell and brick faces attached to the node.
21 - Surface computed using only the shell attached to the node.
22 - Surface computed using only the brick faces attached to the node.

25 - Penalty formulation.
30 - Formulation with cubic curvature of master segment. Not compatible
with nodal time step GRID(CST) on XSTEP card.

LEVEL Hierarchy level of the interface.

No default (Integer > 0)

ISRCH Search formulation flag for the closest master segment.

Default = 2 (Integer)

1 - Old formulation (only used for previous version)

2 - New improved formulation

1724 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

IDELG Flag for node deletion.

0 - No deletion.

1 - The kinematic condition is suppressed on slave node, if the master


element is deleted. (The slave node is removed from the interface).

RUPT Failure model (only available with FSPOT = 20, 21, 22) (Integer).

See comment 7.

0 - Failure when MAXND or MAXTD are reached;

1 - See comment 10.

IFILT Filter flag (See comment 13)

Default = 0 (Integer = 0, 1)

0 - No filtering

1 - Filtering (alpha filter)

SRTID Identification number of TABLEDi entry defining stress factor vs stress


rate (See comment 9).

No default (Integer > 0)

SNTID Identification number of TABLEDi entry defining maximum normal stress vs


normal relative displacement(ND).

This function must be defined. (See comment 9)

No default (Integer > 0)

STTID Identification number of TABLEDi entry defining maximum tangential


stress vs tangential relative displacement (TD).

This function must be defined. (See comment 9)

No default (Integer > 0)

MAXND Maximum normal relative displacement.

Default = 1.0E20 (Real)

MAXTD Maximum tangential relative displacement.

Default = 1.0E20 (Real)

FSTR Stress scale factor (See comment 9)

Altair Engineering OptiStruct 13.0 Reference Guide 1725

Proprietary Information of Altair Engineering


Field Contents

Default = 1.00 (Real)

FSTRATE Stress rate scale factor (See comment 9)

Default = 1.00 (Real)

FDIST Distance scale factor (See comment 9)

Default = 1.00 (Real)

ALPHA Stress filter alpha value

Default = 1.00 (Real)

STFAC Interface stiffness scale factor. (Only used with FSPOT = 25)

Default = 1.00 (Real)

VISC (Optional) Critical damping coefficient on interface stiffness (Only used


with FSPOT = 25)

Default = 0.05 (Real)

Comments

1. The property identification number must be that of an existing PCONT bulk data entry.
Only one PCNTX2 property extension can be associated with a particular PCONT.

2. PCNTX2 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. If FRIC is not explicitly defined on the PCONTX/PCNTX# entries, the MU1 value on the
CONTACT or PCONT entry is used for FRIC in the /INTER entries for Geometric Nonlinear
Analysis. Otherwise, FRIC on PCONTX/PCNTX# overwrites the MU1 value on CONTACT/
PCONT.

4. PCNXT2 is only valid for tied contact on TIE card.

5. Interface type 2 is a kinematic condition, no other kinematic condition should be set on


any nodes of the slave surface.

6. The default value for SRCHDIS is the average of the mater segments.

7. If IGNORE = 1 or 2, the slave nodes without a master segment found during the searching
are deleted from the interface;

If INGORE = 1 and SRCHDIS is blank, then the default value of the distance for searching
closest master segment is the average size of the master segments;

If IGNORE = 2 and SRCHDIS is blank, then the distance for searching closest master
segment is computed as follows for each slave node:

1726 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


d1 = 0.6 * (T s + T m)

d2 = 0.05 * T md

SRCHDIS = max(d1 , d2)

where,

T s - Thickness of the element connected to the slave node, for solids T s = 0.0

T m - Thickness of master segment, for solids T m = Element volume / Segment area

T md - Master segment diagonal

8. Master nodes of an interface type 2 may be slave nodes of another interface type 2 if the
hierarchy level of the first interface is lower than the hierarchy level of the second
interface. Hierarchy levels are only available with FSPOT=2.

9. For failure (FSPOT = 20, 21, 22), it could model glue connection. In this case, the force in
slave node will be scaled by reduced force coefficient f N (f T ), which is computed as;

The reduced force is compared to the maximum value:

If , then ƒN = 1, which means the force will not be reduced.

If , then , which means the force will be then


reduced.

Here the maximum value will be defined by you with:

Altair Engineering OptiStruct 13.0 Reference Guide 1727

Proprietary Information of Altair Engineering


Where:

: maximum normal stress value defined by SNTID

: normal stress

: maximum tangential stress value defined by STTID

: tangential stress

FSTR: the input constant stress factor

SRTID: the input variable coefficient

SNTID and STTID: the input stress-displacement tables.

Once the rupture criterion (defined by Rupt) is reached, the contact will be deleted.

10. If RUPT = 1, the failure criterion is as follows:

11. If FSPOT = 30, slave mass/inertia/stiffness distribution to the master node is based on
the Kirschoff model: bi-cubic form functions are used instead of linear (standard
formulation). It allows a softer contact behavior since the element shape curvature is
taken into account in the force/moment transmission.

12. If IDELG = 1, then when a 4-node shell, a 3-node shell or a solid element is deleted, it is
also removed from the master side of the interface (kinematic condition is suppressed on
relative slave nodes).

13. If IFILT is set to 1, the normal and tangential stresses are filtered with an alpha filter, as
follows:

1728 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


14. FSPOT = 25 (penalty formulation) will keep the penalty formulation during the whole run.
The slave node (of this contact) could also be the slave node of another kinematic
option, like rigid body. The penalty stiffness is constant, calculated as the mean nodal
stiffness of master and slave side. The stiffness factor, STFAC, may be used to modify it,
if needed. The penalty stiffness will be multiplied by STFAC. A critical viscous damping
coefficient (VISC) allows damping to be applied to the interface stiffness.

Altair Engineering OptiStruct 13.0 Reference Guide 1729

Proprietary Information of Altair Engineering


PCNTX5

Bulk Data Entry

PCNTX5 – Extended CONTACT Property type 5 for Geometric Nonlinear Analysis

Description

Defines properties type 5 of a CONTACT interface for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC NTX5 PID IBAG IDEL

STFAC FRIC GAP TSTART TEND

IBC IRM INAC TI

IFRIC IFILT FFAC

FRIC DAT C1 C2 C3 C4 C5 C6

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC ONT 34

PC NTX5 34

Field Contents

PID Property identification number of the associated PCONT.

No default (Integer > 0)

IBAG Airbag vent holes closure flag in case of contact.

Default = 0 (Integer)

1730 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

0 - No closure

1 - Closure

IDEL Flag for node and segment deletion. (See comment 5)

Default as defined by CONTPRM (Integer = 0, …, 2)

0 - No deletion.

1 - When all the elements (shells, solids) associated to one segment are
deleted, the segment is removed from the master side of the interface.
Additionally, non-connected nodes are removed from the slave side of
the interface.

2 - When a shell or a solid element is deleted, the corresponding


segment is removed from the master side of the interface. Additionally,
non-connected nodes are removed from the slave side of the interface.

STFAC Interface stiffness scale factor.

Default = 0.2 (Real > 0)

FRIC Coulomb friction.

Default as defined by CONTPRM (Real > 0)

GAP Gap for impact activation (See comment 4).

Default as defined by CONTPRM (Real > 0)

TSTART Start time

Default = 0.0 (Real > 0)

TEND Time for temporary deactivation.

Default = 1030 (Real > 0)

IBC Flag for deactivation of boundary conditions at impact applied to the


slave grid set.

Default as defined by CONTPRM (Character = X, Y, Z, XY, XZ, YZ, XYZ)

IRM Renumbering flag for segments of the master surface (Integer = 0, 1, 2).

0 - If segment is connected to a solid element its normal is reversed if


entering the solid element (the segment is renumbered).

1 - Normal is always reversed (segment 1234 is read 2143).

Altair Engineering OptiStruct 13.0 Reference Guide 1731

Proprietary Information of Altair Engineering


Field Contents

2 - Normal is never reversed (segment connected to a solid element are


not renumbered).

INACTI Flag for handling of initial penetrations (See comment 6).

Default as defined by CONTPRM (Integer = 0, 3, 4)

0 - No action.
3 - Change slave node coordinates to avoid small initial penetrations.
4 - Change master node coordinates to avoid small initial penetrations.
Invalid entries are ignored.

IFRIC Friction formulation flag (See comment 7).

Default as defined by CONTPRM (Character = COUL, GEN, DARM, REN)

COUL - Static Coulomb friction law.


GEN - Generalized viscous friction law.
DARM - Darmstad friction law.
REN - Renard friction law.

IFILT Friction filtering flag (See comment 8).

Default as defined by CONTPRM (Character = NO, SIMP, PER, CUTF)

NO - No filter is used.
SIMP - Simple numerical filter.
PER - Standard -3dB filter with filtering period.
CUTF - Standard -3dB filter with cutting frequency.

FFAC Friction filtering factor.

Default as defined by CONTPRM (Real = 0.0 < FFAC < 1.0)

FRICDAT FRICDAT flag indicates that additional information for IFRIC will follow.
Only available when IFRIC = GEN, DARM or REN.

C1, C2, C3, Coefficients to define variable friction coefficient in IFRIC = GEN, DARM,
C4, C5, C6 REN.

Default as defined by CONTPRM (Real > 0)

Comments

1. The property identification number must be that of an existing PCONT bulk data entry.
Only one PCNTX5 property extension can be associated with a particular PCONT.

2. PCNTX5 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM or IMPDYN. It is ignored for all other subcases.

1732 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. If FRIC is not explicitly defined on the PCONTX/PCNTX# entries, the MU1 value on the
CONTACT or PCONT entry is used for FRIC in the /INTER entries for Geometric Nonlinear
Analysis. Otherwise, FRIC on PCONTX/PCNTX# overwrites the MU1 value on CONTACT/
PCONT.

4. In implicit analysis, different contact formulations are used for contact where slave and
master set do not overlap and where they overlap (self-contact).

In the case of self-contact, the gap cannot be zero and a constant gap is used. For
small initial gaps, the convergence will be more stable and faster if GAP is larger than the
initial gap.

In implicit analysis, sometimes a stiffness with scaling factor reduction (for example,
STFAC = 0.01) or reduction in impacted thickness (if rigid one) might reduce unbalanced
forces and improve convergence, particularly in shell structures under bending where the
effective stiffness is much lower than membrane stiffness; but it should be noted that too
low of a value could also lead to divergence.

5. Flag IDEL = 1 has a CPU cost higher than IDEL = 2.

6. INACTI = 3, 4 are only recommended for small initial penetrations and should be used with
caution because:

the coordinate change is irreversible.


it may create other initial penetrations if several surface layers are defined in the
interfaces.
it may create initial energy if the node belongs to a spring element.
7. IFRIC defines the friction model.

IFRIC = COUL – Coulomb friction with F T < FRIC * F N.

For IFRIC > 0 the friction coefficient is set by a function (µ = µ (p, V)), where p is the
pressure of the normal force on the master segment and V is the tangential velocity of
the slave node.

The following formulations are available:

IFRIC = 1 - Generalized viscous friction law

µ = FRIC + C1 * p + C2 * V + C3 * p * v + C4 * p2 + C5 * v2

IFRIC = 2 - Darmstad law

µ = C1 * e(C 2V ) * p2 + C3 * e(C 4V ) * p + C5 * e(C 6V )

IFRIC = 3 - Renard law

0 < V < C5

Altair Engineering OptiStruct 13.0 Reference Guide 1733

Proprietary Information of Altair Engineering


C5 < V < C6

C6 < V

where:

The first critical velocity Vcr1


second critical velocity Vcr2 (C5 < C6).

The static friction coefficient C1 and the dynamic friction coefficient C2, must be lower
than the maximum friction C3 (C1 < C3 and C2 < C3).

The minimum friction coefficient C4, must be lower than the static friction coefficient
C1 and the dynamic friction coefficient C2 (C4 < C1 and C4 < C2).

8. IFILT defines the method for computing the friction filtering coefficient. If IFILT NO,
the tangential friction forces are smoothed using a filter:

F T = α * F'T + (1 - α) * F'T-1

where,

F T - Tangential force

F'T - Tangential force at time t

F'T-1 - Tangential force at time t-1

α - filtering coefficient

IFILT = SIMP – α = FFAC

IFILT = PER – α = 2 dt/FFAC, where dt/T = FFAC, T is the filtering period

IFILT = CUTF – α = 2 * FFAC * dt, where FFAC is the cutting frequency

9. This card is represented as an extension to a PCONT property in HyperMesh.

1734 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PCNTX7

Bulk Data Entry

PCNTX7 – Extended CONTACT Property type 7 for Geometric Nonlinear Analysis

Description

Defines properties type 7 of a CONTACT interface for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC NTX7 PID

ISTF ITHE IGAP IBAG IDEL IC URV IADM

GAPFAC GAPMAX FPENMAX

STMIN STMAX MESHSIZ DTMIN IREMGAP


E

STFAC FRIC GAP TSTART TEND

IBC INAC TI VISS VISF BMULT

IFRIC IFILT FFAC IFORM SENSID

C URVDA G1 G2
T

FRIC DAT C1 C2 C3 C4 C5 C6

ADMDAT NRADM PADM ANGLAD


M

THEDAT RTHE TINT ITHEF

FRAD DRAD FHEATS FHEATM

Example

Altair Engineering OptiStruct 13.0 Reference Guide 1735

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC ONT 34

PC NTX7 34

Field Contents

PID Property identification number of the associated PCONT.

No default (Integer > 0)

ISTF Flag for stiffness definition (See comment 5).

Default as defined by CONTPRM (Integer = 0, …, 5)

0 - The stiffness is computed according to the master side


characteristics.
1 - STIF1 is used as interface stiffness.
2, 3, 4 and 5 - The interface stiffness is computed from both master and
slave characteristics.

ITHE Heat contact flag (Integer).

Default = 0.

0 - No heat transfer.

1 - Heat transfer activated.

IGAP Flag for gap definition.

Default as defined by CONTPRM (Character = CONST, VAR, VAR2, VAR3)

CONST - Gap is constant and equal to GAP (See comment 6).

VAR, VAR2, VAR3 - Gap is variable (in space, not in time) according to
the characteristics of the impacting surfaces and nodes (See comment
7).

IBAG Airbag vent holes closure flag in case of contact.

Default = 0 (Integer).

0 - No closure.

1 - Closure.

IDEL Flag for node and segment deletion.

Default as defined by CONTPRM (Integer = 0, …, 2)

1736 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

0 - No deletion.

1 - When all the elements (shells, solids) associated to one segment are
deleted, the segment is removed from the master side of the interface.
Additionally, non-connected nodes are removed from the slave side of
the interface.

2 - When a shell or a solid element is deleted, the corresponding


segment is removed from the master side of the interface. Additionally,
non-connected nodes are removed from the slave side of the interface.

ICURV Gap envelope with curvature (See comment 8).

Integer 0, ..., 3.

0 - No curvature.

1 - Spherical curvature.

2 - Cylindrical curvature.

3 - Automatic bicubic surface.

IADM Computing local curvature flag for adaptive meshing (See comments 9
and 10).

Default = 0 (Integer 0, 1, 2).

0 - Not activated.

1 - Interface update according mesh size.

2 - Interface update according mesh size, penetration and angle.

GAPFAC Gap scale factor (used only when IGAP = VAR2 and VAR3).

Default as defined by CONTPRM (Real > 0)

GAPMAX Maximum gap (used only when IGAP = VAR2 and VAR3).

Default as defined by CONTPRM (Real > 0)

FPENMAX Maximum fraction of initial penetration (See comment 13).

(Real)

STMIN Minimum stiffness (Only with ISTF > 1).

Default as defined by CONTPRM (Real > 0)

STMAX Maximum stiffness (Only with ISTF > 1).

Altair Engineering OptiStruct 13.0 Reference Guide 1737

Proprietary Information of Altair Engineering


Field Contents

Default as defined by CONTPRM (Real > 0)

MESHSIZE Percentage of mesh size (used only when IGAP = VAR3).

Default = 0.4 (Real, 0.0 < MESHSIZE < 1.0)

DTMIN Limiting nodal time step (see comment 19)

IREMGAP Flag to deactivate slave nodes if element size < gap value, in case of
self-impact contact (See comment 20).

Default = 1 (Integer)

1 - No slave node deactivation

2 - Deactivate slave nodes.

STFAC Interface stiffness scale factor.

Default as defined by CONTPRM (Real > 0)

FRIC Coulomb friction.

Default as defined by CONTPRM (Real > 0)

GAP Gap for impact activation (See comments 4 and 6).

Default as defined by CONTPRM (Real > 0)

TSTART Start time

Default = 0.0 (Real > 0)

TEND Time for temporary deactivation.

Default = 1030 (Real > 0)

IBC Flag for deactivation of boundary conditions at impact applied to the


slave grid set.

Default as defined by CONTPRM (Character = X, Y, Z, XY, XZ, YZ, XYZ)

INACTI Flag for handling of initial penetrations (See comment 13).

Default as defined by CONTPRM (Integer = 0, 1, 2, 3, 5, or 6)

0 - No action.
1 - Deactivation of stiffness on nodes.
2 - Deactivation of stiffness on elements.
3 - Change slave node coordinates to avoid small initial penetrations.

1738 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

5 - GAP is variable with time and initial gap is adjusted as follows:

gap0 = gap - P0

6 - Gap is variable with time but initial gap is slightly de-penetrated as


follows:

gap0 = gap - P0 – 0.05*(gap - P0)

Invalid entries are ignored.

VISS Critical damping coefficient on interface stiffness.

Default as defined by CONTPRM (Real > 0)

VISF Critical damping coefficient on interface friction.

Default as defined by CONTPRM (Real > 0)

BMULT Sorting factor. Can be used to speed up the sorting algorithm. Is


machine-dependent.

Default as defined by CONTPRM (Real > 0)

IFRIC Friction formulation flag (See comment 14).

Default as defined by CONTPRM (Character = COUL, GEN, DARM, or REN)

COUL - Static Coulomb friction law.


GEN - Generalized viscous friction law.
DARM - Darmstad friction law.
REN - Renard friction law.

IFILT Friction filtering flag (See comment 15).

Default as defined by CONTPRM (Character = NO, SIMP, PER, or CUTF)

NO - No filter is used.
SIMP - Simple numerical filter.
PER - Standard -3dB filter with filtering period.
CUTF - Standard -3dB filter with cutting frequency.

FFAC Friction filtering factor.

Default as defined by CONTPRM (Real = 0.0 < FFAC < 1.0)

IFORM Type of friction penalty formulation (See comment 16).

Default as defined by CONTPRM (Character = VISC, STIFF)

VISC - Viscous (total) formulation.

Altair Engineering OptiStruct 13.0 Reference Guide 1739

Proprietary Information of Altair Engineering


Field Contents

STIFF - Stiffness (incremental) formulation.

SENSID Sensor identifier to Activate/Deactivate the interface (See comment 21)

No default (Integer)

If a sensor identifier is defined, the activation/deactivation of the


interface is based on SENSID instead of TSTART or TSTOP.

CURVDAT CURVDAT flag indicates that additional information about ICURV will
follow. Only available when ICURV = 1 or 2.

G1 First grid identifier (used only when ICURV = 1 or 2)

(Integer)

G2 Second grid identifier (used only when ICURV = 2, ignored when ICURV =
1)

(Integer)

FRICDAT FRICDAT flag indicates that additional information for IFRIC will follow.
Only available when IFRIC = GEN, DARM or REN.

C1, C2, C3, Coefficients to define variable friction coefficient in IFRIC = GEN, DARM,
C4, C5, C6 REN.

Default as defined by CONTPRM (Real > 0)

ADMDAT ADMDAT flag indicates that additional information about IADM will follow.
Only available when IADM = 2.

NRADM Number of elements through a 90 degree radius 3 (used only when IADM
= 2)

(Integer)

PADM Criteria on the percentage of penetration (used only when IADM = 2).

Default = 1.0 (Real)

ANGLADM Angle criteria (used only when IADM = 2)

(Real)

THEDAT THEDAT flag indicates that additional information about ITHE will follow.
Only available when ITHE = 1.

1740 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

RTHE Heat conduction coefficient (used only when ITHE = 1, see comment 18)

(Real).

TINT Interface temperature (used only when ITHE = 1)

(Real)

ITHEF Heat contact formulation flag (used only when ITHE = 1, Integer).

0 - Exchange between constant temperature in the interface and shells


(slave side).

1 - Heat exchange between pieces in contact.

FRAD Radiation factor (used only when ITHE = 1)

No default (Real)

DRAD Maximum distance for radiation computation (used only when ITHE = 1)

No default (Real)

FHEATS Frictional heating factor of the slave (used only when ITHE = 1, see
comment 25)

No default (Real)

FHEATM Frictional heating factor of the master (used only when ITHE = 1, see
comment 25)

No default (Real)

Comments

1. The property identification number must be that of an existing PCONT bulk data entry.
Only one PCNTX7 property extension can be associated with a particular PCONT.

2. PCNTX7 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. If FRIC is not explicitly defined on the PCONTX/PCNTX# entries, the MU1 value on the
CONTACT or PCONT entry is used for FRIC in the /INTER entries for Geometric Nonlinear
Analysis. Otherwise, FRIC on PCONTX/PCNTX# overwrites the MU1 value on CONTACT/
PCONT.

4. In implicit analysis, different contact formulations are used for contact where slave and
master set do not overlap and where they overlap (self-contact).

In the case of self-contact, the gap cannot be zero and a constant gap is used. For
small initial gaps, the convergence will be more stable and faster if GAP is larger than the

Altair Engineering OptiStruct 13.0 Reference Guide 1741

Proprietary Information of Altair Engineering


initial gap.

In implicit analysis, sometimes a stiffness with scaling factor reduction (for example,
STFAC = 0.01) or reduction in impacted thickness (if rigid one) might reduce unbalanced
forces and improve convergence, particularly in shell structures under bending where the
effective stiffness is much lower than membrane stiffness; but it should be noted that too
low of a value could also lead to divergence.

5.
and/or the slave segment stiffness Ks.

The master stiffness is computed from Km = STFAC * B * S * S/V for solids, Km = 0.5 *
STFAC * E * t for shells.

The slave stiffness is an equivalent nodal stiffness computed as Ks = STFAC * B * V-3 for
solids, Ks = 0.5 * STFAC * E * t for shells.

In these equations, B is the Bulk Modulus, S is the segment area, and V is the volume of a
solid. There is no limitation to the value of stiffness factor (but a value larger than 1.0
can reduce the initial time step).

The interface stiffness is then K = max (STMIN, min (STMAX, K1)) with:

ISTF = 0, K1 = Km
ISTF = 2, K1 = 0.5 * (Km + Ks)
ISTF = 3, K1 = max (Km, Ks)
ISTF = 4, K1 = min (Km, Ks)
ISTF = 5, K1 = Km * Ks / (Km + Ks)
6. The default for the constant gap (IGAP = CONST) is the minimum of:

t, average thickness of the master shell elements;


l/10, l – average side length of the master solid elements;
lmin/2, lmin – smallest side length of all master segments (shell or solid).

7. If IGAP = VAR, the variable gap is computed as gs + gm;

If IGAP = VAR2, the variable gap is computed as max(GAP, min(GAPFAC * (gs+gm),


GAPMAX);

If IGAP = VAR3, the variable gap is computed as max(GAP, min(GAPFAC * (gs+gm),


MESHSIZE * (gsl+gml), GAPMAX).

with:

gm - master element gap, with:


gm = t/2, t: thickness of the master element for shell elements.

gm = 0 for solid elements.

gs - slave node gap:


gs = 0 if the slave node is not connected to any element or is only connected to solid

1742 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


or spring elements.

gs = t/2, t - largest thickness of the shell elements connected to the slave node.

element.

gml - length of the smaller edge of element.


gsl - length of the smaller edge of elements connected to the slave nodes.
If the slave node is connected to multiple shells and/or beams or trusses, the largest
computed slave gap is used.

The variable gap is always at least equal to GAP.

8. If ICURV = 1, a spherical curvature is defined for the gap with node_ID1 (center of the
sphere).

If ICURV = 2, a cylindrical curvature is defined for the gap with node_ID1 and node_ID2
(on the axis of the cylinder).

If ICURV = 3, the master surface shape is obtained with a bicubic interpolation, respecting
continuity of the coordinates and the normal from one segment to the other.

In case of a large change in curvature, this formulation might become unstable (will be
improved in future version).

9. In case of adaptive meshing and IADM =1:

If the contact occurs in a zone (master side) whose radius of curvature is lower than the
element size (slave side), the element on the slave side will be divided (if not yet at
maximum level).

10. In case of adaptive meshing and IADM =2:

Altair Engineering OptiStruct 13.0 Reference Guide 1743

Proprietary Information of Altair Engineering


If the contact occurs in a zone (master side) whose radius of curvature is lower than
NRadm times the element size (slave side), the element on the slave side will be divided
(if not yet at maximum level).

If the contact occurs in a zone (master side) where the angles between the normals are
greater than Angladm and the percentage of penetration is greater than Padm, the
element on the slave side will be divided (if not yet at maximum level).

11. The coefficients NRADM, PADM, and ANGLADM are used only adaptive meshing and IADM
= 2.

12. If GAPMAX is equal to zero, there is no maximum value for the gap.

13. INACTI = 3, is only recommended for small initial penetrations and should be used with
caution because:

the coordinate change is irreversible.


it may create other initial penetrations if several surface layers are defined in the
interfaces.
it may create initial energy if the node belongs to a spring element.
INACTI = 5 is recommended for airbag simulation deployment.

INACTI = 6 is recommended instead of INACTI = 5, in order to avoid high frequency effects


into the interfaces.

1744 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


If FPENMAX is not equal to zero, nodes stiffness is deactivated if penetration >
FPENMAX*GAP, regardless of the value of INACTI.

14. IFRIC defines the friction model.

IFRIC = COUL – Coulomb friction with F T < FRIC * F N.

For IFRIC > 0 the friction coefficient is set by a function ( = (p, V)), where p is the
pressure of the normal force on the master segment and V is the tangential velocity of
the slave node.

The following formulations are available:

IFRIC = 1 - Generalized viscous friction law

= FRIC + C1 * p + C2 * V + C3 * p * v + C4 * p2 + C5 * v2

IFRIC = 2 - Darmstad law

= C1 * e(C 2V) * p2 + C3 * e(C 4V) * p + C5 * e(C 6V)

IFRIC = 3 - Renard law

0 < V < C5

C5 < V < C6

C6 < V

where:

The first critical velocity Vcr1


second critical velocity Vcr2 (C5 < C6).

The static friction coefficient C1 and the dynamic friction coefficient C2, must be lower
than the maximum friction C3 (C1 < C3) and C2 < C3).

Altair Engineering OptiStruct 13.0 Reference Guide 1745

Proprietary Information of Altair Engineering


The minimum friction coefficient C4, must be lower than the static friction coefficient
C1 and the dynamic friction coefficient C2 (C4 < C1 and C4 < C2).

15.
the tangential friction forces are smoothed using a filter:

F T = α * F'T + (1 - α) * F'T-1

where,

F T - Tangential force

F'T - Tangential force at time t

F'T-1 - Tangential force at time t-1

α - filtering coefficient

IFILT = SIMP – α = FFAC

IFILT = PER – α = 2 dt/FFAC, where dt/T = FFAC, T is the filtering period

IFILT = CUTF – α = 2 * FFAC * dt, where FFAC is the cutting frequency

16. IFORM selects two types of contact friction penalty formulation.

The viscous (total) formulation (IFORM = VISC) computes an adhesive force as:

F adh T

F T = min (µF N, F adh)

The stiffness (incremental) formulation (IFORM = STIFF) computes an adhesive force as:

F adh = F Told + F T

F T = K * VT * dt

F Tnew = min (µF N, F adh)

17. Exchange between shell and constant temperature contact TINT.

18. RTHE is the inverse of thermal resistance (units: [W/(m2·K)]).

19. Slave segment contact is deactivated when the segment kinematic time step calculated
for this contact is lower than DTMIN.

20. With IREMGAP = 2, this allows the element size < gap values:

1746 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


In case of self-impact contact, when curvilinear distance (from a node of the master
segment to a slave node) is < gap*sqrt(2) (in initial configuration), then this slave node
will not be taken into account by this master segment, and it will not be deleted from the
contact for the other master segments.

21. When SENSID is defined for activation/deactivation of the interface, TSTART and TSTOP
are not taken into account.

22. If FRAD is not equal to zero, and d, the distance from the slave node to the master
segment, is in the range: Gap < d < DRAD, then radiation is calculated. The radiant heat
transfer conductance is calculated as:

Where, is the Stefan Boltzman constant, 1 is the emissivity of the slave surface, and
2 is the emissivity of the master surface.

23. If FRAD is not equals to zero, then the default value of DRAD is calculated as the
maximum of:

upper value of the gap (at time 0) among all nodes;


smallest side length of slave element.
24. A very high value of DRAD is not recommended as it may reduce the performance of the
solver

25. Frictional energy is converted into heat when heat transfer is activated (ITHE > 0) on the
interface. Options FHEATS and FHEATM are used to control this option.

When FHEATS and FHEATM = 0, the conversion of the frictional sliding energy to heat is
not activated. Non-zero values of FHEATS and FHEATM define the fraction of this energy
which is converted into heat and transferred to the slave and master respectively.

The frictional heat QFric is defined as follows:

Altair Engineering OptiStruct 13.0 Reference Guide 1747

Proprietary Information of Altair Engineering


If IFORM = 2 (a stiffness formulation):

Slave:

Master: (ITHEF=1)

If IFORM = 1 (a penalty formulation):

Slave:

Master: (ITHEF=1)

26. This card is represented as an extension to a PCONT property in HyperMesh.

1748 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PCNTX11

Bulk Data Entry

PCNTX11 – Extended Contact (CONTX11) Property type 11 for Geometric Nonlinear Analysis

Description

Defines properties type 11 of a CONTACT interface for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC NTX11 PID ISTF IGAP IDEL

STMIN STMAX MESHSIZE DTMIN

STFAC FRIC GAP TSTART TEND STF1

IBC INAC TI VISS VISF BMULT

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC ONT 34

PC NTX11 34

Field Contents

PID Property identification number of the associated PCONT.

No default (Integer > 0)

ISTF Flag for stiffness definition (See comment 6).

Default as defined by CONTPRM (Integer = 0, …, 5)

0 - STFAC is a stiffness scale factor and the stiffness is computed


according to the master side characteristics.
1 - STIF1 is used as interface stiffness.
2, 3, 4 and 5 - STFAC is a stiffness scale factor and the interface

Altair Engineering OptiStruct 13.0 Reference Guide 1749

Proprietary Information of Altair Engineering


Field Contents

stiffness is computed from both master and slave characteristics.

IGAP Flag for gap definition.

Default as defined by CONTPRM (Character = CONST, VAR, VAR3)

CONST - Gap is a constant and equal to GAP (See comment 7).

VAR - Gap is a variable (in space, not in time) according to the


characteristics of the impacted master line and the impacting slave
nodes (See comment 8).

VAR3 - Gap is a variable according to the characteristics of the impacted


master line and impacting slave node + gap is taken into account the
size of the elements.

IDEL Flag for node and segment deletion.

Default as defined by CONTPRM (Integer = 0, …, 2)

0 - No deletion.

1 - When all the elements (shells and solids) associated to one segment
are deleted, the segment is removed from the master side of the
interface. Additionally, non-connected nodes are removed from the
slave side of the interface.

2 - When a shell or a solid element is deleted, the corresponding


segment is removed from the master side of the interface. Additionally,
non-connected nodes are removed from the slave side of the interface.

STMIN Minimum stiffness (Only with ISTF > 1).

Default as defined by CONTPRM (Real > 0)

STMAX Maximum stiffness (Only with ISTF > 1).

Default as defined by CONTPRM (Real > 0)

MESHSIZE Percentage of mesh size (Used only when IGAP = VAR3).

Default = 0.4 (Real, 0.0 < MESHSIZE < 1.0)

DTMIN Limiting nodal time step (see comment 10)

No default (Real > 0)

STFAC

Default as defined by CONTPRM (Real > 0)

1750 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

FRIC Coulomb friction.

Default as defined by CONTPRM (Real > 0)

GAP Gap for impact activation (See comments 7 and 8).

Default as defined by CONTPRM (Real > 0)

TSTART Start time.

Default = 0.0 (Real > 0)

TEND Time for temporary deactivation.

Default = 1030 (Real > 0)

STIF1 Interface stiffness (Only with ISTF = 1).

Default = 0.0 (Real > 0)

IBC Flag for deactivation of boundary conditions at impact applied to the


slave grid set.

Default as defined by CONTPRM (Character = X, Y, Z, XY, XZ, YZ, XYZ)

INACTI Flag for handling of initial penetrations (See comment 8).

Default as defined by CONTPRM (Integer = 0, 1, 2, 3, 5, or 6)

0 - No action.
1 - Deactivation of stiffness on nodes.
2 - Deactivation of stiffness on elements.
3 - Change slave node coordinates to avoid small initial penetrations.
5 - GAP is a variable with time and initial gap is adjusted as follows:

gap0 = gap - P0

6 - Gap is variable with time but initial gap is slightly de-penetrated as


follows:

gap0 = gap - P0 – 0.05*(gap - P0)

Invalid entries are ignored.

VISS Critical damping coefficient on interface stiffness.

Default as defined by CONTPRM (Real > 0)

VISF Critical damping coefficient on interface friction.

Default as defined by CONTPRM (Real > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1751

Proprietary Information of Altair Engineering


Field Contents

BMULT Sorting factor. Can be used to speed up the sorting algorithm and is
machine-dependent.

Default as defined by CONTPRM (Real > 0)

Comments

1. The property identification number must be that of an existing PCONT bulk data entry.
Only one PCNTX11 property extension can be associated with a particular PCONT.

2. PCNTX11 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. If FRIC is not explicitly defined on the PCONTX/PCNTX# entries, the MU1 value on the
CONTACT or PCONT entry is used for FRIC in the /INTER entries for Geometric Nonlinear
Analysis. Otherwise, FRIC on PCONTX/PCNTX# overwrites the MU1 value on CONTACT/
PCONT.

4. PCNTX11 defines the properties of contact interface type CONTX11, it describes the edge
to edge or line to line interface. This interface simulates impact between lines, a line can
be a beam or truss element or a shell edge or spring elements. The interface properties
are:

impacts occur between a master and a slave line;


a slave line can impact on one or more master lines;
a line can belong to the master and the slave side. This allows self impact;
this interface can be used in addition to the interface type 7 PCNTX7 to solve the
edge to edge limitation of interface type 7.
5.
and/or the slave segment stiffness Ks.

The master stiffness is computed from Km = STFAC * B * S * S/V for solids, Km = 0.5 *
STFAC * E * t for shells.

The slave stiffness is an equivalent nodal stiffness computed as Ks = STFAC * B * V-3 for
solids, Ks = 0.5 * STFAC * E * t for shells.

In these equations, B is the Bulk Modulus, S is the segment area, and V is the volume of a
solid. There is no limitation to the value of stiffness factor (but a value larger than 1.0
can reduce the initial time step).

The interface stiffness is then, K = max (STMIN, min (STMAX, K1)) with:

ISTF = 0, K1 = Km
ISTF = 2, K1 = 0.5 * (Km + Ks)
ISTF = 3, K1 = max (Km, Ks)
ISTF = 4, K1 = min (Km, Ks)

1752 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


ISTF = 5, K1 = Km * Ks / (Km + Ks)

6. The default for the constant gap (IGAP = CONST) is equal to GAP.

7. If IGAP = VAR, the variable gap is computed as: gm + gs

with:

gm - master element gap with


gm = t/2, t: thickness of the master element for shell elements.

gm = L/10, L - length of the smallest side of a solid element.

element.

gm = 0 for spring elements.

gs - slave element gap is computed as the same way.


If the slave node is connected to multiple shells and/or beams or trusses, the largest
computed slave gap is used.

The variable gap is always at least equal to GAP.

8. INACTI = 3, is only recommended for small initial penetrations and should be used with
caution because:

the coordinate change is irreversible.


it may create other initial penetrations, if several surface layers are defined in the
interfaces.
it may create initial energy, if the node belongs to a spring element.
INACTI = 5 is recommended for airbag simulation deployment.

INACTI = 6 is recommended instead of INACTI = 5, in order to avoid high frequency effects


into the interfaces.

9. The sorting factor BUMULT is used to speed up the sorting algorithm, it is machine
dependent.

Altair Engineering OptiStruct 13.0 Reference Guide 1753

Proprietary Information of Altair Engineering


10. Slave segment is deactivated from the contact when the segment kinematic time step
calculated for this contact becomes smaller than DTMIN.

1754 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PCNTX20

Bulk Data Entry

PCNTX20 – Extended CONTACT Property type 20 for Geometric Nonlinear Analysis

Description

Defines properties type 20 of a CONTACT interface for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC NTX20 PID ISYM IEDGE GRNDID EDGEAngle

IGAP IBAG IDEL

FPENMAX

STFAC FRIC GAP TSATAT TEND

IBC INAC TI VISS VISF

IFRIC IFILT FFAC IFORM

FRIC DAT C1 C2 C3 C4 C5 C6

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC ONT 34

PC NTX20 34

Field Contents

PID Property identification number of the associated PCONT.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1755

Proprietary Information of Altair Engineering


Field Contents

ISYM Flag for symmetric contact.

Default as defined by CONTPRM (Character = SYM or UNSYM)

SYM – Symmetric contact.


UNSYM – Master-slave contact.

If SSID defines a grid set, the contact is always a master-slave contact.

IEDGE Flag for edge generation from slave and master surfaces.

Default as defined by CONTPRM (Character = NO, ALL, BORD, FEAT)

NO – No edge generation.
All – All segment edges are included.
BORD – External border of slave and master surface is used.
FEAT – External border as well as features defined by FANG are used.

GRNDID Optional nodes group identifier (Integer).

EdgeAngle Edges angle (used only if IEDGE = FEAT)

Default = 91 (Real).

If angle between two edges is smaller than EdgeAngle, the edge is


considered.

IGAP Flag for gap definition.

Default as defined by CONTPRM (Character = CONST or VAR)

CONST - Gap is constant and equal to GAP (See comment 6).

VAR - Gap is variable (in space, not in time) according to the


characteristics of the impacting surfaces and nodes (See comment 7).

IBAG Airbag vent holes closure flag in case of contact.

Default = 0 (Integer).

0 - No closure.

1 - Closure.

IDEL Flag for node and segment deletion.

Default as defined by CONTPRM (Integer = 0, …, 2)

0 - No deletion.

1 - When all the elements (shells and solids) associated to one segment
are deleted, the segment is removed from the master side of the

1756 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

interface. Additionally, non-connected nodes are removed from the


slave side of the interface.

2 - When a shell or a solid element is deleted, the corresponding


segment is removed from the master side of the interface. Additionally,
non-connected nodes are removed from the slave side of the interface.

FPENMAX Maximum initial penetration factor (0 < FPENMAX < 1) (See comment 8).

Default = 1.0 (Real)

STFAC Interface stiffness scale factor.

Default as defined by CONTPRM (Real > 0)

FRIC Coulomb friction.

Default as defined by CONTPRM (Real > 0)

GAP Gap for impact activation (See comments 4 and 6).

Default as defined by CONTPRM (Real > 0)

TSTART Start time.

Default = 0.0 (Real > 0)

TEND Time for temporary deactivation.

Default = 1030 (Real > 0)

IBC Flag for deactivation of boundary conditions at impact applied to the


slave grid set.

Default as defined by CONTPRM (Character = X, Y, Z, XY, XZ, YZ, XYZ)

INACTI Flag for handling of initial penetrations (See comment 9).

Default as defined by CONTPRM (Integer = 0, 1, 2, 3, or 5)

0 - No action.
1 - Deactivation of stiffness on nodes.
2 - Deactivation of stiffness on elements.
3 - Change slave node coordinates to avoid small initial penetrations.
5 - Gap is variable with time but initial gap is slightly de-penetrated as
follows:

gap0 = gap - P0 – 0.05 * (gap - P0)

Valid in explicit analysis: 0, 1, 2, 3 and 5.

Altair Engineering OptiStruct 13.0 Reference Guide 1757

Proprietary Information of Altair Engineering


Field Contents

Invalid entries are ignored.

VISS Critical damping coefficient on interface stiffness.

Default as defined by CONTPRM (Real > 0)

VISF Critical damping coefficient on interface friction.

Default as defined by CONTPRM (Real > 0)

IFRIC Friction formulation flag (See comment 10).

Default as defined by CONTPRM (Character = COUL, GEN, DARM, REN)

COUL - Static Coulomb friction law.


GEN - Generalized viscous friction law.
DARM - Darmstad friction law.
REN - Renard friction law.

IFILT Friction filtering flag (See comment 11).

Default as defined by CONTPRM (Character = NO, SIMP, PER, CUTF)

NO - No filter is used.
SIMP - Simple numerical filter.
PER - Standard -3dB filter with filtering period.
CUTF - Standard -3dB filter with cutting frequency.

FFAC Friction filtering factor.

Default as defined by CONTPRM (Real = 0.0 < FFAC < 1.0)

IFORM Type of friction penalty formulation (See comment 12).

Default as defined by CONTPRM (Character = VISC, STIFF)

VISC - Viscous (total) formulation.


STIFF - Stiffness (incremental) formulation.

FRICDAT FRICDAT flag indicates that additional information for IFRIC will follow.
Only available when IFRIC = GEN, DARM or REN.

C1, C2, C3, Coefficients to define variable friction coefficient in IFRIC = GEN, DARM,
C4, C5, C6 REN.

Default as defined by CONTPRM (Real > 0)

Comments

1. The property identification number must be that of an existing PCONT bulk data entry.
Only one PCNTX20 property extension can be associated with a particular PCONT.

1758 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


2. PCNTX20 is only applied in geometric nonlinear explicit dynamic analysis subcase which is
defined by ANALYSIS = EXPDYN, but not supported in NLGEOM or IMPDYN subcases. It is
ignored for all other subcases.

3. If FRIC is not explicitly defined on the PCONTX/PCNTX# entries, the MU1 value on the
CONTACT or PCONT entry is used for FRIC in the /INTER entries for Geometric Nonlinear
Analysis. Otherwise, FRIC on PCONTX/PCNTX# overwrites the MU1 value on CONTACT/
PCONT.

4. In implicit analysis, different contact formulations are used for contact where slave and
master set do not overlap and where they overlap (self-contact).

In the case of self-contact, the gap cannot be zero and a constant gap is used. For
small initial gaps, the convergence will be more stable and faster if GAP is larger than the
initial gap.

In implicit analysis, sometimes a stiffness with scaling factor reduction (for example,
STFAC = 0.01) or reduction in impacted thickness (if rigid one) might reduce unbalanced
forces and improve convergence, particularly in shell structures under bending where the
effective stiffness is much lower than membrane stiffness; but it should be noted that too
low of a value could also lead to divergence.

5.
and/or the slave segment stiffness Ks.

The master stiffness is computed from Km = STFAC * B * S * S/V for solids, Km = 0.5 *
STFAC * E * t for shells.

The slave stiffness is an equivalent nodal stiffness computed as Ks = STFAC * B * V-3 for
solids, Ks = 0.5 * STFAC * E * t for shells.

In these equations, B is the Bulk Modulus, S is the segment area, and V is the volume of a
solid. There is no limitation to the value of stiffness factor (but a value larger than 1.0
can reduce the initial time step).

The interface stiffness is then K = max (STMIN, min (STMAX, K1)) with:

ISTF = 0, K1 = Km

ISTF = 2, K1 = 0.5 * (Km + Ks)


ISTF = 3, K1 = max (Km, Ks)
ISTF = 4, K1 = min (Km, Ks)
ISTF = 5, K1 = Km * Ks / (Km + Ks)
6. The default for the constant gap (IGAP = CONST) is the minimum of:

t, average thickness of the master shell elements;


l/10, l – average side length of the master solid elements;
lmin/2, lmin – smallest side length of all master segments (shell or solid).
7. The variable gap (IGAP = VAR) is computed as: gs + gm

with:

Altair Engineering OptiStruct 13.0 Reference Guide 1759

Proprietary Information of Altair Engineering


gm - master element gap with

gm = t/2, t: thickness of the master element for shell elements.

gm = 0 for solid elements.

gs - slave node gap:


gs = 0 if the slave node is not connected to any element or is only connected to solid
or spring elements.

gs = t/2, t - largest thickness of the shell elements connected to the slave node.

element.

If the slave node is connected to multiple shells and/or beams or trusses, the largest
computed slave gap is used.

8. Maximum penetration value is set as a fraction of the actual gap (including variable gap):

Penmax = FPENMAX * gap

If the initial penetration of a slave node is greater than the calculated maximum value
(Penmax), the node will be deactivated from the interface (node stiffness deactivation).

9. INACTI = 3, is only recommended for small initial penetrations and should be used with
caution because:

the coordinate change is irreversible.


it may create other initial penetrations if several surface layers are defined in the
interfaces.
it may create initial energy if the node belongs to a spring element.
INACTI = 5 works as follows:

10. IFRIC defines the friction model.

IFRIC = COUL – Coulomb friction with F T < FRIC * F N.

p, V
For IFRIC > 0, the friction coefficient is set by a function ( )

1760 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


where, p is the pressure of the normal force on the master segment and V is the
tangential velocity of the slave node.

The following formulations are available:

IFRIC = 1 - Generalized viscous friction law

µ = FRIC + C1 * p + C2 * V + C3 * p * v + C4 * p2 + C5 * v2

IFRIC = 2 - Darmstad law

µ = C1 * e(C 2V ) * p2 + C3 * e(C 4V ) * p + C5 * e(C 6V )

IFRIC = 3 - Renard law

0 < V < C5

C5 < V < C6

C6 < V

where:

The first critical velocity Vcr1


second critical velocity Vcr2 (C5 < C6).

The static friction coefficient C1 and the dynamic friction coefficient C2, must be lower
than the maximum friction C3 (C1 < C3 and C2 < C3).

The minimum friction coefficient C4, must be lower than the static friction coefficient
C1 and the dynamic friction coefficient C2 (C4 < C1 and C4 < C2).

11. IFILT defines the method for computing the friction filtering coefficient. If IFILT NO,
the tangential friction forces are smoothed using a filter:

F T = α * F'T + (1 - α) * F'T-1

Altair Engineering OptiStruct 13.0 Reference Guide 1761

Proprietary Information of Altair Engineering


where,

F T - Tangential force

F'T - Tangential force at time t

F'T-1 - Tangential force at time t-1

α - filtering coefficient

IFILT = SIMP – α = FFAC

IFILT = PER – α = 2 dt/FFAC, where dt/T = FFAC, T is the filtering period

IFILT = CUTF – α = 2 * FFAC * dt, where FFAC is the cutting frequency

12. IFORM selects two types of contact friction penalty formulation.

The viscous (total) formulation (IFORM = VISC) computes an adhesive force as:

F adh T

F T = min (µF N, F adh)

The stiffness (incremental) formulation (IFORM = STIFF) computes an adhesive force as:

F adh = F Told + ∆F T

∆F T = K * VT * dt

F Tnew = min (µF N, F adh)

13. This card is represented as an extension to a PCONT property in HyperMesh.

1762 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PCNTX24

Bulk Data Entry

PCNTX24 – Extended CONTACT Property type 24 for Geometric Nonlinear Analysis

Description

Defines properties type 24 of a CONTACT interface for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC NTX24 PID

ISTF

GAPMAXs GAPMAXm

STMIN STMAX IGAP0 IPEN0 IPENMAX IPENMIN

STFAC FRIC TSTART TEND

IBC INAC TI VISS

IFRIC IFILT FFAC SENSID

FRIC DAT C1 C2 C3 C4 C5 C6

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC ONT 34

PC NTX24 34

Altair Engineering OptiStruct 13.0 Reference Guide 1763

Proprietary Information of Altair Engineering


Field Contents

PID Property identification number of the corresponding PCONT entry.

No default (Integer > 0)

ISTF Flag for stiffness definition (See comment 5).

Default as defined by CONTPRM (Integer = 0, …, 5)

0 - The stiffness is computed according to the master side


characteristics.
2, 3, 4 and 5 - The interface stiffness is computed from both master and
slave characteristics.

GAPMAXs Slave maximum gaps.

No default (Real)

GAPMAXm Master maximum gaps.

No default (Real)

STMIN Minimum stiffness (Only with ISTF > 1).

Default as defined by CONTPRM (Real > 0)

STMAX Maximum stiffness (Only with ISTF > 1).

Default as defined by CONTPRM (Real > 0)

IGAP0 Gap modification flag for slave shell nodes on the free edges.

(Integer)

0 - No change

1 - Set gap to zero for the slave shell nodes

IPEN0 Initial penetration detection flag (See comment 14)

(Integer)

0 - default method (excluding auto-impact in each part)

1 - method 1 (including auto-impact in each part)

IPENMAX Maximum initial penetration: Penetration higher than this value will not be
taken into account.

(Real)

IPENMIN Minimum initial penetration: Penetration higher than this value will be

1764 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

taken into account.

(Real)

STFAC Interface stiffness scale factor.

Default as defined by CONTPRM (Real > 0)

FRIC Coulomb friction.

Default as defined by CONTPRM (Real > 0)

TSTART Start time

Default = 0.0 (Real > 0)

TEND Time for temporary deactivation.

Default = 1030 (Real > 0)

IBC Flag for deactivation of boundary conditions at impact applied to the


slave grid set.

Default as defined by CONTPRM (Character = X, Y, Z, XY, XZ, YZ, XYZ)

INACTI Flag for handling of initial penetrations (See comment 8).

Default as defined by CONTPRM (Integer = 0, 1, -1, 5)

0 - only tiny initial penetrations (1.0e-08) will be taken into account.


1 - all initial penetrations will be ignored.
-1 - all initial penetrations will be taken into account.
5 - GAP is variable with time and initial gap is adjusted as follows:

gap0 = gap - P0 , where P0 is the initial penetration

VISS Critical damping coefficient on interface stiffness.

Default as defined by CONTPRM (Real > 0)

IFRIC Friction formulation flag (See comment 9).

Default as defined by CONTPRM (Character = COUL, GEN, DARM, REN)

COUL - Static Coulomb friction law.


GEN - Generalized viscous friction law.
DARM - Darmstad friction law.
REN - Renard friction law.

IFILT Friction filtering flag (See comment 10).

Altair Engineering OptiStruct 13.0 Reference Guide 1765

Proprietary Information of Altair Engineering


Field Contents

Default as defined by CONTPRM (Character = NO, SIMP, PER, CUTF)

NO - No filter is used.
SIMP - Simple numerical filter.
PER - Standard -3dB filter with filtering period.
CUTF - Standard -3dB filter with cutting frequency.

FFAC Friction filtering factor.

Default as defined by CONTPRM

SENSID Sensor identifier to Activate/Deactivate the interface (See comment 12)

No default (Integer)

If a sensor identifier is defined, the activation/deactivation of interface is


based on the sensor and not on Tstart or Tstop.

FRICDAT FRICDAT flag indicates that additional information for IFRIC will follow.
Only available when IFRIC = GEN, DARM or REN.

C1, C2, C3, Coefficients to define variable friction coefficient in IFRIC = GEN, DARM,
C4, C5, C6 REN.

Default as defined by CONTPRM (Real > 0)

Comments

1. The property identification number must be that of an existing PCONT bulk data entry.
Only one PCNTX24 property extension can be associated with a particular PCONT.

2. PCNTX24 is only supported for geometric nonlinear explicit dynamic analysis subcase
defined by ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. If FRIC is not explicitly defined on the PCONTX/PCNTX# entries, the MU1 value on the
CONTACT or PCONT entry is used for FRIC in the /INTER entries for Geometric Nonlinear
Analysis. Otherwise, FRIC on PCONTX/PCNTX# overwrites the MU1 value on CONTACT/
PCONT.

4. In implicit analysis, different contact formulations are used for contact where slave and
master set do not overlap and where they overlap (self-contact).

In the case of self-contact, the gap cannot be zero and a constant gap is used. For
small initial gaps, the convergence will be more stable and faster if GAP is larger than the
initial gap.

In implicit analysis, sometimes a stiffness with scaling factor reduction (for example,
STFAC = 0.01) or reduction in impacted thickness (if rigid one) might reduce unbalanced
forces and improve convergence, particularly in shell structures under bending where the
effective stiffness is much lower than membrane stiffness; but it should be noted that too
low of a value could also lead to divergence.

1766 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


5.
and/or the slave segment stiffness Ks.

The master stiffness is computed from Km = STFAC * B * S * S/V for solids, Km = 0.5 *
STFAC * E * t for shells.

The slave stiffness is an equivalent nodal stiffness computed as Ks = STFAC * B * V-3 for
solids, Ks = 0.5 * STFAC * E * t for shells.

In these equations, B is the Bulk Modulus, S is the segment area, and V is the volume of a
solid. There is no limitation to the value of stiffness factor (but a value larger than 1.0
can reduce the initial time step).

The interface stiffness is then K = max (STMIN, min (STMAX, K1)) with:

ISTF = 0, K1 = Km
ISTF = 2, K1 = 0.5 * (Km + Ks)
ISTF = 3, K1 = max (Km, Ks)
ISTF = 4, K1 = min (Km, Ks)
ISTF = 5, K1 = Km * Ks / (Km + Ks)
6. The gap is computed automatically (similar with IGAP = VAR on PCNTX7) for each impact
as gs + gm;

with:

gm - master element gap, with:


gm = t/2, t: thickness of the master element for shell elements.

gm = 0 for solid elements.

gs - slave node gap:


gs = 0 if the slave node is not connected to any element or is only connected to solid
or spring elements.

gs = t/2, t - largest thickness of the shell elements connected to the slave node.

element.

gm and gs are limited separately by GAPMAXm and GAPMAXs before the gap
computation.

7. The coefficients C1 - C6 are used to define a variable friction coefficient .

8. INACTI = 0 ignores the initial penetrations, but the contacts are not deleted, new
contact will be well detected once the penetrations are disappeared. INACTI = 5 is similar
to the one of interface type 7, but once the initial penetration is gone, the new contact
will be detected using not-adjusted gap (P0 is reset to zero).

9. IFRIC defines the friction model.

IFRIC = COUL – Coulomb friction with F T < FRIC * F N.

Altair Engineering OptiStruct 13.0 Reference Guide 1767

Proprietary Information of Altair Engineering


p, V
For IFRIC > 0 the friction coefficient is set by a function ( )

where, p is the pressure of the normal force on the master segment and V is the
tangential velocity of the slave node.

The following formulations are available:

IFRIC = GEN - Generalized viscous friction law

FRIC + C1 * p + C2 * V + C3 * p * v + C4 * p2 + C5 * v2

IFRIC = DARM - Darmstad law

= C1 * e(C 2V) * p2 + C3 * e(C 4V) * p + C5 * e(C 6V)

IFRIC = REN - Renard law

0 < V < C5

C5 < V < C6

C6 < V

where:

The first critical velocity Vcr1


second critical velocity Vcr2 (C5 < C6).

The static friction coefficient C1 and the dynamic friction coefficient C2, must be lower
than the maximum friction C3 (C1 < C3 and C2 < C3).

The minimum friction coefficient C4, must be lower than the static friction coefficient
C1 and the dynamic friction coefficient C2 (C4 < C1 and C4 < C2).

10. IFILT defines the method for computing the friction filtering coefficient. If IFILT NO,
the tangential friction forces are smoothed using a filter:

1768 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


F T = α * F'T + (1 - α) * F'T-1

where,

F T - Tangential force

F'T - Tangential force at time t

F'T-1 - Tangential force at time t-1

α - filtering coefficient

IFILT = SIMP – α = FFAC

IFILT = PER – α = 2 dt/FFAC, where dt/T = FFAC, T is the filtering period

IFILT = CUTF – α = 2 * FFAC * dt, where FFAC is the cutting frequency

11. IFORM selects two types of contact friction penalty formulation.

The viscous (total) formulation (IFORM = VISC) computes an adhesive force as:

F adh T

F T = min (µF N, F adh)

The stiffness (incremental) formulation (IFORM = STIFF) computes an adhesive force as:

F adh = F Told + ∆F T

∆F T = K * VT * dt

F Tnew = min (µF N, F adh)

12. When SENSID is defined for activation/deactivation of the interface, TSTART and TSTOP
are not taken into account.

13. When the contact type is the symmetric surface to surface, the output normal contact
forces in TH file are correctly calculated if the two surfaces are well separated.

14. IPEN0 = 0 excludes the initial auto-impacts in the same part (shell and solid elements
only). IPEN0 = 1 takes into account the initial auto-impacts in the same part, but in some
complex situations, wrong initial penetrations might be given.

15. For implicit test: Interface type24 is now only available with SMP. The default of ISTF will
be set to 4. The default INACTI will be set to -1 .

16. This card is represented as an extension to a PCONT property in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1769

Proprietary Information of Altair Engineering


PCOMP

Bulk Data Entry

PCOMP – Composite Laminate Property

Description

Defines the structure and properties of an n-ply composite laminate material.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC OMP PID Z0 NSM SB FT TREF GE LAM

MID1 T1 THETA1 SOUT1 MID2 T2 THETA2 SOUT2

MID3 T3 THETA3 SOUT3 etc.

DS

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC OMP 100 -0.5 1.E5 STRN 100.

120 0.2 0.0 YES 120 0.6 0.0 NO

120 0.2 0.0 YES

1.0

Field Contents

PID Unique composite property identification number.

No default (Integer > 0)

1770 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Z0 Real number or character input (Top/Bottom)

Real Number - It represents the distance from the shell element reference
plane to the bottom surface of the shell (Default = -0.5 * Thick, Thick
being the composite total thickness (Real or blank)).

Character Input - See comment 17

NSM Nonstructural mass per unit area.

No default (Real)

SB Allowable inter-laminar shear stress (shear stress in the bonding material).


Disregarded if blank or 0.0.

No default (Real > 0.0)

FT Failure theory code. If blank, no failure calculations are performed. The


following failure theory codes are supported:

HILL for Hill theory,

HOFF for Hoffman theory,

TSAI for Tsai-Wu theory,

STRN for Maximum Strain Theory.

See comments 13 through 15.

Default = no failure calculations are performed (HILL, HOFF, TSAI, or


STRN)

TREF Reference (stress free) temperature. See comment 1.

Default = 0.0 (Real)

GE Damping coefficient. See comments 10 and 11.

Default = 0.0 (Real)

LAM Laminate option. If blank, all plies must be specified and all stiffness
terms are developed. The following options are supported:

SYM: Only plies on the bottom half of the composite lay-up needs to be
specified. These plies are automatically symmetrically reflected to the top
half of the composite and given consecutive numbers from bottom to top.

Altair Engineering OptiStruct 13.0 Reference Guide 1771

Proprietary Information of Altair Engineering


Field Contents

MEM: All plies must be specified, but only membrane terms MID1 are
developed. Prescribed Z0 is ignored (assumed to be: -0.5* Thick).

BEND: All plies must be specified, but only bending terms MID2 are
developed. Prescribed Z0 is ignored (assumed to be: -0.5* Thick).

SMEAR: All plies must be specified, stacking sequence is ignored, and


MID1 is set equal to MID2 on the derived equivalent PSHELL, while MID3,
MID4, TS/T, and 12I/T**3 are set to zero. Prescribed Z0 is ignored
(assumed to be: -0.5* Thick).

SMEARZ0: All plies must be specified, stacking sequence is ignored. While


the laminate is still considered to be made of homogenized (smeared)
material, the effect of offset Z0 is taken into account. Hence, if Z0 is not
equal to -0.5*Thick, the equivalent PSHELL will include MID1, MID2 and
MID4. MID3 is still set to zero, that is no transverse shear deformation is
considered.

SMCORE: All plies must be specified. The last ply specifies core properties
and the previous plies specify face sheet properties. The face sheet
properties are calculated without regard for stacking sequence; half of the
total face sheet thickness is then placed on top of the core, and half is
placed on the bottom, to produce a symmetric laminate. Stiffness of the
core is ignored while its density is included in inertia calculations.
Prescribed Z0 is ignored (assumed to be: -0.5* Thick).

SYMEM: Only plies on the bottom half of the composite lay-up needs to
be specified. These plies are automatically symmetrically reflected to the
top half of the composite and given consecutive numbers from bottom to
top. Only membrane terms are developed for the full laminate. Prescribed
Z0 is ignored (assumed to be: -0.5* Thick).

SYBEND: Only plies on the bottom half of the composite lay-up needs to
be specified. These plies are automatically symmetrically reflected to the
top half of the composite and given consecutive numbers from bottom to
top. Only bending terms are developed for the full laminate. Prescribed
Z0 is ignored (assumed to be: -0.5* Thick).

SYSMEAR: Only plies on the bottom half of the composite lay-up needs to
be specified. These plies are automatically symmetrically reflected to the
top half of the composite and given consecutive numbers from bottom to
top. Stacking sequence is ignored, and MID1 is set equal to MID2 on the
derived equivalent PSHELL, while MID3, MID4, TS/T and 12I/T**3 are set
to zero. Prescribed Z0 is ignored (assumed to be: -0.5* Thick).

Default = blank, that is all plies must be specified (SYM, MEM, BEND,
SMEAR, SMCORE, SYMEM, SYBEND or SYSMEAR)

1772 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

MIDi Material IDs of individual plies. The plies are identified by consecutively
numbering them from 1 at the bottom layer. The MIDs must refer to
MAT1, MAT2, MAT4, MAT5, or MAT8 bulk data entries. If MIDi is not
specified, default is the last defined MIDi.

Default = last defined MIDi (Integer>0 or blank, except that MID1 must be
specified)

Ti Thicknesses of individual plies. If Ti is not specified, default is the last


defined Ti.

Default = last defined Ti (Real > 0.0 or blank, except that T1 must be
specified)

THETAi Orientation angle, in degrees, of the longitudinal direction of each ply


relative to the x-axis of the material coordinate system associated with a
given element. If no material coordinate system is prescribed for the
element, the angle is measured relative to side 1-2 of this element.

Default = 0.0 (Real or blank)

SOUTi Stress, Strain and Failure Index output request for individual plies. See
comments 2 and 3.

Default = NO (YES or NO)

DS Design switch. If non-zero (1.0), the elements associated with this


PCOMP data are included in the topology design volume or space.

Default = blank (Real = 1.0 or blank)

Comments

1. TREF specified on the PCOMP entry overrides reference temperatures given for individual
ply materials. If TREF is not specified (blank) on the PCOMP card, then all the ply
materials must have the same reference temperature.

2. Stress, Strain and Failure Index output for individual plies is activated by setting SOUTi to
YES for a given ply. In addition, the I/O Options CSTRESS (controlling Stress and Failure
Index output) and/or CSTRAIN (controlling Strain output) must be defined. Failure Index
output also requires that the FT and SB fields be defined and that stress/strain allowables
on the referenced materials are defined.

3. An additional piece of information available with ply results is "failure index for the
element," which is the maximum of failure indices for individual plies in this element. Note
that only the plies with SOUTi set to YES are considered in the evaluation of this
maximum.

Altair Engineering OptiStruct 13.0 Reference Guide 1773

Proprietary Information of Altair Engineering


4. If all plies specify zero transverse shear coefficients (G1Z, G2Z on MAT8 card, isotropic G
for MAT1, not available for MAT2), the in-plane shear modulus will be used to determine
transverse shear stiffness of the composite.

Note: If just one layer has a nonzero value specified for


transverse shear modulus, this substitution is not
being performed, and user-specified values are being
used for all plies.

5. The signs given to stress limits for compression and tension (ST, SC, for MAT1; Xt, Xc,
and so on for MAT8) are of no relevance. Absolute values are taken and used in the
appropriate context to calculate failure indices.

6. For com
bottom and top surfaces of the shell are produced.

Note: These shell stresses are calculated using


homogenized shell properties, and should be
interpreted with caution.

7.
This is because the membrane-bending coupling resulting from composite offset is not
included in the differential stiffness matrix. Hence, the preferred method of incorporating
offset in buckling analysis is the element offset ZOFFS.

8. Element GRID thicknesses cannot be defined for elements that reference PCOMP data.

9. Plies are listed from the bottom surface upwards, in respect to the element’s normal
direction. In the image below, (a) shows the stacking sequence for a non-symmetrical
laminate, and (b) shows the stacking sequence for a symmetrical laminate.

10. GE given on the PCOMP entry will be used for the element, and the values supplied on
material entries for individual plies are ignored. You are responsible for supplying the
equivalent damping value on the PCOMP entry.

11. To obtain the damping coefficient GE, multiply the critical damping ratio C/C0 by 2.0.

12. For convenience, element output for the SMEAR and SMCORE options includes both
homogenized shell stresses and individual ply stresses. However, because stacking
sequence is ignored in these options, individual ply stresses will only be valid in cases of

1774 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


pure membrane deformation.

13. Note that Hill’s failure theory does not differentiate between compressive and tensile
strength. Hence, while different values of respective strength limits are accepted, it is
still recommended that Xt is set to be equal to Xc and Yt is set to be equal to Yc when
this criteria is used. Xt and Xc are allowable tensile and compressive stresses in the
principle x direction of the material. Yt and Yc are allowable tensile and compressive
stresses in the principle y direction of the material.

14. Failure index calculation according to Maximum Strain Theory is based on mechanical
component of strain only, not on total strain. This is because only the mechanical strain
contributes to actual damage of the respective ply (pure thermal expansion produces no
damaging effects).

15. According to the formula, some failure criteria (for example, Tsai-Wu and Hoffman) would
produce a negative ply failure, depending on the problem.

16. If ‘PARAM, SRCOMPS, YES’ is added to the input file, strength ratios with respect to
designated failure theory are output for composite elements that have failure indices
requested.

17. The following two formats are permissible for the Z0 field:

Real Number:

It represents the distance from the shell element reference plane to the bottom surface
of the shell (Default = -0.5 * Thick, Thick being the composite total thickness (Real or
blank)).

Surface:

Top:

The shell reference plane, the plane defined by the grid points, and the top surface of the
shell are coplanar.

This makes the effective "Real" Z0 value equal to the composite total thickness (-1.0 *
Thick). See Figure 1.

Figure 1: Top option for Z0

Bottom:

The shell reference plane, the plane defined by the grid points, and the bottom surface of
the shell are coplanar.

Altair Engineering OptiStruct 13.0 Reference Guide 1775

Proprietary Information of Altair Engineering


This makes the effective "Real" Z0 value equal to 0. See Figure 2.

Figure 2: Bottom option for Z0

Automatic offset control is available in composite free-size and sizing optimization where
the specified offset values are automatically updated based on thickness changes.

18. This card is represented as a property in HyperMesh.

1776 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PCOMPG

Bulk Data Entry

PCOMPG – Composite Laminate Property

Description

Defines the structure and properties of a composite laminate material, allowing for global ply
identification.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC OMPG PID Z0 NSM SB FT TREF GE LAM

GPLYID1 MID1 T1 THETA1 SOUT1

GPLYID2 MID2 T2 THETA2 SOUT2

… … … … …

DS

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC OMP 100 -0.5 1.E5 STRN 100.

101 120 0.2 0.0 YES

2 120 0.6 0.0 NO

103 120 0.2 0.0 YES

1.0

Altair Engineering OptiStruct 13.0 Reference Guide 1777

Proprietary Information of Altair Engineering


Field Contents

PID Unique composite property identification number.

No default (Integer > 0)

Z0 Real number or character input (Top/Bottom)

Real Number - It represents the distance from the shell element


reference plane to the bottom surface of the shell (Default = -0.5 *
Thick, Thick being the composite total thickness (real or blank)).

Character Input - See comment 18.

NSM Nonstructural mass per unit area.

No default (Real)

SB Allowable interlaminar shear stress (shear stress in the bonding


material). Disregarded if blank or 0.0.

No default (Real > 0.0)

FT Failure theory code. If blank, no failure calculations are performed.


The following failure theory codes are supported:

HILL for Hill theory,

HOFF for Hoffman theory,

TSAI for Tsai-Wu theory,

STRN for Maximum Strain Theory.

See comments 14 through 16.

Default = no failure calculations are performed (HILL, HOFF, TSAI, or


STRN)

TREF Reference (stress free) temperature. See comment 1.

Default = 0.0 (Real)

GE Damping coefficient. See comments 10 and 11.

Default = 0.0 (Real)

1778 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

LAM Laminate option. If blank, all plies must be specified and all stiffness
terms are developed. The following options are supported:

MEM: All plies must be specified, but only membrane terms MID1 are
developed. Prescribed Z0 is ignored (assumed to be: -0.5* Thick).

BEND: All plies must be specified, but only bending terms MID2 are
developed. Prescribed Z0 is ignored (assumed to be: -0.5* Thick).

SMEAR: All plies must be specified, stacking sequence is ignored, and


MID1 is set equal to MID2 on the derived equivalent PSHELL, while
MID3, MID4, TS/T, and 12I/T**3 are set to zero. Prescribed Z0 is
ignored (assumed to be: -0.5* Thick).

SMEARZ0: All plies must be specified, stacking sequence is ignored.


While the laminate is still considered to be made of homogenized
(smeared) material, the effect of offset Z0 is taken into account.
Hence, if Z0 is not equal to -0.5*Thick, the equivalent PSHELL will
include MID1, MID2 and MID4. MID3 is still set to zero, that is no
transverse shear deformation is considered.

SMCORE: All plies must be specified. The last ply specifies core
properties and the previous plies specify face sheet properties. The
face sheet properties are calculated without regard for stacking
sequence; half of the total face sheet thickness is then placed on top
of the core, and half is placed on the bottom, to produce a symmetric
laminate. Stiffness of the core is ignored while its density is included in
inertia calculations. Prescribed Z0 is ignored (assumed to be: -0.5*
Thick).

SYMEM: Only plies on the bottom half of the composite lay-up needs to
be specified. These plies are automatically symmetrically reflected to
the top half of the composite and given consecutive numbers from
bottom to top. Only membrane terms are developed for the full
laminate. Prescribed Z0 is ignored (assumed to be: -0.5* Thick).

SYBEND: Only plies on the bottom half of the composite lay-up needs
to be specified. These plies are automatically symmetrically reflected
to the top half of the composite and given consecutive numbers from
bottom to top. Only bending terms are developed for the full laminate.
Prescribed Z0 is ignored (assumed to be: -0.5* Thick).

SYSMEAR: Only plies on the bottom half of the composite lay-up needs
to be specified. These plies are automatically symmetrically reflected
to the top half of the composite and given consecutive numbers from
bottom to top. Stacking sequence is ignored, and MID1 is set equal to
MID2 on the derived equivalent PSHELL, while MID3, MID4, TS/T and
12I/T**3 are set to zero. Prescribed Z0 is ignored (assumed to be: -
0.5* Thick).

Altair Engineering OptiStruct 13.0 Reference Guide 1779

Proprietary Information of Altair Engineering


Field Contents

Default = blank, that is all plies must be specified (SYM, MEM, BEND,
SMEAR, SMCORE, SYMEM, SYBEND or SYSMEAR)

GPLYID# Global Ply identification number, See comment 12.

No default (Integer > 0)

MID# Material IDs of individual plies. The plies are identified by consecutively
numbering them from 1 at the bottom layer. The MIDs must refer to
MAT1, MAT2, MAT4, MAT5, or MAT8 bulk data entries. If MID# is not
specified, default is the last defined MID#.

Default = last defined MID# (Integer > 0 or blank, except that MID1
must be specified)

T# Thicknesses of individual plies. If T# is not specified, default is the last


defined T#.

Default = last defined T# (Real > 0.0 or blank, except that T1 must be
specified)

THETA# Orientation angle, in degrees, of the longitudinal direction of each ply


relative to the x-axis of the material coordinate system associated with
a given element. If no material coordinate system is prescribed for the
element, the angle is measured relative to side 1-2 of this element.

Default = 0.0 (Real or blank)

SOUT# Stress and failure index output request for individual plies. See
comments 2 and 3.

Default = NO (YES or NO)

DS Design switch. If non-zero (1.0), the elements associated with this


PCOMP data are included in the topology design volume or space.

Default = blank (Real = 1.0 or blank)

Comments

1. TREF specified on the PCOMPG entry overrides reference temperatures given for individual
ply materials. If TREF is not specified (blank) on the PCOMPG card, then all the ply
materials must have the same reference temperature.

2. For SOUTi to take effect, CSTRESS must be requested in the I/O options section of the
input deck. Individual ply results will be available in addition to shell stresses and strains

1780 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


based on the homogenized composite properties.

3. An additional piece of information available with ply results is "failure index for the
element", which is the maximum of failure indices for individual plies in this element. Note
that only the plies with SOUTi set to YES are considered in the evaluation of this
maximum.

4. If all plies specify zero transverse shear coefficients (G1Z, G2Z on MAT8 card, isotropic G
for MAT1, not available for MAT2), the in-plane shear modulus will be used to determine
transverse shear stiffness of the composite.

Note: If just one layer has a nonzero value specified for


transverse shear modulus, this substitution is not
being performed, and user-specified values are being
used for all plies.

5. The signs given to stress limits for compression and tension (ST, SC, for MAT1; Xt, Xc,
and so on for MAT8) are of no relevance. Absolute values are taken and used in the
appropriate context to calculate failure indices.

6.
bottom and top surfaces of the shell are produced.

Note: These shell stresses are calculated using


homogenized shell properties, and should be
interpreted with caution.

7.
This is because the membrane-bending coupling resulting from composite offset is not
included in the differential stiffness matrix. Hence, the preferred method of incorporating
offset in buckling analysis is the element offset ZOFFS.

8. Element GRID thicknesses cannot be defined for elements that reference PCOMPG data.

9. Plies are listed from the bottom surface upwards, in respect to the element’s normal
direction. The image below shows the stacking sequence for a non-symmetrical
laminate.

10. GE given on the PCOMP entry will be used for the element, and the values supplied on
material entries for individual plies are ignored. You are responsible for supplying the
equivalent damping value on the PCOMPG entry.

Altair Engineering OptiStruct 13.0 Reference Guide 1781

Proprietary Information of Altair Engineering


11. To obtain the damping coefficient GE, multiply the critical damping ratio C/C0 by 2.0.

12. The global ply identification number must be unique with respect to other plies in the
entry.

13. For convenience, element output for the SMEAR and SMCORE options includes both
homogenized shell stresses and individual ply stresses. However, because stacking
sequence is ignored in these options, individual ply stresses will only be valid in cases of
pure membrane deformation.

14. Note that Hill’s failure theory does not differentiate between compressive and tensile
strength. Hence, while different values of respective strength limits are accepted, it is
still recommended that Xt is set to be equal to Xc and Yt is set to be equal to Yc when
this criteria is used. Xt and Xc are allowable tensile and compressive stresses in the
principle x direction of the material. Yt and Yc are allowable tensile and compressive
stresses in the principle y direction of the material.

15. Failure index calculation according to Maximum Strain Theory is based on mechanical
component of strain only, not on total strain. This is because only the mechanical strain
contributes to actual damage of the respective ply (pure thermal expansion produces no
damaging effects).

16. According to the formula, some failure criteria (for example, Tsai-Wu and Hoffman) would
produce a negative ply failure, depending on the problem.

17. If ‘PARAM, SRCOMPS, YES’ is added to the input file, strength ratios with respect to
designated failure theory are output for composite elements that have failure indices
requested.

18. The following two formats are permissible for the Z0 field:

Real Number:

It represents the distance from the shell element reference plane to the bottom surface
of the shell (Default = -0.5 * Thick, Thick being the composite total thickness (Real or
blank)).

Surface:

Top:

The shell reference plane, the plane defined by the grid points, and the top surface of the
shell are coplanar.

This makes the effective "Real" Z0 value equal to the composite total thickness (-1.0 *
Thick). See Figure 1.

1782 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Figure 1: Top option for Z0

Bottom:

The shell reference plane, the plane defined by the grid points, and the bottom surface of
the shell are coplanar.

This makes the effective "Real" Z0 value equal to 0. See Figure 2.

Figure 2: Bottom option for Z0

Automatic offset control is available in composite free-size and sizing optimization where
the specified offset values are automatically updated based on thickness changes.

19. This card is represented as a property in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1783

Proprietary Information of Altair Engineering


PCOMPP

Bulk Data Entry

PCOMPP – Composite Laminate Property for Ply-Based Composite Definition

Description

Defines the properties of a composite laminate material used in ply-based composite definition.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC OMPP PID Z0 NSM SB FT TREF GE

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC OMPP 1 -0.1 HILL 20

Field Contents

PID Unique composite property identification number.

No default (Integer > 0)

Z0 Real number or character input (Top/Bottom)

Real Number - It represents the distance from the shell element


reference plane to the bottom surface of the shell (Default = -0.5 *
Thick, Thick being the composite total thickness (Real or blank)).

Character Input - See comment 12.

NSM Nonstructural mass per unit area.

No default (Real)

SB Allowable interlaminar shear stress (shear stress in the bonding


material). Disregarded if blank or 0.0.

No default (Real > 0.0)

1784 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

FT Failure theory code. If blank, no failure calculations are performed.


The following failure theory codes are supported:

HILL for Hill theory,

HOFF for Hoffman theory,

TSAI for Tsai-Wu theory,

STRN for Maximum Strain Theory.

See comment 10.

Default = no failure calculations are performed (HILL, HOFF, TSAI or


STRN).

TREF Reference (stress free) temperature. See comment 2.

Default = 0.0 (Real)

GE Damping coefficient. See comments 6 and 7.

Default = 0.0 (Real)

Comments

1. The PCOMPP card is used in combination with the STACK and PLY cards to create
composite properties through the ply-based definition.

2. TREF specified on the PCOMPP entry overrides reference temperatures given for individual
ply materials. If TREF is not specified (blank) on the PCOMPP card, then all the ply
materials must have the same reference temperature.

3.
bottom and top surfaces of the shell are produced.

Note: These shell stresses are calculated using


homogenized shell properties, and should be
interpreted with caution.

4.
correct. This is because the membrane-bending coupling resulting from composite offset
is not included in the differential stiffness matrix. Hence, the preferred method of
incorporating offset in buckling analysis is the element offset ZOFFS.

5. Element GRID thicknesses cannot be defined for elements that reference PCOMPP data.

6. GE given on the PCOMPP entry will be used for the element, and the values supplied on
material entries for individual plies are ignored. You are responsible for supplying the
equivalent damping value on the PCOMPP entry.

Altair Engineering OptiStruct 13.0 Reference Guide 1785

Proprietary Information of Altair Engineering


7. To obtain the damping coefficient GE, multiply the critical damping ratio C/C0 by 2.0.

8. Note that Hill’s failure theory does not differentiate between compressive and tensile
strength. Hence, while different values of respective strength limits are accepted, it is
still recommended that Xt is set to be equal to Xc and Yt is set to be equal to Yc when
this criteria is used. Xt and Xc are allowable tensile and compressive stresses in the
principle x direction of the material. Yt and Yc are allowable tensile and compressive
stresses in the principle y direction of the material.

9. Failure index calculation according to Maximum Strain Theory is based on mechanical


component of strain only, not on total strain. This is because only the mechanical strain
contributes to actual damage of the respective ply (pure thermal expansion produces no
damaging effects).

10. According to the formula, some failure criteria (for example, Tsai-Wu and Hoffman) would
produce a negative ply failure, depending on the problem.

11. If ‘PARAM, SRCOMPS, YES’ is added to the input file, strength ratios with respect to
designated failure theory are output for composite elements that have failure indices
requested.

12. The following two formats are permissible for the Z0 field:

Real Number:

It represents the distance from the shell element reference plane to the bottom surface
of the shell (Default = -0.5 * Thick, Thick being the composite total thickness (Real or
blank)).

Surface:

Top:

The shell reference plane, the plane defined by the grid points, and the top surface of the
shell are coplanar.

This makes the effective "Real" Z0 value equal to the composite total thickness (-1.0 *
Thick). See Figure 1.

Figure 1: Top option for Z0

Bottom:

The shell reference plane, the plane defined by the grid points, and the bottom surface of

1786 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


the shell are coplanar.

This makes the effective "Real" Z0 value equal to 0. See Figure 2.

Figure 2: Bottom option for Z0

Automatic offset control is available in composite free-size and sizing optimization where
the specified offset values are automatically updated based on thickness changes.

13. This card is represented as a property in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1787

Proprietary Information of Altair Engineering


PCOMPX

Bulk Data Entry

PCOMPX – Optional Composite Laminate Property Extension for Geometric Nonlinear Analysis

Description

Defines additional composite laminate properties for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC OMPX PID ISHELL ISH3N ISMSTR HM HF HR

DM DN ITHIC K IPLAS

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC OMP 73

120 0.2 0.0 YES 120 0.6 45.0 YES

PC OMPX 73 24

Field Contents

PID Property ID of the associated PSHELL. See comment 1.

No default (Integer > 0)

ISHELL Flag for CQUAD4 element formulation.

1 - Q4, visco-elastic hourglass modes orthogonal to deformation and rigid


modes (Belytschko)
2 - Q4, visco-elastic hourglass without orthogonality (Hallquist)
3 - Q4, elastic-plastic hourglass with orthogonality

1788 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

4 - Q4 with improved type 1 formulation (orthogonalization for warped


elements)
12 - QBAT or DKT18 shell formulation
24 - QEPH shell formulation

Default as defined by XSHLPRM (Integer)

ISH3N Flag for CTRIA3 element formulation.

1 - Standard triangle (C0)


2 - Standard triangle (C0) with modification for large rotation
30 - DKT18
31 - DKT_S3

Default as defined by XSHLPRM (Integer)

ISMSTR Flag for shell small strain formulation.

1 - Small strain from time = 0


2 - Full geometric non-linearity with optional small strain formulation
activation by time step XSTEP, TYPEi = SHELL, TSCi = CST
3 - Alternative small strain formulation from time = 0 (ISHELL =2 only).
4 - Full geometric non-linearity (Time step limit has no effect)

Default as defined by XSHLPRM (Integer)

HM Shell membrane hourglass coefficient (ISHELL = 1, 2, 3, and 4 only).

Default = 0.01 (Real, 0.0 < HM < 0.05)

Except ISHELL = 3: Default = 0.1 (Real)

HF Shell out of plane hourglass coefficient (ISHELL = 1, 2, 3, and 4 only).

Default = 0.01 (Real, 0.0 < HF < 0.05)

HR Shell rotation hourglass coefficient (ISHELL = 1, 2, 3, and 4 only).

Default = 0.01 (Real, 0.0 < HR < 0.05)

Except ISHELL = 3: Default = 0.1 (Real)

DM Shell membrane damping (with MATX27, MATX36 only).

Default: See comment 7 (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 1789

Proprietary Information of Altair Engineering


Field Contents

DN Shell numerical damping (ISHELL = 12, 24; ISH3N = 30 only).

Default: See comment 8 (Real)

ITHICK Flag for shell resultant stresses calculation.

CONST - Thickness is constant


VAR - Thickness change is taken into account

Default as defined by XSHLPRM (CONST or VAR)

IPLAS Flag for shell plane stress plasticity (with MATX27 only).

RAD - Radial return


NEWT - Iterative projection with 3 Newton iterations

Default as defined by XSHLPRM (RAD or NEWT)

Comments

1. The property identification number must be that of an existing PCOMP, PCOMPG, or


PCOMPP bulk data entry. Only one PCOMPX property extension can be associated with a
particular PCOMP, PCOMPG, or PCOMPP.

2. PCOMPX is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. Q4: Original 4 node OptiStruct shell with hourglass perturbation stabilization.


QEPH: Formulation with physical hourglass stabilization for general use.
QBAT: Modified BATOZ Q4 24 shell with 4 Gauss integration points and reduced
integration for in-plane shear. No hourglass control is needed for this shell.
DKT18: BATOZ DKT18 thin shell with 3 Hammer integration points.

4. If the small strain option (ISMSTR) is set to 1 or 3, engineering strain and stress are
used; otherwise they are true strain and stress.

5. For ITHICK = VAR it is recommended to use IPLAS = NEWT.

6. If ITHICK = VAR or IPLAS = NEWT, the small strain option is automatically deactivated.

7. Defaults for DM:

Material Element type ISHELL/ISH3N Default

MATX27 except QEPH, QBAT except 12, 24 5%

QEPH 24 1.5%

QBAT 12 0%

1790 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Material Element type ISHELL/ISH3N Default

MATX36 except QEPH except 24 0%

QEPH 24 1.5%

8. Defaults for DN:

Element ISHELL/ Default Usage


type ISH3N

QBAT 12 0.1% All stress terms, except


transverse shear

QEPH 24 1.5% Hourglass stress

DKT18 12/30 0.01% Membrane stress only

9. This card is represented as extension to a PCOMP, PCOMPG, and PCOMPP property in


HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1791

Proprietary Information of Altair Engineering


PCONT

Bulk Data Entry

PCONT – Contact Property

Description

Defines properties of CONTACT interface.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC ONT PID GPAD STIFF MU1 MU2 C LEARANC E

FRIC ESL

Examples

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC ONT 34 0.3 0.25

Enforced stick condition:

PC ONT 34 STIC K

Field Contents

PID Property identification number.

No default (Integer > 0)

GPAD “Padding” of the interface to account for additional layers, such as shell
thickness. This value is subtracted from the contact gap opening as
calculated from the location of nodes. See comment 1.

Default = THICK (Real, NONE or THICK)

1792 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

STIFF Relative stiffness of contact interface. See comment 2.

Default = AUTO (AUTO, SOFT, HARD or Real > 0.0)

MU1 Coefficient of static friction ( s). See comments 3 and 4.

Default = 0.0 (Real > 0.0 or STICK or FREEZE)

MU2 Coefficient of kinetic friction ( k). (Ignored in linear analysis).

Default = MU1 (0.0 < Real < MU1)

CLEARANCE Prescribed initial gap opening between master and slave, irrespective of
the actual distance between the nodes. See comment 11.

Default = not prescribed. (Real or blank).

FRICESL Frictional elastic slip – distance of sliding up to which the frictional


transverse force increases linearly with slip distance. Specified in
physical distance units (similar to U0 and GPAD). See Comment 7.

• Non-zero value or blank activates respective friction model based


on Elastic Slip Distance.
• Zero value activates friction model based on fixed transverse
stiffness KT.
Default = AUTO (Real > 0.0 or AUTO)

Comments

1. The initial contact gap opening is calculated automatically based on the relative location
of slave and master nodes (in the original, undeformed mesh). To account for additional
material layers covering master and slave objects, the GPAD entry can be used. GPAD
option THICK automatically accounts for shell thickness on both sides of the contact
interface (this also includes the effects of shell element offset ZOFFS or composite offset
Z0).

2. Option STIFF=AUTO determines the value of normal stiffness for each contact element
using the stiffness of surrounding elements. Additional options SOFT and HARD create
respectively softer or harder penalties. SOFT can be used in cases of convergence
difficulties and HARD can be used if undesirable penetration is detected in the solution.

3. Prescribing MU1=STICK is interpreted in OptiStruct as an enforced stick condition – such


contact interfaces will not enter the sliding phase. Of course, the enforced stick only
applies to contacts that are closed. Note that, in order to effectively enforce the stick
condition, frictional offset may need to be turned off (See comment 8).

4. Prescribing MU1=FREEZE enforces zero relative motion on the contact surface – the
contact gap opening remains fixed at the original value and the sliding distance is zero.
Also, rotations at the slave node are matched to the rotations of the master patch. The

Altair Engineering OptiStruct 13.0 Reference Guide 1793

Proprietary Information of Altair Engineering


FREEZE condition applies to all respective contact elements, no matter whether open or
closed (hence, GPAD is of no relevance in this case). Also, this condition is effective
irrespective of the frictional offset setting.

If FRIC is not explicitly defined on the PCONTX/PCNTX# entries, the MU1 value on the
CONTACT or PCONT entry is used for FRIC in the /INTER entries for Geometric Nonlinear
Analysis. Otherwise, FRIC on PCONTX/PCNTX# overwrites the MU1 value on CONTACT/
PCONT.

5. The CONTACT element force-displacement behavior is different in linear and nonlinear


analysis (see Nonlinear Gap and CONTACT Analysis for more information on nonlinear
solutions). In linear analysis, the contact stiffness is constant and depends on the initial
contact gap opening U0 as calculated from the positions of Slave and Master (and
considering padding GPAD). Note that for open contact elements, a very small stiffness
value of KB =10-14 *STIFF is used to avoid numerical singularities.

C ONTAC T element force deflection curve for linear analysis

The CONTACT force displacement behavior in nonlinear analysis is illustrated in the figure
below. While the contact is open, its normal stiffness is essentially zero (a small value of
KB =10-14 *STIFF is used to avoid singularities). When the contact element closes, the
stiffness becomes STIFF.

1794 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


C ONTAC T element force deflection curve for nonlinear analysis

6. When contact is open, there is no transverse stiffness. When the contact is closed,
friction is activated and the contact has stiffness KT=mu1*STIFF in the transverse
direction (KT=0.1*STIFF in case of STICK). This acts as a linear spring in linear solution
sequences. For nonlinear solution sequences, frictional force increases with sliding
distance in proportion to KT until it reaches static friction force MU1 * Fx, Fx being the
normal force in the contact element. With further transverse deformation, friction
becomes kinetic and the friction force is MU2 * Fx. See the figure below for a one-
dimensional illustration.

C ONTAC T element frictional behavior in nonlinear analysis

Note that the nonlinear contact element's force-displacement behavior may produce
negative contributions to the compliance of the structure. As an example, when slave
and master bodies have initial overlap and the contact releases elastic energy during the
solution.

7. Effective in Release 12.0, two models of friction are available in nonlinear analysis:

(a) Model based on fixed slope KT (previously existing),

Altair Engineering OptiStruct 13.0 Reference Guide 1795

Proprietary Information of Altair Engineering


(b) Model based on Elastic Slip Distance FRICESL (introduced in v12.0 and current
default).

This latter model typically shows better performance in solution of frictional problems
thanks to more stable handling of transitions from stick to slip. Key differences between
the two available models are illustrated in the figure below (F 1 and F 2 represent two
different values of normal force F x ):

C omparison of the two available friction models for contact elements.

Model (a), based on fixed stiffness KT, is relatively simple, yet has certain drawback in
modeling nonlinear friction. Namely, in Coulomb friction the frictional resistance depends
upon normal force. Using fixed KT will predict different range of stick/slip boundary for
different normal forces, and thus may qualify the same configuration as stick or slip,
depending on normal force.
Model (b), based on Elastic Slip Distance, provides unique identification of stick or slip
and generally performs better in solution of problems with friction. This model does
require prescribing elastic slip distance FRICESL – for contact interfaces this value is
determined automatically as 0.5% of typical element size on all Master contact
surfaces.

The model (b), which is currently the default, is recommended for solution of nonlinear
problems with friction. For backwards compatibility, the model based on fixed KT can be
activated by prescribing FRICESL=0 on PCONT or CONTPRM card.

8. The model of friction in OptiStruct is relatively simple. The frictional force is always
directed back to the point where the slave and master first came into contact (changed
status from open to closed). Its location is estimated using proportional interpolation
between the current position and the last converged solution before penetration.
OptiStruct CONTACT should not be used for modeling frictional problems with complex
deformation paths and changing sliding directions.

9. The presence of friction can introduce moment loadings and counter-intuitive results into
the problem by way of frictional offset. The reason for this is that, for contact elements
with non-zero length (distance between slave node and master segment), the actual
location of the contact interface is presumed to be in the middle of the contact element’s
length (see figure below).

1796 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


C ONTAC T presumed contact surface

The frictional forces act along this contact surface. Transferring these forces to the
slave and master objects requires an offset operation that produces both forces and
moments at slave and master. Similarly, the sliding distance at the contact interface is a
result of nodal displacements and rotations of the slave node and master segment (see
figure below).

C ONTAC T sliding with friction

Master segments, which consist of several nodes, can effectively resist these offset
forces and moments. However, for slave bodies that do not support moments (nodes of
solid elements, for example), this offset may render friction ineffective because the free
rotations at slave nodes offer no effective resistance to friction. With the stick condition
formally satisfied, for example, slave and master can move relative to each other (see
figure below).

Altair Engineering OptiStruct 13.0 Reference Guide 1797

Proprietary Information of Altair Engineering


C ONTAC T stick (zero sliding distance)

In practice, for contact interfaces that are initially open, AUTOSPC will effectively fix
respective unsupported rotations. However, for contacts that are initially closed (for
example, pre-penetrating contact with MORIENT=NORMAL) the frictional terms will
prevent AUTOSPC from being effective. Hence, respective SPC on rotations need to be
applied manually to respective slave nodes.

Effective in the Release 12.0, to avoid such counter-intuitive behavior, the frictional
offset operation is by default turned off if the model involves friction or stick and contains
at least one nonlinear subcase (of NLSTAT type). (Note that for consistency, this affects
both linear and nonlinear contact elements.) This produces more intuitive results with
friction. However, it may violate the rigid body balance of the body.

Note: FREEZE condition is enforced using a special


formulation where the above caveat does not apply
and the offset operation is always applied.

The above default setting can be changed via the GAPOFFS command on the GAPPRM
card.

10. The presence of friction, due to its strongly nonlinear, non-conservative nature, may
cause difficulties in nonlinear convergence, especially when sliding is present. If frictional
resistance is essential to the solution of the problem and convergence problems are
encountered, enforcing the stick condition (by prescribing KT>0 and MU=0) may be a
viable solution that will often result in better convergence than with Coulomb friction.
Note however, that this only applies to problems in which minimal sliding is expected. In
the case of larger sliding motions, the stick condition may lead to divergence through a
"tumbling" mode.

11. Prescribing CLEARANCE overrides the default contact behavior of calculating initial gap
opening from the actual distance between Slave and Master. CLEARANCE now becomes
the distance that Slave and Master have to move towards each other in order to close
the contact. Negative value of CLEARANCE means that the bodies have initial pre-
penetration.

1798 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Warning: When prescribing CLEARANCE, it is important to
correctly restrict the contact zones and pick
search distance SRCHDIS so that only desired
Slave-Master pairs are involved. With
prescribed CLEARANCE, all contact elements
created on a given interface, even those
where Slaves are geometrically distant from
the respective Master surface, will be
considered to be at prescribed initial gap and
participate in resolving the contact condition.

Note: CLEARANCE cannot be prescribed together with (non-


zero) GPAD. Blank GPAD field in presence of
CLEARANCE is interpreted as NONE.

12. This card is represented as a property in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1799

Proprietary Information of Altair Engineering


PCONTHT

Bulk Data Entry

PCONTHT – Define Conductivity for Contact in Heat Transfer Analysis

Description

Defines conductivity for CONTACT elements in heat transfer analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC ONTHT PID KC KO TPID TC ID

Examples

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC ONTHT 2 1E6

Contact with automatic determination of KC:

PC ONTHT 2 AUTO

Minimum data required to prescribe pressure based conductivity for contact:

PC ONTHT 2 10

Clearance and pressure based conductivity for contact (see comments 3 and 4):

PC ONTHT 2 1E6 10 20

Field Contents

PID Property identification number. Must match with a PID of a PCONT bulk
data entry. See comment 1.

1800 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

No default (Integer > 0)

KC Conductivity for the closed contact. See comment 2.

KO Conductivity for the open contact. See comment 2.

Default = 10-14 * KC (Real > 0.0) This default is also set when KO =0.

TPID Identification number of a TABLED# entry. This table specifies


conductivity based on contact pressure. See comments 2, 3, and 4.

Default = 0 (Integer > 0)

TCID Identification number of a TABLED# entry. This table specifies


conductivity based on contact clearance. See comments 2, 3, and 4.

Default = 0 (Integer > 0)

Comments

1. PCONTHT provides heat transfer conductivity for CONTACT element. PCONTHT must
match PID with an existing PCONT.

2. KC and KO represent conductivity values for closed and open contacts. Theoretically,
while higher conductivity values enforce a perfect conductor, excessively high values may
cause poor conditioning of the conductivity matrix. If any such symptoms are observed,
it may be beneficial to reduce the value of conductivity, or use conductivity based
contact clearance and pressure.

To facilitate reasonable values for KC, automatic calculation is supported, specifically:

Option KC=AUTO determines the value of KC for each contact element using the
conductivity of surrounding elements.
3. TPID points to a TABLED# entry that specifies conductivity based on contact pressure.
TPID overrides KC.

4. TCID points to a TABLED# entry that specifies contact based on contact clearance. TCID
overrides KO. TPID can be specified together with TCID. When TPID is specified together
with TCID, conductivity is determined from the table with TCID for open contact, and
from the table with TPID for closed contact.

5. PCONTHT is not supported for surface-to-surface contact (DISCRET=S2S on CONTACT/


TIE).

6. Thermal-structural analysis problems involving contact are fully coupled since contact/gap
status changes thermal conductivity. Refer to Contact-based Thermal Analysis in the
User’s Guide for more information.

7. This card is represented as a property in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1801

Proprietary Information of Altair Engineering


PCONTX

Bulk Data Entry

PCONTX – Extended CONTACT Property for Geometric Nonlinear Analysis

Description

Defines properties of a CONTACT interface for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC ONTX PID STFAC FRIC GAP IDEL INAC TI C TYPE

TSTART TEND

ISYM IEDGE FANG IGAP ISTF STIF1 STMIN STMAX

VISS VISF BMULT IBC MULTIMP

IFRIC IFORM IFILT FFAC

C1 C2 C3 C4 C5 C6

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC ONT 34

PC ONTX 34

Field Contents

PID Property identification number of the associated PCONT.

No default (Integer > 0)

1802 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

STFAC Interface stiffness scale factor.

Default as defined by CONTPRM (Real > 0)

FRIC Coulomb friction.

Default as defined by CONTPRM (Real > 0)

GAP Gap for impact activation (See comments 4 and 6).

Default as defined by CONTPRM (Real > 0)

IDEL Flag for node and segment deletion.

Default as defined by CONTPRM (Integer = 0, …, 2)

0 - No deletion.

1 - When all the elements (shells, solids) associated to one segment are
deleted, the segment is removed from the master side of the interface.
Additionally, non-connected nodes are removed from the slave side of
the interface.

2 - When a shell or a solid element is deleted, the corresponding


segment is removed from the master side of the interface. Additionally,
non-connected nodes are removed from the slave side of the interface.

INACTI Flag for handling of initial penetrations (See comment 8).

Default as defined by CONTPRM (Integer = 0, …, 5)

0 - No action.
1 - Deactivation of stiffness on nodes.
2 - Deactivation of stiffness on elements.
3 - Change slave node coordinates to avoid small initial penetrations.
4 - Change master node coordinates to avoid small initial penetrations.
5 - Gap is variable with time but initial gap is slightly de-penetrated as
follows:

gap0 = gap - P0 – 0.05*(gap - P0 )

Valid in explicit analysis: 0, 1, 2, 3 and 5.

Valid in implicit analysis: 0, 3 and 4.

Invalid entries are ignored.

CTYPE Implicit contact type.

Default = TYPE7 (Character = TYPE5, TYPE7)

Altair Engineering OptiStruct 13.0 Reference Guide 1803

Proprietary Information of Altair Engineering


Field Contents

TSTART Start time

Default = 0.0 (Real > 0)

TEND Time for temporary deactivation.

Default = 1030 (Real > 0)

The following entries are relevant for explicit analysis only.

ISYM Flag for symmetric contact.

Default as defined by CONTPRM (Character = SYM, UNSYM)

SYM – Symmetric contact.


UNSYM – Master-slave contact.

If SSID defines a grid set, the contact is always a master-slave contact.

IEDGE Flag for edge generation from slave and master surfaces.

Default as defined by CONTPRM (Character = NO, ALL, BORD, FEAT)

NO – No edge generation.
All – All segment edges are included.
BORD – External border of slave and master surface is used.
FEAT – External border as well as features defined by FANG are used.

FANG Feature angle for edge generation (Only with IEDGE = FEAT).

Default as defined by CONTPRM (Real > 0)

IGAP Flag for gap definition.

Default as defined by CONTPRM (Character = CONST, VAR)

CONST - Gap is constant and equal to GAP (See comment 6).

VAR - Gap is variable (in space, not in time) according to the


characteristics of the impacting surfaces and nodes (See comment 7).

ISTF Flag for stiffness definition (See comment 5).

Default as defined by CONTPRM (Integer = 0, …, 5)

0 - The stiffness is computed according to the master side


characteristics.
1 - STIF1 is used as interface stiffness.
2, 3, 4 and 5 - The interface stiffness is computed from both master and
slave characteristics.

1804 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

STIF1 Interface stiffness (Only with ISTF = 1)

Default = 0.0 (Real > 0)

STMIN Minimum stiffness (Only with ISTF > 1).

Default as defined by CONTPRM (Real > 0)

STMAX Maximum stiffness (Only with ISTF > 1).

Default as defined by CONTPRM (Real > 0)

IBC Flag for deactivation of boundary conditions at impact applied to the


slave grid set.

Default as defined by CONTPRM (Character = X, Y, Z, XY, XZ, YZ, XYZ)

MULTIMP Maximum average number of impacted master segments per slave node

Default = 4 for SMP; 12 for SPMD (Integer > 0)

VISS Critical damping coefficient on interface stiffness.

Default as defined by CONTPRM (Real > 0)

VISF Critical damping coefficient on interface friction.

Default as defined by CONTPRM (Real > 0)

BMULT Sorting factor. Can be used to speed up the sorting algorithm. Is


machine-dependent.

Default as defined by CONTPRM (Real > 0)

IFRIC Friction formulation flag (See comment 8).

Default as defined by CONTPRM (Character = COUL, GEN, DARM, REN)

COUL - Static Coulomb friction law.


GEN - Generalized viscous friction law.
DARM - Darmstad friction law.
REN - Renard friction law.

IFORM Type of friction penalty formulation (See comment 9).

Default as defined by CONTPRM (Character = VISC, STIFF)

VISC - Viscous (total) formulation.


STIFF - Stiffness (incremental) formulation.

Altair Engineering OptiStruct 13.0 Reference Guide 1805

Proprietary Information of Altair Engineering


Field Contents

IFILT Friction filtering flag (See comment 10).

Default as defined by CONTPRM (Character = NO, SIMP, PER, CUTF)

NO - No filter is used.
SIMP - Simple numerical filter.
PER - Standard -3dB filter with filtering period.
CUTF - Standard -3dB filter with cutting frequency.

FFAC Friction filtering factor.

Default as defined by CONTPRM (Real = 0.0 < FFAC < 1.0)

C1, C2, C3, Coefficients to define variable friction coefficient in IFRIC = GEN, DARM,
C4, C5, C6 REN.

Default as defined by CONTPRM (Real > 0)

Comments

1. The property identification number must be that of an existing PCONT bulk data entry.
Only one PCONTX property extension can be associated with a particular PCONT.

2. PCONTX is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. If FRIC is not explicitly defined on the PCONTX/PCNTX# entries, the MU1 value on the
CONTACT or PCONT entry is used for FRIC in the /INTER entries for Geometric Nonlinear
Analysis. Otherwise, FRIC on PCONTX/PCNTX# overwrites the MU1 value on CONTACT/
PCONT.

4. In implicit analysis, different contact formulations are used for contact where slave and
master set do not overlap and where they overlap (self-contact).

In the case of self-contact, the gap cannot be zero and a constant gap is used. For
small initial gaps, the convergence will be more stable and faster if GAP is larger than the
initial gap.

In implicit analysis, sometimes a stiffness with scaling factor reduction (for example,
STFAC = 0.01) or reduction in impacted thickness (if rigid one) might reduce unbalanced
forces and improve convergence, particularly in shell structures under bending where the
effective stiffness is much lower than membrane stiffness; but it should be noted that too
low of a value could also lead to divergence.

5.
and/or the slave segment stiffness Ks.

The master stiffness is computed from Km = STFAC * B * S * S/V for solids, Km = 0.5 *
STFAC * E * t for shells.

The slave stiffness is an equivalent nodal stiffness computed as Ks = STFAC * B * V- 3 for


solids, Ks = 0.5 * STFAC * E * t for shells.

1806 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


In these equations, B is the Bulk Modulus, S is the segment area, and V is the volume of a
solid. There is no limitation to the value of stiffness factor (but a value larger than 1.0
can reduce the initial time step).

The interface stiffness is then K = max (STMIN, min (STMAX, K1)) with

ISTF = 0, K1 = Km
ISTF = 2, K1 = 0.5 * (Km + Ks)

ISTF = 3, K1 = max (Km, Ks)

ISTF = 4, K1 = min (Km, Ks)

ISTF = 5, K1 = Km * Ks / (Km + Ks)

6. The default for the constant gap (IGAP = CONST) is the minimum of

t, average thickness of the master shell elements;


l/10, l – average side length of the master solid elements;

lmin/2, lmin – smallest side length of all master segments (shell or solid).

7. The variable gap (IGAP = VAR) is computed as gs + gm

with:

gm - master element gap with


gm = t/2, t: thickness of the master element for shell elements.

gm = 0 for solid elements.

gs - slave node gap:

gs = 0 if the slave node is not connected to any element or is only connected to solid or
spring elements.

gs = t/2, t - largest thickness of the shell elements connected to the slave node.

If the slave node is connected to multiple shells and/or beams or trusses, the largest
computed slave gap is used.

8. INACTI = 3, 4 are only recommended for small initial penetrations and should be used with
caution because:

the coordinate change is irreversible.


it may create other initial penetrations if several surface layers are defined in the
interfaces.

it may create initial energy if the node belongs to a spring element.

INACTI = 5 works as follows:

Altair Engineering OptiStruct 13.0 Reference Guide 1807

Proprietary Information of Altair Engineering


9. IFRIC defines the friction model.
IFRIC = COUL – Coulomb friction with F T < FRIC * F N .

For IFRIC > 0 the friction coefficient is set by a function (m = m (p, V)), where p is the
pressure of the normal force on the master segment and V is the tangential velocity of
the slave node.

The following formulations are available:

IFRIC = 1 - Generalized viscous friction law

m = FRIC + C1 * p + C2 * V + C3 * p * v + C4 * p2 + C5 * v2

IFRIC = 2 - Darmstad law

m = C1 · e(C 2 V ) · p2 + C3 · e(C 4 V ) · p + C5 · e(C 6 V )

IFRIC = 3 - Renard law

0 < V < C5

C5 < V < C6

C6 < V

where:

1808 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


The first critical velocity Vcr1
second critical velocity Vcr2 (C5 < C6).

The static friction coefficient C1 and the dynamic friction coefficient C2, must be lower
than the maximum friction C3 (C1 < C3) and C2 < C3).

The minimum friction coefficient C4, must be lower than the static friction coefficient
C1 and the dynamic friction coefficient C2 (C4 < C1 and C4 < C2).

10. IFORM selects two types of contact friction penalty formulation.

The viscous (total) formulation (IFORM = VISC) computes an adhesive force as

F adh T

F T = min (µF N , F adh)

The stiffness (incremental) formulation (IFORM = STIFF) computes an adhesive force as

F adh = F T old + ∆F T

∆F T = K * VT * dt

F T new = min (µF N , F adh)

11.
the tangential friction forces are smoothed using a filter:

F T = α * F'T + (1 - α) * F'T - 1

where,

F T - Tangential force

F'T - Tangential force at time t

F'T - 1 - Tangential force at time t-1

α - filtering coefficient

IFILT = SIMP – α = FFAC

IFILT = PER – α = 2 dt/FFAC, where dt/T = FFAC, T is the filtering period

IFILT = CUTF – α = 2 * FFAC * dt, where FFAC is the cutting frequency

12. This card is represented as an extension to a PCONT property in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1809

Proprietary Information of Altair Engineering


PCONV

Bulk Data Entry

PCONV – Free Convection Property Definition

Description
Defines a free convection boundary condition properties.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PC ONV PC ONID MID FORM EXPF

Field Contents

PCONID Convection property identification number of a PCONV card.


No default (Integer > 0)

MID Material property identification number of MAT4 card.


No default (Integer > 0)

FORM Types of formula used for free convection.


Default = 0, Integer 0, 1, 10, 11, 20, 21

EXPF Free convection exponent.


For FORM = 0, 10, and 20, EXPF = 0.0
For FORM = 1, 11, and 21, EXPF = 1.0

Comments

1. Every CONV card must refer a PCONV card.

2. Heat transfer coefficient (H) is specified on MAT4 card with MID.

3. FORM specifies the convection formula type.

If FORM = 0, 10, 20,

q = H * (T - TAMB)E XP F * (T - TAMB)

If FORM = 1, 11, 21

q = H * (T E XP F - TAMBE XP F ))

where, T is grid temperature and TAMB is the ambient temperature.

1810 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


4. EXPF is the free convection temperature exponent.

If FORM = 0, 10, 20, EXPF = 0.0 for linear convection.

If FORM = 1, 11, 21, EXPF = 1.0 for linear convection.

Therefore, linear convection formula is:

q = H * (T-TAMB)

5. This card is represented as a group in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1811

Proprietary Information of Altair Engineering


PDAMP

Bulk Data Entry

PDAMP – Scalar Damper Property

Description

Specifies the damping of a scalar damper element using defined CDAMP1 or CDAMP3 entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PDAMP PID1 B1 PID2 B2 PID3 B3 PID4 B4

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PDAMP 14 2.3 2 6.1

Field Contents

PID# Property identification number.

No default (Integer > 0)

B# Force per unit velocity.

No default (Real)

Comments

1. Damping values are defined directly on the CDAMP2 entry and therefore do not require a
PDAMP entry.

2. A structural viscous damper, CVISC, may also be used for geometric grid points.

3. Up to four damping properties may be defined on a single entry.

4. This card is represented as a property in HyperMesh.

1812 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PEAKOUT

Bulk Data Entry

PEAKOUT – Peak Identification Criteria

Description

Defines criteria used for the automatic identification of loading frequencies at which result
peaks occur. Other result output may then be requested at these “peak” loading frequencies.
This feature is only supported for frequency response solution sequences.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PEAKOUT SID NPEAK NEAR FAR LFREQ HFREQ RTYPE PSC ALE

GRIDC GID1 C ID1 C UTOFF1 GID2 C ID2 C UTOFF2

GID3 C ID3 C UTOFF3 ... ... ...

... ...

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PEAKOUT 396 5 0.5 100.0 0.0 200.0 DISP DB

GRIDC 65 1 11 66 1 10

67 1 11 68 1 11

Field Contents

SID Set identification number.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1813

Proprietary Information of Altair Engineering


Field Contents

NPEAK Desired number of peaks. See comment 2.

Default = 5 (Integer > 0)

NEAR Minimum allowed distance between two peaks. If two peaks are closer
than this value, the loading frequency of the lower peak will be ignored.
See comment 2.

Default = 0.0 (Real > 0.0)

FAR Maximum allowed distance between two peaks. Additional peaks will be
selected (in addition to NPEAK) if the distance between the peaks is
greater than this value. See comment 2.

Default = largest applied loading frequency (Real > 0.0)

LFREQ Starting loading frequency for peak identification. See comment 2.

Default = 0.0 (Real > 0.0)

HFREQ Ending loading frequency for peak identification. See comment 2.

Default = largest applied loading frequency (Real > 0.0)

RTYPE Result type for peak identification for the structural domain.

The result for a structural degree of freedom can be displacement (DISP),


velocity (VELO), or acceleration (ACCE).

Default = DISP (DISP, VELO or ACCE)

PSCALE Pressure scaling method for peak identification for the fluid domain.

The result for a fluid grid can be the scale of pressure, decibels (DB) or A-
weighted decibels (DBA). See comment 3 for decibel calculations and
reference pressure settings. For DBA, standard A-weighting is used.

Default = DBA (DB, DBA or NONE)

GRIDC Flag indicating that a degree-of-freedom list for peak identification is to


follow.

GID# Grid identification number.

No default (Integer > 0)

1814 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

CID# Component identification number.

No default (1 < Integer < 6)

CUTOFF# The cutoff value can be a real value or an integer value. See comment 2.

If the entry is a real value, then this is the value of the cutoff (in the
same unit specified by RTYPE and PSCALE).

If the entry is an integer value, then this is the identification number of a


TABLED1, TABLED2, TABLED3, or TABLED4 entry defining the cutoff as a
function of frequency (in the same unit specified by RTYPE and PSCALE).

Default = 0.0 (Real or Integer > 0)

Comments

1. There can be multiple PEAKOUT cards with the same SETID.

2. The following example shows how the different criteria work in identifying peaks.

Figure 1: Plot of the Acoustic Response vs. Frequency

Altair Engineering OptiStruct 13.0 Reference Guide 1815

Proprietary Information of Altair Engineering


Figure 1 shows a plot of the Acoustic Response versus frequency for a chosen degree-of-
freedom. The total frequency range can be reduced to the frequency range of interest by
defining LFREQ and HFREQ. The search area can be further reduced by defining CUTOFF
such that low magnitude peaks can be ignored. In the remaining region, 5 peaks (P1, P2,
P3, P4, and P5) can easily be identified. Should NPEAK be set to 4, the resulting
frequency set would consist of the frequencies corresponding to the peaks P4, P5, P1,
and P3, with P5 being omitted.

In order to ensure that peaks are neither too far apart nor too close together, the FAR
and NEAR criteria, respectively, may be used.

In the above example, should a value of 50HZ be defined for FAR, P4 would be selected in
addition to the other peaks because D2 (~54 Hz) is greater than 50Hz, and so an
additional peak is required to satisfy the FAR criterion.

Similarly, should a value of 15Hz be defined for NEAR, then P2 will be omitted, as D1 (~11
Hz) is less than 15Hz.

3. The dB value is calculated using 20 * log10 (P/P0), where P0 is the reference pressure.
The reference pressure is dependent on the units specified on the UNITS input data. If
the units are SI, the value is set as 2.0E-5 Pa. If they are CGS, it is set as 2.0E-4 barye.
If they are MPa, it is set as 2.0E-11 MPa. If they are BG or EE, then it is set as 4.17E-7
lbf/ft 2. If no UNITS data is present, the default value is 2.0E-11 MPa.

4. If you wish to include interior points of a superelement (in a CMS model) for the purposes
of peak identification using the PEAKOUT bulk data entry, the SEINTPNT entry can be
used in the subcase information section to convert the interior grid points to exterior grid
points (since points referenced by PEAKOUT should be exterior points only).

1816 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PELAS

Bulk Data Entry

PELAS – Scalar Elastic Property

Description

Used to define the stiffness and stress coefficient of a scalar elastic element (spring) by
means of the CELAS1 or CELAS3 entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PELAS PID K GE S PID K GE S

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PELAS 7 4.29 7.92 27 2.17

Field Contents

PID Unique scalar elastic property identification number.

No default (Integer > 0)

K Elastic property value.

No default (Real)

GE Damping Coefficient. See comments 3 and 4.

Default = 0.0 (Real)

S Stress coefficient.

Default = 0.0 (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 1817

Proprietary Information of Altair Engineering


Comments

1. Be careful using negative spring values.

2. One or two elastic spring properties may be defined on a single entry.

3. To obtain the damping coefficient GE, multiply the critical damping ratio, C/C0, by 2.

4. If PARAM, W4 is not specified, GE is ignored in transient analysis.

5. The element force of a spring is calculated from the equation:

F = k * (u1 – u2)

Where, k is the stiffness coefficient for the scalar element and u1 is the displacement of
the first degree-of-freedom listed on the CELAS entry. Element stresses are calculated
from the equation: s = S * F, where, S is the stress coefficient as defined above.

6. This card is represented as a property in HyperMesh.

1818 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PELAST

Bulk Data Entry

PELAST – Frequency-dependent Elastic Spring Property

Description

Defines the frequency dependent property values for a PELAS bulk data entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PELAST PID TKID TGEID TKNID

Field Contents

PID Property identification number. Must match with a PID of a PELAS bulk data
entry.

No default (Integer > 0)

TKID Identification number of a TABLED# entry that defines the force per unit
displacement versus frequency relationship.

Default = 0 (Integer > 0)

TGEID Identification number of a TABLED# entry that defines the element structural
damping coefficient versus frequency relationship.

Default = 0 (Integer > 0)

TKNID Identification number of a TABLED# entry that defines the nonlinear force
versus displacement relationship.

Default = 0 (Integer > 0)

Comments

1. Each PELAST entry must have a matching PELAS entry.

2. PELAST is ignored in all solution sequences except frequency response analysis. Nominal
values from the PELAS entry are used in all the analyses except frequency response
analysis.

Altair Engineering OptiStruct 13.0 Reference Guide 1819

Proprietary Information of Altair Engineering


3. If a particular TABLED id is blank or 0, the corresponding nominal value from the PELAS
entry will be used.

4. The TKNID table is currently unused in nonlinear analysis and is ignored.

5. This card is represented as a property in HyperMesh.

1820 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PERBC

Bulk Data Entry

PERBC – Defines a connection between opposite edges/faces of the structure (Periodic


Boundary Conditions).

Description

The PERBC bulk data entry can be used to define a connection between opposite edges/faces
of the structure. This entry is used to apply Periodic Boundary Conditions to the model.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PERBC ID GSID RLID TOL

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PERBC 2 45 32 0.01

Field Contents

ID Set identification number.

(Integer > 0)

GSID Identification number of a SET of grid points on one side of the structure.

(Integer > 0)

RLID Identification number of a RELOC bulk data entry that maps the nodes on one
side of the structure to the other. An exact one-to-one match between the two
sides is required.

(Integer > 0)

TOL Specifies the numeric value defining the maximum distance between two grid
points to allow equivalence. All grid points in the set defined by GSID and the
set of grid points on the other side of the structure (mapping defined by the
RELOC entry) are considered for equivalence based on the tolerance.

(Real > 0.0)

Altair Engineering OptiStruct 13.0 Reference Guide 1821

Proprietary Information of Altair Engineering


Comments

1. The PERBC entry can be used to apply periodic boundary conditions, to match results
from one side of the structure to another.

2. The referenced RELOC Bulk Data Entry should be defined with TYPE=MOVE or
TYPE=ROTATE. For TYPE=ROTATE, a simple rotation about a single axis should only be
defined. All grids on one side of the structure (defined via GSID) and matching grids on
the other side should cannot have a coordinate system (Field CD on GRID entry) defined.
If RELOC(ROTATE) is specified, then all matching grids will have CD assigned automatically
to match the structure.

3. Periodic Boundary Conditions are supported for all solution sequences (except OptiStruct-
Multi-body Dynamics (OS-MBD) and Geometric Nonlinear Analysis (ANALYSIS=NLGEOM/
IMPDYN/EXPDYN)) and all optimization types. In shape optimization, when GRID’s identified
on the PERBC entry are in or near the optimized zone, their location changes should be
properly linked through DVGRID, otherwise the results may be incorrect.

1822 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PFAST

Bulk Data Entry

PFAST – CFAST Element Property

Description

Define properties of connector (CFAST) elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PFAST PID D MC ID MFLAG KT1 KT2 KT3 KR1

KR2 KR3 MASS GE

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PFAST 9 0.3 20 1 12800.0 8000.0 8000.0

0.8

Field Contents

PID Identification number of a PFAST entry.

No default (Integer > 0)

D Diameter of the connector. See comment 2.

No default (Real > 0.0)

MCID Identification number of the element stiffness coordinate system. See


comment 3.

Altair Engineering OptiStruct 13.0 Reference Guide 1823

Proprietary Information of Altair Engineering


Field Contents

MFLAG Flag to indicate how the coordinate system specified by MCID will be
used.

If MFLAG = 0, MCID defines a relative coordinate system.

If MFLAG = 1, MCID defines an absolute coordinate system.

Default = 0 (Integer)

KTi Stiffness values in directions 1 through 3.

Default = 0.0 (Real)

KRi Rotational stiffness values in directions 4 through 6.

Default = 0.0 (Real)

MASS Mass of the fastener. See comment 5.

Default = 0.0 (Real)

GE Structural damping.

Default = 0.0 (Real)

Comments

1. For a CFAST element, no material needs to be specified in the corresponding PFAST card
- the stiffness of the element is directly specified in the PFAST card with KTi and KRi
entries.

2. The diameter D will not be involved in the stiffness calculation directly. It is used along
with GA and GB to find appropriate auxiliary points and related shell elements and grids. In
this case, the stiffness contribution of the fastener depends not only on the stiffness
values specified for KTi and KRi, but also the diameter D, because the location of the
auxiliary points will be used to weight the contribution of the shell element grids to GA and
GB of the fastener.

3. Element stiffness coordinate system. The three stiffness values KT1, KT2 and KT3 will be
applied along the three axes of the element coordinate system. The unit vectors of the
three axes are denoted as e1, e2 and e3.

a) If MCID = -1, MFLAG will be ignored and e1 will be defined as:

e2 is defined as being perpendicular to e1 and lined up with the closest axis of the basic
system. This is accomplished by taking the inner product of e1 with the basic system unit
vectors. The smallest will define the basic system direction which is closest to the plane

1824 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


perpendicular to e1* e2 is then defined as the projection of the basic direction onto this
perpendicular plane. For example, assume m is the unit vector of the closest axis of the
basic system. The direction of e2 can be calculated as:

Unify this vector, then

At last, e3 can be calculated by the cross product of e1 and e2 as follows:

e3 = e1 x e2

b) If MCID > 0 and MFLAG = 0, e1 will be defined as:

in which XA and XB are the coordinates of GA and GB.

The T2 direction specified by MCID will be used to define the orientation vector v of the
fastener.

Then, e3 can be obtained as:

At last, the e2 can be easily calculated by the cross product of e3 and e1 as follows:

e2 = e3 x e1

c)
used directly as e1, e2 and e3. The element forces will be computed in the coordinate
system defined in comment 3(a).
d) If MCID refers to a cylindrical or spherical coordinate system, the local origin used to
locate the system is selected as follow: (i) if GA of the CFAST is specified, use GA as
the local origin; (ii) if GA is not specified but GS is specified, use GS as the local origin;
(iii) if neither GA nor GS is specified, use the point (XS, YS, ZS) as the local origin.

4. The final length of the CFAST element is defined by the distance between GA and GB. If
the length is zero, the normal to shell patch A is used to define the axis of the fastener.

5. For the mass of the fastener, half of the value defined in the MASS entry is placed
directly onto the translational degrees-of-freedom of GA and GB. Then they are
distributed, via auxiliary points, to corresponding shell grids. As the result, while the mass
will be represented correctly for general representation of the fastener in the vibrations of
the structure, the moments of inertia relative to the local axes of the fastener will only be

Altair Engineering OptiStruct 13.0 Reference Guide 1825

Proprietary Information of Altair Engineering


roughly approximated.

1826 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PFAT

Bulk Data Entry

PFAT – Fatigue Properties

Description

Defines element properties for fatigue analysis

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PFAT ID Layer Finish Treatme Kf


nt

Field Contents

ID Each PFAT card must have a unique ID. This ID may be referenced from a
FATDEF definition.

No default (Integer > 0)

Finish Material Surface Finish, a result of manufacturing process. See comment 3.

Default = NONE (NONE, POLISH, GROUND, MACHINE, HOTROLL, FORGE or any


float value between 0.0 and 1.0)

When it is a float value, it will be used to modify the fatigue limit by multiplied
with the original fatigue limit.

Treatment Material Surface Treatment for Material S-N Curve, a process used to enhance
the fatigue life. See comment 3.

Default = NONE (NONE, NITRIDED, SHOTPEEN, COLDROLL or any float value


great than 0.0)

When it is a float value, it will be used to modify the fatigue limit by multiplied
with the original fatigue limit.

Layer Region Layer for shell elements. See comment 1.

Default = 0 (0 = Worst, 1 = Top, 2 = Bottom).

Kf Fatigue strength reduction factor. See comments 2 and 3.

Default = 1.0 (Real > 1.0)

Altair Engineering OptiStruct 13.0 Reference Guide 1827

Proprietary Information of Altair Engineering


Comments

1. If shell elements are used, it is necessary to specify the appropriate layer or Surface of
results to use Top or Bottom. Worst is the worst result of Top and Bottom (the one with
larger damage).

2. Fatigue strength reduction factor takes into account the effect of notch effects, size
effects, and loading type influence,

where, Cnotch , Csize, and Cloading are correction factors for notch effect, size effect, and
loading type influence.

3. Finish, Treatment and Kf are ignored in FOS analysis (TYPE=FOS on FATPARM).

4. This card is represented as a loadcollector in HyperMesh.

1828 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PFPATH

Bulk Data Entry

PFPATH – Transfer Path Analysis

Description

Bulk Data Entry for One-Step Transfer Path Analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PFPATH SID C ONPT RID RTYPE C ONEL C ONREL

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PFPATH 10 11 12 DISP 18 23

Argument Options Description

SID <INTEGER> setid The SID is referenced by a PFPATH


card in the control section.

CONPT <INTEGER> gsid The connection points with a SID of


type GRID SET.

RID <INTEGER> rsid The response SID of type GRIDC.


Contribution to each response DOF
through the connection points will be
calculated.

Altair Engineering OptiStruct 13.0 Reference Guide 1829

Proprietary Information of Altair Engineering


Argument Options Description

RPTYPE DISP/VELO/ACCE Criterion for the type of the response; the response type
corresponding to a structural degree of freedom could be
displacement, velocity or acceleration.
Default = DISP

CONEL <INTEGER> esid The ELEMENT set consists of elements


connected to the connection GRIDs in
CONPT. These elements represent
connecting paths from the rest of the
system to the user-defined control
volume.

CONREL <INTEGER> rsid The RIGID set consists of the RIGID


elements, connected to the connection
GRIDs in CONPT. These rigid elements
represent connecting paths from the
rest of the system to the user defined
control volume.

Comments

1. There can be multiple PFPATH cards with the same SID.

2. If CONREL is specified in the 7th entry, the RIGID element IDs must be unique.

1830 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PFBODY

Bulk Data Entry

PFBODY – Flexible Body Definition for Multi-body Simulation

Description

Defines a flexible body out of a list of finite element properties, elements, and grid points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PFBODY BID BODY_NAME

TYPE1 ID1 ID2 ID3 ID4 ID5 ID6 ID7

ID8 …

TYPE2 ID9 ID10 …

TYPE# …

C MS C TYPE UB_FREQ NMODES

FLXNODE NOAUTO/C 1 G1 G2 G3 G4 G5 G6

FLXNODE C2 G8 G9 …

DAMPING DTYPE DVAL

Altair Engineering OptiStruct 13.0 Reference Guide 1831

Proprietary Information of Altair Engineering


Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PFBODY 3 C ontrol_arm

PSHELL 23 21

PBEAM 9 59 48

C ONM2 2345

GRID 400 401 402

C MS CB 50

FLXNODE 123 400 499

FLXNODE 123456 402 300

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PFBODY 3 Linkage

PSOLID 13 15

C MS CB 2000.0

FLXNODE NOAUTO

FLXNODE 123 900 901 902 903 1000 1001

1832 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

FLXNODE 123456 11 12 13

DAMPING C RATIO 0.8

Field Contents

BID Unique body identification number.

No default (Integer > 0)

BODY_NAME Unique body name.

This name is used as the Flex H3D file name to which the reduced
flexible body information will be written out for the PFBODY.

Default = OUTFILE_body_<BID>.h3d (Character string)

TYPE# Flag indicating that the following list of IDs refer to entities of this
type. All property definitions; CELAS2, CONM2, PLOTEL, RBE2, RBE3,
RBAR, RROD, and GRID are valid types for this field.

No default (PBAR, PBARL, PBEAM, PBEAML, PBUSH, PCOMP, PCOMPP,


PCOMPG, PDAMP, PELAS, PGAP, PROD, PSHEAR, PSHELL, PSOLID,
PVISC, PWELD, CELAS2, CONM2, PLOTEL, RBE2, RBE3, RBAR, RROD, or
GRID)

ID# Identification numbers of entities of the preceding TYPE flag.

No default (Integer > 0)

CMS CMS flag indicating that information on the method used for reducing
the flexible body is to follow.

CTYPE Component Mode Synthesis method to be employed.

CB - Craig-Bampton
CC - Craig-Chang

Default = CB (CB or CC)

UB_FREQ Upper bound frequency for the eigenvalue analysis. If 0.0 or blank, no

Altair Engineering OptiStruct 13.0 Reference Guide 1833

Proprietary Information of Altair Engineering


Field Contents

upper bound is used. See comments 8 and 9.

Default = blank (Real > 0.0, or blank)

NMODES Number of modes to be extracted from eigenvalue analysis. If set to -1


or blank, number of modes is limitless. See comments 8 and 9.

Default = blank (Integer > -1, or blank)

FLXNODE FLXNODE flag indicating that flexible body interface node information is
to follow. See comment 11.

NOAUTO NOAUTO flag to not automatically determine the interface nodes for the
flexible body.

C# Component number indicating the interface degrees-of-freedom for the


following list of grids.

No default (up to 6 unique digits (0 < digit < 6) may be placed in the
field with no embedded blanks)

G# Grid identification numbers.

(Integer > 0)

DAMPING DAMPING flag indicating the flexible body modal damping.

DTYPE Damping option.

Default = DEFAULT (DEFAULT or CRATIO)

DVAL Damping ratio value if DTYPE is specified as CRATIO.

(Real > 0.0)

Comments

1. A maximum of 56 characters may be given for BODY_NAME.

2. Flex H3D file name will be <BODY_NAME>.h3d or OUTFILE_body_<BID>.h3d in the outfile


directory.

3. Any number of property definitions; CELAS2, CONM2, PLOTEL, RBAR, RBE2, RBE3 or RROD
elements or grid points can be given.

1834 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


4. At least one property definition, element, or grid point must be given.

5. A property definition; CELAS2, CONM2, PLOTEL, RBE2, RBE3, RBAR or RROD element or grid
point can only belong to one body (flexible or rigid).

6. All property definitions, elements and grid points defined on a PFBODY bulk data entry
form one flexible body.

7. CMS definition defines the component mode synthesis method to reduce the flexible body
for the multi-body analysis. Exactly one must be defined for each PFBODY.

8. UB_FREQ and NMODES cannot both be blank.

9. When UB_FREQ = 0.0 and NMODES = 0, this is a special case where no eigen modes will
be included in CMS mode generation.

10. If FLXNODE is not defined, a default set of interface nodes and degrees-of-freedom. will
be generated based on the actual interface nodes and degrees-of-freedom of the flexible
body.

11. One FLXNODE line can have up to six interface grid IDs. No continuation lines are
allowed. Add multiple FLXNODE lines to add more than six interface nodes.

12. This card is represented as a group in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1835

Proprietary Information of Altair Engineering


PGAP

Bulk Data Entry

PGAP – Gap Element Property

Description

Defines properties of the gap (CGAP or CGAPG) elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PGAP PID U0 F0 KA KB KT MU1 MU2

GPAD FRIC ESL

Examples

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PGAP 2 .025 2.5 1E6 1E6 0.25 0.25

Frictionless contact with automatic determination of U0 and KA:

PGAP 2 AUTO AUTO

Minimum data required to prescribe Coulomb friction:

PGAP 2 1E6 0.3 0.3

Enforced stick condition (See comment 8):

PGAP 2 1E6 AUTO

1836 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

PID Property identification number.

No default (Integer > 0)

U0 Initial gap opening.

Default = 0.0 (Real or AUTO). See comment 2.

F0 Preload. (Ignored in linear analysis).

Default = 0.0 (Real > 0.0)

KA Axial stiffness for the closed gap. See comments 3 and 7.

No default (Real > 0.0 or AUTO, SOFT or HARD)

KB Axial stiffness for the open gap. See comment 3.

Default = 10-14 * KB (Real > 0.0). This default is also set when KB=0.

KT Transverse stiffness when the gap is closed. See comments 4 and 7.

Default = MU1 * KA (Real > 0.0 or AUTO)

MU1 Coefficient of static friction (ms). See comments 8 through 10. (Ignored in
linear analysis).

Default = 0.0 (Real > 0.0 or STICK or FREEZE)

MU2 Coefficient of kinetic friction (mk). (Ignored in linear analysis).

Default = MU1 (0.0 < Real < MU1)

GPAD “Padding” to be added to account for additional layers on the surface of


obstacles A and B. Positive value reduces the initial gap opening. See
comment 11.

Default = NONE (Real or NONE or THICK; THICK applies only to CGAPG


elements)

FRICESL Frictional elastic slip – distance of sliding up to which the frictional


transverse force increases linearly with slip distance. Specified in physical
distance units (similar to U0 and GPAD). See comment 5.

Altair Engineering OptiStruct 13.0 Reference Guide 1837

Proprietary Information of Altair Engineering


Field Contents

Non-zero value activates respective friction model based on Elastic


Slip Distance.
Zero value or blank activates friction model based on prescribed
transverse stiffness KT.
Default = 0.0 (Real > 0.0)

Comments

1. The gap element coordinate system is presented in the following figure. See the CGAP or
CGAPG entry for a more detailed description.

The C GAP or C GAPG Element C oordinate System

2. With the optional value AUTO, the initial gap opening U0 is calculated automatically,
based on the distance between nodes GA and GB (in the original, undeformed mesh). For
gap elements with prescribed coordinate systems, this becomes a projection of vector
GA->GB onto the prescribed axis on the gap element (axis 1 of the coordinate system).

3. The gap element force-displacement behavior is different in linear and nonlinear analysis
(see Nonlinear Quasi-Static Analysis for more information on nonlinear solutions). In linear
analysis, the gap stiffness is constant and depends on the initial gap opening U0 (as
shown in the figure below).

1838 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


C GAP or C GAPG Element Force Deflection C urve for Linear Analysis

The gap force displacement behavior in nonlinear analysis is illustrated in the figure below.
While the gap is open, its normal stiffness is defined by KB. When the gap relative
displacement UA - UB becomes equal to the initial opening U0, first contact occurs. The
gap stiffness becomes KA upon contact.

C GAP or C GAPG Element Force Deflection C urve for Nonlinear Analysis

4. When the gap is open, there is no transverse stiffness. When the gap is closed, friction
is activated and the gap has stiffness KT in the transverse direction (see 5 below for
alternative version). KT acts as a linear spring in linear solution sequences. For nonlinear
solution sequences, frictional force increases with sliding distance in proportion to KT until
it reaches static friction force MU1 * Fx, Fx being the normal force in the gap element.
With further transverse deformation, friction becomes kinetic and the friction force is MU2
* Fx. See the figure below for a one-dimensional illustration.

Altair Engineering OptiStruct 13.0 Reference Guide 1839

Proprietary Information of Altair Engineering


C GAP or C GAPG Element Frictional Behavior in Nonlinear Analysis

5. In addition to the above formulation, in Release 12.0 an additional model of friction has
been introduced, based on Elastic Slip Distance and activated by presence of non-zero
FRICESL. This model typically has better performance in solution of frictional problems
thanks to more stable handling of transitions from stick to slip. Key differences between
the two available models are illustrated in the figure below (F 1 and F 2 represent two
different values of normal force F x ):

C omparison of the two available friction models for gap elements.

Model (a), based on fixed stiffness KT, is relatively simpler and only requires prescribing
coefficient of friction MU1 and MU2 (while KT can be determined automatically).
However, in Coulomb friction the frictional resistance depends upon normal force. Using
fixed KT will predict different range of stick/slip boundary for different normal forces,
and thus may qualify the same configuration as stick or slip, depending on normal
force.

1840 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Model (b), based on Elastic Slip Distance, provides unique identification of stick or slip
and generally performs better in solution of problems with friction. This model does
require prescribing elastic slip distance FRICESL (for gap elements, there is no
automatic determination of FRICESL – a recommended value is about 0.5% of typical
element size in the neighborhood of the gap element).
6. Note that the nonlinear gap element's force-displacement behavior may produce negative
contributions to the compliance of the structure. For example, if KB > 0 and initial gap
opening U0 > 0, then the gap is essentially "preloaded" with an attractive force KB*U0. As
such a gap closes, the work done (and, hence, the gap's contribution to compliance) is
negative. Such very small negative contributions may even be produced if the KB field is
blank or zero – this is due to the default non-zero value of KB applied in such cases. In
most situations, such small negative contributions get overridden by the overall positive
compliance of the entire structure. However, in some cases they may lead to negative
total compliance.

7. Reasonable gap stiffness: the gap stiffness values KA and KT essentially represent penalty
springs that are hard enough to prevent perceptible penetration of contacting nodes.
While, theoretically, higher stiffness values enforce the contact conditions more precisely,
excessively high values may cause difficulties in convergence or poor conditioning of the
stiffness matrix (this is especially true for KT). If any such symptoms are observed, it may
be beneficial to reduce the value of gap stiffness. A reasonable range of gap stiffness is
of the order of:

(103 to 106 ) * E * h

where, E is the typical value of elastic modulus and h is the typical element size in the
area surrounding the gap elements. Such a range will generally keep the gap penetration
below one thousandth / one millionth of the element size, respectively. A good value for
KT is of the order of 0.1*KA.

To facilitate reasonable values of KA and KT, automatic calculation of these parameters is


supported, specifically:

Option KA=AUTO determines the value of KA for each gap element using the stiffness
of surrounding elements. Additional options SOFT and HARD create respectively softer
or harder penalties. SOFT can be used in cases of convergence difficulties and HARD
can be used if undesirable penetration is detected in the solution.

Option KT=AUTO automatically calculates the value of KT. If MU1>0, the result here is
the same as with blank KT -- its value is calculated as MU1*KA. However, if MU1=0 or
blank, KT=AUTO produces a non-zero value of KT, calculated as KT=0.1*KA.
Therefore, KT=AUTO can be used to prescribe enforced stick conditions (see below).
8. Prescribing MU1=STICK is interpreted as an enforced stick condition. (This can also be
accomplished by prescribing KT>0 or KT=AUTO with MU1=0 or blank). Such gap elements
will not enter the sliding phase. Of course, the enforced stick only applies to gaps that
are closed. Note that, in order to effectively enforce stick condition on gaps of non-zero
length,frictional offset may need to be turned off (See comment 10).

9. Prescribing MU1=FREEZE enforces zero relative motion of the gap – the gap opening
remains fixed at the original value and the sliding distance is zero. Also, rotations at GA
node are matched to the rotations of GB or the obstacle patch B. The FREEZE conditions
applies no matter whether the gap is open or closed (hence, U0 is of no relevance in this
case). The prescribed values of KB and KT are ignored. The value of KA is respected,

Altair Engineering OptiStruct 13.0 Reference Guide 1841

Proprietary Information of Altair Engineering


although it is recommended that it is set to AUTO or HARD, to assure good connection.
Also, this condition is effective irrespective of the frictional offset setting.

10. The presence of friction or stick can introduce moment loadings and counter-intuitive
results into the problem by way of frictional offset. The reason is that for gap elements
with non-zero length (distance between GA and GB), the actual location of the contact
interface is presumed to be in the middle of the gap length (see figure below).

C GAP or C GAPG Presumed C ontact Surface

The frictional forces act along this contact surface. Transferring these forces to the grid
points GA and GB requires an offset operation that produces both forces and moments at
the gap grid points. Similarly, the sliding distance at the gap interface is a result of nodal
displacements and rotations at GA and GB (see figure below).

C GAP or C GAPG Sliding with Friction

For contact between bodies that do not support moments (solid elements, for example),
this offset may render friction ineffective because the free rotations at gap nodes offer
no effective resistance to friction. With the stick condition formally satisfied, for
example, nodes GA and GB can move relative to each other (see figure below).

1842 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


C GAP or C GAPG Stick (Zero Sliding Distance)

In practice, for gaps that are initially open, AUTOSPC will effectively fix respective
unsupported rotations. However, for gap elements that are initially closed (U0 < 0 or
U0=AUTO with CID=FLIP), the frictional terms will prevent AUTOSPC from being effective.
Hence, respective SPC on rotations need to be applied manually. (Note that this only
applies to "individual" gap end nodes GA and GB and is not needed for elements or patches
of nodes on the obstacle side of GAPG elements).

Effective in the Release 12.0, to avoid such counter-intuitive behavior, the frictional
offset operation is by default turned off if the model involves friction or stick and contains
at least one nonlinear subcase (of NLSTAT type). (Note that for consistency, this affects
both linear and nonlinear gap elements.) This produces more intuitive results with friction.
However, it may violate the rigid body balance of the body.

For linear gap analysis and for FREEZE condition, the offset operation is applied by default
(this produces correct rigid body balance, especially in natural frequency analysis).

The above default setting can be changed via the GAPOFFS command on the GAPPRM
card.

11. The GPAD option allows you to account for additional layers on the surface on obstacles
A and B, such as shell thickness or coatings on the surface of solids. Positive value
substracts from the gap opening U0, when calculated using AUTO option (GPAD is only
allowed when U0 is set to AUTO).

The GPAD option THICK automatically accounts for shell thickness on both sides of the
gap (this also includes the effects of shell element offset ZOFFS or composite offset Z0).
The THICK option applies only to CGAPG elements and is ignored for CGAP.

12. This card is represented as a property in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1843

Proprietary Information of Altair Engineering


PGAPHT

Bulk Data Entry

PGAPHT – Gap Element Heat Transfer Conduction Property for Heat Transfer Analysis

Description

Defines heat transfer conduction properties of the gap (CGAP or CGAPG) elements for heat
transfer analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PGAPHT PID KAHT KBHT TC ID

Examples

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PGAPHT 2 1E6

Contact with automatic determination of KAHT:

PGAPHT 2 AUTO

Minimum data required to prescribe clearance based contact conduction (see comments 2
and 3):

PGAPHT 2 10

Field Contents

PID Property identification number.

No default (Integer > 0)

KAHT Total conduction for the closed gap. See comment 2.

1844 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

No default (Real > 0.0 or AUTO)

KBHT Total conduction for the open gap. See comment 2.

Default = 10-14 * KAHT (Real > 0.0) This default is also set when KBHT=0.

TCID Identification number of a TABLED# entry. This table specifies total gap
conduction based on gap clearance. See comments 2, 3, and 4.

Default = 0 (Integer > 0)

Comments

1. PGAPHT provides heat transfer conductivity for CGAP/CGAPG element. PGAPHT must
match PID with an existing PGAP.

2. KAHT and KBHT represent total gap conduction values for closed and open gaps.
Theoretically, while higher conduction values enforce a perfect conductor, excessively
high values may cause poor conditioning of the conductivity matrix. If any such
symptoms are observed, it may be beneficial to reduce the value of gap conduction, or
use conduction based contact clearance and pressure.

To facilitate reasonable values of KAHT, automatic calculation is supported, specifically:

Option KAHT=AUTO determines the value of KAHT for each gap element using the
conduction of surrounding elements.
3. TCID points to a TABLED# entry that specifies total conduction based on gap clearance.
TCID overrides KBHT. TCID is ignored for linear CGAP/CGAPG elements.

4. Thermal-structural analysis problems involving contact are fully coupled since contact/gap
status changes thermal conductivity. Refer to Contact-based Thermal Analysis in the
User’s Guide for more information.

5. This card is represented as a property in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1845

Proprietary Information of Altair Engineering


PGASK

Bulk Data Entry

PGASK – Gasket Element Property Definition

Description

Defining the properties for solid gasket elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PGASK PID MIDG MID1 C ORDM H0 GAP VOID LEAKP

STABMT

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PGASK 1 2 1 1 0.5

Field Contents

PID Unique gasket element property identification number.

No default (Integer > 0)

MIDG A MGASK entry identification number that defines thickness-direction and


transverse shear behaviors of the gasket.

No default (Integer > 0)

MID1 A MAT1 entry identification number that defines membrane properties and
mass density of the gasket.

Blank means zero membrane stiffness, zero membrane thermal expansion


coefficient, and zero mass density.

Default = blank (Integer > 0 or blank)

1846 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

CORDM Material coordinate system identification number. See comment 3.

-1 means the element local coordinate system, while 0 means the basic
coordinate system.

Default = -1 (Integer > -1)

H0 Prescribed initial thickness of the gasket. See comment 4.

0.0 or blank means using initial thickness of the gasket element.

Default = 0.0 (Real > 0.0)

GAP Initial open gap of the gasket. See comment 5.

Default = 0.0 (Real > 0.0)

VOID Initial void of the gasket. See comment 5.

Default = 0.0 (Real > 0.0)

LEAKP Leakage pressure. See comment 6.

Default = blank (Real > 0.0 or blank)

STABMT Membrane and transverse shear stabilization flag.

0 - no stabilization.

1 - a stabilization stiffness is used if membrane or transverse shear stiffness


is zero.

Default = 0 (Integer = 0 or 1)

Comments

1. All gasket element property entries must have unique identification numbers.

2. PGASK refers to two material entries, MGASK and MAT1. MGASK defines the thickness-
direction and transverse shear behaviors of the gasket material, and MAT1 defines the
membrane behavior of the gasket material.

The thickness-direction stiffness is defined with the unit of stress per unit displacement
(the pressure—closure distance relationship for the thickness compression), the
transverse shear stiffness is defined with either the unit of stress per unit displacement
or the unit of force per unit area, and the membrane stiffness is defined with the unit of
force per unit area (the stress—strain relationship).

Altair Engineering OptiStruct 13.0 Reference Guide 1847

Proprietary Information of Altair Engineering


3. The gasket material coordinate system can be defined as the element local coordinate
system (CORDM = -1) or a prescribed system (CORDM = Integer > 0). The material local
3-direction is taken as the gasket thickness direction, and the material local 1-direction
and 2-direction are taken as the gasket membrane principle directions. If the angle
between the prescribed thickness direction (the material local 3-direction) and the default
one (the element local 3-direction) is larger than 20 degrees, a warning will be provided.

4. The initial thickness includes initial open gap and initial void of the gasket.

5. The total closure of a gasket element consists of the mechanical closure and the thermal
closure, that is:

Ctotal = Cmech + Cthermal

The thermal closure, Cthermal, is calculated as:

Cthermal = ALPHA * (Tref - T) * (H0 - GAP - VOID)

The effective closure, C, which is used to determine pressure with the loading/unloading
of tables defined in the MGASK card, is calculated as:

C = Cmech – GAP

If there is no initial open gap (GAP=0), C and Cmech are identical.

6. The sealing status of gasket is detected with the leakage pressure. If the gasket pressure
is larger than the leakage pressure, it is detected to be sealed – the output status index
value is 1; otherwise, it is leaking – the output status index value is 0.

7. For gasket in contact, STABMT is recommended to be 1, if its membrane or transverse


shear stiffness is zero.

8. The continuation entry is optional.

9. This card is represented as a property in HyperMesh.

1848 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PHFSHL

Bulk Data Entry

PHFSHL – Shell Element Property for One-Step Stamping Simulation

Description

Defines the thickness, material, blank holder, binder and Forming Limit Curve references for a
shell property in a one-step stamping simulation.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PHFSHL PID MID T BHID FLDID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PHFSHL 1 1 0.01 6 2

Field Contents

PID Unique shell element property identification number.

No default (Integer > 0)

MID Material identification number of a MATHF entry.

No default (Integer > 0)

T Thickness

No default (Real > 0.0)

BHID Blank holder ID referring to a BLKHDF entry.

No default (Integer > 0 or blank)

FLDID User-defined Forming Limit Curve ID referring to FLDATA entry.

No default (Integer > 0 or blank)

Altair Engineering OptiStruct 13.0 Reference Guide 1849

Proprietary Information of Altair Engineering


Comments

1. This entry is only valid with an @HyperForm statement in the first line of the input file.

2. All shell element property entries must have unique identification numbers.

3. PHFSHL is referenced by CTRIA3 and CQUAD4 entries.

1850 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PLOAD

Bulk Data Entry

PLOAD – Static Pressure Load

Description

Defines a static pressure load on a triangular or quadrilateral element. It can also be used to
define the EXCITEID field (Amplitude “A”) of dynamic loads in RLOAD1, RLOAD2, TLOAD1 and
TLOAD2 bulk data entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOAD SID P G1 G2 G3 G4

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOAD 1 -4.0 16 32 11 0

Field Contents

SID Load set identification number.

(Integer > 0)

P Pressure.

G1,...G4 Grid point identification numbers.

(Integer > 0; G4 may be 0)

Comments

1. The grid points define either a triangular or a quadrilateral element to which a pressure is
applied. If G4 is zero or blank, the element is triangular.

Altair Engineering OptiStruct 13.0 Reference Guide 1851

Proprietary Information of Altair Engineering


In the case of a triangular element, the assumed direction of the pressure is computed
according to the right-hand rule using the sequence of grid points G1, G2, and G3.

2. The total load on the element, AP, is divided into three equal parts and applied to the grid
points as concentrated loads. A minus sign in field 3 reverses the direction of the load.

3. In the case of a quadrilateral element, the grid points G1, G2, G3, and G4 should form a
consecutive sequence around the perimeter. The right-hand rule is applied to find the
assumed direction of the pressure.

4. This card is represented as a pressure load in HyperMesh.

1852 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PLOAD1

Bulk Data Entry

PLOAD1 – Applied Load on CBAR or CBEAM Elements

Description

Defines concentrated, uniformly distributed, or linearly distributed applied loads to the CBAR or
CBEAM elements at user-chosen points along the axis. It can also be used to define the
EXCITEID field (Amplitude “A”) of dynamic loads in RLOAD1, RLOAD2, TLOAD1 and TLOAD2 bulk
data entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOAD1 SID EID TYPE SC ALE X1 P1 X2 P2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOAD1 25 1065 MY FRPR 0.2 2.5E3 0.8 3.5E3

Field Contents

SID Load set identification number.

No default (Integer > 0)

EID CBAR or CBEAM element identification number.

No default (Integer > 0)

TYPE Load type. See comment 5.

No default (FX, FY, FZ, FXE, FYE, FZE, MX, MY, MZ, MXE, MYE or MZE)

SCALE Determines scale factor for X1, X2. See comments 6, 7, 8 and 9.

No default (LE, FR, LEPR or FRPR)

Altair Engineering OptiStruct 13.0 Reference Guide 1853

Proprietary Information of Altair Engineering


Field Contents

X1, X2 Distances along the CBAR or CBEAM element axis from end A.

For X1: No default; For X2: Default = blank (Real, 0 < X1 < X2)

P1, P2 Load factors at positions X1, X2.

Default = blank (Real or blank)

Comments

1. In the static solution sequences, the load set ID (SID) is selected by the LOAD command
in the Subcase Information section.

2.
positions X1 and X2, having an intensity per unit length of bar equal to P1 at X1 and
equal to P2 at X2, except as noted in comments 8 and 9.

3. If X2 is blank or equal to X1, a concentrated load of value P1 will be applied at position


X1.

4.
will be applied between positions X1 and X2, except as noted in comments 8 and 9.

5. Load TYPE is used as follows to define loads:

"FX", "FY" or "FZ": Force in the x, y, or z direction of the basic coordinate system.

"MX", "MY" or "MZ": Moment in the x, y, or z direction of the basic coordinate system.

"FXE", "FYE" or "FZE": Force in the x, y, or z direction of the element’s coordinate system.

"MXE", "MYE" or "MZE": Moment in the x, y, or z direction of the element’s coordinate


system.

6. If SCALE = "LE" (length), the xi values are actual distances along the element axis, and, if

7. If SCALE = "FR" (fractional), the xi values are ratios of the distance along the axis to the

8. If SCALE = "LEPR" (length projected), the xi values are actual distances along the element

element.

1854 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PLOAD1 C onvention on Beam or Bar Elements

If SCALE = "LE", the total load applied to the bar is P1 (X2 – X1) in the y-basic direction.

If SCALE = "LEPR", the total load applied to the bar is P1 (X2 – X1) cosα in the y-basic
direction.

9. If SCALE = "FRPR" (fractional projected), the Xi values are ratios of the actual distance to

in terms of the projected length of the bar.

10. Element identification numbers for CBAR and CBEAM entries must be unique.

11. Loads on CBEAM elements defined with PLOAD1 entries are applied along the line of the
shear centers.

12. If on the TYPE field of the PLOAD1 entry, the element coordinate system direction (for
example, TYPE = FYE) option is selected, then the projection (SCALE=FRPR or LEPR)
option is ignored and the result is the same as the SCALE=FR (or LE) option.

13. This card is represented as a pressure load in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1855

Proprietary Information of Altair Engineering


PLOAD2

Bulk Data Entry

PLOAD2 – Pressure Load on a Two-Dimensional Structural Element

Description

Defines a uniform static pressure load applied to two-dimensional elements. Only QUAD4 or
TRIA3 elements may have a pressure load applied to them via this entry. It can also be used
to define the EXCITEID field (Amplitude “A”) of dynamic loads in RLOAD1, RLOAD2, TLOAD1
and TLOAD2 bulk data entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOAD2 SID P EID EID EID EID EID EID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOAD2 21 -3.6 4 16 2

Alternate Format and Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOAD2 SID P EID1 “THRU” EID2 blank blank blank

PLOAD2 1 30.4 16 THRU 48

Field Contents

SID Load set identification number.

(Integer > 0)

1856 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

P Pressure value.

EID, EID1, EID2 Element identification number.

(Integer > 0; EID1<EID2)

Comments

1. EID must be 0 or blank for omitted entries.

2. At least one positive EID must be present on each PLOAD2 entry.

3. If the alternate form is used, all elements EID1 through EID2 must be two-dimensional.

4. The direction of the pressure is computed according to the right-hand rule using the grid
point sequence specified on the element entry. Refer to the PLOAD entry.

5. All elements referenced must exist.

6. Continuations are not allowed.

7. This card is represented as a pressure load in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1857

Proprietary Information of Altair Engineering


PLOAD4

Bulk Data Entry

PLOAD4 – Pressure Loads on Face of Structural Elements

Description

Defines a load on a face of a HEXA, PENTA, TETRA, PYRA, TRIA3, TRIA6, QUAD4, or QUAD8
element. It can also be used to define the EXCITEID field (Amplitude “A”) of dynamic loads in
RLOAD1, RLOAD2, TLOAD1 and TLOAD2 bulk data entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOAD4 SID EID P1 P2 P3 P4 G1 G3 or


G4

C ID N1 N2 N3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOAD4 2 1106 10.0 8.0 5.0 1.0 1 48

6 0.0 1.0 0.0

Alternate Format and Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOAD4 SID EID1 P1 P2 P3 P4 “THRU” EID2

C ID N1 N2 N3

PLOAD4 2 1106 10.0 8.0 5.0 THRU 1143

6 0.0 1.0 0.0

1858 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

SID Load set identification number.

(Integer > 0)

EID1, EID2 Element identification number.

(Integer > 0, EID1 < EID2)

P1, P2, P3, P4 Load per unit surface area (pressure) at the corners of the face of the
element (real or blank). (P1 is the default for P2, P3, and P4).

G1 Identification number of a grid point connected to a corner of the face.


Required data for solid elements only (Integer or blank). For PYRA
elements, this grid must be on an edge of the quadrilateral face.

G3 Identification number of a grid point connected to a corner diagonally


opposite to G1 on the same face of a HEXA or PENTA element. Required
data for quadrilateral faces of HEXA and PENTA elements only (Integer or
blank). G3 must be omitted for a triangular surface on a PENTA element
and the quadrilateral face on a PYRA element. For triangular faces of
PYRA elements, this grid must be on the edge next to the quadrilateral
face. G1 and G3 must define a positive direction into the element using
the right hand rule.

G4 Identification number of the TETRA grid point located at the corner not
on the face being loaded. This is required data and is used for TETRA
elements only.

CID Coordinate system identification number.

(Integer > 0)

N1, N2, N3 Components of vector measured in coordinate system defined by CID


(Real). Used to define the direction (but not the magnitude) of the load
intensity. See comment 10.

Comments

1. The continuation is optional. If fields 2, 3, 4, and 5 of the continuation are blank, the
load is assumed to be a pressure acting normal to the face. If these fields are not blank,
the load acts in the direction defined in these fields. Note that, if CID is a curvilinear
coordinate system, the direction of load may vary over the surface of the element. The
load intensity is the load per unit of surface area, not the load per unit of area normal to

Altair Engineering OptiStruct 13.0 Reference Guide 1859

Proprietary Information of Altair Engineering


the direction of loading.

2. For solid elements the direction of positive pressure (defaulted continuation card) is
inward. The load intensity P1 acts at grid point G1 and load intensities P2, P3 (and P4)
act at the other corners in a sequence determined by applying the right hand rule to the
outward normal.

3. For plate elements the direction of positive pressure (defaulted continuation) is in the
direction of positive normal, determined by applying the right hand rule to the sequence of
connected grid points. The load intensities PI, P2, P3 (and P4) act respectively at corner
points G1, G2, G3 (and G4). (See plate connection).

4. If P2, P3 (and P4) are blank fields, the load intensity is uniform and equal to P1. P4 has
no meaning for a triangular face and may be left blank in this case.

5. Equivalent grid point loads are computed by linear (or bilinear) interpolation of load
intensity, followed by numerical integration using isoperimetric shape functions. Note that
uniform load intensity does not necessarily result in equal equivalent grid point loads.

6. G1 and G3 are ignored for TRIA3, TRIA6, QUAD4, and QUAD8 elements.

7. The alternate form is available only for TRIA3, TRIA6, QUAD4, and QUAD8 elements. The
continuation card may be used in the alternate form.

8. For triangular faces of PENTA elements, G1 is an identification number of a corner grid


point that is on the face being loaded and the G3 or G4 field is left blank. For faces of
TETRA elements, G1 is an identification number of a corner grid point that is on the face
being loaded and G4 is an identification number of the corner grid point that is not on the
face being loaded. Since a TETRA has only four corner points, this point, G4, is unique
and different for each of the four faces of a TETRA element.

9. For the quadrilateral face of the PYRA element, G1 is an identification number of a corner
grid point on the face and the G3 or G4 field is left blank. For the triangular faces, G1 and
G3 must specify the grids on the edge of the face that borders the quadrilateral face and
the grids must be ordered so that they define an inward normal using the right hand rule.

10. N1, N2, and N3 are not supported in NLGEOM subcases.

11. This card is represented as a pressure load in HyperMesh.

1860 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PLOADX1

Bulk Data Entry

PLOADX1 – Static Pressure Load on Axisymmetric Element

Description

Defines a static surface traction on the CTAXI and CTRIAX6 axisymmetric elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOADX1 SID EID PA PB GA GB Theta

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOADX1 3 20 10.5 12.5 11 13 15.0

Field Contents

SID Load set identification number.

(Integer > 0)

EID Element identification number.

(Integer > 0)

PA Surface traction at grid point GA.

No default (Real)

PB Surface traction at grid point GB.

Default = PA (Real or blank)

GA, GB Identification numbers of two adjacent corner grid points on the element
side.

Altair Engineering OptiStruct 13.0 Reference Guide 1861

Proprietary Information of Altair Engineering


Field Contents

No default (Integer > 0)

Theta Angle between surface traction and inward normal to the line segment.

Default = 0.0 (Real or blank)

Comments

1. The surface traction is assumed to vary linearly along the element side between GA and
GB.

2. The surface traction is input as force per unit area.

3. “Theta” is measured counter-clockwise from the inward normal of the straight line
between GA and GB, to the vector of the applied load, as shown in the figure below.
Positive pressure is in the direction of inward normal to the line segment.

Pressure Load on C TRAX6 and C TAXI Elements

4. This card is represented as a pressure load in HyperMesh.

1862 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PLOTEL

Bulk Data Entry

PLOTEL – Dummy Plot Element Definition

Description

Defines a one-dimensional dummy element for use in plotting.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOTEL EID G1 G2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOTEL 29 35 16

Field Contents

EID Unique element identification number.

No default (Integer > 0)

G1,G2 Grid point identification numbers of connection points.

Comments

1. This element is not used in the model during any of the solution phases of a problem. It is
used to simplify the plotting of structures with large numbers of collinear grid points,
where the plotting of each grid point along with the elements connecting them would
result in a confusing plot.

2. Element identification numbers should be unique with respect to all other element
identification numbers.

3. Only one PLOTEL element may be defined on a single entry.

4. This card is represented as a plot element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1863

Proprietary Information of Altair Engineering


PLOTEL3

Bulk Data Entry

PLOTEL3 – Dummy Plot Element Definition

Description

Defines a three-noded, two-dimensional dummy element for use in plotting.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOTEL3 EID G1 G2 G3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOTEL3 29 35 16 22

Field Contents

EID Unique element identification number.

No default (Integer > 0)

G1, G2, G3 Grid point identification numbers of connection points.

Comments

1. This element is not used in the model during any of the solution phases of a problem. It is
used to simplify the plotting of large structures.

2. Element identification numbers should be unique with respect to all other element
identification numbers.

3. This card is represented as a tria3 element in HyperMesh.

1864 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PLOTEL4

Bulk Data Entry

PLOTEL4 – Dummy Plot Element Definition

Description

Defines a four-noded, two-dimensional dummy element for use in plotting.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOTEL4 EID G1 G2 G3 G4

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLOTEL4 29 35 16 22 23

Field Contents

EID Unique element identification number.

No default (Integer > 0)

G1, G2, G3, G4 Grid point identification numbers of connection points.

Comments

1. This element is not used in the model during any of the solution phases of a problem. It is
used to simplify the plotting of large structures.

2. Element identification numbers should be unique with respect to all other element
identification numbers.

3. This card is represented as a quad4 element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1865

Proprietary Information of Altair Engineering


PLSOLID

Bulk Data Entry

PLSOLID – Nonlinear Hyperelastic Solid Element Property

Description

The PLSOLID bulk data entry defines the properties of nonlinear hyperelastic solid elements,
referenced by CHEXA, CPENTA, and CTETRA bulk data entries. The MATHE hyperelastic
material can be referenced to define corresponding material properties.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLSOLID PID MID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLSOLID

Field Contents

PEID Unique solid element property identification number.

No default (Integer > 0)

MID Identification number of a MATHE bulk data entry.

No default (Integer > 0)

Comments

1. All solid element property entries must have unique identification numbers.

2. The PLSOLID bulk data entry can be referenced by a CHEXA, CPENTA or CTETRA bulk
data entry.

3. This card is represented as a property in HyperMesh.

1866 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PLY

Bulk Data Entry

PLY – Ply Information for Ply-based Composite Definition

Description

Defines the properties of a ply used in ply-based composite definition.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLY ID MID T THETA SOUT TMANUF DID

ESID1 ESID2 ESID3 ESID4 ESID5 ESID6 ESID7 ESID8

ESID9 …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PLY 1 2 0.1 45 YES 0.01

Field Contents

ID Unique ply identification number.

No default (Integer > 0)

MID Material identification number. Must refer to a MAT1, MAT2 or MAT8 bulk data
entry.

No default (Integer > 0)

T Ply thickness.

No default (Real > 0.0)

Altair Engineering OptiStruct 13.0 Reference Guide 1867

Proprietary Information of Altair Engineering


Field Contents

THETA Ply orientation angle, in degrees, of the longitudinal direction relative to the x-
axis of the material coordinate system associated with a given element. If no
material coordinate system is prescribed for the element, the angle is measured
relative to side 1-2 of this element.

Default = 0.0 (Real or blank)

SOUT Stress, Strain, and Failure Index output request. See comments 2 and 3.

Default = NO (YES or NO)

TMANUF Thickness of one manufacturable ply. See comment 4.

Default = blank (Real or blank)

DID Draping identification number. Must refer to a DRAPE bulk data entry.

Default = blank (Integer > 0)

ESID# Element SET identification numbers. Lists the elements for which this PLY card
is defined. No continuation line indicates that all elements should be included.

Default = blank (Integer > 0)

Comments

1. The PLY card is used in combination with the PCOMPP and STACK cards to create
composite properties through the ply-based definition.

2. Stress, Strain and Failure Index output for the PLY is activated by setting SOUT to YES.
In addition, the I/O Options CSTRESS (controlling Stress and Failure Index output) and/or
CSTRAIN (controlling Strain output) must be defined. Failure Index output also requires
that the FT and SB fields be defined on the corresponding PCOMPP card, and that stress/
strain allowables on the referenced materials are defined.

3. An additional piece of information available with ply results is "failure index for the
element," which is the maximum of failure indices for individual plies in this element. Note
that only the plies with SOUT set to YES are considered in the evaluation of this
maximum.

4. TMANUF defines the thickness of one manufacturable ply. This parameter is used during
sizing optimization to automatically create discrete design variables such that the
thickness of the ply bundle is equal to a multiple of TMANUF.

5. This card is represented as a ply in HyperMesh.

1868 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PMASS

Bulk Data Entry

PMASS – Scalar Mass Property

Description

Defines the mass value of a scalar mass element (CMASS1 or CMASS3 entry).

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PMASS PID1 M1 PID2 M2 PID3 M3 PID4 M4

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PMASS 7 4.29 6 13.2

Field Contents

PIDi Property identification number.

(Integer > 0)

Mi Value of scalar mass.

(Real)

Comments

1. Mass values are defined directly on the CMASS2 entry, and therefore do not require a
PMASS entry.

2. Up to four mass values may be defined by this entry.

3. This card is represented as a property in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1869

Proprietary Information of Altair Engineering


PRBODY

Bulk Data Entry

PRBODY – Rigid Body Definition for Multi-body Simulation

Description

Defines a rigid body out of a list of finite element properties, elements and grid points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PRBODY BID BODY_NAME

TYPE1 ID1 ID2 ID3 ID4 ID5 ID6 ID7

ID8 …

TYPE2 ID1 ID2 …

TYPE# …

MASS M

INERTIA IXX IYY IZZ IXY IXZ IYZ C ID

C OG X,G Y Z

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PRBODY 3 ARM1

PSHELL 23 21

1870 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PBEAM 9 59 48

C ONM2 2345

GRID 400 401 402

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PRBODY 4 LEVER

PBAR 10 11 13 15 22 99 88

44

MASS 100.0

INERTIA 120.0 130.0 123.0 0.0 0.0 0.0

C OG 29

Field Contents

BID Unique body identification number.

No default (Integer > 0)

BODY_NAME Unique body name. This body name for this PRBODY.

Default = OUTFILE_body_<BID> (Character string)

TYPE# Flag indicating that the following list of IDs refer to entities of this
type. All property definitions; CELAS2, CONM2, PLOTEL, RBE2, RBE3,
RBAR, RROD, and GRID are valid types for this field.

Altair Engineering OptiStruct 13.0 Reference Guide 1871

Proprietary Information of Altair Engineering


Field Contents

No default (PBAR, PBARL, PBEAM, PBEAML, PBUSH, PCOMP, PCOMPP,


PCOMPG, PDAMP, PELAS, PGAP, PROD, PSHEAR, PSHELL, PSOLID,
PVISC, PWELD, CELAS2, CONM2, PLOTEL, RBE2, RBE3, RBAR, RROD,
GRID)

ID# Identification numbers of entities of the preceding TYPE flag.

No default (Integer > 0)

MASS Flag to overwrite the finite element mass of the body. Indicates that
a mass value is to follow.

M Mass.

(Real > 0.0)

INERTIA Flag to overwrite the finite element inertia of the body. Indicates
that the inertia properties are to follow.

IXX,IYY,IZZ, Moments of inertia.


IXY,IXZ,IYZ
(For IXX, IYY, IZZ Real > 0.0; For IXY, IXZ, IYZ Real)

CID Coordinate system identification number to define the orientation of


the inertia tensor.

(Integer > 0 or blank)

COG Flag to overwrite the finite element center of gravity of the body.
Indicates that the center of gravity is to follow.

X, Y, Z Location of the center of gravity.

(Real)

G Grid point identification number to optionally supply X, Y, and Z.

(Integer > 0)

Comments

1. Any number of property definitions; CELAS2, CONM2, PLOTEL, RBAR, RBE2, RBE3 or RROD
elements or grid points can be given.

1872 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


2. At least one property definition, element, or grid point must be given.

3. A property definition; CELAS2, CONM2, PLOTEL, RBE2, RBE3, RBAR or RROD element or grid
point can only belong to one rigid or flexible body.

4. All property definitions, elements and grid points defined on a PRBODY bulk data entry
form one rigid body. The mass and inertia properties are defined by the finite element and
mass properties unless they are overwritten by the mass and inertia properties given on
the continuation lines.

5. The mass, inertia and center of gravity input is optional if element/property information is
provided in the PRBODY definition.

6. If one of MASS, INERTIA or COG continuations is provided, all three continuations must be
provided.

7. A CID of zero or blank references the basic coordinate system.

8. MASS must be positive non-zero values.

9. If just the principal inertia is specified, IXX, IYY, and IZZ must be positive non-zero
values and they must satisfy the condition: the sum of two inertia values must be greater
than the third (IXX + IYY > IZZ, IYY+IZZ > IXX, IZZ+IXX > IYY).

10. This card is represented as a group in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1873

Proprietary Information of Altair Engineering


PRETENS

Bulk Data Entry

PRETENS – 1D or 3D Bolt Pretension Section

Description

Defines 1D or 3D pretensioned bolt section.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PRETENS SID EID SURFID NTYP G1/X1/ G2 / X2 G3 / X3 SPNTID


C ID

Examples

1D pretensioned bolt:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PRETENS 2 5

3D pretensioned bolt:

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PRETENS 3 4

Field Contents

SID Unique section identification number.

EID Element identification number of a bar, beam or rod element for defining
1D pretensioned bolt.

(Integer > 0 for 1D pretensioned bolt, or blank for 3D pretensioned bolt)

1874 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

SURFID Identifier of SURF card which defines cutting section of 3D pretensioned


bolt.

(Integer > 0 for 3D pretensioned bolt, or blank for 1D pretensioned bolt)

See comment 2.

NTYP Type of determination of normal to the pretension section. See


comment 3.

AUTO – automatic determination based on the configuration of the


pretension section.

GRIDS – use G1, G2, G3 to define the plane of pretension – normal to


this plane defines the pretension direction.

VECTOR – use the vector X1, X2, X3 to define pretension direction.

CID – use prescribed coordinate system.

Default = blank = AUTO (AUTO, GRIDS, VECTOR, or CID).

G1, G2, G3 Three grid identifiers that define the plane where its normal is the
direction of the bolt.

Default = blank (Integer > 0). When prescribed, all three nodes must
be prescribed.

X1, X2, X3 Coordinates, in basic system, of the vector that defines direction of
pretension.

Default = blank (Real). The length of the vector must be non-zero.

CID Identifier of a coordinate system that defines direction of pretension.

For rectangular system, the local x-axis defines the pretension


direction;

For cylindrical and spherical systems, the local z-axis defines the
pretension direction.

Default = blank (Integer > 0).

SPNTID SPOINT that defines the DOF containing the pretension deformation and
load.

Default is not to output the pretension deformation in results files.

Comments

1. Each 1D pretension section defines only one element.

Altair Engineering OptiStruct 13.0 Reference Guide 1875

Proprietary Information of Altair Engineering


2. A surface defined by SURFID should be constructed by solid elements on the same side of
the surface.

3. The default direction of pretension is defined automatically from the configuration of the
pretension section.

For 1D elements, it is along the axis of the respective 1D element.


For 3D pretension, it is defined as the average normal to the respective SURFace
(average of respective element normals).

1876 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PRETPRM

Bulk Data Entry

PRETPRM – Parameters for 1D and 3D bolt pretensioning

Description

Defines parameters that control initial loading conditions on pretension sections for 1D and 3D
bolt pretensioning. These parameters also control the printing of diagnostic information about
pretension sections.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PRETPRM PARAM1 VAL1 PARAM2 VAL2 - etc -

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PRETPRM INILOAD ZEROF PRTSW YES

Field Contents

PARM# Name of the parameter

VAL# Value of the parameter

The available parameters and their values are listed below (click the parameter name for
parameter descriptions).

Parameter Description Values

INILOAD Defines the handling of initial loading conditions "ZEROF” or “ZEROA”


on pretension sections that have been defined, Default = “ZEROF”
but not yet explicitly loaded via PRETENSION
command.

Altair Engineering OptiStruct 13.0 Reference Guide 1877

Proprietary Information of Altair Engineering


Parameter Description Values

PRTSW Switch for printing diagnostic information about <YES, NO>


pretension sections. Default = NO

1878 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PRETPRM, INILOAD

Parameter Values Description

INILOAD "ZEROF” or “ZEROA” Defines the handling of initial loading conditions


on pretension sections that have been defined,
Default = “ZEROF” but not yet explicitly loaded via PRETENSION
command.

If “ZEROF”, in a pretensioning subcase, for any


pretension section without pretension load, zero
force will be applied. This is equivalent to
prescribing zero PTFORCE.

If “ZEROA”, zero relative deformation is


enforced on the pretension section defined
above. This is equivalent to prescribing zero
PTADJST.

Altair Engineering OptiStruct 13.0 Reference Guide 1879

Proprietary Information of Altair Engineering


PRETPRM, PRTSW

Parameter Values Description

PRTSW <YES, NO> Switch for printing diagnostic information about


pretension sections.
Default = NO
If NO, diagnostic information will not be printed.

If YES, diagnostic information will be printed to


the .out file.

1880 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PROD

Bulk Data Entry

PROD – Rod Property

Description

Defines the properties of a rod, which is referenced by the CROD entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PROD PID MID A J C NSM

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PROD 17 23 42.6 0.5

Field Contents

PID Unique rod property identification number.

No default (Integer > 0)

MID Material identification number. See comment 1.

No default (Integer > 0)

A Area of rod.

No default (Real)

J Torsional constant.

No default (Real)

Altair Engineering OptiStruct 13.0 Reference Guide 1881

Proprietary Information of Altair Engineering


Field Contents

C Coefficient to determine torsional stress.

Default = 0.0 (Real)

NSM Nonstructural mass per unit length.

No default (Real)

Comments

1. For structural problems, MID may reference only a MAT1 material entry. For heat transfer
problems, MID may reference only a MAT4 material entry.

2. All rod property entries must have unique property identification numbers.

3. Torsional stress is calculated as follows:

CM
J

Where,

M
is the torsional moment

C is the coefficient specified in field C


J is the torsional constant specified in field J
4. This card is represented as a property in HyperMesh.

1882 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PSEAM

Bulk Data Entry

PSEAM – CSEAM Element Property

Description

Define properties of connector (CSEAM) elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PSEAM PID MID TYPE W T

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PSEAM 30 2 LINE 0.8

Field Contents

PID Property identification number.

No default (Integer > 0)

MID Material identification number of a MAT1 or MAT9 entry. See comment 1.

No default (Integer > 0)

TYPE Type of seam weld generated.

Default = LINE (Character)

W Width of the seam weld. See comment 2.

No default (Real > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1883

Proprietary Information of Altair Engineering


Field Contents

T Thickness of the seam weld. See comment 3.

No default (Real > 0)

Comments

1. Material MID is used to calculate the stiffness of the connector (the fictitious CHEXA).
MID can only refer to the MAT1 or MAT9 bulk data entry.

2. The distance between GS and GE is the length of the element. The width of the seam
weld is measured perpendicular to the length and lies in the plane of Shell A or B. See
figure below.

3. If the entry of T is left blank, the thickness of this seam weld will be calculated as the
averaged thickness of Shell A and B.

4. This card is represented as a property in HyperMesh.

1884 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PSEC

Bulk Data Entry

PSEC – Section Property Definition

Description

Defines property information for planar section elements used in the definition of arbitrary
beam cross-sections.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PSEC PID MID T

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PSEC 5 100 0.1

Field Contents

PID Property identification number.

No default (Integer > 0)

MID Identification number of a material definition.

No default (Integer > 0)

T Thickness.

No default (Real > 0.0)

Comments

1. All property identification numbers within a section definition must be unique with respect
to all other property identification numbers within the same section definition.

Altair Engineering OptiStruct 13.0 Reference Guide 1885

Proprietary Information of Altair Engineering


2. This entry is only valid when it appears between the BEGIN and END statements.

1886 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PSHEAR

Bulk Data Entry

PSHEAR – Shear Panel Property

Description

Defines the properties of a shear panel.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PSHEAR PID MID T NSM F1 F2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PSHEAR 21 2 .001

Field Contents

PID Unique shear property identification number.

(Integer > 0)

MID Material identification number of a MAT1 entry.

(Integer > 0)

T Thickness of shear panel.

NSM Nonstructural mass per unit area.

(Real)

Altair Engineering OptiStruct 13.0 Reference Guide 1887

Proprietary Information of Altair Engineering


Field Contents

F1 Effectiveness factor for extensional stiffness along edges 1-2 and 3-4. See
comment 2.

Default = 0.0 (Real > 0.0)

F2 Effectiveness factor for extensional stiffness along edges 2-3 and 1-4. See
comment 2.

Default = 0.0 (Real > 0.0)

Comments

1. The effective extensional area is defined by means of equivalent rods on the perimeter of
the element. If F1 < 1.01, the areas of the rods on edges 1-2 and 3-4 are set equal to
(F1 ×× T ×× PA)/(L12 + L34), where PA is the panel surface areas - half the vector
cross product area of the diagonals - and L12 and L34 are the lengths of sides 1-2 and 3-
4. Thus, if F1 = 1.0, the panel is fully effective for extension in the 1-2 direction. If F1 >
1.01, the areas of the rods on edges 1-2 and 3-4 are each set equal to 0.5 ×× F1 ×× T.

Extensional Area for Shear Panel

Thus, if F1 = 30, the effective width of skin contributed by the panel to the flanges on
edges 1-2 and 3-4 is equal to 15T. The significance of F2 for edges 2-3 and 1-4 is
similar.

2. Poisson's ratio coupling for extensional effects is ignored.

3. This card is represented as a property in HyperMesh.

1888 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PSHELL

Bulk Data Entry

PSHELL – Shell Element Property

Description

Defines the membrane, bending, transverse shear, and membrane-bending coupling of shell
elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PSHELL PID MID1 T MID2 12I/T3 MID3 TS/T NSM

Z1 Z2 MID4 T0 ZOFFS

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PSHELL 203 204 1.90 205 1.2 206 0.8 6.32

+.95 -.95 0.1

Field Contents

PID Unique shell element property identification number.

(Integer > 0)

MID1 Material identification number for membrane. See comment 3.

(Integer > 0)

T Default value for the membrane thickness (Real > 0.0). If T0 is defined for
topology optimization, T is the total thickness.

Altair Engineering OptiStruct 13.0 Reference Guide 1889

Proprietary Information of Altair Engineering


Field Contents

MID2 Material identification number for bending. See comment 3.

(Integer > -1 or blank)

12I/T3 Bending stiffness parameter.

Default = 1.0 (Real > 0.0 or blank)

MID3 Material identification number for transverse shear. See comment 3.

(Integer > 0 or blank, must be blank unless MID2 > 0)

TS/T Transverse shear thickness divided by the membrane thickness.

Default = .833333 (Real > 0.0 or blank)

NSM Nonstructural mass per unit area.

(Real)

Z1,Z2 Fiber distances for stress computation. The positive direction is determined by
the right hand rule and the order in which the grid points are listed on the
connection entry.

(Real or blank, See comment 7 for defaults)

MID4 Material identification number for membrane-bending coupling.

(Integer > 0 or blank, must be blank unless MID1>0 and MID2>0, may not be
equal to MID1 or MID2). See comments 10 and 11.

T0 The base thickness of the elements in topology optimization. Only for MAT1,
T0 can be >0.0. If T0 is blank, then the elements are not included in the
topology design volume or space.

(Real > 0.0 or blank for MAT1, Real = 0.0 or blank for MAT2, MAT8)

ZOFFS Offset from the plane defined by element grid points to the shell reference
plane.

Real or Character Input (Top/Bottom). See comment 15.

Comments

1. All shell element property entries must have unique identification numbers.

1890 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


2. The structural mass is computed from the density using the membrane thickness and
membrane material properties.

3. MID1 cannot be left blank. The effect of leaving an MID2 or MID3 field blank is:

MID2 Pure membrane in plane stress – no bending, coupling, or transverse


(If left blank) shear stiffness. MID3 and MID4 must also be blank.

MID3 No transverse shear deformation is considered (this is actually


(If left blank) accomplished by enforcing very high transverse shear stiffness).

If MID2 = -1 Plane strain. In-plane stiffness only. No bending or transverse shear


stiffness. See comments 13 and 14.

4. The continuation is not required.

5. This entry is used in connection with the CTRIA3, CQUAD4, CTRIA6, and CQUAD8 entries.

6. PSHELL entries may reference MAT1, MAT2, MAT4, MAT5, and MAT8 material property
entries.

7. The default for Z1 is -T/2, and for Z2 it is +T/2. T is the local plate thickness, defined by
T on this entry. For free-sizing optimization, Z1 and Z2 definitions are ignored and the
defaults of –T/2 and +T/2 are used for each element.

8. If MID3 references a MAT2 material, then G33 on the MAT2 data must be blank.

9. If MID3 references a MAT8 material, then G1Z and G2Z must not be blank.

10. MID4 provides a way to represent shells with offset (shell element centerline being offset
from the plane of the grid points) or shells with material properties that are not symmetric
with respect to the middle surface of the shell. However, whenever possible, the
preferred method of representing such shells is through the use of element offset ZOFFS
or the composite property PCOMP. This is because MID4 does not provide sufficient
information about the shell structure to correctly calculate all respective results,
specifically:

The shell stresses calculated in the presence of MID4 are generally incorrect, as they
do not reflect the actual shell offset or the non-uniform material structure.
The effects of MID4 are not considered in the calculation of differential stiffness.
Hence, it is recommended that MID4 be left blank in buckling analysis.
11. If MID4 points to a MAT2 card with a material ID greater than 400,000,000, then the
thermal membrane-bending coefficients A1, A2, and A12 have a modified interpretation,
and represent [G]*[alpha] rather then [alpha]. Here, [G] is a matrix composed of G11,
G22,…G33. This is to maintain consistency with respective terms generated internally by
the PCOMP card.

12. Thermal expansion coefficients provided for materials referenced as MID2 or MID3 are
ignored in shell analysis - only the thermal expansion terms for materials referenced as
MID1 (membrane) and MID4 (coupling) are considered. Furthermore, the reference
temperature (TREF) for the shell property is taken from the material referenced as MID1 -
TREF's provided for other MID's are ignored.

Altair Engineering OptiStruct 13.0 Reference Guide 1891

Proprietary Information of Altair Engineering


13. Plane strain (MID2=-1) MID1 must reference a MAT1 entry.

14. In plane strain computations, in-plane loads are interpreted as line loads with a value
equal to the load, divided by the thickness. Thus, if a thickness of "1.0" is used, the
value of the line-load equals the load value. Pressure can be approximated with multiple
line loads where the pressure value equals the line-load, divided by the length between
the loads.

15. The shell reference plane can be offset from the plane defined by the element nodes by
means of ZOFFS. In this case all other information, such as material matrices or fiber
locations for the calculation of stresses, is given relative to the offset reference plane.
Shell results, such as shell element forces, are output on the offset reference plane.
ZOFFS can be used in all types of analysis and optimization.

ZOFFS can be input in two different formats:

1. Real:
A positive or a negative value of ZOFFS is specified in this format. A positive value of
ZOFFS implies that the reference plane of each shell element is offset a distance of
ZOFFS along the positive z-axis of its element coordinate system.

2. Surface:
This format allows you to select either “Top” or “Bottom” option to specify the offset
value.

Top:

The top surface of the shell element and the plane defined by the element nodes are
coplanar.

This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
element. (The sign of the ZOFFS value would depend on the direction of the offset with
respect to the positive z-axis of the element coordinate system, as defined in the Real
section). See Figure 1.

Figure 1: Top option in ZOFFS

Bottom:

The bottom surface of the shell element and the plane defined by the element nodes are
coplanar.

This makes the effective "Real" ZOFFS value equal to half of the thickness of the PSHELL
element. (The sign of the ZOFFS value would depend on the direction of the offset with

1892 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


respect to the positive z-axis of the element coordinate system, as defined in the Real
section). See Figure 2.

Figure 2: Bottom option in ZOFFS

When ZOFFS is used, both MID1 and MID2 must be specified; otherwise singular matrices
would result.

Moreover, while offset is correctly applied in geometric stiffness matrix and thus can be
used in linear buckling analysis, caution is advised in interpreting the results. Without
offset, a typical simple structure will bifurcate and loose stability “instantly” at the critical
load, shown in Figure (a). With offset though, the loss of stability is gradual and
asymptotically reaches a limit load, as shown below in Figure (b).

Thus, the structure with offset can reach excessive deformation before the limit load is
reached. Note that the above illustrations apply to linear buckling – in a fully nonlinear
limit load simulation, additional instability points may be present on the load path.

16. This card is represented as a property in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1893

Proprietary Information of Altair Engineering


PSHELLX

Bulk Data Entry

PSHELLX – Optional SHELL Property Extension for Geometric Nonlinear Analysis

Description

Defines additional SHELL properties for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PSHELLX PID ISHELL ISH3N ISMSTR NIP HM HF HR

DM DN ITHIC K IPLAS

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PSHELL 73 7 1.0 7 7

PSHELLX 73 24 5

Field Contents

PID Property ID of the associated PSHELL. See comment 1.

No default (Integer > 0)

ISHELL Flag for CQUAD4 element formulation.

Default as defined by XSHLPRM (Integer)

1 - Q4, visco-elastic hourglass modes orthogonal to deformation and rigid


modes (Belytschko).

2 - Q4, visco-elastic hourglass without orthogonality (Hallquist).

1894 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

3 - Q4, elastic-plastic hourglass with orthogonality.

4 - Q4 with improved type 1 formulation (orthogonalization for warped


elements).

12 - QBAT or DKT18 shell formulation.

24 - QEPH shell formulation.

ISH3N Flag for CTRIA3 element formulation.

Default as defined by XSHLPRM (Integer)

1 - Standard triangle (C0).

2 - Standard triangle (C0) with modification for large rotation.

30 - DKT18.

31 - DKT_S3.

ISMSTR Flag for shell small strain formulation.

Default as defined by XSHLPRM (Integer)

1 - Small strain from time = 0.

2 - Full geometric non-linearity with optional small strain formulation activation


by time step XSTEP, TYPEi = SHELL, TSCi = CST.

3 - Alternative small strain formulation from time = 0 (ISHELL =2 only).

4 - Full geometric non-linearity (Time step limit has no effect).

NIP Number of integration points through the thickness. NIP = 0 defines global
integration.

Default as defined by XSHLPRM (0 < Integer < 10)

HM Shell membrane hourglass coefficient (ISHELL = 1, 2, 3, and 4 only).

Default = 0.01 (Real, 0.0 < HM < 0.05)

Except ISHELL = 3: Default = 0.1 (Real)

HF Shell out of plane hourglass coefficient (ISHELL = 1, 2, 3, and 4 only).

Default = 0.01 (0.0 < Real < 0.05)

Altair Engineering OptiStruct 13.0 Reference Guide 1895

Proprietary Information of Altair Engineering


Field Contents

HR Shell rotation hourglass coefficient (ISHELL = 1, 2, 3, and 4 only).

Default = 0.01 (0.0 < Real < 0.05)

Except ISHELL = 3: Default = 0.1 (Real)

DM Shell membrane damping (with MATX27 and MATX36 only).

Default: See comment 11 (Real)

DN Shell numerical damping (ISHELL = 12, 24, ISH3N = 30 only)

Default: See comment 12 (Real)

ITHICK Flag for shell resultant stresses calculation.

Default as defined by XSHLPRM (CONST or VAR)

CONST - Thickness is constant.

VAR - Thickness change is taken into account.

IPLAS Flag for shell plane stress plasticity (with MATX2, MATX27, and MATX36 only).

Default as defined by XSHLPRM (RAD or NEWT)

RAD - Radial return.

NEWT - Iterative projection with 3 Newton iterations.

Comments

1. The property identification number must be that of an existing PSHELL bulk data entry.
Only one PSHELLX property extension can be associated with a particular PSHELL.

2. PSHELLX is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. Q4: Original 4 node OptiStruct shell with hourglass perturbation stabilization.

QEPH: Formulation with physical hourglass stabilization for general use.

QBAT: Modified BATOZ Q4g 24 shell with 4 Gauss integration points and reduced
integration for in-plane shear. No hourglass control is needed for this shell.

DKT18: BATOZ DKT18 thin shell with 3 Hammer integration points.

1896 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


4. If the small strain option (ISMSTR) is set to 1 or 3, engineering strain and stress are
used; otherwise they are true strain and stress.

5. ISHELL = 2 is incompatible with NIP = 1.

6. Global integration (NIP = 0) is only compatible with MAT1, MATS1, MATX2, and MATX36.

7. For MAT1, membrane only behavior happens if NIP = 1. Otherwise, NIP is ignored and
global integration (NIP = 0) is used.

8. For ITHICK = VAR it is recommended to use IPLAS = NEWT.

9. If ITHICK = VAR or IPLAS = NEWT, the small strain option is automatically deactivated.

10. For MATX2, the default value for IPLAS and global integration (NIP=0) is IPLAS = RAD.

11. For MATS1, MATX36 the default value for IPLAS and global integration (NIP=0) is IPLAS =
NEWT.

12. Defaults for DM:

Material Element type ISHELL/ISH3N Default

MATX27 except QEPH, QBAT except 12, 24 5%

QEPH 24 1.5%

QBAT 12 0%

MATX36 except QEPH except 24 0%

QEPH 24 1.5%

13. Defaults for DN:

Element type ISHELL/ISH3N Default Usage

QBAT 12 0.1% All stress terms, except transverse


shear.

QEPH 24 1.5% Hourglass stress.

DKT18 12/30 0.01% Membrane stress only.

14. This card is represented as an extension to a PSHELL property in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1897

Proprietary Information of Altair Engineering


PSLDX6

Bulk Data Entry

PSLDX6 – Optional SOLID Property Extension for Geometric Nonlinear Analysis

Description

Defines additional orthotropic SOLID properties for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PSLDX6 PID ISOLID NIP ISMSTR IC PRE IFRAME DN QS

QB HV DTMIN C ID IP IORTH

Vx Vy Vz THETA

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PSOLID 77 7

PSLDX6 77 24

Field Contents

PID Property ID of the associated PSOLID. See comment 1.

No default (Integer > 0)

ISOLID Flag for solid elements formulation.

Default as defined by XSOLPRM (Integer)

1 - Standard 8-node solid element, 1 integration point. Viscous


hourglass formulation with orthogonal and rigid deformation modes
compensation (Belytschko).

2 - Standard 8-node solid element, 1 integration point. Viscous

1898 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

hourglass formulation without orthogonality (Hallquist).

12 - Standard 8-node solid, full integration (no hourglass).

14 - HA8 locking-free 8-node solid element, co-rotational, full


integration, variable number of Gauss points.

17 - H8C compatible solid full integration formulation.

24 - HEPH 8-node solid element. Co-rotational, under-integrated (1


Gauss point) with physical stabilization.

NIP Number of integration points (ISOLID = 14 and 16 only).

Default as defined by XSOLPRM (Integer = ijk)

2 < i, j, k < 9 for ISOLID =14

< 3, 2 < j < 9 for ISOLID =16

where:

i = Number of integration points in local x direction.


j = Number of integration points in local y direction.
k = Number of integration points in local z direction.

ISMSTR Flag for small strain formulation (ISOLID = 1, 2, 14, and 24 only).

Default as defined by XSOLPRM (Integer)

1 - Small strain from time = 0.

2 - Full geometric non-linearity with small strain formulation activation


by time step.

3 - Simplified small strain formulation from time=0 (non-objective


formulation).

4 - Full geometric non-linearity. Time step limit has no effect.

10 - Lagrange type total strain.

ICPRE Flag for reduced pressure integration (ISOLID = 14 and 24 only).

Default = OFF (ON, OFF, or VAR)

VAR - Variable state between ICPRE = ON and ICPRE = OFF in


function of plasticity state.

Altair Engineering OptiStruct 13.0 Reference Guide 1899

Proprietary Information of Altair Engineering


Field Contents

IFRAME Flag for element coordinate system formulation (ISOLID = 1, 2, 12,


and 17 only).

Default as defined by XSOLPRM (ON or OFF)

DN Numerical damping for stabilization (ISOLID =24 only).

Default = 0.1 (Real)

QS Quadratic bulk viscosity.

Default = 1.1 (Real)

QB Linear bulk viscosity.

Default = 0.05 (Real)

HV Hourglass viscosity coefficient.

Default = 0.1 (0.0 < Real < 0.15)

DTMIN Minimum time step.

Default = 0.0 (Real)

CID Coordinate system identification number to define orthotropic


directions.

(Integer > 0)

IP Reference plane.

Default = 0 (Integer)

0 - Use CID (CID must be different from 0)

1 - Plane (r,s) and angle THETA

2 - Plane (s,t) and angle THETA

3 - Plane (t,r) and angle THETA

11 - Plane (r,s) and orthogonal projection of reference vector (Vx,


Vy, and Vz) on plane (r,s)

12 - Plane (s,t) and orthogonal projection of reference vector (Vx,

1900 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Vy, and Vz) on plane (s,t)

13 - Plane (t,r) and orthogonal projection of reference vector (Vx,


Vy, and Vz) on plane (t,r)

IORTH Flag for orthotropic system formulation.

(Integer = 0, 1)

0 - The first axis of orthotropy is maintained at constant angle with


respect to the orthonormal co-rotational element coordinate system.

1 - The first orthotropy direction is constant with respect to a non-


orthonormal isoparametric coordinates.

Vx X component for reference vector.

(Real)

Vy Y component for reference vector.

(Real)

Vz Z component for reference vector.

(Real)

THETA Orientation angle in degrees of orthotropic with first reference plane


direction.

Default = 0.0 (Real)

Comments

1. The property identification number must be that of an existing PSOLID bulk data entry.
Only one PSLDX6 property extension can be associated with a particular PSOLID.

2. PSLDX6 is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. PSLDX6 is only compatible with 8-node linear solid elements. Quadratic 20-node brick and
6-node pentahedron elements are not compatible, these element types should only be
used with PSOLIDX.

4. The ISOLID flag is not used with CTETRA elements. For elements with 4 and 10 nodes,
the number of integration points is fixed at 1 and 4, respectively.

Altair Engineering OptiStruct 13.0 Reference Guide 1901

Proprietary Information of Altair Engineering


5. For fully-integrated solids (SOLID =12), the deviatoric behavior is computed using 8 Gauss
points; bulk behavior is under-integrated to avoid element locking. It is currently
compatible with material MAT1, MATS1, MATX33, and MATX36.

6. With the small strain option (ISMSTR), strain and stress is engineering strain and stress.
Otherwise, it is true strain and stress.

7. In time history and animation files, the stress tensor is written in the co-rotational frame.

8. Fully-integrated elements (ISOLID =12) only use full geometric non-linearity (corresponds
to ISMSTR = 4). Time step limit has no effect.

9. ISMSTR =10 is only compatible with materials using total strain formulation (MATX42).

10. The time step control XSTEP, TYPEi = SOLID, TSCi = CST only works on elements with
ISMSTR =2.

11. Co-rotational formulation: For ISOLID = 1, 2, 12 and IFRAME = ON, the stress tensor is
computed in a co-rotational coordinate system. This formulation is more accurate if large
rotations are involved. It comes at the expense of higher computation cost. It is
recommended in case of elastic or visco-elastic problems with important shear
deformations. The co-rotational formulation is compatible with 8 node solids.

12. For HA8 (ISOLID = 14) elements: this element uses a locking-free general solid
formulation, co-rotational. The number of Gauss points is defined by NIP flag: for
example, combined with NIP = 222 gives an 8 Gauss integration point element, similar to
ISOLID = 12. The HA8 formulation is compatible with all material laws. Under-integration
for pressure should be used (ICPRE = ON in case of elastic or visco-elastic material; ICPRE
= VAR in case of elasto-plastic material).

13. For H8C (SOLID = 17) elements: Their brick deviatoric behavior is the same as ISOLID =
12, but the bulk behavior can be chosen with ICPRE, and is compatible with all solid type
material laws. ICPRE = VAR is the default value and ICPRE = OFF will not reduce pressure
integration.

14. For HEPH (ISOLID = 24) elements: This element uses an hourglass formulation similar to
QEPH shell elements.

15. ICPRE = VAR is only available for elasto-plastic material law.

16. The hourglass formulation is viscous for ISOLID = 0, 1, and 2.

17. Hourglass viscosity coefficient, HV is not active with 8 point integration.

18. This card is represented as an extension to a PSOLID property in HyperMesh.

1902 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PSOLID

Bulk Data Entry

PSOLID – Solid Element Property

Description

Defines the properties of solid elements, referenced by CHEXA, CPENTA, CPYRA and CTETRA
bulk data entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PSOLID PID MID C ORDM ISOP FC TN DS

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PSOLID 2 100 1

Field Contents

PID Unique solid element property identification number.

No default (Integer > 0)

MID Identification number of a MAT1, MAT4, MAT5, MAT9, MAT10 or


MATPE1 bulk data entry.

No default (Integer > 0)

CORDM MID of material coordinate system. The default is 0, which is the


basic coordinate system.

Default = 0 (Integer > -1)

ISOP Special integration schemes for elasto-plastic nonlinear quasi-static


analysis. The values available are:

Altair Engineering OptiStruct 13.0 Reference Guide 1903

Proprietary Information of Altair Engineering


Field Contents

FULL – full integration, using the same integration schemes as for


linear applications.

MODPLAST – (default) uses special handling of pressure


approximation, designed to circumvent the volumetric locking due to
incompressibility of plastic flow. The specific details differ depending
on the type and order of the element.

REDPLAST – besides special handling for pressure approximation, uses


reduced integration for second-order hexa and penta, and for 8-
noded hexa elements (reduced integration is not practically viable in
other element types, since it would create extensive spurious
modes).

See comments 2 and 3.

(Character: FULL, MODPLAST, REDPLAST or blank)

FCTN Fluid element flag.

SMECH indicates a structural element; PFLUID indicates a fluid


element. PORO indicates poro-elastic material.

Default = SMECH (SMECH, PFLUID or PORO)

DS Design switch. If non-zero, the elements associated with this PSOLID


data are included in the topology design volume or space.

Not valid for fluid elements.

Default = blank (Integer or blank)

Comments

1. All solid element property entries must have unique ID numbers.

2. Special integration flags MODPAST and REDPLAST affect only elasto-plastic materials (as
identified by presence of MATS1) in nonlinear quasi-static subcases. They do not affect
element behavior in linear analysis.

3. The FULL option in the ISOP field provides stable and convergent results, although it may
appear “stiff” and converge rather slowly in cases of significant plastic deformation.
MODPLAST uses special handling for volumetric pressure term, in effect providing good
resolution of plastic flow while avoiding excessive flexibility that would lead to spurious
modes. REDPLAST adds further release of locking tendencies and usually the “softest”
behavior. It may, theoretically, exhibit spurious deformation modes in single unattached
elements, although in practice these modes should vanish in fields of many elements.

1904 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


4. If FCTN = 'PFLUID', then the MID must reference a MAT10 entry. If FCTM=PORO, then
MID must reference a poro-elastic material entry.

5. Stresses are calculated in the material coordinate system. The material coordinate
system may be defined as the basic coordinate system (CORDM = 0), a defined system
(CORDM = Integer > 0), or the element coordinate system (CORDM = -1). Refer to the
CHEXA, CPENTA, CPYRA and CTETRA pages of the Reference Guide for details on how the
material coordinate system is defined for each element.

6. If the material referenced by MID is a MAT9 material definition, then CORDM defines the
material coordinate system for Gij on the MAT9 entry.

7. This card is represented as a property in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1905

Proprietary Information of Altair Engineering


PSOLIDX

Bulk Data Entry

PSOLID – Optional SOLID Property Extension for Geometric Nonlinear Analysis

Description

Defines additional SOLID properties for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PSOLIDX PID ISOLID NIP ISMSTR IC PRE IFRAME DN QS

QB HV DTMIN LAMBDAV MUV IHKT

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PSOLID 77 7

PSOLIDX 77 24

Field Contents

PID Property ID of the associated PSOLID. See comment 1.

No default (Integer > 0)

ISOLID Flag for solid elements formulation.

Default as defined by XSOLPRM (Integer)

1 - Standard 8-node solid element, 1 integration point. Viscous


hourglass formulation with orthogonal and rigid deformation modes
compensation (Belytschko).

2 - Standard 8-node solid element, 1 integration point. Viscous

1906 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

hourglass formulation without orthogonality (Hallquist).

12 - Standard 8-node solid, full integration (no hourglass).

14 - HA8 locking-free 8-node solid element, co-rotational, full


integration, variable number of Gauss points.

16 - Quadratic 20-node solid, full integration, variable number of


Gauss points.

17 - H8C compatible solid full integration formulation.

24 - HEPH 8-node solid element. Co-rotational, under-integrated (1


Gauss point) with physical stabilization.

NIP Number of integration points (ISOLID = 14, 16 only).

Default as defined by XSOLPRM (Integer = ijk)

2 < i, j, k < 9 for ISOLID =14

< 3, 2 < j < 9 for ISOLID =16

where:

i = Number of integration points in local x direction.


j = Number of integration points in local y direction.
k = Number of integration points in local z direction.

ISMSTR Flag for small strain formulation (ISOLID = 1, 2, 14, and 24 only).

Default as defined by XSOLPRM (Integer)

1 - Small strain from time = 0.

2 - Full geometric non-linearity with small strain formulation activation


by time step.

3 - Simplified small strain formulation from time=0 (non-objective


formulation).

4 - Full geometric non-linearity. Time step limit has no effect.

10 - Lagrange type total strain.

ICPRE Flag for reduced pressure integration (ISOLID = 14, 17, and 24 only).

Default = OFF for ISOLID = 14, 24, ON for ISOLID = 17 (ON, OFF, or
VAR)

Altair Engineering OptiStruct 13.0 Reference Guide 1907

Proprietary Information of Altair Engineering


Field Contents

VAR - Variable state between ICPRE = ON and ICPRE = OFF in


function of plasticity state.

IFRAME Flag for element coordinate system formulation (ISOLID = 1, 2, 12, 17


only).

Default as defined by XSOLPRM (ON or OFF)

DN Numerical damping for stabilization (ISOLID =24 only).

Default = 0.1 (Real)

QS Quadratic bulk viscosity.

Default = 1.1 (Real)

QB Linear bulk viscosity.

Default = 0.05 (Real)

HV Hourglass viscosity coefficient.

Default = 0.1 (0.0 < Real < 0.15)

DTMIN Minimum time step.

Default = 0.0 (Real)

LAMBDAV Numerical Navier Stokes viscosity

No default (Real)

MUV Numerical Navier Stokes viscosity

No default (Real)

IHKT Hourglass tangent modulus flag (ISOLID = 24 only)

Default = 1 (Integer = 1, 2)

1 - Elastic modulus or numerical tangent modulus estimation.

2 - Advanced tangent modulus estimation.

1908 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. The property identification number must be that of an existing PSOLID bulk data entry.
Only one PSOLIDX property extension can be associated with a particular PSOLID.

2. PSOLIDX is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. The ISOLID flag is not used with CTETRA elements. For these elements with four and ten
nodes, the number of integration points is fixed at one and four, respectively.

4. For fully integrated solids (SOLID =12), the deviatoric behavior is computed using 8 Gauss
points; bulk behavior is under-integrated to avoid element locking. It is currently
compatible with material MAT1, MATS1, MATX33, and MATX36.

5. With the small strain option (ISMSTR), strain and stress is engineering strain and stress.
Otherwise, it is true strain and stress.

6. In time history and animation files, the stress tensor is written in the co-rotational frame.

7. Fully integrated elements (ISOLID =12) only uses full geometric non-linearity (corresponds
to ISMSTR = 4). Time step limit has no effect.

8. ISMSTR = 10 is only compatible with materials using total strain formulation (MATX42).

9. The time step control XSTEP, TYPEi = SOLID, TSCi = CST only works on elements with
ISMSTR = 2.

10. Co-rotational formulation: For ISOLID = 1, 2, 12 and IFRAME = ON, the stress tensor is
computed in a co-rotational coordinate system. This formulation is more accurate if large
rotations are involved. It comes at the expense of higher computation cost. It is
recommended in case of elastic or visco-elastic problems with important shear
deformations. The co-rotational formulation is compatible with 8 node solids.

11. HA8 (ISOLID = 14) elements: this element uses a locking-free general solid formulation,
co-rotational. The number of Gauss points is defined by NIP flag: for example, combined
with NIP = 222 gives an 8 Gauss integration point element, similar to ISOLID = 12. The
HA8 formulation is compatible with all material laws. Under-integration for pressure should
be used (ICPRE = ON in case of elastic or visco-elastic material; ICPRE = VAR in case of
elasto-plastic material).

12. H8C (SOLID = 17) elements: Their brick deviatoric behavior is the same as ISOLID = 12,
but the bulk behavior can be chosen with ICPRE, and is compatible with all solid type
material laws. ICPRE = VAR is the default value and ICPRE = OFF will not reduce pressure
integration.

13. HEPH (ISOLID = 24) elements: This element uses an hourglass formulation similar to QEPH
shell elements.

14. ICPRE = VAR is only available for elasto-plastic material law.

15. The hourglass formulation is viscous for ISOLID = 0, 1, and 2.

16. Hourglass viscosity coefficient HV is not active with 8 point integration.

Altair Engineering OptiStruct 13.0 Reference Guide 1909

Proprietary Information of Altair Engineering


17. It is recommended to use IHKT=2 (ISOLID=24) and Lagrange type total strain, ISMSTR=10
for foam or rubber materials, like MATX42 and MATX82. For elasto-plastic type material,
IHKT=2 will have a tighter yield stress criterion for an hourglass stress computation.

18. This card is represented as an extension to a PSOLID property in HyperMesh.

1910 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PTADD

Bulk Data Entry

PTADD – Pretension Load Combination (Superposition)

Description

Defines a pretension load as a linear combination of load sets defined via PTFORCE, PTFORC1,
PTADJST and PTADJS1 entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PTADD PSID S S1 L1 S2 L2 S3 L3

S4 L4 -etc-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PTADD 6 2.0 3.0 2 2.0 3

Field Contents

PSID Pretensioning load set identification number.

S Scale factor. (See comment 1)

No default (Real)

Si Scale factor. (See comment 1)

No default (Real)

Li Pretension load set identification number defined via entry types


enumerated above. (See comment 1)

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1911

Proprietary Information of Altair Engineering


Comments

1. The pretension load as a linear combination is defined by:

Where,

S and Si are the scale factors.

Li is the pretension load set defined via PTFORCE, PTFORC1, PTADJST andPTADJS1
entries.

1912 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PTADJS1

Bulk Data Entry

PTADJS1 – Pretension Adjustment Definition, Alternate Form

Description

Defines adjustment (additional shortening) on a set of pretension sections.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PTADJS1 PSID ADJ SID1 SID2 SID3 SID4 SID5 SID6

SID7 SID8 SID9 -etc-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PTADJS1 3 0.05 1 3 4

Field Contents

PSID Pretensioning load set identification number.

(Integer > 0)

ADJ Adjustment applied on this section (positive value means shortening).


See comment 2.

(Real)

SIDi Pretension section identification number.

(Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1913

Proprietary Information of Altair Engineering


Comments

1. PTADJS1 can be referred by PTADD or by the PRETENSION command in the subcase


directly.

2. Pretensioning adjustment shortens the pretensioned bolt by “removing” the prescribed


amount of material. This represents the effect of turning the nut by a prescribed
distance (number of turns).

3. Pretensioning adjustment is an additional shortening applied to a pretension section. This


means that, when adjustment is applied to a section that has already been pretensioned,
the final effect will be a sum of the status reached in the preceding pretensioning
subcase plus the amount of ADJ.

1914 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PTADJST

Bulk Data Entry

PTADJST – Pretensioning Adjustment

Description

PTADJST defines the adjustment (shortening) on a pretension section.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PTADJST PSID SID ADJ

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PTADJST 3 5 0.5

Field Contents

PSID Pretensioning load set identification number.

(Integer > 0)

SID Pretension section identification number.

(Integer > 0)

ADJ Adjustment applied on this section (positive value means shortening).


See comment 2.

(Real)

Comments

1. PTADJST can be referred by PTADD or by the PRETENSION command in the subcase


directly.

Altair Engineering OptiStruct 13.0 Reference Guide 1915

Proprietary Information of Altair Engineering


2. Pretensioning adjustment shortens the pretensioned bolt by “removing” the prescribed
amount of material. This represents the effect of turning the nut by a prescribed
distance (number of turns).

3. Pretensioning adjustment using PTADJST can also be used to define additional shortening
to a pretensioned section. Therefore, when adjustment is applied to a section that has
already been pretensioned, the final effect will be a sum of the status reached in the
preceding pretensioning subcase plus the amount of adjustment through PTADJST.

1916 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PTFORCE

Bulk Data Entry

PTFORCE – Pretensioning Force

Description

Defines pretensioning force on pretension section.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PTFORC E PSID SID F

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PTFORC E 3 5 0.5

Field Contents

PSID Pretensioning load set identification number.

(Integer > 0)

SID Pretension section identification number.

(Integer > 0)

F Pretensioning force applied on this section. (Positive value creates


tension). See comment 2.

(Real)

Comments

1. PTFORCE can be referred by PTADD or by the PRETENSION command in the subcase


directly.

Altair Engineering OptiStruct 13.0 Reference Guide 1917

Proprietary Information of Altair Engineering


2. Pretensioning force is actually a pair of forces, applied to the opposite sides of the
pretension section. This represents the effect of tightening the nut by a prescribed
longitudinal force (which is related to the applied torque).

1918 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PTFORC1

Bulk Data Entry

PTFORC1 – Pretensioning Force Definition, Alternate Form

Description

Defines pretensioning force on a set of pretension sections.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PTFORC 1 PSID F SID1 SID2 SID3 SID4 SID5 SID6

SID7 SID8 SID9 -etc-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PTFORC 1 3 500.0 1 3 4

Field Contents

PSID Pretensioning load set identification number.

(Integer > 0)

F Pretensioning force applied on this set of sections. (Positive value


creates tension). See comment 2.

(Real)

SIDi Pretension section identification number.

(Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1919

Proprietary Information of Altair Engineering


Comments

1. PTFORC1 can be referred by PTADD or by the PRETENSION command in the subcase


directly.

2. Pretensioning force is actually a pair of forces, applied to the opposite sides of the
pretension section. This represents the effect of tightening the nut by a prescribed
longitudinal force (which is related to the applied torque).

1920 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PTUBE

Bulk Data Entry

PTUBE – Tube Property

Description

PTUBE defines the properties of a thin-walled cylindrical tube element, referenced by a CTUBE
entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PTUBE PID MID OD T NSM OD2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PTUBE 2 6 6.29 0.25

Field Contents

PID Unique identification number.

(Integer > 0)

MID Material identification number.

(Integer > 0)

OD Outside diameter of tube.

(Real > 0.0)

T Thickness of tube.

(Real; T < ½ OD)

Altair Engineering OptiStruct 13.0 Reference Guide 1921

Proprietary Information of Altair Engineering


Field Contents

NSM Nonstructural mass per unit length.

(Real)

OD2 Diameter of tube at second grid point – G2 on CTUBE entry. See comment
4.

Default = OD (OD or blank)

Comments

1. If T is zero, a solid circular rod is assumed.

2. All PTUBE entries must have unique property identification numbers.

3. For structural problems, PTUBE entries may only reference MAT1 material entries.

4. Tapered tubes are not allowed.

5. PTUBE data is converted to PROD data as it is read. CTUBE data is converted to CROD
data.

6. This card is represented as a property in HyperMesh.

1922 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PVISC

Bulk Data Entry

PVISC – Viscous Damping Element Property

Description

Defines properties of a one-dimensional viscous damping element (CVISC entry).

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PVISC PID1 C E1 C R1 PID2 C E2 C R2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PVISC 3 6.2 3.94

Field Contents

PID# Property identification number.

No default (Integer > 0)

CE1, CE2 Viscous damping values for extension in units of force per unit
velocity.

No default (Real)

CR1, CR2 Viscous damping values for rotation in units of force per unit velocity.

No default (Real)

Comments

1. Viscous properties are material independent; in particular, they are temperature


independent.

Altair Engineering OptiStruct 13.0 Reference Guide 1923

Proprietary Information of Altair Engineering


2. One or two viscous element properties may be defined on a single entry.

3. This card is represented as a property in HyperMesh.

1924 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PWELD

Bulk Data Entry

PWELD – WELD Element Property

Description

Defines properties of connector (CWELD) elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PWELD PID MID D MSET TYPE

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

PWELD 30 2 2.5

Field Contents

PID Property identification number.

No default (Integer > 0)

MID Material identification number. See comment 1.

No default (Integer > 0)

D Diameter of the connector. See comment 1.

No default (Real > 0.0)

MSET Flag to eliminate m-set degrees-of-freedom. See comment 2.

Default = OFF (ON or OFF)

Altair Engineering OptiStruct 13.0 Reference Guide 1925

Proprietary Information of Altair Engineering


Field Contents

TYPE Indicates type of connection. See comment 3.

SPOT indicates spot weld connector.

blank indicates general connector.

Default = blank (SPOT or blank)

Comments

1. Material MID, diameter D, and the length are used to calculate the stiffness of the
connector in 6 directions. MID can only refer to the MAT1 bulk data entry. The length is
the distance of GA to GB (see below).

Length and Diameter of Weld connector

2. MSET = ON generates explicit m-set constraints. MSET = OFF (default) incorporates


constraints at the element stiffness matrix level avoiding explicit m-set constraint
equations. The exact same results will be obtained regardless of this choice.

3. If TYPE="SPOT" and if the formats PARTPAT, ELPAT, or ELEMID on the CWELD entry are
used, then the effective length for the stiffness of the CWELD element is set to
regardless of the distance GA to GB. t A and t B are the shell thicknesses of
shell A and B respectively. For all other cases, the effective length of the CWELD
element is equal to the true length, the distance of GA and GB, as long as the ratio of

1926 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


length to diameter is in the range 0.2 < L/D 5.0. If L is below the range, the effective
length is set to Le = 0.2D and if L is above the range, the effective length is set to Le =
5.0D.

4. This card is represented as a property in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1927

Proprietary Information of Altair Engineering


QBDY1

Bulk Data Entry

QBDY1 – Heat Flux Boundary Condition (Form 1)

Description

Defines a uniform heat flux for CHBDYE elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

QBDY1 SID Q0 EID1 EID2 EID3 EID4 EID5 EID6

Alternate Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

QBDY1 SID Q0 EID1 “THRU” EID2

Field Contents

SID Load set identification number.

No default (Integer > 0)

Q0 Heat flux into element.

No default (Real)

EID# CHBDYE surface element identification numbers. With alternate format using
“THRU” EID2 > EID1.

Comments

1. QBDY1 entries must be selected with the Case Control command LOAD=SID in order to be
used in static analysis. The total power into an element is given by the equation:

2. The sign convention for Q0 is positive for heat input.

1928 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. This card is represented as a flux load in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1929

Proprietary Information of Altair Engineering


QVOL

Bulk Data Entry

QVOL – Volume Heat Addition

Description

Defines a rate of volumetric heat addition in a conduction element.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

QVOL SID QVOL EID1 EID2 EID3 EID4 EID5

EID6 ... ... ... ... ... ... ...

...

Field Contents

SID
Load set identification number.

No default (Integer > 0)

QVOL
Power input per unit volume produced by a heat conduction element.

No default (Real)

EID#
A list of heat conduction elements.

No default (Integer > 0 or “THRU” or “BY”)

Comments

1. EID# has material properties (MAT4/MAT5) that include HGEN, the scale factor for
volumetric heat generation. This association is made through the element EID.

2. QVOL provides the constant volumetric heat generation rate. QVOL is positive for heat
generation. For steady-state analysis, the total power into an element is:

Where, HGEN is the scale factor from the MAT4 and MAT5 data.

1930 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. For use in steady-state analysis, the load set is selected with the Case Control command
LOAD=SID.

4. This card is represented as a flux load in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1931

Proprietary Information of Altair Engineering


RADPRM

Bulk Data Entry

RADPRM – Parameters definition entry for Geometric Nonlinear Analysis

Description

Defines the parameters for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RADPRM PARAM1 VALUE1 PARAM2 VALUE2 PARAM3 VALUE3 PARAM4 VALUE4

PARAM5 VALUE5

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RADPRM HMNAME YES RBE2RBD YES

Field Contents

PARAMi Name of parameter. See below for allowable names.

VALi Value of parameter.

The available parameters and their values are listed below (click the parameter name for
detailed parameter descriptions).

Parameter Brief Description Value

HMNAME RADPRM, HMNAME controls the conversion of the YES or NO


component, property and material names in
geometric nonlinear analysis. Default = NO

RBE2RBD RBE2 is converted to /RBE2 by default in YES or NO


geometric nonlinear analysis. This parameter can

1932 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Parameter Brief Description Value

be used to convert RBE2 to /RBODY, instead of / Default = NO


RBE2.

Comments

1. The parameters defined by RADPRM bulk card are only applied in geometric nonlinear
analysis subcases which are defined by ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is
ignored for all other subcases.

Altair Engineering OptiStruct 13.0 Reference Guide 1933

Proprietary Information of Altair Engineering


RADPRM, HMNAME

Parameter Values Description

HMNAME YES or NO RADPRM, HMNAME controls the conversion of


Default = NO the component, property and material names in
geometric nonlinear analysis.

If YES, the converter will keep the component,


property and material names defined by
HyperMesh comments in the bulk model file, and
print them in a RADIOSS Starter file.

If NO, the converter will print intermediate


names automatically.

1934 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


RADPRM, RBE2RBD

Parameter Values Description

RBE2RBD YES or NO RBE2 is converted to /RBE2 by default in


Default = NO geometric nonlinear analysis. This parameter
can be used to convert RBE2 to /RBODY,
instead of /RBE2.

Note

RBE2 can be converted to /RBODY only if all six


degrees of freedom of the slave nodes are
dependent on the master node. Otherwise, the
solver errors out when RBE2RBD = YES. Note
that if the master node of the RBE2 is
connected to other elements or in the case of
hierarchical RBE2’s, RADPRM, RBE2RBD activation
is not recommended.

Altair Engineering OptiStruct 13.0 Reference Guide 1935

Proprietary Information of Altair Engineering


RADSND

Bulk Data Entry

RADSND – Defines Grids (microphone locations) where sound levels will be calculated and the
locations of the corresponding source (vibrating panel) grids.

Description

Defines a set of grid points where the sound will be calculated as well as the panels that are
generating the sound.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RADSND RSID MSET

"PANEL" PID PID PID - etc. -

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RADSND 10 100

PANEL 101 103

Field Contents

RSID Radiated sound set ID.

No default (Integer > 0)

MSET ID of a SET of field grids (microphone locations) at which sound levels


will be calculated. The sound levels output at these grid points are due
to panel vibrations (specified separately in the PANEL and PIDi fields,
see comment 4).

No default (Integer > 0)

PANEL Flag indicating that the following panel ID’s will contribute to the sound
at the MSET grids (see comment 4).

1936 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Character (No default)

PIDi Panel ID of the "PANELG" data entry of type "SOUND" data.

No default (Integer > 0)

Comments

1. At least the first panel ID is required.

2. Multiple continuations or multiple RADSND with the same SID are allowed if more than 7
SOUND panels need to be defined.

3. The RADSND bulk data entry is referenced by the RADSND command in the Subcase
Information section of the input data.

4. The MSET and PIDi fields are used to specify the microphone locations (receiving grids)
and the vibrating panels (source grids) respectively.

RADSND data entry field Description

MSET References microphone grid sets (receiving grids).


Outputs are generally calculated at these locations.

PANEL, PIDi Reference vibrating panel ID’s (source grids).


Outputs can also be requested at these locations.

Altair Engineering OptiStruct 13.0 Reference Guide 1937

Proprietary Information of Altair Engineering


RANDPS

Bulk Data Entry

RANDPS – Power Spectral Density Specification

Description

Defines load set power spectral density factors for use in random analysis having the
frequency dependent form S (F) = (X + iY) G(F).
jk

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RANDPS SID J K X Y TID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RANDPS 5 3 7 2.0 2.5 4

Field Contents

SID Random analysis set identification number.

(Integer > 0)

J Subcase identification number of excited load set.

(Integer > 0)

K Subcase identification number of applied load set.

(Integer > 0; K > J)

X, Y Components of complex number.

(Real)

1938 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

TID Identification number of a TABRNDi entry which defines G(F).

Integer > 0

Comments

1. If J = K, then Y must be 0.0.

2. For TID = 0, G(F) = 1.0.

3. Set identification number must be selected in the Subcase Information section (RANDOM
= SID) to activate the RANDPS data.

Altair Engineering OptiStruct 13.0 Reference Guide 1939

Proprietary Information of Altair Engineering


RANDT1

Bulk Data Entry

RANDT1 – Autocorrelation Function Time Lag

Description

Defines time lag constants for use in random analysis autocorrelation function computation.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RANDT1 SID N T0 TMAX

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RANDT1 5 10 3.2 9.6

Field Contents

SID Random analysis set identification number.

(Integer > 0)

N Number of time lag intervals.

(Integer > 0)

TO Starting time lag.

(Real > 0.0)

TMAX Maximum time lag.

(Real > TO)

1940 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. At least one RANDPS entry must be present with the same set identification number.

2. The time lags defined on this entry are given by

3. Time lag sets must be selected in the Subcase Information section (RANDOM = SID) to
activate the RANDT1 data.

Altair Engineering OptiStruct 13.0 Reference Guide 1941

Proprietary Information of Altair Engineering


RBAR

Bulk Data Entry

RBAR – Rigid Bar

Description

Defines a rigid bar with six degrees-of-freedom at each end.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RBAR EID GA GB C NA C NB C MA C MB

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RBAR 5 1 2 234 123

Field Contents

EID Unique element identification number.

GA,GB Grid point identification number of connection points.

(Integer > 0 or <PartName.number>) See comment 6.

CNA,CNB Independent degrees-of-freedom in the global coordinate system for the


element at grid points GA and GB. Up to six unique digits (0 < digit < 6)
may be placed in each field with no embedded blanks, or the field may be
left blank. See comment 1.

CMA,CMB Component numbers of dependent degrees-of-freedom in the global


coordinate system assigned by the element at grid points GA and GB. Up
to six unique digits (0 < digit < 6) may be placed in each field with no
embedded blanks, or the field may be left blank. See comment 2.

1942 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. The total number of components in CNA and CNB must equal six, for example, CNA =
1236, CNB = 34. Furthermore, they must jointly be capable of representing any general
rigid body motion of the element.

2. If both CMA and CMB are zero or blank, all of the degrees-of-freedom not in CNA and CNB
are made dependent.

3. The degree of freedom declared dependent on this entry may not be:

Included in a single point constraint (SPC or SPC1).


Declared a dependent degree-of-freedom on any other RBAR, RBE1, RBE2, RBE3, or
RROD entry.
Declared a dependent degree-of-freedom on an MPC set referenced by a subcase.
4. Element identification numbers must be unique.

5. Rigid elements are ignored in heat transfer analysis.

6. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on RBAR entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry
in the model). “number” is the identification number of a referenced local entry in the part
“PartName”. See Parts and Instances in the User’s Guide for detailed information on the
use of fully qualified references.

7. This card is represented as a weld element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1943

Proprietary Information of Altair Engineering


RBE1

Bulk Data Entry

RBE1 – Rigid Body Element, Form 1

Description

Defines a rigid body connected to an arbitrary number of grid points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RBE1 EID GN1 C N1 GN2 C N2 GN3 C N3

GN4 C N4 GN5 C N5 GN6 C N6

"UM" GM1 C M1 GM2 C M2 GM3 C M3

GM4 C M4 GM5 C M5 etc.

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RBE1 14 100 123456

UM 101 123 102 123

Field Contents

EID Unique element identification number.

No default (Integer)

GNi Grid points at which independent degrees-of-freedom for the element are
assigned.

No default (Integer or <PartName.number>) See comment 7.

1944 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

CNi Independent degrees-of-freedom in the global coordinate system for the


rigid element at grid point(s) GNi.

UM UM flag indicating the start of the dependent degrees-of-freedom.

GMi Grid points at which dependent degrees-of-freedom for the element are
assigned.

No default (Integer or <PartName.number>) See comment 7.

CMi Dependent degrees-of-freedom in the global coordinate system for the


rigid elements at grid point(s) GMi.

No default (Integers 1 through 6 with no embedded blanks)

Comments

1. The total number of components in CN1 to CN6 must equal six; furthermore, they must
jointly be capable of representing and general rigid body motion of the element. The first
continuation entry is not required if there are fewer than four GN points.

2. The degree-of-freedom declared dependent on this entry may not be:

Included in a single point constraint (SPC or SPC1).


Declared a dependent degree-of-freedom on any other RBAR, RBE1, RBE2, RBE3, or
RROD entry.
Declared a dependent degree-of-freedom on an MPC set referenced by a subcase.
3. A degree-of-freedom cannot be both independent and dependent for the same element.
However, both independent and dependent components can exist at the same grid point.

4. Element identification numbers must be unique.

5. Rigid elements, unlike MPCs, may not be selected for use in individual subcases; they
apply to all subcases.

6. Rigid elements are ignored in heat transfer analysis.

7. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on RBE1 entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry
in the model). “number” is the identification number of a referenced local entry in the part
“PartName”. See Parts and Instances in the User’s Guide for detailed information on the
use of fully qualified references.

Altair Engineering OptiStruct 13.0 Reference Guide 1945

Proprietary Information of Altair Engineering


RBE2

Bulk Data Entry

RBE2 – Rigid Body Element, Form 2

Description

Defines a rigid body whose independent degrees-of-freedom are specified at a single grid point
and whose dependent degrees-of-freedom are specified at an arbitrary number of grid points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RBE2 EID GN CM GM1 GM2 GM3 GM4 GM5

GM6 GM7 GM8 -etc.-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RBE2 9 8 12 10 12 14 15 16

20

Field Contents

EID Unique element identification number.

GN The grid point to which all six independent degrees-of-freedom for the
element are assigned.

(Integer > 0 or <PartName.number>) See comment 5.

CM Component number of the dependent degrees of freedom in the global


coordinate system (local output coordinate system) at grid points GM1,
GM2, and so on. Up to six unique digits (1 < digit < 6) may be placed in
the field with no embedded blanks.

1946 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

GM1,GM2, etc. Grid points at which dependent degrees-of-freedom are assigned.

(Integer > 0 or <PartName.number>) See comment 5.

Comments

1. The components indicated by CM are made dependent at all grid points, GMi.

2. The degree-of-freedom declared dependent on this entry may not be:

Included in a single point constraint (SPC or SPC1).


Declared a dependent degree-of-freedom on any other RBAR, RBE1, RBE2, RBE3, or
RROD entry.
Declared a dependent degree-of-freedom on an MPC set referenced by a subcase.
3. Element identification numbers must be unique.

4. Rigid elements are ignored in heat transfer analysis.

5. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on RBE2 entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry
in the model). “number” is the identification number of a referenced local entry in the part
“PartName”. See Parts and Instances in the User’s Guide for detailed information on the
use of fully qualified references.

6. This card is represented as a rigid or rigidlink element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1947

Proprietary Information of Altair Engineering


RBE3

Bulk Data Entry

RBE3 – Interpolation Constraint Element

Description

Defines the motion at a "reference" grid point as the weighted average of the motions at a set
of other grid points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RBE3 EID blank REFGRID REFC WT1 C1 G1,1 G1,2

G1,3 WT2 C2 G2,1 G2,2 etc. WT3 C3

G3,1 G3,2 etc. WT4 C4 G4,1 G4,2 etc.

"UM" GM1 C M1 GM2 C M2 GM3 C M3 blank

blank GM4 C M4 GM5 C M5 etc. blank

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RBE3 14 100 1234 1.0 123 1 3

5 4.7 1 2 4 6 5.2 2

7 8 9 5.1 1 15 16

UM 15 123 5 13 7 3

1948 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

EID Unique element identification number.

REFGRID Reference grid point. This is the dependent GRID. Some, or all, of the
dependent degrees-of-freedom of this grid can be made independent by
redefining all of the dependent degrees-of-freedom following the UM flag.

(Integer > 0 or <PartName.number>) See comment 9.

REFC Global components of motion whose values will be computed at the reference
grid point. Any of the digits 1, 2, ..., 6 with no embedded blanks.

(Integer > 0)

WTi Weighting factor for components of motion on the following entry at grid points
Gi,j.

(Real)

Ci Global components of motion that have weighting factor WTi, at grid points Gi,j.
Any of the digits 1, 2, ..., 6, with no embedded blanks.

(Integer > 0)

Gi,j Grid point whose components Ci have weighting factor WTi in the averaging
equations.

(Integer > 0 or <PartName.number>) See comment 9.

UM Optional flag indicating that a data set redefining the entire dependent degree-
of-freedom set is to follow. The default is that all of the components in REFC at
the reference grid point form the dependent degree-of-freedom set. See
comments 4, 5 and 6.

GMi Grid points with components in the redefined dependent degree-of-freedom set.

(Integer > 0 or <PartName.number>) See comment 9.

CMi Components of motion at GMi in the redefined dependent degree-of-freedom set.


Any of the digits 1 through 6, with no embedded blanks.

(Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1949

Proprietary Information of Altair Engineering


Comments

1. It is recommended that for most applications only the translation components 123 be
used for Ci. An exception is the case where the Gij are collinear. A rotation component
may then be added to one grid point, to stabilize its associated rigid body mode for the
element.

2. Blank spaces may be left at the end of a Gij sequence.

3. The default for the dependent degree-of-freedom set should be used except in cases
where you want to redefine some or all REFC components as the dependent degree-of-
freedom set. If the default is not used for the dependent degree-of-freedom set:

The total number of components therein (that is, the total number of dependent
degrees-of-freedom defined by the element) must be equal to the number of
components in REFC (four components in the example).
The components therein must be a subset of the components mentioned in REFC and
Gij_Ci.
The coefficient matrix [Rm] in the constraints equation [RM] {um} + [Rn] {un} = 0
must be nonsingular, where um denotes the dependent degree-of-freedom set and un
denotes the independent degree-of-freedom set.
4. When the AMSES or AMLS eigenvalue solver is used, the UM data should be used when
loaded RBE3 have more than 500 DOF. Large loaded RBE3 will dramatically increase the
run times for AMSES or AMLS because the residual vectors will contain many DOF, unless
the UM data is used to make the loaded center GRID independent. When UM data is used,
the stiffness matrix becomes full for all the independent DOF of the RBE3, which can
increase the run time for very large RBE3. The number of grids can be reduced using a
HyperMesh macro. The macro is listed as Script 1068 in the Altair HyperWorks Script
Exchange:

www.altairhyperworks.com

5. UM data should not be used on large unloaded RBE3, as this will lead to an increase in the
run time.

6. Dependent degrees-of-freedom assigned by one rigid element may not also be assigned
dependent by another rigid element or by a multi-point constraint, and may not be
specified on SPC data.

7. In version 5.0, the RBE3 element calculation was modified in order to make the results
independent of the units used in the model. For this purpose, the weights of the
rotational degrees-of-freedom have been scaled by the square of the average distance
between the independent grid points and the reference point. This change will only affect
the results if independent grid points with rotational degrees-of-freedom exist in the RBE3
element. The previous RBE3 formulation can be enforced with the debug statement
debug, OLDRBE3,1.0.

8. Rigid elements are ignored in heat transfer analysis.

9. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on RBE3 entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry

1950 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


in the model). “number” is the identification number of a referenced local entry in the part
“PartName”. See Parts and Instances in the User’s Guide for detailed information on the
use of fully qualified references.

10. This card is represented as an rbe3 element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1951

Proprietary Information of Altair Engineering


RCROSS

Bulk Data Entry

RCROSS – Cross-Power Spectral Density Functions Output

Description

Defines a pair of response quantities for computing the cross-power spectral density functions
in random response analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RC ROSS SID RTYPE1 ID1 C OMP1 RTYPE2 ID2 C OMP2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RC ROSS 20 DISP 50 2 STRESS 150 8 4

Field Contents

SID RCROSS set identification number.

No default (Integer > 0)

RTYPE# Type of response quantity. At least one field must be selected. If


either RTYPE1 or RTYPE2 is blank, then the blank field takes the
default from the defined field. See comment 2.

ID# Element, grid, or scalar point identification number.

No default (Integer > 0)

COMP# Component code (item) identification number. See comment 3.

No default (Integer > 0)

1952 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. This entry is required for computing the cross-power spectral density function. SID must
be selected with the I/O Option RCROSS. Fields RTYPE1, ID1, and COMP1 represent the
first response quantity and fields RTYPE2, ID2, and COMP2 represent the second response
quantity.

2. The keywords for field RTYPE# are listed as follows:

Keyword Description

DISP Displacement vector

VELO Velocity vector

ACCEL Acceleration vector

STRESS Element Stress

STRAIN Element Strain

3. For elements, COMP# represents a component of the element stress or strain as


described in the following table.

Element Stress/Strain Item Number code

All Solid Elements Normal X 6 or 12

Normal Y 7 or 13

Normal Z 8 or 14

Shear XY 9 or 15

Shear YZ 10 or 16

Shear XZ 11 or 17

All Shell Elements Normal X at Z1 3 or 4

Normal X at Z2 10 or 11

Normal Y at Z1 5 or 6

Normal Y at Z2 12 or 13

Shear XY at Z1 7 or 8

Altair Engineering OptiStruct 13.0 Reference Guide 1953

Proprietary Information of Altair Engineering


Element Stress/Strain Item Number code

Shear XY at Z2 14 or 15

For grid points, COMP# represents a component of the displacement, velocity or


acceleration as described in the following table:

Response Number code

Translation X 1 or 7

Translation Y 2 or 8

Translation Z 3 or 9

Rotation X 4 or 10

Rotation Y 5 or 11

Rotation Z 6 or 12

For scalar points, COMP# should always be 1.

1954 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


RELOC

Bulk Data Entry

RELOC – Grid Point Relocation

Description

The RELOC bulk data entry can be used to map grid points from one location to another. This
entry allows you to translate, match, rotate or mirror grid points. The grid ID fields can be
input as either numeric or fully qualified references to grid points in the model.

Format

The format of this entry depends on the TYPE field input; the various versions are listed as
follows:

Translation (TYPE = MOVE)


Format 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RELOC ID TYPE GID1 GID2

Format 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RELOC ID TYPE dx dy dz

Rotation (TYPE = ROTATE)


Format 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RELOC ID TYPE GID1 ang_x ang_y ang_z

Matching (TYPE = MATCH)


Format 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RELOC ID TYPE GIDA1 GIDA2 GIDA3 GIDB1 GIDB2 GIDB3

Altair Engineering OptiStruct 13.0 Reference Guide 1955

Proprietary Information of Altair Engineering


Mirroring (TYPE = MIRROR)
Format 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RELOC ID TYPE GIDA1 GIDA2 GIDA3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RELOC 1 MATC H 1001 1012 3992 123 564 665

Field Contents

ID Set identification number.

(Integer > 0)

TYPE This field specifies the type of mapping between grid points in a model. The
format of the RELOC card is different for different values of the TYPE field (see
Comment 2 for detailed information on each option).

(MOVE, ROTATE, MATCH, or MIRROR)

Translation (Format 1)

GID1 Grid point identification number for translation to the reference point location.
Grid point GID1 is moved from its original location to the GID2 location.

(Integer > 0 or <PartName.number>) See comment 4.

GID2 Reference grid point identification number for translation. GID2 is used as a
reference point to move another grid point (GID1) from its original location to
the GID2 location.

(Integer > 0 or <PartName.number>) See comment 4.

Translation (Format 2)

dx, dy, dz Defines the distance that the referenced part (INSTNCE entry) should be
translated in the basic coordinate system. Each entry specifies the
corresponding distance moved in the X, Y, and Z axes, respectively (see
Comment 2).

(Real or blank)

1956 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Rotation (Format 1)

GID1 Specifies the identification number of a grid point that will be used as a center
of rotation based on the angles specified in the following fields.

(Integer > 0 or <PartName.number>) See comment 4.

ang_x, Defines the angle (in degrees) of rotation about the X, Y, and Z axes,
ang_y, respectively with the grid point (GID1) as the center of rotation. In a 2D
ang_z model, only ang_z is specified (see Comment 2).

(Real or blank)

Matching (Format 1)

GIDA1, Specifies the identification numbers of grid points (initial location) that will be
GIDA2, moved to match with the corresponding grid points GIDB1,2,3 (final location,
GIDA3 defined in the following fields). Any rotation, translation or mirroring required
to complete this matching process is accomplished internally by OptiStruct.
These three grid points cannot be collinear.

(Integer > 0 or <PartName.number>) See comment 4.

GIDB1, Specifies the identification numbers of grid points which will be matched with
GIDB2, the corresponding grid points defined in the GIDA1,2,3 fields. Any rotation,
GIDB3 translation or mirroring required to complete this matching process is
accomplished internally by OptiStruct. These three grid points cannot be
collinear.

(Integer > 0 or <PartName.number>) See comment 4.

Mirroring (Format 1)

GIDA1, Specifies the identification numbers of grid points about which the entire part
GIDA2, (defined via INSTNCE) will be laterally mirrored (flipped) by 180 degrees. The
GIDA3 grid points GIDA1,2,3 define an absolute plane of symmetry flip. Any rotation
or translation required to complete this mirroring process is accomplished
internally by OptiStruct. The three grid points specified for mirroring cannot be
collinear. In a 2D model, only GIDA1 and GIDA2 should be specified.

(Integer > 0 or <PartName.number>) See comment 4.

Comments

1. A RELOC entry can be referenced by a INSTNCE entry to define the location of a part in
the full model.

2. The following illustrations depict part relocation examples for each of the four TYPE field
options. All grid point ID’s used on the RELOC entry can belong to any part in the model.
Only their initial locations are relevant. All RELOC entries are evaluated before any parts

Altair Engineering OptiStruct 13.0 Reference Guide 1957

Proprietary Information of Altair Engineering


are moved. This may not always produce the expected result in some cases as the
sequence of moves affects the final part locations. For example, if RELOC, MATCH is
defined using three grid points on part A and three grid points in part B, this may not
result in a final structure with the two parts being connected, if part B is moved again
after this matching process. To avoid such cases, it is strongly recommended to assign
the grid points that define the initial location to a part that has to be moved and the grid
points that define the final location, to a part that will not be moved (for example, the
global structure).

Translation - Format 1:

Format 1 (Special case, assumes that Part B does not relocate)

1958 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Translation - Format 2:

2 2 2
D dx dy dz

Where,

D is the distance moved by the part referenced on the INSTNCE entry.


dx, dy and dz are the distances moved by the part along the X, Y and Z axes.
Rotation - Format 1:

Altair Engineering OptiStruct 13.0 Reference Guide 1959

Proprietary Information of Altair Engineering


Matching - Format 1:

Format 1 (Special case – Part B does not relocate)

1960 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Mirroring - Format 1:

3. In a 2D model, only two TYPE options are allowed: ROTATE and MIRROR. All grid points in
the model should have the same Z coordinate. Rotation and mirroring are defined in the X-
Y plane.

Rotation in a 2D model defined in the X-Y plane

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RELOC ID ROTATE GID1 ang_z

Mirroring in a 2D model defined in the X-Y plane

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RELOC ID MIRROR GIDA1 GIDA2

4. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on RELOC entries in the model. A fully qualified reference
(“PartName.number”) is similar to the format of a numeric reference. “PartName” is the
name of the part that contains the referenced local entry (part names are defined on the
BEGIN bulk data entry in the model). “number” is the identification number of a referenced
local entry in the part “PartName”. See Parts and Instances in the User’s Guide for
detailed information on the use of fully qualified references.

Altair Engineering OptiStruct 13.0 Reference Guide 1961

Proprietary Information of Altair Engineering


RFORCE

Bulk Data Entry

RFORCE – Rotational Force

Description

Defines a static loading condition due to a centrifugal force field. It can also be used to define
the EXCITEID field (Amplitude “A”) of dynamic loads in RLOAD1, RLOAD2, TLOAD1 and TLOAD2
bulk data entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RFORC E SID G C ID A R1 R2 R3

RAC C

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RFORC E 2 5 0.0 0.0 1.0 2.2

1.0

Field Contents

SID Load set identification number.

No default (Integer > 0)

G Grid point identification number through which the rotation vector acts.

Default = 0 (Integer > 0)

CID Coordinate system defining the components of the rotation vector.

1962 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Default = 0 (Integer > 0)

A Scale factor of the rotational velocity in revolutions per unit time.

Default = 0.0 (Real)

R1,R2,R3 Rectangular components of rotation direction vector. The vector defined


will pass through point G.

No default (Real; R12 + R22 + R32 > 0.0)

RACC Scale factor of the rotational acceleration in revolutions per unit time
squared.

(Real)

Comments

1. The rotational forces that are created with an RFORCE entry for a constant angular
velocity (A), act in the positive radial direction. They represent the initial forces on the
structure due to a constant angular velocity. The rotational forces defined for a
constant angular acceleration (RACC), act in the same direction as the angular
acceleration. They would be opposite to the inertia forces on the structure due to a
constant angular acceleration.

The following plot shows that the RFORCE vector at node Gi is given by:

where,

angular velocity =

angular acceleration =

Altair Engineering OptiStruct 13.0 Reference Guide 1963

Proprietary Information of Altair Engineering


RFORC E vector at node Gi

2. G = 0 or blank means the basic coordinate system origin.


3. CID = 0 or blank signifies that the rotation vector acts at the origin of the basic
coordinate system.

4. The RFORCE load is selected for use in a subcase by the Subcase Information entry LOAD.

5. The load vector generated by this entry can be printed using the I/O Option OLOAD.

6. The continuation line containing RACC is optional.

7. For CONM1 and CONM2 entries, OptiStruct calculates the torque, due to rotation, as
follows:

where, I is the moment of inertia.

8. This card is represented as a loadcollector in HyperMesh.

1964 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


RGYRO

Bulk Data Entry

RGYRO – Rotor Dynamics

Description

Bulk Data Entry for the inclusion of data required to perform Rotor Dynamics analysis in Modal
Frequency Response Analysis and/or Modal Complex Eigenvalue Analysis. The RGYRO Bulk Data
Entry is referenced by a corresponding RGYRO Subcase Information Entry in a specific
subcase.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RGYRO RID SYNC FLG REFROTR SPDUNIT SPDLOW SPDHIGH SPEED

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RGYRO 14 ASYNC 3 FREQ 55

Argument Options Description

RID <INTEGER> setid: The SID is referenced by a RGYRO card


in the subcase information section.

SYNCFLG <SYNC, ASYNC > SYNC: Synchronous Rotor dynamic analysis is


selected, if SYNC is input in this field.
(no default)
ASYNC: Asynchronous Rotor dynamic analysis is
selected, if ASYNC is input in this field.

REFROTR <INTEGER > 0> rotid: Reference rotor ID. This field selects
the rotor that will be used in THE Rotor
dynamic analysis.

Altair Engineering OptiStruct 13.0 Reference Guide 1965

Proprietary Information of Altair Engineering


Argument Options Description

(no default)

SPDUNIT <RPM, FREQ> RPM: RPM specifies that the entries SPDLOW,
SPDHIGH and SPEED are input in
(No default) Revolutions Per Minute.

FREQ: FREQ specifies that the entries


SPDLOW, SPDHIGH and SPEED are input
in revolutions per unit time.

SPDLOW <INTEGER> Minimum rotor speed for synchronous analysis.

Default = 0.0

SPDHIGH <INTEGER> Maximum rotor speed for synchronous analysis.

Default = 99999.0

SPEED <INTEGER, Real> <INTEGER> If an integer value is input, it references


a RSPEED bulk data entry that specifies
Default = 0 a set of reference rotor speeds for
asynchronous analysis (See comment
2).

<Real> If a real number is input, the value is


considered constant and a single
Default = 0.0 reference rotor speed value is specified
(See comment 2).

Comments

1. Multiple RGYRO bulk data entries with the same RID cannot exist.

2. The values entered on some optional fields of the RGYRO bulk data entry depend on
factors such as: solution sequence used, type of analysis performed, and the value of
specific parameters. The following table shows some of the optional fields and their
relevance based on the listed factors. Synchronous analysis is performed when the rotor
speed is equal to the modal frequency (Complex eigenvalue analysis) or the frequency of
the forcing function (Frequency response analysis) and Asynchronous analysis is

1966 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


performed when the user specified rotor speed is used for the analysis.

Synchronous/
Required PARAM,
Solution Sequence Asynchronous Comment
Entry GYROAVG
Analysis

Modal Frequency Synchronous None 0 -


Response Analysis
Synchronous SPDLOW, -1 3, 4
SPDHIGH

Asynchronous SPEED 0 -

Asynchronous SPEED -1 4

Modal Complex Synchronous SPDLOW, - 3, 4


Eigenvalue Analysis SPDHIGH

Asynchronous SPEED - 4

3. When multiple rotors are present within the system being modeled, one of the rotors is
chosen as a reference rotor. The speeds of the rest of the rotors are linearly dependent
of the reference rotor. Scale factors S1 and S2 are used to relate the speeds.

S1 S 2 * ref

Where,

is the speed of a rotor (different from the reference rotor)

S1 and S2 are scale factors

ref
is the speed of the reference rotor

The scale factors S1 and S2 will be calculated by a least-mean-square fit of the relative
rotor speeds specified on the RSPINR entries (between SPDLOW to SPDHIGH of the
reference rotor). If the SPDLOW or SPDHIGH values are beyond the range specified on
the RSPINR entry, the values will be extrapolated from the RSPINR entry values.

4. PARAM, WR3 and PARAM, WR4 are necessary for rotor damping.

Altair Engineering OptiStruct 13.0 Reference Guide 1967

Proprietary Information of Altair Engineering


RLOAD1

Bulk Data Entry

RLOAD1 – Frequency Response Dynamic Load, Form1

Description

Defines a frequency-dependent dynamic load of the form


for use in frequency response problems.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RLOAD1 SID EXC ITEID DELAY DPHASE TC TD TYPE

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RLOAD1 5 3 1

Field Contents

SID Set identification number.

No default (Integer > 0)

EXCITEID Identification number of the DAREA, SPCD, FORCEx, MOMENTx,


PLOADx, RFORCE, or GRAV entry set that defines A.

No default (Integer > 0)

DELAY Defines time delay . If it is a non-zero integer, it represents the


identification number of a DELAY bulk data entry that defines . If
it is real, then it directly defines the value of that will be used for
all degrees-of-freedom that are excited by this dynamic load entry.

Default = 0 (Integer > 0, or Real)

1968 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

DPHASE Defines phase . If it is a non-zero integer, it represents the


identification number of a DPHASE bulk data entry that defines . If
it is real, then it directly defines the value of that will be used for
all degrees-of-freedom that are excited by this dynamic load entry.

Default = 0 (Integer > 0, or Real)

TC Set identification number of the TABLED1, TABLED2, TABLED3 or


TABLED4 entry that gives C( ). See comment 2.

Default = 0 if TD is non-zero (Integer > 0)

TD Set identification number of the TABLED1, TABLED2, TABLED3 or


TABLED4 entry that gives D( ). See comment 2.

Default = 0 if TC is non-zero (Integer > 0)

TYPE Identifies the type of the dynamic excitation.

Default = 0 (See comment 5)

Comments

1. Dynamic load sets must be selected in the I/O Options or Subcase Information sections
with the command DLOAD = SID.

2. If any DELAY, DPHASE, TC, or TD fields are blank or zero, the corresponding , , C( ), or
D( ) will be zero. Either TC or TD may be blank or zero, but not both.

3. RLOAD1 loads may be combined with RLOAD2 loads only by specification on a DLOAD
entry. This means that the SID on a RLOAD1 entry must not be the same as that on a
RLOAD2 entry.

4. SID must be unique for all RLOAD1 and RLOAD2 entries.

5. The type field identifies the type of dynamic excitation. Valid entries for this field are
listed alongside a description of the dynamic excitation with they invoke.

Type Description

0, L, LO, LOA, LOAD Applied load; EXCITEID references DAREA data.

1, D, DI, DIS, DISP Enforced displacement; EXCITEID references SPCD data.

2, V, VE, VEL, VELO Enforced velocity; EXCITEID references SPCD data.

Altair Engineering OptiStruct 13.0 Reference Guide 1969

Proprietary Information of Altair Engineering


Type Description

3, A, AC, ACC, ACCE Enforced acceleration; EXCITEID references SPCD data.

6. When EXCITEID refers to an SPCD entry, the modal space will be augmented with
displacement vector(s) from linear static analysis with unit prescribed displacement at
each of the SPCD degrees-of-freedom.

7. All static structural loads can be referenced by EXCITEID by referring to the SID on the
structural load. The structural loads are FORCE, FORCE1, FORCE2, MOMENT, MOMENT1,
MOMENT2, PLOAD, PLOAD1, PLOAD2, PLOAD4, RFORCE, and GRAV. EXCITEID cannot
reference the LOAD and LOADADD Bulk Data entries.

8. This card is represented as a loadcollector in HyperMesh.

1970 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


RLOAD2

Bulk Data Entry

RLOAD2 – Frequency Response Dynamic Load, Form 2

Description

Defines a frequency-dependent dynamic load of the form:

for use in frequency response problems.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RLOAD2 SID EXC ITEID DELAY DPHASE TB TP TYPE

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RLOAD2 5 3 7

Field Contents

SID Set identification number.

No default (Integer > 0)

EXCITEID Identification number of the DAREA, SPCD, FORCEx, MOMENTx,


PLOADx, RFORCE, or GRAV entry set that defines A.

No default (Integer > 0)

DELAY Defines time delay . If it is a non-zero integer, it represents the


identification number of a DELAY bulk data entry that defines . If
it is real, then it directly defines the value of that will be used for
all degrees-of-freedom that are excited by this dynamic load entry.

Altair Engineering OptiStruct 13.0 Reference Guide 1971

Proprietary Information of Altair Engineering


Field Contents

Default = 0 (Integer > 0, or Real)

DPHASE Defines phase . If it is a non-zero integer, it represents the


identification number of a DPHASE bulk data entry that defines . If
it is real, then it directly defines the value of that will be used for
all degrees-of-freedom that are excited by this dynamic load entry.

Default = 0 (Integer > 0, or Real)

TB Set identification number of the TABLED1, TABLED2, TABLED3 or


TABLED4 entry that gives B( ).

No default (Integer > 0)

TP Set identification number of the TABLED1, TABLED2, TABLED3 or


TABLED4 entry that gives in degrees.

Default = 0 (Integer > 0)

TYPE Identifies the type of the dynamic excitation.

Default = 0 (See comment 5)

Comments

1. Dynamic load sets must be selected in the I/O Options or Subcase Information sections
with the command DLOAD = SID.

2. If any DELAY, DPHASE, or TP fields are blank or zero, the corresponding , , or will
be zero.

3. RLOAD2 loads may be combined with RLOAD1 loads only by specification on a DLOAD
entry. This means that the SID on a RLOAD2 entry must not be the same as that on a
RLOAD1 entry.

4. SID must be unique for all RLOAD1 and RLOAD2 entries.

5. The TYPE field identifies the type of dynamic excitation. Valid entries for this field are
listed below alongside a description of the dynamic excitation which they invoke.

Type Description

0, L, LO, LOA, LOAD Applied load; EXCITEID references DAREA data.

1, D, DI, DIS, DISP Enforced displacement; EXCITEID references SPCD data.

1972 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Type Description

2, V, VE, VEL, VELO Enforced velocity; EXCITEID references SPCD data.

3, A, AC, ACC, ACCE Enforced acceleration; EXCITEID references SPCD data.

6. When EXCITEID refers to an SPCD entry, the modal space will be augmented with
displacement vector(s) from linear static analysis with unit prescribed displacement at
each of the SPCD degrees-of-freedom.

7. All static structural loads can be referenced by EXCITEID by referring to the SID on the
structural load. The structural loads are FORCE, FORCE1, FORCE2, MOMENT, MOMENT1,
MOMENT2, PLOAD, PLOAD1, PLOAD2, PLOAD4, RFORCE, and GRAV. EXCITEID cannot
reference the LOAD and LOADADD Bulk Data entries.

8. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1973

Proprietary Information of Altair Engineering


ROTORG

Bulk Data Entry

ROTORG – Grids for the Rotor Line Model (Rotor Dynamics).

Description

This Bulk Data Entry is used for the specification of grids that determine the Rotor Line model.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ROTORG ROTORID GRID1 GRID2 … GRIDn

Alternate Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ROTORG ROTORID GRID1 THRU GRID2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ROTORG 25 2345 2356 2400 2450

Example (Alternate Format)

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

ROTORG 30 2300 THRU 2400

Argument Options Description

ROTORID <INTEGER > 0> setid: The identification number of a rotor.

1974 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

GRIDi <INTEGER > 0> List of grids that define the rotor line model.

No default

THRU Flag indicating that a range of grid identification numbers is defined. The
initial and final grids are specified on the fields either side of the field
(Optional)
containing the THRU flag.

Comments

1. All grid point entries specified on the ROTORG entry must be unique. The program will run
into an error, if duplicate grid entries are specified.

2. Multiple ROTORG entries can be defined with the same ROTORID.

3. This ROTORG entry is used to define a Rotor Line model; therefore, for a specific
ROTORID, all grids specified on the ROTORG entry must be collinear. OptiStruct
automatically checks if the grids are collinear during a run.

4. If superelements are not used, connections between grids in the Rotor Line model and
those not listed on the ROTORG entry must be defined using MPC’s or rigid elements.

5. If superelements are used, connections between grids in the Rotor Line model and those
in the residual structure must be defined using MPC’s or rigid elements.

6. The mass of the Rotor Line model should be defined on the grids defined on the grids
specified by the ROTORG bulk data entry.

Altair Engineering OptiStruct 13.0 Reference Guide 1975

Proprietary Information of Altair Engineering


RROD

Bulk Data Entry

RROD – Rigid Pin-Ended Rod

Description

Defines a pin-ended rod that is rigid in extension.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RROD EID GA GB C MA C MB

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RROD 14 1 1115 2

Field Contents

EID Unique element identification number.

GA,GB Grid point identification numbers of connection points.

(Integer > 0 or <PartName.number>) See comment 6.

CMA,CMB Component number of one and only one dependent translational degree-
of-freedom in the global coordinate system assigned by you to either
GA or GB. Integer equal to 1, 2, or 3, or blank. Either CMA or CMB
must contain the integer and the other must be blank.

Comments

1. Element identification numbers must be unique.

2. Forces of constraint are not recovered.

1976 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. The degree-of-freedom selected to be dependent must have a non-zero component along
the axis of the rod. This implies that the rod must have finite length.

4. The degree-of-freedom declared dependent on this entry may not be:

Included in a single point constraint (SPC or SPC1).


Declared a dependent degree-of-freedom on any other RBAR, RBE1, RBE2, RBE3, or
RROD entry.
Declared a dependent degree-of-freedom on an MPC set referenced by a subcase.

5. Rigid elements are ignored in heat transfer analysis.

6. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on RROD entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry
in the model). “number” is the identification number of a referenced local entry in the part
“PartName”. See Parts and Instances in the User’s Guide for detailed information on the
use of fully qualified references.

7. This card is represented as a rod element in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1977

Proprietary Information of Altair Engineering


RSPEC

Bulk Data Entry

RSPEC – Response Spectrum Analysis Specifications

Description

Specifies directional combination method, modal combination method, excitation direction(s),


response spectra and scale factors.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RSPEC RID DC OMB MC OMB C LOSE

DTISPEC 1 SC ALE1 X11 X12 X13

DTISPEC 2 SC ALE2 X21 X22 X23

DTISPEC 3 SC ALE3 X31 X32 X33

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RSPEC 35 ALG SRSS 1.0

7 1.3 0.5 0.5 -1.

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RSPEC 35 SRSS C QC 0.0

1978 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

7 1.3 0.5 0.5 -1.

4 2.0 -2 -0.0 -1.

2 17. 0.5 -2.5 -1.

Field Contents

RID RSPEC identification number.

No default (Integer > 0)

DCOMB Method for directional combination. Can be either algebraic (ALG) or


square root of sum of squares (SRSS).

Default = ALG (ALG or SRSS)

MCOMB Method for modal combination. Can be either absolute sum (ABS),
square root of sum of squares (SRSS), complete quadratic combination
(CQC), or Navy Reseach Laboratory’s SRSS (NRL).

Default = ABS (ABS, SRSS, CQC, or NRL)

Modal frequency closeness parameter.


CLOSE
Default = 1.0 (Real)

DTISPECi Response spectrum reference. ID of a DTI,SPECSEL entry.

No default (Integer > 0)

SCALEi Scale factor for excitation.

No default (Real <> 0.0)

Xij Components of a vector representing ground excitation i, j = 1..3

Comments

1. All RSPEC cards must have unique ID numbers.

2. DTISPEC2/SCALE2/X21/X22/X23 and DTISPEC3/SCALE3/X31/X32/X33 are optional ground


excitations for multi-directional excitation. The directions of excitation have to be
orthogonal to each other and will be reported as error otherwise.

3. Refer to Response Spectrum Analysis in the User’s Guide for more details.

Altair Engineering OptiStruct 13.0 Reference Guide 1979

Proprietary Information of Altair Engineering


RSPEED

Bulk Data Entry

RSPEED – Reference Rotor Speed Values

Description

This bulk data entry is used to specify a set of reference rotor speed values for asynchronous
analysis in Rotor Dynamics.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RSPEED SID S1 DS NDS

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RSPEED 25 1500 50 5

Argument Options Description

SID <Integer > 0> Set identification number.

No default

S1 <Real > 0.0> Specifies the first reference rotor speed in the set.

No default

DS <Real > 0.0> Specifies the increment in reference rotor speed.


This value is added to each successive entry
No default starting from the first entry (S1).

1980 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

NDS <Integer > 0> Number of reference rotor speed increments.

Default = 1

Comments

1. The RSPEED bulk data entry is referenced by the SPEED field on the RGYRO bulk data
entry. If an integer value is specified in the SPEED field, multiple reference rotor speeds
specified in the RSPEED entry are used in asynchronous analysis.

2. In asynchronous frequency response analysis, if the RSPEED bulk data entry is referenced
in RGYRO, only the first frequency is considered. In complex eigenvalue analysis, the full
range specified by RSPEED is considered.

3. The following formula is used to populate the set of reference rotor speeds:

Ri ( S1 ( DS ) * i) i 1 to NDS

R1 , R2 , … RNDS represent the set of reference rotor speeds


S1 is the first reference rotor speed
DS is the reference rotor speed increment
NDS is the number of reference rotor speed increments

Altair Engineering OptiStruct 13.0 Reference Guide 1981

Proprietary Information of Altair Engineering


RSPINR

Bulk Data Entry

RSPINR – Relative Rotor Spin Rates (Rotor Dynamics)

Description

This entry defines the relative spin rates between rotors during a rotor dynamic analysis in
Modal Complex Eigenvalue or Frequency Response solution sequences.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SPINR ROTORID GRIDA GRIDB SPDUNIT SPTID

GR ALPHAR1 ALPHAR2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RSPINR 130 2400 2401 FREQ 200

0.03 5600

Argument Options Description

ROTORID <Integer > 0> setid Rotor identification number

No default

GRIDA <Integer > 0> GRIDA identifies a grid on the Rotor Line Model.

No default GRIDA and GRIDB define the positive rotor spin


direction. The vector connecting GRIDA and GRIDB is
the positive direction vector. The rotor axis is
defined using the ROTORG bulk data entry and the
two grids (GRIDA, GRIDB) are also specified on the
ROTORG bulk data entry.

1982 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

GRIDB <Integer > 0> GRIDB identifies a grid on the Rotor Line Model.

No default GRIDA and GRIDB define the positive rotor spin


direction. The vector connecting GRIDA and GRIDB is
the positive direction vector. The rotor axis is
defined using the ROTORG bulk data entry and the
two grids (GRIDA, GRIDB) are also specified on the
ROTORG bulk data entry.

SPDUNIT <RPM, FREQ> RPM: RPM specifies that the relative spin
rates are input in Revolutions Per
(No default) Minute.

FREQ: FREQ specifies that the relative spin


rates are input in revolutions
(cycles) per unit time.

SPTID <Integer > 0/Real> <Integer > 0> If an integer value (must be greater
than 0) is input, it references a
(No default) DDVAL bulk data entry that specifies
the relative rotor spin rates (see
comment 3).

<Real> If a real number is input, the value is


considered constant.

GR <Real> Rotor Structural Damping Factor (see comments 4


and 6).
Default = 0.0

ALPHAR1 <Real> Scale factor applied to the rotor mass matrix for
Rayleigh Damping (see comments 5 and 6).
Default = 0.0

Altair Engineering OptiStruct 13.0 Reference Guide 1983

Proprietary Information of Altair Engineering


Argument Options Description

ALPHAR2 <Real> Scale factor applied to the rotor stiffness matrix for
Rayleigh Damping (see comments 5 and 6).
Default = 0.0

Comments

1. A RSPINR entry must exist for each rotor line model defined using the ROTORG bulk data
entry.

2. GRIDA and GRIDB define the positive rotor spin direction. The vector connecting GRIDA
and GRIDB is the positive direction vector. The rotor axis is defined using the ROTORG bulk
data entry and the two grids (GRIDA, GRIDB) are also specified on the ROTORG bulk data
entry.

3. An integer or a real number can be input in the SPTID field. If SPTID is an integer, it
references a DDVAL bulk data entry that specifies the relative rotor spin rates. Each rotor
must be assigned the same number of spin rates. To determine relative spin rates, the
table entries which contain the sequence of spin rates are correlated. The i’th entry for
each rotor corresponds to the relative spin rates between rotors at RPMi/FREQi. The spin
rates for the reference rotor must be specified in ascending or descending order.

4. Rotor structural damping factor (GR) can be incorporated as either equivalent viscous
damping or structural damping depending on the solution sequence.

GR
BRotor structural
K rotor
WR3

Or,

K rotor (1 iGR ) K rotor

Where,

WR3 is a parameter defined by PARAM, WR3


GR is defined as a field on the RSPINR bulk data entry.

The selection depends on the following factors:

Modal frequency response or Complex eigenvalue analysis.


Synchronous or Asynchronous solutions.
Value of PARAM, GYROAVG.
5. The Rayleigh damping value for the rotor is calculated as:

Brotor Rayleigh R1 ( M rotor ) R2 (K rotor )

1984 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


6. The damping and circulation terms added to the corresponding analysis equations are
listed in the table below. Refer to the Rotor Dynamics section in the User's Guide for
detailed information.

Solution Sequence -
Damping Circulation
Analysis

[ BRC ] R1 [ M RC ] R2 [ K RC ]
Frequency Response i ([ BR ] R1 [ M R ] R 2 [ K R ])
R ( ref ) GR 1
(ASYNC) i (GR[ K R ] [ K 4 R ]) [ K RC ] [ K 4CR ]

[ BR ] R1 [M R ] R2 [KR ] [ BRC ] R1 [ M RC ] R2 [ K RC ]
Frequency Response i GR 1 R ( ref ) GR 1
(ASYNC + GYROAVG, -1) [KR ] [ K 4R ] [ K RC ] [ K 4CR ]
WR3 WR 4 WR3 WR 4

[ BRC ] R1 [ M RC ] R2 [ K RC ]
Frequency Response i ([ BR ] R1 [ M R ] R 2 [ K R ])
R ( ) GR 1
(SYNC) i (GR[ K R ] [ K 4 R ]) [ K RC ] [ K 4CR ]

[ BRC ] R1 [ M RC ] R2 [ K RC ]
R GR 1
[ BR ] R1 [M R ] R2 [KR ] [ K RC ] [ K 4CR ]
Frequency Response i
(SYNC + GYROAVG, -1)
GR 1
[KR ] [ K 4 R[ B
] C] [ M RC ] [ K RC ]
WR3 WR 4 R R1 R2

R GR 1
[ K RC ] [ K 4CR ]

[ BR ] R1 [M R ] R2 [KR ] [ BRC ] R1 [ M RC ] R2 [ K RC ]
Complex Eigenvalue i GR 1 ( ) GR 1
(ASYNC) [KR ] [RK 4 Rref] [ K RC ] [ K 4CR ]
WR3 WR 4 WR3 WR 4

Altair Engineering OptiStruct 13.0 Reference Guide 1985

Proprietary Information of Altair Engineering


Solution Sequence -
Damping Circulation
Analysis

[ BRC ] R1 [ M RC ] R2 [ K RC ]
R GR 1
[ BR ] R1 [M R ] R2 [KR ] [ K RC ] [ K 4CR ]
Complex Eigenvalue i
(SYNC)
GR 1
[KR ] [ K 4 R[ B
] C] [ M RC ] [ K RC ]
WR3 WR 4 R R1 R2

R GR 1
[ K RC ] [ K 4CR ]

Where,

[ BR ]
is the rotor viscous damping
[M R ]
is the rotor mass
[K R ]
is the rotor stiffness
[ K 4R ]
is the rotor material damping
C
[B ]
R
is the circulation, due to rotor viscous damping
C
[M ] R
is the circulation, due to rotor ‘mass’
[ K RC ]
is the circulation, due to rotor structural ‘stiffness’
C
[K 4 ] R
is the circulation, due to rotor material damping

R1 R2
and are used to define the Rayleigh viscous damping, as follows:

[ BR ]Rayleigh R1 [M R ] R2 [K R ]

WR3 and WR4 are defined by the parameters PARAM, WR3 and PARAM, WR4,
respectively.

7. Rotor damping is cumulative and caution should be exercised when multiple damping
effects are assigned.

1986 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


RSPLINE

Bulk Data Entry

RSPLINE – Interpolation Constraint Element

Description

Defines multi-point constraints for the interpolation of displacements at grid points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RSPLINE EID D/L G1 G2 C2 G3 C3 G4

C4 G5 C5 G6 … …

… …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RSPLINE 73 0.05 27 28 123456 29 30

123 75 123 71

Field Contents

EID Unique element identification number.

No default (Integer > 0)

D/L Ratio of the diameter of the elastic tube to the sum of the lengths of all
segments.

Default = 0.1 (Real > 0.0)

G# Grid point identification number.

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1987

Proprietary Information of Altair Engineering


Field Contents

C# Components to be constrained. See comment 2.

Default = blank (blank or any combination of the Integers 1 through 6)

Comments

1. Displacements are interpolated from the equations of an elastic beam passing through the
grid points. This is a linear method only element.

2. A blank field for C# indicates that all six degrees-of-freedom at G# are independent.
Since G1 must be independent, no field is provided for C1. Since the last grid point must
also be independent, the last field must be a G#, not a C#. For the example shown G1,
G3 and G6 are independent. G2 has six constrained degrees-of-freedom, while G4 and G5
each have three.

3. Dependent (that is constrained) degrees-of-freedom assigned by one rigid element may


not also be assigned dependent by another rigid element or by a multi-point constraint.

4. Degrees-of-freedom declared to be independent by one rigid body element can be made


dependent by another rigid body element or by a multi-point constraint.

5. Rigid elements (including RSPLINE), unlike MPCs, form part of the model and do not need
to be selected from within a subcase definition.

6. Rigid elements are ignored in heat transfer problems.

7. The constraint coefficient matrix is affected by the order of the Gi Ci pairs on the RSPLINE
entry. The order of the pairs should be specified in the same order that they appear
along the line that joins the two regions. If this order is not followed, then the RSPLINE
will have folds in it that may yield some unexpected interpolation results.

8. The independent degrees-of-freedom that are the rotation components most nearly
parallel to the line joining the regions should not normally be constrained.

9. The default RSPLINE implementation has larger-than-expected in-plane rotation at the


two RSPLINE end nodes and where RSPLINE have sharp angles. Applying
PARAM,RSPLICOR reduces such rotation and yields better results.

10. Rigid elements are ignored in heat transfer analysis.

1988 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


RSSCON

Bulk Data Entry

RSSCON – Shell-to-Solid Element Connector

Description

Defines multi-point constraints to model clamped connections of shell-to-solid elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RSSC ON RBID TYPE ES1 EA1 EB1 ES2 EA2 EB2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RSSC ON 110 GRID 11 12 13 14 15 16

Field Contents

RBID Unique element identification number.

No default (Integer > 0)

TYPE Type of connectivity.

“ELEM” - connection is described with element identification numbers.

“GRID” - connection is described with grid point.

Default = ELEM (GRID or ELEM)

ES1 Shell element identification number if TYPE = “ELEM.”

Shell grid point identification number if TYPE = “GRID.”

No default (Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 1989

Proprietary Information of Altair Engineering


Field Contents

EA1 Solid element identification number if TYPE = “ELEM.”

Solid grid point identification number if TYPE = “GRID.”

No default (Integer > 0)

EB1 Solid grid-point identification number for TYPE = “GRID” only.

Default = blank (Integer > 0 or blank)

ES2 Shell grid-point identification number for TYPE = “GRID” only.

Default = blank (Integer > 0 or blank)

EA2 Solid grid-point identification number for TYPE = “GRID” only.

Default = blank (Integer > 0 or blank)

EB2 Solid grid-point identification number for TYPE = “GRID” only.

Default = blank (Integer > 0 or blank)

Comments

1. RSSCON generates a multipoint constraint that models a clamped connection between a


shell and a solid element. The shell degrees-of- freedom are considered dependent. The
translational degrees-of- freedom of the shell edge are connected to the translational
degrees-of- freedom of the upper and lower solid edge. The rotational degrees-of-
freedom of the shell are connected to the translational degrees-of-freedom of the lower
and upper edges of the solid element face. Poisson’s ratio effects are considered in the
translational degrees-of-freedom.

2. The shell grid point must lie on the line connecting the two solid grid points. It can have
an offset from this line, which can not be more than 5% of the distance between the two
solid grid points. The shell grid points that are out of the tolerance will not be
constrained, and a fatal message will be issued. This tolerance is adjustable. Refer to
PARAM,TOLRSC and PARAM,SEPIXOVR.

3. When using the TYPE = “ELEM” option:

The elements may be first or second order.


When a straight shell element edge and a solid element are connected, the geometry
of the shell edge is not changed to fit the solid face. When a curved shell element
edge and a solid element are connected, the two solid edges and solid face are not
changed to match the shell edge.

1990 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


It is not recommended to connect more than one shell element to the same solid using
the ELEM option. If attempted, conflicts in the multipoint constraint relations may lead
to UFM 6692.

4. When using TYPE = “GRID” option:

The GRID option does not verify that the grids used are valid shell and/or solid grids.

The GRID option is not recommended for 2nd order elements.

5. It is recommended that the height of the solid element’s face is approximately equal to
the shell element’s thickness of the shell. The shell edge should then be placed in the
middle of the solid face.

6. The shell edge may coincide with the upper or lower edge of the solid face.

7. The RSSCON entry, unlike MPCs, is part of the model and does not need to be selected in
a subcase definition.

8. RSSCON is ignored in heat-transfer problems.

Altair Engineering OptiStruct 13.0 Reference Guide 1991

Proprietary Information of Altair Engineering


RWALADD

Bulk Data Entry

RWALADD – Rigid Wall Combination for Geometric Nonlinear Analysis

Description

Defines a rigid wall set as a union of rigid walls defined via RWALL entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RWALADD SID S1 S2 S3 S4 S5 S6 S7

S8 S9 etc.

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RWALADD 101 2 3 1 6 4

Field Contents

SID Set identification number.

(Integer > 0)

Sj Set identification numbers of rigid wall sets defined via RWALL entries.

(Integer > 0)

Comments

1. Multipoint constraint sets must be selected with the Subcase Information command
RWALL=SID.

2. The Sj must be unique and may not be the identification number of a rigid wall set defined
by another RWALADD entry.

1992 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. RWALADD entries take precedence over RWALL entries. If both have the same SID, only
the RWALADD entry will be used.

4. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1993

Proprietary Information of Altair Engineering


RWALL

Bulk Data Entry

RWALL – Rigid Wall for Geometric Nonlinear Analysis

Description

Defines a rigid wall for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RWALL SID RWTYPE SLID GISD1 GSID2 FRIC DIST

G0/X0 Y0 Z0 IFILT FFAC

X1 Y1 Z1 X2 Y2 Z2 DIA

MASS VX VY VZ

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

RWALL 2 PLANE SLIDE 23 5 3

21 2 1

11 24 12

340 7 13 32

Field Contents

SID Load set identification number.

No default (Integer > 0)

1994 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

RWTYPE Rigid wall type.

PLANE – Infinite plane.


CYL – Infinite cylinder of diameter DIA.
SPHER – Sphere of diameter DIA.
PARAL - Parallelogram.

Default = PLANE (PLANE, CYL, SPHERE, or PARAL)

SLID Flag for sliding.

SLIDE – Sliding.
TIED – Tied.
SLFRIC – Sliding with friction.

Default = SLIDE (SLIDE, TIED, or SLFRIC)

GSID1 Grid set ID defining slave grids to be added to the rigid wall.

(Integer > 0)

GSID2 Grid set ID defining slave grids to be deleted from the rigid wall.

(Integer > 0)

FRIC Friction coefficient (ignored if SLID = TIED, SLIDE).

Default = 0.0 (Real > 0)

DIST Distance for slave search (See comment 2).

(Real > 0)

G0 Grid identifier defining M, definition ignores Y0, Z0. Moving rigid wall.

(Integer > 0)

X0, Y0, Z0 Coordinates of a point M defining rigid wall location if G0 not defined.
Rigid wall does not move.

(Real)

IFILT Friction filtering flag (See comment 4).

Altair Engineering OptiStruct 13.0 Reference Guide 1995

Proprietary Information of Altair Engineering


Field Contents

Default = 0 (Integer = 0, …, 3)

1 – Direct user input of filtering coefficient.


2 – Filtering coefficient corresponds to a 3dB filtering level.
3 - Filtering coefficient corresponds to a 3dB filtering level for user
defined frequency (frequency defined in terms of time step number).

FFAC Friction filtering factor.

Default = 0.0 (Real)

X1, Y1, Z1 Coordinates of a point defining M1 for RWTYPE = PLANE, CYL, PARAL.

(Real)

X2, Y2, Z2 Coordinates of a point defining M2 for RWTYPE = PARAL.

(Real)

DIA Diameter for RWTYPE = CYL, SPHER.

(Real > 0)

MASS Mass of moving rigid wall if G0 is defined.

(Real > 0)

VX, VY, VZ Components of initial velocity if G0 is defined.

(Real)

Comments

1. RWALL must be selected in the subcase with RWALL = SID or by RWALADD. It can only
be selected in geometric nonlinear analysis subcases which are defined by an ANALYSIS =
NLGEOM, IMPDYN or EXPDYN subcase entry.

2. Initially the slave nodes can be defined at a distance lower than DIST.

3. Nodal thickness of rigid wall slave nodes is not taken into account.

4. IFILT defines the method for computing the friction filtering coefficient. Friction filtering

slave node in contact are filtered using a simple rule:

F T = α * F'T + (1 - α) * F'T-1

1996 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


where,

F T - Tangential force

F'T - Tangential force at time t

F'T-1 - Tangential force at time t-1

α - filtering coefficient

IFILT = 1 – α = FFAC

IFILT = 2 – α = 2 dt * freq, where dt = time step, and freq = FFAC

IFILT = 3 – α = 2 / N, with 1/freq = T = N * dt, and N = FFAC

5. Surface input type

Type Description

PLANE MM1 defines the normal direction.

CYL MM1 defines the axis of the cylinder.

SPHER M is the center of the sphere.

PARAL MM1 and MM2 define the parallelogram with the normal
as cross product MM1 x MM2.

6. This card is represented as a rigid wall in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 1997

Proprietary Information of Altair Engineering


SECT

Bulk Data Entry

SECT – Section Definition for Section Force Output in Geometric Nonlinear Analysis

Description

Defines a section for force output in geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SEC T SC ID G0 G1 G2 GRSET ELSET IFRAME C ID

DT

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SEC T 2 234 665 723 3 4

Field Contents

SCID Section identification number.

No default (Integer > 0)

G0, G1, G2 Grid points defining the local axes of the section. G0 and G1 define
the local x-axis while G0, G1, and G3 define the local xy-plane.

No default (Integer > 0)

GRSET Grid set ID.

No default (Integer > 0)

ELSET Element set ID. Only sets of SOLID, SHELL, ROD, BAR, and BEAM
elements can be used.

(Integer > 0)

1998 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

IFRAME Flag for computing the center of the output coordinate system.
The local system is defined by G0, G1, and G2.

Default = 0 (Integer = 0, 1, 2, 3, 10, 11, 12, 13)

0 – Origin of the local system defined by G0, G1, and G2

1 – Geometrical center of the section grid in the local system


defined by G0, G1, and G2

2 – Center of gravity of the section in the local system defined by


G0, G1, and G2

3 – Origin of the basic system in the local system defined by G0,


G1, and G2

10 – Origin of the basic system

11 – Geometrical center of the section in the basic system

12 – Center of gravity of the section in the basic system

13 – Origin of the basic system

CID Moving coordinate system identifier for automatic definition of a


section. Only CORD1R and CORD3R can be selected (See comment
4).

Default = 0 (Integer > 0)

DT Time step for saving the data.

Default = DTTH defined on XSOM (Real > 0)

Comments

1. SECT output must be selected for time history output with XHIST. It is only available for
geometric nonlinear analysis subcases which are defined by an ANALYSIS = NLGEOM,
IMPDYN or EXPDYN subcase entry.

2. Moments are computed with respect to the section center defined by the parameter
IFRAME and expressed in the local section frame.

3. Normal force is the component normal to the XY plane of the section. The tangential
force is the component in the plane of the section.

4. For CID > 0:

G0, G1, G2 blank – the local system of the section is built from the grid points defining
the CORD1R or CORD3R.
The element set is created automatically from the elements intersected by the xy-
plane of CID.

Altair Engineering OptiStruct 13.0 Reference Guide 1999

Proprietary Information of Altair Engineering


The grid set is created automatically from the grid points of the intersected elements
on the positive z-axis defined by the xy-plane plane of the frame.

5. This card is represented as an interface in HyperMesh.

2000 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SENSOR

Bulk Data Entry

SENSOR – Sensor Definition

Description

Defines a sensor for geometric nonlinear analysis. Sensors may be used to activate loads
(see NLOAD1).

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SENSOR SID STYPE DELAY NAC C

Continuation lines if STYPE = ACCEL (number of continuation lines = NACC)

AID1 DIR1 AMIN1 TMIN1

AID2 DIR2 AMIN2 TMIN2

… …

Continuation line if STYPE = DIST

G1 G2 DMIN DMAX

Continuation line if STYPE = SENS, AND, OR

SID1 SID2

Continuation line if STYPE = NOT

SID1

Continuation line if STYPE = INTER

C ID

Altair Engineering OptiStruct 13.0 Reference Guide 2001

Proprietary Information of Altair Engineering


Continuation line if STYPE = RWAL

RWID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SENSOR 100 AC C EL 1

7 X 500.0 0.03

Field Contents

SID Unique sensor identification number.

No default (Integer > 0)

STYPE Sensor type. May be one of:

TIME – Start Time


ACCE – Accelerometer
DIST – Nodal distance
SENS – Activation with sensor SID1, deactivation with sensor SID2
INTER – Interface activation and deactivation
RWAL – Rigid wall activation and deactivation
AND – ON as long as sensors SID1 and SID2 are ON
NOT – ON as long as sensor SID1 is OFF
OR – ON as long as sensors SID1 and SID2 are ON

No default (ACCEL, AND, DIST, INTER, NOT, OR, RWAL, SENS, or


TIME)

DELAY Time delay.

(Real > 0)

NACC Number of accelerometers ACCEL.

(0 < Integer < 6)

AID# Accelerometer identifier, references the ID of an ACCLR bulk data


entry.

(Integer > 0)

2002 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

DIR# Direction of accelerometer #. May be one of:

X – X direction

Y – Y direction

Z – Z direction

XY – XY plane

YZ – YZ plane

ZX – ZX plane

XYZ – total acceleration

No default (X, Y, Z, XY, XZ, YZ, or XYZ)

AMIN# Minimum absolute value for acceleration for accelerometer #.

(Real > 0)

TMIN# Minimum duration of AMIN for accelerometer #.

(Real > 0)

G1 Grid ID 1.

(Integer > 0)

G2 Grid ID 2.

(Integer > 0)

DMIN Distance minimum.

(Real > 0)

DMAX Distance maximum.

(Real > 0)

SID1 Activation sensor identifier, references the ID of another SENSOR


bulk data entry.

(Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 2003

Proprietary Information of Altair Engineering


Field Contents

SID2 Deactivation sensor identifier, references the ID of another SENSOR


bulk data entry.

(Integer > 0)

CID Contact identifier, references the ID of a CONTACT bulk data entry.

(Integer > 0)

RWID Rigid Wall identifier, references the ID of a RWALL bulk data entry.

(Integer > 0)

Comments

1. A sensor can only be activated once.

2. For STYPE=TIME, the sensor is activated after the time delay (DELAY).

3. For STYPE=ACCE, the sensor is activated if one of the accelerometers gives an


acceleration greater than AMIN during a time greater than TMIN.

The time of activation of the sensor is the time at which the above criteria is first met
plus the time delay (DELAY).

4. For STYPE=DIST, the sensor is activated once the distance between G1 and G2 moves
outside the allowable range (between DMIN and DMAX).

The time of activation of the sensor is the time at which the above criteria is first met,
plus the time delay (DELAY).

5. For STYPE=SENS, the sensor is activated once the referenced sensor SID1 is activated.
The minimum activation duration is given by the time delay (DELAY). After this minimum
activation duration, the sensor is deactivated if referenced sensor SID2 is activated. If
there is no SID2 referenced, then the sensor is deactivated after the time delay.

2004 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


6. For STYPE=AND, the sensor is activated once both the referenced sensors (SID1 and
SID2) are activated.

7. For STYPE=OR, the sensor is activated once either of the referenced sensors (SID1 or
SID2) are activated.

8. For STYPE=NOT, the sensor is active whenever the referenced sensor SID1 is not active.

Altair Engineering OptiStruct 13.0 Reference Guide 2005

Proprietary Information of Altair Engineering


9. For STYPE=INTER, the sensor is activated once the referenced contact (CID) is impacted.
The sensor is deactivated if there is no impact during a time equal to the time delay
(DELAY).

10. For STYPE=RWAL, the sensor is activated once the referenced rigid wall (RWID) is
impacted. The sensor is deactivated if there is no impact during a time equal to the time
delay (DELAY).

2006 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SET

Bulk Data Entry

SET – Set Definition

Description

Defines a set of grids, elements, design variables, MBD entities, mode numbers, frequencies or
times for reference by other input definitions.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SET SID TYPE SUBTYPE/


OPERATOR

ID1/ ID2/ ID3/ ID4/ ID5/ ID6/ ID7/ ID8/


MODE1/ MODE2/ MODE3/ MODE4/ MODE5/ MODE6/ MODE7/ MODE8/
REAL1/ REAL2/ REAL3/ REAL4/ REAL5/ REAL6/ REAL7/ REAL8/
NAME1/ NAME2/ NAME3/ NAME4/ NAME5/ NAME6/ NAME7/ NAME8/
SID1/ SID2/ SID3/ SID4/ SID5/ SID6/ SID7 SID8
X1/G1/ Y1 Z1 X2/G2 Y2 Z2
ALL

ID9/ … … … … … … …
MODE9/
REAL9/
NAME9/
SID9

… …

Alternate Format for ID Ranges

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SET SID TYPE SUBTYPE

ID1 THRU ID2 EXC EPT ID3 ID4 ID5 ID6

ID7 … ENDTHRU

Altair Engineering OptiStruct 13.0 Reference Guide 2007

Proprietary Information of Altair Engineering


Example 1

The following set contains the grids 1, 17, 22, 23, 29, 33, 35, 48, 88, 93 and 102. It is
defined using a simple ID list (assuming that these GRID cards are present in the Bulk
Data).

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SET 56 GRID LIST

88 93 17 1 23 29 35 48

33 102 22

Example 2

The following set contains the elements 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 33,
34, 34, 35, 36, 37, 38, 41, 42, 43, 44, 45, 94, 95, 96. 97, 98, 99, 106, 107, 108, 109, 110,
111, 120, 121 and 125. It is defined using a combination of ID ranges and lists.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SET 56 ELEM LIST

11 THRU 22

33 THRU 45 EXC EPT 39 40

94 THRU 111 EXC EPT 100 101 102 103

104 105 ENDTHR


U

120 121 125

Example 3

The following set includes any element included in sets 29, 30 or 31. It is defined as
Boolean set.

2008 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SET 50 ELEM OR

29 30 31

Example 4

The following set defines GRID/Component list; intended for use by PFMODE.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SET 11 GRIDC

12 T1 15 R2 128 T3

Example 5

The following set defines list of strings.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SET 11 LABEL

LABEL1 LABEL2 TOP UPPER LOWER LEFT

Example 6

The following set defines list of all elements with specific properties.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SET 11 ELEM PROP EXC EPT PHSELL

1 12 15 thru 128 555

Example 7

Altair Engineering OptiStruct 13.0 Reference Guide 2009

Proprietary Information of Altair Engineering


The following set outputs all of the grids on PLOTEL.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SET ID GRID ELTYPE

PLOTEL

Field Contents

SID Unique set identification number. See comment 1.

No default (Integer > 0)

TYPE Identifies what type of entities the set is comprised of. See comment 2
for description of the types.

No default (GRID, ELEM, RIGID, GRIDC, DESVAR, MODE, FREQ, TIME,


LABEL or PLY)

SUBTYPE Indicates how the set is defined. See comment 2 for description of
subtypes.

Default = LIST (LIST, BBOX, PROP, MAT or ELTYPE)

OPERATOR Operators supported in defining Boolean sets (see comments 4, 5, and


6.)

No default (OR, AND, NOT, MINUS)

ID# ID list. Only valid for certain combinations of TYPE and SUBTYPE. The
entity to which the ID corresponds depends on the TYPE and SUBTYPE
of the set (see comment 2).

ID ranges may be used in combination with ID lists. The keywords


EXCEPT and THRU are used to define ID ranges. The keyword ENDTHRU
identifies the end of an ID range and is required if an ID list is to follow
where the first value is within the previous range.

ID lists following EXCEPT must be in ascending order and must exist


within the previous range.

No default (Integer > 0)

MODE# Mode number list. Only valid when TYPE is MODE (see comment 2).

Mode number ranges may be used in combination with Mode number


lists. The same rules apply as for ID ranges.

No default (Integer > 0)

2010 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

REAL# Real value list. Only valid when TYPE is FREQ or TIME (see comment
2).

No default (Real)

NAME# Keyword list. Only valid for certain combinations of TYPE and SUBTYPE.

The keyword EXCEPT is allowed only as the first entry in a keyword list.

Default = Undefined (see comment 2)

SID# Identification number of another SET definition. Used in defining Boolean


sets. Only valid when OPERATOR is defined in SUBTYPE/OPERATOR field
(see comments 4, 5, 6, and 7).

No default (Integer > 0 or <PartName.number>)

X1, Y1, Z1 X, Y & Z coordinates of two opposing corners of a cuboid. Only valid
X2, Y2, Z2 when SUBTYPE is BBOX (see comment 2).

No default (Real)

G1, G2 Grid ID’s (G1, G2) can be used instead of (X1, Y1, Z1), (X2, Y2, Z2)
data (see field descriptions above). G1, G2 should be defined in the
basic coordinate system (CP field on the GRID entries should be blank).

ALL Keyword used for ID lists to indicate that all IDs of the appropriate
entity type are to be included in the set.

Only valid in first field of ID list.

May be followed by keyword EXCEPT (see below).

THRU Keyword used for ID ranges to indicate that all IDs between the
preceding ID and the following ID are to be included in the set.

Definition of range may contain list of exceptions in the following form:

N1 THRU N2 EXCEPT N3 N4 ... ENDTHRU

where N1 < N3 < N4... < N2; N1 < N2

EXCEPT Keyword used for ID ranges and keyword lists to indicate that the
following IDs or keywords are to be excluded from the set.

Only valid in first field for keyword lists.

When ALL is given as the first entry for an ID list, EXCEPT may be given
as the second entry, in which case all subsequent IDs are excluded from
the set of ALL entities of the defined TYPE.

Altair Engineering OptiStruct 13.0 Reference Guide 2011

Proprietary Information of Altair Engineering


Field Contents

ENDTHRU Optional keyword used after EXCEPT to indicate the end of an excluded
ID list definition.

Comments

1. SID must be unique with respect to all other SET definitions (regardless of type). It must
also be unique with respect to any SURF entries and any legacy SET/PSET I/O Options
definitions.

2. The following table describes subtype combinations and the set TYPEs for which they are
valid.

TYPE SUBTYPE Description

GRID LIST This is a set of grids - structural grids (GRID) or scalar


or points (SPOINT) - defined either as a simple list of grid
undefined IDs, or as some combination of ranges of grid IDs and
lists of grid IDs.

BBOX This is a set of grids defined by a bounding box. The


fields X1, Y1, and Z1 provide the coordinates of one
corner and X2, Y2, and Z2 the coordinates of an
opposing corner of a cuboid. All grids contained within
this cuboid are included in the set.

The bounding box can also be defined using the G1 and


G2 fields instead of (X1, Y1, and Z1) and (X2, Y2, and
Z2), respectively.

ELEM LIST This is a set of elements defined either as a simple list of


or element IDs, or as some combination of ranges of
undefined element IDs and lists of element IDs.

BBOX This is a set of elements defined by a bounding box. The


fields X1, Y1, and Z1 provide the coordinates of one
corner and X2, Y2, and Z2 the coordinates of an
opposing corner of a cuboid. All elements whose
centroids are contained within this cuboid are included in
the set.

The bounding box can also be defined using the G1 and


G2 fields instead of (X1, Y1, and Z1) and (X2, Y2, and
Z2), respectively.

PROP This is a set of elements defined in one of the following


ways:

1. Through a list of property IDs, or some combination

2012 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


TYPE SUBTYPE Description

of ranges of property IDs and lists of property IDs.


If multiple properties have the same ID (as PBAR and
PSHELL may), they are all considered. All elements
referencing the selected properties are included in
the set.

2. Through a list of property types. All elements


referencing properties of the listed type (PBAR,
PCOMP, PSHELL, and so on) are included in the set.

3. Through a list of excluded property types. All


elements except those referencing properties of the
listed type, following the keyword EXCEPT, are
included in the set.

4. List of property types or list of excluded property


types may be followed by some combination of
ranges of property IDs and lists of property IDs. All
elements referencing properties satisfying both
requirements (type and ID) are included in (or
accepted from) the set.

MAT This is a set of elements defined through a list of


material IDs, or some combination of ranges of material
IDs and lists of material IDs. All elements referencing
properties, that in turn reference the selected materials,
are included in the set.

ELTYPE This is a set of elements defined in one of the following


ways:

1. Through a list of element types. All elements of the


listed type (CQUAD4, CHEXA, CBEAM, and so on) are
included in the set.

2. Through a list of excluded element types. All


elements except those of the listed type, following
the keyword EXCEPT, are included in the set.

In addition to all valid element types, the following


element type groupings may be used:

SOLID for CTETRA, CPYRA, CPENTA and CHEXA


elements referencing structural property
definitions

FLAT for CQUAD4, CQUAD8, CTRIA3 and CTRIA6


elements.

Altair Engineering OptiStruct 13.0 Reference Guide 2013

Proprietary Information of Altair Engineering


TYPE SUBTYPE Description

SHELL for FLAT elements referencing properties


with non-zero MID2.

MEMBRANE for FLAT elements referencing properties


with zero MID2.

BEAM for CBAR and CBEAM elements.

ROD for CONROD and CROD elements.

FLUID for CTETRA, CPYRA, CPENTA and CHEXA


elements referencing fluid property
definitions.

For rigid elements (RROD, RBAR, RBE1, RBE2 and RBE3).


See RIGID below.

RIGID LIST This is a set of Rigid elements defined either as a simple


or list of Rigid element IDs, or as a combination of ranges of
undefined Rigid element IDs and lists of Rigid element IDs.

GRIDC LIST This is a set of GRID/Component pairs.


or
undefined

DESVAR LIST This is a set of design variables defined either as a


or simple list of design variable IDs, or as some combination
undefined of ranges of design variable IDs and lists of design
variable IDs.

MODE LIST This is a set of mode numbers defined as a simple list of


or mode numbers, or as some combination of ranges of
undefined mode numbers and lists of mode numbers.

FREQ LIST This is a set of real values representing frequencies


or defined simply as a list of real values.
undefined

TIME LIST This is a set of real values representing times defined


or simply as a list of real values.
undefined

LABEL LIST List of arbitrary labels. Each label must start with a
or letter and contain only letters or digits.
undefined

2014 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


TYPE SUBTYPE Description

PLY LIST This is a set of ply ID’s defined in the PLY or PCOMPG
or data entries.
undefined

3. SET definitions using IDs may refer to non-existing entities. This is allowed, but the
actual SET will contain only grids or elements which are actually present in the structure.

4. The Boolean operators OR, AND, NOT and MINUS are recognized for SET combinations.
These operators are described here:

Operator Description

OR An entity is included in the SET if it is included in at least one of the


constituent sets. Is the entity in set1 or set2 or set3 …?

AND An entity is included in the SET if it is included in all of the listed sets. Is
the entity in set1 and set2 and set3 …?

NOT An entity is included in the SET if it is not included in the listed set. Is
the entity in set1?; if not then it is included in this set.

Only one set may be listed for the NOT operator.

MINUS An entity is included in the SET if it is included in the first set, but not in
the second set. Only two sets may be listed for when this operator is
used.

5. Boolean SET definitions can only be used when all listed sets are of the same TYPE.

6. Boolean SET definitions can reference other Boolean sets, but circular references must be
avoided. Boolean SET can be defined only for GRID, ELEM, or RIGID set types.

7. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on SET entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN bulk data entry
in the model). “number” is the identification number of a referenced local entry in the part
“PartName”. See Parts and Instances in the User’s Guide for detailed information on the
use of fully qualified references.

The SET bulk data entry can be used in the global part to reference SET’s defined within
different parts. These SET entries in the global part can contain fully qualified references
to part-specific SET data only if logical operators (OPERATOR field) are used. For
example:

The following SET entry exists in part “A”:


BEGIN, FEMODEL, A
SET, 29, ELEM, LIST

Altair Engineering OptiStruct 13.0 Reference Guide 2015

Proprietary Information of Altair Engineering


15 THRU 30

END, FEMODEL, A

Referencing SET, 29 in the global part “G”:


BEGIN, FEMODEL, G
SET, 78, ELEM, OR
A.29

END, FEMODEL, G

8. This card is represented as a set in HyperMesh.

2016 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SET1

Bulk Data Entry

SET1 – Set Definition

Description

Defines a list of structural grid points or element identification numbers.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SET1 SID ID1 ID2 ID3 ID4 ID5 ID6 ID7

ID8 etc.

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SET1 3 31 62 93 124 16 17 18

19

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SET1 6 29 32 THRU 50 61 THRU 70

17 57

Field Contents

SID Unique identification number.

(Integer > 0)

Altair Engineering OptiStruct 13.0 Reference Guide 2017

Proprietary Information of Altair Engineering


Field Contents

IDi List of structural grid point or element identification numbers.

(Integer > 0 or "THRU, ENDTHRU, and EXCEPT"; for the "THRU" option,
ID1 < ID2)

Comments

1. When using "THRU," missing ID's are ignored.

2. All set ID’s must be unique for all bulk data SET, SET1, SET3, and solution control SET
data.

3. The use of keywords THRU, ENDTHRU, and EXCEPT are allowed.

4. This card is represented as a set in HyperMesh.

2018 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SET3

Bulk Data Entry

SET3 – Set Definition

Description

Defines a set of grids or elements.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SET3 SID TYPE ID1 ID2 ID3 ID4 ID5 ID6

ID7 ID8 etc.

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SET3 1 PROP 11 12 13 15 18 21

Alternate Format and Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SET3 SID TYPE ID1 "THRU" ID2

SET3 33 GRID 20 THRU 60

Field Contents

SID Unique identification number.

(Integer > 0)

TYPE Set type (Character). Valid options include "GRID," "ELEM," and "PROP."

Altair Engineering OptiStruct 13.0 Reference Guide 2019

Proprietary Information of Altair Engineering


Field Contents

IDi Identifiers of grid points, elements, or properties.

(Integer > 0)

Comments

1. If the set type is PROP, then a list of elements associated with the property ID's listed is
created.

2. All set ID’s must be unique for all bulk data SET, SET1, SET3, and solution control SET
data.

3. The use of keywords THRU, ENDTHRU, and EXCEPT are allowed.

4. This card is represented as a set in HyperMesh.

2020 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SLOAD

Bulk Data Entry

SLOAD – Static Scalar Load

Description

Defines concentrated static loads on scalar, grid or fluid points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SLOAD SID S1 F1 S2 F2 S3 F3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SLOAD 21 3 4.5 4 29.0

Field Contents

SID Load set identification number.

No default (Integer > 0)

S# Identification number of a scalar, grid or fluid point.

No default (Integer > 0)

F# Load magnitude.

No default (Real)

Comments

1. SLOAD may be referenced as the EXCITEID on an ACSRCE bulk data entry.

2. Up to three loads may be defined on a single entry.

Altair Engineering OptiStruct 13.0 Reference Guide 2021

Proprietary Information of Altair Engineering


SOLVTYP

Bulk Data Entry

SOLVTYP – Solver Selection for Static Analysis and Geometric Nonlinear Implicit Analysis

Description

This bulk data entry can be used to define the solver type to be used for linear and nonlinear
static analysis and geometric nonlinear implicit analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SOLVTYP SID SOLVER

Continuation line for SOLVER = PCG, MIXED and AUTO

PC ON MAXIT ITOL TOL

Continuation line for SOLVER = MUMPS

ORDM

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SOLVTYP 4 PC G

FAI

Alternate Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SOLVTYP 1 MUMPS

2022 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PORD

Field Contents

SID Unique set identification number.

No default (Integer > 0)

SOLVER Indicates the solver to be used. See comments 2, 3 and 4.

BCS – Boeing Solver (direct solver).

MUMPS – MUMPS Solver (direct solver).

PCG - Preconditioned Conjugate Gradient (iterative solver).

MIXED – Mixed solver using both BCS and PCG.

AUTO – Select automatic between BCS and PCG.

Default = BCS - for linear static analysis and geometric nonlinear implicit
dynamic analysis (ANALYSIS = IMPDYN);

Default = MIXED - for geometric nonlinear implicit static analysis


(ANALYSIS = NLGEOM).

PCON Indicates the type of pre-conditioner to be used.

NO - No Pre-conditioner

DJ - Diagonal Jacobi

ICH - Incomplete Cholesky

SICH - Stabilized Incomplete Cholesky

FAI - Factored Approximate Inverse

Default = FAI (Character)

MAXIT Maximum number of iterations

Default = Number of degrees-of-freedom of the system (Integer > 0 or


blank)

ITOL Convergence criteria for preconditioned iterative solver.

RROM - Relative residual of original matrices ||r|| < TOL * ||b||

RRPM1 - Relative residual of preconditioned matrices ||r|| < TOL * ||

Altair Engineering OptiStruct 13.0 Reference Guide 2023

Proprietary Information of Altair Engineering


Field Contents

b||

RRPM2 - Relative residual of preconditioned matrices ||r|| < TOL * ||


A|| * ||x||

If the solver solves Ax = b, the residual is r = Ax - b.

Default = RRPM2 (Character)

TOL Convergence tolerance.

Default = 1.0e-5 for ITOL = RROM, RRPM1 or


single precision machine precision (3.0e-8) for ITOL = RRPM2 (Real > 0
or blank)

ORDM Ordering method for the MUMPS solver (see comments 8 and 9).

AMD – Approximate minimum degree method (AMD)

PORD – PORD package

METIS – METIS package

AUTO – Automatically select between PORD and METIS.

Default = METIS (Character)

Comments

1. SOLVTYP bulk data must be referenced by a SOLVTYP subcase statement. It only applies
to linear static subcases, geometric nonlinear implicit static analysis (ANALYSIS=NLGEOM)
and geometric nonlinear implicit dynamic analysis (ANALYSIS=IMPDYN).

2. In optimization of linear static subcases, if iterative solver is selected, and if the


responses DRESP1, RTYPE = DISP, LAMA, STRESS, STRAIN, CSTRESS, CSTRAIN,
CFAILURE, or FORCE are present the solver is automatically reverted to the direct solver.

3. MUMPS is the default non-symmetric solver for nonlinear contact analysis when friction is
present; it is also available as an optional symmetric solver for static runs. MUMPS is SMP
parallelized. Generally, MUMPS performance is similar to or better than the performance of
BCS, especially for 2D models.

MUMPS stands for “Multifrontal Massively Parallel sparse direct Solver”.

For more details, see http://graal.ens-lyon.fr/MUMPS/index.php?page=home

4. Overview of default settings and options for the SOLVER field:

2024 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SOLVER SOLVER SOLVER SOLVER SOLVER
Subcase type
=BCS =MUMPS =PCG =MIXED =AUTO

Linear static Default Optional Optional N/A N/A


analysis

Nonlinear static Default Optional N/A N/A N/A


analysis

Nonlinear contact Optional Default N/A N/A N/A


analysis (when
friction is
present)

Geometric Optional N/A Optional Default Optional


nonlinear implicit
static analysis
(NLGEOM)

Geometric Default N/A Optional Optional Optional


nonlinear implicit
dynamic analysis
(IMPDYN)

5. The iterative solver is a preconditioned conjugate gradient solver. A Factored


Approximate Inverse Preconditioner is the default method. This solver is also SMP
parallelized.

6. The performance of the iterative solver depends on the conditioning of the stiffness
matrix. For compact solid models, the iterative solver may perform considerably better
than the direct solver in terms of memory usage and elapsed times for a single linear
static subcase. In the case of multiple linear static subcases, the iterative solver may
perform worse than the direct solver. The breakeven point is at about 4-6 subcases.
The performance depends on model, hardware, operating system, and potentially the
system load. The performance may be below expectations on Itanium-based computers.

7. When the automatic solver option (SOLVER = AUTO) has been chosen, PCG is used first,
the solver will be changed automatically to direct solver (BCS) if PCG performance is
estimated slower than direct solver. In this case, direct solver will be used for the
remainder of the run.

8. ORDM = PORD provides better performance for a shell-type model.

9. For further information about the MUMPS solver ordering method (ORDM) options, refer to
the MUMPS 4.10 manual.

10. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2025

Proprietary Information of Altair Engineering


SPC

Bulk Data Entry

SPC – Single-Point Constraint

Description

Defines sets of single-point constraints, enforced displacements for static analysis, and
thermal boundary conditions for heat transfer analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SPC SID G C D G C D

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SPC 2 32 436 0.0

Field Contents

SID Identification number of single-point constraint set.

(Integer > 0)

G Grid or scalar point identification number.

(Integer > 0 or <PartName.number>)

C Component numbers.

(Integer zero or blank for scalar points, or up to six unique digits (0 < digit <
6) may be placed in the field with no embedded blanks for grid points. The
components refer to the coordinate system referenced by the grid points.)

D Value of enforced displacement for all coordinates designated by G and C.

(Real)

Comments

2026 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


1. The degree-of-freedom declared dependent on this entry may not be:

Included in a single point constraint (SPC or SPC1).


Declared a dependent degree-of-freedom on any RBAR, RBE1, RBE2, or RROD entry.
Declared a dependent degree-of-freedom on an MPC set referenced in the same
subcase.
2. Single-point forces of constraint are recovered during stress data recovery.

3. Up to twelve single-point constraints may be defined on a single entry.

4. Continuations are not allowed.

5. SPC degrees-of-freedom may be redundantly specified as permanent constraints on the


GRID entry.

6. For static analyses, SPCs can be used to define enforced displacements.

7. For static and dynamic analyses, when the SPSYNTAX setting on the SYSSETTING I/O
option is set to CHECK (default) or STRICT, it is required for grid/component pairs (G#/
C#) that the component be 0 or blank when the grid reference is a scalar point (SPOINT),
and that the component be > 1 when the grid reference is a structural grid point (GRID).
When SPSYNTAX is set to MIXED, it is allowed for grid/component pairs (G#/C#) that the
grid reference be either a scalar point (SPOINT) or a structural grid point (GRID) when the
component is 0, 1 or blank; interpreting all of these as 0 for scalar points and as 1 for
structural grids. When the component is greater than 1, the grid reference must always
be a structural grid (GRID).

8. For linear steady-state heat transfer analysis, an SPC may be used to define a
temperature boundary condition. For thermal boundary conditions, the component should
be 0 or blank when the SPSYNTAX setting on the SYSSETTING I/O option is set to
CHECK(default) or STRICT. When SPSYNTAX is set to MIXED 1 is also accepted as the
component.

9. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on SPC entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry
in the model). “number” is the identification number of a referenced local entry in the part
“PartName”. See Parts and Instances in the User’s Guide for detailed information on the
use of fully qualified references.

10. This card is represented as a constraint load in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2027

Proprietary Information of Altair Engineering


SPC1

Bulk Data Entry

SPC1 – Single-Point Constraint, Alternate Form

Description

Defines sets of single-point constraints and thermal boundary conditions.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SPC 1 SID C G1 G2 G3 G4 G5 G6

G7 G8 G9 -etc.-

Alternate Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SPC 1 SID C G1 "thru" G2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SPC 1 3 2 7 3 10 9 6 5

THRU 8 33 71

SPC 1 2 2 87 “thru” 100

Field Contents

SID Identification number of single-point constraint set.

(Integer > 0)

2028 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


C Component number.

(Integer zero or blank for scalar points, or up to six unique digits (0 < digit <
6) may be placed in the field with no embedded blanks for grid points. The
components refer to the coordinate system referenced by the grid points.)

Gi Grid or scalar point identification numbers.

(Integer > 0)

Comments

1. The degree-of-freedom declared dependent on this entry may not be:

Included in another single-point constraint (SPC or SPC1).


Declared a dependent degree-of-freedom on any RBAR, RBE1, RBE2, or RROD entry.
Declared a dependent degree-of-freedom on an MPC set referenced in the same
subcase.
2. Note that enforced displacements are not available via this entry.

3. Any number of continuations may appear.

4. Multiple “thru” sequences can be used on a single card, and can span across continuation
lines.

5. SPC degrees-of-freedom may be redundantly specified as permanent constraints on the


GRID entry.

6. If the "thru" comment is used, G1 and G2 must exist, but the grid points between G1 and
G2 are not required to exist.

7. For static and dynamic analyses, when the SPSYNTAX setting on the SYSSETTING I/O
option is set to CHECK (default) or MIXED, it is allowed that when grid lists are provided
for a given component, that the grid references be either scalar points (SPOINT) or
structural grid points (GRID) when the component is 0, 1 or blank; interpreting all of these
as 0 for scalar points and as 1 for structural grids. When SPSYNTAX is set to STRICT, it
is required for grid/component pairs (G#/C#) that the component be 0 or blank when the
grid references are to scalar points (SPOINT), and that the component be > 1 when the
grid references are to structural grid points (GRID). When the component is greater than
1, the grid references must always be a structural grid (GRID).

8. For linear steady-state heat transfer analysis, SPC1 may be used to define temperature
boundary conditions; however, unless paired with an SPCD entry, the enforced
temperature is 0.0. For thermal boundary conditions, the component should be 0 or blank
when the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT. When SPSYNTAX is set to MIXED, 1 is also accepted as the component.

9. This card is represented as a constraint load in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2029

Proprietary Information of Altair Engineering


SPCADD

Bulk Data Entry

SPCADD – Single-Point Constraint Set Combination

Description

Defines a single-point constraint set as a union of single-point constraint sets defined via SPC
or SPC1 entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SPC ADD SID S1 S2 S3 S4 S5 S6 S7

S8 S9 -etc-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SPC ADD 101 3 2 9 1

Field Contents

SID Identification number for new single-point constraint set.

(Integer > 0)

Si Identification numbers of single-point constraint sets defined via SPC or SPC1


entries.

(Integer > 0 or <PartName.number>) See comment 5.

Comments

1. The Si field should not reference the identification number of a single-point constraint set
defined by another SPCADD entry.

2. The Si values must be unique.

2030 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. SPCADD entries take precedence over SPC or SPC1 entries. If both have the same set
ID, only the SPCADD entry is used.

4. If all Si are non-existent the solver will exit with an error termination.

5. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on SPCADD entries in the model. A fully qualified reference
(“PartName.number”) is similar to the format of a numeric reference. “PartName” is the
name of the part that contains the referenced local entry (part names are defined on the
BEGIN Bulk Data Entry in the model). “number” is the identification number of a
referenced local entry in the part “PartName”. See Parts and Instances in the User’s
Guide for detailed information on the use of fully qualified references.

6. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2031

Proprietary Information of Altair Engineering


SPCD

Bulk Data Entry

SPCD – Enforced Motion Value

Description

Defines an enforced displacement value for static analysis, an enforced displacement, velocity
or acceleration for dynamic analysis and a thermal boundary condition for heat transfer (or
transient heat transfer) analysis. It can also be used to define the EXCITEID field (Amplitude
“A”) of dynamic loads in RLOAD1, RLOAD2, TLOAD1 and TLOAD2 bulk data entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SPC D SID G C D G C D

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SPC D 100 32 436 -2.6 5 1 +2.9

Field Contents

SID Identification number of a static load set.

(Integer > 0)

G Grid or scalar point identification number.

(Integer > 0 or <PartName.number>) See comment 9.

C Component numbers in the global coordinate system.

(6 > Integer > 0; up to six unique such digits may be placed in the field with
no embedded blanks)

D Value of enforced motion for all grids and components designated by G and
C.

2032 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

(Real)

Comments

1. The degree-of-freedom (G and C) referenced on this entry must also be referenced on an


SPC or SPC1 bulk data entry and selected by the SPC subcase information command in
the same subcase.

2. For use in linear static and linear steady state heat transfer analyses, the load set
identification number must be selected by the LOAD subcase information command.

3. Values of D will override the values specified on an SPC bulk data entry if selected for use
in the same subcase.

4. For use in dynamic analysis, the load set identification number must be referenced by the
EXCITEID field of an RLOAD1, RLOAD2, TLOAD1, or TLOAD2 bulk data entry that has
enforced motion specified in its TYPE field.

5. The bulk data LOAD combination entry cannot combine an SPCD load.

6. This method of applying enforced displacements in static analysis is equivalent to that of


using an SPC entry. For static and dynamic analyses, when the SPSYNTAX setting on
the SYSSETTING I/O option is set to CHECK (default) or STRICT, it is required for grid/
component pairs (G#/C#) that the component be 0 or blank when the grid reference is a
scalar point (SPOINT), and that the component be > 1 when the grid reference is a
structural grid point (GRID). When SPSYNTAX is set to MIXED, it is allowed for grid/
component pairs (G#/C#) that the grid reference be either a scalar point (SPOINT) or a
structural grid point (GRID) when the component is 0, 1 or blank; interpreting all of these
as 0 for scalar points and as 1 for structural grids. When the component is greater than
1, the grid reference must always be a structural grid (GRID).

7. The SPCD units for rotational degrees of freedom is radians.

8. For use in transient heat transfer analysis, the load set identification number must be
referenced by the EXCITEID field of a TLOAD1 or TLOAD2 bulk data entry that has
enforced temperature specified in its TYPE field (TYPE = 1).

9. Supported local entries in specific parts can be referenced by the use of “fully qualified
references” on SPCD entries in the model. A fully qualified reference (“PartName.number”)
is similar to the format of a numeric reference. “PartName” is the name of the part that
contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry
in the model). “number” is the identification number of a referenced local entry in the part
“PartName”. See Parts and Instances in the User’s Guide for detailed information on the
use of fully qualified references.

10. This card is represented as a constraint load in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2033

Proprietary Information of Altair Engineering


SPOINT

Bulk Data Entry

SPOINT – Scalar-Point

Description

Defines scalar points.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SPOINT ID1 ID2 ID3 ID4 ID5 ID6 ID7 ID8

Alternate Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SPOINT ID1 "THRU" ID2

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SPOINT 3 18 1 4 16 2 6 THRU

8 47 99 THRU 128

Field Contents

ID# Scalar point identification number.

No default (0 < Integer)

Comments

1. A scalar point defined by its appearance on the connection entry for a scalar element
(see the CELAS, CMASS, and CDAMP entries) need not appear on an SPOINT entry.

2034 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


2. All scalar point identification numbers must be unique with respect to all other scalar and
grid points.

3. This entry is used primarily to define scalar points appearing in single-point or multipoint
constraint equations to which no scalar elements are connected.

4. If the alternate format is used, all scalar points ID1 through ID2 are defined. ID1 must be
less than ID2.

5. Alternate format can be combined with regular format, and it can span across
continuation lines.

6. This card is represented as a node in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2035

Proprietary Information of Altair Engineering


STACK

Bulk Data Entry

STACK – Stacking Information for Ply-Based Composite Definition

Description

Defines the stacking information and stacking sequence for ply-based composite definition.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

STAC K ID LAM PLYID1 PLYID2 PLYID3 PLYID4 PLYID5 PLYID6

PLYID7 …

Optional continuation lines for substack definitions:

SUB SID1 SNAME1 SPLYID1 SPLYID1 SPLYID1 SPLYID1 SPLYID1


1 2 3 4 5

SPLYID1 SPLYID1 ... ... ... ... ...


6 7

... ...

Optional continuation lines for interface definitions:

INT IPLYID11 IPLYID12

Example 1

Defines a stack consisting of 8 plies with the SMEAR option

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

STAC K 1 SMEAR 1010100 1020100 1010200 1020200 1010300 1020300

1010400 1020400

Example 2

2036 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Defines a stack with substack and interface information. They ply layout is shown below.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

STAC K 2

SUB 1 top 11 12 13 14

SUB 2 left 21 22 23 24

SUB 3 right 31 32 33 34

SUB 4 middle 41 42 43

INT 14 21

INT 14 31

INT 21 41

INT 43 31

Altair Engineering OptiStruct 13.0 Reference Guide 2037

Proprietary Information of Altair Engineering


Field Contents

ID Unique stack identification number.

No default (Integer > 0)

LAM Laminate option. If blank, all plies must be specified and all stiffness terms are
developed. The following options are supported:

SYM: Only plies on the bottom half of the composite lay-up need to be
specified. These plies are automatically symmetrically reflected to the
top half of the composite and given consecutive numbers from bottom
to top.

MEM: All plies must be specified, but only membrane terms are developed.

BEND: All plies must be specified, but only bending terms are developed.

SMEAR: All plies must be specified, stacking sequence is ignored, and MID1 is
set equal to MID2 on the derived equivalent PSHELL, while MID3, MID4,
TS/T, and 12I/T**3 are set to zero.

SMEARZ0: All plies must be specified, stacking sequence is ignored. While the
laminate is still considered to be made of homogenized (smeared)
material, the effect of offset Z0 is taken into account. Hence, if Z0 is
not equal to -0.5*Thick, the equivalent PSHELL will include MID1,
MID2 and MID4. MID3 is still set to zero, that is no transverse shear
deformation is considered.

SMCORE: All plies must be specified. The last ply specifies core properties and
the previous plies specify face sheet properties. The face sheet
properties are calculated without regard for stacking sequence; half of
the total face sheet thickness is then placed on top of the core, and
half is placed on the bottom, to produce a symmetric laminate.
Stiffness of the core is ignored while its density is included in inertia
calculations.

SYMEM: Only plies on the bottom half of the composite lay-up need to be
specified. These plies are automatically symmetrically reflected to the
top half of the composite and given consecutive numbers from bottom
to top. Only membrane terms are developed for the full laminate.

SYBEND: Only plies on the bottom half of the composite lay-up need to be
specified. These plies are automatically symmetrically reflected to the
top half of the composite and given consecutive numbers from bottom
to top. Only bending terms are developed for the full laminate.

SYSMEAR: Only plies on the bottom half of the composite lay-up need to be
specified. These plies are automatically symmetrically reflected to the

2038 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

top half of the composite and given consecutive numbers from bottom
to top. Stacking sequence is ignored, and MID1 is set equal to MID2
on the derived equivalent PSHELL, while MID3, MID4, TS/T and 12I/
T**3 are set to zero.

Default = blank, that is all plies must be specified (SYM, MEM, BEND, SMEAR,
SMCORE, SYMEM, SYBEND or SYSMEAR)

PLYID# PLY identification number.

No default (Integer > 0)

SUB SUB flag indicating that substack data is to follow.

SID# Substack identification number.

No default (Integer > 0)

SNAME Substack user-defined name.


#
No default (Character)

SPLYID PLY identification number.


#
No default (Integer > 0)

INT INT flag indicating that interface data is to follow.

IPLYID# PLY identification number.

No default (Integer > 0)

Comments

1. The STACK card is used in combination with the PCOMPP and PLY cards to create
composite properties through the ply-based definition.

2. Plies are listed from the bottom surface upward, in respect to the element’s normal
direction. In the image below, (a) shows the stacking sequence for a non-symmetrical
laminate, and (b) shows the stacking sequence for a symmetrical laminate.

Altair Engineering OptiStruct 13.0 Reference Guide 2039

Proprietary Information of Altair Engineering


3. For convenience, element output for the SMEAR and SMCORE options includes both
homogenized shell stresses and individual ply stresses. However, because stacking
sequence is ignored in these options, individual ply stresses will only be valid in cases of
pure membrane deformation.

4. Multiple instances of substack and interface continuations are allowed.

5. This card is represented as a laminate in HyperMesh.

2040 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SUPORT

Bulk Data Entry

SUPORT – Fictitious Support

Description

Defines determinate reaction degrees-of-freedom in a free body.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SUPORT ID1 C1 ID2 C2 ID3 C3 ID4 C4

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SUPORT 16 215

Field Contents

ID# Grid point identification number.

No default (Integer > 0)

C# Component numbers.

No default (Any unique combination, with no embedded blanks, of


the integers 1 through 6 for grid points; or 0 for scalar points)

Comments

1. The SUPORT entry specifies reference degrees-of-freedom for rigid body motion. It is not
intended to be used in place of a constraint (SPCi entry or PS on the GRID entry, for
example).

2. SUPORT and/or SUPORT1 entries are required to activate inertia relief unless PARAM,
INREL, -2 is specified, then SUPORT and/or SUPORT1 entries are not required.

3. Be careful not to spell SUPORT with two Ps.

Altair Engineering OptiStruct 13.0 Reference Guide 2041

Proprietary Information of Altair Engineering


4. Degrees-of-freedom specified on this entry cannot be defined as dependent degrees-of-
freedom in rigid body element or constrained in SPCi entry or PS on the GRID entry.

5. An alternative to SUPORT is the SUPORT1 entry, which is requested by the SUPORT1 I/O
Options and Subcase Information command.

6. This card is represented as a constraint load in HyperMesh.

2042 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SUPORT1

Bulk Data Entry

SUPORT1 – Fictitious Support, Alternate Form

Description

Defines determinate reaction degrees-of-freedom in a free body. The SUPORT1 bulk data
entry must be requested in the I/O Options or Subcase Information sections by the SUPORT1
data selection command.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SUPORT1 SID ID1 C1 ID2 C2 ID3 C3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SUPORT1 5 16 215

Field Contents

SID Set identification number. See comment 1.

No default (Integer > 0)

ID# Grid point identification number.

No default (Integer > 0)

C# Component numbers.

No default (Any unique combination, with no embedded blanks, of the


integers 1 through 6 for grid points; or 0 for scalar points)

Altair Engineering OptiStruct 13.0 Reference Guide 2043

Proprietary Information of Altair Engineering


Comments

1. SUPORT1 bulk data entries will not be used unless specifically selected in a subcase
definition by the SUPORT1 subcase information entry.

2. SUPORT bulk data entries are applied in all subcases.

3. The SUPORT1 bulk data entry must be requested in the I/O Options or Subcase
Information sections by the SUPORT1 data selection command. The degrees-of-freedom
specified on SUPORT1 will be combined with those on the SUPORT entry.

4. Be careful not to spell SUPORT with two Ps.

5. Degrees of freedom specified on this entry cannot be defined as dependent degrees-of-


freedom in rigid body element or constrained in SPCi entry or PS on the GRID entry.

6. This card is represented as a constraint load in HyperMesh.

2044 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SURF

Bulk Data Entry

SURF – Surface Definition

Description

Defines a face of a 2D or 3D element as part of a surface.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SURF SRFID ELFAC E

EID1 GA1 GB1 NORMAL1

EID2 GA2 GB2 NORMAL2

EID3 ... ... ...

... ...

Alternative Format (faceted surface)

In this format, surface is represented as collection of 3- or 4-noded polygons (facets). Each


facet is defined by 3 or 4 GRID IDs.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SURF SRFID FAC E

GA1 GB1 GC 1 GD1

GA2 GB2 GC 2 GD2

GA3 ... ... ...

... ...

Altair Engineering OptiStruct 13.0 Reference Guide 2045

Proprietary Information of Altair Engineering


Alternative Format (SET Format)

A surface may also be defined using a form of the SET bulk data entry. With this approach,
the surface is composed of all selected 2D elements and the external faces of all selected 3D
elements; that is, those faces that are not connected to any other 3D elements faces in the
model.

To use this format, the SURF keyword is used in place of the SET keyword and the TYPE must
be ELEM. All methods for defining a set of type ELEM are valid for this form of surface
definition. Refer to the SET bulk data entry.

Field Contents

SRFID Surface identification number.

No default (Integer > 0)

ELFACE Flag indicating that the surface is composed of an element face.

EID# 2D or 3D element identification number.

No default (Integer > 0)

GA# Identification number of a grid point at the corner of the desired face of a
3D element.

This field must be blank for 2D elements.

Default = blank (Integer > 0, blank)

GB# Optional grid point identification number. Used to identify face of 3D


elements. See comment 1.

Default = blank (Integer > 0, blank)

NORMAL Identifies the normal direction for a face of the surface. The normal of a
face of a surface may be different from the normal of the underlying
elements.

0: normal matches the normal of the underlying element. For 3D elements,


this is pointing into the element.

1: normal direction is opposite of the underlying element. For 3D elements,


this is pointing out of the element.

Default = 0 (0 or 1)

Comments

1. GB is used to identify faces of solid elements based on the following table:

2046 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


For HEXA elements: Identification number of a grid point at a corner of the desired
face that is diagonally opposite GA.

For PENTA elements: Quad faces: Identification number of a grid point at a corner of
the desired face that is diagonally opposite GA.

Tria faces: Leave blank.

For TETRA Identification number of a grid point at the corner opposite the
elements: desired face.

For PYRA elements: Quad faces: Leave blank

Tria faces: GA and GB must specify the grids on the edge of the
face that borders the quadrilateral face, and the
grids must be ordered so that they define an inward
normal using the right hand rule.

2. This card is represented as a contactsurface in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2047

Proprietary Information of Altair Engineering


SWLDPRM

Bulk Data Entry

SWLDPRM – Parameters for CWELD and CSEAM Connector Elements

Description

Defines values of parameters used during the CWELD and CSEAM connectivity search.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SWLDPR PARAM1 VAL1 PARAM2 VAL2 PARAM3 VAL3 PARAM4 VAL4


M

PARAM5 VAL5 -etc.-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SWLDPRM GSPROJ 15.0 PRTSW 1

Alternate Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SWLDPR PARAM1 VAL1 PARAM2 VAL2 C TYPE1 PARAM3 VAL3 PARAM4


M

VAL4 C TYPE2 PARAM5 VAL5 PARAM6 VAL6 PARAM7 VAL7

-etc.-

Example (Alternate Format)

2048 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

SWLDPRM GSPROJ 15.0 PRTSW 1 C WELD GSMOVE 2 NREDIA

3 PROJTO 0.03 C SEAM C NRAGLI 150.0 GSPROJ 20.0


L

SHOWAU 1
X

Field Contents

PARAM# Name of parameter.

VAL# Value of parameter

CTYPE Connector type keyword to control the element specific parameters.


Parameters following a keyword will only be applied to the element type
specified by the keyword.

Supported connector types: CWELD or CSEAM

While textual values are recommended for clarity, their integer equivalents will
also be read. The available parameters and their values are listed below (click
the parameter name for parameter descriptions).

Parameter Value

CHKRUN NO, 0, YES, or 1


Default = NO

CNRAGLI 90.0 < Real < 160.0 or -1.0


Default = 160.0

CNRAGLO 0.0 < Real < 90.0 or -1.0


Default = 20.0

GMCHK NO, 0, YES, 1, FULL, or 2


Default = NO

GSMOVE Integer > 0


Default = 0

Altair Engineering OptiStruct 13.0 Reference Guide 2049

Proprietary Information of Altair Engineering


Parameter Value

GSPROJ 0.0 < Real < 90.0 or -1.0


Default = 20.0

GSTOL Real > 0.0


Default = 0.0

NREDIA O < Integer < 4


Default = 0

PROJTOL 0.0 < Real < 0.5


Default = 0.05

PRTSW NO, 0, YES, or 1


Default = NO

SHOWAUX 0, 1, 2, 3
Default = 0

Comments

1. The SWLDPRM entry changes the default settings of parameters for the CWELD and
CSEAM connectivity entries. None of the parameters of this entry are required. The
default settings should be changed only for diagnostic and debug purposes. Only one
SWLDPRM entry is allowed in the bulk data section.

2. Connectivities are created for the CSEAM element and for the CWELD element with
PARTPAT, ELPAT, ELEMID and GRIDID formats. With the parameters on this entry, you
can debug and alter the search algorithm which creates these connector elements.

3. Before the presence of any keyword of the connector, that is CWELD and CSEAM, the
parameter set on the entry will be regarded as “global,” and it will be applied to all of the
connector elements unless it only serves a specific type of connector.

4. Any parameter following a connector keyword will only be applied to the element type
specified by the keyword until the presence of another keyword.

5. Blank fields are allowed in this entry. However, blank fields are not allowed between the
parameter name and the corresponding parameter value or between the connector
keyword and the parameter name followed. If the parameter name or the connector
keyword is located just before the continuation field, then the following content must be
placed in the first field after the continuation marker.

6. Further detailed information about the individual connector elements can be found on the
pertinent CWELD and CSEAM bulk data entries.

7. Some of the above parameters apply only to selected connector types. Such information
is provided within the detailed description of individual parameters.

2050 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SWLDPRM, CHKRUN

Parameter Values Description

CHKRUN NO, 0, YES, or 1 Stop or allow the run after the connectivities of all the
connector elements have been generated. This
Default = NO parameter must be global, meaning it should be placed
before the presence of the first connector keyword.

If NO or 0, the solver will run to completion, unless other


errors are present.

If YES or 1, the solver will stop after connectivity of all


connector elements has been checked.

Altair Engineering OptiStruct 13.0 Reference Guide 2051

Proprietary Information of Altair Engineering


SWLDPRM, CNRAGLI

Parameter Values Description

CNRAGLI 90.0 < Real < 180.0 For CSEAM element only. Minimum angle allowed
or -1.0 between the free edges (no other element shares
these edges) of shell elements EIDSA and EIDEA or
Default = 160.0 EIDSB and EIDEB. The CSEAM element will be rejected
if this minimum angle is violated. See the following
figure.

If α < CNRAGLI, this CSEAM element is rejected (for


clarity suppose that the bold lines are the only couple
of free edges, while the others are connected with
shell elements not shown in this figure).

If CNRAGLI is set to -1.0, the program will skip the


checking of CNRAGLI.

2052 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SWLDPRM, CNRAGLO

Parameter Values Description

CNRAGLO 0.0 < Real < 90.0 For CSEAM element only. Maximum angle allowed
or -1.0 between the normal vectors of EIDSA and EIDEA or
EIDSB and EIDEB. The CSEAM element will not be
Default = 20.0 generated if the angle between these two normal
vectors is greater than the value of CNRAGLO. This
prevents generating single CSEAM element across a very
curved shell configuration. See the following figure.

If α > CNRAGLO, this CSEAM element is rejected. The


same check is also applied to the angle between the
normal vectors of EIDSB and EIDEB.

If CNRAGLO is set to -1.0, the program will skip the


checking of CNRAGLO.

Altair Engineering OptiStruct 13.0 Reference Guide 2053

Proprietary Information of Altair Engineering


SWLDPRM, GMCHK

Parameter Values Description

GMCHK NO, 0, YES, 1, FULL, or A switch to perform geometry check for certain
2 types of connector elements (presently it only
applies to CSEAM).
Default = NO
If NO or 0, no geometry check.

If YES or 1, perform geometry checks for


connector elements.

If FULL or 2, perform geometry checks for


connector elements and output the shell element
ID(s) if an error is found.

If GMCHK=1 or 2, the program will check whether


the CSEAM element spans a cutout or a corner.
If the CSEAM element does, an error will be
issued.

If GMCHK=1 or 2 and GSPROJ > 0, the program


will check the angle between the normal vectors
of Shell A and Shell B. If the angle is larger than
the value defined by GSPROJ, an error will be
issued.

If GMCHK=1 or 2 and CNRAGLO > 0, the program


will check the angle between the normal vectors
of EIDSA and EIDEA or EIDSB and EIDEB. If the
angle is larger than the value defined by
CNRAGLO, an error will be issued.

If GMCHK=1 or 2 and CNRAGLI > 0, the program


will check the angle between the free edges of
shell elements EIDSA and EIDEA or EIDSB and
EIDEB. If the angle is smaller than the value
defined by CNRAGLI, an error will be issued.

2054 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SWLDPRM, GSMOVE

Parameter Values Description

GSMOVE Integer > 0 Maximum number of times GS for the CWELD (PARTPAT or
ELPAT format) or GS/GE for the CSEAM is moved in cases
Default = 0 when not all auxiliary points have projections onto the patch
of shells.

Altair Engineering OptiStruct 13.0 Reference Guide 2055

Proprietary Information of Altair Engineering


SWLDPRM, GSPROJ

Parameter Values Description

GSPROJ 0.0 < Real < 90.0 Maximum angle allowed between the normal vectors of
or -1.0 Shell A and Shell B. Shell A and Shell B are located on
the two different shell surfaces that need to be
Default = 20.0 connected by the connector element. The connector
element will not be generated if the angle between
these two normal vectors is greater than the value of
GSPROJ. This prevents the generation of connector
elements between shell components that depart from
being parallel to each other. See the following figure.

If α > GSPROJ, this connector element is rejected.

Meanwhile, for CSEAM, when locating possible


candidate shell elements to support the auxiliary points,
the program will also check the angle between the
normal vector of the candidate and the thickness
direction of the CSEAM element. If the angle is larger
than the value defined by GSPROJ, this candidate will
be ignored. If the ignored candidate is one of EIDSA,
EIDSB, EIDEA or EIDEB, a warning will be issued.

If GSPROJ is set to -1.0, the program will skip the


checking of GSPROJ.

2056 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SWLDPRM, GSTOL

Parameter Values Description

GSTOL Real > 0.0 Presently it only applies to CSEAM. Maximum distance
between GS-SA, GS-SB, GE-EA and GE-EB for CSEAM.
Default = 0.0 See the following figure.

If the distance is greater than GSTOL, then the


connector element will not be generated and an error will
be issued.

If GSTOL is set to 0.0, the program will skip the checking


of GSTOL.

Altair Engineering OptiStruct 13.0 Reference Guide 2057

Proprietary Information of Altair Engineering


SWLDPRM, NREDIA

Parameter Values Description

NREDIA 0 < Integer < 4 Maximum number of times the diameter (which is used in
locating auxiliary points) is reduced by half when not all
Default = 0 auxiliary points have projections onto the patch of shells.
This parameter is for CWELD (PARTPAT and ELPAT) only.

2058 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SWLDPRM, PROJTOL

Parameter Values Description

PROJTOL 0.0 < Real < 0.5 Tolerance to accept the projected points (from GS for
CWELD and from GS/GE for CSEAM) if the computed
Default = 0.05 coordinates of the projection point lies outside the shell
element but is located within PROJTOL×(dimension of
the shell element). PROJTOL is only activated when a
search without PROJTOL finds no candidate shell to
build connectivity for a connector element. This
prevents the search from picking the wrong shell
element in cases when PROJTOL is not needed.

Altair Engineering OptiStruct 13.0 Reference Guide 2059

Proprietary Information of Altair Engineering


SWLDPRM, PRTSW

Parameter Values Description

PRTSW NO, 0, YES, or 1 Print diagnostic output for connector elements.

Default = NO If NO or 0, diagnostic information is not output.

If YES or 1, diagnostic information is written to the .out


file.

2060 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


SWLDPRM, SHOWAUX

Parameter Values Description

SHOWAUX NO, 0, YES, or 1 Output fictitious grids representing auxiliary points


generated for CWELD and fictitious hexa corner points
Default = NO generated for CSEAM into a file which can be directly
imported into HyperMesh to visualize the connector
elements. For clarity of visualization, this file also
includes the eight-node CHEXA elements with corners
at respective auxiliary points for CWELD or at
respective fictitious hexa corner points for CSEAM.

For each CWELD element, this data will only be output


in cases where no error is issued before the definition
of auxiliary points. For the CSEAM element, this data
will only be output if all seam elements are built
successfully.

For CWELD, the root file name will be followed with


.weldaux.fem.

For CSEAM, the root file name will be followed with


.seamaux.fem. If SHOWAUX = YES, the
displacement/corner stress/grid point stress of the
fictitious hexa element will also be output into an H3D
file if requested.

If NO or 0, no data for the fictitious hexa will be


output.

If YES or 1, the fictitious grids and hexas will be


output (these are the final locations, including all the
adjustments due to connector element radius or
thickness).

Altair Engineering OptiStruct 13.0 Reference Guide 2061

Proprietary Information of Altair Engineering


TABDMP1

Bulk Data Entry

TABDMP1 – Modal Damping Table

Description

Defines modal damping as a tabular function of natural frequency.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABDMP TID TYPE


1

f1 g1 f2 g2 f3 g3 f4 g4

f5 g5 … … … … … …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABDMP 2
1

2.5 0.01057 2.6 0.1362 ENDT

Field Contents

TID Table identification number.

No default (Integer > 0)

TYPE Type of damping units.

Default = G (G, CRIT, or Q)

2062 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Natural frequency value in cycles per unit time.

No default (Real > 0.0)

Damping value.

No default (Real)

Comments

1. Modal damping tables must be selected in the Subcase Information section, using the
SDAMPING command. This form of damping is used only in the modal method of frequency
response analysis.

2. A METHOD statement must be present in the SUBCASE.

3. The frequency values, , must be specified in either ascending or descending order, but
not both.

4. Discontinuities may be specified between any two points except the two starting points
or two end points. For example, in Figure 1 discontinuities are allowed only between
points f2 through f7. Also, if g is evaluated at a discontinuity, then the average value of
g is used. In Figure 1, the value of g at f=f3 is g = (g3+g4)/2.

5. At least one continuation entry must be specified.

6. Any or entry may be ignored by placing 'SKIP' in either of the two fields used for
that entry.

7. The end of the table is indicated by the existence of 'ENDT' in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag 'ENDT'.

8. The TABDMP1 uses the algorithm:

where, f is input to the table and g is returned. The table look-up is performed
using linear interpolation within the table and linear extrapolation outside the table using
the two starting or end points. See Figure 1. No warning messages are issued if table
data is input incorrectly.

Altair Engineering OptiStruct 13.0 Reference Guide 2063

Proprietary Information of Altair Engineering


Figure 1. Example of Table Extrapolation and Discontinuity

9. The KDAMP option, on the PARAM card, may be used to switch between viscous and
structural damping. Viscous is the default and is used when PARAM, KDAMP is not
present.

KDAMP Result

1 (default) B matrix

-1 (1+ig)K matrix

10. If TYPE is 'G' or blank, the damping values are in units of equivalent viscous dampers
as follows:

If TYPE is 'CRIT', the damping values are in units of fraction of critical damping C/C0.
If TYPE is 'Q', the damping values are in the units of amplification or quality factor, Q.
These constants are related by the following equations:

2064 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


11. To achieve identical displacements in Modal frequency response or Modal transient
analyses when the SDAMPING bulk data entry is used instead of PARAM, G , the steps
described here can be followed:

The TYPE field in the TABDMP1 bulk data entry should be set to CRIT. This TABDMP1 bulk
data entry is referenced by the SDAMPING subcase information entry.

Set the damping value (field ) in the TABDMP1 bulk data entry equal to half of the
value of PARAM, G (set the constant value to C/C0).

Set PARAM, KDAMP,-1.

12. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2065

Proprietary Information of Altair Engineering


TABLED1

Bulk Data Entry

TABLED1 – Dynamic Load Tabular Function, Form 1

Description

Defines a tabular function for use in generating frequency-dependent and time-dependent


dynamic loads.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLED1 TID XAXIS YAXIS

x1 y1 x2 y2 x3 y3 x4 y4

x5 y5 … … … … … …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLED1 32

-3.0 6.9 2.0 5.6 3.0 5.6 ENDT

Field Contents

TID Table identification number.

No default (Integer > 0)

XAXIS Specifies a linear or logarithmic interpolation for the x-axis. See


comment 6.

Default = LINEAR (LINEAR or LOG)

2066 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

YAXIS Specifies a linear or logarithmic interpolation for the y-axis. See


comment 6.

Default = LINEAR (LINEAR or LOG)

x#, y# Tabular values.

No default (Real or ENDT)

Comments

1. xi must be in either ascending or descending order, but not both.


2. Discontinuities may be specified between any two points except the two starting points
or two end points. For example, in Figure 1 discontinuities are allowed only between
points x2 through x7 . Also, if y is evaluated at a discontinuity, the average value of y is
used. In Figure 1, the value of y at x = x3 is y = (y3+y4)/2 .

3. At least one continuation entry must be specified.

4. Any x, y pair may be ignored by placing 'SKIP' in either of the two fields used for that
entry.

5. The end of the table is indicated by the existence of 'ENDT' in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag 'ENDT'.

6. The TABLED1 uses the algorithm:

where, x is input to the table and y is returned. The table look-up is performed using
interpolation within the table and linear extrapolation outside the table using the two
starting or end points. See Figure 1. The algorithms used for interpolation or
extrapolation are:

Altair Engineering OptiStruct 13.0 Reference Guide 2067

Proprietary Information of Altair Engineering


where, xj and yj follow xi and yi.

No warning messages are issued if table data is input incorrectly.

Figure 1. Example of Table Extrapolation and Discontinuity

7. Linear extrapolation is not used for Fourier transform methods. The function is zero
outside the range of the table.

8. For frequency-dependent loads, x# is measured in cycles per unit time.

9. Tabular values on an axis if X-Axis or Y-Axis = LOG must be positive. A fatal message will
be issued if an axis has a tabular value < 0.

2068 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


10. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2069

Proprietary Information of Altair Engineering


TABLED2

Bulk Data Entry

TABLED2 – Dynamic Load Tabular Function, Form 2

Description

Defines a tabular function for use in generating frequency-dependent and time-dependent


dynamic loads. Also contains parametric data for use with the table.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLED2 TID X1

x1 y1 x2 y2 x3 y3 x4 y4

x5 y5 … … … … … …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLED2 15 -10.5

1.0 -4.5 2.0 -4.2 2.0 2.8 7.0 6.5

SKIP SKIP 9.0 6.5 ENDT

Field Contents

TID Table identification number.

No default (Integer > 0)

X1 Table parameter. See comment 6.

No default (Real)

2070 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

x#, y# Tabular values.

No default (Real)

Comments

1. xi must be in either ascending or descending order, but not both.


2. Discontinuities may be specified between any two points except the two starting points
or two end points. For example, in Figure 1 discontinuities are allowed only between
points x2 through x7 . Also, if y is evaluated at a discontinuity, the average value of y is
used. In Figure 1, the value of y at x = x3 is y = (y3+y4)/2.

3. At least one continuation entry must be specified.

4. Any x, y pair may be ignored by placing 'SKIP' in either of the two fields used for that
entry.

5. The end of the table is indicated by the existence of 'ENDT' in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag 'ENDT'.

6. The TABLED2 uses the algorithm:

where, x is input to the table and y is returned. The table look-up is performed using
interpolation within the table and linear extrapolation outside the table using the two
starting or end points. See Figure 1. No warning messages are issued if table data is
input incorrectly.

Altair Engineering OptiStruct 13.0 Reference Guide 2071

Proprietary Information of Altair Engineering


Figure 1. Example of Table Extrapolation and Discontinuity

7. Linear extrapolation is not used for Fourier transform methods. The function is zero
outside the range of the table.

8. For frequency-dependent loads, X1 and x# are measured in cycles per unit time.

9. This card is represented as a loadcollector in HyperMesh.

2072 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


TABLED3

Bulk Data Entry

TABLED3 – Dynamic Load Tabular Function, Form 3

Description

Defines a tabular function for use in generating frequency-dependent and time-dependent


dynamic loads. Also contains parametric data for use with the table.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLED3 TID X1 X2

x1 y1 x2 y2 x3 y3 x4 y4

x5 y5 … … … … … …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLED3 15 126.9 30.0

2.9 2.9 3.6 4.7 5.2 5.7 ENDT

Field Contents

TID Table identification number.

No default (Integer > 0)

X1, X2 Table parameters.

Altair Engineering OptiStruct 13.0 Reference Guide 2073

Proprietary Information of Altair Engineering


Field Contents

x#, y# Tabular values.

No default (Real)

Comments

1. xii must be in either ascending or descending order, but not both.


2. Discontinuities may be specified between any two points except the two starting points
or two end points. For example, in Figure 1 discontinuities are allowed only between
points x2 through x7 . Also, if y is evaluated at a discontinuity, the average value of y is
used. In Figure 1, the value of y at x = x3 is y = (y3+y4)/2.

3. At least one continuation entry must be specified.

4. Any x, y pair may be ignored by placing 'SKIP' in either of the two fields used for that
entry.

5. The end of the table is indicated by the existence of 'ENDT' in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag 'ENDT'.

6. The TABLED3 uses the algorithm:

where, x is input to the table and y is returned. The table look-up is performed using
interpolation within the table and linear extrapolation outside the table using the two
starting or end points. See Figure 1. No warning messages are issued if table data is
input incorrectly.

2074 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Figure 1. Example of Table Extrapolation and Discontinuity

7. Linear extrapolation is not used for Fourier transform methods. The function is zero
outside the range of the table.

8. For frequency-dependent loads, X1, X2, and x# are measured in cycles per unit time.

9. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2075

Proprietary Information of Altair Engineering


TABLED4

Bulk Data Entry

TABLED4 – Dynamic Load Tabular Function, Form 4

Description

Defines the coefficients of a power series for use in generating frequency-dependent and
time-dependent dynamic loads. Also contains parametric data for use with the table.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLED4 TID X1 X2 X3 X4

A0 A1 A2 A3 A4 A5 A6 A7

A8 … … … … … … …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLED4 28 0.0 1.0 0.0 100

2.91 -0.0329 6.51e-5 0.0 -3.4-7 ENDT

Field Contents

TID Table identification number.

No default (Integer > 0)

X# Table parameters.

2076 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

A# Coefficients.

No default (Real)

Comments

1. At least one continuation entry must be specified.

2. The end of the table is indicated by the existence of 'ENDT' in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag 'ENDT'.

3. TABLED4 uses the algorithm:

where, x is input to the table, y is returned and N is the number of pairs. Whenever x <
X3, use X3 for x; whenever x > X4, use X4 for x. There are N + 1 entries in the table.
There are no error returns from this table look-up procedure.

4. For frequency-dependent loads, x# is measured in cycles per unit time.

5. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2077

Proprietary Information of Altair Engineering


TABFAT

Bulk Data Entry

TABFAT - Fatigue Loading Time History Definition

Description

Defines y values of each point on the loading time history.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABFAT ID y1 y2 y3 y4 y5 y6 y7

y8 … …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABFAT 1 0.000 -0.601 0.968 0.515 -0.263 -0.090 -0.582

-0.592 -0.877 -0.726 0.297 -0.899 -0.899 -0.165

0.907 0.936 -0.308 -0.308 -0.689 0.592 0.609

-0.600 -0.492 -0.492 -0.224

2078 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

ID Unique identification number.

No default (Integer > 0)

y# Y value of each point on the loading time history curve.

No default (Real)

Comments

1. The TABFAT ID may be referenced by a FATLOAD definition.

2. This card is represented as a loadcollector in HyperMesh.

3. Prior to OptiStruct version 11.0, TABFAT was named TABLEFAT.

Altair Engineering OptiStruct 13.0 Reference Guide 2079

Proprietary Information of Altair Engineering


TABLEM1

Bulk Data Entry

TABLEM1 – Material Property Table, Form 1

Description

Defines a tabular function for use in generating temperature-dependent material properties.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLEM1 TID

x1 y1 x2 y2 x3 y3 -etc.- "ENDT"

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLEM1 32

-3.0 6.9 2.0 5.6 3.0 5.6 ENDT

Field Contents

TID Table identification number.

(Integer > 0)

xi, yi Tabular values.

(Real)

"ENDT" Flag indicating the end of the table.

2080 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. xi must be in either ascending or descending order, but not both.


2. Discontinuities may be specified between any two points except the two start points or
two end points. For example, in the figure below, discontinuities are allowed only
between points x2 through x7 . Also, if y is evaluated at a discontinuity, then the average
value of y is used. In the figure, the value of y at x = x3 is y = (y3 +y4)/2.

3. At least one continuation entry must be specified.

4. Any xi- yi pair may be ignored by placing 'SKIP' in either of the two fields.

5. The end of the table is indicated by the existence of "ENDT" in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag "ENDT".

6. The TABLEM1 uses the algorithm (see comment 7):

y= yT(x)
where, x is input to the table and y is returned. The table look-up is performed using
linear interpolation within the table and linear extrapolation outside the table using the
two start or end points (see figure). No warning messages are issued, if the table data is
input incorrectly.

Example of table extrapolation and discontinuity

7. In a nonlinear heat transfer analysis, TABLEM1 uses the following algorithm:

y = zyT(x)
Where. x is input to the table, y is returned, and z is supplied from the MAT4 entry.

8. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2081

Proprietary Information of Altair Engineering


TABLEM2

Bulk Data Entry

TABLEM2 – Material Property Table, Form 2

Description

Defines a tabular function for use in generating temperature-dependent material properties.


Also contains parametric data for use with the table.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLEM2 TID X1

x1 y1 x2 y2 x3 y3 -etc.-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLEM2 15 -10.5

1.0 -4.5 2.0 -4.5 2.0 2.8 7.0 6.5

SKIP SKIP 9.0 6.5 ENDT

Field Contents

TID Table identification number.

(Integer > 0)

X1 Table parameter.

(Real)

2082 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

xi, yi Tabular values.

(Real)

Comments

1. xi must be in either ascending or descending order, but not both.


2. Discontinuities may be specified between any two points except the two starting points
or two end points. For example, in the figure below, discontinuities are allowed only
between points x2 through x7 . Also, if y is evaluated at a discontinuity, then the average
value of y is used. In the figure, the value of y at x = x3 is y = (y3+y4)/2 .

3. At least one continuation entry must be specified.

4. Any xi-yi pair may be ignored by placing 'SKIP' in either of the two fields.

5. The end of the table is indicated by the existence of "ENDT" in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag "ENDT".

6. The TABLEM2 uses the algorithm:

y= zyT(x – X1)
where, x is input to the table, y is returned, and z is supplied from the MATi entry. The
table look-up is performed using linear interpolation within the table and linear
extrapolation outside the table using the two start or end points (see figure). No warning
messages are issued if table data is input incorrectly.

Example of table extrapolation and discontinuity

Altair Engineering OptiStruct 13.0 Reference Guide 2083

Proprietary Information of Altair Engineering


7. This card is represented as a loadcollector in HyperMesh.

2084 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


TABLEM3

Bulk Data Entry

TABLEM3 – Material Property Table, Form 3

Description

Defines a tabular function for use in generating temperature-dependent material properties.


Also contains parametric data for use with the table.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLEM3 TID X1 X2

x1 y1 x2 y2 x3 y3 -etc.-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLEM3 62 126.9 30.0

2.9 2.9 3.6 4.7 5.2 5.7 ENDT

Field Contents

TID Table identification number.

(Integer > 0)

X1, X2 Table parameters. See comment 6.

xi, yi Tabular values.

(Real)

Altair Engineering OptiStruct 13.0 Reference Guide 2085

Proprietary Information of Altair Engineering


Comments

1. Tabular values for xi must be specified in either ascending or descending order, but not
both.

2. Discontinuities may be specified between any two points except the two start points or
two end points. For example, in the figure below, discontinuities are allowed only
between points x2 through x7 . Also, if y is evaluated at a discontinuity, then the average
value of y is used. In the figure, the value of y at x = x3 is y = (y3+y4)/2 .

3. At least one continuation entry must be specified.

4. Any xi-yi pair may be ignored by placing 'SKIP' in either of the two fields.

5. The end of the table is indicated by the existence of "ENDT" in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag "ENDT".

6. TABLEM3 uses the algorithm:

where, x is input to the table, y is returned and z is supplied from the MATi entry. The
table look-up is performed using linear interpolation within the table and linear
extrapolation outside the table using the two starting or end points (see figure). No
warning messages are issued if table data is input incorrectly.

Example of table extrapolation and discontinuity

7. This card is represented as a loadcollector in HyperMesh.

2086 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


TABLEM4

Bulk Data Entry

TABLEM4 – Material Property Table, Form 4

Description

Defines coefficients of a power series for use in generating temperature-dependent material


properties. Also contains parametric data for use with the table.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLEM4 TID X1 X2 X3 X4

A0 A1 A2 A3 A4 A5 -etc.-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLEM4 28 0.0 1.0 0.0 100.

2.91 -0.0329 6.51-5 0.0 -3.4-7 ENDT

Field Contents

TID Table identification number.

(Integer > 0)

Xi Table parameters.

Ai Coefficients.

(Real)

Altair Engineering OptiStruct 13.0 Reference Guide 2087

Proprietary Information of Altair Engineering


Comments

1. At least one continuation entry must be specified.

2. The end of the table is indicated by the existence of "ENDT" in the field following the last
entry. An error is detected if any continuations follow the entry containing the end-of-
table flag "ENDT".

3. TABLEM4 uses the algorithm:

where, x is input to the table, y is returned, and z is supplied from the MATi entry.
Whenever x < X3 , use X3 for x; whenever x > X4 , use X4 for x. There are N + 1 entries in
the table. There are no error returns from this table look-up procedure.

4. This card is represented as a loadcollector in HyperMesh.

2088 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


TABLES1

Bulk Data Entry

TABLES1 – Material Property Tabular Function, Form 1

Description

Defines a tabular function for use as stress-strain curve in elasto-plastic material properties
MATS1, MATX33, MATX65, MATHF, as well as material curve in nonlinear material properties
MATX36, MATX42, and MATX70.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLES1 TID

x1 y1 x2 y2 x3 y3 x4 y4

x5 y5 … … … … … …

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLES1 32

-3.0 6.9 2.0 5.6 3.0 5.6 ENDT

Field Contents

TID Table identification number.

No default (Integer > 0)

x#, y# Tabular values.

No default (Real, or ENDT)

Comments

1. xi must be in either ascending or descending order, but not both.

Altair Engineering OptiStruct 13.0 Reference Guide 2089

Proprietary Information of Altair Engineering


2. Discontinuities between any two points except the two starting points or two end points.
For example, in Figure 1 discontinuities are allowed only between points x2 through x7 .
Also, if y is evaluated at a discontinuity, the average value of y is used. In Figure 1, the
value of y at x = x3 is y = (y3+y4)/2 .

3. At least one continuation entry must be specified.

4. Any x, y pair may be ignored by placing 'SKIP' in either of the two fields used for that
entry.

5. The end of the table is indicated by the existence of 'ENDT' in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag 'ENDT'.

6. The TABLES1 uses the algorithm:

where, x is input to the table and y is returned. The table look-up is performed using
interpolation within the table and linear extrapolation outside the table using the two
starting or end points. See Figure 1. The algorithms used for interpolation or
extrapolation is:

where, xj and yj follow xi and yi.

7. For TABLES1 referenced by elasto-plastic material property MATS1, additional


requirements apply. See the description of MATS1 for details.

2090 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Figure 1. Example of Table Extrapolation and Discontinuity

8. Linear extrapolation is not used for Fourier transform methods. The function is zero
outside the range of the table.

9. For frequency-dependent loads, x# is measured in cycles per unit time.

10. Some warning or error messages are issued if table data in input incorrectly. However,
since TABLES1 can serve different and distinct purposes, error checking is limited.

Altair Engineering OptiStruct 13.0 Reference Guide 2091

Proprietary Information of Altair Engineering


TABLEST

Bulk Data Entry

TABLEST – Material Property Temperature-Dependence Table

Description

Specifies the material property tables for elasto-plastic, temperature-dependent materials.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLEST TID

T1 TID1 T2 TID2 T3 -etc.-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABLEST 101

150.0 10 175.0 20 ENDT

Field Contents

TID Table identification number.

(Integer > 0)

Ti Temperature values.

(Real)

TIDi Table identification numbers of TABLES1 entries.

(Integer > 0)

2092 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. TIDi must be unique with respect to all TABLES1 and TABLEST table identification
numbers.

2. Temperature values must be listed in ascending order.

3. The end of the table is indicated by the existence of ENDT in either of the two fields
following the last entry. An error is detected if any continuations follow the entry
containing the end-of-table flag ENDT.

4. This table is referenced by MATS1 entries that define elasto-plastic (TYPE = "PLASTIC")
materials.

Altair Engineering OptiStruct 13.0 Reference Guide 2093

Proprietary Information of Altair Engineering


TABRND1

Bulk Data Entry

TABRND1 – Power Spectral Density Table

Description

Defines power spectral density as a tabular function of frequency for use in random analysis.
Referenced on the RANDPS entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABRND1 ID XAXIS YAXIS blank blank blank blank blank

f1 g1 f2 g2 f3 g3 f4 g4

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TABRND1 3

2.5 .01057 2.6 .01362 ENDT

etc.

Field Contents

ID Table identification number.

(Integer > 0)

XAXIS Specifies a linear or logarithmic interpolation for the x-axis. See comment
6.

Default = LINEAR (LINEAR or LOG)

2094 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

YAXIS Specifies a linear or logarithmic interpolation for the y-axis. See comment
6.

Default = LINEAR (LINEAR or LOG)

fi Frequency value in cycles per unit time.

(Real > 0.0)

gi Power Spectral Density.

(Real)

Comments

1. The fi must be in either ascending or descending order, but not both.

2. Jumps between two points ( ) are allowed, but not at the end points.

3. At least two entries must be present.

4. Any f-g entry may be ignored by placing the BCD string "SKIP" in either of the two field
used for that entry.

5. The end of the table is indicated by the existence of the BCD string "ENDT" in either of
the two fields following the last entry. An error is detected if any continuations follow
the entry containing the end-of-table flag "ENDT".

6. The TABRND1 mnemonic infers the use of the algorithm:

G = g T(F)

where, F is input to the table and G is returned. The table look-up gT(f) is performed
using linear extrapolation outside the table using the last two end points at the
appropriate table end. At jump points, the average gT(F) is used. There are no error
returns from this table look-up procedure.

Altair Engineering OptiStruct 13.0 Reference Guide 2095

Proprietary Information of Altair Engineering


TEMP

Bulk Data Entry

TEMP – Grid Point Temperature Field

Description

Defines temperature at grid points for determination of Thermal Loading and Stress recovery.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TEMP SID G T G T G T blank {N.C .}

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TEMP 3 94 316.2 49 219.8

Field Contents

SID LOAD set identification.

(Integer > 0)

G Grid point identification number.

(Integer > 0)

T Temperature.

(Real)

Comments

1. Temperature sets may be selected for use in a subcase by the TEMPERATURE(LOAD) or


TEMPERATURE(BOTH) subcase information entry.

2. From one to three grid point temperatures may be defined on a single entry.

2096 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. In versions of OptiStruct prior to 8.0, thermal loads were selected in the Subcase
Information section using the LOAD data selector. In version 8.0, the TEMPERATURE data
selector was added to perform this function. It is possible to revert to the old behavior
mode by setting the LOADTEMP option to SHAREID in the OptiStruct Configuration File.

4. This card is represented as a temperature load in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2097

Proprietary Information of Altair Engineering


TEMPD

Bulk Data Entry

TEMPD – Grid Point Temperature Field Default

Description

Defines a temperature value for all grid points of the structural model that have not been
given a temperature on a TEMP entry.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TEMPD SID T SID T SID T SID T

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TEMPD 1 216.3

Field Contents

SID LOAD set identification.

(Integer > 0)

T Default temperature value.

(Real)

Comments

1. Temperature sets may be selected for use in a subcase by the TEMPERATURE(LOAD) or


TEMPERATURE(BOTH) subcase information entry.

2. From one to four default temperatures may be defined on a single entry.

2098 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. In versions of OptiStruct prior to 8.0, thermal loads were selected in the Subcase
Information section using the LOAD data selector. In version 8.0, the TEMPERATURE data
selector was added to perform this function. It is possible to revert to the old behavior
mode by setting the LOADTEMP option to SHAREID in the OptiStruct Configuration File.

4. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2099

Proprietary Information of Altair Engineering


TIC

Bulk Data Entry

TIC – Transient and Explicit Analysis Initial Condition

Description

Defines values for the initial conditions of variables used in structural transient analysis and
explicit analysis. Both displacement and velocity values may be specified at independent
degrees-of-freedom.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TIC SID G C U0 V0

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TIC 100 10 3 0.1 0.5

Field Contents

SID Set identification number.

(Integer > 0)

G Grid or scalar point identification number. See comment 4.

(Integer > 0)

C Component numbers.

(Any one of the integers 1 through 6 for grid points, integer zero or blank for
scalar points)

U0 Initial displacement. Not applicable in geometric nonlinear analysis.

2100 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

(Real or blank)

V0 Initial velocity.

(Real or blank)

Comments

1. Transient analysis initial condition sets must be selected with the IC subcase information
command.

2. If no TIC set is selected in the Subcase Information section, all initial conditions are
assumed to be zero.

3. Initial conditions for coordinates not specified on TIC entries will be assumed to be zero.

4. In direct transient analysis, wherein the TIC bulk data entry is selected by an IC subcase
information command, G may reference only grid or scalar points.

5. Initial displacement definition is not applicable in explicit analysis. If U0 is defined, a fatal


error message will be issued.

6. The initial conditions for the independent degrees-of-freedom specified by this bulk data
entry are distinct from, and may be used in conjunction with, the initial conditions for the
enforced degrees-of-freedom specified by NLOAD1, TLOAD1 and/or TLOAD2 bulk data
entries.

7. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).

8. Each degree-of-freedom (grid/component pair: G#/C#) should define a unique value for
U0 and/or V0 within any TIC ID set, but U0 and V0 may be specified on separate TIC
cards. When multiple cards with the same degree-of-freedom are present, only non-zero
values for U0 and V0 are used by the solver. When two non-zero values are defined for
U0 or for V0 for the same degree-of-freedom, a fatal error message will be issued, even if
values match.

9. This card is represented as a constraint load in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2101

Proprietary Information of Altair Engineering


TICA

Bulk Data Entry

TICA – Explicit Analysis Initial Velocity Relative to an Axis

Description

Defines values for the initial velocity of a set of grids along and about an axis for explicit
analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TIC A SID GSID VT VR

GA/XA YA ZA GB/XB YB ZB

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TIC A 100 10 3.0 4.0

123 0.0 0.0 1.0

Field Contents

SID Set identification number.

(Integer > 0)

GSID Grid point set identification number.

Default = all grids in the model (blank or Integer > 0)

VT Initial velocity along the axis.

(Real)

2102 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

VR Initial velocity about the axis.

(Real)

GA/ XA, Axis origin. These fields define the origin of the axis. The point may be
YA, ZA defined by entering a grid ID in the GA field or by entering X, Y, and Z
coordinates in the XA, YA, and ZA fields; these coordinates will be in the
basic coordinate system.

Default is the origin of the basic system (Real in all three fields or Integer in
first field)

GB/ XB, Direction of vector for axis definition. These fields define a point. The
YB, ZB vector goes from the anchor point to this point. The point may be defined
by entering a grid ID in the GB field or by entering X, Y, and Z coordinates in
the XB, YB, and ZB fields; these coordinates will be in the basic coordinate
system.

No default (Real in all three fields or Integer in first field)

Comments

1. Explicit analysis initial condition sets must be selected with the Subcase Information
command IC = SID. It can only be selected in explicit subcases which are defined by an
ANALYSIS = NLGEOM subcase entry.

2. TICA is primarily used for simulating the uniform rotation of a structure about an axis by
defining VR and an axis. A helical (or spiral) shaped motion can also be achieved by
defining VR, VT and an axis.

3. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2103

Proprietary Information of Altair Engineering


TIE

Bulk Data Entry

TIE – Tied Definition

Description

Defines a tied contact.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TIE TID SSID MSID SRC HDIS ADJUST

DISC RET

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TIE 5 7 8 0.01

N25

Field Contents

TID Tied interface identification number. See comment 1.

(Integer > 0)

SSID Identification number of slave entity. See comments 3 and 10.

(Integer > 0)

MSID Identification number of master entity. See comments 4 and 11.

(Integer > 0)

2104 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

SRCHDIS Search distance criterion for creating contact condition. When specified,
only slave nodes that are within SRCHDIS distance from master surface will
have contact condition checked.

Default = All slave nodes checked (Real > 0 or blank)

ADJUST Adjustment of slave nodes onto the master surface at the start of a
simulation.

<NO, AUTO, Real > 0.0, or Integer > 0>

Default = NO.
NO – no adjustment.
AUTO – A real value equal to 5% of the average edge length on the master
surface is internally assigned as the depth criterion (see Comment 7).

Real > 0.0 – Value of the depth criterion which defines the zone in which a
search is conducted for slave nodes (for which contact elements have been
created). These slave nodes (with created contact elements) are then
adjusted onto the master surface. The assigned depth criterion is used to
define the searching zone in the pushout direction (see Comment 7).

Integer > 0 – Identification number of a SET entry with TYPE = “GRID”.


Only the nodes on the slave entity, which also belong to this SET will be
selected for adjustment.

DISCRET Discretization approach type for the construction of contact elements.


<N2S, S2S>
Default = N2S.
N2S – node-to-surface discretization
S2S – surface-to-surface discretization

Comments
(Nonlinear quasi-static analysis)
1. TIE contact needs to keep a unique ID from all CONTACT definitions.

2. The TIE contact is constructed by searching for each slave node for a respective facet of
the master surface, which contains the normal projection of the slave and is within
SRCHDIS distance from the slave node. If no master segment with normal projection is
found, then the nearest segment is picked if the direction from slave to master is within a
certain angle (30 degrees) relative to the normal to the master segment. Having found a
feasible master segment for the slave node, a tie element is created.

Altair Engineering OptiStruct 13.0 Reference Guide 2105

Proprietary Information of Altair Engineering


Figure 1: C reation of a TIE element

If the surface-to-surface (DISCRET=S2S) discretization approach is selected, the


CONTACT interface is constructed by searching, for each facet of the slave surface,
respective facets of the master surface which contain the normal projection of sample
points on the slave facet and is within SRCHDIS distance from the sample points. For a
slave node, a contact element is created with the surrounding slave facets and the
master facets found by projection of the sample points on the slave facets (Figure 2).

Figure 2: C reation of a contact element (surface-to-surface discretization)

3. The slave entity (SSID) always consists of grid nodes. It may be specified as:

a set of grid nodes defined using SET card.


a surface defined using SURF card (the slave nodes are picked from the respective
nodes of the SURF faces).
a set of elements (shells or solids) defined using SET card. Slave nodes are picked
from the respective nodes of the elements in the set. For 3D solids, only nodes on the
surface of the solid body are selected; internal nodes are not considered.
DISCRET = N2S is recommended if the slave entity is a set of grids (nodes) or a set of
solid elements.

4. The master entity (MSID) may be defined as:

a surface defined using SURF card.


a set of elements (shells or solids) defined using SET card. For sets of 3D solids,

2106 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


element faces on the surface are automatically found and selected as master surface.

5. TIE element is created of a same structure as FREEZE CONTACT element. TIE element
enforces zero relative motion on the contact surface – the contact gap opening remains
fixed at the original value and the sliding distance is forced to be zero. Also, rotations at
the slave node are matched to the rotations of the master patch.

6. Presently one TIE element is created for each slave node. This assures reasonably
efficient numerical computations without creating an excessive number of tie elements.
However, this may require special handling in some cases, such as when a master surface
wraps around the slave set. In such cases, switching the role of slave and master may
be recommended. Alternatively, multiple TIE elements can be created in order to cover all
possible directions of relative motion (a simplified illustration is shown in Figure 3).

Figure 3: Special case - Master surface wraps around a slave node set.

7. The adjustment of slave nodes doesn’t create any strain in the model. If DISCRET=N2S is
selected, it is treated as a change in the initial model geometry. If DISCRET=S2S is
selected, it is treated as a change in the initial contact opening/penetration.

If a node on the slave entity lies outside the projection zone of the master surface, it will
always be skipped during adjustment since no contact element has been constructed for
it.

If different contact interfaces involve the same nodes, nodal adjustment definitions are
processed sequentially in the order of identification numbers of the contact interfaces.
Care must be taken to avoid conflicts between the nodal adjustments; otherwise, contact
element errors or lack of compliance may occur.

a) The ADJUST field must be set to “NO” for self-contact.


b) If a real value (the searching depth criterion for adjustment) is input for the ADJUST
field, a searching zone for adjustment is defined. The slave nodes in this searching
zone, for which contact elements have been created, will be adjusted. If ADJUST is
larger than or equal to SRCHDIS, all the slave nodes, for which contact elements have
been created, will be adjusted.

Altair Engineering OptiStruct 13.0 Reference Guide 2107

Proprietary Information of Altair Engineering


Figure 4: An illustration depicting how ADJUST works.

Depth Criterion

The depth criterion (A non-negative real value for ADJUST) is used to define the searching
zone for adjustment as shown in Figure 4. This searching zone is created in the pushout
direction up to a distance equal to the value of the ADJUST field. The slave nodes within
the searching zone (with defined contact elements) are then considered for adjustment
based on the rules specified within this comment (Comment 7).

c) If the ADJUST field is set to an integer value (the identification number of a grid SET
entry), the nodes shared by the slave entity and the grid SET will be checked for
contact creation, that is SRCHDIS will be ignored for these nodes, and then adjusted if a
projection is found. The nodes belonging to the grid SET but not to the slave entity will
be simply ignored.

8. This card is represented as a group in HyperMesh.

(Geometric nonlinear analysis (ANALYSIS = NLGEOM subcases))

9. TIE is implemented as a Tied Contact in geometric nonlinear subcases. A geometric


nonlinear subcase is one that has an ANALYSIS = NLGEOM entry in the subcase
definition.

10. The slave entity (SSID) always consists of grid nodes. It may be specified as:

2108 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


a set of grid nodes defined using SET card.

a surface defined using SURF card (the slave nodes are picked from the respective
nodes of the SURF faces).
a set of elements (shells or solids) defined using SET card. Slave nodes are picked
from the respective nodes of the elements in the set. For 3D solids, only nodes on the
surface of the solid body are selected; internal nodes are not considered.
11. The master entity (MSID) may be defined as:

a surface defined using SURF card.


a set of elements (shells or solids) defined using SET card.
12. This card is represented as a group in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2109

Proprietary Information of Altair Engineering


TLOAD1

Bulk Data Entry

TLOAD1 – Transient Response Dynamic Excitation, Form 1

Description

Defines a time-dependent dynamic load or enforced motion of the form:

for use in transient response analysis.

Where,

f(t) is the time-dependent dynamic load or enforced motion.


A defines the amplitude of the dynamic excitation and is referenced by the EXCITEID field.
(F)t is a user-defined function that defines the time-variant nature of f(t). It is specified by
referencing a predefined TABLEDi entry in the TID field.
is the time delay defined in the DELAY field.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TLOAD1 SID EXC ITEID DELAY TYPE TID

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TLOAD1 5 7 LOAD 13

Field Contents

SID Set identification number.

(Integer > 0)

2110 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

EXCITEID Identification number of the DAREA, SPCD, FORCEx, MOMENTx,


PLOADx, RFORCE, QVOL, QBDY1 or GRAV entry set that defines {A}.
See comments 2 and 3.

(Integer > 0)

DELAY Defines time delay . If it is a non-zero integer, it represents the


identification number of DELAY bulk data entry that defines . If it is
real, then it directly defines the value of that will be used for all
degrees-of-freedom that are excited by this dynamic load entry. See
comment 7.

(Integer > 0, real or blank)

TYPE Defines the type of the dynamic excitation. See comments 2 and 3.

(Integer, character or blank; Default = 0)

TID Identification number of TABLEDi entry that gives F(t).

(Integer > 0)

Comments

1. Dynamic excitation sets must be selected with the subcase information command
DLOAD=SID.

2. The type of dynamic excitation is specified by TYPE (field 5) based on the following table:

TYPE
TYPE of Dynamic Excitation
Integer Character

0 L, LO, LOA, or Applied load (force or moment)


LOAD
(Default)

1 D, DI, DIS, or Enforced displacement or temperature; EXCITEID references


DISP SPC/SPCD data.

2 V, VE, VEL, or Enforced velocity; EXCITEID references SPC/SPCD data.


VELO

3 A, AC, ACC, Enforced acceleration; EXCITEID references SPC/SPCD


or ACCE data.

Altair Engineering OptiStruct 13.0 Reference Guide 2111

Proprietary Information of Altair Engineering


3. TYPE (field 5) also determines the manner in which EXCITEID (field 3) is used by the
program as described below.

Excitation specified by TYPE is applied load. The EXCITEID must reference DAREA,
FORCEx, MOMENTx, PLOAD, RFORCE, GRAV, QVOL or QBDY1 entries.

Excitation specified by TYPE is enforced motion. The EXCITEID must reference SPC/SPCD
entries.

TYPE = 1 must be specified if the EXCITEID field references SPCD data used in transient
heat transfer analysis to define time-dependent thermal boundary conditions.

4. TLOAD1 loads may be combined with TLOAD2 loads only by specification on a DLOAD
entry. That is, the SID on a TLOAD1 entry may not be the same as that on a TLOAD2
entry.

5. SID must be unique for all TLOAD1, TLOAD2, RLOAD1, and RLOAD2 entries.

6. If TLOAD1 entries are selected for Fourier analysis, then the time-dependent loads on the
TLOAD1 entries are transformed to the frequency domain. Then the analysis is performed
as a frequency response analysis, but the solution and the output are converted to and
printed in the time domain.

7. If DELAY is blank or zero, will be zero.

8. When EXCITEID refers to an SPCD entry, the modal space will be augmented with
displacement vector(s) from linear static analysis with unit prescribed displacement at
each of the SPCD degrees-of-freedom. EXCITEID cannot reference the LOAD and
LOADADD bulk data entries.

9. This card is represented as a loadcollector in HyperMesh.

2112 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


TLOAD2

Bulk Data Entry

TLOAD2 – Transient Response Dynamic Excitation, Form 2

Description

Defines a time-dependent dynamic excitation or enforced motion of the form:

for use in a transient response analysis, where .

Where,

is the time-dependent dynamic load or enforced motion.

A defines the amplitude of the dynamic excitation and is referenced by the EXCITEID field.
is the time delay defined in the DELAY field.

T1 and T2 are time constants defined in the T1 and T2 fields.

B, C, and are the growth coefficient, exponential coefficient, frequency and phase angle
respectively and are defined in the corresponding B, C, F and P fields.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TLOAD2 SID EXC ITEID DELAY TYPE T1 T2 F P

C B

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TLOAD2 4 10 2.1 4.7 12.0

Altair Engineering OptiStruct 13.0 Reference Guide 2113

Proprietary Information of Altair Engineering


2.0

Field Contents

SID Set identification number.

(Integer > 0)

EXCITEID Identification number of the DAREA, SPCD, FORCEx, MOMENTx,


PLOADx, RFORCE, QVOL, QBDY1 or GRAV entry set that defines {A}.
See comments 2 and 3.

(Integer > 0)

DELAY Defines time delay . If it is a non-zero integer, it represents the


identification number of DELAY bulk data entry that defines . If it is
real, then it directly defines the value of that will be used for all
degrees-of-freedom that are excited by this dynamic load entry. See
comment 4.

(Integer > 0, real or blank)

TYPE Defines the type of the dynamic excitation. See comments 2 and 3.

(Integer, character or blank; Default = 0)

T1 Time constant.

(Real > 0.0)

T2 Time constant.

(Real; T2>T1)

F Frequency in cycles per unit time.

(Real > 0.0; Default = 0.0)

P Phase angle in degrees.

(Real; Default = 0.0)

C Exponential coefficient.

2114 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

(Real; Default = 0.0)

B Growth coefficient.

(Real; Default = 0.0)

Comments

1. Dynamic excitation sets must be selected with the subcase information command with
DLOAD=SID.

2. The type of dynamic excitation is specified by TYPE (field 5) based on the following
table:

TYPE
TYPE of Dynamic Excitation
Integer Character

0 L, LO, LOA, Applied load (force or moment)


or LOAD
(Default)

1 D, DI, DIS, Enforced displacement or temperature; EXCITEID references


or DISP SPC/SPCD data.

2 V, VE, VEL, Enforced velocity; EXCITEID references SPC/SPCD data.


or VELO

3 A, AC, ACC, Enforced acceleration; EXCITEID references SPC/SPCD data.


or ACCE

3. TYPE (field 5) also determines the manner in which EXCITEID (field 3) is used by the
program as described below.

If the type of dynamic excitation specified by TYPE is applied load, then EXCITEID must
reference DAREA, FORCEx, MOMENTx, PLOAD, RFORCE, GRAV, QVOL or QBDY1 entries.

If the type of dynamic excitation specified by TYPE is enforced motion, then EXCITEID
must reference SPC/SPCD entries.

TYPE = 1 must be specified if the EXCITEID field references SPCD data used in transient
heat transfer analysis to define time-dependent thermal boundary conditions

4. If DELAY is blank or zero, will be zero.

5. TLOAD1 loads may be combined with TLOAD2 loads only by specification on a DLOAD
entry. That is, the SID on a TLOAD1 entry may not be the same as that on a TLOAD2
entry.

Altair Engineering OptiStruct 13.0 Reference Guide 2115

Proprietary Information of Altair Engineering


6. SID must be unique for all TLOAD1, TLOAD2, RLOAD1, and RLOAD2 entries.

7. TLOAD2 entries cannot be used with Fourier analysis.

8. The continuation entry is optional.

9. When EXCITEID refers to an SPCD entry, the modal space will be augmented with
displacement vector(s) from linear static analysis with unit prescribed displacement at
each of the SPCD degrees-of-freedom. EXCITEID cannot reference the LOAD and
LOADADD bulk data entries.

10. This card is represented as a loadcollector in HyperMesh.

2116 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


TSTEP

Bulk Data Entry

TSTEP – Transient Time Step

Description

Defines time step intervals at which a solution will be generated and output in transient
analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TSTEP SID N1 DT1 N01 W3,1 W4,1

N2 DT2 N02 W3,2 W4,2

-etc.-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TSTEP 2 10 .001 5

9 0.01 1

Field Contents

SID Set identification number.

No default (Integer > 0)

N# Number of time steps of value DT#.

No default (Integer > 1)

Altair Engineering OptiStruct 13.0 Reference Guide 2117

Proprietary Information of Altair Engineering


Field Contents

DT# Time increment.

No default (Real > 0.0)

N0# Skip factor for output. Every N0i-th step will be saved for output.

Default = 1 (Integer > 0)

W3,# The frequency of interest in radians per unit time; used for the conversion of
overall structural damping into equivalent viscous damping. See comment 3.

Default = blank (Real > 0.0, or blank)

W4,# The frequency of interest in radians per unit time; used for the conversion of
element structural damping into equivalent viscous damping. See comment 3.

Default = blank (Real > 0.0, or blank)

Comments

1. TSTEP entries must be selected with the Subcase Iinformation command TSTEP = SID.

2. Note that the entry permits changes in the size of the time step during the course of the
solution. Thus, in the example shown, there are 10 time steps of value .001, followed by
9 time steps of value .01. Also, in the case of this example, you have requested that the
output be recorded for t = 0.0, .005, .01, .02, .03, and so on.

3. W3 and W4 define frequencies used in transient analyses to convert structural damping to


equivalent viscous damping. See the Reference Guide entries for PARAM,W3 and
PARAM,W4 for more details.

4. Different values for W3 and W4 may be set for each set of time increments. If any of the
fields are left blank then the value is taken from the PARAM, W3 or PARAM, W4 definition.

5. This card is represented as a loadcollector in HyperMesh.

2118 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


TSTEPNL

Bulk Data Entry

TSTEPNL – Parameters for Geometric Nonlinear Implicit Dynamic Analysis Control

Description

Defines parameters for geometric nonlinear implicit dynamic analysis strategy.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TSTEPNL ID NDT DT KSTEP C ONV

EPSU EPSP EPSW MAXLS LSTOL

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TSTEPNL 99 0.01

Field Contents

ID Each TSTEPNL bulk data card must have a unique ID.

No default (Integer > 0)

NDT Number of implicit load sub-increments.

No default (Integer > 0)

DT Initial time step.

No default (Real > 0)

KSTEP Number of iterations before stiffness update. See comment 3.

Altair Engineering OptiStruct 13.0 Reference Guide 2119

Proprietary Information of Altair Engineering


Field Contents

Default = 6 for BCS solver


Default = 3 for PCG solver

(Integer > 0)

CONV Flags to select implicit convergence criteria.

Default = UPW

(Any combination of U, P and W)

EPSU Error tolerance for displacement (U) criterion.

Default = 1.0E-2

(Real > 0.0)

EPSP Error tolerance for load (P) criterion.

Default = 1.0E-2

(Real > 0.0)

EPSW Error tolerance for work (W) criterion.

Default = 1.0E-3

(Real > 0.0)

MAXLS Maximum number of line searches allowed for each iteration.

Default = 20 (Integer > 0)

LSTOL Line search tolerance.

Default = 1.0E-3 (Real > 0.0)

Comments

1. The TSTEPNL bulk data entry is selected by the Subcase Information command TSTEPNL
= option. Each subcase for which nonlinear implicit dynamic analysis is desired requires a
TSTEPNL command.

2. Additional control for geometric nonlinear implicit dynamic solution schemes (ANALYSIS =
IMPDYN) can be defined using TSTEPNX bulk data entry. Defaults will be used if TSTEPNX
is not present.

3. The solution method for geometric nonlinear implicit dynamic analysis (ANALYSIS =
IMPDYN) is modified or Quasi-Newton. The frequency of stiffness matrix updates is
controlled by KSTEP. For highly nonlinear problems, it is recommended to reduce KSTEP

2120 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


for better performance. KSTEP = 1 means full Newton. The initial implicit time step is DT.
All subsequent time steps will be determined automatically. Termination time, TTERM, is
defined by a TTERM subcase entry or computed from TTERM = NDT*DT. TTERM takes
precedence.

4. The time integration scheme for implicit transient is defined on TSTEPNX. The default
method is α-HHT.

5. For more information about geometric nonlinear analysis, refer to the Geometric Nonlinear
Analysis section.

6. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2121

Proprietary Information of Altair Engineering


TSTEPNX

Bulk Data Entry

TSTEPNX – Optional Parameters for Geometric Nonlinear Implicit Dynamic Analysis Control

Description

Defines additional parameters for geometric nonlinear implicit dynamic analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TSTEPNX ID TA0 DTA DTTH NPRINT RFILE

SOLV TSC TRL DTMIN DTMAX LSMETH RREFIF NC YC LE FIXTID/


TOUT

DYNA ALFA BETA GAMA SMDISP

ITW DTSC I LDTN DTSC D LARC

Example 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TSTEPNL 99 0.01

Example 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TSTEPNL 99 0.01

TSTEPNX 99 0.1

NEWT ARC 1.e-4 0.1

2122 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Example 3

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

TSTEPNL 99 0.01 3 PW

0.01 0.01

TSTEPNX 99 0.1

NEWT ARC 1.e-4 0.1

NEWM 0.25 0.5

Field Contents

ID Identification number of an associated TSTEPNL entry.

No default (Integer > 0)

TA0 Start time for writing animation files.

Default = 0.0 (Real > 0)

DTA Output time step for animation files. If zero, no output (See comment 3).

Default = DT (Real > 0)

DTTH Output time step for time history files. If zero, no output (See comment
3).

Default = 0.1*DT (Real > 0)

NPRINT Print every NPRINT iterations. If negative, to .out and standard output;
if positive, only to .out file.

Default = -1 (Integer)

RFILE Cycle frequency to write restart file for nonlinear iteration.

Altair Engineering OptiStruct 13.0 Reference Guide 2123

Proprietary Information of Altair Engineering


Field Contents

Default = 5000 (Integer > 0)

SOLV Geometric nonlinear implicit solution method.

NEWT – Modified Newton.

BFGS – BFGS quasi-Newton method.

Default = NEWT (Character = NEWT, or BFGS)

TSCTRL Time step control.

ARC – Arc-length is used to accelerate and control the convergence. The


time step is determined by displacement norm control (arc-length).

SIMP – Simple time step control.

NONE – No time step control. A warning will be issued. In the case of


divergence, the time step will be repeated with half the step size. The
run will be terminated according to DTMIN and NCYCLE.

Default = ARC (Character)

DTMIN Minimum geometric nonlinear implicit time step. If DTMIN is reached,


simulation will be terminated (See comment 3).

Default = 1e-5*DT (Real > 0)

DTMAX Maximum geometric nonlinear implicit time step from which time step is set
constant (See comment 3).

Default = 3*DT (Real > 0)

LSMETH Line search method.

Default = ENERGY (Character = NONE, FORCE, ENERGY, or AUTO)

RREFIF Special residual force computation with contact interfaces present.

Default = no special treatment (Integer = 0, …, 5)

0 – Aggressive (modified entirely by the out-of-balance value).


1 – Average (modified each time with 200% maximum).
2 – Light (modified each time with 20% maximum).
3 – No change.
4 – No change; except for the first contact.

2124 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

5 – Modified automatically (for imposed displacement only).


NCYCLE Maximum number of time steps. If reached, solution will be terminated.
NCYCLE = 0 means no limit.

Default = no limit (Integer > 0)

FIXTID Identification number of a TABLEDi entry. The x values of the table define
fixed time points that the automatic time step control will adhere to.

(Integer > 0)

TOUT The method to determine the fixed time point.

AUTO – Fully automatic time step control.

NLOAD - The time points in all TABLEDi that are referenced by NLOAD1 in
one subcase.

Default = AUTO (AUTO or NLOAD)

DYNA Implicit transient solution methods.

HHT – α-HHT method.

NEWM – General Newmark method.

Default = HHT (Character = HHT or NEWM)

ALFA Parameter in α-HHT Method (DYNA = HHT).

Default = -0.05 (Real, -1/3 < ALFA < 0.0)

BETA Parameter in general Newmark method (DYNA = NEWM).

Default = 0.25 (Real, -2 * BETA < GAMA < 0.5)

GAMA Parameter in general Newmark method (DYNA = NEWM).

Default = 0.5 (Real, -2 * BETA < GAMA < 0.5)

SMDISP Perform small displacement and rotation analysis instead of geometric


nonlinear analysis. PARAM, SMDISP, YES overwrites this definition.

OFF – Geometric nonlinear analysis.

Altair Engineering OptiStruct 13.0 Reference Guide 2125

Proprietary Information of Altair Engineering


Field Contents

ON – Small displacements and small rotations analysis.

Default = OFF (Character = ON, OFF)

ITW If the solution of a time step converges within ITW iterations, the next
time step will be increased by a factor controlled by DTSCI.

Default = 6 for TSCTRL = ARC


Default = 2 for TSCTRL = SIMP

(Integer > 0)

DTSCI Maximum scale factor for increasing the time step (TSCTRL = ARC). Scale
factor for TSCTRL = SIMP.

Default = 1.1 (Real > 0)

LDTN Maximum number of iterations before resetting and decreasing the time
step by a factor of DTSCD.

Default = 20 for TSCTRL = ARC


Default = 15 for TSCTRL = SIMP

(Integer > 0)

DTSCD Scale factor for decreasing the time step (TSCTRL = ARC, SIMP).

Default = 0.67 (Real > 0)

LARC Input arc-length for TSCTRL = ARC.

Default = automatic computation (Real)

Comments

1. The TSTEPNX bulk data entry is selected by the Subcase Information command TSTEP =
option. There must also be a TSTEPNL bulk data entry with the same ID. It is only used
in geometric nonlinear implicit dynamic analysis (ANALYSIS = IMPDYN); it is ignored in
other analyses.

2. The solution method for geometric nonlinear implicit analysis is selected by SOLV. The
frequency of stiffness matrix updates is controlled by TSTEPNL, KSTEP. For highly
nonlinear problems, it is recommended to reduce KSTEP for better performance. KSTEP =
1 means full Newton.

3. The initial time step DTINI = DT is defined by TSTEPNL.

2126 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


4. For more information about geometric nonlinear analysis, refer to the Geometric Nonlinear
Analysis section.

5. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2127

Proprietary Information of Altair Engineering


UNBALNC

Bulk Data Entry

UNBALNC – Unbalanced Load (Rotor Dynamics)

Description

This entry defines the unbalanced rotating load during a rotor dynamic analysis in Frequency
Response solution sequences. The unbalanced load is specified in a cylindrical system where
the rotor rotation axis is the Z-axis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

UNBALNC SID MASS GRID X1 X2 X3

ROFFSET THETA ZOFFSET FON FOFF

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

UNBALNC 200 1.2 3103 1.0 0.0 0.0

0.3 45.0 0.1 2 110

Argument Options Description

SID <Integer > 0> setid Set identification number.


No default

MASS <Integer > 0/Real> Defines the magnitude of unbalanced mass (see
comment 4).
(No default)

2128 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

GRID <Integer> Grid Point identification number of node at which the


unbalanced load is applied.
No default

X1, X2, X3 <Real> Components of a vector that are used to define a


cylindrical coordinate system centered at “GRID”. The
No default vector components are defined from “GRID” in the
displacement coordinate system of the grid point at
“GRID” (see comment 6).

ROFFSET <Integer > 0/Real> <Integer > 0> If an integer value (must be greater
than 0) is input, it references the
Default = 1.0 identification number of a TABLEDi
entry that specifies the offset values
as a function of frequency (see
comment 4).

<Real> This field defines the distance by


which the unbalanced mass is offset in
the X-Y plane perpendicular to the Z
direction (spin axis, Figure 1).

If a real number is input, the offset


value is considered constant.

THETA <Real> Angular position (in degrees) of the unbalanced mass in


the cylindrical coordinate system defined by X1, X2, and
Default = 0.0 X3.

ZOFFSET <Integer > 0/Real> <Integer > 0> If an integer value (must be greater than
0) is input, it references the identification
Default = 0.0 number of a TABLEDi entry that specifies
the offset values as a function of
frequency (see comment 4).

<Real> This field defines the distance by which


the unbalanced mass is offset in the Z

Altair Engineering OptiStruct 13.0 Reference Guide 2129

Proprietary Information of Altair Engineering


Argument Options Description

direction (spin axis, Figure 1).

If a real number is input, the offset value


is considered constant.

F ON <Real > 0> This field defines the starting frequency at which the
unbalanced load is applied (see comment 5).
Default = 0.0

F OFF <Real > 0> This field defines the stopping (final) frequency at which
the unbalanced load is applied (see comment 5).
Default = 999999.0

Comments

1. Currently, models containing multiple UNBALNC bulk data entries with the same set
identification number (SID) are not supported. Each UNBALNC bulk data entry must have a
unique SID.

2. For frequency response analysis, the UNBALNC bulk data entry is referenced by a DLOAD
Subcase Information entry.

3. An unbalanced load on the rotating system is generated as a consequence of these three


factors:

Unbalanced mass of the system (rotor) about its axis of rotation (MASS field on the
UNBALNC entry).
The magnitude of separation between the rotating axis and the unbalanced mass
(ZOFFSET and ROFFSET fields on the UNBALNC entry).
The angular spin speed of the rotor (specific fields on the RGYRO and RSPINR bulk data
entries).
4. ROFFSET field:

Each entry in the TABLEDi entry specifies the distance by which the unbalanced mass is
offset in the X-Y plane (perpendicular to the axis of rotation of the rotor).

ZOFFSET field:

Each entry in the TABLEDi entry specifies the distance by which the unbalanced mass is
offset in the Z direction (axis of rotation of the rotor).

2130 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


5. The rotation of the unbalanced load occurs in the positive Z direction which is defined by
GRIDA and GRIDB on the RSPINR bulk data entry.

6. The initial position of the unbalanced mass and the direction of its subsequent rotation
are defined with respect to a cylindrical coordinate system. Its angular position is
measured from the plane defined by both the Z-axis and the vector (X1, X2, and X3) with
THETA=0.0 being the direction of the vector (X1, X2, and X3) itself. The rotation of the
unbalanced load occurs in the positive Z direction.

Altair Engineering OptiStruct 13.0 Reference Guide 2131

Proprietary Information of Altair Engineering


USET

Bulk Data Entry

USET – Set of Degrees-of-Freedom for Residual Vector Calculation

Description

Defines a set of degrees-of-freedom.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

USET SNAME G1 C1 G2 C2 G3 C3

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

USET U6 564 4 765 1456 8 5

Field Contents

SNAME Set name

(Character, only U6, ZEROU6 are allowed)

Gi Grid or scalar point identification numbers.

No default (Integer > 0)

Ci Component numbers.

(Integer zero or blank for scalar points, or up to 6 unique digits (0 <


integer < 6) may be placed in the field with no embedded blanks for
grid points. The components refer to the coordinate system
referenced by the grid points.)

2132 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. A maximum of 18 degrees-of-freedom can be defined on one USET entry.

2. If SNAME=ZEROU6, then the degrees-of-freedom are omitted from the set.

3. For normal modes analysis with the Lanczos eigensolver, the case control command
RESVEC=YES must be used to create residual vectors based on the USET DOF . If the
AMSES or AMLS eigensolvers are used, the residual vectors will always be created. The
residual vectors are calculated using the unit load method.

4. For modal frequency response and modal transient analysis, the USET residual vectors are
always calculated if the AMSES and AMLS eigensolvers are used, and are not calculated if
the Lanczos eigensolver is used.

5. The residual vectors are then exported together with the eigenvectors to the H3D,
PUNCH, and OUTPUT2 files. If stress output is requested, the stress state for each mode
is output to the H3D, PUNCH, and OUTPUT files.

6. If SNAME is not U6 or ZEROU6, USET will be ignored.

7. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank
when the grid reference is a scalar point (SPOINT), and that the component be > 1 when
the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is
allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point
(SPOINT) or a structural grid point (GRID) when the component is 0, 1 or blank;
interpreting all of these as 0 for scalar points and as 1 for structural grids. When the
component is greater than 1, the grid reference must always be a structural grid (GRID).

8. This card is represented as a constraint load in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2133

Proprietary Information of Altair Engineering


USET1

Bulk Data Entry

USET1 – Set of Degrees-of-Freedom for Residual Vector Calculation, Alternate Form

Description

Defines a set of degrees-of-freedom.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

USET1 SNAME C G1 G2 G3 G4 G5 G6

G7 G8 G9 -etc.-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

USET1 U6 123 34 88 4 12 19 7

1234 65

Alternate Format and Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

USET1 SNAME C G1 “THRU” G2

USET1 U6 123456 88 THRU 207

Field Contents

SNAME Set name

(Character, only U6, ZEROU6 are allowed)

2134 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

C Component number.

(Integer zero or blank for scalar points, or up to 6 unique digits (0 <


integer < 6) may be placed in the field with no embedded blanks for
grid points. The components refer to the coordinate system
referenced by the grid points.)

Gi Grid or scalar point identification numbers.

(Integer > 0, for THRU option, G1 < G2)

Comments

1. If the alternate format is used, all points in the sequence G1 through G2 are not required
to exist, but there must be at least one boundary degree-of-freedom for the model or a
fatal error will result. Any grids implied in the THRU that do not exist will collectively
produce a warning message, but will otherwise be ignored.

2. If SNAME=ZEROU6, then the degrees-of-freedom are omitted from the set.

3. For normal modes analysis with the Lanczos eigensolver, the case control command
RESVEC=YES must be used to create residual vectors based on the USET1 DOF. If the
AMSES or AMLS eigensolvers are used, the residual vectors will always be created. The
residual vectors are calculated using the unit load method.

4. For modal frequency response and modal transient analysis, the USET1 residual vectors
are always calculated if the AMSES and AMLS eigensolvers are used, and are never
calculated if the Lanczos eigensolver is used.

5. USET1 is applied to normal modes analysis subcases that have the case control
RESVEC=YES specified. In such cases, residual vectors are calculated using the unit load
method. The residual vectors are then exported together with the eigenvectors to the
H3D, PUNCH, and OUTPUT2 files. If stress output is requested, the stress state for each
mode is output to the H3D, PUNCH, and OUTPUT files.

6. If SNAME is not U6 or ZEROU6, USET1 will be ignored.

7. When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or
MIXED, it is allowed that when grid lists are provided for a given component, that the grid
references be either scalar points (SPOINT) or structural grid points (GRID) when the
component is 0, 1 or blank; interpreting all of these as 0 for scalar points and as 1 for
structural grids. When SPSYNTAX is set to STRICT it is required for grid/component pairs
(G#/C#) that the component be 0 or blank when the grid references are to scalar points
(SPOINT), and that the component be > 1 when the grid references are to structural grid
points (GRID). When the component is greater than 1, the grid references must always
be a structural grid (GRID).

8. This card is represented as a constraint load in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2135

Proprietary Information of Altair Engineering


XDAMP

Bulk Data Entry

XDAMP – Raleigh Damping for Geometric Nonlinear Dynamic Analysis

Description

Defines values for Raleigh damping for geometric nonlinear dynamic analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

XDAMP DID GSID ALFA BETA

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

XDAMP 100 34 3.0 1.0

Field Contents

DID Unique damping identification number.

(Integer > 0)

GSID Grid set identification number. Damping is applied to the grid points
in this set.

Default = all grids in the model (blank or Integer > 0)

ALFA Factor for the stiffness matrix contribution.

(Real > 0)

BETA Factor for the mass matrix contribution.

(Real > 0)

2136 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. Rayleigh damping is applied to all geometric nonlinear dynamic analysis subcases, implicit
and explicit. It is ignored in all other subcases.

2. In implicit dynamic analysis damping is applied to all grid points and GSID is ignored.
Multiple XDAMP is not allowed in implicit dynamic analysis.

3. XDAMP and PARAM W3/G are mutually exclusive.

4. Grid sets in all XDAMP statements must contain unique sets of grid points.

5. The viscous damping matrix B is calculated from the mass matrix M and stiffness matrix K
using:

B = ALFA * M + BETA * K

6. This card is represented as an interface in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2137

Proprietary Information of Altair Engineering


XHISADD

Bulk Data Entry

XHISADD – Time History Output Combination for Geometric Nonlinear Analysis

Description

Defines a time history output set as a union of time history outputs defined via XHIST
entries.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

XHISADD SID S1 S2 S3 S4 S5 S6 S7

S8 S9 etc.

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

XHISADD 101 2 3 1 6 4

Field Contents

SID Set identification number.

(Integer > 0)

Sj Set identification numbers of time history output defined via XHIST


entries.

(Integer > 0)

Comments

1. Multipoint constraint sets must be selected with the Subcase Information command
XHIST=SID.

2138 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


2. The Sj must be unique and may not be the identification number of a rigid wall set defined
by another XHISADD entry.

3. XHISADD entries take precedence over XHIST entries. If both have the same SID, only
the XHISADD entry will be used.

4. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2139

Proprietary Information of Altair Engineering


XHIST

Bulk Data Entry

XHIST – Time History Output Request for Geometric Nonlinear Analysis

Description

Defines the time history output request for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

XHIST SID LABEL

FILE TYPE C ID DTTHM

DATA VAR1 VAR2 VAR3 VAR4 VAR5 VAR6 VAR7

VAR8 ...

ENTRY ID1 ID2 ID3 ID4 ID5 ID6 ID7

ID8 ...

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

XHIST 100

GRID

DATA DEF AX AY

ENTRY 345 6687

2140 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

SID Set identification number.

(Integer > 0)

LABEL (Character or blank)

FILE Creation of different time history files runnameTnnx(n:0-1,x:blank or a-i).

(Characters – A, B, C…, and I, or blank)

TYPE Entity type. See table 1.

(Character according to table)

CID Frame coordinate system identification.

(Integer > 0)

DTTHM Output time step for time history files. Once it is specified, it will
overwrite DTTH on NLPARMX, TSTEPNX and XSTEP to control the output
time step of history file specified by FILE in this card.

DATA DATA flag indicating that data labels follow. If no DATA is specified, the
default is VAR1 = DEF.

VARi Output data label. See table 1.

(Character)

ENTRY ENTRY flag indicating that a list of identifiers is following.

IDi Entry identifier for TYPE. See table 1.

(Integer > 0)

Comments

1. XHIST sets must be selected with the Subcase Information command XHIST = SID or by
XHISADD. It can only be selected in geometric nonlinear analysis subcases which are
defined by an ANALYSIS = NLGEOM, IMPDYN or EXPDYN subcase entry.

2. Table 1 below gives the definitions of TYPE, VARi, and IDi. The notation DEF (DX, DY, DZ,
VX, VY, VZ) means that if DEF is selected, all six values following in parenthesis are
written at once. However, instead of requesting DEF each value can be requested
individually. Details on the output requests can be found in Table 2.

Altair Engineering OptiStruct 13.0 Reference Guide 2141

Proprietary Information of Altair Engineering


3. A property cannot be in several time history groups. In this case, the only variables
output in time history are the variables declared in the last option which refers to the
property.

4. It is not possible to have the same grid point several times in the same GRID group.
OptiStruct provides an error message in such cases.

5. If an output coordinate system GRID, CD is specified: coordinates, displacement, linear


and angular velocities, linear and angular accelerations of the grid are projected to that
system.

6. If a reference frame is specified: local coordinates, relative displacement, relative linear


and angular velocities, relative linear and angular accelerations of the node with respect
to the frame are output.

7. Global results are always written.

8. The OFF element status information works as follows:

OFF = 0 – Element deleted.


OFF = 1 – Element active.
OFF = 2 – Element active using small strain.
OFF = -1 – Element is sleeping (turned rigid).

Table 1: Output Requests

TYPE VARi IDi

GRID DEF (DX, DY, DZ, VX, VY, VZ), D (DX, DY, DZ), Grid ID
V (VX, VY, VZ), A (AX, AY, AZ), VR (VRX, VRY,
VRZ) AR (ARX, ARY, ARZ), XYZ (X, Y, Z),
REACX, REACY, REACZ, REACXX, REACYY,
REACZZ

PROP DEF (IE, KE, XMOM, YMOM, ZMOM, MASS, HE), Property ID
XCG, YCG, ZCG, XXMOM, YYMOM, ZZMOM, IXX,
IYY, IZZ, IXY, IYZ, IZX, RIE, KERB, RKERB, RKE

SHELL DEF (F1, F2, F12, M1, M2, M12, IEM, IEB, EMIN, Element ID
EMAX, OFF), STRESS (F1, F2, F12, Q1, Q2, M1,
M2, M12), STRAIN (E1, E2, E12, SH1, SH2, K1,
K2, K12), PLAS (EMIN, EMAX)

SOLID DEF (SX , SY, SZ, SXY, SYZ, SXZ, IE, DENS, Element ID
PLAS, TEMP, OFF), STRESS (SX, SY, SZ, SXY,
SYZ, SXZ), LOCSTRS (LSX, LSY, LSZ, LSXY,
LSYZ, LSXZ), BULK, VOL, DAM1, DAM2, DAM3,
DAM4, DAM5, DAMA, EPSXX, EPSYY, EPSZZ,
EPSXY, EPSXZ, EPSYZ

2142 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


TYPE VARi IDi

RWALL DEF (FNX, FNY, FNZ, FTX, FTY, FTZ), FN (FNX, Load set ID of
FNY, FNZ), FT (FTX, FTY, FTZ) RWALL

CONTCT DEF (FNX, FNY, FNZ, FTX, FTY, FTZ), FN (FNX, Contact ID
FNY, FNZ), FT (FTX, FTY, FTZ), M (MX, MY,
MZ)

SECT DEF (FNX, FNY, FNZ, FTX, FTY, FTZ, M1, M2, Load set ID of
M3), FN (FNX, FNY, FNZ), FT (FTX, FTY, FTZ), XSECT
M (MX, MY, MZ), GLOBAL (FNX, FNY, FNZ, FTX,
FTY, FTZ, MX, MY, MZ), LOCAL (F1, F2, F3, M1,
M2, M3), CENTER (CX, CY, CZ)

SPRING, DEF (FX, FY, FZ, MX, MY, MZ, LX, LY, LZ, RX, Element ID
BUSH RY, RZ, IE, OFF)

BEAM, BAR DEF (F1, F2, M2, M3, IE, OFF), F3, M1 Element ID

ROD DEF(F, M, IE) Element ID

Table 2: Output Request Descriptions

Type Output Data Label Description and Remarks

Global IE Internal energy.

Global internal energy includes all


material internal energy and global
spring internal energy, but not spring
rotational internal energy.

KE Kinetic energy.

RKE Rotational kinetic energy.

CE Contact energy.

HE Hourglass energy.

SIE Spring internal energy.

EFW External forces work.

TE Energy sum IE + KE.

Altair Engineering OptiStruct 13.0 Reference Guide 2143

Proprietary Information of Altair Engineering


Type Output Data Label Description and Remarks

RTE Total rotational energy IE + KE + RKE.

TTE Total energy sum IE + KE + RKE + CE +


HE.

DTE Delta energy TTE - EFW.

XMOM, YMOM, ZMOM Momentum.

DT Time step.

TER

DTE_REL

VX, VY, VZ Velocities.

GRID X, Y, Z Coordinates.

DX, DY, DZ Displacement components.

VX, VY, VZ Velocity components.

AX, AY, AY Acceleration components.

VRX, VRY, VRZ Angular velocity components.

ARX, ARY, ARZ Angular acceleration components.

REACX, REACY, REACZ Reaction force components

REACXX, REACYY, REACZZ Reaction moment components

PROP IE Internal energy.

KE Kinetic energy.

XMOM, YMOM, ZMOM Momentum components.

HE Hourglass energy.

XCG, YCG, ZCG Center of gravity.

XXMOM, YYMOM, ZZMOM Rotational momentum components.

2144 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Type Output Data Label Description and Remarks

IXX, IYY, IZZ, IXY, IYZ, Inertia matrix components.


IZX

RIE Shear internal energy.

KERB, RKERB Translational and rotational rigid body


energy.

RKE Rotational kinetic energy.

SHELL F1, F2, F12 Stress in direction 1, 2, 12.

Q1, Q2 Mean stress in direction 13, 23.

M1, M2, M12 Moments per unit length per thickness


square in direction 1, 2, 12.

IEM, IEB Internal membrane and bending energy.

EMIN, EMAX Minimum, maximum equivalent plastic


strain.

OFF Element status.

See comment 8.

THIC Thickness.

E1, E2, E12 Stress in direction 1, 2, 12.

SH1, SH2 Shear strain in direction 1, 2.

K1, K2, K12 Curvature in direction 1, 2, 12.

SOLID SX , SY, SZ, SXY, SYZ, Stress tensor components.


SXZ

LSX, LSY, LSZ, LSXY, Local stress tensor components.


LSYZ, LSXZ
Only ISOLID = 1, 2, 12

IE Internal energy.

DENS Density.

BULK Bulk viscosity.

Altair Engineering OptiStruct 13.0 Reference Guide 2145

Proprietary Information of Altair Engineering


Type Output Data Label Description and Remarks

VOL Volume.

PLAS Plastic strain.

Only MATX02.

TEMP Temperature.

OFF Element status.

See comment 8.

CONTCT FNX, FNY, FNZ, FTX, FTY, Normal and tangential force
FTZ components.

MX, MY, MZ Moment components.

RWALL FNX, FNY, FNZ, FTX, FTY, Normal and tangential force
FTZ components.

SECT FNX, FNY, FNZ, FTX, FTY, Normal and tangential force
FTZ components.

MX, MY, MZ Moment components.

F1, F2, F3, M1, M2, M3 Forces and moments in section


coordinates.

CX, CY, CZ Center of the section.

SPRING, BUSH FX, FY, FZ, MX, MY, MZ Forces and moment components.

LX, LY, LZ Elongation.

RX, RY, RZ Rotation.

IE Internal energy.

OFF Element status.

BEAM, BAR F1, F2, F3, M1, M2, M3 Forces and moments in element
coordinates

IE Internal energy

OFF Element status

2146 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Type Output Data Label Description and Remarks

ROD F Axial force

M Torsional moment

IE Internal energy

Altair Engineering OptiStruct 13.0 Reference Guide 2147

Proprietary Information of Altair Engineering


XSHLPRM

Bulk Data Entry

XSHLPRM – Default Definition for Shell Element Properties for Geometric Nonlinear Analysis

Description

Defines default shell element parameters for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

XSHLPRM ISHELL ISH3N ISMSTR ITHIC K IPLAS NIP IDRIL

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

XSHLPRM 14 2 NEWT 5

Field Contents

ISHELL Flag for 4-node shell element formulation.

Default = 24 (Integer)

1 - Q4, visco-elastic hourglass modes orthogonal to deformation and


rigid modes (Belytschko).

2 - Q4, visco-elastic hourglass without orthogonality (Hallquist).

3 - Q4, elastic-plastic hourglass with orthogonality.

4 - Q4 with improved type 1 formulation (orthogonalization for


warped elements).

12 - QBAT or DKT18 shell formulation.

24 - QEPH shell formulation.

ISH3N Flag for 3-node shell element formulation.

2148 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

Default = 2 (Integer)

1 - Standard triangle (C0).

2 - Standard triangle (C0) with modification for large rotation.

30 - DKT18.

31 - DKT_S3.

ISMSTR Flag for shell small strain formulation.

Default = 2 (Integer)

1 - Small strain from time =0

(new formulation compatible with all other formulation flags).

2 - Full geometric non-linearity with optional small strain formulation


activation by time step.

3 - Old small strain formulation (only compatible with ISHELL =2).

4 - Full geometric non-linearity (Time step limit has no effect).

ITHICK Flag for shell resultant stresses calculation.

Default = VAR (CONST or VAR)

CONST - Thickness is constant.

VAR - Thickness change is taken into account.

IPLAS Flag for shell plane stress plasticity (MATX2, MATX27, and MATX36
only).

Default = NEWT (RAD or NEWT)

RAD - Radial return.

NEWT - Iterative projection with 3 Newton iterations.

NIP Number of integration points through the thickness. NIP = 0 defines


global integration.

Default = 5 (Integer 0 < N < 10)

IDRIL Flag for drilling degree of freedom stiffness.

Altair Engineering OptiStruct 13.0 Reference Guide 2149

Proprietary Information of Altair Engineering


Field Contents

If NLGEOM or IMPDYN subcase exists, default = 1,

Otherwise, default = 0 (Integer)

0 = No

1 = Yes

Comments

1. XSHLPRM defines default settings for solid properties that can be overwritten by PSHELLX.

2. XSHLPRM is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. Q4: Original 4 node OptiStruct shell with hourglass perturbation stabilization.

QEPH: Formulation with physical hourglass stabilization for general use.

QBAT: Modified BATOZ Q4 24 shell with 4 Gauss integration points and reduced
integration for in-plane shear. No hourglass control is needed for this shell.

DKT18: BATOZ DKT18 thin shell with 3 Hammer integration points.

4. ISHELL = 2 is incompatible with one integration point for shell element.

5. If the small strain option (ISMSTR) is set to 1 or 3, the strain and stress are engineering
strain and stress; otherwise they are true strain and stress.

6. Global integration (NIP = 0) is only compatible with MAT1, MATX2, and MATX36.

7. For MAT1, membrane only behavior happens if NIP = 1. Otherwise, NIP is ignored and
global integration (NIP = 0) is used.

8. For ITHICK = VAR, it is recommended to use IPLAS = NEWT.

9. For MATX2, the default value for IPLAS and global integration (NIP=0) is IPLAS = RAD.

10. For MATX36, the default value for IPLAS and global integration (NIP=0) is IPLAS = NEWT.

11. This card is represented as a control card in HyperMesh.

2150 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


XSOLPRM

Bulk Data Entry

XSOLPRM – Default SOLID Properties for Geometric Nonlinear Analysis

Description

Defines default SOLID properties for geometric nonlinear analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

XSOLPRM ISOLID ISMSTR IFRAME NIP

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

XSOLPRM 24 222

Field Contents

ISOLID Flag for solid elements formulation.

Default = 1 for explicit analysis and 14 for implicit analysis (Integer).

1 - Standard 8-node solid element, 1 integration point. Viscous


hourglass formulation with orthogonal and rigid deformation modes
compensation (Belytschko).

2 - Standard 8-node solid element, 1 integration point. Viscous


hourglass formulation without orthogonality (Hallquist).

12 - Standard 8-node solid, full integration (no hourglass).

14 - HA8 locking-free 8-node solid element, co-rotational, full


integration, variable number of Gauss points.

16 - Quadratic 20-node solid, full integration, variable number of


Gauss points.

17 - H8C compatible solid full integration formulation.

Altair Engineering OptiStruct 13.0 Reference Guide 2151

Proprietary Information of Altair Engineering


Field Contents

24 - HEPH 8-node solid element. Co-rotational, under-integrated.

(1 Gauss point) with physical stabilization.

ISMSTR Flag for small strain formulation (ISOLID = 1, 2, 14, and 24 only).

Default = 4 (Integer)

1 - Small strain from time=0.

2 - Full geometric non-linearity with small strain formulation


activation by time step.

3 - Simplified small strain formulation from time=0 (non-objective


formulation).

4 - Full geometric non-linearity. Time step limit has no effect.

10 - Lagrange type total strain.

IFRAME Flag for co-rotational element formulation (ISOLID = 1, 2, 12, and


17 only).

Default = OFF (ON or OFF)

NIP Number of integration points (ISOLID = 14, 16 only).

Default = 222 (Integer = ijk):

2 < i,j,k < 9 for ISOLID =14

2 < i,k < 3, 2 < j < 9 for ISOLID =16

where:

i = Number of integration points in local x direction.


j = Number of integration points in local y direction.
k = Number of integration points in local z direction.

Comments

1. XSOLPRM defines default settings for solid properties that can be overwritten by PSOLIDX.

2. XSOLPRM is only applied in geometric nonlinear analysis subcases which are defined by
ANALYSIS = NLGEOM, IMPDYN, or EXPDYN. It is ignored for all other subcases.

3. The ISOLID flag is not used with CTETRA elements. For these, elements with four and
ten nodes the number of integration points is fixed at one and four, respectively.

2152 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


4. For fully integrated solids (SOLID =12), the deviatoric behavior is computed using 8 Gauss
points; bulk behavior is under-integrated to avoid element locking. It is currently
compatible with material MAT1, MATS1, MATX33, and MATX36.

5. With the small strain option (ISMSTR), strain and stress is engineering strain and stress.
Otherwise, it is true strain and stress.

6. In time history and animation files, the stress tensor is written in the co-rotational frame.

7. Fully integrated elements (ISOLID =12) only uses full geometric non-linearity (corresponds
to ISMSTR = 4). Time step limit has no effect.

8. ISMSTR = 10 is only compatible with materials using total strain formulation (MATX42).

9. The time step control XSTEP, TYPEi = SOLID, TSCi = CST only works on elements with
ISMSTR = 2.

10. Co-rotational formulation: For ISOLID = 1, 2, 12 and IFRAME = ON, the stress tensor is
computed in a co-rotational coordinate system. This formulation is more accurate if large
rotations are involved. It comes at the expense of higher computation cost. It is
recommended in case of elastic or visco-elastic problems with important shear
deformations. The co-rotational formulation is compatible with 8 node solids.

11. HA8 (ISOLID = 14) elements: this element uses a locking-free general solid formulation,
co-rotational. The number of Gauss points is defined by NIP flag: for example, combined
with NIP = 222 gives an 8 Gauss integration point element, similar to ISOLID = 12. The
HA8 formulation is compatible with all material laws.

12. HEPH (ISOLID = 24) elements: This element uses an hourglass formulation similar to QEPH
shell elements.

13. The hourglass formulation is viscous for ISOLID = 0, 1, and 2.

14. This card is represented as a control card in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2153

Proprietary Information of Altair Engineering


XSTEP

Bulk Data Entry

XSTEP – Parameters for Explicit Analysis Control

Description

Defines explicit analysis control.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

XSTEP SID TA0 DTA DTTH NPRINT RFILE NITER NPAMS

DTSC A DTMIN TSTYP TAC T

TYPE1 TSC 1 DT1 DTM1 ESID1 AMST1

TYPE2 TSC 2 DT2 DTM2 ESID2 AMST2

-etc.-

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

XSTEP 2

0.9 DETAIL

GRID C ST 0.9 0.1e-6

Field Contents

SID Set identification number.

(Integer > 0)

2154 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

TA0 Start time for writing animation files.

Default = 0.0 (Real > 0)

DTA Output time step for animation files. If zero, no output (See
comment 3).

Default = 0.01*TTERMS (Real > 0)

DTTH Output time step for time history files. If zero, no output (See
comment 3).

Default = 0.001*TTERMS (Real > 0)

NPRINT Print every NPRINT iteration. If negative, to .out and standard


output; if positive, only to .out file.

Default = -1000 (Integer)

RFILE Cycle frequency to write restart file for nonlinear iteration.

Default = 5000 (Integer > 0)

NITER Maximum number of iterations in conjugate gradient.

Only valid when TSTYP = GRID and TACT = AMS.

Default = 1000 (Integer > 0)

NPAMS Frequency (number of cycles) for writing additional output about


the number of iterations before convergence in the conjugate
gradient.

No default (Integer > 0)

DTSCA Default scale factor on explicit time step for all elements.

Default = 0.9 (Real > 0)

DTMIN Default minimum explicit time step.

Default = 0.0 (Real > 0)

TSTYP Type of time step control (See comment 2).

Altair Engineering OptiStruct 13.0 Reference Guide 2155

Proprietary Information of Altair Engineering


Field Contents

ELEM Elemental time step.

GRID Nodal time step.

CONTACT Contact interface time step

DETAIL From definition in continuation lines.

Default = GRID (Character = GRID, ELEM, CONTACT or DETAIL)

TACT Action if minimum time step is reached (For TSTYP = GRID, ELEM,
CONTACT, See comment 3).

DEF Default (TSTYP = GRID, CONTACT – Do nothing, ELEM


(Shells) = DEL, ELEM (Solids) = STOP).

DEL Delete (TSTYP = ELEM and CONTACT only).

STOP Stop run.

CST Standard mass scaling. Continue with constant time step.

AMS Advanced mass scaling. Continue with constant time step


(TSTYP = GRID and CONTACT only).

Default = DEF (Character = DEF, STOP, DEL, CST, or AMS)

TYPEi Entity type selection (See comment 4).

No default (Character = GRID, CONTACT, SHELL, and SOLID)

TSCi Time step control method (See comment 4).

STOP Stop after reaching DTMi. A restart file will be written.


This option is the default for brick and quad elements.
DEL Element deletion. Elements reaching DTMi are removed.
This option is the default for shell elements. For TYPEi =
CONTACT, the impacted grid that fixes the time step will
be removed from the interface.
CST Constant time step after reaching DTMi.

For TYPEi = SHELL, SOLID (except 8 integration points


hexas) the formulation switches to small strain for each

2156 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

element that reaches the DTMi.

For TYPEi = GRID, CONTACT, the mass of the grid that


reaches DTMi is increased. You should check the evolution
of the mass of the model.

AMS Advanced mass scaling. Constant time step after reaching


DTMi. Advanced Mass Scaling does not modify the global
mass so that the global momentum of the related nodes is
conserved. More accurate than TSCi = CST (TYPEi = GRID
and CONTACT only).
SET Forces are reduced to keep constant time step (TYPEi =
GRID only).

Default = according to table (blank or Character = STOP, DEL, CST,


AMS, SET)

DTi Time step scale factor for entity type (See comment 4).

Default = 0.9 (Real > 0.0)

DTMi Minimum time step for entity type.

Default = 0.0 (Real > 0.0)

ESIDi
AMS).

No default (blank, Integer > 0)

AMSTi Tolerance for advanced mass scaling convergence (Only for TYPEi =
AMS).

Default = 10-4 (REAL > 0.0)

Comments

1. The XSTEP bulk data entry is selected by the Subcase Information command XSTEP =
option. It is only used in explicit analysis (ANALYSIS = EXPDYN); it is ignored in other
analyses.

2. Any number of continuation lines can be used.

3. Time step control for explicit analysis

Altair Engineering OptiStruct 13.0 Reference Guide 2157

Proprietary Information of Altair Engineering


TSTYP Elements Default Options

GRID Do nothing AMS, CST, STOP

ELEM Shells DEL CST, STOP

Solids STOP CST, DEL

With TSTYP = GRID, the nodal time step is used. With this option, the computation of
each cycle is slightly more expensive, but the time step can be higher, mainly for non-
optimized meshes and therefore the overall runtime shorter.

For TSTYP = GRID, TACT = CST, the mass of the grid that reaches DTMIN1 is increased.
You should check the evolution of the mass of the model.

For TSTYP = ELEM, TACT = CST, the element formulation switches to small strain for
each element that reaches the DTMIN1.

4. Overview of default settings and options for TYPEi:

Do Nothing STOP DEL CST AMS SET

SHELL N/A Optional Default Optional N/A N/A

SOLID N/A Default Optional Optional N/A N/A

CONTACT Default Optional Optional Optional Optional N/A

GRID Default Optional N/A Optional Optional Optional

With TYPEi = GRID, the nodal time step is used. With this option, the computation of
each cycle is slightly more expensive, but the time step can be higher, mainly for non-
optimized meshes and therefore the overall runtime shorter.

With TYPEi = GRID and TSCi = CST, DTi = 0.67 is recommended.

With TYPEi = CONTACT and TSCi = DEL, the impacted node which fixes the time step is
removed from the interface.

TYPEi = SOLID and TSCi = CST is only active for solid elements with the flag ISMSTR = 2
set on PSOLIDX. This option is not available for 8 integration points.

5. For more information about geometric nonlinear analysis, refer to the Geometric Nonlinear
Analysis section.

6. TSTYP = NODA and TACT = AMS can activate elementary time step for Advanced Mass
Scaling, as well as TYPEi = NODA and TSCi = AMS.

7. NITER and NPAMS are only valid for Advanced Mass Scaling (AMS). If more NITER
iterations have been performed before convergence of the conjugate gradient, the
computation stops and error out. If NPAMS is specified, at each NPAMS cycle an
additional output is provided including: the number of iterations before convergence of

2158 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


the conjugate gradient at this cycle, the final residual norm and the force vector norm.

8. This card is represented as a loadcollector in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2159

Proprietary Information of Altair Engineering


Element Quality Check

In order to prevent analyses from being carried out on badly discretized models, an element
quality check is incorporated into the pre-processing phase. The element quality check is
controlled jointly by the CHECKEL parameter (see PARAM, CHECKEL) and the ELEMQUAL bulk
data entry.

Three types of element quality checks are performed:

1. Validity check of maximum allowable limits – a bound based on mathematical limitations.


Violation will cause singular or ill-conditioned element matrices. Examples are: a re-
entrant angle (equal to or greater than 180 degrees) in quadrilateral element/surface, 0
collapse in tetra.

2. Quality check of error limits – whether an element is in the acceptable range.

3. Quality check of warning limits – whether an element is in the recommended range.


Violation may cause poor result quality, but will not stop the solution process.

With the CHECKEL parameter, type 2 and 3 checks may be controlled and the ELEMQUAL bulk
data entry may be used to set the error and warning limits. However, the "validity" check,
type 1, is always performed – even when the value of PARAM, CHECKEL is NO.

A check for collapsed element nodes is performed for all elements. All other property checks
are performed after this collapsed node check, and will be skipped if collapsed nodes are
found. If the element quality check is activated, the checks for each element are performed
according to the following precedence: (1) validity check, (2) quality check for error limits,
and (3) quality check for warning limits. Violation of any check will skip the subsequent
check(s).

The warp angle check on CQUAD4 elements is relaxed for topography optimization. This
relaxation prevents premature error termination of the optimization due to element quality
concerns. However, be aware that the resulting mesh from a topography optimization may fail
the CQUAD4 warp angle check when reanalyzed.

The checks performed and the default bound values for each element type are outlined in the
following topics:
CGASK6 Element Checks and Default Bound Values
CGASK8 Element Checks and Default Bound Values
CGASK12 Element Checks and Default Bound Values
CGASK16 Element Checks and Default Bound Values
CTRIA3 Element Checks and Default Bound Values
CTRIA6 Element Checks and Default Bound Values
CQUAD4 Element Checks and Default Bound Values
CQUAD8 Element Checks and Default Bound Values
CTAXI / CTRIAX6 Element Checks and Default Bound Values
CTETRA Element Checks and Default Bound Values
CPENTA Element Checks and Default Bound Values
CHEXA Element Checks and Default Bound Values

2160 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CPYRA Element Checks and Default Bound Values

Altair Engineering OptiStruct 13.0 Reference Guide 2161

Proprietary Information of Altair Engineering


CGASK6 Element Checks and Default Bound Values

CGASK6 Element Check and Default Bounds

The element check and default bounds of the CGASK6 element are identical as those of the
first-order (6-noded) CPENTA element.

2162 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CGASK8 Element Checks and Default Bound Values

CGASK8 Element Check and Default Bounds

The element check and default bounds of the CGASK8 element are identical as those of the
first-order (8-noded) CHEXA element.

Altair Engineering OptiStruct 13.0 Reference Guide 2163

Proprietary Information of Altair Engineering


CGASK12 Element Checks and Default Bound Values

CGASK12 Element Check and Default Bounds

The element check and default bounds of the CGASK12 element are identical as those of the
second-order (15-noded) CPENTA element. Notice that CGASK12 has six 3-node edges of
which Hoe Normal Offset and Hoe Tangent Offset are checked.

2164 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CGASK16 Element Checks and Default Bound Values

CGASK16 Element Check and Default Bounds

The element check and default bounds of the CGASK16 element are identical as those of the
second-order (20-noded) CHEXA element. Notice that CGASK16 has 8 3-node edges of which
Hoe Normal Offset and Hoe Tangent Offset are checked.

Altair Engineering OptiStruct 13.0 Reference Guide 2165

Proprietary Information of Altair Engineering


CTRIA3 Element Checks and Default Bound Values

CTRIA3 Element Check

The following qualities of the CTRIA3 element are checked:

Aspect Ratio
The aspect ratio of a CTRIA3 element is defined as the ratio of the maximum side
length to the minimum side length.

Skew Angle
The skew angle of a CTRIA3 element is the difference between 90 degrees and the
minimum of three angles: a1, a2 and a3. These angles are defined, for the CTRIA3
element, as the smallest of the angles created when a line drawn from a node to the
midpoint of the opposing side intersects a line connecting the midpoints of the
adjacent two sides. The skew angle has a range from 0 degrees for a perfect triangle
to 90 degrees for a collapsed triangle.
SKEW = 90 - MIN(a1,a2,a2 )

Vertex Angle
For each vertex, the angle is measured between its two adjacent edges. The minimum
and maximum values of the three nodes are reported for the element.

CTRIA3 Default Bounds

Default values for Default values for Default values for


warning message error message validity check
Information
Lower Upper Lower Upper Lower Upper
Limit Limit Limit Limit Limit Limit

Aspect Ratio - 50.0 - 500.0 - 1.0E5

Skew Angle - 75.0 - 85.0 - 90.0

Vertex Angle 15.0 165.0 3.0 177.0 0.0 180.0

The values used for warning and error checks may be adjusted by the ELEMQUAL bulk data
entry, but validity checks are hard-coded.

2166 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Altair Engineering OptiStruct 13.0 Reference Guide 2167

Proprietary Information of Altair Engineering


CQUAD4 Element Checks and Default Bound Values

CQUAD4 Element Check

The following qualities are checked for CQUAD4 elements:

Vertex Angle
For each vertex, the angle is measured between its two adjacent edges. The minimum
and maximum values of the four nodes are reported for the element.

Aspect Ratio
The aspect ratio of a CQUAD4 element is the length of its longest side, divided by the
length of its shortest side.

Skew Angle
The skew angle in a CQUAD4 element is calculated by finding the minimum angle
between two lines joining opposite mid-sides of the element. Ninety degrees minus the
minimum angle found is reported.

Warp Angle
The warpage of a CQUAD4 element is calculated by splitting the quad into two trias
and finding the angle between the two planes which the trias form. The quad is then
split again, this time using the opposite corners and forming the second set of trias.
The angle between the two planes, which the trias form, is then found. The maximum
angle found between the planes is the warp angle of the element.

CQUAD4 Default Bounds

Default values for Default values for Default values for


warning message error message validity check
Information
Lower Upper Lower Upper Lower Upper
Limit Limit Limit Limit Limit Limit

Aspect Ratio - 100.0 - 1000.0 - 1.0E5

Skew Angle - 60.0 - 75.0 - 90.0

Warp Angle* - 30.0 - 60.0 - 180.0

Vertex Angle 15.0 165.0 3.0 177.0 0.0 180.0

*Warp angle limits are relaxed to 140/160/179 in topography optimization problems.

The values used for warning and error checks may be adjusted by the ELEMQUAL bulk data
entry, but validity checks are hard-coded.

2168 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CQUAD8 Element Checks and Default Bound Values

CQUAD8 Element Check

The following qualities are checked for CQUAD8 elements:

Vertex Angle
This quality is calculated using only the corner nodes. For each vertex, the angle is
measured between its two adjacent edges. The minimum and maximum values of the
four nodes are reported for the element.

Aspect Ratio

This quality is calculated using only the corner nodes. The aspect ratio of a CQUAD8
element is the length of its longest side, divided by the length of its shortest side.

Skew Angle
This quality is calculated using only the corner nodes. The skew angle in a CQUAD8
element is calculated by finding the minimum angle between two lines joining opposite
mid-sides of the element. Ninety degrees minus the minimum angle found is reported.

Warp Angle
This quality is calculated using only the corner nodes. The warpage of a CQUAD8
element is calculated by splitting the quad into two trias and finding the angle between
the two planes which the trias form. The quad is then split again, this time using the
opposite corners and forming the second set of trias. The angle between the two
planes, which the trias form, is then found. The maximum angle found between the
planes is the warp angle of the element.

Hoe Normal Offset


The hoe normal offset is the maximum of its edges normal offset values. See the
definition of hoe normal offset of 3-node edge.

Hoe Tangent Offset


The hoe tangent offset is the maximum of its edges tangent offset values. See the
definition of hoe tangent offset of 3-node edge.

CQUAD8 Default Bounds

Default values for Default values for Default values for


Information warning message error message validity check

Lower Limit Upper Limit Lower Limit Upper Limit Lower Limit Upper Limit

Aspect Ratio - 100.0 - 1000.0 - 1.0E5

Skew Angle - 60.0 - 75.0 - 90.0

Altair Engineering OptiStruct 13.0 Reference Guide 2169

Proprietary Information of Altair Engineering


Default values for Default values for Default values for
Information warning message error message validity check

Lower Limit Upper Limit Lower Limit Upper Limit Lower Limit Upper Limit

Warp Angle - 90.0 - 175.0 - 180.0

Vertex Angle 15.0 165.0 3.0 177.0 0.0 180.0

Hoe Normal Offset - 0.30 - 0.60 - 1.0E5

Hoe Tangent - 0.20 - 0.24 - 0.25


Offset

The values used for warning and error checks may be adjusted by the ELEMQUAL bulk data
entry, but validity checks are hard-coded.

2170 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CTAXI / CTRIAX6 Element Checks and Default Bound
Values

3-node CTAXI / CTRIA6 Element Check and Default Bounds

The element check and default bounds of the 3-node CTAXI or CTRIAX6 element are identical
as those of the CTRIA3 element.

6-node CTAXI / CTRIA6 Element Check and Default Bounds

The element check and default bounds of the 6-node CTAXI or CTRIAX6 element are identical
as those of the CTRIA3 element.

Altair Engineering OptiStruct 13.0 Reference Guide 2171

Proprietary Information of Altair Engineering


CTRIA6 Element Checks and Default Bound Values

CTRIA6 Element Check

The following qualities of the CTRIA6 element are checked:

Aspect Ratio
This quality is calculated using only the corner nodes. It is defined as the ratio of the
maximum side length to the minimum side length.

Skew Angle

This quality is calculated using only the corner nodes. It is the difference between 90
degrees and the minimum of three angles: a1, a2 and a3. These angles are defined, for
the CTRIA6 element, as the smallest of the angles created when a line drawn from a
node to the midpoint of the opposing side intersects a line connecting the midpoints of
the adjacent two sides. The skew angle has a range from 0 degrees for a perfect
triangle to 90 degrees for a collapsed triangle.

Vertex Angle
This quality is calculated using only the corner nodes. For each vertex, the angle is
measured between its two adjacent edges. The minimum and maximum values of the
three nodes are reported for the element.

Hoe Normal Offset


The hoe normal offset is the maximum of its edges normal offset values. See the
definition of hoe normal offset of 3-node edge.

Hoe Tangent Offset


The hoe tangent offset is the maximum of its edges tangent offset values. See the
definition of hoe tangent offset of 3-node edge.

CTRIA6 Default Bounds

Default values for Default values for Default values for


warning message error message validity check
Information
Lower Upper Lower Upper Lower Upper
Limit Limit Limit Limit Limit Limit

Aspect Ratio - 50.0 - 500.0 - 1.0E5

Skew Angle - 75.0 - 85.0 - 90.0

Vertex Angle 15.0 165.0 3.0 177.0 0.0 180.0

Hoe Normal - 0.30 - 0.60 - 1.0E5


Offset

2172 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Default values for Default values for Default values for
warning message error message validity check
Information
Lower Upper Lower Upper Lower Upper
Limit Limit Limit Limit Limit Limit

Hoe Tangent - 0.20 - 0.24 - 0.25


Offset

The values used for warning and error checks may be adjusted by the ELEMQUAL bulk data
entry, but validity checks are hard-coded.

Altair Engineering OptiStruct 13.0 Reference Guide 2173

Proprietary Information of Altair Engineering


Hoe Tangent Offset of 3-node Edge
The hoe tangent offset of a 3-node edge is defined as the ratio of the distance between the
real and ideal mid-side node and the distance between the corner nodes of the edge. If the
mid-side node does not lie on the line connecting the corner nodes (that is the edge has a
non-zero normal offset), then its projection on the line is used in the calculation.

HTEi = Hoe tangent offset of edge i

= di / li

2174 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Hoe Normal Offset of 3-node Edge
The hoe normal offset of a 3-node edge is defined as the ratio between the mid-side node’s
normal offset distance (distance between the mid-side node and the line connecting the two
corner nodes of the edge) and the distance between the two corner nodes.

HNEi = Hoe normal offset of edge i

= hi / li

Altair Engineering OptiStruct 13.0 Reference Guide 2175

Proprietary Information of Altair Engineering


CTETRA Element Checks and Default Bound Values

CTETRA 1st-order (4-noded) Element Checks

The following qualities of the CTETRA 1st-order element are checked:

Aspect Ratio

The aspect ratio of a CTETRA 1st-order element is defined as the maximum of the aspect
ratio of its four triangular faces. Each face is treated as a CTRIA3 element.

Face Skew Angle

The face skew angle of a CTETRA 1st-order element is defined as the maximum of the
skew angles of its four triangular faces. Each face is treated as a CTRIA3 element.

Vertex Angle

The same vertex angle check is performed for all of the faces, and each is treated as a
triangular (CTRIA3) or quadrilateral (CQUAD4) element. The minimum and maximum values
reported for the element.

Collapse

The collapse of a CTETRA 1st-order element is defined as the minimum of four values,
each calculated as the ratio between the distance from a vertex to its opposing face, and
the square root of the area of the opposing face.

collapse = MIN (hi / sqrt(Ai)) i = 1,2,3,4

The reported value is normalized by 1.2408, which gives the equilateral tetra a collapse
value of 1. As the tetra collapses, the collapse value approaches 0.

Edge Angle

An edge angle is the absolute value of the angle between two faces sharing a common
edge subtracted from 90 degrees. The edge angle (EA) of a CTETRA 1st-order element is
defined as the maximum of its six edge angles.

EA = MAX | 90 - ANGLE(Nki, Nli) i = 1, ... 6

Where, Nki and Nli are the normal vectors of faces k and l that have a common edge i.

2176 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CTETRA 2nd-order (10-noded) Element Checks

The following qualities of the CTETRA 2nd-order element are checked:

Aspect Ratio

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CTETRA 1st-order element.

Face Skew Angle

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CTETRA 1st-order element.

Vertex Angle

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CTETRA 1st-order element.

Collapse

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CTETRA 1st-order element.

Edge Angle

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CTETRA 1st-order element.

Hoe Normal Offset

The hoe normal and tangent offsets of the CTETRA 2nd-order element are defined as the
maximum of the hoe normal and tangent offsets of its 6 edges, respectively. See the
definition of hoe normal offset of 3-node edge.

Hoe Tangent Offset

The hoe normal and tangent offsets of the CTETRA 2nd-order element are defined as the
maximum of the hoe normal and tangent offsets of its 6 edges, respectively. See
definition of hoe tangent offset of 3-node edge.

Altair Engineering OptiStruct 13.0 Reference Guide 2177

Proprietary Information of Altair Engineering


CTETRA Default Bounds

Default values for Default values for Default values for


warning message error message validity check
Information
Lower Upper Lower Upper Lower Upper
Limit Limit Limit Limit Limit Limit

Aspect Ratio - 100.0 - 1000.0 - 1.0E5

Face Skew Angle - 75.0 - 85.0 - 90.0

C ollapse 0.001 100.0 0.0 100.0 0.0 1000.0

Edge Angle - 75.0 - 87.0 - 90.0

Hoe Normal Offset - 0.30 - 0.60 - 1.0E5

Hoe Tangent Offset - 0.20 - 0.25 - 0.50

The values used for warning and error checks may be adjusted by the ELEMQUAL bulk data
entry, but validity checks are hard-coded.

2178 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CPENTA Element Checks and Default Bound Values

CPENTA 1st-order (6-noded) Element Checks

The following qualities of the CPENTA 1st-order element are checked:

Aspect Ratio

The aspect ratio of a CPENTA 1st-order element is defined as the maximum of the aspect
ratios of its three quadrilateral faces and two triangular faces. Each quadrilateral face is
treated as a CQUAD4 element and each triangular face as a CTRIA3 element.

Face Skew Angle

The skew angle of a CPENTA 1st-order element is defined as the maximum skew angle
among its three quadrilateral faces and two triangular faces. Each quadrilateral face is
treated as a CQUAD4 element and each triangular face as a CTRIA3 element.

Vertex Angle

The same vertex angle check is performed for all of the faces, and each is treated as a
triangular (CTRIA3) or quadrilateral (CQUAD4) element. The minimum and maximum values
reported for the element.

Face Warpage

The face warpage of a CPENTA 1st-order element is defined as the maximum warpage
among the three quadrilateral faces, each treated as a CQUAD4 element.

Twist Angle

The twist angle is defined as the rotation of one triangular face with respect to the
opposite triangular face. The rotation is computed as follows: first construct a reference
plane perpendicular to the line connecting the centroids of the two triangular faces. The
three edges of each triangular are then projected to this reference plane. The maximum
angle between the corresponding edges of the two projected triangles is reported as the
twist angle of the CPENTA 1st-order element.

Edge Angle

The edge angle is the absolute value of the angle between two faces sharing a common
edge, subtracted from 90 degrees. For warped quadrilateral faces, the projected planes
defined by the plane vectors are used to compute the face normals (see definition of
reference plane for quadrilateral element or face), which are used in the angle calculation.
The edge angle of a CPENTA 1st-order is defined as the maximum edge angles in the
element.

CPENTA 2nd-order (15-noded) Element Checks

The following qualities of the CPENTA 2nd-order element are checked:

Aspect Ratio

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPENTA 1st-order element.

Altair Engineering OptiStruct 13.0 Reference Guide 2179

Proprietary Information of Altair Engineering


Face Skew Angle

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPENTA 1st-order element.

Vertex Angle

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPENTA 1st-order element.

Face Warpage

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPENTA 1st-order element.

Twist Angle

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPENTA 1st-order element.

Edge Angle

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPENTA 1st-order element.

Hoe Normal Offset

The hoe normal offset is the maximum of its edges normal offset values. See the definition
of hoe normal offset of 3-node edge.

Hoe Tangent Offset

The hoe tangent offset is the maximum of its edges tangent offset values. See the
definition of hoe tangent offset of 3-node edge.

CPENTA Default Bounds

Default values for Default values for Default values for


warning message error message validity check
Information
Lower Upper Lower Upper Lower Upper
Limit Limit Limit Limit Limit Limit

Aspect Ratio - 100.0 - 1000.0 - 1.0E5

Skew Angle - 60.0 - 75.0 - 90.0

Face Warp Angle - 30.0 - 60.0 - 180.0

Twist Angle - 30.0 - 75.0 - 90.0

Edge Angle - 75.0 - 87.0 - 90.0

2180 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Default values for Default values for Default values for
warning message error message validity check
Information
Lower Upper Lower Upper Lower Upper
Limit Limit Limit Limit Limit Limit

Hoe Normal Offset - 0.30 - 0.60 - 1.0E5

Hoe Tangent - 0.20 - 0.25 - 0.5


Offset

The values used for warning and error checks may be adjusted by the ELEMQUAL bulk data
entry, but validity checks are hard-coded.

Altair Engineering OptiStruct 13.0 Reference Guide 2181

Proprietary Information of Altair Engineering


Reference Plane for Quadrilateral Element or Face
In order to measure the distortion of the quadrilateral face of a solid element, a unique
reference plane is defined by two auxiliary plane vectors. The plane vectors are calculated
as:

PL1 = (V3 + V2 ) - (V1 + V4 )

PL2 = (V3 + V4 ) - (V1 + V2 )

where, V1, V2, V3, and V4 are the vectors that connect the four corner nodes with the
centroid of the quadrilateral. These two plane vectors and the centroid are then used to
construct the reference plane. These vectors of a non-warping quadrilateral face are shown
below:

2182 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CHEXA Element Checks and Default Bound Values

CHEXA 1st-order (8-noded) Element Checks

The following qualities of the CHEXA 1st-order element are checked:

Aspect Ratio

The aspect ratio of a CHEXA 1st-order element is defined as the maximum aspect ratio
among its six faces; each treated as a CQUAD4 element.

Face Skew Angle

The face skew angle of a CHEXA 1st-order element is defined as the maximum skew angle
among its six faces; each treated as a CQUAD4 element.

Vertex Angle

The same vertex angle check is performed for all of the faces, and each is treated as a
quadrilateral (CQUAD4) element. The minimum and maximum values reported for the
element.

Face Warpage

The face warpage of a CHEXA 1st-order element is defined as the maximum warpage
among its six faces; each treated as a CQUAD4 element.

Twist Angle

The twist angle of a CHEXA 1st-order element is defined as the maximum rotation of one
face with respect to its opposite face. The calculation is done as follows:

For each face, define two diagonal vectors as:

D1 = 0.25 * (PL1 + PL2)


D2 = 0.25 * (PL1 + PL2)

where, PL1 and PL2 are the place vectors of the face treated as CQUAD4. See the
definition of reference plane for quadrilateral element or face. The diagonal vectors for a
planar parallelogram can be show below:

Then, for each pair of opposing faces, a reference plane that is perpendicular to the axis
connecting the centroids of the faces is constructed. The diagonal vectors D1 and D2 of
each of the two opposite faces are projected onto this reference plane. The angles
between the projected and the projected are computed as t 1 and t 2. The
maximum of t 1 and t 2 is defined as the relative rotation between these two opposite faces
(TAF). Finally, the twist angle (TA) of a CHEXA 1st-order is calculated as the maximum
relative rotation of its three pairs of opposing faces.

Altair Engineering OptiStruct 13.0 Reference Guide 2183

Proprietary Information of Altair Engineering


Edge Angle

An edge angle is the absolute value of the angle between two faces sharing a common
edge, subtracted from 90 degrees. For warped faces, the projected planes are used to
compute the face normals used for the angle calculation. The edge angle of a CHEXA 1st-
order is defined as the maximum edge angle in the element.

CHEXA 1st-order Default Bounds

Default values for Default values for Default values for


warning message error message validity check
Information
Lower Limit Upper Limit Lower Limit Upper Limit Lower Limit Upper Limit

Aspect Ratio - 100.0 - 1000.0 - 1.0E5

2184 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Default values for Default values for Default values for
warning message error message validity check
Information
Lower Limit Upper Limit Lower Limit Upper Limit Lower Limit Upper Limit

Face Skew Angle - 60.0 - 75.0 - 90.0

Face Warp Angle - 30.0 - 60.0 - 180.0

Twist Angle - 30.0 - 90.0 - 180.0

Edge Angle - 60.0 - 85.0 - 90.0

CHEXA 2nd-order (20-noded) Element Checks

The following qualities of the CHEXA 2nd-order element are checked:

Aspect Ratio

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CHEXA 1st-order element.

Face Skew Angle

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CHEXA 1st-order element.

Vertex Angle

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CHEXA 1st-order element.

Face Warpage

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CHEXA 1st-order element.

Twist Angle

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CHEXA 1st-order element.

Edge Angle

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CHEXA 1st-order element.

Hoe Normal Offset

The hoe normal offset is the maximum of its edges normal offset values. See the definition
of hoe normal offset of 3-node edge.

Altair Engineering OptiStruct 13.0 Reference Guide 2185

Proprietary Information of Altair Engineering


Hoe Tangent Offset

The hoe tangent offset is the maximum of its edges tangent offset values. See the
definition of hoe tangent offset of 3-node edge.

CHEXA 2nd-order Default Bounds

Default values for Default values for Default values for


warning message error message validity check
Information
Lower Upper Lower Upper Lower Upper
Limit Limit Limit Limit Limit Limit

Aspect Ratio - 100.0 - 1000.0 - 1.0E5

Face Skew Angle - 60.0 - 75.0 - 90.0

Face Warp Angle - 30.0 - 60.0 - 180.0

Twist Angle - 30.0 - 75.0 - 180.0

Edge Angle - 60.0 - 89.0 - 90.0

Hoe Normal - 0.30 - 0.60 - 1.0E5


Offset

Hoe Tangent - 0.20 - 0.25 - 0.50


Offset

The values used for warning and error checks may be adjusted by the ELEMQUAL bulk data
entry, but validity checks are hard-coded.

2186 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CPYRA Element Checks and Default Bound Values

CPYRA 1st-order (5-noded) Element Checks

The following qualities of the CPYRA 1st-order element are checked:

Aspect Ratio

The aspect ratio of a CPYRA 1st-order element is defined as the maximum of the aspect
ratios of its four triangular faces and the quadrilateral base face. Each triangular face is
treated as a CTRIA3 element and the quadrilateral face as a CQUAD4 element.

Face Skew Angle

The face skew angle of a CPYRA 1st-order element is defined as the maximum of the skew
angles of its four triangular faces and the quadrilateral base face. Each triangular face is
treated as a CTRIA3 element and the quadrilateral face as a CQUAD4 element.

Vertex Angle

The same vertex angle check is performed for all of the faces, and each is treated as a
triangular (CTRIA3) or quadrilateral (CQUAD4) element. The minimum and maximum values
reported for the element.

Face Warpage

The face skew angle of a CPYRA 1st-order element is defined as the warpage of its
quadrilateral base face, which is treated as a CQUAD4 element.

CPYRA 2nd-order (13-noded) Element Checks

The following qualities of the CPYRA 2nd-order element are checked:

Aspect Ratio

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPYRA 1st-order element.

Face Skew Angle

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPYRA 1st-order element.

Vertex Angle

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPYRA 1st-order element.

Face Warpage

This quality is calculated using only the corner nodes. Its definition is the same as that
used for the CPYRA 1st-order element.

Altair Engineering OptiStruct 13.0 Reference Guide 2187

Proprietary Information of Altair Engineering


Hoe Normal Offset

The hoe normal offset is the maximum of its edges normal offset values. See the definition
of hoe normal offset of 3-node edge.

Hoe Tangent Offset

The hoe tangent offset is the maximum of its edges tangent offset values. See the
definition of hoe tangent offset of 3-node edge.

CPYRA Default Bounds

Default values for Default values for Default values for


warning message error message validity check
Information
Lower Upper Lower Upper Lower Upper
Limit Limit Limit Limit Limit Limit

Aspect Ratio - 100.0 - 1000.0 - 1.0E5

Skew Angle - 60.0 - 75.0 - 90.0

Face Warp Angle - 30.0 - 60.0 - 180.0

Hoe Normal Offset - 0.30 - 0.60 - 1.0E5

Hoe Tangent Offset - 0.20 - 0.25 - 0.5

The values used for warning and error checks may be adjusted by the ELEMQUAL bulk data
entry, but validity checks are hard-coded.

2188 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Material Property Check

In order to prevent analyses from being carried out on models with poor material definitions, a
material property check is incorporated into the pre-processing phase. The material property
check is controlled by the CHECKMAT parameter (see the PARAM input format).

There are several levels of requirements that material data needs to satisfy:

1. Symmetry requirements - These are assured by the input formats.

2. Mathematical requirements - These have to be satisfied so that the stiffness matrix can
be formulated at all, and are usually not very strict. For example, to avoid division by
zero, MAT1 in 3D must have n¹-1 and n¹0.5. Composite homogenization adds additional
mathematical requirements. Failure to meet these criteria will always result in an error
termination.

3. Stability requirements - By default, "semi-stability" combined with "not-all-zeros" stability


based on the following definitions is required:

Full stability - This means that the material is stable; when pulled it stretches rather
than shrinks, etc. For example, E>0 assures stability for a rod. In a mathematical
sense, stability assures that the stiffness matrix (with proper support) will be Semi-
Positive Definite (SPD).
Semi-stability - This is a slight extension of stability to include borderline cases such as
allowing E=0. It guarantees that the stiffness matrix (with proper support) will be
Semi-Positive Semi-Definite (SPSD). However, this can lead to infinite or very large
compliances.
Not all zeros - This is an additional requirement that at least one deformation mode of
the material is active (non-zero stiffness). This avoids element stiffness matrices that
are identically zero. However, It does not prevent infinite or very large compliances.
An error termination will occur if a material has negative stiffness.

A warning is produced if any individual mode of deformation has zero stiffness.

An error termination will occur if all modes of deformation have zero stiffness.

4. Consistency requirements - This is a requirement that user provided data be internally


consistent. For example, specifying E, G and Nu for isotropic material may lead to
inconsistent data.

5. Practical material requirements - These are requirements that correspond to typical


practical materials. For example, while stability requirements allow for negative Poisson's
ratio, the natural materials usually have positive n (although some composites and nano-
materials with negative n exist).

You may choose to perform only those checks that are necessary to avoid crashes in the
element routines (that is the Mathematical Requirement checks). This is facilitated through
the specification of PARAM,CHECKMAT,NO in the bulk data section of the input deck.

The checks performed for MAT1, MAT2, MAT3, MAT8, and MAT9 are outlined in the following
topics:
Material Property Checks for MAT1
Material Property Checks for MAT2

Altair Engineering OptiStruct 13.0 Reference Guide 2189

Proprietary Information of Altair Engineering


Material Property Checks for MAT3
Material Property Checks for MAT8
Material Property Checks for MAT9

2190 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Material Property Checks for MAT1

In addition to the property requirements, there are usage and recalculation rules for MAT1
data.

Usage Rules for MAT1 Data

Element Type E G n

ROD, BEAM, Used for bending and Used for torsion. Unused.
BAR tension.

QUAD, TRIA Used in combination with Used for transverse Used in combination with
n for bending and shear. E for bending and
membrane. membrane.

SOLID Used in combination with Unused. Used in combination with


n. n.

Recalculation Rules for MAT1

In cases when not all material parameters are given for MAT1, here are the recalculation rules
for the remaining parameters. Note that in cases of two prescribed parameters, this is
obvious; while in cases of a single prescribed parameter, you are making an assumption as to
which one is assumed to be zero.

Given Mean

E G n E G n

given given as given G = E / 2(1 + n) as given

given given as given as given n = E/2G - 1

given given E = 2G(1 + n) as given as given

given as given 0.0 0.0

given 0.0 as given 0.0

given not allowed

Altair Engineering OptiStruct 13.0 Reference Guide 2191

Proprietary Information of Altair Engineering


Material Requirements for MAT1

The property requirements on MAT1 vary depending on whether it is used for 1D, 2D, or 3D
elements. The details are provided in the table below.

Material MAT1 - 1D MAT1 - 2D MAT1 - 3D


Requirements

Mathematical n = -1 results in error n = -1 or n = 1 n = -1 or n = 0.5


termination. results in error results in error
termination. termination.

Semi-stability E < 0 or G < 0 results E < 0, G < 0, n < -1 E < 0, n < -1, or n >
in error termination. > or -n > 0.5 results 0.5 results in error
in error termination. termination.
PARAM,CHECKMAT,NO
will disable this error. PARAM,CHECKMAT,N PARAM,CHECKMAT,N
O will disable this O will disable this
n < -1 or n > 0.5 error. error.
results in a warning
(however, this is
unused in 1D).

Not all zeros If both E = 0 and G = If both E = 0 and G E < 0 results in error
0, an error termination = 0, an error termination.
occurs. termination occurs.

If either E = 0 or G = If either E = 0 or G =
0, a warning is given. 0, a warning is
given.

Consistency A warning is provided A warning is provided A warning is

n). / 2(1 + n).

Mathematical for After


composites homogenization, if
either E = 0 or G =
0, an error
termination occurs.

2192 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Material Property Checks for MAT2

MAT2 only applied to 2D elements.

Material Requirements MAT2

Mathematical none

Semi-stability If any eigenvalues of [G] < 0, an error termination will occur.

PARAM,CHECKMAT,NO will disable this error.

Not all zeros If all eigenvalues of [G] = 0, an error termination will occur.

If any eigenvalue of [G] = 0, a warning is provided.

Consistency none

Mathematical for After homogenization, if Det[G] = 0, an error termination will


composites occur.

Altair Engineering OptiStruct 13.0 Reference Guide 2193

Proprietary Information of Altair Engineering


Material Property Checks for MAT3

MAT3 only applies to axisymmetric elements.

Material Requirements MAT3

Mathematical If EX = 0, ETH = 0, EZ = 0 or

NUXTH * NUTHX + NUTHZ * NUZTH + NUZX * NUXZ + 2 *


NUXTH * NUTHZ * NUZX = 1,

an error termination will occur (See comment 1).

Semi-stability If EX < 0, ETH < 0, EZ < 0 or GZX < 0, an error termination


will occur.

PARAM,CHECKMAT,NO will disable this error.

Not all zeros If GZX = 0, a warning is provided.

Consistency none

Comments

1. By substitution of

into

NUXTH * NUTHX + NUTHZ * NUZTH + NUZX * NUXZ + 2 * NUXTH * NUTHZ * NUZX = 1,

it can be expressed in terms of

2194 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Material Property Checks for MAT8

MAT8 only applies to 2D elements.

Material Requirements MAT8

Mathematical If n1 2 *n2 1 = 1, an error termination will occur (See comment


1).

Semi-stability E1 < 0, E2 < 0, G1 2 < 0, G1 ,Z < 0, or G2 ,Z < 0 will result in an


error termination.

PARAM,CHECKMAT,NO will disable this error.

Not all zeros If E1 = 0, E2 = 0 , and G1 2 = 0, an error termination will


occur.

If E1 = 0, E2 = 0 , or G1 2 = 0, a warning is provided.

Consistency E1 *n2 1 = E2 *n1 2 is assured as only n12 is input.

Mathematical for After homogenization, if Det[G] = 0, an error termination will


composites occur.

Comments

1. By substitution of E1*n21 = E2*n12 into n12*n21 = 1, it can be expressed in terms of


n12*n12*E2/E1 = 1.

Altair Engineering OptiStruct 13.0 Reference Guide 2195

Proprietary Information of Altair Engineering


Material Property Checks for MAT9

MAT9 only applies to 3D elements.

Material Requirements MAT9

Mathematical none

Semi-stability If any eigenvalues of [G] < 0, an error termination will occur.

PARAM,CHECKMAT,NO will disable this error.

Not all zeros If all eigenvalues of [G] = 0, an error termination will occur.

If any eigenvalue of [G] = 0, a warning is provided.

Consistency none

2196 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Output Data

Descriptions for individual output files can be accessed by selecting from the links for each
entry, listed below in groups according to type and alphabetically on the Files Created by
OptiStruct page.

The filenames listed on this page contain only the tail part of the name. For most files, the
full filename is controlled by the OUTFILE command (ASSIGN,OUTFILE), and in the absence of
OUTFILE, they use the root of input filename. Unless otherwise noted for a specific file type
(.#.eigv), all output files have the same root and are located in the same folder. The only
exception is <BODY_NAME>.h3d; these files may not have a common root in the filename.

HyperMesh OptiStruct

.amls_singularity.cmf file .#.asens file


.HM.comp.cmf file .#.eigv file
.HM.conn.cmf file .#.sens file
.HM.elcheck.cmf file .#.grid file
.HM.elcheck.###.cmf file .#.sh file
.HM.ent.cmf file .cstr file
.HM.gapstat.cmf file .dens file
.res file .disp file
.dvgrid file
HyperView/HyperGraph .echo file
.#.h3d file .force file
.h3d file .fsthick file
.hgdata file .gpf file
_des.h3d file .grid file
_freq.mvw file .hist file
_gauge.h3d file .interface file
_hist.mvw file .load file
_mass.mvw file .mass file
_modal.#.mvw file .mpcf file
_modal.mvw file .out file
_rand.mvw file .pret file
_topol.h3d file .prop file
_tran.mvw file .rand file
_s#.h3d file .seplot file
_sens.#.mvw file .sh file

Altair Engineering OptiStruct 13.0 Reference Guide 2197

Proprietary Information of Altair Engineering


_freq.#.mvw file .spcd file
_mass.#.mvw file .spcf file
.stat file
Nastran .strn file
.k.op2 file .strs file
.m.op2 file _err.grid file
.op2 file _s#_a.frf file
.pch file _s#_a.mbd file
.peak file _s#_a.trn file
_s#_d.frf file
OSSmooth _s#_d.mbd file

.oss file _s#_d.trn file


_s#_v.frf file
Multi-body Dynamics _s#_v.mbd file

_mbd.h3d file _s#_v.trn file

_mbd.log file .#.#.fat file

_mbd.mrf file .#.mass file

_mbd.mvw file .desvar file

_mbd.xml file .pcomp file

<BODY_NAME>.h3d file _s#_a.#.frf file

.mnf file _s#_d.#.frf file


_s#_v.#.frf file
_shuffling.#.fem file
_sizing.#.fem file

Patran Alternative Patran

.#.#.#.dis file .#.#.dis.# file


.#.#.dis file .#.dis.# file
.#.#.els file .#.els.# file
.#.dis file .dis.# file
.#.els file .els.# file

HTML
Microsoft Excel

2198 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.html file .#.slk file
_frames.html file
_gso.slk file
_menu.html file

Altair Engineering OptiStruct 13.0 Reference Guide 2199

Proprietary Information of Altair Engineering


List of Files Created by OptiStruct (Alphabetical)

The filenames listed on this page contain only the tail part of the name. For most files, the
full filename is controlled by the OUTFILE command (ASSIGN,OUTFILE), and in the absence of
OUTFILE, they use the root of input filename. Unless otherwise noted for a specific file type
(.#.eigv), all output files have the same root and are located in the same folder. The only
exception is <BODY_NAME>.h3d; these files may not have a common root in the filename.
.#.#.#.dis file
.#.#.dis file
.#.#.dis.# file
.#.#.els file
.#.#.fat file
.#.asens file
.#.dis file
.#.dis.# file
.#.eigv file
.#.els file
.#.els.# file
.#.grid file
.#.h3d file
.#.mass file
.#.sens file
.#.sh file
.#.slk file
.amls_singularity.cmf file
.cntf file
.contgap.fem file
.cstr file
.dens file
.desvar file
.dis.# file
.disp file
.dvgrid file
.echo file
.els.# file
.force file
.fsthick file
.gpf file
.grid file

2200 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.h3d file
.hgdata file
.hist file
.HM.comp.cmf file
.HM.conn.cmf file
.HM.elcheck.cmf file
.HM.elcheck.###.cmf file
.HM.ent.cmf file
.HM.gapstat.cmf file
.html file
.interface file
.k.op2 file
.load file
.m.op2 file
.mass file
.mnf file
.mpcf file
.op2 file
.oss file
.out file
.pch file
.pcomp file
.peak file
.pret file
.prop file
.rand file
.res file
.seplot file
.sh file
.spcd file
.spcf file
.stat file
.strn file
.strs file
_des.h3d file
_err.grid file
_frames.html file
_freq.#.mvw file

Altair Engineering OptiStruct 13.0 Reference Guide 2201

Proprietary Information of Altair Engineering


_freq.mvw file
_gauge.h3d file
_gso.slk file
_hist.mvw file
_mass.#.mvw file
_mass.mvw file
_mbd.h3d file
_mbd.log file
_mbd.mrf file
_mbd.mvw file
_mbd.xml file
_menu.html file
_modal.#.mvw file
_modal.mvw file
_rand.mvw file
_s#.h3d file
_s#_a.#.frf file
_s#_a.frf file
_s#_a.mbd file
_s#_a.trn file
_s#_d.#.frf file
_s#_d.frf file
_s#_d.mbd file
_s#_d.trn file
_s#_v.#.frf file
_s#_v.frf file
_s#_v.mbd file
_s#_v.trn file
_sens.#.mvw file
_shuffling.#.fem file
_sizing.#.fem file
_topol.h3d file
_tran.mvw file
<BODY_NAME>.h3d file

2202 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.#.#.#.dis file

The .#.#.#.dis file is a Patran 2.5 ASCII format results file.

File Creation

This file is created when the PATRAN format is chosen and normal modes analyses are
performed. (See documentation for the I/O Option FORMAT).

File Contents

Result Description

Eigenvector Eigenvector results from normal modes analyses. Output is


controlled by the I/O Option DISPLACEMENT.

Comments

1. One such file is created for each calculated mode at each iteration where the I/O Option
RESULTS requests analytical results to be output.

2. The first # in the file name is the iteration number.

3. The second # in the file name is the user-defined Subcase ID.

4. The third # in the file name is the mode number.

Altair Engineering OptiStruct 13.0 Reference Guide 2203

Proprietary Information of Altair Engineering


.#.#.dis file

The .#.#.dis file is a Patran 2.5 ASCII format results file.

File Creation

This file is created when the PATRAN format is chosen and linear static analysis is performed.
(See documentation for the I/O Option FORMAT).

File Contents

Result Description

Displacement Displacement results from linear static analysis. Output is


controlled by the I/O Option DISPLACEMENT.

Comments

1. One such file is created for each subcase at each iteration where the I/O Option RESULTS
requests analytical results to be output.

2. The first # in the file name is the iteration number.

3. The second # in the file name is the user-defined Subcase ID.

2204 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.#.#.dis.# file

The .#.#.dis.# file is a Patran 2.5 ASCII format results file.

File Creation

This file is created when the APATRAN format is chosen and normal modes analyses are
performed. (See documentation for the I/O Option FORMAT).

File Contents

Result Description

Eigenvector Eigenvector results from normal modes analyses. Output is controlled


by the I/O Option DISPLACEMENT.

Comments

1. One such file is created for each calculated mode at each iteration where the I/O Option
RESULTS requests analytical results to be output.

2. The first # in the file name is the user-defined Subcase ID.

3. The second # in the file name is the mode number.

4. The third # in the file name is the iteration number.

Altair Engineering OptiStruct 13.0 Reference Guide 2205

Proprietary Information of Altair Engineering


.#.#.els file

The .#.#.els file is a Patran 2.5 ASCII format results file.

File Creation

This file is created when the PATRAN format is chosen and linear static analysis is performed.
(See documentation for the I/O Option FORMAT).

File Contents

Result Description

Stress Stress results from linear static analysis. Output is controlled by the I/O
Option STRESS (or ELSTRESS).

Comments

1. One such file is created for each subcase at each iteration where the I/O Option RESULTS
requests analytical results to be output.

2. The first # in the file name is the iteration number.

3. The second # in the file name is the user-defined Subcase ID.

2206 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.#.#.fat file

The .#.#.fat file is an ASCII format result file.

File Creation

This file is created for fatigue analysis and optimization.

File Contents

This file contains the average fatigue life/damage, top five damaged elements, and the
detailed damage information (contribution from each static loadcase).

Comments

1. The first # in the file name is the iteration number.

2. The second # in the file name is the user-defined fatigue subcase ID.

3. If a fatigue optimization is performed, this file is created for each fatigue subcase at the
first and last iterations.

Altair Engineering OptiStruct 13.0 Reference Guide 2207

Proprietary Information of Altair Engineering


.#.asens file

The .#.asens file is an OptiStruct ASCII format results file.

File Creation

This file is created when an optimization is performed. Creation of this file is controlled by the
I/O option OUTPUT.

File Contents

The file contains sensitivity information for all responses with respect to topology design
variables (density) at a given iteration (denoted by the # in the file name).

File Format

The sensitivities are listed in a single column and are grouped by response. A blank line
separates each response grouping.

Comments

1. The # in the file name is the iteration number.

2208 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.#.dis file

The .#.dis file is a Patran 2.5 ASCII format results file.

File Creation

This file is created when the PATRAN format is chosen and shape or topography design
variables are present. (See documentation for the I/O Option FORMAT).

File Contents

Result Description

Shape Shape results from topography or shape optimizations. Output is


controlled by the I/O Option DENSRES.

Comments

1. One such file is created for each iteration where the I/O Option DENSRES requests
topography or shape results to be output.

2. The # in the file name is the iteration number.

Altair Engineering OptiStruct 13.0 Reference Guide 2209

Proprietary Information of Altair Engineering


.#.dis.# file

The .#.dis.# file is a Patran 2.5 ASCII format results file.

File Creation

This file is created when the APATRAN format is chosen and linear static analysis is performed.
(See documentation for the I/O Option FORMAT).

File Contents

Result Description

Displacement Displacement results from linear static analysis. Output is controlled


by the I/O Option DISPLACEMENT.

Comments

1. One such file is created for each subcase at each iteration where the I/O Option RESULTS
requests analytical results to be output.

2. The first # in the file name is the user-defined Subcase ID.

3. The second # in the file name is the iteration number.

2210 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.#.eigv file

The _#.eigv file is an OptiStruct binary data file.

File Creation

This file is created by the subcase information entry EIGVSAVE. The prefix for the file name is
controlled by the I/O option EIGVNAME.

File Contents

Result Description

Eigenvalue Eigenvalue results from normal modes analyses.

Comments

1. This file is used to store eigenvalue results from normal modes analyses for retrieval by
modal frequency response subcases. The EIGVRETRIEVE subcase information entry is
used to retrieve values from this file.

2. The # in the file name is the integer argument given to EIGVSAVE.

Altair Engineering OptiStruct 13.0 Reference Guide 2211

Proprietary Information of Altair Engineering


.#.els file

The .#.els file is a Patran 2.5 ASCII format results file.

File Creation

This file is created when the PATRAN format is chosen and topology design variables are
present. (See documentation for the I/O Option FORMAT).

File Contents

Result Description

Density Density results from topology optimizations. Output is controlled by the


I/O Option DENSRES.

Comments

1. One such file is created for each iteration where the I/O Option DENSRES requests
topology results to be output.

2. The # in the file name is the iteration number.

2212 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.#.els.# file

The .#.els.# file is a Patran 2.5 ASCII format results file.

File Creation

This file is created when the APATRAN format is chosen and linear static analysis is performed.
(See documentation for the I/O Option FORMAT).

File Contents

Result Description

Stress Stress results from linear static analysis. Output is controlled by the I/O
option STRESS (or ELSTRESS).

Comments

1. One such file is created for each subcase at each iteration where the I/O option RESULTS
requests analytical results to be output.

2. The first # in the file name is the user-defined Subcase ID.

3. The second # in the file name is the iteration number.

Altair Engineering OptiStruct 13.0 Reference Guide 2213

Proprietary Information of Altair Engineering


.#.grid file

The .#.grid file is an OptiStruct ASCII format results file.

File Creation

This file is created when topography or shape optimization is performed. Output of this file is
controlled by the I/O Option SHRES.

File Contents

Result Description

Nodal locations The nodal coordinates of the model at iteration # of the


optimization.

File Format

The file uses the following format for each grid in the model:

GRID Id Cp X1 X2 X3 Cd Ps

where:

GRID identifies this as a GRID card image.

Id is the unique grid point identification number.

Cp is blank.

X1, X2, X3 provide the location of the grid point in the global coordinate
system.

Cd is the identification number of the coordinate system in which the


displacements, degrees-of-freedom, constraints, and solution
vectors are defined at the grid point.

Ps is the SPC associated with the grid.

Comments

1. The # in the file name is the iteration number.

2214 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.#.h3d file

The .#.h3d files are compressed binary files, containing model, analysis, and optimization
result data. They can be used to post-process results in HyperView or when using the
HyperView Player.

File Creation

The .#.h3d files are created when the OUTPUT, H3D, <frequency>, BYITER output option is
present and an optimization is performed.

File Contents

The .#.h3d files contain node and element definitions. In the case of shape optimization, the
model is updated to the shape of the respective iteration. The following results are included:

Result Description

Acceleration Acceleration results from frequency response, transient


response, and multi-body dynamics analyses.

Output is controlled by the I/O option ACCELERATION.

Composite ply strain Ply strain results for composite materials from static
analyses.

Output is controlled by the I/O option STRAIN and by the


SOUTi field on the PCOMP definition.

Composite ply stress Ply stress results for composite materials from static and
analyses.

Output is controlled by the I/O option STRESS and by the


SOUTi field on the PCOMP definition.

Composite failure indices Failure indices for composite materials from static
analyses.

Output is controlled by the I/O option STRESS, by the


SOUTi, SB and FT fields on the PCOMP definition and by
the related fields on the relevant material definition (see
MAT1, MAT2, MAT8).

Density Density results from topology optimizations.

Output is controlled by the I/O option DENSITY.

Altair Engineering OptiStruct 13.0 Reference Guide 2215

Proprietary Information of Altair Engineering


Result Description

Displacement Displacement results from static, frequency response,


transient response, and multi-body dynamics analyses.

Output is controlled by the I/O option DISPLACEMENT.

Eigenvector Eigenvector results from normal modes and linear buckling


analyses.

Output is controlled by the I/O option DISPLACEMENT.

Element force Element force results from static, frequency response,


acoustic, and transient response analyses.

Output is controlled by the I/O option FORCE (or


ELFORCE).

Element strain energy Element strain energy results from static and normal
modes analyses.

Output is controlled by the I/O option ESE.

Grid point stress Grid point stress results for 3D elements from static
analyses.

Output is controlled by the I/O option GPSTRESS (or


GSTRESS).

Shape Shape results from topography or shape optimizations.

Output is controlled by the I/O option SHAPE.

Single-point force of Single-point force of constraint results from static


constraint analyses.

Output is controlled by the I/O option SPCFORCE.

Strain Strain results from static, frequency response, transient


response, and multi-body dynamics analyses. Output is
controlled by the I/O option STRAIN.

Stress Stress results from static, frequency response, transient


response, and multi-body dynamics analyses.

2216 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Result Description

Output is controlled by the I/O option STRESS (or


ELSTRESS).

Thickness Thickness results from size and topology optimizations.

Output is controlled by the I/O option THICKNESS.

Velocity Velocity results from frequency response, transient


response, and multi-body dynamics analyses.

Output is controlled by the I/O option VELOCITY.

Comments

1. The # in the file name is the iteration number.

2. Grid point stresses are output for the entire model and for each individual component.
This allows grid point stresses to be accurately obtained at the interface of two
components referencing different material definitions.

Altair Engineering OptiStruct 13.0 Reference Guide 2217

Proprietary Information of Altair Engineering


.#.mass file

The .#.mass file is an ASCII format results file.

File Creation

This file is created when modal optimization is performed and OUTPUT,HGEFFMASS is


presented.

File Contents

This file contains the total effective mass fraction.

File Format

The file is formatted into blocks separated by blank lines. Each block represents a modal
subcase. The subcases are in order of occurrence in the input deck.

Each block contains six columns and a number of rows. The number of rows is equal to the
number of requested modes for this subcase. The columns, from left to right, contain the
total effective mass fraction for X-translation, Y-translation, Z-translation, X-rotation, Y-
rotation, and Z-rotation. The summary of each column is 100%.

Comments

1. The # in the file name is the iteration number.

2. This file is used by the _mass.#.mvw session file which automatically creates bar charts
for the results.

2218 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.#.sens file

The .#.sens file is an OptiStruct ASCII format results file.

File Creation

This file is created when an optimization is performed. Creation of this file is controlled by the
I/O Option OUTPUT.

File Content

The file contains sensitivity information for all responses to size and shape design variables at
a given iteration (denoted by the # in the file name).

File Format

The sensitivities are listed in a single column and are grouped by response. A blank line
separates each response grouping.

Comments

1. The # in the file name is the iteration number.

2. The _sens.#.mvw HyperView script file automatically creates histogram plots for the
results contained in this file.

Altair Engineering OptiStruct 13.0 Reference Guide 2219

Proprietary Information of Altair Engineering


.#.sh file

The .#.sh file is an OptiStruct ASCII format results file.

File Creation

This file is created when an optimization is performed. Output of this file is controlled by the
I/O Option SHRES.

File Contents

Contains information necessary to restart the optimization from a given iteration.

Comments

1. The # in the file name is the iteration number.

2220 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.#.slk file

The .slk file is a Microsoft Excel SYLK Format results file.

File Creation

This file is only created when size or shape optimization is performed. Output of this file is
controlled by the SENSITIVITY and SENSOUT I/O options.

File Contents

The file contains sensitivity information for size and shape design variables.

File Format

The only values that can be changed in this file are those listed in the "New" column. All
other values are either fixed or their calculation is fixed. When the .slk file is created, the
values in the "New" column match those in the "Reference" column. These values may be
adjusted, but should always remain within the design variable's bounds.

Each size and shape design variable in the model is listed in the left-hand column of the
sensitivity table. Information concerning a particular design variable is given in the row where
its label is listed. The current value and the upper and lower bounds of the design variables
are given in the columns, "Reference," "Lower," and "Upper" respectively.

Each referenced response in the model has its own column. These response columns are on
the right-hand side of the sensitivity table. The calculated sensitivity of a response to
changes in a design variable at the current iteration is given in the row corresponding to that
design variable and the column corresponding to that response.

Beneath the list of design variables, in the left-hand column, are the headings "Response lower
bound," "Response reference," and "Response upper bound". If a response is constrained, the
constraint value will be given in either the "Response lower bound" or the "Response upper
bound" row of the column corresponding to that response. The value given in the "Response
reference" row is the calculated value of the response using the design variable reference
values.

At the bottom of the left-hand column are the headings: "Response linear," "Response
reciprocal," and "Response conservative". The response values in these rows are the
predicted values of the responses for three different approximations. Initially, these values
will match one another and the "Response reference" value for each response. This is
because these are the predicted values of the response at the given variable settings, which
initially are the same settings used to calculate the "Response reference" value. Once the
design variable values in the "New" column are altered, these values will change.

The "Response linear" row predicts the response value using linear approximation. This is
calculated as:

where:

Altair Engineering OptiStruct 13.0 Reference Guide 2221

Proprietary Information of Altair Engineering


R1 is the predicted response value.

R0 is the response reference value.

are the new values of the design variables.

are the reference values of the design variables.

are the sensitivities of the response to the design variables.

The "Response reciprocal" row predicts the response value using reciprocal approximation.
This is calculated as:

where:

R1 is the predicted response value.

R0 is the response reference value.

are the new values of the design variables.

are the reference values of the design variables.

are the sensitivities of the response to the design variables.

The "Response conservative" row predicts the response value using a combination of the
above approximations where linear approximation is used, when the sensitivity is positive, and
reciprocal approximation is used when the sensitivity is negative. Therefore, if all sensitivities
are positive, the conservative prediction will match the linear prediction. If all sensitivities are
negative, it will match the reciprocal prediction, but if there is a mixture of positive and
negative sensitivities for a given response then the conservative prediction will match neither
the linear nor the reciprocal prediction.

The normalized values simply show the predicted response as a fraction of the response
reference value.

2222 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Comments

1. The # in the file name refers to the iteration number.

Altair Engineering OptiStruct 13.0 Reference Guide 2223

Proprietary Information of Altair Engineering


.amls_singularity.cmf file

The .amls_singularity.cmf file is a HyperMesh command file.

File Creation

This file is created when an AMLS run is performed and singular grid points are detected by
AMLS.

File Contents

This file contains a list of GRID point identification numbers which are found to be singular
during an AMLS run.

Format
*entitysetcreate("^AMLS singular grids",nodes,#)

*createmark(nodes,#)

List of GRID Identification numbers

*entitysetupdate("^AMLS singular grids",nodes,#)

Comments

1. Verify that the corresponding model is loaded in HyperMesh when executing the command
file.

2224 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.cntf file

The .cntf file is an OptiStruct ASCII format results file.

File Creation

This file is created when the OPTI format is selected in the CONTF I/O Options Entry for
nonlinear quasi-static analysis (NLSTAT) runs.

File Contents

Result Description

Contact Forces Contact force results from nonlinear quasi-static analysis (with
contact) runs. Output is controlled by the I/O option CONTF.

File Format

The .cntf file has the following format:

For each iteration, the following header is used:

iter Iteration Numel

where:

iter is a keyword identifying that the next field is the iteration number.

Iteration is the Iteration number.

Numel is the total number of nonlinear quasi-static subcases (with


contact) in the entire model.

Within the iteration section, the following information is provided for each subcase:

SUBCASE: <Subcase ID> <Number of Contact Interfaces>

LOAD: <Load ID>

LABEL: <Label>

CONTACT INTERFACE: TOTAL FORCE ACTING ON MASTER SURFACE (BASIC SYSTEM)

CONTACT# FORCE-X FORCE-Y FORCE-Z MAGNITUDE

Altair Engineering OptiStruct 13.0 Reference Guide 2225

Proprietary Information of Altair Engineering


where:

CONTACT# is the Contact Interface identification number (CTID on the


CONTACT Bulk Data Entry).

FORCE-X is the component of the total contact force along the X-axis
of the Basic System.

FORCE-Y is the component of the total contact force along the Y-axis
of the Basic System.

FORCE-Z is the component of the total contact force along the Z-axis
of the Basic System.

MAGNITUDE is the magnitude of the total contact force acting on the


Master Surface

2226 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.contgap.fem file

The .contgap.fem file is an ASCII format file. It is used to visualize the internally created
contact elements. The contact elements are presented as CGAPG elements.

File Creation

This file is created when CONTPRM,CONTGAP,YES is used.

File Contents

The file contains CGAPG elements, PGAP properties, and the auxiliary GRIDs for contact
visualization.

File Format

The formats of GRID, CGAPG, and PGAP are the same as for the bulk data entries.

Comments

1. To visualize the configuration of the contact elements, load the original FEA model in
HyperMesh and import this file. Ensure that the FE overwrite option is turned on in the
import panel.

2. During optimization, this file contains the contact elements at the latest iteration. To
visualize this configuration correctly for shape optimization, the shape of the FEA model
should be updated by applying shape change results.

3. The parameter GAPPRM,GPCOINC is automatically included in this file.

Altair Engineering OptiStruct 13.0 Reference Guide 2227

Proprietary Information of Altair Engineering


.cstr file

The .cstr file is an OptiStruct ASCII format results file.

File Creation

This file is created when the OPTI, OS or BOTH formats are chosen. (See documentation for
the I/O options FORMAT and OUTPUT).

File Contents

Result Description

Composite stress or strain Composite stress and strain results from linear static.
Output is controlled by the I/O options CSTRESS or
CSTRAIN. On PCOMP, SOUT=YES needs to be selected.

File Format

The composite stress file format is self-explanatory. It gives the stress, strain and composite
failure for each element and its plies.

Comments

1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.

2228 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.dens file

The .dens file is an OptiStruct ASCII format results file.

File Creation

This file is created when the OPTI, OS or BOTH formats are chosen and a topology
optimization is performed. (See documentation for the I/O options FORMAT and OUTPUT).

File Contents

Result Description

Density Density results from topology optimizations. Output is controlled by the


I/O option DENSRES.

File Format

The density file has the following format:

For each iteration, the following header is used:

iter Iteration Numel

where:

iter is a keyword identifying that the next field is the iteration number.

Iteration is the Iteration number.

Numel is the total number of elements in entire model.

Within the iteration section, the following information is provided for each element:

EID Mat_dens

where:

EID is the element identification number.

Altair Engineering OptiStruct 13.0 Reference Guide 2229

Proprietary Information of Altair Engineering


Mat_dens is the element material density. Non-design elements are
assigned a material density of 1.0.

2230 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.desvar file

The .desvar file is an ASCII format result file.

File Creation

This file is created when OUTPUT,DESVAR is requested in size or shape optimization.

File Contents

This file contains the updated design variables at last iteration.

File Format

The format for design variable output is the same as for the bulk data entries.

Altair Engineering OptiStruct 13.0 Reference Guide 2231

Proprietary Information of Altair Engineering


.dis.# file

The .dis.# file is a Patran 2.5 ASCII format results file.

File Creation

This file is created when the APATRAN format is chosen and shape or topography design
variables are present. (See documentation for the I/O options FORMAT and OUTPUT).

File Contents

Result Description

Shape Shape results from topography or shape optimizations. Output is controlled


by the I/O option DENSRES.

Comments

1. One such file is created for each iteration where the I/O option DENSRES requests
topography or shape results to be output.

2. The # in the file name is the iteration number.

2232 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.disp file

The .disp file is an OptiStruct ASCII format results file.

File Creation

This file is created when the OPTI, OS or BOTH formats are chosen. (See documentation for
the I/O options FORMAT and OUTPUT).

File Contents

Result Description

Acceleration Acceleration results from frequency response analyses. Output is


controlled by the I/O option ACCELERATION.

Displacement Displacement results from linear static, inertia relief, and frequency
response analyses. Output is controlled by the I/O option
DISPLACEMENT.

Eigenvector Eigenvector results from normal modes and linear buckling analyses.
Output is controlled by the I/O option DISPLACEMENT.

Velocity Velocity results from frequency response analyses. Output is


controlled by the I/O option VELOCITY.

File Format

The displacement file has the following format:

For each iteration, the following header is used:

iter Iteration Numids

where:

iter is a keyword identifying that the next field is the iteration


number.

Iteration is the iteration number.

Numids is the number of linear static subcases plus the number of


calculated normal and buckling modes.

Altair Engineering OptiStruct 13.0 Reference Guide 2233

Proprietary Information of Altair Engineering


Within the iteration section, the following header is used for each linear static subcase,
normal or linear buckling mode, or direct modal frequency response:

LCID Numnod Freq Result: SPCcase (Datatype)

where:
LCID is the output ID for the subcase or mode. This is not
necessarily the same as the subcase ID defined in the input
data.

Numnod is the number of grids in the model.

Freq is the frequency or Buckling eigenvalue (1.0 for static


subcases).

Result is a keyword declaring the result type given.

DISP indicates displacement result.

VELO indicates a velocity result (for frequency response


analysis only).

ACCE indicates an acceleration result (for frequency response


analysis only).

SPCcase is the SPC set identification number for linear static, inertia
relief, or frequency response subcases or 1 for eigenvectors.

Datatype is a keyword indicating the type of subcase involved.

(LOAD) declares data is from a static subcase.

(EIGV) declares data is from a normal modes subcase.

(BKLV) declares data is from a linear buckling subcase.

(DFRQ) declares data is from a direct frequency response


subcase.

(MFRQ) declares data is from a modal frequency response


subcase.

2234 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Within the subcase or mode section, the following information is provided for each
node:

NID X disp Y disp Z disp

where:
NID is the node identification number.

X is the X displacement of the node.

Y is the Y displacement of the node.

Z is the Z displacement of the node.

Comments

1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.

Altair Engineering OptiStruct 13.0 Reference Guide 2235

Proprietary Information of Altair Engineering


.dvgrid file

The .dvgrid file is an OptiStruct ASCII format results file.

File Creation

This file is only created when an analysis is performed. Creation of this file is controlled by
the I/O Option OUTPUT.

File Contents

The file contains shape variable definitions for the displacements or eigenvectors resulting
from linear static, inertia relief, or normal modes analyses.

File Format

DESVAR and DVGRID definitions are provided for each linear static subcase and for each
calculated normal mode.

Output for linear static subcases begins with a header in the following format:

$
$ DESVAR and DVGRIDs for static load case subcase_id
$

where:

subcase_id is the user-defined subcase identification number.

Output for calculated normal modes begins with a header in the following format:

$
$ DESVAR and DVGRIDs for eigenvalue load case subcase_id, Mode Number
mode_number
$

where:

subcase_id is the user-defined subcase identification number.

mode_number is the mode number.

The DESVAR and DVGRID definitions are formatted as per the bulk data descriptions.

2236 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.echo file

The .echo file is an OptiStruct input file.

File Creation

Creation of this file is controlled by the I/O option ECHO = PUNCH.

File Contents

The file represents a copy of the input deck in a form suitable to use for another solution
which, when used with the same subcase information and I/O options entries, should generate
identical results (round off error may be noticeable if the original input deck uses large field
format).

Altair Engineering OptiStruct 13.0 Reference Guide 2237

Proprietary Information of Altair Engineering


.els.# file

The .els.# file is a Patran 2.5 ASCII format results file.

File Creation

This file is created when the APATRAN format is chosen and topology design variables are
present. (See documentation for the I/O options FORMAT and OUTPUT).

File Contents

Result Description

Density Density results from topology optimizations. Output is controlled by the


I/O option DENSRES.

Comments

1. One such file is created for each iteration where the I/O option DENSRES requests
topology results to be output.

2. The # in the file name is the iteration number.

2238 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.force file

The .force file is an OptiStruct ASCII format results file.

File Creation

Creation of this file is controlled by the FORCE (ELFORCE) I/O option.

File Contents

Result Description

Force Force results from linear static analysis for ELAS (CELAS1, CELAS2,
CELAS3, CELAS4), ROD (CROD), BAR (CBAR, CBEAM), BUSH (CBUSH),
PLATE (CQUAD, CTRIA), and GAP (CGAP) elements.

File Format

The file is divided up by iteration. Output from each iteration starts with a line in the following
format:

ITER Iteration_number Number_of_subcases

where:

ITER is a keyword denoting the beginning of a new iteration.

Iteration_number is the Iteration number.

Number_of_subcases is the number of subcases for which this output is created.

Each iteration section is divided up by subcase. Output for each subcase starts with a line in
the following format:

Id Number_of_elements Frequency LOAD:Spc_id(Datatype)


subcase_label

where:

ID is the output identification number for the subcase.


This is not the same as the subcase ID used in the input data.

Number_of_elem is the number of elements for which this output is requested.


ents

Frequency is 1.0 for static analysis.

Altair Engineering OptiStruct 13.0 Reference Guide 2239

Proprietary Information of Altair Engineering


LOAD is a keyword declaring applied load information.

Spc_id is the SID for SPC's referenced by this subcase.

(Datatype) is a keyword indicating the type of subcase involved.

(LOAD) declares data is for a linear static subcase.

Each subcase section is divided up by element-type. Output for each element-type section
starts with one of the following formats (depending on the elements present in the model):

ELAS # FORC E

ROD# FORC E-A FORC E-B

BUSH# F-X F-Y F-Z M-X M-Y M-Z

BAR# END AXIAL SHEAR-1 SHEAR-2 TORQUE BENDING BENDING


-1 -2

PLATE# MEMB-X MEMB-Y MEMB-XY BEND-X BEND-Y TWIST- SHEAR- SHEAR-


XY XZ YZ

GAP# C OMP-X SHEAR-Y SHEAR-Z

Element force output is then listed under these headings, depending on the type of elements
for which this output was selected. The format of the element output matches the
corresponding header, that is for ROD elements you would get FORCE-A and FORCE-B;
whereas, for PLATE elements you would get MEMB-X, MEMB-Y, MEMB-XY, BEND-X, BEND-Y,
TWIST-XY, SHEAR-XZ, SHEAR-YZ.

The format is:

Eid value1 value2 value3 …

where:

Eid is the element identification number.

value# is the Force result corresponding to the column header.

Comments

1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.

2240 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.fsthick file

The .fsthick file is an OptiStruct ASCII format file.

File Creation

This file is created when free size optimization is performed and OUTPUT, FSTHICK, YES is
present in the I/O Options section.

File Contents

Result Description

Element definition The element definitions for those elements that were part of a free
size design space. The optimized thickness of these elements are
provided as nodal thickness values (Ti).

File Format

The format for the .fsthick file is the same as for the corresponding bulk data entries.

Altair Engineering OptiStruct 13.0 Reference Guide 2241

Proprietary Information of Altair Engineering


.gpf file

The .gpf file is an OptiStruct ASCII format results file.

File Creation

Creation of this file is controlled by the GPFORCE I/O option.

File Contents

Result Description

Grid point force Grid point force balance table for linear static analysis.
balance table

File Format

The file is divided up by iteration. Output from each iteration starts with a line in the following
format:

ITERATION Iteration_number

where:
ITERATION is a keyword denoting the beginning of a new iteration.

Iteration_number is the Iteration number.

Each iteration section contains a force balance table for each node, for which this output
format was selected, in each linear static subcase.

These tables are given the following header:

Grid point forces for Node_id Subcase ID = Subcase_id


node

where:
Node_id is the ID of the node to which the force balance table applies.

Subcase_id is the user-defined subcase ID to which the force balance


table applies.

2242 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


And the force information is provided, for each contributing element, constraint or load, in
the following format:

Force_type Element_id x-force y-force z-force x- y-moment z-moment


moment

where:

Force_type is one of:

SPC Force contribution of single-point constraints.

Appl. Force contribution of Applied loads.

F-MPC Force contribution of rigid elements or multi-point


constraints.

Elem Force contribution of elastic elements.

Total The sum of all the force contributions.

Element_id is only valid for force contributions from elastic elements. This is
the element's ID.

x-force is the x-translational component of the force.

y-force is the y-translational component of the force.

z-force is the z-translational component of the force.

x-moment is the x-rotational component of the force.

y-moment is the y-rotational component of the force.

z-moment is the z-rotational component of the force.

Comments

1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.

Altair Engineering OptiStruct 13.0 Reference Guide 2243

Proprietary Information of Altair Engineering


.grid file

The .grid file is an OptiStruct ASCII format results file.

File Creation

This file is created when topography or shape optimization is performed. Output of this file is
controlled by the I/O Option SHRES or by the GRID keyword on the OUTPUT card.

File Contents

Result Description

Nodal locations The nodal coordinates of the model for the last iteration of the
optimization.

File Format

The file uses the following format for each grid in the model:

GRID Id Cp X1 X2 X3 Cd Ps

where:

GRID identifies this as a GRID card image.

Id is the unique grid point identification number.

Cp is the identification number of the coordinate system in which the


location of the grid point is defined.

X1, X2, X3 provide the location of the grid point in the global coordinate
system.

Cd is the identification number of the coordinate system in which the


displacements, degrees-of-freedom, constraints and solution
vectors are defined at the grid point.

Ps is the SPC associated with the grid.

2244 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.h3d file

The .h3d file is a compressed binary file, containing both model and result data. It can be
used to post-process results in HyperView or when using the HyperView Player.

File Creation

The .h3d file is created when the H3D format is chosen (see I/O options FORMAT and
OUTPUT), and an analysis only run is performed (meaning no design variables or design spaces
are defined in the model); the I/O option ANALYSIS is present; or the command line switch -
analysis is used (see Run Options for OptiStruct).

File Contents

The .h3d file contains node and element definitions in addition to the following results:

Result Description

Acceleration Acceleration results from frequency response, acoustic,


transient response, and multi-body dynamics analyses.

Output is controlled by the I/O option ACCELERATION.

Composite ply strain Ply strain results for composite materials from static
analyses.

Output is controlled by the I/O option STRAIN and by


the SOUTi field on the PCOMP definition.

Composite ply stress Ply stress results for composite materials from static
and analyses.

Output is controlled by the I/O option STRESS and by


the SOUTi field on the PCOMP definition.

Composite failure indices Failure indices for composite materials from static
analyses.

Output is controlled by the I/O option STRESS, by the


SOUTi, SB and FT fields on the PCOMP definition and by
the related fields on the relevant material definition
(see MAT1, MAT2, MAT8).

Density Density results from topology optimizations.

Output is controlled by the I/O option DENSITY.

Altair Engineering OptiStruct 13.0 Reference Guide 2245

Proprietary Information of Altair Engineering


Result Description

Displacement Displacement results from static, frequency response,


acoustic, transient response, and multi-body dynamics
analyses.

Output is controlled by the I/O option DISPLACEMENT.

Eigenvector Eigenvector results from normal modes and linear


buckling analyses.

Output is controlled by the I/O option DISPLACEMENT.

Element energy loss per cycle Element energy loss per cycle and energy loss per cycle
density output from frequency response analysis.

Output is controlled by the I/O option EDE.

Element force Element force results from static, frequency response,


acoustic, and transient response analyses.

Output is controlled by the I/O option FORCE (or


ELFORCE).

Element kinetic energy Element kinetic energy and kinetic energy density
output from frequency response analysis.

Output is controlled by the I/O option EKE.

Element strain energy Element strain energy and strain energy density results
from static, normal modes and frequency response
analyses.

Output is controlled by the I/O option ESE.

Grid point stress Grid point stress results for 3D elements from static and
normal modes analyses.

Output is controlled by the I/O option GPSTRESS (or


GSTRESS).

Power flow field Power flow field output from frequency response and
acoustic analyses.

Output is controlled by the I/O option POWERFLOW.

2246 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Result Description

Shape Shape results from topography or shape optimizations.

Output is controlled by the I/O option SHAPE.

SPC force Single-point force of constraint results from static,


frequency response, acoustic, and transient response
analyses.

Output is controlled by the I/O option SPCFORCE.

Strain Strain results from static, frequency response,


acoustic, transient response, and multi-body dynamics
analyses. Output is controlled by the I/O option
STRAIN.

Stress Stress results from static, frequency response,


acoustic, transient response, and multi-body dynamics
analyses.

Output is controlled by the I/O option STRESS (or


ELSTRESS).

Thickness Thickness results from size and topology optimizations.

Output is controlled by the I/O option THICKNESS.

Velocity Velocity results from frequency response, acoustic,


transient response, and multi-body dynamics analyses.

Output is controlled by the I/O option VELOCITY.

Comments

1. Grid point stresses are output for the entire model and for each individual component.
This allows grid point stresses to be accurately obtained at the interface of two
components referencing different material definitions.

2. For dynamic analyses like frequency response, transient response, and multi-body
dynamics, it is recommended that sets be used to reduce the amount of model and
results output data. The output file can become very large since results are output for
each frequency or time step.

Altair Engineering OptiStruct 13.0 Reference Guide 2247

Proprietary Information of Altair Engineering


.hgdata file

The .hgdata file is a HyperGraph ASCII results file.

File Creation

This file is created when an optimization is performed. Creation of this file is controlled by the
I/O Option DESHIS.

File Contents

This file may contain the iteration history of the objective function, constraint functions,
design variables, and response functions. Contents of this file are controlled by the I/O
option HISOUT.

2248 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.hist file

The .hist file is an OptiStruct ASCII format results file.

File Creation

This file is created when an optimization is performed. Creation of this file is controlled by the
I/O Option DESHIS.

File Contents

This file contains the iteration history of the objective function, maximum constrain violation,
design variables, DRESP1 type responses, and DRESP2 type responses. Contents of this file
are controlled by the I/O option HISOUT.

File Format

The section outlines the format of the .hist OptiStruct ASCII file.

The file uses the following format:

iteration Objective Max_Const_Violation Design_variables DRESP1s DESP2s

where:

iteration is the iteration number.

Objective is the value of the objective function.

Max_Const_Violation is the Maximum constraint violation in %.

Design_variables is the value of the design variables. Each design variable


is given its own column.

DRESP1s is the value of the DRESP1s. Each DRESP1 type response


is given its own column.

DESP2s is the value of the DRESP2s. Each DRESP2 type response


is given its own column.

Comments

1. The value of each design variable, DRESP1 response and DRESP2 response, is provided in
its own column.

Altair Engineering OptiStruct 13.0 Reference Guide 2249

Proprietary Information of Altair Engineering


.HM.comp.cmf file

The .HM.comp.cmf file is a HyperMesh command file.

File Creation

The .HM.comp.cmf file is created when a topology optimization is performed (see Topology
Optimization in the OptiStruct User's Guide).

File Contents

When executed in HyperMesh, the .HM.comp.cmf file organizes all elements in the model into
ten new components based on their material densities at the final iteration. The components
are named 0.0-0.1, 0.1-0.2, 0.2-0.3, and so on, up to 0.9-1.0. All elements with a material
density between 0% and 10% are contained in 0.0-0.1. All elements with a material density
between 10% and 20% are contained in 0.1-0.2, and so on. This helps you visualize results
by turning components on and off.

Comments

1. Ensure the corresponding model is loaded in HyperMesh when executing the command file.

2. Since elements cannot be in more than one component in HyperMesh, the original
components do not contain any elements.

2250 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.HM.conn.cmf file

The .HM.conn.cmf file is a HyperMesh command file.

File Creation

The .HM.conn.cmf file is created when a topology optimization is performed and 1D elements
form part of the topological design space (see Topology Optimization in the OptiStruct Users
Guide).

File Contents

When executed in HyperMesh, the .HM.conn.cmf file creates connector definitions for those
1D elements which formed part of the topological design space and organizes these
connectors into ten new components based on their material densities at the final iteration.
The components are named 0.0-0.1, 0.1-0.2, 0.2-0.3, and so on, up to 0.9-1.0. The
connector corresponding to those elements with a material density between 0% and 10% are
contained in the 0.0-0.1 component. The connectors corresponding to those elements with a
material density between 10% and 20% are contained in the 0.1-0.2 component, and so on.
This helps you to visualize results by turning components on and off.

Comments

1. Make sure that the corresponding model is loaded in HyperMesh when executing the
command file.

2. Connectors are geometric entities in HyperMesh.

Altair Engineering OptiStruct 13.0 Reference Guide 2251

Proprietary Information of Altair Engineering


.HM.elcheck.cmf file

The .HM.elcheck.cmf file is a HyperMesh command file.

File Creation

The file is created when an element quality check is performed.

File Contents

This file contains results from the following tests:

1. Element quality tests using ELEMQUAL entry and PARAM, CHECKEL.

2. Incorrectly formed CFAST and CWELD elements.

3. CBUSH or CELAS elements with excessive stiffness values (PARAM, BUSHSTIF and PARAM,
ELASSTIF).

When executed in HyperMesh, the .HM.elcheck.cmf file organizes all elements into separate
sets depending on which quality check they fail. One set is created for each failed quality
check. This helps you to visualize results by finding (displaying) elements by set.

Comments

1. Ensure the corresponding model is loaded in HyperMesh when executing the command file.

2252 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.HM.elcheck.###.cmf file

The .HM.elcheck_###.cmf file is a HyperMesh command file.

File Creation

The file is created, as required, when an element quality check is performed for optimization
iterations.

File Contents

This file contains results from the following tests:

1. Element quality tests using ELEMQUAL entry and PARAM, CHECKEL.

2. Incorrectly formed CFAST and CWELD elements.

3. CBUSH or CELAS elements with excessive stiffness values (PARAM, BUSHSTIF and PARAM,
ELASSTIF).

When executed in HyperMesh, the .HM.elcheck_###.cmf file organizes all elements into
separate sets depending on which quality check they fail. One set is created for each failed
quality check. This helps you to visualize results by finding (displaying) elements by set.

Comments

1. Ensure the corresponding model is loaded in HyperMesh when executing the command file.

2. The ### in the file name represents the optimization iteration number.

Altair Engineering OptiStruct 13.0 Reference Guide 2253

Proprietary Information of Altair Engineering


.HM.ent.cmf file

The .HM.ent.cmf file is a HyperMesh command file.

File Creation

The .HM.ent.cmf file is created when a topology optimization is performed (see Topology
Optimization in the OptiStruct User's Guide).

File Contents

When executed in HyperMesh, the .HM.ent.cmf file organizes all elements in the model into
ten new entity sets based on their material densities at the final iteration. The sets are
named 0.0-0.1, 0.1-0.2, 0.2-0.3, and so on, up to 0.9-1.0. All elements with a material
density between 0% and 10% are contained in 0.0-0.1. All elements with a material density
between 10% and 20% are contained in 0.1-0.2, and so on. You can then visualize the
results by masking the entity sets which contain those elements with lower density.

Comments

1. Ensure the corresponding model is loaded in HyperMesh when executing the command file.

2. The advantage of this method over the .HM.comp.cmf method is that the elements
remain in their original components, but can still be selected and masked by entity set.

2254 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.HM.gapstat.cmf file

The .HM.gapstat.cmf file is a HyperMesh command file.

File Creation

This file is created when a nonlinear gap analysis is performed and GAPPRM, HMGAPST is set
as YES or 1.

File Contents

When executed in HyperMesh, the .HM.gapstat.cmf file organizes gap elements into two
sets, open or closed, depending on the status of the gap at the end of the analysis.

Comments

1. Be sure that the corresponding model is loaded in HyperMesh when executing the
command file.

Altair Engineering OptiStruct 13.0 Reference Guide 2255

Proprietary Information of Altair Engineering


.html file

The .html file is a HyperText Markup Language file.

File Creation

This file is always output.

File Contents

This file contains a problem summary and results summary of the run.

The problem summary contains information on the finite element model, subcase definitions,
and optimization parameters.

The results summary lists the following results for an analysis or the final iteration of an
optimization:

For linear static subcases:

The maximum displacement and the node where this occurs


The maximum strain energy density and the element where this occurs
The maximum stress and strain for 1D, 2D, and 3D elements and the elements where
these occur
For normal modes subcases:

The frequencies of the calculated modes


The maximum deformation and the node where this occurs
The maximum strain energy density and the element where this occurs
For linear buckling subcases:

The buckling factor for the calculated modes


The maximum deformation and the node where this occurs

2256 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.interface file

The .interface file is an ASCII format results file.

File Creation

This file is always created when acoustic analysis is performed.

File Contents

This acoustic coupling interface matrix visualization file contains element definitions.

Comments

1. This file is used to verify the fluid/structure coupling matrix.

2. Import this file into HyperMesh with the acoustic model already loaded. For best
performance, ensure that the FE overwrite option is turned on in the HyperMesh import
panel.

Altair Engineering OptiStruct 13.0 Reference Guide 2257

Proprietary Information of Altair Engineering


.k.op2 file

The .k.op2 file is a Nastran output2 format file containing the stiffness matrix.

File Creation

This file is created when PARAM, POST, -5 is present in the bulk data section.

File Contents

This file contains the stiffness matrix.

2258 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.load file

The .load file is an OptiStruct ASCII format results file.

File Creation

Creation of this file is controlled by the OLOAD I/O option.

File Contents

Result Description

Applied Load Applied load vectors for linear static analysis.

File Format

The applied load file has the following format:

For each iteration, the following header is used:

iter Iteration NumIds

where:
iter is a keyword denoting the beginning of a new iteration.

Iteration is the iteration number.

Numids is the number of subcases for which this output is created.

Each iteration section is divided up by subcase. Output for each subcase starts with a line
in the following format:

Id Number_of_node Frequency LOAD:Spc_id(Datatype) subcase_label


s

where:

Id is the output identification number for the subcase. This is


not the same as the subcase ID used in the input data.

Altair Engineering OptiStruct 13.0 Reference Guide 2259

Proprietary Information of Altair Engineering


Number_of_nodes is the number of nodes for which this output is requested.

Frequency is 1.0 for static analysis.

LOAD is a keyword declaring applied load information.

Spc_id is the SID for SPC's referenced by this subcase.

Datatype is a keyword indicating the type of subcase involved.

(LOAD) declares data is for a linear static subcase.

The following information is then provided for each node, for which this output was
requested:

NID X force Y force Z force X mom Y mom Z mom

where:

NID is the node identification number.

X force is the X force at the node.

Y force is the Y force at the node.

Z force is the Z force at the node.

X mom is the X moment at the node.

Y mom is the Y moment at the node.

Z mom is the Z moment at the node.

Comments

1. The I/O option RESULTS controls the frequency of output for analytical results during an
Optimization.

2260 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.m.op2 file

The .m.op2 file is a Nastran output2 format file containing the mass matrix.

File Creation

This file is created when PARAM, POST, -5 is present in the bulk data section.

File Contents

This file contains the mass matrix.

Altair Engineering OptiStruct 13.0 Reference Guide 2261

Proprietary Information of Altair Engineering


.mass file

The .mass file is an OptiStruct ASCII format results file.

File Creation

This file is only created when modal analyses are performed. Creation of this file is controlled
by the I/O Option OUTPUT.

File Contents

Result Description

Modal Effective Masses Modal effective mass results from modal analyses.

Output is controlled by the I/O option OUTPUT,HGEFFMASS.

File Format

The file is formatted into blocks separated by blank lines. Each block represents a modal
subcase; the subcases are in order of occurrence in the input deck.

Each block contains a number of rows equal to the number of requested modes for that
subcase.

The columns, from left to right, contain results for modal effective mass for X-translation, Y-
translation, Z-translation, X-rotation, Y-rotation, and Z-rotation.

Comments

1. The _mass.mvw HyperView script file automatically creates plots for the results contained
in this file.

2262 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.mnf file

The .mnf file is ADAMS modal neutral file.

File Creatio n

This file is created when OUTPUT, ADAMSMNF is presented during flexible body generation.

File Contents

This file contains the flexible body models.

Comments

1. If GPSTRESS output is requested in addition to OUTPUT, ADAMSMNF, nodal stress results


for solid elements will be written to this file.

Altair Engineering OptiStruct 13.0 Reference Guide 2263

Proprietary Information of Altair Engineering


.mpcf file

The .mpcf file is an OptiStruct ASCII format results file.

File Creation

Creation of this file is controlled by the MPCFORCES I/O option.

File Contents

Result Description

Multi-point force of Multi-point force of constraints for linear static analysis.


constraint

File Format

The file is divided up by iteration. Output from each iteration starts with a line in the following
format:

ITERATION Iteration_number

where:
ITERATION is a keyword denoting the beginning of a new iteration.

Iteration_number is the iteration number.

Each iteration section contains the multi-point force of constraint for each node, for which
this output format was selected, in each linear static subcase. Each subcase section is
given the following header:

MPC forces for Subcase_id


Subcase

where:
Subcase_id is the user-defined subcase ID to which the mpc forces apply.

MPC force information is then provided, for each node, in the following format:

2264 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Node_id x-force y-force z-force x-moment y-moment z-moment

where:

Node_id is the node identification number.

x-force is the x-translational component of the force at the node.

y-force is the y-translational component of the force at the node.

z-force is the z-translational component of the force at the node.

x-moment is the x-rotational component of the force at the node.

y-moment is the y-rotational component of the force at the node.

z-moment is the z-rotational component of the force at the node.

Comments

1. The I/O option RESULTS controls the frequency of output for analytical results during an
Optimization.

Altair Engineering OptiStruct 13.0 Reference Guide 2265

Proprietary Information of Altair Engineering


.op2 file

The .op2 file is a Nastran output2 format for model and results data.

File Creation

This file is created when the O2, OUT2, or OUTPUT2 formats are chosen. (See documentation
for the I/O options FORMAT and OUTPUT).

File Contents

Result Description

Acceleration Acceleration results from frequency response, acoustic,


transient response, and multi-body dynamics analyses.

Output is controlled by the I/O option ACCELERATION.

Composite ply strain Ply strain results for composite materials from static analyses.

Output is controlled by the I/O option CSTRAIN and by the


SOUTi field on the PCOMP definition.

Composite ply stress Ply stress results for composite materials from static analyses.

Output is controlled by the I/O option CSTRESS and by the


SOUTi field on the PCOMP definition.

Composite failure Failure indices for composite materials from static analyses.
indices
Output is controlled by the I/O option CSTRESS, by the SOUTi,
SB and FT fields on the PCOMP definition, and by the related
fields on the relevant material definition (see MAT1, MAT2,
MAT8).

Density Density results from topology optimizations.

Output is controlled by the I/O option DENSITY.

Note: Density results are reported as element strain energy.

Displacement Displacement results from static, frequency response, acoustic,


transient response, and multi-body dynamics analyses.

Output is controlled by the I/O option DISPLACEMENT.

2266 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Result Description

Eigenvector Eigenvector results from normal modes and linear buckling


analyses.

Output is controlled by the I/O option DISPLACEMENT.

Element energy Element energy loss per cycle and energy loss per cycle density
loss per cycle output from frequency response analysis.

Output is controlled by the I/O option EDE.

Element force Element force results from static, frequency response, acoustic,
and transient response analyses.

Output is controlled by the I/O option FORCE (or ELFORCE).

Element kinetic Element kinetic energy and kinetic energy density output from
energy frequency response analysis.

Output is controlled by the I/O option EKE.

Element strain Element strain energy and strain energy density results from
energy static, normal modes, frequency response, and transient
response analyses.

Output is controlled by the I/O option ESE.

Grid point stress Grid point stress results for 3D elements from static analyses.

Output is controlled by the I/O option GPSTRESS (or GSTRESS).

MPC force Multi-point force of constraint results from static, frequency


response, acoustic, and transient response analyses.

Output is controlled by the I/O option MPCFORCE.

PSD element strain Power spectral density function of element strains from random
response analysis.

Output is controlled by the I/O option STRAIN.

PSD element stress Power spectral density function of element stresses from
random response analysis.

Altair Engineering OptiStruct 13.0 Reference Guide 2267

Proprietary Information of Altair Engineering


Result Description

Output is controlled by the I/O option STRESS.

RMS element strain Root mean square value of element strains from random
response analysis.

Output is controlled by the I/O option STRAIN.

RMS element stress Root mean square value of element stresses from random
response analysis.

Output is controlled by the I/O option STRESS.

SPC force Single-point force of constraint results from static, frequency


response, acoustic, and transient response analyses.

Output is controlled by the I/O option SPCFORCE.

Strain Strain results from static, frequency response, acoustic,


transient response, and multi-body dynamics analyses.

Output is controlled by the I/O option STRAIN.

Stress Stress results from static, frequency response, acoustic,


transient response, and multi-body dynamics analyses.

Output is controlled by the I/O option STRESS (or ELSTRESS).

Velocity Velocity results from frequency response, acoustic, transient


response, and multi-body dynamics analyses.

Output is controlled by the I/O option VELOCITY.

Comments

1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.

2. In addition to the analysis and optimization results, the finite element model description
(nodes, elements, coordinates systems, and properties) is written to the .op2 file. This
model can be read by HyperView and fatigue codes. To turn off the model output, use
the NOMODEL option on OUTPUT, OP2.

3. To be able to read the model directly from the .op2 file, newer versions of FEMFAT,
Medina (7.4.8 or newer), and Animator (3.0.6.6c or newer) must be used.

2268 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


4. For dynamic analyses like frequency response, transient response, and multi-body
dynamics, it is recommended that sets be used to reduce the amount of model and
results output data. The output file can become very large since results are output for
each frequency or time step.

Altair Engineering OptiStruct 13.0 Reference Guide 2269

Proprietary Information of Altair Engineering


.oss file

The .oss file is an OSSmooth parameter file.

File Creation

This file is created when a topology, topography, or shape optimization is performed.

File Contents

The file contains default settings for running OSSmooth after a successful optimization.

Comments

1. The format of this file is described on the OSSmooth Input Data page.

2270 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.out file

The .out file is an ASCII format results file.

File Creation

This file is always created.

File Contents

This file provides a commentary on the solution process.

File Format

The file starts with an OptiStruct banner, and is followed by three sections which outline the
problem definition:

Optimization File and Parameter Information


Finite Element Model Data Information
Optimization Problem Parameters
Following these, calculated estimates on required memory and disk space are provided under
the headings:

Memory Estimation Information


Disk Space Estimation Information
The Analysis Results or Optimization History information sections provide the following
information (Some information is output for each iteration during optimization, or as a summary
for nonlinear analysis):

Element quality information (If any of the warning or error limits are exceeded).
Global force balance tables for each linear static subcase. (When SPCFORCE or
GPFORCE is a requested output).
Objective function value
Maximum constrain violation % and the ID of this constraint.
Design volume fraction value if topology design variables are present, otherwise the
total volume is given, and the total mass.
Individual subcase compliances and weightings and the total weighted compliance.
Retained responses table
If the constraint violation is higher than 1%, the constraint is flagged as V (violated). If the
violation is lower than 1%, it is flagged as A (active). For stress constraint in topology
optimization, if there is no violation, it is flagged as Inactive; otherwise, it is flagged as
Active.

User-requested responses table (when RESPRINT or DREPORT is a requested output).

Altair Engineering OptiStruct 13.0 Reference Guide 2271

Proprietary Information of Altair Engineering


Most violated constraints table.

Design variable values and bounds if shape or size design variables are present.
Designed property/material/connectivity items table if size design variables are present.
A list of calculated buckling modes and their eigenvalues.
A list of calculated normal modes, their frequencies, eigenvalues and weighting and the
value of the frequencies weighted across the reciprocal eigenvalues.
Center of Gravity table

Moment of Inertia table


Regional compliance table

Manufacturing Constraints table for Composite Optimization

An example table is shown below:

COMPOSITE MANUFACTURING CONSTRAINTS


----------------------------------------------------------------------------
User-ID Constraint Information Status Max Avg Pct
Type Bound Group Elem Viol. Viol. Viol.
----------------------------------------------------------------------------
1 PLYPCT LOWER 0.0 ALL Violated 12.1 2.6 2.5
1 PLYPCT LOWER 90.0 ALL Violated 3.0 1.6 0.2
1 PLYPCT UPPER 90.0 ALL Violated 31.8 5.3 14.6
----------------------------------------------------------------------------
Where,

Max Viol. – Represents the maximum violation of the specified manufacturing constraint
(Type).

Avg Viol. – Represents the average violation of all the violated elements for the
specified manufacturing constraint (Type).

Pct Viol. – Represents the percentage of the total number of elements in the design
space for which the specified manufacturing constraint (Type) is violated.

The Constraint Information columns are self-explanatory and may vary from one
constraint type to the other.

Nonlinear Iteration Summary table for Nonlinear Analysis

An example table is shown below:

2272 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Where,

Avg. U – Represents the average displacement of all elements for a particular iteration
for a subcase

EUI – Represents the relative error in displacements

EPI – Represents the error in terms of loads

EWI – Represents the error in terms of work

Refer to the Nonlinear Convergence Criteria section of Nonlinear Quasi-Static Analysis


in the User’s Guide for more information.

Maximum Plststrn – Represents the Maximum Plastic Strain

The Gap and Contact Element Status columns are self-explanatory.

At the end of the file, the following information is provided:

Resource usage information


Compute time information

Altair Engineering OptiStruct 13.0 Reference Guide 2273

Proprietary Information of Altair Engineering


.pch file

The .pch file is a Nastran punch format results file.

File Creation

This file is created when the NASTRAN or PUNCH formats are chosen. (See documentation for
the I/O options FORMAT and OUTPUT).

File Contents

Result Description

Acceleration Acceleration results from frequency response, acoustic,


transient response, and multi-body dynamics analyses.

Output is controlled by the I/O option ACCELERATION.

Density Density results from topology optimizations.

Output is controlled by the I/O option DENSRES.

Note: Density results are reported as von Mises Strains.

Displacement Displacement results from static, frequency response, acoustic,


and transient response analyses.

Output is controlled by the I/O option DISPLACEMENT.

Eigenvector Eigenvector results from normal modes analyses.

Output is controlled by the I/O option DISPLACEMENT.

Element energy Element energy loss per cycle and energy loss per cycle density
loss per cycle output from frequency response analysis.

Output is controlled by the I/O option EDE.

Element force Element force results from static, frequency response, acoustic,
and transient response analyses.

Output is controlled by the I/O option FORCE (or ELFORCE).

Element kinetic Element kinetic energy and kinetic energy density output from
energy frequency response analysis.

2274 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Result Description

Output is controlled by the I/O option EKE.

Element strain Element strain energy and strain energy density results from
energy static, normal modes and frequency response analyses.

Output is controlled by the I/O option ESE.

Grid point stress Grid point stress results for 3D elements from static analysis.

Output is controlled by the I/O option GPSTRESS (or GSTRESS).

MPC force Multi-point force of constraint results from static, frequency


response, acoustic, and transient response analyses.

Output is controlled by the I/O option MPCFORCE.

PSD acceleration Power spectral density function of accelerations from random


response analysis. (see comment 2)

Output is controlled by the I/O options XYPEAK, XYPLOT, and


XYPUNCH.

PSD displacement Power spectral density function of displacements from random


response analysis. (see comment 2)

Output is controlled by the I/O options XYPEAK, XYPLOT, and


XYPUNCH.

PSD velocity Power spectral density function of velocities from random


response analysis. (see comment 2)

Output is controlled by the I/O options XYPEAK, XYPLOT, and


XYPUNCH.

PSD element strain Power spectral density function of element strains from random
response analysis. (see comment 2)

Output is controlled by the I/O options XYPEAK, XYPLOT, and


XYPUNCH.

PSD element stress Power spectral density function of element stresses from
random response analysis. (see comment 2)

Altair Engineering OptiStruct 13.0 Reference Guide 2275

Proprietary Information of Altair Engineering


Result Description

Output is controlled by the I/O options XYPEAK, XYPLOT, and


XYPUNCH.

RMS element strain Root mean square value of element strains from random
response analysis.

Output is controlled by the I/O options XYPEAK, XYPLOT, and


XYPUNCH.

RMS element stress Root mean square value of element stresses from random
response analysis.

Output is controlled by the I/O options XYPEAK, XYPLOT, and


XYPUNCH.

SPC force Single-point force of constraint results from linear static


analysis.

Output is controlled by the I/O option SPCFORCE.

Strain Strain results from static, frequency response, acoustic,


transient response, and multi-body dynamics analyses.

Output is controlled by the I/O option STRAIN.

Stress Stress results from static, frequency response, acoustic,


transient response, and multi-body dynamics analyses.

Output is controlled by the I/O option STRESS (or ELSTRESS).

Velocity Velocity results from frequency response analyses, acoustic,


transient response, and multi-body dynamics.

Output is controlled by the I/O option VELOCITY.

Comments

1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.

2. Multiple RANDOM subcase information entries with non-unique ID’s are allowed in a single
model. Therefore, if the plot-type field on the XYPUNCH output request is set to PSDF,
then the RANDOM ID will be added to the XYPUNCH headers in the corresponding result
sections of the .pch file when multiple RANDOM entries are present in the same deck. If
only one RANDOM entry is present, the RANDOM ID is not printed.

2276 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Altair Engineering OptiStruct 13.0 Reference Guide 2277

Proprietary Information of Altair Engineering


.pcomp file

The .pcomp file is an ASCII format result file.

File Creation

This file is created when OUTPUT,PCOMP is requested in composite sizing optimization.

File Contents

This file contains elements and PCOMPG property information for each STACK.

2278 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.peak file

The .peak file is an ASCII format results file.

File Creation

This file is created when XYPLOT, XYPEAK, or XYPUNCH is requested in random response
analysis.

File Contents

This file contains the root mean square value, the number of positive crossings, and the peak
power spectral density and responses.

Altair Engineering OptiStruct 13.0 Reference Guide 2279

Proprietary Information of Altair Engineering


.pret file

The .pret file is an OptiStruct ASCII format results file.

File Creation

Creation of this file is controlled by the PRETBOLT I/O Options Entry.

File Contents

Result Description

Pretension force/ Pretension force/adjustment values for pretension bolts in


adjustment pretensioning and pretensioned subcases.

File Format

The file is sorted by iteration. Output from each iteration starts in the following format:

PRETENSION FORCE/ADJUSTMENT VALUES ON THE PRENTESION SECTIONS

ITERATION Iteration_number

Where:

ITERATION is a keyword denoting the beginning of a new iteration.

Iteration_number is the iteration number.

Each iteration section contains the force/adjustment values for each pretension bolt in
each static subcase. Each such subcase section is given the following header:

Subcase Subcase_id Subcase_label

Where:

Subcase is a keyword denoting the beginning of the current subcase section.

Subcase_id is the user-defined subcase ID

Subcase_label is the user-defined subcase label

2280 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Pretension force/adjustment information is then provided, for each bolt, in the following
format:

Pretension Force-incr Adjust-incr Force-tot Adjust-


section ID tot
(PRETENS #)

Where:

Pretension section ID denotes the pretension section ID (SID of the PRETENS bulk data
entry).

Force-incr is the incremental pretension force value when compared to the previous
subcase in the loading sequence.

Adjust-incr is the incremental pretension adjustment value when compared to the


previous subcase in the loading sequence.

Force-tot is the total pretension force value.

Adjust-tot is the total pretension adjustment value.

Comments

1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.

Altair Engineering OptiStruct 13.0 Reference Guide 2281

Proprietary Information of Altair Engineering


.prop file

The .prop file is an OptiStruct ASCII format result file.

File Creation

This file is output when sizing optimization is performed. Creation of this file is controlled by
the PROPERTY I/O option.

File Contents

Result Description

Property definition The property definitions, for those properties that were affected
in the sizing optimization, used for the final iteration of the
optimization.

File Format

The format for the property output is the same as for the bulk data entries.

2282 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.rand file

The .rand file is an OptiStruct ASCII format results file.

File Creation

This file is only created for random response subcases. This file is only created if XYPLOT is
defined in random response.

File Contents

Result Description

Random response results Results from random response analyses.

Comments

1. The # in the file name is the user-defined subcase ID from which these results are
obtained.

2. The _rand.mvw HyperView script file automatically creates plots for the results contained
in this file.

Altair Engineering OptiStruct 13.0 Reference Guide 2283

Proprietary Information of Altair Engineering


.res file

The .res file is a HyperMesh binary results file.

File Creation

The .res file is created when either no format statement is given or when the HM, HYPER, or
BOTH formats are chosen. (See documentation for the I/O options FORMAT and OUTPUT).

File Contents

Result Description

Acceleration Acceleration results from frequency response, transient


response, and multi-body dynamics analyses.

Output is controlled by the I/O option ACCELERATION.

Composite ply strain Ply strain results for composite materials from static
analyses.

Output is controlled by the I/O option STRAIN and by the


SOUTi field on the PCOMP definition.

Composite ply stress Ply stress results for composite materials from static
analyses.

Output is controlled by the I/O option STRESS and by the


SOUTi field on the PCOMP definition.

Composite failure indices Failure indices for composite materials from static analyses.

Output is controlled by the I/O option STRESS, by the


SOUTi, SB and FT fields on the PCOMP definition, and by the
related fields on the relevant material definition (see MAT1,
MAT2, MAT8).

Density Density results from topology optimizations.

Output is controlled by the I/O option DENSITY.

Displacement Displacement results from static, frequency response,


transient response, and multi-body dynamics analyses.

Output is controlled by the I/O option DISPLACEMENT.

2284 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Result Description

Eigenvector Eigenvector results from normal modes and linear buckling


analyses.

Output is controlled by the I/O option DISPLACEMENT.

Element strain energy Element strain energy results from static and normal modes
analyses.

Output is controlled by the I/O option ESE.

Grid point stress Grid point stress results for 3D elements from static
analyses.

Output is controlled by the I/O option GPSTRESS (or


GSTRESS).

Shape Shape results from topography or shape optimizations.

Output is controlled by the I/O option SHAPE.

Single-point force of Single-point force of constraint results from static analyses.


constraint
Output is controlled by the I/O option SPCFORCE.

Strain Strain results from static, frequency response, transient


response, and multi-body dynamics analyses.

Output is controlled by the I/O option STRAIN.

Stress Stress results from static, frequency response, transient


response, and multi-body dynamics analyses.

Output is controlled by the I/O option STRESS (or


ELSTRESS).

Thickness Thickness results from size and topology optimizations.

Output is controlled by the I/O option THICKNESS.

Velocity Velocity results from frequency response analyses, transient


response, and multi-body dynamics.

Output is controlled by the I/O option VELOCITY.

Altair Engineering OptiStruct 13.0 Reference Guide 2285

Proprietary Information of Altair Engineering


Comments

1. If an optimization is terminated abruptly due to an error such as a full disk or power


failure, the HyperMesh binary results file (*.res) may become corrupted. In this event,
run the program "recover," included with OptiStruct, to clean up the results file.

2. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.

3. Grid point stresses are output for the entire model and for each individual component.
This allows grid point stresses to be accurately obtained at the interface of two
components referencing different material definitions.

4. For dynamic analyses, like frequency response, transient response, and multi-body
dynamics, it is recommended that sets be used to reduce the amount of model and
results output data. The output file can become very large since results are output for
each frequency or time step.

2286 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.seplot file

The .seplot file is an ASCII format output file.

File Creation

This file is created when the MODEL, PLOT, and PARAM, SEPLOT, YES options are presented
and the CBN method is used to reach a Component Mode Synthesis solution.

File Contents

This file contains grid and plot element definitions.

Comments

1. By including this file in a residual run, the results of the superelement part will be
recovered and post-processed.

Altair Engineering OptiStruct 13.0 Reference Guide 2287

Proprietary Information of Altair Engineering


.sh file

The .sh file is an OptiStruct ASCII format results file.

File Creation

This file is created when an optimization is performed. Output of this file is controlled by the
I/O option SHRES.

File Contents

Contains information necessary to restart the optimization from the final iteration.

2288 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.spcd file

The .spcd file is an OptiStruct ASCII format results file.

File Creation

This file is created in a residual run when DMIG's are present in the model. The .spcd file
contains displacement results at interface grid points.

File Contents

Result Description

Displacement Displacement results from a residual run. Output is controlled by


the I/O option DISPLACEMENT.

File Format

The .spcd file has the following format:

For each iteration, the following header is used:

SUBCASE SID

where:

SID is the identification number of the corresponding subcase.

Under each applicable subcase header, we have the following columns:

SPC ####SID GRID ID Component Displacement

where:

SID is the identification number of the corresponding subcase.

GRID ID is the identification number of the interface grid at which


the displacement results are output.

Component is the component in which the displacement result output.

Displacement is the displacement result for a give grid in the


corresponding component.

Altair Engineering OptiStruct 13.0 Reference Guide 2289

Proprietary Information of Altair Engineering


Comments

1. Only one .spcd file is created even if there are multiple DMIG’s in the model.

2290 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.spcf file

The .spcf file is an OptiStruct ASCII format results file.

File Creation

Creation of this file is controlled by the SPCFORCES I/O option.

File Contents

Result Description

Single-point force of Single-point force of constraints for linear static


constraint analysis.

File Format

The SPC reaction force file has the following format:

For each iteration, the following header is used:

iter Iteration Numlds

where:
iter is a keyword denoting the beginning of a new iteration.

Iteration is the iteration number.

Numlds is the number of subcases for which this output is created.

Each iteration section is divided up by subcase. Output for each subcase starts with a line
in the following format:

Id Number_of_nodes Frequency SPCF:Spc_id(Datatype) subcase_label

where:

Id is the output identification number for the subcase. This is


not the same as the subcase ID used in the input data.

Altair Engineering OptiStruct 13.0 Reference Guide 2291

Proprietary Information of Altair Engineering


Number_of_nodes is the number of nodes for which this output is requested.

Frequency is 1.0 for static analysis.

SPCF is a keyword declaring SPC-force information.

Spc_id is the SID for SPC's referenced by this subcase.

Datatype is a keyword indicating the type of subcase involved.

(LOAD) declares data is for a linear static subcase.

SPC-force information is then provided, for each node, in the following format:

Node_id x-force y-force z-force x-moment y-moment z-moment

where:

Node_id is the node identification number.

x-force is the x-translational component of the force at the node.

y-force is the y-translational component of the force at the node.

z-force is the z-translational component of the force at the node.

x-moment is the x-rotational component of the force at the node.

y-moment is the y-rotational component of the force at the node.

z-moment is the z-rotational component of the force at the node.

Comments

1. The I/O option RESULTS controls the frequency of output for analytical results during an
Optimization.

2292 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


.stat file

The .stat file is an ASCII format results file.

File Creation

This file is always created.

File Contents

This file provides details on CPU and elapsed time for each solver module.

File Format

Information on CPU and elapsed time is provided in the following format:

TOTAL TIME SPENT IN MODULE: module_name; CPU= cpu_time; WALL= wall_time

where: module_name is the name of the module.

cpu_time is the amount of CPU time spent in this module.

wall_time is the total elapsed time spent in this module.

Altair Engineering OptiStruct 13.0 Reference Guide 2293

Proprietary Information of Altair Engineering


.strn file

The .strn file is an ASCII format results file.

File Creation

This file is created when OPTI, OS, or ASCII formats are chosen. (See documentation for the
I/O options FORMAT and OUTPUT).

File Contents

Result Description

Strain Strain results from linear static analysis. Output is controlled by the I/O
option STRAIN.

File Format

The strain file has the following format:

For each iteration, the following header is used:

iter Iteration Numlds

where:
iter is a keyword denoting the beginning of a new iteration.

Iteration is the Iteration number.

Numlds is the number of load cases for which this output is created.

Each iteration section is divided up by subcase. Output for each subcase starts with a line
in the following format:

Id Number_of_els STRN:Spc_id

where:
Id is the output identification number for the subcase. This is
not the same as the subcase ID used in the input data.

2294 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Number_of_els is the number of elements for which this output is requested.

STRN is a fixed keyword.

Spc_id is the SID for SPC's referenced by this subcase.

Datatype is a keyword indicating the type of subcase involved.

(LOAD) declares data is for a linear static subcase.

Strain information is then provided, for each element, in the following format:

EID Strain1 Strain2 Strain3 Strain4 Strain5 Strain6 Strain7

where:

EID is the element identification number.

Strain1 is von Mises strain for 2D and 3D elements, or Axial strain for 1D
elements.

Strain2 is Normal X-strain at Z1 for 2D elements, Normal X-strain for 3D


elements, or Axial strain for 1D elements.

Strain3 is Normal X-strain at Z2 for 2D elements, Normal Y-strain for 3D


elements, or Axial strain for 1D elements.

Strain4 is Normal Y-strain at Z1 for 2D elements, Normal Z-strain for 3D


elements, or Axial strain for 1D elements.

Strain5 is Normal Y-strain at Z2 for 2D elements, Shear XY-strain for 3D


elements, or Axial strain for 1D elements.

Strain6 is Shear XY-strain at Z1 for 2D elements, Shear YZ-strain for 3D


elements, or Axial strain for 1D elements.

Strain7 is Shear XY-strain at Z2 for 2D elements, Shear XZ-strain for 3D


elements, or Axial strain for 1D elements.

Comments

1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.

Altair Engineering OptiStruct 13.0 Reference Guide 2295

Proprietary Information of Altair Engineering


.strs file

The .strs file is an OptiStruct ASCII format results file.

File Creation

This file is created when the OPTI, OS or BOTH formats are chosen. (See documentation for
the I/O options FORMAT and OUTPUT).

File Contents

Result Description

Stress Stress results from linear static analysis. Output is controlled by the I/O
option STRESS (or ELSTRESS).

File Format

The stress file has the following format:

For each iteration, the following header is used:

iter Iteration Numlds

where:
iter is a keyword denoting the beginning of a new iteration.

Iteration is the Iteration number.

Numlds is the number of load cases for which this output is created.

Each iteration section is divided up by subcase. Output for each subcase starts with a line
in the following format:

Id Number_of_els STRS:Spc_id(Datatype)

where:
Id is the output identification number for the subcase. This is not
the same as the subcase ID used in the input data.

2296 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Number_of_els is the number of elements for which this output is requested.

STRS is a fixed keyword.

Spc_id is the SID for SPC's referenced by this subcase.

Datatype is a keyword indicating the type of subcase involved.

(LOAD) declares data is for a linear static subcase.

Stress information is then provided, for each element, in the following format:

EID Stress1 S Stress3 S Stress5 Stress6 Stress7 Stress8 Stress9


t t
r r
e e
s s
s s
2 4

where:

EID Element identification number.

Stress1 von Mises stress for 2D and 3D elements, Maximum Axial stress for 1D
elements, or maximum stress in CWELD elements.

Stress2 Normal X-stress at Z1 for 2D elements, Normal X-stress for 3D


elements, or Axial stress for 1D elements.

For BAR/BEAM it is the stress at C at end A. Axial Stress for CWELD


elements.

Stress3 Normal X-stress at Z2 for 2D elements, Normal Y-stress for 3D


elements, or Axial stress for 1D elements.

For BAR/BEAM it is the stress at D at end A. Maximum tensile stress at


end A for CWELD elements.

Stress4 Normal Y-stress at Z1 for 2D elements, Normal Z-stress for 3D


elements, or Axial stress for 1D elements.

For BAR/BEAM it is the stress at E at end A. Minimum tensile stress at

Altair Engineering OptiStruct 13.0 Reference Guide 2297

Proprietary Information of Altair Engineering


end A for CWELD elements.

Stress5 Normal Y-stress at Z2 for 2D elements, Shear XY-stress for 3D


elements, or Axial stress for 1D elements.

For BAR/BEAM it is the stress at F at end A. Maximum tensile stress at


end B for CWELD elements.

Stress6 Shear XY-stress at Z1 for 2D elements, Shear YZ-stress for 3D


elements, or Axial stress for 1D elements.

For BAR/BEAM it is the stress at C at end B. Minimum tensile stress at


end B for CWELD elements.

Stress7 Shear XY-stress at Z2 for 2D elements, Shear XZ-stress for 3D


elements, or Axial stress for 1D elements.

For BAR/BEAM it is the stress at D at end B. Maximum shear stress for


CWELD elements.

Stress8 Maximum shear stress for CWELD elements.

For BAR/BEAM it is the stress at E at end B. Bearing stress for CWELD


elements.

Stress9 Bearing stress for CWELD elements.

For BAR/BEAM it is the stress at F at end B.

Comments

1. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.

2298 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


_des.h3d file

The _des.h3d file is a compressed binary file, containing both model and result data. It can
be used to post-process results in HyperView or when using the HyperView Player.

File Creation

The _des.h3d file is created when the H3D format is chosen (see documentation for the I/O
option FORMAT), and an optimization run is performed.

File Contents

The _des.h3d file contains node and element definitions in addition to the following results:

Result Description

Density Density results from topology optimizations. Output is controlled by the


I/O option DENSRES.

Shape Shape results from topography or shape optimizations. Output is


controlled by the I/O option DENSRES.

Thickness Thickness results from size and topology optimizations. Output is


controlled by the I/O option DENSRES.

Altair Engineering OptiStruct 13.0 Reference Guide 2299

Proprietary Information of Altair Engineering


_err.grid file

The _err.grid file is an OptiStruct ASCII format results file.

File Creation

This file is automatically created when freeshape and topography (or shape) optimization runs
are terminated due to mesh distortion.

File Contents

Result Description

Nodal locations It contains the nodal coordinates of the distorted mesh for
freeshape and topography (or shape) optimization.

File Format

The file uses the following format for each grid in the model:

GRID Id Cp X1 X2 X3 Cd Ps

where:

GRID identifies this as a GRID card image.

Id is the unique grid point identification number.

Cp is blank.

X1, X2, X3 provide the location of the grid point in the global coordinate
system.

Cd is the identification number of the coordinate system in which the


displacements, degrees-of-freedom, constraints, and solution
vectors are defined at the grid point.

Ps is the SPC associated with the grid.

2300 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


_frames.html file

The _frames.html file is a HyperText Markup Language file.

File Creation

This file is output when the H3D FORMAT is chosen.

File Contents

The file contains two frames. The top frame opens one of the .h3d files using the HyperView
Player browser plug-in. The .h3d file opened depends on the results selected for display in
the bottom frame. The bottom frame opens the _menu.html file, which facilitates the
selection of results to be displayed.

Comments

1. Requires HyperView Player plug-in to be installed.

2. This file is linked to from the "Results summary" section of the .html file and is created
primarily for this purpose.

Altair Engineering OptiStruct 13.0 Reference Guide 2301

Proprietary Information of Altair Engineering


_freq.#.mvw file

The _freq.#.mvw file is a HyperView session file.

File Creation

This file is created when frequency response optimization is performed and OUTPUT,HGFREQ is
requested.

Comments

1. The # in the file name is the iteration number.

2. This file may be opened from the File menu in HyperView or HyperGraph. It automatically
creates plots for the results contained in the files: _s#_a.#.frf, _s#_d.#.frf, and
_s#_v.#.frf.

2302 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


_freq.mvw file

The _freq.mvw file is a HyperView session file.

File Creation

This file is only created when frequency response analysis is performed. Creation of this file is
controlled by the I/O option OUTPUT.

File Contents

This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph. The file automatically creates plots for each of the results contained in the
files: _s#_a.frf, _s#_d.frf, and _s#_v.frf.

Altair Engineering OptiStruct 13.0 Reference Guide 2303

Proprietary Information of Altair Engineering


_gauge.h3d file

The _gauge.h3d file is a compressed binary file containing both model and result data. It can
be used to post-process shell thickness (gauge) sensitivity in HyperView.

File Creation

This file is created when an optimization is performed. Creation of this file is controlled by the
I/O option OUTPUT.

File Contents

The _gauge.h3d file contains node and element definitions in addition to the following results:

Result Description

Sensitivity Sensitivity of response vs. shell thickness (gauge) of PSHELL property.


Output is controlled by the I/O option OUTPUT.

Comments

1. The # in the file name is the iteration number.

2304 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


_gso.slk file

The _gso.slk file is a Microsoft SLK Data Import format results file.

File Creation

This file is created when Global Search Option (GSO) is activated and executed using the
DGLOBAL I/O entry and the DGLOBAL Bulk Data entry, respectively. This file outputs the
results of Global Search Option (GSO).

File Contents

Result Description

Optimized Designs It contains the list of unique and similar optimized designs based
on the Global Search Option (GSO) method. The designs in this
resulting subset of the total design space are then sorted based
on their rank (based on the number of convergences from unique
starting points to result in a specific design).

File Format

The file uses the following format for the designs optimized from specified starting points:

Unique Designs

Design Startin Times Directo Objecti C onstr Max. Avg. Max. Avg. DV1 DVN
Rank g Point Found ry ve aint Obj. Obj. DV DV
Name Functio Violatio Deviati Deviati Deviati Deviati
n n on on on on

All Designs

Design Starting Unique Directory Objective C onstraint DV1 DVN


Rank Point Design Name Function Violation

Where,

Design Rank Denotes the rank of the design. This is assigned based initially on the values
of Constraint Violation and then the Objective Function values.

Starting Point Denotes the starting point of the optimization for a design in the design
space.

Times Found The number of times designs (from unique starting points) converge to the
same design.

Directory Name of the Directory where the output files associated with the specified
Name design are stored.

Altair Engineering OptiStruct 13.0 Reference Guide 2305

Proprietary Information of Altair Engineering


Objective The value of the Objective Function for the current design.
Function

Constraint The value of the Constraint Violation for the current design
Violation

Maximum The maximum deviation (of a design) from the objective function among
Objective designs from unique starting points that converged to this unique design.
Deviation

Average The average deviation (of a design) from the objective function among
Objective designs from unique starting points that converged to this unique design.
Deviation

Maximum DV The maximum deviation between two design variables in the design space
Deviation among designs from unique starting points that converged to this unique
design.

Average DV The average deviation between design variables in the design space among
Deviation designs from unique starting points that converged to this unique design.

DV# The various design variables values represented by DV1, DV2,….., DVN.

Unique Design This represents the Design Rank used in the UNIQUE DESIGN Table.

2306 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


_hist.mvw file

The _hist.mvw file is a HyperView session file.

File Creation

This file is created when an optimization is performed. Creation of this file is controlled by the
I/O option DESHIS.

File Contents

This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph. The file automatically creates individual plots for each of the results contained in
the .hist file. Each plot occupies its own page within HyperView (HyperGraph).

Altair Engineering OptiStruct 13.0 Reference Guide 2307

Proprietary Information of Altair Engineering


_mass.#.mvw file

The _mass.#.mvw file is a HyperView session file.

File Creation

This file is created when modal optimization is performed and OUTPUT,HGEFFMASS is


requested.

Comments

1. The # in the file name is the iteration number.

2. This file may be opened from the File menu in HyperView or HyperGraph. It automatically
creates bar charts for the results contained in .#.mass file.

2308 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


_mass.mvw file

The _mass.mvw file is a HyperView session file.

File Creation

This file is only created when modal analyses are performed. Creation of this file is controlled
by the I/O option OUTPUT.

File Contents

This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph. The file automatically creates plots for the results contained in the .mass file.

Altair Engineering OptiStruct 13.0 Reference Guide 2309

Proprietary Information of Altair Engineering


_mbd.h3d file

The _mbd.h3d file is a compressed binary file containing both model and result data from a
multi-body dynamics analysis. It can be used to post-process results in HyperView.

File Creation

This file is created when a multi-body dynamics subcase is executed.

File Contents

The _mbd.h3d file contains node and element definitions in addition to the following results:

Result Description

Displacement Displacement results from static, frequency response,


transient response, and multi-body dynamics analyses.

Deformation > Displacement Deformations (deflections) of flexible bodies from multi-


body dynamics analyses in the body reference frame.

Deformation > Rotation Deformation (rotations) of flexible bodies from multi-body


dynamics analyses in the body reference frame.

Strain Strain results of flexible bodies from a multi-body


dynamics analysis.

Stress Stress results of flexible bodies from a multi-body


dynamics analysis.

Comments

1. This file format is the most compressed animation output for multi-body dynamics
analyses. It generates the smallest files compared to other formats.

2310 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


_mbd.log file

The _mbd.log file is an ASCII format log file from a multi-body dynamics analysis.

File Creation

This file is created when a multi-body dynamics subcase is executed. It is a direct output file
of MotionSolve.

File Contents

The file provides commentary on the multi-body dynamics solution progress.

Altair Engineering OptiStruct 13.0 Reference Guide 2311

Proprietary Information of Altair Engineering


_mbd.mrf file

The _mbd.mrf file is a Multi-body Results File.

File Creation

This file is created when a multi-body dynamics subcase is defined. The file contains time
history data that can be used for 2D plotting in HyperGraph. Some data is written by default,
and some needs to be requested.

File Contents

Data output by default.

Type Component Description

Rigid Body X, Y, Z Position

E0, E1, E2, E3 Orientation in Euler parameters.

VM, VX, VY, VZ Magnitude and X, Y, Z components


of velocity.

WM, WX, WY, WZ Magnitude and X, Y, Z components


of angular velocity.

ACCM, ACCX, ACCY, ACCZ Magnitude and X, Y, X components


of acceleration.

WDTM, WDTX, WDTY, WDTZ Magnitude and X, Y, Z components


of angular acceleration.

KE Kinetic energy

Flex Body All Rigid Body results

Q/i, i = 1,2,…,n Modal participation factors.

XD/i, i=1,2,…,N Modal velocity.

2312 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Type Component Description

System KE Kinetic energy

CPU Usage Total CPU time used.

CPU/Sim. Time Ratio The ration between the total CPU


time used and the simulation time.

Stepsize Actual step size used in the


integration.

Integration Order Order of the integrator used in the


integration.

Data output by request. The request needs to be defined through a REQUEST I/O statement.

Type
Component Description

Marker Displacement DM, DX, DY, DZ Magnitude and X, Y, Z components


of displacement.

E0, E1, E2, E3 Orientation in Euler parameters.

Marker Velocity VM, VX, VY, VZ Magnitude and X, Y, Z components


of velocity.

WM, WX, WY, WZ Magnitude and X, Y, Z components


of angular velocity.

Marker Acceleration ACCM, ACCX, ACCY, ACCZ Magnitude and X, Y, Z components


of acceleration.

WDTM, WDTX, WDTY, WDTZ Magnitude and X, Y, Z components


of angular acceleration.

Altair Engineering OptiStruct 13.0 Reference Guide 2313

Proprietary Information of Altair Engineering


Type
Component Description

Marker Force FM, FX, FY, FZ Magnitude and X, Y, Z components


of force.

TM, TX, TY, TZ Magnitude and X, Y, Z components


of torque.

Expressions F1, F2, …, F8 Vectors containing evaluated


expressions.

2314 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


_mbd.mvw file

The _mbd.mvw file is a HyperView session file.

File Creation

This file is only created when a multi-body dynamics analysis is performed. Creation of this
file is controlled by the I/O option OUTPUT.

File Contents

This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph. The file automatically creates plots for each of the results contained in the
files: _s#_a.mbd, _s#_d.mbd, and _s#_v.mbd.

Altair Engineering OptiStruct 13.0 Reference Guide 2315

Proprietary Information of Altair Engineering


_mbd.xml file

The _mbd.xml file is a MotionSolve XML file from a multi-body dynamics analysis.

File Creation

This file is created when a multi-body dynamics subcase is executed.

File Contents

The file format is documented in the MotionSolve manual. The purpose is the communication
between the OptiStruct core and the integrated MotionSolve. This file, together with the
<BODY_NAME>.h3d files, forms a full representation of the multi-body dynamics model which
can be run separately in MotionSolve.

2316 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


_menu.html file

The _menu.html file is a HyperText Markup Language file.

File Creation

This file is output when the H3D FORMAT is chosen.

File Contents

This file facilitates the selection of the appropriate .h3d file, for the HyperView Player browser
plug-in in the top frame of the _frames.html file, based on chosen results.

Comments

1. This file serves no purpose on its own.

Altair Engineering OptiStruct 13.0 Reference Guide 2317

Proprietary Information of Altair Engineering


_modal.#.mvw file

The _modal.#.mvw file is a HyperView session file.

File Creation

This file is only created for frequency response and transient analyses. Creation of this file is
controlled by the I/O option OUTPUT (with the HGMODFAC keyword).

File Contents

This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph3D. The file contains HyperGraph3D plots of modal participation factors. The plots
display the mode number on the x-axis, the frequency (for frequency response analyses) or
time (for transient analyses) on the y-axis, and the modal participation factor on the z-axis.

In HyperGraph3D, it is possible to define cross-sections to generate 2D plots of either:

Modal participation factor vs. frequency or time for a given mode number
Modal participation factor vs. mode number at a given frequency or time
For frequency response analyses, plots are generated for the real part, the imaginary part and
the magnitude of the participation factors. Magnitude plot is visible by default, while real and
imaginary plots are hidden by default.

Comments

1. The # in the file name is the iteration number.

2318 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


_modal.mvw file

The _modal.mvw file is a HyperView session file.

File Creation

This file is only created for frequency response and transient analyses. Creation of this file is
controlled by the I/O option OUTPUT (with the HGMODFAC keyword).

File Contents

This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph3D. The file contains HyperGraph3D plots of modal participation factors. The plots
display the mode number on the x-axis, the frequency (for frequency response analyses) or
time (for transient analyses) on the y-axis, and the modal participation factor on the z-axis.

In HyperGraph3D, it is possible to define cross-sections to generate 2D plots of either:

Modal participation factor vs. frequency or time for a given mode number
Modal participation factor vs. mode number at a given frequency or time
For frequency response analyses, plots are generated for the real part, the imaginary part and
the magnitude of the participation factors. Magnitude plot is visible by default, while real and
imaginary plots are hidden by default.

Comments

1. This file is generated for an analysis-only run; the _modal.#.mvw is generated for
optimization runs where # is the iteration number.

Altair Engineering OptiStruct 13.0 Reference Guide 2319

Proprietary Information of Altair Engineering


_rand.mvw file

The _rand.mvw file is a HyperView session file.

File Creation

This file is only created when random response analysis is performed. This file is only created
if XYPLOT is defined in random response.

File Contents

This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph. The file automatically creates plots for each of the results contained in .rand
files.

2320 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


_s#.h3d file

The _s#.h3d file is a compressed binary file, containing both model and result data. It can be
used to post-process results in HyperView or using the HyperView Player.

File Creation

The _s#.h3d file is created when the H3D format is chosen (See documentation for the I/O
option FORMAT), and an optimization is performed containing a linear static subcase. A similar
file is created for each static subcase.

File Contents

The _s#.h3d file contains node and element definitions in addition to the following results:

Result Description

Displacement Displacement results from linear static analysis. Output is


controlled by the I/O option DISPLACEMENT.

Element strain energy Element strain energy results from linear static analysis.
Output is controlled by the I/O option ESE.

Stress Stress results from linear static analysis. Output is controlled


by the I/O option STRESS (or ELSTRESS).

Density Density results from topology optimization. Output is controlled


by the I/O option DENSITY.

Shape Shape results from topography, shape, and free shape


optimization. Output is controlled by the I/O option SHAPE.

Comments

1. The # in the file name is the user-defined subcase ID.

2. The I/O option RESULTS controls the frequency of output for analytical results during an
optimization.

Altair Engineering OptiStruct 13.0 Reference Guide 2321

Proprietary Information of Altair Engineering


_s#_a.#.frf file

The _s#_a.#.frf file is an OptiStruct ASCII format results file.

File Creation

This file is only created for frequency response optimization. Output is controlled by the I/O
option ACCELERATION and OUTPUT,HGFREQ.

File Contents

This file contains the acceleration results from frequency response optimization.

File Format

If the real and imaginary format was selected on the ACCELERATION card, the file starts with
the following header:

Frequency "REA | X Trans"IMA | X Trans"REA | Y Trans"IMA | Y Trans"REA | Z Trans"IMA | Z


Trans

If the phase and magnitude format was selected on the DISPLACEMENT card, the file starts
with the following header:

Frequency"PHA | X Trans"MAG | X Trans"PHA | Y Trans"MAG | Y Trans"PHA | Z Trans"MAG |


Z Trans

In either case, the results are grouped by node with results for different nodes separated by a
blank line. The format of each line after the header is as follows:

Frequency X-rl/ph X-im/mag Y-rl/ph Y-im/mag Z-rl/ph Z-im/mag

where:

Frequency is the frequency at which results are calculated.

X-rl/ph is either the real component in the x-direction or the phase angle
in the x-direction component.

X-im/mag is either the imaginary component in the x-direction or the


magnitude in the x-direction component.

Y-rl/ph is either the real component in the y-direction or the phase angle
in the y-direction component.

2322 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Y-im/mag is either the imaginary component in the y-direction or the
magnitude in the y-direction component.

Z-rl/ph is either the real component in the z-direction or the phase angle
in the z-direction component.

Z-im/mag is either the imaginary component in the z-direction or the


magnitude in the z-direction component.

Comments

1. The first # in the file name is the user-defined subcase ID.

2. The second # in the file name is the iteration number.

3. The_freq.#.mvw HyperView script file automatically creates plots for the results
contained in this file.

Altair Engineering OptiStruct 13.0 Reference Guide 2323

Proprietary Information of Altair Engineering


_s#_a.frf file

The _s#_a.frf file is an OptiStruct ASCII format results file.

File Creation

This file is only created for frequency response subcases. Creation of this file is controlled by
the I/O option OUTPUT.

File Contents

Result Description

Acceleration Acceleration results from frequency response analyses. Output is


controlled by the I/O option ACCELERATION.

File Format

If the real and imaginary format was selected on the ACCELERATION card, the file starts with
the following header:

Frequency"REA | X Trans"IMA | X Trans"REA | Y Trans"IMA | Y Trans"REA | Z Trans"IMA | Z


Trans

If the phase and magnitude format was selected on the ACCELERATION card, the file starts
with the following header:

Frequency"PHA | X Trans"MAG | X Trans"PHA | Y Trans"MAG | Y Trans"PHA | Z Trans"MAG |


Z Trans

In either case the results are grouped by node with results for different nodes separated by a
blank line. The format of each line after the header is as follows:

Frequency X-rl/ph X-im/mag Y-rl/ph Y-im/mag Z-rl/ph Z-im/mag

where:

Frequency is the frequency at which results are calculated.

X-rl/ph is either the real component in the x-direction or the phase angle

2324 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


in the x-direction component.

X-im/mag is either the imaginary component in the x-direction or the


magnitude in the x-direction component.

Y-rl/ph is either the real component in the y-direction or the phase angle
in the y-direction component.

Y-im/mag is either the imaginary component in the y-direction or the


magnitude in the y-direction component.

Z-rl/ph is either the real component in the z-direction or the phase angle
in the z-direction component.

Z-im/mag is either the imaginary component in the z-direction or the


magnitude in the z-direction component.

Comments

1. The # in the file name is the user-defined subcase ID from which these results are
obtained.

2. The _freq.mvw HyperView script file automatically creates plots for the results contained
in this file.

Altair Engineering OptiStruct 13.0 Reference Guide 2325

Proprietary Information of Altair Engineering


_s#_a.mbd file

The _s#_a.mbd file is an OptiStruct ASCII format results file.

File Creation

This file is only created for Multi-Body Dynamics subcases. Creation of this file is controlled
by the I/O option OUTPUT.

File Contents

Result Description

Acceleration Acceleration results from multi-body dynamics analyses. Output is


controlled by the I/O option ACCELERATION.

File Format

Time"X Trans"Y Trans"Z Trans

Comments

1. The # in the file name is the user-defined subcase ID from which these results are
obtained.

2. The _mbd.mvw HyperView script file automatically creates plots for the results contained
in this file.

2326 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


_s#_a.trn file

The _s#_a.trn file is an OptiStruct ASCII format results file.

File Creation

This file is only created for transient response subcases. Creation of this file is controlled by
the I/O option OUTPUT.

File Contents

Result Description

Acceleration Acceleration results from frequency response analyses. Output is


controlled by the I/O option ACCELERATION.

File Format

Time"X Trans"Y Trans"Z Trans

Comments

1. The # in the file name is the user-defined subcase ID from which these results are
obtained.

2. The _tran.mvw HyperView script file automatically creates plots for the results contained
in this file.

Altair Engineering OptiStruct 13.0 Reference Guide 2327

Proprietary Information of Altair Engineering


_s#_d.#.frf file

The _s#_d.#.frf file is an OptiStruct ASCII format results file.

File Creation

This file is only created for frequency response optimization. Output is controlled by the I/O
option DISPLACEMENT and OUTPUT,HGFREQ.

File Contents

This file contains the displacement results from frequency response optimization.

File Format

If the real and imaginary format was selected on the DISPLACEMENT card, the file starts with
the following header:

Frequency"REA | X Trans"IMA | X Trans"REA | Y Trans"IMA | Y Trans"REA | Z Trans"IMA | Z


Trans

If the phase and magnitude format was selected on the DISPLACEMENT card, the file starts
with the following header:

Frequency"PHA | X Trans"MAG | X Trans"PHA | Y Trans"MAG | Y Trans"PHA | Z Trans"MAG |


Z Trans

In either case, the results are grouped by node with results for different nodes separated by a
blank line. The format of each line after the header is as follows:

Frequency X-rl/ph X-im/mag Y-rl/ph Y-im/mag Z-rl/ph Z-im/mag

where:

Frequency is the frequency at which results are calculated.

X-rl/ph is either the real component in the x-direction or the phase angle
in the x-direction component.

X-im/mag is either the imaginary component in the x-direction or the


magnitude in the x-direction component.

Y-rl/ph is either the real component in the y-direction or the phase angle
in the y-direction component.

2328 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Y-im/mag is either the imaginary component in the y-direction or the
magnitude in the y-direction component.

Z-rl/ph is either the real component in the z-direction or the phase angle
in the z-direction component.

Z-im/mag is either the imaginary component in the z-direction or the


magnitude in the z-direction component.

Comments

1. The first # in the file name is the user-defined subcase ID.

2. The second # in the file name is the iteration number.

3. The _freq.#.mvw HyperView script file automatically creates plots for the results
contained in this file.

Altair Engineering OptiStruct 13.0 Reference Guide 2329

Proprietary Information of Altair Engineering


_s#_d.frf file

The _s#_d.frf file is an OptiStruct ASCII format results file.

File Creation

This file is only created for frequency response subcases. Creation of this file is controlled by
the I/O option OUTPUT.

File Contents

Result Description

Displacement Displacement results from frequency response analyses. Output is


controlled by the I/O option DISPLACEMENT.

File Format

If the real and imaginary format was selected on the DISPLACEMENT card, the file starts with
the following header:

Frequency"REA | X Trans"IMA | X Trans"REA | Y Trans"IMA | Y Trans"REA | Z Trans"IMA | Z


Trans

If the phase and magnitude format was selected on the DISPLACEMENT card, the file starts
with the following header:

Frequency"PHA | X Trans"MAG | X Trans"PHA | Y Trans"MAG | Y Trans"PHA | Z Trans"MAG |


Z Trans

In either case, the results are grouped by node with results for different nodes separated by a
blank line. The format of each line after the header is as follows:

Frequency X-rl/ph X-im/mag Y-rl/ph Y-im/mag Z-rl/ph Z-im/mag

where:

Frequency is the frequency at which results are calculated.

X-rl/ph is either the real component in the x-direction or the phase angle

2330 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


in the x-direction component.

X-im/mag is either the imaginary component in the x-direction or the


magnitude in the x-direction component.

Y-rl/ph is either the real component in the y-direction or the phase angle
in the y-direction component.

Y-im/mag is either the imaginary component in the y-direction or the


magnitude in the y-direction component.

Z-rl/ph is either the real component in the z-direction or the phase angle
in the z-direction component.

Z-im/mag is either the imaginary component in the z-direction or the


magnitude in the z-direction component.

Comments

1. The # in the file name is the user-defined subcase ID from which these results are
obtained.

2. The _freq.mvw HyperView script file automatically creates plots for the results contained
in this file.

Altair Engineering OptiStruct 13.0 Reference Guide 2331

Proprietary Information of Altair Engineering


_s#_d.mbd file

The _s#_d.mbd file is an OptiStruct ASCII format results file.

File Creation

This file is only created for Multi-Body Dynamics subcases. Creation of this file is controlled
by the I/O option OUTPUT.

File Contents

Result Description

Displacement Displacement results from multi-body dynamics analyses. Output is


controlled by the I/O option DISPLACEMENT.

File Format

Time"X Trans"Y Trans"Z Trans

Comments

1. The # in the file name is the user-defined subcase ID from which these results are
obtained.

2. The _mbd.mvw HyperView script file automatically creates plots for the results contained
in this file.

2332 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


_s#_d.trn file

The _s#_d.trn file is an OptiStruct ASCII format results file.

File Creation

This file is only created for transient response subcases. Creation of this file is controlled by
the I/O option OUTPUT.

File Contents

Result Description

Displacement Displacement results from frequency response analyses. Output is


controlled by the I/O option DISPLACEMENT.

File Format

Time"X Trans"Y Trans"Z Trans

Comments

1. The # in the file name is the user-defined subcase ID from which these results are
obtained.

2. The _tran.mvw HyperView script file automatically creates plots for the results contained
in this file.

Altair Engineering OptiStruct 13.0 Reference Guide 2333

Proprietary Information of Altair Engineering


_s#_v.#.frf file

The _s#_v.#.frf file is an OptiStruct ASCII format results file.

File Creation

This file is only created for frequency response optimization. Output is controlled by the I/O
option VELOCITY and OUTPUT,HGFREQ.

File Contents

This file contains the velocity results from frequency response optimization.

File Format

If the real and imaginary format was selected on the VELOCITY card, the file starts with the
following header:

Frequency "REA | X Trans"IMA | X Trans"REA | Y Trans"IMA | Y Trans"REA | Z Trans"IMA | Z


Trans

If the phase and magnitude format was selected on the DISPLACEMENT card, the file starts
with the following header:

Frequency"PHA | X Trans"MAG | X Trans"PHA | Y Trans"MAG | Y Trans"PHA | Z Trans"MAG |


Z Trans

In either case, the results are grouped by node with results for different nodes separated by a
blank line. The format of each line after the header is as follows:

Frequency X-rl/ph X-im/mag Y-rl/ph Y-im/mag Z-rl/ph Z-im/mag

where:

Frequency is the frequency at which results are calculated.

X-rl/ph is either the real component in the x-direction or the phase angle
in the x-direction component.

X-im/mag is either the imaginary component in the x-direction or the


magnitude in the x-direction component.

Y-rl/ph is either the real component in the y-direction or the phase angle
in the y-direction component.

2334 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Y-im/mag is either the imaginary component in the y-direction or the
magnitude in the y-direction component.

Z-rl/ph is either the real component in the z-direction or the phase angle
in the z-direction component.

Z-im/mag is either the imaginary component in the z-direction or the


magnitude in the z-direction component.

Comments

1. The first # in the file name is the user-defined subcase ID.

2. The second # in the file name is the iteration number.

3. The _freq.#.mvw HyperView script file automatically creates plots for the results
contained in this file.

Altair Engineering OptiStruct 13.0 Reference Guide 2335

Proprietary Information of Altair Engineering


_s#_v.frf file

The _s#_v.frf file is an OptiStruct ASCII format results file.

File Creation

This file is only created for frequency response subcases. Creation of this file is controlled by
the I/O option OUTPUT.

File Contents

Result Description

Velocity Velocity results from frequency response analyses. Output is controlled


by the I/O option VELOCITY.

File Format

If the real and imaginary format was selected on the VELOCITY card, the file starts with the
following header:

Frequency"REA | X Trans"IMA | X Trans"REA | Y Trans"IMA | Y Trans"REA | Z Trans"IMA | Z


Trans

If the phase and magnitude format was selected on the VELOCITY card, the file starts with
the following header:

Frequency"PHA | X Trans"MAG | X Trans"PHA | Y Trans"MAG | Y Trans"PHA | Z Trans"MAG |


Z Trans

In either case, the results are grouped by node with results for different nodes separated by a
blank line. The format of each line after the header is as follows:

Frequency X-rl/ph X-im/mag Y-rl/ph Y-im/mag Z-rl/ph Z-im/mag

where:

Frequency is the frequency at which results are calculated.

X-rl/ph is either the real component in the x-direction or the phase angle
in the x-direction component.

2336 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


X-im/mag is either the imaginary component in the x-direction or the
magnitude in the x-direction component.

Y-rl/ph is either the real component in the y-direction or the phase angle
in the y-direction component.

Y-im/mag is either the imaginary component in the y-direction or the


magnitude in the y-direction component.

Z-rl/ph is either the real component in the z-direction or the phase angle
in the z-direction component.

Z-im/mag is either the imaginary component in the z-direction or the


magnitude in the z-direction component.

Comments

1. The # in the file name is the user-defined subcase ID from which these results are
obtained.

2. The _freq.mvw HyperView script file automatically creates plots for the results contained
in this file.

Altair Engineering OptiStruct 13.0 Reference Guide 2337

Proprietary Information of Altair Engineering


_s#_v.mbd file

The _s#_v.mbd file is an OptiStruct ASCII format results file.

File Creation

This file is only created for multi-body dynamics subcases. Creation of this file is controlled by
the I/O option OUTPUT.

File Contents

Result Description

Velocity Velocity results from multi-body dynamics analyses. Output is controlled


by the I/O option VELOCITY.

File Format

Time"X Trans"Y Trans"Z Trans

Comments

1. The # in the file name is the user-defined subcase ID from which these results are
obtained.

2. The _mbd.mvw HyperView script file automatically creates plots for the results contained
in this file.

2338 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


_s#_v.trn file

The _s#_v.trn file is an OptiStruct ASCII format results file.

File Creation

This file is only created for transient response subcases. Creation of this file is controlled by
the I/O option OUTPUT.

File Contents

Result Description

Velocity Velocity results from frequency response analyses. Output is


controlled by the I/O option VELOCITY.

File Format

Time"X Trans"Y Trans"Z Trans

Comments

1. The # in the file name is the user-defined subcase ID from which these results are
obtained.

2. The _tran.mvw HyperView script file automatically creates plots for the results contained
in this file.

Altair Engineering OptiStruct 13.0 Reference Guide 2339

Proprietary Information of Altair Engineering


_sens.#.mvw file

The _sens.#.mvw file is a HyperView session file.

File Creation

This file is created when an optimization is performed. Creation of this file is controlled by the
I/O option OUTPUT.

File Contents

This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph. The file automatically creates a histogram for each of the results contained in
the .#.sens file. The plots are grouped so that design variable sensitivities for different
responses are given on separate pages.

Comments

1. The # in the file name is the iteration number.

2340 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


_shuffling.#.fem file

The _shuffling.#.fem file is an ASCII format file.

File Creation

This file is created when OUTPUT, SZTOSH (sizing to shuffling) is requested during the ply-
based sizing optimization phase.

File Contents

This file is a ply-based stacking optimization input deck. It contains the updated PLY and
STACK cards describing the stacking model, as well as a DSHUFFLE card defining shuffling
design variables.

Comments

1. The # in the file name is the number of the last iteration.

Altair Engineering OptiStruct 13.0 Reference Guide 2341

Proprietary Information of Altair Engineering


_sizing.#.fem file

The _sizing.#.fem file is an ASCII format file.

File Creation

This file is created when OUTPUT, FSTOSZ (free-sizing to sizing) is requested during the free-
sizing optimization phase.

File Contents

This file is a ply-based sizing optimization input deck. It contains PCOMPP, STACK, PLY, and
SET cards describing the ply-based composite model, as well as DCOMP, DESVAR, and DVPREL
cards defining the optimization data.

Comments

1. The # in the file name is the number of the last iteration.

2342 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


_topol.h3d file

The _topol.h3d file is a compressed binary file containing both model and result data. It can
be used to post-process topology (density) sensitivity in HyperView.

File Creation

This file is created when an optimization is performed. Creation of this file is controlled by the
I/O option OUTPUT.

File Contents

The _topol.h3d file contains node and element definitions in addition to the following results:

Result Description

Sensitivity Sensitivity of response vs. element density from topology optimization.


Output is controlled by the I/O option OUTPUT.

Comments

1. The # in the file name is the iteration number.

Altair Engineering OptiStruct 13.0 Reference Guide 2343

Proprietary Information of Altair Engineering


_tran.mvw file

The _tran.mvw file is a HyperView session file.

File Creation

This file is only created when a transient response analysis is performed. Creation of this file
is controlled by the I/O option OUTPUT.

File Contents

This file is a HyperView session file and may be opened from the File menu in HyperView or
HyperGraph. The file automatically creates plots for each of the results contained in the files
_s#_a.trn, _s#_d.trn, and _s#_v.trn.

2344 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


<BODY_NAME>.h3d file

The <BODY_NAME>.h3d file is a compressed binary file from a multi-body dynamics analysis
that uses flexible bodies defined through a PFBODY bulk data entry.

File Creation

This file is created when a multi-body dynamics subcase is executed. One file for each
PFBODY entry is generated. BODY_NAME is taken directly from PFBODY, BODY_NAME. If no
BODY_NAME is given, the default is OUTFILE_body_<BID>.h3d. By default, the flexible body is
only generated once; and if a file already exists in the execution directory, the flexible body
generation is not repeated. The default can be changed by the parameter PARAM, FLEXH3D.

File Contents

This file contains the modal representation of the flexible body for direct use in the multi-body
dynamics solution sequence or in MotionSolve. It is generated using a Component Mode
Synthesis. Each flexible body is written to a separate file.

Altair Engineering OptiStruct 13.0 Reference Guide 2345

Proprietary Information of Altair Engineering


Results Output by OptiStruct

The tables in this section summarize the results output for different analysis types. They
show the formats available for each result and the I/O option entry that controls the output
of the result.

The columns in the tables represent the major output streams:

H3D – Hyper3D format (.h3d file)

HM – HyperMesh format (.res file)

OP2 – Nastran Output2 format (.op2 file)

PCH – Nastran Punch format (.pch file)

OPT – OptiStruct ASCII format (multiple files)

PAT – Patran and Alternative-Patran formats (multiple files)

H3D (MBD) – Hyper3D format for body results (_mbd.h3d)

MRF – Multi-body results file (_mbd.mrf)

Results for Linear Static Analysis and Nonlinear Quasi-Static Analysis

Controlling
H3D HM OP2 PCH OPT PAT
I/O Option

Nodal Displacements DISPLACEMENT

Element Strain Energy ESE

Element Stresses * STRESS

Element Strains * STRAIN

Ply Stresses CSTRESS

Composite Failure CSTRESS


Indices

Ply Strains CSTRAIN

2346 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Controlling
H3D HM OP2 PCH OPT PAT
I/O Option

Element Forces FORCE

Grid Point Stresses GPSTRESS

SPC Forces SPCFORCE

MPC Forces MPCFORCE

Grid Point Forces GPFORCE

Applied Loads OLOAD

Results for Linear Steady-state Heat Transfer Analysis

H3D OP2 PCH Controlling I/O Option

Nodal Temperatures THERMAL

Element Fluxes and FLUX


Gradients

Results for Linear Transient Heat Transfer Analysis

H3D OP2 PCH Controlling I/O Option

Nodal Temperatures THERMAL

Altair Engineering OptiStruct 13.0 Reference Guide 2347

Proprietary Information of Altair Engineering


Results for Normal Modes Analysis

Controlling
H3D HM OP2 PCH OPT PAT
I/O Option

Eigenvectors DISPLACEMENT

Element Kinetic Energy EKE

Element Strain Energy ESE

Grid Point Energy GPKE

Grid Point Stress GPSTRESS

Element Stresses * STRESS

SPC Forces SPCFORCE

MPC Forces MPCFORCE

Grid Point Forces GPFORCE

Nodal Pressures (Fluid) PRESSURE

Ply Stresses CSTRESS

Ply Strains CSTRAIN

Results for Complex Eigenvalue Analysis

Controlling
H3D OP2 PCH
I/O Option

Eigenvectors DISPLACEMENT

2348 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Results for Linear Buckling Analysis

Controlling
H3D HM OP2 PCH OPT
I/O Option

Eigenvectors DISPLACEMENT

Results for Frequency Response Analysis

Controlling
H3D HM OP2 PCH OPT XYPUNCH
I/O Option

Nodal Displacements DISPLACEMENT

Modal Participation SDISPLACEMENT


Displacements

Element Energy Loss Per EDE


Cycle

Element Kinetic Energy EKE

Element Strain Energy ESE

Nodal Velocities VELOCITY

Modal Participation Velocities SVELOCITY

Nodal Accelerations ACCELERATION

Modal Participation SACCELERATION


Accelerations

Element Stresses * STRESS

Element Strains * STRAIN

Altair Engineering OptiStruct 13.0 Reference Guide 2349

Proprietary Information of Altair Engineering


Controlling
H3D HM OP2 PCH OPT XYPUNCH
I/O Option

Element Forces FORCE

SPC Forces SPCFORCE

MPC Forces MPCFORCE

Grid Point Forces GPFORCE

Power Flow Field POWERFLOW

Ply Stresses CSTRESS

Ply Strains CSTRAIN

Sound Power SPOWER

Sound Intensity SINTENS

Sound Pressure Level SPL

Applied Load Vectors OLOAD

Results for Coupled Frequency Response Analysis of Fluid-structural Models (Acoustic


Analysis)

H3D OP2 PCH Controlling I/O Option

Nodal Displacements DISPLACEMENT

Modal Participation SDISPLACEMENT


Displacements

Nodal Velocities VELOCITY

2350 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


H3D OP2 PCH Controlling I/O Option

Modal Participation Velocities SVELOCITY

Nodal Accelerations ACCELERATION

Modal Participation SACCELERATION


Accelerations

Nodal Pressures (Fluid) PRESSURE

Element Stresses * STRESS

Element Strains * STRAIN

Element Forces FORCE

SPC Forces SPCFORCE

MPC Forces MPCFORCE

Grid Point Forces GPFORCE

Power Flow Field POWERFLOW

Ply Stress CSTRESS

Ply Strain CSTRAIN

Results for Transient Analysis

H3D HM OP2 PCH OPTI Controlling


I/O Option

Nodal Displacements DISPLACEMENT

Altair Engineering OptiStruct 13.0 Reference Guide 2351

Proprietary Information of Altair Engineering


H3D HM OP2 PCH OPTI Controlling
I/O Option

Modal Participation SDISPLACEMENT


Displacements

Nodal Velocities VELOCITY

Modal Participation Velocities SVELOCITY

Nodal Accelerations ACCELERATION

Modal Participation SACCELERATION


Accelerations

Element Stresses * STRESS

Element Strains * STRAIN

Element Forces FORCE

MPC Forces MPCFORCE

Ply Stresses CSTRESS

Ply Strains CSTRAIN

Composite Failure Indices CSTRESS

Applied Load Vectors OLOAD

Results for Random Response Analysis (PSDF Request)

XYPLOT
XYPUNCH PUNCH OP2 H3D
(HyperGraph)

DISP / VELO / ACCE

2352 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


XYPLOT
XYPUNCH PUNCH OP2 H3D
(HyperGraph)

Shell Stress

Shell Strain

Solid Stress

Solid Strain

CBUSH Force

CELAS / CDAMP / CVISC


Forces

Results for Random Response Analysis

OP2 PCH H3D Controlling I/O Option

Displacement PSD and DISP, XYPEAK, XYPLOT, XYPUNCH


RMS

Velocity PSD and RMS VELO, XYPEAK, XYPLOT, XYPUNCH

Acceleration PSD and ACCEL, XYPEAK, XYPLOT, XYPUNCH


RMS

PSD Element Force and FORCE, XYPEAK, XYPLOT, XYPUNCH


RMS

PSD Element Stress STRESS, XYPEAK, XYPLOT, XYPUNCH

PSD Element Strain STRAIN, XYPEAK, XYPLOT, XYPUNCH

RMS Element Stress STRESS

Altair Engineering OptiStruct 13.0 Reference Guide 2353

Proprietary Information of Altair Engineering


RMS Element Strain STRAIN

Results for Multi-body Dynamics Analysis

H3D HM OP2 H3D MRF Controlling


(MBD) I/O Option

Nodal Displacements DISPLACEMENT

Nodal Velocities VELOCITY

Nodal Accelerations ACCELERATION

Element Stresses * STRESS

Element Strains * STRAIN

Body time history

System time history

Marker time history REQUEST

Results for Fatigue Analysis

H3D Controlling I/O Option

Element Life LIFE

Element Damage DAMAGE

2354 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Results for Geometric Nonlinear Analysis (ANALYSIS=NLGEOM, IMPDYN or EXPDYN)

Controlling
Controlling
H3D OP2 PCH I/O Option
I/O Option
(Block Format)

/ANIM/VECT/DISP
Nodal Displacements DISPLACEMENT
/ANIM/VECT/DROT

Nodal Velocities VELOCITY /ANIM/VECT/VEL

Nodal Accelerations ACCELERATION /ANIM/VECT/ACC

/ANIM/BRICK/TENS/
STRESS
/ANIM/SHELL/TENS/
STRESS/UPPER
Element Stresses* STRESS /ANIM/SHELL/TENS/
STRESS/LOWER
/ANIM/BEAM/VONM
/ANIM/TRUSS/SIGX

/ANIM/BRICK/TENS/
STRAIN
/ANIM/SHELL/TENS/
Element Strains* STRAIN
STRAIN/UPPER
/ANIM/SHELL/TENS/
STRAIN/LOWER

/ANIM/SHELL/TENS/
STRESS/N
Ply Stresses CSTRESS
/ANIM/SHELL/TENS/
STRESS/ALL

/ANIM/SHELL/TENS/
Ply Strains CSTRAIN
STRAIN/ALL

Composite Failure
CSTRESS N/A
Indices

Element Forces FORCE /ANIM/Eltyp/FORC

/ANIM/GPS1/TENS
Grid Point Stresses GPSTRESS
/ANIM/GPS1/SHELL/

Altair Engineering OptiStruct 13.0 Reference Guide 2355

Proprietary Information of Altair Engineering


Controlling
Controlling
H3D OP2 PCH I/O Option
I/O Option
(Block Format)

UPPER
/ANIM/GPS1/SHELL/
LOWER

/ANIM/VECT/FREAC
SPC Forces SPCFORCE
/ANIM/VECT/MREAC

MPC Forces MPCFORCE /ANIM/VECT/FINT

Applied Loads OLOAD /ANIM/VECT/FEXT

/ANIM/ELEM/EPSP
/ANIM/SHELL/EPSP/
STRAIN
Plastic Strain UPPER
(PLASTIC)
/ANIM/SHELL/EPSP/
LOWER

Contact Force and /ANIM/VECT/CONT


CONTF
Pressure /ANIM/VECT/PCONT

Element Thinning and /ANIM/ELEM/THIC


THIN
Thickness /ANIM/SHELL/THIN

/ANIM/ELEM/ENER
Element Energy ENERGY
/ANIM/ELEM/HOURG

Optimization Results

Controlling
H3D HM OP2 PCH OPT PAT
I/O Option

Element Density DENSITY

Element Thickness THICKNESS

2356 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Controlling
H3D HM OP2 PCH OPT PAT
I/O Option

Ply Thickness THICKNESS

% Thickness THICKNESS

Shape SHAPE

* The element stress and strain results written to the various output streams are not
always the same. Refer to the following pages for more details on the stress results
available in the different output streams:
Strain Results Written in HyperView .h3d Format
Strain Results Written in Nastran .op2 and .pch Formats
Strain Results Written in HyperMesh .res Format
Stress Results Written in HyperView .h3d Format
Stress Results Written in Nastran .op2 and .pch Format
Stress Results Written in HyperMesh .res Format

Altair Engineering OptiStruct 13.0 Reference Guide 2357

Proprietary Information of Altair Engineering


Strain Results Written in HyperView .h3d Format

1D Elements

ALL, DIRECT and TENSOR options


Von Mises Strain
CELAS Strain
CROD Axial Strain
CBAR Longitudinal Strain SAC
CBAR Longitudinal Strain SAD
CBAR Longitudinal Strain SAE
CBAR Longitudinal Strain SAF
CBAR Longitudinal Strain SAMIN
CBAR Longitudinal Strain SAMAX
CBAR Longitudinal Strain SBC
CBAR Longitudinal Strain SBD
CBAR Longitudinal Strain SBE
CBAR Longitudinal Strain SBF
CBAR Longitudinal Strain SBMIN
CBAR Longitudinal Strain SBMAX
CWELD Axial Strain
CWELD Maximum Strain A
CWELD Minimum Strain A
CWELD Maximum Strain B
CWELD Minimum Strain B
CWELD Maximum Shear Strain

VON and PRINC options


Von Mises Strain
1D Elements (CBAR/CBEAM via PBARL/PBEAML)

The following strain results are output for CBAR/CBEAM elements defined via PBARL/PBEAML
property entries. The Result type: HyperView is CBAR/CBEAM Strains (<TYPE>), where the
<TYPE> entry is based on the selected cross-section (TYPE/NAME field) on the PBARL/PBEAML
entries. The element strain results can be reviewed for each cross-section type,
corresponding evaluation point, at element ends (A or B). The maximum normal/shear/von
Mises strains can also be reviewed.

Syntax

- CBAR/CBEAM Strains (<Type>)

<Strain Result Output> <evaluation point> (A/B)

Where,

<Type> = BAR, BOX, BOX1, CHAN, CHAN1, CHAN2, CROSS, H, HAT, I, I1, ROD, T, T1,
T2, TUBE, Z.
<Strain Result Output> = normal, shear, and von Mises
<evaluation point> = evaluation point of the element

2358 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Examples

- CBAR/CBEAM Strains(BAR)

Normal S1N(A)
Normal S1N(B)
Shear S4S(A)
Shear S4S(B)
von Mises S8V(A)
von Mises S8V(B)

Example descriptions

Normal S3N(B): normal strain at the 3rd evaluation point of the beam element (end B);

Shear S6S(A): shear strain at the 6th evaluation point of the beam element (end A);

von Mises S5V(B): von Mises strain at the 5th evaluation point of the beam element (end
B).

Review evaluation points via: DRESP1 - Static Strain Item Codes for Bar Elements using
PBARL, PBEAML Properties

The von Mises strains for all CBEAM/CBAR elements with PBARL/PBEAML properties at the same
time can be output using the Result type: CBAR/CBEAM vonMises Strains.

Syntax

- CBAR/CBEAM vonMises Strains

<Strain Result Output>

Where,

<Strain Result Output> = Von Mises

2D Elements

ALL and TENSOR options

Results are calculated by HyperView.

DIRECT option
Von Mises Strain
Maximum Principal Strain
Von Mises Strain (Z1)
Von Mises Strain (Z2)
Von Mises Strain (mid)
P1 (major) Strain (Z1)
P1 (major) Strain (Z2)
P1 (major) Strain (mid)

Altair Engineering OptiStruct 13.0 Reference Guide 2359

Proprietary Information of Altair Engineering


P3 (minor) Strain (Z1)
P3 (minor) Strain (Z2)
P3 (minor) Strain (mid)
Normal X Strain (Z1)
Normal X Strain (Z2)
Normal X Strain (mid)
Normal Y Strain (Z1)
Normal Y Strain (Z2)
Normal Y Strain (mid)
Shear XY Strain (Z1)
Shear XY Strain (Z2)
Shear XY Strain (mid)
Principal Strain Angle (Z1)
Principal Strain Angle (Z2)
Principal Strain Angle (mid)

VON option
Von Mises Strain - This is equal to max[Von Mises Strain (Z1), Von Mises Strain
(Z2)]

PRINC option
Von Mises Strain
Maximum Principal Strain

3D Elements

ALL and TENSOR options

Results are calculated by HyperView.

DIRECT option
Von Mises Strain
Signed Von Mises Strain
P1 (major) Strain (solid)
P2 (mid) Strain (solid)
P3 (minor) Strain (solid)
Normal X Strain (solid)
Normal Y Strain (solid)
Normal Z Strain (solid)
Shear XY Strain (solid)
Shear YZ Strain (solid)
Shear XZ Strain (solid)

VON option
Von Mises Strain

PRINC option

2360 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Von Mises Strain
Maximum Principal Strain

Comments

1. In the TENSOR mode, pass tensor components to HyperView which then calculates derived
results on-the-fly.

2. For frequency response loadcases, only the TENSOR mode is available.

Altair Engineering OptiStruct 13.0 Reference Guide 2361

Proprietary Information of Altair Engineering


Strain Results Written in Nastran .op2 and .pch Formats

Static, Transient and Multi-body Loadcases

1D elements
CROD Axial Strain

CELAS Strain

CBAR SA1
CBAR SA2
CBAR SA3
CBAR SA4
CBAR Axial
CBAR SA-maximum
CBAR SA-minimum
CBAR SB1
CBAR SB2
CBAR SB3
CBAR SB4
CBAR SB-maximum
CBAR SB-minimum

CBEAM Long Strain at Point C1


CBEAM Long Strain at Point D1
CBEAM Long Strain at Point E1
CBEAM Long Strain at Point F1
CBEAM Maximum Strain1
CBEAM Minimum Strain1
CBEAM Long Strain at Point C2
CBEAM Long Strain at Point D2
CBEAM Long Strain at Point E2
CBEAM Long Strain at Point F2
CBEAM Maximum Strain2
CBEAM Minimum Strain2

2D elements
Fibre Distance (Z1)
Normal XX Strain (Z1)
Normal YY Strain (Z1)
Shear XY Strain (Z1)
Principal Strain Angle (Z1)
Major Principal Strain (Z1)
Minor Principal Strain (Z1)
Von Mises Strain (Z1)
Fibre Distance (Z2)
Normal XX Strain (Z2)
Normal YY Strain (Z2)
Shear XY Strain (Z2)

2362 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Principal Strain Angle (Z2)
Major Principal Strain (Z2)
Minor Principal Strain (Z2)
Von Mises Strain (Z2)

3D elements
Normal XX Strain
Shear XY Strain
Major Principal Strain
Major Principal X Cosine
Mid Principal X Cosine
Minor Principal X Cosine
Mean Strain
Von Mises Strain
Normal YY Strain
Shear YZ Strain
Mid Principal Strain
Major Principal Y Cosine
Mid Principal Y Cosine
Minor Principal Y Cosine
Normal ZZ Strain
Shear XZ Strain
Minor principal Strain
Major Principal Y Cosine
Mid Principal Y Cosine
Minor Principal Y Cosine

Eigenvalue Loadcases

1D elements
None.

2D elements
Fibre Distance (Z1)
Normal XX Strain (Z1)
Normal YY Strain (Z1)
Shear XY Strain (Z1)
Principal Strain Angle (Z1)
Major Principal Strain (Z1)
Minor Principal Strain (Z1)
Von Mises Strain (Z1)
Fibre Distance (Z2)
Normal XX Strain (Z2)
Normal YY Strain (Z2)
Shear XY Strain (Z2)
Principal Strain Angle (Z2)
Major Principal Strain (Z2)
Minor Principal Strain (Z2)

Altair Engineering OptiStruct 13.0 Reference Guide 2363

Proprietary Information of Altair Engineering


Von Mises Strain (Z2)
3D elements

Normal XX Strain
Shear XY Strain
Major Principal Strain
Major Principal X Cosine
Mid Principal X Cosine
Minor Principal X Cosine
Mean Strain
Von Mises Strain
Normal YY Strain
Shear YZ Strain
Mid Principal Strain
Major Principal Y Cosine
Mid Principal Y Cosine
Minor Principal Y Cosine
Normal ZZ Strain
Shear XZ Strain
Minor principal Strain
Major Principal Y Cosine
Mid Principal Y Cosine
Minor Principal Y Cosine

Frequency Response Loadcases

1D elements
CROD Axial Strain

CELAS Strain

CBAR SA1
CBAR SA2
CBAR SA3
CBAR SA4
CBAR Axial
CBAR SA-maximum
CBAR SA-minimum
CBAR SB1
CBAR SB2
CBAR SB3
CBAR SB4
CBAR SB-maximum
CBAR SB-minimum

CBEAM Long Strain at Point C1


CBEAM Long Strain at Point D1
CBEAM Long Strain at Point E1
CBEAM Long Strain at Point F1

2364 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CBEAM Maximum Strain1
CBEAM Minimum Strain1
CBEAM Long Strain at Point C2
CBEAM Long Strain at Point D2
CBEAM Long Strain at Point E2
CBEAM Long Strain at Point F2
CBEAM Maximum Strain2
CBEAM Minimum Strain2

2D elements
Fibre Distance (Z1)
Normal XX Strain (real) (Z1)
Normal XX Strain (imag) (Z1)
Normal YY Strain (real) (Z1)
Normal YY Strain (imag) (Z1)
Shear XY Strain (real) (Z1)
Shear XY Strain (imag) (Z1)
Fibre Distance (Z2)
Normal XX Strain (real) (Z2)
Normal XX Strain (imag) (Z2)
Normal YY Strain (real) (Z2)
Normal YY Strain (imag) (Z2)
Shear XY Strain (real) (Z2)
Shear XY Strain (imag) (Z2)

3D elements
Normal XX Strain (real)
Normal YY Strain (real)
Normal ZZ Strain (real)
Shear XY Strain (real)
Shear YZ Strain (real)
Shear XZ Strain (real)
Normal XX Strain (imag)
Normal YY Strain (imag)
Normal ZZ Strain (imag)
Shear XY Strain (imag)
Shear YZ Strain (imag)
Shear XZ Strain (imag)

Comments

1. The order above reflects the contents of the OP2 file, but post-processors such as
HyperView may display results in a different manner.

Altair Engineering OptiStruct 13.0 Reference Guide 2365

Proprietary Information of Altair Engineering


Strain Results Written in HyperMesh .res Format

Static, Eigenvalue, Transient and Multi-body Loadcases

ALL, DIRECT and TENSOR options


Von Mises Strain
Maximum Principal Strain
Von Mises Strain (Z1)
Von Mises Strain (Z2)
Von Mises Strain (mid)
P1 (major) Strain (Z1)
P1 (major) Strain (Z2)
P1 (major) Strain (mid)
P1 (major) Strain (max)
P3 (minor) Strain (Z1)
P3 (minor) Strain (Z2)
P3 (minor) Strain (mid)
P3 (minor) Strain (min)
Normal X Strain (Z1)
Normal X Strain (Z2)
Normal X Strain (mid)
Normal Y Strain (Z1)
Normal Y Strain (Z2)
Normal Y Strain (mid)
Shear XY Strain (Z1)
Shear XY Strain (Z2)
Shear XY Strain (mid)
Principal Strain Angle (Z1)
Principal Strain Angle (Z2)
Principal Strain Angle (mid)
Signed Von Mises Strain (solid)
P1 (major) Strain (solid)
P2 ( mid ) Strain (solid)
P3 (minor) Strain (solid)
Normal X Strain (solid)
Normal Y Strain (solid)
Normal Z Strain (solid)
Shear XY Strain (solid)
Shear YZ Strain (solid)
Shear XZ Strain (solid)

VON option
Von Mises Strain

PRINC option
Von Mises Strain
Maximum Principal Strain

2366 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Frequency Response Loadcases
Normal X Strain (Z1) (comp)
Normal X Strain (Z2) (comp)
Normal Y Strain (Z1) (comp)
Normal Y Strain (Z2) (comp)
Shear XY Strain (Z1) (comp)
Shear XY Strain (Z2) (comp)
Normal X Strain (solid) (comp)
Normal Y Strain (solid) (comp)
Normal Z Strain (solid) (comp)
Shear XY Strain (solid) (comp)
Shear YZ Strain (solid) (comp)
Shear XZ Strain (solid) (comp)

Comments

1. "von Mises Strain" and "Maximum Principal Strain" apply to 1D, 2D, and 3D elements
simultaneously. Other results apply to 2D or 3D elements exclusively. There are no
specific results for 1D elements.

2. For frequency response loadcases, (comp) may be replaced by (real) (imag) (magn) and/or
(phas), depending on the complex format request.

3. "Maximum Principal Strain" is the maximum absolute principal strain:

max(abs(P1(Z1)),abs(P1(Z2)),abs(P3(Z1)),abs(P3(Z2))) for shells.


max(abs(P1),abs(P2),abs(P3)) for solids.

4. "P1 (major) Strain (max)" is the maximum major principal strain:


max(P1(Z1),P1(Z2)).

5. "P3 (minor) Strain (min)" is the minimum minor principal strain:


min(P3(Z1),P3(Z2)).

6. "Signed von Mises Strain" is the von Mises strain with traction/compression sign:
sign(P1+P2+P3) * VonMises.

Altair Engineering OptiStruct 13.0 Reference Guide 2367

Proprietary Information of Altair Engineering


Stress Results Written in HyperView .h3d Format

1D Elements

ALL, DIRECT and TENSOR options


Von Mises Stress
CELAS Stress
CROD Axial Stress
CBAR Longitudinal Stress SAC
CBAR Longitudinal Stress SAD
CBAR Longitudinal Stress SAE
CBAR Longitudinal Stress SAF
CBAR Longitudinal Stress SAMIN
CBAR Longitudinal Stress SAMAX
CBAR Longitudinal Stress SBC
CBAR Longitudinal Stress SBD
CBAR Longitudinal Stress SBE
CBAR Longitudinal Stress SBF
CBAR Longitudinal Stress SBMIN
CBAR Longitudinal Stress SBMAX
CWELD Axial Stress
CWELD Maximum Stress A
CWELD Minimum Stress A
CWELD Maximum Stress B
CWELD Minimum Stress B
CWELD Maximum Shear Stress
CWELD Bearing Stress

VON and PRINC options


Von Mises Stress

1D Elements (CBAR/CBEAM via PBARL/PBEAML)

The following stress results are output for CBAR/CBEAM elements defined via PBARL/PBEAML
property entries. The Result type: HyperView is CBAR/CBEAM Stresses (<TYPE>), where the
<TYPE> entry is based on the selected cross-section (TYPE/NAME field) on the PBARL/PBEAML
entries. The element stress results can be reviewed for each cross-section type,
corresponding evaluation point, at element ends (A or B). The maximum normal/shear/von
Mises stresses can also be reviewed.

Syntax

- CBAR/CBEAM Stresses (<Type>)

<Stress Result Output> <evaluation point> (A/B)

Where,

<Type> = BAR, BOX, BOX1, CHAN, CHAN1, CHAN2, CROSS, H, HAT, I, I1, ROD, T, T1,
T2, TUBE, Z.

2368 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


<Stress Result Output> = normal, shear, and von Mises
<evaluation point> = evaluation point of the element
Examples

- CBAR/CBEAM Stresses(BAR)

Normal S1N(A)
Normal S1N(B)
Shear S4S(A)
Shear S4S(B)
von Mises S8V(A)
von Mises S8V(B)

Example descriptions

Normal S3N(B): normal stress at the 3rd evaluation point of the beam element (end B);

Shear S6S(A): shear stress at the 6th evaluation point of the beam element (end A);

von Mises S5V(B): von Mises stress at the 5th evaluation point of the beam element (end
B).

Review evaluation points via: DRESP1 - Static Stress Item Codes for Bar Elements using
PBARL, PBEAML Properties

The von Mises stresses for all CBEAM/CBAR elements with PBARL/PBEAML properties at the
same time can be output using the Result type: CBAR/CBEAM vonMises Stresses.

Syntax

- CBAR/CBEAM vonMises Stresses

<Stress Result Output>

Where,

<Stress Result Output> = Von Mises

2D Elements

ALL and TENSOR options

Results are calculated by HyperView.

DIRECT option
Von Mises Stress
Maximum Principal Stress
Von Mises Stress (Z1)
Von Mises Stress (Z2)

Altair Engineering OptiStruct 13.0 Reference Guide 2369

Proprietary Information of Altair Engineering


Von Mises Stress (mid)
P1 (major) Stress (Z1)
P1 (major) Stress (Z2)
P1 (major) Stress (mid)
P3 (minor) Stress (Z1)
P3 (minor) Stress (Z2)
P3 (minor) Stress (mid)
Normal X Stress (Z1)
Normal X Stress (Z2)
Normal X Stress (mid)
Normal Y Stress (Z1)
Normal Y Stress (Z2)
Normal Y Stress (mid)
Shear XY Stress (Z1)
Shear XY Stress (Z2)
Shear XY Stress (mid)
Principal Stress Angle (Z1)
Principal Stress Angle (Z2)
Principal Stress Angle (mid)

VON option - This is equal to max[Von Mises Stress (Z1), Von Mises Stress (Z2)]

PRINC option
Von Mises Stress
Maximum Principal Stress

3D Elements

ALL and TENSOR options

Results are calculated by HyperView.

DIRECT option
Von Mises Stress
Signed Von Mises Stress
P1 (major) Stress (solid)
P2 (mid) Stress (solid)
P3 (minor) Stress (solid)
Normal X Stress (solid)
Normal Y Stress (solid)
Normal Z Stress (solid)
Shear XY Stress (solid)
Shear YZ Stress (solid)
Shear XZ Stress (solid)

VON option
Von Mises Stress

2370 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PRINC option
Von Mises Stress
Maximum Principal Stress

Comments

1. In the TENSOR mode, pass tensor components to HyperView, which then calculates
derived results on-the-fly.

2. For frequency response loadcases, only the TENSOR mode is available.

Altair Engineering OptiStruct 13.0 Reference Guide 2371

Proprietary Information of Altair Engineering


Stress Results Written in Nastran .op2 and .pch Formats

Static, Transient and Multi-body Loadcases

1D elements
CROD Axial Stress

CELAS Stress

CBAR SA1
CBAR SA2
CBAR SA3
CBAR SA4
CBAR Axial
CBAR SA-maximum
CBAR SA-minimum
CBAR SB1
CBAR SB2
CBAR SB3
CBAR SB4
CBAR SB-maximum
CBAR SB-minimum

CBEAM Long Stress at Point C1


CBEAM Long Stress at Point D1
CBEAM Long Stress at Point E1
CBEAM Long Stress at Point F1
CBEAM Maximum Stress1
CBEAM Minimum Stress1
CBEAM Long Stress at Point C2
CBEAM Long Stress at Point D2
CBEAM Long Stress at Point E2
CBEAM Long Stress at Point F2
CBEAM Maximum Stress2

CBEAM Minimum Stress2

2D elements
Fibre Distance (Z1)
Normal XX Stress (Z1)
Normal YY Stress (Z1)
Shear XY Stress (Z1)
Principal Stress Angle (Z1)
Major Principal Stress (Z1)
Minor Principal Stress (Z1)
Von Mises Stress (Z1)
Fibre Distance (Z2)
Normal XX Stress (Z2)
Normal YY Stress (Z2)

2372 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Shear XY Stress (Z2)
Principal Stress Angle (Z2)
Major Principal Stress (Z2)
Minor Principal Stress (Z2)
Von Mises Stress (Z2)

3D elements
Normal XX Stress
Shear XY Stress
Major Principal Stress
Major Principal X Cosine
Mid Principal X Cosine
Minor Principal X Cosine
Mean Stress
Von Mises Stress
Normal YY Stress
Shear YZ Stress
Mid Principal Stress
Major Principal Y Cosine
Mid Principal Y Cosine
Minor Principal Y Cosine
Normal ZZ Stress
Shear XZ Stress
Minor principal Stress
Major Principal Y Cosine
Mid Principal Y Cosine
Minor Principal Y Cosine

Eigenvalue Loadcases

1D elements
None

2D elements
Fibre Distance (Z1)
Normal XX Stress (Z1)
Normal YY Stress (Z1)
Shear XY Stress (Z1)
Principal Stress Angle (Z1)
Major Principal Stress (Z1)
Minor Principal Stress (Z1)
Von Mises Stress (Z1)
Fibre Distance (Z2)
Normal XX Stress (Z2)
Normal YY Stress (Z2)
Shear XY Stress (Z2)
Principal Stress Angle (Z2)
Major Principal Stress (Z2)
Minor Principal Stress (Z2)

Altair Engineering OptiStruct 13.0 Reference Guide 2373

Proprietary Information of Altair Engineering


Von Mises Stress (Z2)
3D elements
Normal XX Stress
Shear XY Stress
Major Principal Stress
Major Principal X Cosine
Mid Principal X Cosine
Minor Principal X Cosine
Mean Stress
Von Mises Stress
Normal YY Stress
Shear YZ Stress
Mid Principal Stress
Major Principal Y Cosine
Mid Principal Y Cosine
Minor Principal Y Cosine
Normal ZZ Stress
Shear XZ Stress
Minor principal Stress
Major Principal Y Cosine
Mid Principal Y Cosine
Minor Principal Y Cosine

Frequency Response Loadcases

1D elements
CROD Axial Stress

CELAS Stress

CBAR SA1
CBAR SA2
CBAR SA3
CBAR SA4
CBAR Axial
CBAR SA-maximum
CBAR SA-minimum
CBAR SB1
CBAR SB2
CBAR SB3
CBAR SB4
CBAR SB-maximum
CBAR SB-minimum

CBEAM Long Stress at Point C1


CBEAM Long Stress at Point D1
CBEAM Long Stress at Point E1
CBEAM Long Stress at Point F1
CBEAM Maximum Stress1
CBEAM Minimum Stress1

2374 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


CBEAM Long Stress at Point C2
CBEAM Long Stress at Point D2
CBEAM Long Stress at Point E2
CBEAM Long Stress at Point F2
CBEAM Maximum Stress2
CBEAM Minimum Stress2

2D elements
Fibre Distance (Z1)
Normal XX Stress (real) (Z1)
Normal XX Stress (imag) (Z1)
Normal YY Stress (real) (Z1)
Normal YY Stress (imag) (Z1)
Shear XY Stress (real) (Z1)
Shear XY Stress (imag) (Z1)
Fibre Distance (Z2)
Normal XX Stress (real) (Z2)
Normal XX Stress (imag) (Z2)
Normal YY Stress (real) (Z2)
Normal YY Stress (imag) (Z2)
Shear XY Stress (real) (Z2)
Shear XY Stress (imag) (Z2)

3D elements
Normal XX Stress (real)
Normal YY Stress (real)
Normal ZZ Stress (real)
Shear XY Stress (real)
Shear YZ Stress (real)
Shear XZ Stress (real)
Normal XX Stress (imag)
Normal YY Stress (imag)
Normal ZZ Stress (imag)
Shear XY Stress (imag)
Shear YZ Stress (imag)
Shear XZ Stress (imag)

Comments

1. The order above reflects the contents of the OP2 file, but post-processors such as
HyperView may display results in a different manner.

2. For 2D elements, results are printed at the center of the element, followed by results at
each grid when corner stresses are requested.

3. For 3D elements, results are printed at the center of the element, followed by results at
each grid when corner stresses are requested. In the OP2 format, regardless of the
corner stress request, results are printed at each grid by duplicating results at the
center.

Altair Engineering OptiStruct 13.0 Reference Guide 2375

Proprietary Information of Altair Engineering


Stress Results Written in HyperMesh .res Format

Static, Eigenvalue, Transient and Multi-body Loadcases

ALL, DIRECT and TENSOR options


Von Mises Stress
Maximum Principal Stress
Von Mises Stress (Z1)
Von Mises Stress (Z2)
Von Mises Stress (mid)
P1 (major) Stress (Z1)
P1 (major) Stress (Z2)
P1 (major) Stress (mid)
P1 (major) Stress (max)
P3 (minor) Stress (Z1)
P3 (minor) Stress (Z2)
P3 (minor) Stress (mid)
P3 (minor) Stress (min)
Normal X Stress (Z1)
Normal X Stress (Z2)
Normal X Stress (mid)
Normal Y Stress (Z1)
Normal Y Stress (Z2)
Normal Y Stress (mid)
Shear XY Stress (Z1)
Shear XY Stress (Z2)
Shear XY Stress (mid)
Principal Stress Angle (Z1)
Principal Stress Angle (Z2)
Principal Stress Angle (mid)
Signed Von Mises Stress (solid)
P1 (major) Stress (solid)
P2 ( mid ) Stress (solid)
P3 (minor) Stress (solid)
Normal X Stress (solid)
Normal Y Stress (solid)
Normal Z Stress (solid)
Shear XY Stress (solid)
Shear YZ Stress (solid)
Shear XZ Stress (solid)

VON option
Von Mises Stress

PRINC option
Von Mises Stress
Maximum Principal Stress

2376 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Frequency response loadcases
Normal X Stress (Z1) (comp)
Normal X Stress (Z2) (comp)
Normal Y Stress (Z1) (comp)
Normal Y Stress (Z2) (comp)
Shear XY Stress (Z1) (comp)
Shear XY Stress (Z2) (comp)
Normal X Stress (solid) (comp)
Normal Y Stress (solid) (comp)
Normal Z Stress (solid) (comp)
Shear XY Stress (solid) (comp)
Shear YZ Stress (solid) (comp)
Shear XZ Stress (solid) (comp)
Comments

1. "von Mises Stress" and "Maximum Principal Stress" apply to 1D, 2D, and 3D elements
simultaneously. Other results apply to 2D or 3D elements exclusively. There are no
specific results for 1D elements.

2. For frequency response loadcases, (comp) may be replaced by (real) (imag) (magn) and/or
(phas), depending on the complex format request.

3. "Maximum Principal Stress" is the maximum absolute principal stress:


max(abs(P1(Z1)),abs(P1(Z2)),abs(P3(Z1)),abs(P3(Z2))) for shells.
max(abs(P1),abs(P2),abs(P3)) for solids.

4. "P1 (major) Stress (max)" is the maximum major principal stress:


max(P1(Z1),P1(Z2)).

5. "P3 (minor) Stress (min)" is the minimum minor principal stress:


min(P3(Z1),P3(Z2)).

6. "Signed von Mises Stress" is the von Mises stress with traction/compression sign:
sign(P1+P2+P3) * VonMises.

Altair Engineering OptiStruct 13.0 Reference Guide 2377

Proprietary Information of Altair Engineering


Legacy Data
Previous (OS3.5) Input Format
Setting Up Decks in OptiStruct 5.0 and higher with OptiStruct 3.5 Objectives and Constraints
Previously Supported Input

2378 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Previous (OS3.5) Input Format

OptiStruct will continue to support the old input format from version 3.5. The new
optimization capabilities will not be available if the old format is used for the set up of the
optimization problem, that is, if matfrac, mini, maxi, ubcon or lbcon are present.

This section is intended to be used for the purpose of debugging or re-running older decks.

OptiStruct Version 3.5 Parameters:

Checkerboard 0,1,2, or blank Controls checkerboarding. Use 0 for no


(default = 0, checkerboard control. Use 1 or blank for global
if card not in deck) averaging over the entire design domain. This
option generally yields a large number of semi-
(Default = 1, if blank) dense elements around fully dense elements.
To reduce the number of semi-dense elements
in the solution, restart the final iteration with
checkerboard control off and run for 10-20
iterations. This may reintroduce some local
checkerboarding. This method is used with
plate/shell and solid design elements and is
highly recommended for tetra elements. Nodal
densities are output to the .res file if this
option is used. Use 2 for averaging at local
areas identified as checkerboarded. Since
averaging is only applied locally, a much smaller
number of semi-dense elements are found in the
final iteration compared to the global averaging
method. This method applies only to plate/shell
design elements. If used in models with solid
design elements, checkerboard control is not
applied to solid elements.

OptiStruct errors out if this parameter is


repeated on DOPTPRM in the bulk data section.

Discrete <real>default = 1.0 Discreteness parameter. Influences the


tendency for elements to converge to a
material density of 0 or 1. Higher values
decrease the number of elements that remain
between 0 and 1. Recommended bounds are
0.0 and 2.0.

OptiStruct errors out if this parameter is


repeated on DOPTPRM in the bulk data section.

Dcomp <integer> Shell elements with PCOMP PID given on this


card will be placed in the topology design
domain. This card overrides declarations in the
bulk data deck.

Altair Engineering OptiStruct 13.0 Reference Guide 2379

Proprietary Information of Altair Engineering


Dshell <integer>no Shell elements with PSHELL PID given in first
def<real>def=0.0 field of DSHELL card will be placed into the
topology design domain with T0 given in the
second field. This card overrides declarations in
the bulk data deck.

Dsolid <integer> Solid elements with PSOLID PID given on this


card will be placed into the topology design
domain. This card overrides declarations in bulk
data deck.

Matinit <real>def. = 0.9 or This card declares the initial material fraction.
constraint val. For runs with mass as the objective, default is
0.9. For runs with constrained mass, default is
reset to constraint value.

OptiStruct errors out if this parameter is


repeated on DOPTPRM in the bulk data section.

Maxiter <integer>default = 30 Maximum number of iterations. Sets an upper


limit on the number of iterations OptiStruct can
perform before completion. If maxiter = 0,
baseline analysis is conducted after initializing
material fractions of all design elements at the
matfrac value. If check is present, it overrides
maxiter = 0. If analysis is present, it overrides
maxiter = 0.

OptiStruct errors out if this parameter is


repeated on DOPTPRM in the bulk data section.

Mindens <real>default = 0.01 Minimum element material density. Sets a lower


limit on the amount of material that can be
assigned to any design element. Extremely low
values for this parameter can result in an ill-
conditioned stiffness matrix.

OptiStruct errors out if this parameter is


repeated on DOPTPRM in the bulk data section.

Minmember <real>no Specifies the minimum diameter of members


default<method> formed by OptiStruct. This also eliminates
default= 2 checkerboard results. This command is used to
eliminate small members. Method is either 1 or
2. Method 2 is set as default since it achieves
more discrete solutions for most examples.

OptiStruct errors out if this parameter is


repeated on DOPTPRM in the bulk data section.

2380 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Mmcheck No input The use of this card will ensure a checkerboard
free solution, although with the undesired side
effect of achieving a solution that involves a
large number of semi-dense elements, similar to
the result of using CHECKER=1. Therefore, use
this card only when it is necessary.

OptiStruct errors out if this parameter is


repeated on DOPTPRM in the bulk data section.

Objtol <real>default = 0.005 Tolerance in objective function. If the


fractional change in objective function is below
this quantity for two consecutive iterations, the
optimization is considered converged and is
stopped.

OptiStruct errors out if this parameter is


repeated on DOPTPRM in the bulk data section.

Smooth <real>default = Solution smoothness. Influences the step size


0.7071 of the optimization iterations if the optimality
criteria method is used for topology
optimization. Changing this parameter generally
results in changes in the solution topology.
Larger values of this parameter create smoother
topologies for shell element models. Leave this
parameter at the default value, unless a
different solution topology is desired.
Recommended bounds are 0.5 and 0.9.

OptiStruct Version 3.5 Subcase Information:

lbcon <real> <integer*> Sets a lower bound constraint of value given


<string> <integer*> in the first field of this card for the response
no given in the second field of the card.
defaults Supported responses are: volume, mass, disp,
comp, freq, wcomp, wfreq, and comb. Global
responses (volume, mass, wcomp, wfreq, and
comb) must be located outside of all subcase
declarations. Local responses (comp, freq,
and disp) must be located within a subcase
declaration. The third field is used for mode
number declarations for freq responses or grid
number declarations for disp responses. The
fourth field is used for grid component
declarations for disp responses.

Mass <real> Mass of total model. If present, the matfrac


parameter is not used. Input the total target

Altair Engineering OptiStruct 13.0 Reference Guide 2381

Proprietary Information of Altair Engineering


no default mass for the part and OptiStruct calculates
the material fraction automatically. If the
computed material fraction is below 0.0 or
above 1.0, OptiStruct returns an error. Not
available if using multiple material types in the
design domain.

Matfrac <real> Material fraction. Defines the amount of


default = 0.30 material to be distributed within the design
range = 0.0-1.0 domain as a fraction of the design domain.
For shell elements, design volume is equal to
(T - T0) * area. For solid elements, design
volume is equal to the sum of the volume of
the elements designated as design space.
The design volume multiplied by the material
fraction is the total amount of design material
available. Material fractions for all design
elements in the design space are initialized to
matfrac value.

maxi <string> <integer*> Sets objective function to maximize a


no default <integer*> response. Supported responses are: volume,
mass, disp, comp, freq, wcomp, wfreq, and
comb. Global responses (volume, mass,
wcomp, wfreq, and comb) must be located
outside of all subcase declarations. Local
responses (comp, freq, and disp) must be
located within a subcase declaration. The
second field is used for mode number
declarations for freq responses or grid number
declarations for disp responses. The fourth
field is used for grid component declarations
for disp responses.

mini <string> <integer*> Sets objective function to minimize a


no default <integer*> response. Supported responses are: volume,
mass, disp, comp, freq, wcomp, wfreq, and
comb. Global responses (volume, mass,
wcomp, wfreq, and comb) must be located
outside of all subcase declarations. Local
responses (comp, freq, and disp) must be
located within a subcase declaration. The
second field is used for mode number
declarations for freq responses or grid number
declarations for disp responses. The fourth
field is used for grid component declarations
for disp responses.

Primary <integer This card sets which mode of eigenvalue


solution is used to set material orientation

2382 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


or blank> angles. Primary mode declaration only applies
default= to runs without static analyses and must be
lowest placed in the subcase declaration. If the card
mode with is placed in a static subcase, only that
highest subcase is used to determine material
weight if orientation angle - no fields are necessary.
eigen.
Subcase
no default
if static.

ubcon <real> <integer*> Sets an upper bound constraint of value given


<string> <integer*> in the first field of this card for the response
no given in the second field of the card.
defaults Supported responses are: volume, mass, disp,
comp, freq, wcomp, wfreq, and comb. Global
responses (volume, mass, wcomp, wfreq, and
comb) must be located outside of all subcase
declarations. Local responses (comp, freq,
and disp) must be located within a subcase
declaration. The third field is used for mode
number declarations for freq responses or grid
number declarations for disp responses. The
fourth field is used for grid component
declarations for disp responses.

Altair Engineering OptiStruct 13.0 Reference Guide 2383

Proprietary Information of Altair Engineering


Setting Up Decks in OptiStruct 5.0 with OptiStruct 3.5
Objectives and Constraints

Setting up an optimization was simpler in OptiStruct 3.5, but it was also very limited. Starting
with OptiStruct 5.0, a lot more flexibility has been added to the way objectives and
constraints are set up, but the problem setup is more complex. Although versions of
OptiStruct (including and beyond 5.0) will execute OptiStruct 3.5 decks flawlessly, users are
urged to create decks using the new optimization format. This section demonstrates how
objectives and constraints in OptiStruct 3.5 (such as comp, freq, wcomp, wfreq, and comb)
can be set up in OptiStruct 5.0 and higher.

The new optimization capabilities of OptiStruct 5.0 and higher will not be available if the old
format is used for the setup of the optimization problem (if matfrac, mini, maxi, ubcon, or
lbcon are present in the setup).

Minimize Compliance for Constrained Mass Fraction

In OptiStruct 3.5, two cards were used to do this kind of optimization: mini, comp and ubcon,
0.3, volume.

The new setup is as follows: mini, comp is replaced by DESOBJ(MIN) = 1 and ubcon, 0.3,
volume is replaced by DESGLB = 101. Three cards (two DRESP1s and one DCONSTR) defining
the responses and constraint values referenced in the header are added after the BEGIN BULK
statement as shown below:
$
DESGLB = 101
$
SUBCASE 1
LOAD = 2
SPC = 1
DESOBJ(MIN) = 1
$
BEGIN BULK
$
DRESP1, 1, comp, COMP
DRESP1, 100, massf, MASSFRAC
DCONSTR, 101, 100, , 0.300
$

Minimize Mass for Constrained Displacement

The deck setup for this problem is similar to the previous one. Since the objective is global
(mass), the DESOBJ statement goes outside of the load case definition. The constraint on
displacement is only active for the first load case; thus a DESSUB statement is used within
that load case.
$
DESOBJ(MIN) = 1
$
SUBCASE 1
LOAD = 2
SPC = 1
DESSUB = 101

2384 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


$
BEGIN BULK
$
DRESP1, 1, weight, MASS
$
DRESP1, 100, disp, DISP, , , 7, , 1202
DCONSTR, 101, 100, , 1.4e-6
$

Minimize Weighted Compliance for Constrained Mass

OptiStruct provides the response type WCOMP, weighted compliance, to be defined on the
DRESP1 card. In addition, you need to define the weight factors for each load case included
in the weighted compliance function. Note that both the objective and constraint are global
quantities (not specific to any single load case) and thus the DESOBJ and DESGLB statements
occur before the load case declarations.
$
DESOBJ = 50
DESGLB = 101
$
SUBCASE 1
LOAD = 2
SPC = 1
WEIGHT = 2.0
$
SUBCASE 2
LOAD = 3
SPC = 1
WEIGHT = 1.0
$
BEGIN BULK
$
DRESP1, 50, wcomp, WCOMP
$
DRESP1, 100, weight, MASS
DCONSTR, 101, 100, , 1.560
$

Maximize Frequency for Constrained Volume

The setup for this deck is similar to that for the first two decks except that, starting with
OptiStruct 5.0, the volume response now refers to the actual volume (not the volume
fraction).
$
DESGLB = 101
$
SUBCASE 1
METHOD = 2
SPC = 1
DESOBJ(MAX) = 1
$

Altair Engineering OptiStruct 13.0 Reference Guide 2385

Proprietary Information of Altair Engineering


BEGIN BULK
$
DRESP1, 1, freq1, FREQ, , , 1
$
DRESP1, 100, vol, VOLUME
DCONSTR, 101, 100, , 20000.0
$

Maximize Weighted Frequencies for Constrained Volume

In OptiStruct 3.5, the weighted frequency response (wfreq), was minimized since the inverse
of the eigenvalues was being summed together. This was done so that increasing the
frequencies of the lower modes would have a larger effect on the objective function than
increasing the frequencies of the higher modes. If the frequencies of all modes are simply
added together, OptiStruct will put more effort into increasing the higher modes than the
lower modes. Note that the DESOBJ statement goes above the first load case since wfreq is
a global response. To duplicate the frequency weighting and summing in OptiStruct 3.5, use
the following approach:
$
DESGLB = 101
$
DESOBJ(MIN) = 11
SUBCASE 1
METHOD = 2
SPC = 1
MODEWEIGHT, 1, 1.0
MODEWEIGHT, 2, 1.0
$
BEGIN BULK
$
DRESP1, 11, wfreq, WFREQ
$
DRESP1, 100, vol, VOLUME
DCONSTR, 101, 100, , 20000.0
$

Minimize Combined Compliance and Frequencies for Constrained Volume Fraction

In OptiStruct 3.5, the combined reciprocal frequency and compliance response (comb)
required a normalization factor in order to properly add frequency values and compliance. The
equivalent setup for OptiStruct 5.0 and higher is shown below.

If no NORM is given, OptiStruct will evaluate the frequencies and compliances in the initial
iteration step to automatically select a NORM factor.
$
DESOBJ(MIN) = 50
DESGLB = 101
$
NORM = 1000.0
$
SUBCASE 1

2386 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


LOAD = 2
SPC = 1
WEIGHT = 1.0
$
SUBCASE 2
LOAD = 3
SPC = 1
WEIGHT = 1.0
$
SUBCASE 3
METHOD = 10
SPC = 1
MODEWEIGHT, 1, 1.5
MODEWEIGHT, 2, 1.0
$
BEGIN BULK
$
DRESP1, 50, comp, COMB
$
DRESP1, 100, volf, VOLFRAC
DCONSTR, 101, 100, , 0.300
$

Altair Engineering OptiStruct 13.0 Reference Guide 2387

Proprietary Information of Altair Engineering


Previously Supported Input
BEAD (Not Supported in 8.0 or Later Versions)
MASSTOH3D (Not Supported in 8.0 or Later Versions)
ROTATION (Not Supported in 8.0 or Later Versions)
DOPTPRM, MINMETH (Not Supported in 8.0 or Later Versions)
PARAM, PRTRENUM (Not Supported in 9.0 or Later Versions)
INFILE (Not Supported in 10.0 or Later Versions)
PARAM, GAPOFFST (Not Supported in 10.0 or Later Versions)
SET/PSET (Not Recommended for use in 10.0 or Later Versions)
DENSRES (Not Recommended for use in 10.0 or Later Versions)
SHRES (Not Recommended for use in 10.0 or Later Versions)
FLSPOUT (Not Supported in 11.0 or Later Versions)
PARAM, INRGAP (Not Supported in 11.0 or Later Versions)
MODELMPC (Not Supported in 12.0 or Later Versions)
PARAM, AMLSASPC (Not Supported in 12.0 or Later Versions)
UPDATE (Not Supported in 12.0 or Later Versions)

2388 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


BEAD (Not Supported in 8.0 or Later Versions)

Bulk Data Entry

BEAD – Topography Design Variables

Description

Defines parameters for the generation of topography design variables.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

BEAD BID MW ANG BF HGT norm/ YD ZD SKIP


XD

FID/XF YF ZF AID/XA YA ZA LB UB TYP

SID/XS YS ZS UC YC

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

BEAD 1 3.0 60.0 yes 5.0 norm both

0.0 1.0 0.0 0.0 25.0 0.0 50

1.0 0.0 0.0 3

Field Contents

BID PID or DID (Integer > 0; no default). This field can contain the PSHELL
or PCOMP property ID of the elements or the desvar number of any set
of DVGRIDs present in the deck to be optimized for topography. If field
6 contains data, OptiStruct will assume that the BEAD card references
a property, otherwise it assumes that the card references a DESVAR
and its corresponding DVGRIDs.

Altair Engineering OptiStruct 13.0 Reference Guide 2389

Proprietary Information of Altair Engineering


Field Contents

MW Bead minimum width (Real > 0.0; no default). This parameter controls
the width of the beads in the model [recommended value between 1.5
and 2.5 times the average element width]. See comment 1.

ANG Draw angle in degrees (1.0 < Real < 89.0; no default). This parameter
controls the angle of the sides of the beads [recommended value
between 60 and 75 degrees]. See comment 1.

BF Buffer zone (‘yes’ or ‘no’; default = ‘yes’). This parameter will establish
a buffer zone between elements in the design domain and elements
outside the design domain.

HGT Draw height: (Real > 0.0; no default). This parameter sets the
maximum height of the beads to be drawn. This field is only valid if a
PID is declared in field 2.

norm/XD,YD,ZD Draw direction (‘norm’ in field 7 or Real in all three fields; default =
‘norm’). If field 7 is ‘norm’, the shape variables will be created in the
normal directions of the elements. If all the fields are real, the shape
variable will be created in the direction specified by the xyz vector
defined by fields 7, 8, and 9. The X, Y, and Z values are in the basic
coordinate system. This field is only valid if a PID is declared in field 2.

SKIP Boundary skip (‘both’, ‘bc’, ‘spc’, ‘load’, or ‘none’; default = ‘both’). This
parameter tells OptiStruct to leave certain nodes out of the design
domain. If ‘none’, all nodes attached to elements whose PID was
specified in field 2 will be a part of the shape variables. If ‘bc’ or ‘spc’,
any nodes which have SPC or SPC1 declarations are omitted from the
design domain. If ‘load’, any nodes which have FORCE, FORCE1,
MOMENT, MOMENT1, or SPCD declarations are omitted from the design
domain. If ‘both’, nodes with either ‘spc’ or ‘load’ declarations are
omitted from the design domain. This field is only valid if a PID is
declared in field 2.

FID/XF,YF,ZF Direction of first vector for variable pattern grouping (Real in all three
fields or Integer in field 12; default = blank). These fields define an xyz
vector which determines how grids are grouped into variables. The X,
Y, and Z values are in the global coordinate system. You may put a
grid ID in field 12 to define the first vector. This vector goes from the
anchor point to this grid. If all fields are blank and field 20 is not blank
or zero, OptiStruct gives an error.

AID/XA,YA,ZA Variable grouping pattern anchor point (Real in all three fields or integer
in field 15; default = blank). These fields define a point which

2390 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Field Contents

determines how grids are grouped into variables. The X, Y, and Z


values are in the global coordinate system. You may put a grid ID in
field 15 to define the anchor point.

LB Lower bound on variables controlling grid movement (Real < UB, default
= 0.0). This sets the lower bound on grid movement equal to LB*HGT.

UB Upper bound on variables controlling grid movement (Real > LB, default
= 1.0). This sets the upper bound on grid movement equal to UB*HGT.

TYP Type of variable grouping pattern. (Integer > 0, default = 0) Required


if any symmetry or variable pattern grouping is desired. If zero or
blank, anchor node, first vector, and second vector definitions are
ignored. If less than 20, second vector definition is ignored.

SID/XS,YS,ZS Direction used to determine second vector for variable pattern grouping
(Real in all three fields or Integer in field 22; default = blank). These
fields define an xyz vector which, when combined with the first vector,
form a plane. The second vector is calculated to lie in that plane and
is perpendicular to the first vector. The second vector is sometimes
required to determine how grids are grouped into variables. The X, Y,
and Z values are in the global coordinate system. You may put a grid
ID in field 22 to define the second vector. This vector goes from the
anchor point to this grid. If all fields are blank and field 20 contains a
value of 20 or higher, OptiStruct gives an error.

UCYC Number of cyclical repetitions for cyclical symmetry (Integer > 0 or


blank; default = 0). This field defines the number of radial "wedges" for
cyclical symmetry. The angle of each wedge is computed as 360.0 /
UCYC.

Comments

1. The BEAD bulk data entry will no longer be supported for the definition of topography
optimization. All definitions must be provided using the DTPG bulk data entry. HyperMesh
will continue to read BEAD entries, but will convert them into DTPG entries.

Altair Engineering OptiStruct 13.0 Reference Guide 2391

Proprietary Information of Altair Engineering


DOPTPRM, MINMETH (Not Supported in 8.0 or Later
Versions)

Parameter Values Description

MINMETH Integer = 1,2 Specifies the method of minimum member size control.
Default = 2 Method 2 is set as default since it achieves more
discrete solutions for most examples.

2392 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MASSTOH3D (Not Supported in 8.0 or Later Versions)

I/O Options Entry

MASSTOH3D - Output Request

Description

The MASSTOH3D command can be used in the I/O Options section to request the output of the
mass matrix to the .h3d file.

Format
MASSTOH3D = option

Argument Options Description

option <YES, ALL, NO, NONE, YES, ALL, blank: Mass matrix is output to .h3d
blank> file.

Default = ALL
NO, NONE: Mass matrix is not output.

Comments

1. Mass matrix is not output if this card is not present.

2. This option is only for use with MotionView's MBD Flexbody utility.

Altair Engineering OptiStruct 13.0 Reference Guide 2393

Proprietary Information of Altair Engineering


ROTATION (Not Supported in 8.0 or Later Versions)

I/O Options Entry

ROTATION - Output Request

Description

The ROTATION command can be used in the I/O Options or Subcase Information sections to
request the output of rotation information for all subcases or individual subcases respectively.

Format
ROTATION (format, form) = option

Argument Options Description

format <HM, H3D, OPTI, HM: Results are output in HyperMesh


PUNCH, OUTPUT2, results format (.res file).
PATRAN, APATRAN,
blank> H3D: Results are output in Hyper3D
format (.h3d file).
Default = blank

OPTI: Results are output in OptiStruct


results format (.disp file).

PUNCH: Results are output in Nastran punch


results format (.pch file).

OUTPUT2: Results are output in Nastran


output2 format (.op2 file).

PATRAN: Results are output in Patran format


(multiple files).

APATRAN: Results are output in Alternative


Patran format (multiple files).

blank: Results are output in all active


formats for which the result is
available.

2394 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


Argument Options Description

form <COMPLEX, REAL, COMPLEX, blank: Provides a combined magnitude/


IMAG, PHASE, phase form of complex output to
BOTH> the .res file if HM output format is
chosen. The REAL form of complex
Default = COMPLEX output is used for other formats, if
they are not specifically defined.
(Phase output is in degrees).

REAL, IMAG: Provides rectangular format (real


and imaginary) of complex output.

PHASE: Provides polar format (magnitude


and phase) of complex output.
Phase output is in degrees.

BOTH: Provides both polar and rectangular


formats of complex output.

option <YES, ALL, YES, ALL, blank: Rotations are output for all nodes.
NO, NONE, SID>

Default = ALL NO, NONE: Rotations are not output.

SID: If a set ID is given, rotations are


output only for nodes listed in that
set.

Comments

1. When a ROTATION command is not present, rotations are not output.

2. The form argument is only applicable for frequency response analysis. It is ignored for
other analysis types.

3. The form BOTH does not apply to the .frf output files. Results are output to these files
using the rectangular form of complex output when BOTH is the chosen form.

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

Altair Engineering OptiStruct 13.0 Reference Guide 2395

Proprietary Information of Altair Engineering


5. Multiple instances of this card are allowed; if instances are conflicting, the last instance
dominates.

6. For optimization, the frequency of output to a given format is controlled by the I/O option
OUTPUT. In previous versions of OptiStruct, a combination of the I/O options FORMAT
and RESULTS were used; this method is still supported, but not recommended as it does
not allow different frequencies for different formats.

2396 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


FLSPOUT (Not Supported in 11.0 or Later Versions)

I/O Options and Subcase Information Entry

FLSPOUT – Output Request

Description

The FLSPOUT command can be used in the I/O Options section to control output of modal
participation factors for coupled fluid-structure models.

Format

FLSPOUT(argument = option, argument = option, ...)

Argument Options Description

FLUIDMP <ALL, NONE> Requests fluid participation calculation of fluid response on


selected fluid points.
Default = NONE
ALL: Requests that all the fluid modes extracted be
used.

NONE: Requests no participation calculation.

GRIDFMP <SID> Requests inclusion or exclusion of specific fluid grids to be


used in all the requested types of participation
No default calculations.

SID: Set identification number - Results are output


only for fluid grids listed in the selected set.

FEPS <Real> Filter Threshold for fluid participation.

Default = 1.0e-11

ARF <Real> Acceptance ratio for fluid participation.

Default = 1.0e-11

Altair Engineering OptiStruct 13.0 Reference Guide 2397

Proprietary Information of Altair Engineering


Argument Options Description

STRUCTMP <ALL, NONE> Requests structural, load, and panel participation


calculations on the selected fluid points.
Default = NONE
ALL: Requests that all the structural modes extracted
be used.

NONE: Requests no participation calculation.

PANELMP <ALL> Requests inclusion or exclusion of panel participation


calculations on the selected fluid points.
Default = ALL
ALL: Requests that all the panels defined be included
in the participation calculations on the selected
fluid points.

SEPS <Real> Filter Threshold for structural participation.

Default = 1.0e-11

ARS <Real> Acceptance ratio for structural participation.

Default = 1.0e-11

PSORT <ABSOLUTE> Requests type of sort.

Default =
ABSOLUTE

Comments

1. GRIDFMP is required for all FLSPOUT statements.

2. FLUIDMP and STRUCTMP are required when PANELMP is defined.

3. The output file name for modal participation is *.modal.

2398 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


MODELMPC (Not Supported in 12.0 or Later Versions)

Subcase Information Entry

MODELMPC –

Description

MODELMPC command can be used in the Subcase Information section while including h3d DMIG
in residual runs. This card converts interior DOFs of the DMIG to exterior DOFs.

Format
MODELMPC = setdof

Examples
MODELMPC = 100

SET,100,GRIDC,

+,10643,T1,10643,T2,10643,T3

Argument Option Description

setdof < SID > Interior DOF of h3d DMIG to be converted into exterior
DOF. SID refers to the ID of a SET of type GRIDC.

Comments

1. After the conversion with MODELMPC, these DOFs are part of the analysis DOFs and can be
used as connection points, load DOFs, response DOFs during optimization.

Altair Engineering OptiStruct 13.0 Reference Guide 2399

Proprietary Information of Altair Engineering


PARAM, AMLSASPC (Not Supported in 12.0 or Later
Versions)

Parameter Values Description

AMLSASPC 0, 1 This parameter is used to indicate when to automatically


Default = 0 constrain degrees-of-freedom with no stiffness for AMLS
run.

If 0, then the constraints are applied before constraint


reduction.

If 1, then the constraints are applied after constraint


reduction.

2400 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, GAPOFFST (Not Supported in 10.0 or Later
Versions)

Parameter Values Description

GAPOFFST YES, NO If YES, frictional offset for nonlinear gap analysis is


Default = YES active.

If NO, frictional offset for nonlinear gap analysis in


inactive.

For more details, refer to the PGAP description.

Altair Engineering OptiStruct 13.0 Reference Guide 2401

Proprietary Information of Altair Engineering


PARAM, INRGAP (Not Supported in 11.0 or Later
Versions)

Parameter Values Description

INRGAP <YES, NO> PARAM, INRGAP can be used during nonlinear gap analysis
Default = NO to improve the performance for some models. In this
method, an internal super element which includes all of
the gap elements is created automatically, and the
nonlinear iterations are only processed in this super
element. If the degrees-of-freedom associated with gap
elements make up less than 3% of the total degrees-of-
freedom and the gap elements are concentrated in one
area of the model, this approach may be beneficial.
However, a performance gain is not guaranteed.

2402 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


PARAM, PRTRENUM (Not Supported in 9.0 or Later
Versions)

Parameter Values Description

PRTRENUM <YES, NO, LIST> If YES, prints a warning message when element
Default = YES nodes have been renumbered, including the number
of such elements. (Renumbering is applied to
elements that have node sequence reversed with
respect to the standard numbering as described on
respective bulk data cards).

If NO, no such message is printed.

If LIST, the warning message is printed for every


element where renumbering was necessary. The
message includes the node list before and after
renumbering.

Altair Engineering OptiStruct 13.0 Reference Guide 2403

Proprietary Information of Altair Engineering


UPDATE (Not Supported in 12.0 or Later Versions)

I/O Options and Subcase Information Entry

UPDATE – Input Definition

Description

The UPDATE command controls the behavior of ASSIGN,UPDATE,<filename>.

Format

UPDATE option

Option Description

off Disable update.

permissive Allow all cards and repeat IDs.

quiet Less output [default].

strict Do not allow non-supported cards in update deck


[default].

unique Each ID only once.

verbose More output including old and new values.

Example
UPDATE verbose,unique

Comments

1. Choose only one option: verbose or quiet.

2. Choose only one option: unique, strict, permissive, or off.

2404 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


INFILE (Not Supported in 10.0 or Later Versions)

I/O Options Entry

INFILE - File Selection

Description

The INFILE command is used in the I/O Options section to identify the file containing the bulk
data entries.

Format
INFILE = option

Argument Option Description

option <file prefix> file prefix: The path to and prefix of the .fem
file containing the bulk data entries.
Default = passed
in from the
command line.

Comments

1. This card is used in the obsolete two-file setup; the one-file or multiple-file setups are
recommended (see The Input File for more information).

2. Prefixes specified on the INFILE card can be arbitrary file prefixes with optional paths
appropriate to the operating system (Windows or UNIX). They may be enclosed in
quotes (double or single quotes can be used), and either forward slash (/) or back slash
(\) characters can be used to separate parts of the path name.

The following rules are used to locate a file referenced on the INFILE card:

When the argument contains the absolute path of the file (if it starts with "/" on UNIX
or a drive letter, such as "D:", on Windows, for example), the file at the given location
is used.
When only the file prefix is given (without the path), the file has to be located in the
same directory as the file containing the INFILE command.
When the argument contains a relative path (../filename or sub/filename, for
example), it is located in the directory relative to the file containing the INFILE
command and is NOT relative to the directory in which the solver was executed, or to
the directory where the main file is located.
3. The total length of information on this card is limited to 200 characters (including the card
name and spaces between arguments). This data can be on a single line or span multiple
continuation lines. See Guidelines for I/O Options and Subcase Information Entries for an
example showing how to enter long file names on multiple lines.

Altair Engineering OptiStruct 13.0 Reference Guide 2405

Proprietary Information of Altair Engineering


SET/PSET (Not Recommended for use in 10.0 or Later
Versions)

I/O Options and Subcase Information Entry

SET - Set Definition

PSET - Set Definition

Description

The SET and PSET commands can be used in the I/O Options or Subcase Information section
input deck to define sets of grids, elements, properties, or frequencies.

Format

SET n = i1, i2, …, in Integer sets are used for sets of grids,
elements, modes, and design variables.

SET n = r1, r2, …, rn Real value sets are used for frequencies or
times.

SET n = i1, c1, i2, c2, …, in, cn Sets of Gird/Component pairs are used for
PFMODE data.

Example:
SET 24 = 12, T1, 15, R2, 128, T3

(alternatively 12/T1, 15/R2, 128/T3 is


acceptable, see Guidelines for I/O Options
and Subcase Information Entries).

PSET n = PID1, PID2, …, PIDn Property identification numbers are used for
property set definition.

Comments

1. Every SET must have a unique identification number, n, regardless of whether the SET is
defined within a subcase or in the I/O Options section. Also, a SET cannot have the same
ID as a PSET or the bulk data entries SET, SET1, or SURF.

2. From 10.0 onwards, it is recommended to use the SET bulk data entry for set definitions.

2406 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


DENSRES (Not Recommended for use in 10.0 or Later
Versions)

I/O Options Entry

DENSRES - Output Control

Description

The DENSRES command can be used in the I/O Options section to control the frequency of
output of design results (density, shape, or thickness).

Format
DENSRES = frequency

Argument Options Description

frequency <FIRST, LAST, FIRST: Optimization results are output for the first
FL, ALL, N> iteration only.

Default = ALL
LAST: Optimization results are output for the final
iteration only.

FL: Optimization results are output for the first


and last iterations only.

ALL, blank: Optimization results are output for all


iterations.

N: Optimization results are output for the first


and last iterations and every Nth iteration.
If N = 5, output occurs for iterations 0, 5,
10, 15, 20, and so on, and the final
iteration.

Comments

1. This output control is ignored if OUTPUT, DESIGN is present.

2. When the DENSRES command is not present, results are output for all iterations.

3. From 10.0 onwards, it is recommended to use the OUTPUT I/O Option entry to control this
output.

Altair Engineering OptiStruct 13.0 Reference Guide 2407

Proprietary Information of Altair Engineering


SHRES (Not Recommended for use in 10.0 or Later
Versions)

I/O Options Entry

SHRES - Output Control

Description

The SHRES command can be used in the I/O Options section to control the frequency of
output of the state files (.sh file and the .grid file).

Format

SHRES = frequency

Argument Options Description

frequency <FIRST, LAST, FIRST: The files are output for the first
FL, ALL, NONE, N> iteration only.

Default = LAST
LAST, blank: The files are output for the final
iteration only.

FL: The files are output for both the


first and last iterations.

ALL: The files are output for all


iterations.

NONE: The files are not output.

N: The files are output for the first


and last iterations and for every
Nth iteration. If N = 5, output
occurs for iterations 0, 5, 10, 15,
20, and so on, and the final
iteration. All equation and
combination responses are output.

Comments

1. When a SHRES command is not present, state files are output for the final iteration only.

2. The .grid file is only output for shape, topography, and free-shape optimization.

2408 OptiStruct 13.0 Reference Guide Altair Engineering

Proprietary Information of Altair Engineering


3. For all .sh and .grid output files bar the last one, the files are named
<prefix><iter#>.sh(.grid). The last one is just named <prefix>.sh(.grid).

4. The .grid file output may also be controlled by the GRID keyword on the OUTPUT card.

5. From 10.0 onwards, it is recommended to use the OUTPUT I/O Option entry to control this
output.

Altair Engineering OptiStruct 13.0 Reference Guide 2409

Proprietary Information of Altair Engineering

You might also like