-
Notifications
You must be signed in to change notification settings - Fork 12
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
merge binomen into this package #12
Comments
i'm waiting on this until major changes are merged in in https://github.com/ropenscilabs/taxa/tree/issue-9 |
Ok. The only thing that perhaps should get done is adding examples to the documentation for |
Right on the examples, but most of your changes are not on master branch right? So I want to merge those in before merging together with for examples happy to add some, but again, would be nice to merge in your changes first. can you send PR soon? |
Oh yea, its ready to merge. I assumed you would make the changes on the issue-9 branch, but a PR makes more sense. I will send it now |
thanks, i wasn't sure which branch was the most recent |
i'm going to ask CRAN to archive -- scratch that - forget that we were going to rename pkg to |
Thanks for the update |
working on branch |
so far just pop, and only supporting Hierarchy objects right now
@zachary-foster What do you think? See |
oh, and install from |
Cool, I will look at this later today |
thx |
Looks good. Perhaps rename to something that mentioned rank? Like It would be cool if we could do something like When I was looking at this, I thought we might be able to add an abstracted version as well that can filter by taxon name and taxon ids or any other information we can derive from the class. We might be able to reuse a lot of code from
For example: filter_taxa(hier_obj, ranks == "species", ids %in% c(123, 456)) We could also add |
Thinking about this more, the filter_taxa syntax could be apllied to all of the classes with multiple taxa like 'taxa' 'hierarchy' 'hierarchies' and 'taxonomy'. All of the NSE code can be reused and having a 'get_data' method for each class would make converting class info to tables a simple wrapper over get_data |
that sounds good, though we'll probably only be able to do a subset of operations with names and ids since there's no ordering to them
this is the operation Will have a look at |
from #6
The text was updated successfully, but these errors were encountered: