How to use Attribute Map node in Oraphim

Type ID: motion.geometry.attribute_map
Category: Utility

What this node does

The Attribute Map 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 5 properties for this node. Its main registered inputs are Geometry, Value; its main outputs are Geometry, Metadata. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Geometry	in_geometry	Geometry3D
Value	in_value	Float

Outputs

Socket	Key	Type
Geometry	out_geometry	Geometry3D
Metadata	out_metadata	Metadata

Controls

Control	Key	Type	Group	Registry default
Source Attribute	sourceAttribute	String	Attribute	index
Target Attribute	targetAttribute	String	Attribute	scale
Domain	domain	String	Attribute	0.0
Blend Mode	blendMode	String	Map	0.0
Strength	strength	Float	Map	1.0

How to use it

1. Add Attribute Map from node search. Use motion.geometry.attribute_map when you need the exact registry entry.
2. Connect a compatible Geometry3D source to Geometry. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Source Attribute, Target Attribute, Domain first so you can see the node's effect in isolation.
4. Route Geometry (Geometry3D) 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 Attribute Map. Feed a compatible source into Geometry. Change Source Attribute away from its registry default and compare the result. Connect Geometry 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

• Curve Primitive — motion.geometry.curve_primitive
• Primitive — motion.geometry.primitive
• Boolean Math — motion.logic.boolean
• Clamp — motion.value.clamp
• Compare — motion.logic.compare

Return to the complete Oraphim node reference.