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

When workflows are aborted and then recontinued later, check that the database used is still the same... #19

Open
jvollme opened this issue Feb 7, 2022 · 0 comments
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@jvollme
Copy link
Collaborator

jvollme commented Feb 7, 2022

sometimes, when the gtdb databse is updated, it can happen that the representative genome of a species changes.
if a process was started with one database, and then finished with another, it can happen that a query species that was present n the one db-version is not found anymore in the other...

An example is the presence of "GCF_002879875.1_NZ_PNXZ01000140.1" in gtrp_r95 which was replaced with "GCF_007097545.1" in gtdb_r202.

--> for every workflow/intermediate result make a note of the exact database version that was used to create it. return an error if a workflow is being continued with a different db version!

@jvollme jvollme added the bug Something isn't working label Feb 7, 2022
@jvollme jvollme self-assigned this Feb 7, 2022
@jvollme jvollme added the enhancement New feature or request label Feb 8, 2022
@jvollme jvollme changed the title some accessions apparently still missing from lookup table... When workflows are aborted and then recontinued later, check that the database used is still the same... Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant