Bugs in ancestral output order
lamthuy opened this issue · comments
lamthuy commented
Andrew Rambaut commented
Thanks for noticing this. I propose fixing this by changing the ancestral output to follow the order given by the tree (1,2,0
) as this is less likely to break other things.