> 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/icm/analyses/analysis-functionality/task-menu/qa-qc.md).

# QA/QC

Connected Multiomics contains a number of quality control tools and reports that can be used to evaluate the current status of your analysis and decide downstream steps. Quality control tools are organized under the Quality Assurance / Quality Control (QA/QC) section of the context-sensitive menu and are available for different type of data nodes.

This section will illustrate:

* [Feature distribution](/icm/analyses/analysis-functionality/task-menu/qa-qc/feature-distribution.md)
* [Imported count matrix report](/icm/analyses/analysis-functionality/task-menu/qa-qc/feature-distribution-1.md)
* [Single-cell QA/QC](/icm/analyses/analysis-functionality/task-menu/qa-qc/single-cell-qa-qc.md)
* [Cell barcode QA/QC](/icm/analyses/analysis-functionality/task-menu/qa-qc/cell-barcode-qa-qc.md)
* [5-base Methylation QC](/icm/analyses/analysis-functionality/task-menu/qa-qc/5-base-methylation-qc.md)

In addition to the tools listed above, many other functionalities can also be interpreted in sense of quality control. For instance, principal components analysis, hierarchical clustering (on sample level), variant detection report, and quantification report.


---

# 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/icm/analyses/analysis-functionality/task-menu/qa-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.