Home
Manage Files and Data
Create, open, import, and save models.
Import Files
Import various file types into the selected client.
Solver Deck Import
Import FE models for supported solver interfaces.
Entity Import Behavior
Overview of how entities are imported.

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.
  - Solver Deck Import
    Import FE models for supported solver interfaces.
    - Entity Import Behavior
      Overview of how entities are imported.
    - Import Error Messages
      When an external input translator is used to import data, the application creates a file for messages in the directory in which the program was started.
    - By HM Comment
      An overview of how solver interfaces use the Create components by HyperMesh comments import option.
    - By Property Hierarchy
    - By Component Hierarchy
    - Duplicate Entity IDs
      IDs that are duplicated within element and property groups for the LS-DYNA user profile are supported in the application.
  - 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

Entity Import Behavior

Overview of how entities are imported.

Assemblies

Import assembly comment cards (HMASSEM, HMASSEM_IDS) that may exist in the import file and create assemblies per the data in the comment cards.
Optional additional imports: Components, Elements, Nodes, Connectors

Components

Import component comment cards (HMNAME COMP, HWCOLOR COMP, HMMOVE, HMDPRP) that may exist in the import file and create component collectors per the data in the comments cards.
Optional additional imports: Elements, Nodes and Connectors. If both nodes and elements are not imported, then components are imported and created but will contain no elements, that is, empty components. Similar for Connectors.

Load Collector

Import load collector comment cards (HMNAME LOADCOL, HWCOLOR LOADCOL) that may exist in the import file and create load collectors per the data in the comment cards.
Optional additional imports: Loads. If loads are not imported then load collectors are imported and created but will contain no loads (that is, empty load collectors)

System Collector

Import system collector cards (HMNAME SYSTCOL, HWCOLOR SYSTCOL) that may exist in the import file and create system collectors per the data in the comment cards.
Optional additional imports: Systems. If systems are not imported then system collectors are imported and created but will contain no systems (empty system collectors).

Vector Collector

Import vector collector cards (HMNAME VECTORCOLS, HWCOLOR VECTORCOLS ) that may exist in the import file and create vector collectors per the data in the comments cards.
Optional additional imports: Vectors. If vectors are not imported then vector collectors are imported and created but will contain no vectors (empty vector collectors).

Beam Section Collector

Import beam section collector cards (HMNAME BEAMSECTCOLS) that may exist in the import file and create beam section collectors per the data in the comment cards.
Optional additional imports: BeamSections. If beam sections are not imported then beam section collectors are imported and created but will contain no beam sections (empty beam section collectors).

MultiBody

Import multibody comment cards that may exist in the import file and create multibody collectors per the data in the comment cards.
Optional additional imports: Ellipsoids, MBJoints, MBPlanes. If elipsoids, MBJoints, MBPlanes are not imported, then Multibody collectors are imported and created but will contain no ellipsoids, MBJoints, MBPlanes (empty multibody collectors).

LoadStep

Import solver load step card definitions and load step comment cards (HMNAME LOADSTEP) that may exist in the import file and create load step entities per the solver and comment cards data.

Output Block

Import solver output block card definitions and output block comment cards that may exist in the import file and create output block entities per the solver and comment cards data.

Control Card

Import solver control card definitions that may exist in the import file and create card entities per the solver cards data.

Property

Import solver property card definitions and property comment cards (HMNAME PROP, HWCOLOR PROP) that may exist in the import file and create property entities per the solver and comment cards data.

Materials

Import solver material card definitions and material comments cards (HMNAME MAT, HWCOLOR MAT) that may exist in the import file and create material entities per the solver and comment cards data.

Sets

Import solver set card definitions and set comment cards (HMSET) that may exist in the import file and create set entities per the solver and comment cards data.

Blocks

Import solver block card definitions and block comment cards that may exist in the import file and create block entities per the solver and comment cards data.

Tags

Import solver tag card definitions and tag comment cards (HMTAG) that may exist in the import file and create tag entities per the solver and comment cards data.

Titles

Import solver title card definitions and title comment cards that may exist in the import file and create title entities per the solver and comment cards data.

Plots

Import solver plot card definitions and plot comment cards that may exist in the import file and create plot entities per the solver and comment cards data.
Optional additional imports: Curves

Contact Surface

Import solver contract surface card definitions and contact surface comment cards that may exist in the import file and create contact surface entities per the solver and comment cards data.
Optional additional imports: Nodes, Elements

Group

Import solver group card definitions and group comment cards (Domain) that may exist in the import file and create contact surface entities per the solver and comment cards data.
Optional additional imports: Nodes, Elements

Sensor

Import solver sensor card definitions and sensor comment cards that may exist in the import file and create sensor entities per the solver and comment cards data.

Control Volume

Import solver control volume card definitions and control volume comment cards that may exist in the import file and create control volume entities per the solver and comment cards data.

Node

Import solver node card definitions that may exist in the import file and create node entities per the solver cards data.

Element

Import solver element card definitions that may exist in the import file and create the appropriate element config/type entities per the solver cards data.
Required: Nodes
Optional additional imports: Assemblies, Components. If components are not imported then all elements will be organized into an "Auto" component.

Connector

Import master connector file xml data that may exist in the import file and create connector entities per the connector xml data.
Required: Nodes, Elements, Components
Optional additional imports: Assemblies

Load

Import solver load card definitions that may exist in the import file and create the appropriate load config/type entities per the solver cards data.
Required: Nodes (Forces, Moments, Temperatures)
Optional additional imports: Load Collectors. If load collectors are not imported then all loads will be organized into an "Auto" load collector

Equation

Import solver equation card definitions that may exist in the import file and create the appropriate equation entities per the solver cards.
Required: Nodes
Optional additional imports: Load Collectors. If load collectors are not imported then all loads will be organized into an "Auto" load collector

System

Import solver system card definitions that may exist in the import file and create system entities per the solver cards.
Required: Nodes (For Node Dependent Systems)
Optional additional imports: System Collectors. If system collectors are not imported then all systems will be organized into an "Auto" system collector.

Vector

Import solver vector card definitions that may exist in the import file and create vector entities per the solver cards data.
Required: Nodes (For Node Dependent Systems)
Optional additional imports: Vector Collectors. If vector collectors are not imported, then all vectors will be organized into an "Auto" vector collector.

BeamSections

Import beam section comment cards (HMNAME BEAMSECTS) that may exist in the import file and create beam section entities per the comment cards data.
Optional additional imports: Beam Section Collectors. If beam section collectors are not imported then all beam sections will be organized into an "Auto" beam section collector.

Curve

Import solver curve card definitions and curve comment cards (HMNAME CURVES, HMCOLOR CURVES, HMCURVE) that may exist in the import file and create HyperMesh curve entities per the solver and comment cards data.
Optional additional imports: Plots