Author: Bruce Moreland
Date: 22:58:22 08/12/01
Go up one level in this thread
On August 13, 2001 at 01:53:46, Peter McKenzie wrote: >Not quite. When it is the engine's turn to move, chessbase sends a 'new'. Then >it puts the engine into force mode and pumps it the moves from the game so far. >Then it tells the engine to move. > >There are a couple of problems with this approach: > >- some engines clear their main hash table when getting the 'new' command, >because the real winboard only sends this at the start of a game. Clearing a >big hash table EVERY MOVE in a game will slow you down significantly. > >- playing through the entire game at each move is a minor performance hit. If >implemented ok it is a trivial penalty, but some engines might have a slight >delay in their routine that makes a game move. > >An engine could check its book for example, or just have some goofy timing issue >because its thread synchronisation isn't that flash. If makemove takes 0.05 >seconds, you will die in a game of 1 0 if you have to trundle thru. the movelist >every move. But such a delay would not be noticable under the real winboard. My program's time allocation would not work well under that system. It would think every move is the first move out of book, so it would think longer than usual. bruce
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.