Home
Manage Files and Data
Create, open, import, and save models.
Import Files
Import various file types into the selected client.
CAD Import
Learn about the supported CAD readers and the options available for importing CAD geometry data.
CAD Metadata Naming
The metadata names generated by the CAD readers are composed of a general prefix followed by a metadata specific name. The prefix is specified using the @MetadataPrefix option in each _reader.ini file.

Welcome
What's New
View new features for Altair HyperWorks 2024.1.
Get Started
Learn the basics and discover the workspace.
Tutorials
Learn more about the Altair HyperWorks suite of products with interactive tutorials.
Startup Procedures and Customizations
Start and configure the applications.
Tool Finder
View a list of deprecated panels and their newer, equivalent workflows.
Manage Files and Data
Create, open, import, and save models.
- Supported File Types
  The following file types can be read, depending upon the active application.
- Create New Files
  Create a new file.
- Open Files
  Open a file.
- Import Files
  Import various file types into the selected client.
  - CAD Import
    Learn about the supported CAD readers and the options available for importing CAD geometry data.
    - Supported CAD Readers
      CAD readers supported by the application.
    - CAD Import Options
      CAD readers provide options for processing data during import.
    - CAD Import Message Files
      Each reader reads the CAD file and stores the geometry information. When a CAD file is read, a .msg file is created (or appended to) in the current working directory.
    - CAD Import Difficulties
      Learn about possible difficulties you may encounter during CAD import.
    - CAD Metadata Naming
      The metadata names generated by the CAD readers are composed of a general prefix followed by a metadata specific name. The prefix is specified using the @MetadataPrefix option in each _reader.ini file.
  - Solver Deck Import
    Import FE models for supported solver interfaces.
  - Connector Import
    Learn about importing connector files.
- Warning Messages When Loading Files
  When loading an .hm file, you may receive a warning message depending on the version and solver interface in which the file was last saved.
- Change Solver Interfaces
  Load a different solver interface in the application.
- Conversion Between Solver Formats
  Convert finite element models to another solver format.
- Load Files
  Load command files, scripts, solver template files, preferences, or the Metadata Table.
- Save Files
  Save all of the data in your current session.
- Export Files
  Export various file types from the selected client to another format.
- Include Files
  Most FEA solvers allow you to organize the input deck into separate files and provide a mechanism to include (or refer) these files in the main input deck.
- Import Templates
  Templates can be imported by means of the File > Import menu.
- Take a Screen Capture
  Record a video or take a snapshot of the screen.
- Convert Units
  Use the Units tool to convert a finite element model from its initial unit system to a new unit system.
Sessions and Report Templates
Set up sessions and create report templates.
Interface with External Products
Solver interfaces supported in HyperMesh.
Entities and Solver Interfaces
A solver interface is made up of a template and a FE-input reader.
Browsers
Browsers provide a structured view of model data, which you can use to review, modify, create, and manage the contents of a model. In addition to visualization, browsers offer features like search, filtering, and sorting, which enhance your ability to navigate and interact with the model data.
Sketching
Create and edit 2D parametric sketch geometry.
Topology
Create, edit, and cleanup geometry.
FE Geometry
FE geometry is topology on top of mesh, meaning CAD and mesh exist as a single entity. The purpose of FE geometry is to add vertices, edges, surfaces, and solids on FE models which have no CAD geometry.
Meshing and Elements
Explore the different types of mesh you can create in HyperMesh and create and edit 0D, 1D, 2D, and 3D elements.
Model Build and Assembly
Create, organize and manage parts and subsystems.
Composites
HyperMesh composites modeling.
Connectors
Create connections between parts of your model.
Morph
Rapidly change the shape of the FE mesh without severely sacrificing the mesh quality.
Skeleton Modeling
Create a reduced ordered model to facilitate optimization at the concept phase.
Design Space
Workflow to support topology optimization model build and setup.
Optimization
Setup an Optimization in HyperMesh.
Design Explorer
Multi-disciplinary design exploration and optimization tools.
Validate
Validate the model built before running solver analysis.
Analyze
Models require loads and boundary conditions in order to represent the various physics and/or physical equivalents to bench and in-use testing.
Axisymmetry
Reduce a full 3D model with axisymmetric surfaces while accounting for imperfections.
Concept Modeling
Tools and workflows that are dedicated to rapidly creating new parts for specific use cases, or amending existing parts. The current capabilities are focused on stiffening parts.
Crash and Safety
Tools used for crash and safety analysis.
Airbag
Use airbag folder utilities and export a resulting airbag in a Radioss deck.
Aerospace
Essential utility tools developed using HyperMesh-Tcl.
Aeroelasticity
Import an aeroelastic finite element model with Nastran Bulk Data format.
Certification
Framework to plug certification methods to assess margin of safety from the model and result information.
PhysicsAI
Use PhysicsAI to build fast predictive models from CAE data. PhysicsAI can be trained on data with any physics or remeshing and without design variables.
Results Data
Results data can be post-processed using both HyperMesh and HyperView.
Developer
The Developer ribbon contains tools for automation and customization.
Plot Data
HyperGraph is a data analysis and plotting tool with interfaces to many file formats.
Multibody Modeling
MotionView is a general pre-processor for Multibody Dynamics.
Media Files
MediaView plays video files, displays static images, tracks objects, and measures distances.
Tabulate Results
Use TableView to create an Excel-like spreadsheet.
Text Files
TextView math scripts reference vector data from HyperGraph windows to automate data processing and data summary.
Publishing and Reporting
Create, define, and export reports.

View All Altair HyperWorks Help

CAD Metadata Naming

The metadata names generated by the CAD readers are composed of a general prefix followed by a metadata specific name. The prefix is specified using the @MetadataPrefix option in each _reader.ini file.

The @MetadataPrefix option works as follows:

The string you specify is appended as a prefix to the metadata name generated by that reader. The prefix is used explicitly with the metadata name. No . (period) is automatically added if it is not specified by the option. For example:
- @MetadataPrefix = ".ALTAIR.HW"
- .ALTAIR.HW<metadata name>
- @MetadataPrefix = ".ALTAIR.HW."
- .ALTAIR.HW.<metadata name>
If the option is commented out, or the value is set to null "", no prefix is prepended and only the names of the metadata are used. For example:
- @MetadataPrefix = ""
- <metadata name>
There are some pre-defined strings that have specific meaning. These pre-defined strings are automatically substituted with specific data where applicable. These strings are as follows:
- <FORMAT> - the format of the CAD file (CATIA, STEP, NX, and so on)
- <VERSION> - the version of the CAD file. For CATIA, this is V4 or V5. For NX, this is any NX version (for example, NX 10.0, NX 11.0, and so on). No other format currently supports this option. In the case where there is no <VERSION> possible, an empty string is substituted.
All other strings are used verbatim. For example:
- @MetadataPrefix = "<MYSTRING>"
- <MYSTRING><metadata name>
By default, the prefix is empty string for all readers. To maintain consistency with metadata names used by previous versions, a value of ".ALTAIR.HW.<FORMAT>." is appropriate.

Additional Examples:

@MetadataPrefix = ".ALTAIR.HW.<FORMAT>."
.ALTAIR.HW.CATIA.<metadata name>

@MetadataPrefix = "/ALTAIR/HW/<FORMAT>/"
/ALTAIR/HW/CATIA/<metadata name>

@MetadataPrefix = "<FORMAT><VERSION>."
CATIAV5.<metadata name>

@MetadataPrefix = "<FORMAT>.<VERSION>."
CATIA.V5.<metadata name>