Author: Bas Hamstra
Date: 09:11:39 09/19/99
Hello friends, When you do nullmove everywhere, it causes a lot of qsearches. Without nullmove I have a good qnode/node rate, roughly around 5-10% or so. With nullmove that worsens quite a bit, I see rates over 100% frequently. Is that normal? I read about nullhashing, a few times. I don't hash the result of a nullmove search. To be more precise: when a position is cut by a nullmovesearch I don't put that position in the hashtable, and just return Beta. Should I? And has that got something to do with the bad qrates I'm seeing? Can someone give a few pointers for nullhashing? Just putting a position that is about to be cut by nullmove in the table, as a normal upperbound record, but without a move? With flag "NULLHASH"? Record only to be used by nullmove, so store with adjusted depth = depth-R ? That's how I would figure it, and I tried it quickly, but without much result... A second question: I don't store leaf-nodes at all, just see no point in that. I would like to check if that's normal. A simple yes is enough :) Regards, Bas Hamstra.
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.