Re: [gnugo-devel] How to teach gnugo wonderful tesujis?

[bump]

> 1. Try disconnect()s between the strings enclosing the moyo.
> I fear this would give far too many false postives, where a
> disconnection is only succesful in a readconnect sense, but the cutting
> stones will get captured eventually.

How about a pattern driven call to disconnect through
the autohelper macros oplay_disconnect and xplay_disconnect
with an appropriate action line?

The action line would generate a move reason.

The advantage of this approach is that you wouldn't be
randomly going around the board trying disconnections.
The disadvantage is that you would miss examples for
which real creativity is required.

Dan