bug-gnubg
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] Re: Naw..panic or teach me what I am doing wrong !!


From: Gary Wong
Subject: Re: [Bug-gnubg] Re: Naw..panic or teach me what I am doing wrong !!
Date: Thu, 9 Jan 2003 17:10:29 -0500
User-agent: Mutt/1.3.28i

On Wed, Jan 08, 2003 at 09:45:49PM +0100, Jim Segrave wrote:
> On Wed 08 Jan 2003 (18:32 +1300), Joseph Heled wrote:
> > Can gnubg log the rollouts? I would like to analyze them with fibs2html 
> > to see where the differences are?
> 
> I was thinking the same thing. It's easy to syslog the dice rolls, the
> game number, player on move, cube action (although it's not important
> here). The hard part is that all rollouts seem to use
> BasicCubefulRollout() and that doesn't actually provide the chosen
> move. 
> 
> I can change the call to FindBestMove() in this routine to return the
> best move for non 0ply rollouts. Fixing it for 0 ply is a bit messy.
> 
> These patches may be a bit ugly and will assume the presence of
> syslog() and openlog(), so it may not be usable under Windows.

I really like the idea of being able to log the rollouts, but I'm a
bit doubtful about the use of syslog() to do it.  It's not particularly
portable; on a multiuser system, there's a good chance the user won't
have even have permission to read it; and it introduces yet another
file format, which makes it tedious to write other programs to process
the logged output.

How about we add some sort of command like "set rollout log <file>", and
then write the results of the rollout to the specified file (if there is
one) in SGF format as we go?  SGF can already handle most of the important
data, and if we want to log other information that comes up we could either
dump it to a C[] property or invent another random property to hold it.

Cheers,
Gary.
-- 
   Gary Wong           address@hidden           http://www.cs.arizona.edu/~gary/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]