Replies: 1 comment 9 replies
-
If by "genotypes" you're referred to nucleotide sequences, such as in VCF, then yes, you could get a mutation at the same site to the same nucleotide coming from both processes, and appearing the same, I think. But mutational lineages are treated separately in the tree sequence, and so at that level you'd be able to tell the difference between the two mutations. Exporting to nucleotide sequences, such as VCF, is lossy, and loses ancestry information including this distinction between different mutational lineages, "flattening" all of that information into a simple nucleotide sequence. If you don't want that to happen, don't work at the nucleotide sequence level, work at the tree sequence level. :-> |
Beta Was this translation helpful? Give feedback.
-
With the default settings of slim and pyslim, I'm assuming that the generated sequence data doesn't distinguish between a mutation with a nonzero selection coefficient introduced in a slim simulation and a neutral mutation introduced at the same site from the neutral coalescent recapitation in pyslim?
Specifically, suppose I have a three population model with no migration with a genealogy (C,(B,A)). If I introduce a beneficial mutation at a random site in an A genome (after its split with B) and it undergoes a complete selective sweep, I should have a configuration 1,0,0 for the frequency of the variant allele in population A,B,C. However, for a small number of replicates, I get a nonzero frequency of the variant allele in populations B or C. The only explanation I can think of is that a neutral mutation is introduced in population B or C (or their common ancestor) at the same site as the beneficial mutation in A, and since by default all sites are either "0" wildtype or "1" variant, the genotypes generated don't distinguish between the variant introduced in slim and a variant introduced at the same site (in another propulation) by pyslim. Is this correct?
Beta Was this translation helpful? Give feedback.
All reactions