4.17. Shell to Solid-generation

This option enables the generation of a solid mesh using a provided shell mesh.

4.17.1. Main Mapping Command

ENVYO = SHELL-SOLID(GENERATION)

4.17.2. Input and Output Meshes

SourceFile = STRING Define the name and, if needed, the path of the source file (usually a *.dynain file).
MappingResult = STRINGDefine the result filename. The mapping result is written to this newly-generated file.
TransformedMeshFile = STRING Specify the filename for transformed mesh output. This option is intended solely for postprocessing of the transformation. For additional details, refer to the Transformation Options section below.

4.17.3. Target Part IDs and Source Part IDs

For this option, the target mesh part ID declarations are considered as mapping result part ID information. It is therefore expected to have the following:

 NumTargetPIDs=1 
 TargetPID#1=INT
NumTargetPids = INT

Define the number of parts in the target mesh that are considered within the mapping. This option should be followed by TargetPid#i definitions.

TargetPid#i = INTDefine as many part IDs as specified in NumTargetPids. These parts are considered for the mapping.
NumSourcePIDs = INT

Define the number of parts in the source mesh that are considered within the mapping. This option should be followed by SourcePID#i definitions.

SourcePID#i = INTDefine as many part IDs as specified in NumSourcePIDs. These parts are considered for the mapping.

Note:  The options above specifically narrow down the scope of the mapping procedure to defined-part IDs. Other parts are ignored on both the source and target meshes.


4.17.4. Transformation Options

TRANSFORMATION = YES

NO

Enable/disable the transformation option.

WriteTransformedMesh = YES

NO

Flag to enable output of the transformed mesh used for mapping. This enables success verification for the transformation. If set to YES, a TransformedMeshFile must be specified (see above).

A custom sequence of user-defined transformations can be applied. These transformations are executed in the order in which they are specified and multiple transformations may be defined:

RotateSRC = DOUBLE;X

DOUBLE;Y

DOUBLE;Z

DOUBLE; DOUBLE DOUBLE DOUBLE

The source mesh is rotated by a specified angle (first value, in degrees) around a defined axis. Predefined axes include X, Y, and Z. Alternatively, a custom axis can be specified by providing three space-separated floating-point values following a semicolon (; x y z).
MoveSRC = DOUBLE DOUBLE DOUBLEThe source mesh is moved along the user-defined vector (x y z).
ScaleSRC = DOUBLEThe source mesh is scaled around the origin using the defined scale factor.

In addition to the transformation options, you can convert the unit systems:

ChangeUnitSystem = YES

NO

Activate/deactive unit system conversion.

SourceUnitSystem = kg - m - s

ton - mm - s

kg - mm - ms

g - mm - ms

lb - in - s

If unit system conversion is activated, provide information about the source unit system.

TargetUnitSystem = kg - m - s

ton - mm - s

kg - mm - ms

g - mm - ms

lb - in - s

If unit system conversion is activated, provide information about the target unit system.

4.17.5. Mapping Options

ALGORITHM = ClosestPoint The only available option is ClosestPoint. Values are mapped to the nearest node, integration point, or element center.

Search_Radius = SrcEleLen

TarEleLen

DOUBLE

Specifies the search radius for the mapping algorithm. By default, SrcEleLen is used, which sets the radius to the average element size of the source mesh. Alternatively, you can use TarEleLen to apply the average element size of the target mesh, or provide a positive DOUBLE value to define a custom radius.
Scale_SearchRadius = DOUBLE

Coefficient to scale search radius. The default value is 1.0.

ETYP = INT

1 - Reduced integrated solid elements.

2 - Fully integrated solid elements.

MapStress = YES

NO

Activate/deactivate stress mapping.

MapStrain = YES

NO

Activate/deactivate strain mapping.

MapThickness = YES

NO

Activate the generation of shell elements on top and bottom surfaces of the generated solid mesh.

Thck_Avg_Opt = Ele Avg

Nodal Avg

Thickness averaging option. When using *ELEMENT SHELL THICKNESS, nodes may hold different thickness information, depending on the element to which they belong. This is especially critical for components with ribs.

With the default setting (Ele Avg), the Envyo application calculates through-thickness integration points using the nodal thicknesses stored on the element nodes by interpolating the resulting thicknesses at the in-plane integration points via shape functions, allowing for the correct calculation of the local through-thickness integration points.

By choosing the Nodal Avg option, the application first collects all thicknesses stored on one node from its attached elements and averages these thicknesses. Interpolation to the in-plane integration points using shape functions is then performed.

LargeFile = YES

NO

Activate/deactivate large file handling to reduce memory usage.
StartNodeID = INT Starting node ID for the generated solid element nodes.
StartEleID = INT Starting element ID for the generated solid elements.

NumSolidLayers = INT

fromInitialStress

The number of solid layers created during mesh generation. If NumSolidLayers=fromInitialStress, the number of generated solid layers is equal to the number of through-thickness IPs for the source mesh shell elements.
SourceMaterialModel = INT

Number of the material model used for the generation of the *.dynain file. Only *MAT_USER_DEFINED_MATERIAL_MODELS (*MAT 41) is supported.

VisualizeThickness = YES

NO

When enabled, generated solid element thicknesses are stored as the last history variable for visualization purposes.
SORT = BUCKET Using bucket sort is strongly recommended, as it provides a substantial performance improvement for the search algorithm.
REPEAT = YESEnable this option to ensure that all elements and integration points receive mapped data. When there is a significant difference in element sizes between the source and target meshes, the default bucket refinement may be insufficient to cover all points, sometimes by design. In such cases, this flag must be set to guarantee complete data coverage.