You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p class="p6">The <span class="s1">Chromosome</span> object which this haplosome represents; for example, if this haplosome represents the X sex chromosome in a particular individual, then this property provides the <span class="s1">Chromosome</span> object that defines the genetic structure of the X sex chromosome in that individual’s species.</p>
<p class="p6">The position index of the haplosome, within the set of haplosomes associated with the <span class="s1">Chromosome</span> object which this haplosome represents.<span class="Apple-converted-space"> </span>For example, if an individual in a multi-chromosome model has two haplosomes that represent a given chromosome within its <span class="s1">haplosomes</span> vector, the first of those haplosomes will have a <span class="s1">chromosomeSubposition</span> value of <span class="s1">0</span>, the second will have a <span class="s1">chromosomeSubposition</span> value of <span class="s1">1</span>.<span class="Apple-converted-space"> </span>For an intrinsically diploid chromosome in individuals generated by a standard biparental cross, the first haplosome (at subposition <span class="s1">0</span>) came from its first parent (the female parent, in sexual models), and the second haplosome (at subposition <span class="s1">1</span>) came from its second parent (the male parent, in sexual models).</p>
<p class="p6">If pedigree tracking is turned on with <span class="s1">initializeSLiMOptions(keepPedigrees=T)</span>, <span class="s1">haplosomePedigreeID</span> is a “semi-unique” non-negative identifier for each haplosome in a simulation, never re-used throughout the duration of the simulation run.<span class="Apple-converted-space"> </span>The <span class="s1">haplosomePedigreeID</span> of a given haplosome will be equal to either <span class="s1">(2*pedigreeID)</span> or <span class="s1">(2*pedigreeID + 1)</span> of the individual that the haplosome belongs to (the former for a first haplosome of the individual, the latter for a second haplosome of the individual if one exists); this invariant relationship is guaranteed.</p>
254
256
<p class="p6">This value is “semi-unique” in the sense that it is shared by <i>all</i> of the first haplosomes of an individual, or by <i>all</i> of the second haplosomes of an individual.<span class="Apple-converted-space"> </span>In a single-chromosome model, a given individual will have just one first haplosome, and perhaps (depending on the chromosome type) one second haplosome, and so the value of <span class="s1">haplosomePedigreeID</span> for each of those haplosomes will be truly unique.<span class="Apple-converted-space"> </span>In a multi-chromosome model, however, an individual has a first haplosome for each chromosome, and perhaps (depending on the chromosome types) a second haplosome for each chromosome.<span class="Apple-converted-space"> </span>In that case, the value of <span class="s1">haplosomePedigreeID</span> is unique in the sense that it is different for each individual, but it is <i>not</i> unique in the sense that it will be shared by other haplosomes within the same individual – shared by all the first haplosomes, or shared by all the second haplosomes.<span class="Apple-converted-space"> </span>This “semi-uniqueness” is intentional; it allows <span class="s1">haplosomePedigreeID</span> to be used as a “key” that associates the haplosomes of an individual across disparate datasets, such as across the different tree sequences for each chromosome that are produced by tree-sequence recording in a multi-chromosome model.<span class="Apple-converted-space"> </span>See sections 1.5.1 and 8.3 for further discussion of multi-chromosome models.</p>
\f4\fs20 \cf2 The position index of the haplosome, within the set of haplosomes associated with the
1572
+
\f3\fs18 Chromosome
1573
+
\f4\fs20 object which this haplosome represents. For example, if an individual in a multi-chromosome model has two haplosomes that represent a given chromosome within its
1574
+
\f3\fs18 haplosomes
1575
+
\f4\fs20 vector, the first of those haplosomes will have a
1576
+
\f3\fs18 chromosomeSubposition
1577
+
\f4\fs20 value of
1578
+
\f3\fs18 0
1579
+
\f4\fs20 , the second will have a
1580
+
\f3\fs18 chromosomeSubposition
1581
+
\f4\fs20 value of
1582
+
\f3\fs18 1
1583
+
\f4\fs20 . For an intrinsically diploid chromosome in individuals generated by a standard biparental cross, the first haplosome (at subposition
1584
+
\f3\fs18 0
1585
+
\f4\fs20 ) came from its first parent (the female parent, in sexual models), and the second haplosome (at subposition
1586
+
\f3\fs18 1
1587
+
\f4\fs20 ) came from its second parent (the male parent, in sexual models).\
Copy file name to clipboardExpand all lines: VERSIONS
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,8 @@ development head (in the master branch):
12
12
write "chromosomes" and "this_chromosome" keys out to provenance as well as metadata (#520)
13
13
fix an annoying autoindent cursor position bug that I suspect is a Qt 6 regression in QPlainTextEdit
14
14
add a define of TSK_TRACE_ERRORS in Xcode for slim and SLiMguiLegacy, in DEBUG only, for easier tskit debugging; break on _tsk_trace_error()
15
-
fix a regression that caused the sourceSubpop pseudo-parameter to be NULL in modifyChild() clabbacks in all cases; add tests, improve documentation (#522)
15
+
fix a regression that caused the sourceSubpop pseudo-parameter to be NULL in modifyChild() callbacks in all cases; add tests, improve documentation (#522)
16
+
add chromosomeSubposition property to Haplosome, providing whether the haplosome is index 0 or 1 within its individual, within the set of haplosomes for its associated chromosome
0 commit comments