Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This patch is a combinaison of two parameters tweaks patches which have failed as strong yellows at LTC recently, by Alain Savard (Rocky640) and Fabian Fichter (ianfab): http://tests.stockfishchess.org/tests/view/5b8a71e60ebc592cf2749b1d http://tests.stockfishchess.org/tests/view/5b81ce3b0ebc5902bdbb6585 Passed STC: LLR: 2.95 (-2.94,2.94) [0.00,4.00] Total: 57200 W: 12392 L: 12008 D: 32800 http://tests.stockfishchess.org/tests/view/5b8d0a5a0ebc592cf274c48f And LTC: LLR: 2.96 (-2.94,2.94) [0.00,4.00] Total: 37215 W: 6233 L: 5962 D: 25020 http://tests.stockfishchess.org/tests/view/5b8d56090ebc592cf274cb53 Closes #1764 Bench: 4136116 --------------- How to continue from there? The null move reduction formula in line 769 of search.cpp is quite convoluted and full of mysterious magic constants at the moment, it would certainly be nice to simplify it and/or gain more Elo from it: ``` Depth R = ( (823 + 67 * depth / ONE_PLY) / 256 + std::min(int(eval - beta) / 200, 3)) * ONE_PLY; ```
- Loading branch information
4bef7aa
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ElbertoOne
with respect to your comment regarding this line:
you can bake it down to this with no change in bench ...
with the added benefit that it actually makes it understandable...
4bef7aa
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MichaelB7 Although it does not change bench, it still is a functional change, since the results of the formulas start to differ at depth 26. However, I agree that it would be a nice simplification, and since the functional change is very minor, it should pass [-3,1] tests.
4bef7aa
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MichaelB7 thanks, let's give it a go in a test: http://tests.stockfishchess.org/tests/view/5b9791800ebc592cf275a553
4bef7aa
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks is for running @ElbertoOne. Looks like LTC will fail.
You might want to try this @ (0,4):
‘’’
Depth R = ((52 + 17 * depth / ONE_PLY) / 16
+ std::min(int(eval - beta) / 200, 3)) * ONE_PLY;
‘’’
Not really a simplification, but it is tad more aggressive. I would ask for LTC test since STC will probably fail with (0,4) and this is really a parameter tweak that will only materialize at LTC. Should pass STC with (-3,1). Would they let you do that? Run STC with (-3,1) and LTC with (0,4)?
4bef7aa
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ello friends. need to something. i want to contuniue to game not to win . i must to close to win but dont want to win.i want to to continue to game. what should i do. how can i chance codes.thanks