scoping:on mesh property
Last update: 31.07.2026Version: 0.0.0
Description
Provides a scoping on a given property name and a property number.
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 | requested_location | string |
|
| 1 | property_name | Required | string |
| 2 | property_id | vector<int32>, int32 |
|
| 5 | inclusive | int32 |
|
| 7 | mesh | Required | abstract_meshed_region |
requested_location (Pin 0)
- Required: No
- Expected type(s):
string
Nodal or Elemental location are expected
property_name (Pin 1)
- Required: Yes
- Expected type(s):
string
ex "apdl_element_type", "elprops", "mat", "eltype", "connectivity", "shell_elements", "solid_elements", "skin_elements", "beam_elements", "point_elements"...
property_id (Pin 2)
- Required: No
- Expected type(s):
vector<int32>,int32
inclusive (Pin 5)
- Required: No
- Expected type(s):
int32
Default is 1 (inclusive is true). Only used if 'shape_values' property is requested. If inclusive is set to 1 and 'elprops' property field is available, it will select all elements that are set on the corresponding property. If inclusive is set to 0 (exclusive) and 'elprops' property field is available, it will select the elements that are only set on this property.
mesh (Pin 7)
- Required: Yes
- Expected type(s):
abstract_meshed_region
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 | mesh_scoping | scoping |
mesh_scoping (Pin 0)
- Expected type(s):
scoping
Scoping
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: scoping
Plugin: core
Scripting name: on_mesh_property
Full name: scoping.on_mesh_property
Internal name: meshscoping_provider_by_prop
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("meshscoping_provider_by_prop"); // operator instantiation
op.connect(0, my_requested_location);
op.connect(1, my_property_name);
op.connect(2, my_property_id);
op.connect(5, my_inclusive);
op.connect(7, my_mesh);
ansys::dpf::Scoping my_mesh_scoping = op.getOutput<ansys::dpf::Scoping>(0);
CPython
import ansys.dpf.core as dpf
op = dpf.operators.scoping.on_mesh_property() # operator instantiation
op.inputs.requested_location.connect(my_requested_location)
op.inputs.property_name.connect(my_property_name)
op.inputs.property_id.connect(my_property_id)
op.inputs.inclusive.connect(my_inclusive)
op.inputs.mesh.connect(my_mesh)
my_mesh_scoping = op.outputs.mesh_scoping()
IPython
import mech_dpf
import Ans.DataProcessing as dpf
op = dpf.operators.scoping.on_mesh_property() # operator instantiation
op.inputs.requested_location.Connect(my_requested_location)
op.inputs.property_name.Connect(my_property_name)
op.inputs.property_id.Connect(my_property_id)
op.inputs.inclusive.Connect(my_inclusive)
op.inputs.mesh.Connect(my_mesh)
my_mesh_scoping = op.outputs.mesh_scoping.GetData()
Changelog
- Version 0.0.0: Initial release.