Re: [gnugo-devel] 2 questions

[bump]

> 1/
> gnugo -l g1.sgf -L 152 -a -w -t  > g1.txt
> creates the g1.txt output file but does not put anything inside .
> is there an other way to do this ?

Traces are written to stderr not stdout, so the correct syntax is:

gnugo -l g1.sgf -L 152 -a -w -t  2> g1.txt

> 2/ the break_in(off) evaluators are available if GNUGo has been invoked at
> level 10 or more .
> In that case ,does the GPT command -level 9 switch them off ?

In GNU Go 3.4 the breakin code is switched off at level 9 and
in fact this is the only difference between levels 9 and 10.
The rationale behind this was due to the slowness of the
breakin code. This policy might change before GNU Go 3.6.

Dan