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.
The native CAD model is imported into HyperMesh and exported using CAD readers in HyperMesh that are run in the background. The exported model is re-imported and overlaid. With superposed models using
advanced CAD-CAD comparison, any loss of geometric data is identified, along with any entity changes. A reference
report is also created.
The native CAD model is imported using CAD readers in HyperMesh that are run in the background, and exported in different HyperMesh versions over two sessions. Exported models are superposed and compared using advanced CAD-CAD comparison, and any
loss of geometric data is identified along with any entity changes. A reference report is also created.
The native CAD model is imported into HyperMesh along with a user-defined parameter and criteria files. The CAD model is batch meshed and the finite element
(FE) mesh created is compared with the CAD model using advanced CAD-FE comparison. A reference report is also created,
indicating any change in the meshed profile with respect to geometry.
The native CAD model is imported into HyperMesh along with a user-defined parameter and criteria files in two different HyperMesh versions. CAD models are batch meshed and FE meshes are superposed. Using advanced FE-FE comparison, any change in
mesh quality are identified and reported.
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.
The native CAD model is imported into HyperMesh along with a user-defined parameter and criteria files in two different HyperMesh versions. CAD models are batch meshed and FE meshes are superposed. Using advanced FE-FE comparison, any change in
mesh quality are identified and reported.
The native CAD model is imported into HyperMesh along
with a user-defined parameter and criteria files in two different HyperMesh versions. CAD models are batch meshed and FE meshes are
superposed. Using advanced FE-FE comparison, any change in mesh quality are identified and
reported.
Click the CAD tab then the FE-FE
tab.
Select the current and reference solver
version.
Enter a Tolerance value for use in the comparison.
Activate any of the check boxes to assist in loading files.
Option
Description
Same as Criteria
If there is more than one model file loaded in the input table,
there is no need to load the Criteria file in each row. If you activate
this check box, HVVH loads the first Criteria file in each row for all
selected input files
Same as Parameter
If there is more than one model file loaded in input table, there is
no need to load a Parameter file in each row. If you activate this check
box, HVVH loads the first Parameter file in each row for all selected
input files.
BM (Batch Mesher)
This check-box allows you to load a batch mesher session file and
executes the batch mesher.
Use the Input file(s) section to load a CAD model file(s), parameter file(s)
and criteria files(s).
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 add a
row to the table.
Click to
delete a row from the table.
Select an output directory.
The CAD models are converted into FE meshes via batch mode, using the criteria
and parameter files, in two HyperMesh sessions (also
in two different versions).
Click Compare.
The CAD > FE comparison report is generated for the HyperMesh FE meshed files across different versions of
HyperMesh.
Under the Current Mesh Status
heading, click Status to return the status of the
meshing operation on the CAD model using the current HyperMesh version. In case of failure, it will
indicate the same.
Under the Reference Mesh Status heading, click
Status to return the status of the meshing
operation on the CAD model using the reference HyperMesh version. In case of failure, it will
indicate the same.
Under the Report heading, click
Report to return a report that compares the FE
model generated using the current version of HyperMesh and the FE model
generated using the reference HyperMesh version.
The report is written to a text file.
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.