This document describes the output produced by the pipeline. Most of the plots are taken from the MultiQC report, which summarises results at the end of the pipeline.

The directories listed below will be created in the results directory after the pipeline has finished. All paths are relative to the top-level results directory.

Pipeline overview

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

  • Quality Control - compute QC metrics for NanoString data, assess data quality
  • Normalize - compute normalized gene counts for given RCC files
  • Annotate - annotate the normalized gene counts with metadata from samplesheet
  • MultiQC - aggregate report, describing results of the whole pipeline
  • Pipeline information - Report metrics generated during the workflow execution

Quality Control

This step currently uses the NACHO NanoString analysis package to perform basic QC of the input RCC files. Several quality metrics are created and the majority of these are available in the MultiQC report. These have been created using the bin/nacho_qc.R script in the pipeline. In addition to this, the output also has two NACHO reports, once with outliers highlighted and once without highlighting outliers in the visualizations:

Output files
    • png/: Directory containing the generated qc plots for the MultiQC report.
    • hk_detected_mqc.txt: Text file containing the housekeeping genes that have been detected in the data.
    • NanoQC.html: Basic Nacho QC report - a standalone HTML file that can be viewed in your web browser.
    • NanoQC_with_outliers.html: The same as above, but with highlighted outliers.
    • normalized_qc_mqc.txt: QC metrics from NACHO. This is also shown in table format in a MultiQC table.


This holds the normalized gene expression data, normalized using NACHO (bin/nacho_norm.R).

Output files
  • normalized_counts/
    • *_normalized_counts.tsv: Normalized count matrix, unmodified.
    • *_normalized_counts_wo_HKnorm.tsv: Normalized count matrix without Housekeeping-normalization applied (housekeeping_norm=FALSE), unmodified.


Output files

This holds the normalized and non-housekeeping-normalized annotated gene expression data. There are two tables each - one for endogenous genes of interest, one for housekeeping genes. Annotation is performed using the custom script bin/write_out_prepared_gex.R in the pipeline. These tables are also part of the MultiQC report.

  • annotated_tables/
  • *_normalized_counts_Norm_GEX_HK.tsv: TSV table holding all normalized housekeeping gene expression values with annotation.
  • *_normalized_counts_Norm_GEX_ENDO.tsv: TSV table holding the normalized endogenous gene expression values with annotation.
  • *_normalized_counts_wo_HKnorm_Norm_GEX_HK.tsv: TSV table holding the non-HK-normalized endogenous gene expression values with annotation.
  • *_normalized_counts_wo_HKnorm_Norm_GEX_ENDO.tsv: TSV table holding the non-HK-normalized endogenous gene expression values with annotation.


Output files
  • multiqc/
    • multiqc_report.html: a standalone HTML file that can be viewed in your web browser.
    • multiqc_data/: directory containing parsed statistics from the different tools used in the pipeline.
    • multiqc_plots/: directory containing static images from the report in various formats.

MultiQC is a visualization tool that generates a single HTML report summarising all samples in your project. Most of the pipeline QC results are visualised in the report and further statistics are available in the report data directory.

Results generated by MultiQC collate pipeline QC from supported tools e.g. FastQC. The pipeline has special steps which also allow the software versions to be reported in the MultiQC output for future traceability. For more information about how to use MultiQC reports, see

Pipeline information

Output files
  • pipeline_info/
    • Reports generated by Nextflow: execution_report.html, execution_timeline.html, execution_trace.txt and
    • Reports generated by the pipeline: pipeline_report.html, pipeline_report.txt and software_versions.yml. The pipeline_report* files will only be present if the --email / --email_on_fail parameter’s are used when running the pipeline.
    • Reformatted samplesheet files used as input to the pipeline: samplesheet.valid.csv.

Nextflow provides excellent functionality for generating various reports relevant to the running and execution of the pipeline. This will allow you to troubleshoot errors with the running of the pipeline, and also provide you with other information such as launch commands, run times and resource usage.