Author: Heiner Marxen
Date: 09:11:19 03/22/04
Go up one level in this thread
On March 21, 2004 at 10:56:29, Uri Blass wrote: >On March 21, 2004 at 10:03:16, Dan Andersson wrote: > >> See http://www.xs4all.nl/~aske/Papers/AAAI-final.ps.gz figure 5. The ETC part >>is marked with '**'. The main benefit is information reuse, not mate detection. >> And to use ETC efficiently you should refactor your code a bit. >> >>MvH Dan Andersson > >In this case what Fruit does is not logical because fruit care to make all >possible moves and unmake them when you only needs to calculate the hash key for >all the possible moves that should be cheaper than making and unmaking the >moves. I have not yet looked at fruit source, but from my own recollection how to do ETC... in Chest I restrict the usage of ETC to non-trivial depths. If the expected work without ETC probing is too small, the overhead of ETC is does not pay off. May be fruit does restrict it in such a way, that even the additional overhead of move make/undo is small compared to the potential savings. But then, may be I'm just wrong. Cheers, Heiner
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.