Only this pageAll pages
Powered by GitBook
Couldn't generate the PDF for 132 pages, generation stopped at 100.
Extend with 50 more pages.
1 of 100

DRAGEN TSO 500 and TSO 500 ctDNA Analysis Software

Loading...

Loading...

Loading...

Loading...

DRAGEN TSO 500 Guides

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

DRAGEN TSO 500 ctDNA Guides

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

DRAGEN TSO 500 and TSO 500 ctDNA Analysis Software

DRAGEN TruSight™ Oncology 500 and DRAGEN TruSight™ Oncology 500 ctDNA Analysis Software support secondary analysis for the data generated by assays in the TruSight™ Oncology 500 (TSO 500) portfolio:

  • DRAGEN TruSight™ Oncology 500 Analysis Software supports the following assays, all Research Use Only (RUO):

    • TruSight Oncology 500 Assay

    • TruSight Oncology 500 High-Throughput Assay

    • TruSight Oncology 500 HRD Add-on Assay

    • TruSight Oncology 500 v2 Assay

  • DRAGEN TruSight™ Oncology 500 ctDNA Analysis Software supports the following assays, all Research Use Only (RUO):

    • TruSight Oncology 500 ctDNA Assay v1

    • TruSight Oncology 500 ctDNA v2 Assay

Depending on the version, the analysis software is available on:

  • Illumina Connected Analytics (ICA): A cloud-based secure platform for data analysis and management. Analysis setup, monitoring, and results access is facilitated via user-friendly interface of BaseSpace Sequence Hub.

  • DRAGEN server: An on-premises server that offers secondary analysis in a fraction of the time compared with a traditional CPU-based system.

  • On-board of select instruments: Enabled by a user-friendly analysis application installed on a sequencer.

This resource provides information on installation, configuration, running, troubleshooting as well as analysis algorithms of DRAGEN TruSight™ Oncology 500 and DRAGEN TruSight™ Oncology 500 ctDNA Analysis Software.

Launching Analysis

Performance Testing

The following sections describe performance testing methods.

Analytical Performance Testing

Illumina tests the analytical performance of variant calling for TruSight Oncology 500 and TruSight Oncology 500 ctDNA assays 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.

Some versions of the DRAGEN TruSight™ Oncology 500 Analysis Software and DRAGEN TruSight™ Oncology 500 ctDNA Analysis Software include results generated by features tested in silico and by beta features. Beta features have not been fully evaluated for performance, see Beta Features for more details.

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 of the DRAGEN TruSight Oncology 500 Analysis Software, variants of interest are compiled 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.

In silico tested features for DRAGEN TruSight Oncology 500 Analysis Software and DRAGEN TruSight Oncology 500 ctDNA Analysis Software are summarized in the table below.

Name
in Silico Tested Features

Beta Features

DRAGEN TruSight Oncology 500 Analysis Software also includes beta features. The features 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 was 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 produced by the DRAGEN TruSight Oncology 500 Analysis Software. Illumina will continue to evaluate beta features with intent to fully release upon completion of verification for each feature.

Beta features are summarized in the table below.

Beta feature results are included in the Combined Variant Output file and other files. However, disclaimers that the results are generated by beta features are only provided in the Combined Variant Output file.

Name
Beta Features

DRAGEN TruSight Oncology 500 Analysis Software for TruSight Oncology 500 and TruSight Oncology 500 HT (v2.1+)

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

DRAGEN TruSight Oncology 500 Analysis Software for TruSight Oncology 500 HT (v2.1+)

  • Exon-level CNVs in BRCA1 and BRCA2

DRAGEN TruSight Oncology 500 ctDNA Analysis Software (v2.1+)

  • Complex variants in genes beyond EGFR

  • Insertions and deletions > 25 bp

DRAGEN TruSight Oncology 500 Analysis Software (v2.6.2+) for :

  • TruSight Oncology 500 + HRD Add-on

  • TruSight Oncology 500 v2

  • Absolute copy numbers (ACN)

  • Gene-level loss of heterozygosity (LOH) events

DRAGEN TruSight Oncology 500 Analysis Software (v2.5.2 - 2.6.1) for:

  • TruSight Oncology 500 + HRD Add-on

  • Tumor fraction

  • Ploidy

  • Absolute copy numbers (ACN)

  • Gene-level loss of heterozygosity (LOH) events

Block List

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.

Troubleshooting

DRAGEN TSO 500 v2.5

Block List

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.

DRAGEN TSO 500 v2.6

Coverage Reports

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.

DRAGEN TSO 500 ctDNA v2.6

Getting Started

Getting Started

Launching Analysis

Run Planning

FastQ Generation

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.

FASTQ Generation

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.

Getting Started

Run Planning

Analysis Launch with NovaSeq 6000Dx Application

When using the NovaSeq 6000Dx application, DRAGEN TSO 500 analysis starts automatically after sequencing completes.

ICA Pipeline Troubleshooting

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

Error
Description

Failure type: ValueError: Could not find pipeline ID for app BCLConvert in sample sheet SampleSheet.csv

Action: Ensure StartsFromFastq field is in the [TSO500S_Settings] section, and it is not present in the [BCLConvert_Settings] Section. Refer to for more information.

Run on Multiple DRAGEN Servers

DRAGEN TruSight Oncology 500 Analysis Software can be used to run in parallel on multiple 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.

Demultiplex and Scatter

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:

Sample Sheet Introduction

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 .

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:

Auto-Launch with FASTQs generated by Standalone BCL Convert Pipeline (Start from FASTQ)

When using BSSH Run Planning to generate a sample sheet to auto-launch analysis on ICA, you must designate "Start from Fastq" to be True or False (default is False). If you choose "False", BSSH will kick off the TSO 500 pipeline normally using BCL input from the run folder.

If you choose "True" for this option, BSSH will run two ICA pipelines in sequence:

  • First, it will run the BCL Convert v3.10.9 pipeline to generate the FASTQ files

  • Second, it will kick off the TSO 500 pipeline using the FASTQ files generated above as the input

Analysis Methods

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

Analysis Pipeline Troubleshooting

Failure Type
Action

Sample Sheet Introduction

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 .

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:

Metrics Output

Metrics Output

One metrics output file is generated for the entire run. An additional file is generated for each sample (or DNA-RNA pair).

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

  • DNA library QC metrics for:

Getting Started on Illumina Connected Analytics

Prerequisites

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

  • An ICA account with a valid subscription

Standalone DRAGEN Server - Troubleshooting

Failure Type
Actions

Run Planning

Here are the articles in this section:

Getting Started on Illumina Connected Analytics

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

Block List

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

Analysis Launch on ICA

Methods for Launching Analysis

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

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

Metrics Output

Metrics Output

One metrics output file is generated for the entire run. An additional file is generated for each sample (or DNA-RNA pair).

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

  • DNA library QC metrics for:

Determine how many DRAGEN servers are available to run.

  • Run demultiplex

    1. on a single DRAGEN server; or

    2. if the flow cell was loaded with individually-addressable lanes, follow the tip below to avoid copying data across servers.

  • To run scatter for flow cells loaded with individually-addressable lanes (i.e. using the NovaSeq 6000 XP workflow), modify the sample sheet to include a subset of the lanes. For example, on an S2 flowcell, create two modified sample sheets with one containing the samples from lane 1 and the other from lane 2. This allows only the sample sheet to be modified instead of copying files between servers. This strategy would use the start from Run Folder commands without the --demultiplexOnly option. The entire run folder would need to be copied to each analysis server as demultiplexing is performed once per server.

    1. Transfer the FASTQ folder output from the original DRAGEN server to additional servers (not needed if option 2b was used).

      • Find the FASTQ folder at: Logs_Intermediates/FastqGeneration.

    Moving or modifying files during an analysis may cause the analysis to fail or provide incorrect results.

    Analysis

    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.

    Gather Results

    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 Multi-node Analysis

    Step
    Command

    Demultiplexing

    DRAGEN_TSO500_2.6.0.sh --resourcesFolder /staging/illumina/DRAGEN_TSO500/resources --hashtableFolder /staging/illumina/DRAGEN_TSO500/ref_hashtable --runFolder /staging/{RunFolderName} --analysisFolder /staging/{DemultiplexAnalysisFolderName} --demultiplexOnly --sampleSheet /staging/illumina/{SampleSheetName}

    Analysis (one server)

    DRAGEN_TSO500_2.6.0.sh --resourcesFolder /staging/illumina/DRAGEN_TSO500/resources --hashtableFolder /staging/illumina/DRAGEN_TSO500/ref_hashtable --fastqFolder /staging/{DemultiplexAnalysisFolderName}/Logs_Intermediates/FastqGeneration/ --analysisFolder /staging/{Node1AnalysisFolderName} --sampleSheet /staging/illumina/{SampleSheetName} --sampleOrPairIDs Pair_1,Pair_2

    Analysis (additional servers)

    DRAGEN_TSO500_2.6.0.sh --resourcesFolder /staging/illumina/DRAGEN_TSO500/resources --hashtableFolder /staging/illumina/DRAGEN_TSO500/ref_hashtable --fastqFolder /staging/{DemultiplexAnalysisFolderName}/Logs_Intermediates/FastqGeneration/ --analysisFolder /staging/{Node1AnalysisFolderName} --sampleSheet /staging/illumina/{SampleSheetName} --sampleOrPairIDs Pair_3

    Gather

    DRAGEN_TSO500_2.6.0.sh --analysisFolder /Gathered_Results --resourcesFolder staging/illumina/DRAGEN_TSO500/resources --runFolder /staging/{RunFolderName}/--sampleSheet /staging/illumina/{SampleSheetName} --gather /Demultiplex_Output /Node1_Output /Node2_Output

    DNA Alignment and Error Correction
  • Small Variant Calling and Filtering

  • Copy Number Variant (CNV) Calling

  • BRCA Large Rearrangements

  • Annotation

  • Tumor Mutational Burden (TMB) Scoring

  • Microsatellite Instability (MSI) Status

  • Genomic Instability Score (GIS)

    • Tumor purity (beta)

    • Ploidy (beta)

  • Absolute Copy Number (beta)

  • Gene-level Losss of Heterozygosity (LOH) (beta)

  • Contamination Detection

  • RNA Analysis

    • Downsampling

    • Read Trimming

    • Alignment

    • Fusion Calling and Filtering

    • Splice Variant Calling

    • Fusion Merging

    • Annotation

  • Quality Control

    • Run QC

    • DNA Sample QC

    • RNA Sample QC

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

    A positive balance of iCredits for data storage

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

    A positive balance of iCredits for data storage

    Refer to Software Set Up for information on how to register ICA subscription and iCredits.

    KMT2B

  • KMT2C

  • KMT2D

  • chrY

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

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

    One or more pipeline steps fail

    - Open the log file ./<AnalysisFolder>/Logs_Intermediates/pipeline_trace.txt. This log file displays each pipeline step run by the Nextflow workflow manager software. If a step fails, it is marked as FAILED. Each step generates log files that are stored in step-specific subfolders in the Logs_Intermediates folder. Review the log files in the relevant Logs_Intermediates folder for the step to identify potential sources of error. - Open the errors folder ./<AnalysisFolder>/errors. The workflow creates an error file, error_<NameOfFailedStep>.json, for each step that failed during analysis. For steps that fail per sample, there is a separately labeled file for each sample that failed each step error_<NameOfFailedStep>_<SampleIDIfRelevant>.json. These files contain the command and stdout and stderr from the step.

    One or more samples are missing results for one or more variant types

    Open the combined metrics output results file ./<AnalysisFolder>/Results/<PairId>/MetricsOutput.tsv. If a sample fails an analysis step, the Pair ID that contains the sample shows the failure under FAILED_STEPS in the Analysis Status section, and COMPLETED_ALL_STEPS shows as False. If available, review the individual log files for the failed steps under ./<AnalysisFolder>/Logs_Intermediates to identify potential sources of error.

    Single exon (single probe) genes are still reported in the CNV VCF file, but not the CNV TSV file

    No action needed; software is working as expected.

    For v2.6.1 and below, CNV events for genes with low probe coverage are not emitted to the Copy Number Variants section of our CombinedVariantOutput.tsv. However, you can still find these events in the cnv.vcf.gz.

    Due to the low probe coverage, accurate CNV calling has not been validated and as such they are emitted as REF These events are no longer included in the VCF starting in v2.6.2.

    Testing of cell lines, contrived samples and commercial controls does not return expected results

    Review recommendations for using these samples types here.

    The output file directory contains information from previous analyses

    If this issue is seen, specify a new target output folder and repeat analysis To prevent this issue: specify an empty directory before starting analysis

    Multinode Gather

    If the following error appears, check if the sample or pair ID was included multiple times during separate node analysis runs, before being gathered together. If the error exists, rerun one of the analyses without the duplicate and reattempt gathering. ERROR:Gather:Destination file ... already exists - check if the same sample ID is in multiple input folders

    Sample Sheet Requirements

    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 NovaSeq 6000Dx Run Set Up 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 Planning" 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.

    Illumina Connected Software - Sample Sheet

    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

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

    Illumina Connected Software - Sample Sheet
    Sample Sheet Introduction
    Sample Sheet Requirements
    Sample Sheet Creation in BaseSpace Run Planning tool
    NovaSeq 6000Dx Run Set Up
    Sample Sheet Templates

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

    For the data generated by NextSeq 1000/2000 and NextSeq X, only manual option for launching analysis on ICA is available. The analysis can only start from FASTQs files.

    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

    Auto-launch

    Please note. Run QC metrics are generated inside the TSO 500 pipeline from interop files in the run folder. When starting TSO 500 from FASTQ (via auto-launch or manual launch), Run QC metrics will not be generated.

    When the auto-launched analysis completed, you will see the analysis result shows results from both the BCL Convert pipeline and the TSO 500 pipeline, like below:

    Installation of NovaSeq 6000Dx TSO 500 Analysis Application

    Instructions to install DRAGEN TSO 500 Analysis Application on NovaSeq 6000Dx (RUO mode).

    Prerequisites

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

    • Illumina Run Manager installed by Illumina support personnel

    • TSO500Combined and TSO500_HRD licenses installed by Illumina support personnel

      • TSO500Combined and TSO500_HRD licenses are pre-installed in manufacturing since February 2025 and will need to be installed only for instruments purchased prior to that

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

    Installation Instructions

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

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

    It is recommended to use a command line tool like wget or curl to download the file rather than pasting the link into the web browser bar. For example:

    curl -o {filename} "{link}"

    wget -O {filename} '{link}'

    Where the file name is the name of either DRAGEN TSO 500 Analysis Application file or DRAGEN ires file, and the link is provided by Illumina Customer Care.

    1. Installation package contents The installation package contains the following:

    Software
    Version
    Type
    Dragen version installed
    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

    \

    Contamination

    The contamination score evaluates presence of sample-to-sample contamination. The algorithm uses common germline SNPs in the homozygous state expected to have variant allele frequencies (VAF) at 0% and 100%. In contaminated samples, the VAFs shift away from the expected values allowing the detection of sample-to-sample contamination.

    The contamination score can detect sample-to-sample contamination greater than or equal to 2% (more than 2% of DNA input is coming from the non-source sample)

    Contamination Score Calculation

    The contamination score is calculated using the SNP error file and Pileup file that are generated during the small variant calling, as well as the TMB trace file. The algorithm includes the following steps:

    • All positions that overlap with a pre-defined set of common SNPs that have variant allele frequencies of < 25% or > 75% are collected (only SNP are considered, indels are excluded)

    • Variants in CNV events are removed using a clustering method

    • The likelihood that the positions are an error or a real mutation is calculated by:

      • Estimating the error rate per sample

    CONTAMINATION_SCORE = sum(log10(P(vi is False Positive)))

    Contamination Score Interpretation

    • The contamination score is output in the metrics output file, MetricsOutput.tsv

    • If a contamination score is equal or below 1457 (the upper specification limit provided in the "USL Guideline" field in the metrics output file, see ), the sample has less than 2% sample-to-sample contamination.

    • If a contamination score is above 1457, the sample has more than 2% sample-to-sample contamination. In this case, an estimation of the contamination can be obtained from the PCT_CONTAMINATION_EST metric, see more details on the . As noted, PCT_CONTAMINATION_EST is not valid unless the contamination score exceeds 1457.

    Samples with highly rearranged genomes (HRD samples) can have variants with VAFs that shift away from the expected frequencies due to genomic rearrangement, which can lead to false-positive contamination scores

    • Visual examination can help determine if a shift of VAFs is due to true contamination

    How to build a VAF plot for visual examination

    1. To build a VAF plot, use the {Sample_ID}.tmb.trace.csv file. Filter to only germline variants (for example, by using tags "Germline_DB" and "Germline_Proxi" in the column "Status") and use values in the VAF column.

    2. Select Scatter from the Charts menu

    3. Review plot as described above analyzing whether variants are scattered or clustered around 50% and 100% VAF

    Analysis Launch on ICA

    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.

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

    Resources used by ICA Analyses

    EC2 Instance Support

    As of DRAGEN TSO500 v2.6.2, ICA pipelines are able to run on F2 instance type nodes (in addition to F1, when available).

    For additional details on performance and availability of supported instance types, please see:

    BCL Convert in parallel by lane

    As of DRAGEN TSO500 v2.6.2, BCL Convert in ICA pipeline is parallelized by lane. A node is created to convert BCL to fastq from a particular lane. After demultiplex is complete for all lanes, the fastq files are then aggregated per sample. On average, the turn-around time for BCL Convert per lane is ~35mins.

    RNA Expanded Metrics

    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.

    Metric
    Description
    Units

    PCT_CHIMERIC_READS

    Percentage of reads that are aligned as two segments which map to nonconsecutive regions in the genome.

    %

    PCT_ON_TARGET_READS

    Percentage of reads that cross any part of the target region versus total reads. A read that partially maps to a target region is counted as on target.

    %

    SCALED_MEDIAN_GENE_COVERAGE

    NovaSeq 6000Dx App Troubleshooting

    Failure Type
    Action Taken

    Analysis is unable to start, hanging indefinitely after installing another app with incompatible DRAGEN version. For detailed scenario, see:

    The following steps need to be executed by a user with root access to the server that is paired with the NovaSeq 6000Dx:

    1. Locate the DRAGEN .run file on the server

      1. The file should be under the following path with the following name pattern: /staging/data/install/dragen/illumina.drageninstaller@{dragen_version}/dragen-{dragen_version}..run, where dragen_version is the version of DRAGEN needed for the application

        1. For example: /staging/data/install/dragen/[email protected]/dragen-3.10.19-11.multi.el8.x86_64.run

    Same problem as above, but running an app using a lower version of DRAGEN (ie 2.6.0 using DRAGEN 3.10.17)

    Same instructions as above

    Combined Variant Output

    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)

    • Exon-level CNVs

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

    Analysis Details
    Sequencing Run Details

    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.

    RNA Analysis Methods

    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.

    Note: In v2.6.2 the rna_repeats_hg19.bed file was been updated to include NPM1 to increase sensitivity for that gene (previously this list included only DUX4, SEPT14, CIC, and PSPH).

    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.

    HRD and GIS Outputs

    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.

    Metric
    Description

    Genomic Instability Score (GIS)

    Proprietary Genomic Instability Score (GIS) indicating level of genomic instability in sample genome. Combination of Loss of Heterozygosity (LOH), Telomeric allelic imbalance and Large-scale State Transitions (LST) scores. The GIS scores provided by TruSight Oncology 500 HRD show good correlation (R2= 0.98) with Myriad Genetics GIS however they are not identical (Refer to TruSight Oncology 500 HRD Product Data Sheet Doc# M-GL-00748 for more details). GIS from alternative HRD assays should be not be considered equivalent to Illumina/Myriad GIS.

    The GIS algorithm within the TSO500 pipeline (which does not have a cell line mode due to the TSO500 pipeline being non-configurable) is only intended for FFPE samples. Cell line samples will not accurately report GIS results as the tumor fraction (>90%) is too high to reliably distinguish tumor vs germline variants.

    HRD Metrics Included in Metrics Output File

    Metric
    Description
    Section in Metrics Output

    Contrived and Cell Line Sample Considerations

    Using cell lines or contrived samples for validation or as positive controls may result in inconsistent or unusual results depending on how the samples were constructed. Illumina recommends using commercial controls only for the variant class they are intended for. For example, if the sample is contrived for CNVs but not explicitly for SNV, MSI, TMB, or fusions, we would not recommend using this sample for validation or as a positive control for SNV, MSI, TMB, or fusions.

    Demo Data for Commercial Controls

    Illumina has provided demo data of some common commercial controls on BaseSpace Sequence Hub on various flow cells:

    Combined Variant Output

    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)

    RNA Analysis Methods

    Refer to 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.

    Run on Multiple DRAGEN Servers

    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.

    NovaSeq 6000Dx Run Set Up

    The following instructions describe steps to set up a run on NovaSeq 6000Dx Analysis Application.

    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”

    Input Checks

    Items to check before submitting your analysis

    Input Validation Steps

    In addition to sample sheet validation, before starting an analysis, the software performs the following checks:

    • Resource bundle integrity

    HRD and GIS Outputs

    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.

    Metric
    Description

    The GIS algorithm within the TSO500 pipeline (which does not have a cell line mode due to the TSO500 pipeline being non-configurable) is only intended for FFPE samples. Cell line samples will not accurately report GIS results as the tumor fraction (>90%) is too high to reliably distinguish tumor vs germline variants.

    Installation of NovaSeq 6000Dx TSO 500 ctDNA Analysis Application

    Instructions to install DRAGEN TSO 500 ctDNA Analysis Application on NovaSeq 6000Dx (RUO mode)

    Prerequisites

    The following requirements must be met to install and run DRAGEN TruSight Oncology 500 ctDNA Analysis Application on NovaSeq 6000Dx:

    • A NovaSeq 6000Dx sequencing instrument with Illumina Run Manager v1.6.2 installed and paired with DRAGEN Server v4.

    Contamination

    The contamination score evaluates presence of sample-to-sample contamination. The algorithm uses common germline SNPs in the homozygous state expected to have variant allele frequencies (VAF) at 0% and 100%. In contaminated samples, the VAFs shift away from the expected values allowing the detection of sample-to-sample contamination.

    The contamination score can detect sample-to-sample contamination greater than or equal to 2% (more than 2% of DNA input is coming from the contaminant)

    Sample Sheet Introduction

    Overview

    A sample sheet is required for each analysis with DRAGEN TruSight Oncology 500 ctDNA 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 ctDNA Analysis Software is compatible with the sample sheet v2. For general information on the sample sheet v2, refer to .

    The sample sheet includes a list of samples and their index sequences, along with additional information required to run DRAGEN TruSight Oncology 500 ctDNA Analysis Software. For example, the library prep kit used for analysis will need to be listed in 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:

    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.

    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:

    Analysis Details
    Sequencing Run Details

    - Pair ID - DNA Sample ID (if DNA is run) - RNA Sample ID (if RNA is run)

    - Library Prep Kit - Output Date - Output Time - Module Version - Pipeline Version (Docker image version #)

    - Run Name - Run Date - DNA Sample Index ID (if DNA is run) - RNA Sample Index ID (if RNA is run) - Instrument ID - Instrument Control Software Version - Instrument Type

    - Instrument Platform

    - [HRD] Sample feature

    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 - All variants with the FILTER field marked as PASS and ALT field is <DUP or <DEL> in cnv.vcf file from DRAGEN DNA call or abcn_annotated.vcf from GIS step(HRD assay))are present in the combined variant output:

      • Gene Name.

      • Fold Change.

      • Copy Number Variant (<DUP or <DEL>) .

      • Absolute Copy Number (HRD Assay) – This value is included only if the HRD assay was run and the sample passed HRD sample QC. If the HRD assay failed QC , the Absolute Copy Number will be reported as NA, and the CNVs will be sourced from the DRAGEN DNA call (cnv.vcf).

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

    Moving or modifying files during an analysis may cause the analysis to fail or provide incorrect results.

    To sequence runs on multiple DRAGEN servers using the NovaSeq 6000 XP workflow, modify the sample sheet to include a subset of the lanes. For example, on an S2 flowcell, create two modified sample sheets with one containing the samples from lane 1 and the other from lane 2. This allows only the sample sheet to be modified instead of copying files between servers. This strategy would use the start from Run Folder commands without the --demultiplexOnly option. The entire run folder would need to be copied to each analysis server as demultiplexing is performed once per 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

    Step
    Command

    Demultiplexing

    DRAGEN_TSO500.sh --resourcesFolder /staging/illumina/DRAGEN_TSO500/resources --hashtableFolder /staging/illumina/DRAGEN_TSO500/ref_hashtable --runFolder /staging/{RunFolderName} --analysisFolder /staging/{DemultiplexAnalysisFolderName} --demultiplexOnly --sampleSheet /staging/illumina/{SampleSheetName}

    Analysis

    (one server)

    DRAGEN_TSO500.sh --resourcesFolder /staging/illumina/DRAGEN_TSO500/resources --hashtableFolder /staging/illumina/DRAGEN_TSO500/ref_hashtable --fastqFolder /staging/{DemultiplexAnalysisFolderName}/Logs_Intermediates/FastqGeneration/ --analysisFolder /staging/{Node1AnalysisFolderName} --sampleSheet /staging/illumina/{SampleSheetName} --sampleOrPairIDs Pair_1,Pair_2

    Analysis (additional servers)

    DRAGEN_TSO500.sh --resourcesFolder /staging/illumina/DRAGEN_TSO500/resources --hashtableFolder /staging/illumina/DRAGEN_TSO500/ref_hashtable --fastqFolder /staging/{DemultiplexAnalysisFolderName}/Logs_Intermediates/FastqGeneration/ --analysisFolder /staging/{Node1AnalysisFolderName} --sampleSheet /staging/illumina/{SampleSheetName} --sampleOrPairIDs Pair_3

    Gather

    DRAGEN_TSO500.sh --analysisFolder /Gathered_Results --resourcesFolder staging/illumina/DRAGEN_TSO500/resources --runFolder /staging/{RunFolderName}/--sampleSheet /staging/illumina/{SampleSheetName} --gather /Demultiplex_Output /Node1_Output /Node2_Output

    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

    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

      3. TruSight Oncology 500 v2

    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.

      Note: If the sample is not paired, this field is still required. In this case, one could choose to use the same value for sample ID and pair ID (as long as your pair IDs remain unique in the run); or, use a value that fits with your chosen schema.

    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.

    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.

    Median of median base coverage of genes scaled by length. An indication of median coverage depth of genes in the panel.

    Count

    TOTAL_PF_READS

    Total number of reads passing filter.

    Count

    GENE_MEDIAN_COVERAGE

    The median coverage depth of all genes in the panel.

    Count

    GENE_ABOVE_MEDIAN_CUTOFF

    Number of genes above the median coverage cutoff.

    Count

    PER_GENE_MEDIAN_COVERAGE

    Median deduped coverage across each gene (available in Logs_Intermediates only)

    Count

    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

  • Exon-level CNVs - Exon-levels CNVs must meet the following conditions:

    • BRCA1 or BRCA2 contains at least one affected exon.

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

  • - Pair ID - DNA sample ID (if DNA is run) - RNA sample ID (if RNA is run) - Output date - Output time - Module version - Pipeline version (Docker image version #)

    - Run name - Run date - DNA sample index ID (if DNA is run) - RNA sample index ID (if RNA is run) - [HRD] Sample feature - Instrument ID - Instrument control software version - Instrument type - RTA version - Reagent cartridge lot number

    Manual launch
    Illumina Connected Analytics support site page
    BaseSpace Sequence Hub support site page
    F2 Support on ICA
  • Execute the DRAGEN run file by typing the appropriate command into the server terminal similar to the following:

    1. "./{COMPLETE_RUN_FILE_PATH}/dragen-{dragen_version}..run

  • Navigate to the DRAGEN page from the IRM menu to see that the installed version of DRAGEN is as intended. If the version has not updated, navigate away from the DRAGEN page and then return to the DRAGEN page.

  • Analysis Launch with NovaSeq 6000Dx Application
    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.

    RNA Output

    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 ctDNA 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 ctDNA Analysis Software.

    Illumina Connected Software - Sample Sheet

    Counting mutation support

  • Counting total depth

  • The contamination score is calculated as the sum of all the log likelihood scores across the pre-defined SNP positions whose minor allele frequency is <25% in the sample and not likely due to CNV events:

  • Metrics Output page
    DNA Expanded Metrics page
    Visual investigation of VAFs across the genome can help determine if a shift of VAFs is due to true contamination

    PCT_TARGET_HRD_50X

    Percent of HRD probe SNP panel covered by at least 50X coverage

    DNA Library QC Metrics for GIS

    EXCESSIVE_TF

    EXCESSIVE TF indicates if there is excessive tumor content in sample. Troubleshooting: Samples with pure tumor fraction >90% are outside the design for GIS estimation (this includes pure tumor cell lines)

    DNA Library QC Metrics for GIS

    ALLELE_DOSAGE_RATIO

    Proprietary Myriad Genetics estimate of b-allele dosage based on b-allele noise/signal ratio. B-Allele noise is correlated with coverage; lower coverage samples will have higher noise. B-allele signal is also correlated with tumor fraction; a higher tumor fraction produces a higher signal for b-allele sites. Samples with lower tumor fraction and higher amount of noise (or lower coverage) will have higher Allele Dosage Ratio. The upper limit of the score is 50, therefore any sample with 50 Allele Dosage Ratio can be assumed to have tumor fraction close to zero and typically has a GIS = 0.

    DNA Expanded Metrics

    MEDIAN_TARGET_HRD_COVERAGE

    Median target fragment coverage across all target positions in the genome. Coverage is the total number of non-duplicate pair alignments that overlap.

    DNA Expanded Metrics

    The installation is complete once the DRAGEN version as list in table above is in the install version(s) list

    DRAGEN TSO 500 v2.6.0

    2.6.0

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

      • MD5sum:

        After Feb 5, 2025: 608bde0f63bc1ae54e746e273055e749

        Before Feb 5, 2025: dc4fe5fe2fc3eca57969e978886dcedf

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

      • MD5sum: 12df06502776d8b673c73fb714dc466a

    3.10.17

    DRAGEN TSO 500 v2.6.2

    2.6.2

    • DRAGEN TSO 500 Analysis Application: DRAGEN_TSO500HRD_v2.6.2-4v3.iapp

      • MD5sum:f3d6575ef068fbc13f1cfdc2cb9e633e

    • DRAGEN ires: drageninstaller_3.11.2-8.el8.x86_64_prod.ires

      • MD5sum: cd980922bb3ed456ff31295ff49cb2fa

    3.11.2

    [email protected]

    The v2.6.2 app uses DRAGEN v3.11.2, which is not designed to be co-installed with earlier DRAGEN versions (e.g. v3.10.18 and below, v4.3.5 and below). When launching analysis after installing another NovaSeq 6000Dx app and its dependent version of DRAGEN (that does not support multi-version installation), the software may sporadically be unable to run. For example, users may encounter an issue if the following steps occur in order:

    1. installation of the DRAGEN TSO 500 v2.6.2 app for NovaSeq 6000Dx and its dependent DRAGEN, v3.11.2

    TSO 500 ctDNA v2: 1.5B (NovaSeq X)
  • TSO 500 ctDNA v2: 10B (NovaSeq X)

  • TSO 500 ctDNA v2: S2 (NovaSeq 6000)

  • TSO 500 v1: NextSeq 550

  • Known Limitations with Commercial Controls

    TSO 500 ctDNA v2

    Product Name
    Variant Class
    Description
    SW Version Impacted

    Seraseq ctDNA Complete Mutation Mix AF0.5%; Material Number 0710-0531

    Small Variants

    Low recall on Deletion chr17 41245586 CT>C due to a high noise region adjacent to a homoploymer. Under review to be addressed in the future SW versions.

    All

    Seraseq ctDNA Complete Mutation Mix AF0.5%; Material Number 0710-0531

    TMB

    Not recommended for TMB validation due to many small variants having VAF close to the TMB limit of detection. Small changes in preparation and dilution result in large changes in TMB scores (behavior not observed in clinical samples).

    All

    Twist cfDNA Pan-Cancer Reference Standard v2

    Fusions

    False negatives due to a known issue on high efficiently libraries.

    TSO 500 v1 and v2

    Product Name
    Variant Class
    Description
    SW Version Impacted

    Seraseq® FFPE BRCA1/2 LGR Reference Material Material Number 0730-0564

    BRCA LR

    Not recommended for LR validation due to 1) high level of noise 2) method of contriving resulting in some artifacts. We have found Seraseq BRCA 1/2 Exon Deletions DNA Mix Material Number 0730-0570 to work well.

    All

    DRAGEN license validity
  • NEW in v2.6.2! Instrument Type determination

  • Instrument type is required by the software because different instrument platforms produce output with distinct systematic noise profiles. DRAGEN TSO 500 analysis software requires instrument-specific baseline noise files. Before kicking off analysis, the software determines the instrument type in order to select which baseline files to use. This means that even when starting from FASTQ, all samples in the run must be sequenced on the same type of instrument.

    Instrument Type Determination for Baselines

    When starting analysis from BCL files, the software references the RunInfo.xml file in the Run folder to identify the sequencing instrument type. For analyses beginning with FASTQ files, the software reads the FASTQ file headers for this information. Correct baselines for variant calling are then applied based on the determined instrument type.

    For analysis starting from FASTQ files, if a mixed instrument type is detected, the software will exit with an error.

    The Combined Variant Output File will include the instrument type Combined Variant Output

    Baselines are selected based on a combination of Library Prep Kit and Instrument Type.

    • Library Prep Kit: TSO500_v2

      • Instrument Types:

        • NovaSeq 6000, NovaSeq 6000Dx, NextSeq 500, NextSeq 550: Use one set of baselines.

        • NextSeq 1000/ 2000: Use a different set of baselines.

        • NovaSeqX, NovaSeqXPlus: Use another set of baselines.

    • Library Prep Kit: TSO500 or TSO500HT

      • A single set of baselines applies to all instrument types.

    If instrument type is undetermined (ie not matching any of the below), the software will set instrument type to NA, and the baselines for NovaSeq 6000, NovaSeq 6000Dx, NextSeq 500, and NextSeq 550 will be applied.

    /Run/Instrument in RunInfo.xml or Header of the FASTQ GZ Files Starts With
    Instrument Type

    A

    NovaSeq6000

    ADX

    NovaSeq6000Dx

    NS50 or NB50 or NL50

    NextSeq500

    NS55 or NB55 or NDX

    NextSeq550

    VH

    NextSeq1k2k

    LH

    HRD Metrics Included in Metrics Output File

    Metric
    Description
    Section in Metrics Output

    PCT_TARGET_HRD_50X

    Percent of HRD probe SNP panel covered by at least 50X coverage

    DNA Library QC Metrics for GIS

    EXCESSIVE_TF

    EXCESSIVE TF indicates if there is excessive tumor content in sample. Troubleshooting: Samples with pure tumor fraction >90% are outside the design for GIS estimation (this includes pure tumor cell lines)

    DNA Library QC Metrics for GIS

    ALLELE_DOSAGE_RATIO

    Proprietary Myriad Genetics estimate of b-allele dosage based on b-allele noise/signal ratio. B-Allele noise is correlated with coverage; lower coverage samples will have higher noise. B-allele signal is also correlated with tumor fraction; a higher tumor fraction produces a higher signal for b-allele sites. Samples with lower tumor fraction and higher amount of noise (or lower coverage) will have higher Allele Dosage Ratio. The upper limit of the score is 50, therefore any sample with 50 Allele Dosage Ratio can be assumed to have tumor fraction close to zero and typically has a GIS = 0.

    DNA Expanded Metrics

    MEDIAN_TARGET_HRD_COVERAGE

    Median target fragment coverage across all target positions in the genome. Coverage is the total number of non-duplicate pair alignments that overlap.

    Genomic Instability Score (GIS)

    Proprietary Genomic Instability Score (GIS) indicating level of genomic instability in sample genome. Combination of Loss of Heterozygosity (LOH), Telomeric allelic imbalance and Large-scale State Transitions (LST) scores. The GIS scores provided by TruSight Oncology 500 HRD show good correlation (R2= 0.98) with Myriad Genetics GIS however they are not identical (Refer to TruSight Oncology 500 HRD Product Data Sheet Doc# M-GL-00748 for more details). GIS from alternative HRD assays should be not be considered equivalent to Illumina/Myriad GIS.

    Administrator privileges on Illumina Run Manager.

    Installation Instructions

    Perform the following steps to download and install the DRAGEN TruSight Oncology 500 ctDNA Analysis Application on NovaSeq 6000Dx installation package:

    1. Contact Illumina Customer Care for the link to the installation package. The link expires after 7 days.

    2. Download the installation package with the link provided in the email from Illumina Customer Care. The installation package contains the following files:

      1. DRAGEN IRES file: drageninstaller_<DRAGEN_VERSION>.el8.x86_64_prod.ires

      2. Illumina Run Manager: TSO500L_v<APP_VERSION>.iapp

    3. Install the DRAGEN version using the IRES file.

      1. Log into Illumina Run Manager as an administrator.

      2. From the Settings menu, select DRAGEN.

      3. Select Add DRAGEN Installer.

    4. Install the Illumina Run Manager-compatible application.

      1. Log into Illumina Run Manager as an administrator.

      2. From the left-hand menu, select Applications.

      3. Select the RUO tab, select Install Application, and then select the IAPP file to install the application.

    External Storage Configuration

    Perform the following steps to specify a location to store analysis results:

    1. Log into Illumina Run Manager as an administrator.

    2. From the Settings menu, select External Storage for Analysis Results.

    3. Configure the following parameters:

      1. Server Location: The path of the preferred output file location. A change to the server location may prompt you to enter the domain, user name, and password to the new server location.

        1. In addition to storing the analysis results from any sequencing runs, this location contains the input data created when setting up runs. Make sure that the server location has sufficient storage space for your run.

      2. Encryption—Select Require encryption during file transfer.

    4. Select Save to preserve the changes to the external storage output parameters.

    The v2.6.3 app uses DRAGEN v3.11.2, which is not designed to be co-installed with earlier DRAGEN versions (e.g. v3.10.18 and below, v4.3.5 and below). When launching analysis after installing another NovaSeq 6000Dx app and its dependent version of DRAGEN (that does not support multi-version installation), the software may sporadically be unable to run. For example, users may encounter an issue if the following steps occur in order:

    1. installation of the DRAGEN TSO 500 ctDNA v2.6.3 app for NovaSeq 6000Dx and its dependent DRAGEN, v3.11.2

    2. installation of the DRAGEN TSO 500 ctDNA v2.6.1 app* for NovaSeq 6000Dx and its dependent DRAGEN, v3.10.18

    3. analysis is initiated using DRAGEN TSO 500 ctDNA v2.6.3 app

    *or any other app requiring an incompatible DRAGEN version. See for DRAGEN co-installation compatibility.

    See Troubleshooting section for a workaround.

    Contamination Score Calculation

    The contamination score is calculated using the SNP error file and Pileup file that are generated during the small variant calling, as well as the TMB trace file. The algorithm includes the following steps:

    • All positions that overlap with a pre-defined set of common SNPs that have variant allele frequencies of < 25% or > 75% are collected (only SNP are considered, indels are excluded)

    • Variants in CNV events are removed using a clustering method

    • The likelihood that the positions are an error or a real mutation is calculated by:

      • Estimating the error rate per sample

      • Counting mutation support

      • Counting total depth

    • The contamination score is calculated as the sum of all the log likelihood scores across the pre-defined SNP positions whose minor allele frequency is <25% in the sample and not likely due to CNV events:

    CONTAMINATION_SCORE = sum(log10(P(vi is False Positive)))

    Contamination Score Interpretation

    • The contamination score is output in the metrics output file, MetricsOutput.tsv

    • If a contamination score is equal or below 1457 (the upper specification limit provided in the "USL Guideline" field in the metrics output file, see Metrics Output page), the sample has less than 2% sample-to-sample contamination.

    • If a contamination score is above 1457, the sample has more than 2% sample-to-sample contamination. In this case, an estimation of the contamination can be obtained from the PCT_CONTAMINATION_EST metric, see more details on the DNA Expanded Metrics page. As noted, PCT_CONTAMINATION_EST is not valid unless the contamination score exceeds 1457.

    Samples with highly rearranged genomes (HRD samples) can have variants with VAFs that shift away from the expected frequencies due to genomic rearrangement, which can lead to false-positive contamination scores

    • Visual examination can help determine if a shift of VAFs is due to true contamination

    Visual investigation of VAFs across the genome can help determine if a shift of VAFs is due to true contamination

    How to build a VAF plot for visual examination

    1. To build a VAF plot, use the {Sample_ID}.tmb.trace.csv file. Filter to only germline variants (for example, by using tags "Germline_DB" and "Germline_Proxi" in the column "Status") and use values in the VAF column.

    2. Select Scatter from the Charts menu

    3. Review plot as described above analyzing whether variants are scattered or clustered around 50% and 100% VAF

    Auto-Launch of DRAGEN TSO 500 Analysis on ICA

    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. Import the sample sheet to the instrument and start the sequencing run. Refer to for sample sheet guidance.

      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.

    To avoid invalid sample sheet configurations, Illumina recommends using BaseSpace Run Planning tool to generate sample sheets. Using an invalid sample sheet can result in failed runs and analyses.

    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.

    Refer to the for information on setting up a BaseSpace Sequence Hub project.

    Requeue Analysis

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

    Refer to the for more information on requeuing an analysis.

    Minimum Storage Requirements on ICA

    Sequencing System
    Minimum Disk Space (Gb)

    Refer to the for information on how to manage accounts and subscriptions.

    Guided Examples

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

    Analysis Launch on Standalone DRAGEN Server

    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 for input requirements.

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

    Before running the analysis, confirm that the output directory for the software to write to is empty and does not include results of previous analyses.

    Storage Requirements

    For optimal performance, run analysis on data stored locally on the DRAGEN server. Analysis of data stored on network-attached storage (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:

    Sequencing System
    Run Folder Output (Gb)
    Analysis Output (Gb)
    Minimum Disk Space (Gb)

    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.

    Moving or modifying files during an analysis may cause the analysis to fail or provide incorrect results.

    Analysis Methods

    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

    • Quality Control

      • Run QC

      • DNA Sample QC

      • RNA Sample QC

    RNA Expanded Metrics

    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.

    Metric
    Description
    Units

    PCT_CHIMERIC_READS

    Percentage of reads that are aligned as two segments which map to nonconsecutive regions in the genome.

    %

    PCT_ON_TARGET_READS

    Percentage of reads that cross any part of the target region versus total reads. A read that partially maps to a target region is counted as on target.

    %

    SCALED_MEDIAN_GENE_COVERAGE

    Sample Sheet Templates

    Sample Sheet templates for TSO 500 v2.5.x standalone DRAGEN server and ICA manual launch analysis can be found in the table below. For auto-launch compatible sample sheets, use BaseSpace Run Planner.

    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.

    For interactive run planning or to create a sample sheet for ICA Auto-launch, use BaseSpace Run Planner to create valid sample sheets for either local or cloud analysis. To set up a run in BaseSpace run planner, refer to Sample Sheet Creation in BaseSpace Run Planner.

    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:

    Assay
    Instrument
    Assay Workflow
    File

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

    Sample Sheet Troubleshooting

    General troubleshooting for a failed sample sheet:

    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.

    Auto-Launch of DRAGEN TSO 500 Analysis on ICA

    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.

    Manual Launch of DRAGEN TSO 500 Analysis on ICA

    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 .

    Sample Sheet Templates

    Sample Sheet templates for TSO 500 standalone DRAGEN server and ICA manual launch analysis can be found in the table below. For auto-launch compatible sample sheets, use BaseSpace Run Planner.

    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.

    For interactive run planning or to create a sample sheet for ICA Autolaunch, use to create valid sample sheets for either local or cloud analysis. To set up a run in BaseSpace run planner, refer to .

    Users can visit the 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:

    Analysis Launch on Standalone DRAGEN Server

    Start the DRAGEN TruSight Oncology 500 Analysis Software with the DRAGEN_TSO500.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 . 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.

    Introduction to DRAGEN TSO 500 ctDNA Analysis Software v2.6

    The Illumina DRAGEN TruSight Oncology 500 (TSO 500) ctDNA Analysis Software supports analysis for DNA libraries that are isolated from plasma and prepared using TruSight Oncology 500 ctDNA v2 and v1 assays. The software, which can be run on the DRAGEN Server, on Illumina Connected Analytics, and as an analysis application on NovaSeq 6000Dx, produces a variant call file (VCF) for small variants. Other outputs include tumor mutational burden (TMB), a Jensen-Shannon divergence (sum JSD) score that can be used for evaluating microsatellite instability (MSI) status, files with copy number variants (CNV), fusions as well as coverage reports.

    The secondary analysis software starts from a sequencing run folder containing base call files (BCL) or from FASTQ files staged in a FASTQ folder.

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

    The software is optimized for analyzing sequencing outputs generated by the TruSight Oncology 500 ctDNA v2 and v1 assays. Modification might lead to inaccurate data and is a violation of the .

    Manual Launch of DRAGEN TSO 500 Analysis on ICA

    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 .

    Getting Started on Illumina Connected Analytics

    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. Refer to the for information on how to register ICA subscription and iCredits.

    The v2.6.2 app uses DRAGEN v3.11.2, which is not designed to be co-installed with earlier DRAGEN versions (e.g. v3.10.18 and below, v4.3.5 and below). When launching analysis after installing another NovaSeq 6000Dx app and its dependent version of DRAGEN (that does not support multi-version installation), the software may sporadically be unable to run. For example, users may encounter an issue if the following steps occur in order:

    1. installation of the DRAGEN TSO 500 v2.6.2 app for NovaSeq 6000Dx and its dependent DRAGEN, v3.11.2

    Duplicate Marking
  • Fusion Calling

  • RNA Fusion Filtering

  • Splice Variant Calling

  • Annotation

  • Fusion Merging

  • installation of the DRAGEN TSO 500 v2.6.0 app* for NovaSeq 6000Dx and its dependent DRAGEN, v3.10.17
  • analysis is initiated using DRAGEN TSO 500 v2.6.2 app

  • *or any other app requiring an incompatible DRAGEN version. See Installation of 2.6.2 on Standalone DRAGEN Server for DRAGEN co-installation compatibility.

    See Troubleshooting section for a workaround. NovaSeq 6000Dx App Troubleshooting

    installation of the DRAGEN TSO 500 v2.6.0 app* for NovaSeq 6000Dx and its dependent DRAGEN, v3.10.17
  • analysis is initiated using DRAGEN TSO 500 v2.6.2 app

  • *or any other app requiring an incompatible DRAGEN version. See Installation of 2.6.2 on Standalone DRAGEN Server for DRAGEN co-installation compatibility.

    See Troubleshooting section for a workaround. NovaSeq 6000Dx App Troubleshooting

    Resolved 2.6.1+

    Seraseq ctDNA Reference Material v2 (multiple VAF)

    Fusions

    False negatives due to a known issue on high efficiently libraries.

    Resolved 2.6.1+

    NovaSeqXPlus

    LL

    NovaSeqX

    DNA Expanded Metrics

    Median of median base coverage of genes scaled by length. An indication of median coverage depth of genes in the panel.

    Count

    TOTAL_PF_READS

    Total number of reads passing filter.

    Count

    GENE_MEDIAN_COVERAGE

    The median coverage depth of all genes in the panel.

    Count

    GENE_ABOVE_MEDIAN_CUTOFF

    Number of genes above the median coverage cutoff.

    Count

    PER_GENE_MEDIAN_COVERAGE

    Median deduped coverage across each gene (available in Logs_Intermediates only)

    Count

    PCT_SOFT_CLIPPED_BASES

    percentage of based that were not used for alignment but retained as part of the alignment file

    %

    RNA_PCT_030_BASES

    Average percentage of bases ≥ Q30. A prediction of the probability of an incorrect base call (Q‑score). Troubleshooting: An indicator of sequencing run quality, low Q30 across all samples on a run could be the result of run overclustering.

    %

    Select the DRAGEN IRES file to begin installation.
  • Check the install versions list to verify that the appropriate DRAGEN version is listed

  • Check the RUO Applications list to verify that the appropriate application version is listed. You can configure application settings such as required users from this list.

    Installation of TSO 500 ctDNA v2.6.2, v2.6.3 on Standalone DRAGEN Server
    NovaSeq 6000Dx App Troubleshooting

    NovaSeq X 10B

    4300

    NovaSeq X 25B

    8400

    NextSeq 1000/2000

    350

    NextSeq 500/550/550Dx (RUO) HO flow cell

    350

    NovaSeq 6000/6000Dx (RUO) SP Flow Cell

    500

    NovaSeq 6000/6000Dx (RUO) S1 Flow Cell

    1100

    NovaSeq 6000/6000Dx (RUO) S2 Flow Cell

    2500

    NovaSeq 6000/6000Dx (RUO) S4 Flow Cell

    4300

    NovaSeq X 1.5B

    2000

    ICA Auto-launch Sample Sheet Requirements
    BaseSpace Sequence Hub support site page
    BaseSpace Sequence Hub support site page
    Software Registration page
    NovaSeq 6000Dx: TSO 500 Auto-launch Analysis in Cloud
    NextSeq 500/550Dx: TSO 500 and Connected Insights Auto-launch Analysis in Cloud

    800

    NovaSeq 6000/6000Dx (RUO) S2 Flow Cell

    290-460

    890-1600

    1500

    NovaSeq 6000/6000Dx (RUO) S4 Flow Cell

    800-1200

    2700-4100

    3000

    NovaSeq X 1.5B

    213

    352

    800

    NovaSeq X 10B

    1100

    1800

    3000

    NovaSeq X 25B

    1800

    3300

    4000

    NextSeq 1000/2000

    41

    107

    150

    NextSeq 500/550/550Dx (RUO) HO flow cell

    32-55

    82-85

    150

    NovaSeq 6000/6000Dx (RUO) SP Flow Cell

    85-100

    250-374

    300

    NovaSeq 6000/6000Dx (RUO) S1 Flow Cell

    164-200

    Starting from BCL Files
    Command-Line Options

    360-665

    TSO500 + HRD

    NovaSeq 6000Dx (in RUO mode)

    Standard

    TSO 500 HRD_NovaSeq6000Dx_fwd_v2 Sample Sheet Template.csv

    TSO500 HT

    NovaSeq 6000

    Standard

    TSO 500 HT_NovaSeq6000_SP_S1_S2_S4_v2 Sample Sheet Template.csv

    TSO500 HT

    NovaSeq 6000

    XP*

    TSO 500 HT_NovaSeq6000_SP_S1_S2_S4_XP_v2 Sample Sheet Template.csv

    TSO500 HT

    NovaSeq 6000Dx (in RUO mode)

    Standard

    TSO 500 HT_NovaSeq6000DxRUO_S1_S2_S4_v2 Sample Sheet Template_200037181.csv

    TSO500 HT

    NovaSeq 6000Dx (in RUO mode)

    XP*

    TSO 500 HT_NovaSeq6000DxRUO_S1_S2_S4_XP_v2 Sample Sheet Template_200037182.csv

    TSO500

    NextSeq 550

    Standard

    TSO500 + HRD

    NextSeq 550

    Standard

    TSO500 + HRD

    NovaSeq 6000

    Standard

    TSO 500 NextSeq550_v2 Sample Sheet Template.csv
    TSO 500 NextSeq550_v2 Sample Sheet Template.csv
    TSO 500 HRD_NovaSeq6000_v2 Sample Sheet Template.csv

    Open the SamplesheetValidation-.log file

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

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

  • Failure Type
    Action

    Sample Sheet not found

    Verify that SampleSheet.csv is present at the top level of the run folder with the name "SampleSheet.csv". If the sample sheet is in a different location, supply the sample sheet using the --sampleSheet option

    Indexes are not valid for the sequencer and/or assay

    See Valid indexes for assay and instrument combinations for correct indexes for the sequencer and assay.

    Pair_ID is not unique

    Pair_ID column is required in the TSO500S_Data section of the sample sheet, which pairs at most one RNA and one DNA sample together for analysis. If the sample does not have a pair, use a unique pair ID for single samples.

    Sample Sheet is not in v2 format

    Verify that the format of the sample sheet is v2. v1 sample sheet is not compatible with DRAGEN TruSight Oncology 500 Analysis Software.

    Analysis does not run

    Verify the analysis starts from the run folder, and BCLs or FASTQs are in the correct locations as outlined in Starting From BCL Files and Starting From FASTQ Files respectively.

    Indexes included in Library Prep Kit:

    Assay
    Index Set ID

    TSO 500

    • UP1-UP16

    • CP1-CP16 (DNA Only)

    TSO 500 HT

    • UDP0001–UDP0192

    TSO 500 v2

    • UDP0001–UDP0384 (v3 index when applicable)

    Troubleshooting BCL issues

    Failure Type
    Action

    Lane Column without Values

    Ensure that the column is completed. If lane is not applicable to the run, delete the column.

    Format of v2 sample sheet is incorrect

    Verify that the following sections and fields are present in the sample sheet and follow the individual rules in [BCLConvert_Settings] - SoftwareVersion - AdapterRead1 - AdapterRead2 - AdapterBehavior - MinimumTrimmedReadLength - MaskShortReads [BCLConvert_Data] - Sample_ID - index - index2 [TS0500S_Data] - Sample_ID - Index_ID - Sample_Type - Pair_ID - Sample Feature (Optional)

    HRD analysis is missing

    Verify that HRD is in the Sample Feature column in the sample sheet. Refer to for more information.

    Troubleshooting FASTQs issues

    Failure Type
    Action

    Sample_ID and/or Sample_Type is not present

    Verify that the sample sheet has columns and values for Sample_ID and Sample_Type.

    Unique sample IDs

    Verify that the Sample_IDs are unique in the sample sheet.

    Format of v2 Sample Sheet is incorrect

    Verify that the following sections and fields are present in the sample sheet and follow the individual rules in Sample Sheet Requirements. [TS0500S_Data] - Sample_ID - Index_ID - Sample_Type - Pair_ID

    - Sample Feature (Optional) Verify when FASTQs were generated using the HRD add-kit (Not available in Japan), Sample Feature is added to those DNA Samples. Refer to for more information.

    Incorrect folder structure

    Verify that the FASTQ files are in the correct structure. Refer to for more information.

    Invalid FASTQ input files

    If the FASTQs are invalid, start TSO 500 analysis from BCL files.

    HRD analysis missing

    Make sure that HRD is in the correct column in the sample sheet.

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

  • Import the sample sheet to the instrument and start the sequencing run. Refer to ICA Auto-launch Sample Sheet Requirements for sample sheet guidance.

    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.

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

  • To avoid invalid sample sheet configurations, Illumina recommends using BaseSpace Run Planning tool to generate sample sheets. Using an invalid sample sheet can result in failed runs and analyses.

    For the data generated by NextSeq 1000/2000 and NextSeq X, only manual option for launching analysis on ICA is available. The analysis can only start from FASTQs files.

    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.

    Refer to the BaseSpace Sequence Hub support site page for information on setting up a BaseSpace Sequence Hub project.

    Requeue Analysis

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

    Refer to the BaseSpace Sequence Hub support site page for more information on requeuing an analysis.

    Minimum Storage Requirements on ICA

    Sequencing System
    Minimum Disk Space (Gb)

    NextSeq 500/550/550Dx (RUO) HO flow cell

    350

    NovaSeq 6000/6000Dx (RUO) SP Flow Cell

    500

    NovaSeq 6000/6000Dx (RUO) S1 Flow Cell

    1100

    NovaSeq 6000/6000Dx (RUO) S2 Flow Cell

    2500

    NovaSeq 6000/6000Dx (RUO) S4 Flow Cell

    4300

    NovaSeq X 1.5B

    2000

    Refer to the Software Registration page for information on how to manage accounts and subscriptions.

    Guided Examples

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

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

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

    ICA standard storage is used by default as soon as the Project is saved. To connect a different storage source, set it up before creating your Project. For details and options, refer to the Storage section in Illumina Connected Analytics help.

    1. Edit Project and Add Bundle: Edit the Project and add the bundle titled, "DRAGEN TSO 500 v2.5.2 (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.

    After adding the Bundle to the Project, an example dataset becomes available in the Demo_Data folder for the Project. 

    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, desired TSO 500  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.

    Parameter Name
    Description

    User Reference

    The analysis run name.

    User Tags

    Text labels to help index the analysis.

    Notify me when task is completed

    Option to receive an email notification when analysis is complete.

    Output Folder

    The path to the analysis output folder. The default path is the project output folder.

    Entitlement Bundle

    Automatically populated from the project details.

    Sample Sheet

    Select a sample sheet in CSV format for the analysis.

    To note: Sample Sheet selection is optional if starting from a run folder, and required when submitting a FASTQ folder.

    Known Limitations

    • FASTQ Folder Naming Requirements

      • When specifying input FASTQ folder names, avoid using folder names that consist entirely of numeric characters with a leading zero, as this will cause the software to error out.

      • Unsupported naming pattern:

        • '01234' (numeric-only with leading zero)

      • Supported naming patterns:

        • '12340' (numeric without leading zero)

        • 'sample01' (alphanumeric)

        • 'A1234' (alphanumeric)

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

    Illumina Connected Analytics help
    Assay
    Instrument
    Assay Workflow
    Files

    TSO500

    NextSeq 550

    Standard

    Sample_Sheet_Template_TSO 500_i5Rev_Std_Local.csv

    TSO500 + HRD

    NextSeq 550

    Standard

    Sample_Sheet_Template_TSO 500 HRD_i5Rev_Std_Local.csv

    TSO500 + HRD

    NovaSeq 6000

    Standard

    BaseSpace Run Planner
    Sample Sheet Creation in BaseSpace Run Planner
    Sample Sheet guidelines

    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.

  • Before running the analysis, confirm that the output directory for the software to write to is empty and does not include results of previous analyses.

    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:

    Sequencing System
    Run Folder Output (Gb)
    Analysis Output (Gb)
    Minimum Disk Space (Gb)

    NextSeq 500/550/550Dx (RUO) HO flow cell

    32-55

    82-85

    150

    NovaSeq 6000/6000Dx (RUO) SP Flow Cell

    85-100

    250-374

    300

    NovaSeq 6000/6000Dx (RUO) S1 Flow Cell

    164-200

    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.

    Moving or modifying files during an analysis may cause the analysis to fail or provide incorrect results.

    Command-Line Options
    Variant reporting by DRAGEN TruSight™ Oncology 500 ctDNA Analysis Software is limited by a manifest file and a block list file. The manifest file excludes regions where the probe set does not effectively capture targets, and the block list file excludes specific positions from variant calling. TSO 500 ctDNA assay probes target at least 97% of the CDS of 474 genes. Please contact your local Illumina representative for more information if needed.

    Scope

    This resource provides information on installation, configuration, running, troubleshooting and analysis algorithms for the following software:

    Software
    Versions

    DRAGEN TruSight Oncology 500 ctDNA Analysis Software on Illumina Connected Analytics (ICA)

    • v2.6.0.25

    • v2.6.1.8

    • v2.6.3

    DRAGEN TruSight Oncology 500 ctDNA Analysis Software (for standalone DRAGEN server)

    • v2.6.0

    • v2.6.1

    • v2.6.2

    • v2.6.3

    DRAGEN TruSight Oncology 500 ctDNA Analysis Application on NovaSeq 6000Dx (uses a paired DRAGEN server)

    • v2.6.0

    • v2.6.1

    • v2.6.3

    The content is applicable to all 3 software versions unless otherwise specified. The content related to setting up and running the analysis on ICA is only relevant to software versions v2.6.0 and v2.6.1. The content related to the analysis application on NovaSeq 6000Dx is only relevant to v2.6.1.

    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 ctDNA analysis software is compatible with data generated on the Illumina instruments as summarized in the table below.

    Instrument
    Illumina Connected Analytics
    Standalone DRAGEN Server
    Paired DRAGEN server
    On-board DRAGEN

    NovaSeq 6000

    Yes (v2.6.0.25, v2.6.1.8, v2.6.3)

    Yes

    N/A

    N/A

    NovaSeq 6000Dx (RUO mode)

    Yes (v2.6.0.25, v2.6.1.8, v2.6.3)

    Yes

    Yes (v2.6.0, v2.6.1, v2.6.3)

    Navigation of Guide

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

    Workflow Diagram

    Workflow Overview
    Illumina Software Subscription Agreement

    ICA standard storage is used by default as soon as the Project is saved. To connect a different storage source, set it up before creating your Project. For details and options, refer to the Storage 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.

    After adding the Bundle to the Project, an example dataset becomes available in the Demo_Data folder for the Project. 

    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.

    Parameter Name
    Description

    User Reference

    The analysis run name.

    User Tags

    Text labels to help index the analysis.

    Notify me when task is completed

    Option to receive an email notification when analysis is complete.

    Output Folder

    The path to the analysis output folder. The default path is the project output folder.

    Entitlement Bundle

    Automatically populated from the project details.

    Sample Sheet

    Select a sample sheet in CSV format for the analysis.

    To note: Sample Sheet selection is optional if starting from a run folder, and required when submitting a FASTQ folder.

    Known Limitations

    • FASTQ Folder Naming Requirements

      • When specifying input FASTQ folder names, avoid using folder names that consist entirely of numeric characters with a leading zero, as this will cause the software to error out.

      • Unsupported naming pattern:

        • '01234' (numeric-only with leading zero)

      • Supported naming patterns:

        • '12340' (numeric without leading zero)

        • 'sample01' (alphanumeric)

        • 'A1234' (alphanumeric)

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

    Illumina Connected Analytics help
    A positive balance of iCredits for data storage. Please refer to the iCredits pricing page and storage requirements for more information.

    Minimum Storage Requirements on ICA

    The table provides guidance on the storage needs and associated ICA storage size settings.

    Sequencing System
    Minimum Disk Space (Gb)
    ICA Storage Size Value

    NextSeq 500/550/550Dx (RUO) HO flow cell

    350

    Large

    NovaSeq 6000/6000Dx (RUO) SP Flow Cell

    500

    Large

    NovaSeq 6000/6000Dx (RUO) S1 Flow Cell

    1100

    Large

    NovaSeq 6000/6000Dx (RUO) S2 Flow Cell

    2,500

    Software Registration page

    DNA Expanded Metrics

    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.

    Metric
    Description
    Troubleshooting

    TOTAL_PF_READS (count)

    Total number of non-supplementary, non-secondary, and passing QC reads after alignment to the whole genome sequence.

    Primarily driven by data output of sequencer, quality of library and balancing of library in library pool. If TOTAL_PF_READS is in line with other samples, but coverage metrics are more may suggest non-specific enrichment.

    Low values for all samples indicate a poor quality run with possible low cluster numbers or low numbers of Q30 and PF%.

    A low value for an individual sample indicates poor pooling of this library into the final pool.

    MEAN_FAMILY_SIZE (count)

    A UMI Family is a group of reads that all have the same UMI barcode. The family size is the number of reads in family. MEAN_FAMILY_SIZE is the mean of the entire population of reads assembled into UMI families. In V1 chemistry only the TSO500 manifest is considered while in V2 the TSO500 and HRD manifests are both considered.

    The mean UMI family size decreases with increased unique read numbers, and more input DNA leads to more unique reads. Conversely over sequencing of a fixed population of unique DNA molecules leads to increased family size.

    As a guide, for a good run with optimal cluster density, passing specs, even sample pooling, and good quality DNA we usually observe values <10.

    UMI family size = 1 is not ideal as it is harder to correct for errors.

    UMI family size of 2 to 5 enables efficient error correction without wasting sequencing capacity on high percentages of duplicate reads.

    MEDIAN_TARGET_COVERAGE (count)

    Introduction to DRAGEN TSO 500 Analysis Software v2.6.x

    Scope

    This resource provides information on installation, configuration, running, troubleshooting and analysis algorithms for the following software:

    • DRAGEN TruSight Oncology 500 Analysis Software v2.6.0

      • for standalone DRAGEN server

      • on Illumina Connected Analytics (ICA)

      • on NovaSeq 6000Dx v2.6.0 (uses a paired DRAGEN server)

    • DRAGEN TruSight Oncology 500 Analysis Software on Illumina Connected Analytics (ICA) v2.6.0.8

    • DRAGEN TruSight Oncology 500 Analysis Software v2.6.1 (for standalone DRAGEN server)

    • DRAGEN TruSight Oncology 500 Analysis Software v2.6.2

      • for standalone DRAGEN server

      • on Illumina Connected Analytics (ICA)

      • on NovaSeq 6000Dx (uses a paired DRAGEN server)

    The content is applicable to all software versions unless otherwise specified. The content related to setting up and running the analysis on ICA is only relevant to v2.6.0.

    Overview

    DRAGEN TruSight™ Oncology 500 Analysis Software supports data analysis for TruSight Oncology 500 Assay , TruSight Oncology 500 High-Throughput Assay, and TruSight Oncology 500 v2 Assay all 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 and RNA biomarkers.

    In addition, this software supports data analysis for TruSight Oncology 500 HRD (RUO), which enables detection of homologous recombination deficiency (HRD) through assessment of a genomic instability score (GIS). TSO 500 HRD is available as an optional library prep in TruSight Oncology 500 v2 or as an add-on kit to TruSight Oncology 500.

    TruSight Oncology 500 v2 and TruSight Oncology 500 HRD are not available in Japan.

    DNA biomarkers

    • Single nucleotide variants (SNVs)

    • Insertions

    • Deletions

    • Copy number variants (CNVs)

    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)*

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

    *Requires TruSight Oncology 500 v2 kit or TruSight Oncology 500 HRD add-on kit

    Variant reporting by DRAGEN TruSight™ Oncology 500 Analysis Software is limited by a manifest file and a . The manifest file excludes regions where the probe set does not effectively capture targets, and the block list file excludes specific positions from variant calling. TSO 500 assay probes target at least 97% of the CDS of 474 genes. Please contact your local Illumina representative for more information if needed.

    Local and Cloud Deployments

    Local analysis is available using a standalone DRAGEN server or Illumina Run Manager which is a user interface installed 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.

    Instrument
    Illumina Connected Analytics
    Standalone DRAGEN Server
    Paired DRAGEN server
    On-board DRAGEN

    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.

    Introduction to DRAGEN TSO 500 Analysis Software v2.5.x

    Scope

    This resource provides information on installation, configuration, running, troubleshooting and analysis algorithms for the following software:

    • DRAGEN TruSight Oncology 500 Analysis Software on Illumina Connected Analytics (ICA) v2.5.2

    • DRAGEN TruSight Oncology 500 Analysis Software v2.5.3 (for standalone DRAGEN server)

    • DRAGEN TruSight Oncology 500 Analysis Software v2.5.4 (for standalone DRAGEN server)

    The content is applicable to all 3 software versions unless otherwise specified. The content related to setting up and running the analysis on ICA is only relevant to v2.5.2.

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

    TruSight Oncology 500 HRD is not available in Japan

    DNA biomarkers:

    • Single nucleotide variants (SNVs)

    • Insertions

    • Deletions

    • Copy number variants (CNVs)

    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.

    *Requires TruSight Oncology 500 HRD add-on kit

    Variant reporting by DRAGEN TruSight™ Oncology 500 Analysis Software is limited by a manifest file and a . The manifest file excludes regions where the probe set does not effectively capture targets, and the block list file excludes specific positions from variant calling. TSO 500 assay probes target at least 97% of the CDS of 474 genes. Please contact your local Illumina representative for more information if needed.

    Local and Cloud Deployments

    Local analysis is available using a standalone DRAGEN server. 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 (from BCL) or manual launch (from BCLs and FASTQs), see exceptions for NextSeq 1000/2000 and NovaSeq X in the instrument compatibility tabel below.

    Instrument Compatibility

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

    Instrument
    Illumina Connected Analytics*
    Standalone DRAGEN Server
    Paired DRAGEN server
    On-board DRAGEN

    *Among v2.5.x, only DRAGEN TruSight Oncology 500 analysis software v2.5.2 is supported on ICA

    **For the data generated with NextSeq 1000/2000 and NovaSeq X, analysis can be started only from FASTQs (not from BCLs). Only manual launch is available for ICA.

    Sample Sheet Requirements

    DRAGEN TSO 500 ctDNA Analysis Software has optional and required fields that are required in addition to general sample sheet requirements. Follow the steps below to create a valid samplesheet.

    TSO 500L Data Section header changes depending on the deployment:

    • Standalone DRAGEN Server and ICA with Manual Launch: TSO500L_Data

    • ICA with Auto-launch: Cloud_TSO500L_Data

    [TSO500L_Data] Section

    Parameter
    Required
    Details

    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 . Samples sheets can be created using BaseSpace Run Planning Tool or manually by downloading and editing a sample sheet template

    To auto-launch analysis from the sequencer run folder, ensure the StartsFromFastq and SampleSheetRequested fields are set to FALSE. To auto-launch analysis from FASTQs after BCL Convert auto-launch, StartsFromFastq and SampleSheet Requested fields must be set to TRUE

    [Cloud_TSO500L_Data] Section

    Refer to for this section's requirements.

    [Cloud_TSO500L_Settings] Section

    Parameters
    Required
    Details

    [Cloud_Data] Section

    Parameter
    Required
    Details

    [Cloud_Settings] Section

    Parameter
    Required
    Details

    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 ctDNA Analysis Software sample sheet requirements, refer to the sections above.

    Mismatches between the samples and index primers can cause incorrect results due to loss of positive sample identification. Enter sample IDs and assign indexes in the sample sheet before beginning library preparation. Record sample IDs, indexes, and plate well orientation for reference during library preparation.

    [BCLConvert_Settings] Section

    Parameter Name
    Required

    Multi-Assay Flow Cells

    How to plan a run and analyze data with multiple assays loaded individually per lane on one flow cell.

    Introduction

    The NovaSeq X platform supports loading samples from different assays into different lanes within a single sequencing run. To ensure compatibility, the DRAGEN TSO 500 analysis software (v2.6.0 and above) supports sample sheets containing multiple data sections, with one section per assay (for example, TSO500S_Data and TSO500L_Data).

    This section describes how the software validates and processes multi-assay sample sheets and details the specific rules and logic applied during validation.

    Planning a Run with a Multi-Assay Flow Cell

    1. In the BaseSpace Sequence Hub home page, click "Runs" -> "New Run" -> "Run Planning".

    2. In the "Create a Run" page, select "NovaSeq X Series" as instrument platform.

    3. Provide information for the first assay until the "Run Review" page.

      • For TSO 500 or TSO 500 ctDNA assays, to auto-launch multiple pipelines at once, set "" to True

    Analyzing Data from a Multi-Assay Flow Cell

    Sample Sheet Validation

    The sample sheet validator determines which data section(s) to validate based on the active workflow type. The list of samples to process is generated only from the relevant section (for example, Solid or ctDNA). This ensures that only valid samples for the selected workflow are validated.

    The workflow’s data section may contain fewer samples than the BCLConvert_Data section. However, all samples listed in the workflow data section must exist in BCLConvert_Data section. The downstream pipeline will only process samples found in the workflow-specific data section.

    Library Prep Kits

    Multi-assay sample sheets may include multiple library prep kits values separated by semicolons (";").

    Validation Logic:

    Workflow Type
    Validation Logic
    Example of Accepted Values

    Adapter Reads

    When working with multiple assays, the "AdapterRead" field in the sample sheet may include multiple adapter sequences separated by "+". The adapter read of the selected workflow will be filled in the intermediate sample sheet.

    Override Cycles

    Override cycles are determined by the index and read length specified in the "Reads" section of the RunInfo.xml file and assay specifics. For multi-assay flow cells, the index and read length provided in RunInfo.xml should be the longer of the sequencing cycles required by the two assays. Override cycles for assays requiring shorter indexes and read lengths will be padded to match the cycle lengths used in the run.

    BCL Convert Settings and Data

    Starting from BCL:

    • Sample Sheet Validator recalculates and inserts the correct override cycles into the BCLConvert_Data section of the intermediate sample sheet.

      • If index lengths vary, the logic has been enhanced to automatically pad shorter indexes with "N" to standardize cycle lengths.

    • Sample Sheet Validator also writes in values for: Adapter Reads, MaskShortReads, AdapterBehavior, MinimumTrimmedReadLength. These values are based on the TSO 500 library prep kit determined from the input sample sheet.

    Starting from FASTQ:

    • If users run BCL Convert separately to generate FASTQ files:

      • The input sample sheet must already contain valid override cycles, adapter reads, and other BCL Convert Settings.

      • The resulting TSO 500 workflow run will start from FASTQ input files.

      • BCLConvert_Settings and BCLConvert_Data sections will be excluded from the intermediate sample sheet created by the TSO 500 workflow.

    BaseSpace Autolaunch

    Analyses of samples in multi-assay flow cells can be launched simultaneously from BaseSpace. As long as "Starts from FASTQ" is set to True in Analysis Settings, all samples from a multi-assay flow cell will be demultiplexed first to generate FASTQ files. Then, the ICA pipelines (e.g. DRAGEN TSO 500, DRAGEN TSO 500 ctDNA) will be launched simultaneously to process the samples for each of the assays.

    For more information about auto-launching BCL Convert before starting TSO 500 analysis from FASTQ, see

    Summary of Rule Changes

    Component
    Update Summary
    Effect

    Command-Line Options

    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.

    Option
    Required
    Description

    Installation of 2.6.0 on Standalone DRAGEN Server

    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

    DNA Expanded Metrics

    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.

    Metric
    Description
    Troubleshooting

    Multi-Assay Flow Cells

    How to plan a run and analyze data with multiple assays loaded individually per lane on one flow cell.

    Introduction

    The NovaSeq X platform supports loading samples from different assays into different lanes within a single sequencing run. To ensure compatibility, the DRAGEN TSO 500 ctDNA v2.6.3 analysis software supports sample sheets containing multiple data sections, with one section per assay (for example, TSO500S_Data and TSO500L_Data).

    This section describes how the software validates and processes multi-assay sample sheets and details the specific rules and logic applied during validation.

    NovaSeq X 10B

    4300

    NovaSeq X 25B

    8400

    NextSeq 1000/2000

    350

    360-665

    800

    NovaSeq 6000/6000Dx (RUO) S2 Flow Cell

    290-460

    890-1600

    1500

    NovaSeq 6000/6000Dx (RUO) S4 Flow Cell

    800-1200

    2700-4100

    3000

    NovaSeq X 1.5B

    213

    352

    800

    NovaSeq X 10B

    1100

    1800

    3000

    NovaSeq X 25B

    1800

    3300

    4000

    NextSeq 1000/2000

    41

    107

    150

    Large

    NovaSeq 6000/6000Dx (RUO) S4 Flow Cell

    4,300

    Large

    NovaSeq X 1.5B

    2,000

    Large

    NovaSeq X 10B

    4,300

    Large

    NovaSeq X 25B

    8,400

    XLarge

    NextSeq 1000/2000

    350

    Large

    Median depth across all the unique loci occurring in all regions of the manifest file.

    Lower median target coverage may be due to poor sample input/quality, library preparation issues or low sequencing output.

    PCT_EXON_100X (%)

    Percentage of exon bases with 100X fragment coverage. Calculated against all regions in manifest containing _exon in name.

    Can be used in combination with other PCT_EXON metrics to understand under or over coverage of exons.

    PCT_READ_ENRICHMENT (%)

    Percentage of reads that have overlapping sequence with the target regions defined in the sample manifest. In V1 chemistry only the TSO500 manifest is considered while in V2 the TSO500 and HRD manifests are both considered.

    Indicative of general enrichment performance. Reduced proportions of enriched reads may indicate issues with the enrichment proportion of the library preparation.

    PCT_USABLE_UMI_READS (%)

    Percentage of reads that have valid UMI sequences associated with them.

    As UMI reads are sequenced at the start of each read, loss of valid UMI sequence may be cause by sequencing issues impacting the quality of base calling in this portion of the sequencing read.

    MEAN_TARGET_COVERAGE (count)

    Mean depth across all the unique loci defined in the manifest file.

    Lower mean target coverage may be due to poor sample input/quality, library preparation issues or low sequencing output. Large differences between the median and mean target coverage values may indicated a skewed distribution of target coverage.

    PCT_ALIGNED_READS (%)

    Proportion of aligned reads that are non-supplementary, non-secondary and pass QC versus aligned reads that are non-supplementary, non-secondary, mapped and pass QC.

    PCT_CONTAMINATION_EST (%)

    This metric should only be evaluated if the CONTAMINATION_SCORE metric exceed the USL. This metric estimates the amount of contamination in a sample. The contamination level is computed by taking 2.0* the average of the adjusted allele frequencies of all variants that were selected. The adjusted alllele frequency is either the actual allele frequency of the variant if it is less than 0.5, or 1 -allele frequency if it is greater than or equal to 0.5.

    If the sample does not fail the CONTAMINATION_SCORE this metric has no intended meaning as it will be driven by statistical noise (e.g. the few variants that naturally fall outside an expected interval around 0.5 due to random chance)

    High contamination estimates may be due to any of the following:

    Inter-sample contamination caused by mixing of samples during extraction or library preparation.

    Intra-sample contamination, due to mixing of clonally different cell populations during extraction. Large scale genomic rearrangements that cause unexpected VAFs for large numbers of variants.

    PCT_TARGET_0.4X_MEAN (%)

    Parentage of target (all locations in manifest) reads that have a coverage depth of greater the 0.4x the mean target coverage depth (see definition above).

    Provides an indication of uniformity of coverage of the target regions in the manifest file. When trended over time reductions in this metric may indicate an issue with the enrichment process resulting in coverage bias.

    PCT_TARGET_50X (%)

    Percentage of target bases with 50X fragment coverage. Calculated against all regions in manifest file.

    Can be used in combination with other PCT_TARGET metrics to understand under or over coverage of targets.

    PCT_TARGET_100X (%)

    Percentage of target bases with 100X fragment coverage. Calculated against all regions in manifest file.

    Can be used in combination with other PCT_TARGET metrics to understand under or over coverage of targets.

    PCT_TARGET_250X (%)

    Percentage of target bases with 250X fragment coverage. Calculated against all regions in manifest file.

    Can be used in combination with other PCT_TARGET metrics to understand under or over coverage of targets.

    PCT_SOFT_CLIPPED_BASES (%)

    percentage of based that were not used for alignment but retained as part of the alignment file

    Soft clipped reads are used as a part of the downstream analysis for small variants calling. A higher-than-expected number could indicate a low-quality enrichment step.

    PCT_Q30_BASES (%)

    Average percentage of bases ≥ Q30. A prediction of the probability of an incorrect base call (Q‑score).

    An indicator of sequencing run quality, low Q30 across all samples on a run could be the result of run overclustering.

    ALLELE DOSAGE_RATIO (HRD samples)

    Proprietary Myriad Genetics estimate of b-allele dosage based on b-allele noise/signal ratio. B-Allele noise is correlated with coverage; lower coverage samples will have higher noise. B-allele signal is also correlated with tumor fraction; a higher tumor fraction produces a higher signal for b-allele sites. Samples with lower tumor fraction and higher amount of noise (or lower coverage) will have higher Allele Dosage Ratio.

    The upper limit of the score is 50, therefore any sample with 50 Allele Dosage Ratio can be assumed to have tumor fraction close to zero and typically has a GIS = 0.

    MEDIAN TARGET HRD (HRD samples)

    Median target fragment coverage across all target positions in the HRD manifest. Coverage is the total number of non-duplicate pair alignments that overlap.

    IndexAdapterKitName

    Not Required

    The Index Adapter Kit used.

    Sample_ID

    Required

    The unique ID to identify a sample. The sample ID is included in the output file names. Sample IDs are not case sensitive. Sample IDs must have the following characteristics: - Unique for the run. - 1–40 characters. - No spaces. - Alphanumeric characters with underscores and dashes. If you use an underscore or dash, enter an alphanumeric character before and after the underscore or dash. eg, Sample1-T5B1_022515. - Cannot be called all, default, none, unknown, undetermined, stats, or reports. - Must match a Sample_ID listed in the BCL Convert Data section. - Each sample must have a unique combination of Lane (if applicable), sample ID, and index ID or the analysis will fail.

    Sample_Type

    Required

    Enter DNA

    Sample_Description

    Not Required

    Sample description must meet the following requirements: - 1–50 characters. - Alphanumeric characters with underscores, dashes and spaces. If you enter a underscore, dash, or space, enter an alphanumeric character before and after. eg, Liquid-Sample_213.

    SoftwareVersion

    Not Required

    The TSO500S software version

    StartsFromFastq

    Required

    Set the value to TRUE or FALSE. To auto-launch from BCL files, set to FALSE. To auto-launch from FASTQ files after auto-launch of BCL Convert, set to TRUE.

    SampleSheetRequested

    Required

    Set the value to TRUE or FALSE.

    To auto-launch from BCL files, set to FALSE. To auto-launch from FASTQ files after auto-launch of BCL Convert, set to TRUE.

    Sample_ID

    Not Required

    The same sample ID used in the Cloud_TSO500L_Data section.

    ProjectName

    Not Required

    The BaseSpace project name.

    LibraryName

    Not Required

    Combination of sample ID and index values in the following format: sampleID_Index_Index2

    LibraryPrepKitName

    Required

    The Library Prep Kit used.

    GeneratedVersion

    Not Required

    The cloud GSS version used to create the sample sheet. Optional if manually updating a sample sheet.

    CloudWorkflow

    Not Required

    Ica_workflow_1

    Cloud_TSO500L_Pipeline

    Required

    This value is a universal record number (URN) . The valid value is: urn:ilmn:ica:pipeline:850b4fe6-2a2f-4a85-ae57-cf082dfbefd4#DRAGEN_TruSight_Oncology_500_ctDNA_v2_6_1_4

    BCLConvert_Pipeline

    Required

    The value is a URN in the following format: urn:ilmn:ica:pipeline: <pipeline-ID>#<pipeline-name>

    SoftwareVersion

    Required

    Enter the IRM iapp software version 2.6.1-4v2

    Standard Sample Sheet Requirements
    [TSO500L_Data] Section
    Sample Sheet Requirements
    Sample Sheet Requirements
    Sample Sheet Requirements
    Starting From FASTQ Files

    TSO500 + HRD

    NovaSeq 6000Dx (in RUO mode)

    Standard

    TSO500 HT

    NextSeq 1000 / 2000

    Standard

    TSO500 HT

    NovaSeq 6000

    Standard

    TSO500 HT

    NovaSeq 6000

    XP*

    TSO500 HT

    NovaSeq 6000Dx (in RUO mode)

    Standard

    TSO500 HT

    NovaSeq 6000Dx (in RUO mode)

    XP*

    TSO500 HT

    NovaSeq X

    Standard

    TSO500 HT

    NovaSeq X

    XP*

    TSO500 v2

    NextSeq 550/DX (in RUO Mode)

    Standard

    TSO500 v2

    NextSeq 1000 / 2000

    Standard

    TSO500 v2

    NovaSeq 6000

    Standard

    TSO500 v2

    NovaSeq 6000

    XP*

    TSO500 v2

    NovaSeq 6000Dx (in RUO mode)

    Standard

    TSO500 v2

    NovaSeq 6000Dx (in RUO mode)

    XP*

    TSO500 v2

    NovaSeq X

    Standard

    TSO500 v2

    NovaSeq X

    XP*

    Sample_Sheet_Template_TSO 500 HRD_i5Rev_Std_Local.csv
    Sample_Sheet_Template_TSO 500 HRD_i5Fwd_Std_Local.csv
    Sample_Sheet_Template_TSO 500 HT_i5Fwd_Std_Local.csv
    Sample_Sheet_Template_TSO 500 HT_i5Rev_Std_Local.csv
    Sample_Sheet_Template_TSO 500 HT_i5Rev_XP_Local.csv
    Sample_Sheet_Template_TSO 500 HT_i5Fwd_Std_Local.csv
    Sample_Sheet_Template_TSO 500 HT_i5Fwd_XP_Local.csv
    Sample_Sheet_Template_TSO 500 HT_i5Fwd_Std_Local.csv
    Sample_Sheet_Template_TSO 500 HT_i5Fwd_XP_Local.csv
    Sample_Sheet_Template_TSO_500_HRD_v2_i5Rev_Std_Autolaunch.csv
    Sample_Sheet_Template_TSO_500_HRD_v2_i5Fwd_Std_Autolaunch.csv
    Sample_Sheet_Template_TSO_500_HRD_v2_i5Rev_Std_Autolaunch.csv
    Sample_Sheet_Template_TSO_500_HRD_v2_i5Rev_XP_Autolaunch.csv
    Sample_Sheet_Template_TSO_500_HRD_v2_i5Fwd_Std_Autolaunch.csv
    Sample_Sheet_Template_TSO_500_HRD_v2_i5Fwd_XP_Autolaunch.csv
    Sample_Sheet_Template_TSO_500_HRD_v2_i5Fwd_Std_Autolaunch.csv
    Sample_Sheet_Template_TSO_500_HRD_v2_i5Fwd_XP_Autolaunch.csv

    N/A

    NovaSeq X

    Yes (v2.6.0.25, v2.6.1.8, v2.6.3)

    Yes

    N/A

    No

    NextSeq2K

    Yes (v2.6.3)

    Yes

    N/A

    No

    Exon-level CNVs
  • Multinucleotide variants (MNVs)

  • Genomic Instability Score (GIS Score) *

  • Tumor fraction*

  • Ploidy*

  • NovaSeq 6000

    Yes

    Yes

    N/A

    N/A

    NovaSeq 6000Dx (RUO mode)

    Yes

    Yes

    Yes

    N/A

    NextSeq 1000/2000

    Yes

    Yes

    N/A

    No

    NovaSeq X

    Yes

    Yes

    N/A

    No

    NextSeq 550Dx (RUO mode)

    Yes

    Yes

    No

    N/A

    NextSeq 500/550

    Yes

    Yes

    N/A

    block list file

    N/A

    Exon-level CNVs
  • Multinucleotide variants (MNVs)

  • Genomic Instability Score (GIS Score) *

  • NovaSeq 6000

    Yes

    Yes

    N/A

    N/A

    NovaSeq 6000Dx (RUO mode)

    Yes

    Yes

    No

    N/A

    NextSeq 1000/2000

    Yes**

    Yes**

    N/A

    No

    NovaSeq X

    Yes**

    Yes**

    N/A

    No

    NextSeq 550Dx (RUO mode)

    Yes

    Yes

    No

    N/A

    NextSeq 500/550

    Yes

    Yes

    N/A

    block list file

    N/A

    In the "Run Review" page, click "Add another configuration" to add the sample prep info for the second assay.

  • A sample sheet containing multiple data sections (one per assay) will be available for exporting at the end of the run planning.

  • The intermediate sample sheet includes only samples listed in the TSO 500 Data section.

  • BCL Convert (inside the TSO 500 workflow) then generates FASTQ files only for those samples.

  • Override Cycles

    Auto-calculated or user-provided depending on workflow

    Maintains correct cycle definitions per sample

    Solid

    One and only one value must match the predefined Solid kit set: TSO500, TSO500HT, or TSO500_v2. The validation fails if none or more than one valid Solid kit is provided. The validated value will be written into the intermediate sample sheet for baseline selection.

    TSO500HT

    ctDNA

    The library prep kit and the Sequencing_Settings section are not required. The library prep kit validation rule is skipped, and the Sequencing_Settings section is excluded from the intermediate sample sheet.

    N/A

    Sample Index Rule

    Filtered to process samples only from workflow-specific data section

    Prevents validation failures for multi-assay sample sheets

    Sample Parity Rule

    Enforces that workflow samples exist in BCLConvert_Data

    Ensures downstream consistency

    Library Prep Kit Rule

    Supports multiple values separated by ;

    Allows multi-assay sample sheets

    Adapter Read Rule

    Supports multiple adapters separated by +

    Starts from FASTQ
    Auto-Launch with FASTQs generated by Standalone BCL Convert Pipeline (Start from FASTQ)

    Expands flexibility across assays

    Lower median target coverage may be due to poor sample input/quality, library preparation issues or low sequencing output.

    PCT_CHIMERIC_READS (%)

    Chimeric reads occur when one sequencing read aligns to two distinct portions of the genome with little or no overlap. Metric is proportion of total number of non-supplementary, non-secondary, and passing QC reads after alignment to the whole genome sequence.

    While this can be indicative of large-scale structural rearrangement of the genome, values that are elevated above the usual baseline may indicate enrichment probe contamination during library preparation. A suggested metric USL is 8% (those that are higher might see decrease performance in small variant and tmb scores).

    PCT_EXON_100X (%)

    Percentage of exon bases with 100X fragment coverage. Calculated against all regions in manifest containing _exon in name.

    Can be used in combination with other PCT_EXON metrics to understand under or over coverage of exons.

    PCT_READ_ENRICHMENT (%)

    Percentage of reads that have overlapping sequence with the target regions defined in the sample manifest.

    Indicative of general enrichment performance. Reduced proportions of enriched reads may indicate issues with the enrichment proportion of the library preparation.

    PCT_USABLE_UMI_READS (%)

    Percentage of reads that have valid UMI sequences associated with them.

    As UMI reads are sequenced at the start of each read, loss of valid UMI sequence may be cause by sequencing issues impacting the quality of base calling in this portion of the sequencing read.

    MEAN_TARGET_COVERAGE (count)

    Mean depth across all the unique loci defined in the manifest file.

    Lower mean target coverage may be due to poor sample input/quality, library preparation issues or low sequencing output. Large differences between the median and mean target coverage values may indicated a skewed distribution of target coverage.

    PCT_ALIGNED_READS (%)

    Proportion of aligned reads that are non-supplementary, non-secondary and pass QC versus aligned reads that are non-supplementary, non-secondary, mapped and pass QC.

    PCT_CONTAMINATION_EST (%)

    This metric should only be evaluated if the CONTAMINATION_SCORE metric exceed the USL. This metric estimates the amount of contamination in a sample. The contamination level is computed by taking 2.0* the average of the adjusted allele frequencies of all variants that were selected. The adjusted alllele frequency is either the actual allele frequency of the variant if it is less than 0.5, or 1 -allele frequency if it is greater than or equal to 0.5.

    If the sample does not fail the CONTAMINATION_SCORE this metric has no intended meaning as it will be driven by statistical noise (e.g. the few variants that naturally fall outside an expected interval around 0.5 due to random chance)

    High contamination estimates may be due to any of the following:

    Inter-sample contamination caused by mixing of samples during extraction or library preparation.

    Intra-sample contamination, due to mixing of clonally different cell populations during extraction. Large scale genomic rearrangements that cause unexpected VAFs for large numbers of variants.

    PCT_TARGET_0.4X_MEAN (%)

    Parentage of target (all locations in manifest) reads that have a coverage depth of greater the 0.4x the mean target coverage depth (see definition above).

    Provides an indication of uniformity of coverage of the target regions in the manifest file. When trended over time reductions in this metric may indicate an issue with the enrichment process resulting in coverage bias.

    PCT_TARGET_50X (%)

    Percentage of target bases with 50X fragment coverage. Calculated against all regions in manifest file.

    Can be used in combination with other PCT_TARGET metrics to understand under or over coverage of targets.

    PCT_TARGET_100X (%)

    Percentage of target bases with 100X fragment coverage. Calculated against all regions in manifest file.

    Can be used in combination with other PCT_TARGET metrics to understand under or over coverage of targets.

    PCT_TARGET_250X (%)

    Percentage of target bases with 250X fragment coverage. Calculated against all regions in manifest file.

    Can be used in combination with other PCT_TARGET metrics to understand under or over coverage of targets.

    ALLELE DOSAGE_RATIO (with HRD add-on)

    Proprietary Myriad Genetics estimate of b-allele dosage based on b-allele noise/signal ratio. B-Allele noise is correlated with coverage; lower coverage samples will have higher noise. B-allele signal is also correlated with tumor fraction; a higher tumor fraction produces a higher signal for b-allele sites. Samples with lower tumor fraction and higher amount of noise (or lower coverage) will have higher Allele Dosage Ratio. The upper limit of the score is 50, therefore any sample with 50 Allele Dosage Ratio can be assumed to have tumor fraction close to zero and typically has a GIS = 0.

    MEDIAN TARGET HRD (with HRD add-on)

    Median target fragment coverage across all target positions in the genome. Coverage is the total number of non-duplicate pair alignments that overlap.

    TOTAL_PF_READS (count)

    Total number of non-supplementary, non-secondary, and passing QC reads after alignment to the whole genome sequence.

    Primarily driven by data output of sequencer, quality of library and balancing of library in library pool. If TOTAL_PF_READS is in line with other samples, but coverage metrics are more may suggest non-specific enrichment.

    Low values for all samples indicate a poor quality run with possible low cluster numbers or low numbers of Q30 and PF%.

    A low value for an individual sample indicates poor pooling of this library into the final pool.

    MEAN_FAMILY_SIZE (count)

    A UMI Family is a group of reads that all have the same UMI barcode. The family size is the number of reads in family. MEAN_FAMILY_SIZE is the mean of the entire population of reads assembled into UMI families.

    The mean UMI family size decreases with increased unique read numbers, and more input DNA leads to more unique reads. Conversely over sequencing of a fixed population of unique DNA molecules leads to increased family size.

    As a guide, for a good run with optimal cluster density, passing specs, even sample pooling, and good quality DNA we usually observe values <10.

    UMI family size = 1 is not ideal as it is harder to correct for errors.

    UMI family size of 2 to 5 enables efficient error correction without wasting sequencing capacity on high percentages of duplicate reads.

    MEDIAN_TARGET_COVERAGE (count)

    Median depth across all the unique loci occurring in all regions of the manifest file.

    'test_sample' (alphanumeric with underscore)

    Input Folder

    The run folder or FASTQ folder that contains files to analyze.

    Starts from FASTQ

    True for analysis performed on files in the FASTQ folder. False for analysis performed on files in the run folder.

    Sample or Pair IDs

    Optional subset of Sample IDs or Pair IDs to analyze.

    Storage Size

    The storage size to allocate for the analysis. The default and recommended value is Large.

    'test_sample' (alphanumeric with underscore)

    Input Folder

    The run folder or FASTQ folder that contains files to analyze.

    FASTQ List CSV

    Do not use, this only applies to auto-launch TSO 500 analysis from FASTQs after BCL auto-launch.

    Starts from FASTQ

    True for analysis performed on files in the FASTQ folder. False for analysis performed on files in the run folder.

    Sample or Pair IDs

    Optional subset of Sample IDs or Pair IDs to analyze.

    Sample List

    Do not use, this only applies to auto-launch TSO 500 analysis from FASTQs after BCL auto-launch.

    Storage Size

    The storage size to allocate for the analysis. The default and recommended value is Large.

    --resourcesFolder

    No

    Path to the resource folder location. The default location is /staging/illumina/DRAGEN_TSO500_2.6.0/resources. If not using the default location, enter the full path to the resource folder.

    --runFolder

    Yes

    Required when --fastqFolder is not specified. Provide the full path to the local run folder.

    --fastqFolder

    Yes

    Required when --runFolder is not specified. Provide the full path to the local FASTQ folder. Analysis starts at this location.

    --user

    No

    Optional for Docker. Specify the user ID to be used within the Docker container.

    --version

    No

    Displays the version of the software.

    --sampleSheet

    No

    Provide the full path, including file name, if not provided as SampleSheet.csv in the run folder.

    --sampleOrPairIDs

    No

    Provide the comma-delimited sample or pair IDs that should be processed on this node with no spaces. For example, Pair_1,Pair_2,Sample_1.

    --demultiplexOnly

    No

    Demultiplex to generate FASTQ only without additional analysis.

    --gather

    No

    Follow this option for any directories with results that should be gathered into a single Results folder.

    --hashtableFolder

    No

    Defaults to the DRAGEN hash table location created upon install. If not using the default location, enter the hash table location.

    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:

    Folder/File
    Description

    Config folder

    Configuration files.

    Data folder

    *.bcl files.

    Images folder

    [Optional] Raw sequencing image files.

    InterOp folder

    InterOp metric files.

    Logs folder

    [Optional] Sequencing system log files.

    RTALogs folder

    Real-Time Analysis (RTA) log 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.

    Use BCL Convert to produce FASTQ files for DRAGEN TruSight Oncology 500 Analysis Software. Using bcl2fastq does not produce the same results and is discouraged.

    Make sure that BCL Convert is set to write UMI sequences to the read headers in the FASTQ files.

    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.

    --help

    No

    Displays a help screen with available command line options.

    --analysisFolder

    No

    Path to the local analysis folder. The default location is /staging/DRAGEN_TSO500_2.6.0_Analysis_{timestamp}. If not using the default location, provide the full path to the local analysis folder. Folder must have sufficient space and must be on an NVMe SSD drive. For example, the /staging directory on the DRAGEN server. Refer to table in for minimum disk space requirements.

    DRAGEN Software if a compatible version is not present
  • Docker software if a compatible version is not present

  • A script required to generate DRAGEN genome hash table

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

    Software Dependency
    Compatible
    Installs

    Docker

    20.10 or greater

    Docker 20.10.15

    DRAGEN Software

    v3.10.x where x is 17 or greater

    DRAGEN Software 3.10.17

    DRAGEN TruSight Oncology 500 v2.6.0 Analysis Software is not compatible with DRAGEN Software v4.0 or above on the same standalone DRAGEN server.

    Licenses

    • TSO500Combined license

    • TSO500_HRD license (to analyze data generated with the TSO 500 HRD add-on kit)

    TSO500Combined license has been pre-installed to DRAGEN servers in manufacturing since August 2022 and TSO500_HRD since February 2025 and additionally distributed to DRAGEN servers connected online. To generate a list of installed DRAGEN server licenses, run the following command: /opt/edico/bin/dragen_lic. If a license is not installed, contact Illumina Customer Care at [email protected] for the license.

    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*)dr

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

    When installing DRAGEN TruSight Oncology 500 and DRAGEN TruSight Oncology 500 ctDNA software on the same DRAGEN server, install the software with the highest corresponding DRAGEN Software version last, as versions below v2.6.0 will overwrite with its corresponding DRAGEN Software version.

    If a prior version of DRAGEN TruSight Oncology 500 Analysis Software (eg. v2.5.3) is installed after v2.6.0, re-execute the installation script for v2.6.0 to install the compatible version of DRAGEN Software without impacting other installations.

    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 [email protected] 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.

    It is recommended to use a command line tool like wget or curl to download the file rather than pasting the link into the web browser bar. For example:

    curl -o {filename} "{link}"

    wget -O {filename} '{link}'

    Where the file name is the installation script file name, and the link is provided by Illumina Customer Care.

    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.

    Installation Script: install_DRAGEN_TSO500-2.6.0.run

    MD5sum: 578cda2b8837845b26e2c3c020f2264c

    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 if any errors occur.

    License Installation

    Review license requirements, how to check which licenses are installed and how to receive a license in Licenses. Licenses can be installed before or after DRAGEN TSO 500 software installation.

    To install a license (TSO500Combined and/or TSO500_HRD) on a DRAGEN server connected to the internet:

    1. Confirm that the server is connected to the Internet, example: ping www.illumina.com

    2. Run the following command: /opt/edico/bin/dragen_lic -i auto

    To install a license (TSO500Combined and/or TSO500_HRD) on a DRAGEN server not connected to the internet:

    1. Contact Customer Care at [email protected] to request a license file for each of the needed licenses

    2. Download and save the license file(s) to a location that is accessible from the DRAGEN server

    3. For each license file, run the command, where <license file received> is the absolute path to the license file: sudo /opt/edico/bin/dragen_lic -i /tmp/<license file received>.bin

    To check the success of license installation, run: /opt/edico/bin/dragen_lic. Installed licenses should be in the list.

    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.

    Planning a Run with a Multi-Assay Flow Cell
    1. In the BaseSpace Sequence Hub home page, click "Runs" -> "New Run" -> "Run Planning".

    2. In the "Create a Run" page, select "NovaSeq X Series" as instrument platform.

    3. Provide information for the first assay until the "Run Review" page.

      • For TSO 500 or TSO 500 ctDNA assays, to auto-launch multiple pipelines at once, set "" to True

    4. In the "Run Review" page, click "Add another configuration" to add the sample prep info for the second assay.

    5. A sample sheet containing multiple data sections (one per assay) will be available for exporting at the end of run planning.

    Analyzing Data from a Multi-Assay Flow Cell

    Sample Sheet Validation

    The sample sheet validator determines which data section(s) to validate based on the active workflow type. The list of samples to process is generated only from the relevant section (for example, Solid or ctDNA). This ensures that only valid samples for the selected workflow are validated.

    The workflow’s data section may contain fewer samples than the BCLConvert_Data section. However, all samples listed in the workflow data section must exist in BCLConvert_Data section. The downstream pipeline will only process samples found in the workflow-specific data section.

    Library Prep Kits

    Multi-assay sample sheets may include multiple library prep kits values separated by semicolons (";").

    Validation Logic:

    Workflow Type
    Validation Logic
    Example of Accepted Values

    Solid

    One and only one value must match the predefined Solid kit set: TSO500, TSO500HT, or TSO500_v2. The validation fails if none or more than one valid Solid kit is provided. The validated value will be written into the intermediate sample sheet for baseline selection.

    TSO500HT

    ctDNA

    The library prep kit and the Sequencing_Settings section are not required. The library prep kit validation rule is skipped, and the Sequencing_Settings section is excluded from the intermediate sample sheet.

    N/A

    Adapter Reads

    When working with multiple assays, the "AdapterRead" field in the sample sheet may include multiple adapter sequences separated by "+". The adapter read of the selected workflow will be filled in the intermediate sample sheet.

    Override Cycles

    Override cycles are determined by the index and read length specified in the "Reads" section of the RunInfo.xml file and assay specifics. For multi-assay flow cells, the index and read length provided in RunInfo.xml should be the longer of the sequencing cycles required by the two assays. Override cycles for assays requiring shorter indexes and read lengths will be padded to match the cycle lengths used in the run.

    BCL Convert Settings and Data

    Starting from BCL:

    • Sample Sheet Validator recalculates and inserts the correct override cycles into the BCLConvert_Data section of the intermediate sample sheet.

      • If index lengths vary, the logic has been enhanced to automatically pad shorter indexes with "N" to standardize cycle lengths.

    • Sample Sheet Validator also writes in values for: Adapter Reads, MaskShortReads, AdapterBehavior, MinimumTrimmedReadLength. These values are based on the TSO 500 ctDNA library prep kit determined from the input sample sheet.

    • The intermediate sample sheet includes only samples relevant to the workflow type (Solid or ctDNA).

    • BCL Convert (inside the TSO 500 ctDNA workflow) then generates FASTQ files only for those samples.

    Starting from FASTQ:

    • If users run BCL Convert separately to generate FASTQ files:

      • The input sample sheet must already contain valid override cycles, adapter reads, and other BCL Convert Settings.

      • The resulting TSO 500 ctDNA workflow run will start from FASTQ input files.

      • BCLConvert_Settings and BCLConvert_Data sections will be excluded from the intermediate sample sheet created by the TSO 500 ctDNA workflow.

    BaseSpace Autolaunch

    Analyses of samples in multi-assay flow cells can be launched simultaneously from BaseSpace. As long as "Starts from FASTQ" is set to True in Analysis Settings, all samples from a multi-assay flow cell will be demultiplexed first to generate FASTQ files. Then, the ICA pipelines (e.g. DRAGEN TSO 500, DRAGEN TSO 500 ctDNA) will be launched simultaneously to process the samples for each of the assays.

    For more information about auto-launching BCL Convert before starting TSO 500 analysis from FASTQ, see

    Summary of Rule Changes

    Component
    Update Summary
    Effect

    Sample Index Rule

    Filtered to process samples only from workflow-specific data section

    Prevents validation failures for multi-assay sample sheets

    Sample Parity Rule

    Enforces that workflow samples exist in BCLConvert_Data

    Ensures downstream consistency

    Library Prep Kit Rule

    Supports multiple values separated by ;

    Allows multi-assay sample sheets

    Adapter Read Rule

    Supports multiple adapters separated by +

    Troubleshooting

    General Troubleshooting on Standalone DRAGEN Server

    Failure Type
    Actions

    Software

    - Open the log file ./<AnalysisFolder>/Logs_Intermediates/pipeline_trace.txt. This log file displays each pipeline step run by the Nextflow workflow manager software. If a step fails, it is marked as FAILED. Each step generates log files that are stored in step-specific subfolders in the Logs_Intermediates folder. Review the log files in the relevant Logs_Intermediates folder for the step to identify potential sources of error. - Open the errors folder ./<AnalysisFolder>/errors. The workflow creates an error file, error_<NameOfFailedStep>.json, for each step that failed during analysis. For steps that fail per sample, there is a separately labeled file for each sample that failed each step error_<NameOfFailedStep>_<SampleIDIfRelevant>.json. These files contain the command and stdout and stderr from the step.

    Samples

    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.

    General troubleshooting for a failed sample sheet:

    Failure Type
    Action

    Valid indexes for assay and instrument combinations:

    Assay
    Index Set ID

    Troubleshooting BCL issues:

    Failure Type
    Action

    Troubleshooting FASTQs issues:

    Failure Type
    Action

    Other Troubleshooting Tips

    Failure Type
    Action

    Troubleshooting on ICA

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

    Error
    Description

    Sample Sheet Creation in BaseSpace Run Planning tool

    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

    Parameter Name
    Required
    Description

    Step 2: Configuration

    Parameter Name
    Required
    Description

    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.

    Parameter Name
    Required
    Description

    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.

    Guided Examples

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

    Command-Line Options

    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.

    Option
    Required
    Description

    --help

    No

    Displays a help screen with available command line options.

    --analysisFolder

    No

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

    Starting from BCL Files

    For the data generated by NextSeq 1000/2000 and NextSeq X, the analysis can only be started from FASTQs and not from BCLs.

    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:

    Folder/File
    Description

    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

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

    Use BCL Convert to produce FASTQ files for DRAGEN TruSight Oncology 500 Analysis Software. Using bcl2fastq does not produce the same results and is discouraged.

    Make sure that BCL Convert is set to write UMI sequences to the read headers in the FASTQ files.

    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.

    Installation of TSO 500 ctDNA v2.6.0, v2.6.1 on Standalone DRAGEN Server

    Overview

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

    1. DRAGEN TruSight Oncology 500 ctDNA 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 ctDNA Analysis Software is installed properly

    Installation Requirements

    Hardware

    • DRAGEN server v3 or v4

    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.

    Software Dependency
    Compatible
    Installs

    DRAGEN TruSight Oncology 500 ctDNA v2.6.0 Analysis Software is not compatible with DRAGEN Software v4.0 or above on the same standalone DRAGEN server.

    Licenses

    • TSO500Combined license

    TSO500Combined license has been pre-installed to DRAGEN servers in manufacturing since August 2022. To generate a list of installed DRAGEN server licenses, run the following command: /opt/edico/bin/dragen_lic. If a license is not installed, contact Illumina Customer Care at for the license.

    Permissions

    Illumina recommends logging in as root user for installation, but as a non-root user for running TSO 500 ctDNA 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 .

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

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

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

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

    1. DRAGEN TruSight Oncology 500 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 ctDNA Analysis Software v2.6.0 and DRAGEN TruSight Oncology 500 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 ctDNA Analysis Software, refer to the respective guide.

    When installing DRAGEN TruSight Oncology 500 and DRAGEN TruSight Oncology 500 ctDNA software on the same DRAGEN server, install the software with the highest corresponding DRAGEN Software version last, as versions below v2.6.0 will overwrite with its corresponding DRAGEN Software version.

    If a prior version of DRAGEN TruSight Oncology 500 ctDNA Analysis Software (eg. v2.5.0) is installed after v2.6.0, re-execute the installation script for v2.6.0 to install the compatible version of DRAGEN Software without impacting other installations.

    Installation Instructions

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

    1. Contact Illumina Customer Care at 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.

    It is recommended to use a command line tool like wget or curl to download the file rather than pasting the link into the web browser bar. For example:

    curl -o {filename} "{link}"

    wget -O {filename} "{link}"

    Where the file name is the installation script file name, and the link is provided by Illumina Customer Care.

    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.

    Installation Script:

    install_DRAGEN_TSO500_ctDNA-2.6.0.run

    install_DRAGEN_TSO500_ctDNA-2.6.1.run

    MD5sum values v2.6.0: sha256:e98ab87152b02e2c7958f2f750fa37880a496d68e77858a09f4ad5fb07b2145b v2.6.1: sha256:026efd4402e91e8472effb30749e231817958532aae128334c5f9943564e4b8d

    1. Use the following command to update the run script permission: chmod +x /staging/install_DRAGEN_TSO500_CTDNA-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_CTDNA-2.6.0.run . The script installs compatible DRAGEN software and removes any previously installed versions.

    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_CTDNA-2.6.0.sh

    The script checks that:

    • All required services are running

    • Proper Docker image is installed

    • DRAGEN TruSight Oncology 500 ctDNA 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_CTDNA_<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_CTDNA-2.6.0.sh, which is located in /usr/local/bin.

    Executing the uninstall script removes the following assets:

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

    • Resources found in /staging/illumina/DRAGEN_TSO500_CTDNA

    • The dragen_tso500_ctdna Docker image

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

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

    DNA Output

    Refer to DNA Analysis Methods 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.

    Filter
    Note

    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.

    Column
    Description

    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.

    In analysis versions prior to v2.5, <DEL> calls in the VCF are marked as LowValidation. The LowValidation filter indicates that the calls have been validated only with in silico data sets and are provided as information only.

    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.

    Installation of 2.6.1 on Standalone DRAGEN Server

    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

    DNA Output

    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.

    Sample Sheet Creation in BaseSpace Run Planning tool

    How to Create TSO 500 ctDNA 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 ctDNA 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 for descriptions of fields that appear in ICA sample sheets.

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

    DNA Analysis Methods

    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.

    DNA Analysis Methods

    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.

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

    Open the combined metrics output results file ./<AnalysisFolder>/Results/<PairId>/MetricsOutput.tsv. If a sample fails an analysis step, the Pair ID that contains the sample shows the failure under FAILED_STEPS in the Analysis Status section, and COMPLETED_ALL_STEPS shows as False. If available, review the individual log files for the failed steps under ./<AnalysisFolder>/Logs_Intermediates to identify potential sources of error.

    Multinode Gather

    If the following error appears, check if the sample or pair ID was included multiple times during separate node analysis runs, before being gathered together. If the error exists, rerun one of the analyses without the duplicate and reattempt gathering. ERROR:Gather:Destination file ... already exists - check if the same sample ID is in multiple input folders

    Sample Sheet not found

    Verify that SampleSheet.csv is present at the top level of the run folder with the name "SampleSheet.csv". If the sample sheet is in a different location, supply the sample sheet using the --sampleSheet option

    Indexes are not valid for the sequencer and/or assay

    See Valid indexes for assay and instrument combinations for correct indexes for the sequencer and assay.

    Pair_ID is not unique

    Pair_ID column is required in the TSO500S_Data section of the sample sheet, which pairs at most one RNA and one DNA sample together for analysis. If the sample does not have a pair, use a unique pair ID for single samples.

    Sample Sheet is not in v2 format

    Verify that the format of the sample sheet is v2. v1 sample sheet is not compatible with DRAGEN TruSight Oncology 500 Analysis Software.

    Analysis does not run

    Verify the analysis starts from the run folder, and BCLs or FASTQs are in the correct locations as outlined in Starting From BCL Files and Starting From FASTQ Files respectively.

    TSO 500

    • UP1-UP16

    • CP1-CP16 (DNA Only)

    TSO 500 HT

    • UDP0001–UDP0192

    Lane Column without Values

    Ensure that the column is completed. If lane is not applicable to the run, delete the column.

    Format of v2 sample sheet is incorrect

    Verify that the following sections and fields are present in the sample sheet and follow the individual rules in Sample Sheet Requirements [BCLConvert_Settings] - SoftwareVersion - AdapterRead1 - AdapterRead2 - AdapterBehavior - MinimumTrimmedReadLength - MaskShortReads [BCLConvert_Data] - Sample_ID - index - index2 [TS0500S_Data] - Sample_ID - Index_ID - Sample_Type - Pair_ID - Sample Feature (Optional)

    HRD analysis is missing

    Verify that HRD is in the Sample Feature column in the sample sheet. Refer to Sample Sheet Requirements for more information.

    Sample_ID and/or Sample_Type is not present

    Verify that the sample sheet has columns and values for Sample_ID and Sample_Type.

    Unique sample IDs

    Verify that the Sample_IDs are unique in the sample sheet.

    Format of v2 Sample Sheet is incorrect

    Verify that the following sections and fields are present in the sample sheet and follow the individual rules in Sample Sheet Requirements. [TS0500S_Data] - Sample_ID - Index_ID - Sample_Type - Pair_ID

    - Sample Feature (Optional) Verify when FASTQs were generated using the HRD add-kit (Not available in Japan), Sample Feature is added to those DNA Samples. Refer to Sample Sheet Requirements for more information.

    Incorrect folder structure

    Verify that the FASTQ files are in the correct structure. Refer to Starting From FASTQ Files for more information.

    Invalid FASTQ input files

    If the FASTQs are invalid, start TSO 500 analysis from BCL files.

    HRD analysis missing

    Make sure that HRD is in the correct column in the sample sheet.

    The output file directory contains information from previous analyses

    If this issue is seen: specify a new target output folder and repeat analysis To prevent this issue: specify an empty directory before starting analysis

    Single exon (single probe) genes are still reported in the CNV VCF file, but not the CNV TSV file

    No action needed; software is working as expected.

    Currently all single probe genes are not emitted to the Copy Number Variants section of our CombinedVariantOutput.tsv. However, you can still find these events in the cnv.vcf.gz.

    Due to the single probe nature, accurate CNV calling has not been validated and as such they are emitted as REF

    Testing of cell lines, contrived samples and commercial controls does not return expected results

    Review recommendations for using these samples types here.

    Failure type: ValueError: Could not find pipeline ID for app BCLConvert in sample sheet SampleSheet.csv

    Action: Ensure StartsFromFastq field is in the [TSO500S_Settings] section, and it is not present in the [BCLConvert_Settings] Section. Refer to Sample Sheet Requirements for more information.

    multiallelic

    Site filtered because more than two alt alleles pass tumor LOD.

    no_reliable_supporting_read

    Site filtered because no reliable supporting somatic read exists.

    read_position

    Site filtered because median of distances between start/end of read and this locus is below threshold.

    str_contraction

    Site filtered due to suspected PCR error where the alt allele is one repeat unit less than the reference.

    too_few_supporting_reads

    Site filtered because there are too few supporting reads in the tumor sample.

    weak_evidence

    Somatic variant score (SQ) does not meet threshold.

    systematic_noise

    Site filtered based on evidence of systematic noise in normal sample.

    excluded_regions

    Site overlaps with VC excluded regions bed.

    CytoBand

    Cytoband of variant

    GeneName

    Name of gene if applicable. A semicolon delimited list is used for multiple genes.

    VariantType

    Type of the variant: SNV, insertion, deletion, MNV

    CosmicIDs

    Cosmic IDs, if multiple concatenated by “;”

    MaxCosmicCount

    Maximum Cosmic study count

    AlleleCountsGnomadExome

    Variant allele count in gnomAD exome database

    AlleleCountsGnomadGenome

    Variant allele count in gnomAD genome database

    AlleleCounts1000Genomes

    Variant allele count in 1000 genomes database

    MaxDatabaseAlleleCounts

    Maximum variant allele count over the three databases

    GermlineFilterDatabase

    TRUE if variant was filtered by the database filter

    GermlineFilterProxi

    TRUE if variant was filtered by the proxi filter

    CodingVariant

    TRUE if variant is in the coding region

    Nonsynonymous

    TRUE if variant has any transcript annotations with nonsynonymous consequences

    IncludedinTMBNumerator

    TRUE if variant is used in the TMB calculation

    PASS

    PASS variants.

    base_quality

    Site filtered because median base quality of alt reads at this locus does not meet threshold.

    filtered_reads

    Site filtered because the fraction of reads is too large.

    fragment_length

    Site filtered because absolute difference between the median fragment length of alt reads and median fragment length of ref reads at this locus exceeds threshold.

    low_depth

    Site filtered because the read depth is too low.

    low_frac_info_reads

    Site filtered because the fraction of informative reads is below threshold.

    long_indel

    Site filtered because the indel length is too long.

    mapping_quality

    Site filtered because median mapping quality of alt reads at this locus does not meet threshold.

    Chromosome

    Chromosome

    Position

    Position of variant

    RefCall

    Reference base

    AltCall

    Alternate base

    VAF

    Variant allele frequency

    Depth

    Coverage of position

    n=[(200Y)−2(100−X)]/Xn=[(200Y)-2(100-X)]/Xn=[(200Y)−2(100−X)]/X
    Troubleshooting
  • Start from BCL files in the run folder with a different sample sheet and demultiplexing only. DRAGEN_TSO500.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.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.sh \ --fastqFolder /staging/{FastqFolderName} \ --analysisFolder /staging/{AnalysisFolderName} \ --sampleOrPairIDs "Pair_1,Pair2"

  • RunInfo.xml file

    Run information.

    RunParameters.xml file

    Run parameters.

    SampleSheet.csv file

    Sample information. If you want to use a sample sheet that is not in the run folder or a sample sheet named something other than SampleSheet.csv, provide the full path.

    Path to the local analysis folder. The default location is /staging/DRAGEN_TSO500_Analysis_{timestamp}. If not using the default location, provide the full path to the local analysis folder. Folder must have sufficient space and must be on an NVMe SSD drive. For example, the /staging directory on the DRAGEN server. Refer to table in Storage Requirements for minimum disk space requirements.

    --resourcesFolder

    No

    Path to the resource folder location. The default location is /staging/illumina/DRAGEN_TSO500/resources. If not using the default location, enter the full path to the resource folder.

    --runFolder

    Yes

    Required when --fastqFolder is not specified. Provide the full path to the local run folder.

    --fastqFolder

    Yes

    Required when --runFolder is not specified. Provide the full path to the local FASTQ folder. Analysis starts at this location.

    --user

    No

    Optional for Docker. Specify the user ID to be used within the Docker container.

    --version

    No

    Displays the version of the software.

    --sampleSheet

    No

    Provide the full path, including file name, if not provided as SampleSheet.csv in the run folder

    --sampleOrPairIDs

    No

    Provide the comma-delimited sample or pair IDs that should be processed on this node with no spaces. For example, Pair_1,Pair_2,Sample_1.

    --demultiplexOnly

    No

    Demultiplex to generate FASTQ only without additional analysis.

    --gather

    No

    Follow this option for any directories with results that should be gathered into a single Results folder.

    --hashtableFolder

    No

    Defaults to the DRAGEN hash table location created upon install. If not using the default location, enter the hash table location.

    Config folder

    Configuration files

    Data folder

    *.bcl files

    Images folder

    [Optional] Raw sequencing image files.

    Interop folder

    Interop metric files.

    Logs folder

    [Optional] Sequencing system log files.

    RTALogs folder

    Real-Time Analysis (RTA) log files.

    FASTQ File Organization.

    RunInfo.xml file

    Run information.

    RunParameters.xml file

    Run parameters.

    SampleSheet.csv file

    Sample information. If you want to use a sample sheet that is not in the run folder or a sample sheet named something other than SampleSheet.csv, provide the full path.

    Storage Requirements

    Sample Container ID

    Optional

    • Unique Identifier for the container that holds the sample

    DNA Index ID

    Required

    Index set ID options are based on selected Index Adapter Kit

    DNA Sample Feature

    Required for TSO 500 HRD

    Column appears when TSO 500 HRD application is selected. Enter for HRD enriched DNA Samples

    RNA Index ID

    Required

    Index set ID options are based on selected Index Adapter Kit

    Project

    Optional

    Optional field to describe the associated project

    Starts from Fastq

    Required

    True or False

    If auto-launching TSO 500 from BCL files, set the value to False.

    Run Name

    Required

    Run Name can contain 255 alphanumeric characters, dashes, underscores, periods, and spaces; and must start with an alphanumeric, a dash or an underscore.

    Run Description

    Optional

    Run Description can contain 255 characters except square brackets, asterisks, and commas.

    Instrument Platform

    Required

    Choose from TSO 500 supported instruments:

    • NextSeq 500/550

    • NovaSeq 6000/6000Dx

    Secondary Analysis

    Required

    Application

    Required

    • DRAGEN TruSight Oncology 500 Analysis Software - 2.5.x (with HRD)

    • DRAGEN TruSight Oncology 500 Analysis Software - 2.5.x

    Description

    Optional

    Optional text field

    Library Prep Kit

    Required

    • TruSight Oncology 500

    • TruSight Oncology 500 High Throughput

    Index Adapter Kit

    Required

    Read Lengths: Read 1 and Read 2

    Required

    Auto filled with the standard values, but can be optionally overwritten.

    Lane Usage

    Optional

    Checkbox allows users to apply the same lane across samples.

    Lane

    Required if Lane Usage is unchecked

    Specify lanes for each sample. The unmarked checkbox at the top of the dropdown selects all lanes.

    Pair ID

    Required

    NovaSeq 6000Dx: TSO 500 Auto-launch Analysis in Cloud
    NextSeq 500/550Dx: TSO 500 and Connected Insights Auto-launch Analysis in Cloud
    • BaseSpace/Illumina Connected Analytics (to generate sample sheet for cloud analysis)

    • Local

    TSO 500:

    • TruSight Oncology 500 (NovaSeq 6000Dx, NovaSeq X, NextSeq 1000/2000)

    • TruSight Oncology 500 (NovaSeq 6000, NextSeq 550)

    TSO 500 HT:

    • TruSight Oncology 500 (NovaSeq 6000Dx, NovaSeq X, NextSeq1000/2000)

    The identifier used to pair DNA and RNA samples in a run. The field is mandatory whether a sample is part of a pair, or not.

    To note: The Sample ID field in the generated samplesheet will be auto-filled based on the Pair ID values captured. “_dna” and “_rna” (for DNA and RNA samples respectively) will be appended to the Pair ID value to create the Sample ID.

    For Apptainer, use the following command: sudo TMPDIR=/staging /staging/install_DRAGEN_TSO500_CTDNA-2.6.0.run -- --noDockerInstall This will not install Apptainer, but will install the analysis software in the Singularity Image File (SIF) format and modify the software to launch analyses using Apptainer.

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

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

  • Install your DRAGEN server licenses if needed:

    1. To run DRAGEN TruSight Oncology 500 ctDNA 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. 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

    3. For servers not connected to the internet, contact Illumina Customer Care at for license information.

  • 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 the expected licenses are not installed, contact Illumina Customer Care.

  • Docker

    20.10 or greater

    Docker 20.10.15

    DRAGEN Software

    v3.10.x where x is 17 or greater

    DRAGEN Software 3.10.17

    [email protected]
    Docker website
    [email protected]
    DRAGEN Software if a compatible version is not present
  • Docker software if a compatible version is not present

  • A script required to generate DRAGEN genome hash table

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

  • Installation Requirements

    Hardware

    • DRAGEN server v3 or v4

    • Network-attached storage (NAS) with enabled mkfifo if performing analysis for the TruSight Oncology 500 High-Throughput assay

    Software

    • Linux CentOS 7.9 operating system (or later) or Oracle Linux 8 (or later), one of which is provided on the server. Oracle Linux 8 is recommended.

    • Docker Software, see table below for minimum version needed. If sufficient Docker software is not present on the server, the TSO 500 installer will install compatible Docker software.

    • DRAGEN Server Software*, see table below for minimum version needed as the host version on the server. If sufficient DRAGEN software is not present on the server, the TSO 500 installer will install compatible DRAGEN software.

    Software Dependency
    Compatible
    Installs

    Docker

    20.10 or greater

    Docker 20.10.15

    DRAGEN Server Software*

    v3.10.x, where x ≥ 19

    DRAGEN Software 3.10.19

    *The DRAGEN Server Software version may be higher than the DRAGEN version used by the DRAGEN TSO 500 v2.6.1 pipeline (DRAGEN v3.10.17), which is provided inside the DRAGEN TSO 500 docker image.

    Licenses

    • TSO500Combined license

    • TSO500_HRD license (to analyze data generated with the TSO 500 HRD add-on kit)

    TSO500Combined license has been pre-installed to DRAGEN servers in manufacturing since August 2022 and TSO500_HRD since February 2025 and additionally distributed to DRAGEN servers connected online. To generate a list of installed DRAGEN server licenses, run the following command: /usr/bin/dragen_lic. If a license is not installed, contact Illumina Customer Care at [email protected] for the license.

    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 DRAGEN pipelines

    DRAGEN TSO 500 Analysis Software v2.6.1 is multi-version compatible. Multi-version compatibility refers to ability to be installed on a single DRAGEN server with software running a different version of DRAGEN software. For example, multi-version compatible pipelines running DRAGEN v4.3.6 can be co-installed on a server alongside DRAGEN TSO 500 pipelines running DRAGEN v3.10.17. For more details on DRAGEN multi-version compatibility, please visit page 7 of the DRAGEN v4.3.6 software release notes.

    Software versions without multi-version compatibility referred to as single-version compatible. DRAGEN TSO 500 Analysis Software v2.6.1 will disrupt installations of single-version compatible software from the DRAGEN server. To uninstall a previous version of DRAGEN TSO 500 Analysis Software, refer to the respective guide.

    Compatibility of software for co-installation with DRAGEN TSO 500 v2.6.1 on a DRAGEN server is summarized in the table below:

    Software
    Version
    Type
    Compatible

    DRAGEN TSO 500

    2.6.0

    Single-version

    No

    DRAGEN TSO 500

    2.5.4

    Multi-version

    Yes*

    DRAGEN TSO 500

    2.5.3 or below

    Single-version

    *DRAGEN TSO 500 Analysis Software v2.6.1 can run on a single server with another multi-version compatible DRAGEN TSO 500 Analysis Software, e.g. DRAGEN TSO 500 v2.5.4 (v2.5.4 should be installed before installing v2.6.1). DRAGEN TSO 500 Analysis Software v2.6.1 can be co-installed with multi-version compatible DRAGEN TSO 500 ctDNA Analysis Software or other DRAGEN pipelines with any order of installation.

    **For example, DRAGEN Enrichment, DRAGEN Germline, DRAGEN WGS Heme v1.0.0 and others. Order of installation does not matter.

    Installation Instructions

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

    1. Contact Illumina Customer Care at [email protected] 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.

    It is recommended to use a command line tool like wget or curl to download the file rather It is recommended to use a command line tool like wget or curl to download the file rather than pasting the link into the web browser bar. For example:

    curl -o {filename} "{link}"

    wget -O {filename} '{link}'

    Where the file name is the installation script file name, and the link is provided by Illumina Customer Care.

    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.

    Installation Script: install_DRAGEN_TSO500-2.6.1.run

    MD5sum value:

    sha256:83caa30860363e1c7027f1b021157ce32d78b31841bec788611796ed470e96bd

    1. Use the following command to update the run script permission: chmod +x /staging/install_DRAGEN_TSO500-2.6.1.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.1.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.1.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.1.sh Refer to if any errors occur.

    License Installation

    Review license requirements, how to check which licenses are installed and how to receive a license in Licenses. Licenses can be installed before or after DRAGEN TSO 500 software installation.

    To install a license (TSO500Combined and/or TSO500_HRD) on a DRAGEN server connected to the internet:

    1. Confirm that the server is connected to the Internet, example: ping www.illumina.com

    2. Run the following command: /usr/bin/dragen_lic -i auto

    To install a license (TSO500Combined and/or TSO500_HRD) on a DRAGEN server not connected to the internet:

    1. Contact Customer Care at [email protected] to request a license file for each of the needed licenses

    2. Download and save the license file(s) to a location that is accessible from the DRAGEN server

    3. For each license file, run the command, where <license file received> is the absolute path to the license file: sudo /usr/bin/dragen_lic -i /tmp/<license file received>.bin

    To check the success of license installation, run: /usr/bin/dragen_lic. Installed licenses should be in the list.

    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.1.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.1.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.1: Docker image

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

    uninstall_DRAGEN_TSO500-2.6.1.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.

    Filter
    Note

    PASS

    PASS variants.

    base_quality

    Site filtered because median base quality of alt reads at this locus does not meet threshold.

    filtered_reads

    Site filtered because the fraction of reads is too large.

    fragment_length

    Site filtered because absolute difference between the median fragment length of alt reads and median fragment length of ref reads at this locus exceeds threshold.

    low_depth

    Site filtered because the read depth is too low.

    low_frac_info_reads

    Site filtered because the fraction of informative reads is below threshold.

    long_indel

    Site filtered because the indel length is too long.

    mapping_quality

    Site filtered because median mapping quality of alt reads at this locus does not meet threshold.

    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.

    Column
    Description

    Chromosome

    Chromosome

    Position

    Position of variant

    RefCall

    Reference base

    AltCall

    Alternate base

    VAF

    Variant allele frequency

    Depth

    Coverage of position

    Copy Number VCF

    File name: {SAMPLE_ID}.cnv.vcf

    The copy number VCF file contains CNV calls for DNA libraries for 500 of the 523 genes from the TSO 500 manifest, as some genes have high homology to other genes or only have probes covering one exon region. The CNV call indicates fold change results for each gene classified as reference, deletion, or amplification. The CNV vcf reports fold change for all 500 genes while the Combined Variant output reports only genes that have events qualifying as amplifications or deletions.

    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.

    In analysis versions prior to v2.5, <DEL> calls in the VCF are marked as LowValidation. The LowValidation filter indicates that the calls have been validated only with in silico data sets and are provided as information only.

    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.

    HRD JSON

    The GIS Score is a Proprietary Genomic Instability Score (GIS) indicating level of genomic instability in sample genome. Combination of Loss of Heterozygosity (LOH), Telomeric allelic imbalance and Large-scale State Transitions (LST) scores. The GIS scores provided by TruSight Oncology 500 HRD show good correlation (R2= 0.98) with Myriad Genetics GIS however they are not identical (Refer to TruSight Oncology 500 HRD Product Data Sheet Doc# M-GL-00748 for more details). GIS from alternative HRD assays should be not be considered equivalent to Illumina/Myriad GIS.

    Within the HRD output (Logs_Intermediates/Gis/), LOH variants are not denoted in the .abcn_annotated.vcf; instead this information can be found in the abcn_genes.tsv

    *The GIS algorithm within the TSO500 pipeline (which does not have a cell line mode due to the TSO500 pipeline being non-configurable) is only intended for FFPE samples. Cell line samples will not accurately report GIS results as the tumor fraction (>90%) is too high to reliably distinguish tumor vs germline variants.

    DNA Analysis Methods
    n=[(200Y)−2(100−X)]/Xn=[(200Y)-2(100-X)]/Xn=[(200Y)−2(100−X)]/X

    Note that NovaSeq X Series has a different run set up screen than other instrument platforms, as it allows the user to include multiple assay configurations in one run. DRAGEN TSO 500 ctDNA supports multi-assay flow cell analysis starting in version 2.6.3.

    For ctDNA v2.6.0 and above, in order to run TSO 500 ctDNA on NovaSeq X Series, enter the appropriate Read 1, Read 2, Index 1 and Index 2 described in the instructions below.

    BaseSpace Run Planning tool cannot generate a valid sample sheet for the NovaSeq 6000Dx TSO 500 ctDNA Analysis Application on Illumina Run Manager. Refer to Sample Sheet Requirements page to create a valid sample sheet.

    Step 1: Run Settings

    Parameter Name
    Required
    Description

    Run Name

    Required

    Run Name can contain 255 alphanumeric characters, dashes, underscores, periods, and spaces; and must start with an alphanumeric, a dash or an underscore.

    Run Description

    Optional

    Run Description can contain 255 characters except square brackets, asterisks, and commas.

    Instrument Platform

    Required

    Choose from TSO 500 ctDNA supported instruments:

    • NovaSeq 6000/6000Dx

    • NovaSeq X Series

    Secondary Analysis

    Required

    Step 2: Configuration

    Note: On NovaSeq X Series, this page is called "Configuration 1". The right hand corner of the UI displays the Read 1, Read 2, Index 1 and Index 2 entered on the previous run settings screen.

    Parameter Name
    Required
    Description

    Application

    Required

    • DRAGEN TruSight Oncology 500 ctDNA Analysis Software - 2.6.1

    Description

    Optional

    Optional text field

    Library Prep Kit

    Required

    • TruSight Oncology 500 ctDNA (only for NovaSeq 6000/6000Dx instruments)

    • TruSight Oncology 500 ctDNA v2

    Index Adapter Kit

    Required

    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.

    Parameter Name
    Required
    Description

    Read Lengths: Read 1 and Read 2

    Required Not applicable on NovaSeq X Series

    Auto filled with the standard values, but can be optionally overwritten.

    Override Cycles

    Required on NovaSeq X Series

    Entered based on Run Settings read lengths & index 1 / index 2

    Lane Usage

    Not applicable on NovaSeq X Series

    Checkbox allows users to apply the same lane across samples.

    Lane

    Required if Lane Usage is unchecked

    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

    ICA Auto-launch Sample Sheet Requirements

    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.

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

    BRCA Large Rearrangement 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:

    Database
    Version

    gnomeAD

    2.1

    COSMIC

    v84

    ClinVar

    2019-02-04

    dbSNP

    v151

    1000 Genomes Project

    Phase 3 v5a

    RefSeq

    NCBI Homo sapiens Annotation Release 105.20201022

    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 (50).

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

    • 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 VariantsEligible Region Size(Mbp)TMB = {Filtered\ Variants \over Eligible\ Region\ Size (Mbp)}TMB=Eligible Region Size(Mbp)Filtered Variants​

    NonsynonymousTMB=Filtered Nonsynonymous VariantsEligible Region Size(Mbp)Nonsynonymous TMB = {Filtered\ Nonsynonymous\ Variants \over Eligible\ Region\ Size (Mbp)}NonsynonymousTMB=Eligible Region Size(Mbp)Filtered Nonsynonymous Variants​

    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. Normal reference files were generated by tabulating read counts for each microsatellite site. The normal file contains the read count distribution for each microsatellite site.

    MSI calling is assessed on a predefined list of 130 A and T repeats. The first step in calculating the MSI score is determining how many sites are assessable. A site is considered assessable if it has at least 60 spanning reads. A spanning read is defined as one that extends 5 bp before and after the repeat.

    Once assessable sites are identified, the distribution of repeat lengths is compared to the panel of normals. A site is classified as unstable if:

    • Jensen-Shannon distance ≥ 0.1, and

    • P-value ≤ 0.01.

    After all sites are evaluated, DRAGEN reports:

    • The total number of sites assessed

    • The count of unstable sites

    • The percentage of unstable sites across the sample

    Finally, the MSI score is calculated as:

    Genomic Instability Score

    Requires HRD add-on assay (included with v2 kits)

    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.

    Tumor fraction

    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

    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 Number (Beta)

    This is a beta feature. Beta feature results are included in the Combined Variant Output file and other files. However, disclaimers that the results are generated by beta features are only provided in the Combined Variant Output file. Requires HRD add-on assay.

    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.vcf, Logs_Intermediates/Gis/SAMPLE/SAMPLE.abcn_genes.tsv and Combined Variant Output file.

    Absolute copy number estimation has an upper limit of 6. While biological samples may exhibit copy numbers exceeding this value, the estimation algorithm does not report values above 6.

    Gene-level Loss of Heterozygosity (Beta)

    This is a beta feature. Beta feature results are included in the Combined Variant Output file and other files. However, disclaimers that the results are generated by beta features are only provided in the Combined Variant Output file. Requires HRD add-on assay.

    Gene-level loss of heterozygosity is calculated based on the minor copy number reported in the abcn_annotated.vcf. 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.

    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.

    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.

  • 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 novo graph 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 variant 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:

    Database
    Version

    gnomeAD

    2.1

    COSMIC

    v84

    ClinVar

    2019-02-04

    dbSNP

    v151

    1000 Genomes Project

    Phase 3 v5a

    RefSeq

    NCBI Homo sapiens Annotation Release 105.20201022

    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 (50).

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

    • 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 VariantsEligible Region Size(Mbp)TMB = {Filtered\ Variants \over Eligible\ Region\ Size (Mbp)}TMB=Eligible Region Size(Mbp)Filtered Variants​

    NonsynonymousTMB=Filtered Nonsynonymous VariantsEligible Region Size(Mbp)Nonsynonymous TMB = {Filtered\ Nonsynonymous\ Variants \over Eligible\ Region\ Size (Mbp)}NonsynonymousTMB=Eligible Region Size(Mbp)Filtered Nonsynonymous Variants​

    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. Normal reference files were generated by tabulating read counts for each microsatellite site. The normal file contains the read count distribution for each microsatellite site.

    MSI calling is assessed on a predefined list of 130 A and T repeats. The first step in calculating the MSI score is determining how many sites are assessable. A site is considered assessable if it has at least 60 spanning reads. A spanning read is defined as one that extends 5 bp before and after the repeat.

    Once assessable sites are identified, the distribution of repeat lengths is compared to the panel of normals. A site is classified as unstable if:

    • Jensen-Shannon distance ≥ 0.1, and

    • P-value ≤ 0.01.

    After all sites are evaluated, DRAGEN reports:

    • The total number of sites assessed

    • The count of unstable sites

    • The percentage of unstable sites across the sample

    Finally, the MSI score is calculated as:

    Genomic Instability Score

    Requires HRD add-on assay

    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

    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

    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 Number (Beta)

    This is a beta feature. Beta feature results are included in the Combined Variant Output file and other files. However, disclaimers that the results are generated by beta features are only provided in the Combined Variant Output file. Requires HRD add-on assay.

    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.vcf, Logs_Intermediates/Gis/SAMPLE/SAMPLE.abcn_genes.tsv and Combined Variant Output file.

    Absolute copy number estimation has an upper limit of 6. While biological samples may exhibit copy numbers exceeding this value, the estimation algorithm does not report values above 6.

    Gene-Level Loss of Heterozygosity (Beta)

    This is a beta feature. Beta feature results are included in the Combined Variant Output file and other files. However, disclaimers that the results are generated by beta features are only provided in the Combined Variant Output file. Requires HRD add-on assay.

    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.

    Expands flexibility across assays

    Override Cycles

    Auto-calculated or user-provided depending on workflow

    Maintains correct cycle definitions per sample

    Sample Sheet Creation in BaseSpace Run Planning tool

    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.

    Note that NovaSeq X Series has a different run set up configuration screen than other instrument platforms. TSO 500 does not support multi analysis, and in order to run TSO 500 on NovaSeq X Series, enter the appropriate Read 1, Read 2, Index 1 and Index 2 described in the instructions below.

    BaseSpace Run Planning tool cannot generate a valid sample sheet for NovaSeq 6000Dx Analysis Application. Refer to to create a valid sample sheet.

    Step 1: Run Settings

    Parameter Name
    Required
    Description

    Step 2: Configuration

    Note: On NovaSeq X Series, this page is called "Configuration 1". The right hand corner of the UI displays the Read 1, Read 2, Index 1 and Index 2 entered on the previous run settings screen.

    Parameter Name
    Required
    Description
    Notes

    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.

    Parameter Name
    Required
    Description

    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 .

    Guided Examples

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

    RNA Output

    Refer to RNA Analysis Methods 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:

    Filter Name
    Description

    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

    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

    Filter
    Filter Type
    Description

    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

    Fusion Object Field
    Source

    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

    Quality Control

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

    These metrics and guidelines apply to DRAGEN TSO 500 v2.1 and above.

    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)

    Metric
    Description
    Recommended Guideline Quality Threshold
    Variant Class

    NovaSeq 6000 or NovaSeq 6000Dx (RUO)

    Metric
    Description
    Recommended Guideline Quality Threshold
    Variant Class

    NextSeq 1000/2000

    Metric
    Description
    Recommended Guideline Quality Threshold
    Variant Class

    NovaSeq X

    Metric
    Description
    Recommended Guideline Quality Threshold
    Variant Class

    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.

    Metric
    Description
    Recommended Guideline Quality Threshold
    Variant Class

    RNA Sample QC

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

    Metric
    Description
    Recommended Guideline Quality Threshold
    Variant Class

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

    Installation of 2.6.2 on Standalone DRAGEN Server

    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

    • Network-attached storage (NAS) with enabled mkfifo if performing analysis for the TruSight Oncology 500 High-Throughput assay

    Software

    • Linux CentOS 7.9 operating system (or later) or Oracle Linux 8 (or later), one of which is provided on the server. Oracle Linux 8 is recommended.

    • Docker Software, see table below for minimum version needed. If sufficient Docker software is not present on the server, the TSO 500 installer will install compatible Docker software.

    • DRAGEN Server Software*, see table below for minimum version needed as the host version on the server. If sufficient DRAGEN software is not present on the server, the TSO 500 installer will install compatible DRAGEN software.

    Software Dependency
    Compatible
    Installs

    *The DRAGEN Server Software version may be higher than the DRAGEN version used by the DRAGEN TSO 500 v2.6.2 pipeline (DRAGEN v3.11.2), which is provided inside the DRAGEN TSO 500 docker image.

    Licenses

    • TSO500Combined license

    • TSO500_HRD license (to analyze data generated with the TSO 500 HRD add-on kit)

    TSO500Combined license has been pre-installed to DRAGEN servers in manufacturing since August 2022 and TSO500_HRD since February 2025 and additionally distributed to DRAGEN servers connected online. To generate a list of installed DRAGEN server licenses, run the following command: /usr/bin/dragen_lic. If a license is not installed, contact Illumina Customer Care at for the license.

    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 .

    • 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 DRAGEN pipelines

    DRAGEN TSO 500 Analysis Software v2.6.2 is multi-version compatible. Multi-version compatibility refers to ability to be installed on a single DRAGEN server with software running a different version of DRAGEN software. For example, multi-version compatible pipelines running DRAGEN v4.3.6 can be co-installed on a server alongside DRAGEN TSO 500 pipelines running DRAGEN v3.10.19+. For more details on DRAGEN multi-version compatibility, please visit .

    Software versions without multi-version compatibility referred to as single-version compatible. DRAGEN TSO 500 Analysis Software v2.6.2 will disrupt single-version compatible software on the DRAGEN server. To uninstall a previous version of DRAGEN TSO 500 Analysis Software, refer to the respective guide.

    Compatibility of software for co-installation with DRAGEN TSO 500 v2.6.2 on a DRAGEN server is summarized in the table below:

    Software
    Version
    Type
    Compatible

    *DRAGEN TSO 500 Analysis Software v2.6.2 can run on a single server with another multi-version compatible DRAGEN TSO 500 Analysis Software, e.g. DRAGEN TSO 500 v2.5.4 (v2.5.4 should be installed before installing v2.6.1). DRAGEN TSO 500 Analysis Software v2.6.2 can be co-installed with multi-version compatible DRAGEN TSO 500 ctDNA Analysis Software or other DRAGEN pipelines with any order of installation.

    **For example, DRAGEN Enrichment, DRAGEN Germline, DRAGEN WGS Heme v1.0.0 and others. Order of installation does not matter.

    Installation Instructions

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

    1. Contact Illumina Customer Care at 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.

    It is recommended to use a command line tool like wget or curl to download the file rather It is recommended to use a command line tool like wget or curl to download the file rather than pasting the link into the web browser bar. For example:

    curl -o {filename} "{link}"

    wget -O {filename} '{link}'

    Where the file name is the installation script file name, and the link is provided by Illumina Customer Care.

    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.

    Installation Script: install_DRAGEN_TSO500-2.6.2.run

    SHA-256 value: c477c36abcf0d05aea7ac9ab965ef83d522fe5af60c2a99a456cb9a2e3d47a7f

    1. Use the following command to update the run script permission: chmod +x /staging/install_DRAGEN_TSO500-2.6.2.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.2.run . The script installs compatible DRAGEN software and removes any previously installed versions.

    License Installation

    Review license requirements, how to check which licenses are installed and how to receive a license in . Licenses can be installed before or after DRAGEN TSO 500 software installation.

    To install a license (TSO500Combined and/or TSO500_HRD) on a DRAGEN server connected to the internet:

    1. Confirm that the server is connected to the Internet, example: ping www.illumina.com

    2. Run the following command: /usr/bin/dragen_lic -i auto

    To install a license (TSO500Combined and/or TSO500_HRD) on a DRAGEN server not connected to the internet:

    1. Contact Customer Care at to request a license file for each of the needed licenses

    2. Download and save the license file(s) to a location that is accessible from the DRAGEN server

    3. For each license file, run the command, where <license file received> is the absolute path to the license file: sudo /usr/bin/dragen_lic -i /tmp/<license file received>.bin

    To check the success of license installation, run: /usr/bin/dragen_lic. Installed licenses should be in the list.

    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.2.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.2.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.2: Docker image

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

    uninstall_DRAGEN_TSO500-2.6.2.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.

    Installation of v2.5.4 on Standalone DRAGEN Server

    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

    • Network-attached storage (NAS) with enabled mkfifo if performing analysis for the TruSight Oncology 500 High-Throughput assay

    Software

    The following software is required to successfully install DRAGEN TSO 500 v2.5.4:

    • Linux CentOS 7.9 operating system (or later) or Oracle Linux 8 (or later), one of which is provided on the server. Oracle Linux 8 is recommended.

    • Docker Software, see table below for minimum version needed. If sufficient Docker software is not present on the server, the TSO 500 installer will install compatible Docker software.

    • DRAGEN Server Software*, see table below for minimum version needed as the host version on the server. If sufficient DRAGEN software is not present on the server, the TSO 500 installer will install compatible DRAGEN software.

    Software Dependency
    Compatible
    Installs

    *The DRAGEN Server Software version may be higher than the DRAGEN version used by the DRAGEN TSO 500 v2.5.4 pipeline (DRAGEN v3.10.16), which is provided inside the DRAGEN TSO 500 docker image.

    Licenses

    • TSOCombined license

    • TSO500_HRD license (to analyze data generated with the TSO 500 HRD add-on kit)

    TSOCombined license has been pre-installed to DRAGEN servers in manufacturing since August 2022 and TSO500_HRD since February 2025 and additionally distributed to DRAGEN servers connected online. To generate a list of installed DRAGEN server licenses, run the following command: /opt/edico/bin/dragen_lic. If a license is not installed, contact Illumina Customer Care at for the license.

    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 .

    • 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 DRAGEN pipelines

    DRAGEN TSO 500 Analysis Software v2.5.4 is multi-version compatible. Multi-version compatibility refers to ability to be installed on a single DRAGEN server with software running a different version of DRAGEN software. For example, multi-version compatible pipelines running DRAGEN v4.3.6 can be co-installed on a server alongside DRAGEN TSO 500 pipelines running DRAGEN v3.10.17. For more details on DRAGEN multi-version compatibility, please visit .

    Software versions without multi-version compatibility referred to as single-version compatible. DRAGEN TSO 500 Analysis Software v2.5.4 will disrupt installations of single-version compatible software from the DRAGEN server. To uninstall a previous version of DRAGEN TSO 500 Analysis Software, refer to the respective guide.

    Compatibility of software for co-installation with DRAGEN TSO 500 v2.5.4 on a DRAGEN server is summarized in the table below:

    Software
    Version
    Type
    Compatible

    *DRAGEN TSO 500 Analysis Software v2.5.4 can run on a single server with another multi-version compatible DRAGEN TSO 500 Analysis Software, e.g. DRAGEN TSO 500 v2.6.1, and should be installed before v2.6.1. DRAGEN TSO 500 Analysis Software v2.5.4 can be co-installed with multi-version compatible DRAGEN TSO 500 ctDNA Analysis Software or other DRAGEN pipelines with any order of installation.

    **For example, DRAGEN Enrichment, DRAGEN Germline, DRAGEN WGS Heme v1.0.0 and others. Order of installation does not matter.

    Installation Instructions

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

    1. Contact Illumina Customer Care at 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.

    It is recommended to use a command line tool like wget or curl to download the file rather than pasting the link into the web browser bar. For example:

    curl -o {filename} "{link}"

    wget -O {filename} '{link}'

    Where the file name is the installation script file name, and the link is provided by Illumina Customer Care.

    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.

    Installation Script: install_DRAGEN_TSO500-2.5.4.run

    MD5sum: sha256:0d871d8b93b4e535c0c1b5614c180fdb815f80764274279881c8a25a4e153160

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

    2. Use the following command to run the installation script (run time ~ 20 mins):

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

    License Installation

    Review license requirements, how to check which licenses are installed and how to receive a license in . Licenses can be installed before or after DRAGEN TSO 500 software installation.

    To install a license (TSOCombined and/or TSO500_HRD) on a DRAGEN server connected to the internet:

    1. Confirm that the server is connected to the Internet, example: ping www.illumina.com

    2. Run the following command: /usr/bin/dragen_lic -i auto

    To install a license (TSOCombined and/or TSO500_HRD) on a DRAGEN server not connected to the internet:

    1. Contact Customer Care at to request a license file for each of the needed licenses

    2. Download and save the license file(s) to a location that is accessible from the DRAGEN server

    3. For each license file, run the command, where <license file received> is the absolute path to the license file: sudo /usr/bin/dragen_lic -i /tmp/<license file received>.bin

    To check the success of license installation, run: /usr/bin/dragen_lic. Installed licenses should be in the list.

    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.5.4.sh

    The script checks that:

    • All required services are running

    • Proper Docker image is installed

    • DRAGEN TSO 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 TSO 500 Analysis Software installation includes an uninstall script called uninstall_DRAGEN_TSO500-2.5.4.sh, which is located in /usr/local/bin.

    Executing the uninstall script removes the following assets:

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

    • Resources found in /staging/illumina/DRAGEN_TSO500

    • The dragen_tso500:2.5.4: Docker image

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

    uninstall_DRAGEN_TSO500-2.5.4.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.

    Analysis Output

    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

    • Results

      • Metrics Output TSV (all pair IDs)

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

        • Combined Variant Output 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.

    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

    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

    The Results subfolder contains the following files:

    • Results

      • MetricsOutput.tsv

      • <Pair_id>

        • CombinedVariantOutput.tsv

    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

    Errors Folder Structure

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

    • Errors

      • Errors.tsv

    Installation of 2.5.3 on Standalone DRAGEN Server

    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

    • Network-attached storage (NAS) with enabled mkfifo if performing analysis for the TruSight Oncology 500 High-Throughput assay

    Software

    The following software is required to successfully install DRAGEN TSO 500 v2.5.3:

    • Linux CentOS 7.9 operating system (or later) or Oracle Linux 8 (or later), one of which is provided on the server. Oracle Linux 8 is recommended.

    • Docker Software, see table below for minimum version needed. If sufficient Docker software is not present on the server, the TSO 500 installer will install compatible Docker software.

    • DRAGEN Server Software, see table below for minimum version needed as the host version on the server. If sufficient DRAGEN software is not present on the server, the TSO 500 installer will install compatible DRAGEN software.

    Software Dependency
    Compatible
    Installs

    Licenses

    • TSOCombined license

    • TSO500_HRD license (to analyze data generated with the TSO 500 HRD add-on kit)

    TSOCombined license has been pre-installed to DRAGEN servers in manufacturing since August 2022 and TSO500_HRD since February 2025 and additionally distributed to DRAGEN servers connected online. To generate a list of installed DRAGEN server licenses, run the following command: /opt/edico/bin/dragen_lic. If a license is not installed, contact Illumina Customer Care at for the license.

    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 .

    • 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 DRAGEN Pipelines

    DRAGEN TSO 500 Analysis Software v2.5.3 is single-version compatible. It does not include multi-version compatibility that refers to ability to be installed on a single DRAGEN server with software running a different version of DRAGEN software. For example, multi-version compatible pipelines running DRAGEN v4.3.6 can be co-installed on a server alongside DRAGEN TSO 500 pipelines running DRAGEN v3.10.17. For more details on DRAGEN multi-version compatibility, please visit .

    Compatibility of software for co-installation with DRAGEN TSO 500 v2.5.3 on a DRAGEN server is summarized in the table below:

    Software
    Version
    Type
    Compatible

    *Install DRAGEN TSO 500 Analysis Software v2.6.0 after installing 2.5.3. If v2.5.3 is installed after v2.6.0, re-execute the installation script for v2.6.0 to install the compatible version of DRAGEN Software without impacting v2.5.3.

    ** When co-installing v2.5.3 with DRAGEN TSO 500 ctDNA software on the same DRAGEN server, install the software with the highest corresponding DRAGEN Software version last. Find DRAGEN software versions for DRAGEN TSO 500 ctDNA software in parentheses: v2.1.1 (v3.10.9), v2.5.0 (v3.10.15), 2.6.0 (v3.10.17), 2.6.1 (v3.10.18).

    ***For example, DRAGEN Enrichment, DRAGEN Germline, and others

    Installation Instructions

    As a root user, perform the following steps to install DRAGEN TSO 500 v2.5.3 Analysis Software:

    1. Contact Illumina Customer Care at to obtain the DRAGEN TSO 500 Analysis Software installer package.

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

    It is recommended to use a command line tool like wget or curl to download the file rather than pasting the link into the web browser bar. For example:

    curl -o {filename} "{link}"

    wget -O {filename} '{link}'

    Where the file name is the installation script file name, and the link is provided by Illumina Customer Care.

    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.

    Installation Script: install_DRAGEN_TSO500-2.5.3.run

    MD5sum: sha256:ab9fae7ba58842d797ba689e702693c0fd7a5c2852dda610dce6d68152fe1f8d

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

    2. Use the following command to run the installation script (run time ~ 20 mins):

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

    License Installation

    Review license requirements, how to check which licenses are installed and how to receive a license in . Licenses can be installed before or after DRAGEN TSO 500 software installation.

    To install a license (TSOCombined and/or TSO500_HRD) on a DRAGEN server connected to the internet:

    1. Confirm that the server is connected to the Internet, example: ping www.illumina.com

    2. Run the following command: /opt/edico/bin/dragen_lic -i auto

    To install a license (TSOCombined and/or TSO500_HRD) on a DRAGEN server not connected to the internet:

    1. Contact Customer Care at to request a license file for each of the needed licenses

    2. Download and save the license file(s) to a location that is accessible from the DRAGEN server

    3. For each license file, run the command, where <license file received> is the absolute path to the license file: sudo /opt/edico/bin/dragen_lic -i /tmp/<license file received>.bin

    To check the success of license installation, run: /opt/edico/bin/dragen_lic. Installed licenses should be in the list.

    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.5.3.sh

    The script checks that:

    • All required services are running

    • Proper Docker image is installed

    • DRAGEN TSO 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.5.3.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.5.3: Docker image

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

    uninstall_DRAGEN_TSO500-2.5.3.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.

    Sample Sheet Requirements

    DRAGEN TSO 500 Analysis Software has optional and required fields that are required in addition to general sample sheet requirements. Follow the steps below to create a valid samplesheet.

    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), certain sections and required values can deviate from the standard requirements. These deviations are noted in the information below.

    The analysis fails if the sample sheet requirements are not met.

    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 BCL Convert Settings section, enter the following required parameters:

    [BCLConvert_Settings] Section

    Sample Parameter
    Required
    Details
    1. In the BCL Convert Data section, enter the following parameters for each sample.

    [BCLConvert_Data] Section

    Sample Parameter
    Required
    Details
    1. In the TSO 500 Data section, enter the following parameters:

    TSO 500 Data Section header changes depending on the deployment:

    • Standalone DRAGEN Server and ICA with Manual Launch: TSO500S_Data

    • ICA with Auto-launch: Cloud_TSO500S_Data

    [TSO500S_Data] Section

    Sample Parameter
    Required
    Details

    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 . 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 for this section's requirements.

    [Cloud_TSO500S_Settings] Section

    Parameters
    Required
    Details

    [Cloud_Data] Section

    Parameters
    Required
    Details

    [Cloud_Settings] Section

    Parameter
    Required
    Details

    Sample Sheet Requirements

    DRAGEN TSO 500 Analysis Software has optional and required fields that are required in addition to general sample sheet requirements. Follow the steps below to create a valid sample sheet.

    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.

    Installation of TSO 500 ctDNA v2.6.2, v2.6.3 on Standalone DRAGEN Server

    Overview

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

    1. DRAGEN TruSight Oncology 500 ctDNA Analysis Software itself

    RNA Output

    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:

    Filter Name
    Description

    Analysis Output

    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.

    Quality Control

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

    These metrics and guidelines apply to DRAGEN TSO 500 v2.1 and above.

    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.

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

  • 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

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

  • _tags.json

  • Logs_intermediates

  • Errors—This folder is only present when analysis fails

  • Sample_<#>

  • _tags.json

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

  • FastqGeneration

  • MetricsOutput

  • DnaDragenExonCnvCaller

  • DnaFastqValidation

  • Gis

  • Tmb

  • SampleAnalysisResults

  • SampleSheetValidation

  • passing_sample_steps.json

  • RnaFusion

  • Contamination

  • Annotation

  • RnaAnnotation

  • RnaDragenCaller

  • RnaSpliceVariantCalling

  • RunQc

  • FastqDownsample

  • PassingSampleSteps

  • ResourceVerification

  • LrCalculator

  • LrAnnotation

  • RnaQcMetrics

  • RnaFastqValidation

  • TruSight Oncology 500 (NovaSeq 6000, NextSeq 550)

    multiallelic

    Site filtered because more than two alt alleles pass tumor LOD.

    no_reliable_supporting_read

    Site filtered because no reliable supporting somatic read exists.

    read_position

    Site filtered because median of distances between start/end of read and this locus is below threshold.

    str_contraction

    Site filtered due to suspected PCR error where the alt allele is one repeat unit less than the reference.

    too_few_supporting_reads

    Site filtered because there are too few supporting reads in the tumor sample.

    weak_evidence

    Somatic variant score (SQ) does not meet threshold.

    systematic_noise

    Site filtered based on evidence of systematic noise in normal sample.

    excluded_regions

    Site overlaps with VC excluded regions bed.

    CytoBand

    Cytoband of variant

    GeneName

    Name of gene if applicable. A semicolon delimited list is used for multiple genes.

    VariantType

    Type of the variant: SNV, insertion, deletion, MNV

    CosmicIDs

    Cosmic IDs, if multiple concatenated by “;”

    MaxCosmicCount

    Maximum Cosmic study count

    AlleleCountsGnomadExome

    Variant allele count in gnomAD exome database

    AlleleCountsGnomadGenome

    Variant allele count in gnomAD genome database

    AlleleCounts1000Genomes

    Variant allele count in 1000 genomes database

    MaxDatabaseAlleleCounts

    Maximum variant allele count over the three databases

    GermlineFilterDatabase

    TRUE if variant was filtered by the database filter

    GermlineFilterProxi

    TRUE if variant was filtered by the proxi filter

    CodingVariant

    TRUE if variant is in the coding region

    Nonsynonymous

    TRUE if variant has any transcript annotations with nonsynonymous consequences

    IncludedinTMBNumerator

    TRUE if variant is used in the TMB calculation

    • BaseSpace/Illumina Connected Analytics (to generate sample sheet for cloud analysis. May also be used for analysis on a DRAGEN server.)

    • Local (only for analysis onboard the sequencer— not applicable to TSO 500 ctDNA)

    • None (to generate a sample sheet for analysis on a DRAGEN server. Note that cloud sample sheets may also be used for local analysis.)

    Read 1

    Required on Instrument Platform NovaSeq X Series

    • Fill with value 151 for TSO 500 ctDNA analysis

    Index 1

    Required on Instrument Platform NovaSeq X Series

    • Fill with value 10 for TSO 500 ctDNA analysis

    Index 2

    Required on Instrument Platform NovaSeq X Series

    • Fill with value 10 for TSO 500 ctDNA analysis

    Read 2

    Required on Instrument Platform NovaSeq X Series

    • Fill with value 151 for TSO 500 ctDNA analysis

    Sample Container ID

    Optional

    • Unique Identifier for the container that holds the sample

    TSO 500 ctDNA:

    • TruSight Oncology 500 ctDNA (NovaSeq6000Dx)

    • TruSight Oncology 500 ctDNA (NovaSeq6000)

    TSO 500 ctDNA v2:

    • TruSight Oncology 500 ctDNA Index Set A and B (UDP 1-192) (NovaSeq6000Dx, NovaSeqX Series)

    • TruSight Oncology 500 ctDNA Index Set A and B (UDP 1-192) (NovaSeq6000)

    Specify lanes for each sample. The unmarked checkbox at the top of the dropdown selects all lanes.

    Index ID

    Required

    Index set ID options are based on selected Index Adapter Kit

    Project

    Optional

    Optional field to describe the associated project

    Starts from Fastq

    Required

    True or False

    If auto-launching TSO 500 ctDNA from BCL files, set the value to False. If auto-launching TSO 500 ctDNA from FASTQ after auto-launching BCL Convert, set the value to True.

    DNA Barcode Mismatches Index 1

    DNA Barcode Mismatches Index 2

    Required on NovaSeq X

    Default value is set to 1.

    These fields are required by NovaSeq X and represent BCL Convert settings for index diversity checks when demultiplexing. These values are not used in TSO 500 ctDNA analysis.

    [email protected]

    No

    DRAGEN TSO 500 ctDNA

    2.6.2+

    Multi-version

    Yes

    DRAGEN TSO 500 ctDNA

    2.6.1 or below

    Single-version

    No

    DRAGEN pipelines**

    4.3.6+

    Multi-version

    Yes

    DRAGEN pipelines**

    4.2 or below

    Single-version

    No

    Troubleshooting
    Canonical
  • Consequence

  • MIN_SUPPORT

    Confidence filter

    The fusion candidate has very few fusion supporting reads (< 5 supporting read pairs).

    READ_THROUGH

    Confidence filter

    The breakpoints are cis neighbors (< 200 kbp) on the reference genome.

    ANCHOR_SUPPORT

    Information only

    Read alignments of fusion supporting reads are not long enough (12 bp) at either of the two breakpoints.

    HOMOLOGOUS

    Information only

    The candidate is likely a false candidate generated because the two genes involved have high gene homology.

    LOW_ALT_TO_REF

    Information only

    The number of fusion supporting reads is < 1% of the number of reads supporting the reference transcript at either of the two breakpoints.

    LOW_GENE_COVERAGE

    Information only

    Each breakpoint in an enriched gene has fewer than 125 bp with nonzero read coverage.

    NO_COMPLETE_SPLIT_READS

    Confidence filter

    For every fusion-supporting split read, the total number of aligned bases across two breakpoints is less 60% of the read length.

    UNENRICHED_GENE

    Confidence filter

    Neither of the two parent genes is in the enrichment panel.

    Gene B Breakpoint

    [Information only] The chromosome and offset of the Gene B side of the fusion.

    Gene B Location

    Location of the breakpoint within Gene B: - IntactExon—Matches exon boundary - BrokenExon—Inside an exon - Intronic—Within an intron - Intergenic—No gene overlap (currently excluded) If multiple genes in Gene B, then semicolon separated list of locations. This column is used internally to identify genes to report when a breakpoint occurs in a region overlapping multiple genes. Occasionally, additional values are listed for genes that were excluded from the GeneB list.

    Gene B Sense

    Boolean indicating whether left/right breakpoint order suggests fusion transcript is in the same sense of Gene B. If multiple genes are in Gene B, then semicolon separated list of bools.

    Gene B Strand

    Strand of Gene B, + for forward, - for reverse.

    Score

    The quality of fusion as determined by DRAGEN server.

    Filter

    The filter associated with the fusion as determined by the respective caller. Results from different callers are not equivalent.

    Ref A Dedup

    Gene A uniquely mapping reads paired across or split by the junction. Does not support fusion. Duplicate reads are not included.

    Ref B Dedup

    Gene B uniquely mapping reads paired across or split by the junction. Does not support fusion. Duplicate reads are not included.

    Alt Split Dedup

    Uniquely mapping reads split by the junction. Supports fusion. Duplicate reads are not included.

    Alt Pair Dedup

    Uniquely mapping reads paired across junction. Supports fusion. Duplicate reads are not included.

    KeepFusion

    The determination whether the fusion should be kept or dropped from the list of fusions.

    Fusion Directionality Known

    Whether fusion directionality is known and indicated by gene order.

    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

  • LowQ

    Splice variant score < passing quality score threshold value of 1.

    PASS

    Splice variant score ≥ passing quality score threshold value of 1.

    LowUniqueAlignments

    All splice junction supporting reads map to a unique genomic interval near at least one of the two splice sites.

    DOUBLE_BROKEN_EXON

    Confidence filter

    If both breakpoints are distant from annotated exon boundaries, the number of supporting reads do not satisfy a high threshold requirement (≥ 10 supporting reads).

    LOW_MAPQ

    Confidence filter

    All fusion supporting read alignments at either of the breakpoints have MAPQ < 20.

    LOW_UNIQUE_ALIGNMENTS

    Confidence filter

    All fusion supporting read alignments map to a unique genomic interval at either of the breakpoints.

    LOW_SCORE

    Confidence filter

    Gene A

    The gene associated with the A side of the fusion. A semicolon delimited list is used for multiple genes.

    Gene B

    The gene associated with the B side of the fusion. A semicolon delimited list is used for multiple genes.

    Gene A Breakpoint

    [Information only] The chromosome and offset of the Gene A side of the fusion.

    Gene A Location

    Location of the breakpoint within Gene A: - IntactExon—Matches exon boundary - BrokenExon—Inside an exon - Intronic—Within an intron - Intergenic—No gene overlap (currently excluded) If multiple genes are in Gene A, then semicolon separated list of locations. This column is used internally to identify genes to report when a breakpoint occurs in a region overlapping multiple genes. Occasionally, additional values are listed for genes that were excluded from the GeneA list.

    Gene A Sense

    Boolean indicating whether left/right breakpoint order suggests fusion transcript is in the same sense of Gene A. If multiple genes are in Gene A, then semicolon separated list of bools.

    Gene A Strand

    Strand of Gene A, + for forward, - for reverse.

    The fusion candidate has probabilistic score as determined by the features of the candidate.

    All

    All

    Small variant TMB

    MEDIAN_INSERT_SIZE

    The median fragment length in the sample.

    ≥ 70

    Small variant TMB

    USABLE_MSI_SITES

    The number of MSI sites usable for MSI calling.

    ≥ 40

    MSI

    MEDIAN_BIN_COUNT_CNV_TARGET

    The median raw bin count per CNV target.

    ≥ 1.0

    CNV

    Fusion Splice

    GENE_MEDIAN_COVERAGE*

    The median deduped coverage across all genes in the RNA panel (55 genes).

    N/A

    Fusion Splice

    PCT_PF_READS (%)

    Total percentage of reads passing filter.

    ≥80.0

    All

    PCT_Q30_R1 (%)

    Percentage of Read 1 reads with quality score ≥ 30.

    ≥80.0

    All

    PCT_Q30_R2 (%)

    Percentage of Read 2 reads with quality score ≥ 30.

    PCT_PF_READS (%)

    Total percentage of reads passing filter.

    ≥55.0

    All

    PCT_Q30_R1 (%)

    Percentage of Read 1 reads with quality score ≥ 30.

    ≥80.0

    All

    PCT_Q30_R2 (%)

    Percentage of Read 2 reads with quality score ≥ 30.

    PCT_Q30_R1 (%)

    Percentage of Read 1 reads with quality score ≥ 30.

    ≥85.0

    All

    PCT_Q30_R2 (%)

    Percentage of Read 2 reads with quality score ≥ 30.

    ≥85.0

    All

    PCT_Q30_R1 (%)

    Percentage of Read 1 reads with quality score ≥ 30.

    ≥85.0

    All

    PCT_Q30_R2 (%)

    Percentage of Read 2 reads with quality score ≥ 30.

    ≥85.0

    All

    CONTAMINATION_SCORE

    The contamination score is based on VAF distribution of SNPs.

    ≤ 1457

    All

    MEDIAN_EXON_COVERAGE

    Median exon fragment coverage across all exon bases.

    ≥ 150

    Small variant TMB

    PCT_EXON_50X

    Percent exon bases with 50x fragment coverage.

    MEDIAN_CV_GENE_500X

    The median CV for all genes with median coverage > 500x. Genes with median coverage > 500x are likely to be highly expressed. Higher CV median > 500x indicates an issue with library preparation (poor sample input and/or probes pulldown issue).

    <= 0.93

    Fusion Splice

    MEDIAN_INSERT_SIZE

    The median fragment length in the sample.

    ≥ 80

    Fusion Splice

    TOTAL_ON_TARGET_READS

    The total number of reads that map to the target regions.

    ≥80.0

    ≥80.0

    ≥ 90.0

    ≥ 9000000

    DRAGEN TSO 500

    2.5.3 or below

    Single-version

    No

    DRAGEN TSO 500 ctDNA

    2.6.2+

    Multi-version

    Yes

    DRAGEN TSO 500 ctDNA

    2.6.1 or below

    Single-version

    No

    DRAGEN pipelines**

    4.3.6+

    Multi-version

    Yes

    DRAGEN pipelines**

    4.2 or below

    Single-version

    No

    For Apptainer, use the following command: sudo TMPDIR=/staging /staging/install_DRAGEN_TSO500-2.6.2.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.

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

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

  • 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.2.sh Refer to Troubleshooting if any errors occur.

  • Docker

    20.10 or greater

    Docker 20.10.15

    DRAGEN Server Software*

    v3.11.x, where x ≥ 2

    DRAGEN Software 3.11.2

    DRAGEN TSO 500

    2.6.1

    Multi-version

    Yes

    DRAGEN TSO 500

    2.6.0

    Single-version

    No

    DRAGEN TSO 500

    2.5.4

    Multi-version

    [email protected]
    Docker website
    page 7 of the DRAGEN v4.3.6 software release notes
    [email protected]
    Licenses
    [email protected]

    Yes*

    DRAGEN TSO 500 ctDNA

    2.6.2+

    Multi-version

    Yes

    DRAGEN TSO 500 ctDNA

    2.6.1 or below

    Single-version

    No

    DRAGEN pipelines**

    4.3.6+

    Multi-version

    Yes

    DRAGEN pipelines**

    4.2 or below

    Single-version

    No

    For Apptainer, use the following command: sudo TMPDIR=/staging /staging/install_DRAGEN_TSO500-2.5.4.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.

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

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

  • Use the following command to build the DRAGEN server hash table (run time ~ 1 hr): /usr/local/bin/build-hashtable_DRAGEN_TSO500-2.5.4.sh Refer to Troubleshooting if any errors occur.

  • Docker

    20.10 or greater

    Docker 20.10.15

    DRAGEN Server Software*

    v3.10.x, where x >=19, v4.3+

    DRAGEN Software 3.10.19

    DRAGEN TSO 500

    2.6.1

    Multi-version

    Yes*

    DRAGEN TSO 500

    2.6.0

    Single-version

    No

    DRAGEN TSO 500

    2.5.3 or below

    Single-version

    [email protected]
    Docker website
    page 7 of the DRAGEN v4.3.6 software release notes
    [email protected]
    Licenses
    [email protected]

    No

    DRAGEN TSO 500

    2.6.1+

    Multi-version

    No

    DRAGEN TSO 500 ctDNA

    1.2 or below

    Single-version

    No

    DRAGEN TSO 500 ctDNA

    2.1.1, 2.5.0, 2.6.0, 2.6.1

    Single-version

    Yes**

    DRAGEN TSO 500 ctDNA

    2.6.2+

    Multi-version

    No

    DRAGEN pipelines***

    3.10.16

    Single-version

    Yes

    DRAGEN pipelines***

    Any version except 3.10.16

    Single- or multi-version

    No

    For Apptainer, use the following command: sudo TMPDIR=/staging /staging/install_DRAGEN_TSO500-2.5.3.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.

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

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

  • 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.5.3.sh Refer to Troubleshooting if any errors occur.

  • Docker

    20.10 or greater

    Docker 20.10.15

    DRAGEN Software

    v3.10.x where x is 16 or greater

    DRAGEN Software 3.10.16

    DRAGEN TSO 500

    2.5.2 or below

    Single-version

    No

    DRAGEN TSO 500

    2.5.4

    Multi-version

    No

    DRAGEN TSO 500

    2.6.0

    Single-version

    [email protected]
    Docker website
    page 7 of the DRAGEN v4.3.6 software release notes
    [email protected]
    Licenses
    [email protected]

    Yes*

    MinimumTrimmedReadLength

    Required

    Enter 35. Reads with a length trimmed below this point are masked.

    MaskShortReads

    Required

    Enter 35. Reads with a length trimmed below this point are masked.

    Sample_Description

    Not Required

    Sample description must meet the following requirements: - 1–50 characters. - Alphanumeric characters with underscores, dashes and spaces. If you enter a underscore, dash, or space, enter an alphanumeric character before and after. eg, Solid-FFPE_213.

    IndexAdapterKitName

    Not Required

    The Index Adapter Kit used.

    SoftwareVersion

    Required

    The DRAGEN component software version. For DRAGEN TSO 500 v2.5.3 and v2.5.4 specify 3.10.16.

    AdapterRead1

    Required

    If using 8 bp indexes starting with UP or CP (used with TSO 500): AGATCGGAAGAGCACACGTCTGAACTCCAGTCA If using 10 bp indexes with UDP (used with TSO 500 HT): CTGTCTCTTATACACATCTCCGAGCCCACGAGAC Analysis fails if the incorrect adapter sequences are used

    AdapterRead2

    Required

    If using 8 bp indexes starting with UP or CP (used with TSO 500): AGATCGGAAGAGCGTCGTGTAGGGAAAGAGTGT If using 10 bp indexes with UDP (used with TSO 500 HT): CTGTCTCTTATACACATCTGACGCTGCCGACGA Analysis fails if the incorrect adapter sequences are used

    AdapterBehavior

    Required

    Sample_ID

    Required

    Must match a Sample_ID listed in the TSO 500 Data section.

    Index

    Required

    Index 1 sequence valid for Index_ID assigned to matching Sample_ID in the TSO 500 Data section.

    Index2

    Required

    Index 2 sequence valid for Index_ID assigned to matching Sample_ID in the TSO 500 Data section.

    Lane

    Only for NovaSeq 6000 XP, NovaSeq 6000Dx, or NovaSeq X workflows

    Sample_ID

    Required

    The unique ID to identify a sample. The sample ID is included in the output file names. Sample IDs are not case sensitive. Sample IDs must have the following characteristics: - Unique for the run. - 1–40 characters. - No spaces. - Alphanumeric characters with underscores and dashes. If you use an underscore or dash, enter an alphanumeric character before and after the underscore or dash. eg, Sample1-T5B1_022515. - Cannot be called all, default, none, unknown, undetermined, stats, or reports. - Must match a Sample_ID listed in the TSO 500 Data section. - Illumina recommends that the sample ID be based on the pair ID. Example: <Pair_ID>-DNA,<Pair_ID>-RNA. - Each sample must have a unique combination of Lane (if applicable), sample ID, and index ID or the analysis will fail.

    Sample_Type

    Required

    Enter DNA or RNA. For HRD samples, this parameter must be DNA.

    Pair_ID

    Required

    A unique ID that links DNA and RNA from the same biological sample from the same individual. Pair ID shares, at most, one DNA and one RNA sample per run. eg, if a Sample_ID is TestSample1-DNA for DNA and TestSample1-RNA for RNA, the Pair_ID TestSample1 will link these samples that are on different rows in the sample sheet together. If the pair ID is associated with more than one DNA or RNA sample, the analysis fails.

    Sample_Feature

    Required when using HRD add-on kit

    SoftwareVersion

    Not Required

    The TSO500S software version

    StartsFromFastq

    Required

    Set the value to TRUE or FALSE. To auto-launch from BCL files, set to FALSE.

    Sample_ID

    Not Required

    The same sample ID used in the Cloud_TSO500S_Data section.

    ProjectName

    Not Required

    The BaseSpace project name.

    LibraryName

    Not Required

    Combination of sample ID and index values in the following format: sampleID_Index_Index2

    LibraryPrepKitName

    Not Required

    The Library Prep Kit used.

    GeneratedVersion

    Not Required

    The cloud GSS version used to create the sample sheet. Optional if manually updating a sample sheet.

    CloudWorkflow

    Not Required

    Ica_workflow_1

    Cloud_TSO500_Pipeline

    Required

    This value is a universal record number (URN). The valid values are:

    • Solid—urn:ilmn:ica:pipeline:e8eff7ef-1683-4f63-a0ba-9af542cd39e0#DRAGEN_TSO500_RUO_TISSUE_HT_v2_5_2_1_Pipeline

    • Solid HRD —urn:ilmn:ica:pipeline:172270e9-3678-45a9-a9f4-c9c7a0a32bb8#DRAGEN_TSO500_RUO_TISSUE_HRD_v2_5_2_1_Pipeline

    BCLConvert_Pipeline

    Required

    The value is a URN in the following format: urn:ilmn:ica:pipeline: <pipeline-ID>#<pipeline-name>

    Standard Sample Sheet Requirements
    [TSO500_Data] Section

    Enter trim This indicates that the BCL Convert software trims the specified adapter sequences from each read.

    Indicates which lane corresponds to a given sample. Enter a single numeric value per row. Cannot be empty, i.e the analysis fails if the Lane column is present without a value in each row.

    Required for HRD enriched samples. For DNA samples that have undergone HRD enrichment, enter HRD in this column of the sample sheet. If the sample has not undergone HRD enrichment, leave the field empty.

    Starts from FASTQ
    Auto-Launch with FASTQs generated by Standalone BCL Convert Pipeline (Start from FASTQ)

    Read 1

    Required on Instrument Platform NovaSeq X Series

    Fill with value 101 for TSO 500 analysis

    Index 1

    Required on Instrument Platform NovaSeq X Series

    Fill the value depending on the TSO 500 assay used:

    • TSO 500 v2: 10

    • TSO 500 HT: 10

    • TSO 500: 8

    Index 2

    Required on Instrument Platform NovaSeq X Series

    Fill the value depending on the TSO 500 assay used:

    • TSO 500 v2: 10

    • TSO 500 HT: 10

    • TSO 500: 8

    Read 2

    Required on Instrument Platform NovaSeq X Series

    Fill with value 101 for TSO 500 analysis

    Sample Container ID

    Optional

    Unique Identifier for the container that holds the sample

    Index Adapter Kit

    Required

    TruSight Oncology 500 ...

    • ...(NovaSeq6000Dx, NextSeq1000/2000, NovaSeqX Series)

    • ... (NovaSeq6000, NextSeq)

    TruSight Oncology 500 High Throughput ...

    • ...(NovaSeq6000Dx, NextSeq1000/2000, NovaSeqX Series)

    For sample sheet generation, each Library Prep Kit has two options for Index Adapter Kit. The options are need to ensure i5 indexes are in the correct orientation (forward or reverse complement) in the sample sheet. Select the option that aligns with the sequencing instrument used.

    Pair ID

    Required

    The identifier used to pair DNA and RNA samples in a run. The field is mandatory whether a sample is part of a pair, or not.

    To note: The Sample ID field in the generated samplesheet will be auto-filled based on the Pair ID values captured. “_dna” and “_rna” (for DNA and RNA samples respectively) will be appended to the Pair ID value to create the Sample ID.

    DNA Index ID

    Required

    Index set ID options are based on selected Index Adapter Kit.

    DNA Sample Feature

    Required

    Enter for HRD enriched DNA Samples.

    RNA Index ID

    Required

    Index set ID options are based on selected Index Adapter Kit.

    Project

    Optional

    Optional field to describe the associated project.

    Starts from Fastq

    Required

    True or False

    If auto-launching TSO 500 from BCL files, set the value to False. If auto-launching TSO 500 from FASTQ after auto-launching BCL Convert, set the value to True.

    DNA Barcode Mismatches Index 1

    DNA Barcode Mismatches Index 2

    RNA Barcode Mismatches Index 1

    RNA Barcode Mismatches Index 2

    Required on NovaSeq X

    Default value is set to 1.

    These fields are not used in TSO 500 analysis.

    Run Name

    Required

    Run Name can contain 255 alphanumeric characters, dashes, underscores, periods, and spaces; and must start with an alphanumeric, a dash or an underscore.

    Run Description

    Optional

    Run Description can contain 255 characters except square brackets, asterisks, and commas.

    Instrument Platform

    Required

    Choose from TSO 500 supported instruments:

    • NextSeq 500/550

    • NextSeq 1000/2000

    • NovaSeq 6000/6000Dx

    • NovaSeq X Series

    Secondary Analysis

    Required

    Application

    Required

    • DRAGEN TruSight Oncology 500 Analysis Software - v2.6.2 (includes HRD)*

    • DRAGEN TruSight Oncology 500 Analysis Software - v2.6.0.8 (F2-compatible, includes HRD)*

    • DRAGEN TruSight Oncology 500 Analysis Software - 2.6.0 (with HRD)

    • DRAGEN TruSight Oncology 500 Analysis Software - 2.6.0**

    *v2.6.2 and v2.6.0.8 are F2-compatible: can run on F2 or F1 nodes on ICA ** All v2.6 versions except v2.6.0 include support for HRD. If running HRD with v2.6.0, select "... Analysis Software v2.6.0 (with HRD)"

    Description

    Optional

    Optional text field

    Library Prep Kit

    Required

    • TruSight Oncology 500

    • TruSight Oncology 500 High Throughput

    • TruSight Oncology 500 v2

    Read Lengths: Read 1 and Read 2

    Required Not applicable on NovaSeq X Series

    Auto filled with the standard values, but can be optionally overwritten.

    Override Cycles

    Required on NovaSeq X Series

    Entered based on Run Settings read lengths & index 1 / index 2.

    Lane Usage

    Not applicable on NovaSeq X Series or NextSeq 1000 / 2000

    Checkbox allows users to apply the same lane across samples.

    Lane

    Required if Lane Usage is unchecked Not applicable on NextSeq 1000 / 2000

    Sample Sheet Requirements page
    BaseSpace Sequence Hub support site page
    NovaSeq 6000Dx: TSO 500 Auto-launch Analysis in Cloud
    NextSeq 500/550Dx: TSO 500 and Connected Insights Auto-launch Analysis in Cloud
    • BaseSpace/Illumina Connected Analytics (to generate sample sheet for cloud analysis. May also be used for analysis on a DRAGEN server.)

    • Local (only for analysis onboard the sequencer— not applicable to TSO 500)

    • None (to generate a sample sheet for analysis on a DRAGEN server. Note that cloud sample sheets may also be used for local analysis.)

    Specify lanes for each sample. The unmarked checkbox at the top of the dropdown selects all lanes.

    The analysis fails if the sample sheet requirements are not met.

    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

    Sample Parameter
    Required
    Details

    LibraryPrepKits

    Required

    Accepted values are:

    • TSO500 (for UP or CP indexes)

    • TSO500HT (for UDP indexes)

    • TSO500_v2 (for UDP v3 indexes) Analysis results may be compromised if this value does not match the index set used.

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

    [BCLConvert_Settings] Section

    Sample Parameter
    Required
    Details

    SoftwareVersion

    Required

    The DRAGEN component software version. For example, TruSight Oncology 500 2.6.0 requires 3.10.17. To ensure you are using the latest compatible version, refer to the software release notes.

    AdapterRead1

    Required

    If using TSO 500 Library Prep Kit (with UP or CP indexes): AGATCGGAAGAGCACACGTCTGAACTCCAGTCA If using TSO 500 HT Library Prep Kit (with UDP indexes): CTGTCTCTTATACACATCTCCGAGCCCACGAGAC

    If using TSO500 v2 Library Prep Kit (with UCP v3 indexes):

    CTGTCTCTTATACACATCT

    AdapterRead2

    Required

    If using TSO 500 Library Prep Kit: AGATCGGAAGAGCGTCGTGTAGGGAAAGAGTGT If using TSO 500 HT Library Prep Kit: CTGTCTCTTATACACATCTGACGCTGCCGACGA

    If using TSO500 v2 Library Prep Kit:

    CTGTCTCTTATACACATCT

    AdapterBehavior

    Required

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

    [BCLConvert_Data] Section

    Mismatches between the samples and index primers can cause incorrect results due to loss of positive sample identification. Enter sample IDs and assign indexes in the sample sheet before beginning library preparation. Record sample IDs, indexes, and plate well orientation for reference during library preparation.

    Sample Parameter
    Required
    Details

    Sample_ID

    Required

    The unique ID to identify a sample. The sample ID is included in the output file names. Sample IDs must have the following characteristics:

    • Case-insensitive unique values

    • 1 to 40 characters

    • Alphanumeric, dash, and underscore characters only

    • An underscore or dash must have an alphanumeric character immediately before and after

    Index

    Required

    Index 1 sequence valid for Index_ID assigned to matching Sample_ID in the TSO 500 Data section.

    Index2

    Required

    Index 2 sequence valid for Index_ID assigned to matching Sample_ID in the TSO 500 Data section.

    Lane

    Not Required. Only for NovaSeq 6000 XP, NovaSeq 6000Dx, or NovaSeq X workflows

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

    TSO 500 Data Section header changes depending on the deployment:

    • Standalone DRAGEN Server and ICA with Manual Launch: TSO500S_Data

    • ICA with Auto-launch: Cloud_TSO500S_Data

    • Illumina DRAGEN TruSight Oncology 500 (HRD) Analysis Application on NovaSeq 6000Dx: TSO500HRD_Data

    [TSO500S_Data] Section

    Sample Parameter
    Required
    Details

    Sample_ID

    Required

    The unique ID to identify a sample. The sample ID is included in the output file names. Sample IDs are not case sensitive. Sample IDs must have the following characteristics: - Unique for the run. - 1–40 characters. - No spaces. - Alphanumeric characters with underscores and dashes. If you use an underscore or dash, enter an alphanumeric character before and after the underscore or dash. eg, Sample1-T5B1_022515. - Cannot be called all, default, none, unknown, undetermined, stats, or reports. - Must match a Sample_ID listed in the BCLConvert data section. - Illumina recommends that the sample ID be based on the pair ID. Example: <Pair_ID>-DNA,<Pair_ID>-RNA.

    Sample_Type

    Required

    Enter DNA or RNA. For HRD samples, this parameter must be DNA.

    Pair_ID

    Required

    A unique ID that links DNA and RNA from the same biological sample from the same individual. Pair ID shares, at most, one DNA and one RNA sample per run. eg, if a Sample_ID is TestSample1-DNA for DNA and TestSample1-RNA for RNA, the Pair_ID TestSample1 will link these samples that are on different rows in the sample sheet together. If the pair ID is associated with more than one DNA or RNA sample, the analysis fails.

    Sample_Feature

    Required when using HRD add-on kit

    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.

    To auto-launch analysis from the sequencer run folder, ensure the StartsFromFastq and SampleSheetRequested fields are set to FALSE. To auto-launch analysis from FASTQs after BCL Convert auto-launch, StartsFromFastq and SampleSheet Requested fields must be set to TRUE

    [Cloud_TSO500S_Data] Section

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

    [Cloud_TSO500S_Settings] Section

    Parameters
    Required
    Details

    SoftwareVersion

    Not Required

    The TSO500S software version.

    StartsFromFastq

    Required

    Set the value to TRUE or FALSE. To auto-launch from BCL files, set to FALSE. To auto-launch from FASTQ files after auto-launch of BCL Convert, set to TRUE.

    SampleSheetRequested

    Required

    Set the value to TRUE or FALSE.

    To auto-launch from BCL files, set to FALSE. To auto-launch from FASTQ files after auto-launch of BCL Convert, set to TRUE.

    [Cloud_Data] Section

    Parameters
    Required
    Details

    Sample_ID

    Not Required

    The same sample ID used in the Cloud_TSO500S_Data section.

    ProjectName

    Not Required

    The BaseSpace project name.

    LibraryName

    Not Required

    Combination of sample ID and index values in the following format: sampleID_Index_Index2

    LibraryPrepKitName

    Required

    The Library Prep Kit used.

    [Cloud_Settings] Section

    Parameter
    Required
    Details

    GeneratedVersion

    Not Required

    The cloud GSS version used to create the sample sheet. Optional if manually updating a sample sheet.

    CloudWorkflow

    Not Required

    Ica_workflow_1

    Cloud_TSO500_Pipeline

    Required

    This value is a universal record number (URN) . The valid values are:

    v2.6.0.8 (F2 compatible, includes HRD) urn:ilmn:ica:pipeline:142fb3af-f0aa-41f2-b043-f2913671e0b4#DRAGEN_TruSight_Oncology_500_v2_6_0_8 v2.6.2 urn:ilmn:ica:pipeline:b4dec62d-f3af-4dc3-8d15-6fe6c9a4df6c#DRAGEN_TruSight_Oncology_500_v2_6_2_4

    BCLConvert_Pipeline

    Required

    urn:ilmn:ica:pipeline:a0778b16-f318-40df-ae04-95998e3a7564#BCL_Convert_v3_10_9_for_TSO500

    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

    Parameter Name
    Required

    SoftwareVersion

    Required

    Enter the IRM iapp software version 2.6.0-2v12ui

    [TSO500S_Data] Section

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

    DRAGEN Software if a compatible version is not present
  • Docker software if a compatible version is not present

  • A script required to generate DRAGEN genome hash table

  • A script to check that DRAGEN TruSight Oncology 500 ctDNA Analysis Software is installed properly

  • Installation Requirements

    Hardware

    • DRAGEN server v3 or v4

    Software

    • Linux CentOS 7.9 operating system (or later) or Oracle Linux 8 (or later), one of which is provided on the server. Oracle Linux 8 is recommended.

    • Docker Software, see table below for minimum version needed. If sufficient Docker software is not present on the server, the TSO 500 installer will install compatible Docker software.

    • DRAGEN Server Software*, see table below for minimum version needed as the host version on the server. If sufficient DRAGEN software is not present on the server, the TSO 500 installer will install compatible DRAGEN software.

    Software Dependency
    Compatible
    Installs

    Docker

    20.10 or greater

    Docker 20.10.15

    DRAGEN Server Software*

    v3.10.x, where x >=19, v4.3+ for TSO500 ctDNA v2.6.2;

    v3.11.x, where x >=2, v4.3+ for TSO500 ctDNA v2.6.3

    DRAGEN Software 3.10.19 for TSO500 ctDNA v2.6.2;

    DRAGEN Software 3.11.2 for TSO500 ctDNA v2.6.3

    *The DRAGEN Server Software version may be higher than the DRAGEN version used by the DRAGEN TSO 500 ctDNA v2.6.2 pipeline (DRAGEN v3.10.18), which is provided inside the DRAGEN TSO 500 ctDNA docker image.

    Licenses

    • TSO500Combined license

    TSO500Combined license has been pre-installed to DRAGEN servers in manufacturing since August 2022. To generate a list of installed DRAGEN server licenses, run the following command: /usr/bin/dragen_lic. If a license is not installed, contact Illumina Customer Care at [email protected] for the license.

    Permissions

    Illumina recommends logging in as root user for installation, but as a non-root user for running TSO 500 ctDNA 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 ctDNA Analysis Software and running the system check requires root privileges.

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

    Compatibility with other DRAGEN pipelines

    DRAGEN TSO 500 Analysis Software ctDNA v2.6.2 and v2.6.3 (v2.6.2+) are multi-version compatible. Multi-version compatibility refers to ability to be installed on a single DRAGEN server with software running a different version of DRAGEN software. For example, multi-version compatible pipelines running DRAGEN v4.3.6+ can be co-installed on a server alongside DRAGEN TSO 500 ctDNA pipelines with DRAGEN server software v3.10.19 and above. For more details on DRAGEN multi-version compatibility, please visit page 7 of the DRAGEN v4.3.6 software release notes.

    Software versions without multi-version compatibility referred to as single-version compatible. DRAGEN TSO 500 ctDNA Analysis Software v2.6.2+ will disrupt installations of single-version compatible software from the DRAGEN server. To uninstall a previous version of DRAGEN TSO 500 ctDNA Analysis Software, refer to the respective guide.

    Compatibility of software for co-installation with DRAGEN TSO 500 ctDNA on a DRAGEN server is summarized in the table below:

    Software
    Version
    Type
    Compatible

    DRAGEN TSO 500 ctDNA

    2.6.2+

    Multi-version

    Yes

    DRAGEN TSO 500 ctDNA

    2.6.1 or below

    Single-version

    No

    DRAGEN TSO 500

    2.6.1+

    Multi-version

    *DRAGEN TSO 500 Analysis Software ctDNA v2.6.2+ can run on a single server with DRAGEN TSO 500 v2.5.4, and should be installed after v2.5.4. DRAGEN TSO 500 Analysis Software ctDNA v2.6.2+ can be co-installed with multi-version compatible DRAGEN TSO 500 Analysis Software or other DRAGEN pipelines with any order of installation.

    **For example, DRAGEN Enrichment, DRAGEN Germline, and others. Order of installation does not matter.

    Installation Instructions

    Pre- and Post- Installation Steps

    1. Uninstall all existing single-version compatible software on the server (see table above)

    2. Install DRAGEN TSO 500 ctDNA Analysis Software v2.6.2+

      • This step will disrupt previously installed single-version compatible software but will not impact multi-version compatible ones (see table above)

    3. Install other multi-version DRAGEN software/pipelines if needed

      • Multi-version software can be installed in any order

    Steps to Install DRAGEN TSO 500 ctDNA Analysis Software v2.6.2+

    As a root user, perform the following steps to install DRAGEN TSO 500 ctDNA Analysis Software v2.6.2 and v2.6.3 (v2.6.2 for an example):

    1. Contact Illumina Customer Care at [email protected] to obtain the DRAGEN TSO 500 ctDNA Analysis Software installer package.

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

    It is recommended to use a command line tool like wget or curl to download the file rather than pasting the link into the web browser bar. For example:

    curl -o {filename} "{link}"

    wget -O {filename} "{link}"

    Where the file name is the installation script file name, and the link is provided by Illumina Customer Care.

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

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

    Installation Script: install_DRAGEN_TSO500_CTDNA-2.6.2.run

    SHA256 value: 1324c86183526e12afb267f553a569cf78b01fd7a4ee85f8e07cc2f6a33d8f41

    Installation Script: install_DRAGEN_TSO500_CTDNA-2.6.3.run

    SHA256 value: 77a4f3b44af22c8c83e0bfe43d3b186d2b74dc58b8bbdb6f324ba3ce6220ab9e

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

    2. Use the following command to run the installation script (run time ~ 20 minutes):

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

        1. If new DRAGEN version is not installed from the above command, use sudo TMPDIR=/staging /staging/install_DRAGEN_TSO500_CTDNA-2.6.2.run -- --forceDragenInstall to force a reinstall of DRAGEN.

      2. For Apptainer, use the following command: sudo TMPDIR=/staging /staging/install_DRAGEN_TSO500_CTDNA-2.6.2.run -- --noDockerInstall This will not install Apptainer, but will install the analysis software in the Singularity Image File (SIF) format and modify the software to launch analyses using Apptainer.

    3. During the installation process, you may 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 log back in.

    5. Install your DRAGEN server licenses if needed (use /opt/dragen/3.11.2/bin/dragen_lic for v2.6.3):

      1. To run DRAGEN TSO 500 ctDNA Analysis Software v2.6.2 , 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/dragen/3.10.19/bin/dragen_lic command.

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

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

      If license installation is successful, the list should include TSOCombined.

      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_CTDNA-2.6.2.sh

    The script checks that:

    • All required services are running

    • Proper Docker image is installed

    • DRAGEN TSO 500 ctDNA 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_CTDNA_<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 TSO 500 ctDNA Analysis Software installation includes an uninstall script called uninstall_DRAGEN_TSO500_CTDNA-2.6.2.sh, which is located in /usr/local/bin.

    Executing the uninstall script removes the following assets:

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

    • Resources found in /staging/illumina/DRAGEN_TSO500_CTDNA-2.6.2

    • The dragen_tso500_ctdna Docker image

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

    uninstall_DRAGEN_TSO500_CTDNA-2.6.2.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.

    Splice variant score < passing quality score threshold value of 1.

    PASS

    Splice variant score ≥ passing quality score threshold value of 1.

    LowUniqueAlignments

    All splice junction supporting reads map to a unique genomic interval near at least one of the two splice sites.

    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

    Filter
    Filter Type
    Description

    DOUBLE_BROKEN_EXON

    Confidence filter

    If both breakpoints are distant from annotated exon boundaries, the number of supporting reads do not satisfy a high threshold requirement (≥ 10 supporting reads).

    LOW_MAPQ

    Confidence filter

    All fusion supporting read alignments at either of the breakpoints have MAPQ < 20.

    LOW_UNIQUE_ALIGNMENTS

    Confidence filter

    All fusion supporting read alignments map to a unique genomic interval at either of the breakpoints.

    LOW_SCORE

    Confidence filter

    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

    Fusion Object Field
    Source

    Gene A

    The gene associated with the A side of the fusion. A semicolon delimited list is used for multiple genes.

    Gene B

    The gene associated with the B side of the fusion. A semicolon delimited list is used for multiple genes.

    Gene A Breakpoint

    [Information only] The chromosome and offset of the Gene A side of the fusion.

    Gene A Location

    Location of the breakpoint within Gene A: - IntactExon—Matches exon boundary - BrokenExon—Inside an exon - Intronic—Within an intron - Intergenic—No gene overlap (currently excluded) If multiple genes are in Gene A, then semicolon separated list of locations. This column is used internally to identify genes to report when a breakpoint occurs in a region overlapping multiple genes. Occasionally, additional values are listed for genes that were excluded from the GeneA list.

    Gene A Sense

    Boolean indicating whether left/right breakpoint order suggests fusion transcript is in the same sense of Gene A. If multiple genes are in Gene A, then semicolon separated list of bools.

    Gene A Strand

    Strand of Gene A, + for forward, - for reverse.

    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

    RNA Analysis Methods

    LowQ

    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

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

    Metric
    Description
    Recommended Guideline Quality Threshold
    Variant Class

    PCT_PF_READS (%)

    Total percentage of reads passing filter.

    ≥80.0

    All

    PCT_Q30_R1 (%)

    Percentage of Read 1 reads with quality score ≥ 30.

    ≥80.0

    All

    PCT_Q30_R2 (%)

    Percentage of Read 2 reads with quality score ≥ 30.

    NovaSeq 6000 or NovaSeq 6000Dx (RUO)

    Metric
    Description
    Recommended Guideline Quality Threshold
    Variant Class

    PCT_PF_READS (%)

    Total percentage of reads passing filter.

    ≥55.0

    All

    PCT_Q30_R1 (%)

    Percentage of Read 1 reads with quality score ≥ 30.

    ≥80.0

    All

    PCT_Q30_R2 (%)

    Percentage of Read 2 reads with quality score ≥ 30.

    NextSeq 1000/2000

    Metric
    Description
    Recommended Guideline Quality Threshold
    Variant Class

    PCT_Q30_R1 (%)

    Percentage of Read 1 reads with quality score ≥ 30.

    ≥85.0

    All

    PCT_Q30_R2 (%)

    Percentage of Read 2 reads with quality score ≥ 30.

    ≥85.0

    All

    NovaSeq X

    Metric
    Description
    Recommended Guideline Quality Threshold
    Variant Class

    PCT_Q30_R1 (%)

    Percentage of Read 1 reads with quality score ≥ 30.

    ≥85.0

    All

    PCT_Q30_R2 (%)

    Percentage of Read 2 reads with quality score ≥ 30.

    ≥85.0

    All

    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.

    Metric
    Description
    Recommended Guideline Quality Threshold
    Variant Class

    CONTAMINATION_SCORE

    The contamination score is based on VAF distribution of SNPs.

    ≤ 1457

    All

    MEDIAN_EXON_COVERAGE

    Median exon fragment coverage across all exon bases.

    ≥ 150

    Small variant TMB

    PCT_CHIMERIC_READS

    Proportion of total number of non-supplementary, non-secondary, and passing QC reads after alignment to the whole genome sequence.

    RNA Sample QC

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

    Metric
    Description
    Recommended Guideline Quality Threshold
    Variant Classes

    MEDIAN_CV_GENE_500X

    The median CV for all genes with median coverage > 500x. Genes with median coverage > 500x are likely to be highly expressed. Higher CV median > 500x indicates an issue with library preparation (poor sample input and/or probes pulldown issue).

    ≤ 0.93

    Fusion, Splice

    MEDIAN_INSERT_SIZE

    The median fragment length in the sample.

    ≥ 80

    Fusion, Splice

    TOTAL_ON_TARGET_READS*

    The total number of reads that map to the target regions.

    *TOTAL_ON_TARGET_READS is the only QC metric with guidelines specific to chemistry (v1 vs. v2 assay); all other guidelines are applicable to both

    ** To avoid failing RNA samples unnecessarily, Illumina does not recommend a universal threshold for GENE_MEDIAN_COVERAGE 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.

    F2 Support on ICA

    Mandatory Upgrade for TSO on ICA

    that their F1 instances, which are used by TSO 500 pipelines on ICA, will be replaced by a new generation of FPGA-powered cloud hardware, Amazon EC2 F2 instances. Furthermore, F1 instances will cease availability on December 20, 2025, their end-of-life date. To ensure uninterrupted service, Illumina is releasing new versions of current DRAGEN TSO 500 and DRAGEN TSO 500 ctDNA pipelines on ICA compatible with F2 instances.

    F2-compatibility provides significant performance improvements: 40% lower turnaround time for TSO 500 analyses, on average. Furthermore, this suite of versions has been validated to produce bit-exact results.

    To aide your transition to F2-compatible pipelines, this document contains:

    MergedSmallVariants.vcf
  • microstat_output.json

  • TMB_Trace.tsv

  • ... (NovaSeq6000, NextSeq)

    TruSight Oncology 500 v2 ...

    • ... (NovaSeq6000Dx, NextSeq1000/2000, NovaSeqX Series)

      Illumina DNA/RNA UD Indexes V3 Sets A-D (1-384)

    • ... (NextSeq 500/ 550, NovaSeq 6000)

      Illumina DNA/RNA UD Indexes V3 Sets A-D (1-384)

  • Cannot be called all, default, none, unknown, undetermined, stats, or reports.

  • Each sample must have a unique combination of Lane (if applicable), sample ID, and index ID or the analysis will fail.

  • Enter trim This indicates that the BCL Convert software trims the specified adapter sequences from each read.

    MinimumTrimmedReadLength

    Required

    Enter 35. Reads with a length trimmed below this point are masked.

    MaskShortReads

    Required

    Enter 35. Reads with a length trimmed below this point are masked.

    Indicates which lane corresponds to a given sample. Enter a single numeric value per row. Cannot be empty, i.e the analysis fails if the Lane column is present without a value in each row.

    Required for HRD enriched samples. For DNA samples that have undergone HRD enrichment, enter HRD in this column of the sample sheet. If the sample has not undergone HRD enrichment, leave the field empty.

    Sample_Description

    Not Required

    Sample description must meet the following requirements: - 1–50 characters. - Alphanumeric characters with underscores, dashes and spaces. If you enter a underscore, dash, or space, enter an alphanumeric character before and after. eg, Solid-FFPE_213.

    IndexAdapterKitName

    Not Required

    The Index Adapter Kit used.

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

  • To install the license, enter: /opt/dragen/3.10.19/bin/dragen_lic -i auto

  • For servers not connected to the internet, contact Illumina Customer Care at [email protected] for license information.

  • Yes

    DRAGEN TSO 500

    2.6.0

    Single-version

    No

    DRAGEN TSO 500

    2.5.4

    Multi-version

    Yes*

    DRAGEN TSO 500

    2.5.3 or below

    Single-version

    No

    DRAGEN pipelines**

    4.3.6+

    Multi-version

    Yes

    DRAGEN pipelines**

    4.2 or below

    Single-version

    No

    The fusion candidate has probabilistic score as determined by the features of the candidate.

    MIN_SUPPORT

    Confidence filter

    The fusion candidate has very few fusion supporting reads (< 5 supporting read pairs).

    READ_THROUGH

    Confidence filter

    The breakpoints are cis neighbors (< 200 kbp) on the reference genome.

    ANCHOR_SUPPORT

    Information only

    Read alignments of fusion supporting reads are not long enough (12 bp) at either of the two breakpoints.

    HOMOLOGOUS

    Information only

    The candidate is likely a false candidate generated because the two genes involved have high gene homology.

    LOW_ALT_TO_REF

    Information only

    The number of fusion supporting reads is < 1% of the number of reads supporting the reference transcript at either of the two breakpoints.

    LOW_GENE_COVERAGE

    Information only

    Each breakpoint in an enriched gene has fewer than 125 bp with nonzero read coverage.

    NO_COMPLETE_SPLIT_READS

    Confidence filter

    For every fusion-supporting split read, the total number of aligned bases across two breakpoints is less 60% of the read length.

    UNENRICHED_GENE

    Confidence filter

    Neither of the two parent genes is in the enrichment panel.

    Gene B Breakpoint

    [Information only] The chromosome and offset of the Gene B side of the fusion.

    Gene B Location

    Location of the breakpoint within Gene B: - IntactExon—Matches exon boundary - BrokenExon—Inside an exon - Intronic—Within an intron - Intergenic—No gene overlap (currently excluded) If multiple genes in Gene B, then semicolon separated list of locations. This column is used internally to identify genes to report when a breakpoint occurs in a region overlapping multiple genes. Occasionally, additional values are listed for genes that were excluded from the GeneB list.

    Gene B Sense

    Boolean indicating whether left/right breakpoint order suggests fusion transcript is in the same sense of Gene B. If multiple genes are in Gene B, then semicolon separated list of bools.

    Gene B Strand

    Strand of Gene B, + for forward, - for reverse.

    Score

    The quality of fusion as determined by DRAGEN server.

    Filter

    The filter associated with the fusion as determined by the respective caller. Results from different callers are not equivalent.

    Ref A Dedup

    Gene A uniquely mapping reads paired across or split by the junction. Does not support fusion. Duplicate reads are not included.

    Ref B Dedup

    Gene B uniquely mapping reads paired across or split by the junction. Does not support fusion. Duplicate reads are not included.

    Alt Split Dedup

    Uniquely mapping reads split by the junction. Supports fusion. Duplicate reads are not included.

    Alt Pair Dedup

    Uniquely mapping reads paired across junction. Supports fusion. Duplicate reads are not included.

    KeepFusion

    The determination whether the fusion should be kept or dropped from the list of fusions.

    Fusion Directionality Known

    Whether fusion directionality is known and indicated by gene order.

    ≥80.0

    All

    ≥80.0

    All

    ≤ 8

    Small variant TMB

    PCT_EXON_50X

    Percent exon bases with 50x fragment coverage.

    ≥ 90.0

    Small variant TMB

    MEDIAN_INSERT_SIZE

    The median fragment length in the sample.

    ≥ 70

    Small variant TMB

    USABLE_MSI_SITES

    The number of MSI sites usable for MSI calling.

    ≥ 40

    MSI

    MEDIAN_BIN_COUNT_CNV_TARGET

    The median raw bin count per CNV target.

    ≥ 1.0

    CNV

    PCT_TARGET_HRD_50X (HRD samples)

    Percent of HRD probe SNP panel covered by at least 50X coverage

    ≥ 50

    GIS

    EXCESSIVE_TF (HRD samples)

    EXCESSIVE TF indicates if there is excessive tumor content in sample. Troubleshooting: Samples with pure tumor fraction >90% are outside the design for GIS estimation (this includes pure tumor cell lines)

    = 0 (= 1 indicates Excessive TF)

    GIS

    ≥ 9000000 (v1)

    ≥ 2,500,000 (v2)

    Fusion, Splice

    GENE_MEDIAN_COVERAGE**

    The median deduped coverage across all genes in the RNA panel (55 genes).

    N/A

    Fusion, Splice

  • Recommended transition paths for all current pipeline versions

  • Instructions for accessing new pipelines, no matter how you launch analyses

  • Detailed comparisons between pipeline versions on each transition path

  • Bit exact results comparisons

    Bit-exact means that the new F2-compatible versions will have no analytical changes to the bioinformatics pipeline and results are identical to the current F1-compatible versions.

    For each new pipeline version, the same data set was analyzed with both the F2-compatible and F1-compatible pipeline versions. For each output file in Logs_Intermediates/ and Results/ folders, F1 and F2 outputs were compared using an automated script. All differences were logged and manually reviewed.

    Across all pipeline versions, the only changes observed were those that were expected: related to versioning and naming (pipeline name, analysis ID, time stamp, etc.) and the mapping rate, a metric found in mapping_metrics.csv, an output of DNA and RNA Map/ Align. Mapping Rate is a measure of speed, in millions of reads per second. It varies based on the hardware used, can be different between cloud, local, different fpga cards, etc. Changes to mapping rate do not impact map/ align outputs, and therefore there is no impact to results.

    Turnaround time improvements

    F2 instances introduce significant capacity and performance improvements compared to the currently used F1 instances, with approximately 40% lower turnaround time for the same TSO 500 analysis on F2 instances versus F1.

    See a summary of turnaround time improvements in the table below. Run Time is the time analysis was ongoing, while Analysis Turnaround Time (TAT) is the end-to-end processing time: from submitting the analysis to results being available in ICA.

    Pipeline Version
    Run Time Improvement
    Analysis TAT Improvement

    DRAGEN TSO 500 v2.6.0.8

    1.84x (46%)

    1.69x (41%)

    DRAGEN TSO 500 v2.5.2.6

    2.46x (59%)

    1.86x (46%)

    DRAGEN TSO 500 ctDNA v2.6.1.8

    1.55x (35%)

    1.40x (29%)

    DRAGEN TSO 500 ctDNA v2.6.0.25

    1.90x (47%)

    Recommended transition paths

    Starting in May 2025, Illumina will be releasing F2-compatible versions (of some, but not all, current pipelines) in ICA.

    For pipelines without bit-exact F2 versions, we recommend following Transition Path A and upgrading to the highest available F2-compatible pipeline (v2.6.0.8 tissue and v2.6.1.8 ctDNA).

    For pipelines with bit-exact F2 versions, you may choose to transition to the bit-exact version (Transition Path B) or upgrade to the highest available version (Transition Path A).

    For those following Transition Path A and upgrading their pipeline to a newer version, we provide additional information about changes between pipeline versions here.

    DRAGEN TSO 500 Recommended Transitions

    Current Version
    Recommended Version
    Transition Path

    v2.1.2

    v2.6.0.8*

    A: pipeline upgrade

    v2.1.2 HRD

    v2.6.0.8*

    A: pipeline upgrade

    v2.5.2

    v2.5.2.6*

    B: bit-exact

    v2.5.2 HRD

    v2.5.2.6*

    *will include HRD

    A note for those using the HRD add-on assay kit:

    With previous pipelines versions on ICA, Illumina released two configurations: DRAGEN TSO 500 HRD, which supported all TSO analysis steps including those enabled by the HRD add-on assay (GIS, LOH#, Absolute Copy Number#) and DRAGEN TSO 500, which did not include those outputs specific to the HRD add-on assay.

    For F2-compatible pipeline versions, Illumina will only release one configuration, DRAGEN TSO 500, which will support both options: TSO 500 with and without the HRD add-on assay kit.

    #LOH and Absolute Copy Number are beta features, available starting in DRAGEN TSO 500 v2.5.2.

    DRAGEN TSO 500 ctDNA Recommended Transitions

    Current Version
    Recommended Version
    Transition Path

    v2.1.1

    v2.6.1.8

    A: pipeline upgrade

    v2.5.0

    v2.6.1.8

    A: pipeline upgrade

    v2.6.0

    v2.6.0.25

    B: bit-exact

    v2.6.1

    v2.6.1.8

    How to access new pipeline versions…

    Access to new ICA pipelines depends on whether you launch analysis manually (via the ICA command line or user interface); or use auto-launch to automatically kick off analyses after sequencing.

    …when manually launching in ICA

    To kick off analysis with a new pipeline version, you need that pipeline to be accessible within your ICA project. In other words, the bundle containing that pipeline must be linked to your project.

    If the new pipeline version is bit-exact to the current version, i.e. Transition Path B, there is nothing for you to do. The new version will be added to the same bundle as your current pipeline and automatically linked to your project. Simply select the new version from the list of pipelines available in your project when you want to use it for a new analysis.

    If the new pipeline version is an upgrade from your current version, i.e. Transition Path A, you must link the bundle for that pipeline to your ICA project. The bundles are found in Entitled Bundles and named with the corresponding 3-digit pipeline version (e.g. DRAGEN TSO 500 v2.6.0). See the TSO 500 User Guide for instructions on getting started in ICA.

    …when Auto-launching via BaseSpace Sequence Hub

    To auto-launch a new pipeline version, you need to make sure your sample sheet has the correct URN. Updated URNs will be listed on this page when the F2-compatible pipelines are available. See the User Guide for instructions on Auto-launching TSO 500 pipelines.

    Note: If you are auto-launching TSO 500 from FASTQ (by first auto-launching BCL Convert 3.10.9), you can continue to use the same BCL Convert 3.10.9 pipeline as before: it does not run on F1 nodes and will therefore continue to work as before.

    Guidance for Upgrading TSO 500 Pipelines (Transition Path A)

    The following sections contain information to guide users that are transitioning from one pipeline version to a higher one (e.g. 2.1 to 2.6). Analytical output changes are detailed along with differences in sample sheet and input requirements.

    Bioinformatics changes

    Refer to the tables below for a summary of analytical changes (algorithm updates, new variant types, accuracy improvements, etc.) between v2.1 and v2.6.

    DRAGEN TSO 500 Analytical Changes

    For a detailed understanding of analysis methodology and output files, please refer to the relevant section of the DRAGEN TSO 500 v2.6 user guide.

    Analysis Step
    v2.1.2 to v2.5.2
    v2.5.2 to v2.6.0

    Demultiplex

    No change

    No change

    DNA Map/ Align

    No change

    No change

    Small Variants

    • Manifest expanded 8bp into introns

    • MNVs and component SNVs/ indels all reported in VCF

    • Accuracy improvements

    No change

    Tumor Mutational Burden

    Updates from small variant caller

    *only for HRD samples

    DRAGEN TSO 500 ctDNA Analytical Changes

    For a detailed understanding of analysis methodology and output files, please refer to the relevant section of the DRAGEN TSO 500 ctDNA v2.6 user guide.

    Analysis Step
    v2.1.1 to v2.5.0
    v2.5.0 to v2.6.0
    v2.6.0 to v2.6.1

    Demultiplex

    No change

    No change

    No change

    Map/ Align

    No change

    No change

    No change

    Small Variants

    • MNVs and component SNVs/ indels all reported in VCF

    • Accuracy improvements

    Input changes

    DRAGEN TSO 500 Input Changes

    Refer to the table below for a summary of changes to input requirements between 2.1.2 and 2.6.0. To ensure your sample sheet will pass validation in the 2.6 pipeline, please refer to the sample sheet requirements detailed in the DRAGEN TSO 500 v2.6 user guide.

    DRAGEN TSO 500 Inputs
    v2.1.2
    v2.5.2
    v2.6.0

    Sample sheet section: [Sequencing_Settings]

    LibraryPrepKits field is now required.

    Valid values are: TSO500, TSO500HT

    Sample sheet section: [TSO500S_Data]

    Index ID is now optional

    FASTQ folder structure

    Sub-folders per sample

    Sub-folders per sample or one folder with all FASTQs

    DRAGEN TSO 500 ctDNA Input Changes

    Refer to the table below for a summary of changes to input requirements between 2.1.1 and 2.6.0. To ensure your sample sheet will pass validation in the 2.6 pipeline, please refer to the sample sheet requirements detailed in the DRAGEN TSO 500 ctDNA v2.6 user guide.

    Inputs
    v2.1.1
    v2.5.0
    v2.6.0
    v2.6.1

    Sample sheet section: [TSO500L_Data]

    Index ID is now optional

    FASTQ folder structure

    Sub-folders per sample

    Sub-folders per sample or one folder with all FASTQs

    No change

    No change

    References

    For additional details on changes between versions, please refer to the customer release notes for not only the last version, but also each version in between.

    Transition
    Relevant Customer Release Notes

    DRAGEN TSO 500 v2.1.2 to

    DRAGEN TSO 500 v2.5.2

    DRAGEN TSO 500 v2.5.2 to

    DRAGEN TSO 500 v2.6.0

    DRAGEN TSO 500 ctDNA v2.1.1 to

    DRAGEN TSO 500 ctDNA v2.5.0

    DRAGEN TSO 500 ctDNA v2.5.0 to

    DRAGEN TSO 500 ctDNA v2.6.0

    DRAGEN TSO 500 ctDNA v2.6.0 to

    DRAGEN TSO 500 ctDNA v2.6.1

    Amazon recently announced

    1.74x (42%)

    TSO 500 Overall

    1.80x (44% reduction)

    1.65x (39% reduction)

    B: bit-exact

    v2.6.0

    v2.6.0.8*

    B: bit-exact

    v2.6.0 HRD

    v2.6.0.8*

    B: bit-exact

    B: bit-exact

    MNVs removed from TMB calculation

    Microsatellite Instability

    No change

    No change

    Copy Number Variants

    • Report predicted sex

    • Expand CNVs from 55 genes to 514

    • Report deletions in addition to amplifications

    No change

    BRCA Large Rearrangements

    • Breakpoint coordinates shifted (now 0-based instead of 1-based)

    • Algorithm update for events with small fold change

    Genomic Instability Score*

    Accuracy improvements

    No change

    Loss of Heterozygosity*

    New biomarker (beta feature)

    No change

    Absolute Copy Number*

    New biomarker (beta feature)

    No change

    RNA Map/ Align

    No change

    Differences due to update in DRAGEN versions

    RNA Fusions

    No change

    Accuracy improvements

    Splice Variants

    No change

    Differences due to RNA map align updates

    QC Metrics

    Added: PER_GENE_MEDIAN_COVERAGE (RNA)

    Added:

    • gene- and exon-level coverage

    • PCT_Q30

    • PCT_SOFT_CLIPPED_BASES

    Removed: PCT_PF_UQ_READS (%)

    DRAGEN SW

    v3.10.9 to v3.10.16

    v3.10.16 to v3.10.17

    No change

    No change

    Tumor Mutational Burden

    No change

    No change

    No change

    Microsatellite Instability

    No change

    No change

    No change

    Copy Number Variants

    Report predicted sex

    No change

    No change

    DNA Fusions

    SV evidence BAM added to Logs_Intermediates/

    No change

    Improved SV detection in samples with high chimeric reads

    QC Metrics

    No change

    • gene- and exon-level coverage

    • PCT_Q30

    • PCT_SOFT_CLIPPED_BASES

    No change

    DRAGEN SW

    v3.10.9 to v3.10.15

    v3.10.15 to v3.10.17

    v3.10.17 to v3.10.18

    No change

    DRAGEN TSO 500 v2.5.2
    DRAGEN TSO 500 v2.6.0
    DRAGEN TSO 500 ctDNA v2.5.0
    DRAGEN TSO 500 ctDNA v2.6.0
    DRAGEN TSO 500 ctDNA v2.6.1