## On this page

  

 

 # Changelog

 Last update: 31.07.2026 

Changes introduced with **DPF 26.1**.

This changelog is organized by category, with sections for different types of updates (new features, bug fixes, changes, performance improvements).

The following table shows which components have updates in each category.

ComponentFeaturesFixesPerformance improvementsc#[1 item](#Features_csharp)cff[2 items](#Features_cff)[3 items](#Fixes_cff)cgns[1 item](#Features_cgns)compression[2 items](#Features_compression)documentation[3 items](#Features_documentation)[1 item](#Fixes_documentation)engineeringdata[1 item](#Fixes_engineeringdata)femutils[3 items](#Feat_femutils)[18 items](#Fixes_femutils)[5 items](#Perf_femutils)framework[6 items](#Feat_framework)[15 items](#Fixes_framework)grpc[1 item](#Features_grpc)[3 items](#Fixes_grpc)hdf5[8 items](#Features_hdf5)[7 items](#Fixes_hdf5)[2 items](#Perf_hdf5)hgp[6 items](#Features_hgp)[3 items](#Fixes_hgp)lsdyna[1 item](#Features_lsdyna)mapdl[16 items](#Features_mapdl)[29 items](#Fixes_mapdl)math[2 items](#Fixes_math)[1 item](#Perf_math)mechanical[1 item](#Features_mechanical)mesh[3 items](#Fixes_mesh)multiphysicsmapper[1 item](#Fixes_multiphysicsmapper)native[7 items](#Feat_native)[20 items](#Fixes_native)[2 item](#Perf_native)rbd[1 item](#Fixes_rbd)vtk[1 item](#Fixes_vtk)## c#

### <a id="Features_csharp"></a> Features

- Enable C# wrapping of DPF C++ plugins: > Add the capability to expose any DPF C++ plugin in C# using DPF\_Plugin\_CSharp\_Wrapper.exe.

## cff

### <a id="Features_cff"></a> Features

- Expose is\_mesh\_available:
    
    > Expose `is_mesh_available` for cff files.
- Expose all results from Fluid files:
    
    > Previously, only a selected set of results could be retrieved from Fluid files (velocity, pressure...). With this enhancement, all results contained in a Fluent/CFX result file can be retrieved.

### <a id="Fixes_cff"></a> Fixes

- Ensure that gRPC servers are running on 1 thread:
- Fix out of bounds issue in units handling:
- Set proper names for User-Defined Memory variables:

## cgns

### <a id="Features_cgns"></a> Features

- Expose is\_mesh\_available operator:
    
    > Expose `is_mesh_available` for cgns and h5dpf files.

## compression

### <a id="Features_compression"></a> Features

- Support threshold by number of components in quantization operator:
    
    > It is now possible to apply a different threshold on each component in the operators **Quantization** ("quantization\_fc") and **QuantizationFC** ("quantization\_fc").
- New [quantization](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/compression/quantization.md) and [quantization\_fc](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/compression/quantization_fc.md) operator:
    
    > Scales a field to a given precision threshold, then rounds all the values to the unit.

## documentation

### <a id="Features_documentation"></a> Features

- Show operator version and changelog:
    
    > The html\_doc operator now generates the html operator documentation with the operator version and its changelog displayed.
    > 
    > Also adds to the HGP `ansys::dpf::Changelog.toMap()`.
- Add supported file types for operators in generated documentation:
    
    > Operator **html\_doc** now displays information about supported file types if available.
    > 
    > New operator **info::router\_discovery** allows to access information through DataTree.
- Add Markdown and LaTeX example operator:
    
    > This PR adds an example operator `markdown_latex_example` to `Ans.Dpf.Documentation` where usage of supported Markdown and LaTeX is showcased.
    > 
    > It also allows to test whether the operator is properly exposed in all clients and pipelines.
    > 
    > We take the opportunity to fix support for multiline descriptions in output pins during generation of operator classes in C#.

### <a id="Fixes_documentation"></a> Fixes

- Sanitize pin names in script examples for html\_doc documentation: > Fix operator usage examples in the documentation generated by operator `html_doc` by sanitizing pin names with annotations (such as "modified inplace").

## engineeringdata

### <a id="Fixes_engineeringdata"></a> Fixes

- Evaluation of temperature dependent material property field from rst was not working properly: > Correction of **ans\_mat\_from\_materials\_data**, which was not working properly when reading temperature dependent material properties from rst file.

## femutils

### <a id="Feat_femutils"></a> Features

- Support nodal/element scopings container and summation fields container in force summation operators:
    
    > - Input mesh scopings container are now supported in force\_summation and force\_summation\_psd operators
    > - Input fields container for summation point are now supported in force\_summation, torque and force\_summation\_psd operators
- Change the licensing type of the `geo.normals_provider_nl` operator from Premium to Entry:
    
    > The `geo.normals_provider_nl` is changed from Premium to Entry (it now only requires a license check and was previously requiring a checkout).
- Allow for cyclic constant expansion in `result.recombine_harmonic_indeces_cyclic`:
    
    > Add a new `is_constant` input pin to `result.recombine_harmonic_indeces_cyclic` to let it know the result is constant across sectors. If the result is constant, the operator only uses the result at the first sector.

### <a id="Fixes_femutils"></a> Fixes

- Correction for averaged midside nodes from corner nodes when having multiple shell layers:
    
    > Correction of size for averaging operators when having multiple shell layers and skin elements.
- Keep the input unit when computing torque and force summation:
    
    > The torque and force summation operator now output moments matching the mesh and force units.
- Seg fault in mapping `solid_to_skin` for heterogenous location:
    
    > In case of mixed location (Elemental + Nodal for example), seg fault appeared using mapping `solid_to_skin` op.
- Wrong initialization of tolerance in mapping operator:
    
    > The tolerance initialization in mapping operator caused a random bug.
- Memory allocation bug:
    
    > Fix a memory allocation bug in the `poynting_vector_surface` operator.
- Incorrect number of data on the last id after `nodal_to_elemental_nodal_fc`:
    
    > Fixing error of incorrect number of data on the last id after `nodal_to_elemental_nodal_fc`.
- Issue with shell layers calculation in the results field while having mid-side nodes on some elements:
    
    > Fixed issue with shell layers calculation in the results field while having mid-side nodes on some elements where additional values were shown in the output.
- Add support for contact element filtering in force summation operators:
    
    > Force summation operators now filter contact elements by default, and account for the summation point unit.
- Missing results with `on_coordinates` mapping operator:
    
    > Correcting behavior of the `on_coordinates` mapping operator as some nodes were not retrieved.
- Fix incorrect normals for shells with `normals_provider_nl`:
    
    > Fix the incorrect calculation of normals for a model containing shell elements of `Quad8` shape described in length units other than meters.
    > 
    > The proposed improvement fixes the normal calculations affecting node, element and face normals for shell elements.
- Fix `normals_provider_nl` operator crash:
    
    > A crash arose from a segmentation fault that occurred when the `normal_provider_nl` operator that is designed for a shell element was used on a solid element. The operator now throws a clear error if the input mesh contains a solid region.
- Support fields with a heterogeneous number of shell layers in all averaging operators:
    
    > Fields with heterogeneous shell layers (e.g. entities that have a different number of shell layers to the one reflected by the FieldDefinition ShellLayers) had a wrong behavior in different averaging operators. This is now fixed.
- Support fields with a heterogeneous number of shell layers in the `elemental_to_nodal` operator:
    
    > Support heterogeneous shell layer fields in the `elemental_to_nodal` operator.
- Fix support in `entity_average` of fields with a heterogeneous number of shell layers that have already undergone a `change_shell_layer` operation:
    
    > Fixed the concatenation step of the `entity_average` operator for fields with a heterogeneous number of shell layers that have undergone a `change_shell_layer` operation.
- Crash when querying skin mesh with `mesh.from_scopings` and `mesh.split_mesh`:
    
    > Fixed an issue in mesh connectivity reconstruction for skin meshes with `mesh.from_scopings` and `mesh.split_mesh` that resulted in the wrong number of nodes.
- Undefined behavior with custom property fields in mesh::by\_scoping:
    
    > Fixed undefined behavior with `mesh::by_scoping` when we create custom property fields.
- Issue with empty fields in `mapping.solid_to_skin_fc` operator:
    
    > Fix handling of empty fields in the `mapping.solid_to_skin_fc` operator.

### <a id="Perf_femutils"></a> Performance improvements

- Performance improvement for split\_fields:
    
    > Performance improvement for the `split_fields` operator when several meshes are the input.
- Performance issues on Nodal Extend To Mid Nodes:
- Performance improvements when splitting skin mesh by material:
- Performance issue of mapping solid to skin with Nodal locations:
    
    > Improvement of performance of `solid_to_skin_fc` for Nodal results. Parallelization is now available for this operator.
- Performance issue with solid to skin operator with ElementalNodal and Elemental:
    
    > Improving performance of the `solid_to_skin_fc` operator for `Elemental` and `ElementalNodal` locations.

## framework

### <a id="Feat_framework"></a> Features

- Add a Unit string to express British ton:
    
    > The string `"ton"` in DPF units denotes the Metric Ton (1000 kg). The string `"tonuk"` now denotes the British ton (also known as Long ton, approximately 1016.05 kg or 2240 pounds of mass).
- Establish thread safety and STL compliance for scopingIterators:
    
    > - Test for thread safety when using scoping Iterators for read access within parallel regions (over fields, over scoping etc).
    > - Promote STL algorithm compliance in scoping iterators so that scoping objects can be directly manipulated with them.
- Support creep strain results:
    
    > DPF and several plugins now support creep strain results (EPCR)
- Support pressure and fluid velocity results:
    
    > Addition of operators to read fluid velocity and pressure (corresponding to the dofs VX, VY, VZ and PRES)
- Support new material properties:
    
    > Add support for new material properties:
    > 
    > enthalpy, dielectric loss tangent, major/minor Poisson's ratio, magnetic relative permeability, electric relative permittivity, magnetic coercive force, Seebeck coefficients, Sonic velocity, constant material damping coefficient, bulk viscosity, heat generation rate, reference temperature, instantaneous coefficient of thermal expansion, thermal strain, damping ratio, magnetic loss tangent, stiffness matrix multiplier for damping, mass matrix multiplier for damping, Hall coefficient, diffusivity coefficient, coefficient of diffusion expansion, saturated concentration, reference concentration, heat coefficient at constant volume per unit of mass, diffusivity of sound used in the Westervelt equation, coefficient of nonlinearity used in the Westervelt equation.
- Support new result for Nodal Orientations:
    
    > Support Node Euler Angles results at the framework level for node orientations.

### <a id="Fixes_framework"></a> Fixes

- Fix the names associated to some materials properties:
    
    > - `Volumic Mass` is now exposed as `Mass Density`.
    > - `Second Lame's coefficient` is now exposed as `Coefficient of friction`.
- Property field not available error:
    
    > DPF now throws an explicit error when the queried property field is not available. This impacts operator such as `metadata.property_field_provider_by_name` or `metadata.mesh_property_provider`.
- Expose PinSpecification.ellipsis to replace PinSpecification.ellispis:
    
    > Prepare deprecation of the old method containing a typo by adding a new method with the correct name.
- Fix header copy in `Field.deep_copy`:
    
    > The Field header was not deep-copied in a deep-copy operation of the Field, which caused issues when it was modified downstream. This is now fixed.
- Remove `nodal_moment` operator:
    
    > The `nodal_moment` result operator currently has no plugin implementing it in the standard installation, resulting in user confusion as to what file type is supported. The choice is made to remove it from result operators recorder at the framework level until an official plugin supports it.
- Fix the error message when using a wrong name for workflow input or output:
    
    > Improve the error message when an unavailable name is used when connecting a workflow input or requesting a workflow output.
    > 
    > The error message now mentions both the available workflow inputs and available workflow outputs.
- Fix `compute_residual_and_error` operator for inputs with generic labels:
    
    > Input Fields containers with multiple labels (not only time) were not allowed in `compute_residual_and_error` operator.
    > 
    > The operator now computes the norm and the error for each field in the collection, even if there are multiple fields associaed to a single time step.
- Fix parallelization in several operators:
    
    > Multithreading parallelization was not properly enforced in several operators (like merge\_fields or generalized\_inner\_product).
- Fixed issue with Qua4FindElementCoordinates for mapping and find\_reduced\_coordinates:
    
    > Fix bug with interpolation points at corner node in the mapping operator.
- Fixing memory error in Scoping Iterators for empty scoping:
    
    > - This fix prevents memory exception errors arising during initialization of the scoping iterators for non-memory allocated scopings.
- Fix the name associated to result PL2:
    
    > Fix the name associated to the `square of the L2 norm of pressure over element volume`. It is now exposed as `squared_l2norm_pressure`.
- Make load library on local core possible after plugin already loaded:
    
    > fix: possibility to load a plugin on a specific registry after loading it once
- Fix the definition of Beam3 elements in the framework:
    
    > Elements of type beam3 were treated the same as line3 elements. They now have their specific definition.
- Support heterogeneous ShellLayers Fields in all averaging operators:
    
    > Fields with heterogeneous shell layers (e.g. entities that have a different number of shell layers to the one reflected by the FieldDefinition ShellLayers) had a wrong behavior in different averaging operators. This is now fixed.
- Fix the automatic creation of a `.ansys` folder in the home folder:
    
    > fix: .ansys folder creation in home folder

## grpc

### <a id="Features_grpc"></a> Features

- Support named Dimensionless units in gRPC: > Support named Dimensionless units in gRPC. Since 25.2 this was possible from the HgP In Process. Now it is also possible in gRPC.

### <a id="Fixes_grpc"></a> Fixes

- Fix non-matching versions of Kernel in DataProcessingCore and Ans.Dpf.GrpcClient:
- Entities copied remotely via gRPC now reference the IP of the original server:
    
    > In some specific contexts, connecting remote data to a remote operator lead to an infinite loop and consumption of memory on the gRPC server.
- Creation of Any from DataSources in gRPC:
    
    > Fix creation of Any from DataSources in gRPC.

## hdf5

### <a id="Features_hdf5"></a> Features

- Provide links to fields and change the layout of labels for field containers in HDF5 files:
- Initial HDF5 built-in link implementation for "support references" in a scoping object:
    
    > Introduces the built-in HDF5 link mechanism to replace the mesh reference of a scoping object.
- HDF5 writing to use explicit dimensionality for improved visualization and to enable chunking:
    
    > Refactors the HDF5 data writing logic to explicitly use dimensionality (e.g., 2D layout instead of flat vectors) for improved data readability in visualization tools. It also enables **chunking**.
- Add HDF5 support for DataTree and AnyCollection:
    
    > Add support for DataTree and AnyCollection for HDF5 import and export.
- Move rotations to SourceOperators to enable them from h5dpf datasources:
    
    > Allow rotation to global from H5DPF result file.
- Expose `is_mesh_available` operator:
    
    > Expose `is_mesh_available` for cgns and h5dpf files.
- Support creep strain results:
    
    > DPF and several plugins now support creep strain results (EPCR)
- Support pressure and fluid velocity results:
    
    > Addition of operators to read fluid velocity and pressure (corresponding to the dofs VX, VY, VZ and PRES)

### <a id="Fixes_hdf5"></a> Fixes

- Expose missing solver version in hdf5:
- The deprecation message for `serialize_to_hdf5` now mentions the new operator by its scripting name:
    
    > The operator `serialize_to_hdf5` is marked as deprecated in its description but redirects to the internal name of the new operator to use. This changes the message to use the scripting name (`hdf5dpf_generate_result_file`).
- Correction of mesh detection in `mesh_property_provider` for HDF5:
    
    > In HDF5 version 6, the mesh section is located under the *Results* section, which differs from its placement in previous versions. To ensure backward compatibility, additional code has been implemented.
- Operator `result.migrate_to_h5dpf` now exports NAR results:
    
    > Operator `result.migrate_to_h5dpf` now export NAR results by default
- Only write support for collections if support is available:
    
    > Only write support for collections if support is available
- Operator `meshes_provider` for HDF5 does not split the mesh anymore:
    
    > Correction of `meshes_provider` for h5dpf to not split the mesh.
- Fix thickness extraction from SMISC/NMISC from h5dpf file:
    
    > Fix thickness extraction from SMISC/NMISC from h5dpf file

### <a id="Perf_hdf5"></a> Performance improvements

- Improve performance when reading a large number of fields from H5DPF:
- Improve performance when reading results using a scoping:

## hgp

### <a id="Features_hgp"></a> Features

- CustomTypeField of int64:
    
    > Allows to create a CustomTypeField of int64\_t in the DPF C++ HGP API.
- Add CustomTypeField.deep\_copy:
    
    > Allows to make a deep copy of a CustomTypeField.
- Allow user to get the path to the DPFClientAPI library directory:
    
    > Expose `LibraryHandle::libraryDir` which returns the path to the directory where DPF is loaded.
- Add new hgp functions to copy without data into a new field/scoping:
    
    > Add new hgp functions to copy without data into a new field.
- New getMatching\* API on Hgp:
    
    > Exposure of getMatching\* API on Hgp which allows to get the entry matching a LabelSpace in a Collection.
- New `can_replace` parameter for `add` methods of Collections:
    
    > To improve performance when creating fields containers with a large number of fields, such as when averaging a huge number of solutions on MSUP analyses, one can add an entity to a collection without checking first if the LabelSpace in question already exists in the collection.

### <a id="Fixes_hgp"></a> Fixes

- Fix Streams constructor on the HgP:
- Fix the copy of an empty vector:
- Improve the error message for unsupported unit creation:
    
    > Creating a unit in HGP using an unknown symbol generated a non-informative error.
    > 
    > It now raises an `std::invalid_argument` error which message indicates a homogeneity must be given along with the custom unit symbol.

## lsdyna

### <a id="Features_lsdyna"></a> Features

- Support d3plot files serialized with FEMZIP: > Support d3plot files serialized with FEMZIP.

## mapdl

### <a id="Features_mapdl"></a> Features

- New operator to extract records from RST files:
    
    > Operator `record_reader` is now available to read results from an RST file based on MAPDL record names.
- Source Operators for Acoustic Ops:
    
    > Adding Source Operators for Acoustic Operators.
- Adding new operator and result for Nodal Orientations:
    
    > Adding new operator and result for Nodal Orientations
- Nodal results on changing meshes:
    
    > Allow to read nodal results on changing meshes (adaptive model with NLAD or SMART Crack growth).
- Add ability to record all the skipped mesh elements:
    
    > The `mesh_provider` for MAPDL result files now has the ability to record skipped elements during result reading, and log them in debug logs.
    > 
    > The list of unsupported element types that were skipped when reading the MAPDL mesh is also available as a mesh property called `unsupported_apdl_element_type`.
- Expose rotation, rotation velocity and rotation acceleration results:
    
    > Addition of operators to read rotation (ROT), rotation velocity (OMG) and rotation acceleration (DMG) results.
- Expose MAPDL Beam Results:
    
    > - Expanding LS-Dyna Beam Result Operators to MAPDL Beam Results: Axial\_Force `B_N`, Bending Moments Y and Z `B_M1` and `B_M2`, Torque `B_MT`, Shear Forces `B_T1` and `B_T2`, Axial Stress `B_SN` and Axial Strain `B_EL`.
- Support operator `is_mesh_available` for rst, rfrq and rdsp file formats:
    
    > The framework exposes a new operator `is_mesh_available` to check if the result file contains the mesh.
    > 
    > The adds support for `rst`, `rfrq`, and `rdsp` file formats.
- Support creep strain results:
    
    > DPF and several plugins now support creep strain results (EPCR).
- Support pressure and fluid velocity results:
    
    > Addition of operators to read fluid velocity and pressure (corresponding to the dofs VX, VY, VZ and PRES)
- Support adaptive meshes in mesh providers:
    
    > When conducting Crack Growth analysis or an NLAD analysis, an adaptive remeshing process creates new meshes at some time steps.
    > 
    > Mesh getters (`mesh_provider`, `meshes_provider`) now support models with adaptive meshing.
- Support new material properties:
    
    > Add support for new material properties:
    > 
    > enthalpy, dielectric loss tangent, major/minor Poisson's ratio, magnetic relative permeability, electric relative permittivity, magnetic coercive force, Seebeck coefficients, Sonic velocity, constant material damping coefficient, bulk viscosity, heat generation rate, reference temperature, instantaneous coefficient of thermal expansion, thermal strain, damping ratio, magnetic loss tangent, stiffness matrix multiplier for damping, mass matrix multiplier for damping, Hall coefficient, diffusivity coefficient, coefficient of diffusion expansion, saturated concentration, reference concentration, heat coefficient at constant volume per unit of mass, diffusivity of sound used in the Westervelt equation, coefficient of nonlinearity used in the Westervelt equation.
- Support shell layers in APDLElementDescriptor:
    
    > Add management of shell layers to element descriptions.
    > 
    > Add support for elements `SHELL43-63-93`, `SHELL131&132`, `SHELL181-281-208-209`, `SOLSH190`, `SHELL294`, `SOLID185-186`, `SOLID278-279`, `ELBOW290`.
    > 
    > Add support for shell section data.
- Support contact results from mode and RST files:
    
    > Support reading ECT\_STAT, ECT\_PENE, ECT\_GAP, ECT\_CNOS, ECT\_FRES, ECT\_PRES, ECT\_SFRIC, ECT\_STOT, ECT\_SLIDE, and ECT\_FLUX from mode and rst files.
- Allow reading from RDSP and RFRQ files when outres is used with MXPAND,OFF:
    
    > Allow reading rotations, displacements, velocities, and accelerations from RDSP and RFRQ files when `outres` is used with `MXPAND,OFF`.
- Support live monitoring of an MAPDL output result file:
    
    > Refresh the result cache if the result file changes to allow live output monitoring.

### <a id="Fixes_mapdl"></a> Fixes

- Gradient and fluxes results incorrectly extracted:
    
    > Gradient and fluxes results could be incorrectly extracted if only one of the following DOFS was on the file: VOLT, MAG, AZ, TEMP.
    > 
    > If only one of these DOFs was in the file and we queried the flux (or gradient) of another DOF, incorrect data was retrieved.
- Fix a mesh loading failure for some degenerated quadratic elements:
    
    > Fix an `incomplete connectivity` failure in the `meshes_provider` for some degenerated quadratic elements.
- Fix physics type for models in RSTP files:
    
    > The physics type for RSTP files is now set to `mechanical`.
- Fix a bug in the detection of the number of plies detection when filtering elemental results:
    
    > Fix the management of plies in shell elements when filtering elemental results.
- Fix mapdl::rst::mesh\_property\_provider for specific input mesh scopings for ditributed files:
    
    > Fix mapdl::rst::mesh\_property\_provider building incorrect fields due a pontential mismatch between input scoping and actual mesh scoping.
    > 
    > This operator was building corrupted fields when used with a distributed datasource and a specific scoping, or when a scoping was including elements outside of the result file.
- Add a heat generation unit and fix current and electric flux densities:
    
    > Fix `result.current_density` (JC) and `result.electric_flux_density` (EFD) results not being available for some elements types.
- Block unsupported files and fix multiple memory management issues:
    
    > - Fix multiple memory management issues when using older or specific MAPDL result files.
    > - **Block the reading of MAPDL result files created with the option /fsplit,1**.
    > - **Deprecate the reading of MAPDL result file created before the release 14.5, this will be an error in 2027R1**.
- Fix support of heat transfer results for LINK33:
    
    > Add Heat Flux result support for LINK33 elements.
- Fix the reading of state variables for BEAM elements:
    
    > Fix the reading of state variable (SVAR) results on BEAM elements.
- Fix missing available results in the result info for mode files:
    
    > Fix available results in result info from result\_info\_provider operator when the available results are coming from the mode file. Only displacements results were listed before.
- Fix calculation of combined thermal strain:
    
    > The effective Poisson ratio was missing for thermal strain results.
- Fix nodal result PRES filtering:
    
    > Fix a bug where Pressure was filtered out on midside nodes for acoustic elements with linear pressure behavior (FLUID220, FLUID221 &amp; FLUID244 with KEYOPT(2) =5/6)
- Update rotation matrix documentation for coordinate\_system\_provider:
    
    > Clarify that the rotation matrix generated is from the local to the global coordinate system.
- Fix a bug in nodal averaging when requested for a nodal scoping of midside nodes only:
    
    > Results averaged to nodes were incorrect when requested on a mesh scoping containing only midside nodes.
- Fix a bug when reading complex results from complex mode files for a Full Damped solver type:
    
    > Fix a bug when reading complex results from complex mode files for a Full Damped solver type in analyses where the damped system mode-extraction method is used.
- Include enforced motion into modal basis:
    
    > Include enforced motion into modal basis.
- Fix the logic on plies/position for BFE filter:
    
    > Fix the handling of plies/position for BFE filter.
- Fix duplicate sector results sign when reading cyclic mode pairs and CYCOPT,MSUP,1:
    
    > Fix cyclic duplicate sectors results sign when reading non raw mechanical results (e.g. elements temperature or elements volume) of a cyclic mode pair from a result file written with CYCOPT,MSUP,1.
- Fix model title being truncated:
    
    > Titles from MAPDL models now take into account the full 80 characters allowed by the solver.
- Fix crash caused by invalid iterator when reading shell data:
    
    > Fix an access violation when reading shell elements in operator `pres_to_field`.
- Fix a bug in Modal Superposition Harmonic expansion of element nodal forces (ENF):
    
    > Fix a bug in the Modal Superposition Harmonic expansion of inertial element nodal forces.
- Avoid reading MCF at each chunk computation:
    
    > Bug fix to enhance performance on MCF requests.
- Fix filtering of unsupported degenerated elements:
    
    > Filtering functions were not correctly filtering-out unsupported elements if degenerated.
- Fix MSUP expansion of results from distributed models where one domain is empty:
    
    > Fix MSUP expansion of results from distributed models where one domain is empty.
- Fix a crash for cms expansion:
    
    > Fix a crash for cms expansion on models with zero bodies.
- Add missing TimeFreqSupport to modal results:
    
    > Add missing TimeFreqSupport to modal results.
- Fix gasket closure results:
    
    > Fix bugs concerning gasket results
    > 
    > 
    > - GKD -&gt; was returning GKDI -&gt; now returns sum of GKTH and GKDI.
    > - GKDI -&gt; was returning an error or wrong values -&gt; works correctly now.
    > - GKS / GKTH / GKDI -&gt; rotation of these results is now blocked to match APDL results.
- Fix connectivity in linear CONTA177 elements:
    
    > Previously a -1 was reported in the last node index, only 2 nodes are reported now.
- Fix a performance issue for nodal averaged results requested on a large number of scopings on large meshes:
    
    > Getting nodal averaged results on a large number of scopings with a large mesh was virtually impossible due to a performance issue which is now fixed.

## math

### <a id="Fixes_math"></a> Fixes

- Fix handling of empty fields in mode shapes in `expansion_psd`
- Reduce the threshold for detection of division by zero in the complex division operator:
    
    > Change the tolerance for complex division from 1e-10 to 1e-15.

### <a id="Perf_math"></a> Performance improvements

- Performance enhancements for `math.fft_multi_harmonic_minmax`: > FFT Multiharmonic performance enhancements

## mechanical

### <a id="Features_mechanical"></a> Features

- Addition of events to monitor the status of producer\_consumer\_for\_each operator: > Addition of events to monitor the status of producer\_consumer\_for\_each operator.

## mesh

### <a id="Fixes_mesh"></a> Fixes

- Fix a crash in meshed\_skin\_sector with non elemental properties:
    
    > meshed\_skin\_sector: Fix a crash when the mesh includes non-elemental properties
- Fix support for Beam3 elements in skin and mesh\_to\_pyvista operators:
    
    > The `"skin"` operator was only transferring Line2 and Line3 elements to the output mesh. Beam3 elements are supported now as well.
    > 
    > Similarly, the `"mesh_to_pyvista"` operator was not handling Beam3 elements. They are now correctly treated.
- Fix connectivity of Line3 elements in skin mesh:
    
    > With a previous change, Line3 elements were shipped with only 2 nodes after a skin extraction operation. They now have the 3 nodes they are expected to have (2 corner nodes and the midside node).

## multiphysicsmapper

### <a id="Fixes_multiphysicsmapper"></a> Fixes

- Fix parallelization in Linux:
    
    > The `mapping.apply_mechanical_native_mapping` operator now runs properly in parallel in Linux.

## native

### <a id="Feat_native"></a> Features

- Support header in field::get\_attribute operator and expose propertyfield/customtypefield::get\_attribute:
    
    > Headers are supported as valid properties to forward in the `field::get_attribute` operator. The `propertyfield::get_attribute` and `customtypefield::get_attribute` operators are created mimicking the behavior of the other one.
- Add operator `utility.cyclic_support_get_attribute`:
    
    > Operator `utility.cyclic_support_get_attribute` is now available to request either `element_duplicate_offset` or `node_duplicate_offset` properties from a CycliSupport.
- Operator `metadata.time_freq_support_get_attribute` now supports property `step_id_from_harmonic_index`.
- New input pin `upper_bound` for operator `utility.ints_to_scoping`.
- Add operator `is_mesh_available`:
    
    > The new operator `is_mesh_available` checks if a result file contains a mesh.
- Allow vector of properties as input for `scoping.on_property`:
    
    > - The `property_id` input pin (2) now accepts a vector of property IDs.
- Add an `extend_to_mid_nodes` input pin to result operators with default `elemental_nodal` location:
    
    > Add an input pin `extend_to_mid_nodes` to source operators to allow not using mid-nodes during averaging from `elemental_nodal` to `nodal`.

### <a id="Fixes_native"></a> Fixes

- Avoid crashing when connecting streams or data sources to the wrong pin in Source Operators:
- Enhance the documentation of operator `logic.identical_fields`:
    
    > Explain the behavior of the `logic.identical_fields` operator in its specification.
- Clarify usage of the `bool_rotate_to_global` pin:
- Operator `serialization.csv_to_field` now handles empty fields correctly:
- Clarify error for operator `boundary_condition_provider` when using the wrong input pins:
    
    > If using the operator *boundary\_conditions\_provider* only with pins exposed in the documentation, it was crashing without a clear message.
    > 
    > Now, all the available pins are exposed in the documentation, and the operator outputs an understandable message when using wrong inputs.
- Fix operator `logic.elementary_data_selector` when no data pointer is available:
    
    > Fix operator `logic.elementary_data_selector` when no data pointer is available.
- Support fields with different scopings in `concatenate_fields`:
    
    > Added the possibility to merge fields with different scopings in operators *concatenate\_fields* and *concatenate\_fields\_containers*, with the possibility to choose the scoping to keep for output.
    > 
    > These operators are now public.
- Fix `solid_shell_fields` operator handling of empty fields:
    
    > The operator `solid_shell_fields` is now able to handle fields containers with empty fields.
- Fix stream\_provider error handling of empty datasources:
    
    > Fix stream\_provider returning an empty stream when the datasources is in input is empty. Throw instead.
    > 
    > Fix the stream\_provider returning a nullptr if a stream\_provider is not found for this namespace. Throw instead.
    > 
    > Also update the descriptions of the operator.
- Fix an access violation crash in the `math.scale` operator:
    
    > Program was crashing when not using the MKL to do the computation in the scale operator.
- Fix issue with empty label and crash for `math.average_over_label_fc`:
    
    > Fix a crash in `math.average_over_label_fc` in the case of an empty label input.
- Fix shell layers support for `scale_by_field` operator:
    
    > The `scale_by_field` operator now supports fields with shell layers.
- Scaling factors for absolute normalization in the `compute_residual_and_error` have a wrong size:
    
    > Absolute normalization in the `compute_residual_and_error` operator was exporting scaling factors with a size of the original data instead of having only one unit value per field.
- Remove the **bool\_rotate\_to\_global** pin from **raw\_operators**:
    
    > Remove the **bool\_rotate\_to\_global** pin from operators such as **raw\_displacement** and **raw\_reaction\_force**.
- Improve rotation handling on Invariant Source operators:
    
    > Improve rotation handling on Invariant operators.
- Fix of nested cms rotation with empty angles for harmonic msup:
    
    > Fix of nested cms rotation with empty angles for harmonic msup
- Fix scripting names of `merge::solid_shell_fields` and `incremental::merge` operators:
    
    > The operators `merge::solid_shell_fields` and `incremental::merge::xxx` had an inconsistent scripting name with the one generated in pydpf-core. This is now fixed.
- Support heterogeneous ShellLayers Fields in all averaging operators:
    
    > Fields with heterogeneous shell layers (e.g. entities that have a different number of shell layers to the one reflected by the FieldDefinition ShellLayers) had a wrong behavior in different averaging operators. This is now fixed.
- Updated specification of min\_max\_over\_time\_by\_entity:
    
    > Clarified the behavior for output pins 2 &amp; 3 (`time_freq_of_min` and `time_freq_of_max`).
    > 
    > Mention that input pin `compute_amplitude` is only relevant for complex fields.
- Fix operators `scoping.elemental_from_mesh` and `scoping.nodal_from_mesh`:
    
    > Fixed operators `scoping.elemental_from_mesh` and `scoping.nodal_from_mesh` returning scopings with an empty location property.
- Fix the accepted type for `shell_layer` input pin in result operators:
    
    > Correct the accepted value type for the `shell_layer` input pin in result operators such as `result.stress`. The accepted type is `int`, not `bool`.

### <a id="Perf_native"></a> Performance improvements

- Improve `scoping.transpose` operator performance:
    
    > Refactoring of the transpose scoping operator for performance improvements
- Performance issue with transpose scoping:
    
    > Improving performance of the `transpose_scoping` operator for cases with multiple scopings at a specific ratio with the length of the mesh.

## rbd

### <a id="Fixes_rbd"></a> Fixes

- Add support for `result_info_provider` for *mbd* files:

## vtk

### <a id="Fixes_vtk"></a> Fixes

- Fix support for Beam3 elements in skin and mesh\_to\_pyvista operators: > The `"skin"` operator was only transferring Line2 and Line3 elements to the output mesh. Beam3 elements are supported now as well.
    > 
    > Similarly, the `"mesh_to_pyvista"` operator was not handling Beam3 elements. They are now correctly treated.

## Operator changes

### New operators

#### compression

- [quantization](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/compression/quantization.md):
    
    > Scales a field to a given precision threshold, then rounds all the values to the unit.
- [quantization\_fc](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/compression/quantization_fc.md):
    
    > Scales all the fields of a fields container to a given precision threshold, then rounds all the values to the unit.

#### info

- [markdown\_latex\_example](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/info/markdown_latex_example.md): > This operator showcases the use of Markdown and LaTeX in operator and pin descriptions.

#### mapping

- [apply\_mechanical\_native\_mapping](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/apply_mechanical_native_mapping.md):
    
    > Maps source data from source mesh to target mesh (computes interpolation).This operator needs to be used with the prepare mechanical native mapping associated one.
- [create\_mech\_kriging\_workflow](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/create_mech_kriging_workflow.md):
    
    > Prepares a workflow able to map data from an input mesh to a target mesh.
- [create\_mech\_point\_cloud\_workflow](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/create_mech_point_cloud_workflow.md):
    
    > Prepares a workflow able to map data from an input mesh to a target mesh.
- [create\_mech\_shape\_func\_surf\_workflow](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/create_mech_shape_func_surf_workflow.md):
    
    > Prepares a workflow able to map data from an input mesh to a target mesh.
- [create\_mech\_shape\_func\_vol\_workflow](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/create_mech_shape_func_vol_workflow.md):
    
    > Prepares a workflow able to map data from an input mesh to a target mesh.
- [create\_sc\_mapping\_workflow](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/create_sc_mapping_workflow.md):
    
    > Prepares a workflow able to map data from an input mesh to a target mesh.
- [prepare\_mechanical\_native\_mapping](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/prepare_mechanical_native_mapping.md):
    
    > Prepare mapping of source data from source mesh to target mesh by operating the source\_mesh/target\_mesh weights computation. This operator needs to be used with the apply mechanical native mapping associated one. At least one of the optional DataTree inputs need to be set, in order to chose the mapping algorithm and set the mapping options.
- [prepare\_mechanical\_native\_mapping\_kriging](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/prepare_mechanical_native_mapping_kriging.md):
    
    > Prepare mapping of source data from source mesh to target mesh by operating the source\_mesh/target\_mesh weights computation. This operator will use a point kriging algorithm. This operator needs to be used with the apply mechanical native mapping associated one.
- [prepare\_mechanical\_native\_mapping\_point\_cloud](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/prepare_mechanical_native_mapping_point_cloud.md):
    
    > Prepare mapping of source data from source mesh to target mesh by operating the source\_mesh/target\_mesh weights computation. This operator will use a point cloud based algorithm. This operator needs to be used with the apply mechanical native mapping associated one.
- [prepare\_mechanical\_native\_mapping\_shape\_functions\_for\_surfaces](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/prepare_mechanical_native_mapping_shape_functions_for_surfaces.md):
    
    > Prepare mapping of source data from source mesh to target mesh by operating the source\_mesh/target\_mesh weights computation. This operator will use the shape functions of the elements. This operator is meant for surfaces elements. This operator needs to be used with the apply mechanical native mapping associated one.
- [prepare\_mechanical\_native\_mapping\_shape\_functions\_for\_volume](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/prepare_mechanical_native_mapping_shape_functions_for_volume.md):
    
    > Prepare mapping of source data from source mesh to target mesh by operating the source\_mesh/target\_mesh weights computation. This operator will use the shape functions of the elements. This operator is meant for volume elements but can also be used with surfaces elements. This operator needs to be used with the apply mechanical native mapping associated one.
- [sc\_mapping](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/sc_mapping.md):
    
    > Apply System Coupling to map data from an input mesh to a target mesh.
- [sysc\_point\_cloud\_wf](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/sysc_point_cloud_wf.md):
    
    > Prepares a workflow able to map data from an input mesh to a target mesh.
- [sysc\_shape\_function\_wf](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/sysc_shape_function_wf.md):
    
    > Prepares a workflow able to map data from an input mesh to a target mesh.

#### mesh

- [morphed\_field](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mesh/morphed_field.md):
    
    > Computes the displacement to apply on input coordinates (in 2) if a morphing field (in 0) is applied on coordinates (in 1)
- [morphing](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mesh/morphing.md):
    
    > Applies morphing on a meshed region depending on an input displacement field.
- [prepare\_morphing](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mesh/prepare_morphing.md):
    
    > Prepare morphing on a meshed region depending on an input displacement field.

#### result

- [acoustic\_energy\_density](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/acoustic_energy_density.md):
    
    > Read/compute AED by calling the readers defined by the datasources.
- [creep\_strain](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/creep_strain.md):
    
    > Read/compute element nodal component creep strains by calling the readers defined by the datasources.
    > 
    > 
    > - The 'requested\_location' and 'mesh\_scoping' inputs are processed to see if they need scoping transposition or result averaging. The resulting output fields have a 'Nodal', 'ElementalNodal' or 'Elemental' location.
    > - Once the need for averaging has been detected, the behavior of the combined connection of the 'split\_shells' and 'shell\_layer' pins is:
    > 
    > Averaging is needed'split\_shells''shell\_layer'Expected outputNoNot connected/falseNot connectedLocation as in the result file. Fields with all element shapes combined. All shell layers present.NotrueNot connectedLocation as in the result file. Fields split according to element shapes. All shell layers present.NotrueConnectedLocation as in the result file. Fields split according to element shapes. Only the requested shell layer present.NoNot connected/falseConnectedLocation as in the result file. Fields with all element shapes combined. Only the requested shell layer present.YesNot connected/trueNot connectedLocation as requested. Fields split according to element shapes. All shell layers present.YesfalseNot connectedLocation as requested. Fields with all element shapes combined. All shell layers present.YesfalseConnectedLocation as requested. Fields with all element shapes combined. Only the requested shell layer present.YesNot connected/trueConnectedLocation as requested. Fields split according to element shapes. Only the requested shell layer present.
    > - The available 'elshape' values are:
    > 
    > elshapeRelated elements1Shell (generic)2Solid3Beam4Skin5Contact6Load7Point8Shell with 1 result across thickness (membrane)9Shell with 2 results across thickness (top/bottom)10Shell with 3 results across thickness (top/bottom/mid)11Gasket12Multi-Point Constraint13Pretension
- [creep\_strain\_X](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/creep_strain_X.md):
    
    > Read/compute element nodal component creep strains XX normal component (00 component) by calling the readers defined by the datasources. Regarding the requested location and the input mesh scoping, the result location can be Nodal/ElementalNodal/Elemental.
- [creep\_strain\_XY](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/creep_strain_XY.md):
    
    > Read/compute element nodal component creep strains XY shear component (01 component) by calling the readers defined by the datasources. Regarding the requested location and the input mesh scoping, the result location can be Nodal/ElementalNodal/Elemental.
- [creep\_strain\_XZ](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/creep_strain_XZ.md):
    
    > Read/compute element nodal component creep strains XZ shear component (02 component) by calling the readers defined by the datasources. Regarding the requested location and the input mesh scoping, the result location can be Nodal/ElementalNodal/Elemental.
- [creep\_strain\_Y](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/creep_strain_Y.md):
    
    > Read/compute element nodal component creep strains YY normal component (11 component) by calling the readers defined by the datasources. Regarding the requested location and the input mesh scoping, the result location can be Nodal/ElementalNodal/Elemental.
- [creep\_strain\_YZ](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/creep_strain_YZ.md):
    
    > Read/compute element nodal component creep strains YZ shear component (12 component) by calling the readers defined by the datasources. Regarding the requested location and the input mesh scoping, the result location can be Nodal/ElementalNodal/Elemental.
- [creep\_strain\_Z](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/creep_strain_Z.md):
    
    > Read/compute element nodal component creep strains ZZ normal component (22 component) by calling the readers defined by the datasources. Regarding the requested location and the input mesh scoping, the result location can be Nodal/ElementalNodal/Elemental.
- [creep\_strain\_eqv](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/creep_strain_eqv.md):
    
    > Read/compute element nodal equivalent component creep strains by calling the readers defined by the datasources.
    > 
    > 
    > - The 'requested\_location' and 'mesh\_scoping' inputs are processed to see if they need scoping transposition or result averaging. The resulting output fields have a 'Nodal', 'ElementalNodal' or 'Elemental' location.
    > - Once the need for averaging has been detected, the behavior of the combined connection of the 'split\_shells' and 'shell\_layer' pins is:
    > 
    > Averaging is needed'split\_shells''shell\_layer'Expected outputNoNot connected/falseNot connectedLocation as in the result file. Fields with all element shapes combined. All shell layers present.NotrueNot connectedLocation as in the result file. Fields split according to element shapes. All shell layers present.NotrueConnectedLocation as in the result file. Fields split according to element shapes. Only the requested shell layer present.NoNot connected/falseConnectedLocation as in the result file. Fields with all element shapes combined. Only the requested shell layer present.YesNot connected/trueNot connectedLocation as requested. Fields split according to element shapes. All shell layers present.YesfalseNot connectedLocation as requested. Fields with all element shapes combined. All shell layers present.YesfalseConnectedLocation as requested. Fields with all element shapes combined. Only the requested shell layer present.YesNot connected/trueConnectedLocation as requested. Fields split according to element shapes. Only the requested shell layer present.
    > - The available 'elshape' values are:
    > 
    > elshapeRelated elements1Shell (generic)2Solid3Beam4Skin5Contact6Load7Point8Shell with 1 result across thickness (membrane)9Shell with 2 results across thickness (top/bottom)10Shell with 3 results across thickness (top/bottom/mid)11Gasket12Multi-Point Constraint13Pretension
- [creep\_strain\_intensity](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/creep_strain_intensity.md):
    
    > Reads/computes element nodal component creep strains, average it on nodes (by default) and computes its invariants. This operation is independent of the coordinate system unless averaging across elements is requested, in which case a rotation to the global coordinate system is performed.
- [creep\_strain\_max\_shear](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/creep_strain_max_shear.md):
    
    > Reads/computes element nodal component creep strains, average it on nodes (by default) and computes its invariants. This operation is independent of the coordinate system unless averaging across elements is requested, in which case a rotation to the global coordinate system is performed.
- [creep\_strain\_principal\_1](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/creep_strain_principal_1.md):
    
    > Read/compute element nodal component creep strains 1st principal component by calling the readers defined by the datasources and computing its eigen values. This operation is independent of the coordinate system unless averaging across elements is requested, in which case a rotation to the global coordinate system is performed. The off-diagonal strains are first converted from Voigt notation to the standard strain values.
- [creep\_strain\_principal\_2](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/creep_strain_principal_2.md):
    
    > Read/compute element nodal component creep strains 2nd principal component by calling the readers defined by the datasources and computing its eigen values. This operation is independent of the coordinate system unless averaging across elements is requested, in which case a rotation to the global coordinate system is performed. The off-diagonal strains are first converted from Voigt notation to the standard strain values.
- [creep\_strain\_principal\_3](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/creep_strain_principal_3.md):
    
    > Read/compute element nodal component creep strains 3rd principal component by calling the readers defined by the datasources and computing its eigen values. This operation is independent of the coordinate system unless averaging across elements is requested, in which case a rotation to the global coordinate system is performed. The off-diagonal strains are first converted from Voigt notation to the standard strain values.
- [fluid\_velocity](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/fluid_velocity.md):
    
    > Read/compute FV by calling the readers defined by the datasources.
- [gasket\_total\_closure](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/gasket_total_closure.md):
    
    > computes the gasket total closure (sum of gasket thermal closure and gasket inelastic closure).
- [gasket\_total\_closure\_X](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/gasket_total_closure_X.md):
    
    > Read/compute elemental gasket total closure XX normal component (00 component) by calling the readers defined by the datasources. Regarding the requested location and the input mesh scoping, the result location can be Nodal/ElementalNodal/Elemental.
- [gasket\_total\_closure\_XY](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/gasket_total_closure_XY.md):
    
    > Read/compute elemental gasket total closure XY shear component (01 component) by calling the readers defined by the datasources. Regarding the requested location and the input mesh scoping, the result location can be Nodal/ElementalNodal/Elemental.
- [gasket\_total\_closure\_XZ](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/gasket_total_closure_XZ.md):
    
    > Read/compute elemental gasket total closure XZ shear component (02 component) by calling the readers defined by the datasources. Regarding the requested location and the input mesh scoping, the result location can be Nodal/ElementalNodal/Elemental.
- [input\_sound\_power](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/input_sound_power.md):
    
    > Read/compute PINC by calling the readers defined by the datasources.
- [layer\_orientation\_provider](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/layer_orientation_provider.md):
    
    > Read the layer orientations.
- [modal\_acceleration](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/modal_acceleration.md):
    
    > Read/compute modal acceleration by calling the readers defined by the datasources.
- [modal\_coordinate](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/modal_coordinate.md):
    
    > Read/compute modal coordinate by calling the readers defined by the datasources.
- [modal\_velocity](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/modal_velocity.md):
    
    > Read/compute modal velocity by calling the readers defined by the datasources.
- [nodal\_rotation](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/nodal_rotation.md):
    
    > Read/compute nodal rotation by calling the readers defined by the datasources.
- [nodal\_rotation\_X](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/nodal_rotation_X.md):
    
    > Read/compute nodal rotation X component of the vector (1st component) by calling the readers defined by the datasources.
- [nodal\_rotation\_Y](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/nodal_rotation_Y.md):
    
    > Read/compute nodal rotation Y component of the vector (2nd component) by calling the readers defined by the datasources.
- [nodal\_rotation\_Z](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/nodal_rotation_Z.md):
    
    > Read/compute nodal rotation Z component of the vector (3rd component) by calling the readers defined by the datasources.
- [nodal\_rotational\_acceleration](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/nodal_rotational_acceleration.md):
    
    > Read/compute nodal rotational acceleration by calling the readers defined by the datasources.
- [nodal\_rotational\_acceleration\_X](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/nodal_rotational_acceleration_X.md):
    
    > Read/compute nodal rotational acceleration X component of the vector (1st component) by calling the readers defined by the datasources.
- [nodal\_rotational\_acceleration\_Y](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/nodal_rotational_acceleration_Y.md):
    
    > Read/compute nodal rotational acceleration Y component of the vector (2nd component) by calling the readers defined by the datasources.
- [nodal\_rotational\_acceleration\_Z](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/nodal_rotational_acceleration_Z.md):
    
    > Read/compute nodal rotational acceleration Z component of the vector (3rd component) by calling the readers defined by the datasources.
- [nodal\_rotational\_velocity](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/nodal_rotational_velocity.md):
    
    > Read/compute nodal rotational velocity by calling the readers defined by the datasources.
- [nodal\_rotational\_velocity\_X](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/nodal_rotational_velocity_X.md):
    
    > Read/compute nodal rotational velocity X component of the vector (1st component) by calling the readers defined by the datasources.
- [nodal\_rotational\_velocity\_Y](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/nodal_rotational_velocity_Y.md):
    
    > Read/compute nodal rotational velocity Y component of the vector (2nd component) by calling the readers defined by the datasources.
- [nodal\_rotational\_velocity\_Z](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/nodal_rotational_velocity_Z.md):
    
    > Read/compute nodal rotational velocity Z component of the vector (3rd component) by calling the readers defined by the datasources.
- [node\_orientations](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/node_orientations.md):
    
    > Read/compute node euler angles by calling the readers defined by the datasources.
- [node\_orientations\_X](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/node_orientations_X.md):
    
    > Read/compute node euler angles X component of the vector (1st component) by calling the readers defined by the datasources.
- [node\_orientations\_Y](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/node_orientations_Y.md):
    
    > Read/compute node euler angles Y component of the vector (2nd component) by calling the readers defined by the datasources.
- [node\_orientations\_Z](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/node_orientations_Z.md):
    
    > Read/compute node euler angles Z component of the vector (3rd component) by calling the readers defined by the datasources.
- [output\_sound\_power](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/output_sound_power.md):
    
    > Read/compute POUT by calling the readers defined by the datasources.
- [record\_reader](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/record_reader.md):
    
    > Extracts a record from a file.
- [squared\_l2norm\_pressure](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/squared_l2norm_pressure.md):
    
    > Read/compute Square of the L2 norm of pressure over element volume by calling the readers defined by the datasources.

#### serialization

- [export\_mesh\_with\_prime](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/serialization/export_mesh_with_prime.md): > Transfer DPF's meshed region into an external layer prime model and serialize it into a given file format.

#### utility

- [concatenate\_fields](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/utility/concatenate_fields.md):
    
    > Concatenates fields into a unique one by incrementing the number of components.
    > 
    > Example:
    > 
    > 
    > - Field1 components: { UX, UY, UZ }
    > - Field2 components: { RX, RY, RZ }
    > - Output field : { UX, UY, UZ, RX, RY, RZ }
- [concatenate\_fields\_containers](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/utility/concatenate_fields_containers.md):
    
    > Concatenates fields containers into a unique one by concatenating each of their fields.
    > 
    > Example:
    > 
    > 
    > - Fields Container 1: 
    >     - Field1 with components: { UX, UY, UZ }
    >     - Field2 with components: { VX, VY, VZ }
    > - Fields Container 2: 
    >     - Field1 with components: { RX, RY, RZ }
    >     - Field2 with components: { AX, AY, AZ }
    > - Output Fields Container: 
    >     - Field1 with components: { UX, UY, UZ, RX, RY, RZ }
    >     - Field2 with components: { VX, VY, VZ, AX, AY, AZ }
- [customtypefield\_get\_attribute](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/utility/customtypefield_get_attribute.md):
    
    > Gets a property from an input field/field container. A CustomTypeFieldin pin 0, a property name (string) in pin 1 are expected as inputs
- [cyclic\_support\_get\_attribute](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/utility/cyclic_support_get_attribute.md):
    
    > A CyclicSupport in pin 0 and a property name (string) in pin 1 are expected in input.
- [get\_operators](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/utility/get_operators.md):
    
    > Getter on operators inside a workflow.
- [operator\_changelog](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/utility/operator_changelog.md):
    
    > Return a GenericDataContainer used to instantiate the Changelog of an operator based on its name.
- [propertyfield\_get\_attribute](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/utility/propertyfield_get_attribute.md):
    
    > Gets a property from an input field/field container. A PropertyFieldin pin 0, a property name (string) in pin 1 are expected as inputs

### Changed operators

#### averaging

- [force\_summation](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/averaging/force_summation.md)
    
    > 0.1.0: Scopings container supported on pins 1 and 2. Fields container supported on pin 6.
    > 
    > 0.2.0: Add support for excluding or not contact elements.
    > 
    > 1.0.0: The moment unit is now kept from the input units and not converted to N.m.
- [force\_summation\_psd](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/averaging/force_summation_psd.md)
    
    > 0.1.0: Scopings container supported on pins 1 and 2. Fields container supported on pin 6.
    > 
    > 0.1.1: Contact elements are now excluded from the summation.
    > 
    > 1.0.0: The moment unit is now kept from the input units and not converted to N\*m.
- [nodal\_to\_elemental\_nodal](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/averaging/nodal_to_elemental_nodal.md)
    
    > 0.0.1: Fixed issue with resize output field.
- [nodal\_to\_elemental\_nodal\_fc](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/averaging/nodal_to_elemental_nodal_fc.md)
    
    > 0.0.1: Fixed issue with resize output fields.

#### filter

- [abc\_weightings](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/filter/abc_weightings.md)
    
    > 0.0.1: Fixed bug in frequency calculation with multiple rpms in the support.

#### geo

- [normals\_provider\_nl](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/geo/normals_provider_nl.md)
    
    > 0.0.1: Bug fixed for input mesh type containing solid elements.
    > 
    > 1.0.0: Fixed reference coordinate-system on which normals are calculated.
- [rotate\_in\_cylindrical\_cs](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/geo/rotate_in_cylindrical_cs.md)
    
    > 1.0.0: Fix bug for the rotation of strain fields with a cylindrical system whose axis is rotated.

#### logic

- [elementary\_data\_selector](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/logic/elementary_data_selector.md)
    
    > 0.1.0: fix of crash when input field data pointer is empty, the operator will output an empty field in this case moving forward.
    > 
    > 0.2.0: fix of crash when input field had no data pointer, the operator will output an empty field in this case moving forward.
- [solid\_shell\_fields](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/logic/solid_shell_fields.md)
    
    > 0.0.1: Input Fields Containers can contain empty fields.

#### mapping

- [find\_reduced\_coordinates](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/find_reduced_coordinates.md)
    
    > 0.1.0: Fix bug with interpolation points at corner nodes.
- [on\_coordinates](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/on_coordinates.md)
    
    > 0.1.0: Performance improvement.
    > 
    > 0.2.0: Fix bug with interpolation points at corner nodes.
    > 
    > 0.3.0: Fix bug with missing results and use\_quadratic\_elements pin.
- [solid\_to\_skin](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/solid_to_skin.md)
    
    > 0.1.0: Improving performance for Nodal locations.
    > 
    > 0.2.0: Improving performance for ElementalNodal and Elemental locations.
    > 
    > 0.2.1: Removing unneeded output hidden pin.
    > 
    > 0.2.2: Fixed issue with shell layers calculation in the results field while having mid-side nodes on some elements.
- [solid\_to\_skin\_fc](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mapping/solid_to_skin_fc.md)
    
    > 0.1.0: Improving performance for Nodal locations. Added parallelization.
    > 
    > 0.1.1: Bug fixed for empty fields container.
    > 
    > 0.2.0: Improving performance for ElementalNodal and Elemental locations.
    > 
    > 0.2.1: Fixed issue with different scopings in the input field.
    > 
    > 0.2.2: Fixed issue with shell layers calculation in the results field while having mid-side nodes on some elements.
    > 
    > 0.2.3: Fixed issue with fields container with mixed location.

#### math

- [accumulate\_level\_over\_label\_fc](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/math/accumulate_level_over_label_fc.md)
    
    > 0.0.1: Fixed issue with crash due to empty label.
- [accumulate\_min\_over\_label\_fc](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/math/accumulate_min_over_label_fc.md)
    
    > 0.0.1: Fixed issue with crash due to empty label.
- [accumulate\_over\_label\_fc](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/math/accumulate_over_label_fc.md)
    
    > 0.0.1: Fixed issue with crash due to empty label.
- [average\_over\_label\_fc](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/math/average_over_label_fc.md)
    
    > 0.0.1: Fixed issue with crash due to empty label.
- [compute\_residual\_and\_error](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/math/compute_residual_and_error.md)
    
    > 0.1.0: Support generic labels (not only time) in the input FieldsContainer
    > 
    > 0.1.1: Fixed the size of output scaling factors for the absolute normalization
- [expansion\_psd](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/math/expansion_psd.md)
    
    > 0.0.1: Fix handling of empty fields in mode shapes.
- [scale](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/math/scale.md)
    
    > 0.0.1: Fixed a segmentation fault.
- [scale\_by\_field](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/math/scale_by_field.md)
    
    > 0.0.1: Add support of fields with shell layers
- [scale\_by\_field\_fc](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/math/scale_by_field_fc.md)
    
    > 0.0.1: Add support of fields with shell layers
- [sweeping\_phase](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/math/sweeping_phase.md)
    
    > 0.0.1: Clarify the documentation.
- [sweeping\_phase\_fc](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/math/sweeping_phase_fc.md)
    
    > 0.0.1: Clarify the documentation.

#### mesh

- [from\_scoping](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mesh/from_scoping.md)
    
    > 0.1.0: Improvement in the performance.
    > 
    > 0.1.1: Fixed bug when the scoping of a property field and its mesh are different.
    > 
    > 0.1.2: Fixed bug when some of the ids of the desired new scoping is not present in the property field or in the mesh.
    > 
    > 0.1.3: Fixed undefined behavior with custom property fields.
- [from\_scopings](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mesh/from_scopings.md)
    
    > 0.0.1: Improvement in the performance.
    > 
    > 0.0.2: Fixing issue with connectivity.
- [mesh\_provider](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mesh/mesh_provider.md)
    
    > 0.1.0: Update the effect of the permissive configuration.
- [meshes\_provider](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mesh/meshes_provider.md)
    
    > 0.1.0: Update the effect of the permissive configuration.
- [skin](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mesh/skin.md)
    
    > 0.0.1: Fixing issue related to share pointers of property fields and mesh.
    > 
    > 0.0.2: Internal change to share pointers of property fields and mesh.
- [split\_mesh](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/mesh/split_mesh.md)
    
    > 0.0.1: Improvement in the performance.
    > 
    > 0.0.2: Fixing issue with connectivity

#### metadata

- [boundary\_condition\_provider](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/metadata/boundary_condition_provider.md)
    
    > 0.0.1: Improved documentation and exceptions handling.
- [element\_types\_provider](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/metadata/element_types_provider.md)
    
    > 0.1.0: Added the possibility to output a PropertyField.
- [streams\_provider](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/metadata/streams_provider.md)
    
    > 0.1.0: Add the permissive configuration.
- [time\_freq\_support\_get\_attribute](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/metadata/time_freq_support_get_attribute.md)
    
    > 0.1.0: Add new supported property name 'step\_id\_from\_harmonic\_index' returning an int.

#### result

- [accu\_eqv\_creep\_strain](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/accu_eqv_creep_strain.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [accu\_eqv\_plastic\_strain](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/accu_eqv_plastic_strain.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [artificial\_hourglass\_energy](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/artificial_hourglass_energy.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [beam\_axial\_force](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/beam_axial_force.md)
    
    > 0.1.0: MAPDL results supported.
- [beam\_axial\_stress](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/beam_axial_stress.md)
    
    > 0.1.0: MAPDL results supported.
- [beam\_axial\_total\_strain](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/beam_axial_total_strain.md)
    
    > 0.1.0: MAPDL results supported.
- [beam\_s\_bending\_moment](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/beam_s_bending_moment.md)
    
    > 0.1.0: MAPDL results supported.
- [beam\_s\_shear\_force](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/beam_s_shear_force.md)
    
    > 0.1.0: MAPDL results supported.
- [beam\_t\_bending\_moment](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/beam_t_bending_moment.md)
    
    > 0.1.0: MAPDL results supported.
- [beam\_t\_shear\_force](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/beam_t_shear_force.md)
    
    > 0.1.0: MAPDL results supported.
- [beam\_torsional\_moment](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/beam_torsional_moment.md)
    
    > 0.1.0: MAPDL results supported.
- [co\_energy](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/co_energy.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [contact\_fluid\_penetration\_pressure](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/contact_fluid_penetration_pressure.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [contact\_friction\_stress](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/contact_friction_stress.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [contact\_gap\_distance](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/contact_gap_distance.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [contact\_penetration](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/contact_penetration.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [contact\_pressure](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/contact_pressure.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [contact\_sliding\_distance](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/contact_sliding_distance.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [contact\_status](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/contact_status.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [contact\_surface\_heat\_flux](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/contact_surface_heat_flux.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [contact\_total\_stress](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/contact_total_stress.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [coordinate\_system](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/coordinate_system.md)
    
    > 0.0.1: Output pin 0 documentation update.
- [creep\_strain\_energy\_density](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/creep_strain_energy_density.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [displacement](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/displacement.md)
    
    > 1.0.0: Modal coordinates from RFRQ, RDSP and DSUB files can't be extracted through displacement operator anymore, user can use modal\_coordinate operator instead.
- [elastic\_strain](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/elastic_strain.md)
    
    > 0.1.0: Add pin eExtendMidNodesPin to add/remove mid-nodes when averaging from ElementalNodal to Nodal. Default:True
- [elastic\_strain\_energy\_density](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/elastic_strain_energy_density.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [elastic\_strain\_eqv](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/elastic_strain_eqv.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [elastic\_strain\_intensity](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/elastic_strain_intensity.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [elastic\_strain\_max\_shear](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/elastic_strain_max_shear.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [elastic\_strain\_principal\_1](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/elastic_strain_principal_1.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [elastic\_strain\_principal\_2](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/elastic_strain_principal_2.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [elastic\_strain\_principal\_3](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/elastic_strain_principal_3.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [electric\_field](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/electric_field.md)
    
    > 0.1.0: Add pin eExtendMidNodesPin to add/remove mid-nodes when averaging from ElementalNodal to Nodal. Default:True
- [electric\_flux\_density](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/electric_flux_density.md)
    
    > 0.1.0: Add pin eExtendMidNodesPin to add/remove mid-nodes when averaging from ElementalNodal to Nodal. Default:True
- [electric\_potential](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/electric_potential.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [element\_centroids](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/element_centroids.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [element\_nodal\_forces](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/element_nodal_forces.md)
    
    > 0.1.0: Add pin eExtendMidNodesPin to add/remove mid-nodes when averaging from ElementalNodal to Nodal. Default:True
- [element\_orientations](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/element_orientations.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [elemental\_heat\_generation](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/elemental_heat_generation.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [elemental\_mass](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/elemental_mass.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [elemental\_volume](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/elemental_volume.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [equivalent\_mass](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/equivalent_mass.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [eqv\_stress\_parameter](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/eqv_stress_parameter.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [gasket\_inelastic\_closure](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/gasket_inelastic_closure.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [gasket\_stress](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/gasket_stress.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [gasket\_thermal\_closure](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/gasket_thermal_closure.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [heat\_flux](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/heat_flux.md)
    
    > 0.1.0: Add pin eExtendMidNodesPin to add/remove mid-nodes when averaging from ElementalNodal to Nodal. Default:True
- [hydrostatic\_pressure](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/hydrostatic_pressure.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [incremental\_energy](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/incremental_energy.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [kinetic\_energy](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/kinetic_energy.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [magnetic\_field](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/magnetic_field.md)
    
    > 0.1.0: Add pin eExtendMidNodesPin to add/remove mid-nodes when averaging from ElementalNodal to Nodal. Default:True
- [magnetic\_flux\_density](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/magnetic_flux_density.md)
    
    > 0.1.0: Add pin eExtendMidNodesPin to add/remove mid-nodes when averaging from ElementalNodal to Nodal. Default:True
- [magnetic\_scalar\_potential](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/magnetic_scalar_potential.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [magnetic\_vector\_potential](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/magnetic_vector_potential.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [mapdl.pres\_to\_field](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/mapdl.pres_to_field.md)
    
    > 0.0.1: Fix crash caused by invalid iterator when reading shell data.
- [nmisc](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/nmisc.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [num\_surface\_status\_changes](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/num_surface_status_changes.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [plastic\_state\_variable](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/plastic_state_variable.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [plastic\_strain](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/plastic_strain.md)
    
    > 0.1.0: Add pin eExtendMidNodesPin to add/remove mid-nodes when averaging from ElementalNodal to Nodal. Default:True
- [plastic\_strain\_energy\_density](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/plastic_strain_energy_density.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [plastic\_strain\_eqv](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/plastic_strain_eqv.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [plastic\_strain\_intensity](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/plastic_strain_intensity.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [plastic\_strain\_max\_shear](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/plastic_strain_max_shear.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [plastic\_strain\_principal\_1](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/plastic_strain_principal_1.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [plastic\_strain\_principal\_2](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/plastic_strain_principal_2.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [plastic\_strain\_principal\_3](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/plastic_strain_principal_3.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [poynting\_vector\_surface](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/poynting_vector_surface.md)
    
    > 0.0.1: Fix bug in memory allocation for some local variables participating in interpolation at integration points.
- [pressure](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/pressure.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [raw\_displacement](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/raw_displacement.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [raw\_reaction\_force](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/raw_reaction_force.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [recombine\_harmonic\_indeces\_cyclic](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/recombine_harmonic_indeces_cyclic.md)
    
    > 0.1.0: Addition of is\_constant pin
- [remove\_rigid\_body\_motion](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/remove_rigid_body_motion.md)
    
    > 0.0.1: Replace vector of pointers with array of objects to prevent memory leaks
- [remove\_rigid\_body\_motion\_fc](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/remove_rigid_body_motion_fc.md)
    
    > 0.0.1: Replace vector of pointers with array of objects to prevent memory leaks
- [result\_provider](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/result_provider.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were only performed if the requested result was a 3D vector or a symmetrical 3x3 matrix.
- [smisc](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/smisc.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [state\_variable](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/state_variable.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [stiffness\_matrix\_energy](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/stiffness_matrix_energy.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [stress](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/stress.md)
    
    > 0.1.0: Add pin eExtendMidNodesPin to add/remove mid-nodes when averaging from ElementalNodal to Nodal. Default:True
- [stress\_intensity](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/stress_intensity.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [stress\_max\_shear](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/stress_max_shear.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [stress\_principal\_1](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/stress_principal_1.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [stress\_principal\_2](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/stress_principal_2.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [stress\_principal\_3](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/stress_principal_3.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [stress\_ratio](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/stress_ratio.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [stress\_von\_mises](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/stress_von_mises.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [structural\_temperature](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/structural_temperature.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [swelling\_strains](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/swelling_strains.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [temperature](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/temperature.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [temperature\_grad](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/temperature_grad.md)
    
    > 0.1.0: Add pin eExtendMidNodesPin to add/remove mid-nodes when averaging from ElementalNodal to Nodal. Default:True
- [thermal\_dissipation\_energy](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/thermal_dissipation_energy.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [thermal\_strain](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/thermal_strain.md)
    
    > 0.1.0: Add pin eExtendMidNodesPin to add/remove mid-nodes when averaging from ElementalNodal to Nodal. Default:True
- [thermal\_strain\_principal\_1](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/thermal_strain_principal_1.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [thermal\_strain\_principal\_2](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/thermal_strain_principal_2.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [thermal\_strain\_principal\_3](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/thermal_strain_principal_3.md)
    
    > 1.0.0: bool\_rotate\_to\_global pin removed for server versions &gt;25.2. An error is raised if connected.
- [thermal\_strains\_eqv](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/thermal_strains_eqv.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [thickness](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/thickness.md)
    
    > 1.0.0: This operator had previously the bool\_rotate\_to\_global pin exposed and set as True while rotations to global were not performed and results were output in the Solution Coordinate System.
- [torque](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/result/torque.md)
    
    > 0.1.0: Fields container supported on pin 1. Pin 1 name changed.
    > 
    > 1.0.0: The torque unit is now kept from the input units and not converted to N\*m.

#### scoping

- [rescope](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/scoping/rescope.md)
    
    > 0.1.0: Performance improvement.
- [rescope\_custom\_type\_field](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/scoping/rescope_custom_type_field.md)
    
    > 0.1.0: Performance improvement.
- [rescope\_fc](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/scoping/rescope_fc.md)
    
    > 0.1.0: Performance improvement.
- [rescope\_property\_field](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/scoping/rescope_property_field.md)
    
    > 0.1.0: Performance improvement.
- [transpose](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/scoping/transpose.md)
    
    > 0.1.0: Improvement of performance
    > 
    > 0.1.1: Error with license

#### serialization

- [csv\_to\_field](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/serialization/csv_to_field.md)
    
    > 1.0.0: Fixed issue while reading csv with multiple fields and common time id between fields.
- [field\_to\_csv](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/serialization/field_to_csv.md)
    
    > 1.0.0: Fixed issue while writing csv with multiple fields and common time id between fields.

#### utility

- [extract\_scoping](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/utility/extract_scoping.md)
    
    > 0.0.1: Error with license
- [html\_doc](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/utility/html_doc.md)
    
    > 0.1.0: Show operator version and changelog.
- [ints\_to\_scoping](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/utility/ints_to_scoping.md)
    
    > 0.1.0: Add input pin 2 to specify an upper bound to create a scoping for a given range (taking single input in pin 0 as the lower bound).
- [producer\_consumer\_for\_each](https://developer.ansys.com/docs/dpf-framework-2026-r1/operator-specifications/utility/producer_consumer_for_each.md)
    
    > 0.1.0: Addition of events to monitor the status of the operator.
    > 
    > 0.2.0: Moving event of progress bar at the beginning of the loop and changing input stream.

### Deleted operators

#### gasket\_deformation

#### gasket\_deformation\_X

#### gasket\_deformation\_XY

#### gasket\_deformation\_XZ

#### nodal\_moment