Closed haleyhallowell closed 1 year ago
Hi @haleyhallowell. I don't think I've seen this error before. Do you still get it if you remove short sequences? Could you share the input with me?
Hey! Sure, I can share with you; it is attached! I'm currently waiting on another run to go through the HPC queue. I noticed that when i used pip install genomad
that i had to manually install prodigal-gv
and mmseqs2
, so i made a new environment using a conda install. ill update you once that goes through!
final_vOTUs_numbered.txt.zip
Not sure on the short sequences, nothing should be that short as i filter out <2000bp
Hi! Just wanted to let you know i got it working -- seems like it was the weird install with pip i mentioned above that made it throw this error. Conda install the second time got it working. Thanks!
Thanks for letting me know! I'll close the issue.
Maybe it was a problem with the MMseqs2 version? The latest versions of geNomad are only compatible with version 14-7e284
.
Hello! I am currently trying to utilize the
genomad annotate
module to annotate a .fna file of Megahit assembled contigs. After downloading the database and attaching a unique identifier to each .fna headline (because they all started with k127), i ran the following command:genomad annotate final_vOTUs_numbered.fna ./genomad_output ./genomad_db
I get this error directly from genomad:
Here is the output from mmseqs2:
the .fna file, the
genomad_output
directory and thegenomad_db
directory are all in the same directory, and i am running the command from that directory as well. Any ideas how to fix this? Thanks!!