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.
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 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 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.
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.
When source data is not in the correct location and overlaps with the target model, the tools provided in the Field Realization dialog can be used to transform the source model to the target model's location with linear transformation,
rotation, or scale methods.
Joint entities define the kinematic relationship between two bodies (for Ball, Cylinder, Revolute, Slider joints) or three
bodies (for DoubleSlider joints).
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.
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.
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.
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.
Many essential utility tools using HyperWorks-Tcl have been developed over the years to support Aerospace customers. A few tools have been collected and upgraded to
be compatible with this release.
Perform nodal force balance mapping using OptiStruct to
ensure mapped target nodal forces and source nodal forces are in equilibrium.
Forces from a source model are mapped to new target model nodal forces. The total
load calculation on the source model and the new mapped model must be the same in order
to ensure forces are balanced.
Equilibrium mapping is performed using the linear
OptiStruct solver, therefore you must have the
OptiStruct installed with license on the same
installation directory as HyperWorks Desktop.
Open or import the target model. When importing, use ID Offset to preserve the
source model ID.
Create and define a field entity:
In the Model Browser, right-click and select Create > Field from the menu.
In the Entity Editor, define the nodal field
using the current model and forces data source, then select the loads to
map.
Realize the field:
In the Model Browser, right-click on the
field and select
Realize from the menu.
In the Field Realization dialog, define the
realization settings.
Set Interpolation to forcebalancing.
Click Apply.
New forces and moments are created and applied to the nodes of
the target mesh.