In the Import tab you can import the following types of FE model files:
Finite Element:
|
OptiStruct, RADIOSS, Abaqus, Actran, ANSYS, EXODUS, LS-DYNA, MADYMO, Marc, Nastran, PAM CRASH 2G, PERMAS, and Samcef.
|
Custom:
|
Uses custom FE input translators (created by customers for any internal or proprietary solvers) to import Finite Element models.
|
Importing FE Model Files
| 1. | Click File > Import > Solver Deck from the menu bar, or click  on the Standard toolbar. The Import tab opens. |
| 2. | Set File Type to the solver-specific file type you want to import. By default, this field is automatically set to the solver-specific file type of the currently loaded user profile. |
| 3. | If Custom is chosen as the File Type, specify the location of the appropriate reader in the Reader field. |
| 4. | In the File field, click  and select the file to import. |
| 5. | Under Import options, define advance import options. |
Advanced Import Options
| 1. | In the Import field, select the type of entities to import. |
| • | All. Imports all entities in the selected file. |
| • | Custom. Enables you to select which entities to import from the selected file. |
Select which entities to import by clicking Select Entities. In the Import dialog, select the checkboxes of the entities to import. The import behavior for each entity is specified in import behavior.
| 2. | In the Display field, select whether to turn the display of newly imported load collectors and/or system collectors on or off. This can help improve the performance for FE input models containing large numbers of loads/systems. This is supported for all import readers. Existing load collectors and system collectors are not affected by this option. |
| • | All. Turns the display of newly imported load collectors and system collectors on. |
| • | Custom. Enables you to select which entities to display. |
Select which entities to display by clicking Select Entities. In the Display dialog, select the checkboxes of the entities to display. Inactive entities will not be displayed.
| 3. | In the Solver options field, click Select Options to define solver-specific import settings. |
| Note: | Options vary depending on the file (solver) type selected. Only available for Abaqus, LS-DYNA, Nastran, OptiStruct, and RADIOSS. |
| 4. | The Create comps and Assign props fields define how components are created as well as how properties are assigned to elements during import. Each solver interface might work differently for these options, but general behavior is as follows: |
| • | Create comps. Specifies how components are created on import. |
| o | By HM Comments. Honors the HyperMesh comments $HMNAME COMP, $HMMOVE, and $HMDPRP in the selected file that were created by HyperMesh in any previous export of the model. |
| o | By Property. Ignores any $HMNAME COMP, $HMMOVE, and $HMDPRP comments that may be in the selected file and automatically creates components based on each property in the file. The component name will be the name of the property. The property will also be created and assigned to the component, not the elements. (View a diagram of the data hierarchy) |
| o | By 1 Component. Ignores any $HMNAME COMP, $HMMOVE, and $HMDPRP comments that may be in the selected file and creates one component into which all elements in the selected file will be organized. Properties will be created and assigned directly to the elements. (View a diagram of the data hierarchy) |
Assign props. Specifies how properties are assigned to elements on import.
| • | By HM Comments. Honors the $HMNAME COMP, $HMMOVE, and $HMDPRP comments and assigns properties to elements accordingly. Any elements listed in the $HMDPRP comment will have their property directly assigned, and the remaining elements will take their property from the component. |
| • | On Element. Honors the $HMNAME COMP and $HMMOVE comments and directly assigns properties to all elements based on their card definitions |
| • | On Component. Honors the $HMNAME COMP and $HMMOVE comments and leaves all elements to take their property from their components. |
| Note: | Elements can take a property assignment from the component in which it resides, or it can have a property directly assigned to it. Direct assignment takes precedence over component assignment. |
| 5. | Import as include loads and displays non-include files as include files. |
| 6. | In the Include files field, specify how includes are imported. |
| • | Merge. Imports the contents from all include files into the HyperMesh model, but does not maintain their references. When exporting, all entities are written into the master file. |
| • | Preserve. Preserves the data in individual include files along with their references in the master model. Review the contents of individual include files in the Include browser. When exporting, entities are written into the corresponding include files along with their references in the master file. |
| • | Skip. Data in the include file is not imported into HyperMesh. Include references are maintained and written out to the master model during export. |
| 6. | ID Rules imports ID management rules that were defined in the ID-Manager and exported to a solver deck as an XML block at the end of each Include file. This option is only available when Include files is set to Preserve. |
| 7. | FE overwrite overwrites entities that have matching IDs. If checked off, entity IDs are offset to avoid duplicates. |
| 7. | ID Offset adjusts offset settings. Click Define Offsets and specify values to offset each entity in the Define Offsets dialog. |
| 8. | Display import errors displays any errors that occur during the import procedure. |
See Also:
HyperMesh Comments
Import Error Messages
Importing and Exporting Data
