Skip to content
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

ENH: Adding in hierarchy type #112

Merged
merged 2 commits into from
May 12, 2017
Merged

ENH: Adding in hierarchy type #112

merged 2 commits into from
May 12, 2017

Conversation

mortonjt
Copy link
Contributor

@mortonjt mortonjt commented Apr 8, 2017

This pull request is for introducing another tree data type Hierarchy.

The main motivation behind this is there are other instances of trees other than Phylogeny such as hierarchical clusterings. And using Phylogeny to represent these data types are incredibly misleading. This is critical for reducing confusion for performing analyses with Gneiss, which can operate directly on Phylogeny and Hierarchy types.

@mortonjt
Copy link
Contributor Author

mortonjt commented May 5, 2017

Is there anything else that is required here? This would be really nice for clarifying the semantics for tree types other than phylogenies in the future.

@ebolyen
Copy link
Member

ebolyen commented May 5, 2017

I'm fine with this as written, but we'll need some transformers for it (it looks like your commit history may have gotten backwards, I see the AlphaDiversity stuff).

Anyone else have thoughts here?

@jairideout
Copy link
Member

Just a note that this resolves #99.

@ebolyen
Copy link
Member

ebolyen commented May 12, 2017

Sorry we don't need transformers, I completely forgot how this worked when I wrote that comment.

@ebolyen ebolyen merged commit ec964f1 into qiime2:master May 12, 2017
@mortonjt
Copy link
Contributor Author

mortonjt commented May 12, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants