You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on my analysis of droplet scRNA-Seq cell barcodes (e.g blog post here), I think we should add the option to remove cell barcodes within the automatically generated whitelist if they are within an edit distance threshold of another whitelisted barcode with greater frequency. I believe there is sufficient evidence to suggest error barcodes (INDEL or sequencing error) may pass the whitelist threshold. We could merge these barcodes into the true barcode from which they derive but this risks merging two truly different cells. On balance, removing these potential error barcodes seems like the best approach. This is compatible with the current error correction within extract which is restricted to only barcodes not in the whitelist. Thus the steps for whitelist generation and filtering would be:
Parse first 50M reads, extract cell barcodes and generate a whitelist using the knee method
(Optionally) identify all cell barcodes within an edit distance threshold of exactly one whitelisted barcode
(Optionally) Remove whitelisted barcodes within an edit distance threshold of another whitelisted barcode within greater frequency
Parse all reads, extract cell barcodes and filter reads against the whitelist (with optional correction of cell barcodes not in the whitelist)
The text was updated successfully, but these errors were encountered:
Based on my analysis of droplet scRNA-Seq cell barcodes (e.g blog post here), I think we should add the option to remove cell barcodes within the automatically generated whitelist if they are within an edit distance threshold of another whitelisted barcode with greater frequency. I believe there is sufficient evidence to suggest error barcodes (INDEL or sequencing error) may pass the whitelist threshold. We could merge these barcodes into the true barcode from which they derive but this risks merging two truly different cells. On balance, removing these potential error barcodes seems like the best approach. This is compatible with the current error correction within extract which is restricted to only barcodes not in the whitelist. Thus the steps for whitelist generation and filtering would be:
The text was updated successfully, but these errors were encountered: