Author: Uri Blass
Date: 02:56:35 10/31/01
Go up one level in this thread
On October 31, 2001 at 04:27:42, Jeremiah Penery wrote: >On October 31, 2001 at 01:47:08, Uri Blass wrote: > >>On October 30, 2001 at 20:36:49, Dann Corbit wrote: >> >>>Why take a risk when you don't have to? >> >>not using null move pruning is taking a risk. >> >>null move pruning does not mean playing unsound moves when the time to calculate >>is not important because it is possible to use zunzwang detection. >> >>Some programs like yace already do it. > >Zugzwang is not the only danger in using null-move. Null-move also works to >hide lines that contain material sacrifices. Against Kasparov, that could be >really dangerous. I believe that null move usually helps to find sacrifices at long time control and it hide sacrifices mainly at blitz. Here is a simple test: take the nolot test suite and try the same program with null move pruning and without null move pruning and compare times. I believe that null move pruning is going to be faster. I believe that Deep blue could solve the nolot test suite faster with null move pruning. Deep blue and even deep thought was very good in solving the nolot test suite thanks to singular extensions but I believe that it could be even faster with null move pruning. We cannot test deeper blue but we can test other programs and it will be interesting if there is a single program that can solve this test faster without null move pruning. 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.