Author: Robert Allgeuer
Date: 01:40:07 08/29/04
Go up one level in this thread
On August 27, 2004 at 18:30:10, Stuart Cracraft wrote: > >>Fruit v1.5nmalways: nullmove search is tried always (instead of in the fail-high case only) > >It seems this is the big result, and I don't understand it. > >In my program, nullmove search is always done except if there >is an immediate previous nullmove done the "move" before, and >are not endgame, not in check, and either verify null >move set (null verification search) or depth > 1. Those are my >conditions. > >There is no search prior to the null move to fail high to serve as >another condition of whether null move is done or not so I don't >understand your point. > >Maybe I am missing something in terms of my understanding or >don't have all the conditions necessary for null move to be >successful or have too many conditions? > >What do you think? > >Stuart > Hi, I am not the author of Fruit, I also have not looked at the source, but my understanding is that this does not mean the Fruit does nullmove "always" even when this UCI parameter is turned on. It will still not do nullmove in check etc.. "Nullmove always" is just the name of the UCI parameter that tells Fruit to turn off one additional Fruit specific condition for doing a nullmove, which is this fail high condition that tells Fruit to try nullmove only if it thinks that there is a good chance that the nullmove search will indeed fail high. Robert
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.