Abaqus Include File Export

Solution > Settings(Right click) > Format and Execute Options

SimLab provides a few methods to automatically organize and export the model as include files. This helps to avoid the manual organization of data by the user.

Also, this helps to replace parts in the assembly by directly replacing the include files.

The following methods of include file structure export are supported.
  • Nodes, Elements, Contact, etc. in separate file (Only for Abaqus | Drop Impact)
  • Using sub models
  • Each body in separate file
  • First level of sub models and contact across sub models in separate file
  • Mesh, material and property in separate file

Nodes Elements Contact etc. in separate file:

This option is used for Drop impact analysis. It creates the following include files anl, msh, sec, tie, mtl, conn, sets and assem.

Using sub-models:

Used to export the solver deck based on sub-models. Creates a separate include file for each sub-model.

Organizing the data
  • Nodes, Elements and Properties will be exported to the include files based on the body in the sub-model.
  • RBE and Bar
    • Connected within the sub-model - will be exported to the respective sub-model include file.
    • Connected across the sub-model - will be exported in the main file.
  • Material
    • All materials are written in a separate file (MainFileName_Material)
  • Contact
    • If contact is defined within a sub-model it will be exported to the respective sub-model include the file.
    • If contact is defined across the sub-model, it will be exported in the main file.
  • Sets and Sets for Boundary Condition:
    • *NSET and *ELSET:
      • Within sub-model - Will be exported to respective sub-models include file.
      • Across sub-model - Export the data defined in each sub-model to the respective include file in the same sets name.
    • *SURFACE is always exported in the main file
      • Within sub-model - Will be exported to respective sub-models include file.
      • Across sub-model - Exported in the main file.
  • Step definition of the BC’s will be written in the main file.

Each body in separate file:

Write each body detail (node and elements) in a separate include file. Rest of the information write in main file itself.

First level of sub-models and contact across sub-models in separate file:

This export is similar to the “Using Sub-models” options, but only the first level of sub-models will be considered and exported as include files.

Organization of include file:
  • Node and Elements
    • Bodies and corresponding BC’s present in the first level of sub-model will be exported in a respective include file.
  • Contacts
    • Within first level of sub-models – Exported to respective include file.
    • Contact defined across each pair of sub-models will be exported to a separate include file.

Mesh, material and property in separate file(Only for Abaqus | Drop Impact)

This option is used to organize the folder structure while exporting the solver deck file. When exporting, it writes geometry data, material, and properties into different files: MSH, MAT, and SEC, respectively. This separation helps maintain a structured and organized set of output files.

  1. File Separation:
    • MSH: Contains geometry data.
    • MAT: Stores material properties.
    • SEC: Contains section properties.
  2. Running DOE Simulations:
    • This organization is primarily used for running Design of Experiments (DOE) to collect solver deck files efficiently
    • To achieve this, enable the "Skip Solver Run" option by setting it to "True". You can find this option under DOE Solution > Settings > Right-click > Execute options.
    • Enabling this option helps group the solver deck files without actually solving the equations, which is beneficial for batch processing or later analysis.

  3. Impact Surface Definition:
    • The impact surface (rigid floor) is defined by a single quadrilateral element with hardcoded nodes and element ID.
    • This setup allows for a simplified and consistent definition of the impact surface across different simulations.