hmgenres

Translates generic ASCII-formatted results into HyperMesh binary results (.res).

Syntax

hmgenres ?-lf? ?-lid? ascii_source_file res_target_file

Application

Translators

Description

The tool is available from the <altair_home>/io/translators/bin/<platform> directory.

Inputs

-lf
An optional argument that specifies if long input format is used for double value fields. By default, hmgenres accepts double value fields with a width of 8. This option is used to expand double value fields to a width of 16 for increased precision.
-lid
An optional argument that specifies if long input format is used for integer value ID fields. By default, hmgenres accepts integer value ID fields with a width of 8. This option is used to expand integer value ID fields to a width of 16 for increased precision.
ascii_source_file
The name and path of the file containing the ASCII input data to translate. See below for the required format of this data.
res_target_file
The name and path of the .res file to write.

The ASCII input format is a fixed width format, with both short (8) and long (16) double value and integer value ID fields available. The use of the long formats is recommended. The fixed format is defined as follows.

The keyword SUBCASE defines the start of a subcase and specifies the subcase ID and name. The ID width is based on the -lid option, but the name can be any width. There can be multiple subcases defined in a file.

The RESULTS keyword follows and defines the beginning of a results block. It also specifies the result block name. Each subcase can contain multiple result blocks of different result types or result values.

There are three result types that are support in the RESULTS block. Each result block can only have one result type at a time.
DISPLACE
Used to specify node-based results with 3 values per node
ESTRESS
Used to specify element-based results with 1 value per element
NSTRESS
Used to specify node-based results with 1 value per node

Each RESULTS block can contain information for different entities. It is not necessary to specify results for all entities, nor for the same entities in each block.

All integer ID and double value fields must be right-justified, while name and keyword fields must be left-justified.

An example of the short format is below where all fields have a fixed width of 8. The numbers at the top show the field width and are for illustration purposes only.
<234567><234567><234567><234567><234567>
SUBCASE       idname
RESULTS name
DISPLACE node_id   x_val   y_val   z_val
DISPLACE node_id   x_val   y_val   z_val
DISPLACE node_id   x_val   y_val   z_val
RESULTS name
ESTRESS elem_id     val
ESTRESS elem_id     val
ESTRESS elem_id     val
RESULTS name
NSTRESS node_id     val
NSTRESS node_id     val
NSTRESS node_id     val
An example of the long format is below where double value fields have a fixed width of 16 and all integer and keyword fields have a fixed width of 8. The numbers at the top show the field width and are for illustration purposes only.
<234567><234567><23456789012345><23456789012345><23456789012345>
SUBCASE       idname
RESULTS name
DISPLACE node_id           x_val           y_val           z_val
DISPLACE node_id           x_val           y_val           z_val
DISPLACE node_id           x_val           y_val           z_val
RESULTS name
ESTRESS elem_id             val
ESTRESS elem_id             val
ESTRESS elem_id             val
RESULTS name
NSTRESS node_id             val
NSTRESS node_id             val
NSTRESS node_id             val
An example of the long format is below where double value fields have a fixed width of 16 and the integer ID fields have a fixed with of 16, with all keyword fields having a fixed width of 8. The numbers at the top show the field width and are for illustration purposes only.
<234567><23456789012345><23456789012345><23456789012345><23456789012345>
SUBCASE               idname
RESULTS name
DISPLACE         node_id           x_val           y_val           z_val
DISPLACE         node_id         x_val           y_val           z_val
DISPLACE         node_id           x_val           y_val           z_val
RESULTS name
ESTRESS         elem_id             val
ESTRESS         elem_id             val
ESTRESS         elem_id             val
RESULTS name
NSTRESS         node_id             val
NSTRESS         node_id           val
NSTRESS         node_id             val
An example using the short format that contains multiple subcases with two result types per subcase:
SUBCASE        1X Loads Subcase
RESULTS Displacements
DISPLACE       1     0.0     0.0     0.0
DISPLACE       2     1.0     0.0     0.0
DISPLACE       3     1.0     0.0     0.0
DISPLACE       4     0.0     0.0     0.0
RESULTS Element stress
ESTRESS        1  1000.0
SUBCASE        1Y Loads Subcase
RESULTS Displacements
DISPLACE       1     0.0     0.0     0.0
DISPLACE       2     0.0     1.0     0.0
DISPLACE       3     0.0     1.0     0.0
DISPLACE       4     0.0     0.0     0.0
RESULTS Element stress
ESTRESS        1  1000.0

Example

To translate the file C:/result.txt into C:/result.res:
hmgenres C:/result.txt
        C:/result.res