search

Matthies / RubiChess

Another chess engine
GNU General Public License v3.0
158 stars 17 forks source link

Time management query #314

Closed eskstrand10 closed 2 years ago

eskstrand10 commented 2 years ago

Rubichess is using maximum of 1/3rd of allowed time per move, see attached txt files rubi test 1-10: rubi 2.2 vs Xiphos 6.1 1 minute and 10 sec/per move rubi test 1-3: rubi 2.2 vs Xiphos 6.1 1 minute and 3 sec/per move

Settings for Rubi are 4 threads, 1024 Hash, opening book off, ponder off, NNUE on, large pages off, avx2 binary used Xiphos using same 4 threads, 1024 hash, ponder off Book is at max 3 moves deep Cutechess used

rubi test 1-10.txt rubi test 1-3.txt

Is the time management correct?

Matthies commented 2 years ago

I will take a deeper look later but what comes to my eyes immediately is this: TimeControl: 500/60+10 What is this 500? Could it be that you used a moves-based time control?

Can you configure cutechess to write a logfile where I can see the detailed UCI commands like go wtime 60000 winc 10000 etc.?

Later...

Matthies commented 2 years ago

Okay, I can reproduce. You are using the (quite exotic) timecontrol "time for n moves with additional increment". Rubi doesn't use the increment and tries to press all the 500 moves into one minute. Will fix...

Matthies commented 2 years ago

The bug should be fixed now in current master. If you don't want to wait for new Windows binary, you can workaround the bug by setting Moves to "Whole game" in the cutechess time control GUI which is probably what you want when you set it to 500 before. Anyway, thanks for reporting the bug.

eskstrand10 commented 2 years ago

Thanks for fixing, I will try and and use more normal settings as well