Author: Robert Hyatt
Date: 14:04:11 11/09/97
Go up one level in this thread
On November 09, 1997 at 16:12:57, Komputer Korner wrote: >I admit that this request is overkill but I have a better idea. Why >can't you provide as an option the estimated time expected that a >program will think on a move. There have been many times on long time >controls where to plan my activities to do something else it would be >nice to know how long the program plans to spend thinking. Crafty has *always* done this. Right before the "depth time ... " heading, you see a "target time: " line. This is the anticipated search time for this move, assuming the bottom doesn't fall out right at the end. I do this because in a tournament game, it is nice to know whether I have time for a quick trip to the restroom or water fountain, before Crafty will move. I did this in Cray Blitz for the same reason. Of course, if it fails low at the last minute, it will take longer, and it is not easy to predict how long it will take, since it may find a "saving" move quickly, or it might complete the current iteration without doing so. But for normal moves, the "target" is within 1 second of how long it will take...
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.