mapping:prepare mapping workflow
Last update: 31.07.2026Version: 0.0.0
Description
Generates a workflow that can map results from a support to another one.
Inputs
This table lists the input pins for this operator. Input pins define the data that the operator requires to perform its operation. Some inputs are required, while others are optional and provide additional configuration. Each parameter is detailed in the sections that follow the table.
| Pin number | Name | Status | Expected type(s) |
|---|---|---|---|
| 0 | input_support | Required | field, abstract_meshed_region |
| 1 | output_support | Required | field, abstract_meshed_region |
| 2 | filter_radius | Required | double |
| 3 | influence_box | double |
input_support (Pin 0)
- Required: Yes
- Expected type(s):
field,abstract_meshed_region
output_support (Pin 1)
- Required: Yes
- Expected type(s):
field,abstract_meshed_region
filter_radius (Pin 2)
- Required: Yes
- Expected type(s):
double
Radius size for the RBF filter
influence_box (Pin 3)
- Required: No
- Expected type(s):
double
Outputs
This table lists the output pins for this operator. Output pins provide the results of the operator's computation and can be connected to inputs of other operators or retrieved for further processing. Each output is detailed in the sections that follow the table.
| Pin number | Name | Expected type(s) |
|---|---|---|
| 0 | mapping_workflow | workflow |
mapping_workflow (Pin 0)
- Expected type(s):
workflow
Configurations
This operator supports configuration options that modify its behavior.
mutex
- Expected type(s):
bool - Default value: false
If this option is set to true, the shared memory is prevented from being simultaneously accessed by multiple threads.
Scripting
This operator can be accessed through scripting interfaces using these identifiers.
Category: mapping
Plugin: core
Scripting name: prepare_mapping_workflow
Full name: mapping.prepare_mapping_workflow
Internal name: prepare_mapping_workflow
License: None
Examples
These examples demonstrate how to use this operator in different programming environments. Each example shows how to instantiate the operator, connect the required inputs, and retrieve the output.
C++
#include "dpf_api.h"
ansys::dpf::Operator op("prepare_mapping_workflow"); // operator instantiation
op.connect(0, my_input_support);
op.connect(1, my_output_support);
op.connect(2, my_filter_radius);
op.connect(3, my_influence_box);
ansys::dpf::Workflow my_mapping_workflow = op.getOutput<ansys::dpf::Workflow>(0);
CPython
import ansys.dpf.core as dpf
op = dpf.operators.mapping.prepare_mapping_workflow() # operator instantiation
op.inputs.input_support.connect(my_input_support)
op.inputs.output_support.connect(my_output_support)
op.inputs.filter_radius.connect(my_filter_radius)
op.inputs.influence_box.connect(my_influence_box)
my_mapping_workflow = op.outputs.mapping_workflow()
IPython
import mech_dpf
import Ans.DataProcessing as dpf
op = dpf.operators.mapping.prepare_mapping_workflow() # operator instantiation
op.inputs.input_support.Connect(my_input_support)
op.inputs.output_support.Connect(my_output_support)
op.inputs.filter_radius.Connect(my_filter_radius)
op.inputs.influence_box.Connect(my_influence_box)
my_mapping_workflow = op.outputs.mapping_workflow.GetData()
Changelog
- Version 0.0.0: Initial release.