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

Pairing information causing errors? #1

Closed
peterdfields opened this issue May 21, 2019 · 6 comments
Closed

Pairing information causing errors? #1

peterdfields opened this issue May 21, 2019 · 6 comments
Labels
bug Something isn't working

Comments

@peterdfields
Copy link

peterdfields commented May 21, 2019

I just gave bwa-mem2 (binaries; building from source doesn't change the effect) a quick try, using paired reads in two separate files, and I got the following error:

[0000] 1: Calling process()

Threads used (compute): 1
Projected #read in a task: 79375
------------------------------------------
Memory pre-allocation for chaining: 2544445000
Memory pre-allocation for BSW: 239617024
Memory pre-allocation for BWT: 51611776
------------------------------------------
No. of pipeline threads: 2
bwa-mem2: src/fastmap.cpp:253: ktp_data_t *kt_pipeline(void *, int, void *, mem_opt_t *, worker_t &): Assertion `ret->n_seqs <= nreads' failed.
Aborted (core dumped)

If I run the same command with only the left or right set of reads there isn't an issue. I think an important point here is the way the headers of the fastq encode the left and right read. The read set that I'm working that causes this error arises from mapping followed by subsetting of the bam to retain only mapped reads, and then output with samtools fastq with the -N flag (so left and right are distinguished by the /1 and /2 suffix). If I use the original reads that retain the @<instrument>:<run number>:<flowcell ID>:<lane>:<tile>:<x-pos>:<y-pos> <read>:<is filtered>:<control number>:<sample number> format then bwa-mem2 seems to work fine. Note that both read sets work with bwa-mem so I assume the error is just arising as a result of the pairing information? Please let me know if additional information would be useful.

@lh3
Copy link
Member

lh3 commented May 22, 2019

Do you have example input?

@peterdfields
Copy link
Author

Sure, I can share the read set with you. Is there an email address I could send the link to?

@lh3
Copy link
Member

lh3 commented May 22, 2019

Do you see the error in a small set of reads? Thanks.

@lh3
Copy link
Member

lh3 commented May 22, 2019

I understand what happens to this. I don't need sample data any more.

@lh3 lh3 added the bug Something isn't working label May 22, 2019
@NickyPan
Copy link

yeah, I got the error either, waiting for good news

@peterdfields
Copy link
Author

This error seems fixed now if building from source at commit dc3bb8d, though probably before. I will close this issue now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants