MetaGEAR Tools (CLI)
MetaGEAR Tools is a small command-line wrapper (metagear) that installs the pipeline, configures defaults for your machine, manages reference databases, and launches workflows — so you can run a full metagenomic analysis without writing Nextflow.
→ schirmer-lab/metagear-tools ↗ — installer, CLI source, configuration templates, and full reference.
Why a wrapper
Nextflow and nf-core are powerful but have a learning curve. MetaGEAR Tools removes it by:
- Detecting your hardware (CPUs, RAM) and setting resource limits to roughly 80% of available capacity, capped at 48 CPUs and 80 GB.
- Installing the matching pipeline version alongside itself, so you don’t have to coordinate Nextflow + pipeline versions yourself.
- Centralizing configuration under
~/.metagear/with editable defaults. - Wrapping every workflow behind a one-word subcommand.
Prerequisites
Install
1. Run the installer.
curl -L https://get-metagear.schirmerlab.de | bashLatest stable release, installed to ~/.metagear/.
2. (Optional) Pin a specific pipeline version.
curl -L https://get-metagear.schirmerlab.de | bash -s -- --pipeline 26.09.13. Review generated configuration in ~/.metagear/metagear.config and ~/.metagear/metagear.env. Adjust paths or resource limits if needed.
Basic usage
# Install reference databases (one-time, per machine)metagear download_databases
# Run workflowsmetagear qc_dna --input samples.csvmetagear microbial_profiles --input samples.csv
# Generate the launch script without executing it (useful for HPC)metagear qc_dna --input samples.csv -previewInput samplesheet:
sample,fastq_1,fastq_2SAMPLE-01,/path/to/sample1_R1.fastq.gz,/path/to/sample1_R2.fastq.gzSAMPLE-02,/path/to/sample2_R1.fastq.gz,/path/to/sample2_R2.fastq.gzPresets
A preset runs several workflows in dependency order in one workspace, with --reuse-outputs switched
on so each step picks up what the ones before it produced instead of recomputing:
| Preset | Runs |
|---|---|
profiles | microbial_profiles |
genomes | genes → classification → mag → msp |
microbiome | genomes + virus |
→ Presets — what each one produces and what it costs.
metagear microbiome --input samples.csv --outdir results/
# show the plan without running anythingmetagear microbiome --input samples.csv --outdir results/ --previewIf a step fails, the ones after it do not start. Fix what it reported and run the same command again — the steps that already finished resume from their own caches rather than starting over.
Running across machines
metagear cluster brings up a HyperQueue cluster across the machines listed in nodes.conf, so one
cohort spreads over all of them:
metagear cluster up --pct 75 # also: ensure, down, status, restart, jobs, scratch, db, sweepMETAGEAR_MODE=cluster metagear microbiome --input samples.csv --outdir results/METAGEAR_MODE=single, the default, keeps a run on the machine you launched it from.
Where to go next
- metagear-tools repository — full reference, configuration options, troubleshooting
- MetaGEAR Pipeline — what each workflow actually does
- Open an issue — bug reports for the installer or CLI