On Jul 20, 2007, at 8:04 AM, Jason House wrote:
On 7/20/07, Peter Drake <[EMAIL PROTECTED]> wrote:
On Jul 20, 2007, at 7:23 AM, Jason House wrote:
Thanks for the documentation. I have a few questions.
Looking at only the four neighbors to detect eye-like points seems
like it could leave many false eyes and allow captures of dangling
chains. Is there any mechanism to avoid this problem in the play
of the bot?
It does also look at the diagonals; see Board.isEyelike(). I'll
note this in the next version of the document.
I lost a game in the most recent tournament from a buggy
alternative to isEyelike. I believe that it may be a bug that
affects many, but I'm not really sure... That makes me especially
interested in seeing how others do it and the trades they accepted
for it.
My program disallows playing in eyes (string of empty surrounded by
self) unless a neighboring stone is in atari. That catches your
special-case, but is not good for saving tails (strings connected by
false eyes, often found along the edge of the board).
Ian
_______________________________________________
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.org/mailman/listinfo/computer-go/
