On Thu, 2008-07-31 at 15:50 -0700, 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?
I haven't implemented this yet, but... I'd have the ladder reader output one of two values: working ladders and broken ladders. An attacker should (only) continue a working ladder and a defender should (only) continue a broken ladder. It's important to detect if the status of a ladder changes. I know an early mogobot had a bias in the random playouts to capture stones in atari. > > Peter Drake > http://www.lclark.edu/~drake/ > > > > _______________________________________________ > computer-go mailing list > computer-go@computer-go.org > http://www.computer-go.org/mailman/listinfo/computer-go/ _______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
