TRIMF
I/O Options and Subcase Information Entry Used to specify options for the output of trim loads from a static aeroelastic analysis as FORCE/MOMENT Bulk Data Entries.
Format
TRIMF (LOADSET=n, LARGE, INERTIA, APPLIED, AIR, NOSUM, RIGID, NOELASTIC, QNORM) = option
Definitions
Argument | Description |
---|---|
LOADSET | Load SET ID for output Bulk Data eEtries. If the
TRIMF specification results in multiple
load sets, then the defined ID will be used for the first and
each subsequent load set has an ID incremented by 1. Default = 1 (Integer) |
LARGE | Write the output data in large field format (16 characters
per field). The default is 8 characters per field. |
INERTIA | Write out inertial loads as a separate load set. By default, the separate load set will not be written. |
APPLIED | Write out applied loads as a separate load set. By default, the separate load set will not be written. |
AIR | Write out aerodynamic loads as a separate load set. By default, the separate load set will not be written. |
NOSUM | Suppresses the writing of that set of loads. By default, the sum of the inertial, applied, and aerodynamic loads will be written as a separate load set. |
RIGID | Write out rigid instances of the selected loads (Inertial,
Applied, Air and/or Sum) as separate load sets. By default, the separate load set will not be written. |
NOELASTIC | Suppresses the writing of that set of loads. By default, the sum of the rigid and elastic increment loads will be written as a separate load set. |
QNORM | Normalize the load by the dynamic pressure used in the trim
analysis. By default, the loads are not normalized. |
option |
(Integer > 0) |
Comments
- The loads are written to the .trim ASCII file.
- Up to eight loads sets are available:
Rigid Inertial, Rigid Applied, Rigid Air, Rigid Sum and four more with the
sum of the rigid and elastic increment. This table indicates how the
describers invoke each of these sets.
INERTIA APPLIED AIR SUM RIGID O O O O ELASTIC O O O Default - Care must be taken if
LOADSET is specified in a run with multiple subcases.
There are no checks that the load set IDs which are generated by one subcase
are not also used for another subcase. For example, consider the following
Case Control
commands:
SUBCASE 101 TRIM = 101 TRIMF(RIGID) = ALL $ SUBCASE 201 TRIM = 201 TRIMF(LOADSET=3) = ALL
Subcase 1 will generate two load sets with set IDs 1 and 2. Subcase 2 can then have TRIMF with LOADSET=3 so that the load set IDs for subcase 2 will start at 3.
- The LOADSET option should not be specified above the subcase level when there are multiple subcases. If it is, each subcase will start numbering its load ID’s from LOADSET.