Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use equations for PushAway and PushClose #2570

Closed

Conversation

protonspring
Copy link

@protonspring protonspring commented Mar 4, 2020

This is a functional simplification. I was trying to replace all of the tables, but in doing so, found that this particular version seems to do very well at LTC. I think we should commit this, then I can continue. This version is slightly simplified from the one that passed STC.

Both LTC tests are included. I honestly can't explain the difference. The change is pretty minimal.

STC
LLR: 2.95 (-2.94,2.94) {-1.50,0.50}
Total: 57864 W: 11092 L: 11001 D: 35771
Ptnml(0-2): 826, 6458, 14320, 6455, 873
http://tests.stockfishchess.org/tests/view/5e5da5b6e42a5c3b3ca2e05c

LTC
LLR: 2.95 (-2.94,2.94) {-1.50,0.50}
Total: 7198 W: 982 L: 883 D: 5333
Ptnml(0-2): 33, 575, 2296, 650, 45
http://tests.stockfishchess.org/tests/view/5e5df13ae42a5c3b3ca2e077

LTC (This exact version. . . more simplified)
LLR: 2.95 (-2.94,2.94) {-1.50,0.50}
Total: 5392 W: 729 L: 631 D: 4032
Ptnml(0-2): 23, 405, 1751, 485, 32
http://tests.stockfishchess.org/tests/view/5e5ead99e42a5c3b3ca2e0e4

Bench 5123316

@adentong
Copy link

adentong commented Mar 4, 2020

This looks pretty legit.

@ddugovic
Copy link

ddugovic commented Mar 4, 2020

My guess is that these parameter values are significantly better in endgames where search affects the result (likely KQKP, probably not KXK or KBNK). Congrats!

@protonspring
Copy link
Author

protonspring commented Mar 4, 2020 via email

@vondele vondele closed this in 5a7b45e Mar 4, 2020
@vondele
Copy link
Member

vondele commented Mar 4, 2020

Thanks! I'm inclined to think these very strong LTC results are lucky runs.... but we'll see in later regression tests.

@xoto10
Copy link
Contributor

xoto10 commented Mar 4, 2020 via email

@vondele
Copy link
Member

vondele commented Mar 4, 2020

@xoto10 in would say in a code like SF, a single memory access that is not in cache has a measurable performance penalty (that's why we prefetch the TT entries). Apart from reducing the number of parameters, that's why we should encourage such arrays -> equation changes IMO. However, it seems very unlikely to me to gain 5 Elo from a mere speedup, by accessing less certain arrays in the endgame.

@adentong
Copy link

adentong commented Mar 4, 2020

This is interesting because it was not one, but two extremely strong LTCs. I wonder if it's still due to luck.

@ddugovic
Copy link

ddugovic commented Mar 4, 2020

I'd expect this to perform better at LTC than STC since being able to prune away entire endgame search trees from middlegame and opening positions is useful in slower games.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants