> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/illumina-trupath-genome/data-visualizations-and-analysis/visualize-data-in-igv.md).

# Visualize Data in IGV

This page provides instructions for visualizing DRAGEN secondary analysis outputs using IGV.

### Visualizing Phased Variants in IGV&#x20;

IGV ([Integrative Genomics Viewer](https://igv.org/)) is an interactive desktop tool for visualizing and exploring genomic data—like BAM/CRAM alignments, variants (VCF), and annotation tracks—so you can quickly inspect regions of interest, assess read support, and validate findings.

DRAGEN Germline analysis for Illumina TruPat Genome generates standard output formats such as BAM/CRAM and VCF files that can be directly loaded into IGV for visualization and review. The key files useful for IGV visualizations are listed below:

* Phased BAM: `<sample_name>/<sample_name>.bam`
  * Index: `<sample_name>/<sample_name>.bam.bai`
* Phased small variant VCF: `<sample_name>/<sample_name>.hard-filtered.gvcf.gz`
  * Index: `<sample_name>/<sample_name>.hard-filtered.gvcf.gz.tbi`
* CNV VCF: `<sample_name>/<sample_name>.cnv.vcf.gz`
  * Index: `<sample_name>/<sample_name>.cnv.vcf.gz.tbi`
* SV VCF: `<sample_name>/<sample_name>.sv.vcf.gz`
  * Index: `<sample_name>/<sample_name>.sv.vcf.gz.tbi`
* Phase block GTF: `<sample_name>/<sample_name>.phase_blocks.gtf.gz`
* MRJD VCF: `<sample_name>/<sample_name>.mrjd.hard-filtered.vcf.gz`
* MRJD phased BAM: `<sample_name>/<sample_name>.mrjd.phased.bam`
* MRJD VCF in haplotype separated format: `<sample_name>/mrjd_supporting_files/<sample_name>.mrjd.<paralog_name>.vcf.gz`
* SAM file containing reference region alignments for MRJD: `<sample_name>/mrjd_supporting_files/<sample_name>.mrjd.reference_region_alignments.sam`

IGV supports both loading data from local files and streaming tracks directly from signed URLs for remote, secure access.

**Option 1 — Download files locally from Platform Core, then open in IGV.**\
You can download the DRAGEN output files from Platform Core onto your computer and load them into IGV as local tracks. This can be done either via the [**Platform Core CLI**](https://help.ica.illumina.com/command-line-interface/cli-datatransfer#download-data) (e.g., using `icav2 projectdata download <file_path>`) or directly from the **Platform Core web browser UI** by clicking data and download.

<figure><img src="https://2122546113-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCiFAstZpxWHpI6k3vTvF%2Fuploads%2Fgit-blob-8d9da06faa843893e9173b522c4c1d18c505ff58%2FScreenshot%202026-01-21%20at%2011.56.00.png?alt=media" alt=""><figcaption><p>Click [Download] to start downloading from browser</p></figcaption></figure>

Next, click **File → Load from File** to load local files to IGV.

**Option 2 — Stream files directly into IGV using signed URLs.**\
If you prefer not to download large files locally, you can stream tracks straight into IGV using **signed URLs**. Generate signed URLs with:

```
icav2 projectdata downloadurl -o table <file_path>
```

where `file_path` can be found by right-clicking the data, and copy either Path or ID

<figure><img src="https://2122546113-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCiFAstZpxWHpI6k3vTvF%2Fuploads%2Fgit-blob-28e8f041070e799808f1ea7f1b3d3fa2933caf67%2FScreenshot%202026-01-23%20at%2012.19.13.png?alt=media" alt=""><figcaption></figcaption></figure>

Then copy the output URL(s) and paste them into IGV (**File → Load from URL**) to load the tracks remotely.

\
We recommend using the following IGV preference for alignment:

* Group by: HP
* Color by: PS
* Display mode: squished
* Show softclips
* Turn off downsampling

<figure><img src="https://2122546113-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCiFAstZpxWHpI6k3vTvF%2Fuploads%2Fgit-blob-86466a70511d0de55fe3bc0c46f4e6eac042a02f%2Fimage.png?alt=media" alt=""><figcaption><p>Phased VCF, and Haplotagged BAM at TP53 Gene</p></figcaption></figure>

In view above, reads are grouped by haplotype ("HP") and colored by Phase Block ("PS"). The grey reads are unphased, meaning they cannot be confidently assigned to either group.

### Visualizing MRJD Data in IGV&#x20;

To inspect MRJD results in IGV, load the following files generated by the pipeline:

* `<prefix>.mrjd.phased.bam`
* `mrjd_supporting_files/<prefix>.mrjd.<paralog_name>.vcf.gz`
* `mrjd_supporting_files/<prefix>.mrjd.reference_region_alignments.sam`

The following steps use the *SMN1–SMN2* paralog set as an example. For other paralog sets, use the corresponding per-gene VCF file and region.

1. Load the phased BAM file.
2. Go to the region of interest, for example *SMN1* (`chr5:70924941-70966375`).
3. Right-click the reads in the alignment track, select **Group alignments by**, and then select **phase**. IGV groups the reads by copy label, for example `copy1_SMN1` or `copy4_SMN2`.
4. Load the per-gene VCF file for the paralog set, `mrjd_supporting_files/<prefix>.mrjd.SMN1-SMN2.vcf.gz`. This file adds a variant track for each copy.
5. Load the reference region alignments SAM file. This track shows how the reference sequence of the paralogous region (for example, *SMN2*) aligns to the region you are viewing (for example, *SMN1*).

The following example shows the resulting IGV view for *SMN1*.

<figure><img src="https://2122546113-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCiFAstZpxWHpI6k3vTvF%2Fuploads%2FUdnxSAG94LWO3J4Ffg60%2Fmrjd_trupath_igv_example.png?alt=media&amp;token=189bcd2a-4b82-4bab-8d02-a59dc33edb2b" alt=""><figcaption></figcaption></figure>

<p align="center"></p>

**Interpret the IGV View**

The per-gene VCF file reports every *SMN1* and *SMN2* copy under both regions. The sample column names show the copy‑to‑region assignments. In the example above, copies 1, 2, and 3 are assigned to *SMN1*, and copy 4 is assigned to *SMN2*.

In the phased BAM track, each group contains the reads assigned to one copy. Use these reads to check the read support for the variants called in each copy.

The reference region alignments track shows the reference sequence of region 2 aligned under region 1. For paralog sets with three regions, such as *NCF1–NCF1B–NCF1C*, the track also shows region 3. Mismatches in this track mark the reference difference sites between the paralogous regions. At these sites, a copy that carries the alternate allele usually matches the paralogous region sequence.

Compare the variants in each copy with the reference difference sites to interpret the origin of the copy:

* If a copy matches region 1 at most reference difference sites, the copy is likely derived from region 1, which usually contains the functional gene.
* If a copy matches region 2 (or 3) at most reference difference sites, the copy is likely derived from that region, which often contains a pseudogene.
* If a copy matches region 1 except for a short stretch of consecutive sites that match region 2 (or 3), the copy might carry a putative gene conversion event.
* If a copy matches region 1 on one side of a breakpoint and region 2 (or 3) on the other side, the copy might carry a putative recombination event.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.bioinsight.illumina.com/illumina-trupath-genome/data-visualizations-and-analysis/visualize-data-in-igv.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
