# “On Bait” reads localized to ACCESS panel

![](/files/-M9Z5eq57iPNBxeZUEz7)

**Theoretical Method**

Divide the number of reads mapping to ACCESS genome bait regions by the sample’s total read count.&#x20;

{% hint style="info" %}
Note: This metric comes from the standard BAM
{% endhint %}

**Technical Methods**

* Tool Used:
  * waltz.jar CountReads
  * aggregate\_bam\_metrics.sh
  * tables\_module.py
  * plots\_module.r
* Input
  * ACCESS pool A and pool B bed files
  * Standard Bam (tables also produced for U / S / D bams)
* Output
  * Text file with the read count information: “sample\_id.bam.read-counts.txt”&#x20;
  * Text files for aggregated results “read-counts.txt”<br>

**Interpretations**\
Ideally should be between 60%-80% and should not drop below 50% for ctDNA samples (A + B targets combined). Because A and B targets are mixed in 50:1 ratio, there should be a larger on-target rate for the A targets. If the rate drops below 50%, with adequate read counts, this could be indicative of a bad capture.  For buffy coats, this is about 35%-45%.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cmo-ci.gitbook.io/access-quality-control-v1/on-bait-reads-localized-to-access-panel-standard-bam.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
