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

mismatch read in strip_error_barcodes #465

Open
adamcantor22 opened this issue Feb 21, 2024 · 0 comments
Open

mismatch read in strip_error_barcodes #465

adamcantor22 opened this issue Feb 21, 2024 · 0 comments

Comments

@adamcantor22
Copy link
Member

Describe the bug
When running demultiplexing of MTC 16S Run23, one sample, "EAR4", ended up with one more read in the reverse file than in the forward after the strip_error_barcodes step. I used diff, zgrep, and awk to determine the extraneous sample and removed it. This was that read:

@M02617:814:GW231120000:1:1114:21145:14315 2:N:0:CGTAGCGA-CTACTATA GCCAGTTTGGGTCTTGGCTATTGTGAGATCAGATATGTTAAAGCCACTTTCGTAGTCTATTTTGTGTCAACTGGAGTTTTTTACAACTCAGGTGAGTTTTAGCTTTATTGGGGAGGGTGTGATCTAAAACACTCTTTACGCCGGCTTCTA
+
111>A113@111A1B1B1BDBAG333D3311FF3GF2D2AF2FBECGB11F?GEFFEF2DDDHHFGFHDGHF00F01A12//BFHHFGHHFEFGHAGHHGFGHHHHGFHGFH?FGGG/?E/GFGBGDF1BGGGFHHHHEFC?BC/BCCGF

Completely unclear to me why this has happened, never happened before. Will have to take a closer look at this read, its associated forward read. I suspect it has something to do with a weird special character.

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

No branches or pull requests

1 participant