Back to corpus
technical noteexperiment writeup candidatescore 28
Development Runbook
```bash python training/trainers/train_rps.py \ --config training/experiments/exp_baseline.yaml \ --epochs 50 \ --checkpoint-dir training/checkpoints/rps ```
Full HTML reader
Read the full artifact
Extracted abstract or opening context
**What it does**: 1. Replays synthetic session at 100 Hz 2. Encodes → RPS → GRU → controls 3. Emits MIDI CC to IAC Driver 4. Logs controls to `data/processed/sim_output.parquet`
**What it does**: 1. Connects to mocopi suit (UDP) 2. Real-time encoding → controls 3. Emits MIDI CC to Strudel
1. Open https://strudel.cc 2. Paste contents of `sound/strudel/patches/core_patch.strudel.md` 3. Enable Web MIDI → select "IAC Driver Bus 1" 4. Click "Run"
**Flow**: 1. Starts Strudel embed (if configured) 2. Runs `realtime_loop.py` with test session 3. Monitors MIDI traffic 4. Generates evaluation report
**Fix**: 1. Open Audio MIDI Setup 2. Enable IAC Driver 3. Restart Python interpreter
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.