20220321-pgen-nextflow_rnaseq-tissues-2666621
A modular tool to aggregate results from bioinformatics analyses across many samples into a single report.
This report has been generated by the nf-core/rnaseq analysis pipeline. For information about how to interpret these results, please see the documentation.
Report
generated on 2022-03-26, 16:16
based on data in:
/gscratch/scrubbed/samwhite/outputs/20220323-pgen-nextflow_rnaseq-tissues/work/52/429af6e7d80a8084c003f8911b5a80
General Statistics
Showing 15/15 rows and 24/30 columns.| Sample Name | M Reads Mapped | % rRNA | dupInt | % Dups | 5'-3' bias | M Aligned | % Proper Pairs | % Aligned | M Aligned | Error rate | M Non-Primary | M Reads Mapped | % Mapped | % Proper Pairs | M Total seqs | % Aligned | M Aligned | % Dups | % GC | M Seqs | % BP Trimmed | % Dups | % GC | M Seqs |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ctenidia | 80.6 | 0.00% | 0.47% | 64.2% | 0.97 | 36.7 | 30.6% | 18.5% | 10.6 | 0.78% | 7.1 | 73.5 | 100.0% | 99.9% | 73.5 | 60.3% | 34.5 | |||||||
| ctenidia_1 | 68.9% | 36% | 60.3 | 6.7% | 67.5% | 36% | 57.3 | |||||||||||||||||
| ctenidia_2 | 73.8% | 37% | 60.3 | 7.1% | 73.0% | 36% | 57.3 | |||||||||||||||||
| gonad | 88.7 | 0.00% | 0.84% | 94.6% | 1.06 | 41.0 | 4.6% | 18.9% | 12.4 | 0.77% | 6.6 | 82.1 | 100.0% | 99.9% | 82.1 | 59.3% | 38.9 | |||||||
| gonad_1 | 76.8% | 38% | 69.6 | 7.5% | 77.9% | 37% | 65.6 | |||||||||||||||||
| gonad_2 | 83.5% | 38% | 69.6 | 8.5% | 86.1% | 37% | 65.6 | |||||||||||||||||
| heart | 144.8 | 0.00% | 0.18% | 50.6% | 1.05 | 66.3 | 42.9% | 24.7% | 25.7 | 0.67% | 12.2 | 132.6 | 100.0% | 99.9% | 132.6 | 59.8% | 62.1 | |||||||
| heart_1 | 44.8% | 38% | 104.7 | 3.1% | 44.6% | 38% | 103.9 | |||||||||||||||||
| heart_2 | 46.4% | 38% | 104.7 | 2.5% | 46.6% | 38% | 103.9 | |||||||||||||||||
| juvenile | 462.0 | 0.00% | 0.31% | 57.0% | 0.93 | 210.2 | 36.7% | 20.2% | 65.9 | 1.17% | 41.4 | 420.6 | 100.0% | 99.9% | 420.6 | 60.0% | 196.1 | |||||||
| juvenile_1 | 64.3% | 37% | 329.0 | 2.4% | 65.3% | 37% | 326.7 | |||||||||||||||||
| juvenile_2 | 67.4% | 37% | 329.0 | 2.6% | 69.3% | 37% | 326.7 | |||||||||||||||||
| larvae | 98.4 | 0.00% | 0.79% | 77.0% | 0.94 | 44.6 | 19.2% | 22.1% | 15.9 | 1.19% | 9.2 | 89.2 | 100.0% | 99.9% | 89.2 | 57.4% | 41.4 | |||||||
| larvae_1 | 68.0% | 38% | 73.0 | 3.2% | 69.1% | 38% | 72.1 | |||||||||||||||||
| larvae_2 | 76.2% | 39% | 73.0 | 3.7% | 77.8% | 38% | 72.1 |
SALMON DESeq2 sample similarity
is generated from clustering by Euclidean distances between DESeq2 rlog values for each sample in the deseq2_qc.r script.
SALMON DESeq2 PCA plot
PCA plot between samples in the experiment. These values are calculated using DESeq2 in the deseq2_qc.r script.
STAR_SALMON DESeq2 PCA plot
PCA plot between samples in the experiment. These values are calculated using DESeq2 in the deseq2_qc.r script.
STAR_SALMON DESeq2 sample similarity
is generated from clustering by Euclidean distances between DESeq2 rlog values for each sample in the deseq2_qc.r script.
Biotype Counts
shows reads overlapping genomic features of different biotypes, counted by featureCounts.
DupRadar
provides duplication rate quality control for RNA-Seq datasets. Highly expressed genes can be expected to have a lot of duplicate reads, but high numbers of duplicates at low read counts can indicate low library complexity with technical duplication. This plot shows the general linear models - a summary of the gene duplication distributions.
Picard
Picard is a set of Java command line tools for manipulating high-throughput sequencing data.
Mark Duplicates
Number of reads, categorised by duplication state. Pair counts are doubled - see help text for details.
The table in the Picard metrics file contains some columns referring read pairs and some referring to single reads.
To make the numbers in this plot sum correctly, values referring to pairs are doubled according to the scheme below:
READS_IN_DUPLICATE_PAIRS = 2 * READ_PAIR_DUPLICATESREADS_IN_UNIQUE_PAIRS = 2 * (READ_PAIRS_EXAMINED - READ_PAIR_DUPLICATES)READS_IN_UNIQUE_UNPAIRED = UNPAIRED_READS_EXAMINED - UNPAIRED_READ_DUPLICATESREADS_IN_DUPLICATE_PAIRS_OPTICAL = 2 * READ_PAIR_OPTICAL_DUPLICATESREADS_IN_DUPLICATE_PAIRS_NONOPTICAL = READS_IN_DUPLICATE_PAIRS - READS_IN_DUPLICATE_PAIRS_OPTICALREADS_IN_DUPLICATE_UNPAIRED = UNPAIRED_READ_DUPLICATESREADS_UNMAPPED = UNMAPPED_READS
Preseq
Preseq estimates the complexity of a library, showing how many additional unique reads are sequenced for increasing total read count. A shallow curve indicates complexity saturation. The dashed line shows a perfectly complex library where total reads = unique reads.
Complexity curve
Note that the x axis is trimmed at the point where all the datasets show 80% of their maximum y-value, to avoid ridiculous scales.
QualiMap
QualiMap is a platform-independent application to facilitate the quality control of alignment sequencing data and its derivatives like feature counts.
Genomic origin of reads
Classification of mapped reads as originating in exonic, intronic or intergenic regions. These can be displayed as either the number or percentage of mapped reads.
There are currently three main approaches to map reads to transcripts in an RNA-seq experiment: mapping reads to a reference genome to identify expressed transcripts that are annotated (and discover those that are unknown), mapping reads to a reference transcriptome, and de novo assembly of transcript sequences (Conesa et al. 2016).
For RNA-seq QC analysis, QualiMap can be used to assess alignments produced by the first of these approaches. For input, it requires a GTF annotation file along with a reference genome, which can be used to reconstruct the exon structure of known transcripts. This allows mapped reads to be grouped by whether they originate in an exonic region (for QualiMap, this may include 5′ and 3′ UTR regions as well as protein-coding exons), an intron, or an intergenic region (see the Qualimap 2 documentation).
The inferred genomic origins of RNA-seq reads are presented here as a bar graph showing either the number or percentage of mapped reads in each read dataset that have been assigned to each type of genomic region. This graph can be used to assess the proportion of useful reads in an RNA-seq experiment. That proportion can be reduced by the presence of intron sequences, especially if depletion of ribosomal RNA was used during sample preparation (Sims et al. 2014). It can also be reduced by off-target transcripts, which are detected in greater numbers at the sequencing depths needed to detect poorly-expressed transcripts (Tarazona et al. 2011).
Gene Coverage Profile
Mean distribution of coverage depth across the length of all mapped transcripts.
There are currently three main approaches to map reads to transcripts in an RNA-seq experiment: mapping reads to a reference genome to identify expressed transcripts that are annotated (and discover those that are unknown), mapping reads to a reference transcriptome, and de novo assembly of transcript sequences (Conesa et al. 2016).
For RNA-seq QC analysis, QualiMap can be used to assess alignments produced by the first of these approaches. For input, it requires a GTF annotation file along with a reference genome, which can be used to reconstruct the exon structure of known transcripts. QualiMap uses this information to calculate the depth of coverage along the length of each annotated transcript. For a set of reads mapped to a transcript, the depth of coverage at a given base position is the number of high-quality reads that map to the transcript at that position (Sims et al. 2014).
QualiMap calculates coverage depth at every base position of each annotated transcript. To enable meaningful comparison between transcripts, base positions are rescaled to relative positions expressed as percentage distance along each transcript (0%, 1%, …, 99%). For the set of transcripts with at least one mapped read, QualiMap plots the cumulative mapped-read depth (y-axis) at each relative transcript position (x-axis). This plot shows the gene coverage profile across all mapped transcripts for each read dataset. It provides a visual way to assess positional biases, such as an accumulation of mapped reads at the 3′ end of transcripts, which may indicate poor RNA quality in the original sample (Conesa et al. 2016).
The Normalised plot is calculated by MultiQC to enable comparison of samples with varying sequencing depth. The cumulative mapped-read depth at each position across the averaged transcript position are divided by the total for that sample across the entire averaged transcript.
RSeQC
RSeQC package provides a number of useful modules that can comprehensively evaluate high throughput RNA-seq data.
Read Distribution
Read Distribution calculates how mapped reads are distributed over genome features.
Inner Distance
Inner Distance calculates the inner distance (or insert size) between two paired RNA reads. Note that this can be negative if fragments overlap.
Read Duplication
read_duplication.py calculates how many alignment positions have a certain number of exact duplicates. Note - plot truncated at 500 occurrences and binned.
Junction Annotation
Junction annotation compares detected splice junctions to a reference gene model. An RNA read can be spliced 2 or more times, each time is called a splicing event.
Junction Saturation
Junction Saturation counts the number of known splicing junctions that are observed in each dataset. If sequencing depth is sufficient, all (annotated) splice junctions should be rediscovered, resulting in a curve that reaches a plateau. Missing low abundance splice junctions can affect downstream analysis.
Infer experiment
Infer experiment counts the percentage of reads and read pairs that match the strandedness of overlapping transcripts. It can be used to infer whether RNA-seq library preps are stranded (sense or antisense).
Bam Stat
All numbers reported in millions.
Samtools
Samtools is a suite of programs for interacting with high-throughput sequencing data.
Percent Mapped
Alignment metrics from samtools stats; mapped vs. unmapped reads.
For a set of samples that have come from the same multiplexed library, similar numbers of reads for each sample are expected. Large differences in numbers might indicate issues during the library preparation process. Whilst large differences in read numbers may be controlled for in downstream processings (e.g. read count normalisation), you may wish to consider whether the read depths achieved have fallen below recommended levels depending on the applications.
Low alignment rates could indicate contamination of samples (e.g. adapter sequences), low sequencing quality or other artefacts. These can be further investigated in the sequence level QC (e.g. from FastQC).
Alignment metrics
This module parses the output from samtools stats. All numbers in millions.
Samtools Flagstat
This module parses the output from samtools flagstat. All numbers in millions.
Mapped reads per contig
The samtools idxstats tool counts the number of mapped reads per chromosome / contig. Chromosomes with < 0.1% of the total aligned reads are omitted from this plot.
FastQC (raw)
FastQC (raw) This section of the report shows FastQC results before adapter trimming.
Sequence Counts
Sequence counts for each sample. Duplicate read counts are an estimate only.
This plot show the total number of reads, broken down into unique and duplicate if possible (only more recent versions of FastQC give duplicate info).
You can read more about duplicate calculation in the FastQC documentation. A small part has been copied here for convenience:
Only sequences which first appear in the first 100,000 sequences in each file are analysed. This should be enough to get a good impression for the duplication levels in the whole file. Each sequence is tracked to the end of the file to give a representative count of the overall duplication level.
The duplication detection requires an exact sequence match over the whole length of the sequence. Any reads over 75bp in length are truncated to 50bp for this analysis.
Sequence Quality Histograms
The mean quality value across each base position in the read.
To enable multiple samples to be plotted on the same graph, only the mean quality scores are plotted (unlike the box plots seen in FastQC reports).
Taken from the FastQC help:
The y-axis on the graph shows the quality scores. The higher the score, the better the base call. The background of the graph divides the y axis into very good quality calls (green), calls of reasonable quality (orange), and calls of poor quality (red). The quality of calls on most platforms will degrade as the run progresses, so it is common to see base calls falling into the orange area towards the end of a read.
Per Sequence Quality Scores
The number of reads with average quality scores. Shows if a subset of reads has poor quality.
From the FastQC help:
The per sequence quality score report allows you to see if a subset of your sequences have universally low quality values. It is often the case that a subset of sequences will have universally poor quality, however these should represent only a small percentage of the total sequences.
Per Base Sequence Content
The proportion of each base position for which each of the four normal DNA bases has been called.
To enable multiple samples to be shown in a single plot, the base composition data is shown as a heatmap. The colours represent the balance between the four bases: an even distribution should give an even muddy brown colour. Hover over the plot to see the percentage of the four bases under the cursor.
To see the data as a line plot, as in the original FastQC graph, click on a sample track.
From the FastQC help:
Per Base Sequence Content plots out the proportion of each base position in a file for which each of the four normal DNA bases has been called.
In a random library you would expect that there would be little to no difference between the different bases of a sequence run, so the lines in this plot should run parallel with each other. The relative amount of each base should reflect the overall amount of these bases in your genome, but in any case they should not be hugely imbalanced from each other.
It's worth noting that some types of library will always produce biased sequence composition, normally at the start of the read. Libraries produced by priming using random hexamers (including nearly all RNA-Seq libraries) and those which were fragmented using transposases inherit an intrinsic bias in the positions at which reads start. This bias does not concern an absolute sequence, but instead provides enrichement of a number of different K-mers at the 5' end of the reads. Whilst this is a true technical bias, it isn't something which can be corrected by trimming and in most cases doesn't seem to adversely affect the downstream analysis.
Rollover for sample name
Per Sequence GC Content
The average GC content of reads. Normal random library typically have a roughly normal distribution of GC content.
From the FastQC help:
This module measures the GC content across the whole length of each sequence in a file and compares it to a modelled normal distribution of GC content.
In a normal random library you would expect to see a roughly normal distribution of GC content where the central peak corresponds to the overall GC content of the underlying genome. Since we don't know the the GC content of the genome the modal GC content is calculated from the observed data and used to build a reference distribution.
An unusually shaped distribution could indicate a contaminated library or some other kinds of biased subset. A normal distribution which is shifted indicates some systematic bias which is independent of base position. If there is a systematic bias which creates a shifted normal distribution then this won't be flagged as an error by the module since it doesn't know what your genome's GC content should be.
Per Base N Content
The percentage of base calls at each position for which an N was called.
From the FastQC help:
If a sequencer is unable to make a base call with sufficient confidence then it will
normally substitute an N rather than a conventional base call. This graph shows the
percentage of base calls at each position for which an N was called.
It's not unusual to see a very low proportion of Ns appearing in a sequence, especially nearer the end of a sequence. However, if this proportion rises above a few percent it suggests that the analysis pipeline was unable to interpret the data well enough to make valid base calls.
Sequence Length Distribution
The distribution of fragment sizes (read lengths) found. See the FastQC help
Sequence Duplication Levels
The relative level of duplication found for every sequence.
From the FastQC Help:
In a diverse library most sequences will occur only once in the final set. A low level of duplication may indicate a very high level of coverage of the target sequence, but a high level of duplication is more likely to indicate some kind of enrichment bias (eg PCR over amplification). This graph shows the degree of duplication for every sequence in a library: the relative number of sequences with different degrees of duplication.
Only sequences which first appear in the first 100,000 sequences in each file are analysed. This should be enough to get a good impression for the duplication levels in the whole file. Each sequence is tracked to the end of the file to give a representative count of the overall duplication level.
The duplication detection requires an exact sequence match over the whole length of the sequence. Any reads over 75bp in length are truncated to 50bp for this analysis.
In a properly diverse library most sequences should fall into the far left of the plot in both the red and blue lines. A general level of enrichment, indicating broad oversequencing in the library will tend to flatten the lines, lowering the low end and generally raising other categories. More specific enrichments of subsets, or the presence of low complexity contaminants will tend to produce spikes towards the right of the plot.
Overrepresented sequences
The total amount of overrepresented sequences found in each library.
FastQC calculates and lists overrepresented sequences in FastQ files. It would not be possible to show this for all samples in a MultiQC report, so instead this plot shows the number of sequences categorized as over represented.
Sometimes, a single sequence may account for a large number of reads in a dataset. To show this, the bars are split into two: the first shows the overrepresented reads that come from the single most common sequence. The second shows the total count from all remaining overrepresented sequences.
From the FastQC Help:
A normal high-throughput library will contain a diverse set of sequences, with no individual sequence making up a tiny fraction of the whole. Finding that a single sequence is very overrepresented in the set either means that it is highly biologically significant, or indicates that the library is contaminated, or not as diverse as you expected.
FastQC lists all of the sequences which make up more than 0.1% of the total. To conserve memory only sequences which appear in the first 100,000 sequences are tracked to the end of the file. It is therefore possible that a sequence which is overrepresented but doesn't appear at the start of the file for some reason could be missed by this module.
Adapter Content
The cumulative percentage count of the proportion of your library which has seen each of the adapter sequences at each position.
Note that only samples with ≥ 0.1% adapter contamination are shown.
There may be several lines per sample, as one is shown for each adapter detected in the file.
From the FastQC Help:
The plot shows a cumulative percentage count of the proportion of your library which has seen each of the adapter sequences at each position. Once a sequence has been seen in a read it is counted as being present right through to the end of the read so the percentages you see will only increase as the read length goes on.
Status Checks
Status for each FastQC section showing whether results seem entirely normal (green), slightly abnormal (orange) or very unusual (red).
FastQC assigns a status for each section of the report. These give a quick evaluation of whether the results of the analysis seem entirely normal (green), slightly abnormal (orange) or very unusual (red).
It is important to stress that although the analysis results appear to give a pass/fail result, these evaluations must be taken in the context of what you expect from your library. A 'normal' sample as far as FastQC is concerned is random and diverse. Some experiments may be expected to produce libraries which are biased in particular ways. You should treat the summary evaluations therefore as pointers to where you should concentrate your attention and understand why your library may not look random and diverse.
Specific guidance on how to interpret the output of each module can be found in the relevant report section, or in the FastQC help.
In this heatmap, we summarise all of these into a single heatmap for a quick overview. Note that not all FastQC sections have plots in MultiQC reports, but all status checks are shown in this heatmap.
Cutadapt
Cutadapt is a tool to find and remove adapter sequences, primers, poly-Atails and other types of unwanted sequence from your high-throughput sequencing reads.
Filtered Reads
This plot shows the number of reads (SE) / pairs (PE) removed by Cutadapt.
Trimmed Sequence Lengths (3')
This plot shows the number of reads with certain lengths of adapter trimmed for the 3' end.
Obs/Exp shows the raw counts divided by the number expected due to sequencing errors. A defined peak may be related to adapter length.
See the cutadapt documentation for more information on how these numbers are generated.
FastQC (trimmed)
FastQC (trimmed) This section of the report shows FastQC results after adapter trimming.
Sequence Counts
Sequence counts for each sample. Duplicate read counts are an estimate only.
This plot show the total number of reads, broken down into unique and duplicate if possible (only more recent versions of FastQC give duplicate info).
You can read more about duplicate calculation in the FastQC documentation. A small part has been copied here for convenience:
Only sequences which first appear in the first 100,000 sequences in each file are analysed. This should be enough to get a good impression for the duplication levels in the whole file. Each sequence is tracked to the end of the file to give a representative count of the overall duplication level.
The duplication detection requires an exact sequence match over the whole length of the sequence. Any reads over 75bp in length are truncated to 50bp for this analysis.
Sequence Quality Histograms
The mean quality value across each base position in the read.
To enable multiple samples to be plotted on the same graph, only the mean quality scores are plotted (unlike the box plots seen in FastQC reports).
Taken from the FastQC help:
The y-axis on the graph shows the quality scores. The higher the score, the better the base call. The background of the graph divides the y axis into very good quality calls (green), calls of reasonable quality (orange), and calls of poor quality (red). The quality of calls on most platforms will degrade as the run progresses, so it is common to see base calls falling into the orange area towards the end of a read.
Per Sequence Quality Scores
The number of reads with average quality scores. Shows if a subset of reads has poor quality.
From the FastQC help:
The per sequence quality score report allows you to see if a subset of your sequences have universally low quality values. It is often the case that a subset of sequences will have universally poor quality, however these should represent only a small percentage of the total sequences.
Per Base Sequence Content
The proportion of each base position for which each of the four normal DNA bases has been called.
To enable multiple samples to be shown in a single plot, the base composition data is shown as a heatmap. The colours represent the balance between the four bases: an even distribution should give an even muddy brown colour. Hover over the plot to see the percentage of the four bases under the cursor.
To see the data as a line plot, as in the original FastQC graph, click on a sample track.
From the FastQC help:
Per Base Sequence Content plots out the proportion of each base position in a file for which each of the four normal DNA bases has been called.
In a random library you would expect that there would be little to no difference between the different bases of a sequence run, so the lines in this plot should run parallel with each other. The relative amount of each base should reflect the overall amount of these bases in your genome, but in any case they should not be hugely imbalanced from each other.
It's worth noting that some types of library will always produce biased sequence composition, normally at the start of the read. Libraries produced by priming using random hexamers (including nearly all RNA-Seq libraries) and those which were fragmented using transposases inherit an intrinsic bias in the positions at which reads start. This bias does not concern an absolute sequence, but instead provides enrichement of a number of different K-mers at the 5' end of the reads. Whilst this is a true technical bias, it isn't something which can be corrected by trimming and in most cases doesn't seem to adversely affect the downstream analysis.
Rollover for sample name
Per Sequence GC Content
The average GC content of reads. Normal random library typically have a roughly normal distribution of GC content.
From the FastQC help:
This module measures the GC content across the whole length of each sequence in a file and compares it to a modelled normal distribution of GC content.
In a normal random library you would expect to see a roughly normal distribution of GC content where the central peak corresponds to the overall GC content of the underlying genome. Since we don't know the the GC content of the genome the modal GC content is calculated from the observed data and used to build a reference distribution.
An unusually shaped distribution could indicate a contaminated library or some other kinds of biased subset. A normal distribution which is shifted indicates some systematic bias which is independent of base position. If there is a systematic bias which creates a shifted normal distribution then this won't be flagged as an error by the module since it doesn't know what your genome's GC content should be.
Per Base N Content
The percentage of base calls at each position for which an N was called.
From the FastQC help:
If a sequencer is unable to make a base call with sufficient confidence then it will
normally substitute an N rather than a conventional base call. This graph shows the
percentage of base calls at each position for which an N was called.
It's not unusual to see a very low proportion of Ns appearing in a sequence, especially nearer the end of a sequence. However, if this proportion rises above a few percent it suggests that the analysis pipeline was unable to interpret the data well enough to make valid base calls.
Sequence Length Distribution
The distribution of fragment sizes (read lengths) found. See the FastQC help
Sequence Duplication Levels
The relative level of duplication found for every sequence.
From the FastQC Help:
In a diverse library most sequences will occur only once in the final set. A low level of duplication may indicate a very high level of coverage of the target sequence, but a high level of duplication is more likely to indicate some kind of enrichment bias (eg PCR over amplification). This graph shows the degree of duplication for every sequence in a library: the relative number of sequences with different degrees of duplication.
Only sequences which first appear in the first 100,000 sequences in each file are analysed. This should be enough to get a good impression for the duplication levels in the whole file. Each sequence is tracked to the end of the file to give a representative count of the overall duplication level.
The duplication detection requires an exact sequence match over the whole length of the sequence. Any reads over 75bp in length are truncated to 50bp for this analysis.
In a properly diverse library most sequences should fall into the far left of the plot in both the red and blue lines. A general level of enrichment, indicating broad oversequencing in the library will tend to flatten the lines, lowering the low end and generally raising other categories. More specific enrichments of subsets, or the presence of low complexity contaminants will tend to produce spikes towards the right of the plot.
Overrepresented sequences
The total amount of overrepresented sequences found in each library.
FastQC calculates and lists overrepresented sequences in FastQ files. It would not be possible to show this for all samples in a MultiQC report, so instead this plot shows the number of sequences categorized as over represented.
Sometimes, a single sequence may account for a large number of reads in a dataset. To show this, the bars are split into two: the first shows the overrepresented reads that come from the single most common sequence. The second shows the total count from all remaining overrepresented sequences.
From the FastQC Help:
A normal high-throughput library will contain a diverse set of sequences, with no individual sequence making up a tiny fraction of the whole. Finding that a single sequence is very overrepresented in the set either means that it is highly biologically significant, or indicates that the library is contaminated, or not as diverse as you expected.
FastQC lists all of the sequences which make up more than 0.1% of the total. To conserve memory only sequences which appear in the first 100,000 sequences are tracked to the end of the file. It is therefore possible that a sequence which is overrepresented but doesn't appear at the start of the file for some reason could be missed by this module.
Adapter Content
The cumulative percentage count of the proportion of your library which has seen each of the adapter sequences at each position.
Note that only samples with ≥ 0.1% adapter contamination are shown.
There may be several lines per sample, as one is shown for each adapter detected in the file.
From the FastQC Help:
The plot shows a cumulative percentage count of the proportion of your library which has seen each of the adapter sequences at each position. Once a sequence has been seen in a read it is counted as being present right through to the end of the read so the percentages you see will only increase as the read length goes on.
Status Checks
Status for each FastQC section showing whether results seem entirely normal (green), slightly abnormal (orange) or very unusual (red).
FastQC assigns a status for each section of the report. These give a quick evaluation of whether the results of the analysis seem entirely normal (green), slightly abnormal (orange) or very unusual (red).
It is important to stress that although the analysis results appear to give a pass/fail result, these evaluations must be taken in the context of what you expect from your library. A 'normal' sample as far as FastQC is concerned is random and diverse. Some experiments may be expected to produce libraries which are biased in particular ways. You should treat the summary evaluations therefore as pointers to where you should concentrate your attention and understand why your library may not look random and diverse.
Specific guidance on how to interpret the output of each module can be found in the relevant report section, or in the FastQC help.
In this heatmap, we summarise all of these into a single heatmap for a quick overview. Note that not all FastQC sections have plots in MultiQC reports, but all status checks are shown in this heatmap.
nf-core/rnaseq Software Versions
are collected at run time from the software output.
| Process Name | Software | Version |
|---|---|---|
| BEDTOOLS_GENOMECOV | bedtools | 2.30.0 |
| CAT_FASTQ | cat | 8.30 |
| CUSTOM_DUMPSOFTWAREVERSIONS | python | 3.9.5 |
| yaml | 5.4.1 | |
| CUSTOM_GETCHROMSIZES | custom | 1.14 |
| DESEQ2_QC_SALMON | bioconductor-deseq2 | 1.28.0 |
| r-base | 4.0.3 | |
| DESEQ2_QC_STAR_SALMON | bioconductor-deseq2 | 1.28.0 |
| r-base | 4.0.3 | |
| DUPRADAR | bioconductor-dupradar | 1.18.0 |
| r-base | 4.0.2 | |
| FASTQC | fastqc | 0.11.9 |
| GFFREAD | gffread | 0.12.1 |
| GTF2BED | perl | 5.26.2 |
| GTF_GENE_FILTER | python | 3.9.5 |
| MAKE_TRANSCRIPTS_FASTA | rsem | 1.3.1 |
| star | 2.7.6a | |
| MULTIQC_CUSTOM_BIOTYPE | python | 3.9.5 |
| PICARD_MARKDUPLICATES | picard | 2.26.10 |
| PRESEQ_LCEXTRAP | preseq | 3.1.1 |
| QUALIMAP_RNASEQ | qualimap | 2.2.2-dev |
| RSEQC_BAMSTAT | rseqc | 3.0.1 |
| RSEQC_INFEREXPERIMENT | rseqc | 3.0.1 |
| RSEQC_INNERDISTANCE | rseqc | 3.0.1 |
| RSEQC_JUNCTIONANNOTATION | rseqc | 3.0.1 |
| RSEQC_JUNCTIONSATURATION | rseqc | 3.0.1 |
| RSEQC_READDISTRIBUTION | rseqc | 3.0.1 |
| RSEQC_READDUPLICATION | rseqc | 3.0.1 |
| SALMON_INDEX | salmon | 1.5.2 |
| SALMON_QUANT | salmon | 1.5.2 |
| SALMON_SE_GENE | bioconductor-summarizedexperiment | 1.20.0 |
| r-base | 4.0.3 | |
| SALMON_TX2GENE | python | 3.9.5 |
| SALMON_TXIMPORT | bioconductor-tximeta | 1.8.0 |
| r-base | 4.0.3 | |
| SAMPLESHEET_CHECK | python | 3.9.5 |
| SAMTOOLS_FLAGSTAT | samtools | 1.14 |
| SAMTOOLS_IDXSTATS | samtools | 1.14 |
| SAMTOOLS_INDEX | samtools | 1.14 |
| SAMTOOLS_SORT | samtools | 1.14 |
| SAMTOOLS_STATS | samtools | 1.14 |
| STAR_ALIGN | star | 2.6.1d |
| STAR_GENOMEGENERATE | star | 2.6.1d |
| STRINGTIE | stringtie | 2.1.7 |
| SUBREAD_FEATURECOUNTS | subread | 2.0.1 |
| TRIMGALORE | cutadapt | 3.4 |
| trimgalore | 0.6.7 | |
| UCSC_BEDCLIP | ucsc | 377 |
| UCSC_BEDGRAPHTOBIGWIG | ucsc | 377 |
| Workflow | Nextflow | 21.10.6 |
| nf-core/rnaseq | 3.6 |
nf-core/rnaseq Workflow Summary
- this information is collected when the pipeline is started.
Core Nextflow options
- runName
- voluminous_visvesvaraya
- containerEngine
- singularity
- launchDir
- /gscratch/scrubbed/samwhite/outputs/20220323-pgen-nextflow_rnaseq-tissues
- workDir
- /gscratch/scrubbed/samwhite/outputs/20220323-pgen-nextflow_rnaseq-tissues/work
- projectDir
- /gscratch/srlab/programs/nf-core-rnaseq-3.6/workflow
- userName
- samwhite
- profile
- singularity
- configFiles
- /gscratch/srlab/programs/nf-core-rnaseq-3.6/workflow/nextflow.config, /gscratch/srlab/programs/nf-core-rnaseq-3.6/configs/conf/base-srlab_500GB_node.config
Input/output options
- input
- sample_sheet-2666621.csv
- outdir
- /gscratch/scrubbed/samwhite/outputs/20220323-pgen-nextflow_rnaseq-tissues
- multiqc_title
- 20220321-pgen-nextflow_rnaseq-tissues-2666621
Reference genome options
- fasta
- /gscratch/srlab/sam/data/P_generosa/genomes/Panopea-generosa-v1.0.fa
- gff
- /gscratch/srlab/sam/data/P_generosa/genomes/Panopea-generosa-v1.0.a4_biotype-trna_strand_converted-no_RNAmmer.gff
- save_reference
- true
Read trimming options
- trim_nextseq
- 20
- save_trimmed
- true
Alignment options
- pseudo_aligner
- salmon
- save_align_intermeds
- true
Institutional config options
- custom_config_base
- /gscratch/srlab/programs/nf-core-rnaseq-3.6/workflow/../configs/
