> 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.

## Where to find the versions for a case

* In the **sample drawer**, available on every interpreter screen, under the sample's workflow history.
* The [report](/products/workbench/variant-interpreter/generating-a-report.md)'s **Methods** section records the workflow and run ID, but not the caller versions or reference genome.

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

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

```
GET https://docs.omics.ai/products/workbench/variant-interpreter/pipeline-and-caller-versions.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.