Computer Chess Club Archives

Search

Messages

Subject: TranspositionTables and NULL-move

Author: Renze Steenhuisen

Date: 01:49:48 03/10/04

Hi anyone!

Today I tested the effects the saving of NULL-move search results has on the
size of the search-tree. The conclusion was unexpected!

I compared saving LOWER, EXACT, and UPPER bound values only in the PVS part of
the code, with additionally saving the LOWER bound value from the NULL-move
cut-off.

To my surprise, the additional information had a negative impact on the size of
the search-tree! And I do not understand why or how this is possible.

Can it be because my evaluation() is not really good yet?
Is it a real error somewhere?

Some comments/thoughts/experience is very much appreciated!

Renze

• Re: TranspositionTables and NULL-move Vincent Diepeveen 06:45:43 03/11/04
• Re: TranspositionTables and NULL-move Uri Blass 02:31:25 03/10/04
  • Re: TranspositionTables and NULL-move Renze Steenhuisen 02:45:47 03/10/04
    • Re: TranspositionTables and NULL-move Vincent Diepeveen 06:54:40 03/11/04
    • Re: TranspositionTables and NULL-move Uri Blass 03:24:22 03/10/04
      • Re: TranspositionTables and NULL-move Vincent Diepeveen 07:06:32 03/11/04
    • Re: TranspositionTables and NULL-move Michel Langeveld 02:56:46 03/10/04
      • Re: TranspositionTables and NULL-move Vincent Diepeveen 06:47:52 03/11/04
      • Re: TranspositionTables and NULL-move Renze Steenhuisen 03:09:55 03/10/04
        • Re: TranspositionTables and NULL-move Michel Langeveld 03:21:35 03/10/04
      • Re: TranspositionTables and NULL-move Renze Steenhuisen 03:06:35 03/10/04
        • Re: TranspositionTables and NULL-move Michel Langeveld 03:27:53 03/10/04

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.