## On this page

  

 

 # result:nodal moment

 Last update: 31.07.2026 

**Version: 0.0.0**

## Description

Read/compute nodal moment by calling the readers defined by the datasources.

## Inputs

InputNameExpected type(s)Description**Pin 0**time\_scoping[`scoping`](../../core-concepts/dpf-types.md#scoping), [`int32`](../../core-concepts/dpf-types.md#standard-types), [`vector<int32>`](../../core-concepts/dpf-types.md#standard-types), [`double`](../../core-concepts/dpf-types.md#standard-types), [`field`](../../core-concepts/dpf-types.md#field), [`vector<double>`](../../core-concepts/dpf-types.md#standard-types)time/freq values (use doubles or field), time/freq set ids (use ints or scoping) or time/freq step ids (use scoping with TimeFreq\_steps location) required in output. To specify time/freq values at specific load steps, put a Field (and not a list) in input with a scoping located on "TimeFreq\_steps". Linear time freq intrapolation is performed if the values are not in the result files and the data at the max time or freq is taken when time/freqs are higher than available time/freqs in result files. To get all data for all time/freq sets, connect an int with value -1.**Pin 1**mesh\_scoping[`scopings_container`](../../core-concepts/dpf-types.md#scopings-container), [`scoping`](../../core-concepts/dpf-types.md#scoping)nodes or elements scoping required in output. The output fields will be scoped on these node or element IDs. To figure out the ordering of the fields data, look at their scoping IDs as they might not be ordered as the input scoping was. The scoping's location indicates whether nodes or elements are asked for. Using scopings container allows you to split the result fields container into domains**Pin 2**fields\_container[`fields_container`](../../core-concepts/dpf-types.md#fields-container)Fields container already allocated modified inplace**Pin 3**streams\_container[`streams_container`](../../core-concepts/dpf-types.md#streams-container)result file container allowed to be kept open to cache data**Pin 4**   
Requireddata\_sources[`data_sources`](../../core-concepts/dpf-types.md#data-sources)result file path container, used if no streams are set**Pin 5**bool\_rotate\_to\_global[`bool`](../../core-concepts/dpf-types.md#standard-types)if true the field is rotated to global coordinate system (default true). Please check your results carefully if 'false' is used for Elemental or ElementalNodal results averaged to the Nodes when adjacent elements do not share the same coordinate system, as results may be incorrect.**Pin 7**mesh[`abstract_meshed_region`](../../core-concepts/dpf-types.md#meshed-region), [`meshes_container`](../../core-concepts/dpf-types.md#meshes-container)prevents from reading the mesh in the result files## Outputs

OutputNameExpected type(s)Description**Pin 0**fields\_container[`fields_container`](../../core-concepts/dpf-types.md#fields-container)## Configurations

NameExpected type(s)Default valueDescription**mutex**[`bool`](../../core-concepts/dpf-types.md#standard-types)falseIf this option is set to true, the shared memory is prevented from being simultaneously accessed by multiple threads.**num\_threads**[`int32`](../../core-concepts/dpf-types.md#standard-types)0Number of threads to use to run in parallel**run\_in\_parallel**[`bool`](../../core-concepts/dpf-types.md#standard-types)trueLoops are allowed to run in parallel if the value of this config is set to true.## Scripting

**Category**: result

**Plugin**: core

**Scripting name**: nodal\_moment

**Full name**: result.nodal\_moment

**Internal name**: M

**License**: None

## Changelog

- Version 0.0.0: Initial release.