-
Notifications
You must be signed in to change notification settings - Fork 553
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
Assertion in bntseq fails #120
Comments
I have the same question when using the latest version of BWA (0.7.15). while when i change the version to 0.7.8, the question disappeared. i really confused about the result. |
This seems to happen if you use a named pipe when creating the index, as in: PS: It happens both in the latest version from GitHub (0.7.15-r1144-dirty) and in the version from the Canonical repo (0.7.12-r1039). |
Hello every one, Any suggestions ? |
I'd love to. But I can't find the bntseq.c file. Is it because the tool has been installed with conda ? |
You may try like this, build from the source, and try this test version:
|
@yanlinlin82 |
Thank you for testing and feeding back. |
Reopening this as I am facing the exact same issue: Here's the output from my command: I tried to do understand the error. It complained about an equality. Here's the output from bc:
The length is the same except it has a negative sign. Edit: I tried to run the patch. Here's the output from the patch:
|
How did you solve this problem |
I run into the same problem. I tried to increase memory at first, but it still didn't work and I solved it by using bwa-mem2. First I installed bwa-mem2:
and instead of using the standard:
after installing bwa-mem2 the code will look like this:
In my case it looked like this:
I hope it's still useful and it will work for you guys! PS I will try to give an update to make bwa-mem2 possible to be used while running speedseq or other tools that base on bwa algorythm. |
Reindex the reference fasta helps me under the same problem. |
BWA crashes when running on my PE RNA-seq data.
It looks like the failure is caused by a failed assertion here.
The logged error is as follows:
The text was updated successfully, but these errors were encountered: