Hi,
Do you have an example of your 2nd diagram in SGF format ? It feels
strange to me that it evaluates to
!
...
I would have expected either
!
!..
or maybe simply
!..
So I'd like to check how the engine comes to that result.
nando
On 3/29/07, George Zhong <[EMAIL PROTECTED]> wrote:
Some eye patterns seems not suitable to be applied on the board edge.
Following condition (3.7.10, recognize_eye() in optics.c, line 1301)
if (neighbors[mv] != gv->neighbors
|| marginal[mv] != gv->marginal
|| edge[mv] < gv->edge)
implies that GG hard code always take space on the edge as advantage, but it
may be the opposite.
For example, Eye Pattern: 420, which yields 1-1-1-2, typically,
ooooo
o...o
ooo.xx
xxxxxx
the following position can also matches unexpectedly, and, of course,
missing the vital point.
--------------------------
o...o
ooo.xx
xxxxxx
I am not sure which solution is side-effect free, setup constraints or split
up those patterns?
George Zhong
_______________________________________________
gnugo-devel mailing list
gnugo-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/gnugo-devel
_______________________________________________
gnugo-devel mailing list
gnugo-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/gnugo-devel
