Closed taltman closed 3 years ago
Confirmed this bug. Reported upstream to Eric at NCBI: https://github.com/nawrockie/vadr/issues/21
@tomer this bug is independent of the PFAM annotations, right? Is it possible to run the PFAM alignments on the GB entries that crashed outside of VADR while we're waiting for the bug to be resolved?
It is not independent, as the Pfam annotations are currently used to identify the maturation proteins on ORF 1ab, and the gene-calling of ORF 1ab comes from VADR.
The first thing I'd like to see is for @rchikhi to re-run these few samples, and see if that clears up some of the failed runs. I can then look at the output from that second run of each sample, to see what the issue is.
As I suspected, merely re-running them seemed to clear up ~96% of the issues. The two accessions that caused that obscure VADR crash have been reported up-stream to Eric.
Thanks @rchikhi for re-running. @rcedgar , please leave this open as a reminder on my part to follow up with Eric.
FYI, I filed this bug in the VADR repo, and Eric responded that he's currently working on a fix:
looks like it's been temp-fixed https://github.com/nawrockie/vadr/issues/21#issuecomment-661279793
Yep, he provided me with a work-around for now, and a proper fix will go out in the next VADR release, which will be a few weeks from now. I'll incorporate it into the updated version of DARTH that I'll send to you this evening.
Confirmed that my implementation of the work-around works for the example above. Closing!