Dev Builds » 20180310-1104

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 5dc381a56692a378674fe61e9ee2d64900aa3aa6
Author protonspring
Date 2018-03-10 11:04:03 UTC
Implement an old Russian proverb "Loose pieces drop, in blitz keep everything protected" Adding a small S(2,2) bonus for knights, bishops, rooks, and queens that are "connected" to each other (in the sense that they are under attack by our own pieces) apparently is a good thing. It probably helps the pieces work together a bit better. STC LLR: 2.96 (-2.94,2.94) [0.00,5.00] Total: 12317 W: 2655 L: 2467 D: 7195 LTC LLR: 2.96 (-2.94,2.94) [0.00,5.00] Total: 35725 W: 5516 L: 5263 D: 24946 How to continue from there (by Stefan Geschwentner)? • First we should identify all other eval terms which have an overlap with new connectivity bonus (like the outpost bonus). A simple way would be subtract the connectivity bonus from them and look if this better, or use a SPSA session for these terms. • Tuning Connectivity himself with SPSA seems not so promising because of the small range which is useful. Here manual testing changes of Connectivity like +-1 seems better. • The eg value is more important because in endgame the position gets more open and so attacks on pieces are easier. Another important point is that when defending/fortress-like positions each defending piece needs a protection, otherwise attacks on them can break defense. Closes Bench: 5318575
Copyright 2011–2024 Next Chess Move LLC