Chapter 24 — Configuration-Key Reference
Bench settings
The Bench reads ~/.iris/iris-bench.cfg. Supported launch preferences
include [server] port, [launch] open_browser, and remembered [tree]
positions. Let the UI write tree selections unless you have a reason to
edit them by hand. An illustrative preference file is:
[server]
port = 8765
[launch]
open_browser = false
Use --port N for a launch-specific port preference and --no-open to
suppress browser opening. Read the actual startup address rather than
assuming the preferred port was available.
Tracker settings and live controls
~/.iris/iris-tracker.cfg supplies host-wide tracker preferences. Use only
keys supported by your installed version. Unknown or unusable tracker keys
can refuse startup; a misspelled setting is not silently a valid setting.
Use the run's iris.cmd for supported live controls such as interval,
adaptive bounds, sensitivity, and dryrun. See Chapter 11.
Capture coverage can be reduced when resources are constrained. Read the frame's mode and missing-channel reasons. A manual mode cannot force the instrument to capture beyond what it can support, and changing a resource setting does not manufacture data already omitted from a bundle.
Butler and derived expressions
~/.iris/iris-butler.cfg supplies relay defaults; a run's iris.cfg is a
Butler-specific override. It is not a per-run Bench or tracker configuration.
Saved User-tab expressions live in ~/.iris/derived_metrics.toml and retain
their definitions and provenance for later runs.
Configuration boundaries
Keep credential-bearing configuration private. The Bench has no password;
network policy controls viewing. Writes require localhost on the Bench
machine or a supported SSH port-forward as your own account; see
Chapter 10. For precedence and its exceptions, see
Chapter 7.
