Re: [Bug-gnubg] Problems using Stop rollout when one move appears to be best option

[Michael Petch]

On 23/08/09 3:23 PM, "Michael Petch" <address@hidden> wrote:

> My progress bar has never ended early Even with 16 threads).

The answer to this is because I never used the "Stop when one move appears
to be best" I the past. Sorry about that, explains why I never saw  rollouts
that ended early. Now that I have been using the option in testing, I have
seen it :). I guess that options says is "IF all rolls fall >
#ofJSDsfromBestMoveLimit", then stop rollout.

I assume what you are suggesting is that the rollout stops but there is a
move ranked higher than best that still has a JSD less than the limit you
set (3.1) when it stopped. Correct? (I haven't seen this behavior - yet).
Although I have found an issue that makes a Multithreaded build using 1
thread differs from a non multithreaded build with regards to JSD. I'll post
about that separately.