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

Cached move analysis not changing when best move is different with a newer stockfish #11471

Open
mrobaczyk opened this issue Sep 1, 2022 · 2 comments
Labels

Comments

@mrobaczyk
Copy link

mrobaczyk commented Sep 1, 2022

Correct me if I'm wrong, but in this position:

https://lichess.org/analysis/8/2pp2pp/8/2PP1P2/1p5k/8/PP4p1/6K1_w_-_-_0_1?color=white#0

for 1 PV line the best move is Kxg2 at depth 52. When I hit the plus it instantly sees f6 as winning. After I analyze to about depth 25 it does not replace the cached result despite lower depth. But this is a known study where white is winning with f6.

Probably the cached move was done with weaker stockfish. Maybe stockfish version should also somehow override earlier deep analysis.

image

@mrobaczyk mrobaczyk added the bug label Sep 1, 2022
@mrobaczyk mrobaczyk changed the title Cached move analysis not changing when best move is different Cached move analysis not changing when best move is different with a newer stockfish Sep 1, 2022
@mrobaczyk
Copy link
Author

After giving it a little bit more thought it's unclear for me how it should exactly work. The SF version on lichess is changing very often, right? Given that, maybe the cached analysis should have a time expire (let's say 1 year or so) so eventually in this position it would get replaced with f6.

@dav1312
Copy link

dav1312 commented Sep 10, 2022

The SF version on lichess is changing very often, right?

Depends on what you consider "very often". They are currently using a +1yo version.

official-stockfish/Stockfish@1946a675

image

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

No branches or pull requests

2 participants