RE: computer-go: Applying Moore's Law to Computer Go

["Xu, Mousheng (SEA)" <moushengxu@xxxxxxxxxxxxxxxx>]

-----Original Message-----
From: Jeff Massung [mailto:jmassung@xxxxxxxxxxxxxxxxx]
Sent: Tuesday, November 23, 1999 7:51 AM
To: computer-go@xxxxxxxxxxxxxxxxx
Subject: RE: computer-go: Applying Moore's Law to Computer Go


>My problem might be
>that, for every move, the program needs to do a lot of other stuff than
>simply evaluate the move. Activities include game control (who is next
>turn), rule validation (is it a legal move), board update (does it
kill?
>update safeties of groups ...).

I have this problem, too.  Especially calculating for "ko", because
every 
call I make to IsValid() basically places the piece on the board,
updates 
everything, and then checks to see if it is the same baord position-2.
This 
takes way too much time.  Anyone found something better?

* There is a better way. Here is my logic: if a move 1) captures one
stone; 2) is surrounded by non-own stones; 3) has one breath, then this
move creates a ko at the captured enemy stone position.

-- Mousheng