Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document case for demultiplexed data #19

Merged
merged 1 commit into from
Apr 28, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions docs/MANUAL.md
Original file line number Diff line number Diff line change
Expand Up @@ -665,6 +665,26 @@ condition/row barcode ID pairs.
Row barcodes are counted as unexpected sequences if they are not successfully matched by the above
procedure.

## Using PoolQ on Demultiplexed Data
PoolQ was designed to quantify multiplexed DNA sequence data, and its features and interface are
specifically designed for that use case. However, it is still possible to use PoolQ to quantify
demultiplexed data. PoolQ still requires a column barcode, representing the samples. So, the
simplest way to process demultiplexed data is to create a "dummy" column reference file such as:

```
A,Sample
C,Sample
G,Sample
T,Sample
```

If you provide a column barcode policy of `FIXED@0`, PoolQ will use the first base of each read as
its demultiplexing barcode. The column reference file maps each base to the same sample, named
"Sample". Note that in this case if the first base of a read is `N`, it will not match to a barcode
in the sample reference file, and the read will not be counted as a match. If this is undesirable,
you can additionally specify that PoolQ should use the `mismatch` barcode matching scheme for
column barcodes.

## Contact Us

Your feedback of any kind is much appreciated. Please email us at
Expand Down