Author: Thomas Mayer
Date: 05:11:05 05/25/05
Go up one level in this thread
Hi Dieter, >> By the way: The reason why I send an "ucinewgame" before every position is >> simple: just to keep sure that the hash is cleared. Else solutions are not >> reproduceable at all. > It is of course no guarantee, that the engine will clear the hash tables. Well, I know that, but what else should I do ? I think in many engines this will clear the hash. By the way: When I want to use the clear hash function ? How is it done ? setoption Clear Hash value true or what ? I did not find anything about that in the specs... > I think, Yace never clears HTs under UCI, unless the user hits the "clear > hash" button. I don't see much of a disadvantage for this, either. In test- > suites, it might yield in non reproducable node numbers - but really no > problem. If I really want to have reproducable node numbers, I will use some > engine specific test routines. Those who prefer to use a tool, like epd2wb, > would need to judge for themselves, how to approach the problem of possibly > not reproducable node numbers. well, yes, at least it is not THAT important... > It might be interesting to note, that CB UCI implementation more or less > assumes, that Clear Hash is a hardcoded option with a defined meaning, and > will send it for new games. But Clear Hash is not defined like this in the > UCI protocol, it is just given as an example. It might have been a good > idea, to have this hardcoded like few other options (preferably with a name > like "UCI_Clear_Hash"). I think CB assume that it does something similar to their reset command which they have introduced in their winboard adapter some years ago. Greets, Thomas
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.