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
I get the warning: /home/trc468/.conda/envs/snakemake_new/lib/python3.10/site-packages/msprime/ancestry.py:831: TimeUnitsMismatchWarning: The initial_state has time_units=ticks but time is measured in generations in msprime. This may lead to significant discrepancies between the timescales.
Which I am a bit confused about - the SLiM manual indicates to me that ticks and generations are synonymous in a WF model (I did indeed simulate a WF model from SLiM). Is this just a safety warning?
The text was updated successfully, but these errors were encountered:
Yep, just a safety warning! For more info on this, see the docs.
I'll close this, but feel free to re-open if there's an issue here. I suppose one could make the case that in WF models SLiM should make the output time unit "generations" (or, ["ticks", "generations"]?), but this also sounds like a can of worms.
Hey @petrelharp. I suggested that @trevorcousins ought to open this issue, because it seems weird to me that the warning is issued for WF models. If WF models ticks and generations are the same thing, so what, really, is pyslim warning about? And pyslim does know that the tree sequence came from a WF model, right? So, should it really warn in this case?
Hi, I am following the SLiM manual for recapitation, and after doing the command:
I get the warning:
/home/trc468/.conda/envs/snakemake_new/lib/python3.10/site-packages/msprime/ancestry.py:831: TimeUnitsMismatchWarning: The initial_state has time_units=ticks but time is measured in generations in msprime. This may lead to significant discrepancies between the timescales.
Which I am a bit confused about - the SLiM manual indicates to me that ticks and generations are synonymous in a WF model (I did indeed simulate a WF model from SLiM). Is this just a safety warning?
The text was updated successfully, but these errors were encountered: