Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VIBRANT error: could not identify KEGG HMM files in database directory. Please run VIBRANT_setup.py. #35

Closed
BikramDroid opened this issue Dec 14, 2020 · 9 comments
Labels
bug Something isn't working

Comments

@BikramDroid
Copy link

Getting below error every time I try to run any file from example_data folder
VIBRANT error: could not identify KEGG HMM files in database directory. Please run VIBRANT_setup.py.

Please note below setup command was successful,

_python VIBRANT_setup.py -test

Verifying correct dependency versions ...
Logger started. Check log file for messages and errors.

VIBRANT v1.2.1 is good to go!
See example_data/ for quick test files._

I'm running it on macOS 11.0.1 with python 3.7 and all dependencies installed as per the mentioned steps.

@BikramDroid
Copy link
Author

@KrisKieft
Any help appreciated

@KrisKieft
Copy link
Member

Hi,

I do not believe I have seen this issue before with a successful setup. There are two questions that I can ask to start with. (1) are there any error messages in the setup log file (see databases folder) or (2) do you see pressed HMM files in the databases folder? Pressed HMM files will end in .h3f, .h3i, .h3m and .h3p. It's likely that you downloaded the databases but they were unable to be pressed for some reason. If you do not see the pressed files then type in hmmpress -h and let me know if you get an error or a help message. If you do see the pressed files let me know and I'll try to figure out a different solution.

Kris

@BikramDroid
Copy link
Author

Hi,
Thanks for the quick reply, below are the answers

Q1:
Complete set of messages in the setup log file, no errors

This script will download, extract subsets and press HMM profiles for VIBRANT.
This process will require ~20GB of temporary free storage space, but the final size requirement is ~11GB in the form of pressed HMM databases.
Please be patient. This only needs to be run once and will take a few minutes.

Verifying Pfam, KEGG and VOG source websites are available for download ...

Downloading HMM profiles for Pfam, KEGG and VOG from their source websites ...

Unzipping profiles ...

Concatenating individual profiles ...

Extracting profiles used for VIBRANT ...

Retrieved 19182 HMMs.

Retrieved 10033 HMMs.

Pressing profiles used for VIBRANT ...

Done with databases. Several new databases are now in this folder.

Verying correct dependency versions ...

VIBRANT v1.2.1 is good to go!
See example_data/ for quick test files.

  1. hmmpress-h command results in databases folder

Screenshot 2020-12-15 at 10 54 30

And I can only see .h3i files in that folder and no file ending with h3p/h3m/h3f. Below are the only files in databases folder and after setup completed.

Screenshot 2020-12-15 at 10 57 20

@KrisKieft
Copy link
Member

It looks like we found the problem, we now need to figure out how to resolve it. Since there are no h3p/h3m/h3f files it means the databases were not pressed correctly/fully. My first guess is that your machine may have ran out of memory (RAM), but I'm not entirely sure.

It's possible that we can finish the setup manually. First, remove the existing files ending in ".h3i" (just the 3 files). Retain all of the other .HMM files. Then, run the command hmmpress KEGG_profiles_prokaryotes.HMM. It's likely that you'll receive an error, but we need to know what that error is (pressing may take a couple minutes).

The image below is the successful output for pressing the HMMs. If you get an error please let me know what it says. If you get a successful prompt then go ahead and run hmmpress VOGDB94_phage.HMM and hmmpress Pfam-A_v32.HMM.

image

@BikramDroid
Copy link
Author

Thank you very much.
Manual hmmpress on all .HMM files did the work, now all files are there and I'm able to run through example data.
Output is also OK.

Maybe some compatibility problem with different dependencies and this might be helpful to others who get such issue.

Thanks again and have a great festive season ahead.

@KrisKieft
Copy link
Member

Wonderful, I'm happy to hear this worked. I'll dig a little deeper to see if this is a solvable issue to be implemented in a new version. Happy holidays.

@KrisKieft KrisKieft added the bug Something isn't working label Dec 18, 2020
@WDPLA
Copy link

WDPLA commented Jan 26, 2024

Same problem, solved! Thanks to KrisKieft so much! By the way, to everyone with the same problem. Do not run "VIBRANT_setup.py" after running HMMPRESS, or those newly created files will be erased.

@lexikazen
Copy link

Here as well! HMMPRESS needs to be run on the KEGG, VOG, and PFAM HMM files and then it seems to be ok!

@Jlee795
Copy link

Jlee795 commented Feb 28, 2024

Hello, I did this and mine is not working. I am still getting the same error VIBRANT error: could not identify KEGG HMM files in database directory. Please run VIBRANT_setup.py.

I'm not sure what to do to sort it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants