You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Saruman never produces a bestmove unless the go command is followed by wtime. However, it appears to ignore the values of wtime, btime and movestogo and whatever time control -- 40/4 or 40/40 -- almost never spends more than a fraction of a second on a move.
An example game, TC=40 moves in 20 minutes repeating (local equivalent of CCRL's 40/40):
This bug must cost Saruman several hundred Elo points.
The exec used is HK's 2017-08-10 build linked via CCW. Tested under Cute Chess GUI (latest dev build) and Arena 3.5.1.
Tirsa@CCRL
The text was updated successfully, but these errors were encountered:
Thanks for filing this, we developed this engine when we were in our first year of university as a side project and didn't really know what we were doing. It's likely got a lot of issues because of this.
I will look into fixing this as it seems like it's just an issue with our UCI implementation.
This is related to #22 but is more general.
Saruman never produces a bestmove unless the go command is followed by wtime. However, it appears to ignore the values of wtime, btime and movestogo and whatever time control -- 40/4 or 40/40 -- almost never spends more than a fraction of a second on a move.
An example game, TC=40 moves in 20 minutes repeating (local equivalent of CCRL's 40/40):
This bug must cost Saruman several hundred Elo points.
The exec used is HK's 2017-08-10 build linked via CCW. Tested under Cute Chess GUI (latest dev build) and Arena 3.5.1.
Tirsa@CCRL
The text was updated successfully, but these errors were encountered: