Yeah, that's always the trouble with these simple heuristics. They may lead to unintended consequences. I guess how it works out in practice depends on what other heuristics you have. For example, if you use tactics to prevent capture of the chains in question, using the rule I proposed may be less problematic than when you don't.
Mark On Mon, Apr 4, 2011 at 6:12 PM, Aja <[email protected]> wrote: >> How about trying not to fill in a false eye unless one of the >> surrounding chains has less than 3 liberties? I'm sure it's not >> perfect, but may be a fairly good rule anyway. > > Interesting idea, Mark. But how about black's E4 in the attached example? > If E4 is not allowed, then in the endgame, the probability to save the F7 > stone is getting lower (even 1/3 lower, if E4 has the same probability with > E7 and F6). Then it will cause problem when the game is close, espeically if > F7 is a bigger string. > > Aja > _______________________________________________ > Computer-go mailing list > [email protected] > http://dvandva.org/cgi-bin/mailman/listinfo/computer-go > _______________________________________________ Computer-go mailing list [email protected] http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
