This section describes the Abaqus input translator, the output template, summary templates, and the result translator in HyperMesh.
By selecting the Abaqus user profile, you can work with pre-defined panels that are more specific to Abaqus usage. The User Profiles dialog is launched by default when HyperMesh is started the first time.
Three user profiles (and templates) are available for the Abaqus interface:
Standard.2d
|
Generates a deck for two-dimensional models containing planar or axisymmetric elements for use with Abaqus Standard.
|
Standard.3d
|
Generates a deck for three-dimensional models containing bar, shell, and solid elements for use with Abaqus Standard.
|
Explicit
|
Generates a deck for use with Abaqus Explicit.
|
These are some general comments about HyperMesh interface with Abaqus:
Import and Export
|
| • | The Abaqus interface supports Abaqus version 6.10. |
|
| • | HyperMesh places all elements into separate components, based on sectional property. Each component is written out from HyperMesh as element set in the Abaqus input deck. |
|
| • | Although HyperMesh supports 160 characters in entity names, Abaqus output files are truncated at 80 characters to match the Abaqus name support level. |
|
| • | The loads and constraints are organized under load collectors in HyperMesh. These load collectors need to be added to a load step for the *STEP card in Abaqus history definition. If loads are applied to node or element sets there is a solver option provided in the Import panel under Import options. The option Expand loads on sets allows you to resolve these sets to individual nodes or elements. |
|
| • | The output options are organized under output blocks in HyperMesh. These output blocks also need to be added to load steps. |
|
| • | Solver options in the Import panel (see Import options) allows you to resolve sets into nodes or elements which are defined using the GENERATE parameter. This is useful when nodes/elements are renumbered due to ID conflicts during import. |
|
|
|
Syntax
|
| • | HyperMesh supports some abbreviated key words and parameters. |
|
| • | All Abaqus keywords and parameters supported in HyperMesh are not case insensitive. |
|
| • | HyperMesh ignores spaces in keyword lines. |
|
| • | HyperMesh supports quotation marks around component (ELSET with sectional properties) names, which is especially useful for names that begin with a number. |
|
|
|
HyperMesh Operations
|
| • | Warnings and error messages are written to a file named abaqus.msg. Unrecognized lines are written to a *.hmx file. These files are created in the same directory from where HyperMesh is launched. |
|
| • | Step time calculations can differ between HyperMesh and Abaqus (Explicit analyses), so you may find differences between reported values in the Abaqus status (.sta) file and the time subpanel of the Check Elems panel. The values reported by HyperMesh are close estimates of the step time; refer to the Abaqus documentation to learn more about the factors that Abaqus/Explicit uses to reach the final result. |
|
See Also:
Model browser
Solver browser
Connector browser
Include Files
Using the Abaqus Utility Menu
Supported Abaqus Keywords
Unsupported Abaqus Keywords
Solver Conversion
