Runs, checkpoints, export

A step is run as often as its parameters change, and nothing is overwritten.

Every run is kept

Under a step's Run button is the list of every run it made: the parameters in words (k 2–8 · 20 replicates, purity 0.8 · bootstrap 10), when it started, how long it took, its state, a log toggle, and a download. Each run is a folder in the daemon's workspace, sigscape-runs/<id>/, with the files the package wrote, the job's record and its log.

Choosing the one to carry forward

The next step reads the chosen run of the step before it. Until you choose, that is the newest finished run; click another row to choose it instead. Choosing a run also chooses the runs it was computed from, so a chain stays consistent. A run computed from a different upstream run stays listed, dimmed, labeled from another <step>; choosing it brings its own ancestry along.

In MuSiCal this is discover, match, refit; in SigMA2 built on the runner it is build, simulate, tune. Compare in SigMA2 can set any two tune runs against each other.

Export

• The download on a row is that run's folder as a zip.
• The last stage of a tool offers Export results: the chosen chain as one zip, a folder per step.

Both are plain links the daemon serves, so a script can fetch them too.

History

Runs are the daemon's job list, so a reload and a daemon restart show the same runs. Your choice per step is kept in the browser, keyed by what the runs ran on, so the same records show the same chosen chain next time.