Page 1 of 1

info string

PostPosted: 10 Aug 2009, 09:40
by Michel
I have implemented relaying of info string commands to the GUI (trivial!). However I have not
found any engines that actually emit such commands.

So is this an empty feature?

Re: info string

PostPosted: 10 Aug 2009, 09:49
by F.Huber
Michel wrote:I have implemented relaying of info string commands to the GUI (trivial!). However I have not
found any engines that actually emit such commands.

So is this an empty feature?

Take for example Rybka: it displays a lot of "info string ..." (whenever you change any of its options).

Not to speak of ChestUCI of course ... :wink:

Re: info string

PostPosted: 10 Aug 2009, 09:53
by Michel
Ok. I tried Rybka.

setoption name UCI_LimitStrength value true
info UCI_LimitStrength set to true


Shouldn't that be

info string UCI_LimitStrength set to true

Or am I misreading the UCI protocol?

Re: info string

PostPosted: 10 Aug 2009, 09:54
by F. Bluemers
Michel wrote:I have implemented relaying of info string commands to the GUI (trivial!). However I have not
found any engines that actually emit such commands.

So is this an empty feature?

As far as i know it is not (much) used.
Certainly not in the fruit/toga family.
It is a nice feature while debugging...

Re: info string

PostPosted: 10 Aug 2009, 10:01
by F. Bluemers
Michel wrote:Ok. I tried Rybka.

setoption name UCI_LimitStrength value true
info UCI_LimitStrength set to true


Shouldn't that be

info string UCI_LimitStrength set to true

Or am I misreading the UCI protocol?

That is also the way I understand it.However maybe its possible to understand it in a different manner:
If there is no string keyword ,the gui might interprete and reformat whatever is send as info commands.
Even if it did not start with one of the info commands.


Anyway info string UCI_LimitStrength set to true is the better choice.

Re: info string

PostPosted: 10 Aug 2009, 10:03
by F.Huber
Michel wrote:Ok. I tried Rybka.

setoption name UCI_LimitStrength value true
info UCI_LimitStrength set to true


Shouldn't that be

info string UCI_LimitStrength set to true

Or am I misreading the UCI protocol?


No, of course you are right, but you seem to have used Rybka 2.3.2, and in this old version it was really done wrong (i.e. omitting 'string' after 'info').

Re: info string

PostPosted: 10 Aug 2009, 11:05
by Michel
Well I implemented it. I restricted to info that is shown during searching (that is PG's current philosophy).
The other info seems to disappear very quickly anyway.