Configuration Generation

Odatix can generate configurations automatically instead of you writing one parameter file per variant. With a few YAML rules, it produces customized parameter combinations using ranges, powers of two, lists, computed functions and set operations.

Syntax

To enable generation, add the following to an architecture _settings.yml (or a parameter domain _settings.yml):

generate_configurations: Yes
generate_configurations_settings:
  template: "parameter VALUE = $var;"
  name: "config_${var}"

variables:
  # one or more variable definitions (see below)

Variables

Every value set is declared as a variable with a type and its settings:

The Variables page is the exhaustive reference: every type, its settings, the whitelist / blacklist filters and the optional format, unit and group keys. The rest of this page shows how those variables turn into parameter files.

A typical example

variables:
  var:
    type: range
    settings:
      from: 10
      to: 100
      step: 10

Generates {10, 20, 30, …, 100} — hence ten configurations config_10 … config_100.

Computed values (functions)

Reference another variable with $name and compute a new one:

generate_configurations: Yes
generate_configurations_settings:
  template: "parameter VALUE_START = $var;\n parameter VALUE_END = ${var_func};"
  name: "config_${var}..${var_func}"

variables:
  var:
    type: multiples
    settings: { from: 0, to: 56, base: 8 }
  var_func:
    type: function
    settings:
      op: ${var}+7

var → {0, 8, 16, …, 56}, var_func → {7, 15, 23, …, 63}, producing config_0..7, config_8..15, …

Variables can also be combined with set operations (union, intersection…) so that a generated configuration list follows several constraints at once — see Variables.

Combining multiple parameters

Several generated variables can be combined so Odatix produces the full cross-product of configurations:

generate_configurations: Yes
generate_configurations_settings:
  template: "\n  parameter p_dmem_depth_pw2 = $dmem_depth,\n  parameter p_imem_depth_pw2 = $imem_depth,\n"
  name: "DMEM_${dmem_depth_pw2}-IMEM_${imem_depth_pw2}"

variables:
  dmem_depth:
    type: range
    settings: { from: 8, to: 10 }
  dmem_depth_pw2:
    type: function
    settings: { op: 2^$dmem_depth }
  imem_depth:
    type: range
    settings: { from: 8, to: 10 }
  imem_depth_pw2:
    type: function
    settings: { op: 2^$imem_depth }

Produces DMEM_256-IMEM_256, DMEM_256-IMEM_512, … DMEM_1024-IMEM_1024 (nine configurations).

Generate

odatix generate

Odatix lists every configuration it will create and asks for confirmation before writing the parameter files.

See also

• Variables — the exhaustive variable reference
• Parameter domains
• Virtual parameter domains — the same variables, used by workflows and generated-RTL architectures
• Configuration reference