hgm wrote:ChessGUI expects the engines to look at the full-move number of FENs to know when a new session starts?
That certainly breaks all of my engines!
I always assumed that all serious testing is done by feeding moves, and never by starting from positions. I often don't even bother to equip them with setboard.
Even with setboard it can work. In Jumbo (as in all my previous engines) I ignore the full move number given through setboard, and if I wouldn't ignore it then I would certainly not assume that some of the moves that belong to a time control session have already been played. So if I get a "level 40 X Y" then the number of remaining moves starts at 40 for me no matter what comes in setboard.
Therefore, considering that Graham tested Jumbo successfully under ChessGUI (see his post above), I'm not sure whether we already know all about this problem ...
I've had to use the wb2uci adapters with both Jumbo and Dorpsgek to overcome the issue.
hgm wrote:ChessGUI expects the engines to look at the full-move number of FENs to know when a new session starts?
That certainly breaks all of my engines!
I always assumed that all serious testing is done by feeding moves, and never by starting from positions. I often don't even bother to equip them with setboard.
Even with setboard it can work. In Jumbo (as in all my previous engines) I ignore the full move number given through setboard, and if I wouldn't ignore it then I would certainly not assume that some of the moves that belong to a time control session have already been played. So if I get a "level 40 X Y" then the number of remaining moves starts at 40 for me no matter what comes in setboard.
Therefore, considering that Graham tested Jumbo successfully under ChessGUI (see his post above), I'm not sure whether we already know all about this problem ...
I've had to use the wb2uci adapters with both Jumbo and Dorpsgek to overcome the issue.
Ok, that explains a lot. So without wb2uci Jumbo would suffer from the same problem under ChessGUI as several other WB engines.
hgm wrote:ChessGUI expects the engines to look at the full-move number of FENs to know when a new session starts?
That certainly breaks all of my engines!
I always assumed that all serious testing is done by feeding moves, and never by starting from positions. I often don't even bother to equip them with setboard.
Even with setboard it can work. In Jumbo (as in all my previous engines) I ignore the full move number given through setboard, and if I wouldn't ignore it then I would certainly not assume that some of the moves that belong to a time control session have already been played. So if I get a "level 40 X Y" then the number of remaining moves starts at 40 for me no matter what comes in setboard.
Therefore, considering that Graham tested Jumbo successfully under ChessGUI (see his post above), I'm not sure whether we already know all about this problem ...
I've had to use the wb2uci adapters with both Jumbo and Dorpsgek to overcome the issue.
Ok, that explains a lot. So without wb2uci Jumbo would suffer from the same problem under ChessGUI as several other WB engines.
Intel i5 Quad
ChessGUI
256mb hash each where possible
3-4-5 piece tablebases
Ponder off
GBSelect2016-2.cgb book
40 moves in 25 minutes repeating (adapted for the CCRL)
5 cycles 50 rounds
All engines 64-bit 1CPU where available
Intel i5 Quad
ChessGUI
256mb hash each where possible
3-4-5 piece tablebases
Ponder off
GBSelect2016-2.cgb book
40 moves in 25 minutes repeating (adapted for the CCRL)
5 cycles 50 rounds
All engines 64-bit 1CPU where available
Intel i5 Quad
ChessGUI
256mb hash each where possible
3-4-5 piece tablebases
Ponder off
GBSelect2016-2.cgb book
40 moves in 25 minutes repeating (adapted for the CCRL)
5 cycles 50 rounds
All engines 64-bit 1CPU where available