Re: [computer-go] double threats

[matth1@xxxxxxxxxxxxxx]

If such a decision leads to one group. the lesser one, being sacrificed, then that group should be deemed to be dead (at least for the time being, in Go, dead groups can re-animate in complex fights) while the status of the other group is still in question. If a move is available to stengthen it, then that move will still lead to it either being alive or unclear. The status of the important group is an isolated question, it does not depend upon the status of a group already discarded.

Matthew Holton

>  from:    Jens Lieberum <jenslieberum@xxxxxxxxxxxxxxxxx>
>  date:    Wed, 07 Jan 2004 18:28:27
>  to:      computer-go@xxxxxxxxxxxxxxxxx
>  subject: Re: [computer-go] double threats
> 
> Go programs often analyse the tactical status of blocks (sometimes called strings) of stones. A block tactician performs some local search and then assigns the status ALIVE, DEAD or UNCLEAR to a block.
> I have the problem how to treat double threats in this context. Let's say that two blocks are threatened and the defender may choose which block he wants to give up. Then the block tactician might treat the two blocks as "half-DEAD" or it might treat the bigger (or "more important") block as ALIVE and the smaller one as DEAD. None of these solutions is really satisfying and some special treatment seems to be necessary.
> Since the situation is often too complex for a global quiescence search, a good solution of a direct evaluation of double threats might be helpful. Does anybody know about a good solution of this problem?
> 
> Jens 

_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://computer-go.org/mailman/listinfo/computer-go