Dev Builds » 20140503-1940

Use this dev build

NCM plays each Stockfish dev build 20,000 times against Stockfish 15. 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 c0d3010438e9cec2d40dec9e92695b58514497bb
Author Ronald de Man
Date 2014-05-03 19:40:09 UTC
Fix KXK endgame Position is win also if strong side has a bishop and a knight (plus other material, otherwise KBNK would be triggered instead of KXK). This fixes a subtle bug where a search on position k7/8/8/8/8/P7/PB6/K7 b - - 6 1 Instead of returning a draw score, suddendly returns a big score. This happens because at one point in search we reach this position: 8/Pk6/8/8/8/4B3/P7/K7 w - - 3 8 Where white can promote. In case of rook promotion (and also in case of queen promotion) the resutling position gets a huge static eval that is above VALUE_KNOWN_WIN (from the point of view of white). So for rook promotion it is && futilityBase > -VALUE_KNOWN_WIN that prevents futility pruning in qsearch. (Removing this condition indeed lets the problem occur). Raising the static eval for K+B+N+X v K to a value higher than VALUE_KNOWN_WIN fixes this particular problem without having to introduce an extra futility pruning condition in qsearch. I just checked and it seems K+R v K, K+2B v K and even K+B+N v K already get a huge static eval. Why not K+B+N+P v K? I think this fix corrects an oversight. There is special code for KBNK, but KBNXK is handled by KXK, so the test for sufficient material should also test for B+N. bench: 8678654
Copyright 2011–2024 Next Chess Move LLC