## On this page

  

 

 # utility:merge fields containers

 Last update: 31.07.2026 

**Version: 0.0.0**

## Description

Assembles a set of fields containers into a unique 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 numberNameStatusExpected type(s)**-200**[should\_merge\_named\_selections](#input_-200)[`bool`](../../core-concepts/dpf-types.md#standard-types)**-3**[sum\_merge](#input_-3)[`bool`](../../core-concepts/dpf-types.md#standard-types)**-2**[merged\_fields\_support](#input_-2)`abstract_field_support`**-1**[merged\_fields\_containers\_support](#input_-1)`abstract_field_support`, `umap<string,shared_ptr<abstract_field_support>>`0[fields\_containers](#input_0)Required`vector<shared_ptr<fields_container>>`, [`fields_container`](../../core-concepts/dpf-types.md#fields-container)<a id="input_-200"></a>

### should\_merge\_named\_selections (Pin -200)

- **Required:** No
- **Expected type(s):** [`bool`](../../core-concepts/dpf-types.md#standard-types)

For some result files (such as RST), the scoping on names selection is duplicated through all the distributed files.If this pin is false, the merging process is skipped. If it is true, this scoping is merged. Default is true.

<a id="input_-3"></a>

### sum\_merge (Pin -3)

- **Required:** No
- **Expected type(s):** [`bool`](../../core-concepts/dpf-types.md#standard-types)

Default is false. If true, redundant quantities are summed instead of being ignored.

<a id="input_-2"></a>

### merged\_fields\_support (Pin -2)

- **Required:** No
- **Expected type(s):** `abstract_field_support`

Already merged field support.

<a id="input_-1"></a>

### merged\_fields\_containers\_support (Pin -1)

- **Required:** No
- **Expected type(s):** `abstract_field_support`, `umap<string,shared_ptr<abstract_field_support>>`

Already merged fields containers support.

<a id="input_0"></a>

### fields\_containers (Pin 0)

- **Required:** Yes
- **Expected type(s):** `vector<shared_ptr<fields_container>>`, [`fields_container`](../../core-concepts/dpf-types.md#fields-container)

A vector of fields containers to merge or fields containers from pin 0 to ...

## 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 numberNameExpected type(s)0[merged\_fields\_container](#output_0)[`fields_container`](../../core-concepts/dpf-types.md#fields-container)<a id="output_0"></a>

### merged\_fields\_container (Pin 0)

- **Expected type(s):** [`fields_container`](../../core-concepts/dpf-types.md#fields-container)

## Configurations

This operator supports [configuration options](../../core-concepts/operator-configurations.md) that modify its behavior.

### [mutex](../../core-concepts/operator-configurations.md#mutex)

- **Expected type(s):** [`bool`](../../core-concepts/dpf-types.md#standard-types)
- **Default value:** false

If this option is set to true, the shared memory is prevented from being simultaneously accessed by multiple threads.

### [read\_inputs\_in\_parallel](../../core-concepts/operator-configurations.md#read_inputs_in_parallel)

- **Expected type(s):** [`bool`](../../core-concepts/dpf-types.md#standard-types)
- **Default value:** false

If this option is set to true, the operator's inputs will be evaluated in parallel.

## Scripting

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

**Category**: utility

**Plugin**: core

**Scripting name**: merge\_fields\_containers

**Full name**: utility.merge\_fields\_containers

**Internal name**: merge::fields\_container

**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++```cpp
#include "dpf_api.h"

ansys::dpf::Operator op("merge::fields_container"); // operator instantiation
op.connect(-200, my_should_merge_named_selections);
op.connect(-3, my_sum_merge);
op.connect(-2, my_merged_fields_support);
op.connect(-1, my_merged_fields_containers_support);
op.connect(0, my_fields_containers);
ansys::dpf::FieldsContainer my_merged_fields_container = op.getOutput<ansys::dpf::FieldsContainer>(0);

```

CPython```python
import ansys.dpf.core as dpf

op = dpf.operators.utility.merge_fields_containers() # operator instantiation
op.inputs.should_merge_named_selections.connect(my_should_merge_named_selections)
op.inputs.sum_merge.connect(my_sum_merge)
op.inputs.merged_fields_support.connect(my_merged_fields_support)
op.inputs.merged_fields_containers_support.connect(my_merged_fields_containers_support)
op.inputs.fields_containers1.connect(my_fields_containers1)
op.inputs.fields_containers2.connect(my_fields_containers2)
my_merged_fields_container = op.outputs.merged_fields_container()

```

IPython```python
import mech_dpf
import Ans.DataProcessing as dpf

op = dpf.operators.utility.merge_fields_containers() # operator instantiation
op.inputs.should_merge_named_selections.Connect(my_should_merge_named_selections)
op.inputs.sum_merge.Connect(my_sum_merge)
op.inputs.merged_fields_support.Connect(my_merged_fields_support)
op.inputs.merged_fields_containers_support.Connect(my_merged_fields_containers_support)
op.inputs.fields_containers.Connect(my_fields_containers)
my_merged_fields_container = op.outputs.merged_fields_container.GetData()

```

  
## Changelog

- Version 0.0.0: Initial release.