We subtract a default 1 second ("Time Buffer" UCI option) to the available time before we calculate the maximum time when the engine should return a move, so it shouldn't lose on time. My testing with 10s + 100ms TC doesn't have any time losses but it is not ponder on games and it uses cutechess, so it's probably a UCI implementation issue when using the Shredder interface, like not replying to isready or returning an empty bestmove. I'll investigate further.IWB wrote:Hello Edsel,Edsel Apostol wrote:Hi Ingo, we have fixed the issue with ponder games on the Shredder UI. We'll be looking forward to see it in your list.IWB wrote:Hello Edsel,
I started a test already. If it gets into the TOP 16 it will throw out the old horse Naum
I remember Hanibal 1.5 having some ponder issues which causes a lot of time losses. The first 20 games of 1.7 are fine ... I am crossing fingers!
Thanks for the version
It is not completly gone. In 2014 games I have 7 losses on time. That is nothing to worry about but it is still there.
Do you allways keep some time on the clock left or do you play in the last fraction of the last second?
Besides that, the performance until now is briliant!
In the meantime, hopefully it retains the good performance until the end of the matches!