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
When a graph has its minimal end_time > 0, export to tskit will
still shift all node times such that they are 0.0 in that format.
This behavior is not great and can complicate some downstream work.
The export function already takes an optional demes graph as input.
We should check if it is not None, check the minimal end time,
and use that value as an offset for all exported node times.
sequence that has alive node times all > 0.0.
* manual: remove documentation on allowing > 1 ModelParams exported to
tskit.
* remove test of multiple modelparam export
See #1257 and #1256Fixes#1253
sequence that has alive node times all > 0.0.
* manual: remove documentation on allowing > 1 ModelParams exported to
tskit.
* remove test of multiple modelparam export
See #1257 and #1256Fixes#1253
sequence that has alive node times all > 0.0.
* manual: remove documentation on allowing > 1 ModelParams exported to
tskit.
* remove test of multiple modelparam export
See #1257 and #1256Fixes#1253
end at times > 0. (#1255)
* manual: remove documentation on allowing > 1 ModelParams exported to
tskit.
* remove test of multiple modelparam export
See #1257 and #1256Fixes#1253
When a graph has its minimal end_time > 0, export to tskit will
still shift all node times such that they are 0.0 in that format.
This behavior is not great and can complicate some downstream work.
The export function already takes an optional demes graph as input.
We should check if it is not None, check the minimal end time,
and use that value as an offset for all exported node times.
cc @apragsdale
The text was updated successfully, but these errors were encountered: