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.
This entity defines additional material features coupled to the referenced material, like: Failure, Permeability,
Porosity, Thermal, Fatigue, Cohesive, Inelasticity, and so on.
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.
This task is an example of thermal analysis mapping using heat transfer coefficients and bulk temperatures. This mapping
option is available for the OptiStruct profile. CSV files or result logs from AcuSolve can also be used as a source.
This method is useful when transferring data from existing solver decks (.bdf, .fem, .inp, and so forth) to new meshed models. Old mesh shape functions are used with this method.
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).
Perturbation entities provide a means of defining deviations from the designed structure, such as buckling imperfections.
Define the stochastic variation in the material models with the STOCHASTIC keyword option.
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.
State Equations are used to describe the thermodynamic equation relating material state variables under a given set
of physical conditions, such as pressure, volume, temperature, or internal energy. State Equations are useful in describing
the properties of fluids, mixtures of fluids, and so on.
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.
Browsers supply a great deal of view-related functionality 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.
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.
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.
This task is an example of thermal analysis mapping using heat transfer coefficients and bulk temperatures. This mapping
option is available for the OptiStruct profile. CSV files or result logs from AcuSolve can also be used as a source.
This task is an example of thermal analysis mapping using heat transfer coefficients
and bulk temperatures. This mapping option is available for the OptiStruct profile. CSV files or result logs
from AcuSolve can also be used as a source.
Data in a .csv file can be based on a local coordinate system.
The format of the .csv file is x, y, z, value1, value2, and so
forth. The x, y, z data can be in a global or local system , including cylindrical.
In the Model Browser, right-click and select Create > Field from the menu.
In the Entity Editor, edit the field's corresponding
attributes.
In the Model Browser, right-click on the field
entity and select Realize from the menu.
In the Field Realization dialog, define the realization
settings:
Select the target mesh in the Entity field.
From the Field type drop-down menu, select
convection.
From the Interpolation drop-down menu, select the appropriate
interpolation method.
Set the Normal distance and Tolerance values as appropriate.
Select the sub-case and simulation from which the heat transfer
coefficients and bulk temperatures are to be mapped.
When you are ready, click Apply.
Data is mapped to the selected structural mesh. The following solver
entries are created for the OptiStruct profile:
Group - PCONV
Heat transfer coefficient calculated during the mapping process,
stored in card: attribute:H1.
CHBDYE
Surface elements over target or base elements.
CONV
PCONV ID and arbitrary node number (TA1) created for bulk
temperature.
SPC
An arbitrary node is created and the SPC (without any DOF) is
attached to this node. Used to store the bulk temperature calculated
during the mapping process.