Computer Chess Club Archives

Search

Messages

Subject: Re: Nullmove: when to avoid it?

Author: Severi Salminen

Date: 09:58:47 03/01/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.

>But diep is hell slower!
>
>Are you sure that this futile prevention is working at big depths?
>It never worked for me at big depths!

Well, I never reach big depths with my slow Celeron300. I also have not tested
it in large scale but it seemed to reduce nodes a little (maybe 0-5%). Maybe
I'll test it some more and report the results - it still seems to be a good way
to disable null moves.

Severi

• Re: Nullmove: when to avoid it? Miguel A. Ballicora 14:24:53 03/01/01
  • Nullmove: when to avoid it? Why not when depth=1? Severi Salminen 10:56:21 03/02/01
    • 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.