Dev Builds » 20181014-1815

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 0370077c375e313cec055c8e52c34f05ae06fdc4
Author Miguel Lahoz
Date 2018-10-14 18:15:16 UTC
Simplify evaluation of blockers_for_king Currently, we have two evaluation terms which account for pinned pieces. One is for all pinned pieces in kingDanger computation and another for just pinned pawns in ThreatByRank. We can increase the relevant bonus for kingDanger calculation and do away with the ThreatByRank, which seems to just add more complexity. STC: LLR: 2.95 (-2.94,2.94) [-3.00,1.00] Total: 113353 W: 24299 L: 24356 D: 64698 http://tests.stockfishchess.org/tests/view/5ba348c20ebc592cf2766e61 LTC: LLR: 2.95 (-2.94,2.94) [-3.00,1.00] Total: 96458 W: 15514 L: 15511 D: 65433 http://tests.stockfishchess.org/tests/view/5ba398830ebc592cf2767563 At 100k games, I thought it struggles a bit, but some related [0,4] tests attempting individual tweaks seem to fail: I tried directly tweaking ThreatByRank: http://tests.stockfishchess.org/tests/view/5ba3c6300ebc592cf276791c http://tests.stockfishchess.org/tests/view/5ba3c6190ebc592cf2767917 @Vizveznedec was also recently trying to tweak the same coeffecients for kingDanger calculation: http://tests.stockfishchess.org/tests/view/5ba2c7320ebc592cf27664b2 http://tests.stockfishchess.org/tests/view/5ba2c8220ebc592cf27664b8 http://tests.stockfishchess.org/tests/view/5ba2c7880ebc592cf27664b4 http://tests.stockfishchess.org/tests/view/5ba2c7ce0ebc592cf27664b6 Bench: 4648095
Copyright 2011–2024 Next Chess Move LLC