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

Fix go mate in multithreading #5087

Closed
wants to merge 1 commit into from
Closed

Fix go mate in multithreading #5087

wants to merge 1 commit into from

Conversation

peregrineshahin
Copy link
Contributor

@peregrineshahin peregrineshahin commented Mar 2, 2024

To actually have consistency one cannot use bestValue as it can propagate the aborted scores and more importantly out of the bound scores that we do not accept in outputting (thus we use uciScore) and label them as lowerbound/upperbound .

The extra checks for .score is needed in voting because we use .score not .uciScore this renders only the thread that can actually be picked as best to be the one printing the mate.

No functional change

To actually have consistency one cannot use bestValue as it can propagate the aborted scores and more importantly out of the bound scores that we do not accept in outputting (thus we use uciScore) and label them as lowerbound/upperbound .

The extra checks for `.score` is needed in voting because we use .score not .uciScore this renders only the thread that can actually be picked as best to be the one printing.

No functional change
@peregrineshahin
Copy link
Contributor Author

Related niklasf/python-chess#1070

@peregrineshahin
Copy link
Contributor Author

This is still bugged after thinking about it.. discussed in discord why

@robertnurnberg
Copy link
Contributor

Link to discord for completeness.

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.

2 participants