Bill Spight wrote:
One thing that I have noticed with the Elf annotated files is that Elf will frequently judge the human response more favorably than its top choice, especially when the human response was not on Elf's radar. Usually this may be considered noise, but it yields the possibility of coming up with alternative lines of play that may be better than the original ones produced by Elf. I don't know if that happens with KataGo, but I would try setting the komi for KataGo so that the winrate estimate is approximately 50% and seeing what happens. I am not talking about rare or unusual positions, but fairly common and everyday ones.

Dear Bill,
I am sorry, but I can only report on my experiences with the combination of KataGo and Igo Hatsuyôron 120, and here below especially for positions, for which we assume that KataGo has not sufficiently encountered these during the selfplay training. Simply because these positions are quite interesting for further comperative analysis, but "hidden" behind several mistakes of both sides (so there is no reason for KataGo to visit especially these positions during training). And yes, Igo Hatsuyôron 120 is kind of special, just because some decisive effects in the longish sequences seem to be far behind KataGo's event horizon, and so unavailable during "play" / "analysis".
You are right with emphasising the need to vary the komi during analysis. There will be cases where you will have to do so per move.
In my experience, it is especially important to achieve a win rate level (around 50 % likely) that stops KataGo from considering / favouring "desperate measures" for the side that seems to be too large behind for winning the game. These "desperate moves" are likely to result in an even worse result at the end of the game (human understanding, in points). On the other heand, you cannot trust that the side that is largely ahead (in win rate) favours the "best" move (human understanding, in points).
During this process, you must forget what you know about the position / result. It seems to be best to let KataGo believe -- based on its OWN analysis, not the absolut truth -- that the current position in nearly balanced.
However, you will encounter positions / sequences that are extremely sensible with varying the komi. In these cases, you will have to go back and forth some times, until you have a better understanding of what is going on.
There will be also positions, which ensuing sequences have several "local" maxima (human understanding, in points => several lines for winning the game, but with different scores at the end). If you vary the komi in these cases, it is likely that KataGo's favourite moves / sequences differ, dependent on which "local" maximum (being enough for winning the game with the current komi) is the nearest.
With Igo Hatsuyôron 120, we have the large advantage that we (believe to) have a quite good understanding what is going on, and indeed can find moves (sometimes) that are better (human understanding, in points) than what KataGo recommended, based on the current knowledge of the special net.
Based on this understanding, we can provide the selfplay training with suitable material for the database of starting positions to be examined (besides much more that KataGo chooses automatically). It needs a long time until KataGo has had so many selfplay games started from these positions that it will sustainable adjust its network, and also come up with the then "correct" line of play during "play" / "analysis".
To come back to the beginning:
The effect you described with Elf might have a similar reason. In a position that is "unknown" to the network used I assume it definitely possible that a human choice will be assessed better than the AI's favourite, once the stone has been put on the board. If the AI cannot rely on the knowledge in his network, but is dependent on its processing power only, you cannot be sure that the AI's favourite is really the "best" move.
_________________
The really most difficult Go problem ever:
https://igohatsuyoron120.de/index.htmIgo Hatsuyōron #120 (really solved by KataGo)