You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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
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!
The text was updated successfully, but these errors were encountered: