Inova-Mk1-Telemetry

Time-aligned printer-state recordings from Inova Mk1 SLS print runs. One row per 10 Hz tick of the recorder's /state/snapshot poll, with the full sensor state (~64 columns: temperatures, position, power, lights) on every row, the nearest camera frame paths attached when one fell in the prior 100 ms window, and any 1 kHz position-stream samples from that window collected as a nested list.

Builds are denormalized into every row, so each parquet file is self-sufficient for ML — no joins needed for build context. A print_profile_id references ppak10/Inova-Mk1-Database when the build's printProfileName matches a known PrintProfile.Name.

from datasets import load_dataset
ticks = load_dataset("ppak10/Inova-Mk1-Telemetry", split="train")
# ticks now has rows like:
#   {build_id, ts, job_name, ..., powderBed.temp.current, laser.power, ...,
#    frame_chamber: "26/...jpg" | None, position_hf_burst: [...]}

---

Row shape

Each row is one moment in time (a single 10 Hz tick). 80+ columns:

Group	Columns	Notes
Build context (denormalized)	build_id, job_name, started_at, ended_at, phase, print_profile_id, print_profile_name, inova_session_id	Same value on every row in a given parquet file. inova_session_id is null until the upstream build_to_inova_session.csv is filled in by hand.
Tick timestamp	ts (timestamp[us, UTC])	The respondedAt field on the /state/snapshot frame.
Position (10 Hz)	positions.position.{x,y,z1,z2,r}	Stage position at the tick, microns (firmware native; e.g. z1 = 47272.79 is 47.27 mm). Always present.
Lights	lights.lights.{enabled,count}
Power (W)	{laser,fanGalvo,buzzer,laserSafety,io-en,wd-en,wd-in}.power, powerman.power.{current,required,max}	Per-component power draw and the overall manager state.
Temperature (°C)	{powderBed,printBed}.temp.{current,average,target}, {powderChamber1..4,printChamber1..4}.temp.{current,average,target}, {quadrant1..4,surface,surfaceAvg,surfaceMin,surfaceMax,testTemp1}.temp.{current,average}	~51 columns. All firmware temperatures in °C.
Frame paths	frame_chamber, frame_galvo, frame_thermal	Nullable. Path is relative to the upstream recorder repo's data/frames/ — this dataset does not ship the 81 GB of image bytes. Null when no frame of that kind was captured in the 100 ms window before the tick.
Position burst	position_hf_burst	A list<struct<ts_offset_ms, x, y, z1, z2, r, has_homed>>. Captures any 1 kHz position-stream events that fell in (tick_ts - 100 ms, tick_ts]. Empty list when no motion was happening.

Files

data/ticks/{build_id}.parquet      # one file per build that had telemetry

10 builds had recorded telemetry; very-short failed-heating builds (~12–38 s, no rows) produce no file. The HF glob data/ticks/*.parquet loads everything across builds.

What's lost vs the raw exporter format

This dataset is tick-anchored, not strict-outer-join. Compared to the upstream flat exports, three things are reduced:

• Position resolution between motion bursts: the 1 kHz position_hf stream is preserved during motion (via the per-tick position_hf_burst list) but not as standalone rows between ticks. If you need the raw 1 kHz timeline outside the 100 ms windows, fall back to the upstream position_hf/{build_id}.parquet.
• Sparse-stream events without telemetry: there is no row for a frame timestamp that doesn't fall near a 10 Hz tick, and no row for sparse events (build phase transitions, etc.). Treat this dataset as "what was the state at each tick", not "every recorded event".
• plotter_commands: not exposed yet — historical builds predate the recorder feature, and the table is empty.

Joining back to Inova-Mk1-Database

Each row carries print_profile_id resolved by matching the build's printProfileName (from build_start event payload) against PrintProfile.Name in Inova-Mk1-Database/source/PrintProfiles/. If no match exists, print_profile_id is null and print_profile_name is preserved as a breadcrumb (typical when a new profile hasn't landed in Inova-Mk1-Database yet).

A planned authoritative inova_session_id UUID join will replace the fuzzy fallback once the upstream Agentic-Additive-Manufacturing-Process-Optimization/data/exports/build_to_inova_session.csv has been filled in.

Upstream

The raw data lives in the sibling repository Agentic-Additive-Manufacturing-Process-Optimization. Its scripts/export.py writes flat files under data/exports/. This dataset reads from there directly via a sibling-folder relative path — no live database connection required.

Regenerate

uv run scripts/ticks/01_extract.py            # all builds with telemetry
uv run scripts/ticks/01_extract.py 13 26      # specific build ids