A pipeline for the detection and mapping of long non-coding RNAs
Make sure you have all the required dependencies listed in the last section.
Install the Nextflow runtime by running the following command:
$ curl -fsSL get.nextflow.io | bash
When done, you can launch the pipeline execution by entering the command shown below:
$ ./nextflow run cbcrg/piper-nf
By default the pipeline is executed against the provided example dataset. Check the Pipeline parameters section below to see how specify your input data on the program command line.
nextflow run piper-nf --query=/some/path/query.fa
nextflow run piper-nf --genomes-file=my-genomes.txt
nextflow run piper-nf --genomes-db=/my/db/path
nextflow run piper-nf --query-chunk-size=50
nextflow run piper-nf --result-dir=./my-result/
ncbi-blast
(default) or wu-blast
nextflow run piper-nf --blast-strategy=wu-blast
Run with Docker
Piper-nf dependecies are also distributed by using a Docker container which frees you from the installation and configuration of all the pieces of software required by Piper-nf.
The Piper-nf Docker image is published at this address https://registry.hub.docker.com/u/cbcrg/piper-nf/
If you have Docker installed in your computer pull this image by entering the following command:
$ docker pull cbcrg/piper-nf
After that you will be able to run Piper-nf using the following command line:
$ ./nextflow run cbcrg/piper-nf -with-docker
Piper-NF execution relies on Nextflow framework which provides an abstraction between the pipeline functional logic and the underlying processing system.
Thus it is possible to execute it on your computer or any cluster resource manager without modifying it.
Currently the following clusters are supported:
By default the pipeline is parallelized by spanning multiple threads in the machine where the script is launched.
To submit the execution to a SGE cluster create a file named nextflow.config
, in the directory
where the pipeline is going to be launched, with the following content:
task {
processor='sge'
queue='<your queue name>'
}
In doing that, tasks will be executed through the qsub
SGE command, and so your pipeline will behave like any
other SGE job script, with the benefit that Nextflow will automatically and transparently manage the tasks
synchronisation, file(s) staging/un-staging, etc.
Alternatively the same declaration can be defined in the file $HOME/.nextflow/config
.
To lean more about the avaible settings and the configuration file read the Nextflow documentation http://www.nextflow.io/docs/latest/config.html