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
Since NCBI taxonomy evolves over time (e.g.), it's possible that the NCBI taxonomy at the time that the index workflow is run will differ from that that was used in whatever kraken database is being pulled in the index workflow.
How I'd imagine handling this would be to do something like: make sure we're using a GenBank release that is compatible with whatever RefSeq release is used in the Kraken database, and then make sure that we have the correct NCBI taxonomy dump for these releases.
Alternatively, there are probably ways to determine what the changes are, but it might not be easy to figure out what to do with the differences.
@willbradshaw , can you say something as to how discrepancies are/aren't handled currently?
The text was updated successfully, but these errors were encountered:
I think this is essentially a documentation question, rather than a pipeline feature per se. It's up to the user generating the index to make sure that the versions of the various resources they're pulling in are compatible. I agree that the documentation should reflect this, though.
Since NCBI taxonomy evolves over time (e.g.), it's possible that the NCBI taxonomy at the time that the index workflow is run will differ from that that was used in whatever kraken database is being pulled in the index workflow.
How I'd imagine handling this would be to do something like: make sure we're using a GenBank release that is compatible with whatever RefSeq release is used in the Kraken database, and then make sure that we have the correct NCBI taxonomy dump for these releases.
Alternatively, there are probably ways to determine what the changes are, but it might not be easy to figure out what to do with the differences.
@willbradshaw , can you say something as to how discrepancies are/aren't handled currently?
The text was updated successfully, but these errors were encountered: