Closed jzrapp closed 2 years ago
It seems you are running out of memory. Try to set the --splits
parameter to something line 8
, or even 16
. This parameter splits the search step into multiple parts. This will reduce speed a bit but will prevent memory issues.
I'll probably change the default value in the next version to prevent cases like this.
Let me know it it works!
Hi, I actually already did this after receiving the error the first time.
I run the command like this genomad end-to-end --splits 16 all-samples.fasta all-samples_VIRUSES_out genomad_db/genomad_db_v1.1/
and I allocated 250 GB memory..
What version of MMseqs2 are you sing? The 14-7e284 release that came out a few days ago doesn't work with geNomad yet. I just fixed the Conda recipe to fix that
wow, thanks! I installed it today, so, yes, I was using 14.7e284. I will change that and see what happens! Thanks again!
No problem! I'll add support for 14.7e284 in the next geNomad release, but it might take some time.
Hi,
I'm trying to run genomad for the first time! I'm using it on a compute cluster but with shared resources, so trying to control memory and threads. I've tried several times, each time adjusting cores and memory resources, and also using the split option you indicated in the manual. But I always end up here:
The above exception was the direct cause of the following exception:
It seems like mmseqs is using 128 threads and I don't know how to contain it. Do you think this is the issue?
Thanks!