> For the complete documentation index, see [llms.txt](https://cmo-ci.gitbook.io/access-quality-control-v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cmo-ci.gitbook.io/access-quality-control-v1/master.md).

# Introduction

MSK-ACCESS Quality Control (QC) Version 1 (v1) is intended to ensure all samples are processed in an accurate and consistent manner using the <https://github.com/mskcc/ACCESS-Pipeline> workflow.&#x20;

The following pages give descriptions on how to interpret Quality Control metrics presented in the PDF report, page by page.&#x20;

Here is an example Quality Control report for the V1 [ACCESS pipeline](https://github.com/mskcc/ACCESS-Pipeline):

{% file src="/files/-M9Z4soSmZ5KdMTIE7Ar" %}
09780\_B
{% endfile %}

{% hint style="info" %}
Note: All **output** sections in the following pages will refer to files found in the **QC\_Results** folder from a V1 ACCESS pipeline run.&#x20;

The subfolders are named as: **waltz\_\<bam\_type>\_\<pool\_A\_or\_B>\_(exon\_level\_files)?**

There will be 12 such subfolders, and each will contain a copy of that metrics file, for the specific combination of bam type and Pool (which may be either target-specific or bait-specific) that is listed.
{% endhint %}