-
Notifications
You must be signed in to change notification settings - Fork 2.7k
[RFC] Prefer suboptimal moves to time losses #6424
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
base: master
Are you sure you want to change the base?
[RFC] Prefer suboptimal moves to time losses #6424
Conversation
|
Pushed a change that always uses WDL as fall-back at root. |
|
Some comments from my side: firstly, I would completely understand if maintainers say they would rather not open this can of worms and leave master as it is. Secondly, if this gets merged it should be on the understanding that the code is off-limits for any tinkering with constants and so on. We should come to some agreement on what approach makes sense, and then stick with that. If we want to go ahead with this, then imo the main thing to discuss is the |
|
I think it is a bit a can of worms... my first question would be how does this work if we're not playing with TC, but fixed depth or nodes? |
b94e78d to
79d691f
Compare
|
Pushed a fix for nodestime option (also for the pv extension part). Also corrected small test numbers, sorry about previously misleading numbers. |
|
Some more results on the standard book, at different TC, with my setup. Just for completeness. |
This PR is a follow up to #6422. We now also abort DTZ probes at root if we run low on time.
Edit: Apologies about previously published numbers, they were for an old master binary without the pv extension dtz patch. Corrected numbers show no measurable impact at the tested TC.
No functional change.