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 features added in #764 cause LibraryError due to invalid times.
The issue is probably a complication of the precapitation. We need tests of precapitate/evolve/export to know if this is an issue specific to the dev branch or if it affects the current release for certain work flows. Either way, this will be fixed on 0.16.0 rather than a point release for 0.15.
The text was updated successfully, but these errors were encountered:
Hint to self: this seems to be related to converting the floating-point node times that come from msprime to the integer node times that fwdpy11 requires.
1. If the mutation's node's parent is NULL, choose
the closest int64 <= the node's time.
2. Otherwise, choose a uniform int64 <= the node time and >
the parent node's time.
Fixes#798
molpopgen
changed the title
Error exporting to tskit after adding mutations manually
Error in generating origin times for mutations added "manually" via DiploidPopulation.add_mutation
Jul 12, 2021
0. If the motation's node's time can be represented exactly as
int64, the use that representation as the time.
1. If the mutation's node's parent is NULL, choose
the closest int64 <= the node's time.
2. Otherwise, choose a uniform int64 <= the node time and >
the parent node's time.
Fixes#798
0. If the motation's node's time can be represented exactly as
int64, the use that representation as the time.
1. If the mutation's node's parent is NULL, choose
the closest int64 <= the node's time.
2. Otherwise, choose a uniform int64 <= the node time and >
the parent node's time.
3. Add new tests to tests/test_add_mutation.py
tests/test_selective_sweeps.py
Fixes#798
The features added in #764 cause LibraryError due to invalid times.
The issue is probably a complication of the precapitation. We need tests of precapitate/evolve/export to know if this is an issue specific to the dev branch or if it affects the current release for certain work flows. Either way, this will be fixed on 0.16.0 rather than a point release for 0.15.
The text was updated successfully, but these errors were encountered: