To: "computer-go" <computer-go@xxxxxxxxxxxxxxxxx>
Sent: Monday, February 14, 2005 11:59 PM
Subject: Re: [computer-go] Computer Go tournament at EGF
And just to be concrete again, SlugGo will rarely take 3
hours per game,
Interesting issue.
In fact, time limits are both necessary and "arbitrary".
1 hour limit is not good for your program, bec. it needs more time to play
strong.
I have the opposite problem, my program plays only one strength, which is
not very strong, but it needs less than a millisecond for a move. It *might*
be that my program beats the current word chapion comp. Go if the time limit
was 250 milliseconds for a game! (125 milliseconds per player).
So, I want the time limit restricted to an absolute maximum of 1 second
instead of 1 hour per game, to benefit *me* and *my* program :)
(I would in fact prefer 100 mSec. for a game, if I speed up the code a
little it should be possible, then every opponent will loose on time :)
For a "real" computer Go tournament, part of the objective is to provide
some interest and excitement for the onlookers, even if these are only
the programmers themselves. Also, there is the need to fit the event
into a schedule. This might best be done with time limits of around
half an hour each. But tradition, and inertia, and the wish not to
exclude many entrants, suggests increasing this to an hour each.