|
»Click here to display Table of Contents«
|
Abaqus Support of Include Files |
|
|
|
|
|
Abaqus Support of Include Files |
|
|
|
|
Many FEA solvers allow you to organize your input deck into separate files and provide a mechanism to include all the files in a single input deck. This capability is commonly known as "include" capability. HyperMesh allows you to import such models for Abaqus.
HyperMesh’s Model browser allows you to create, review, edit, organize, and update the contents of a model into various include files.
The following rules and considerations apply to the Abaqus include file support in HyperMesh:
| • | Include files must include complete information for each keyword. A keyword and its data lines must be part of the same file. |
| • | Include files must contain complete information for cards that contain multiple sub-keywords. For example, all sub-keywords and their data lines in a *Material card must be part of the same include file. |
| • | Include files must contain complete information for *STEP cards. All history keywords and their data lines must be a part of the same file. |
| • | The Abaqus interface is comprised of four types of include files: Model (start), Model (middle), Model, and History. They define the sequence of the *INCLUDE keywords in the model. Model (start) type of include files are written at the beginning of the deck, after the *NODE block. Model (middle) is written in the middle of the deck, after the *MATERIAL block. Model is written at the end of the model definition, and History keywords are written after the model definition. |
| • | Include file names are sorted according to their names in the browser. The sequence in the exported model is primarily determined by the four types of includes files as described above. Within each type the sequence is determined by the order in which they are created. |
| • | The Abaqus syntax for the include file path is: |
In Abaqus, file names can include a full or relative path name. Relative path names must be in relation to the directory from which the job was started. If a path is not specified, it is assumed that the file is located in the same directory from which the job was submitted.
From HyperMesh, it is, however, not always possible to predict the directory from which the job will finally be submitted. Therefore a relative path must be defined. This relative path should be defined with respect to the folder where the corresponding *Include keyword appears. If you run the job from a different folder in subsequent runs, you must also update the path name.
