How to use Select Elements node in Oraphim

Type ID: geometry.select_elements
Category: Utility

What this node does

The Select Elements 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 14 sockets and 12 properties for this node. Its main registered inputs are Geometry, Mode, Filter Output; its main outputs are Geometry. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Geometry	geometry	Geometry3D
Mode	mode	String
Filter Output	filter	Bool
Probability	probability	Float
Every Nth	every	Int
Offset	offset	Int
Start	start	Int
End	end	Int
Center X	centerX	Float
Center Y	centerY	Float
Center Z	centerZ	Float
Radius	radius	Float
Seed	seed	Int

Outputs

Socket	Key	Type
Geometry	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Mode	mode	String	Inputs	Random
Filter Output	filter	Bool	Inputs	0.0
Probability	probability	Float	Inputs	0.5
Every Nth	every	Int	Inputs	2.0
Offset	offset	Int	Inputs	0.0
Start	start	Int	Inputs	0.0
End	end	Int	Inputs	0.0
Center X	centerX	Float	Inputs	0.0
Center Y	centerY	Float	Inputs	0.0
Center Z	centerZ	Float	Inputs	0.0
Radius	radius	Float	Inputs	1.0
Seed	seed	Int	Inputs	1.0

How to use it

1. Add Select Elements from node search. Use geometry.select_elements 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 Mode, Filter Output, Probability 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 Select Elements. Feed a compatible source into Geometry. Change Mode 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

• Geometry Proximity — geometry.proximity
• Image Info — geometry.image_info
• Sample Nearest Surface — geometry.sample_nearest_surface
• Attribute Statistic — geometry.attribute_statistic
• Data Elements — geometry.data_elements

Return to the complete Oraphim node reference.