gunnar:45

45 reg_genmove black
#? [K1]

Isn't K1 a full point for black ?

---

It sure is. I have no idea what's up with this but apparently the original problem (move at H13) has been solved, so now remains the question why K1 isn't found. Looks like a missing endgame pattern to me. The answer should of course be changed from [Q7|Q6|J16|J17|E7|N4] to K1.

/Gunnar

---

Changing EE5 as following:

Pattern EE5

???
XO?       descend to edge
.*?       may quite possibly be 0 points gote
---

:8,OXe,terri(0.1)

eab
XOc
.*d
---

;o_somewhere(a,b,c,d,e)

seems to solve the case and apparently solves kgs:720 as well, without adverse effects.

720 reg_genmove white
#? [A15]

I tested it on my ggexp branch though, not sure what it does for CVS.

--nando

---

The change looks fine to me, but I don't really understand why the constraint is needed in the first place. Apparently it was introduced by the patch arend_3_20.8. See also http://lists.gnu.org/archive/html/gnugo-devel/2003-05/msg00129.html. Maybe Arend remembers the purpose.

/Gunnar

I added this constraint exactly for the posistion at quoted at the beginning of http://lists.gnu.org/archive/html/gnugo-devel/2003-05/msg00129.html. Nando's revision seems fine of course. --Arend