Re: [gnugo-devel] GnuGo violates time_settings?

[Gunnar Farnebäck]

On 06/21/2012 04:40 PM, TS wrote:
> it seems the problem is in fact that gnugo just ignores
>
> 1) the "time_settings" command completely, using completely arbitrary
> (eg 20s more than allowed) amounts of time

If you want to control its initial speed you need to set the initial
level to a matching value. --min-level and --max-level may also be of
use.

> 2) the "clear_board" command: If you resign a game while gnugo is still
> thinking of its move, it WILL return the move much later, possibly
> thereby messing up another game that has just started!

GNU Go processes the GTP commands sequentially as the protocol
requires. If you send a clear_board command while it's processing a
genmove it will return the move when it's finished thinking, then
clear the board. If you want to interrupt it you need to kill the
process and start a new. If you get confused about the returned move
you should consider using the id option in GTP to tag each command
with a number, then it's easy to know which response you're no longer
interested in.

/Gunnar