> 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/instrumentation/general/instrumentation-general-faq-list/000006622.md).

# How to determine the appropriate kit configuration to use based on the data needed?

To determine the number of reads needed for the run (project), multiply the desired reads per sample by the number of samples in the pool. With the total number of reads, identify the kit and sequencer that fits the data needs using the sequencer specifications pages, listed below.

* [Specifications for the iSeq 100 System](https://www.illumina.com/systems/sequencing-platforms/iseq/specifications.html)
* [Specifications for the MiniSeq System](https://www.illumina.com/systems/sequencing-platforms/miniseq/specifications.html)
* [Specifications for the MiSeq System](https://www.illumina.com/systems/sequencing-platforms/miseq/specifications.html)
* [Specifications for the MiSeq i100](https://www.illumina.com/systems/sequencing-platforms/miseq-i100/specifications.html)
* [Specifications for the NextSeq 500/550 System](https://www.illumina.com/systems/sequencing-platforms/nextseq/specifications.html)
* [Specifications for the NextSeq 1000/2000 System](https://www.illumina.com/systems/sequencing-platforms/nextseq-1000-2000/specifications.html)
* [Specifications for the NovaSeq 6000 System](https://www.illumina.com/systems/sequencing-platforms/novaseq/specifications.html)
* [Specifications for the NovaSeq X/X Plus](https://www.illumina.com/systems/sequencing-platforms/novaseq-x-plus/specifications.html)

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #6622), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000006622%20-%20Instrumentation%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/instrumentation/general/instrumentation-general-faq-list/000006622.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.
