configuration_directives

There are two levels of configuration directives: those that are applied at the frontend level by the aia tool and those that are applied by the backend tools.

On the front end the config directive has this pattern:

//config item [=|:=] value

where "item" is the same as a long-form CLI option. Examples are:

• out_file
• log_file
• role
• model
• backend
• terse

The assignment operator is complete optional as is the number of spaces between the item and the value.

The value is appropriate to the item. For example for switch items which are basically boolean in nature, the value is expected to be trutht to set the switch as on. Anything that is not truthy is considered as setting the switch off. Truthy values are things like 1, y, yes, yea, yep, t, true . Anything not in that list will set the switch off.

The switch items can also be writte in the config directive with a "?" at the end. For example:

//config terse = true
# and
//config terse? yes

do the same thing.

Backend Configuration

Any long-form CLI option for a backend can be expressed using this pattern:

//item [=|:=] value

For example the mods backend has a CLI option --topp so to change its calue within the prompt file you can do it like this:

//topp = 0.2