> 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/tso500/dragen-tso-500-guides/dragen-tso-500-v2.6/overview-1/quality-control/run-qc.md).

# Run QC

## Run QC

The Run Metrics section of the metrics output report provides sequencing run quality metrics along with suggested values to determine if they are within an acceptable range. The overall percentage of reads passing filter is compared to a minimum threshold. For Read 1 and Read 2, the average percentage of bases ≥ Q30, which gives a prediction of the probability of an incorrect base call (Q‑score), are also compared to a minimum threshold. The following tables show run metric and quality threshold information for different systems.

The values in the Run Metrics section are listed as NA in the following situations:

* If the analysis was started from FASTQ files.
* If the analysis was started from BCL files and the InterOp files are missing or corrupt.

### NextSeq 500/550 or NextSeq 550Dx (RUO)

| Metric             | Description                                         | Recommended Guideline Quality Threshold | Variant Class |
| ------------------ | --------------------------------------------------- | --------------------------------------- | ------------- |
| PCT\_PF\_READS (%) | Total percentage of reads passing filter.           | ≥80.0                                   | All           |
| PCT\_Q30\_R1 (%)   | Percentage of Read 1 reads with quality score ≥ 30. | ≥80.0                                   | All           |
| PCT\_Q30\_R2 (%)   | Percentage of Read 2 reads with quality score ≥ 30. | ≥80.0                                   | All           |

### NovaSeq 6000 or NovaSeq 6000Dx (RUO)

| Metric             | Description                                         | Recommended Guideline Quality Threshold | Variant Class |
| ------------------ | --------------------------------------------------- | --------------------------------------- | ------------- |
| PCT\_PF\_READS (%) | Total percentage of reads passing filter.           | ≥55.0                                   | All           |
| PCT\_Q30\_R1 (%)   | Percentage of Read 1 reads with quality score ≥ 30. | ≥80.0                                   | All           |
| PCT\_Q30\_R2 (%)   | Percentage of Read 2 reads with quality score ≥ 30. | ≥80.0                                   | All           |

### NextSeq 1000/2000

| Metric           | Description                                         | Recommended Guideline Quality Threshold | Variant Class |
| ---------------- | --------------------------------------------------- | --------------------------------------- | ------------- |
| PCT\_Q30\_R1 (%) | Percentage of Read 1 reads with quality score ≥ 30. | ≥85.0                                   | All           |
| PCT\_Q30\_R2 (%) | Percentage of Read 2 reads with quality score ≥ 30. | ≥85.0                                   | All           |

### NovaSeq X

| Metric           | Description                                         | Recommended Guideline Quality Threshold | Variant Class |
| ---------------- | --------------------------------------------------- | --------------------------------------- | ------------- |
| PCT\_Q30\_R1 (%) | Percentage of Read 1 reads with quality score ≥ 30. | ≥85.0                                   | All           |
| PCT\_Q30\_R2 (%) | Percentage of Read 2 reads with quality score ≥ 30. | ≥85.0                                   | All           |


---

# 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/tso500/dragen-tso-500-guides/dragen-tso-500-v2.6/overview-1/quality-control/run-qc.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.