Should time parameter (add_individual) of parent and offspring be set to 1 and 0? #551
-
When using |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
No, the time in tsinfer is not measured in generations, sorry. In general, there is no standard meaning of time in a tree sequence - it depends on how it was created. For tree sequence created from tsinfer, the "time" ranges from 0 to 1, and simply measures the frequency of the focal derived allele. For tsinfer we assume that all input genomes are "samples" and not internal nodes (i.e. they are not the ancestors of other individuals in the tree sequence, although something that does indeed happen. We haven't thought much about how to incorporate knowledge of the pedigree into the inference process. It should probably work just treating them as samples, all at time 0, but caveat emptor. To turn the dates from tsinfer into something meaningful, you'll need to date the tree sequence, e.g. using tsdate. Note that the dates for coalescence times are likely to be many orders of magnitude larger than single generations. E.g. the average coalescent time of two alleles from the same individual is of the order of thousands of generations (hundreds of thousands of years) |
Beta Was this translation helpful? Give feedback.
No, the time in tsinfer is not measured in generations, sorry.
In general, there is no standard meaning of time in a tree sequence - it depends on how it was created. For tree sequence created from tsinfer, the "time" ranges from 0 to 1, and simply measures the frequency of the focal derived allele.
For tsinfer we assume that all input genomes are "samples" and not internal nodes (i.e. they are not the ancestors of other individuals in the tree sequence, although something that does indeed happen.
We haven't thought much about how to incorporate knowledge of the pedigree into the inference process. It should probably work just treating them as samples, all at time 0, but caveat emptor.
To…