hmp run, calibrate, spinup#
Three flat verbs execute a workflow declared in a TOML file. They all write
their results into <project>/runs/<name>/, next to the configuration.
hmp run#
Synopsis: hmp run [config] [--resume REF] [--from STEP] [--until STEP]
[--dry-run] [--frozen] [--force] [--no-lock] [--no-display] [--no-parallel]
[--overlay FILE] [--set PATH=VALUE] [--profile [HTML]]
hmp run reads the TOML, picks the workflow declared under
[workflow].mode (simulation, overview, calibration,
comparison, testbed or site_selection) and executes the whole
pipeline.
hmp run projects/my_basin/run_demo.toml
hmp run projects/my_basin/run_demo.toml --dry-run
Flags#
Flag |
Effect |
|---|---|
|
Print the resolved workflow, the sections found and the numbered pipeline steps. Nothing is executed. |
|
Resume from the last journalled checkpoint. With a config, |
|
Start at, or stop after, a named or indexed pipeline step. Step
names and indices come from |
|
Run even when a completed run with an identical resolved config
exists. Without it, the launch is skipped and points at the existing
run. The forced result is versioned ( |
|
Reject any fresh download when |
|
Skip the post-run |
|
Do not auto-render the figures listed in |
|
Force sequential cohort execution. Useful for debugging, deterministic step ordering, single-CPU environments, or when parallel I/O contention shows up. |
|
Merge an extra TOML payload after the |
|
Override one dotted TOML path after the overlays, for example
|
|
Profile the execution with pyinstrument and write an interactive HTML
report (default |
Override precedence, lowest to highest: defaults, the base_config
chain, --overlay files, then --set values. The environment
variables HMP_CACHE_HOME, HMP_STATE_HOME, HMP_BIN and
HMP_WORKSPACE relocate machine caches and the shared data workspace;
they never patch a config field.
hmp calibrate#
Synopsis: hmp calibrate <config> [--profile [HTML]]
Shortcut for a TOML whose [workflow].mode is calibration; the same
file also runs through hmp run. The session journal is written live
under <project>/sessions/<stamp>-<method>-<id8>/ as session.json
plus trials.jsonl, and the promoted runs land in runs/ like any
other run.
Render the HTML report of a session with hmp report render <session or
run ref>; it lands in share/reports/<session>/report.html.
hmp spinup#
Synopsis: hmp spinup <config> [--then-run] [--profile [HTML]]
Restarts the same simulation cycle after cycle, each cycle starting from
the converged state of the previous one, until heads and lake stage stop
moving. --then-run chains the full production chronicle from the
converged state once convergence is reached.