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

plasmidfinder the specified database directory does not exist! (due to an extra comma) #6810

Open
dadrasarmin opened this issue Feb 27, 2025 · 6 comments

Comments

@dadrasarmin
Copy link

Hi,

there was a report that a user cannot use plasmidfinder on usegalaxy.eu with the built-in database called: "81c11f4_2023_12_04". I could reproduce the error here. I believe it is because of the extra comma (81c11f4_2023_12_04,/data) in the submitted command:

mkdir output_dir && mkdir temp_dir && plasmidfinder.py -i '/data/dnb10/galaxy_db/files/7/0/c/dataset_70c9bbbd-7907-43d2-ac0b-b827bca736f1.dat' -p '/data/db/data_managers/plasmidfinder-db/81c11f4_2023_12_04,/data/db/data_managers/plasmidfinder-db/81c11f4_2023_12_04' -l '0.6' -t '0.95' -mp blastn -x -o output_dir -tmp temp_dir | tee 'XXXX'

the same input fasta file will successfully work with the "2.1_2019_08_28" database. As attached below we can also see that the 2023 database is available twice as an option which I believe is also for that extra comma.

Image

I looked into the xml files but could not figure out were these information has been coded. I appreciate if someone can help.

@bgruening
Copy link
Member

please try again.

@dadrasarmin
Copy link
Author

It works and finishes successfully. Thanks.

@wennj
Copy link

wennj commented Feb 28, 2025

Now the tool is still aborting with the following error message:

Fatal error:
Error: KMA did not run as expected.
KMA finished with the following response:

Filename: /data/db/data_managers/plasmidfinder-db/81c11f4_2023_12_04/enterobacteriales.length.b
Error: 2 (No such file or directory)

https://usegalaxy.eu/u/wennmannj/h/plasmidfinder-error

@dadrasarmin dadrasarmin reopened this Feb 28, 2025
@SaimMomin12
Copy link
Contributor

@bgruening Looks like there are some missing files in the plasmidfinder db causing the error

@bgruening
Copy link
Member

Yes, but why and how should such a directory look like....

@bgruening
Copy link
Member

Or does the tool tries to write into this directory and this is why we get this error ...

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

4 participants