Overview of external readers and the Altair Binary Format, the generic ASCII reader, running applications in batch mode, using Tcl/Tk commands, translators, and result math.
A generic ASCII reader is now available which allows you to bring custom results directly into HyperView. The AltairASCII format is useful for reading the results of any in-house or propriety codes which are saved in a generic format.
External resources can be registered in preference files, session files, or Templex files. If an external resource is registered in a program session, it is automatically registered in the session
file when the session is saved.
This API allows external applications to link HyperMesh as a library and provides a limited set of functions and structures to access specific functionality.
This section contains details on general HyperWorks scripting concepts, along with documentation on the Tcl commands that can be used to query and modify the database and GUI.
The HyperMesh Card Image panel is used to define solver specific data and review card information. The format of the cards and
the menus in the panel are defined in the export template, using HyperMesh Card Preview Commands.
Starts an equation output block. The equations in the HyperMesh database with a type equal to the type argument are output according to the user-defined format in this block.
Starts a group output block. The groups in the HyperMesh database whose configuration and type are equal to the parameters are output according to the user-defined format
in this block.
Starts an include file output block. The include file references in the HyperMesh database are output according to the user-defined format in this block.
Starts a line output block. All of the lines in the database are output according to the user-defined format in the block
following the *lines()command.
Starts a load output block. The loads in the HyperMesh database whose configuration is equal to the parameter configuration, and whose type is equal to the parameter type
are output according to the user-defined format in this block.
Starts a metadata output block. All of the metadata entries in the database are output according to the user-defined format
in the block following the *metadata() command.
Starts a node output block. All of the nodes in the database are output according to the user-defined format in the block
following the *nodes() command.
Sets the current collector based on the last *pointerset() command. This is commonly used with loadsteps. You can also use this command with sets that contain components.
Overview of external readers and the Altair Binary Format, the generic ASCII reader, running applications in batch mode, using Tcl/Tk commands, translators, and result math.
*assemblies()
Starts an assembly output block. All the assemblies in the HyperMesh database are output according to the user-defined format in this block.
*blocks()
Starts a finite difference block output block. All the blocks in the HyperMesh database are output according to the user-defined format in this block.
*equations()
Starts an equation output block. The equations in the HyperMesh database with a type equal to the type argument are output according to the user-defined format in this block.
*field()
Places a formatted value from the database into the output file.
*fieldleft()
Places a left-justified, formatted value from the database into the output file.
*fieldleftwithcomments()
Places a left-justified, formatted field name and value from the database into the output file. The field name is written just above the value line.
*fieldright()
Places a right-justified, formatted value from the database into the output file.
*fieldrightwithcomments()
Places a right-justified, formatted field name and value from the database into the output file. The field name is written just above the value line.
*fieldwithcomments()
Places a formatted field name and value from the database into the output file. The field name is written just above the value line.
*format()
Indicates that the following commands should be executed on the format level.
*geometryoverride()
Overrides the lines option on the Export Data panel and activates lines for output.
*groups()
Starts a group output block. The groups in the HyperMesh database whose configuration and type are equal to the parameters are output according to the user-defined format in this block.
*include()
Includes a file from the include directory.
*includefiles()
Starts an include file output block. The include file references in the HyperMesh database are output according to the user-defined format in this block.
*lines()
Starts a line output block. All of the lines in the database are output according to the user-defined format in the block following the *lines()command.
*loads()
Starts a load output block. The loads in the HyperMesh database whose configuration is equal to the parameter configuration, and whose type is equal to the parameter type are output according to the user-defined format in this block.
*metadata()
Starts a metadata output block. All of the metadata entries in the database are output according to the user-defined format in the block following the *metadata() command.
*nodes()
Starts a node output block. All of the nodes in the database are output according to the user-defined format in the block following the *nodes() command.
*setcollector()
Sets the current collector based on the last *pointerset() command. This is commonly used with loadsteps. You can also use this command with sets that contain components.