> 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/icm/analyses/analysis-functionality/data-viewer/chromosome-view/selecting-data-tracks-for-visualization.md).
# Selecting Data Tracks for Visualization
Genomic information plotted on the canvas is organized into horizontal sections called tracks. The exact number, type, and presentation of tracks depend on several factors, such as the underlying analysis pipeline, available annotation, and the level of zoom. The tracks are added, removed, or customized via the **Select tracks** dialog.
The content of the *Select tracks* dialog depends on the data nodes present on the *Analyses* tab of the current analysis. Current analysis pipeline is depicted in the center of the window, while data nodes that can be visualised are highlighted by the colour of their layer. Tracks can be turned on or off by selecting the check boxes in the list of possible tracks (and data nodes) on the left.
For the ease of use, the analysis pipeline and the list of tracks are linked: hovering over the track list highlights the matching data node in the pipeline and vice versa, i.e. selecting a data node in the pipeline panel highlights the respective node in the track list. Once you decided on the tracks that should be plotted, push **Display selection** to depict them on the canvas.
---
# 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/icm/analyses/analysis-functionality/data-viewer/chromosome-view/selecting-data-tracks-for-visualization.md?ask=&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.
