Exactly, ooooo o...o ooo.xx xxxxxx
may have ( (*. --- since there exists THREE defend points. I restrict the considtion optics.c +1698 || eye[pos].neighbors > 2 || eye[pos].neighbors > 1 && !is_edge_vertex(pos)) -1698 || eye[pos].neighbors > 1) to get ! !h. --- but that is four space with a half, still can not match Eye: 448 as Gunnar suggests. ( (*. The mechanism to use virtual marginal vertex on half eye is fathomless to me, and I have no idea to complete such a matcher as the exmple. By the way, the amend above can solve position like (;AB[be][bc][cc][dc][ec][fc][hc][gb]AW[ab][bb][cb][db][eb]SZ[19]GM[1]CA[UTF- 8]FF[4]) That is, +------------------------------ |........ |OOOOO.X. |.XXXXX.X yields 1-1-2-2 instead of 1-2-2-2 before amendation. Ya, it is tricky. George Have you tried this on an actual board position? The first case has the eye graph "...!" but in the second case the topological half/false eye analysis should detect both a false eyepoint and a halfeye on the edge, and the eyespace segmentation should find ".h!" which is translated to a graph matching eye pattern 448 for a 0011 value. An example where the same graph is found but the value is different on the edge is OOOOO O.X.O O..XO OOOOO and OOOOO O.X.O O..XO ----- which are matched by eye patterns 6513 and 6504 respectively. There are things that are tricky with the eyespace analysis though, and where we don't have very good solutions. These include marginal vertices of different quality, shortage of external liberties, and cutting points inside the eyespace. /Gunnar _______________________________________________ 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
