[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [computer-go] GTP and Tourney in SmartGo 1.4

At 06:12 PM 3/12/2004 +0200, Paul Pogonyshev wrote:

David Fotland wrote:
> At 03:01 PM 3/12/2004 +0200, Paul Pogonyshev wrote:
> >A van Kessel wrote:

Maybe there's a misunderstanding.  By "referee" I meant a
third GTP engine that scores finished games if the players
are not capable of that.  At present, none of `twogtp' scripts
from GNU Go distribution has referee/arbiter support, but only
because no one requested that (and we obviously don't need it
for matches between different versions of GNU Go).  If there
are new weak engines that cannot score, authors can ask on GNU
Go mailing list and we will implement this so you can have GNU
Go or whatever else score your GTP matches.
Ah. I thought you were talking about a tournament referee. Of course in
a tournament, the programs will be running on different computers. I thought this
would mean that a 3rd program would act as a referee, and arbitrate between the programs.
Presumably this mans that gtp is running over some network, using TCP perhaps.

I was trying to understand how this is something that could be figured out and coded in
an hour, as someone claimed.

Maybe I don't understand what someone means when they say we should support GTP. When
they compare it with GMP, I naturally assume they are talking about a protocol to communicate between
two computers in a tournament. If GTP has some other purpose, can someone please explain it,
and why I would want to add it to Many Faces of Go.


And if you meant GTP controller for Windows, take one of the
scripts from GNU Go distribution.  Or take one of the Java
GUI programs that support GTP.

> Is there any standard for how to set up the
> Windows pipe involved (presumably some named pipe), since you can't
> do it form the command line like under Unix?
>
> My impression was that GTP was only for GNU/Unix/Linux, where everything
> is run from the command line.  This is not interesting for commercial
> programs, since
> we all have pretty graphic interfaces and run under Windows.  Whether you
> like Windows
> or not, its the only way to get sales.

Unless I miss something, there is still `stdin' and `stdout'.
People working on GNU Go who use Windows never complained about
twogtp scripts being unusable at least not on my memory.

There is stdin and stdout for dos or console programs.  WIn32 programs don't
have this, since they are usually launched from a starrt menu or by clicking on
an icon.  Windows does have named pipes, but I don't know how gtp
supports them.



As you may know, there is a large number of portable programs
(including scripting language; I beleive there are interpreters
for Perl and Python for Windows and Pike works too).  This
implies that there are pipes.  Maybe not the same pipes as ones
that exist in UNIX-like systems, but at least usable enough to
connect to `stdin' and `stdout'.

And if there are no pipes, I have to say that Windows is even
more screwed up than I thought.

Finally, GTP doesn't require using pipes.  All you need is a
controller that can connect via whatever your engine uses for
GTP communication.
Wouldn't this make it unlikely that my program would talk to another one in a tournament :)

David


Paul
_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://computer-go.org/mailman/listinfo/computer-go


_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://computer-go.org/mailman/listinfo/computer-go