Author: Jeroen van Dorp
Date: 14:52:19 07/26/01
Go up one level in this thread
It's about the time-trouble.... Forgive my ignorance, but with the same reasoning a program with the "ponder is always on-code" could decide to cut off calculations earlier because it thinks it has some calcluations done already -or will do - which in fact isn't the truth. In that case not *time trouble* but bigger chance of flawed analysis (because it allots itself too little time to think) would be the problem. IOW: a chess engine wouldn't use extra time with ponder=off because it also counts the non-existing pondering time during opponent's moves,so *no* (extra) chance of time trouble. But it *would* run into calculation problems because the time allocation for proper calculation is wrong. Where am I going wrong? J.
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.