Laskos wrote: ↑Sun May 17, 2020 10:43 pm
Ok, I see now. Chimera accepts only regular books or PGNs as openings, not EPD files and not "fake" PGNs as 2moves_v1.pgn of SF framework. I was always using either 2moves_v1.pgn or EPD files, and for the first time a regular CTG book in Fritz 17. Adding EPD support would be helpful.
The opening book/suite (PGN or EPD) is totally handled by the GUI you are using. Chimera is only invoked by the GUI when the book has no more moves or at the end of the opening line from PGN opening suite or from EPD (i'm not very familiar with EPD)
Chimera receives
position command from the GUI which tells it about the current board setup, following the position command is usually a
go command to let the engine start the thinking.
If your PGN opening suite/EPD contains FEN strings that does not have the
actual current move number then that explains why Chimera is not switching at move
36 when it should!
Just to elaborate, consider the following FEN strings:
- 4r1k1/5pp1/P2P4/1p2p2p/7N/5r1P/5n1K/1R1R4 b - - 0 34
- 4r1k1/5pp1/P2P4/1p2p2p/7N/5r1P/5n1K/1R1R4 b - - 0 1
Both FEN strings represent the exact same board setup but the first one states that the current move number is
34 while the second one states that the current move number is
1
Both FEN strings are valid and acceptable by GUI's and engines. But the second FEN string is going to mislead Chimera becasue it does not tell it what is the real move number and therefore Chimera will not switch to the next engine when you expect it to.
Again, I'm not familiar with EPD because it is not part of the official UCI protocol, but if EPD consists of FEN strings or something similar to it then it is possible that the move numbers there are
not accurate which is causing Chimera to fail to switch when it should