Author: Lance Perkins
Date: 17:58:34 08/19/05
Go up one level in this thread
If you look at the Winboard code, you will see two functions - SendTimeRemaining and SendMoveToProgram, and you will see that they are invoked one right after the other. SendTimeRemaining sends to the engine both the time and otim commands in one string (but seperated by a line break). In your log, there is 0.25 sec delay between the two - for two commands that are in one string! The delay between the time and the move command should also be next to nothing. So, I conclude here that the problem is with the interval that you check for input. On August 19, 2005 at 19:06:59, Brian Richardson wrote: >From time to time, Tinker loses games on time, even though it is very rare, and >sometimes even with an increment. The text below is from Tinker's log file (not >the Winboard debug file). Notice the "long" (nearly one full second) time >between the time, otim and move messages. Earlier in this game, the time >between these messages was very short. Of course, Tinker was pondering during >this time, so the delay is likely due to Tinker not checking for input >frequently enough. However, just wondering if others have seen anything like >this. > >More importantly, when do you count your time as starting: with the actual >move, or the "time" message which comes earlier? > >Thanks > >13:14:10.671 Got2: time 200 >13:14:10.921 Got2: otim 500 >13:14:11.546 Got2: d7d6
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.