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
The docs currently say that the order in which admixture pulses were specified is ignored during the comparison. But this shouldn't strictly be the case. If multiple pulses are specified for the same time, then the order in which pulses were defined will matter. Hence the correct thing to do is to (stable)sort pulses by the time field and then compare.
The text was updated successfully, but these errors were encountered:
Actually, it might be more tricky that this... The order of pulses with the same time value only matters when the pulses have demes in common. E.g. for pulse 1: source=A, dest=B, pulse 2: source=B, dest=C, the pulse order matters. But in other cases, e.g. pulse 1: source=A, dest=B, pulse 2: source=X, dest=Y, the order of pulses should be ignored.
The docs currently say that
the order in which admixture pulses were specified
is ignored during the comparison. But this shouldn't strictly be the case. If multiple pulses are specified for the same time, then the order in which pulses were defined will matter. Hence the correct thing to do is to (stable)sort pulses by the time field and then compare.The text was updated successfully, but these errors were encountered: