2020.1
A solver interface is made up of a template and a FE-input reader.
Entities used to set up optimization problems.
View new features for HyperMesh 2020.1.
Learn the basics and discover the workspace.
Discover HyperMesh functionality with interactive tutorials.
Solver interfaces supported in HyperMesh.
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.
Entities which are given a name but are not collected or organized into containers.
Entities used for morphing the shape of FE model.
Design variable entities define and store design variables for optimization problems.
Design variable link entities define links between design variables for optimization problems.
Design variable property relationship entities define relationships between design variables and properties for optimization problems.
Discrete design variable entities define and store discrete design variables for optimization problems.
Optimization response entities define and store model responses for optimization problems.
Optimization constraint entities define and store constraints on model responses for optimization problems.
Optimization equation entities define and store equations for optimization problems.
Optimization table entry entities define and store table data for optimization problems.
Objective entities define and store an objective for an optimization problem.
Objective reference entities define and store objective references for an optimization problem.
Optimization constraint screening entities define and store constraint screening data for optimization problems.
Optimization control entities define and store controls for optimization problem run.
Control card entities create solver control cards such as results file I/O options, CPU and memory limits, and others.
Undefined entities are entities that will not be written to the solver deck.
The encryption of solver entities is used to translate entity data into an undisclosed language.
Element property and material assignment rules are based on the current user profile (solver interface).
Supported cards organized by solver.
Support provided by the CAD readers and writers.
Browsers supply a great deal of view-related functionality in HyperMesh by listing the parts of a model in a tabular and/or tree-based format, and providing controls inside the table that allow you to alter the display of model parts.
Panels contains pre-processing and post-processing tools.
Create, edit, and cleanup geometry.
Learn about the different types of mesh you can create in HyperWorks.
Create connections between parts of your model.
Create, organize, and manage the CAE parts.
Perform automatic checks on CAD models, and identify potential issues with geometry that may slow down the meshing process using the Verification and Comparison tools.
Tools used for crash and safety analysis.
HyperMesh composites and tools.
Overview of how to build a finite element model.
Morph the shape of your finite element model.
Setup an Optimization in HyperMesh.
Convert finite element models to another solver format.
Study relationships between data vectors in results files.
Learn how to use post-processing functions.
View All Altair HyperWorks Help