On 20-nov-08, at 14:03, Michael Williams wrote:
You could simply allow the pass all the time. Early in the game,
it will be a significantly inferior move and not often explored
in the tree. That may not be optimal, but it's certainly not
convoluted and you are guaranteed to never fail to generate the
pass move when you needed it.
I remember that's how I implemented it initially. I do not
remember the exact details of why I moved away from that, but I
believe that (in part) it had to do with the program occasionally
passing too early in the game.
When you say "too early", do you mean before the game is decided or
before all dead stones are removed. Only the first one is truly
too early.
In other words, there is no harm in leaving a dead stone on the
board given that it does not impact who the winner is.
The problem is there were large interval's while working on it. So
sometimes I don't exactly remember why I made certain decisions. (The
older you get, the more you learn how important it is to document
these kind of decisions ;-( )
I only remember being particularly annoyed by it. So possibly it
occasionally passed too early in both cases you mentioned. It's also
possible that it was a solution to a problem that doesn't exist
anymore due to other changes / improvements in the code made in the
meantime.
Mark
_______________________________________________
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.org/mailman/listinfo/computer-go/
