How to use Domain Size node in Oraphim

Type ID: geometry.attribute_domain_size
Category: Utility

What this node does

The Domain Size 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 8 sockets and 0 properties for this node. Its main registered inputs are Geometry; its main outputs are Point Count, Edge Count, Face Count. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Geometry	geometry	Geometry3D

Outputs

Socket	Key	Type
Point Count	pointCount	Int
Edge Count	edgeCount	Int
Face Count	faceCount	Int
Face Corner Count	faceCornerCount	Int
Spline Count	splineCount	Int
Instance Count	instanceCount	Int
Layer Count	layerCount	Int

Controls

This node has no registered editable properties; use its sockets and graph context.

How to use it

1. Add Domain Size from node search. Use geometry.attribute_domain_size 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 socket/context behavior first so you can see the node's effect in isolation.
4. Route Point Count (Int) 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 Domain Size. Feed a compatible source into Geometry. Connect Point Count 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

• Data Elements — geometry.data_elements
• Geometry Proximity — geometry.proximity
• Get List Item — geometry.list_get_item
• Image Info — geometry.image_info
• Index Switch — geometry.index_switch

Return to the complete Oraphim node reference.