-
Notifications
You must be signed in to change notification settings - Fork 0
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
update_databases fails #18
Comments
I called by accident the module instead of the conf object. Fixed it - sorry for that. But there is a problem with the higher blast version now - which has no update_blastdb function anymore - just the perl script which I cannot call from within python. Will work on a fix. |
Ok, looks like it is fixed. Blast version > 2.9 needs update_blastdb.pl instead. It might need some more cpan and json modules for linux installed to get it to run... |
I am still getting the same error. Was this supposed to be fixed? I have |
You get the same error when running update_databases.py? Did you pull the newest version? It is updating the databases currently on my end. The update of the blast database will only happen if your database is older than 90 days (made more explicit in the wiki now). Added the |
Yes, I have pulled and am up-to-date and still get a similar error:
Is there an additional step I need to do after pulling? |
Fixed. Nothing else to do. There was an error in the class assignment - which I did not encounter before. |
Eep still not working for me :( Too many arguments?
|
Do you need further information to diagnose my problem? I cannot see where |
No, sorry for the delay. I was moving to a different place and wanted to make sure things are really working this time. (I havent updated my blast db again - but the rest was working now for me) |
I have set my
data/localblast.config
to point to my database (which it seems to find), but when I try to run the database updater I get the following error:I cannot figure out what is going wrong. Is it looking for
./data/names.dmp
or something else?The text was updated successfully, but these errors were encountered: