Skip to main content

mapping:prepare mechanical native mapping

Version: 0.0.0

Description

Prepare mapping of source data from source mesh to target mesh by operating the source_mesh/target_mesh weights computation. This operator needs to be used with the apply mechanical native mapping associated one. At least one of the optional DataTree inputs need to be set, in order to chose the mapping algorithm and set the mapping options.

Inputs

InputNameExpected type(s)Description
Pin 0
Required
source_meshabstract_meshed_regionSource mesh
Pin 1
Required
target_meshabstract_meshed_region, fieldTarget mesh. Can be a meshed region or a node coordinates field depending on the algorithm that is used. Refer to the dedicated algorithm operator documentation.
Pin 3target_mesh_scopingscopingTarget mesh scoping. If used, ensure to give only the elements where results are expected into source mesh input to have optimized computation.
Pin 8html_report_pathstringPath for html report (for example 'my_disk/my_report.html'). If set, an html report will be generated and exported to the html file. If not set, nothing will be generated.
Pin 30shape_function_volumes_mappingdata_treeMapping options as DataTree object with 'mapping_options' subtree for mapping with shape function algorithm. Another 'data_definition' subtree needs to be contained, with at least 'dimensionality' int and 'location' string attributes. The other 'data_definition' and 'mapping_options' attributes can be found looking at the corresponding operator definition. The available mapping_options are: scale (int), edge_tolerance (double), conservative (bool), ignore_outside_nodes (bool). Corresponding operator definition can be checked to know the default values of the mapping options.
Pin 31shape_function_surfaces_mappingdata_treeMapping options as DataTree object with 'mapping_options' subtree for mapping with shape function algorithm. Another 'data_definition' subtree needs to be contained, with at least 'dimensionality' int and 'location' string attributes. The other 'data_definition' and 'mapping_options' attributes can be found looking at the corresponding operator definition. The available mapping_options are: scale (int), edge_tolerance (double), conservative (bool), ignore_outside_nodes (bool), key (string), normal_distance_check (bool), normal_tolerance (double), pinball_controll (bool), pinball_key (string), exclude_elements_outside_pinball (bool), pinball_value (double). Corresponding operator definition can be checked to know the default values of the mapping options.
Pin 32point_cloud_mappingdata_treeMapping options as DataTree object with 'mapping_options' subtree for mapping with point cloud algorithm. Another 'data_definition' subtree needs to be contained, with at least 'dimensionality' int and 'location' string attributes. The other 'data_definition' and 'mapping_options' attributes can be found looking at the corresponding operator definition. The available mapping_options are: weighting_type (string), outside_option (string), num_outside_nodes (int), max_outside_distance (double), search_limit (int), bouding_box_range (double), geometry_type (string),shell_thickness_factor (double). Corresponding operator definition can be checked to know the default values of the mapping options.
Pin 33kriging_mappingdata_treeMapping options as DataTree object with 'mapping_options' subtree for mapping with kriging algorithm. Another 'data_definition' subtree needs to be contained, with at least 'dimensionality' int and 'location' string attributes. The other 'data_definition' and 'mapping_options' attributes can be found looking at the corresponding operator definition. The available mapping_options are: samples_limit (int), correlation_function_type (string), polynomial_type (string), outside_distance_checking (bool), bouding_box_tolerance (double), adaptive_tolerance_percent (double), geometry_type (string). Corresponding operator definition can be checked to know the default values of the mapping options.
Pin 100is_element_centroidal_data_mappingboolDefault is 'false'. Set to 'true' if the source elemental data is representing as element centroidal nodal data
Pin 101projection_optionsdata_treeDefault is empty. This data tree contains 2D projection options for mapping 2D to 3D
Pin 102dynamic_coordinate_systemdata_treeDefault is empty. This data tree contains the dynamic coordinate system for performing rigid body transformation on the source mesh
Pin 103source_dimensionstringDefault is empty string. The string contains either "2D" or "3D" which specifies the source dimension
Pin 104wb_external_data_infodata_treeDefault is empty. This data tree contains the Rigid & Analytical transformations specified in the workbench external data system
Pin 105target_dimensionstringDefault is empty string. The string contains either "2D" or "3D" which specifies the target dimension

Outputs

OutputNameExpected type(s)Description
Pin 0source_meshabstract_meshed_regionSource mesh
Pin 1source_mesh_idint32Source mesh id
Pin 2target_meshabstract_meshed_regionTarget mesh
Pin 3target_mesh_idint32Target mesh id
Pin 4mapping_manager_data
Pin 6target_scopingscopingTarget scoping
Pin 7prepare_outputA Map containing the outputs of the mapping as a key value pair

Configurations

NameExpected type(s)Default valueDescription
mutexboolfalseIf this option is set to true, the shared memory is prevented from being simultaneously accessed by multiple threads.

Scripting

Category: mapping

Plugin: N/A

Scripting name: prepare_mechanical_native_mapping

Full name: mapping.prepare_mechanical_native_mapping

Internal name: mechanical_native_mapping::prepare

License: any_dpf_supported_increments

Changelog

  • Version 0.0.0: Initial release.