Fix imprecision when winrate is extreme #16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pull request leela-zero#1386.
* Extend GTP to add support for displaying winrates and variations from LZ while LZ is thinking. * Use UCI format for lz-analyze and lz-genmove-analyze. * Don't sort gtp lz-analyze ouput because it is not thread-safe. Pull request leela-zero#1388.
For discussion see pull request leela-zero#1412.
More in line with UCI, cleaner, easier to parse, smaller code.
Don't hardcode the clang version in the Makefile.
Regression from leela-zero#1388. Fixes issue leela-zero#1424.
Send leelaz version embedded in the URL used to ask for a new job. Pull request leela-zero#1430.
winrate from the viewpoint of the opponent, theoretically equal to 1 - winrate, but if it is small it is more accurate to calculate it directly from network output.
Now winrate is black value and opp_winrate is white value
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.