Manage runs¶

A run is a search and its run directory. This guide shows how to restart, continue and re-evaluate runs.

Start again¶

qseek search does not overwrite an existing run directory. To start the search again with the same name:

qseek search my-search.json --force      # keep the old run as a backup
qseek search my-search.json --force --no-backup  # overwrite the old run

With --force, Qseek renames the old run directory with a .bak-<time> suffix.

Continue a search¶

If a search stops, e.g. on a machine restart, continue it where it stopped:

qseek continue my-search/

Qseek reads the configuration of the run from its search.json and the progress from progress.json. Detections after the last processed window are removed and searched again.

Recalculate magnitudes and features¶

To change the magnitudes or features of a finished run, edit the magnitudes and features in the run's search.json and recalculate them for all detections:

qseek feature-extraction my-search/ --recalculate

--nparallel sets how many detections are processed in parallel.

Search again with station corrections¶

After a first run, extract station corrections from its travel time residuals and run a second search with them. The corrections refine the locations and can reveal more events.

Export the detections¶

Export the detections of a run to other formats, e.g. a VELEST project for velocity model inversion:

qseek export list
qseek export velest my-search/ velest-project/

--force overwrites an existing export directory.