I've been having a bit of fun slaughtering gnugo 3.7.13, and came across a case where dragon-status leads to incorrect results.

The position is included. I'm using gogui and the "dragon-status" button, which summons gnugo, and reports that the dragon at B14 is dead.

There are at least two ways to make the dragon live. D12 or C12 will do.

I've attached both the position and the game which led to this little study. Since I'm only an AGA 8kyu, the lopsided win suggests that GnuGo ( level 15 ) must have made more than one serious error along the way.

Hope this helps with debugging.

Attachment: gnugo_collapses.sgf
Description: Binary data

Attachment: gnugo_status_failure.sgf
Description: Binary data

_______________________________________________
gnugo-devel mailing list
gnugo-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/gnugo-devel

Reply via email to