OVERHEAD CAMERA
t 0.0 s
Loading frames
0.0 / 0.0 s
The paper's results come from these session files. This page reads them as they are, from the sessions/ folder beside it: the prompt each model received, the code it wrote, its reasoning, the overhead camera frames of every run, the robot's console log and its telemetry.
| Source | sessions/games/ |
|---|---|
| Games | — |
Outcome of each model on each game, as reported in §8 of the paper. One square per attempt. The photo is the last overhead frame of the deciding run. Select a cell to open it below.
exp_001 ran one attempt and was replaced eight minutes later by exp_002, which the harness names “Actual Opus”. The paper reports one Opus entry for Game 3, so exp_001 is shown but not scored.frames.json. Field crops each 1920 × 1080 frame to the middle 60% of its width, where the field sits. Full frame shows the file as recorded.console.log has no timestamps of its own. Line times come from the times the model's program printed ([ 12.3s], t=12.3, elapsed=12.3). A printed time that runs ahead of the lines after it, such as a deadline, is ignored. Lines in between are spaced evenly and marked ≈. The program starts its timer after it connects, so expect up to about a second of offset from the frame clock.telemetry_series.json holds about 4–5 samples per second. Position is wheel odometry relative to the start pose. It drifts and cannot see the robot being pushed. Speed is computed from consecutive positions. The camera panel plots only the detection the telemetry reports (ai_x, ai_y, ai_score), in the robot camera's 320 × 240 frame.input/prompt.txt into its tagged sections and shows the images from input/ that were attached. The checks at the top of that tab compare files byte for byte in your browser: trace.txt against the system prompt plus prompt.txt, <previous_code> against the previous attempt's output.txt, and the game description against the game's prompt.txt.