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

feature request: show KataGo endstate on every point #589

Closed
ivysrono opened this issue Jun 26, 2019 · 9 comments
Closed

feature request: show KataGo endstate on every point #589

ivysrono opened this issue Jun 26, 2019 · 9 comments

Comments

@ivysrono
Copy link
Contributor

Newest Lizzie for KataGo:
图片

@yishn
Copy link
Member

yishn commented Aug 6, 2019

I don't get it. What's the difference to the analysis mode we have now? Please elaborate.

@ivysrono
Copy link
Contributor Author

ivysrono commented Aug 6, 2019


For KataGo, Lizzie displays three parameters: winning rate, calculation amount, and endstate. And the option can determine which parameters are displayed.
LizGoban displays the endstate and the amount of calculation by default.
Now Sabaki can only display the first two, no endstate.
I hope to show the third and the most inportant: endstate.

@ivysrono
Copy link
Contributor Author

@yishn Are you still need more info now?

@yishn
Copy link
Member

yishn commented Sep 11, 2019

What does endstate mean and how do you get it?

@yzyray
Copy link

yzyray commented Sep 12, 2019

What does endstate mean and how do you get it?

lightvector/KataGo#25 (comment)

use kata-analyze command and lizzie displayed the "scoreMean" on suggestions points

@Nihisil
Copy link
Contributor

Nihisil commented Jan 18, 2020

https://github.com/lightvector/KataGo/blob/master/docs/GTP_Extensions.md

The attribute was renamed to the scoreLead:

scoreLead - The predicted average number of points that the current side is leading by (with this many points fewer, it would be an even game).

@ivysrono
Copy link
Contributor Author

ivysrono commented Feb 29, 2020

similar #619

@egri-nagy
Copy link

I agree that the score estimate is more informative for analysis. I do a lot of game reviews (for a university course) and beginners often get a flat line in the winrate graph (definite loss or win), so there is no information whehter the moves are good or not after some deciding blunder in the beginning. On the other hand the score estimate can still go up and down in a meaningful way.

So I can confirm, that displaying the average score estimate would be a useful addition.

@yishn yishn added the blocked label Mar 1, 2020
@yishn
Copy link
Member

yishn commented Mar 1, 2020

Sabaki can't integrate with features that are only available in kata-analyze because kata-analyze doesn't conform to our analyze command standards.

@yishn yishn closed this as completed in 8efebdb Mar 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

5 participants