💊 ZARP - RNA-Seq analysis made easy! 💉
- You have a bunch of RNA-Seq samples and wanna know what's in them? ZARP 'em!
- You have an extensive SRA query with hundreds of runs and you don't know where to start? Easy - ZARP 'em!
- Barry left you some samples to analyze and then went on vacation, again? No problem, ZARP 'em!
ZARP-cli uses the HTSinfer package to infer missing metadata and then runs the ZARP RNA-Seq analysis pipeline on your samples. Impress your colleagueswith your sudden productivity boost. Or better yet, use the time saved to go on that camping trip with Barry. Just make sure to guard your secret! 😉
zarp [-h] [--init] [--verbosity {DEBUG,INFO,WARN,ERROR,CRITICAL}] [--version]
PATH/ID [PATH/ID ...]
# Examples
zarp --init # set up user defaults for ZARP
zarp sample_1.fq.gz /path/to/sample_2.fq.gz # ZARP two single-end libraries
zarp my_sample@abcdefgh.fq.gz # assign a sample name
zarp mate_1.fq.gz,mate_2.fq.gz # ZARP one paired-end library
zarp table:table.tsv # ZARP all samples from a sample table
zarp SRR0123456789 my_other_sample@SRR0123456789 # ZARP SRA runs
zarp \
sample_1.fq.gz /path/to/sample_2.fq.gz \
my_sample@adcdefgh.fg.gz \
mate_1.fq.gz,mate_2.fq.gz \
table:table.tsv \
SRR0123456789 my_other_sample@SRR0123456789 # ZARP everything at once!Quick installation requires the following:
- Linux with root permissions
conda >= 22.11.1mamba >=1.3.0
Execute the following commands:
git clone git@github.com:zavolanlab/zarp
git clone git@github.com:zavolanlab/zarp-cli.git
cd zarp-cli
mamba env create -f install/environment.root.yml
conda activate zarp-cliIf you do not have root privileges on your machine, replace the
mamba env createcall with the following one:mamba env create -f install/environment.yml
That's it - you can now use ZARP-cli!
We have designed ZARP-cli to be easy to use. However, there are still a lot
of ways in which execution can be tweaked. For the full documentation visit:
https://zavolanlab.github.io/zarp-cli
The project adopts the Semantic Versioning specification for
versioning. Currently the service is still in beta stage, so the API may change
and even break without further notice. However, we are planning to release a
1.0.0 release as soon as we feel that the software is reasonably stable and
"feature complete" for all of the major use cases we wish to cover.
This project lives off your contributions, be it in the form of bug reports, feature requests, discussions, or fixes and other code changes. Please refer to the contributing guidelines if you are interested to contribute. Please mind the code of conduct for all interactions with the community.
For questions or suggestions regarding the code, please use the issue tracker. For any other inquiries, please contact us by email.