-
Notifications
You must be signed in to change notification settings - Fork 448
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
Comments
please try again. |
It works and finishes successfully. Thanks. |
Now the tool is still aborting with the following error message: Fatal error: Filename: /data/db/data_managers/plasmidfinder-db/81c11f4_2023_12_04/enterobacteriales.length.b |
@bgruening Looks like there are some missing files in the plasmidfinder db causing the error |
Yes, but why and how should such a directory look like.... |
Or does the tool tries to write into this directory and this is why we get this error ... |
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: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.
I looked into the xml files but could not figure out were these information has been coded. I appreciate if someone can help.
The text was updated successfully, but these errors were encountered: