Adam Freedman opened issue #348: busco fails to create blastdb for large genome but doesn't throw any related exceptions at ezlab / busco

Adam Freedman
2020-10-29T15:59:58Z

I've used BUSCO quite a bit over the past few years, both for genome and transcriptome analyses. In my most recent attempt, I ran BUSCO on the axolotl genome with the most current built (from conda) and with the tetrapoda_odb10 lineage directory. The problem seems to be that makeblastdb is failing someplace ... as all that gets output is a nal file ... nothing else. As a result, things downstream don't work ... logging indicate files get created that subsequently don't appear to exist, and while busco completes, is says that all buscos are missing (presumably because there is no blast dbase). Also, for what it's worth, this was run with exclusive use of a compute node and all 48 cores (so ~ 225G). Stderr and stdout do not indicate anything went wrong with makeblastdb so I'm wondering if buried in the code someplace there is a try/except where logging of stderr is bypassed? Regardless, a solution would be welcome!