Configure experiments
Keep one case explicit
Section titled “Keep one case explicit”A version: 2 YAML configuration names one experiment. Start with a supplied example and change one dimension at a time: model, runtime, memory setup or platform mode.
uv run helx validate config path/to/experiment.yamluv run helx run --config path/to/experiment.yamlThe schema rejects unknown fields, except extension keys beginning with x-. It also checks combinations that cannot be executed by the selected runtime. See the configuration reference for exact fields and defaults.
Preserve the experiment
Section titled “Preserve the experiment”Keep the original configuration, result bundle and platform revision together. Use a separate results directory for each experiment. Model inputs can be local files or supported remote URIs; retain the resolved model identity recorded in the bundle.
Platform definitions
Section titled “Platform definitions”A platform combines a SoC definition with energy parameters and revision history. Values carry provenance, and the result repeats the status it depends on. Use the platform supplied for your evaluation; modifying its values creates a different experiment, not a validated hardware configuration.
The platform schema describes the format. Platform-specific engineering data is supplied with tool access.