-
Notifications
You must be signed in to change notification settings - Fork 31
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
v1.4 segfault consensus #174
Comments
It didn't just align incorrectly, it aligned to sequence that doesn't even exist. Neat trick, that! Can you upload 7-consensus/packages/part026.cnspack so I can debug? |
I can, but immediately only via Globus (same as for my other tickets). Does that work as well? |
That works. |
To confirm, is this a Hi-C (or any non-trio) run? I think it might be related to b5d87b0 where we didn't tell consensus which reads are ONT in that case, leading to slower and potentially worse consensus. Can you see how many ONT reads you have in this case being used for consensus, there should be a |
Yes, this is a consensus run based on phasing paths derived from Strand-seq. The count of entries in the ont subset fasta is 6513. |
OK, I confirmed if you change the |
Ok. Does that bug also affect the consensus in case of an unphased assembly run (no trio, no phasing paths)? |
No, only those that use the --paths option. |
that is good to know. I will apply b5d87b0 to my Verkko installation as well and rerun the consensus for my assemblies. |
P.S.: any plans for a v1.4 bugfix release yet? |
Yeah we plan to have one this month, I was waiting to see if #173 can also be fixed. |
Hi,
I have a single case of a segfault in the consensus phase:
It's v1.4 plus two bug fixes (3119b39 and 4f6a54e). As a side note, the overall run was registered by Snakemake as having failed, despite the weird
did not finish successfully, exit code 0.
Best,
Peter
The text was updated successfully, but these errors were encountered: