OptiStruct configuration files may be used to establish default settings for OptiStruct. Configuration files must be named optistruct.cfg. Any errors or warnings caused by the content of these files will be echoed to the screen only.
Any default setting will be ignored if it is defined by an environment variable (see Running OptiStruct), input deck entry (see Reference Guide), or command line argument (see Options for Running OptiStruct).
The configuration file allows default settings to be established on five different levels:
System level
- If a configuration file is located in the ${ALTAIR_HOME}/optistruct directory on Windows or in the ${ALTAIR_HOME}/os directory on UNIX or LINUX, the default settings defined in this file apply to all OptiStruct runs.
- A configuration file is included in the installation at this location. This configuration file contains all of the configuration file options in a comment format. Uncommenting an option will activate it. This file may be used as a template for all configuration files.
- If the ${ALTAIR_HOME} environment variable is not set, then the configuration file at this location will not be used. This variable is automatically set when the recommended HyperWorks or OptiStruct installation and execution procedures are followed.
Corporate level
- If a configuration file is located in the ${HW_CORPORATE_CUSTOMIZATION_DIR} directory, the default settings defined in this file are added to the system defaults.
- If a default setting, which was defined at the system level, is redefined at this level, the redefined setting is used.
- If the ${HW_CORPORATE_CUSTOMIZATION_DIR} environment variable is not set, then the configuration file at this location will not be used.
Group level
- If a configuration file is located in the ${HW_GROUP_CUSTOMIZATION_DIR} directory, the default settings defined in this file are added to the system and corporate defaults.
- If a default setting, which was defined at the system or corporate level, is redefined at this level, the redefined setting is used.
- If the ${HW_GROUP_CUSTOMIZATION_DIR} environment variable is not set, then the configuration file at this location will not be used.
User level
- If a configuration file is located in the ${HOME} directory, the default settings defined in this file are added to the system, corporate and group defaults.
- If a default setting, which was defined at the system, corporate or group level, is redefined at this level, the redefined setting is used.
- If the ${HOME} environment variable is not set, then the configuration file at this location will not be used. This variable is normally set for UNIX and LINUX operating systems to point to a user's home directory, but it may vary for different versions of the Windows operating system.
Local level
- If a configuration file is located in the current directory, the default settings defined in this file are added to the system, corporate, group and user defaults.
- If a default setting, which was defined at the system, corporate, group or user level, is redefined at this level, the redefined setting is used.
Entries and Format
Below is a list of entries recognized in the configuration file. As stated above, the configuration file contained in the installation may be used as a template for other configuration files.
The format of the entries (with the exception of ELEMQUAL) is similar to the format of the I/O Options in the input deck, namely:
ENTRY = Argument
Comments may be inserted using the $ character; which indicates that everything which follows on that line is a comment.
ELEMQUAL is a recognized entry in the configuration file. It is used as described in the bulk data entry description ELEMQUAL with the condition that it must be written in free format (See Guidelines for Bulk Data Entries).
Entry |
Argument |
Description |
|
DOS_DRIVE_$ |
Path |
Same as DOS_DRIVE_$ environment variable (see Running OptiStruct). |
|
SYNTAX |
<ALLOWINT, STRICT> |
The SYNTAX entry controls how strict the syntax checker in the reader is. 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 (e.g. 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 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 parameter never changes results – it can only cause the rejection of files that do not follow the restrictions. |
|
SPSYNTAX |
<STRICT, CHECK, |
Same as I/O option SPSYNTAX. |
|
LOADTEMP |
<SHAREID> |
The LOADTEMP entry allows backward compatibility for thermal loading. Prior to OptiStruct 8.0, there was no TEMPERATURE subcase selector; instead, TEMP bulk data entries were selected with the LOAD subcase selector. This option allows TEMP bulk data entries to be selected by the LOAD subcase selector, as in pre-OptiStruct 8.0 analyses. |
|
OS_RAM |
RAM in Mbytes |
Same as OS_RAM environment variable (see Running OptiStruct). |
|
OS_RAM_INIT |
RAM in Mbytes |
Same as OS_RAM_INIT environment variable (see Running OptiStruct). |
|
RAM_SAFETY_FACTOR |
Multiplier |
Same as -rsf option for running OptiStruct (see Options for Running OptiStruct). |
|
FORMAT |
<HM, H3D,
ASCII, |
Same as I/O option FORMAT . |
|
SCREEN |
<OUT, LOG, NONE> |
Same as I/O option SCREEN . |
|
TMPDIR |
Path |
Same as I/O option TMPDIR . |
|
SCRFMODE |
<BASIC, BUFFERED, UNBUFFERED, STRIPE, OVERFLOW, RAMDISK> |
Same as I/O Option SCRFMODE. |
|
CHECKEL |
<YES, NO, FULL> |
Same as CHECKEL option for bulk data entry PARAM . |
|
OutputDefault |
<AUTO, NONE> |
The OutputDefault entry allows default outputs to be disabled. This entry controls output for subcases for which there is no output requested. AUTO: Output is automatically generated for certain solution sequences. NONE: No output that is not specifically requested is output. |
|
CHECKMAT |
<YES, NO, FULL> |
Same as CHECKMAT option for bulk data entry PARAM. |
|
COUPMASS |
<-1, 0, 1, YES, NO> |
Same as COUPMASS option for bulk data entry PARAM . |
|
EFFMASS |
Integer |
Same as EFFMASS option for bulk data entry PARAM . |
|
PRGPST |
<YES, NO> |
Same as PRGPST option for bulk data entry PARAM . |
|
SHALTER |
<YES, NO> |
Same as SHALTER option for bulk data entry PARAM . |
|
KGRGD |
<YES, NO> |
Same as KGRGD option for bulk data entry PARAM. |
|
WTMASS |
Real > 0.0 |
Same as WTMASS option for bulk data entry PARAM . |
|
MBDH3D |
<NODAL, MODAL, |
Same as MBDH3D option for bulk data entry PARAM. |
|
FLEXH3D |
<AUTO, YES, NO> |
Same as FLEXH3D option for bulk data entry PARAM. |