gtp

gtp@lists.lysator.liu.se

164 discussions

resignation support in clients?
by Arend Bayer 03 Sep '04

03 Sep '04

The upcoming GNU Go 3.6 release will be able to resign games. (This is already included in the latest development version 3.5.10.) It would of course be nice if as many GTP clients as possible would support this feature by the time it gets released. Arend

6 7

Converting from GTP v1 to GTP v2
by Gunnar Farneb�ck 27 Aug '04

27 Aug '04

Since there are some applications out there which still use GTP version 1, it may be useful with a short guide on how to convert to version 2. On the controller side the following changes are needed: 1. (Optional) Use "protocol_version" to check which version the engine is talking. I don't consider it important to continue supporting GTP version 1 but if you already have the code it should be easy to support both. It may be useful to issue a warning if the engine says it talks version 3 or higher. 2. "boardsize" is no longer required to clear the board. Use "clear_board" for this. You need to do this also before starting the first game. 3. Replace the "black" and "white" commands with "play" commands. In practice this means prepending "play " to what you previously sent. 4. Replace "genmove_black" and "genmove_white" with "genmove black" and "genmove white". 5. Be prepared that "genmove" can also return "resign" if the engine wishes to resign. 6. (Optional) If applicable, use the "time_settings" and "time_left" commands to send timing information to the engine. 7. (Optional) Use the "list_commands" or "known_command" commands to find out which non-required commands the engine has implemented to avoid sending commands it doesn't understand anyway. For testing I recommend to use Brown (linked from the GTP web page), which is intentionally implemented to do many of the unusual things that the specification allows, e.g. starting with a non-empty board. On the engine side the following changes are needed: 1. Implement "clear_board" to clear the board. 2. Implement "play" to do the work previously done by "black" and "white". 3. Implement "genmove" to do the work previously done by "genmove_black" and "genmove_white". 4. If any of the remaining required commands "protocol_version", "name", "version", "known_command", "list_commands", "quit", "boardsize", and "komi" are missing, implement those. 5. (Optional) Implement any other GTP v2 commands you want to support. While this is not required for GTP v2 compliance it increases the number of controller applications you can use. I think this should cover everything. Of course it is a good idea to read through the specification (well, the draft) and check that your code follows it. /Gunnar

1 0

GTP-FAQ?
by Arend Bayer 26 Aug '04

26 Aug '04

Gunnar, would you be interested in a GTP-FAQ for you official GTP, web site? It should answer questions like: Why should I implement GTP in my go program? In which setups can I use GTP? How to set up the communication stream between controller and engine? How do I use GTP to connect to a go server? How do I use GTP to play matches between two programs? If yes, I would make a start that we can improve on together. Arend

6 10

RE: gtp digest, Vol 1 #112 - 5 msgs
by Persson, Magnus 26 Aug '04

26 Aug '04

> > > 6. Windows. > > > > There are several options for the communication stream under Windows. > > > > a) Stdin/Stdout. It is not very widely known that Windows GUI programs > > can use console stdin and stdout, too. See > > This Q&A set makes no sense to me. I am absolutely no capable Win32 API > programmer, but with my mere knowledge I did know that you can grab > stdin/out to a processes on Windows just like you can do on Unix. > A Win32 guru who has never programmed on Unix would rather ask "How can > I do it on Unix?" Your writing suggests Unix is the norm and Windows is > something special. I'd suggest to keep that sort of stuff out of a GTP FAQ. > > I'd remove this whole Q&A set and maybe replace it with something like: > > How can I connect a client to the GTP engine? > > a) Start a process and grab stdin/out > b) Named pipes > c) TCP/IP socket How do I start a process? What is a named pipe? Etc. These are not the answers you need to implement gtp. The purpose of a FAQ is that *the most ignorant person* who reads it should be able to get answers from it. This happens to be me (or was before I did implement gtp by trial and error). I have programmed in Windows for almost 10 years using Delphi. The nice thing with Delphi is that you are Win32 is encapsulated in a way so for me low level windows programming is completely abstracted away. Unfortunately this made it very difficult for me to initially even have an idea how to do things right. The kind of information included by Arend is exactly what I would have needed in order to avoid trial and error and searching for help in the blind. Best wishes Magnus -- Magnus Persson Center for Adaptive Behavior and Cognition

1 0

Computer Go Test Collection 2.0
by Markus Enzenberger 21 May '04

21 May '04

Version 2.0 of the Computer Go Test Collection has been released. The original Computer Go Test Collection version 1.0 was developed by Martin Müller in 1995. The current collection is based on the "specialized collections" subset of the CGTC 1.0. It has been greatly improved in content and restructured to take advantage of current regression testing tools based on the Go Text Protocol (GTP). Information and download: http://www.cs.ualberta.ca/~games/go/cgtc/ We welcome feedback on the test set: modifications and additions to the test cases, alternative good (or bad) moves, and comments about which types of tests are most useful. Martin Müller, Email (in domain cs.ualberta.ca): mmueller Markus Enzenberger, Email (in domain cs.ualberta.ca): emarkus

1 0

Brown 1.0, release announcement
by Gunnar Farneb�ck 29 Mar '04

29 Mar '04

I have released Brown 1.0, a simple go program. This is a random go player implementing GTP version 2. It can be downloaded (as source code) from http://www.lysator.liu.se/~gunnar/gtp/brown-1.0.tar.gz This program is of potential interest to the following groups: * People who want to see an implementation of the engine end of GTP version 2 which strictly follows the specification but is much smaller than the one in GNU Go. (Mainly because it does not have any private extensions.) * People who want to see a reasonably simple implementation of the go board logic. * People who want to test their GTP applications with an engine which strictly follows the GTP version 2 specification but tends to make uncommon choices where the specification leaves details open. (Default board size 6x6, default komi -3.14, starts with a couple of random stones on the board.) Below is appended the README for the program. Boston, March 28, 2004 Gunnar Farnebäck ------------------------------------------- This is Brown, a simple go program. Version: 1.0, released March 28 2004. Main features: * Plays randomly, but avoids filling small eyes. * Portable, written in pure ISO C (conforms to the c89 standard). * Talks the Go Text Protocol (GTP) version 2 on stdin/stdout. * Small code base. Secondary features: * Follows the GTP version 2 specification strictly but makes uncommon choices where the specification leaves details open. * Always correctly scores its own finished games. (Assuming simple ko rule and three passes to end the game.) Author: Gunnar Farnebäck gunnar(a)lysator.liu.se Installation: Compile the three files brown.c, gtp.c, and interface.c together into a binary. An example for gcc is included in the Makefile. Running: Start the program and enter GTP commands. For a smoother interface, use a GTP aware GUI. More information about the protocol and available software can be found at http://www.lysator.liu.se/~gunnar/gtp. Algorithm: All empty vertices are considered, except 1) suicide moves and illegal ko captures (simple ko rule), 2) vertices which would be suicide for the opponent, unless playing there captures at least one opponent stone. The move is randomly chosen from this list of vertices. It passes if the list is empty. Files: README - This file brown.c - Go board logic and move generation brown.h - Header file gtp.c - GTP support code, imported from GNU Go gtp.h - GTP header file, imported from GNU Go interface.c - GTP interface code and main() function License: The MIT/X11 license. See the source code files for details. Copyright: The files gtp.c and gtp.h are taken from GNU Go and are copyright the Free Software Foundation. The remaining files are copyright Gunnar Farnebäck and are independent from GNU Go. Any similarities between those files and code from GNU Go are due to constraints on the code structure imposed by using gtp.c/gtp.h and the fact that corresponding code in GNU Go was written by the same person.

1 0

Re: Random Go Challenge
by Markus Enzenberger 25 Mar '04

25 Mar '04

Gunnar Farnebäck wrote: > In order to get some testing of GTP implementations, and to some > extent because it's interesting in itself, I have started a Random Go > Challenge. For current standings and information about how to > > http://www.lysator.liu.se/~gunnar/gtp/random_go_challenge.html a very nice idea, though probably not a good benchmark for Go programs. The simple algorithm MaxAvgLib which tries to maximize the average number of liberties outperforms all other programs. I am wondering if you plan to make the source for your server available. It might be interesting to extend it for games between programs or even as a server for computer Go tournaments. For easier connection I extended the tool gtpserver, which is part of GoGui (only in the development CVS so far) for doing outgoing connections, you can run it like this: gtpserver -remote sellafield.lysator.liu.se -port 9697 \ -user name_and_password \ "gnugo --quiet --mode gtp --chinese-rules" also, there is a new tool gtpadapter, which can do protocol translation for programs that use GTP version 1 and emulate the free handicap commands with play commands (this is not 100% compliant to the standard, but works well) - Markus

2 1

Random Go Challenge
by Gunnar Farneb�ck 21 Mar '04

21 Mar '04

In order to get some testing of GTP implementations, and to some extent because it's interesting in itself, I have started a Random Go Challenge. For current standings and information about how to participate, see http://www.lysator.liu.se/~gunnar/gtp/random_go_challenge.html The software driving the challenge has only been marginally tested so far and there will probably be some initial problems. But please try to connect your programs and see what breaks and I'll try to fix it. /Gunnar

1 0

GTP version 2
by Paul Pogonyshev 10 Feb '04

10 Feb '04

I think I found two things missed from the specification. The first is whether engine and/or controller is allowed to use not one, but several spaces (tabs) to separate syntatical entities in commands/ responses. I would say yes, if only because GNU Go parses them fine (mainly with sscanf()). Another, stronger reason is the same why tabs are allowed at all: it might be handy in GTP scripts. Also, I think there should be some lines about how to handle erroneous responses on the controller side. I'd propose that specification recommends controllers to _not_ try to parse responses that fail to confirm specification. Stricter protocols are way easier to implement properly and we all know what happened to HTML in which erroneous and custom not standardized tags are common. Paul

1 0

GTP on KGS: Ranked games available
by William M. Shubert 05 Feb '04

05 Feb '04

Just a note about the kgsGtp program that lets GTP-based go engines to connect to KGS. The new server was realeased today, it is now possible to play rated games on KGS. The GTP client is at http://www.igoweb.org/~wms/upload/ still. I will move it eventually, but for now that is the address to go to. The client includes a manual on using kgsGtp; the manual also includes information on how rated games work. You need to get a special account on KGS to play rated games via GTP, just email me if you want to do this and I'll be happy to set the account up for you. -- William M. Shubert <wms(a)igoweb.org>

1 0

← Newer
1
2
3
4
5
6
7
...
17
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

gtp