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

Fail in processing vogdb #341

Open
ShangLiii opened this issue Apr 1, 2024 · 4 comments
Open

Fail in processing vogdb #341

ShangLiii opened this issue Apr 1, 2024 · 4 comments

Comments

@ShangLiii
Copy link

I tried a lot of times to install dram (v.1.4.6) but failed at the step of vogdb.
the error is "subprocess.SubprocessError(f"The subcommand {' '.join(command)} experienced an error"
Does anyone know what is the problem and how to fix this?
Here is what I have got:

2024-04-01 14:16:54,384 - Processing vogdb
2024-04-01 14:17:24,864 - The subcommand ['hmmpress', '-f', './DRAM_db/vog_latest_hmms.txt'] experienced an error:
Error: File format problem in trying to open HMM file ./DRAM_db/vog_latest_hmms.txt.
File exists, but appears to be empty?

Traceback (most recent call last):
File "/data2/lishang/miniconda3/envs/DRAM/bin/DRAM-setup.py", line 184, in
File "/data2/lishang/miniconda3/envs/DRAM/lib/python3.9/site-packages/mag_annotator/database_processing.py", line 555, in prepare_databases
File "/data2/lishang/miniconda3/envs/DRAM/lib/python3.9/site-packages/mag_annotator/database_processing.py", line 317, in process_vogdb
File "/data2/lishang/miniconda3/envs/DRAM/lib/python3.9/site-packages/mag_annotator/utils.py", line 71, in run_process
raise subprocess.SubprocessError(f"The subcommand {' '.join(command)} experienced an error, see the log for more info.")
subprocess.SubprocessError: The subcommand hmmpress -f ./DRAM_db/vog_latest_hmms.txt experienced an error, see the log for more info.

@yaojian1997
Copy link

I also meet this problem.

@anbadilla
Copy link

I'm facing the same problem when running DRAM through Atlas-Metagenome.

@schmigle
Copy link

See my solution here:
#340

Seems to be linked to a directory structure mismatch

@sahilrishav2
Copy link

I also faced the same issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants