|
»Click here to display Table of Contents«
|
FATSEQ |
|
|
|
|
|
FATSEQ |
|
|
|
|
|
»Click here to display Table of Contents«
|
FATSEQ |
|
|
|
|
|
FATSEQ |
|
|
|
|
FATSEQ – Load Sequence Definition for Fatigue Analysis
This bulk data entry can be used to define a loading sequence for a Fatigue Analysis.
(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 2) No default (Integer > 0) |
N# |
Number of times this loading sequence or event is repeated. Repeat number (N#) has no effect on the results of a Factor of Safety (FOS) analysis. Default = 1 (Integer > 0) |
| 1. | Identification numbers of FATSEQ and FATEVNT entries share the same ID pool. |
| 2. | 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. |
| 3. | This card is represented as a loadcollector in HyperMesh. |
See Also: