Author: Jan K.
Date: 17:50:14 07/22/04
Hi, i have seen in fruit and in other engines too that there is no test if (remainingDepth-rFactor-1)>(=)0 before doing null move, only remainingDepth>=someConstant, which means making many cutoffs based only on the values given by qsearch. That gived a very nice speed up when I tried it, but I soon found that my engine makes mistakes in some positions like this one, where it shows a draw after <almost every move> <e6e2> <d3c4> <f7g6> <c4d3>, altough only <d3c4> doesn't lose(normally seen at depth 5): [D]8/5kpp/4rp2/2p5/PP1p4/3Q2PP/2P2q2/R1B4K w - - 3 30 it didn't help when I used verification search, checks in qsearch.... But Fruit doesn't seem to have a problem so do I have a bug or just miss something? :))
This page took 0.01 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.