Node reference

How to use Data Chart node in Oraphim

Use the Data Chart node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID motion.chart.data.

Updated August 28, 2026

How to use Data Chart node in Oraphim

Type ID: motion.chart.data
Category: Generator

What this node does

The Data Chart node is registered in Oraphim's Generator category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 5 sockets and 31 properties for this node. Its main registered inputs are Color, Data; its main outputs are Geometry, Metadata, Color. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Color in_color Image
Data in_data Metadata

Outputs

Socket Key Type
Geometry out_geometry Geometry3D
Metadata out_metadata Metadata
Color out_color Image

Controls

Control Key Type Group Registry default
Chart Type chartType String Chart Bar
Title title String Data 0.0
Data JSON dataJson String Data 0.0
Chart Width width Float Layout 1280.0
Chart Height height Float Layout 560.0
Depth depth Float Layout 28.0
Orientation orientation String Layout Vertical
Sort Descending sortDescending Bool Layout 0.0
Item Gap itemGap Float Layout 36.0
Baseline baselineMode String Baseline Zero
Custom Value baselineValue Float Baseline 0.0
Show Baseline showBaseline Bool Baseline 1.0
Baseline Width baselineThickness Float Baseline 3.0
Auto Range autoRange Bool Scale 1.0
Minimum minimum Float Scale 0.0
Maximum maximum Float Scale 100.0
Stroke Width strokeWidth Float Style 18.0
Point Radius pointRadius Float Style 18.0
Red colorR Float Color 0.2199999988079071
Green colorG Float Color 0.7200000286102295
Blue colorB Float Color 1.0
Alpha colorA Float Color 1.0
Inner Radius donutInnerRatio Float Style 0.5799999833106995
Line Shape lineInterpolation String Line Smooth
Smoothness curveSubdivisions Int Line 8.0
Moving Endpoint showEndpoint Bool Line 1.0
Endpoint Size endpointRadius Float Line 20.0
Reveal Easing easing String Animation Cinematic
Overshoot overshoot Float Animation 0.05999999865889549
Reveal reveal Float Animation 1.0
Stagger stagger Float Animation 0.07999999821186066

How to use it

  1. Add Data Chart from node search. Use motion.chart.data when you need the exact registry entry.
  2. Connect a compatible Image source to Color. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Chart Type, Title, Data JSON 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 Data Chart. Feed a compatible source into Color. Change Chart Type 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.

Return to the complete Oraphim node reference.