bug-gnubg
[Top][All Lists]
Advanced

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

Re: [Bug-gnubg] Problem using command files for rollouts.


From: Nis
Subject: Re: [Bug-gnubg] Problem using command files for rollouts.
Date: Wed, 26 Feb 2003 08:52:30 +0100

--On Wednesday, February 26, 2003 00:24 +0100 Jim Segrave <address@hidden> wrote:

I don't know if this is in the wishlist already: "Rollout until
certain".  This should probably be combined with a minimum and maximum
number of  trials.

Would this be for a single rollout - where you'd say something like
minimum 100, max 2592, stop if STD < 0.01 * abs(equity)?

I would think this would be most useful when rolling out a set of
moves to decide which is the best move. In this case, some real
surgery is required, as you'd then want to stop when say x * JSD <
abs(equity of best play - equity of 2nd best play).

I consider both of these useful. As you write yourself, the second option is the most obviously cool one. What is JSD, by the way?

I have a feeling that this is what people would most often want. But
that means being able to stop and restart rollouts, so you'd do
something involving doing a block of rollouts of each candidate play,
eliminate any whose equity difference from the best so far is more
than x JSDs from the best play. Then do another block of rollouts of
the remaining candidates, continuing until either you've reached the
limit of rollouts or ou've eliminated all but one play. This requires
the ability to resume rollouts (which I'm working towards) and a
better view of what moves to roll out.

There is one small complication: What if the top candidate drops in equity when the rollout is extended, causing a previously dropped move to be within range? Should we then resume the rollout of this move also?

At the moment, you can use the
hint or analysis window to get a list of moves, then select a block of
those (I don't think you can select non-adjacent ones for a single
rollout).

Ctrl-click to select/deselect individual moves works in the Windows version.

After that the current code is very simple minded - roll
each selected move out to the limit.

Yes - and option 1 above would not be very hard to implement either - it "just" needs a new break-condition after each trial.

--
Nis Jorgensen
Greenpeace
Amsterdam




reply via email to

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