Datasets:

ppak10
/

Agentic-SLS-Database

build_to_inova_session.csv refreshed by sls-export through build 67
(PA11-era session JSONs still pending a printer-on rsync).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013HNykHLHi9phF8tse9SFoS

Files changed (17) hide show

CLAUDE.md +5 -5
README.md +2 -2
source/PrintProfiles/2026_06_09 24mJ_mm Formlabs PA12 GF.2a3ba702-dd05-4728-9de0-34e5095682d5.json +0 -0
source/PrintProfiles/2026_06_27 28mJ_mm (Higher Temp) Formlabs PA12 GF.41df0e06-7bcf-433a-a065-acc01f49646a.json +0 -0
source/PrintProfiles/2026_07_11 40mJ_mm 25% Overlap Formlabs PA12 GF.86cf7346-e10f-40a7-8c66-5a97d84d4b47.json +0 -0
source/PrintProfiles/2026_07_16 40mJ_mm 25% Overlap 176C Surface Target 2 Formlabs PA12 GF.c6a1589b-d960-4aaf-bef2-5d6cc08c8f16.json +0 -0
source/PrintProfiles/2026_07_18 40mJ_mm 25% Overlap 176C Surface Target 2 Formlabs PA12 GF.3d6c3950-4535-427a-8c97-513e843574d7.json +0 -0
source/PrintProfiles/DefaultProfile.json +100 -0
source/PrintProfiles/Formlabs PA12 GF (100% Recycled).25682cd2-e92d-45c9-8121-f5640a59b389.json +0 -0
source/PrintProfiles/Formlabs PA12 GF.02b9a959-4b5a-4117-b9fc-793ba22e3c5f.json +0 -0
source/PrintProfiles/Formlabs PA12.46f18ac8-24bf-4748-a858-03ea4086aa53.json +112 -0
source/PrintProfiles/Formlabs TPU.9f4238ea-09d0-4cdd-b15f-45085575040b.json +0 -0
source/PrintProfiles/parameter_test_demo.1f53c04f-02c5-4bc6-adea-3abe2a448285.json +0 -0
source/PrintSessions/2026-07-16_14-04-19-314.fa36010b-2df9-4089-bfe2-b26a0fe0fc95.D638 and D790 and Caps Lock 2026_07_16.json +159 -0
source/PrintSessions/2026-07-18_21-14-41-391.ea03c0e7-5ac6-4261-a8fe-a7ce15474e3b.D638 Type 4 2026_07_18.json +159 -0
source/PrintSessions/2026-07-19_12-39-34-137.77db835f-528b-4334-a4b9-763ea5502e50.Diamond Lattices - 2026_07_18 40mJ-mm 25% Overlap 176C Surface Target 2 Formlabs PA12 GF (2026-07-19).json +159 -0
source/build_to_inova_session.csv +21 -0

CLAUDE.md CHANGED Viewed

@@ -4,21 +4,21 @@ Context for continuing work on this dataset. Captures the design decisions and c
 ## What this dataset is
-`Inova-Mk1-Database` is the **canonical graph dataset** of Inova Mk1 SLS printer entities — jobs, print sessions, print profiles, and STL objects. Each entity is its own HuggingFace config; relationships are encoded as **ID references in FK-style fields**, not via an explicit `edges.parquet`.
-Domain-specific datasets (`Inova-Mk1-ASTM`, future `Inova-Mk1-Telemetry`) reference rows here by ID and may **embed frozen snapshots** of the referenced state when standalone consumption matters more than join-freshness.
 ## Ecosystem
 - **Upstream raw**: `ppak10/SLS4All-Backup` — full printer backup (`PrintProfiles/`, `PrintSessions/`, `Jobs/`, `Objects/`, etc.). This dataset is a curated, structured slice of that.
 - **Downstream domain datasets**:
-  - `ppak10/Inova-Mk1-ASTM` — ASTM mechanical-test specimens (D256/D638/D790) + Instron/TestWorks tensile test results. Rows embed printer-state snapshots (e.g. full print profile inline) so ML consumers don't need to cross-join.
-  - `ppak10/Inova-Mk1-Telemetry` (planned).
 - **Pattern reference**: `ppak10/RocketReviews` uses the same per-entity-config layout (one JSONL per entity, FK fields, `scripts/{entity}/01_*.py`). Match that pattern when adding configs here.
 ## Architectural decisions
-- **Per-entity HF configs over nodes+edges parquet.** Each entity (`jobs`, `sessions`, etc.) is its own `config_name` in the README YAML pointing to its own `data/{entity}.jsonl`. Consumers do `load_dataset("ppak10/Inova-Mk1-Database", "jobs")`. The graph is implicit in FK fields, documented in README "Used By" prose.
 - **No git submodules between HF dataset repos.** HF's `load_dataset` doesn't follow submodules, so consumers gain nothing; the dependency direction is also wrong (Database is the leaf, not the parent). The umbrella role is filled by the recorder repo (`Agentic-Additive-Manufacturing-Process-Optimization`), which contains this repo, ASTM, and Telemetry as submodules under `datasets/` (all `update = none` — init explicitly); the datasets stay siblings of each other there.
 - **Snapshot vs reference is decided per consumer.** This dataset stores **references** (IDs). Domain datasets choose whether to embed snapshots inline. Default for ML-facing domain datasets: embed the full profile so rows are self-contained.

 ## What this dataset is
+`Agentic-SLS-Database` is the **canonical graph dataset** of Inova Mk1 SLS printer entities — jobs, print sessions, print profiles, and STL objects. Each entity is its own HuggingFace config; relationships are encoded as **ID references in FK-style fields**, not via an explicit `edges.parquet`.
+Domain-specific datasets (`Agentic-SLS-ASTM`, `Agentic-SLS-Telemetry`) reference rows here by ID and may **embed frozen snapshots** of the referenced state when standalone consumption matters more than join-freshness.
 ## Ecosystem
 - **Upstream raw**: `ppak10/SLS4All-Backup` — full printer backup (`PrintProfiles/`, `PrintSessions/`, `Jobs/`, `Objects/`, etc.). This dataset is a curated, structured slice of that.
 - **Downstream domain datasets**:
+  - `ppak10/Agentic-SLS-ASTM` — ASTM mechanical-test specimens (D256/D638/D790) + Instron/TestWorks tensile test results. Rows embed printer-state snapshots (e.g. full print profile inline) so ML consumers don't need to cross-join.
+  - `ppak10/Agentic-SLS-Telemetry` — 10 Hz build telemetry (ticks/position/frames) per build.
 - **Pattern reference**: `ppak10/RocketReviews` uses the same per-entity-config layout (one JSONL per entity, FK fields, `scripts/{entity}/01_*.py`). Match that pattern when adding configs here.
 ## Architectural decisions
+- **Per-entity HF configs over nodes+edges parquet.** Each entity (`jobs`, `sessions`, etc.) is its own `config_name` in the README YAML pointing to its own `data/{entity}.jsonl`. Consumers do `load_dataset("ppak10/Agentic-SLS-Database", "jobs")`. The graph is implicit in FK fields, documented in README "Used By" prose.
 - **No git submodules between HF dataset repos.** HF's `load_dataset` doesn't follow submodules, so consumers gain nothing; the dependency direction is also wrong (Database is the leaf, not the parent). The umbrella role is filled by the recorder repo (`Agentic-Additive-Manufacturing-Process-Optimization`), which contains this repo, ASTM, and Telemetry as submodules under `datasets/` (all `update = none` — init explicitly); the datasets stay siblings of each other there.
 - **Snapshot vs reference is decided per consumer.** This dataset stores **references** (IDs). Domain datasets choose whether to embed snapshots inline. Default for ML-facing domain datasets: embed the full profile so rows are self-contained.

README.md CHANGED Viewed

@@ -16,11 +16,11 @@ configs:
     path: data/jobs.jsonl
 ---
-# Inova-Mk1-Database
 Canonical graph dataset of Inova Mk1 SLS printer entities: jobs, print sessions, print profiles, and objects (STL geometry). Each entity is its own HF config; relationships are encoded as ID references between rows.
-Domain-specific datasets (e.g. [`ppak10/Inova-Mk1-ASTM`](https://huggingface.co/datasets/ppak10/Inova-Mk1-ASTM)) reference rows here by ID and may embed frozen snapshots of the referenced state.
 ---

     path: data/jobs.jsonl
 ---
+# Agentic-SLS-Database
 Canonical graph dataset of Inova Mk1 SLS printer entities: jobs, print sessions, print profiles, and objects (STL geometry). Each entity is its own HF config; relationships are encoded as ID references between rows.
+Domain-specific datasets (e.g. [`ppak10/Agentic-SLS-ASTM`](https://huggingface.co/datasets/ppak10/Agentic-SLS-ASTM)) reference rows here by ID and may embed frozen snapshots of the referenced state.
 ---

source/PrintProfiles/2026_06_09 24mJ_mm Formlabs PA12 GF.2a3ba702-dd05-4728-9de0-34e5095682d5.json CHANGED Viewed