Skip to main content

DPF Framework 2026 R1

math:* (component-wise field)

Last update: 31.07.2026

Version: 0.0.0

Description

Computes component-wise product between two fields of same dimensionality. If one field's scoping has an 'overall' location, then this field's values are applied on the other field entirely. When using a constant or 'work_by_index', you can use 'inplace' to reuse one of the fields.

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 fieldA Required field, fields_container
1 fieldB Required field, fields_container

fieldA (Pin 0)

field or fields container with only one field is expected

fieldB (Pin 1)

field or fields container with only one field is expected

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.

binary_operation

  • Expected type(s): binary_operation_enum, int32
  • Default value: 1

This option allows to choose how two inputs will be treated together. eOnlyIntersection (0) means that the output will only contain the entities shared by all the inputs. eUnion (1) means that the output will contain all the entities contained in at least one of the inputs.

inplace

  • Expected type(s): bool
  • Default value: false

The output is written over the input to save memory if this config is set to true.

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

permissive

  • Expected type(s): bool
  • Default value: false

If this option is set to true, warning checks (like unit or data sizes) won't be done.

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.

use_cache

  • Expected type(s): bool
  • Default value: true

Some intermediate data is put in cache if this config is set to true. This option can reduce computation time after the first run.

work_by_index

  • Expected type(s): bool
  • Default value: false

If this option is set to true, loops and comparisons by entity will be done by index instead of ids.

Scripting

This operator can be accessed through scripting interfaces using these identifiers.

Category: math

Plugin: core

Scripting name: None

Full name: None

Internal name: component_wise_product

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("component_wise_product"); // operator instantiation
op.connect(0, my_fieldA);
op.connect(1, my_fieldB);
ansys::dpf::Field my_field = op.getOutput<ansys::dpf::Field>(0);
CPython
import ansys.dpf.core as dpf

op = dpf.operators.math.None() # operator instantiation
op.inputs.fieldA.connect(my_fieldA)
op.inputs.fieldB.connect(my_fieldB)
my_field = op.outputs.field()
IPython
import mech_dpf
import Ans.DataProcessing as dpf

op = dpf.operators.math.None() # operator instantiation
op.inputs.fieldA.Connect(my_fieldA)
op.inputs.fieldB.Connect(my_fieldB)
my_field = op.outputs.field.GetData()

Changelog

  • Version 0.0.0: Initial release.

Connect with Ansys