Skip to content

Reproduce index

Every result on the wiki that ships a reproduce command, in one table: what the command does, whether it re-runs the search or only re-checks a stored board, and roughly what it costs to run. Click a column head to reorder.

23 commands

Pipeline
Blackwood's solver, decoded and run hereheavysearch60-120 s per run0.033
CSP presets, measuredseededsearch60 s2.0
Entropy and the area lawexactsearchentropy-area-law
Forbidden patternsexactsearchforbidden-patterns
GAUNTLETstochasticverify only~5 min ALNS lift per build (exploratory run, not the standardized single-core bench)0.67record-boards
KEYRINGstochasticverify onlynot logged (exploratory run, not the standardized single-core bench)record-boards
LODESTONEstochasticverify onlynot logged (exploratory run, not the standardized single-core bench)record-boards
McGavin's C backtracker: the throughput story, built hereheavysearch30 s per run0.0083
No forced movesexactsearchno-forced-moves
PALIMPSESTstochasticverify only~30 min × 6 seeds (exploratory run, not the standardized single-core bench)4.0record-boards
Piece theft, where solvers dieexactsearchpiece-theft
PRIORstochasticverify onlynot logged (exploratory run, not the standardized single-core bench)record-boards
Reference numbersexactsearchsubgrid-placement-counts
Single-core benchmarkseededsearch60 s2.5
STAGEDstochasticverify onlynot logged (exploratory run, not the standardized single-core bench)record-boards
The DFS studyseededsearch60 s0.017
The hint studyseededsearch8 s per run0.0022
The JIT backtracker: portable Rust that ties hand-tuned C on hard boardsheavysearch6–30 s per benchmark run0.0083
The rare colors live on the frameexactsearchrare-color-geography
The repair studyseededsearch60 s0.017
Tuned to the hardness peakexactsearchphase-transition
Verhaard reimplementationseededsearch120 s0.033
Why a faster computer doesn't helpexactsearchprune-vs-speed