HyperMesh uses templates to create the analysis input decks for finite element solvers. You can modify the existing templates to support a desired feature or create a new template to support another analysis code. HyperMesh templates can be used to create model summaries and perform some analysis calculations. You can also use the templates to perform complex editing or data manipulation tasks.
| 1. | From the menu bar, click File > Export > Solver Deck. This Export tab opens. |
| 2. | Set File type to the solver-specific file type to export. By default, this field is automatically set to the solver-specific file type of the currently loaded user profile. |
| 3. | Set Template to the appropriate template file type. By default, this field is automatically set when you make your selection in the File type field, but if you have customized your template and want to use one other than the default, you can reset the option here. |
| 4. | In the File field, click  and select the file to import. |
| 5. | Under Export options, set advanced export options. |
Advanced Export Options
| 1. | In the Export field, select the type of entities to import. |
| • | All. Exports all entities in the current database. |
| • | Custom. Enables you to select which entities to export from the current database. |
Select which entities to export by clicking Select Entities. In the Entity State browser, select the checkboxes in the export column to set the export state of any HyperMesh entity. Only the entities which have a checkbox activated will be exported to the template. When finished setting the export state for all entities, click the Export tab. The export behavior for each entity is explained in HyperMesh Entities Export Behavior.
| • | Displayed. Exports only the entities that are currently displayed. |
| o | Entities that have a display state and/or a mask state are displayed on the screen are exported. This includes elements, loads, equations, systems, vectors, groups, components, blocks, contactsurfs, multibodies, ellipsoids, mbplanes, mbjoints, assemblies, control cards (that are enabled), loadcols, systemcols, vectorcols, and connectors. |
| o | Entities that do not have a display state and/or a mask state are exported if at least one of the entities it contains is displayed. For example, entity sets do not have a display state (on/off). If an entity set contains elements and some of the elements are displayed, the set is exported. However, the contents of the set are limited to the displayed portion only. If this set contains 20 elements, five of which are displayed and remaining turned off, the exported set will contain only five elements.Entities in this category include: entity sets, output blocks, loadsteps, control vols, and beamsect cols. |
| o | Entities that do not have a display state and/or a mask state are exported if the entity is being used by a displayed entity. For example, materials do not have a display state, but if a displayed component or element uses it, that material is exported. Entities in this category are: nodes, materials, properties, entity sets, and curves. |
| o | Sometimes entities that are not displayed are exported anyway, if the entity is referred to by another entity that is displayed. For example, when a vector is turned off, but is used in defining the orientation of a beam element, the vector will be exported in order to export the beam element correctly. Entities in this category are: vectors, systems, beamsections, multibodies, and components. |
| o | Any entity that is used or required by an attribute of a displayed entity is also exported. For example, if a material is defined as an attribute on an element, that material is exported. All entities in the HyperMesh database belong to this category. |
| o | Any entity that points to a displayed entity is exported. Tags and titles belong to this category. |
| 2. | In the Solver options field, click Select Options to define solver-specific export settings. |
| Note: | Options vary depending on the file (solver) type selected. |
| 3. | Under Comments, select the type of comments to write upon export. |
| • | HyperMesh. Writes HyperMesh comments upon export. When unchecked, HyperMesh comment cards are ignored. |
| • | Connectors. Exports all of the connectors in the model. This operation appends the master connector file xml data to the end of the solver input file as solver comments and thus does not effect the operation of the solver. This operation can remove the necessity to perform a FE-absorb on a imported model since the connector information is retained in the solver input file. |
| • | Part Assemblies/Parts. Exports an xml comment block containing HyperMesh part assemblies/parts, along with PDM metadata. |
| 4. | In the Include files field, specify how includes are exported. |
| • | 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. |
| 5. | ID Rules exports ID management rules defined in the ID-Manager as an XML block at the end of each Include file. This option is only available when Include files is set to Preserve. |
| 6. | Prompt to save invalid elements and Prompt before overwrite prompts you on these potential export errors. |
See Also:
Importing and Exporting Data
