> For the complete documentation index, see [llms.txt](https://docs.omics.ai/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omics.ai/products/workbench/variant-interpreter/pipeline-and-caller-versions.md).

# Pipeline & caller versions

Each case is produced by a specific version of the long-read WGS workflow, which in turn pins specific versions of each variant caller and the reference data they use. That version set determines which variants are called and how they're annotated, so it is recorded on every case and every report.

## Where to find the versions for a case

* In the **sample drawer**, available on every interpreter screen, under the sample's workflow history.
* On the submitted [report](/products/workbench/variant-interpreter/generating-a-report.md).

## Released version sheets

For each workflow release, the lab publishes a standardized **Variant Caller Versions** sheet (PDF) listing every caller and its pinned version. These are published alongside the release and linked here:

* `[LINK: Tertiary Variant Caller Versions, v1.12.0 (PDF)]`
* `[LINK: Tertiary Variant Caller Versions, v1.11.0 (PDF)]`

{% hint style="info" %}
If you need to compare two cases that behave differently, check whether they were produced by different workflow versions first; that's the most common explanation.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.omics.ai/products/workbench/variant-interpreter/pipeline-and-caller-versions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.