Limit eval-based history updates#1055
Merged
codedeliveryservice merged 1 commit intoMay 29, 2026
Merged
Conversation
If we encounter the same position again at high depth, we skip the eval-difference update and let the depth-based history handle it later, this should minimize the uncertain bias introduced by the feedback loop of doing it again. Elo | 2.34 +- 1.80 (95%) SPRT | 8.0+0.08s Threads=1 Hash=16MB LLR | 2.90 (-2.25, 2.89) [0.00, 3.00] Games | N: 39490 W: 10256 L: 9990 D: 19244 Penta | [173, 4613, 9905, 4883, 171] https://recklesschess.space/test/15083/ Elo | 2.35 +- 1.73 (95%) SPRT | 40.0+0.40s Threads=1 Hash=64MB LLR | 3.01 (-2.25, 2.89) [0.00, 3.00] Games | N: 36296 W: 8949 L: 8704 D: 18643 Penta | [21, 4062, 9742, 4297, 26] https://recklesschess.space/test/15086/ Bench: 4014185
60d1bdd
into
codedeliveryservice:main
20 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If we encounter the same position again at high depth, we skip the eval-difference update and let the depth-based history handle it later, this should minimize the uncertain bias introduced by the feedback loop of doing it again.
Elo | 2.34 +- 1.80 (95%)
SPRT | 8.0+0.08s Threads=1 Hash=16MB
LLR | 2.90 (-2.25, 2.89) [0.00, 3.00]
Games | N: 39490 W: 10256 L: 9990 D: 19244
Penta | [173, 4613, 9905, 4883, 171]
https://recklesschess.space/test/15083/
Elo | 2.35 +- 1.73 (95%)
SPRT | 40.0+0.40s Threads=1 Hash=64MB
LLR | 3.01 (-2.25, 2.89) [0.00, 3.00]
Games | N: 36296 W: 8949 L: 8704 D: 18643
Penta | [21, 4062, 9742, 4297, 26]
https://recklesschess.space/test/15086/
Bench: 4014185