mapping:solid to skin
Last update: 31.07.2026Version: 0.0.0
Description
Maps a field defined on solid elements to a field defined on skin elements. Three cases are possible, based on the solid field data location; (i) Elemental: The values associated with the solid elements are copied according to those underlying the skin, (ii) Nodal: The solid field is rescoped with respect to the nodes of the skin mesh, (iii) ElementalNodal: The values are copied from the solid mesh to the skin mesh for each element face and the nodes associated with it.
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 | field | Required | field, fields_container |
| 1 | mesh | Required | abstract_meshed_region |
| 2 | solid_mesh | abstract_meshed_region |
field (Pin 0)
- Required: Yes
- Expected type(s):
field,fields_container
field or fields container with only one field is expected
mesh (Pin 1)
- Required: Yes
- Expected type(s):
abstract_meshed_region
skin mesh region expected
solid_mesh (Pin 2)
- Required: No
- Expected type(s):
abstract_meshed_region
Solid mesh support (optional).
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 | field | field |
field (Pin 0)
- Expected type(s):
field
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.
num_threads
- Expected type(s):
int32 - Default value: 0
Number of threads to use to run in parallel
run_in_parallel
- Expected type(s):
bool - Default value: true
Loops are allowed to run in parallel if the value of this config is set to true.
Scripting
This operator can be accessed through scripting interfaces using these identifiers.
Category: mapping
Plugin: core
Scripting name: solid_to_skin
Full name: mapping.solid_to_skin
Internal name: solid_to_skin
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("solid_to_skin"); // operator instantiation
op.connect(0, my_field);
op.connect(1, my_mesh);
op.connect(2, my_solid_mesh);
ansys::dpf::Field my_field = op.getOutput<ansys::dpf::Field>(0);
CPython
import ansys.dpf.core as dpf
op = dpf.operators.mapping.solid_to_skin() # operator instantiation
op.inputs.field.connect(my_field)
op.inputs.mesh.connect(my_mesh)
op.inputs.solid_mesh.connect(my_solid_mesh)
my_field = op.outputs.field()
IPython
import mech_dpf
import Ans.DataProcessing as dpf
op = dpf.operators.mapping.solid_to_skin() # operator instantiation
op.inputs.field.Connect(my_field)
op.inputs.mesh.Connect(my_mesh)
op.inputs.solid_mesh.Connect(my_solid_mesh)
my_field = op.outputs.field.GetData()
Changelog
- Version 0.0.0: Initial release.