Moderator: Andres Valverde
cnchang wrote:However, it seems impossible to call a timeout at will in the middle of a game in WinBoard without messing up timers and/or chess engines flow.
But, if a tourney can be resumed after killing WinBoard and then restarting it, is it possible to erase the aborted game from the tourney schedule/record somehow so that particular match in the tourney can be replayed?
Regarding if chess engines will take STOP command from the chess board, my test on BHWS chess board's(2012 test version) tourney management menu's PAUSE TOURNEY switch will stop both the board timers and chess engines all at once. No pondering; actually no nothing is taking up any CPU resources from task manager. The same engines are used.
H.G.Muller wrote:Pausing an engine-engine game is tricky, because one of the engines will always be thinking. I suppose the best approach would be to pause the game only after the thinking engine produces its move; interrupting a thinking engine (if the engine would allow this at all; many WB engines do not) is likely to disadvantage the interrupted engine if you start it thinking again on resuming the game, but probably does advantage it when you give it back the time that it has been thinking so far (because it did use the time to fill its hash table).
...
It would be nice if WinBoard had the general capability to continue aborted games. Perhaps I should store the clock settings in the result message (which now only says 'XBoard exit'), so that on reloading the game the clocks could be put back in the state they were in when the game was aborted, so it could be continued from there. That would not solve the problem of the aborted game appearing in the PGN file, though.
...
Well, both UCI and UCCI protocols have a 'stop' command to stop the engine immediately, and it is an essential part of the protocol. (You could not implement pondering without it). In WB protocol there is a move-now command ('?'), but not any engines implement it, as it is not needed in normal game play. BHWS really does not wait until the thinking engine produces its move? I don't know very well how the BHWS GUI works, because it is all in Chinese... I suppose one could just send 'stop' commands to the thinking and pondering engine, and add the clock time the thinking engine has been using so far on the current move back to the clock. Or does it just leave the time as it is?
WB protocol specs wrote:pause
resume
(These commands are new in protocol version 2 and will not be sent unless feature pause=1 is set. At this writing, xboard actually does not use the commands at all, but it or other interfaces may use them in the future.) The "pause" command puts the engine into a special state where it does not think, ponder, or otherwise consume significant CPU time. The current thinking or pondering (if any) is suspended and both player's clocks are stopped. The only command that the interface may send to the engine while it is in the paused state is "resume". The paused thinking or pondering (if any) resumes from exactly where it left off, and the clock of the player on move resumes running from where it stopped.
Return to Winboard and related Topics
Users browsing this forum: No registered users and 20 guests