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 #362: show best moves after --visit exhaustion #363

Merged

Conversation

OlivierBlanvillain
Copy link
Contributor

@OlivierBlanvillain OlivierBlanvillain commented Sep 17, 2018

This PR adds a new parser for what I've called "summary line". Leelaz will systematically output small summaries like the following once it reached the maximum number of visits specified with the --visit flag:

  O4 ->       5 (V: 53.21%) (N: 39.95%) PV: O4 F3 C6 C17
  F3 ->       4 (V: 54.48%) (N: 34.51%) PV: F3 F17 E17 F16

Parsing this data fixes #362.

This PR also setups JUnit and adds a few tests for the new regular expression.

Plus some minor cosmecis improvements.
Moves are always outputed in order by leelaz, so this processing this
info is redundent. Furthermore, summary lines do not include any order,
so we can only rely on print order for these. This commit remove the
order field, and remove the Comparable interface from MoveData.
With the new "summary parser", Lizzie will now properly show best moves
even after exhaustion of the --visit visits.
@OlivierBlanvillain
Copy link
Contributor Author

@zsalch Would you have time for a review?

@zsalch
Copy link
Contributor

zsalch commented Oct 1, 2018

@OlivierBlanvillain
The code looks good to me. I need do some testing.

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.

3 participants