2021.1
A solver interface is made up of a template and a FE-input reader.
Entities which are given a name but are not collected or organized into containers.
Mechanism entities are the root of the hierarchy in the Mechanism Browser.
View new features for HyperWorks 2021.1.
Learn the basics and discover the workspace.
Discover HyperWorks functionality with interactive tutorials.
Create, open, import, and save models.
Set up sessions and create report templates.
Solver interfaces supported in HyperWorks.
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.
Accelerometer entities measure acceleration in the simulation.
Ale Fsi Projection entities provide a coupling method for simulating the interaction between a Lagrangian material set (structure) and ALE material set (fluid).
Ale Reference System Curve entities defines a motion and/or a deformation prescribed for a geometric entity, where a geometric entity may be any part, part set, node set, or segment set.
Ale Reference System Group entities used to associate a geometric entity to a reference system type.
Ale Reference System Node entities defines a group of nodes that control the motion of an ALE mesh.
Ale Reference System Switch entities allows for the time-dependent switches between different types of reference systems, that is, switching to multiple PRTYPEs at different times during the simulation.
Ale Smoothing entities constraint keeps an ALE secondary node at its initial parametric location along a line between two other ALE nodes.
Ale Tank Test keyword provides curve through an engineering approximation when control volume airbags only require two engineering curves to define gas inflator and those two curves can be experimentally measured but the ALE inflator needs one additional state variable - the inlet gas velocity which is impractical to obtain.
Attachments facilitate the ease of joining subsystems.
Block entities are enclosed volumes represented by a "box" or block.
Body entities define a kinematic assembly made of FE parts or nodes.
Box entities are enclosed volumes, which are represented by a box.
Constrained extra node entities define and store the keywords *CONSTRAINED_EXTRA_NODES_NODE and *CONSTRAINED_EXTRA _NODES_SET.
Constrained rigid bodies entities define and store the keyword *CONSTRAINED_RIGID_BODIES.
Constraint entities define kinematical constraints on a body at a specified node or point location.
Contact surface entities define and store contact definitions typically used in contact analysis.
Control volume entities define and store control volumes typically used in safety analysis.
Cross section entities store cross section definitions used in a crash analysis.
Curve entities define and store xy data and are associated with a plot entity.
In LS-DYNA, damping entities define damping applied on the parts and nodes in case of *DAMPING_GLOBAL. In Radioss, damping entities used to set Rayleigh mass and stiffness damping coefficients are applied to a set of nodes used to stabilize the results.
Dummy entities are defined by bodies representing the different kinematic assemblies of the dummy.
Element clusters are used to describe an assembly of elements for post-processing and failure control.
Failures describe material failure criteria to be coupled to material models.
Feature entities track and manage certain geometric features.
Field entities store spatially varying values, which can later be realized (mapped) to the element and node data of a new target mesh.
Frictions entities define friction coefficients between parts.
Group entities define and store interfaces and rigid walls typically used in contact analysis.
Hourglass entities define hourglass and bulk viscosity properties which are referenced via HGID in the *PART command.
Interface Component entities create an interface in interface file for use in subsequent linking calculations.
Interface Linking Discrete keyword link node(s) to an interface in an existing interface file.
Joint entities define the kinematic relationship between two bodies (for Ball, Cylinder, Revolute, Slider joints) or three bodies (for DoubleSlider joints).
Laminate entities define the list of stacked plies which make up a laminated structure.
Load step entities define and store load cases for a given analysis.
Material entities define and store material definitions for a model.
Output block entities define and store solver output requests.
Parameter entities parameterize FE entity and geometric entity attributes.
Ply entities define composite lamina.
Plot entities associate and organize curve entities within a xy plot window.
Position entities allow you to apply a Transformation sequence on set of nodes or SolverSubmodels.
Pretensioner entities define pretensioners.
Property entities define and store 1D, 2D, and 3D property definitions for a model.
Reference Geometries define the reference shape of foam or airbag components.
Region entities store information used to facilitate and automate modeling practices and processes. It enables a selection which can be common across design changes or other models, provided region data is the same.
Retractor entities define retractors.
Rigid bodies entities define and store the keywords *RBODY and *RBADD.
Rigid wall entities provide a method for treating a contact between a rigid surface and nodal points of a deformable body. In the LS-DYNA and Radioss user profiles, rigid walls can be created in the Model and Solver browsers.
Sensor entities define and store sensors typically used in safety analysis.
Set entities define and store lists of entity IDs for entities, sets of sets, or lists of set IDs.
Slip ring entities define sliprings.
Solver masses are used to model lumped mass finite element mesh.
Table entities collect data points.
Tag entities tag a piece of information, called the body, onto a node, element, line, surface, point, or solid within the model.
Termination entities provides an alternative way to stop the calculation before the termination time is reached.
Title entities attach a title box with text to the modeling window, or to a node, element, load, or system.
Transformation entities define solver transformations, and are used to define a transformation sequence in a Position entity, to be applied on a set of nodes or on a SolverSubmodel.
Entities used for morphing the shape of FE model.
Entities used to set up optimization problems.
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.
Create, organize and manage parts and subsystems.
Create, edit, and cleanup geometry.
Different types of mesh you can create in HyperWorks.
Create and edit 0D/1D entities and edit 2D elements.
Rapidly change the shape of the FE mesh without severely sacrificing the mesh quality.
Create connections between parts of your model.
HyperMesh composites modelings.
Tools used for crash and safety analysis.
Airbag solutions offer airbag folder utilities and exports a resulting airbag in a Radioss deck.
Workflow to support topology optimization model build and setup.
Multi-disciplinary design exploration and optimization tools.
Essential utility tools developed using HyperWorks-Tcl.
Import an aeroelastic finite element model with Nastran Bulk Data format.
Framework to plug certification methods to assess margin of safety from the model and result information.
Streamline the creation of properties and 1D stiffener mesh using the info read from Marine CAD tools.
Create evaluation lines, evaluate them, and optimize the interfaces to eliminate squeak and rattle issues.
A Packaged Solution Offering (PSO) that provides a flexible and customizable platform for building and analyzing geomechanical models.
Panels contains pre-processing and post-processing tools.
HyperView is a complete environment to visualize, query, and process results data.
HyperGraph is a data analysis and plotting tool with interfaces to many CAE file formats.
MotionView is a general pre-processor for Multibody Dynamics.
MediaView plays video files, displays static images, tracks objects, and measures distances.
TextView math scripts reference vector data from HyperGraph windows to automate data processing and data summary.
TableView creates an Excel-like spreadsheet in HyperWorks.
Create and export Document and Presentation reports with one click and also define your own report structure.
View All Altair Simulation Help
