4. Quality Control

Aim:

• Assess the quality of raw datasets

• Define quality trimming parameters prior running the complete RNAseq gene profiling pipeline

Run RNA-seq QC check

The pipeline requires preparing at least 2 files:

• Metadata file (samplesheet.csv) that specifies the name of the samples, location of FASTQ files ('Read 1' and ‘Read 2’), and strandedness (forward, reverse, or auto. Note: auto is used when the strandedness of the data is unknown)

• PBS Pro script (launch_nf-core_RNAseq_QC.pbs) with instructions to run the pipeline

Create the metadata file (samplesheet.csv):

Change to the data folder directory:

cd $HOME/workshop/2024-2/session4_RNAseq/data/

Copy the bash script to the working folder

cp /work/training/2024/rnaseq/scripts/create_samplesheet_nf-core_RNAseq_SEdata.sh $HOME/workshop/20242/session4_RNAseq/data

• Note: you could replace ‘$HOME/workshop/data’ with “.” A dot indicates ‘current directory’ and will copy the file to the directory where you are currently located

View the content of the script:

cat create_samplesheet_nf-core_RNAseq_SEdata.sh

Example for Single-End data (when only ‘Read 1’ is available):

NOTE: modify ‘read1_extension’ as appropriate for your data. For example: _1.fastq.gz or _R1_001.fastq.gz or _R1.fq.gz , etc

Example for Paired-End data (when ‘Read 1’ and ‘Read2’ are available) - Copy available script if working with PE data:

cat /work/training/2024/rnaseq/

Let’s generate the metadata file by running the following command:

sh create_samplesheet_nf-core_RNAseq_SEdata.sh

Check the newly created samplesheet.csv file:

cat samplesheet.cvs

Copy the PBS Pro script for QC (launch_nf-core_RNAseq_QC.pbs)

Copy and paste the code below to the terminal:

cp $HOME/workshop/2024-2/session4_RNAseq/data/samplesheet.csv $HOME/workshop/2024-2/session4_RNAseq/runs/run2_QC
cp $HOME/workshop/2024-2/session4_RNAseq/scripts/launch_nf-core_RNAseq_QC.pbs $HOME/workshop/2024-2/session4_RNAseq/runs/run2_QC
cd $HOME/workshop/2024-2/session4_RNAseq/runs/run2_QC

• Line 1: Copy the samplesheet.csv file to the working directory

• Line 2: move to the working directory

• Line 3: copy the launch_nf-core_RNAseq_QC.pbs submission script to the working directory

View the content of the launch_nf-core_RNAseq_QC.pbs script:

cat launch_nf-core_RNAseq_QC.pbs

• 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.

• Version 3.12.0 allows running the pipeline to do quality assessment only, without any alignment, read counting, or trimming.

Submitting the job

Once you have created the folder for the run, the samplesheet.csv file, and launch.pbs, you are ready to submit the job to the HPC scheduler:

qsub launch_nf-core_RNAseq_QC.pbs

Monitoring the Run

qjobs

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.

Once the pipeline has finished running - Assess the QC report:

NOTE: To proceed, you need to be on QUT’s WiFi network or signed via VPN.

To browse the working folder in the HPC type in the file finder:

Windows PC

\\hpc-fs\work\training\rnaseq

Mac

smb://hpc-fs/work/training/rnaseq

Evaluate the nucleotide distributions in the 5'-end and 3'-end of the sequenced reads (Read1 and Read2). Look into the “MultiQC” folder and open the provided HTML report.

Items to check:

• The overall quality of the experiment and reads. Look at the “Sequence Quality Histogram” plot. For example, if Phred assigns a quality score of 30 to a base, the chances that this base is called incorrectly are 1 in 1000. Phred quality scores are logarithmically linked to error probabilities.

• Assess QC reports (FastQC and MultiQC) to define how many nucleotides should be trimmed from the 5'-end and/or 3-end regions of the FASTQ reads (see Case 3 below).