Formatting for Analysis

The purpose for using a finite element (FE) pre-processor is to create a model that can be run by a solver.  HyperMesh interfaces with many FE solvers and all of them have unique input file formats. HyperMesh has a unique template(s) for each solver it supports. A template contains solver specific formatting instructions, which HyperMesh uses to create an input file for that solver.

This exercise gives you an understanding of the basic concepts for creating a solver input file by using a template. More specifically, you will learn how to review entities in HyperMesh to see how they will appear in the solver input file, define materials and properties and select solver element types for HyperMesh element configurations.

Interacting with Solvers

HyperMesh interacts with many solvers. Each solver has its own unique formats, terminology, etc. In the example below an OptiStruct deck is compared to an Abaqus deck.

HyperMesh interacts with the different solvers using "templates". Each entity may have several available formats for a solver. Each format has has fields that make up its definition. These fields may need to have values entered by the user. For example, a component for OptiStruct can be a PSHELL or a PSOLID format.


Tools

Collectors - for more information on collectors see the Organizing Models chapter.

During Collector Creation


During Collector Update


Elem types > load types panel


Card Edit - Right click in the Model Browser, click the Card Edit icon in the toolbar.


Process

  1. Create Materials and enter values into them. Use the Model Browser or create the material as the Property or Component is being created.
  2. Create Properties using the Model Browser or during the creation of the Components and enter values into them.  Material collectors can be associated with Properties during creation.
  3. Create component collectors and organize entities into them.  Property collectors can be associated with components during creation or properties can be assigned directly to elements. Use the Model Browser to create the component.
  4. Mesh the model and create loads and constraints where appropriate.
  5. Create loadcases from combinations of the loads and collectors.
  6. Create solver specific cards and controls.

While it is not required that events follow these steps in order, if you follow these steps then there is no need to go back to update or assign information to collectors as the required information will already be in place. The goal in formatting for analysis is to have all entities in the proper formats (card image/type) and for all necessary information to be entered into the card images.