First, I use for Lc0 in json filembabigian wrote: ↑Wed Jun 24, 2020 8:25 pmHow many time forfeits did you get running that timecontrol? I tried reproducing your results with similar conditions and I got a ridiculous number of time forfeits. More than 10%. I ran 5s+0.08 as I have a faster GPU and wanted to be close to your nodes/move. Perhaps that's just too fast for reliable results.Here is the result for 6s+0.1s
Did you adjust any of the time settings in LC0?
I was terribly disappointed with cutechess as I see no suspend and resume capability like Arena. Running a test that finishes overnight is doable, but tests that take days are not. I'm not giving up my machine for a week to run silly engine matches. I need a match player that can be killed and restarted where it left off. Is there something I'm missing with not-so-cutechess?
"name" : "MoveOverheadMs",
"value" : 0
Second, I set in Cutechess-Cli a ridiculous "timemargin=5000" in every match at every time control. So, Lc0 might overstep its time limit, but it never happens in these fast games by more than some dozen milliseconds. All in all, I have no time losses (not at all if something else is not wrong) and I think the result is reliable, engines usually don't cheat and between two Lc0's, both might cheat just a bit but equally. Windows 10 used with its 1ms clock tick.