The Altair GUI Toolkit is a resource tool for coding Tcl/Tk dialogs. It contains documentation of the HyperWorks commands, demo pages that illustrate our Altair GUI standards, and sample code for creating those examples.
The Model Identification Tool, known as HyperWorks, is a profile in HyperGraph for fitting test data from frequency- and amplitude-dependent bushings to analytical models. The HyperWorks operates in conjunction with HyperGraph, MotionView and MotionSolve to provide you with a comprehensive solution for modeling and analysis.
HgTrans translates solver results files from their native file format to Altair Binary Format (ABF). This can be done using
the HgTrans GUI or via the HgTrans batch mode.
The HyperWorks Automation Toolkit (HWAT) is a collection of functions and widgets that allows an application to quickly assemble
HyperWorks automations with minimal effort and maximum portability.
HyperWorks Verification and Validation Harness (HVVH) is a tool that can be used to verify and validate HyperWorks products. End users can use this tool to quickly evaluate the software quality, performance, reliability,
scalability, and robustness, and to gain more confidence in HyperWorks products.
Using the Basic IO tab, you can verify that HyperMesh and HyperCrash do not deprecate any model during import and export. The show different report identifies any loss or change of data.
The Compare HM Versions tab allows you to compare input/output solver files between any two HyperMesh versions. You can also compare with a reference file or previously certified file. This is most useful for non-HyperMesh generated solver decks.
The actual time to import and export the solver decks across different HyperMesh versions are captured and available as a performance chart along with the difference in timing and percent change.
This helps you assess the solver interfaces based on performance.
The Compare HC Versions tab compares solver files between any two versions of HyperCrash. You can also compare with a reference file or previously certified file.
The actual time to import and export the solver decks across different HyperCrash versions are captured and available as a performance chart along with the difference in timing and percent change.
This helps you assess the solver interfaces based on performance.
The solver output results are used for further design verification and validation. The accuracy of the results as
processed, interpreted, and visualized by a post-processor is key. HyperView is used to post-process most of the solver(s) results. Use the Result tab to ensure that HyperView does not deprecate any result information after post-processing.
Uninstall HyperWorks is a tool to launch the HyperWorks uninstallation program. This program contains two options that allow you to either remove the originally installed
files, or remove all the files that resides in the installation directory.
HyperWorks Verification and Validation Harness (HVVH) is a tool that can be used to verify and validate HyperWorks products. End users can use this tool to quickly evaluate the software quality, performance, reliability,
scalability, and robustness, and to gain more confidence in HyperWorks products.
If this option is activated, it replaces all HyperWorks paths with the selected HyperWorks version and generates a new
copy(copies) of the .cmf file(s).
Config file
Activate this option to load a config file.
Ref Version
Select the HyperWorks version number of
your reference file from the drop-down menu.
Model (Solver Deck/HM File)
Deactivate this check box if there are no models to load. Or,
activate the check box to load a solver deck model or HyperMesh file.
Tip:
Click in the cell for each file type to
activate it. Once the cell is active, click to
display the file browser and load only selected files. You can also
add multiple files.
Click
to delete a selected file from the list.
Note: Only one file
is supported at an instance.
Add or delete any scripts/cmf files.
Tip:
Click
below the list box to select a folder that contains multiple
script files (Tcl/Tcb) or cmf files. You can select the top
level folder and load all files of selected file type.
Click to
display the file browser and load a single file. You can also add
multiple files.
Click to delete a selected file from
the list.
Select an output directory.
Click Run.
All selected scripts/cmf files are run in the (solver deck
model/HyperMesh model) batch mode.
If no
models are selected, then the scripts/cmf files are run batch mode. In this
case, the model should be read through scripts/cmf files.
HyperMesh(hm) and solver deck files are saved to the
output directory. Click Status to browse to the
output directory.
Tip:
The message log file displays
the current status of processes in progress. Click
Status/Diff to display the respective
report. The message log file is a text file and is saved to your
output directory.
Click Html
Report to generate an HTML report of your
session information for any number of files run through the
process.
You can set the environmental variables in the config file.
If ModelSetup is 0: Execute hmbatch.exe.
If ModelSetup is 1: Execute hmopengl.exe.
If ModelSetupConfig is 0: Reads the config file but doesn't replace
the paths (only reads the ModelSetup variable).
If ModelSetupConfig is 1: Reads the config file and replaces all
paths in the CMF files.