> 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/emedgene/emedgene-analyze-manual/variant-visualization/variant-visualization-tool/visual-aids.md).

# Visual aids

Visual aids in the [**Variant visualization tool**](/emedgene/emedgene-analyze-manual/variant-visualization/variant-visualization-tool.md) help you follow the selected variant and interpret signal tracks during review. They include a variant highlighting overlay and reference lines on supported tracks.

## Variant highlighting <a href="#variant-highlighting" id="variant-highlighting"></a>

To assist in identifying and tracking genomic variants, the platform highlights variant regions with a light blue overlay in all relevant tracks. The highlight remains visible when zooming or panning and dynamically moves to newly selected variants.

## Reference lines

To enhance clarity and facilitate a better understanding of genomic data, distinct reference lines are incorporated across various tracks, tailored to provide critical data points at a glance.

### TNS Track

* Grey dashed line at Y=0.0
* Red dashed line at Y=-0.5
* Blue dashed line at Y=0.5
* Y-axis fixed range from 2.0 to -2.0

### BAF Track

* Grey dashed lines at Y=1.0, Y=0.5, and Y=0.0
* Y-axis fixed range from 1.1 to -0.1

### LogR Track (array only)

* Grey dashed line at Y=0.0
* Red dashed line at Y=-0.5
* Blue dashed line at Y=0.5
* Y-axis fixed range from 2.0 to -2.0


---

# 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/emedgene/emedgene-analyze-manual/variant-visualization/variant-visualization-tool/visual-aids.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.