> 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/general/library-preparation-general-faq-list/000006988.md).
# How to pool Illumina DNA Prep with Exome 2.5 libraries on the NextSeq series and NovaSeq 6000?
Recommendations for approximate number of samples to pool for estimated coverages of 50X, 100X, or 200X, for the NextSeq 500/550, NextSeq 1000/2000, and NovaSeq 6000 are available in the Illumina DNA Prep with Exome 2.5 Enrichment [Data Sheet](https://support.illumina.com/content/dam/illumina/gcs/assembled-assets/marketing-literature/illumina-dna-exome-enrich-m-gl-00002/illumina-dna-exome-enrich-data-sheet-m-gl-00002.pdf).
These are estimates and each lab must verify empirically. Also, note that the reference guide does not contain specific instructions for plexities between 1-plex and 12-plex, so this may require optimization. Illumina does not have specific guidance for other sequencing instruments.
\
\
\
| |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #6988), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000006988%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/general/library-preparation-general-faq-list/000006988.md?ask=&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.