]> git.sesse.net Git - stockfish/commit
Remove PawnsOnBothFlanks
authorprotonspring <mike@whiteley.org>
Wed, 29 Aug 2018 00:48:45 +0000 (02:48 +0200)
committerStéphane Nicolet <cassio@free.fr>
Wed, 29 Aug 2018 00:49:10 +0000 (02:49 +0200)
commite846a9306d6108fb24cb216689867777ac2b0c4f
treec4ece88ef1fcfcba16777d5079d9cf2f398b05f6
parent10bb2e6cdb5c8e7a34f1f1fbf3dd0cc0d0cf63ed
Remove PawnsOnBothFlanks

It looks like PawnsOnBothFlanks can be removed from initiative().
A barrage of tests seem to confirm that the adjustment to -110
does not gain elo to offset any potential loss by removing
PawnsOnBothFlanks.

STC
LLR: 2.96 (-2.94,2.94) [-3.00,1.00]
Total: 22014 W: 4760 L: 4639 D: 12615
http://tests.stockfishchess.org/tests/view/5b7f50cc0ebc5902bdbb3a3e

LTC
LLR: 2.96 (-2.94,2.94) [-3.00,1.00]
Total: 40561 W: 6667 L: 6577 D: 27317
http://tests.stockfishchess.org/tests/view/5b801f9f0ebc5902bdbb4467

The barrage of 0,4 tests on the -136 value are in my ps_tunetests branch.
http://tests.stockfishchess.org/tests/user/protonspring

Closes https://github.com/official-stockfish/Stockfish/pull/1751

Bench: 4413173

-------------

How to continue from there?

The fact that endgames with all the pawns on only one flank are
drawish is a well-known chess idea, so it seems quite strange that
this can be removed so easily without losing Elo.

In the past there had been attempts to improve on PawnsOnBothFlanks
with similar concepts (for instance using the pawn span value), but
the tests were at best neutral. Maybe Stockfish is now mature enough
that these refined ideas would work to replace PawnsOnBothFlanks?
src/evaluate.cpp