On Sat, 2008-10-11 at 16:55 -0400, Don Dailey wrote:
> To fix this I would have to test every move just to see if there is a
> ko
> situation (although there are no doubt some shortcuts.)

One shortcut is to simply not test for this until after you make a 1
stone capture,  then test all possible moves for the previous position.
But of course this greatly complicates most implementations I fear.   

An extension of this shortcut is to delay ALL testing until the number
of 1 stone captures indicate that you need to test N previous positions
for KO.   This would not be easy for me unless I were to accept the
slowdown of using my slow move maker in the playouts.   My slow move
maker maintains full state between moves.  


- Don

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
computer-go mailing list
[email protected]
http://www.computer-go.org/mailman/listinfo/computer-go/

Reply via email to