Life In 19x19

There is now a 0.7 release with one important bug fix, as well as support for Kombilo databases.

This works, loading my Kombilo data flawlessly. I was hoping to see pattern search but it seems "support for Kombilo databases" simply means opening games from the database files.

macelee wrote:This works, loading my Kombilo data flawlessly. I was hoping to see pattern search but it seems "support for Kombilo databases" simply means opening games from the database files.

Yes - I wrote that in the first post but maybe I should have repeated it in the bump post above yours as well.

It would be nice to have pattern search, but I looked at that code in kombilo and it looks complicated to say the least. There's also the question of how to present it in the user interface, which is usually the hardest problem when adding features. Should there be another pane or two in the board window, or should pattern search be a part of the database open dialog? I don't know at this point, but it might be something I'll look at in the future.

In "Batch computer analysis" is it possible to write the win rate (difference) in the SGF file (comments)? For example the same format Lizzie uses in the analysis mode:
Move 7
46,4% (-4,5%)
(network.gz / 226 playouts)

mb76 wrote:In "Batch computer analysis" is it possible to write the win rate (difference) in the SGF file (comments)? For example the same format Lizzie uses in the analysis mode:
Move 7
46,4% (-4,5%)
(network.gz / 226 playouts)

The win rates are saved, but not in the comments. They are shown as titles for the diagrams, and in the evaluation graph, where there is a bar graph showing the move-to-move swings.

I guess I can make an option to also add some text to the comments if that seems useful?

I think this is useful if there is an option to enable this.
Same information as Lizzie.

Ok, I've added something like this. Here's some sample output after leting two engines analyze a game:
If you're able to build it yourself, the code is now on github. But it's getting to the point where there is enough new stuff (the major bits this time being multi-engine analysis, slide export) to make a release, so that should happen some time this week after I've tested it a bit more.

I personally would like a different order:
Engine top choice: D5, 549 visits, winrate B: 47.14%
Game move: D6, choice #2, winrate B: 0.5495% (+7.81)
Analysis: Leela Zero 199-15x192 analysis @7.5 komi

The reason is I open these analyzed files on a mobile phone so I think the most important information should be on top (I don't want to nitpick). Like the extra choice# info.
Does it overwrite current comments? I wait for the compiled version!

Release 0.8 is now out - it includes two major new features, slide export (useful for slide shows or videos), and multi-engine analysis. Also, with engines like LZ, batch analysis can now produce reverse-komi evaluations by internally flipping the colors.
As usual, see the first post for more information.

I tested the Batch computer analysis mode V.08:
A) In which folder are the configuration files stored for the Engines? Because a new or deleted configuration file only (dis)appears when I restart Q5.
B1) The analysis function works fine with Leela 0.16. Including the Add evaluation info!
B2) But with Leela 0.17 beta (LZ_0.17-next-x64-28032019) it gets stuck in a loop at the first move (so it stays at 0%). See attachment for the log file.
C) It is not clear to me what the "If fixed engine komi" does or how it should be set-up. It needs a read me/help?

mb76 wrote:I tested the Batch computer analysis mode V.08:
A) In which folder are the configuration files stored for the Engines? Because a new or deleted configuration file only (dis)appears when I restart Q5.

Which OS are you on? On Windows, the config file is in (I think) %APPDATA%/Local/q5go/, on Linux it should be ~/.config/q5go/.
I'm not sure what situation or actions you are describing. What exactly are you doing and what is the behaviour?

B1) The analysis function works fine with Leela 0.16. Including the Add evaluation info!
B2) But with Leela 0.17 beta (LZ_0.17-next-x64-28032019) it gets stuck in a loop at the first move (so it stays at 0%). See attachment for the log file.

Hmm, I just tried with a build from the next branch on Linux, and it seems to work fine here. I'll try on Windows the next time I boot into it.

C) It is not clear to me what the "If fixed engine komi" does or how it should be set-up. It needs a read me/help?

This is the reverse komi support. LZ only supports a fixed komi of 7.5, and you should put that in the configuration. The combo box then selects the behaviour - keep the 7.5 komi always, or switch to -7.5 if the analyzed game has reverse komi, or just analyze both.
That definitely ought to have a tooltip, which appears to be missing. I'll fix that.

mb76 wrote:B2) But with Leela 0.17 beta (LZ_0.17-next-x64-28032019) it gets stuck in a loop at the first move (so it stays at 0%). See attachment for the log file.

This should be fixed now with version 0.8.1.

Many thanks to Adrian Petrescu, who has built the latest release on the Mac and provided a Mac binary package on his Github page.

bernds wrote:Many thanks to Adrian Petrescu, who has built the latest release on the Mac and provided a Mac binary package on his Github page.

I downloaded the binary, but when I unzipped it and tried to run it, after giving permission, I got the dreaded OSStatus=99999 error message. I have a MacBook pro with Mojave 10.14.4 and NVIDIA GeForce GT 750M 2GB.

Bill Spight wrote:

bernds wrote:Many thanks to Adrian Petrescu, who has built the latest release on the Mac and provided a Mac binary package on his Github page.

I downloaded the binary, but when I unzipped it and tried to run it, after giving permission, I got the dreaded OSStatus=99999 error message. I have a MacBook pro with Mojave 10.14.4 and NVIDIA GeForce GT 750M 2GB.

Unfortunately it's not something I can help with - I've never owned a Mac. There are a few Google results, several of them suggesting a similar solution, but I can't tell whether those are safe to use.