You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After adding the ability to read in a tree sequence and keep the mutations, we have the potential for an incompatibility between features:
exporting a simulation to a trees file and then generating a new population from its mutations will fail because the origin time of the metadata is forwards in time and the time on the treeseq is backwards.
but importing w/o mutations and then adding them as metadata before creating a population works fine if you make the origin time be a backwards time. This works because the forwards origin time is "faked" upon import.
After adding the ability to read in a tree sequence and keep the mutations, we have the potential for an incompatibility between features:
cc @apragsdale
The text was updated successfully, but these errors were encountered: