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: add "number of visits per board position" to the batch analysis #58

Open
Trevoke opened this issue Apr 8, 2022 · 2 comments

Comments

@Trevoke
Copy link
Contributor

Trevoke commented Apr 8, 2022

It would be nice to specify a number of visits to put on each board position, as a different option from "time to spend on each board position".

Currently I end up with some fairly uneven visits on board positions - some positions get 700 visits, some get a few thousands, some apparently get up to 20 or 30. I imagine that some of these numbers are due to how q5go does the analysis in the reverse, so it reconnects to prior-done work in the analysis, but I'd like to have a minimum number of visits guaranteed on all board positions.

@bernds
Copy link
Owner

bernds commented Apr 11, 2022

Well, the idea is that you choose the time setting to guarantee a minimum number of visits for the position - with reverse analysis giving you a bonus sometimes. As far as I remember, the engine doesn't report a number of visits for the position, only per-move.

Are you asking for a minimum number for the top move? That could probably be arranged.

@Trevoke
Copy link
Contributor Author

Trevoke commented May 7, 2022

Oof a month ago for this discussion, so sorry.

Tools like katrain and lizzie are able to ask for a number of desired visits for a given board position (if I analyze the game and ask for 500 visits per move, every move in the game will have 500 visits, split between all the moves that katago looked at). I don't know how they do that, maybe they're doing more work client-side to tally up all the results?

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

No branches or pull requests

2 participants