[computer-go] KO in Hashtable-UCT?

chrilly c.donninger at wavenet.at
Fri May 18 02:29:07 PDT 2007


>
> 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.

 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.

>
> Only for balanced cycles.
>
The cycles I have found so far are balanced. Each side captures in turn 1 
stone.

Chrilly



More information about the computer-go mailing list