Missing UCI parameters Komodo 9.1

[Canoike]

Hi,

1) When using Komodo 9 in command line, I notice an uci option called "UCI_AnalyseMode type check default false"
However, when I use Arena or Fritz, I no longer see this option in the GUI. Why ?

2) Under Linux, I use Polyglot. What value must I put in the Polyglot.ini file to enable writing hash to the hard disk ?
Hash File Name ?
Save Hash to File ? (this is a button)
Load Hash from File ? (this is a button)

Thank you.

[mjlef]

Hi,

1) When using Komodo 9 in command line, I notice an uci option called "UCI_AnalyseMode type check default false"
However, when I use Arena or Fritz, I no longer see this option in the GUI. Why ?

2) Under Linux, I use Polyglot. What value must I put in the Polyglot.ini file to enable writing hash to the hard disk ?
Hash File Name ?
Save Hash to File ? (this is a button)
Load Hash from File ? (this is a button)

Thank you.

1. UCI_AnalseMode is intercepted and controlled internally by some GUIs, and so does not appear in the engine UCI Parameters screens. When you click the "analyze" butt in Arena, Arena sets the value for you. Most GUIs also move the Hash field for setting hash memory to some other menu too. I assume this is so they can have a common Hash size when running engine matches, but it can be confusing.

2. After stopping the search, a sequence that would work to save the hash to file name fred.has is:

setoption name Hash File Name value fred.has
setoption name Save Hash to File

to load it (assuming the Hash File Name is already set):

setoption name Load Hash from File

I do not know a lot about polyglot.ini files, but those are the commands the engine understands.

Mark

[hgm]

setoption name Hash File Name value fred.has

This is a UCI protocol violation, right? UCI options are not case sensitive, and 'name' is a protected keyword. So you should not be surprised if some interfaces will choke on this option.

I do not know a lot about polyglot.ini files, but those are the commands the engine understands.

Button options are inherently interactive, and thus cannot be controlled from an ini file. You should press them in the Engine Settings dialog at the time you want the action performed. One should never mess with polyglot.ini files anyway. Leave their creation to Polyglot, by invoking the latter with the command

polyglot -noini -ec ENGINECOMMAND

Or better yet, leave it to XBoard to issue that command, by invoking XBoard with the option -fUCI (or by ticking the UCI checkbox when you load and register the engine through the menus).

[mar]

This is a UCI protocol violation, right? UCI options are not case sensitive, and 'name' is a protected keyword. So you should not be surprised if some interfaces will choke on this option.

Interesting, I missed this detail. In fact, UCI spec even says that

Code: Select all

The name and value of the option in <id> should not be case sensitive and can inlude spaces.

but I consider this a flaw, for value it makes no sense to ignore case sensitivity because of paths and case-sensitive file systems
(in fact, I'd prefer case sensitivity for name as well).
I hope that options in CECP are case sensitive (which would make perfect sense).

[hgm]

CECP options are indeed case sensitive, as are their values.