Closed zachary-foster closed 7 years ago
fixed no. 1 above, sorry, had originally assigned input hierarchies to a variable called taxa, but then removed it.
No, probably don't need to store edgelists
and graph
variables
I changed the internal method unique_taxa
to get_unique_taxa
, but didn't change uniqtaxa
, but you can change it
Ok, sounds good. I will pull your changes and merge them with mine before submitting a PR.
It seems like this has been addressed by the recent PR
agree
Hi @sckott, nice work with the
taxonomy
class! I am looking through the code and trying to figure a few things out:taxa
variable. It results inno. hierarchies: 0
when the print method is used.edgelists
andgraph
variables? They seem redundant to me and would require recalculation every time a change is made.make_graph
could be used in the print method directly instead ofgraph
. The contents ofedgelists
could be inferred fromedgelist
, except for multiple instances of the same edge list, but if users are interested in that they should usehierarchies
ortaxmap
(with a column for taxon counts).uniqtaxa
taxa
or changing the private functionunique_taxa
to something likeget_unique_taxa
, so that the public variable can beunique_taxa
?I am going to play with it on a new branch and submit a PR if I come up with anything good.