Dev Builds » 20180228-1137

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.


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 ID ad5d86c7714ae3eaad71e8b3630d38c29dd2c3fe
Author Leonid Pechenik
Date 2018-02-28 11:37:20 UTC
Tweak time management Using a SPSA tuning session to optimize the time management parameters. With SPSA tuning it is not always possible to say where improvements came from. Maybe some variables changed randomly or because result was not sensitive enough to them. So my explanation of changes will not be necessarily correct, but here it is. • When decrease of thinking time was added by Joost a few months ago if best move has not changed for several plies, one more competing indicator was introduced for the same purpose along with increase in score and absence of fail low at root. It seems that tuning put relatively more importance on that new indicator what allowed to save time. • Some of this saved time is distributed proportionally between all moves and some more time were given to moves when score dropped a lot or best move changed. • It looks also that SPSA redistributed more time from the beginning to later stages of game via other changes in variables - maybe because contempt made game to last longer or for whatever reason. All of this is just small tweaks here and there (a few percentages changes). STC (10+0.1): LLR: 2.96 (-2.94,2.94) [0.00,4.00] Total: 18970 W: 4268 L: 4029 D: 10673 LTC (60+0.6): LLR: 2.95 (-2.94,2.94) [0.00,4.00] Total: 72027 W: 12263 L: 11878 D: 47886 Additional non-regression tests at other time controls Sudden death 60s: LLR: 2.95 (-2.94,2.94) [-4.00,0.00] Total: 14444 W: 2715 L: 2608 D: 9121 40 moves repeating at LTC: LLR: 2.95 (-2.94,2.94) [-4.00,0.00] Total: 10309 W: 1880 L: 1759 D: 6670 This is a functional patch only for time management, but the bench does not reflect this because it uses fixed depth search, so the number of nodes does not change during bench. No functional change.
Copyright 2011–2024 Next Chess Move LLC