The bug reported by Alastair is now fixed. This required to change some
C code, and so the whole package needs to be recompiled (this will be in
the next release of ape). The svn has been updated.
For developers, the code in src/tree_build.c has been slightly improved
at this occasion and it
Alastair,
That's indeed the correct work-around. The is because a different code
is used whether the NEXUS file has a TRANSLATE block or not. I'll fix
the bug very soon.
Cheers,
Emmanuel
PS: thanks for the tip on using Figtree.
Alastair Potts wrote on 24/02/2011 14:57:
Hi All,
I think I
Hi All,
I'm sure I've had this problem before and found a way to fix it. I've
spent an hour looking for the solution, but can't seem to find it.
In short, I've run a bootstrap analysis in PAUP* which provided a
consensus tree with bootstrap values. This tree opens fine in FigTree. I
read it
Hi Alastair,
I copied the Newick string below into R, read it with read.tree, and
this seems to work as normal.
I also tried to do the same with Figtree: the tree and its tip labels
are OK, but the node labels are not (eg, it displays 377 for the root
instead of 100). My guess is that it's
Hi Emmanuel,
I can read in the tree fine using read.nexus too (I've attached the file
this time).
When in FigTree, if you leave the Node Labels display at 'Node Heights',
then you will see 377 at the root of the tree. If you change this
setting to 'label', you will see that the bootstrap
Hi All,
I think I have located the problem. As usual I had experienced it before
and I found (or someone else found) a workaround - but I couldn't
remember it.
The bootstrap values ($node.label) is mixed up when I save the bootstrap
tree as a nexus file with a translation table in PAUP (this
