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

RefineTagsAndSort #1646

Closed
bshim181 opened this issue May 7, 2024 · 1 comment
Closed

RefineTagsAndSort #1646

bshim181 opened this issue May 7, 2024 · 1 comment

Comments

@bshim181
Copy link

bshim181 commented May 7, 2024

This is an example image and explanation posted on MiXCR website. I could not fully comprehend what the threshold was accomplishing.
Screenshot 2024-05-07 at 3 21 33 PM

In general, during refineTagsAndSort, it seems to correct huge proportion of artificial barcode generated as a artifact of sequencing error.
Screenshot 2024-05-07 at 3 29 22 PM

Previously I assumed that MiXCR discards barcodes with read evidences lower than the threshold, but based on the refineTagsAndSort reports for my samples, that seems to be not the case. Rather it corrects the UMIs and most of the reads are retained. In this case, what is the threshold accomplishing? Are UMIs under that threshold corrected and converged into UMIs over that threshold?

@bshim181 bshim181 closed this as completed May 7, 2024
@mizraelson
Copy link
Member

MiXCR does both. It first corrects the errors in the UMI sequence and then applies the threshold.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants