Abaqus
When importing Abaqus files, you can use the By HM Comment option, understanding the following items:
• | If available, HyperMesh will consider comments written during a previous model export. |
• | If neither **HM_comp_by_property nor **HM_set_by_property comments are present, HyperMesh creates a component and a property collector for every element set (ELSET) that points to a sectional property. Both collectors will have the name of the referenced element set. |
• | If a comment such as **HM_comp_by_property “<property name>” <color> is found before a sectional property (e.g. *SHELL SECTION) is found, a component with the name of the referenced element set will be created. At the same time, a property collector will be created, which defines the sectional property of the component (property assignment on component level). Its name will be taken from the HyperMesh comment. |
• | If a **HM_set_by_property comment is found, HyperMesh will create a property collector, which defines the sectional property of the elements mentioned in the element set (property assignment on element level). In addition, the elements will be placed into the component they were in before exporting. If present, the prefix “HMprop_” will be stripped on import. |
Nastran
When this import option is selected, HyperMesh will:
• | Create a component based on the HMCOMP NAME card |
• | Move elements into component based on the HMMOVE card |
• | Assign properties based on the HMDPRP card |
• | When HMCOMP NAME does not exist in the imported deck, and there is a one to one ratio between elements and properties (2D and 3D properties), HyperMesh will create one component and move all the elements into this one component. Properties will be assigned to the element. |
• | When HMCOMP NAME does not exist in the imported deck, and there are multiple elements with the same property, HyperMesh will create a component for every property, move all the elements that have a property into the associated component, and create one component for all elements that do not have a property. The property will be assigned to the component. |
• | When importing a Nastran input file containing ANSA or Patran comments, using the By HM Comments import option, HyperMesh will automatically recognize and use them to organize the model. The supported ANSA and Patran comments and their interpretation in HyperMesh, are listed below: |
HyperMesh supports organizing Nastran input files containing the following ANSA comments:
ANSA Comments
|
HyperMesh Mapping
|
$ANSA_PART;GROUP
|
Assembly
|
$ANSA_PART; PART
|
Component
|
$ANSA_NAME
|
Property / Material / Set Name
|
$ANSA_COLOR
|
Property / Material Color
|
$ANSA_DEFAULT_SET_TYPE
|
Set
|
Only one property can be indirectly assigned to a HyperMesh component. Any additional properties associated to a single ANSA_PART component will be assigned to the HyperMesh component using Direct Property Assignment (a warning message will be issued during import). The resulting elemental property assignment and integrity of the solver input file will not be affected by this.
|
HyperMesh supports organizing Nastran input files containing the following Patran comments:
Patran Comments
|
HyperMesh Mapping
|
$Elements and Element Properties for region
|
Property
|
$Material Record
|
Material
|
$<load type> of Load Set
|
Load Collector
|
$Deform Body Contact LBC Set
|
Contact Surface
|
$Subcase name
|
Loadstep
|
$Connector elements and properties for region
|
Property
|
|