yup - that was it. thanks.

Hi everybody, that's me again!

One more update regarding v0.6 that should be released this week. Leela 0.10 has been released last week, and GoReviewPartner v0.5 works just fine with that latest Leela. The new Leela GUI now displays the moves sequences with numerated stones on the Goban just like uses to do GoReviewPartner. I would like to believe that GoReviewPartner prompted Leela's author to implement the same feature, but that's probably not the case

I was reading the comments about Leela on Reddit, and somebody mentioned an improved influence GTP function. I had not noticed that Leela had such function, so I just had a look and implemented the result into GoReviewPartner the same way GnuGo territory is implemented. Here is the result for the same position as in the previous screen-shot for GnuGo:
Two things to notice:

• It's an influence function, not a territory function (I will rename the button) so comparing GnuGo and Leela maps is probably not a good idea
• I noticed Leela provides the data instantly when asked for the map, it must be some sort of fast heuristic (so no simulation or whatever)

As for what I mentioned in the previous post, about completely separating GnuGo and Leela, this is now completed. So before running the analysis, the user is asked what bot to used:
This forced me to make some big code factorization, but the resulting code is (hopefully) much cleaner and it should be easier to finally implement support for additional bots.

All this new code has been pushed to GitHub already, but not heavily tested yet.

_________________
I am the author of GoReviewPartner, a small software aimed at assisting reviewing a game of Go. Give it a try!

such a fickle friend of the gnu - you have now made it possible for the discerning customer to ignore the old cow completely.

at last!... thank you very much!

Can you please add "Net Win %" instead of "Net Prob %" (it's the last row on the right screen)? It's very useful number to evaluate the game, much better than MC... Can you please add it on the left screen too (for the current position as well as variations)?

Thanks for contributing to the go community with this app! I find it very useful and use it very often to analyze what was the best sequence in my tournament and online games. I tried replacing Leela 0.9.0 files with 0.10.0 and it works just perfectly.

@pnprog thx it looks great.

Can you create an ios version?
It would be great to have it on the ipad pro 12.9 screen and especially on the ipad pro 2 and iphone 8.

Hi johnsmith,

Thanks for your positive feedback, it's very motivating for me!
If I am not wrong, it is what GoReviewPartner calls black/white win probability, or am I wrong?

_________________
I am the author of GoReviewPartner, a small software aimed at assisting reviewing a game of Go. Give it a try!

Hi goame,
It is unlikely that Leela will run on ios anytime soon (if ever). So the analysis part would not be available on ios or android.

It would be possible to have a application of ios/android for reviewing the *.rsgf files just like a viewer (without possibility to test alternative sequence against Leela), but it would have to be another project, because the graphical framework I use (tkinter) is not available on ios or android.

One possible option would be using Kivy, another graphical framework dedicated to touch interface. I did experiment with it and made some small go applications on my android phone last year, so it would be possible. But the "work-flow" would be awkward: running the analysis from computer, then transferring it on the tablet, then reviewing it. Plus, some "mouse gestures" (like "mouse over" or "mouse scrolling") would not be available on tablet, so the interface would have to be rethink from scratch.

So... yes, another project

_________________
I am the author of GoReviewPartner, a small software aimed at assisting reviewing a game of Go. Give it a try!

Hi everybody!

Here come v0.6 !

So v0.6 does not really bring new features. In fact, this version is more about "polishing" the software (code cleaning, code re-factorization, better error handling) and is a big step forward v0.7 that will add support for Alphago that will add support for Ray.

So what's new:

• Separate analysis for Leela and Gnugo
• Territory map for GnuGo and influence map for Leela
• A few more settings to review a game
• Possibility to export an image for the gobans (postscript for now, i will try to change it for png later)
• Tons of bug fixes
• v0.6 for windows ships with Leela 0.10 (but v0.5 was working fine already)

Same as before, there is a direct download for GoReviewPartner+Leela for Windows users.
For Linux/Mac, it is best to get the source code from Github.

So next step is adding support for Ray, zakki, the author of Ray, has just added a feature (a GTP command) to allow GoReviewPartner to get similar data than what it get already from Leela (best moves and sequences with %win rate). So I just started playing with it, in fact, I have the analysis/review part already quite working, I need more testing and integration to complete v0.7

I target to release v0.7 before the end of the month.

_________________
I am the author of GoReviewPartner, a small software aimed at assisting reviewing a game of Go. Give it a try!

Thanks for all the great work, I'm sure many many more people appreciate it than just those who liked your post

What I meant in one of my previous posts was explained on the very, very simplified example (maybe even stupid example even though I'm dan player) in the attached images.

Image 1: first column is some kind of average of second and third column, while fourth is the probability of pro player spotting that move.
Image 2: if I understood GoReviewPartner correctly, then these columns are represented in this particular fashion as shown.

With current version I let GoReviewPartner analyzes the game for one hour, and then I have to switch to Leela UI to check number 3 (Net Win%). Which is small effort for me but still it's an effort What I'd like very much to have is number 3 in both current game window and variation window.

Cheers!

Hi!

Below is the "dialogue" that will happen between GoreviewPartner and Leela "in the terminal" (this is the GTP protocol), for the same board position (I assumed a komi of 6.5) (blue are messages sent by GoReviewPartner, and red replies by Leela):
The interesting part is:
So the information currently displayed are:

• Black/white win probabilities: W: 83.23%
• Number of play-outs: 29533
• Neural network value: N: 21.9%

So we are left with those 2 informations: (U: 64.20%) and (V: 90.80%: 668) and I don't know what they mean. Is (V: 90.80%: 668) the one you want? (to be understood as 100%-90.80% for white maybe? so 9.20%)

_________________
I am the author of GoReviewPartner, a small software aimed at assisting reviewing a game of Go. Give it a try!

Yes, (V: 90.80%: 668) is what I'd like it is the same like those parameters above:
W => Win
U => Monte Carlo (MC)
V => Value Network (VN)

The thing is, similar to this example, that MC can sometimes show evaluation of 50% while value net can be as high as 75%. So MC might trick you the game is even, while value net tells you how things really are. The same thing goes for Win since it takes MC into account...
So you're right - since it is white's turn it means white is leading by 90.8%, and black is losing by 100-90.8=9.2%. That number 668 I have no idea what it means

edit:
for black I think...

V is the value network win rate estimate. It moves much quicker, and generally is more accurate, than the U (Monte Carlo) win rate. However it is subject to blind spots where it makes errors (like the policy network does) so the author uses a weighted average W of the U and V values (bit heavier weight on the Monte Carlo value) for the decision making process when Leela does tree search.

N is the policy network based odds a pro player would choose that move. The tree search is seeded and weighted based on the N values. If a move has an N value of 0, Leela won't consider it, which can lead to the rare "blunder" moves where Leela just can't see a move.

The number after the V % is (I think) the number of nodes evaluated by the value network in that variation. The NN evaluation, even with GPU, is much slower than the tree search itself can explore.

Ok, so it seems I was quite wrong regarding all those values
I will fix that quickly and add all those values in a v0.6.1 that I will try to release tomorrow.

_________________
I am the author of GoReviewPartner, a small software aimed at assisting reviewing a game of Go. Give it a try!

Hi!

When trying on a 9x9 games, I got this type of data from Leela instead:So:

• 17924: Number or play-outs
• (U: 89.10%): I guess this is still the MonteCarlo search result
• (R: 87.78%: 33386): Do you know what that one would be?
• (N: 144.9%): Apparently, this is: Eval: displayed in non-19x19 games instead of Net Prob%. A dimensionless number expressing the likelihood of the move being good, based on a pattern database and the moves' features.

Best regards,

_________________
I am the author of GoReviewPartner, a small software aimed at assisting reviewing a game of Go. Give it a try!

9x9 is really puzzling.

Agreed!

But anyway, I made the modifications to now clearly indicate the MC values, policy values, network value. And the enigmatic R% value for 9x9 or 13x13.

This is the v0.6.1 available for download there: http://ns1297.imingo.net/ (or github)

By the way, the windows download is set up to use the non-opencl version of Leela, so if your computer can run Leela with GPU, make sure to modify the command line in the Settings menu.

_________________
I am the author of GoReviewPartner, a small software aimed at assisting reviewing a game of Go. Give it a try!

It is the RAVE value. See here:

viewtopic.php?f=18&t=13692&p=216390&hilit=rave#p216390

Thanks pnprog!

This tool makes me wanna play more deep and serious games! It's like having a strong teacher that can pinpoint your mistakes.

Players on reddit have noticed that a completed file was 2.3mb large and as such can't be uploaded to websites for online review. I am not a programmer myself but I have awful lot of ideas Maybe there can be a 'save as' option to keep the comments only for the main variation. File as such probably wouldn't be that large. And keep all other comments in the original app. Or just say "W=..., MC=..., VN=..." so the file will definitely be smaller. Some people suggested a toggle for various stuff, too.

My other idea is to have a graph in the app, below the left board for example, that will show you graphically where the game went wrong. Sgf will be smaller that way. I hope pngprog will like this idea Just like in Leela with 3 colors. And I just hope it is not a violation of copyright, right? When you have visual representation of the game you can easily notice which move was wrong and specifically analyze that one. When I briefly see difference between two moves with evals like 55.xy and 56.xy I immediately think it's not a bad move, but it may be almost 2% difference (56.99-55.01).

The third idea is to have all those evals (Win, Monte Carlo, Value) on the left board as well. Though file will be extremely huge, but oh well

Hi!

Thanks you fore your comments. Redditors are right to say that it could be improved. In fact, all the comments from Leela for all variations are duplicated for each move of the variation... this is redundant, and so useless. You can see it if you open a rsgf file using a standard sgf editor (rename the file from *.rsgf to *.sgf).

I had never noticed that, so I fixed that for the next version (already on GitHub). I think this should already make for a huge size reduction.

I never imagined somebody would go as far as renting Google cloud computers and run GoReviewPartner on it that much power allows for a lot of branches, all branches being very deep. Hahaha, it's cool seeing people doing unexpected things with GoReviewPartner

Then, the real constraint is the sgf format. It's a standard, and so, I cannot take too much freedom with the format standard, otherwise the compatibility with other sgf editors (or eidogo) will be lost. I encourage you to open one of your sgf files using the windows block note (drag and drop the sgf file directly into it) to get an idea of how it work.

"W=..." instead of "black/white win rate for this move is..." will definitively help, and it could be a toggle. Another toggle to deactivate the influence analysis would help also.

Otherwise, the long term solution would be, in my opinion, to issue a new sgf standard, that takes in consideration all the new possibilities brought by computers being now stronger than humans. The last version of this standard, FF4, is already 20 years old. The new version could include standard properties like MTCS score, win rate, number of simulation.

In fact, I am considering introducing a few new properties in my rsgf files to make things easier (like drawing a win rate graph). If I am careful enough, I can do that without breaking the compatibility with FF4 readers (they would just ignore the new properties).

I guess there would be not copyright issue with a graph (such graph already existed before Leela, for example in The Many Faces Of Go). It is just that sgf format is not intended for that, I need to find a workaround.

_________________
I am the author of GoReviewPartner, a small software aimed at assisting reviewing a game of Go. Give it a try!