Re: [gnugo-devel] Decide dead stone

[bump]

> i wouldn't recommend using dragon_status since it might have some problems
> in its current state. since recently, ld_owl:161 failed, though owl correctly
> understood the position if asked through owl_attack and owl_defend. this
> test now passes, but that's not because dragon_status has been fixed. so,
> i don't think that using it is a good idea.

GTP dragon_status reports the dragon status, which is initially
computed by make_dragons using the owl code and crude status,
but which can be revised, notably by the semeai code. This is
the status that is used by the engine during the move
generation. So it may be wrong, but it is the most reliable
answer GNU Go can give.

The change in ld_owl was due to the experimental semeai
code being activated in 3.3.14.

Dan