when using the new feature of AI analysis for 9x9 games, passing apparently screws up the winning probability graph. It shows something like 100% for the player whose turn it is after a player passed. Also, there are no moves printed on the board. Take a look yourself at this example: https://online-go.com/game/view/20952322
It’s not exactly a bug. Like other “zero” bots, KataGo basically uses Tromp-Taylor rules (https://senseis.xmp.net/?TrompTaylorRules), which are the simplest possible form of rules to implement. Under these rules, you get only score for the space you surround that has no opponent stones in it. So if there are “dead” stones, you have to actually prove them dead by capturing them.
If you end the game without doing so, then technically under Tromp-Taylor, that area is not your territory yet, and passing would indeed be a fatal mistake (much like it might be a mistake under human rules to pass when your territory has an unfinished border, regardless of whether you would be winning if the border was finished). So it’s a little less of a “bug” and more like “mismatch between computer rules vs human rules, computer is analyzing correctly under one particular ruleset but that ruleset is the wrong one for human analysis”.
@anoek For now, you can fix this just by skipping analysis on any move that follows an opponent’s pass. You can resume analysis on any moves after that pass if they are not pass moves, because on any moves that are not immediately following a pass, there should be no danger of the game ending.
I’ll add a hack in the next release of KataGo where you can configure it to assume that passes cannot end the game for the purpose of analysis, which should address the rules mismatch here.
Just wanted to add that this “passing bug” also occurs at my local KataGo at 19x19. Even on finished boards, sometimes, not always, at the very end when a pass occurs, the graph swings from black to white or vice versa, only to swing back in the next move. And if you run the analyis at that point, it will give the correct result.
If you have a sgf for which it happens on the newest KataGo version ( 2020-04-03T22:00:00Z v1.3.5) on your own installation, please submit it to the KataGo issue tracker. Maybe they have an idea why this happens. At least they should know it happens, so they can fix it some day.
It’s usefull to check first if you haven’t overlooked a L&D.
Will do. Not sure I want to recheck all my recent games… there were a handful out of a whole lot. I’ll upgrade to 1.3.5 today (mine is 1.3.3 so not actually the very latest) and see if this will happen again.