Seer 2.0.0

[Damir]

Hi Connor,

I don't know why but Seer stopped responding on my hardware.

My hardware is 64 cores AMD 3990X Threadripper

Here is a picture where the engine stopped pondering, ( the analysis field is empty) and is about to lose on time.

https://ibb.co/rtSRwpb

Here is the 2nd picture where the engine lost on time:

https://ibb.co/K2GTDJ8

[Damir]

I was playing the games on Fritz 18 GUI online against other opponents.

Also in offline analysis in Fritz 18 GUI the engine does not move and ponder....

[Damir]

I was using the latest bug fix update released today. The issue is still the same. Engine does not move and also does not ponder..

[connor_mcmonigle]

Can you share UCI logs? Or at least maybe your UCI option configuration?

Unfortunately, I can't debug things further as is. I recently played several games with high thread count + ponder enabled via Lichess without any issues: https://lichess.org/A22EFDDu.

[connor_mcmonigle]

Can you share UCI logs? Or at least maybe your UCI option configuration?

Unfortunately, I can't debug things further as is. I recently played several games with high thread count + ponder enabled via Lichess without any issues: https://lichess.org/A22EFDDu.

In the absence of logs, some other information would also be helpful such as: does it work with fewer threads? Does it work if you disable ponder? Is there any configuration where it works? Also, I'm confused as to whether it was ever responsive based on those screenshots. Were those just book moves at the start or did Seer transition from responsive to unresponsive during the game? Thanks

[Damir]

Also with fewer Threads the engine becomes unresponsive. The 12 moves that engine played was from book. After the engine was out from book it never moved and gradually lost on time.

Here is my UCI Engine Options:

https://ibb.co/x5nWcDN

[RubiChess]

A GUI that you pay money for and no UCI log available? Really??

[Damir]

I will post the UCI log tomorrow. Right now my PC is unavailable.

[Damir]

Here is UCI log of Seer 2.70:

https://ibb.co/c3QjFQG

[RubiChess]

Here is UCI log of Seer 2.70:

https://ibb.co/c3QjFQG

You obviously didn't understand. Your output just shows what the engine answers to the 'uci' command (ignoring the obsolete parameter 'log').

What I meant is that the GUI should offer an option to write the communication via UCI protocol between the GUI and the engine(s) to a log file so that you can send this log file (after reproduction of the problem) to Connor who may see at what part of communication the problem occures.

All free GUIs that I know have this kind of logging option so it would be very disappointing if commercial GUI doesn't have.

Regards, Andreas