wai-quantum: an optimisation stops and goes on to the same bytes #608

Merged

dcharlot merged 2 commits from wai/quantum-optimize-resume-2 into main 2026-11-04 10:26:30 -05:00

Conversation 0 Commits 2 Files changed 11 +601 -54

2026-11-03

Transaction Science

wai-quantum docs: the checkpoint example runs, and shows its claim ...

The page's --checkpoint example was a shell block marked neither runnable
nor norun, which the docs check refuses. It now runs: a whole run, the same
run stopped by --slice (exit 2) and gone on with, and cmp of the two answers,
so the page holds the command line to "the same bytes as a run that never
stopped", receipt and all.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

0636f34e20

• View at this point in history

2026-11-03 23:43:39 -05:00

Transaction Science

wai-quantum: an optimisation stops and goes on to the same bytes ...

A long optimisation ran to its end in one process or not at all; one
killed partway lost every step. The engine's optimiser now runs from a
checkpoint (engine::variational::optimize_resumable, call_optimize): after
every step its caller has the run as it stands and may stop it there, and
the checkpoint, wai.quantum.optimize-checkpoint/1, holds the steps taken
with their links and the optimiser's whole state (the point, Adam's
moments and the powers of its betas, SPSA's stream, the best point and the
counts), every number as the bits of its f64. Gone on with from any step,
a run ends with the same bytes as one that never stopped, for each
optimiser; a checkpoint of another request, or one whose steps were
changed, is refused (J052).

wai-quantum optimize --checkpoint FILE keeps the state in FILE as it goes
(at most once a second, and when it stops; written whole or not at all),
goes on from FILE when it is there, and removes it when the run ends; a
run killed and started again with the same arguments ends with the same
bytes, receipt and all. --slice N takes at most N steps, then stops with
the state kept (exit 2).

Co-Authored-By: Claude Opus 5.5 <[email protected]>

980fffc34d

• View at this point in history

2026-11-03 17:46:09 -05:00