Computer Chess Club Archives

Search

Messages

Subject: Nullmove: when to avoid it? Why not when depth=1?

Author: Severi Salminen

Date: 10:56:21 03/02/01

Go up one level in this thread

>>>I can save bunches of nodes by not nullmoving on the last ply before
>>>qsearch. So if depthleft == 1 ply then not nullmoving reduces
>>>for me the number of nodes considerably.
>>
>>Interesting idea, I'll give it a try in my engine.
>
>Try it severi!
>I have observed the same thing. I don't do nullmove
>unless depth > 1. I think it makes sense.

Why does it make sense? I have not yet tried it but I don't understand why
should it be better? Do you have any opinions? I allways want to understand the
features I put into my engine and I don't get this one...

Severi

• Re: Nullmove: when to avoid it? Why not when depth=1? Ernst A. Heinz 13:01:21 03/02/01
  • Re: Nullmove: when to avoid it? Why not when depth=1? Robert Hyatt 19:06:14 03/02/01
    • Re: Nullmove: when to avoid it? Why not when depth=1? Ernst A. Heinz 20:07:49 03/02/01
      • Re: Nullmove: when to avoid it? Why not when depth=1? Peter McKenzie 19:34:53 03/03/01
      • Re: Nullmove: when to avoid it? Why not when depth=1? Robert Hyatt 07:34:23 03/03/01
  • Re: Nullmove: when to avoid it? Why not when depth=1? Severi Salminen 13:35:43 03/02/01
    • Re: Nullmove: when to avoid it? Why not when depth=1? Ernst A. Heinz 16:23:41 03/02/01

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.