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

In smooth TM, use piggybank when it seems like the bestmove can be overtaken. #1762

Merged
merged 12 commits into from
Dec 4, 2022

Conversation

mooskagh
Copy link
Member

Should help against this:
image

Not tested, likely also fixes #1582.

@mooskagh
Copy link
Member Author

Example where it worked.

image

@mooskagh
Copy link
Member Author

mooskagh commented Aug 1, 2022

Looking at times where this logic triggered at WCCC, it didn't help, gave up too early.

Example from WCSC R4 game vs Ginkgo:

image

@mooskagh
Copy link
Member Author

mooskagh commented Aug 1, 2022

image
Example where it did help!

But it was just one example like this during the entire event.

@Naphthalin
Copy link
Contributor

Do we plan on using/maintaining the smooth time manager any time soon?

@Naphthalin Naphthalin added the bug fix Fixes intended behavior label Nov 3, 2022
@borg323 borg323 self-assigned this Nov 17, 2022
@mooskagh mooskagh merged commit d1237b8 into LeelaChessZero:master Dec 4, 2022
@mooskagh mooskagh deleted the smooth-nps branch December 4, 2022 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug fix Fixes intended behavior
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Smooth time manager should use piggybank then the eval for the current bestmove rapidly drops
3 participants