Date Map/Table
Data map with element set (ply shapes), material orientation angles
(orient1 , orinet2 , draping corrections) thickness corrections,
reference direction and normal information for each ply is
preserved/mapped in the table entity, therefore each ply has a table
associated with it. Nodes and elements are not created in the database
from FiberSim triangulation data to
define ply shapes. Instead, it preserves this information in a table so
that when these plies are mapped (realized) on actual good mesh,
HyperMesh uses this triangular
information to define the ply boundary and extract the actual
elements.
Laminates
One laminate per HDF5 component with all the ply sequence preserved as
per layer_id value.
Materials
Material names and their mechanical properties are read and mapped to
solver cards automatically depending on the user profile loaded while
importing the model. Currently mechanical properties such as E1, E2, E3,
G12, G13, G23, Alpha1, Alpha2 and Alpha_ref temperature are mapped to
solver material attributes.
Rosette/Systems
All the system definitions available in the HDF5 file will be imported
into one system collector. Currently HyperMesh does not preserve the ply and system relation.