Version 3.11.2

Owned by Magdalena Antczak
Last updated: Jul 24, 2023
6 min read

Prepared by the eResearch Office, QUT.

This page provides a guide to QUT users on how to install and run the nextflow nf-core/rnaseq workflow on the HPC.

Pre-requisites

Install Nextflow

The nf-core/rnaseq workflow requires Nextflow to be installed in your account on the HPC. Find details on how to install and test Nextflow here. Prepare a nextflow.config file and run a PBS pro submission script for Nextflow pipelines.

Additional information is available here: https://nf-co.re/usage/installation

Additional details on the workflow can be found at:

Overview: https://nf-co.re/rnaseq/3.11.2

Usage: https://nf-co.re/rnaseq/3.11.2/usage

GitHub: https://github.com/nf-core/rnaseq

Pipeline Summary

The pipeline is built using Nextflow and processes data using the following steps:

Getting Started

Download and run the workflow using minimal data provided by nf-core/rnaseq. We recommend using singularity as the profile for QUT’s HPC. Another profile option can be ‘conda.’ Note: the profile option ‘docker’ is unavailable on the HPC.

nextflow run nf-core/rnaseq -profile test,singularity --outdir results -r 3.11.2

Preparing a ‘samplesheet.csv’ file

Prepare a sample sheet file that specifies the input files to be used. To do this, we use an nf-core script to generate the ‘samplesheet.csv’ file as follows (setting strandedness to auto allows the pipeline to determine the strandedness of your RNA-seq data automatically):

#load python 3.10 module load python/3.10.8-gcccore-12.2.0 #download script and make executable wget -L https://raw.githubusercontent.com/nf-core/rnaseq/master/bin/fastq_dir_to_samplesheet.py chmod +x fastq_dir_to_samplesheet.py #generate the samplesheet.csv file ./fastq_dir_to_samplesheet.py /path/to/directory/containing/fastq_files/ samplesheet.csv \ --strandedness auto \ --read1_extension _R1.fastq.gz \ --read2_extension _R2.fastq.gz

Example of 'samplesheet.csv' required for nf-core/rnaseq pipeline version 3.11.2:

sample,fastq_1,fastq_2,strandedness control_1,/path/to/directory/containing/fastq_files/control-1_R1.fastq.gz,/path/to/directory/containing/fastq_files/control-1_R2.fastq.gz,auto control_2,/path/to/directory/containing/fastq_files/control-2_R1.fastq.gz,/path/to/directory/containing/fastq_files/control-2_R2.fastq.gz,auto control_3,/path/to/directory/containing/fastq_files/control-3_R1.fastq.gz,/path/to/directory/containing/fastq_files/control-3_R2.fastq.gz,auto infected_1,/path/to/directory/containing/fastq_files/infected-1_R1.fastq.gz,/path/to/directory/containing/fastq_files/infected-1_R2.fastq.gz,auto infected_2,/path/to/directory/containing/fastq_files/infected-1_R1.fastq.gz,/path/to/directory/containing/fastq_files/infected-2_R2.fastq.gz,auto infected_3,/path/to/directory/containing/fastq_files/infected-1_R1.fastq.gz,/path/to/directory/containing/fastq_files/infected-3_R2.fastq.gz,auto

Preparing to run on the HPC

To run this on the HPC a PBS submission script needs to be created using a text editor. For example, create a file called launch.pbs using a text editor of choice (i.e., vi or nano) and then copy and paste the code below:

This script will run version 3.11.2 of the nf-core/rnaseq pipeline on RNA-seq data from the ‘samplesheet.csv’ file. You can see here that the only truly compulsory parameter is the output directory. However, you must specify the ‘singularity’ profile to run it on this HPC. In addition, you need to select a reference genome. We recommend using one from the AWS iGenomes repository if available (you can find the list of available genomes in this config file), but other reference genome options are available too. Finally, in version 3.11.2, setting the ‘aligner’ parameter is unnecessary unless you want to use an option other than ‘star_salmon' (default). However, specifying it is not a mistake.

To submit the script to PBS, follow the instructions at the bottom of the page (section Submitting the job).

However, before you do it, consider running the version of the pipeline that will preprocess reads and then adjust the Trim Galore options (described below).

Reads preprocessing

We recommend running the nextflow nf-core/rnaseq pipeline once and then assessing the fastqc results folder to assess if sequence biases are present in the 5'-end and 3'-end ends of the sequences. In version 3.11.2, there is no option to run only quality control processes. Instead, it is possible to force the pipeline to skip reads trimming and alignment and quantify the data using pseudo-aligned reads (pink path on the image above) - this will reduce significantly the first run of the pipeline. To execute that option, add the following flags to your nextflow run nf-core/rnaseq command: --skip_trimming, --skip_alignment and select which method should perform pseudo-alignment.

Then, we can use the PBS script below to tell the pipeline to remove a defined number of bases from the 5'-end (--clip_r1 or --clip_r2) or 3'-end (--three_prime_clip_r1 or --three_prime_clip_r2). Also, we can specify to remove ribosomal RNA as these sets of sequences are non-informative (more details about this and other read filtering options in the guide).

You can experiment with different clipping options. To do this, use the nextflow run nf-core/rnaseq command with--skip_alignment like at the beginning when you were only assessing the quality of the reads, but this time, do not use--skip_trimming flag. For example, if the FastQC report suggests that you only need to clip 10 bases from the 5' end, modify the nextflow run nf-core/rnaseq in the PBS script in the following way:

Adjusting the Trim Galore options

When the initial trimming is done, verify if any more clipping needs to be done and run the nf-core/rnaseq pipeline that will perform all the steps. For example:

Submitting the job

Once you have created the folder for the run, the samplesheet.csv file, nextflow.config, and launch.pbs, you are ready to submit.

Submit the run with this command (On Lyra)

Monitoring the Run

You can use the command

Alternatively, use the command

to check on the jobs, you are running. Nextflow will launch additional jobs during the run.

You can also check the .nextflow.log file for details on what is going on.

Finally, if you have configured the connection to the NFTower, you can log on and check your run.

 

Troubleshooting

 

Add output folders/files

 

sample data

If the running was interrupted or you did not complete a particular step, or you want to modify a parameter for a particular step, instead of re-running all processes again, nextflow enables you to “-resume” the workflow.