How to use Random Distribution node in Oraphim

Type ID: motion.random.distribution
Category: Utility

What this node does

The Random Distribution 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 6 sockets and 11 properties for this node. Its main registered inputs are Index; its main outputs are Value, Normalized, Integer. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Index	in_index	Int

Outputs

Socket	Key	Type
Value	out_value	Float
Normalized	out_normalized	Float
Integer	out_integer	Int
Event	out_event	Bool
Valid	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Distribution	distribution	String	Distribution	Uniform
Seed	seed	Int	Random	1.0
Index	index	Int	Random	0.0
Channel	channel	Int	Random	0.0
Minimum	minimum	Float	Range	0.0
Maximum	maximum	Float	Range	1.0
Mean	mean	Float	Normal	0.0
Standard Deviation	standardDeviation	Float	Normal	1.0
Rate Lambda	lambda	Float	Exponential	1.0
Probability	probability	Float	Bernoulli	0.5
Clamp To Range	clamp	Bool	Output	0.0

How to use it

1. Add Random Distribution from node search. Use motion.random.distribution when you need the exact registry entry.
2. Connect a compatible Int source to Index. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Distribution, Seed, Index first so you can see the node's effect in isolation.
4. Route Value (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 Random Distribution. Feed a compatible source into Index. Change Distribution away from its registry default and compare the result. Connect Value 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

• Stable Random — motion.random.stable
• 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.