Author: Tony Werten
Date: 12:44:53 04/07/04
Go up one level in this thread
On April 07, 2004 at 10:59:49, Renze Steenhuisen wrote: > >>>I only store result from the main search, so no NULL-move and no Qsearch >>>results. >>>I get a TT-hit ratio of 11.73%, of which a part will generate cut-offs. >>> (I call something a tt-hit when an entry is found with the same hashkey, >>> draft does not need to be sufficient) >> >>Hmm, I'm sorry but that's way too low. You probably have a problem with your >>hashkey. >> >>In XiniX I get a hitrate of at least 60% in normal search, >20% in qsearch. >> >>Tony > >Hi Tony, > >And you're storing just the same information? Any suggestions what part of the >hashkey could be wrong? I am getting desperate here :-( Lets see, what have I done wrong the last couple of years. Not adding ep hash Not removing ep hash after nullmove Not correctly adjusting after promotion Not correctly checking if the move is legal Trying to make a nullmove Taking the move from the wrong entry I think that basicly was it. Best is to make a function that builds your hash from scratch and let it run along ( and compare ) for at least 1 year. After the first year you're allowed to switch it off every now and then. But remember to switch it on after every "optimization" Tony
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.