Le Lundi 15 Mai 2006 10:11, hena a écrit :
{...]
>
> i don't feel too comfortable to patch gnugo yet myself so im just including
> these. Also any pointers how to start debugging these are appresiated.
>
Hi Hena
i recently began to put my hands in GNU Go, and can share some clues :
- simplest and fun: run with -t option (trace explains everything)
gnugo -t -l gnugo-seki-error.sgf -L45
- nice graphic display: -T (show color boards)
gnugo -T -l gnugo-seki-error.sgf -L45
- The best interactive tool is the wonderful Gogui. It gives access to many
things (show analyse, show shell) inside the engine through GTP commands.
- Read the fabulous documentation :) and use debug options
(gnugo --help / --help debug / --debug-flags)
- Read the patches in trac.gnugo.org, to see how things works and slowly
understand the engine.
- try something, see how it works/breaks.
Alain
_______________________________________________
gnugo-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnugo-devel
