-
Notifications
You must be signed in to change notification settings - Fork 164
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
Error parsing bubbles file during polishing #584
Comments
This may have something to do with the warning in the log. Flye does not expect non-ACGT fasta characters in general and may not handle them right. Do you think you may have those in your reads? Did you get this warning earlier in the run as well? If you don't expect this characters, but see the warning, this may be a fasta/q formatting error. Flye parser is supposed to catch those, but maybe not in 100% cases. Otherwise, I've never seen this error in a released version yet. |
Probably I should have mentioned this earlier but my input long reads are Illumina-corrected ONT (R9.4) reads. I don't use the ( |
I just tried Flye 2.9.2 and got exactly the same error at the same location. |
@GuillaumeHolley thanks. I will need an input example that reproduces the problem to fix it.. Can you come up with a bam file that could be provided as input to Misha |
Just wanted to check if you were able to fix the problem? |
Hi @fenderglass, Unfortunately not. The problem is that even though the issue has occurred on multiple occasions, it is still a rare occurrence. Any attempt to reproduce the issue using a smaller input resulted in Flye finishing the job as expected. |
Very strange.. But the whole run (that is problematic) is failing consistently? Could you be that you have a disk data corruption somewhere? |
Closing the thread because of inactivity. If the issue is still unresolved, feel free to reopen! |
Hi,
I get the following error during the polishing step:
The error happened a first time on a machine with 48 threads and 386G of RAM attributed to the job. I resumed it from the last completed stage (see log above) on a machine with 64 threads and 480G of RAM given to the job but I got the same error. I've run the exact same command many times on similar data and never got this issue before. When inspecting the
40-polishing
sub-directory, the minimap2 log shows no issue. The bubble file is quite large, 358GB.Thank you for your help,
Guillaume
The text was updated successfully, but these errors were encountered: