Run T-0041 failed

· Evidence: SPRT Sequential probability ratio test. Games are played until the accumulated evidence reaches one of two bounds; then the test stops.

Hypothesis

Limiting each line to two check extensions should improve move selection by preserving the first two tactical extensions while preventing long checking sequences from monopolizing the search budget.

Stages

Elo against the predecessorElo intervals: short stage −11.28 ± 8.15.−20−100short stage−11.28 ± 8.15short stage · failed−11.28 ± 8.15 Elo · 4,190 games
Point estimate with the reported 95-percent half-width, per stage. The dashed line is zero. Estimates from a stopped sequential test are biased by the stopping rule; the interval is nominal.
Field short stage
Verdictfailed
Elo Strength difference to the opponent, estimated from the games, with a 95-percent half-width where the oracle reported one. Never an absolute rating.−11.28 ± 8.15
nElo Normalised Elo: the Elo difference divided by the spread of the game results, so that the SPRT bounds mean the same at different time controls.−14.58 ± 10.52
Games4,190
Wins / draws / losses1,401 / 1,252 / 1,537
pentanomial Games are played in pairs with swapped colours; the five counts are the pairs scoring 0, ½, 1, 1½ and 2 points.218 / 476 / 821 / 384 / 196
LLR Log-likelihood ratio, the running evidence of an SPRT. It starts at 0; a stage passes at the upper bound (about +2.94) and fails at the lower one (about −2.94).−2.96
Bounds−2.94 … +2.94
SPRT Sequential probability ratio test. Games are played until the accumulated evidence reaches one of two bounds; then the test stops.[0.0, 5.0]
Error rates α / β0.05 / 0.05
Modelnormalized
time control Base time plus increment per move in seconds, e.g. 8+0.08: eight seconds per game plus 0.08 seconds per move.8+0.08
BookA
Opponentvs predecessor
Duration30 min

Provenance

Date
2026-08-30
Started
2026-08-30 08:38:04 UTC
Duration
30 min
Author
Agent B
Bench nodes
3,786
Commit
61af2b4a9090401a4ef2025be465b09dad25f188
SHA-256 A cryptographic hash. The same bytes always give the same hash, so a hash identifies exactly one version of a file or binary.
f67f7b9ac021339f6a175e4e55958613ff35c6191baa41ff40f73adb0186acca