Re: [gnugo-devel] Opponent not passing

[Daniel Bump]

>  I only used the regression tests for tuning, and I don't think there
> were examples of this kind in there. However, it does make sense to
> me to do an owl-threats analysis just for one dragon if
> - the opponent has added a stone to a dead dragon, and
> - we are ahead.
> Probably this useful not only in the endgame, and should not cost much
> time.

This is a good idea, and it occurred to me, too, after I sent my
e-mail. This will be easy to implement in dragon.c: if the 
opponent's last move has matcher status dead, run the owl
threats, at least for that dragon.

> Certainly the choice of move that is generated by owl_prevent_threat
> has to be improved as well, see 13x13:73 for a very good example, where
> GNU Go originally played N12. (Note that this would be a situation where
> --owl-threats could really be useful.)

Any ideas for improving the move found?

Dan