[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnubg] Analysis/Evaluation Settings
From: |
Joern Thyssen |
Subject: |
Re: [Bug-gnubg] Analysis/Evaluation Settings |
Date: |
Wed, 22 Jan 2003 19:16:06 +0000 |
User-agent: |
Mutt/1.4i |
On Tue, Jan 21, 2003 at 06:26:53PM +0100, Holger wrote
> At 12:21 21.01.2003 +0000, you wrote:
> >On Mon, Jan 20, 2003 at 07:10:45PM +0100, Holger wrote
> >> And in order to understand how this speed option works: Could you relate on
> >> this, especially in conjunction with move filters? Are the settings for the
> >> move filters then halved for the next ply, or so?
> >
> >The speed option has nothing to do with move filters.
> >
> >Speed option:
> >
> >A n-ply evaluation is an average over 21 n-1 ply evaluations.
> >A reduced evaluation averages over a reduced set of dice, e.g., a 33%
> >speed evaluation averages over 7 n-1 ply evaluations.
Hmm, maybe I was a bit quick here. The code actually does something
different:
A n ply evaluation is an average over 21 n-1 ply evaluations. These are
again averages over n-2 ply evaluations etc. When n-m=1 then gnubg will
average over a reduced set of dice.
Hmm, wonder which algorithm is correct/best???
> Thanks for the explanation.
>
> How are the dice combinations determined? Is there (can there be?) any try
> to reduce the error introduced by this by selecting appropriate dice
> combinations?
gnubg will loop through different reduced sets of dice. The 50% speed
option has two different sets, the 33% speed option three etc.
AFAIK the sets are chosen such that "good" rolls are divided bewteen the
different sets. For example, the double rolls.
Jørn