-
Notifications
You must be signed in to change notification settings - Fork 5
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
Export support values into extended newick as attributes. #33
Comments
not clear to me why you need the extended one, in the specific case alexis On 22.10.2015 11:42, Tomas Flouri wrote:
Alexandros (Alexis) Stamatakis Research Group Leader, Heidelberg Institute for Theoretical Studies |
I don't know if there is a standard syntax that tree-viewers are able to parse, and how standardized the eNewick notation is. I've noticed that BEAST uses the following syntax to add attributes to nodes:
For example, to set the attributes the syntax BEAST uses is:
This seems to be compatible at least with FigTree. Is this the syntax you have in mind? |
The standard syntax for node labels using your example is: (A:0.1,B:0.2)Node_Label:0.0; see: http://evolution.genetics.washington.edu/phylip/newick_doc.html that's what almost every viewer can digest, we may also just chose to On 22.10.2015 17:34, Tomas Flouri wrote:
Alexandros (Alexis) Stamatakis Research Group Leader, Heidelberg Institute for Theoretical Studies |
Okay, I get what you mean. I'm aware of this format; we're already using it for labeling inner nodes in fastdate. This however allows us to only place a single label to a node (either inner or tip). To place multiple attributes, labels are not sufficient, but could be solved as you say with multiple trees. For now what you suggest will suffice since we only plan to add for each node the frequency it appears as the root of a coalescent process. But later on, with more attributes (confidence intervals for instance) we'll need a better (more generic) solution. |
It seems most editors do not support neither the extended format nor the BEAST format. I reverted back to printing support values only as inner node labels (as Alexis suggested). |
Export the node support values generated from Bayesian runs into a tree into the extended newick format:
[label]#[type]tag[:branch_length]
The text was updated successfully, but these errors were encountered: