Explanatory illustrations #22
Replies: 1 comment 5 replies
-
For fig 1 I have the "milk-bottles"-like image which shows not only the pedigree but also the series of cell divisions within individuals, which is, of course, more fundamental. The nice thing about this is that the RE and CA nodes are necessarily different. The bad thing is that it it one level too deep, since in our definitions we refer to an individual without distinguishing the pattern of coalescences within an individual (these are normally compressed into a single node). Here's the image I'm talking about (I have the original in SVG form): The image in the recent Nielsen paper (https://www.biorxiv.org/content/10.1101/2021.11.15.468686v1 fig 1, esp fig 1A) also springs to mind. |
Beta Was this translation helpful? Give feedback.
-
The current draft has two placeholder figures, with the following captions:
and
I initially started with having one figure to explain all of this, but then decided that it was probably too much and would end up being confusing. So, there's two figures now:
The Pedigree and the ARG
The ARG is embedded within the pedigree, but there is some nuance which means it's misleading to say that the ARG is a subset of the pedigree:
So, terminology wise, we're following Mathieson and Scally in that we're defining the unqualified term "ARG" as just the graph (nodes and edges) that is embedded within the pedigree.
For this figure I'd imagined showing a simple pedigree and how the ARG is emdedded within it. It's not obvious whether this should be one figure showing everything or two panels, one showing the pedigree and one the ARG. Whatever's most effective I think.
ARG annotations
This figure shows that the graph stucture (under the mathematical understanding of the term, a set of nodes and edges) is not sufficient to encode the local tree relationships along the genome. We need to add some "annotations" to the graph in order to do this. The classical approach is to add a breakpoint to each RE node, and is shown in panel (A). We can equivalently add annotations to the edges (B). We discuss this in detail in the text, and note the generality and computational advantages we get from working with edge annotated ARGs.
In a way, this figure is the most important in the paper, as this is the central message we want to convey. Perhaps we should also add an illustration of the work that's required to generate trees or something?
@hyanwong, do you have anything lying around that'll get us started on these two figures? Should we keep it as two figures or join the two described here into one multi-panel figure?
Beta Was this translation helpful? Give feedback.
All reactions