> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/library-preparation/dna-library-prep/library-preparation-dna-library-prep-reference_material-list/000001409.md).

# Optimizing coverage for targeted resequencing

Determining the distribution of coverage depth for targeted regions requires the generation of normalized coverage plots. Simply calculating the mean sequencing coverage will provide only a summary of the average read depth across the bases targeted in the enriched sample. The most commonly used methods report a given percentage of targeted bases covered at a particular depth (eg, 90% of targeted bases covered at 10× read depth). It is possible to increase the total sequencing coverage by deeper sequencing.

TruSeq exome analysis scripts generate mean normalized coverage plots, showing the distribution of coverage depth across all targeted bases. This enables researchers to calculate just how much sequencing will be required to yield a given percentage of targeted bases at a particular read depth. It is important to note that this normalization is a characteristic property of the Illumina TruSeq Exome Enrichment assay, averaged over a number of runs. TruSeq analysis scripts have been designed to report the distribution of depth of coverage in both an absolute and normalized manner (eg, 90% of targeted bases covered at 0.2× of the normalized mean).

Information regarding Creation of Cumulative Normalized Coverage Plots and How to Calculate the Required Amount of Sequencing Data can be found in the Technical Note [Optimizing Coverage for Targeted Resequencing](https://www.illumina.com/documents/products/technotes/technote_optimizing_coverage_for_targeted_resequencing.pdf).

* The information outlined in this technical note can also be helpful for calculating and optimizing target coverage for other targeted sequencing panels.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                              |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #1409), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000001409%20-%20Library%20Preparation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# 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://knowledge.illumina.com/library-preparation/dna-library-prep/library-preparation-dna-library-prep-reference_material-list/000001409.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.
