Re: [gnugo-devel] twogtp.py matches broken

[Evan Berggren Daniel]

On Tue, 29 Apr 2003, Arend Bayer wrote:

>
> Currently, running matches with twogtp.py is broken, because the random
> seed is always set to 0 starting from the 2nd game. This is due to
> the final_score command:

twogtp-a does not exhibit this problem, because it starts a new gnugo
process for every game.  This seems like a good idea to me, to avoid any
other such bugs.  twogtp has the same problem as twogtp.py.

Evan Daniel