Re: [gnugo-devel] Bug in critical status ?

[bump]

> Does anybody know why the N4 white dragon is critical  when the
> engine is started at move 68, but not when GNU Go plays the game?
> Or, maybe more importantly, where I should look in the
> code to try to figure it out?

Presumably this is a persistent cache effect. The result
of owl reading is cached, and not repeated unless moves are
played in the active area for the read result. But if the
active area is too small this can give a wrong result.

Dan