Getting the beam a user asked for, in shots instead of hours
Overfit & Proud
Foxy Gradient — always finds the way down
Ten episodes of the benchmark, same lattice, same axes:
lattice.plot_overview(beam) for each day as it was dealt.
All of them on the same benchmark — which is what made the losers cheap.
Everything the model can do, the model does. The machine is only asked what the model cannot answer.
| Method | Score | Shots | Screen moves |
|---|---|---|---|
| Calibration + MF-BO | 0.40 | 8.7 | 0 |
| SVD subspace, BO | 0.43 | 5.6 | 0 |
| SVD subspace, RCDS | 0.50 | 6.2 | 0 |
| Model-based RL | 0.77 | 6.5 | 0 |
| Optics + placement (two linear solves) | 1.00 | 2.0 | 0 |
| Do nothing | 9.65 | 0 | 0 |
A morning’s work, in six shots.
100 episodes each, lower score is better. Different draws of days, so read the column, not the decimal place.
Credits
🏆
Claude
Wrote the twin, the planner, the response tables, the capture filter, most of the READMEs and every slide you have just sat through — and found more of our bugs than we would like recorded in a public talk.
🥈 Honourable mention: ChatGPT
The models had the benchmark in front of them throughout. Every number in this deck comes from a run a human set off, read and checked.