How to use Normalize Values node in Oraphim

Type ID: motion.data.normalize
Category: Utility

What this node does

The Normalize Values 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 2 sockets and 3 properties for this node. Its main registered inputs are Value; its main outputs are Normalized. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Value	in_value	Float

Outputs

Socket	Key	Type
Normalized	out_value	Float

Controls

Control	Key	Type	Group	Registry default
Minimum	minValue	Float	Range	0.0
Maximum	maxValue	Float	Range	100.0
Clamp	clamp	Bool	Range	1.0

How to use it

1. Add Normalize Values from node search. Use motion.data.normalize when you need the exact registry entry.
2. Connect a compatible Float source to Value. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Minimum, Maximum, Clamp first so you can see the node's effect in isolation.
4. Route Normalized (Float) into a compatible downstream node, viewer, or output path.
5. 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 Normalize Values. Feed a compatible source into Value. Change Minimum away from its registry default and compare the result. Connect Normalized 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

• Attribute Map — motion.geometry.attribute_map
• Boolean Math — motion.logic.boolean
• Clamp — motion.value.clamp
• Compare — motion.logic.compare
• Curve Map — motion.value.curve

Return to the complete Oraphim node reference.