[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnubg] Problem with new always accept 0 move filter.
From: |
Joern Thyssen |
Subject: |
Re: [Bug-gnubg] Problem with new always accept 0 move filter. |
Date: |
Fri, 10 Jan 2003 16:52:44 +0000 |
User-agent: |
Mutt/1.4i |
On Fri, Jan 10, 2003 at 11:34:25AM -0500, address@hidden wrote
> Hi
> Nice to see the always accept 0 moves in the new build but...
> I have set the evaluation (hint) to 2 plies.
> Move filters:
> 2 ply Tab:
>
> 0 ply filter: Always accept 0 add 13 within 0.308
> 1 ply filter: Always accept 0 add 7 within 0.154
>
> Now for example opening 31 should only be evaluated up to 1 ply
> but in the hint window GNU still evaluates the move up to 2 ply.
> (the whole point of always accept 0 was to avoid this and save cpu time!)
I'm not sure....
If the user asked for a 2-ply evaluation I think he deserves to get one.
However, when gnubg makes his moves during a match, your suggestion
makes sense, since gnubg just have to select the best move, not show
detailed analysis for all moves.
As I understand it, this is exactly why Joseph doesn't like the move
filters for analysis (or "hint"). For analysis (and possibly also
"hint") I would expect to see at least two moves evaluated on the
highest ply so I can see the difference between the best move and the
second best move, and you really can't compare a 2-ply evaluation of 8/5
6/5 with a 1-ply ditto of 13/10 24/23.
Jørn