-
Notifications
You must be signed in to change notification settings - Fork 8
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
Provide commands to create database file [Feature Request] #45
Comments
It might just be that particular genome being used during testing is not in the database (I'm not 100%) sure, so at least instructions would indeed be helpful :) |
I could make a small db for testting yeah.. the thing is that the database versions are tied to a gunc version so opening it up for users to make their own database might cause confusion. maybe it would be fine, i dont know tbh. I could add a small test db in the next version release.. would an addition |
Thanks for looking into this @fullama ! For clarity, the purpose for me (and I guess @chrisgulvik ) is not to allow users to make a custom database - a small test DB would indeed suffice. A small database that is compatible with the standard gunc commands rather than a specific So a separate |
OK no prob.. ive added it to the milestones for the next release.. ill update here when its ready |
Can you provide example commands to create a database?
I'd like to make a super small db for built-in functionality testing of the software within a container. For example, just adding 2 different species genomes (perhaps just 1 Gram Pos here and 1 Gram Neg here) and querying with 1 of them. This would also speed up any dev work you do and make GitHub Actions a possibility for you. Nothing fancy needed for commands to share, just notes in shell would be helpful.
If you added an example on how to create a GTDB database, that would also take the workload off of you, ensure future utility of the pkg as taxonomy continues to change, and avoid future issues like #40 and #43 .
The text was updated successfully, but these errors were encountered: