Include Files

Most FEA solvers allow you to organize the input deck into separate files and provide a mechanism to include (or refer) these files in the main input deck.

This capability is commonly known as "include" capability. HyperMesh allows you to import such models using three options.
Option
Description
preserve includes
Preserves the data in individual include files along with their references in the main model. You can review the contents of individual include files via the Include Browser. When exporting, entities are written into the corresponding include files along with their references in the main file.
skip includes
The data in the include files is not imported into HyperMesh. The include references are maintained and are written out to the main model during export.
merge includes
The contents from the all include files are imported into the HyperMesh model but their references are not maintained. When exporting, all entities are written into the main file.
The Model Browser allows you to create, review, edit, organize and update the contents of a model into various include files. Every entity in HyperMesh belongs to either the main model or an include file. Each include file has a name (title) and location (full or relative path). An include file can be designated as the current include file. Any new entities created or imported are placed in the current include file. You can create a new include file, and drag and drop entities between various include files using the Model Browser.
Note: Models that do not reference any include files are placed entirely in the main model.

Abaqus Support

Many FEA solvers allow you to organize the 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.

The Model Browser in HyperMesh 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:
  • Includes 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 include file types that define the sequence of the *INCLUDE keywords in the model.
    Model (start)
    Written at the beginning of the deck, after the *NODE block.
    Model (middle)
    Written in the middle of the deck, after the *MATERIAL block.
    Model
    Written at the end of the model definition.
    History
    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.