Back to corpus
technical noteexperiment writeup candidatescore 24
Data Capture - Current Verified Paths
This page documents what the current code can record. It does not claim that a specific training run has already consumed the data unless a run artifact is identified.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
This page documents what the current code can record. It does not claim that a specific training run has already consumed the data unless a run artifact is identified.
- schema version; - dimensionality; - timestamp; - frame number; - optional bar number; - optional track name; - optional track time; - 128D input; - four audio parameter groups; - seven camera scores; - cut timing; - pattern intensity and variation; - phrase lifecycle; - gesture probabilities; - phase; - regime; - calibration confidence; - latency.
The logger captures SAN's flat input and SAN output at runtime. It is useful for:
- replay analysis; - checking whether SAN output is flat or moving; - future supervised training; - comparing heuristic vs SAN-blended outputs; - correlating track metadata with body state.
- the current SAN weights were trained from this session; - the session was accepted into a training set; - a train/validation split exists; - the model improved; - Rekordbox gestures worked; - mocopi, watch, and camera were all active.
Promotion decision
What has to happen next
Attach run IDs, datasets, metrics, and reproduction commands.
Why this is not always a full paper yet
Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.