Life In 19x19

jlt wrote:

sanderl wrote:Try 'P:weighted' and see how it feels.

I just played a couple of quick games. In the first one I resigned quickly after losing a group. I won the second game by 18.5. The game felt pretty natural for about 150 moves, but the AI started playing strange moves when it was behind, wasted ko threats although a ko was going on, and didn't see immediate threats at the late endgame.

Yeah wasting ko threats is a very persistent issue. I guess atari/throw-in is fairly high up there in terms of policy and the score loss of ko threats is fairly minimal.

There's some interesting work going on in this github issue.
A contributor developed some calibration for playing a reasonably even game against gnugo and pachi, leading to a new AI option. However, the next step is even more challenging: can we invert this and estimate someone's rank from their moves automatically?
I'd be interesting in hearing if any of you have ideas about this.

Just want to note that I just installed KaTrain on my iMac (June 2017, 27" Retina 5K, macOS 10.14, 32 GB RAM), installation was a breeze following your installation instructions, just a few Terminal commands copy/pasted, and your Teaching Game option simply blew me off my feet, this is SO! AWESOME!
Very nice also that I can use it to play against a calibrated version of KataGo, so I can use this very strong AI to play against an opponent who is just a little bit stronger than I am while learning better moves. (Of course I still prefer human opponents for “real” games but as a tool KaTrain is wonderful!)

I immediately decided to sponsor your project (albeit with a small amount only) on https://github.com/sponsors/sanderland, as I think this is an extremely valuable tool for learning.

Before, I hesitated to install KataGo etc. because I was afraid it would be too much fumbling, but KaTrain makes it all very easy.

Screenshot:

Just out of interest; if you take a weight file from a STRONG neural net and change just some small part of its contents, what will that do to its strength? Is it a sick hack too far?

Sander,

I’m not sure where the best place is for a support question, so I’m asking it here:

Re: “models” I’m a total n00b when it comes to using modern Go AI apps, understanding close to nothing of “weights”, “playouts”, visits, “depth” and “width”, etc.—how do I know which the “best” model for which purpose?

TIA,
Tom

Here's some guidance on that question (scroll down a little from here to the "Which model/network should I use?"). Anyone should feel free to relay this guidance. You might have to drill down into the links there to see which models match up with which models that katrain is showing you, but the general point is that bigger nets are slower to run but stronger. Often stronger enough to compensate or more than compensate being slower, but depends on hardware.

https://github.com/lightvector/KataGo#other-questions

Thanks a lot, @lightvector!

Hi,
Just my two cents : after a bot is weakened, it would be a good thing to prevent it to ignore important ataris.

It feels really unnatural and disappointing when you play atari to a huge chain of stones and the bot just doesn't see it. Capture, game over.

Pio2001 wrote:Hi,
Just my two cents : after a bot is weakened, it would be a good thing to prevent it to ignore important ataris.

It feels really unnatural and disappointing when you play atari to a huge chain of stones and the bot just doesn't see it. Capture, game over.

It tries to do this by making 'important enough' moves non-optional, but it can be hard to determine which ones are important enough. However, a super hard to see 30 point life and death problem and a 15 stone atari can be essentially equivalent.
Also when this is a bit too highly tuned, it's easy to get an AI which is accidentally high dan.
If you save example games in which this happens and send them, it will help in creating something that might avoid this.

How about making weak KataGo not playing a move worse than what low level GnuGo would pick. That would probably be a reasonable way to discard wacky bad moves a 25 kyu wouldn't do.

Uberdude wrote:How about making weak KataGo not playing a move worse than what low level GnuGo would pick. That would probably be a reasonable way to discard wacky bad moves a 25 kyu wouldn't do.

How do you know a move is better or worse than a certain level of GnuGo?

The only thing you have is:

* The policy network values, as a probability map over all moves
* The score/win rate/lcb/utility for the current position for a limited number (~10) of moves.

Most weaker AIs just use the policy, which is around 5d by itself, but does on occasion make mistakes. Less so for the 20b network, but still.
The new KataHandicap setup allows to submit additional queries apart from the one for analysis, so it could be used to double-check the move chosen based on the policy (and then? play the top move instead?) but it requires some serious testing. It can easily end up as the '15k' AI that suddenly plays like an extremely murderous 9p when you invade a moyo.

sanderl wrote:

Uberdude wrote:How about making weak KataGo not playing a move worse than what low level GnuGo would pick. That would probably be a reasonable way to discard wacky bad moves a 25 kyu wouldn't do.

How do you know a move is better or worse than a certain level of GnuGo?

Ask strong KataGo.

So my idea the workflow would be like:

1) Generate move suggestion with weak KataGo (from just policy or whatever else you do to cripple it), called wKn, where n is currently 0
2) Generate move suggestion with GnuGo, called g0
3) Ask strong KataGo (doesn't need to be that strong, maybe just 100 playouts is enough) is g0 > wKn in winrate or score? (doesn't matter really which one used)
3a) If n > 10 (or so) play wKn anyway
3b) If yes: get another choice from weak KataGo (either further down policy, or re-roll random number generator), called wKn where n is now n+1, go to step 3 and compare to this new move
3c) If no, play wKn as it's not a retarded move.

Uberdude wrote:2) Generate move suggestion with GnuGo, called g0

This would require packaging another executable for multiple platforms, GTP engine support, with all the UI elements for configuring it and potential errors that can occur.
Way too much work for something like this.

Hmm, I wonder if a query with wideRootNoise can be used for this, that should get back a lot of moveInfos for relatively few visits.

I am a new user of KaTrain! (I have fooled around a lot with katago)

Nice work!

The calibrated rank, what scale is it aiming for (EGF, AGA, IGS)?

Is it possible to let two bots play each other at different calibrated ranks?

Thanks!

When trying to get a calibrated rank, don't you think it could be useful to train a very small net (6 block) to just tell how probable a certain move is to be played by an human? And then just skip moves with a (very) low score.

(I bet an atari on a 25 stone group would get a high score)