> 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/illumina-ffpe-dna-prep-with-exome-2.5/additional-information/quick-check-of-run-quality.md).

# Quick check of run quality

Checking coverage on the target regions can be a quick way to determine if the map/align step ran as expected. Following the enrichment and sequencing guidelines, the Mean Target Coverage (MTC) Depth for tumor samples is expected to be ≥130x, for normal samples ≥50x. This metric is called "Average alignment coverage over target region" and can be found in the \<sample>.target\_bed\_coverage\_metrics\_\<tumor/normal>.csv file. Note that results for "Target bed" should be evaluated, as DRAGEN Report defaults to genome, while this is a target-based, WES, assay. Another metric to check is "Aligned reads in target region", which gives a percentage of the reads in the target region relative to the entire genome and can be thought as Percent Read Enrichment.\
\
Other quality metrics to check can include the percentage of Mapped Reads (aim of ≥ 90%) and the Insert length (aim of ≥ 125bp) in the \<sample>.mapping\_metrics.csv file.


---

# 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/illumina-ffpe-dna-prep-with-exome-2.5/additional-information/quick-check-of-run-quality.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.