Skip to content

ts: Storing time/generation forward in time #11

@gregorgorjanc

Description

@gregorgorjanc

msprime counts generations/time backwards in time, and I think tskit too, but we should check (I assume that any node sorting based on time would have to follow this logic).

SLiM is simulating forward in time. Is it storing that information into node table, and if so, in what format (negative values to make it consistent with positive values in tskit)? Or is it storing it separately into the top-level metadata?

AlphaSimR is simulating forward in time, but it is not storing anywhere the notion of time really - apart from the notion of generations in pedigree SP$pedigree. However, users often keep track of time - usually in years. @hannesbecher we had some discussion with @gaynorr, but I can not fine that issue/discussion on AlphaSimR anymore. Do you recall where we brainstormed about this?

  • Does tskit assume that time goes backwards in time?
  • How is SLiM storing time and where?

@LynxJinyangii can you explore what tskit and SLiM do? For the later check also pyslim package - that enables you to load SLiM tree sequence into Python and work with it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions