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

thread 'main' panicked at 'assertion failed: p <= 0.0' #43

Closed
menickname opened this issue Apr 13, 2020 · 9 comments
Closed

thread 'main' panicked at 'assertion failed: p <= 0.0' #43

menickname opened this issue Apr 13, 2020 · 9 comments

Comments

@menickname
Copy link

I am currently using longshot for variant calling in a reference-based bacterial genome assembly pipeline. For most genomes longshot does not render issues. However for some genomes I encounter the following error:

thread 'main' panicked at 'assertion failed: p <= 0.0'

I am using ONT reads and have set the -P 0.01 value which does not lead to a solution in this case.

Thank you in advance.
Beste regards,
Nick Vereecke

@philres
Copy link

philres commented Jul 15, 2020

Hi,

I get the same error with a human dataset.

Would appreciate any help.

Thanks,
Philipp

@vibansal
Copy link
Collaborator

Can you share a small dataset that can reproduce this error?

@menickname
Copy link
Author

menickname commented Jul 29, 2020

Dear @vibansal
When using long-read sequencing data (Nanopore) from viral origin, no problems occur upon implementation of longshot in the pipeline, nevertheless upon using it in a bigger dataset from bacterial origin, the error occurs. I got it again for a new dataset from another bacterial species. When using the complete dataset I got the error. This is an example of a few reads used in this analysis:
subsample_data.fastq.zip

Unfortunately, I am not able to share the complete dataset on here.
Thanks,
Nick

@SegoleneDiry
Copy link

Hi,

I get the same error on a bacterial dataset using Longshot v4.0.1
Did you fix the issue?

Thanks,

@menickname
Copy link
Author

Dear @SegoleneDiry

I am still waiting on a respons on my final answer on July 29.
Any update on this @vibansal

Thank you in advance.

@vibansal
Copy link
Collaborator

vibansal commented Oct 29, 2020

If either of you can share a dataset (bam file and reference fasta) to reproduce this error, I would really like to fix it. You can upload the files to a secure OneDrive folder here

@amandawarr
Copy link

I have the same problem with a virus.

I can upload data. I've got one dataset that it will run on and one that it won't for the same reference.

@vibansal
Copy link
Collaborator

vibansal commented Nov 5, 2020

Thanks.

vibansal added a commit that referenced this issue Nov 6, 2020
@vibansal
Copy link
Collaborator

vibansal commented Nov 6, 2020

Fixed. If you still encounter the error, please let us know.

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

5 participants