Computer Chess Club Archives


Search

Terms

Messages

Subject: Re: futility pruning?

Author: Uri Blass

Date: 06:26:23 11/09/03

Go up one level in this thread


On November 09, 2003 at 09:13:49, Jeremiah Penery wrote:

>On November 09, 2003 at 04:55:40, Matthias Gemuh wrote:
>
>>>Anyway my question is since you go directly to quiescent search
>>>(where stand pat cutoff of all futile moves occur) after making the move,
>>>we only saved ourselves "making of the futile moves".I can comprehend the
>>>extended futlity pruning but not this.For me as long as standing pat cut off
>>>is there , futility pruning at frontier is unnecessary,and if it is,it only
>>>saves the time to make and unmake futile moves.Where does the 60% tree shrinkage
>>>comes from?Please try to see where my proble is.
>>
>>Your logic seems sound for me. We seem to save only
>>MakeMove() + UnmakeMove() + Evaluate().
>
>The difference of pruning before or after making the move is probably very tiny,
>assuming you always prune the same nodes.

Dependent on the speed of your makemove and unmakemove.

My makemove is not fast because it update information about some tables
and also calculate part of the evaluation.

It is possible that I could do better by having different definition of
functions and having start_make_move and only if some conditions happen
continue_make_move but I am afraid that today changing things there without bugs
is not simple and I prefer to look for other improvements.

Uri



This page took 0 seconds to execute

Last modified: Thu, 15 Apr 21 08:11:13 -0700

Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.