-
Notifications
You must be signed in to change notification settings - Fork 80
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
Genbank downloading problems #2179
Comments
Hi sourmash creators! Thanks a lot for your work! I am having the exact same problem as being described above. Thanks in advance! Gabri |
hi! sorry about this, it's been difficult to find good places to store these files ;(. these problems occur when using the dweb.link URLs at https://sourmash.readthedocs.io/en/latest/databases.html, right? If so there are some options discussed here but it is not simple at the moment... I'll see if I can document it more clearly today. |
yes -- they've been plaguing me for days. another potential alternative -- the OSF links are super fast. are you trying to move away from google drive to OSF for the large files? in the short term can we update the documentation so that it downloads from the links on OSF until we fix the dweb links? |
some solutions while we don't move everything to R2: remove
with the cloudflare gateway:
with
|
Hello! I am pleased to report that our databases may now be Robustly Available via the local UC Davis infrastructure of the dib-lab ;). Please see #2255 for the PR; you can view the databases file directly here until that PR is merged, at which point it will show up here. I will update this issue once the PR is merged (which should be fairly quickly). 🎉 |
Merged & docs updated: prepared databases page here now has robustified farm links. |
I'm having difficulties to download Genbank databases. I was able to download GTDB, and Genbank viral k31. Is there any other place I can find these files? Please suggest how I can download them. I use curl and usually i get this error: curl: (33) HTTP server doesn't seem to support byte ranges, or just time out.
The text was updated successfully, but these errors were encountered: