Show run history
run_historyInspect previous optimization runs from disk, newest first, to review state, YAML, key settings, metrics, and data problems without writing anything.
Instructions
Facts of the earlier runs under a folder, newest first, read from the files on disk. Writes nothing.
Use it to see what was tried: state, the YAML of each run, key settings, main metrics. A missing or partial file
(no metrics.json, a cut last history line, a broken status.json) is a fact in problems, not an error.
CONTRACTS.md section 21.
root: the folder to search (relative paths start at the work folder). Default: the work folder.
depth: how many levels of folders to search (default 2: runs/ under the work folder; at most 5). A run
folder holds run.json or status.json. A root that is a run folder gives that run. The scan stops after 5000
folders and says so.
limit: the newest runs only (default 20). count is the number of runs found, and a note says when older runs
are left out. 0 gives all runs.
detail: the full facts of each run (all settings, all metrics, which files exist).
Each run: name, run_dir, path (relative), state, iteration, iterations, process_alive, modified, yaml_path,
yaml_exists, yaml_newer_than_run (the YAML file is newer than the run: it may not be the one that ran), settings
(voxel_size_mm, volume_fraction, iterations, solver, filter_radius_mm, n_active, load case names), metrics
(compliance_initial and compliance_final, mass_final_g, volume_final_mm3, volume_fraction_final, run_time_s),
metrics_source and problems. list_runs is the cheaper list (it reads no metrics).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| root | No | ||
| depth | No | ||
| limit | No | ||
| detail | No |