> 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/str-visualization-v100.41+.md).

# STR visualization (v100.41+)

In v100.41 and later, inspect the repeat structure and read alignments for STR variants in the [**Variant visualization tool**](/emedgene/emedgene-analyze-manual/variant-visualization/variant-visualization-tool.md).

{% hint style="success" %}
Review repeat counts and other STR quality values on the [**Quality tab**](/emedgene/emedgene-analyze-manual/variant_page/quality_section/quality-metrics-per-variant-type/str-quality-metrics.md).
{% endhint %}

## How to open the STR graph alignment image

<figure><img src="https://1131024994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGCW0DnLlE7QjoZPNmKIi%2Fuploads%2Fgit-blob-13fe0de98c58548e39bbcbaa1dfe85e09b5abab0%2Fv41_view_str_graph%20(1).gif?alt=media" alt=""><figcaption><p>Opening the STR graph alignment image.</p></figcaption></figure>

**Prerequisite**: The STR locus has a supported alignment image in a case.

{% hint style="info" %}
If no supported alignment image exists for the locus, the **View STR graph** option is not available for variants in this locus.
{% endhint %}

{% stepper %}
{% step %}
Select the STR variant in the variant table or open its variant page and move to the **Variant visualization tool**.
{% endstep %}

{% step %}
In the **Variant visualization tool**, select **View STR graph** from the top navigation panel.
{% endstep %}
{% endstepper %}

**Result:** One popup opens for each sequenced sample that has a supported STR graph alignment image for the locus.

When you navigate to another variant, **View STR graph** returns to its default state. Any open STR graph popups close.

## Learn more

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Variant visualization tool</strong></td><td>IGV-based genome viewer for inspecting variants, tracks, and supporting evidence during case review.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-analyze-manual/variant-visualization/variant-visualization-tool.md">Learn more</a></td></tr><tr><td><strong>STR quality metrics</strong></td><td>Repeat counts and other quality values for STR variants on the <strong>Quality tab</strong>.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-analyze-manual/variant_page/quality_section/quality-metrics-per-variant-type/str-quality-metrics.md">Learn more</a></td></tr></tbody></table>


---

# 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/str-visualization-v100.41+.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.