Next: Nodal Point Coordinate Data Up: Format of the neutral Previous: Overview
Next: Nodal Point Coordinate Data
Up: Format of the neutral
Previous: Overview
FORMAT (1X, I4, A1, 6A1, E12.5, 12X, 20A1, I2, I5, 10A1, I2)Where:
| KEY | = | data set identification key, see Table B.1 |
| OPCODE | = | operation code |
| `C' = create a new model (or new data set) | ||
| `A' = append to an existing model | ||
| `B' = build an assembly of models | ||
| `I' = increment a data set | ||
| `R' = replace a data set | ||
| Name | = | user-key, project, model or load case name |
| STPVAL | = | step value for loadcase, |
| for example: | ||
| time instance | ||
| frequency | ||
| load step | ||
| Text | = | descriptive text for loadcase |
| ICTYPE | = | Analysis type |
| 0 = static | ||
| 1 = time step | ||
| 2 = frequency | ||
| 3 = load step | ||
| 4 = user named | ||
| NUMSTP | = | Step number for loadcase |
| Analysis | = | Analysis type name name (used if ICTYPE=4) |
| IFORMT | = | Format indicator |
| 0 = 5 digit node/element/transformation number format | ||
| 1 = 10 digit node/element/transformation number format |
Note that the `STPVAL', `Text', `ICTYPE', `NUMSTP' and `Analysis' fields are only required with Header Records for the Loadcase Information, Loadcase Combination, Loadcase Scan and User-defined Results data sets.
| Record Type | KEY | OPCODE | Name |
| User Header | 1 | U | User key |
| Project Header | 1 | P | Project Name |
| Model Header | 1 | C, A or B | Model Name |
| Nodal Point Coordinate Header | 2 | C | -- |
| Element Definition Header | 3 | C | -- |
| Node Set Definition Header | 18 | C | -- |
| Element Set Definition Header | 19 | C | -- |
| Material Properties Header | 20 | C | -- |
| Loadcase Information Header | 28 | C | Loadcase Name |
| Loadcase Combination Header | 29 | C | Loadcase Name |
| Gauss Point Coordinates Header | 30 | C | -- |
| Loadcase Scan Header | 31 | C | Loadcase Name |
| Nodal Results Local Systems Header | 32 | C | -- |
| Element Results Local Systems Header | 33 | C | -- |
| Gauss Point Results Local Systems Header | 34 | C | -- |
| Nodal Constraints Header | 41 | C | -- |
| Multi-Point Constraints Header | 42 | C | -- |
| Local Systems for Constraints and DOFs Header | 43 | C | -- |
| Transformations Header | 50 | C | -- |
| Structured Grid (IJK) : Definition Header | 60 | C | -- |
| Structured Grid (IJK) : Blockage and Material Data Header | 61 | C | -- |
| User Defined Results Header | 100 | C, I or R | Loadcase Name |
| User Defined Loads Header | 300 | C, I or R | Loadcase Name |
| File Delimiter | 9999 | -- | -- |
Notes:
| C | = | create a new model or data set in the database. |
| A | = | append to an existing model. New data sets may be created (added), or existing data sets may be incremented or replaced. |
| B | = | build an assembly of models. |
| I | = | increment a data set. |
| R | = | replace a data set. |
Operation code `A' may only be used to add new analysis results to a model already stored in the database. When adding analysis results the operation code in the Model header record is set to `A' and the model name must correspond to the model existing in the database. The header records for the new analysis results data sets must have operation code `C'.
Note that the geometry and topology data sets should NOT be re-submitted when appending analysis results to an existing model.
Operation codes `I' and `R' are used only with user-defined results or loads data. In both these situations the operation code in the Model header record should be set to `A' and the model name must correspond to a model existing in the database.
The `I' increment operation is as follows and is the same for both loads and results data:
| 1. | If a results attribute of the same name already exists then the incremental update will be performed such that any node or element result values being read in will replace those already existing. Those not replaced will remain valid. Note that it is only possible to replace values at the node and element level, not at the individual component level. |
| 2. | If a results attribute of the same name does not exist then the node or element results values read in will form the new data set. |
| 3. | It is possible to specify a base attribute to be used where an attribute of the same name does not exist. ref: B.14.2 |
The `R' increment operation is such that the results (or loads) data set read in will completely replace an existing results (or loads) data set with the same atrribute name.
Femsys Limited