RE: computer-go: Most simple Go rules

["Mark Boon" <tesuji@xxxxxxxxx>]

You don't have to run both Go programs on the same computer. The referee
program could be on one of the computers of one of the competitors or on a
different computer alltogether, causing little or no overhead.

I've never seen the GMP as a satisfactory solution. Wouldn't it be much
better to use a Go server as a tournament referee, having all the programs
communicate through TCP/IP? In straightforward cases, the server can run on
one of the competing computers, in bigger tournaments you can reserve an
extra computer for it. It also puts less restrictions on the hardware and
programming language used.

> -----Original Message-----
> From: owner-computer-go@xxxxxxxxxxxxxxxxx
> [mailto:owner-computer-go@xxxxxxxxxxxxxxxxx]On Behalf Of Nick Wedd
> Sent: Tuesday, June 26, 2001 11:18 PM
> To: computer-go@xxxxxxxxxxxxxxxxx
> Subject: Re: computer-go: Most simple Go rules
>
>
> Tom Cooper <coopert@xxxxxxxxxxxxxxxxx> writes
>
> >Perhaps it would be worthwhile agreeing on a computer referee
> programme to
> >manage computer games.  Obviously this would require some
> one-off work from
> >the computer go programmers, but if agreement could be reached then the
> >referee could be used in most (?) computer go tournaments and should
> >i) save human referees from having to make difficult decisions
> >ii) let competitors know exactly where they stand
> >iii) decrease the workload during the competition
>
> I think this code assumes that the referee program and both competitors
> will all be running on the same PC.  There are various snags with this.
>
> Some programs may want to think in their opponent's time.  This should
> not be discouraged.
>
> It allows cheating, by attempting to overwrite bits of one's opponent,
> or of its data.
>
> It allows cheating by setting up interrupts and using them to steal
> one's opponent's time.
>
> >As an illustration of the kind of thing I mean, I have written
> some pseudo
> >C++ code.
> >This is not meant as a model of programming style but feel free to
> >critisize anyway
> >
> < pseudocode snipped >
>
> 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.
>
> Nick
> --
> Nick Wedd
>