Closed kingaa closed 1 month ago
Actually, all trees are parsed incorrectly: the root edge is not correctly decoded. This is fixed (both bugs) and pushed here (under v. 5.8-0.2). Thanks for the report. Emmanuel
Brilliant! That seems to have resolved the issue! Thanks so much @emmanuelparadis !
The following examples with a single tip but several nodes seem to give incorrect results. . This may be a similar issue to #104, but the fix of that issue did not resolve this one.
Running the above, I get
So the first (3-node) tree is parsed correctly, but the second and third are parsed incorrectly.