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

All paired-end MiSeq reads end up unmatched #26

Closed
zwets opened this issue Oct 19, 2021 · 1 comment
Closed

All paired-end MiSeq reads end up unmatched #26

zwets opened this issue Oct 19, 2021 · 1 comment

Comments

@zwets
Copy link

zwets commented Oct 19, 2021

Running KneadData against MiSeq paired-end reads results in all reads ending up in *_unmatched_1.fq and *_unmatched_2.fq.

This appears to be a regression introduced in commit ecf589d. In particular, the deletion of these lines:

    if " 1:" in lines[0]:
        lines[0]=lines[0].replace(" 1","").rstrip()+"#0/1\n"
    elif " 2:" in lines[0]:
        lines[0]=lines[0].replace(" 2","").rstrip()+"#0/2\n"

The replace(" 1","") and replace(" 2","") used to strip the Illumina read index, so that reformatted read headers became:

@M01336:233:000000000-AJKD1:1:1101:15356:1498:N:0:15#0/1
@M01336:233:000000000-AJKD1:1:1101:15356:1498:N:0:15#0/2

Since commit ecf589d the headers are rewritten to:

@M01336:233:000000000-AJKD1:1:1101:15356:1498.1:N:0:15#0/1
@M01336:233:000000000-AJKD1:1:1101:15356:1498.2:N:0:15#0/2

and therefore don't match up.

@github-actions
Copy link

Thank you for creating this issue.
We currently field issues through our bioBakery Discourse Support Forum.
If you would please post the issue to discourse we would be happy to sync up with you to get it resolved.

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

1 participant