Export Files

In HyperWorks Desktop exporting various file types from the selected client to another format.

During export you can write information from a HyperMesh database to many finite element formats. However, geometry data can only be written in IGES format.

Use the Custom option to export models using your own custom-built export translator, or export models using a translator provided with the HyperMesh installation but which is not directly accessible via the default Export pull-down menu.

Export Models

Export model files.

Export a model in the following ways:
- From the menu bar, click File > Export > Model.
- From the Standard toolbar, click (Export Model).
The Export - Model tab opens.
For File type, select the type of file to export.
In the File field, specify a filename and location.
Define model export options by clicking to the left of Export Options.
Click Export.

Model Export Options

Options used to export model files.

Write titles as notes: Export HyperMesh titles as HyperView notes. By default, HyperMesh titles are not exported as HyperView notes.
Write results: For supported entities and result contours, this option writes the displayed results to an H3D file. If no supported result contour is displayed, this option is ignored.
Prompt before overwrite: Display prompt before overwriting information.

Export Solver Decks

Export solver input files.

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.

The Media (*.bif) is also supported for nodes, elements (mass, beam, tria3, quad4, tetra4, tetra10, penta6, penta15, hexa8, hexa20), and sets (nodes, elements) in the LS-DYNA user profile.

Export a solver deck in the following ways:
- From the menu bar, click File > Export > Solver Deck.
- From the Standard toolbar, click (Export Solver Deck).
The Export - Solver Deck tab opens.
For File type, select the type of solver file to export.
For Template, select 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.
In the File field, specify a filename and location.
Define Solver Deck Export Options by clicking to the left of Export Options.
Click Export.

Solver Deck Export Options

Options used to export solver decks.

Export

Type of entities to export.

All

Export all entities in the current database.

Custom

Select entities to export from the selected file.

Click Select Entities to open the Export State Browser and 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 Entity Export Behavior.

Displayed

Export only the entities that are currently displayed.

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.
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.
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.
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.
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.
Any entity that points to a displayed entity is exported. Tags and titles belong to this category.

Solver options

Define Solver Export Options export settings by clicking Select Options.

Comments

Select the type of comments to write upon export.

HyperMesh: Write HyperMesh comments upon export. When unchecked, HyperMesh comment cards are ignored.
Connectors: Export 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: Export an xml comment block containing HyperMesh part assemblies/parts, along with PDM metadata.

Include files

Method for exporting includes.

Merge: Import the contents from all include files into the HyperMesh model, but do not maintain their references. When exporting, all entities are written into the master file.
Preserve: Preserve 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: Do not import data in the include file into HyperMesh. Include references are maintained and written out to the master model during export.

ID Rules

Export ID management rules defined in the ID Manager as an XML block at the end of each Include file.

Restriction: Available when Include files is set to Preserve.

Prompt warnings of ID Conflicts

Display prompt when there are ID conflicts.

Prompt to save invalid elements

Display prompt to save invalid elements.

Prompt before overwrite

Display prompt before overwriting information.

Solver Export Options

Supported solver export options.

Access solver export options by clicking Select Options, next to Solver Options in the Export - FE Models tab.

OptiStruct and Nastran

When exporting a model, HyperMesh always tries to use the greatest precision when writing real numbers in small format. The following options in the Solver Options dialog will allow you to control precision and accuracy in the model.

Remove ‘E’ from real values: OptiStruct and Nastran solvers do not require explicitly writing an E to recognize the proper exponent of a real number, and removing the E allows one more digit of precision to be included. For example, -1.12E-7 becomes -1.123-7.
Zero tolerance: With this option, any real numbers in the model whose absolute value is less than specified here will be written out as zero. For example, if Zero tolerance = 1.0E-12, it means all real values from -1.0E-12 to 1.0E-12 will be exported as 0.0.

Non-structural mass [NSM1, NSML1] must be referenced in case control for it to be applied in the model. In order to make this process easier, the following option in the Solver Options dialog has been added:

Auto-organize NSM: When turned on, this option automatically collects all non-structural mass entities [NSM1, NSML1] into a NSMADD loadcollector. This loadcollector is then automatically referenced in the NSM GLOBAL_CASE_CONTROL control card. As long as Auto-organize NSM is checked on, it will update the NSMADD loadcollector on every export and if you delete all NSM* cards, this option will delete NSMADD and case control reference along with it.

The default behavior in HyperMesh when exporting RBE3 weight factors is to maintain all values defined by you, even if they have a value of 0.0. This behavior can be modified with the following option:

Auto adjust RBE3 0.0 weight factor: When turned on, HyperMesh will change any 0.0 weight factors on RBE3 elements to the specified small value. This adjustment is done in the exported solver deck only, and the original model values in the current HyperMesh session will not be modified.

Others:

Compress Nodes/Element Sets: When turned on, all node sets and element sets in the model are exported with the THRU statement.
Free Format Export: (OptiStruct only): When turned on, the model will be exported in free format (comma separated format). This option supersedes other export templates like standard format and long format.

Permas

While rigid and rbe3 elements use the same ID pool in HyperMesh, equations and groups have separate ones. During creation, it is possible to use this situation to create duplicate IDs for MPCs as well. To resolve this, during export a solver option is available in the Export tab to renumber MPCs if duplicate IDs are present (Renumber MPCs if IDs are duplicated). This option will check for the highest rigid/rbe3 ID and renumber equation entities accordingly. Groups are not included in the renumbering functionality as contact IDs would be affected by renumbering.

The Export to gzip compressed file (.gz) option allows you to export files to .gz file format (gzip), which is Permas compressing tool. This format is directly read into their solver.

Abaqus

Export Entities With Quotes: Abaqus does not support special characters or staring with numbers in entity names. In order to retain entity names during export, quotes can be added to entity names. By default, entities with quotes are not exported in the solver deck. Select this checkbox to export entities with quotes in the solver deck.; This option is only supported for the following entities: Components, Properties, Materials, Sets, and Groups.
Export *NMAP keyword: Exports the solver deck with the *NMAP keyword (default). Clearing this checkbox exports a flat solver deck without the *NMAP keyword.
Auto adjust RBE3 0.0 weight factor: When enabled, HyperMesh changes any 0.0 weight factor on RBE3 elements to the specified small value. This adjustment is only done in the exported solver deck. The original model values in the current HyperMesh session will not be modified.

Additional export options specific to Abaqus are available under Export options.

Export Id's

Each entity is assigned to an ID when it is imported into HyperMesh. In cases of Abaqus Interface, when you export the solver deck from HyperMesh, entity IDs will not be retained. By activating the Export ID’s option, entities will be assigned a range of IDs that are specific to each entity during export. Since more than one entity may exist, an alphabetic prefix is assigned to each entity in order to avoid a duplicate ID conflict.

For example, bumper-system will always have Part ID 2000000-2100000 across all carlines. Therefore, an engineer will have to isolate PIDs 2000000-2100000, if he wants to examine the bumper-system. This is essential in pre- and post-processing. Exporting the solver deck with IDs, will retain the prefix, ID and entity name.

Example for a surface entity with ID’s in solver deck (HM group): *SURFACE, NAME = <Prefix><ID>;<name_of_surface>
Example for a surface entity without ID’s in solver deck (HM group): *SURFACE, NAME = <name_of_surface>

When the Export Id's option is activated, you are able to edit the prefix for each entity by clicking Default Prefix. The Default Prefix dialog is arranged by HyperMesh entities. Each tab contains the entity which will be supported when exporting the ID’s into solver decks. You can change the prefix based on your own personal requirements. The Restore Default Prefix button allows you to reset the prefix for each entity. Instead of using letters from the English alphabet, you can also use the “-“ symbol to filter the entities when exporting the ID’s.

Table 1. Entities and Corresponding Prefixes. List of entities and their corresponding prefixes that are displayed by default in the Default Prefix dialog.
Entity	Prefix
Curve
Amplitude	XY
Group
SURFACE_ELEMENT, SURFACE_NODE, SURFACE_COMBINE_CROP, CUTTING SURFACE, ANALYTICAL_RIGID_SURFACE, TIE, CAVITY_DEFINITION, COUPLING, SHELL_SOLID_COUPLING, INTEGRATED_OUTPUT_SECTION	G
Material
CONNECTOR_BEHAVIOR, GASKET_BEHAVIOR	M
ABAQUS_MATERIAL, GENERIC_MATERIAL	-
Property
BEAM_SECTION, COHESIVE_SECTION, CONNECTOR_SECTION, SURFACE_SECTION, GASKET_SECTION, SHELL_SECTION, SOLID_SECTION	P
JOIN_PROPERTY, SPRING_PROPERTY, SECTION_CONTROL, SURFACE_INTERACTION, FASTENER_PROPERTY,DASHPOT_PROP,GAP_PROP	A
RIGID_BODY, MEMBRANESECTION, SURFACE_SMOOTHING, MASS, ROTARY_INERTIA, FLUIDPROPERTY, FRICTION, NONSTRUCTURAL_MASS, PHYSICAL_CONSTANTS, ELEMENT_PROPERTIES	-
Set
SET	S

LS-DYNA

Remove Numerical Suffix from Duplicate Titles: Removes numerical suffixes from duplicate titles.
Activate Transformations after Export Operation: Activates transformations after export operation.
Repeat Keyword Titles: Repeats keyword titles for each instance of the card.
Auto create property for COMPS with TETRA4/PENTA6/HEX8 elements: Creates properties for components that have TETRA4, PENTA6, and HEX8 elements.
Remove include file reference based on export status: Removes include file reference based on export status.

PAM-CRASH 2G

Activate Transformations after Export Operation: Activates transformations after export operation.

Entity Export Behavior

Overview of how entities are exported into HyperWorks Desktop.

Free Nodes

Nodes associated to elements are always exported. Element export is controlled by the component/group export state that the element resides in.
Nodes associated to node dependent systems are always exported. System export is controlled by the systemcol export state that the system resides in.
Nodes associated to node dependent vectors are always exported. Vector export is controlled by the vectorcol export state that the vector resides in.
Nodes associated to rigid wall's base node are always exported. Rigid wall export is controlled by the group export state that the rigid wall resides in.
Nodes on card images of exported entities are exported with those entities. Entity export is controlled by the export state of that entity (all entities).
Temporary nodes are always exported.
Nodes with a non-empty card image are always exported, for example SPOINT.

Assembly

Do Not Export: Does not export assembly comments. If there are components defined within an assembly that is set to Do Not Export, then these component are also not exported. If the same component is referenced in multiple assemblies which have different export statuses, then you must also verify the export status for each component to assure its final export status.
Export: Export assembly comments. When changing from Do Not Export to Export, it sets any components defined within that assembly to Export, regardless if that component exists in multiple assemblies.

Component

Do Not Export: Does not export component comments, component definitions, nodes (see below), elements, connector comments, points, lines, surfaces, and solids within that component.
Nodes within components can be of two types: Internal nodes and Boundary nodes. Internal nodes are not shared with any other component. Boundary nodes are shared with other components. Internal nodes "export" is based solely on their component export state. Boundary nodes do not export, if all components which they reside in are set to Do Not Export. If a boundary node exists in any one component set to Export, then that boundary node is also exported.
Export: Export component comments, component definitions, nodes (internal and boundary), elements, connector comments, points, lines, surfaces, and solids within that component.

Load Collector

Do Not Export: Does not export LoadCollector comments, loads, or equations within that LoadCollector
Export: Exports LoadCollector comments, nodes/elements attached to loads/equations, loads, and equations within that LoadCollector

System Collector

Do Not Export: Does not export SystemCollector comments or systems within that SystemCollector
Export: Exports SystemCollector comments, nodes attached to systems, and system definitions within that SystemCollector

Vector Collector

Do Not Export: Does not export VectorCollector comments or vectors within that VectorCollector
Export: Exports VectorCollector comments, nodes attached to vectors and vector definitions within that VectorCollector

BeamSection Collector

Do Not Export: Does not export BeamSectionCollector comments or BeamSection comments within that BeamSectionCollector
Export: Exports BeamSectionCollector comments and BeamSection comments within that BeamSectionCollector

MultiBody

Do Not Export: Does not export Multibody comments, ellipsoids, MultibodyPlanes or MultibodyJoints within that Multibody Collector
Export: Exports Multibody comments, nodes attached to ellipsoids/MultibodyPlanes/MultibodyJoints, ellipsoids, MultibodyPlanes and MultibodyJoints within that Multibody Collector

LoadStep

Do Not Export: Does not export LoadStep comments or LoadStep definitions of the LoadStep
Export: Exports LoadStep comments and LoadStep definition of the LoadStep. The LoadStep export status has NO effect on the export behavior of LoadCollectors, OutputBlocks, or groups associated with the LoadStep.

Output Block

Do Not Export: Does not export OutputBlock comments or OutputBlock definitions of the OutputBlock
Export: Exports OutputBlock comments and OutputBlock definitions of the OutputBlock

Card

Do Not Export: Does not export card comments or card definition of the card. This is same as "Disable" on the Card panel.
Export: Exports card comments and card definitions of the card

Property

Do Not Export: Does not export property Comments or property definitions of the property
Export: Exports property comments and property definitions of the property

Material

Do Not Export: Does not export material comments or material definition of the material
Export: Exports material comments and material definition of the material

Sets

Do Not Export: Does not export set comments or set definitions of the set
Export: Exports set comments and set definitions of the set

Blocks

Do Not Export: Does not export block comments or block definitions of the block
Export: Exports block comments and block definitions of the block

Titles

Do Not Export: Does not export title comments or title definitions of the title
Export: Exports title comments and title definitions of the title

Plots

Do Not Export: Does not export plot comments, plot definitions, curve comments, or curve definitions associated to the plot
Export: Exports plot comments, plot definitions, curve comments, and curve definitions associated to the plot

Contact Surface

Do Not Export: Does not export ContactSurface comments or ContactSurface definitions of the ContactSurface
Export: Exports comments and nodes/elements associated to ContactSurface or ContactSurface definitions of the ContactSurface

Group

Do Not Export: Does not export group comments or group definitions of the group
Export: Exports group comments, nodes/elements associated with Group and group definitions of the group

Sensor

Do Not Export: Does not export sensor comments or sensor definitions of the sensor
Export: Exports sensor comments and sensor definitions of the sensor

Control Volume

Do Not Export: Does not export ControlVolume comments or ControlVolume definitions of the ControlVolume
Export: Exports ControlVolume comments and Control Volume definitions of the ControlVolume

Element

Controlled by component collector export status

Connector

Controlled by component collector export status

Load

Controlled by load collector export status

Equation

Controlled by load collector export status

System

Controlled by system collector export status

Vector

Controlled by vector collector export status

Point

Controlled by component collector export status

Line

Controlled by component collector export status

Surfaces

Controlled by component collector export status

Solid

Controlled by component collector export status

Beam Section

Controlled by beam section collector export status

Ellipsoids

Controlled by multibody collector export status

Multibody Planes

Controlled by multibody collector export status

Multibody Joints

Controlled by multibody collector export status

Load Summary Templates

Summary templates are templates that you can use to count elements or categorize properties.

These templates do not create solver input, but are used to gain a quick overview of a model or to find specific solver-related information about a model.

Summary template functions include:

Calculating the center of gravity
Listing components associated with materials
Checking for errors that would cause an input deck to be rejected by a solver

For more information about creating and using a summary template, see the Summary panel.

From the menu bar, click Tools > Summary Template.
Click Load.
Browse to your solver specific folder and click the name of your solver. When using a summary template for the first time, jump to step 4 thereafter.
Click on the summary template to use and click Open.
Click browse... and select an output file from the Save file Browser to store the summary.
Click Save.
Select all or displayed to output all or only some of the contents of the deck.
Click summary.

Supported Summary Templates

Overview of the Summary Templates supported by the solver interfaces.

ANSYS

Path Within HyperWorks Installation	Description
.../templates/summary/ansys/components	Reviews components of the current database containing 1-D, 2-D and 3-D elements
.../templates/summary/ansys/elements	Reviews all elements of the current database
.../templates/summary/ansys/loads	Reviews the loads of the current database
.../templates/summary/ansys/ctr_of_gravity	Calculates the model’s center of gravity
.../templates/summary/ansys/mom_of_inertia	Determines area properties
.../templates/summary/ansys/materials	Reviews material properties of the current database
.../templates/summary/ansys/id_info	This reviews the minimum and maximum IDs of nodes, elements, components, materials, properties, and so on.

Note: To use the mom_of_inertia template, create a planar area with shell43/shell63 elements (quads and trias) in the x-y plane.

LS-DYNA

LS-DYNA summary template files are located in the template/summary/ls-dyna directory.

Template	Description
elements	Provides a listing of element types and the number of each type contained in the current model. It also indicates the total number of elements in the model.
errorcheck	Gives a brief overview of problems that exist in the model.
sharedrigids	Highlights the elements with nodes that are shared among rigids.
ctr_of_gravity	Calculates each part’s center of gravity and the model's center of gravity based on the procedure described in the Mass Calculations section.
components	Describes the components and their properties contained in the model. The template lists the name, ID, property name and ID, material name and ID, mass, nodal mass added to each part, thickness and numbers of elements in each part. The mass is calculated using the same procedure as the mass panel.
mom_of_inertia	Calculates each component's and the model’s moment of inertia based on the procedure described in the Mass Calculations section.

Both the errorcheck template and sharedrigids template check for shared rigids, but the template highlights only the second element that uses a node. If an element in a rigid material is sharing a node with another rigid, only the first element in that component is highlighted.

Possible error messages:

Elements in components pointing to a *SECTION card of the wrong type
Zero or negative thickness
Rigid elements, components, or interfaces sharing nodes
Components do not have a *SECTION card selected
Components do not have a necessary *PART card defined
Components do not have a material selected

A more advanced error check tool is available on the Tools option on the Utility menu. This tool checks components, rigids, joints, properties, boundary conditions, and other model entities and displays the results in a user-friendly format that enables you to select an error and go directly to the relevant part of the model to make corrections.

Marc

Note: Marc is not available in Engineering Solutions.

Template	Description
ctr_of_gravity	Calculates the center of gravity of the model.
mom_of_inertia	Calculates the moment of inertia of each component of the model as well as the moment of inertia of the entire model.
show_normals2d.sum	Shows the orientation of a 2-D rigid body which consist of plot elements of type FACET_2.
reverse_normals2d.sum	Reverse the orientation of a 2-D rigid body.

Nastran

Template	Description
elements	Summarizes the number of each element type in the current HyperMesh database.
loads	Summarizes the forces and moments applied to the current model.
ctr_of_gravity	Calculates the center of gravity of the model.
errorcheck	Summarizes some common model errors.
mom_of_intertia	Calculates the mass moment of inertia of each component of the model as well as the mass moment of inertia of the entire model. The mass moment of inertia of the entire model is presented in matrix format.
components	Summarizes the component information in the current HyperMesh database.

The Mass Moment of Inertia template writes out the mass matrix in the following form,

where

For Inertia Matrix for Model (Using Origin As Reference), the following applies,

For Inertia Matrix for Model (Using Center of Gravity As Reference), the following applies,

PAM-CRASH 2G

Summary template directory: $hmdir/template/summary/pamcrash2g

Summary templates with a _txt appendix, for example, components_txt, can be used to export summary template information to a text file only.

Template Name	Description
ctr_of_gravity	Lists the component and model center of gravity.
moment_of_inertia	Lists the moment of inertia for components and for the model.
components	Lists the components with ID, thickness, mass, and number of elements. You can write the result data in other units using the command, "*uservariableset("#MASS_UNIT_FACTOR",[1.0])" at the beginning of the components file in the include directory of the summary files. All calculated values are multiplied with this factor before being written. You can change this value for your own purpose. Non-structural masses are also listed in addition to the structural masses.
elements	Lists the elements with their PAM-CRASH 2G equivalent keywords.
groups	Lists the groups with their PAM-CRASH 2G equivalent keywords, type, and ID.
materials	Lists the materials and their corresponding elements. The model mass is calculated for each material. Lumped masses and type 3 rigid bodies are also listed.
sensor	Lists the sensors and their PAM-CRASH 2G keywords and types.
property	Lists the number of airbags, friction card, gaspec definitions, and rupture models.
find_cnodes	Displays the CNODEs as temporary nodes.
id_info	Lists the IDs and ranges of used HyperMesh entities.
nsmas	Lists the non-structural masses in the model together with the attached components.

Permas

Note: Permas is not available in Engineering Solutions.

Template	Description
elements	Summarizes the number and type of elements in the current HyperMesh model for a Permas analysis.
ctr_of_gravity	Calculates the center of gravity of the model.
mom_of_inertia	Calculates the moment of inertia of each component of the model, as well as the moment of inertia of the entire model.

OptiStruct

The optistruct template generates OptiStruct input decks.

The optistructlf template generates OptiStruct input decks using the long format for CELAS, CONM2, FORCE, GRID, MAT1, MAT2, MAT8, MAT9, MOMENT, MPC, PBEAM, PBEAML, PCOMP, PCOMPG, PBARL, PROD, and PSHELL bulk data entries.

DVGRID bulk data entries are written in long format with both templates.

All settings necessary to interface with OptiStruct can be loaded by loading the OptiStruct user profile.

Template	Description
components	Summarizes the name, number, material, mass, and number of elements for each component in the current HyperMesh database.
constraints	Summarizes the name, number, response, lower, and upper bounds for each constraint in an optimization problem defined in the current HyperMesh database.
ctr of gravity	Calculates the center of gravity of the model.
elements	Summarizes the number of each element type in the current HyperMesh database.
loads	Summarizes the forces and moments applied to the current model.
mom of inertia	The mom_of_inertia template calculates the moments of inertia of the model. The mass moment of inertia of the entire model is presented in matrix format.
errorcheck	Summarizes the model errors.
responses	Summarizes the name and type of responses in an optimization problem defined in the current HyperMesh database.

The Mass Moment of Inertia template writes out the mass matrix in the following form,

where

For Inertia Matrix for Model (Using Origin As Reference), the following applies,

For Inertia Matrix for Model (Using Center of Gravity As Reference), the following applies,

Export HyperView Solver Decks

Export deformed shapes as an Abaqus, DynaKey, OptiStruct/Nastran or STL model.

These files can be read into a pre-processor, such as HyperMesh, or into a CAD tool to view the deformed geometry.

Note: Only unscaled coordinates are exported. If scaled coordinates are needed, use the Linear Superposition utility in HyperView to create a subcase, and then use this utility to export the solver deck (with scaled coordinates). To create a derived loadstep from a simulation list, refer to Derived Load Cases.

Export a solver deck in the following ways:
- From the menu bar, select File > Export > Solver Deck.
- From the Standard toolbar, click (Export Solver Deck).
The Export Deformed Shape dialog opens.
For Select format, select a file type.
In the File name field, specify a file name and location.
Click OK.
In the HyperView dialog that opens:
- Click Yes to continue exporting the solver deck.
- Click No if scaled coordinates are needed and you need to stop exporting the solver deck.

Export Geometry

Export a CAD file.

Import geometry in the following ways:
- From the menu bar, click File > Export > Geometry.
- From the Standard toolbar, click (Export Geometry).
The Export - Geometry tab opens.
For File Type, select the file type to export.
In the File field, specify a filename and location.
Define CAD export options by clicking to the left of Export Options.
Click Export.

CAD Export Options

CAD writers provide options for processing data during export.

Some of these options are available from the Export browser, while other options are accessed only from each writer's _writer.ini file.

Version: Corresponds to the @Version option.
File mode: Corresponds to the @FileMode option.
Export: Corresponds to the @Export option.
Source units: Corresponds to the @SourceUnits option.; Set a source unit before exporting by manually selecting a unit system from a list of units, or click From Metadata to select a source unit from the MODEL_UNIT metadata attached to the component/part. If the components/parts have differing MODEL_UNIT metadata values, the most commonly used value is adopted and a warning message is displayed.
To prevent the frequent, unintended, selection of units, the source units selection is cleared anytime the export CAD file type is changed and you must reselect the units before exporting.
Target units: Corresponds to the @TargetUnits option. When Target units value is selected as Source units (default), Target units is assigned a value from Source units and used during export.
Output Loop: Corresponds to the @OuterLoop option.
Layers: Corresponds to the @LayersMode options.
Geom mode: Corresponds to the @GeometryMode option.
Topo mode: Corresponds to the @TopologyMode option.
Assem mode: Corresponds to the @AssemblyMode option.
Naming mode: Corresponds to the @WriteMetaDataAsName and @WriteNameFrom options.
User defined: Additional options not explicitly exposed in the GUI, in the form option1_name=option1_value, option2_name=option2_value, and so on. If an option is also exposed in GUI is mentioned in this field, the value of this field prevails.
Name from representation: Corresponds to the @NameFromRepresentation option.
Optimize for CAD: Corresponds to the @OptimizeForCAD option.
Prompt before overwrite: Prompts you if the specified file name already exists and will be overwritten.

Export BOMs

Export bill of material files.

Export BOMs in the following ways:
- From the menu bar, select File > Export > BOM.
- From the Standard toolbar, click (Export BOM).
The Import - BOM tab opens.
For File type, select the type of file to import.

Tip: Choose Auto Detect to automatically select an input translator.
In the File field, specify a location and file name.
Define BOM export options by clicking to the left of Export Options.
1. To display a prompt if the filename already exist and will be overwritten upon export, select the Prompt before overwrite checkbox.
2. To save a HyperMesh binary file that contains the model hierarchy and the currently loaded representations, and attach a representation to the top level Part Assembly, select the Save Monolithic HM binary file.
Click Export.

Export Curves

Export plot data in several different formats so that it can be read by other software applications.

Export templates can be added to the Export Curves dialog using the *AddExportFormat() statement in the preference.mvw file.

Export format templates are written using the Templex programming language.

Note:

Only curves that are turned on are exported. Any curves that are currently turned off within a plot are not exported.

Export curves in the following ways:
- From the menu bar, select File > Export > Curves.
- From the Standard toolbar, click (Export Curves).
The Export Curves dialog opens.

For Export Format, select the format for exported data.

Option	Description
Excel (.csv)	CSV, comma separated values, format. CSV is compatible with most spreadsheet applications. Commas delimit the data.
Columns (.col)	One column for X data and another for Y data. A blank line separates each curve in the plot. Tabs delimit the data.
XY DATA (.dat)	One column for X data and another for Y data. The data set for each curve in the plot begins with XYDATA and ends with ENDATA. The XY units and the axis labels are included at the top of each data set. Tabs delimit the data. HyperMesh uses this format.
XGRAPH (.xgr)	One column for X data and another for Y data. The XY units and the axis labels are included as comments at the top of each data set. Tabs delimit the data.
tableG (.dat)	OptiStruct tableG format.
Summary (.sum)	The summary file contains the plot title and a table listing the curves in the plot, the X and Y data labels, and the min and max values of each curve.
ADAMS Spline (.adm)	The X values for each curve are listed in comma delimited columns followed by the Y values in comma delimited columns. The first data set in the file is labeled SPLINE/0. The label for each successive data set is incremented by one.
Altair Binary (.abf)	All curves in the window are written to an Altair Binary format file.
CSV Blocks (.csv)	CSV blocks writes out a file with four values, XYXY. The data is comma separated.
DAC (.dac)	Exports curve data to DAC files, one file per curve. If more than one curve is requested, the name of the output file is modified by adding the unique request name to the file name.
RPC (.rsp)	The RPC file will contain one time channel and multiple signal channels. Value-based and file-based curves can be exported as an RPC file.
Excel Europe (.csv)	The Excel Europe .csv format writes out a file with the CSV extension, but uses a semi-colon instead of a comma to separate columns.
User-specified DLL (.dll)	A user-specified DLL, registered with the preferences statement *RegisterExportDLL(). After the preference file is read, if you select Export Curves, the name of the DLL will be at the end of the list of formats in the Export Curves dialog box.
ISO MME (.mme)	Exports curve data to an export.mme file. Upon export, a channel folder is created that contains a channel for each curve. See the ISO MME section below for more information.

In the File Path field, specify a location and file name.
For Range, select which pages to export.
- Choose All to export every curve on every page in the page list to the specified file.
- Choose Current plot to export just the currently displayed plot to the specified file.
- Choose Current page to export just the currently displayed page to the specified file.
- Choose Pages to export a specific group of pages from the page list. Enter the page number of the first page in the From field, and enter the page number of the last page in the To field.
For Values, select the curve values to export.

Value pairs, where either x, y, or both values cause a domain violation, will not be exported.
- Choose Original Curve Values to export the curve's original values.
- Choose Displayed Axis Values to export the dB scaled values.
  Restriction: Not available when Export Format is set to Summary, DAC, RPC, or ISO MME.
If Export Format is set to ISO MME, define additional options.

Exporting curves using the ISO MME format creates a channel folder that contains one channel file with the format export.chn as well as a file for each curve in your session. The curve files have the format export.001, export.002, and so on. The files contain curve and session information.

You can then import the export.mme file to read the data back into HyperGraph.
- To delete any existing files in the channel directory upon export, select the Delete all existing files in channel directory checkbox.
- To enter a start and end point to remove data outside of the specified range, select the Trim curve label checkbox.
Click OK.

Export Markers

Export marker files from MediaView.

Export markers in the following ways:
- From the menu bar, select File > Export > Markers.
- From the Standard toolbar, click (Export Markers).
The Export Markers dialog opens.
In the File Path field, specify a location and file name.
Click Save.

Export Connectors

Export connector files.

Export connectors in the following ways:
- From the menu bar, select File > Export > Connectors.
- From the Standard toolbar, click (Export Connectors).
The Export - Connectors tab opens.
For File type, select a file type to export.
- ASCII: The very basic format. The data labeled in a header line for one connector are in a row and separated by "::". This format outputs the information of connector id, layer, position, config, and link and is only for spot connectors.
- XML1.0: The Altair 1st version of xml format and can be used as both a standalone file or embedded in a solver deck. This format outputs all information about different types of connectors except realization state and FEs, which are only output together with a solver deck. Connectors are organized based on links in an xml file of this format.
- XML 2.0 (default): The Altair 2nd version of xml formats. Compared to XML 1.0, it is a more flexible format and there are two differences: individual connector structure and connectors are not grouped based on links. Most data are written in the format of name-value pair.
- MCF (version A): By default, HyperMesh will export the bolt connector vector that was dynamically identified during realization. The vector can be exported with or without the bolt. If a bolt connector vector is not identified after you import the connector, HyperMesh will search for the dynamic vector again. If a vector is already defined on the connector, HyperMesh will use that vector for realization.
- MCF (verion B): Only output limited information of connectors, like links and positions. Version A and version B have some subtle differences, for example, version B only supports component links whereas version A supports both component and property links.
- VIP: Very simple column data format for spot connector only, includes connector id, position and link IDs.
- xMCF: An advanced xml format, it is a standard that is currently being established between different software vendors for CAD, FEA and Fatigue. Compared to MCF (version A) and MCF (version B), this format outputs more details.
In the File field, specify a file name and location.
Define Connector Export Options by clicking to the left of Export Options.
Click Export.

Note:

For XMCF files, the following types of connectors and features are managed:

0D: Spotweld, bolt, screw, gumdrop, clinch, rivet (blind, self-piercing, solid, swop), robscan, contact_list, threaded connection, heat stake, clip, nail
1D: Sequence connection 0D (spotweld, gumdrop), seamweld (butt_joint, corner weld, edge weld, i_weld, overlap weld, y-joint, k-joint, cruciform joint, flared joint), adhesive-line, hemming, contact list
2D: Adhesive face
Custom attributes are managed.
Appdata is not managed.

Connector Export Options

Supported connector export options.

Export

Specify which connectors to export.

All: Export all of the connectors in the model.
Displayed: Export only the connectors that are currently displayed in the modeling window.

Include metadata

Export the metadata information.

Include bolt dynamic vector

Convert Links

Export as Common Format

Prompt before overwrite

Display a warning message before a file is overwritten during export.

Export Table CSV

Export a comma separated value file.

TableView supports multiple lines of data in a single cell. To add a line break, press Alt + Enter. In TableView, the Conditional Formatting and the Cell Data panels are disabled if you select a cell that contains multiple lines or if you press Alt + Enter.

Export a CSV file in the following ways:
- From the menu bar, select File > Export > Table CSV.
- From the Standard toolbar, click (Export Table CSV).
In the Export CSV File dialog, specify a location and filename.

You can also use the default name, tableexport.
Click Save.

HyperMesh Comments

If you insert special comment cards into your input deck, you can provide HyperMesh with additional information about the colors and names of entities. You can also use comments to preserve information that is not supported by a particular solver, for example, assemblies or system references.

HyperMesh Comments

Input

compid(s): A list of identification numbers.

Supported Solvers

Abaqus

Nastran

PAM-CRASH 2G

HMASSEM_ID

Import comment to sort and organize entity types into HyperMesh.

Syntax

HMASSEM_ID assembly id(s)

Type

HyperMesh Comments

Description

assembly id(s): A list of identification numbers.

Supported Solvers

Nastran

HMBEAMSEC

Import comment to sort and organize property types and info into HyperMesh.

This Comment appears above /PROP/BEAM & /PROP/TRUS definitions. When reading an input deck that includes these comments, HyperMesh takes the Ixx,Iyy & AREA values from the HyperBeam comments definition.

If you want to edit the card image values for such property cards in a text editor instead of using HyperMesh, then this comment has to be deleted. Otherwise, the Ixx, Iyy and AREA values present in these Prop card definitions are not taken into consideration, but instead the values from the HyperBeam comments Association definitions, i.e. data following ##HMNAME BEAMSECTS, are taken.

Syntax

HMBEAMSEC type, prop_id, beamsec_id

Type

HyperMesh Comments

Input

type: PBARASSOC, PBARLASSOC, PBEAMASSOC, PBEAMINTASSOC, PBEAMLASSOC, PBEAMLINTASSOC, PRODASSOC, PTUBEASSOC, PWELDASSOC
prop_id: Unique property identification number.
Beamsec_id: A beam section identification number.

Supported Solvers

OptiStruct

Radioss

ANSYS

PAM-CRASH 2G

Permas

HMBEGINDOC

Import comment that indicates the beginning of the model documentation into HyperMesh.

The $HMBEGINDOC card indicates the beginning of card used for model documentation. Any number of comment lines can be placed after this line. The end of this block is indicated by a $HMENDDOC statement. Only one model documentation block is allowed per model. Upon import, the comments within the block are placed in the control card “Model Documentation”.

Syntax

HMBEGINDOC Comment 1, Comment 2, Comment 3, HMENDDOC

Type

HyperMesh Comments

Input

Comment 1, 2, 3, and so on.: <Any text entered>

Supported Solvers

OptiStruct

PAM-CRASH 2G

HMCOMP

Import comment to sort and organize entity types into HyperMesh.

Syntax

HMCOMP id, name color_id

Type

HyperMesh Comments

Input

id: Unique entity type identification number.
name: A name given by you to help organize the model or describe the entity.
color_id: A color identification number from the HyperMesh color palate.

Supported Solvers

Radioss

PAM-CRASH 2G

HMCONT

Continuation card for the HMBEAMSEC card.

Syntax

HMCONT id, set_id,name

Type

HyperMesh Comments

Input

id: Unique entity type identification number.
set_id: Unique entity type identification number.
name: A name given by you to help organize the model or describe the entity.

Supported Solvers

LS-DYNA

PAM-CRASH 2G

HMCURVE

Preserves the style information for load curves.

Syntax

HMCURVE line_type, marker_type, title

TYPE

HyperMesh Comments

Input

line_type: A five-character integer that describes the style of the line, such as solid and dashed.
marker_type: A five-character integer that describes the style of the point marker on the curve, such as square and round.
title: An 80-character string used to save the label given to the curve.

Supported Solvers

OptiStruct

Radioss

Abaqus

LS-DYNA

HMDB

Points to a material database file for the solver.

Syntax

HMDB entitytype, id, name

Type

HyperMesh Comments

Input

entity_type: ASSEM, BEAMSECTCOL, BEAMSECTCOLS, BEAMSECTS, BLOCKS, BLOCKS, CGAPG, COMP, CONNECTOR, CONTACTSURF, CONTROLVOL, CSURF, CURVE, CWELD, DDVAL, DEQUATIONS, DESVARS, DLINKS, DOBJREF, DVPRELS, GROUP, LOADCOL, LOADSTEP, MAT, METADATA, OBJECTIVES, OPTICONSTRAINTS, OPTICONTROLS, OPTIDSCREENS, OPTITABLEENTRS, OUTPUTBLOCKS, PLOT, PROP, SENSOR, SETS, SHAPE, SYSCOL, VECTORCOL
id: Unique entity type identification number.
name: A name given by you to help organize the model or describe the entity.

Supported Solvers

OptiStruct

Radioss

Abaqus

ANSYS

LS-DYNA

Nastran

PAM-CRASH 2G

Permas

And other miscellaneous solvers

HMDISPLAY

Defines the base location of a velocity load in HyperMesh.

Syntax

HMDISPLAY type, base_location_x, base_location_y, base_location_z

Type

HyperMesh Comments

Input

type: LOCATION
base_location_x: X location of the grid for the display.
base_location_y: Y location of the grid for the display.
base_location_z: Z location of the grid for the display.

Supported Solvers

Abaqus

HMDPRP

Import comment to sort and organize design properties into HyperMesh.

Syntax

HMDPRP elements, ids

Type

HyperMesh Comments

Input

elements: A list of elements.
IDs: IDs

Supported Solvers

Abaqus

Nastran

HMENDDOC

Import comment that indicates the end of the model documentation into HyperMesh.

The $HMENDDOC card indicates the end of a card used for model documentation. Any number of comment lines can be placed before this line. The beginning of this block is indicated by a $HMBEGINDOC statement. Only one model documentation block is allowed per model. Upon import, the comments within the block are placed in the control card “Model Documentation”.

Syntax

HMENDDOC

Type

HyperMesh Comments

Input

N/A

Supported Solvers

OptiStruct

PAM-CRASH 2G

HMENT

Preserves the ADMASS card upon import in Radioss.

Syntax

HMENT elem_id, vis_nod, node_id

Type

HyperMesh Comments

Input

elem_id: Element identification number
vis_nod
node_id: Node_id

Supported Solvers

OptiStruct

HMERROR

Export comment that detects a problem upon export.

The HMERROR comment is output when the HyperMesh template detects and/or corrects a problem during creation of the deck. It is included to inform you of possible problems with the deck.

Syntax

HMERROR type

Type

HyperMesh Comments

Input

type: text

Supported Solvers

N/A

HMFIXEDSURFPOINT

Describes weld points for the automesher.

The HMFIXEDSURFPOINT comment is used to describe weld points for the automesher. X, Y, and Z are 16-character real numbers that describe the x, y, z location of the fixed point, and suppressed is an eight-character integer describing the type of fixed point.

Syntax

HMFIXEDSURFPOINT x, y, z, suppressed

Type

HyperMesh Comments

Input

x: X location of the fixed point.
y: Y location of the fixed point.
z: Z location of the fixed point.
suppressed: An eight-character integer describing the type of fixed point.

Supported Solvers

N/A

HMFOOTERBEGIN

Import comment that indicates the beginning of the footer for the deck.

The $HMFOOTERBEGIN card indicates the beginning of footer notes in the deck. Any number of comment lines can be placed after this line. The end of this block is indicated by a $HMFOOTEREND statement. Only one footer documentation block is allowed per model.

Syntax

HMFOOTERBEGIN Comment 1, Comment 2, Comment 3, HMFOOTEREND

Type

HyperMesh Comments

Input

Comment 1: Text entered

Supported Solvers

OptiStruct

HMFOOTEREND

Import comment that indicates the end of the footer for the deck.

The $HMFOOTEREND card indicates the end of the footer notes in the deck. The begining of this block is indicated by a $HMFOOTERBEGIN statement. Only one footer documentation block is allowed per model.

Syntax

HMFOOTERBEGIN Comment 1, Comment 2, Comment 3, HMFOOTEREND

Type

HyperMesh Comments

Input

Comment 1, 2, 3, and so on.: Text entered

Supported Solvers

OptiStruct

HMFLAG

Syntax

HMFLAG entity_type, slave

Type

HyperMesh Comments

Input

entity_type: COMPS, GROUPS
slave

Supported Solvers

LS-DYNA

HMGPMV

Defines a conduction group identification number in HyperMesh.

Syntax

HMGPMV conduction_group_id

Type

HyperMesh Comments

Input

conduction_group_id: Unique conduction group identification number

Supported Solvers

Nastran

HMMOVE

Change the input component of an element.

The HMMOVE comment helps to preserve the original user organization of elements into components when exporting and importing models via solver decks. This comment is required when the solver does not have a card/keyword corresponding to the HyperMesh component. In the case of PAM-CRASH, HMMOVE is also used to organize systems into system collectors.

The format of the HMMOVE comment varies with the different solver interfaces.

OptiStruct/Nastran

$HMMOVE  comp_id
$           eid1    eid2     ...
$       rangeid1THRU    rangeid2     ...

The component ID on the $HMMOVE comment line starts at column 9, and is written using a field width of 8.

The first element ID on each following line starts at column 9, and every element ID is written using a field width of 8.

A continuous sequence of element IDs is written as a range as shown in the third line. The THRU statement is also written using a field width of 8.

A single $HMMOVE comment can consist of either just individual IDs, just ranges, or any combination.

A new comment line begins once column 80 is reached.

Example:

$HMMOVE        8
$          50000   50002   50004   50006   50008   50010   50012   50014   50016
$          50018THRU       50022

PAM-CRASH

$HMMOVE  collector_id
Solver card corresponding to 0-D/1-D element or system

The collector ID on the $HMMOVE comment line starts at column 9, and its field width that is exactly equal to the number of digits used for the ID.

Examples:

$HMMOVE 9
RBODY /    47283               0   12705                       0             0.0

$HMMOVE  1
FRAME /        1       0       0

Radioss

##HMMOVE elements eid comp_id
Solver card corresponding to 0-D/1-D element

The element ID (eid) on the ##HMMOVE comment line starts at column 19. Both eid and comp_id occupy a field width that is exactly equal to the number of digits used for the corresponding ID, and are separated by a single space.

Example:

$HMMOVE 9
##HMMOVE elements 2 8
/RBODY/2
    26683                                                           2

Syntax

HMMOVE ?options?

Type

HyperMesh Comments

Input

N/A

Supported Solvers

OptiStruct

Radioss

Nastran

PAM-CRASH

HMNAME

Import comment to sort and organize entity types into HyperMesh.

Syntax

HMNAME entity_type, id, name, ?id_pool?

Type

HyperMesh Comments

Input

entity_type

BEAMSECTCOL, BEAMSECT, BLOCK, CGAPG, CONNECTOR, CONTACTSURF, CONTROLVOL, CSURF, CURVE, CWELD, DDVAL, DEQUATIONS, DESVARS, DLINKS, DOBJREF, DVPRELS, LOADCOL, LOADSTEP, METADATA, OBJECTIVES, OPTICONSTRAINTS, OPTICONTROLS, OPTIDSCREENS, OPTITABLEENTRS, OUTPUTBLOCKS, PLOT, SENSOR, SHAPE, SYSTCOL, VECTORCOL, PROP

id

Unique entity type identification number.

name

A name given by you to help organize the model or describe the entity.

id_pool

The entity ID pool for applicable solvers.

Property Grouping	Applicable Card Image(s)	ID pool #
0D_Rigids	Nastran/OptiStruct PMASS	1
Springs_Gaps	Nastran/OptiStruct PBUSH, PBUSH1D, PDAMP, PELAS, PGAP, PVISC Nastran PHBDY	2
1D	Nastran/OptiStruct PBAR, PBARL, PBEAM, PBEAML, PFAST, PROD, PTUBE, PWELD Nastran PAERO2, PBEND, PSEAM	3
2D	Nastran/OptiStruct PCOMP, PCOMPG, PCOMPP, PSHEAR, PSHELL Nastran PAERO1	4
3D	Nastran/OptiStruct PSOLID Nastran PLSOLID OptiStruct PGASK	5
Contact	OptiStruct PCONT	6
Acoustic	Nastran/OptiStruct PAABSF, PACABS Nastran PACINF	7

Supported Solvers

OptiStruct

Radioss

Abaqus

ANSYS

LS-DYNA

Nastran

PAM-CRASH 2G

Permas

And other miscellaneous solvers

HMNAME ASSEM

Import comment to sort and organize entity types into HyperMesh.

Syntax

HMNAME ASSEM, id, name

Type

HyperMesh Comments

Input

entity_type: ASSEM
id: Unique entity type identification number.
name: A name given by you to help organize the model or describe the entity.

Supported Solvers

ANSYS

HMNAME COMP

Import comment to sort and organize entity types into HyperMesh.

Syntax

HMNAME COMP id, name, property_id, property_name, id_pool

Type

HyperMesh Comments

Input

entity_type: COMP
id: Unique entity type identification number.
name: A name given by you to help organize the model or describe the entity.
property_id: Unique entity type identification number. Valid only for OptiStruct and Nastran.
property_name: A name given by you to help describe the entity. Valid only for OptiStruct and Nastran.
id_pool: Internal solver ID pool. Valid only for OptiStruct and Nastran.

Supported Solvers

OptiStruct

Radioss

ANSYS

LS-DYNA

Nastran

HMNAME GROUP

Import comment to sort and organize entity types into HyperMesh.

Syntax

HMNAME GROUP id, name, card_image

Type

HyperMesh Comments

Input

entity_type: GROUP
id: Unique entity type identification number.
name: A name given by you to help organize the model or describe the entity.
card_image: Solver related card image.

Supported Solvers

OptiStruct

Radioss

Nastran

HMNAME MAT

Import comment to sort and organize entity types into HyperMesh.

Syntax

HMNAME MAT id, name

Type

HyperMesh Comments

Input

entity_type: MAT
id: Unique entity type identification number.
name: A name given by you to help organize the model or describe the entity.

Supported Solvers

OptiStruct

Radioss

ANSYS

LS-DYNA

Nastran

PAM-CRASH 2G

HMNAME PROP

Import comment to sort and organize entity types into HyperMesh.

Syntax

HMNAME PROP id, name, id_pool

Type

HyperMesh Comments

Input

entity_type: PROP
id: Unique entity type identification number.
name: A name given by you to help organize the model or describe the entity.
id_pool: Internal solver ID pool.

Supported Solvers

OptiStruct

Radioss

Abaqus

ANSYS

LS-DYNA

Re-associate nodes/systems with their local systems.

Some solver codes do not support nodes or coordinate systems created in or referencing local coordinate systems. If you define a block of comments at the end of the deck, you can re-associate the nodes/systems with their local coordinate systems.

Syntax

HMREFSYSTEM type, id, system_id

Type

HyperMesh Comments

Input

type: The five-character name of the entity type, either NODES or SYSTS.
id: The HyperMesh ID of the node/system referencing the system, a 10-character integer.
System_id: The HyperMesh ID of the coordinate system, a 10-character integer.

Supported Solvers

N/A

HMSET

Import comment to sort and organize entity sets into HyperMesh.

This comment is used to signify that the following set was created by you in HyperMesh and not while the deck was being output by the templates. This changes the method by which the set is imported into HyperMesh and how it is associated with groups.

Syntax

HMSET id, entity_type, name

Type

HyperMesh Comments

Input

id: Unique entity type identification number.
entity_type: ASSEM, BEAMSECTCOL, BEAMSECTCOLS, BEAMSECTS, BLOCKS, BLOCKS, CGAPG, COMP, CONNECTOR, CONTACTSURF, CONTROLVOL, CSURF, CURVE, CWELD, DDVAL, DEQUATIONS, DESVARS, DLINKS, DOBJREF, DVPRELS, GROUP, LOADCOL, LOADSTEP, MAT, METADATA, OBJECTIVES, OPTICONSTRAINTS, OPTICONTROLS, OPTIDSCREENS, OPTITABLEENTRS, OUTPUTBLOCKS, PLOT, PROP, SENSOR, SETS, SHAPE, SYSCOL, VECTORCOL, “regular/formula”
name: A name given by you to help organize the model or describe the entity.

Supported Solvers

OptiStruct

LS-DYNA

OptiStruct

Abaqus

Nastran

Permas

HMUNSUPPORTED

Import comment to indicate to the reader that information in this section should be retained in the unsupported area of HyperMesh.

This comment is used in pairs, with the type argument indicating the beginning or end of the comment block.

Syntax

HMUNSUPPORTED BEGIN Comment 1, Comment 2, Comment 3, HMUNSUPPORTED END

Type

HyperMesh Comments

Input

type: BEGIN, END
comment: Any desired text.

Supported Solvers

N/A

HWCOLOR

Import comment to color an entity in HyperMesh.

Syntax

HWCOLOR entity_type, id, color_id

Type

HyperMesh Comments

Input

entity_type: ASSEM, BEAMSECTCOL, BEAMSECTCOLS, BEAMSECTS, BLOCKS, BLOCKS, CGAPG, COMP, CONNECTOR, CONTACTSURF, CONTROLVOL, CSURF, CURVE, CWELD, DDVAL, DEQUATIONS, DESVARS, DLINKS, DOBJREF, DVPRELS, GROUP, LOADCOL, LOADSTEP, MAT, METADATA, OBJECTIVES, OPTICONSTRAINTS, OPTICONTROLS, OPTIDSCREENS, OPTITABLEENTRS, OUTPUTBLOCKS, PLOT, PROP, SENSOR, SETS, SHAPE, SYSCOL, VECTORCOL
id: Unique entity type identification number.
color_id: A color identification number from the HyperMesh color palate.

Supported Solvers

OptiStruct

Radioss

Abaqus

ANSYS

LS-DYNA

Nastran

PAM-CRASH 2G

Permas

And other miscellaneous solvers

Export Settings

Export settings for AMF, AVI, H3D, JPEG, and GIF files.

Access export settings by selecting Preferences > Export Settings > <file type> from the menu bar.

AMF and AVI

Control the quality of images saved to an AMF file or AVI animation file by changing the number of colors used and by changing the graphic size.

Palette

Full Color: Save the image as a 24 or 32 bit uncompressed full color file as it appears on the screen.
Motion JPEG: Save the file as an animated JPEG file. The quality of the animation is controlled through the Options button.
Reduced Color: Reduce the number of colors included in the saved image. Reduced color means the file is 8 bit Microsoft RLE codec or 256 color.
Grayscale: Convert the image to gray scale. Reducing the size of the image results in a reduction in file size with some loss of detail.
Window compressor: Export the file using the default AVI compressor set in your Windows operating system.

Size: Size of the exported file as a percentage of the original. Select 100 percent, 75 percent, 50 percent or 33 percent. Thirty-three percent is the default.
Frame rate (fps): Frame rate at which you want the file to be saved. The default frame rate is 25.000000.; Frame rate controls the speed of the AVI playback in the Windows Media Player and other players that use the frame rate setting. It does not change the file size nor the number of steps in the AVI file, rather only the number contained in one byte in the AVI header inside that file. In other words, the number of frames and the size of each frame are unaffected by the frame rate setting.
Restriction: AVI files only.
Encoding: Select JPEG or ZLIB.; If you select ZLIB for the Encoding parameter, there are currently no options to change the image quality.
Restriction: AVI files only.
JPEG Quality: Value for the JPEG quality.; Choosing a lower number creates a smaller file with reduced image quality, while choosing a higher.

H3D

Options to export with the HTML report.

Compression Maximum % Loss: Suggested amount that the model's values can be perturbed when compressed. The value you provide will be compared to the results of an error estimation function to allow your compression algorithm to maintain an acceptable level of accuracy for your data. However, even a percentage of zero may result in some loss due to minute rounding errors.
All models: Export all the models in the window to individual files when two or more models are loaded.; The active model will be exported to the file name shown in the dialog. All inactive models will be exported using the following naming convention: <filename>.x.h3d, where "x" increases incrementally as required. For example, the active model is exported as LSP.h3d, while the other (inactive) models will be exported as LSP.1.h3d, LSP.2.h3d, and so on.; The resulting exported H3D files are complete files which can be used independently. These files can be abstracted from the original session that exported them and used in a new session.; To read the exported files back into HyperView they must be loaded one file at a time using the Overlay option in the Load Model panel.
Entity Attributes: Output specific attributes assigned to the model's entities, such as color and transparency. If deselected, the default attributes will be used when the file is loaded.
Include Masked Elements: Export all masked elements with the model.
Include sets: Export all sets with the model.
Animation: Export any animation settings applied.
Results: Export result values with the model. If not selected, only the model and animation are exported.
View Attributes: Output all attributes assigned to the model during a HyperView session. If deselected, the default attributes will be used when the file is loaded.
HTML: Create an HTML file for use with HyperView Player.
Preview Image: Export a preview image.

Note: When exporting CFD data to an H3D file:

If there is a streamline created for at least one rake, the exported H3D file will contain the datatypes/datasets used by the CFD/Streamlines panel. In addition, all of the rake definitions and streamline settings/display options will also be captured in the H3D file.
If there are no streamlines available in the model, the exported H3D file will not contain any datatypes/datasets solely used by the CFD/Streamlines panel. In addition, none of the rake definitions or streamline settings/display options will be captured in the H3D file.

JPEG

JPEG quality: Value for the JPEG quality.; Choosing a lower number creates a smaller file with reduced image quality, while choosing a higher number creates a larger file but improves the quality of the image.

GIF

The Animated GIF Export option allows you more flexibility in controlling the playback speed and size of the GIF image. You can specify the size and the time delay between frames which will be used for all of the animated GIFs exported in video capture or publish session. You can also specify whether or not the animated GIF has a transparent background.

Due to recent enhancements, the memory usage on the Animated GIF Export has been reduced in half. This is significant when exporting a large number of timesteps/frames on low end machines with limited RAM, or 32-bit machines which have process limits set by the operating system. It should also be noted that the animated GIF format is not really well suited to the production of feature length high definition movies, due in part to its very high memory consumption during creation, and also due to the unavoidable reduction in image quality, which comes with transformation from full color to a GIF’s 256 colors.

If the rate of memory consumption is too high compared to the actual physical memory, a warning is posted informing you that the process is likely to fail, and a choice to abort or continue will be offered. It is also highly recommended that an MPEG 4 format in an AVI container be used for this type of output.

Size: Size of the exported file as a percentage of the original. Select 100 percent, 75 percent, 50 percent or 33 percent from the drop-down menu.
Note: One-hundred percent is the default setting.
Time Delay (s): Time delay between frames (in seconds) to control the playback speed of the animated GIF. The default value is 1 second.; The time delay controls the speed of the GIF playback in PowerPoint and Internet Explorer.
Transparent Background: Display the animated GIF with a transparent background.

Export Files

Export Models

Model Export Options

Export Solver Decks

Solver Deck Export Options

Solver Export Options

OptiStruct and Nastran

Permas

Abaqus

LS-DYNA

PAM-CRASH 2G

Entity Export Behavior

Free Nodes

Assembly

Component

Load Collector

System Collector

Vector Collector

BeamSection Collector

MultiBody

LoadStep

Output Block

Card

Property

Material

Sets

Blocks

Tags

Titles

Plots

Contact Surface

Group

Sensor

Control Volume

Element

Connector

Load

Equation

System

Vector

Point

Line

Surfaces

Solid

Beam Section

Ellipsoids

Multibody Planes

Multibody Joints

Load Summary Templates

Supported Summary Templates

ANSYS

LS-DYNA

Marc

Nastran

PAM-CRASH 2G

Permas

OptiStruct

Export HyperView Solver Decks

Export Geometry

CAD Export Options

Export BOMs

Export Curves

Export Markers

Export Connectors

Connector Export Options

Export Table CSV

HyperMesh Comments

HM_ASSEM

Syntax

Type

Input

Supported Solvers

HM_COMP_BY_PROP

Syntax

Type

Input

Supported Solvers

HMASSOC

Syntax

Type