SpikyClip/llrnaseq is a simple RNA-seq pipeline adapted to the Latrobe Institute of Molecular Science (LIMS) High Performance Computing Cluster (HPCC).
The pipeline is built using Nextflow, a workflow tool to run tasks across multiple compute infrastructures in a very portable manner. It uses Docker/Singularity containers making installation trivial and results highly reproducible. The Nextflow DSL2 implementation of this pipeline uses one container per process which makes it much easier to maintain and update software dependencies.
As the new cluster now has singularity
support, the best profile to run
the pipeline is now -profile lims,singularity
.
- Read QC
(
FastQC 0.11.9
) - Present QC for raw reads (
MultiQC 1.9
) - Trim reads (
Trim Galore 0.6.3
) - Index genome (
Hisat2.1.0
) - Align reads (
Hisat2.1.0
) - Sort and index alignments (
Samtools 1.9
) - Read quantification (
featureCounts 1.6
,StringTie 1.3.5
)
-
Install
Nextflow
(>=21.04.3
) (seeinstallation.md
for more information) -
If executing the pipeline on a computer that can support it, install any of
Docker
,Singularity
,Podman
,Shifter
orCharliecloud
for full pipeline reproducibility (please only useConda
as a last resort; see docs). If executing the pipeline on the LIMS-HPCC, ignore this step. -
Download the pipeline and test it on a minimal dataset with a single command:
- If running on the LIMS-HPCC:
nextflow run SpikyClip/llrnaseq -profile test,lims,singularity
- If running on a
Docker
/Singularity
capable machine:nextflow run SpikyClip/llrnaseq -profile test,<docker/singularity/podman/shifter/charliecloud/conda/institute>
- If you are using
singularity
then the pipeline will auto-detect this and attempt to download the Singularity images directly as opposed to performing a conversion from Docker images. If you are persistently observing issues downloading Singularity images directly due to timeout or network issues then please use the--singularity_pull_docker_container
parameter to pull and convert the Docker image instead. Alternatively, it is highly recommended to use thenf-core download
command to pre-download all of the required containers before running the pipeline and to set theNXF_SINGULARITY_CACHEDIR
orsingularity.cacheDir
Nextflow options to be able to store and re-use the images from a central location for future pipeline runs. - If you are using
conda
, it is highly recommended to use theNXF_CONDA_CACHEDIR
orconda.cacheDir
settings to store the environments in a central location for future pipeline runs.
- If running on the LIMS-HPCC:
-
Start running your own analysis!
-
You will first need to create a samplesheet with information about the samples you would like to analyse before running the pipeline.
-
The pipeline can pull some common genome references used for alignment from Illumina iGenomes. Check out
igenomes.config
to see the full list of iGenomes this pipeline recognises.nextflow run llrnaseq \ -profile lims,singularity \ --input <samplesheet>.csv \ --genome GRCh37
-
Alternatively, you can specify
genome.fa
andgenome.gtf
explicitly:nextflow run llrnaseq \ -profile lims,singularity \ --input <samplesheet>.csv \ --fasta <genome>.fa> \ --gtf <annotation>.gtf
-
If running a job on the LIMS-HPCC, wrap the
nextflow run
command in a shell script (e.g.run_pipeline.sh
) and submit it usingslurm
:sbatch run_pipeline.sh
Consider specifying the estimated time needed in the script if the job may take more than 8 hours using
#SBATCH --time=<HH>:<MM>:<SS>
. This is to avoid the pipeline ending prematurely. However, if the job is interrupted, it may be resumed with the nextflow-resume
flag. See the usage docs for more information on the-resume
flag.
-
The SpikyClip/llrnaseq pipeline comes with documentation about the pipeline usage, parameters and output.
SpikyClip/llrnaseq was originally written by Vikesh Ajith.
We thank the following people for their extensive assistance in the development of this pipeline:
This applied research project was supervised by Dr. Mathew Lewsey and Dr. Bhavna Hurgobin from lewseylab.
If you would like to contribute to this pipeline, please see the contributing guidelines.
An extensive list of references for the tools used by the pipeline can be found
in the CITATIONS.md
file.
You can cite the nf-core
publication as follows:
The nf-core framework for community-curated bioinformatics pipelines.
Philip Ewels, Alexander Peltzer, Sven Fillinger, Harshil Patel, Johannes Alneberg, Andreas Wilm, Maxime Ulysse Garcia, Paolo Di Tommaso & Sven Nahnsen.
Nat Biotechnol. 2020 Feb 13. doi: 10.1038/s41587-020-0439-x.