Page 1 of 1
UCI go command precedence
Posted: Mon Feb 22, 2021 9:50 pm
by KLc
Suppose I send (for whatever stupid reason) the following UCI go commands (with white to move):
and
What’s the thinking time then? I checked and it seems the first time has precedence. However, this is not documented in the protocol and I’m not sure if I observed a general or an exceptional feature.
Re: UCI go command precedence
Posted: Mon Feb 22, 2021 9:53 pm
by Ras
KLc wrote: ↑Mon Feb 22, 2021 9:50 pmWhat’s the thinking time then?
These are contradictory parameters for mutually exclusive game modes, so the engine can follow either of them, whatever it likes.
Re: UCI go command precedence
Posted: Mon Feb 22, 2021 9:54 pm
by KLc
Ras wrote: ↑Mon Feb 22, 2021 9:53 pm
KLc wrote: ↑Mon Feb 22, 2021 9:50 pmWhat’s the thinking time then?
These are contradictory parameters for mutually exclusive game modes, so the engine can follow either of them, whatever it likes.
Thank you! Then it was just due to the parsing of the particular engine I tested I suppose. Good.
Re: UCI go command precedence
Posted: Mon Feb 22, 2021 9:56 pm
by Ras
KLc wrote: ↑Mon Feb 22, 2021 9:54 pmThank you! Then it was just due to the parsing of the particular engine I tested I suppose. Good.
Yeah, my engine will follow the second one because that overwrites the time handling mode suggested by the first one.
Re: UCI go command precedence
Posted: Mon Feb 22, 2021 10:40 pm
by Ferdy
KLc wrote: ↑Mon Feb 22, 2021 9:50 pm
Suppose I send (for whatever stupid reason) the following UCI go commands (with white to move):
and
What’s the thinking time then? I checked and it seems the first time has precedence. However, this is not documented in the protocol and I’m not sure if I observed a general or an exceptional feature.
There is a quote from the
specs,
Code: Select all
If one command is not sent its value should be interpreted as it would not influence the search.
Since both are specified, determine the one that is higher and use it.
go movetime 5000 wtime 1000
movetime 5000
That is 5s.
wtime 1000
White has 1s left on the clock.
So select go movetime 5000.