-
Notifications
You must be signed in to change notification settings - Fork 354
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
mosdepth behaves abnormal. #3581
Comments
yes, this one was giving me a hard time as well. The very issue is well known for many years in the old samtools code: But why we are hitting it here, I am not sure. In the debugger if you delete the viral.bam and re-creates just well. I've made the samtools call safer here: And it seems to be solving the issue in my bcbio run. Let me know how it works for you (you'd need to upgrade to the latest code). Sergey |
Hi @naumenko-sa , I circumvented this issue by turning off
And finally, it went through. Cheers! Best, |
Thanks for confirming! In my project, it finished with multicore bcbio (one-node, as opposed to ipython). |
see also this fix: #3587 |
Version info
bcbio_nextgen.py --version
): 1.2.9alsb_release -ds
): CentOS Linux release 7.8.2003 (Core)To Reproduce
Exact bcbio command you have used:
Your yaml configuration file:
Log files (could be found in work/log)
Please attach (10MB max):
bcbio-nextgen-commands.log
, andbcbio-nextgen-debug.log
.bcbio-nextgen-commands log
bcbio-nextgen-debug.log
The text was updated successfully, but these errors were encountered: