RE: computer-go: Most simple Go rules

["Grajdeanu, Adrian" <adrian.grajdeanu@xxxxxxx>]

I'm not clear on time... If I write a program that moves at least every 5
seconds, in one hour it will have time to move more then 720 times. Counting
the opponent the same, in one hour there is time for 1440 moves. Too long by
all reasonable standards I would think.
But then if there is no limit for the number of moves, I'm fine with that
too.

Adrian


> -----Original Message-----
> From: Nick Wedd [mailto:nick@xxxxxxxxxxxxxxxxx]
> Sent: Wednesday, 27 June, 2001 02:47
> To: computer-go@xxxxxxxxxxxxxxxxx
> Subject: Re: computer-go: Most simple Go rules
> 
> 
> In message <5144A3121B37D411BC0100508B955A1801024AD2@USPALX20>,
> Grajdeanu, Adrian <adrian.grajdeanu@xxxxxxxxxxxxxxxxx> writes
> 
> >> I don't like 
> >>    const MAXMOVES=500;// a draw will be declared after 
> this many moves
> >> This is not like anything in any published rule set.  It does 
> >> not solve
> >> any problem.  It encourages unsporting behaviour.
> >
> >Still Nick, what would you do if the players would want to 
> run forever.
> >Current professional programs won't, but I may enter into a 
> competition two
> >programs that I wrote and they would tend to do that. How 
> would you want to
> >have it handled? Personally I'm neither for nor against the 
> MAXMOVES=500,
> >just looking for your oppinion.
> 
> I would enforce "sudden death" time limits - or some kind of 
> time limit
> that eventually becomes inextensible, like Ing time-purchase.  One of
> them would run out of time.
> 
> Nick
> -- 
> Nick Wedd
>