Re: [computer-go] how to use GTP in place of GMP

["yonik" <yseeley@xxxxxxxxxxxxxxx>]

An example of why *some* communication protocol needs to be established for
GTP:

I show up at a computer go tournament that has only specified "speak GTP to
stdin/stdout" with
my custom built FPGA go playing machine.  Don comes over to me and says
"hey, let's play".  I say, "OK, how do we do that".  He says "just let me
ssh into your box".  I say "ssh, what's that?".  You see the problems that
can arise (even w/o a non-standard type of machine).

Talking GTP over stdin/stdout *is* a protocol.... it just doesn't fully
specify how to get from one box to the next.  You don't want everyone having
to try to do it ad-hoc.

Talking GTP over SSH *is* a protocol that will get you communication between
different boxes, but you still have to specify other things (accounts,
passwords, etc).

Talking GTP over TCP seems like the most natural choice (easiest, most
ubiquitous).  It does not exclude other protocol implementations however!
one could still choose to just talk to stdin/stdout and use a pre-built
adapter to do GTP/whatever_networking_technology!

I think this has been beaten to death...

-Yonik

----- Original Message ----- 
From: "Don Dailey" <drd@xxxxxxxxxxxxxxxxx>
To: <computer-go@xxxxxxxxxxxxxxxxx>
Cc: <computer-go@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, August 11, 2004 11:54 PM
Subject: Re: [computer-go] how to use GTP in place of GMP


>
> I did  the UNIX remote  shell part  of the GTP  test and it  worked as
> expected and only took 5 minutes to set up.
>
> I'm playing autotest games with  my local autotester program now.  One
> of  the programs is  running on  a computer  in Massachusetts  and the
> other is running on a computer  in Virginia.  I did not write any code
> to do this, all I did was invoke the programs from ssh (a remote shell
> utility.)
>
> The program invocation looks like  this (the first "field" is a handle
> my autotester system uses for reporting.)
>
> progA  ssh don@xxxxxxxxxxxxxxxxx ./playgo -r -b pattern.brain -o A.log -l 3
> progB  ssh drd@xxxxxxxxxxxxxxxxx ./playgo -r -b simple.brain -o B.log -l
3
>
> If I run everything locally it's this:
>
> progA  ./playgo -r -b pattern.brain -o A.log -l 3
> progB  ./playgo -r -b simple.brain -o B.log -l 3
>
> The trick is  making this work in Windows  because you normally cannot
> "log in" to a windows machine to use it directly.
>
> The TCP stuff  you guys are kicking around is a  good solution, but it
> will be interesting to know if it can be solved without any additional
> programming, whether  it's actually done or not  and without requiring
> the GO programmer to worry about TCP stuff.
>
> - Don
> _______________________________________________
> computer-go mailing list
> computer-go@xxxxxxxxxxxxxxxxx
> http://www.computer-go.org/mailman/listinfo/computer-go/

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