[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[computer-go] A superko paradox
While most ko detections are easy (if this point has never been
captured, playing here can't violate ko), I occasionally have to check
if the current configuration has occurred before. While most of these
checks are quick Zobrist hash comparisons, occasionally two positions
will hash to the same value. Thus, I have to store the entire board
configuration with each move. This is a frequent, expensive operation
to deal with a situation that is very rare, but can happen.
Is there any way out of this?
Peter Drake
Assistant Professor of Computer Science
Lewis & Clark College
http://www.lclark.edu/~drake/
_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://www.computer-go.org/mailman/listinfo/computer-go/