bug-gnubg
[Top][All Lists]
Advanced

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

Re: [Bug-gnubg] unwanted extension of rollouts


From: Jim Segrave
Subject: Re: [Bug-gnubg] unwanted extension of rollouts
Date: Mon, 4 Aug 2003 09:14:09 +0200
User-agent: Mutt/1.2.5.1i

On Mon 04 Aug 2003 (00:21 +0200), Robert-Jan Veldhuizen wrote:
> At 15:10 8/3/2003 +0200, you wrote:
> >On Sun 03 Aug 2003 (01:30 +0200), Robert-Jan Veldhuizen wrote:
> 
> It seems like GNUBG stores rollout parameters for each move/decision 
> individually. So GNUBG might check current rollout settings, compare to 
> stored rollout settings, and only resume an earlier rollout if the current 
> settings are the same as those of the older rollout, except for more 
> trials. Otherwise, GNUBG could start a new rollout from trial 1.

Yes, but there's only room to have one analysis, whether it's static
or a rollout for any given move. Changing that so you could compare
rollouts or so that it kept old results and did a different rollout
involves a major re-structuring of the way moves are stored.

> >  What do you do with rollout results in an .sgf file
> >when you open that file?
> 
> Identical to the above?
> 
> >I prefer the 'carry on where you left off', because it's so quick to
> >force the rollout to be forgotten by using 0 ply evaluation.
> 
> Well it's not a big deal, but I think it would be nice if GNUBG itself 
> detects whether an old rollout should be resumed, or a new one should 
> start. When the user changes settings, he obviously doesn't want the older 
> rollout with different settings to resume, but a new one to start?

My thinking was that the most common operation would be someone
rolling out some moves in a game, going back to look at the results
later and deciding that some moves need to be rolled out further (in
particular when the Python scripting gets more complete, this would be
a very sensible thing to do). But to resume a rollout, either gnubg
needs to remember what settings you were using (so it automagically
resumes what you were doing before) or you need to figure out what
settings you were using, which might mean exporting the position just
to see what the settings were, then go in and manually set the rollout
back to the way it was before. One tiny mistake and the results are lost
forever.

Maybe the best solution is a pop-up dialogue box that warns you that a
move you have selected for rolling out was rolled out with different
settings than the current ones with options to 

   Cancel/Start Over/Extend Using Original Settings

would address this best?


-- 
Jim Segrave           address@hidden





reply via email to

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