IncompatibleMeshMapperByProjection Class Reference

Imports data from an incompatible mesh.

• The meshes can be incompatible (and deformed)
• Deformations may be of medium size, i.e. they must be detectable by a direct closest point projection onto the boundary (segments, edges or nodes - whatever feature is closest)
• Eroded elements can not be detected
• Non-matching boundary portions (due to cut-offs, holes, etc.) can not be detected
• Zones with erroneous detection or with larger distance than the maximum search distance are marked as eroded elements
• Coordinate deviations are the true deviation vectors. They are not necesarily parallel to the nodal normal vectors of the boundary. Hence, you can not use the normal deviations for simulation of deformed geometries.
• If nodal normal deviations are imported, interior nodes and boundary nodes with incorrect normal will be marked as eroded in the deviation objects.
• If number-sided node-to-segment projection is used, one can treat differently fine meshes better.
• Element data objects are imported by converting them to node objects, project theme and convert them back to element objects. This will introduce some degree of data smoothing.
• The choice of the maximum search distance may affect the performance significantly.
• The ability of simulating geometry deviations can be restored by enforcing the colinearity of the normal vectors of the reference mesh boundary and the deviation vectors