-
Notifications
You must be signed in to change notification settings - Fork 58
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
improve taxonomy rank indexing #805
Conversation
merged from upstream
Hi @sckott |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please explain the problem in more detail? I'm not sure what problem this is solving.
For the vcr thing, delete the cassette file class2tree_classification_call.yml
, from the command line e.g, like rm tests/fixtures/class2tree_classification_call.yml
or just in rstudio or however. Then re-run tests again, and it should work. (p.s. we're thinking about how to make this easier for contributors to packages that use vcr in tests - ropensci/vcr#145)
@sckott removing the cassette files solved the issue, the test for |
thanks for fixing cassettes for the travis failure, i restarted it, its a server system dependency problem - probably intermittent please answer the above too: Can you please explain the problem in more detail? I'm not sure what problem this is solving. |
I will use this small example to reproduce the issue
This is the result:
So, please notice the position of the norank_1783272. According to the order of the NCBI taxonomy ranks for the first species, this rank must be placed between phylum and superkingdom:
However, the old P.S.: the changes in other functions ( P.P.S.: the travis-ci still failed because of other cassettes, should I also removed them and run the test agains for the whole package? |
Looks good to me, thanks for the fix! |
Description
The previous rank indexing function did not work correctly while sorting the noranks (undefined ranks). This has been fixed now.
Related Issue
Example