bug-gnubg
[Top][All Lists]
Advanced

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

Re: [Bug-gnubg] Analysis/Evaluation Settings


From: Holger
Subject: Re: [Bug-gnubg] Analysis/Evaluation Settings
Date: Mon, 20 Jan 2003 19:10:45 +0100

At 17:33 20.01.2003 +0000, Joern Thyssen wrote:
>On Mon, Jan 20, 2003 at 05:49:35PM +0100, Holger wrote
>> Since the move filters have been introduced I'm trying to find reasonable
>> settings. Unfortunately, my computer isn't one of the fastest (P1-MMX 233).
>> Which method should give the better result in terms of a compromise between
>> speed and reliable results: Reducing the search space with the move filters
>> or (presumably also reducing the search space ?) by reducing the speed
>> setting?
>
>I think you have to experiment yourself.
>
>Try analysing the same match on a number of different settings and
>record the time spent analysing (do a cold-start of gnubg to flush the
>evaluation cache) as well a key parameters from the analysis.

OK.

I was hoping to avoid extensive trials as presumably one match doesn't do.
At least it should be a rather long one.
And then I'm no bg expert. I can say whether it takes too long for my
taste, but I can't assess GNUbg's match evaluation. So I can't really
decide when to stop reducing the search space. Maybe even static analysis
is enough. I don't know. However, from comments on this list I believe it's
safer with 2ply.

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?

>Michael Depreli and I have had some off-list discussion regarding move
>filters. We're in the process of setting up an experiment.

Please, keep us informed. I'd be interested in this discussion.

Regards,

        Holger




reply via email to

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