> 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/000007457.md).

# Differences in the percent clusters passing filter on patterned and non-patterned flow cells

Illumina sequencers use either patterned or non-patterned flow cells. Instruments that usenon-patterned flow cells areMiSeq, NextSeq 500/550, and MiniSeq. Instruments that usepatterned flow cells include iSeq 100, NextSeq 1000/2000, NovaSeq 6000, NovaSeq X Series, and MiSeq i100 Series.

Instruments that use patterned flow cells have artificially lower percent clusters Passing Filter (%PF) metrics compared to non-patterned flow cells.

* With patterned flow cells, there is no template generation or preliminary filtration step during image analysis, which results in lower %PF values.
* Because template generation and the associated preliminary filtration steps are not applied, all nanowells, including empty wells or clusters that may be dim, low quality, or polyclonal are included in the raw cluster count, which leads to lower %PF values.
* The uniform feature sizes and optimal spacing in the patterned flow cell enable significantly increased cluster density for patterned flow cells, ultimately resulting in a greater yield capacity.
* Although the %PF metric is generally lower with patterned flow cells, it does not negatively impact performance or data quality.
* Consult the specifications for the instrument and sequencing configuration to evaluate run performance, quality, and data output.

For further information, see Knowledge Base article [Calculating Percent Passing Filter for Patterned and Nonpatterned Flow Cells](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000006309.md)

\
\
\ <br>

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