On 31-jul-08, at 19:50, Peter Drake wrote:
I know we had this conversation recently, but I just can't seem to
get my head around writing a ladder reader. What, exactly, does the
ladder reader do?
Our approach was to read out ladders involving the last stone
played. In the playout (beyond the tree), if the attacker can
capture by continuing a ladder, the attacker plays that move. If
the defender can escape by running, the defender plays that move.
Otherwise, a random move is played.
The trouble seems to be that, once the attacker plays, there's
nothing more for the ladder reader to say. At this point, it's
50-50 whether the attacker or defender will play on the defender's
last liberty. Thus, the ladder reader doesn't give any pressure to
stop running when caught in a ladder.
What am I missing?
What you're missing (or so it seems to me) is that it's not to
prevent from running a ladder that is caught. It is to ensure to
escape when you can or capture when necessary to prevent an escape.
And not only the last stone played of course, it could be the
neighbour of the last stone played as well.
Mark
_______________________________________________
computer-go mailing list
[email protected]
http://www.computer-go.org/mailman/listinfo/computer-go/