The following versions of DRAGEN Array have been released:

• DRAGEN Array v1.1.0 Release Notes

• DRAGEN Array v1.0.0 Release Notes

  • DRAGEN Array Genotyping Cloud v1.0.0 Release Notes

  • DRAGEN Array Methylation QC Cloud v1.0.0 Release Notes

DRAGEN Array Cloud Analysis Overview

DRAGEN Array Cloud utilizes the user-friendly graphical interface of BaseSpace Sequence Hub to simplify DRAGEN Array analysis setup and kickoff. Optional integration with the iScan System allows data to be streamed directly from the instrument to the cloud platform. Analysis data is stored on the Illumina Connected Platform providing secure storage for both microarray and sequencing data.

Getting Started

The following prerequisites are needed to get started with DRAGEN Array Cloud:

• Illumina Connected Analytics subscription: An ICA Basic, Professional or Enterprise subscription can be used which include access to BaseSpace Sequence Hub. Follow the Illumina Software Registration Guide to register the software.

• Workgroup setup: Workgroups must be created before login. Using a workgroup allows all members of the workgroup to share access to resources, analyses, and data. Learn more about managing a Workgroup.

  • Designating a workgroup as ‘Collaborative’ allows projects to be shared with collaborators or Illumina Tech Support to assist with troubleshooting. To create a collaborative workgroup, select the Enable collaborators outside of this domain checkbox during workgroup creation.

• Software consumables: iCredits can be purchased for storage on the cloud platform and analysis pipelines with a compute charge. Per sample analysis can be purchased for relevant pipelines as listed in section Applications. Follow the Illumina Software Registration Guide (found under Example 3: Configuring the Software Consumables) to register the software consumables.

• [Optional] iScan integration: The iScan System is integrated with Illumina Connected Platform and can send IDATs for further analysis. The iScan System must be running iScan Control Software version 4.2.1 or later.

  • Instructions to Use Illumina Connect Analytics (ICA) with the iScan System

  • Troubleshooting iScan integration

• EULA acceptance: Accept all necessary End User License Agreements in BaseSpace Sequence Hub before scanning begins.

• Internet connection: For uploading product files or IDATs, a network connection 1 GbE or faster is recommended.

Note: Accessioning BeadChips before scanning and starting analysis is no longer a required step and has been automated within the system.

Running Analysis

Before beginning analysis, ensure workgroup context is being used so analysis can be viewed by all members of your workgroup. The name of your workgroup should appear in the top right corner.

Use the following steps to run the Microarray Analysis Setup on BaseSpace Sequence Hub:

1. Select the Runs tab

2. Select New Run

3. Select Microarray Analysis Setup

4. Enter the Analysis Name (Figure 1)
5. Use the Select Project link to choose the project for your output files To select an existing project, click the radio button next to the desired project name. You can also create a project by clicking the New button in the project selection window.

6. Select the Type of Analysis Further detail of each Type of Analysis is available in section Applications. Note: For PGx CNV calling, it is recommended that 96 or more samples passing LogRDev <= 0.2 are included in the analysis. For PGx star allele calling, it is recommended to QC the samples and review the samples that have Log R Dev > 0.2, call rate < 0.99, or TGA Control probe < 1.0 to assess the reliability of the analysis. These metrics are provided in the genotyping sample summary file (gt_sample_summary.csv).

7. (Optional) Create a custom configuration via the "Add Custom Configuration" option in Configuration Settings. Custom configurations must be assigned a name and product files can be uploaded or selected (Figure 2). Custom configuration options vary by Type of Analysis including:

• DRAGEN Array - Genotyping provides flexibility for turning off/on specific output files and adjusting GenCall score cutoff. Its recommended to turn off VCF output for non-human species and Final Report output for large sample numbers.

• DRAGEN Array - Methylation - QC provides options to adjust thresholds as detailed in section DRAGEN Array Methylation QC Threshold Adjustment.

1. Select your preferred option in the Configuration Settings drop-down menu Configuration setup will vary based on the Type of Analysis selected. More details are available in section Applications.

2. Select Next

3. Select either Import Sample Sheet, Select BeadChips, or Import IDAT Files (Figure 3)

• Import Sample Sheet presents a link to upload sample sheet. Users may download a template sample sheet by selecting the Download Template link.

• Select BeadChips allows users to select BeadChips from the displayed list of available BeadChips. If selecting specific samples within the BeadChip is desired the Import Sample Sheet option should be used.

• Import IDAT Files allows users to upload the IDAT files from a local folder to the cloud platform for use with the current and future analyses by users within the same workgroup.

1. Select Launch Analysis

View Outputs

1. On the Analyses tab, view the analysis status, e.g., initializing or complete.

2. After the analysis is complete, select the analysis and select the Files tab.

3. From the Files tab, select the Output folder.

Manage Data

The data management tab allows you to view and manage all your scanned IDAT files in the cloud. Before viewing, ensure workgroup context is being used so all data available your workgroup can be seen. The name of your workgroup should appear in the top right corner. For more information, see BaseSpace Data Management

DRAGEN Array Methylation QC

Threshold Adjustment

When using DRAGEN Array – Methylation – QC cloud analysis type, additional customization options will appear after product files are selected within Configuration Settings. Adjustments to these thresholds will be saved as part of the Configuration Setting. Thresholds can be adjusted based on study objectives. Adjusting thresholds will impact the pass or fail status of samples in the output files.

Illumina recommends thresholds for MethylationEPIC v1 & v2 and Methylation Screening Array (MSA). Users may use these thresholds as a starting point when defining thresholds for their custom or semi-custom BeadChip or other Infinium Methylation arrays. Further tuning may be required based on BeadChip used, laboratory conditions, iScan settings, bisulfite conversion methods, FPPE sample type, etc. A dataset deemed acceptable to the user based on proportion probes passing can be used for these additional threshold adjustments.

To customize thresholds, use the toggle to allow additional thresholds to be displayed and adjust as desired by typing in a numeric value or using the arrows to adjust up or down. Further detail of these thresholds including calculation method can be found in the Methylation Sample QC Summary Files section.

The recommended thresholds are pre-set within the software for MethylationEPIC and Methylation Screening Array with the following values:

The first 21 rows in the tables correspond to the 21 control metrics used in the methylation sample QC. See section Methylation Sample QC Summary Files for details.

DRAGEN Array Methylation QC and GenomeStudio Methylation Module Differences

DRAGEN Array Methylation QC software provides automated methylation sample QC using assay control probes on the Infinium Methylation Arrays. Unlike the manual visual QC in GenomeStudio, DRAGEN Array ultilizes 21 numerical metrics defined based on the control probes and uses standard thresholds to determine pass/fail status of a sample. Unlike GenomeStuio, probe detection rate (proportion of probes passing at a given p-value threshold) is not utilized to determine sample pass/fail status in DRAGEN Array. For more information, see High-throughput Infinium methylation array QC using DRAGEN Array Methylation QC software tech note.

DRAGEN Array Methylation QC performs background normalization, dye bias correction, and detection p-value calculation differently in comparison to the GenomeStudio Methylation module, leading to differences in probe detection p-values and detection rates. For the GenomeStudio Methylation Module, non-cancer samples at standard DNA input typically have detection rate > 96%. The detection rates from DRAGEN Array Methylation QC are typically lower compared to GenomeStudio, because the detection p-value from DRAGEN Array is more stringent than that from the GenomeStudio Methylation Module. The table below shows example detection rates from the DRAGEN Array Methylation QC software from MSA (Methylation Screening Array) datasets.

Note that only samples passing QC are included and all samples are at or above 50ng DNA input. Detection p-value threshold 0.05.

Troubleshooting and Additional Support

Troubleshooting iScan integration

The firewall protects the iScan control computer by filtering incoming traffic to remove potential threats. The firewall is enabled by default to block all inbound connections. Keep the firewall enabled and allow outbound connections.

For the instrument to connect to BaseSpace Sequence Hub, you will need to add regional platform endpoints and instrument specific endpoints to the allow list on your firewall. Regional endpoints and further detail can be found in Security and Networking for Illumina instrument control computers.

The following table shows the applicable endpoints for the iScan.

Some notes on IDAT fail status: iScan will mark certain samples with a FAIL status if the registration quality is too poor for that particular section. Selected samples that are marked with FAIL status will be excluded from analysis and there would be no results for that sample, even though IDATs are generated. The registration quality can be found in the metrics.txt file.

Sharing a project

Project sharing allows a user to share files with users outside the workgroup for collaboration or with Illumina Tech Support for troubleshooting. To share a project on BaseSpace Sequence Hub, first set the Workgroup type as ‘Collaborative’ during Workgroup setup, and then use the following steps to obtain a link to your project. The project can then be accessed by anyone with the link. All files in the project are shared.

1. Navigate to the Projects tab

2. Click the button next to the desired project

3. Select the Share button above to list (Figure 3)

4. Select the Get Link Option to Activate a link for the project

5. Copy the link and send it to the desired recipient(s)

Additional Notes:

• The project owner maintains ownership and write access. If project owner deletes the data, the collaborators lose access to it.

• Either sending or receiving domain must be collaborative

  • https://help.basespace.illumina.com/microarray/getting-started -> Workgroup Setup

• Must be in the same AWS regional instance

  • https://help.basespace.illumina.com/manage-your-account/regions -> "Data cannot be transferred directly between instances, however you can download and share data separately."

• For Enterprise domains, use this same method (share-by-link, not share-by-transfer)

  • https://help.basespace.illumina.com/collaborate/share-with-collaborators/share-by-link

DRAGEN (Dynamic Read Analysis for GENomics) Array secondary analysis is a powerful bioinformatics software for Illumina Infinium array-based assays. DRAGEN Array uses cutting-edge data analysis tools to provide accurate, comprehensive, and highly efficient secondary analysis to maximize genomic insights and meet your research needs across multiple applications.

DRAGEN Array is offered as a local package with command-line interface (no specialized server or hardware required) and as a cloud-based package with an intuitive graphical user interface, as summerized in the table below.

This product documentation describes the installation and setup, analysis execution, and result outputs. For the latest updates and release details, see the DRAGEN Array Release Notes. See Introducing DRAGEN™ Array 1.0 for Infinium™ Array-Based Pharmacogenomics Analysis for additional details on DRAGEN Array genotyping, PGx CNV calling and PGx star allele annotation.

Technical Support

For support, questions, and feedback on DRAGEN Array, please contact Illumina Tech Support at techsupport@illumina.com.

Additional Resources

RELEASE DATE

September 2024

RELEASE HIGHLIGHTS

• New EX PGx beadchips enabled for PGx analysis

• Increased coverage of high priority PGx genes

• Custom optimized .egt files accepted in PGx analysis

• Up-to-date database reflecting latest versions of public PGx resources

• DPWG guidelines now available for metabolizer status calling on cloud analysis

NEW FEATURES IN DETAIL

• DRAGEN Array supports multiple PGx products

  • Two new EX PGx beadchips enabled through genotyping, PGx CNV calling, and star allele annotation

    • Infinium Global Screening Array with Enhanced PGx-48 v4.0 Kit

    • Infinium Global Clinical Research Array with Enhanced PGx-24 v1.0 Kit

  • In total 3 PGx products supported

    Product	Manifest Name	Genome Build	Product Files Link

• Increased coverage of high priority PGx genes

  • Star allele annotation now covers CYP2E1, CYP1A2, ABCG2, CYP2C8, HMGCR, UGT1A4, UGT2B15, F13A1, and HLA-B*15:02

  • CNV calling now covers SULT1A1

  • Extended bi-allelic PGx variants from source databases to multi-allelic variants based on the designs in the supported PGx products.

  • See and for the full coverage lists.

• Allows flexibility for GTCs generated with a custom cluster file (.egt) to be used with the commercial CN model file (.dat). This alleviates the burden to retrain the CN model file.

  • The cluster file is a required input for the genotype call command in DRAGEN Array. The CN (Copy Number) model file is a required input to the copy-number call command to enable accurate copy number calling for pharmacogenomics. Custom cluster files and CN model files may be required for optimal genotyping and PGx performance. See section Optimizing cluster files and copy number models for additional details.

• Database revision reflecting updates.

• Standardization of star allele JSON output file

  • Renamed databaseSources to phenotypeDatabaseSources and starAlleleDatabaseSources

  • Renamed Phenotype to PhenotypeDatabaseAnnotation

  • Combined missingVariants and allMissingVariants to missingVariantSites

  • JSONized supportingVariants and missingVariants at the gene and candidate solution allele levels

  • Removed redundant info in the Alleles fields

• Updated VCF tabix indexing, improving performance and disk usage for SNV VCF.

KNOWN ISSUES

• Some simple variants have REF and ALT delimited by _ instead of > in the star_alleles.csv and metabolizer status JSON files (e.g., "ryr1.38577931a_c" instead of "ryr1.38577931a>c")

• Some multi-nucleotide variant (MNV) designs reverse compliment the "Allele1/2 Top" fields in the Final Report

• Occasional star-allele solution score discorcordance between Linux and Windows OS with concordant solution ranking.

• Rare intermittent memory issues during star allele calling. Example error message: The model has been changed since the solution was last computed.. To workaround the issue, user should restart star allele calling or run it on a machine with more memory.

KNOWN LIMITATIONS

• Star allele calling does not support novel alleles but those defined in the PharmVar and PharmGKB databases.

• CYP2D6 non-*36 star alleles with exon 9 conversion, such as *83, are reported as *36 with *83 as an underlying allele.

• Genotyping only supports diploid organisms. Polyploid genotyping is currently not supported.

• DRAGEN Array were only validated and intended to be used for commercial PGx beadchips with specified manifests (see table above). PGx star allele annotation is not backwards compatable with v1.0 manifest version, e.g., GDA_PGx-8v1-0_20042614_E2 is supported in DRAGEN Array v1.0, GDA_PGx-8v1-0_20042614_G2 is supported in DRAGEN Array v1.1.

• Command line options unsquash-duplicates and filter-loci for gtc-to-vcf conversion should not be used when star allele calling is desired. In addition, VCFs must be gzipped and tabix indexed (the default for gtc-to-vcf) to be used in star allele calling.

RELEASE DATE

December 2023

RELEASE HIGHLIGHTS

• Improved star allele calling accuracy for Global Diversity Array with enhanced PGx (GDA-ePGx) BeadChips.

• Reports star allele calls with quality scores for greater transparency and confidence.

• Provides missing variant reporting to improve data quality.

NEW FEATURES IN DETAIL

• Star Allele Calling

  • Star allele calling for genes listed in

    • For in-silico datasets, call rate ≥99%, diplotyping accuracy ≥ 90%

    • Includes reporting of the hybrid star alleles and allelic specific copy number

  • Provides quality score that estimates confidence in the star allele call as an additional quality metric

  • Star allele call rate increased through more robust error tolerance and missing data tolerance

    • Supporting variants and missing variants are listed and can be further reviewed

    • Quality score indicates confidence in result considering the missing data

  • Reports alternative ranked PGx star allele solutions

    • Allows an alternative to be investigated which may be desirable for samples with low confidence calls

    • Provides quality score (negative log likelihood) for alternative solutions

• Function annotations for PGx genes listed in section

  • Metabolizer and function annotations are supported for two sets of guidelines from CPIC and DPWG respectively

  • Activity scores are provided for CYP2C9, CYP2D6, and DPYD

• CNV VCF

  • CNV coverage for genes listed in PGx CNVs Coverage

  • Compressed and indexed files for size reduction and faster reading

  • Updated VCF header description to indicate copy number of 5 may be reported by the software

  • Revised filter field delimiter to comply with VCF 4.3 specification which allows VCF parsing software to parse the file successfully

• Genotyping VCF

  • Compressed and indexed files for size reduction and faster reading

KNOWN ISSUES

• Corrupt or invalid GTC files will abort with an error instead of skipping. The corrupt or invalid GTC files will need to be removed before proceeding.

• In the gtc-to-vcf subcommand a mismatch between BPM and CSV manifests will not cause the command to abort with an error. The mismatch will need to be addressed before proceeding.

• For gtc-to-vcf, multi-allelic variants designed with multiple assays might not always collapse into one variant correctly and be reported as two separate variants instead. Some indel variants are missing from SNV VCF due to mapping issue between the designed indels and the reference genome.

• Manifest names greater than 80 characters will cause failure when converting IDATs to GTCs.

• Symbolic links for VCFs are not supported as the inputs to the “star-allele call” subcommand.

• The local Linux CLI and Cloud offering do not sort the star_alleles.csv and various fields in the metabolizer_status.json. The local Windows CLI does.

KNOWN LIMITATIONS

• PGx CNV calling and star allele calling and annotation were only validated and intended to be used with GDA_PGx_E2 product files.

• Using subcommands “unsquash-duplicates” and “filter loci” during gtc-to-vcf conversion should not be used when star allele calling is desired.

• Only CPIC guidelines are available for star allele annotation (metabolizer status calling) for the cloud offering. For local, CPIC and DPWG are available.

RELEASE DATE

March 2024

RELEASE HIGHLIGHTS

• Ability to genotype and produce related reports for human and non-human arrays in the cloud.

• Configureable interfaces in Basespace that allows for flexibility and easy kick off.

NEW FEATURES IN DETAIL

• SNV VCF File

• Final Report

• Locus Summary

KNOWN ISSUES

• Some multi-nucleotide variant (MNV) designs reverse compliment the "Allele1/2 Top" fields in the Final Report

KNOWN LIMITATIONS

• Genotyping only works on diploid organisms at this time. Polyploid genotyping is not currently supported.

1. Is DRAGEN Array analysis a local (on-premises) or cloud solution? DRAGEN Array analysis is available locally (on-premises) and cloud.

   DRAGEN Array Local Analysis utilizes a command-line interface for power users to have granular control and flexibility to support large scale microarray genomic studies. Deployed on Windows or Linux operating systems, the local package is CPU-based and does not require a specialized server or hardware.

   DRAGEN Array Cloud Analysis utilizes the user-friendly, graphical interface of BaseSpace Sequence Hub to simplify analysis setup and kickoff.

2. Which Infinium arrays is DRAGEN Array compatible with? Refer to the Product and Analysis Compatibility table in the Applications section.

3. How many samples are needed per analysis? Genotyping: As few as one sample can be used for genotyping. Multiple analysis batches can be kicked off and run in parallel.

   Pharmacogenomics: A minimum of 24 samples is required for PGx CNV calling with 22 passing QC. Passing QC is defined as Log R Dev < 0.2. 96 samples are recommended for the most accurate CNV results. Multiple analysis batches can be kicked off and run in parallel.

4. Which PGx CNVs and star alleles are available? Please refer to the DRAGEN Array release notes.

5. Where can I find demo data? Demo data is available in BaseSpace under the “Demo Data” section. All array data starts with “iScan:” and includes the name of the type of analysis. Supported types of analysis can be found in the Applications section.

RELEASE DATE

May 2024

RELEASE HIGHLIGHTS

• Adjustable thresholds to determine pass/fail status

• Data summary plots for a quick visual check of each analysis batch

• Determining detection p-value, beta-values, and m-values from each methylation sample

• Deployment on BaseSpace™ Sequence Hub user interface for easy analysis kickoff

NEW FEATURES IN DETAIL

• Adjustable thresholds for 21 built in controls, p-value detection, proportion probes passing, and offset correction within BaseSpace Sequence Hub to customize for user’s study needs

  • Thresholds are used to assign pass (1) or fail (0) status to each sample

    • Failed metrics can be highlighted for easy viewing

  • Pinpoint areas of failure including bisulfite conversion, staining, hybridization, etc. to identify assay steps in need of troubleshooting

  • Quantitative values for each control removing ambiguity with manual interpretation

• Data summary plots with information on passing p-value detection and principal component analysis of beta values

• Provides detection p-value, beta-values and m-values for each CG site per sample to use in downstream analysis

KNOWN ISSUES

KNOWN LIMITATIONS

• Standard thresholds may not be applicable for all discontinued, semi-custom or custom BeadChips and IDATs originating from NextSeq550

• Built-in controls may not be available on all discontinued, semi-custom or custom BeadChips

The following section describes the input files required by DRAGEN Array. Product files (anything other than the IDATs) can be found on the support site.

IDAT Files

For each sample a pair of raw intensity files (.idat) are generated from the iScan System or NextSeq550 (for select arrays). They provide intensities in the red and green channels for each probe on the Infinium array. More information on which arrays can be used with NextSeq550, can be found on the Illumina Knowledge page on NextSeq550.

An IDAT file is identified by the BeadChip Barcode (12-digit unique Sentrix ID, i.e. 123456789101), BeadChip Position (row and column of the sample, i.e. R01C01), and Grn (Green) or Red for the specific channel.

Manifest Files

The CSV and BPM manifest files can be found on the Illumina Support Site for all commercial Infinium BeadChips or on MyIllumina for custom and semi-custom designs. DRAGEN Array only supports manifest files from the Illumina Support site. For instructions on obtaining manifest files from MyIllumina, see Illumina Knowledge article, How to access custom array product files (manifest and product definition files) in MyIllumina.

The CSV manifest file (.csv) provides complementary data to the BPM manifest file in a human readable format. It is a required input to the genotype gtc-to-vcf command to enable VCF generation for insertion/deletion variants. gtc-to-vcf depends on the presence of accurate mapping information within the manifest, and may produce inaccurate results if the mapping information is incorrect. Mapping information follows the implicit dbSNP standard, where

• Positions are reported with 1-based indexing.

• Positions in the PAR are reported with mapping position to the X chromosome.

• For an insertion relative to the reference, the position of the base immediately 5' to the insertion (on the plus strand) is given.

• For a deletion relative to the reference, the position of the most 5' deleted based (on the plus strand) is given.

Cluster File

The cluster file (.egt) is a standard product file provided by Illumina for commercial genotyping products and it is a required input for the genotype call command in DRAGEN Array. Custom cluster files may be required for optimal genotyping performance. See section Optimizing cluster files and copy number models for additional details.

CN Model File

The CN (Copy Number) model file (.dat) is a required input to the copy-number call command to enable accurate copy number calling for pharmacogenomics. Illumina provides a standard CN model file for each PGx array product. See section Optimizing cluster files and copy number models for additional details.

Mask File

The mask file (.msk) is a required input to the copy-number train command to enable accurate copy number training for pharmacogenomics. It does not need to be provided as an explicit input to the command line interface but should reside in the same folder as the BPM manifest. It should have the same base name as the manifest for the product. Illumina provides a mask file for each PGx array product and these can be found on the product files support page.

PGx Database File

The PGx database file (.zip) contains the variant mapping information from Infinium PGx arrays to PGx variants. For each gene and each variant used in the star allele definitions of the gene, there is a mapping to the ID field in the SNV VCF file. Each line in the gene mapping file represents a single variant and contains the SNV VCF ID for that variant followed by the HGVS (Human Genome Variation Society) tag for the variant. The PGx database file is array specific and is one of the product files provided by Illumina for each PGx array product.

Genome FASTA Files

The genome FASTA file (.fa) is a text file with the reference genome sequences.The FASTA index file (.fai) contains metadata about chromosomal orchestration within the FASTA file for a particular species. DRAGEN Array PGx calling supports human genome build 37 and 38. The genome FASTA file and FASTA index file are both provided by Illumina for human species and should be stored together in the same input folder. For custom reference genomes, the contig identifiers in the provided genome FASTA file must match exactly the chromosome identifiers specified in the provided manifest. For a standard human product manifest, this means that the contig headers should read ">1" rather than ">chr1".

IDAT Sample Sheet

For local analysis, the IDAT sample sheet can be a CSV or JSON formatted file with direct paths to sample IDAT files. It enables easy analysis of samples from different directories.

Example CSV format:

Green IDAT Path,Red IDAT Path

/path/to/sample1_Grn.idat,/path/to/sample1_Red.idat

/path/to/sample2_Grn.idat,/path/to/sample2_Red.idat

/path/to/sample3_Grn.idat,/path/to/sample3_Red.idat

Example JSON format:

[

{

"Green IDAT Path": "/path/to/sample1_Grn.idat",

"Red IDAT Path": "/path/to/sample1_Red.idat"

},

{

"Green IDAT Path": "/path/to/sample2_Grn.idat",

"Red IDAT Path": "/path/to/sample2_Red.idat"

},

{

"Green IDAT Path": "/path/to/sample3_Grn.idat",

"Red IDAT Path": "/path/to/sample3_Red.idat"

},

]

For cloud analysis, the IDAT sample sheet can be a CSV formatted file.

beadChipName,sampleSectionName

Beadchip 1 barcode (204753010023), sample section (R01C01)

Beadchip 1 barcode (204753010023), sample section (R02C01)

Beadchip 2 barcode (204753010024), sample section (R01C01)

Beadchip 2 barcode (204753010024), sample section (R02C01)

For DRAGEN Array Methylation QC on cloud, additional optional sample sheet fields are available.

Following Sample_Group, any number of additional columns can be added to include meta data fields such as sex, sample type, plate and well information, etc. Additional columns added after the Sample_Group column may have user-defined column header values. The Sample_ID field and any additional metadata added will be replicated in the Sample QC Summary output files.

The Sample_Group field will be used to populate the PCA Control Plot within the Sample QC Summary Plots file and the Principal Component Summary file. For the PCA Control Plot, each sample group will be assigned a unique color. Samples assigned to the same Sample_Group value will be the same color in the PCA Control Plot.

beadChipName,sampleSectionName,Sample_ID,Sample_Group,MetaData1

Beadchip 1 barcode (204753010023), sample section (R01C01),NA1231,Group1,F

Beadchip 1 barcode (204753010023), sample section (R02C01),NA1232,Group2,F

Beadchip 2 barcode (204753010024), sample section (R01C01),NA1233,Group2,M

Beadchip 2 barcode (204753010024), sample section (R02C01),NA1234,Group1,M

GTC Sample Sheet

The GTC sample sheet is a CSV or JSON formatted file with direct paths to sample GTC files. It enables easy analysis of samples from different directories.

Example CSV format:

GTC Path

/path/to/sample1.gtc

/path/to/sample2.gtc

/path/to/sample3.gtc

Example JSON format:

[

{

"GTC Path": "/path/to/sample1.gtc"

},

{

"GTC Path": "/path/to/sample2.gtc"

},

{

"GTC Path": "/path/to/sample3.gtc"

}

]

Input File Summary Table

In addition to the input files, there are set of intermediate files, including GTC, SNV VCF, CNV VCF and PGx CSV, which are outputs of some DRAGEN Array Local commands and inputs to other commands.

The table below summarizes the input files or intermediate file, their sources, and the associated DRAGEN Array Local commands and options.

The following section describes the outputs produced by DRAGEN Array.

CNV VCF File

DRAGEN Array produces one CNV variant call file (VCF) (*.cnv.vcf) per sample to report the CN status on the gene and sub gene level, along with the CN events for PGx targets.

The CNV VCF output file follows the standard VCF format. The QUAL field in the VCF file measures the CNV call quality. The CNV call quality is a Phred-scaled score capped at 60 and the minimal value is 0. Low quality calls (QUAL<7) are flagged by the Q7 filter. Low quality samples with LogRDev greater than a threshold 0.2 are flagged with the SampleQuality flag.

The CNV VCF files are by default bgzipped (Block GZIP) and have the “.gz” extension. The compression saves storage space and facilitates efficient lookup when indexed with the TBI Index File. To view these files as plain text, they can be uncompressed with bgzip from Samtools or other third-party tools. The CNV VCF must be bgzipped and indexed to be used in downstream DRAGEN Array commands, such as star allele calling.

The CNV VCF output file includes the following content.

##fileformat=VCFv4.1

##source=dragena 1.1.0

##genomeBuild=38

##reference=file:///hg38_with_alt/hg38_nochr_MT.fa

##FORMAT=<ID=CN,Number=1,Type=Integer,Description="Copy number genotype for imprecise events. CN=5 indicates 5 or 5+">

##FORMAT=<ID=NR,Number=1,Type=Float,Description="Aggregated normalized intensity">

##ALT=<ID=CNV,Description="Copy number variant region">

##FILTER=<ID=Q7,Description="Quality below 7">

##FILTER=<ID=SampleQuality,Description="Sample was flagged as potentially low-quality due to high noise levels.">

##INFO=<ID=CNVLEN,Number=1,Type=Integer,Description="Number of bases in CNV hotspot">

##INFO=<ID=PROBE,Number=1,Type=Integer,Description="Number of probes assayed for CNV hotspot">

##INFO=<ID=END,Number=1,Type=Integer,Description="End position of CNV hotspot">

##INFO=<ID=SVTYPE,Number=1,Type=String,Description="Structural Variant Type">

##CNVOverallPloidy=1.8

##CNVGCCorrect=True

##contig=<ID=1,length=248956422>

##contig=<ID=4,length=190214555>

##contig=<ID=10,length=133797422>

##contig=<ID=16,length=90338345>

##contig=<ID=19,length=58617616>

##contig=<ID=22,length=50818468>

##contig=<ID=22_KI270879v1_alt,length=304135>

#CHROM POS ID REF ALT QUAL FILTER INFO FORMAT 204619760001_R01C01

1 109687842 CNV:GSTM1:chr1:109687842:109693526 N <CNV> 60 PASS CNVLEN=5685;PROBE=124;END=109693526;SVTYPE=CNV CN:NR 2:0.966631132771593

4 68537222 CNV:UGT2B17:chr4:68537222:68568499 N <CNV> 60 PASS CNVLEN=31278;PROBE=383;END=68568499;SVTYPE=CNV CN:NR 0:0.376696837881692

10 133527374 CNV:CYP2E1:chr10:133527374:133539096 N <CNV> 60 PASS CNVLEN=11723;PROBE=194;END=133539096;SVTYPE=CNV CN:NR 2:0.980059731860893

16 28615068 CNV:SULT1A1:chr16:28603587:28613544 N <CNV> 57 PASS CNVLEN=8315;PROBE=164;END=28623382;SVTYPE=CNV CN:NR 2:0.980552325552963

19 40844791 CNV:CYP2A6.intron.7:chr19:40844791:40845293 N <CNV> 60 PASS CNVLEN=503;PROBE=38;END=40845293;SVTYPE=CNV CN:NR 2:0.9663775484762

19 40850267 CNV:CYP2A6.exon.1:chr19:40850267:40850414 N <CNV> 60 PASS CNVLEN=148;PROBE=21;END=40850414;SVTYPE=CNV CN:NR 2:0.9663775484762

22 42126498 CNV:CYP2D6.exon.9:chr22:42126498:42126752 N <CNV> 48 PASS CNVLEN=255;PROBE=370;END=42126752;SVTYPE=CNV CN:NR 2:0.981703411438716

22 42129188 CNV:CYP2D6.intron.2:chr22:42129188:42129734 N <CNV> 10 PASS CNVLEN=547;PROBE=333;END=42129734;SVTYPE=CNV CN:NR 2:0.965498002434641

22 42130886 CNV:CYP2D6.p5:chr22:42130886:42131379 N <CNV> 60 PASS CNVLEN=494;PROBE=172;END=42131379;SVTYPE=CNV CN:NR 2:0.970341562236357

22_KI270879v1_alt 270316 CNV:GSTT1:chr22_KI270879v1_alt:270316:278477 N <CNV> 60 PASS CNVLEN=8162;PROBE=91;END=278477;SVTYPE=CNV CN:NR 2:1.01191145130511

SNV VCF File

The software produces one genotyping variant call file (*.snv.vcf) file per sample, covering single nucleotide variants (SNV) and indels for the sample. It reports GenCell score (GS), B Allele Frequency (BAF), and Log R Ratio (LRR) per variant. The VCF file output follows VCF4.1 format.

Some additional details:

• Genotypes are adjusted to reflect the sample ploidy. Calls are haploid for loci on Y, MT, and non-PAR chromosome X for males.

• Multiple SNPs in the input manifest which are mapped to the same chromosomal coordinate (e.g. tri-allelic loci or duplicated sites) are collapsed into one VCF entry and a combined genotype generated. To produce the combined genotype, the set of all possible genotypes is enumerated based on the queried alleles. Genotypes which are not possible based on called alleles and assay design limitations (e.g. Infinium II designs cannot distinguish between A/T and C/G calls) are filtered. If only one consistent genotype remains after the filtering process, then the site is assigned this genotype. Otherwise, the genotype is ambiguous (more than 1) or inconsistent (less than 1) and a no-call is returned.

• Certain SNV and indel calls can be skipped when reported in the VCF. Skipped data can include unmapped loci, intensity-only probes used for CNV identification, and indels that do not map back to the genome. See Warning/Error Messages and Logs for messages that may be seen with DRAGEN Array Local related to the skipped data.

• The BAF and LRR are oriented with Ref as A and Alt as B relative to the reference genome, while GS is agnostic to the reference genome. Users familiar with GenomeStudio may observe BAF and LRR reported in the VCF as 1 minus the value reported in GenomeStudio depending on the Ref Alt allele orientation with the reference genome. GenomeStudio reports these values based on the information in the manifest without knowledge of the reference genome.

• The SNV VCF files are by default bgzipped (Block GZIP) and have the “.gz” extension. The compression saves storage space and facilitates efficient lookup when indexed with the TBI Index File. To view these files as plain text, they can be uncompressed with bgzip from Samtools or other third-party tools. The SNV VCF must be bgzipped and indexed to be used in downstream DRAGEN Array commands, such as star allele calling.

The SNV VCF output file includes the following content. The last row shows an example of variant call.

##fileformat=VCFv4.1

##source=dragena 1.1.0

##genomeBuild=38

##reference=file:///genomes/38/genome.fa

##FORMAT=<ID=GT,Number=1,Type=String,Description="Genotype">

##FORMAT=<ID=GS,Number=1,Type=Float,Description="GenCall score. For merged multi-assay or multi-allelic records, min GenCall score is reported.">

##FORMAT=<ID=BAF,Number=1,Type=Float,Description="B Allele Frequency">

##FORMAT=<ID=LRR,Number=1,Type=Float,Description="LogR ratio">

##contig=<ID=1,length=248956422>

##contig=<ID=2,length=242193529>

##contig=<ID=3,length=198295559>

##contig=<ID=4,length=190214555>

##contig=<ID=5,length=181538259>

##contig=<ID=6,length=170805979>

##contig=<ID=7,length=159345973>

##contig=<ID=8,length=145138636>

##contig=<ID=9,length=138394717>

##contig=<ID=10,length=133797422>

##contig=<ID=11,length=135086622>

##contig=<ID=12,length=133275309>

##contig=<ID=13,length=114364328>

##contig=<ID=14,length=107043718>

##contig=<ID=15,length=101991189>

##contig=<ID=16,length=90338345>

##contig=<ID=17,length=83257441>

##contig=<ID=18,length=80373285>

##contig=<ID=19,length=58617616>

##contig=<ID=20,length=64444167>

##contig=<ID=21,length=46709983>

##contig=<ID=22,length=50818468>

##contig=<ID=MT,length=16569>

##contig=<ID=X,length=156040895>

##contig=<ID=Y,length=57227415>

#CHROM POS ID REF ALT QUAL FILTER INFO FORMAT 202937470021_R06C01

1 2290399 rs878093 G A . PASS . GT:GS:BAF:LRR 0/1:0.7923:0.50724137:0.14730307

Genotype Call (GTC) File

The genotype call algorithm produces one genotype call file (.gtc) per sample analyzed. The Genotype Call (GTC) file contains the small variant (SNV and indel) genotype for each marker specified by the product and sample quality metrics. The sample marker location is not included and must be extracted from the manifest file. Binary proprietary format can be parsed using the Illumina open-source tool BeadArray Library File Parser.

BedGraph File

The BedGraph file contains the log R ratios from the genotyping algorithm for use in visual tools.

Star Allele CSV File

The Star Allele CSV file is an intermediate file generated by the star-allele call command and serves as the input to the star-allele annotate command. It contains all the star allele calls for all samples in a run. Each row in the file provides either a star allele diplotype or simple variant call for a PGx-related gene. Star allele diplotype calls for a sample and a gene may span multiple lines where alternative solutions can be listed.

The Star Allele CSV file also contains meta information marked by # at the top of the file for the genome build and PGx database used for the star allele calling.

The star_allele.csv file contains the following details per sample:

Below is an example of the first 4 columns from a star allele CSV file:

Sample,Rank,Gene or Variant,Type,Solution

204650490282_R02C01,1,CYP2C9,Haplotype,*9/*11

204650490282_R02C01,1,CYP2C19,Haplotype,*2/*10

Genotype Summary Files

The software produces genotype summary files (gt_sample_summary.csv and gt_sample_summary.json) that contains the following details per sample:

• Sample ID

• Sample Name

• Sample Folder

• Autosomal Call Rate

• Call Rate

• Log R Ratio Std Dev

• Sex Estimate

• TGA_Ctrl_5716 Norm R

The TGA_Ctrl_5716 Norm R field is specific to PGx products (e.g., Global Diversity Array with enhanced PGx). The field value is the Normalized R value of one probe and is meant as an assay control where < 1 indicates the sample failed in the TGA (Targeted Gene Amplification) process. If the product does not have this probe, it is not included in the gt_sample_summary.

Final Report

DRAGEN Array Cloud produces a Final Report (gtc_final_report.csv) per analysis batch similar to the one available in GenomeStudio. It contains the following details per locus per sample:

Note: Analyses on products with large numbers of loci (>1 Million) and large numbers of samples (>100) yield a large (50+ Gigabyte) Final Report that are difficult to download and review. It’s recommended to create analysis configurations that do not produce this report if large batches are desired.

For more information on interpreting DNA strand and allele information, see Illumina Knowledge article How to interpret DNA strand and allele information for Infinium genotyping array data.

Locus Summary

DRAGEN Array Cloud produces a Locus Summary (locus_summary.csv) per analysis batch similar to the one available in GenomeStudio. It contains the following details per locus:

CN Summary File

The sample summary contains per sample key stats for each sample in a batch that contains the following details per sample:

• Sample ID

• Sample Name

• Sample Folder

Copy Number Batch File

The copy number batch summary file (cn_batch_summary.csv) shows the total copy number gain, loss, and neutral (CN=2) values for each target region across all the samples in the analysis.

Example copy number batch summary file content:

Target Region,Total CN gain,Total CN loss,Total CN neutral

CYP2A6.exon.1,0,1,47

CYP2A6.intron.7,0,1,47

CYP2D6.exon.9,2,4,42

CYP2D6.intron.2,7,2,39

CYP2D6.p5,13,2,33

CYP2E1,2,0,46

GSTM1,0,42,6

GSTT1,0,33,15

SULT1A1,0,0,48

UGT2B17,0,34,14

All Target Regions,24,119,337

Warning/Error Messages and Logs

The following scenarios result in a warning or error message:

• Manifest file used to generate GTC is not the same as the manifest file used to generate the CN model.

• FASTA files and FASTA index files do not match.

For the following scenarios, the software reports messages to the terminal output (as either a warning or an error):

• Indel processing for GTC to VCF conversion failed.

• The input folder does not contain the required input files.

• An input file is corrupt.

Examples of such notifications can include the following:

Star allele JSON File

The star allele JSON file is produced per sample. It contains the fields present in the star allele CSV file as well as additional meta data and annotations.

Fields included in the star allele JSON header are described below.

Fields included in the star allele call (locusAnnotations) information are described below.

Fields included in the candidateSolution section, only available for star allele call type, are described below.

Example of JSON file content:

{
  "softwareVersion": "dragena 1.1.0+9f82ed31d8c17e42b80f67a3e2b271f1a873e1d1",
  "genomeBuild": "38",
  "starAlleleDatabaseSources": [
    "PharmVar Version: 6.1",
    "PharmGKB Database Version: Snapshot-2024.05.16",
    "UGT Alleles Nomenclature: 2010.12.21",
    "The Human Cytochrome P450 (CYP) Allele Nomenclature Database, July 2024"
  ],
  "phenotypeDatabaseSources": [
    "CPIC Database Version: 1.38.0",
    "DPWG Database Version: June 2023"
  ],
  "mappingFile": "DRAGENA-549-fix-annotate-sha.e56e884ed1f2d118e796cdab578ab895456bb94e.zip",
  "pgxGuideline": "CPIC",
  "sampleId": "207883050020_R08C03",
  "locusAnnotations": [
    {
      "gene": "CYP2C9",
      "callType": "Star Allele",
      "genotype": "*1/*1",
      "activityScore": "2",
      "phenotypeDatabaseAnnotation": "CYP2C9 Normal Metabolizer",
      "qualityScore": "0.9999",
      "rawScore": "0.9999",
      "supportingVariants": [],
      "candidateSolutions": [
        {
          "rank": 1,
          "genotype": "*1/*1",
          "activityScore": "2",
          "phenotypeDatabaseAnnotation": "CYP2C9 Normal Metabolizer",
          "qualityScore": 0.9999,
          "rawScore": 0.9999,
          "alleles": [
            {
              "solutionLong": "Complete: *1",
              "supportingVariants": [],
              "missingVariantSites": [],
              "collapsedAlleles": ""
            }
          ],
          "copyNumberRegions": "p5,exon.1,intron.1,exon.2,intron.2,exon.3,intron.3,exon.4,intron.4,exon.5,intron.5,exon.6,intron.6,exon.7,intron.7,exon.8,intron.8,exon.9,p3",
          "copyNumberSolution": "2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2"
        }
      ],
      "missingVariantSites": [
        {
          "id": "NC_000010.11:g.94938719T>G",
          "alleleIds": "*80"
        },
        {
          "id": "NC_000010.11:g.94938788C>T",
          "alleleIds": "*83"
        },
        {
          "id": "NC_000010.11:g.94938800G>A",
          "alleleIds": "*76"
        },
        {
          "id": "NC_000010.11:g.94941975G>A",
          "alleleIds": "*77"
        },
        {
          "id": "NC_000010.11:g.94942243T>G",
          "alleleIds": "*78"
        },
        {
          "id": "NC_000010.11:g.94942306C>T",
          "alleleIds": "*72"
        },
        {
          "id": "NC_000010.11:g.94942308C>T",
          "alleleIds": "*73"
        },
        {
          "id": "NC_000010.11:g.94942309G>T",
          "alleleIds": "*27"
        },
        {
          "id": "NC_000010.11:g.94947939G>T",
          "alleleIds": "*74"
        },
        {
          "id": "NC_000010.11:g.94949145C>T",
          "alleleIds": "*82"
        },
        {
          "id": "NC_000010.11:g.94949163del",
          "alleleIds": "*85"
        },
        {
          "id": "NC_000010.11:g.94972183A>T",
          "alleleIds": "*81"
        },
        {
          "id": "NC_000010.11:g.94981258C>T",
          "alleleIds": "*79"
        },
        {
          "id": "NC_000010.11:g.94986136A>C",
          "alleleIds": "*75"
        },
        {
          "id": "NC_000010.11:g.94986174G>C",
          "alleleIds": "*84"
        }
      ],
      "allelesTested": "*1,*2,*3,*4,*5,*6,*7,*8,*9,*10,*11,*12,*13,*14,*15,*16,*17,*18,*19,*20,*21,*22,*23,*24,*25,*26,*27,*28,*29,*30,*31,*32,*33,*34,*35,*36,*37,*38,*39,*40,*41,*42,*43,*44,*45,*46,*47,*48,*49,*50,*51,*52,*53,*54,*55,*56,*57,*58,*59,*60,*61,*62,*63,*64,*65,*66,*67,*68,*69,*70,*71,*72,*73,*74,*75,*76,*77,*78,*79,*80,*81,*82,*83,*84,*85"
    },
    {
      "gene": "CYP2C19",
      "callType": "Star Allele",
      "genotype": "*1/*2",
      "activityScore": "n/a",
      "phenotypeDatabaseAnnotation": "CYP2C19 Intermediate Metabolizer",
      "qualityScore": "0.9999",
      "rawScore": "0.9958",
      "supportingVariants": [
        {
          "chrom": "10",
          "pos": "94842866",
          "ref": "A",
          "alt": "G",
          "gt": "1/1",
          "gs": "0.2669",
          "baf": "1",
          "id": "NC_000010.11:g.94842866A>G",
          "alleleIds": "*1"
        },
        {
          "chrom": "10",
          "pos": "94775367",
          "ref": "A",
          "alt": "G",
          "gt": "0/1",
          "gs": "0.2191",
          "baf": "0.4690612",
          "id": "NC_000010.11:g.94775367A>G",
          "alleleIds": "*2"
        },
        {
          "chrom": "10",
          "pos": "94781859",
          "ref": "G",
          "alt": "A",
          "gt": "0/1",
          "gs": "0.3351",
          "baf": "0.66212183",
          "id": " NC_000010.11:g.94781859G>A",
          "alleleIds": "*2"
        },
        {
          "chrom": "10",
          "pos": "94842866",
          "ref": "A",
          "alt": "G",
          "gt": "1/1",
          "gs": "0.2669",
          "baf": "1",
          "id": " NC_000010.11:g.94842866A>G",
          "alleleIds": "*2"
        }
      ],
      "candidateSolutions": [
        {
          "rank": 1,
          "genotype": "*1/*2",
          "activityScore": "n/a",
          "phenotypeDatabaseAnnotation": "CYP2C19 Intermediate Metabolizer",
          "qualityScore": 0.9999,
          "rawScore": 0.9958,
          "alleles": [
            {
              "solutionLong": "Complete: *1",
              "supportingVariants": [
                {
                  "chrom": "10",
                  "pos": "94842866",
                  "ref": "A",
                  "alt": "G",
                  "gt": "1/1",
                  "gs": "0.2669",
                  "baf": "1",
                  "id": "NC_000010.11:g.94842866A>G"
                }
              ],
              "missingVariantSites": [],
              "collapsedAlleles": ""
            },
            {
              "solutionLong": "Complete: *2",
              "supportingVariants": [
                {
                  "chrom": "10",
                  "pos": "94775367",
                  "ref": "A",
                  "alt": "G",
                  "gt": "0/1",
                  "gs": "0.2191",
                  "baf": "0.4690612",
                  "id": "NC_000010.11:g.94775367A>G"
                },
                {
                  "chrom": "10",
                  "pos": "94781859",
                  "ref": "G",
                  "alt": "A",
                  "gt": "0/1",
                  "gs": "0.3351",
                  "baf": "0.66212183",
                  "id": " NC_000010.11:g.94781859G>A"
                },
                {
                  "chrom": "10",
                  "pos": "94842866",
                  "ref": "A",
                  "alt": "G",
                  "gt": "1/1",
                  "gs": "0.2669",
                  "baf": "1",
                  "id": " NC_000010.11:g.94842866A>G"
                }
              ],
              "missingVariantSites": [],
              "collapsedAlleles": "*2.001"
            }
          ],
          "copyNumberRegions": "p5,exon.1,intron.1,exon.2,intron.2,exon.3,intron.3,exon.4,intron.4,exon.5,intron.5,exon.6,intron.6,exon.7,intron.7,exon.8,intron.8,exon.9,p3",
          "copyNumberSolution": "2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2"
        }
      ],
      "missingVariantSites": [
        {
          "id": "NC_000010.11:g.94762715T>C",
          "alleleIds": "*34"
        }
      ],
      "allelesTested": "*1,*2,*3,*4,*5,*6,*7,*8,*9,*10,*11,*12,*13,*14,*15,*16,*17,*18,*19,*22,*23,*24,*25,*26,*28,*29,*30,*31,*32,*33,*34,*35,*38,*39"
    }

TBI Index File

The TBI (TABIX) index file is associated with the bgzipped VCF files. It allows for data line lookup in VCF files for quick data retrieval. The format is a tab-delimited genome index file developed by Samtools as part of the HTSlib utilities. For more information, visit the Samtools website.

Methylation Control Probe Output File

The software produces a control probe output file ({BeadChipBarcode}_{Position}_ctrl.tsv.gz) per sample that includes the raw methylated and unmethylated values for each control probe.

Each control probe has an address, type, color channel, name, and probe ID. It also provides the raw signal for methylated green (MG), methylated red (MR), unmethylated green (UG) and unmethylated red (UR).

The file can help identify which probes are available on a given BeadChip.

Methylation CG Output File

The software produces a CG output file ({BeadChipBarcode}_{Position}_cgs.tsv.gz) per sample that includes beta values, m-values and detection p-values for each CG site.

Beta values measure methylation levels in a linear fashion for easy interpretation. Unmethylated probes are close to zero and methylated probes are close to 1.

M-values are a log transformed beta value which provides a more representative measure of methylation.

Detection p-values measure the likelihood that the signal is background noise. It is recommended that p-value >0.05 are excluded from analysis as they are likely background noise.

see High-throughput Infinium methylation array QC using DRAGEN Array Methylation QC software tech note for further detail on calculation of these metrics.

Methylation Sample QC Summary Files

The software produces methylation sample QC summary in .xlsx and .tsv file formats (sample_qc_summary.xlsx and sample_qc_summary.tsv) per analysis batch, which provides per sample QC data for all samples in the batch.

The QC summary provides details on 21 controls metrics (see tables below), which are computed in same way as in the BeadArray Controls Reporter software from Illumina. In addition, it provides average red and green raw and normalized signals, time of scanning, proportion of probes passing, overall sample pass/fail status, and the failure codes for control metrics that did not pass. The sample pass status is defined as the passing of all 21 control metrics. The QC summary .xlsx file further highlights failing parameters for easy viewing.

The QC summary files contain the following fields:

The control metrics in the QC summary files are calculated as following. The default value for background correction offset (x) of 3,000 can be modified and applies to all background calculations indicated with (bkg + x). Note that the table uses default thresholds for EPIC arrays as example, the default thresholds changes with the methylation arrays. See section Threshold Adjustment for additional details.

Methylation Sample QC Summary Plots

The software produces methylation sample QC summary plots (sample_qc_summary.pdf) per analysis batch which provides visual depictions of two QC summary plots for quick visual review.

The file contains the following control plots:

Methylation Principal Component Summary

The software produces a methylation principal component summary file (pcs.tsv.gz) per analysis batch which provides principal component data for each sample within the batch. This can be used to identify the specific samples associated with points on the PCA control plot within the Methylation Sample QC Control Plots output file.

The files contain the following fields:

Methylation Manifest Files

The software produces two methylation manifest files

1. Manifest in Sesame format (probes.csv)

2. Additional information for control probes (controls.csv)

The probes.csv file has the following columns:

The controls.csv file has the following columns:

Methylation Warning/Error Messages and Logs

The following scenarios result in a warning or error message:

• Missing IDATs or manifest

• Incorrect sample sheet formatting

• Duplicate BeadChip Barcode and Position within the sample sheet

• Missing control or assay probes

• Missing required columns in the manifest

• Unable to compute certain metrics

Examples of such notifications can include the following:

Theoretical Coverage

The PGx genes and star/variant alleles listed below can be detected by DRAGEN Array v1.1 if available on the microarray. Known and novel star alleles not in the below list will not be reported. Star allele definitions are sourced from PharmVar and PharmGKB.

Among the PGx genes, HLA-A, HLA-B, and IFNL3/IFNL4 alleles are covered through tagging variants, specifically HLA-A,*31:01 (rs1061235.A>T); HLA-B,*15:02 (rs144012689.T>A); HLA-B,*57:01 (rs2395029.T>G); HLA-B,*58:01 (rs9263726.G>A); IFNL3/4, rs12979860 variant (T). Reliability of the tagging SNPs varies depending on the population. Additional information on PGx gene types, variant type versus star allele type, can be found here: Introducing-dragen-array-1-0-for-infinium-array-based-pharmacogenomics-analysis

PGx Star Allele Coverage for Specific PGx Products

PGx star alleles can only be called when the related variants in the star allele definition are present in a PGx product. An auxiliary file ([Product]_GS_import.txt) is provided for each product with the PGx variants and associated star alleles. The product files pages that contain the auxiliary files are listed in the table below.

Instructions on how to use the auxiliary file can be found here: How to use the auxiliary file.

Known Limitations of GDA-ePGx, GSAv4-ePGx, and GCRA-ePGx.

• APOE: GSAv4-ePGx and GCRA-ePGx do not support calling E2 and E4 due to the lack of functional probes for rs7412 and rs429358.

• CYP2A6: GDA-ePGx does not support *5 due to lack of coverage for *5 core variants.

• CYP4F2: for all three products

  • *1 and *2 are not distinguishable due to the lack of probes for rs30193105. Samples with *2 will be called as *1.

  • *3 and *4 are not distinguishable due to the lack of probes for rs30193105, while *3 core variant rs2108622 is covered by all three products. Samples with *4 will be called as *3.

• UGT1A1: *28 (rs8175347 [TA]8) and *37 (rs8175347 [TA]9) are not covered in all three PGx products due to the lack of functional probes.

• UGT2B15: GSAv4-ePGx and GCRA-ePGx do not support *4 or *5 due to the lack of probes for rs4148269 and rs1902023.

PGx Variants Masked in DRAGEN Array

During DRAGEN Array star allele calling, poorly performing PGx variants are masked and treated as "No Calls". Star alleles that are solely defined by the masked variants will NOT be called by DRAGEN Array. The tables below provide the variants that are masked per product with each row represents a single variant. The Variant_ID matches the ID field of the corresponding SNV VCF entry of the PGx product.

GDA-ePGx

GSAv4-ePGx

GCRA-ePGx

The following Types of Analysis are currently supported by DRAGEN Array:

• DRAGEN Array – Genotyping

• DRAGEN Array – PGx – CNV calling

• DRAGEN Array – PGx – Star allele annotation

• DRAGEN Array - Methylation QC

Product & Analysis Compatibility

These products/beadchips have been verified to be compatible with the following analyses and versions of DRAGEN Array:

DRAGEN Array – Genotyping

DRAGEN Array - PGx – CNV calling

DRAGEN Array – PGx – Star Allele Annotation

DRAGEN Array – Methylation QC

DRAGEN Array Local Overview

DRAGEN Array provides accurate, comprehensive, and efficient analysis of Infinium microarray data. The local command-line interface makes it easy for power users to have granular control and flexibility to support large scale microarray genomic studies.

Getting Started

DRAGEN Array Local utilizes a command-line interface which allows full user control of software functionality and easy automation of tasks. The software is designed to be used by power users and bioinformaticians. If new to using command-line interface, please review the Command-line interface Basics.

Computing Requirements

Before downloading and installing the software, ensure the following specifications are met for best performance:

Quota Specifications

The star-allele call command in DRAGEN Array Local requires quota to run. The quota is charged per sample analyzed and can be purchased on the Illumina Product Page. Quota is used for all samples analyzed including re-analysis or low-quality samples.

The credential provided in the activation email after purchasing should be used as an input to the star-allele call command through the "--license-server-url" option. During runtime, the logs will record the remaining quota at the beginning and the end of the analysis.

Internet is required to do a software license check and ensure paid quota is available for all samples in the analysis batch. For the software license check, the following endpoint is used: license.edicogenome.com.

Installation

Please follow the steps below to install the software on your compute infrastructure:

1. Click on the latest DRAGEN Array version installation package for the platform of your choice. Installers for Windows and Linux are available on the Illumina Support Site. Once download is completed, move the DRAGEN Array installation package to the desired folder. Administrative permissions may be required for system folders, for example /usr/local/bin for Linux, and C:\Program Files for Windows. Note: Throughout the remainder of the document, Linux will be assumed in the examples.

2. Unzip and extract the package. The executable can be found in the dragena subfolder of the software download after extraction.

3. To check that the DRAGEN Array installation was successful, follow these steps:

   • Open a command prompt (Windows) or terminal (Linux).

   • [Optional] Add /path/to/dragena/, e.g. /usr/local/bin/dragena-linux-x64-DAv1.1.0/dragena/, to your PATH – to access the executable anywhere in the folder structure

   • Execute the following command: /path/to/dragena/dragena version, or if the environmental variable PATH is set: dragena version

The version of the software will be displayed in the terminal window when the installation was successful.

Run DRAGEN Array Local

For genotyping analysis, there is no sample minimum required to run analysis.

For CNV PGx analysis, a minimum of 24 samples is required to run analysis. For a successful analysis, 22 samples must pass QC defined as having log R dev < 0.2. With a standard hardware specification in section Computing Requirements, up to 500 GDA-ePGx samples can be processed per analysis batch.

To optimize performance of the targeted PGx CNV caller and minimize batch effect, it is recommended to:

• Group samples in the same assay batch (e.g. whole genome amplication and targeted gene application assay batch) into the same analysis batch.

• Avoid combining sample batches processed on different reagent lots.

• Analyze batches of 96 samples or more.

• Samples processed in a two-week period from multiple library preparation batches can be grouped together to meet size requirement of an analysis batch. In such cases, it is recommended to use the same lot of reagents and instruments used in the workflow.

• Use the CN Model and PGx Database File provided as part of the standard product files

Quick Start

Use the following instructions to start the full PGx analysis, covering genotyping, PGx CNV and PGx star allele calling. Refer to Command Index for parameters for all commands.

Review section DRAGEN Array Applications for information on input files to use, sample minimums per analysis type and other best practices.

Command examples show analysis for a Linux system using folders instead of sample sheets. For Windows users, make sure to substitute the file paths in the commands following windows conventions, e.g., using backslash (\) instead of forward-slash (/). A sample sheet can be used to select specific samples out of a folder.

1. Open a command prompt (Windows) or terminal window (Linux) and navigate to the directory where the software was installed. Or a different, desired directory if the executable was added to the PATH environmental variable.

2. Use the genotype call command to call genotypes and generate GTC files using IDAT files as input. dragena genotype call --bpm-manifest /user/productfiles/manifest.bpm --cluster-file /user/productfiles/clusterfile.egt --idat-folder /user/IDATs --output-folder /user/gtc

3. Use the genotype gtc-to-vcf command to create SNV VCF files from the GTC files generated by the genotype call command. dragena genotype gtc-to-vcf --bpm-manifest /user/productfiles/manifest.bpm --csv-manifest /user/productfiles/manifest.csv --genome-fasta-file /user/productfiles/genome.fa --gtc-folder /user/gtc --output-folder /user/vcf

4. Use the copy-number call command to call PGx CNVs from the GTC files and produce CNV VCF files. It is recommended to use the same output folder used for SNV VCF since the star-allele call command accepts one VCF folder with SNV and CNV VCFs. dragena copy-number call --cn-model /user/productfiles/cnv_model.dat --gtc-folder /user/gtc --output-folder /user/vcf Note: For PGx CNV calling, it is recommended that 96 or more samples passing LogRDev <= 0.2 are included in the analysis.

5. Use the star-allele call command to generate star allele calls using the CNV and SNV VCF files generated by the gtc-to-vcf and copy-number call commands. dragena star-allele call --vcf-folder /user/vcf --database /user/productfiles/GDA_ePGx_E2_DAv1.0.0.zip --output-folder /user/star-alleles --license-server-url https://username:password@license.edicogenome.com Note: For PGx star allele calling, it is recommended to QC the samples and review the samples that have Log R Dev > 0.2, call rate < 0.99, or TGA Control probe < 1.0 to assess the reliability of the analysis. These metrics are provided in the genotyping sample summary file (gt_sample_summary.csv).

6. Use the star-allele annotate command to summarize the star alleles and add metabolizer statuses to the star alleles generated by the star-allele call command. Guidelines (CPIC or DPWG) can be specified. dragena star-allele annotate --star-alleles star_alleles.csv --guidelines CPIC --output-folder /user/metabolizer-statuses

7. [Optional] Use the copy-number train command to retrain the copy number model. dragena copy-number train --bpm-manifest /user/productfiles/manifest.bpm --genome-fasta-file /user/productfiles/genome.fa --gtc-folder /user/gtc --platform LCG --output-folder /user/productfiles/cnmodelnew

Note: DRAGEN Array will overwrite older files if using the same --output-folder from a previous analysis. If this is not desired, use different --output-folder for re-analyses.

Command Index

Use the following syntax when using the command-line interface:

dragena [command] [required parameters] [optional parameters]

copy-number

The root command for actions that act on copy number variants.

copy-number call

The command used to call copy number variants. A batch of 24 samples or more are required for analysis. For a successful analysis, 22 samples must pass QC defined as having log R dev < 0.2.

copy-number help

Displays help information for a copy-number command.

copy-number train

Trains copy number (CN) model for a set of samples. Generate a new CN model if using a customized cluster file (.egt) optimized for the specific data set.

• Execute the train command using the data sets that were used to optimize the cluster file.

• To use a CN model generated by the train command, the mask file for the manifest must be saved in the same directory as the manifest.

• A minimum of 96 samples is required to use the copy-number train command. For optimal performance, at least 150 is recommended.

• For best performance, validate the CN model using truth data before using in CN calling.

See Optimizing cluster files and copy number models for further details.

copy-number version

Displays version information for copy-number command.

genotype

The root command for genotype calling.

genotype call

Determines genotype calls (GTC) from IDAT files.

genotype gtc-to-bedgraph

Converts GTC to BedGraph files, producing BedGraph formatted visualization files from the log R ratio data contained in the GTC intermediate files.

genotype gtc-to-vcf

Converts GTC (v5) to SNV VCF Files. The command is only applicable for Genotype Call Files produced by DRAGEN Array.

Squashing duplicates

In the manifest, there can be cases where the same variant is probed by multiple different assays. These assays may be the same design or alternate designs for the same locus. In the default mode of operation, these duplicates will be "squashed" into a single record in the VCF to reflect a true variant rather than probe genotype. The method used to incorporate information across multiple assays is defined further in the VCF description . When the --unsquash-duplicates option is provided, this "squashing" behavior is disabled, and each duplicate assay will be reported in a separate entry in the VCF file. This option is helpful when you are interested in investigating or validating the performance of individual assays, rather than trying to generate genotypes for specific variants. Note that if a locus has more than two alleles and is also queried with duplicated designs, the duplicates will not be unsquashed (i.e., in the case of multi-allelic variants). DO NOT use --unsquash-duplicates option if doing star allele calling downstream as that command expects squashed variants.

Genome cache

By default, the entire reference genome will be read into memory. Generally, this will be more efficient than reading data from the indexed reference on disk at the expense of greater memory utilization. For situations in which the genome caching is not desirable (low memory availability or a small input manifest), it is possible to disable this default behavior with the --disable-genome-cache option.

Auxiliary loci

Certain classes of variant types (such as multi-nucleotide variants) are not currently supported in the upstream analysis software that produces GTC files. However, it is possible to query this type of variant by creating a SNP design that differentiates the specific multi-nucleotide alleles of interest. For example, if the true source sequence is

ATGC[AT/CG]GTAA

This assay could be designed as a SNP assay with the following source sequence

ATGC[A/C]NNNN

gtc-to-vcf provides an option (--auxiliary-loci) to supply a list of auxiliary records (in VCF format) to restore the true alleles for these cases in the output VCF. There are several restrictions around this function

• The auxiliary definition must NOT be a multi-allelic variant.

• The auxiliary definition must be a multi-nucleotide variant.

• There must NOT be multiple array assays (e.g., duplicates) for the locus.

Note: The genome fasta files for human genomes are provided by illumina on the support site.

genotype help

Displays the help information for a genotype command.

genotype version

Displays current DRAGEN Array Local version.

help

Displays the help information.

version

Displays current DRAGEN Array Local version.

star-allele

The root command PGx star allele calling.

star-allele help

Displays help information for a star-allele command.

star-allele version

Displays version information for star-allele.

star-allele call

Calls PGx star allele diplotypes. The SNV VCF files should be generated using the DRAGEN Array gtc-to-vcf command with unsquash-duplicates off (default) and without filter loci.

star-allele annotate

Annotates and summarizes the star-alleles, specifically for metabolizer statuses and outputs in a consolidated JSON report. Metabolizer status is determined through direct lookup into public PGx guidelines CPIC or DPWG as specified by the user.

Troubleshooting and Additional Support

Tips for using the Command-line interface

DRAGEN Array Local utilizes a command-line interface which allows full user control of software functionality and easy automation of tasks. The software is designed to be used by power users and bioinformaticians.

When using command-line consider the following tips:

• Spaces cannot be part of a file name in a command. If the file name has spaces, use quotes around the file name

• To correct a typing error in a previously entered command, use the up arrow to repeat the previous command, then correct the error before re-entering it.

• Double check the command. Misspelling, extra, or missing dashes, etc. will cause the command to be unrecognizable by the software.

  • When entering paths or long names, copy and paste the values to help avoid errors.

  • If using Windows, use a File Explorer window to navigate to the product file or folder that is needed by the DRAGEN Array Local command. While holding down the shift button on the keyboard, right click the file and select the 'Copy as Path' option. Then paste the copied path into the command prompt to use the file or folder.

• To cancel a command while it is running, press Control + C on the keyboard.

Optimizing cluster files and copy number models

A Cluster File (.egt) contains the cluster positions of every probe used for genotyping analysis. Illumina provides a standard cluster file for all commercial Infinium BeadChips. It may be desirable to create a custom cluster file if the one provided does not fit the data well or if a semi-custom or custom BeadChip, that do not come with a cluster file, are used. GenomeStudio 2.0 is the software used to create custom cluster files.

To facilitate the review and optimization of PGx variant GenTrain cluster positions, a GenomeStudio auxiliary file is provided for each PGx Array product through the DRAGEN Array Support Site and array product files page, e.g. Infinium Global Diversity Array with Enhanced PGx Product Files. The auxiliary file is a tab-delimited text file that can be imported into GenomeStudio through Column Import. The file contains the Infinium Assay to PGx star allele mapping, covering the variants involved in DRAGEN Array PGx star allele calling.

When updating the cluster file for pharmacogenomic applications, understand the specifications for the copy number model file before beginning.

Before creating a custom cluster file, review the Infinium Genotyping Data Analysis Technical Note, the Infinium Arrays Support Webinar Video, and Custom cluster file creation for improved copy number analysis.

A Copy Number (CN) Model File (.dat) contains the data needed to make accurate copy number calls for pharmacogenomics. This file is used in the creation CNV VCFs which are inputs to the star allele calling command. Illumina provides a standard CN model file for all commercial PGx Infinium BeadChips. If it is determined the cluster file needs to be customized, the CN Model File should also be updated using the copy-number train command available with DRAGEN Array Local only. i.e.,

1. Use GenomeStudio 2.0 to generate a new cluster file.

2. Use the genotype call command to call genotypes and generate GTC files using IDAT files as input. dragena genotype call --bpm-manifest /user/productfiles/manifest.bpm --cluster-file /user/productfiles/new_clusterfile.egt --idat-folder /user/IDATs --output-folder /user/new_gtcs

3. Use the copy-number train command to retrain the copy number model. Note: The --platform option can be found in the Assay Format heading value from the CSV manifest. dragena copy-number train --bpm-manifest /user/productfiles/manifest.bpm --genome-fasta-file /user/productfiles/genome.fa --gtc-folder /user/new_gtcs --platform LCG --output-folder /user/productfiles/new_cnmodel

4. Use the new_cnmodel for subsequent copy-number call commands.

Note the difference in the cluster file requirement based upon the version of DRAGEN Array used:

• Version 1.1: If using a CN model with a different cluster file, the software will provide a warning but will proceed with copy number calling. As a result, a user can choose to keep using the commercial CN model from illumina in combination with custom updated EGT file in the PGx analysis.

• Version 1.0: The same cluster file used for copy number training must be used to generate GTC files for copy number calling. Otherwise, the software will produce an error and exit.

For reference, see the Command Index for details of copy-number train command.

To retrain the CN model file, 96 samples must be used at minimum with 90 of those samples passing QC defined as Log R Dev less than or equal to 0.2. It is recommended to train with at least 150 samples. A greater number of samples can be advantageous, but diminishing returns and longer computation times are seen after 3,000 samples.

It is recommended to manually QC the training samples and remove samples that have Log R Dev > 0.2, call rate < 0.99, or TGA Control probe < 1.0 so only the highest quality samples are used in the training. The same samples used to create the new cluster file should be used to retrain the CN Model. To minimize batch effect in the training sample set, the samples should be analyzed in as few batches as possible and come from the same reagent lots.

The copy-number train algorithm is designed with the assumption that the copy number distribution resembles the standard population distributions. This ensures the updated CN model file is representative of the normal populations in which it will be used to calculate copy number for key pharmacogenomic targets.

Pharmacogenomic analysis for semi-custom arrays

Semi-custom arrays add additional content or other pre-designed Infinium booster content to enhance the commercial array content. This additional content can be analyzed for genotyping applications to obtain information on SNV and indel calls.

For pharmacogenomic applications, PGx CNV and star allele calls are limited to content included on the commercial Infinium PGx arrays. Additional semi-custom content will not be included in the pharmacogenomic results.

When designing a semi-custom array using a commercial Infinium PGx array backbone, such as the Global Diversity Array with enhanced PGx, it is important to retain all backbone content in the design as removing content could decrease the quality of result.

Pharmacogenomic analysis for semi-custom arrays should be run using DRAGEN Array Local. Because the PGx CNV calling and PGx star allele calling algorithms are only compatible with commercial product files (see Applications), to fully analyze semi-custom PGx beadchips some steps of the pipeline can be run twice; once with the semi-custom product files (to get complete semi-custom SNV VCF files), and once with the commercial product files (to get the PGx CNV VCF files, PGx Star Allele output, and metabolizer report).

The semi-custom product files can be used via the Command-line interface in genotype call, genotype gtc-to-vcf, and used in GenomeStudio, i.e.,

1. Use GenomeStudio 2.0 to prepare a custom cluster file for the semi-custom array, following guidance outlined in Custom cluster file creation for improved copy number analysis.

2. Open a command prompt (Windows) or terminal window (Linux) and navigate to the directory where the software was installed. Or a different, desired directory if the executable was added to the PATH environmental variable.

3. Use the genotype call command to call all semi-custom genotypes and generate custom content GTC files using IDAT files as input. dragena genotype call --bpm-manifest /user/productfiles/semi_custom_manifest.bpm --cluster-file /user/productfiles/semi_custom_clusterfile.egt --idat-folder /user/IDATs --output-folder /user/semi_custom_gtcs

4. Use the genotype gtc-to-vcf command to create custom content SNV VCF files from the custom content GTC files generated by the genotype call command. dragena genotype gtc-to-vcf --bpm-manifest /user/productfiles/semi_custom_manifest.bpm --csv-manifest /user/productfiles/semi_custom_manifest.csv --genome-fasta-file /user/productfiles/genome.fa --gtc-folder /user/semi_custom_gtcs --output-folder /user/semi_custom_vcfs

5. Perform Quick Start steps 1-6 using the commercial Infinium PGx array product files to obtain PGx CNV VCFs, star allele calls, and metabolizer status annotations.

Keep the GTC files and SNV VCF files generated using the semi-custom product files in clearly labelled folders to distinguish them from the GTC and SNV VCF files generated using the commercial product files. Note that the GTC and SNV VCFs generated using the commercial product files will not contain genotypes for the semi-custom/add-on content. The GTC and SNV VCFs generated using the semi-custom product files cannot be used for downstream PGx analysis commands.

Copy number variation can be detected for genes and regions listed below. The chromosome locations are GRCh38 based.

PGx Allele Definitions and PGx Guidelines

DRAGEN Array star allele calling leverages the star allele definitions provided by PharmVar and PharmGKB. DRAGEN Array star allele phenotype annotation, using the “star-allele annotate” command, is achieved through direct lookup into public PGx guidelines CPIC or DPWG, which is selected by the user when running DRAGEN Array.

See table below for details of the data sources.

DRAGEN Array “star-allele annotate” command provides both metabolizer status and activity score annotations for genes covered by the CPIC and DPWG guidelines.

Specifically, CPIC metabolizer/phenotype annotations are supported for CACNA1S, CYP2B6, CYP2C19, CYP2C9, CYP2D6, CYP3A5, DPYD, G6PD, MT-RNR1, NUDT15, RYR1, SLCO1B1, TPMT, UGT1A1, CFTR, IFNL3/IFNL4 and VKORC1, among them activity scores are supported for CYP2C9, CYP2D6, and DPYD. DPWG metabolizer/phenotype annotations are supported for CYP1A2, CYP2B6, CYP2C19, CYP2C9, CYP2D6, CYP3A4, CYP3A5, DPYD, NUDT15, SLCO1B1, TPMT, UGT1A1, VKORC1 and F5, among them activity scores are supported for CYP2D6 and DPYD.

Extended Multi-allelic variants based on the designs in the supported PGx products

• DRAGEN Array PGx extends any single allele variant definitions obtained from PharmVar or PharmGKB that have multiple alleles in Illumina's product files to include all alleles of the Multi Allelic Variant (MAV). The table below shows the MAVs that were extended in the DRAGEN Array Database to cover all alleles for that MAV that are in the product files. Allele Name describes the allele that was added to the database.

Exceptions to Star Allele Definitions

G6PD

With the changes of reference genomes, the definition for a star allele sometimes need to be updated accordingly.

Mediterranean Haplotype and Mediterranean, Dallas, Panama, Sassari, Cagliari, Birmingham are defined by two variants rs5030868 and rs2230037. In genome build GRCh37, Mediterranean Haplotype is defined by rs2230037 G>A and rs5030868 G>A, and Mediterranean, Dallas, Panama, Sassari, Cagliari, Birmingham is defined by rs5030868 G>A, with rs2230037 reference allele G.

In genome build GRCh38, Mediterranean Haplotype is defined by rs5030868 G>A, with rs2230037 reference allele A, and Mediterranean, Dallas, Panama, Sassari, Cagliari, Birmingham is defined by rs2230037 A>G and rs5030868 G>A.

Variant rs2230037 is ignored in all other G6PD alleles except in the two Mediterranean alleles.

The version history for DRAGEN Array product documentation: