Home
Entities and Solver Interfaces
A solver interface is made up of a template and a FE-input reader.
Optimization Entities
Entities used to set up optimization problems.
Optimization Responses
Optimization response entities define and store model responses for optimization problems.

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.
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.
- Collectors and Collected Entities
  Collectors are named organizational containers for collected entities. Collected entities are nameless entities which must reside within one, and only one, collector. Collected entities are mutually exclusive to a collector.
- Named Entities
  Entities which are given a name but are not collected or organized into containers.
- Morphing Entities
  Entities used for morphing the shape of FE model.
- Optimization Entities
  Entities used to set up optimization problems.
  - Design Variables
    Design variable entities define and store design variables for optimization problems.
  - Design Variable Links
    Design variable link entities define links between design variables for optimization problems.
  - Design Variable Property Relationships
    Design variable property relationship entities define relationships between design variables and properties for optimization problems.
  - Discrete Design Variables
    Discrete design variable entities define and store discrete design variables for optimization problems.
  - Optimization Responses
    Optimization response entities define and store model responses for optimization problems.
  - Optimization Constraints
    Optimization constraint entities define and store constraints on model responses for optimization problems.
  - Optimization Equations
    Optimization equation entities define and store equations for optimization problems.
  - Optimization Table Entries
    Optimization table entry entities define and store table data for optimization problems.
  - Objectives
    Objective entities define and store an objective for an optimization problem.
  - Objective References
    Objective reference entities define and store objective references for an optimization problem.
  - Optimization Constraint Screenings
    Optimization constraint screening entities define and store constraint screening data for optimization problems.
  - Optimization Controls
    Optimization control entities define and store controls for optimization problem run.
- Control Cards
  Control card entities create solver control cards such as results file I/O options, CPU and memory limits, and others.
- Undefined Entities
  Undefined entities are entities that will not be written to the solver deck.
- Solver Encryption Entities
  The encryption of solver entities is used to translate entity data into an undisclosed language.
- Element Property and Material Assignment Rules
  Element property and material assignment rules are based on the current user profile (solver interface).
- Supported Cards
  Supported cards organized by solver.
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

Optimization Responses

Optimization response entities define and store model responses for optimization problems.

Optimization responses do not have a display state in the modeling window.

Nastran Cards


Card	Description
DRESP1	Defines a set of structural responses that is used in the design either as constraints or as an objective. Note: Generic response
DRESP2	Defines equation responses that are used in the design, either as constraints or as an objective. Note: Function response

OptiStruct Cards


Card	Description
DRESP1	A response or a set of responses that are the result of a design analysis iteration. These responses can be used as a design objective or as design constraints. Note: Bulk Data Entry
DRESP2	When a desired response is not directly available from OptiStruct, it may be calculated using DRESP2. This response can be a functional combination of any set of responses resulting from the design analysis iteration. Responses defined in this manner can be used as design objectives or constraints. The DRESP2 card identifies the equation to use for the response relationship and the input values to evaluate the response function. Note: Bulk Data Entry
DRESP3	When a desired response is not available from OptiStruct, either directly or via equations, it may be calculated through external user-supplied functions implemented in shared/dynamic libraries or external files. The DRESP3 card identifies the external function to be called and defines the parameters to be transferred to that function. Note: Bulk Data Entry
DSYSID	Defines responses and their target values for a system identification problem. Note: Bulk Data Entry
MODEWEIGHT	Defines a multiplier for computed eigenvalues that are to be used in the calculation of the "weighted reciprocal eigenvalue" and "combined compliance index" optimization responses. Note: Subcase Information Entry
PSD STRAIN
PSD STRESS
RMS STRAIN
RMS STRESS
WEIGHT	Defines a multiplier for computed eigenvalues that are to be used in the calculation of the "weighted reciprocal eigenvalue" and "combined compliance index" optimization responses. Note: Subcase Information Entry

Radioss Cards


Card	Description
DRESSP1	Defines a response (mass, displacement, stress, velocity, and so on) or a set of responses.
DRESP2	Design Response via Equations for Design Optimization.