Closed taltman closed 2 years ago
Here are some example inputs that trigger this issue for me (GitHub won't accept a file extension of ".fna", so I've tacked on a ".txt" as well): MalbNV.fna.txt SilNV.fna.txt
It looks like you've hit a memory limit of some kind based on the 'Killed' in the output. For coronavirus, 64G of RAM is recommended. One way around this is to add the --glsearch
option which reduces the memory requirement considerably. And using -s
and --glsearch
reduces it even further and results in much faster processing. I recommend you try that and see how it goes. We use -s
and --glsearch
for SARS-CoV-2.
Argh, I forgot to set up my swap space before running the container. That explains the memory issue. Thanks for pointing that out.
Renaming this issue to focus on the need for VADR to clearly communicate to the user that there is a memory limitation issue.
I think the docs could be more explicit about the expected memory requirements for running VADR in different ways. And the error messages should clearly state that there was insufficient memory for the process to continue.
Ok, thanks for the suggestion, I will look into updating the error message.
I do still suggest trying to run with -s --glsearch
if you continue to have problems with memory. Recommended options for SARS-CoV-2 are in step 4 after following this link:
And how to modify those command-line options to use the 'corona' set of models that you are using is explained here:
VADR 1.4.1 outputs a more informative error message in this situation by appending:
v-annotate.pl may have run out of available memory, especially if you see a 'Killed' message.
When processing a Coronavirus genome, I encountered the following error. Any hints?