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

Tree branch support #130

Closed
matsen opened this issue Jan 27, 2017 · 5 comments
Closed

Tree branch support #130

matsen opened this issue Jan 27, 2017 · 5 comments

Comments

@matsen
Copy link
Contributor

matsen commented Jan 27, 2017

We have already seen lots of examples from @lauranoges where there is significant homoplasy, meaning that we have some apparent back-mutation.

I don't want to pull the trigger on these right yet, but some things to think about doing.

  1. Apply a consensus tree method to the list of max parsimony trees
  2. Calculate a consistency index or some such to measure this level of back-mutation
  3. Use some network method? I think this is a bad idea but I had to include it.

We should probably do the first, but that's going to make Laura unhappy again because the branch lengths won't be interpretable in terms of level of mutation.

BTW, @lauranoges -- are all of these sequences observed once, or is there some (albeit noisy) measure of frequency?

@lauradoepker
Copy link

Which sequences, @matsen ? And is this referencing the conversation that Megan and I had with @psathyrella this morning?

@psathyrella
Copy link
Contributor

sorry, I can't resist compensating for the emoji in the title not displaying:

the-scream-auction-parody-3-e1336072880184

@matsen
Copy link
Contributor Author

matsen commented Jan 28, 2017

I think the best is to show a single tree, along with either

  1. A consensus tree of all of the MP trees
  2. Branch support of that tree based on the other MP trees

@metasoarous metasoarous assigned metasoarous and unassigned wsdewitt Apr 11, 2017
@metasoarous metasoarous changed the title Sometimes the data ain't treelike 🙀 Tree branch support Apr 11, 2017
@matsen matsen modified the milestone: MB release May 1, 2017
@metasoarous
Copy link
Member

We're putting this on Ice for now, and removing from the MB Release Milestone. It's still something we want to do, but we weren't able to make it in on this iteration, because of the issues that cropped up with prank (#131, #170) and the fact that we were banking on being able to use RaxML for computing support, but that we were depending on prank doing ancestral constructions separately for this. It's possible that we might get dnaml to do this, but I'd rather not wade through that arcana any more than I have to if there's any sliver of hope on the horizon for another method.

@metasoarous metasoarous removed this from the MB release milestone Jul 26, 2017
@metasoarous metasoarous removed their assignment Oct 21, 2018
@matsen
Copy link
Contributor Author

matsen commented May 29, 2019

RAxML does give branch support cheaply, I believe.

In a sense, though, ecgtheow/linearham are there to integrate over the uncertainty we have in the trees, and the display that we have in Olmsted is to give a digestible overview. Thus, I'd suggest closing. @lauradoepker ?

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

No branches or pull requests

5 participants