Re: computer-go: Authenticating the identity of a remote go-playing computer program

[Heikki Levanto <heikki@xxxxxx>]

Steve Pagliarulo <s_pagliarulo@xxxxxxxxxxxxxxxxx> wrote:

> 1. For tournament purposes don't allow random play. Allow pseudo random play 
> based on an initial seed (to avoid predictability). For verification, the 
> seed is disclosed and the program will play identically.

As someone pointed out, careful time management can easily produce
non-repeatable play, even without randomness.

If detailed time management has to be disallowed, what do we do about time
limits? Some programs will play better if given more time, so we have to put
a limit somewhere, or risk really long tournaments...

-- 
Heikki Levanto     LSD Levanto Software Development   heikki@xxxxxxxxxxxxxxxxx
               "In Murphy we Turst"