[computer-go] KO in Hashtable-UCT?

[Erik van der Werf]

On 5/18/07, chrilly <c.donninger at wavenet.at> wrote:
> >
> > Non-capturing moves can create repetition (but there will of course be
> > captures elsewhere in the cycle).
> So far the SuperKOs I have found where a "round-trip" of KOs.

Maybe the others are just hiding from you ;-)


>  Fortunately, there are other simple
> > criteria. E.g., you can stop whenever a move is played on an
> > intersection for the first time.
> >
> Okay.
>
> >> If a SuperKO occurs, the position is evaluated by the Material-Balance.
> >> BlackCaptures - WhiteCaptures + Komi.
> >
> > I guess you mean the *change* in material balance after one cycle. I
> > don't see why komi should be used here.
> >
> No. I assume the game is over. As there is usually no reliable method for
> counting territory I use the difference of the captured stones as a - first
> approximation - for the evaluation. If e.g. both sides have captured - in
> the whole game - the same amount of stones, the eval is 0, but white wins
> due to Komi.
> At least for significant differences in captures this is true. MC-Runs are
> also stopped, when one sides leads in Capture by a large margin.
> Depending on the margin it produces only a negible bias.

Hmm... To me it seems more natural that the evaluation primarily
depends on the nature of the cycle. Your program may choose to play a
cycle because of some arbitrary material balance value, which will be
meaningless if you can't break out of that cycle. IMO you should
simply treat balanced cycles as draws.

Erik