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
Some of the ugliness we currently have has to do with preserving the reference sequence, which recall is stored as a separate column in the kastore. However, if it was just top-level metadata, then we'd get it passed around for free, and we could get rid of a number of ugly things, for instance, the need for a wrapper on simplify. However, this would require a change in how SLiM writes it out as well.
However, maybe we're just going to put support for reference sequences into tskit; if so, we should just wait for that. If not, we should definitely move it to metadata.
The text was updated successfully, but these errors were encountered:
Some of the ugliness we currently have has to do with preserving the reference sequence, which recall is stored as a separate column in the kastore. However, if it was just top-level metadata, then we'd get it passed around for free, and we could get rid of a number of ugly things, for instance, the need for a wrapper on simplify. However, this would require a change in how SLiM writes it out as well.
However, maybe we're just going to put support for reference sequences into tskit; if so, we should just wait for that. If not, we should definitely move it to metadata.
The text was updated successfully, but these errors were encountered: