Overview

A sample sheet is required for each analysis with DRAGEN TruSight Oncology 500 Analysis Software. A sample sheet is a comma-separated value (*.csv) file format used by Illumina instruments, platforms, and analysis pipelines to store settings and data for sequencing and analysis. The DRAGEN TruSight Oncology 500 Analysis Software is compatible with the sample sheet v2. For general information on the sample sheet v2, refer to Illumina Connected Software - Sample Sheet.

The sample sheet includes a list of samples and their index sequences, along with additional information required to run DRAGEN TruSight Oncology 500 Analysis Software. For example, DNA samples with the TruSight Oncology 500 HRD add-on probes must be indicated in the Sample Feature column of the sample sheet. Appropriate index adapter sequences are determined by the assay used to perform analysis.

When running analysis on a standalone DRAGEN server or on ICA, a valid sample sheet can be created by:

• BaseSpace Run Planner (preferred), see Sample Sheet Creation in BaseSpace Run Planner page for details

• Downloading and modifying a sample sheet template following the requirements, see Sample Sheet Requirements page for details

When running analysis using a NovaSeq 6000Dx Analysis Application, a valid sample sheet can be created by:

• Using the user interface of the DRAGEN TruSight Oncology 500 Analysis Application, see Run Planning on Illumina Run Manager for details

• Downloading and modifying a sample sheet template following the requirements (see Sample Sheet Requirements page for details), then importing it to Illumina Run Manager.

The run set up section of this guide includes specific instructions to plan a run and set up a valid sample sheet for each deployment of DRAGEN TruSight Oncology 500 Analysis Software.

Prerequisites

Illumina Connected Analytics (ICA) subscription includes access to DRAGEN TruSight Oncology 500 Analysis Software. To get started, you need:

• An ICA account with a valid subscription

• A positive balance of iCredits for data storage

Refer to the for information on how to register ICA subscription and iCredits.

Start the DRAGEN TruSight Oncology 500 Analysis Software with the DRAGEN_TSO500-2.6.0.sh Bash script. The script is installed in the /usr/local/bin directory. The Bash script is executed on the command line and runs the software with Docker (or Apptainer if specified).

For arguments, refer to Command-Line Options. You can start from BCL files or from the FASTQ folder produced by BCL Convert. The following requirements apply for both methods:

• Path to the sequencing run or FASTQ folder. Copy the run or FASTQ folder to the DRAGEN server into the staging folder with the following recommended organization: /staging/runs/{RunID}. You can copy the run folder onto the DRAGEN server using Linux commands such as rsync. The sample sheet within the run folder is used unless otherwise specified through the command line.

• Run folder must be intact. Refer to Starting from BCL Files for input requirements.

• If the analysis output folder path is different from the default, provide the analysis output folder path. Refer to Command-Line Options.

Storage Requirements

For optimal performance, run analysis on data stored locally on the DRAGEN server. Analysis of data stored on NAS can take longer and performance can be less reliable.

The DRAGEN server provides an NVMe SSD in the /staging directory to use as the software output directory. Network-attached storage is required for long-term storage.

When running the DRAGEN TruSight Oncology 500 Analysis Software, use the default settings or set the -analysisFolder command line option to a directory in /staging to make sure the DRAGEN server processes read and write data on the NVMe SSD.

Before beginning analysis, develop a strategy to copy data from the DRAGEN server to a network‑attached storage. Delete output data on the DRAGEN server as soon as possible.

The following are the run and analysis output sizes for each sequencing system per 101 bp:

When launching the analysis, the software checks that the minimum disk space required is available. If the minimum disk space is not available, the software shows an error message and prevents analysis from starting. If disk space is exhausted during a run, the run shows an error and stops analyzing.

DNA expanded metrics are provided for information only. They can be informative for troubleshooting but are provided without explicit specification limits and are not directly used for sample quality control. For additional guidance, contact Illumina Technical Support.

Prerequisites

• A NovaSeq 6000Dx sequencing instrument with paired DRAGEN server v4.

• Illumina Run Manager installed by Illumina support personnel.

• HRD license installed on the DRAGEN server v4 (not required for customers in Japan)

• The user installing the app must have admin privileges on Illumina Run Manager.

Installation Instructions:

1. Contact Illumina Customer Care at customercare@illumina.com to obtain installation package for Illumina DRAGEN TruSight Oncology 500 (HRD) Analysis Application on NovaSeq 6000Dx

   1. If you are a customer in Japan, request Illumina DRAGEN TruSight Oncology 500 Analysis Application on NovaSeq 6000Dx

2. Download the installation package provided in the email by Illumina Customer Care. The link will expire after 7 days.

1. The installation package contains the following:

   1. DRAGEN TSO 500 Analysis Application: DRAGEN_TSO500HRD_v2.6.0-2v12.iapp

      1. If you are a customer in Japan, you will be provided DRAGEN_TSO500S_v2.6.0-2v12.iapp

   2. DRAGEN ires: drageninstaller_3.10.17-8.el8.x86_64_prod.ires

1. Install the DRAGEN version using the ires:

   1. Log into Illumina Run Manager as a user with admin credentials

   2. Navigate to the top left menu to "DRAGEN" in the drop down

   3. Select "Add DRAGEN Installer" and upload the DRAGEN ires file

   4. The installation is complete once the DRAGEN version 3.10.17 is in the install version(s) list.

\

Methods for Launching Analysis

Illumina Connected Analytics (ICA) supports the following methods for launching DRAGEN TruSight Oncology 500 Analysis Software.

• Auto-launch—Stream run data directly from the instrument to ICA via a specially configured sample sheet and automatically begin DRAGEN TSO 500 analysis.

• Manual launch—Initiate DRAGEN TSO 500 analysis on ICA using the run files and sample sheet files in the project.

For more information about using ICA or BaseSpace Sequence Hub, refer to the following support pages on the Illumina support site.

• Illumina Connected Analytics support site page

• BaseSpace Sequence Hub support site page

Use the following steps to configure a TruSight™ Oncology 500 run in Illumina Run Manager.

1. Go to the "Runs" section of Illumina Run Manager by selecting "Runs" on the left-hand side.

2. Enter sample data manually or by importing a sample sheet

3. To enter sample data run manually, select “Create Run”.

4. Choose "DRAGEN TruSight™ Oncology 500 (with HRD) Analysis Application" from the "Create Run" screen to set-up and analyze runs for TruSight Oncology 500 assay with or without HRD add-on.

   • If you are a customer in Japan, choose "DRAGEN TruSight™ Oncology 500 Analysis Application"

Run Settings

1. On the "Run Settings" screen, enter a run name with the following criteria:

   1. 1 - 40 characters.

   2. Alphanumeric characters, underscores, or dashes only.

   3. Unique across all runs on the instrument.

   The run name identifies the run from sequencing through analysis.

2. [Optional] Enter a run description. The run description must have the following criteria:

   1. 1 - 50 characters.

   2. Alphanumeric characters or spaces only.

   3. Spaces must be preceded and followed by an alphanumeric character.

3. Select kit used during library preparation:

   1. TruSight Oncology 500

   2. TruSight Oncology 500 High-Throughput

4. Index adapter kit will be automatically selected based on the library prep kit selection

5. [Optional] Enter a library tube ID.

Depending on the library prep kit selected, additional fields will be populated for run settings and are not editable. Read and index lengths will differ between library prep kit type.

Sample Data

Use the table on the "Sample Data" screen to enter sample information manually.

Alternately, select Import Samples to upload sample information. Refer to NovaSeq 6000Dx Analysis Application: Sample Sheet Requirements for sample sheet requirements.

1. Select lane information. Options include one to four, or all lanes.

2. Enter a unique sample ID in the sample ID field with the following criteria:

   1. Controls should be added first.

   2. 1 - 40 characters.

   3. Alphanumeric characters, underscores, or dashes only.

   4. Underscores and dashes must be preceded and followed by an alphanumeric character.

3. Select an index set ID for the DNA / RNA library prepared from the sample.

4. [Optional] Enter a library name.

Depending on the options selected for index set ID, additional fields will be auto-populated for sample data and are not editable.

Sample Settings

Use the table on the "Sample Settings" screen to enter additional sample information.

1. Enter Pair ID with the following criteria:

   1. 1 - 40 characters.

   2. Alphanumeric characters, underscores, or dashes only.

   3. Underscores and dashes must be preceded and followed by an alphanumeric character.

   4. Pairs at most one DNA and one RNA samples from the same biological sample from the same individual.

2. Select Sample Type: DNA or RNA

3. Enter Sample Feature: Select HRD for DNA samples with HRD probes. For all other samples, leave the field blank.

   1. Note: This only applies to DRAGEN TruSight™ Oncology 500 (with HRD) analysis application

4. [Optional] Enter a sample name with the following criteria:

   1. 1 - 50 characters.

   2. Alphanumeric characters, dashes, underscores, or spaces.

   3. Spaces, underscores, and dashes must be preceded and followed by an alphanumeric character.

5. [Optional] Enter a sample description with the following criteria:

   1. 1 - 50 characters.

   2. Alphanumeric characters, dashes, underscores, or spaces.

   3. Spaces, underscores, and dashes must be preceded and followed by an alphanumeric character.

Additional fields will be auto-populated based on selections made in the Sample Data screen, which are not editable.

Before starting your run, review that the information entered is correct in the “Run Review” page before saving.

When the analysis run completes, the DRAGEN TruSight Oncology 500 Analysis Software generates an analysis output folder in a specified location.

To view analysis output, navigate to the analysis output folder and select the files that you want to view.

Single Node Analysis Output Folder Structure

Single output folder structure is as follows.

• Logs_Intermediates

  • AdditionalSarjMetrics— Contains per pair ID calculations to support the PCT_TARGET_250X metric.

  • Annotation—Contains outputs for small variant annotation.

    • Subfolders per sample ID—Contains the aligned small variants JSON.

  • CombinedVariantOutput

    • Subfolders per pair ID—Contains the combined variant output TSV files.

    • A combined output log file.

  • Contamination

    • Subfolders per DNA sample ID—Contains the contamination metrics JSON file and output logs.

  • DnaDragenCaller

    • Subfolders per sample ID—Contains the aligned BAM and index files, small variant VCF and gVCF, copy number variant VCF, MSI JSON, exon coverage report bed, and QC outputs in CSV format.

  • DnaDragenExonCNVCaller

    • Subfolders per DNA sample ID—Contains the exon-level CNV JSON,the supporting calculation, and the QC files.

  • DnaFastqValidation—Contains the FASTQ validation output log for DNA samples.

  • FastqDownsample

    • Subfolders per RNA sample ID—Contains FASTQ files and output logs.

    • FastqDownsample output

  • FastqGeneration

  • Gis—Contains GIS-related files for HRD samples.

    • Subfolders per HRD sample ID—Contains the GIS JSON, the supporting calculation, and the QC files.

    • Also contains the annotated CNV VCF and gene level TSV file with absolute copy number and minor copy number information

  • LrAnnotation

    • Subfolders per DNA sample ID—Contains the annotated exon-level CNV JSON.

  • LrCalculator

    • Subfolders per DNA sample ID—Contains the exon-level CNV VCF.

  • MetricsOutput

    • Subfolders per pair ID—Contains the metrics output TSV files.

    • A combined output log file.

  • ResourceVerification—Contains the resource file checksum verification logs.

  • RnaAnnotation

    • Subfolders per RNA sample ID—Contains the annotated splice variant JSON.

  • RnaDragenCaller

    • Subfolders per sample ID—Contains the aligned BAM, fusion candidates CSV, exon coverage report bed and QC outputs in CSV format.

  • RnaFastqValidation—Contains the FASTQ validation output log for RNA samples.

  • RnaFusion

    • Subfolders per RNA sample ID—Contains the All Fusions CSV and Fusion Processor logs.

  • RnaQcMetrics

    • Subfolders per RNA sample ID—Contains the RNA QC metrics JSON.

  • RnaSpliceVariantCalling

    • Subfolders per RNA sample ID—Contains the splice variants VCF.

  • Run QC—Contains the Run QC metrics JSON, Intermediate Run QC metrics JSON, and log file.

  • SampleAnalysisResults

    • Subfolders per pair ID—Contains the Sample Analysis Results JSON and detailed log file.

    • SampleSheetValidation—Contains the Intermediate sample sheet and validation log.

  • Tmb

    • Subfolders per DNA sample ID—Contains the TMB metrics CSV, TMB trace TSV, and related files and logs. passing_sample_steps.json —Contains the steps passed for each sample ID. pipeline_trace.txt—Contains a summary and troubleshooting file that lists each Nextflow task executed and the status (for example, COMPLETED or FAILED). run.log—Contains a complete trace-level log file describing the Nextflow pipeline execution. run_report.html—Contains high-level run statistics (performance, usage, etc.) run_timeline.html —Contains timeline-related information about the analysis run.

• Results

  • Metrics Output TSV (all pair IDs)

  • Pair ID—The following outputs are produced for each sample:

    • Combined Variant Output TSV

      • Metrics Output TSV

      • TMB Trace TSV

      • Small Variant Genome VCF

      • Small Variant Genome Annotated JSON

      • Copy Number Variant VCF

      • GIS JSON

      • MSI JSON

      • Large Rearrangements CNV VCF

      • Large Rearrangements CNV Annotated JSON

      • All Fusion CSV

      • Splice Variant VCF

      • Splice Variant Annotated JSON

      • Exon Coverage Report TSV

      • Gene Coverage Report TSV

Multiple Node Analysis Output Folder Structure

Multiple output folder structure is as follows.

• Demultiplex Output

  • A Logs_Intermediates folder containing FASTQ files per sample.

• Node(X) Output—The following outputs are produced for each node used:

  • A Logs_Intermediates folder containing step specific and component specific outputs and logs for every step/component run in the analysis pipeline for the sample run on the node.

  • A Results folder containing results only for the sample run on the node.

• Gathered Output

  • A Logs_Intermediates folder containing step specific and component specific outputs and logs for every step/component run in each analysis pipeline on every node—this contains outputs for all samples and pairs ran across all nodes in the analysis.

  • A Results folder containing results for all samples and pairs ran across all nodes—results are organized by Pair_ID, then Sample_ID. This folder also contains summary files which contain information on all samples.

ICA Output Folder Structure

This section describes each output folder generated during analysis and where to find metric and analytic files when the pipeline is executed. The same output folder structure and content exist in ICA and BaseSpace Sequence Hub.

High-Level Folder Structure

• Run ID

  • TSO500_Nextflow_logs

    • _manifest.json

  • Results

    • _tags.json

  • Logs_intermediates

  • Errors—This folder is only present when analysis fails

TSO500_Nextflow_logs Folder Structure

The TSO_500_Nextflow_Logs provides information related to the execution of the pipeline on ICA as a whole and for specific nodes (when an analysis is split across multiple nodes). It contains files used to execute parts of the workflow on different nodes as well as records of the nextflow execution on those nodes.

• TSO_500_Nextflow_Logs

  • _manifest.json

Results Folder Structure

Contains the aggregated MetricsOutput.tsv file at the root level. Additionally, the Results folder contains a subfolder for each pair ID.

• Results

  • MetricsOutput.tsv

  • Sample_1

  • Sample_2

  • Sample_<#>

  • _tags.json

The Results subfolder contains the following files:

• Results

  • MetricsOutput.tsv

  • <Pair_id>

    • CombinedVariantOutput.tsv

    • <SampleName>_MetricsOutput.tsv

  • <DNA_Sample_id>

    • CopyNumberVariants.vcf

    • DNAMergedSmallVariants_Annotated.json.gz

    • MergedSmallVariants.genome.vcf

    • MergedSmallVariants.vcf

    • microstat_output.json

    • TMB_Trace.tsv

  • <RNA_Sample_id>

    • AllFusions.csv

    • RNA_Annotated.json.gz

    • SpliceVariants.vcf

Logs_intermediates Folder Structure

Contains folders for each submodule in the DRAGEN TSO 500 on ICA pipeline. The folders contain a copy of all the relevant files required to create the metric output files and report files, as well as the combined log files at the root level and subfolders for each sample.

• Logs_intermediates

  • DnaDragenCaller

  • AdditionalSarjMetrics

  • CombinedVariantOutput

  • FastqGeneration

  • MetricsOutput

  • DnaDragenExonCnvCaller

  • DnaFastqValidation

  • DNACoverageReport

  • Gis

  • Tmb

  • SampleAnalysisResults

  • SampleSheetValidation

  • passing_sample_steps.json

  • RnaFusion

  • Contamination

  • Annotation

  • RnaAnnotation

  • RnaDragenCaller

  • RnaSpliceVariantCalling

  • RunQc

  • FastqDownsample

  • PassingSampleSteps

  • ResourceVerification

  • LrCalculator

  • LrAnnotation

  • RnaQcMetrics

  • RnaFastqValidation

  • RNACoverageReport

Errors Folder Structure

Contains Errors.tsv. This file contains the summary of all the errors encountered during pipeline execution.

• Errors

  • Errors.tsv

NovaSeq 6000Dx Analysis Application Output Folder Structure

The following files and folders are created during analysis by NovaSeq 6000Dx Analysis Application:

• analysisResults.json

• CopyComplete.txt

• edgeos.nextflow.config

• inputs/

  • sampleMapping.json

  • SampleSheet.csv

  • SampleSheet.json

• Manifest.tsv

• params.json

• Results/

• workflowLogs/

  • nf-main-***.log

When the analysis run completes, the analysis application generates an analysis output in a specified location. To view analysis output, follow the steps below:

1. On the “Completed” runs tab, select the run

2. Review the run details page, and this will give the information to access the output folder

3. External Location: is the input for the run

4. Analysis Output Folder: is where the output is stored. To navigate to this page, follow the “server location” and the gds analysis output folder

5. Navigate to the directory that contains the analysis output folder

6. Open the folder, and then select the files that you want to view

The gene and exon coverage report files are tab-separated value (TSV) files with coverage values matching respectively the exons and genes for both DNA and RNA samples specified in the manifest file.

The block list represents high noise regions in the panel where false positive variant calls are likely produced. As a result, all positions in the gVCF are marked as Filter=excluded_regions to indicate variant call results are not reliable in such regions.

The block list includes the following genes:

• HLA A

• HLA B

• HLA C

• KMT2B

• KMT2C

• KMT2D

• chrY

• Any position with VAF 1% occurrence in six or more of the 60 baseline samples.

The software processes sequencing data to perform quality control, detect variants, determine tumor mutational burden (TMB), microsatellite instability (MSI) status, and genomic instability score (GIS), and report results. The following sections describe the analysis methods used in DRAGEN TruSight Oncology 500 Analysis Software.

DRAGEN TruSight Oncology 500 Analysis Software uses the following workflows to analyze sequencing data.

• FASTQ Generation

• DNA Analysis

  • DNA Alignment and Realignment

  • Read Collapsing

  • Indel Realignment and Read Stitching

  • Small Variant Calling

  • Small Variant Filtering

  • Copy Number Variant (CNV) Calling

  • Phased Variant Calling

  • Variant Merging

  • Annotation

  • Tumor Mutational Burden (TMB) Scoring

  • Microsatellite Instability (MSI) Status

  • Contamination Detection

• RNA Analysis

  • Downsampling

  • Read Trimming

  • Alignment

  • Duplicate Marking

  • Fusion Calling

  • RNA Fusion Filtering

  • Splice Variant Calling

  • Annotation

  • Fusion Merging

• Quality Control

  • Run QC

  • DNA Sample QC

  • RNA Sample QC

Overview

DRAGEN TruSight™ Oncology 500 Analysis Software supports data analysis for TruSight Oncology 500 Assay and TruSight Oncology 500 High-Throughput Assay, both Research Use Only (RUO).

The software provides local and cloud analysis for DNA and RNA libraries generated from formalin-fixed, paraffin-embedded (FFPE) tissue samples. The assays and the software are optimized to provide high sensitivity and specificity for low-frequency somatic variants across coding exons and additional regions of biological relevance in 523 genes for DNA biomarkers.

In addition, this software supports data analysis for TruSight Oncology 500 HRD (RUO), an optional add-on kit to TruSight Oncology 500, that enables detection of homologous recombination deficiency (HRD) through assessment of a genomic instability score (GIS).

DNA biomarkers:

• Single nucleotide variants (SNVs)

• Insertions

• Deletions

• Copy number variants (CNVs)

• Exon-level CNVs

• Multinucleotide variants (MNVs)

• Genomic Instability Score (GIS Score) *

DNA Immunotherapy Biomarkers:

• Tumor mutational burden (TMB)

• Microsatellite instability (MSI)

RNA biomarkers (called from 55 genes):

• Fusions

• Splice variants

Beta features:

• Absolute copy numbers (ACN)*

• Loss of heterozygosity (LOH)*

• Tumor fraction*

• Ploidy*

Details of the regions covered by the assays can be found in the assay manifest file. Contact your local Illumina representative for more information.

Local and Cloud Deployments

Local analysis is available using a standalone DRAGEN server or an application with a user interface on NovaSeq 6000Dx. The software on the standalone DRAGEN server allows for analysis on a single DRAGEN server or splitting across multiple servers.

Cloud analysis is available on Illumina Connected Analytics with auto-launch or manual launch. Both methods are available from BCLs and FASTQs.

Instrument Compatibility

DRAGEN TruSight Oncology 500 analysis software is compatible with data generated on the Illumina instruments as summarized in the table below.

Navigation of Guide

This resource provides information on installation, configuration, running, troubleshooting as well as analysis algorithms of DRAGEN TruSight Oncology 500 analysis software on Illumina Connected Analytics, standalone DRAGEN server, and the NovaSeq 6000Dx analysis application.

Overview

The installation script for DRAGEN TruSight Oncology 500 Analysis Software installs the following software and dependencies:

1. DRAGEN TruSight Oncology 500 Analysis Software itself

2. DRAGEN Software if a compatible version is not present

3. Docker software if a compatible version is not present

4. A script required to generate DRAGEN genome hash table

5. A script to check that DRAGEN TruSight Oncology 500 Analysis Software is installed properly

Installation Requirements

Hardware

• DRAGEN server v3 or v4

• If performing analysis for the TruSight Oncology 500 High-Throughput assay, mkfifo needs to be enabled on the network-attached storage (NAS).

Software

• By default Linux CentOS 7.9 operating system (or later) or Oracle Linux 8 (or later), is provided. Oracle Linux 8 is recommended.

• Docker Software, see table below

• DRAGEN Software, see table below

Permissions

Illumina recommends logging in as root user for installation, but as a non-root user for running TSO 500 analysis.

• A non-root user must be a member of the Docker group to run Docker. For more information on Docker permission requirements and alternatives to running as root, refer to the Docker documentation available on the Docker website.

• Installing and uninstalling DRAGEN TruSight Oncology 500 Analysis Software and running the system check requires root privileges.

• Run DRAGEN TruSight Oncology 500 Analysis Software without being logged in as a root user. Running the DRAGEN TruSight Oncology 500 Analysis Software as root is not required or recommended.

Compatibility with other TruSight Oncology 500 and TruSight Oncology 500 ctDNA Analysis Software

DRAGEN TruSight Oncology 500 Analysis Software v2.6.0 can be installed on one DRAGEN server with:

1. DRAGEN TruSight Oncology 500 ctDNA Analysis Software v2.6.0 (v3.10.17*)

2. One prior 2.x version of DRAGEN TruSight Oncology 500 ctDNA Analysis Software (v2.1.1 (v3.10.9*), v2.5.0 (v3.10.15*), 2.6.0 (v3.10.17*), 2.6.1 (v3.10.18*))

3. One prior 2.x version of DRAGEN TruSight Oncology 500 Analysis Software (v2.1.1 (v3.10.9*), v2.5.3 (v3.10.16*)

*DRAGEN Software version

Contrary to the prior versions, the installation scripts for DRAGEN TruSight Oncology 500 Analysis Software v2.6.0 and DRAGEN TruSight Oncology 500 ctDNA v2.6.0 do not uninstall previous versions of DRAGEN TruSight Oncology 500 Analysis Software. To uninstall a previous version of DRAGEN TruSight Oncology 500 Analysis Software, refer to the respective guide.

Installation Instructions

As a root user, perform the following steps to install DRAGEN TruSight Oncology 500 v2.6.0 Analysis Software:

1. Contact Illumina Customer Care at customercare@illumina.com to obtain the DRAGEN TruSight Oncology 500 Analysis Software installer package.

2. Download the installation package provided in the email from Illumina. The link expires after 7 days.

1. Make sure no other analysis is being performed. Installing the software while performing other analyses prevent the installer process from proceeding

2. Copy the install script to the /staging directory to store the script in the directory.

1. Use the following command to update the run script permission: chmod +x /staging/install_DRAGEN_TSO500-2.6.0.run

2. Use the following command to run the installation script, which runs for approximately 20 minutes:

   1. For Docker, use the following command: sudo TMPDIR=/staging /staging/install_DRAGEN_TSO500-2.6.0.run . The script installs compatible DRAGEN software and removes any previously installed versions.

   2. For Apptainer, use the following command: sudo TMPDIR=/staging /staging/install_DRAGEN_TSO500-2.6.0.run -- --noDockerInstall This will not install Apptainer, but will install the analysis software in the SIF container format and modify the software to launch analyses using Apptainer.

3. During the installation process, you might be instructed to reboot or power cycle the system to complete the installation of the DRAGEN software. A power cycle of the system requires the server be shut down and restarted.

4. Log out of the server and then log back in.

5. Use the following command to build the DRAGEN server hash table, which runs for approximately 60 minutes: /usr/local/bin/build-hashtable_DRAGEN_TSO500-2.6.0.sh Refer to Troubleshooting if any errors occur.

6. Install your DRAGEN server licenses if needed:

   1. To run DRAGEN TruSight Oncology 500 v2.6.0 Analysis Software, you need TSOCombined license. This license is pre-installed on DRAGEN servers purchased after August 2022. To check if the license is already installed, run /opt/edico/bin/dragen_liccommand.

   2. To run analysis for the HRD add-on kit, you need TSO500_HRD license (not available in Japan).

   3. For servers connected to the Internet, install your software licenses as follows:

      1. First, test and confirm that the server is connected to the Internet. Example: ping www.illumina.com

      2. To install the license, enter: /opt/edico/bin/dragen_lic -i auto

   4. For servers not connected to the internet, contact Illumina Customer Care at customercare@illumina.com for license information.

7. After installing DRAGEN server licenses, generate a list of installed DRAGEN server licenses by running the following command: /opt/edico/bin/dragen_lic

   If license installation is successful, the list should include TSOCombined. If you have a license for HRD, the list should include TSO500_HRD.

   If the expected licenses are not installed, contact Illumina Customer Care.

Running the System Check

After installation is complete, make sure the system functions properly by running the following command: /usr/local/bin/check_DRAGEN_TSO500-2.6.0.sh

The script checks that:

• All required services are running

• Proper Docker image is installed

• DRAGEN TruSight Oncology 500 Analysis Software can successfully process a test data set

The system check script runs for approximately 25 minutes. If the script prints a failure message, contact Illumina Technical Support and provide the /staging/check_DRAGEN_TSO500_<timestamp>.tgz output file.

If using MacOS to connect to a server, an error can occur if the local settings are not in English. To resolve the error, disable the ability to set environment variables automatically in Terminal settings.

Uninstall Software

The DRAGEN TruSight Oncology 500 Analysis Software installation includes an uninstall script called uninstall_DRAGEN_TSO500-2.6.0.sh, which is located in /usr/local/bin.

Executing the uninstall script removes the following assets:

• All DRAGEN TruSight Oncology 500 Analysis Software related scripts located in /usr/local/bin

• Resources found in /staging/illumina/DRAGEN_TSO500

• The dragen_tso500:2.6.0: Docker image

To uninstall the DRAGEN TruSight Oncology 500 Analysis Software, run the following command as a root user:

uninstall_DRAGEN_TSO500-2.6.0.sh

You are not required to uninstall Docker or DRAGEN software. To remove Docker, review the install instructions for your operating system in the Docker documentation.

DRAGEN TruSight Oncology 500 Analysis Software can be used to run a subset of samples on different DRAGEN servers to decrease overall processing time. This is possible using a three stage process called scatter/gather, which consists of demultiplexing, analysis, and result gathering.

The first stage is demultiplexing. Demultiplexing runs once on the entire run folder, generates FASTQ files for each sample in the run, and then separates sample files into respective folders. Once complete, note the output directory containing the sample directories holding the FASTQ files.

The process for scattering the analysis on multiple DRAGEN servers is as follows:

1. Determine how many DRAGEN servers are available to run.

2. Run demultiplexing on a single DRAGEN server.

1. Transfer the FASTQ folder output from the original DRAGEN server to additional servers.

   1. Logs_Intermediates/FastqGeneration.

2. Run analysis software using the --fastqFolder option on both the original and additional DRAGEN servers.

   • Option 1 Copy the original SampleSheet.csv to each server. Then provide a subsetted list to the Bash script on each DRAGEN server with the intended samples/pairs to run.

   • Option 2 Copy and modify the SampleSheet.csv to each DRAGEN server to only contain the list of samples/pairs to run. The software verifies that all samples in the sample sheet are contained within the FASTQ folders unless the --sampleOrPairIDs command-line option is present in the analysis launch. Failure to account for these checks results in an error.

3. Copy the results from demultiplexing and each analysis run onto a single server, and then generate the final /Results directory, which contains the aggregated results. Enter the --gather command followed by the output directories of the demultiplexing step and each individual analysis run.

Commands for Multinode Analysis

How to Create TSO 500 Sample Sheets in BaseSpace Run Planning tool

The BaseSpace Sequence Hub Run Planning tool is available, and is used to generate a valid sample sheet in v2 format for use on a TSO 500 supported sequencer for both ICA and Standalone DRAGEN Server analysis options. Filling out the form on the user interface will produce a exportable sample sheet with the required fields filled in. Refer to ICA Auto-launch Sample Sheet Requirements for descriptions of fields that appear in ICA sample sheets.

The sections below represent each step in the BaseSpace Run Planning tool.

Step 1: Run Settings

Step 2: Configuration

Step 3: Sample Settings

Users can manually enter sample information, or download a template file to bulk upload sample information. Users can import the completed template or a compatible sample sheet.

Step 4: Run Review

Once all details are captured and pass validation, the user can review the details on the Run Review screen. From here they can choose to edit details in previous screens or export the sample sheet. Once completed, press the Cancel button to finish run planning.

Note: once leaving this screen, the run and sample sheet will not be accessible.

For NovaSeqX Plus users, the run can be saved as a draft or as a planned run (via “Save as Draft” and “Save as Planned” buttons respectively). Either selection will save the run to the Planned Runs screen on BaseSpace. There is no option to export the sample sheet on this screen.

Planned Runs Screen (NovaSeq X Series only)

The Planned Runs screen lists all planned or drafted runs. Users can set drafted runs to planned, export the sample sheet, and edit or delete a run on this screen.

Once the run is saved as Planned, it will appear on the NovaSeq X Series instrument where it can be selected for sequencing.

For more information on run planning, refer to the BaseSpace Sequence Hub support site page.

Guided Examples

Please review these guided examples of analysis workflows that include a step of setting up a run in BaseSpace Run Planning tool:

• NovaSeq 6000Dx: TSO 500 Auto-launch Analysis in Cloud

• NextSeq 500/550Dx: TSO 500 and Connected Insights Auto-launch Analysis in Cloud

Standard Sample Sheet Requirements

The following sample sheet requirements describe required and optional fields for DRAGEN TSO 500 Analysis Software. Depending on the deployment (standalone DRAGEN server, ICA with auto-launch, ICA with manual launch, NovaSeq 6000Dx analysis application), certain sections and required values can deviate from the standard requirements. These deviations are noted in the information below.

Use the following steps to create a valid sample sheet.

1. Download the sample sheet v2 template that matches the instrument & assay run.

2. In the Sequencing Settings section, enter the following required parameters:

[Sequencing_Settings] Section

1. In the BCL Convert Settings section, enter the following required parameters:

[BCLConvert_Settings] Section

1. In the BCL Convert Data section, enter the following parameters for each sample.

[BCLConvert_Data] Section

1. In the TSO 500 Data section, enter the following parameters:

[TSO500S_Data] Section

To ensure a successful analysis, follow these guidelines:

1. Avoid any blank lines at the end of the sample sheet; these can cause the analysis to fail.

2. When running local analysis using the command line save the sample sheet in the sequencing run folder with the default name SampleSheet.csv, or choose a different name and specify the path in the command-line options.

ICA with Auto-launch: Sample Sheet Requirements

Refer to the following requirements to create sample sheets for running the analysis on ICA with Auto-launch. For sample sheet requirements common between deployments see Standard Sample Sheet Requirements. Samples sheets can be created using BaseSpace Run Planning Tool or manually by downloading and editing a sample sheet template

[Cloud_TSO500S_Data] Section

Refer to [TSO500_Data] Section for this section's requirements.

[Cloud_TSO500S_Settings] Section

[Cloud_Data] Section

[Cloud_Settings] Section

NovaSeq 6000Dx Analysis Application: Sample Sheet Requirements

This section describes fields specific for sample sheets for NovaSeq 6000Dx Analysis Application. For more information on DRAGEN TSO 500 Analysis Software sample sheet requirements, refer to the sections above.

[BCLConvert_Settings] Section

[TSO500HRD_Data] Section

Refer to [TSO500S_Data] Section for this section's requirements.

How to Launch Analysis

1. Create a Project: Project can be specific for the DRAGEN TruSight Oncology 500 pipeline or it can contain multiple Pipelines and/or Tools). For information on creating Projects, refer to the Projects section in Illumina Connected Analytics help.

1. Edit Project and Add Bundle: Edit the Project and add the bundle titled, "DRAGEN TSO 500 v2.6.0 (XX)." XX is a 2-letter code designating the region from which you are launching the analysis. Adding the Bundle automatically adds the pipeline and associated resource files and datasets to the Project. For information on Bundles, refer to the Bundles section in Illumina Connected Analytics help.

1.  Upload the sequencing data: For information on viewing and uploading data, refer to the Data section in Illumina Connected Analytics help.

2. Start Analysis: In the Project, navigate to Pipelines, select the TSO 500 v2.6.0  Pipeline, and then select  "Start New Analysis". Set up the new analysis by configuring the parameters listed in the table below. When the required files are completed, start analysis.

3. Download Results: After analysis is complete, navigate to results in the configured output location.

Please see the Illumina Support Shorts for guidance on how to set up and run DRAGEN TSO 500 RUO analysis on ICA.

Analysis Parameters on ICA

To launch an analysis via the ICA user interface, configure a DRAGEN TSO 500 pipeline analysis with the following parameters.

For information about using pipelines, refer to Illumina Connected Analytics support site page.

DRAGEN TSO 500 analysis software is compatible with several instruments and assay workflows (standard, XP), each of which have implications for the sample sheet.

Sample sheet templates contain all required fields, including index sequences in the proper orientation for all indexes from a given library prep kit. The templates are provided as a starting point for creating a sample sheet manually when launching analysis on a standalone DRAGEN server or on ICA using manual launch.

Users can visit the Sample Sheet guidelines section to learn additional details on required fields and values as they fill-in their sample information. Use the lookup table below to select and download the sample sheet template that matches your instrument, assay, and workflow configuration:

*Lane numbers cannot exceed what is supported by the flow cell in use.

You can use the following command-line options with DRAGEN TruSight Oncology 500 Analysis Software.

To learn more about the input requirements, use the --help command-line option.

Note:

• Use full paths when specifying the file paths in the command line.

• Avoid special characters such as &, *, #, and spaces.

• When starting from BCL files, only the run folder needs to be specified. The immediate parent directory containing the BCL files does not need to be specified.

When running the analysis software using SSH, Illumina recommends using additional software to prevent unexpected termination of analysis. Illumina recommends screen and tmux.

1. Wait for any running DRAGEN TruSight Oncology 500 Analysis Software containers to complete before launching a new analysis. Run the following command to generate a list of running containers:docker ps

2. Select from one of the following options:

• Start from BCL files in the run folder with the sample sheet included in the run folder. DRAGEN_TSO500-2.6.0.sh \ --runFolder /staging/{RunFolderName} \ --analysisFolder /staging/{AnalysisFolderName}

• Start from BCL files in the run folder with the sample sheet located in a folder other than the run folder. DRAGEN_TSO500.sh \ --runFolder /staging/{RunFolderName} \ --analysisFolder /staging/{AnalysisFolderName} \ --sampleSheet /staging/{SampleSheetName}.csv

• Start from BCL files in the run folder with a different sample sheet and demultiplexing only. DRAGEN_TSO500-2.6.0.sh \ --runFolder /staging/{RunFolderName} \ --analysisFolder /staging/{AnalysisFolderName} \ --sampleSheet /staging/{SampleSheetName}.csv \ --demultiplexOnly

• Start from FASTQ with the sample sheet included in the FASTQ folder and with different resources and hash table folders. DRAGEN_TSO500-2.6.0.sh \ --resourcesFolder /staging/illumina/DRAGEN_TSO500/resources \ --hashtableFolder /staging/illumina/DRAGEN_TSO500/ref_hashtable \ --fastqFolder /staging/{FastqFolderName} \ --analysisFolder /staging/{AnalysisFolderName}

• Start from FASTQ folder with sample sheet included in the FASTQ folder and subset of samples or pairs. DRAGEN_TSO500-2.6.0.sh \ --fastqFolder /staging/{FastqFolderName} \ --analysisFolder /staging/{AnalysisFolderName} \ --sampleOrPairIDs "Pair_1,Pair2"

Starting from BCL Files

If starting from BCL (*.bcl) files, DRAGEN TruSight Oncology 500 Analysis Software requires the run folder to contain certain files and folders. These inputs are required for Docker.

The run folder contains data from the sequencing run, make sure that the folder contains the following files:

Starting from FASTQ Files

The following inputs are required for running the DRAGEN TruSight Oncology 500 Analysis Software using FASTQ (*.fastq) files. The requirements apply to Docker.

• Full path to an existing FASTQ folder.

• The FASTQ folder structure conforms to the folder structure in FASTQ File Organization.

• The sample sheet is in the FASTQ folder path, or you can set the path to the sample sheet with the --sampleSheet override command line option.

Make sure there is sufficient disk space for the analysis to complete. Refer to the --help command line argument details for disk space requirements.

FASTQ File Organization

Store FASTQ files in individual subfolders that correspond to a specific Sample_ID. Keep file pairs together in the same folder. Alternatively, store the FASTQ files in one flat folder structure where the FASTQ files are stored in one folder.

The DRAGEN TruSight Oncology 500 Analysis Software requires separate FASTQ files per sample. Do not merge FASTQ files.

The instrument generates two FASTQ files per flow cell lane, so that there are eight FASTQ files per sample.

Sample1_S1_L001_R1_001.fastq.gz

• Sample1 represents the Sample ID.

• The S in S1 means sample, and the 1 in S1 is based on the order of samples in the sample sheet, so S1 is the first sample.

• L001 represents the flow cell lane number.

• The R in R1 means Read, so R1 refers to Read 1.

File name: {Pair_ID}_CombinedVariantOutput.tsv

The combined variant output file contains the variants and biomarkers in a single file that is based on a single sample. If using pair ID, the file is based on paired DNA and RNA samples from the same individual. The output contains the following variant types and biomarkers:

• Small variants

• Copy number variants (CNV) (with absolute copy number when HRD Assay is run)

• TMB

• MSI

• Fusions

• Splice variants

• GIS (when HRD Assay is run)

• Gene-level Loss of Heterozygosity (when HRD Assay is run)

• Large Rearrangements

The combined variant output file also contains Analysis Details and Sequencing Run Details sections. The details of each are listed in the following table:

Combined variant output produces small variants with blank fields in the following situations:

• The variant has been matched to a canonical RefSeq transcript on an overlapping gene not targeted by TruSight Oncology 500.

• The variant is located in a region designated iSNP, indel, or Flanking in the TST500_Manifest.bed file located in the Resources folder.

Variant Filtering Rules

• Small Variants - All variants with the FILTER field marked as PASS in the hard-filtered genome VCF are present in the combined variant output.

  • Gene information is only present for variants belonging to canonical transcripts that are within the Gene Allow List–Small Variants.

  • Transcript information is only present for variants belonging to canonical transcripts that are within the Gene Allow List–Small Variants.

• Copy Number Variants - Copy number variants must meet the following conditions:

  • FILTER field marked as PASS.

  • ALT field is <DUP or <DEL> .

• Fusion Variants - Fusion variants must meet the following conditions:

  • Passing variant call (KeepFusion field is true).

  • Contains at least one gene on the fusion allow list.

  • Genes separated by a dash (-) indicate that the fusion directionality could be determined. Genes separated by a slash (/) indicate that the fusion directionality could not be determined.

• Biomarkers TMB/MSI - Always present when DNA sample is processed.

• Splice Variants - Passing splice variants that are contained on genes EGFR, MET, and AR.

• Biomarker GIS - Present only if TruSight Oncology 500 HRD analysis is performed

• Loss of Heterozygosity - Present only when TruSight Oncology 500 HRD is run. Loss of heterozygosity (LOH) must meet the following condition:

  • MCN field is equal to 0

• Large Rearrangements CNV - Large Rearrangements CNVs must meet the following conditions:

  • BRCA1 or BRCA2 contains at least one affected exon.

  • ALT field is <DUP> or <LOSS> .

Auto-launch Prerequisites and Workflow

*The BaseSpace Sequence Hub setting for run monitoring and storage must be selected on the instrument to use DRAGEN TSO 500 analysis auto-launch. For information on preparing your instrument for DRAGEN TSO 500 Auto-launch, refer to the documentation for your instrument.

1. Use BaseSpace Sequence Hub Run Planning tool or the sample sheet templates provided on the support page to create and export a sample sheet.

   1. If BaseSpace Run Planning tool is not available in your region, use the sample sheet template.

2. 1. Data is uploaded to BaseSpace Sequence Hub and then pushed to ICA. You can monitor the run in BaseSpace Sequence Hub.

   2. Analysis auto launches in ICA when sequencing and the upload completes. You can monitor the status of the analysis in BaseSpace Sequence Hub or ICA

   3. If necessary, you can requeue the analysis via BaseSpace Sequence Hub.

3. View the analysis output results in either BaseSpace Sequence Hub or ICA.

BaseSpace Sequence Hub Requirements for ICA Auto-Launch

BaseSpace Run Planning tool is a multi-step workflow that generates a manual launch or auto-launch capable sample sheet for export and requires the following additional settings:

• Access to BaseSpace Sequence Hub.

• ICA Run Storage is enabled under BaseSpace Sequence Hub settings.

Requeue Analysis

You can requeue analysis of a run via the run's Summary page in BaseSpace Sequence Hub.

Minimum Storage Requirements on ICA

Guided Examples

Please review these guided examples of using DRAGEN TSO 500 Analysis Software with auto-launch on ICA:

Refer to for more information.

Small Variant gVCF

File name: {SAMPLE_ID}_hard-filtered.gvcf.gz

The small variant genome variant call file contains information on all candidate small variants evaluated, including complex variants up to 15 bp from phased variant calling across the entire TSO 500 panel.

The variant status is determined by the FILTER column in the genome VCF as follows.

Small Variant Annotated JSON

File name: {SAMPLE_ID}_DNAVariants_Annotated.json.gz

The small variants annotated file provides variant annotation information for all nonreference positions from the genome VCF including pass and nonpass variants.

TMB Trace

The TMB trace file provides comprehensive information on how the TMB value is calculated for a given sample. All passing small variants from the small variant filtering step are included in this file. To calculate the numerator of the TmbPerMb value in the TMB JSON, set the TSV file filter to use the IncludedInTMBNumerator with a value of True.

The TMB trace file is not intended to be used for variant inspections. The filtering statuses are exclusively set for TMB calculation purposes. Setting a filter does not translate into the classification of a variant as somatic or germline.

Copy Number VCF

The copy number VCF file contains CNV calls for DNA libraries of the amplification genes targeted by DRAGEN TruSight Oncology 500 Analysis Software. The CNV call indicates fold change results for each gene classified as reference, deletion, or amplification.

The value in the QUAL column of the VCF is a Phred transformation of the p-value where Q=-10xlog10(p-value). The p-value is derived from the t-test between the fold change of the gene against the rest of the genome. Higher Q-scores indicate higher confidence in the CNV call.

In the VCF notation, <DUP> indicates the detected fold change (FC) is greater than a predefined amplification cutoff. <DEL> indicates the detected FC is less than a predefined deletion cutoff for that gene. This cutoff can vary from gene to gene.

Each copy number variant is reported as a fold change on normalized read depth in a testing sample relative to the normalized read depth in diploid genomes. Given tumor purity, you can infer the ploidy of a gene in the sample from the reported fold change.

Given tumor purity X%, for a reported fold change Y, you can calculate the copy number n using the following equation:

For example, a tumor purity at 30% and a MET with fold change of 2.2x indicates that 10 copies of MET DNA are observed.

RNA expanded metrics are provided for information only. They can be informative for troubleshooting but are provided without explicit specification limits and are not directly used for sample quality control. For additional guidance, contact Illumina Technical Support.

The Illumina DRAGEN TruSight Oncology 500 Analysis Software allows for analysis of sequencing data generated from the TruSight Oncology 500 HRD assay. When HRD samples are analyzed new results and metrics are included in the CombinedVariantOutput and MetricsOutput files respectively. The following tables detail how these scores and QC metrics are derived.

HRD Metrics Added to Metrics Output File

Metrics Output

The MetricsOutput.tsv file contains the following quality control metrics for all samples:

• DNA library QC metrics for:

  • Small variant calling

  • TMB

  • MSI

  • CNV

  • [HRD] GIS

• RNA library QC metrics

• Run QC metrics, analysis status, and contamination

This TSV file also includes expanded DNA library QC metrics per sample, based on total reads, collapsed reads, chimeric reads, and on-target reads. Analysis using RNA samples also produces RNA library QC metrics and expanded RNA library QC metrics per sample based on total reads and coverage.

The MetricsOutput.tsv file is a final combined metrics report with sample status, key analysis metrics, and metadata. Sample metrics within the report include suggested lower specification limits (LSL) and upper specification limits (USL) for each sample in the run.

For troubleshooting information, refer to

Please visit support page for release notes and additional information.

Revision History

Sequencing data stored in BCL format are demultiplexed through a process that uses the index sequences unique to each sample to assign clusters to the library from which they originated. Each cluster contains two indexes (i7 and i5 sequences, one at each end of the library fragment). The combination of those index sequences are used to demultiplex the pooled libraries.

After demultiplexing, this process generates FASTQ files, which contain the sequencing reads for each individual sample library and the associated quality scores for each base call, excluding reads from any clusters that did not pass filter.

Refer to RNA Output for more information.

Downsampling

Each sample is downsampled to 30 million RNA reads. This number represents the total number of single reads (eg, R1 + R2, from all lanes). When using the recommended sequencing configurations or plexity, the samples can have fewer reads than the downsampling limit. In these cases, the FASTQ files are left as-is.

Read Trimming

Reads are trimmed to 76 base pairs for further processing.

RNA Alignment and Fusion Detection

RNA alignment and fusion detection uses trimmed reads in FASTQ format as input. The outputs include a BAM file that contains duplicate-marked read alignments, an SJ.out.tab file that contains unannotated splice junctions, and a CSV file that contains fusion candidates.

DRAGEN aligns RNA reads in a transcript-aware mode using the human hg19 genome containing unplaced contigs (ie, chrUn_gl regions) and uses GENCODEv19 transcript annotations to identify splice sites. DRAGEN identifies and marks duplicate read alignments using start and end coordinates of alignments, which are adjusted for soft clipped reads.

Fusion and splice variant calling only use deduped fragments to score variants. DRAGEN identifies fusion candidates using chimeric split read alignments (pairs of primary and supplementary alignments) against multiple genes. DRAGEN scores and filters reads based on the various features of each candidate such as the number of supporting reads, mapping quality of supporting reads, and sequence homology between parent genes.

The DRAGEN RNA Fusion caller identifies gene fusions by searching for chimeric reads spanning two distinct parent genes. Based on the chimeric reads, DRAGEN first creates a list of fusion candidates, then scores the candidates to report the list of high confidence fusion calls from the candidate pool.

DRAGEN RNA Fusion caller performs the following steps:

1. Generates fusion candidate generation based on split read alignment.

2. Recruits additional evidence from fusion supporting discordant read pairs and soft-clipped reads.

3. Computes fusion candidate features such as gene coverage, read mapping quality, alternate allele frequency, gene homology, alignment anchor length, and breakpoint distance from exon boundary.

4. Scores and ranks the fusion candidates using a logistic regression model.

5. Selects a final list of fusion calls based on score and other filters including number of supporting reads, unique read alignment count, read through transcripts, and fusions matching the enriched regions.

Splice Variant Calling

RNA splice variant calling is performed for RNA sample libraries. Candidate splice variants (junctions) from RNA Alignment are compared against a database of known transcripts and a splice variant baseline of non-tumor junctions generated from a set of normal FFPE samples from different tissue types. Any splice variants that match the database or baseline are filtered out unless they are in a set of junctions with known oncological function. If there is sufficient read support, the candidate splice variant is kept. This process also identifies candidate RNA fusions.

RNA Fusion Merging

Fusions identified during RNA fusion calling are merged with fusions from proximal genes identified during RNA splice variant calling. These are then annotated with gene symbols or names with respect to a static database of transcripts (GENCODE Release 19). The result of this process is a set of fusion calls that are eligible for reporting

RNA Splice Variant Annotation

The Illumina Annotation Engine annotates detected RNA splice variant calls with transcript-level changes (eg, affected exons in the transcript of a gene) with respect to RefSeq. This RefSeq database is the same RefSeq database used by the small variant annotation process.

The following sections describe performance testing methods.

Analytical Performance Testing

Illumina tests the analytical performance of variant calling using an approach that covers the entire workflow including library preparation, sequencing, and secondary analysis. This approach is used to test a diverse selection of variants. When the variant calling pipeline is expanded to call a new variant class, this approach is always used.

This version of the software includes results generated by features tested in silico and by beta features. Beta features have not been fully evaluated for performance, see Beta Features.

In Silico Testing Methods

Illumina uses in silico testing to the test the ability of the software to call an expanded scope of clinically relevant variants, including rare variants. In silico testing is used as a complementary method to analytical performance testing with wet lab step to expand the scope of testing. For example, while Illumina has analytically verified the performance of the software for calling complex variants in EGFR, the in silico testing approach characterizes the ability of the software to call complex variants in other genes.

For in silico testing, variants of interest are extracted from public databases like Cosmic and ClinVar. Each variant is simulated at different VAF levels by, depending on the variant class, spiking in mutant reads into a normal FFPE background (for sequence variants) or by increasing or decreasing the coverage of exons in the normal FFPE sample (for CNVs, for example, exon-level CNVs. The simulated reads match the expected quality of typical FFPE samples, such as fragment length, error rate, and family size. After the simulation, the software processes samples with spiked-in variants and determines the results. This approach does not include library prep and sequencing of tumor FFPE samples that include the rare variants of interest. The software reports these variants, but analytical verification was not performed.

DRAGEN TruSight Oncology 500 Analysis Software includes the following features that were tested i_n silico_ for both TruSight Oncology 500 and TruSight Oncology 500 HT:

• Complex variants in genes beyond EGFR

• Insertions and deletions > 25 bp

• CNV amplifications

• CNV deletions

• Variants in intron-exon junctions (2 bp – 10 bp into introns)

In addition, the following features were tested in silico for TruSight Oncology 500 HT:

• Exon-level CNVs in BRCA1 and BRCA2

Beta Features

This version of DRAGEN TruSight Oncology 500 Analysis Software includes beta features which have not been verified by Illumina due to limited access to samples or lack of an appropriate orthogonal method to perform testing, and, the use of in silico testing alone is not sufficient for verification purposes.

Customers are responsible for evaluating and demonstrating performance of any beta features they choose to implement. Beta features are indicated as such in the CombinedVariantOutput.tsv file. Illumina will continue to evaluate beta features with intent to fully release upon completion of verification for each feature.

This version includes the following beta features that may be used with the TruSight Oncology 500 HRD Assay:

• Tumor fraction (beta)

• Ploidy (beta)

• Absolute copy numbers (ACN) (beta)

• Gene-level loss of heterozygosity (LOH) events (beta)

DNA Alignment and Error Correction

DNA alignment and error correction involves aligning sequencing reads derived from DNA libraries to a reference genome and correcting errors in the sequencing reads prior to variant calling.

DRAGEN unique molecular identifier (UMI) error correction comprises three main steps:

1. DRAGEN UMI uses its HW accelerated mapper (based on a hash table implementation) to align DNA sequences in FASTQ files to the hg19 reference genome. These alignments are not written to a BAM.

2. The raw alignments are processed to remove errors, including errors introduced during FFPE preservation, PCR amplification, and sequencing. Reads from the same original DNA molecule are tagged with the same UMI during library preparation. The UMI allows DRAGEN to compare related reads, remove outlier signals, and collapse multiple reads into a single high-quality sequence. Read collapsing adds the following BAM tags:

   • RX/XU—UMI.

   • XV—Number of reads in the family.

   • XW—Number of reads in the duplex-family or 0 if not a duplex family.

3. DRAGEN performs a final alignment step on the UMI-collapsed reads. These final alignments are then written to a BAM file and a corresponding BAM index file is created.

DRAGEN continues to use these final alignments as input for gene amplification (copy number) calling, small variant calling (SNV, indel, MNV, delin), microsatellite instability (MSI) status determination, and DNA library quality control.

Small Variant Calling and Filtering

DRAGEN supports calling SNVs, indels, MNVs, and delins in tumor-only samples by using mapped and aligned DNA reads from a tumor sample as input. Variants are detected via both column wise pileup analysis and local de novo assembly of haplotypes. The de novo haplotypes allow the detection of much larger insertions and deletions than possible through column wise pileup analysis only. DRAGEN insertions and deletions are validated with lengths of at least 0–25 bp and more than 25 bp can be supported. In addition, DRAGEN also uses the de novo assembly to detect SNVs, insertions, and deletions that are co-phased and part of the same haplotypes. Any such co-phased variants that are within a window of 15 bp can then be reassembled into complex variants (MNVs and delins). The tumor-only pipeline produces a VCF file containing both germline and somatic variants that can be further analyzed to identify tumor mutations. Variant calling extends ± 10 bp into introns; details of the regions covered can be found in the assay manifest file. The pipeline makes no ploidy assumptions, enabling detection of low-frequency alleles.

DRAGEN small variant calling includes the following steps:

1. Detects regions with sufficient read coverage (callable regions).

2. Detects regions where the reads deviate from the reference and there is a possibility of a germline or somatic call (active regions).

3. Assembles de novograph haplotypes are assembled from reads (haplotype assembly).

4. Extracts possible somatic or germline calls (events) from column wise pileup analysis.

5. Calibrates read base qualities to account for FFPE noise.

6. Computes read likelihoods for each read/haplotype pair.

7. Performs mutation calling by summing the genotype probabilities across all reads/haplotype pairs.

8. Performs additional filtering to improve variant calling accuracy, including using a systematic noise file. The systematic noise file indicates the statistical probability of noise at specific positions in the genome. This noise file is constructed using clean (normal) samples. Regions where noise is common (eg, difficult to map regions) have higher noise values. The small variant caller penalizes those regions to reduce the probability of making false positive calls.

Copy Number Variant Calling

The DRAGEN copy number variant caller performs amplification, reference, and deletion calling for CNV targets within the assay. It counts the coverage of each target interval on the panel, uses a preprocessed panel of normal samples to normalize target counts, corrects for GC coverage bias, and calculates scores of a CNV event from observed coverage and makes copy number calls.

Exon-Level Copy Number Variant Calling

The BRCA large rearrangement step generates segmentation of the BRCA1 and BRCA2 genes for exon-level CNV detection from the BAM file. Using the same method as CNV calling, the large rearrangement component counts coverage of each target interval of the panel, performs normalization, and calculates the fold change values for each probe across the BRCA genes. Normalization includes GC bias correction, sequencing depth, and probe efficiency using a collection of normal FFPE and genomic DNA samples. Initial segmentation is performed for each gene with circular binary segmentation. The merging of segments is then determined by amplitude, noise, and variance at adjacent segments using thresholds established with in silico data. A large rearrangement is reported for genes with more than one segment. Coordinates of the exon-level CNV and the log2 mean fold change for each of the BRCA gene segments are found in the *_DragenExonCNV.json file.

Annotation

The Illumina Annotation Engine performs annotation of small variants, CNVs, and exon-level CNVs. The inputs are gVCF files and the outputs are annotated JSON files.

The Illumina Annotation Engine processes each variant entry and annotates with available information from databases such as dbSNP, gnomAD genome and exome, 1000 genomes, ClinVar, COSMIC, RefSeq, and Ensembl. The header includes version information and general details. Each annotated variant is included as a nested dictionary structure in separate lines following the header.

The following table shows version information for each annotation database:

Tumor Mutational Burden

DRAGEN is used to compute tumor mutational burden (TMB) in coding regions where there is sufficient coverage.

The following variants are excluded from the TMB calculation:

• Non-PASS variants.

• Mitochondrial variants.

• MNVs.

• Variants that do not meet a minimum depth threshold.

• Variants that do not meet the minimum variant allele threshold.

• Variants that fall outside the eligible regions.

• Tumor driver mutations. Variants with a population allele count ≥ 50 are treated as tumor driver mutations. Germline variants are not counted towards TMB. Variants are determined as germline based on a database and a proxy filter.

Variants with a population allele count ≥ 10 that are observed in either the 1000 Genomes or gnomAD databases are marked as germline. MNVs, which do not count towards TMB, may be marked as germline when all their component small variants are marked as germline. The proxy filter scans the variants surrounding a specific variant and identifies those variants with similar variant allele frequencies (VAF). If the majority of surrounding variants of similar VAF are germline, then the variant is also marked as germline.

The formula for TMB calculation is:

$TMB = {Filtered\ Variants \over Eligible\ Region\ Size (Mbp)}$

$Nonsynonymous TMB = {Filtered\ Nonsynonymous\ Variants \over Eligible\ Region\ Size (Mbp)}$

Outputs are captured in a _TMB_Trace.tsv file that contains information on variants used in the TMB calculation and a .tmb.json file that contains the TMB score calculation and configuration details.

Microsatellite Instability Status

DRAGEN can determine the MSI status of a sample. It uses a normal reference file, which was created from a set of normal samples. During sequencing, normal reference files are generated by tabulating read counts for each microsatellite site. The normal file contains the read count distribution for each microsatellite.

MSI calling for a tumor-only sample is performed by first tabulating tumor counts from the read alignments for each microsatellite site. Then, the Jensen-Shannon distance (JSD) is calculated between each pair of tumor and normal baseline samples. DRAGEN determines unstable sites by performing Chi-square testing of tumor JSD and normal JSD distributions. Unstable sites are called if the mean distance difference of the two JSD distributions is ≥to the distance threshold and Chi-square p-value is ≤ to the p-value threshold. Lastly, DRAGEN produces an MSI status given assessed site count, unstable site count, the percentage of unstable sites in all assessed sites, and the sum of the Jensen-Shannon distance of all the unstable sites.

Genomic Instability Score

Genomic instability score (GIS) is a whole genome signature for homologous recombination deficiency. The GIS is composed of the sum of three components: loss of heterozygosity, telomeric allele imbalance, and large-scale state transition. These components are estimated using the GIS algorithm contracted from Myriad Genetics, which uses an input of the b-allele frequency and coverage across a genome-wide single nucleotide panel. A panel of normal samples is used for both bias reduction and normalization prior to GIS estimation. Final GIS results can be found in the *.gis.json file.

Contamination Detection

The contamination analysis step detects foreign human DNA contamination using the SNP error file and pileup file that are generated during the small variant calling and the TMB trace file. The software determines whether a sample has foreign DNA using the contamination score. In contaminated samples, the variant allele frequencies in SNPs shift from the expected values of 0%, 50%, or 100%. The algorithm collects all positions that overlap with common SNPs that have variant allele frequencies of < 25% or > 75%. Then, the algorithm computes the likelihood that the positions are an error or a real mutation. The contamination score is the sum of all the log likelihood scores across the predefined SNP positions with minor allele frequency < 25% in the sample and are not likely due to CNV events.

The larger the contamination score, the more likely there is foreign DNA contamination. A sample is considered to be contaminated if the contamination score is above predefined quality threshold. The contamination score was found to be high in samples with highly rearranged genomes or HRD samples. 1% of HRD samples found to be above the threshold with no evidence for actual contamination.

Tumor fraction (beta)

Tumor fraction is calculated as described in the User Guide, section “HRD Metrics Report” and leverages the Myriad Genetics algorithm. Tumor fraction is output in the Logs_Intermediates/Gis/SAMPLE/SAMPLE.gis.json and Combined Variant Output file.

Ploidy (beta)

Ploidy is calculated as described in the User Guide, section “HRD Metrics Report” and leverages the Myriad Genetics algorithm. Ploidy is output in the in the Logs_Intermediates/Gis/SAMPLE/SAMPLE.gis.json and Combined Variant Output file.

Absolute Copy Numbers (beta)

Absolute copy numbers are calculated by leveraging the Myriad Genetics algorithm. The algorithm segments the entire genome using the HRD panel and provides an A and B allele estimate for each segment. After the TSO 500 pipeline determines CNV calls (using the TSO 500 panel), the segment covering the gene is identified, and the A and B allele numbers of the segment overlapping the gene are reported. If the gene is within 300 kbases from the segment boundary, the estimate is unreliable and “-1” is output. Absolute copy numbers are output in the Logs_Intermediates/Gis/SAMPLE/SAMPLE.abcn_annotated.vc f, Logs_Intermediates/Gis/SAMPLE/SAMPLE.abcn_genes.tsv and Combined Variant Output file.

Gene-Level Loss of Heterozygosity (beta)

Gene-level loss of heterozygosity is calculated based on the minor copy number reported in the abcn_annotated.vc f. If the minor copy number is 0 then the gene is assumed to have a loss of heterozygosity. Gene-level loss of heterozygosity is output in the Logs_Intermediates/Gis/SAMPLE/SAMPLE.abcn_genes.tsv and Combined Variant Output file.

The software calculates several quality control metrics for runs and samples.

Run QC

The Run Metrics section of the metrics output report provides sequencing run quality metrics along with suggested values to determine if they are within an acceptable range. The overall percentage of reads passing filter is compared to a minimum threshold. For Read 1 and Read 2, the average percentage of bases ≥ Q30, which gives a prediction of the probability of an incorrect base call (Q‑score), are also compared to a minimum threshold. The following tables show run metric and quality threshold information for different systems.

The values in the Run Metrics section are listed as NA in the following situations:

• If the analysis was started from FASTQ files.

• If the analysis was started from BCL files and the InterOp files are missing or corrupt.

NextSeq 500/550 or NextSeq 550Dx (RUO)

NovaSeq 6000 or NovaSeq 6000Dx (RUO)

NextSeq 1000/2000

NovaSeq X

DNA Sample QC

DRAGEN TruSight Oncology 500 uses QC metrics to assess the validity of analysis for DNA libraries that pass contamination quality control. If the library fails one or more quality metrics, then the corresponding variant type or biomarker is not reported, and the associated QC category in the report header displays FAIL. Additionally, a companion diagnostic result may not be available if it relies on QC passing for one or more of the following QC categories.

DNA library QC results are available in the MetricsOutput.tsv file. Refer to Metrics Output for details.

RNA Sample QC

The input for RNA Library QC is RNA alignment. Metrics and guideline thresholds can be found in the MetricsOutput.tsv file. Refer to Metrics Output for details.

• To avoid failing RNA samples unnecessarily, Illumina does not recommend a universal threshold to determine RNA sample quality. RNA expression varies significantly across tissue types and a small panel size (55 genes), which makes normalization challenging. Tissue-specific thresholds could be considered for normalization.

General Troubleshooting on Standalone DRAGEN Server

Sample Sheet Validation Failures

In DRAGEN TruSight Oncology 500 Analysis Software, the analysis fails if a sample sheet is invalid. If an invalid sample sheet in suspected, log files can help troubleshoot a failed analysis. Use the following steps to find the log file for the sample sheet:

1. Navigate to the following location /<analysis_output>/Logs_Intermediates/SamplesheetValidation.

2. Open the SamplesheetValidation-.log file

3. Find a line with the following: SampleSheetValidationTask:NA:1 exited with return code 1 which has not been declared as a valid return code.

4. Search for errors in the sample sheet validation log and compare with the guidelines and warnings in Sample Sheet Requirements and the following tables.

General troubleshooting for a failed sample sheet:

Valid indexes for assay and instrument combinations:

Troubleshooting BCL issues:

Troubleshooting FASTQs issues:

Other Troubleshooting Tips

Troubleshooting on ICA

In addition to TSO 500 managed sample sheet validations, ICA managed TSO 500 errors include the following:

Refer to for more information.

Splice Variant VCF

The splice variant VCF contains all candidate splice variants targeted by the analysis panel identified by the RNA analysis pipeline. You can apply the following filters for each variant call:

Refer to the headers in the output for more information about each column.

Splice Variant Annotated JSON

If available, each splice variant is annotated using the Illumina Annotation Engine. The following information is captured in the JSON:

• HGNC Gene

• Transcript

• Exons

• Introns

• Canonical

• Consequence

All Fusions CSV

The all fusions CSV file contains all candidate fusions identified by the DRAGEN RNA pipeline. Two output columns in the file describe the candidate fusions: Filter and KeepFusion.

The following table describes the semicolon-separated output found in the Filter columns. The output is either a confidence filter or information only as indicated. If none of the confidence filters are triggered, the Filter column contains the output PASS, else it contains the output FAIL.

Filter Column Output

The KeepFusion column of the output has a value of TRUE when none of the confidence filters are triggered.

Refer to the headers in the output for more information about each column.

Fusion Columns

When using Microsoft Excel to view this report, genes that are convertible to dates (such as MARCH1 automatically convert to dd-mm format (1 Mar) by Excel. The following are fusion allow list genes:

• ABL1

• AKT3

• ALK

• AR

• AXL

• BCL2

• BRAF

• BRCA1

• BRCA2

• CDK4

• CSF1R

• EGFR

• EML4

• ERBB2

• ERG

• ESR1

• ETS1

• ETV1

• ETV4

• ETV5

• EWSR1

• FGFR1

• FGFR2

• FGFR3

• FGFR4

• FLI1

• FLT1

• FLT3

• JAK2

• KDR

• KIF5B

• KIT

• KMT2A

• MET

• MLLT3

• MSH2

• MYC

• NOTCH1

• NOTCH2

• NOTCH3

• NRG1

• NTRK1

• NTRK2

• NTRK3

• PAX3

• PAX7

• PDGFRA

• PDGFRB

• PIK3CA

• PPARG

• RAF1

• RET

• ROS1

• RPS6KB1

• TMPRSS2