Announcing GoReviewPartner - v0.15 with Pachi and PhoenixGo

[luchador]

Hello:

I just want to say THANK YOU to our friend pnprog, for all the work done. Excellent!

[pnprog]

Hi!
I was out of town last week, so no time to work on GRP.

Hi, is it possible to provide an option to download GRP with CPU-only Leelazero? Thank you!

Yep no problem. I think the 64bit version is fine?

The below text boxes do not scale when the window is stretched vertically. Text boxes end with "Black Value Network win probability:" - for the interesting part I have to scroll. Instead, GRP shows plenty of unused space. Can this be changed?

I will see what can be done. Those two text boxes are really not satisfying

I used "Convert RSGF" on a rsgf file it just created, this is what happens:

The exact same problem was reported on Github, I will investigate this.

would it be possible to change the table behavior in such a way, that it auto-updates when you step through the game moves? For me it will stay on the move that it has been opened with!

Yes, I will change that.

I just want to say THANK YOU to our friend pnprog, for all the work done. Excellent!

Thanks you! Encouragements are much appreciated

[Caesura]

Hi!

Hi, is it possible to provide an option to download GRP with CPU-only Leelazero? Thank you!

Yep no problem. I think the 64bit version is fine?

Thank you! 64 bit is fine

[pnprog]

Hi everybody!

So I finally found the time to complete the documentation of v0.11, so here is the official announcement

The big change for that version are:

• each bot can be configured in 2 profiles, a slow profile (good for analysis) and a fast profile (good for real time play)
• the new Live Analysis mode

For the live analysis, I am going to copy paste the description I put in the documentation:

A live analysis makes it possible to record a game or play against a bot, while, in the background, having the analysis proceed. This is a way to save on the analysis time, so that when the game is over, part of the analysis is already completed, and the review can start immediately.

It also has the advantage to make the result of the analysis directly available (given the bot performing the analysis is fast enough to catch up with the game speed) which is interesting during a live review.

So first, you have to select the bot that will perform the analysis. It is probably better to select a slow profile bot.
Second, you select who will be playing as black and white. You basically have three options:

• Human : you will enter the move one by one for that color.
• Bot used for the analysis : you want to reuse the bot performing the analysis in the background to play for that color as well
• Another bot : that other bot will play for that color

So here are different way to use the live analysis mode:

• Human VS Human:
  
  • You can use that mode when watching a game online or at a tournament. If the bot used for analysis is faster than the players, then it will provide you with real time data about the on going game, like win rate, and different possibilities for the on going moves.
  • You can use it when playing across the board, to record the game. At the end of the game, then the analysis result can be used to discuss the game with your opponent and check out your respective mistakes.
  • It can also be used as well when reading a game commentary: you enter the moves as you read the commentary, and play the variations in the open position mode. Then you can stop at different moves and check the bot own opinion against the commenter opinion.
  • Of course, the bot opinion is relevant only if the bot is stronger than the human players.
• Human VS Bot: This is mainly for training. You play the bot, and at the end of the game, you review the analysis. You can also stop mid game and check the analysis of the first part of the game.
  
  • You can have the bot playing with you different from the bot used for analysis. Then it makes sense to have this bot weaker than the bot performing the analysis:
    
    • You can use the slow profile version of a bot for analysis, and the fast profile version of that same bot to play against you.
    • If your level is DDK (11 kyu or weaker) then you can play against GnuGo, and have Leela to perform the analysis, and point out your mistakes and how to avoid them, but also GnuGo's mistakes and how to exploit them.
    • You could also set Leela Zero with an old weights file as her fast profile and using the latest weights file for her slow profile for the analysis.
  • You can have the bot playing with you to be the same as the bot used for analysis. This is interesting to save on computing, because the bot analysis is performed at the same time it is choosing its next move. But in that case, you will have to wait for the bot to finish analysing your last move before it starts thinking about its next move. Also, because it plays and analyse at the same time, the Delta for its moves will all be at zero (meaning it considers its move the best moves).
• Bot VS Bot: this is a possibility, but I am not sure for what use case...

When a bot is selected as black or white, that is not the same as the bot used for analysis, or when black and white are played by different bots, then an additional option appears No overlap thinking time that indicates to GRP to make sure the bots are no thinking at the same time, so that your computer processing power (CPU, GPU, RAM) does not becomes a shared resource.

Depending of the situation, this option will be or won't be useful:

• If the bots have a limited number of play-outs, then it is not really necessary
• If one bot run on CPU and the other one on GPU, then it is not that necessary
• If one of the bots is ran across the network from another computer, then it is not really necessary
• If the bot has a limited thinking time, then you should use it

Generally speaking, it is best to use play-outs limits for your bots. You can also set the process of the bot performing the analysis to run at low priority, so that it won't make your opponent slower.



During the live analysis, there is an Open position button available at any time to try out variations. And when the analysis for the 2 first moves is completed, a Start review button will appear that starts the usual review panel for this game. Of course, only the moves already analysed will be available, but the review panel will update itself automatically as the analysis progresses.

So basically I have been using this mode a lot since i started implementing it, playing Live against an older version of Leela Zero, and having our game reviewed by Leela. To me this was eye opening.

Some of the other improvements since v0.10:

• More graphs available
• Quick evaluation in Open Position mode
• Auto update of the Review Panel and graph to follow the analysis
• All analysis data are now saved as SGF (non standard) properties
• RSGF to SGF converter (at the moment now really working apparently)
• A GTP tester (like a terminal) to quickly check the bot is running fine and find out issue, because at the moment, issue with bot settings is a big obstacle to the adoption of Leela Zero (and other bots)
• More check for Leela Zero to handle configuration issues (opencl tunner, wrong weights files...)
• A table to summarize the data off the position and all variations
• Several options to display the variations labels and colors
• Fixed plenty of bugs
• Added plenty of new bugs

Added plenty of new bugs

In fact, I now realize I tried to put too much things into this version, and by doing so, I kept delaying and delaying and delaying this new v0.11, which is detrimental to GRP. More frequent small versions are better to try out the features and find bugs. In fact, there are more bugs than usual in this version, because it's hard for me now to try out all configurations options and combination of those options.

So I will probably release a v0.11.1 soon after I fix all current issues, before going on implement more features.

For the next version v0.12, the main feature I plan to add is support for generic GTP bots that can be used in Live Analysis (and Open Position). Now, we have plenty of very strong bots to analyse our games, and it's good also to have some weaker bots to play against (while leaving the analysis to the strong bots of course).

Then Ideally, that v0.12 will be the last version before v1.0
For v1.0, v1.1, v1.2, v1.3... I would like to stop adding new features, only maintenance:

• Adding support for new strong bots when they appears
• Bug fix
• Translation

The last point is important to me: I received a translation in German after v.10, but with all the interface changes I made since then, that translation is all broken. I feel bad about this, and I cannot really fix that by myself. So I would like to stabilize the programme (at least the interface) so that any work on translation won't be broken in the future, before asking for help for translation.

Then, once V1.0 will be out and living it's own life ("in production" as they say), I will probably slowly start a v2, that will be a restart from scratch, avoiding the design issues I made with v1, probably using wxpython instead of tkinter, python3 instead of python2, and that one will be opened to new features.

So, here you are:

• Documentation (make sure to refresh the page)
• Code source
• Windows download (Leela Zero no GPU coming soone)

[pnprog]

Hi, is it possible to provide an option to download GRP with CPU-only Leelazero? Thank you!

I just added the link on the download page.

[Caesura]

Hi, is it possible to provide an option to download GRP with CPU-only Leelazero? Thank you!

I just added the link on the download page.

Awesome, thank you so much!

[AriGato]

I wonder if this would be a good place to ask.. I just built leela zero and goreviewpartner using the git repos on a mac. Everything worked fine, I can review a game.

However, my mac is quite slow. I would like to spin an Amazon AWS instance to run the analysis.
There doesn't appear to be any way to configure goreviewpartner to connect it if I do?

[pnprog]

Hi!

I wonder if this would be a good place to ask.. I just built leela zero and goreviewpartner using the git repos on a mac. Everything worked fine, I can review a game.

However, my mac is quite slow. I would like to spin an Amazon AWS instance to run the analysis.
There doesn't appear to be any way to configure goreviewpartner to connect it if I do?

I never used AWS, but I see no reason why it wouldn't work.

• If it possible, have GRP directly run on the AWS (GRP can perform analysis in command line mode, with or without graphical interface).
• If GRP cannot run of AWS, only Leela Zero of AWS, it should still be possible, but a bit more tricky: I did ran GRP on my computer, with Leela on another computer, through SSH, the important thing is that you can have GRP run Leela from inside a bash file, for example, in the settings:
  
  • Command: /home/user/running_leela_from_AWS.sh
  • Parameters: (nothing here)
  • Inside running_leela_from_AWS.sh: whatever command that make you remotely run Leela Zero from AWS

[AriGato]

If it possible, have GRP directly run on the AWS (GRP can perform analysis in command line mode, with or without graphical interface).

I think this is worth a try. What command line parameters does it take? I had a quick view on the sources, and I didn't notice any.

[pnprog]

If it possible, have GRP directly run on the AWS (GRP can perform analysis in command line mode, with or without graphical interface).

I think this is worth a try. What command line parameters does it take? I had a quick view on the sources, and I didn't notice any.

Haha, those are the secret features that you will find at the very end of the documentation

[pnprog]

Hi!

I just want to mention I fixed the "known bugs" of the version 0.11, and so released a version 0.11.1

So, at the moment, my todo list for v0.12:

• Add support for generic GRP bots, to use for Live Analysis
• Merge the 2 comment boxes into one, that by default show the comments of the real game variation, and when pointing the mouse on a left side variation, then displaying that variation's comments. If possible, make them stretch vertically
• Change the table behaviour in such a way, that it auto-updates when you step through the game moves
• If possible, provide way to resume an analysis that would have been interrupted. But I don't know at the moment how to do that.
• An option to keep the variations only when the difference in win rate with the game move are higher/lower than a certain value. Might be merged with the existing feature of keeping only the variations when the moves are different.
• If possible, add an option to play a sound when playing a stone (in open position, or live analysis), but the sound file (*.wav, *.mp3) would be provided by the user, not by GRP.
• Maybe have the last played stone somehow "shine" for 1~2s, to help locate it visually. I could also extend this feature by allowing any stone (or location) to shine after mouse click on it. This feature, and the one above, would be of use for people streaming using GRP. For example, in the Michael Redmond video, he often has to mark the stones with A, B, C... to make it clear what group of stones he is talking about (because his mouse pointer is barely visible on the video).

Generally speaking, I am looking for ideas to replace both gobans by only one, or maybe reuse the left goban for open position, to de-clutter a bit the interface.

[Dontbtme]

An option to keep the variations only when the difference in win rate with the game move are higher/lower than a certain value.

That would be AWESOME!
That way, weak players could stick with game changer mistakes only (to focus on what matters most), while strong players wouldn't feel compelled to imitate the bot' style when their own moves were perfectly fine to begin with too.
In short, with such a feature I think ANY KIND of players could benefit greatly from GoReviewPartner's insights.
This is getting real exciting. Thanks and thanks A LOT again!

[nasdaq]

Great your updating it, its been great to use with leelaZero.

As regards ideas:

I like to see the graph, mybe make it always at the bottom of the window.

A way to get rid of the left side board (the one with game variation) is that when the game variation and bot variation are the same, then if user holds down 'shift key' when over the variation it shows the game variation.
I almost never look at game variation because i know it already.
Actually having the game move in a bolder circle might be best to visually see it than have funky 'shift' keys

the table of percentages with variations always displayed, and have the current game percentage as well so i know how much less % the move i played was.

not sure what the left bottom comment box does. it says 'Move 7
Black to play, in the game, black played E16
For this position, Leela Zero would play: E17'
which is nothing i dont get from just looking at the boards.

The right bottom box could be replaced with the table of variaton percentages always shown

bigger board, nicer stones, etc, although I'm fine with it, its functional.

The start review button after doing a 'run sgf file analysis' doesn't work on my installation. using linux debian.


Thanks for GRP! it really is very usefull and hopefully I've not been to nit picky with my ideas!

[pnprog]

That way, weak players could stick with game changer mistakes only (to focus on what matters most), while strong players wouldn't feel compelled to imitate the bot' style when their own moves were perfectly fine to begin with too.

Haha, I did not saw it like this, but yes, this bot imitation style is quite the hot topic at the moment, and GRP somehow encourage that. In fact, the proposal to keep variations only based on win rate difference is a proposal from a github user, not my own idea. The way I see that setting is as a % value that the user can enter in 3 ways, maybe something like this:

• "3" : keep variations with win rate 3% higher or 3% lower than the game actual move
• ">3" : keep variations with win rate 3% higher than the game actual move
• "<3" : keep variations with win rate 3% lower than the game actual move
• Maybe more symbols, to keep variation within 3% or something, like ">3<" ? There must be an efficient notation for that all this, I will have to check wikipedia

By the way:

But the thing is: I HAVE A DREAM

Normally, with v0.11.1, you should be able to use the setting "Keep only variations when bot move and actual game move differ", to keep only the variations for LZ's moves that are different than yours. Then, by converting the RSGF file to SGF file, all the data will be saved back inside the SGF file as comments, so they should be readable on your smartphone.

The thing is, to reduce the size of the RSGF file, all data are now saved as non standard SGF properties, and formatted nicely by GRP when reviewing the RSGF file. It reduces the size, and so the data are latter displayed in English/french/German based on the user setting. But converting back to SGF brings those data back in SGF comments, readable on any SGF editor.

[Dontbtme]

Really? Cool!
To be honest, I saw that GRP evolved quite a bit, but since I've been really busy lately, I wasn't able to get the hang of all its features yet... but since you posted a link to the documentation above, that means I'll finally be able to