Skip to content

GAUNTLET

Run the same beam search across nine different scan orders, so it lands in different regions instead of always converging to the same one. The zigzag order found a brand-new 458 board.

by Raphaël Anjou

experimentsolvermeasurednew basin458/480matched edgesBuild boards upUpdated 2026-07-21
Reproducestochastic — won't reproduce exactly; the board is verifiablere-verifies a stored boardBudget: ~5 min ALNS lift per build (exploratory run, not the standardized single-core bench)
Pipeline
  1. 1
    beam producernot yet written up

    A scan-order sweep builds many diverse boards, sampling different regions

    carries: A positional corpus prior plus a swappable scan order for construction diversity

  2. 2
    ALNSnot yet written up

    Destroy-and-repair lifts a promising build; the committed 458 is a lifted board

  3. 3
    clustering

    Group results by corner arrangement to flag genuinely new basins (not a solver stage)

Complexity
Time
9 scans × 4 seeds beam builds, then 5-min ALNS lift per strong build
Space
one live beam per (scan, seed); shares PRIOR's 256×256 prior matrix

Scan order is a preprocessing choice, not a cost: the nine orders reuse the same beam machinery and the same prior.

Hardware & run
Native runCPU only
0.67core-hours
Cores
8
RAM
16 GiB
GPUs
0
CPU
Apple M1
Machine
MacBook (Apple M1, 8 cores)
Budget
~5 min ALNS lift per build (exploratory run, not the standardized single-core bench)
Start
stochastic; see the run's repro command
Verify the stored board

stochastic — won't reproduce exactly; the board is verifiable

This verifies the board, not the search that produced it.

just research-record-boards
Code & data on GitHub

Keep exploring

Referenced by

Page sourceView as Markdown