|
»Click here to display Table of Contents«
|
FOS |
|
|
|
|
|
FOS |
|
|
|
|
|
»Click here to display Table of Contents«
|
FOS |
|
|
|
|
|
FOS |
|
|
|
|
FOS – Output Request
The FOS command can be used in the I/O Options or Subcase Information sections to request fatigue factor of safety, hydrostatic pressure, and shear stress output for all fatigue subcases or individual fatigue subcases.
Format
FOS (format, type) = option
Argument |
Options |
Description |
|
format |
<H3D, OPTI, blank> Default = blank |
H3D: |
Results are output in Hyper3D format (.h3d file). |
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, EVENT> Default = SUB |
SUB: |
Total FOS, hydrostatic pressure, and shear stress results are output for Fatigue Subcases. |
EVENT: |
FOS, hydrostatic pressure, and shear stress results are output for each FATEVNT in addition to results output via the SUB option. |
||
|
|||
option |
<YES, ALL, NO,NONE,SID, PSID> Default = ALL |
YES, ALL, blank: |
Results are output for all elements. |
NO, NONE: |
Results are not output. |
||
SID: |
If a set ID is provided, results are output only for elements listed in that set. |
||
PSID: |
If a property set ID is provided, results are output only for elements referenced by the corresponding set of properties (SET (TYPE=ELEM, SUBTYPE=PROP)). |
||
| 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 a format is not specified, this output control applies to all formats defined by the OUTPUT command, for which the result is available. See Results Output by OptiStruct for information on which results are available, in which formats. |
| 3. | Hydrostatic Pressure and Shear Stress are not output in the OPTI format. Only Event-based FOS results are output in OPTI format. The H3D format supports full output. |
| 4. | Center of the yield surface is determined based on the entire load history across multiple events. Therefore, the FOS of an event is affected by the entire load history and not just the local load history of the event. |
| 5. | Multiple instances of this card are allowed; if instances are conflicting, the last instance dominates. |
See Also: