Dev Builds » 20260409-1953

You are viewing an old NCM Stockfish dev build test. You may find the most recent dev build tests using Stockfish 15 as the baseline here.

Use this dev build

NCM plays each Stockfish dev build 20,000 times against Stockfish 14. This yields an approximate Elo difference and establishes confidence in the strength of the dev builds.

Summary

Host Duration Avg Base NPS Games WLD Standard Elo Ptnml(0-2) Gamepair Elo

Test Detail

ID Host Base NPS Games WLD Standard Elo Ptnml(0-2) Gamepair Elo CLI PGN

Commit

Commit ID ead7e650da1dd07a2614ba4d8207470fe921a87b
Author anematode
Date 2026-04-09 19:53:08 UTC
Fix weird indexing bug [Passed STC](https://tests.stockfishchess.org/tests/live_elo/69cf6a5d1668971c9da23ae1) LLR: 2.93 (-2.94,2.94) <-1.75,0.25> Total: 51104 W: 13376 L: 13180 D: 24548 Ptnml(0-2): 134, 5555, 13963, 5781, 119 [Passed LTC](https://tests.stockfishchess.org/tests/live_elo/69d00a7ee2b443cb2670b5c6) LLR: 2.95 (-2.94,2.94) <-1.75,0.25> Total: 101256 W: 25867 L: 25732 D: 49657 Ptnml(0-2): 59, 10423, 29520, 10576, 50 When processing a promotion we add/remove nonsensical threats, namely, piece threats of pawns on the 1st or 8th rank. This is not only inefficient but also seems to lead to an obscure bug during a promotion–capture + `double_inc_update` that causes a lingering invalid feature. Currently – as an artifact of the training process – these parts of the net are filled with random values in [-1,1], which is why there is a bench change. @ces42 did a helpful analysis: > checking bench with depth 17 actually shows that the bug in has been there all the time since 8e5392d7 (when threat inputs was merged into master) > i.e. double_inc_update for ThreatFeatureSet has always been slightly bugged After this patch is applied we'll be able to better compress the net by filling the invalid features with 0, w/o changing bench. I expect a 15%-ish size savings. closes https://github.com/official-stockfish/Stockfish/pull/6701 Bench: 2700393
Copyright 2011–2026 Next Chess Move LLC