On Jul 7, 2010, at 1:13 AM, Peter Drake <[email protected]> wrote: > Our hash codes are longs, incorporating: > > - The stones on the board (Zobrist style) > - The current color to play (all bits are flipped if it's white to play) > - The current simple ko point (also Zobrist style) > > The last item was the catch. In a transposition table, you want to include > the simple ko point, because you don't want to conflate two states, in only > one of which some point (possibly a key point) is illegal. In the superko > table, on the other hand, you do NOT want to include this information, > because a repetition of a previous position (with the same color to play) is > a repetition, regardless of the simple ko point.
If this is used as the key to your transposition table, are you ok with two physical stone collections with different legal moves being treated as _exactly_ the same search node? This can lead to subtle bugs. > _______________________________________________ Computer-go mailing list [email protected] http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
