Node reference
How to use Field Average node in Oraphim
Use the Field Average node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.field_average.
Updated August 28, 2026How to use Field Average node in Oraphim
Type ID: geometry.field_average
Category: Utility
What this node does
The Field Average node is registered in Oraphim's Utility category and performs the graph operation represented by its sockets and controls below.
The current Oraphim runtime registers 4 sockets and 4 properties for this node. Its main registered inputs are Value, Group ID; its main outputs are Mean, Median. The tables below are generated from the runtime registry rather than a handwritten approximation.
Inputs
| Socket | Key | Type |
|---|---|---|
| Value | value |
Float |
| Group ID | groupIndex |
Int |
Outputs
| Socket | Key | Type |
|---|---|---|
| Mean | mean |
Float |
| Median | median |
Float |
Controls
| Control | Key | Type | Group | Registry default |
|---|---|---|---|---|
| Value | value |
Float |
Inputs | 0.0 |
| Group ID | groupIndex |
Int |
Inputs | 0.0 |
| Data Type | data_type |
String |
Node | 0.0 |
| Domain | domain |
String |
Node | 0.0 |
How to use it
- Add Field Average from node search. Use
geometry.field_averagewhen you need the exact registry entry. - Connect a compatible
Floatsource to Value. Add the other inputs only when the operation needs them. - Start with the registry defaults and adjust Value, Group ID, Data Type first so you can see the node's effect in isolation.
- Route Mean (
Float) into a compatible downstream node, viewer, or output path. - Preview a representative frame, change one input/control at a time, and save/reopen reusable graphs to verify persistence.
Practical example
Create a small test graph with Field Average. Feed a compatible source into Value. Change Value away from its registry default and compare the result. Connect Mean to a compatible downstream stage so the result is visible. Keeping this test graph small makes socket-type, context, and parameter mistakes easier to diagnose before the node is used in a production graph.
Troubleshooting
- If a connection is rejected, compare the exact socket data types in the tables above; Oraphim graph connections are typed.
- If the result looks unchanged, confirm this node is on the active path to the viewer/output and that the expected graph/resource is selected.
- If a control is unavailable, check required inputs and whether the property belongs to an internal or mode-dependent group.
- If a saved graph behaves differently later, reopen it and verify node identity, connections, and edited property values before rendering.
Related nodes
- Accumulate Field —
geometry.accumulate_field - Evaluate at Index —
geometry.evaluate_at_index - Field Min & Max —
geometry.field_min_and_max - Field to List —
geometry.field_to_list - Field Variance —
geometry.field_variance
Return to the complete Oraphim node reference.