Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation: confusion between pedigree and genetic ancestry? #126

Open
hyanwong opened this issue Jan 18, 2021 · 3 comments
Open

Documentation: confusion between pedigree and genetic ancestry? #126

hyanwong opened this issue Jan 18, 2021 · 3 comments

Comments

@hyanwong
Copy link
Member

hyanwong commented Jan 18, 2021

In the intro part of the documentation, lots of the explanation about removing individuals discusses the pedigreegenealogy. But I usually take the word genealogy to mean the pedigree rather than the genetic ancestry. E.g. if the example were to be simulated in SLiM with a 0 recombination rate, wouldn't a lot more of the nodes be removed?. for this reason, I find find it a bit odd to use the term "genealogical", and the diagram not entirely clear on the distinction.

@hyanwong
Copy link
Member Author

For example, instead of

SLiM can read and write tree sequences, which store genealogical data of entire populations. These can be used to efficiently store both the state of the population at various points during a simulation as well as its genealogical history. Furthermore, SLiM can “load” a saved tree sequence file to recreate the exact state of the population at the time it was saved. To do this, SLiM has added several additional types of information to the basic tree sequence file.

could we say

SLiM can read and write tree sequences, which store the genetic ancestry of entire populations. These can be used to efficiently store both the state of the population at various points during a simulation as well as its full genetic history. Furthermore, SLiM can “load” a saved tree sequence file to recreate the exact state of the population at the time it was saved. To do this, SLiM has added several additional types of information to the basic tree sequence file.

@petrelharp
Copy link
Contributor

Good point, but saying "genetic history" doesn't necessarily connote that we're recording actual genealogical relationships (although not necessarily all of them, as you say). For instance, a new arrival might read "genetic history" to mean that, like, we're recording which of some ancestral populations everyone is descended from. That's why I've gone with "genealogical", as I think its more precise as to what we're actually doing. (And, as written it says it stores "genealogical data", but does not say it stores all the genealogical data.)

I'm sure I've not said things in the best possible way, so suggestions welcome! But this one isn't doing it for me...

@hyanwong
Copy link
Member Author

It's all tricky stuff! I guess we could also use "inheritance" or something. Or genetic (or "gene") genealogy? Perhaps we should put it in a google doc and then we can both edit it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants