IncompatibleMeshMapper Class Reference
Last update: 16.07.2025imports data from an incompatible mesh More...
Public Types | |
| typedef boost::shared_ptr< CoorTransformationBase > | CoorTransformationBasePtr |
| a pointer to a rigid transformation algorithm object | |
| enum | Type { eCOMPATIBLE =0, eINCOMPATIBLE, eINCOMPATIBLE_CPP, eINCOMPATIBLE_RAY, eGRID, eP2VOLUME, eMORPHED_MESH } |
| an enum type defining the type of the derived class More... | |
Public Member Functions | |
| virtual string | generateScriptOfSettingsDefinition (string variable_ident) |
| IncompatibleMeshMapper () | |
| constructor | |
| virtual Type | mapperType () |
| virtual string | mapperTypeIdent () |
Public Attributes | |
| bool | deviations_along_boundary_normal |
| If true, then the algorithm will enforce colinearity of the normal vectors of the reference mesh boundary and the coordinate deviations. Default: true. | |
| number | maximum_search_distance |
| destructor More... | |
| bool | number_sided_projection |
| If true, then one uses number-sided node-to-segment detection, else only one-sided node-to-segment (reference-to-design) detection is used (default: false) | |
| bool | overwrite_existing |
| If true, then existing data objects will be replaced. More... | |
| string | transferred_data_ident_prefix |
| The prefix for re-transferred data. More... | |
| bool | use_half_space_test_for_associating_faces |
| If true, the algorithm tries to associate the correct boundary segments by assuming that the normal vectors of linked segments point into the same half space. default: true. | |
Detailed Description
imports data from an incompatible mesh
- The meshes can be incompatible (and deformed)
- Deformations should be rather small, i.e. they must be detectable by the 'Inside-Outside test' of Wang et al.
- Eroded elements can not be detected
- Non-matching boundary portions (due to cut-offs, holes, etc.) will be marked as eroded elements
- Zones with erroneous detection or with larger distance than the maximum search distance are marked as eroded elements
- Coordinate deviations will be projected onto the nodal normal vectors of the boundary. These are, therefore, not the true deviation vectors. They are suitable 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, but may lose the ability to simulate deformed geometries.
- 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 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
Member Enumeration Documentation
◆ Type
|
inherited |
an enum type defining the type of the derived class
Member Data Documentation
◆ maximum_search_distance
| number maximum_search_distance |
destructor
The maximum search distance (default: infinity)
◆ overwrite_existing
| bool overwrite_existing |
If true, then existing data objects will be replaced.
This option is used by transferData
◆ transferred_data_ident_prefix
| string transferred_data_ident_prefix |
The prefix for re-transferred data.
transferData is able to transfer the data to the new database, and to transfer the same data back This strategy allows to check the error that is obtained when transferring data between two meshes, since one can compare it with the original data on the same mesh. If the prefix is an empty string, then no data will be created. Else one choses the new quantity ident as "prefix[original_quantity_ident]"
