-
Notifications
You must be signed in to change notification settings - Fork 3
amalgkit rerun
Kenji Fukushima edited this page Jun 8, 2026
·
2 revisions
amalgkit rerun reads sanity_report.json, resolves failed pipeline targets, and reruns selected commands.
It also writes a manifest so the rerun plan can be inspected or archived.
Run sanity first:
amalgkit sanity --out_dir ./ --allPreview rerun targets:
amalgkit rerun --out_dir ./ --dry_run yesExecute the rerun:
amalgkit rerun --out_dir ./Report: out_dir/sanity/sanity_report.json
Manifest: out_dir/sanity/rerun_manifest.json
--metadata report is the default. It uses the metadata path recorded in the sanity report and is usually the safest choice.
If --check is omitted, rerun uses the checks recorded in sanity_report.json.
Supported targets:
getfastqindexquantmergebuscofinalizeall
Rerun selected target families:
amalgkit rerun --out_dir ./ --check getfastq,quantLimit by run:
amalgkit rerun \
--out_dir ./ \
--check getfastq,quant \
--run SRR000001,SRR000002Limit by species:
amalgkit rerun \
--out_dir ./ \
--check merge,busco,finalize \
--species "Homo sapiens"Include warning-level issues, such as missing global summary PDFs:
amalgkit rerun --out_dir ./ --include_warnings yesWrite the default manifest:
amalgkit rerun --out_dir ./ --manifest inferredWrite to an explicit path:
amalgkit rerun --out_dir ./ --manifest ./rerun_manifest.jsonDisable manifest output:
amalgkit rerun --out_dir ./ --manifest none-
--redo yesis the default so broken outputs can be overwritten. -
--download_dirand--download_lock_dirare shared with download-heavy targets. - Use
--dry_run yesbefore large cluster reruns. - Use
--include_warnings yeswhen the goal is to regenerate warning-level missing summaries, not only failed core outputs.
-
Start
-
Active commands
-
Migration and release