Re: [gnugo-devel] how to trace:

[Evan Berggren Daniel]

The usual process is not to trace for the whole move.  Usually, you only
need the reading traces for owl or semeai or tactics cases, and only care
about a specific piece of the reading.  For example, if in the testcase
you are trying to solve you determine that gnugo doesn't see an attack on
a group, then you care only about the trace for owl_attack on that group.
To get this, go into gtp mode, load the game, and start the trace.  Then,
instead of executing a genmove command, just run owl_attack on that group.
This will only give you the owl reading, which is what you want.
Similarly for tactics or semeai.

Hope this helps

Evan Daniel

On Sat, 17 May 2003, kevin yong wrote:

> Hi:
>
>   in regression test, ussually we test a specific move
> in each test. we want to know the thinking process of
> gnugo for that specific move.
>
>   when we use sgftrace, we got reading process for all
> moves, which is 10mg++ size file, and it is little
> hard to pin down to the specific move we want to know.
>
>   i personally tried to insert something into the
> source code to print out the reading process for the
> specific move, but i realize that it has big problem
> considering we need to update to new version in just
> few weeks time.
>
>   so, i just think a 'ideal' trace would be: when we
> specify which move we want to know in a regression
> test, gnugo only print out the reading process for
> that move. i have not figure out how to implement it.
>
>   best regards.
>
> kevin.
>
>
>
> ______________________________________________________________________
> Post your free ad now! http://personals.yahoo.ca
>
>
> _______________________________________________
> gnugo-devel mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/gnugo-devel
>