Build the laboratory corpus with the Scenario Builder #7
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
All 14 scenario descriptors in
docs/laboratory/corpus.jsonstill wait for save files. That is why these STATUS gates were closed as "decided" rather than passed:12-reproducible12-held-out12-cross-scenario13-non-inferiorityand13-superioritydepend on ready saves tooThe Scenario Builder can now generate forces on empty scenarios: 2,000 units spawned and read back in 26.8 s live (
docs/verification/SCENARIO-BUILDER-LIVE-2026-10-05.md).Proposal:
tools/lab.pycapture/replay and the held-out evaluation against them.Found in the 2026-10-13 review (PR #1).
Lab run status, 2026-10-17
Steps 1 and 2 are done. All 14 corpus scenarios are built and
ready, with their SHA-256 indocs/laboratory/corpus.json.Step 3 is partly done. I ran live trials with
tools/lab_run.pyon CMOnet 0.7.87–0.7.97, using the expert-commander flow r72. Nine of the 14 scenarios have a completed trial:Five scenarios have no completed trial yet:
restart_cmonetfault. The runner now connects the new process (#149).Fixes that came out of the runs: #146–#155, plus tester fixes ef27991 (tester issue 2) and bfcbde0. Tester issue 6 is still open.
This issue stays open until the five remaining trials have run on the current version.
🤖 Generated with Claude Code