gtp August 2004

gtp@lists.lysator.liu.se

9 participants
4 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

2025

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 August 2004