Hi Alice,
as the error message states, RAxML is expecting to read a
strictly bifurcating tree. Could you check whether this is the
case, for example using Geneious or some other tree viewer?!
If you just change the problematic "," into ")", you are changing the tree topology, which is probably not want to want. One way to resolve this is to infer a new tree (for example, using RAxML). How did you obtain your tree in the first place?
Cheers
Lucas
To unsubscribe from this group and stop receiving emails from it, send an email to raxml+un...@googlegroups.com.
Hi Alice,
thanks, there is the issue - the tree is indeed not bifurcating. "Bifurcating" means, each node splits exactly into two child nodes (see also https://en.wikipedia.org/wiki/Phylogenetic_tree#Bifurcating_tree). In other words, your tree contains polytomies. When working with Maximum Likelihood methods (like RAxML EPA does), the trees usually have to be bifurcating (no polytomies). So that means, in order to run EPA, you first need to infer a bifurcating tree.
Hope that helps, so long
Lucas
Hi Alice,
that sounds great; glad it worked out.
I'm not entirely sure, but it sounds like you are mixing up a couple of things here:
In summary, the likelihood weights can be seen as a probability
distribution of placement positions for a query on the branches of
the tree.
Does that make sense to you?
Lucas
For more options, visit https://groups.google.com/d/optout.
Hi hi,
yep, the tree you posted indeed just shows unique branch numbers, no bootstrap supports or likelihood weights.
The jplace file is not a tree, but contains it, followed by the placement data - you can simply open it in a text editor and have a look, if you want ;-)
I guess you want to show bootstrap values of the reference tree,
right? (As opposed to bootstrap support for the query sequences -
this would be a totally different problem)
In this case, obtaining those bootstrap values can be done
independently of the placements. Just use your original alignment
and call RAxML so that it calculates a bootstrap tree (see the
RAxML manual for details on how to do that).
Then, you get a tree that has bootstrap support values for the inner branches. Use this tree as a reference tree for EPA (I'm afraid you have to re-run it, unless your current reference tree already has bootstrap support values. If so, read on).
Finally, you end up with a reference tree with bootstrap values, and the placement files (labelled tree and jplace file), which do not have the bootstrap values. So, you need to combine those trees.
We had exactly this issue a couple of weeks ago in the gooogle
group, see
https://groups.google.com/forum/#!topic/raxml/V7ZS5dhffgQ
I proposed to use a custom tool for this, which you find here:
http://doc.genesis-lib.org/demos_labelled_tree.html
Let me know if this is what you want to achieve.
Lucas
Nice! Let me know if you have any trouble running it!
Lucas
Hi Alice,
are you observing polytomies only at the new branches that are added for the query sequences, or does the underlying reference tree suddenly have them?
In the first case, this is one of two ways of adding query sequences as new branches. See here for details: http://doc.genesis-lib.org/namespacegenesis_1_1placement.html#af6874a6171b7665adedce46c8ffb55a4
In the documentation of the program, it is also mentioned how to change this to the second kind of behaviour, see http://doc.genesis-lib.org/demos_labelled_tree.html
If however the second is the case, i.e., you are suddenly getting polytomies in your reference sequences, then something went wrong. In that case, please send me your files so that I can investigate.
Cheers and have a nice weekend
Lucas
Well, that depends on what you want to show with those
placements. I chose to merge all queries per branch into a
polytomy for two reasons:
If you instead want to fully resolve them into single branches, like pplacer guppy does, the tree will be a bit more crowded and collapsing is not that easy any more. Your choice. See the two links for details and for how to change the behaviour.
Lucas