bug-gnubg
[Top][All Lists]
Advanced

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

RE: [Bug-gnubg] BUG: Rollout statistics wrong - Another Secondary Point


From: Ned Cross
Subject: RE: [Bug-gnubg] BUG: Rollout statistics wrong - Another Secondary Point
Date: Thu, 11 Mar 2004 13:03:36 -0800

-----Original Message-----
From: address@hidden
[mailto:address@hidden Behalf Of Jim
Segrave
Sent: Monday, March 08, 2004 4:30 AM
To: Ian Shaw
Cc: GnuBg Bug (E-mail)
Subject: Re: [Bug-gnubg] BUG: Rollout statistics wrong

> Secondary issue:
>
> When resuming a rollout, the window shows 0 trials until the first new
trial is complete. It would be nice to immediately show the start position.
It doesn't matter much on 0-ply, but it is unnerving on 2-ply, where it
looks for a while as if all your previous hard work has been lost and gnubg
is starting again.

Good point.

--
Jim Segrave           address@hidden

When stopping, then resuming a rollout of several candidate checker plays,
how can one be sure all the candidates see he same number of trials?

Scenario:  I am running a long 2-ply rollout, 1296 trials, for 4 candidate
checker plays.  I need to stop the rollout for whatever reason after only
349 trials.  When I hit stop, It's not clear how many of the 4 candidates
have actually completed the 349th trial.  When I resume the rollout (by
selecting the candidate checker plays and hitting "rollout" from the
annotation window), GNUBG opens the rollout window, and after a pause, tells
me that we are now on trial 350, starting at the first candidate.

It seems possible that GNUBG is truncating the trial when "stop" is hit,
then resuming at the next trial, forgetting about the unfinished business in
the previous trial.  If so, the rollout results could be skewed.


Also the estimated time remaining is off when resuming a rollout, since GNU
thinks it has completed 350 trials (the example scenario) in several
seconds.  This is of course very minor and does not affect the integrity of
the result.







reply via email to

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