I just
pushed
a small fix to fastBM for cases in which the input trees are
not in "cladewise" order. Since re-ordering is very fast, the
fix first checks to see if the current order is "cladewise" (or
if no order attribute is specified), and if not, reorders the tree's edges in
a clade-wise fashion.
This bug was identified by Josselin Cornuault. Thanks!
No comments:
Post a Comment
Note: due to the very large amount of spam, all comments are now automatically submitted for moderation.