Mitochondrial
William R. Hurst
Abstract
Long neglected by scientists and
mostly excluded from their phylogenetic trees, the variants at positions 00514-00524
in mitochondrial
Address for correspondence: wrhurst_17@msn.com. W. R. Hurst is the Administrator of the
Haplogroup K Project.
Received:
Introduction
This
study began as an investigation of the variants at mitochondrial
The goal
in the present study is to rectify the past neglect of these interesting mutations
by (1) studying the added resolution that they bring to one mtDNA
haplogroup–Haplogroup K, (2) looking at the few scientific papers that focused
on them, (3) looking at their role in the mtDNA tree in general, and (4)
summarizing what has been learned.
Suggestions for future research will follow.
Nomenclature
The first
large hurdle that must be dealt with is nomenclature. The
Family
Tree
Another
nomenclature factor is that the sequence 514-524 is part of the original HVR3 (aka HVS-
References
will be made below to sequences in FTDNA’s MitoSearch
database, the mtDNA Haplogroup K Project (which included 321 high-resolution
HVR1+HVR2 sequences as of July 23, 2007), and the federal GenBank
database. In MitoSearch, sequences are
always labeled as just K, while in the K Project about 10% of the total
sequences or 14% of the high-resolution sequences have confirmed subclade (also
called subhaplogroup) designations based on
full-sequence tests. GenBank sequences
vary in how they are labeled, based on their origin. Most subclade designations are those from
Behar et al. (2006, Fig. 1), referred to below as the “Behar K tree.” Subclade
designations of sequences not confirmed by full-sequence tests are as predicted
by the author. Additional provisional
subclade designations used in this article are those of the author and may
change when a new authoritative K tree is published.
Definitions
Mutations
Mitochondrial
Heteroplasmy
The
phenomenon of different mtDNA variants being found in different mitochondria or
in different cells in the same person is known as heteroplasmy. Point heteroplasmy (or structural heteroplasmy) is the term used when different SNP
variants are found in a cell. Length heteroplasmy is the occurrence of
any mixture of a
Strictly
speaking, when the term heteroplasmic
mutation is used, or when heteroplasmy is used as a noun, what is usually
meant is a situation where two or more variants for the same position are
detected by an mtDNA test. Where the
heteroplasmy is due to SNP variants, there is a set of IUPAC (International
Union of Pure and Applied Chemistry) codes; 16093Y, for example, would mean
that both the mutated version 16093C and the
Heteroplasmy
and heteroplasmic mutation are often used more loosely to explain why certain
mutations, SNPs or indels, occur by the inheritance of different variants
between generations. Apparently, even if
the mutated variant is not detected in the mother, by the normal ra
Perhaps
there was an intermediate step where, using the strict definition of a
heteroplasmic mutation, both variants were detectable. The key word here is “detectable,” since
those heteroplasmies that are not detectable by the direct sequencing method
commonly used by testing companies – which would require perhaps 20% for the
minority variant to be observed – may be
detectable at 5% by other methods (Tully et al. 2000). In fact, detection of heteroplasmies as low
as 1-2% has a special name: microheteroplasmy (Smigrodzki and Khan, 2005).
The Behar
K tree demonstrates the problem which the effects of undetectable heteroplasmy
cause with trees created with software such as Fluxus-Engineering’s
Network program. To prevent
reticulations caused by heteroplasmic and other recurrent mutations, Behar
excluded our 524 insertions as well as the positions 309 and 315 insertions and
certain other HVR and coding-region mutations.
And yet, there are patterns involving position 524 in the K
subclades. The 524 insertions are found
in certain subclades, but not in others; and likewise the deletions. These patterns will be discussed in detail
for each subclade below. Even adding
them back to the data used for the Fluxus diagram
does not always explain the appearances of the 524 indels. Turner (2006) expressed the situation well in
the title of an article in this Journal: “Now You See It, Now You Don’t:
Heteroplasmy in Mitochondrial
We see
that a mutation reported for a person may have occurred in two general ways;
(1) by a de novo mutation similar to
a nuclear
In the
context of heteroplasmy, the term “fixed” means that only one heteroplasmic
variant is inherited by the founder of a subclade. If a different variant appears later in that
subclade or a lower subclade, it may be assumed that there has been a de novo mutation. “Fixed out” means that a particular variant
is missing from the group of inherited variants. If that variant later appears in that
subclade or one of its descendant subclades, it again may be assumed that there
has been a de novo mutation. Tully et al. (2000) has some discussion of
the term “fixed.” A related term is “resolved.”
If a woman with a strict heteroplasmy (two or more variants detectable)
has a descendant with only one variant detectable, the position is said to be
resolved at that variant. A progression
over many generations might be (1) a woman with only the T or
Haplogroup
Notation
For any
mtDNA haplogroup, there are often several levels of subclades or
subhaplogroups. For this article, the
major or high-level K subclades are K1, K1a, K1b, K1c and
Points of Conundrum
For this
article the term points of conundrum will
be used for certain branching points on the K phylogenetic tree which are
clearly defined by coding-region or HVR mutations, but which may appear to originate or pass on the
length heteroplasmic variants at position 524 between generations and nodes on
the tree by the only occasionally visible heteroplasmic system. The reason for using the new term is not that
a new method of heredity has been discovered, just that the effects of
undetected heteroplasmic mutations has not been widely discussed. Typically, a subclade which has haplotypes
with more than one variant, divides into two or more lower subclades with
different combinations of the variants. Table
1 shows the percentages of each type of variant (deletions,
In Table 1, the percentages of the
position 524 variants for the members of the mtDNA Haplogroup K Project are
those of the Family Tree
Table 1. 524 Variants in Haplogroup K
|
|
Deletions % |
|
Insertions % |
|
K Project |
2.2 |
68.4 |
29.4 |
|
SMGF |
16.8 |
76.8 |
6.4 |
Table 2 illustrates the percentages of
each variant in most K subclades. The
subclades listed include those from the Behar K tree which have examples in the
K Project confirmed by full-sequence tests or known examples in GenBank, plus
provisional subclades used by the author: K1a10, K1a11, Pre-K1a9 and
Pre-K1a10. Those with plus signs, K1a+,
K1b+, K1c+ and K2+, include not only samples which have been assigned
high-level subclade designations after full-sequence tests; but also samples
from the K Project that have not been tested adequately to determine their
possible membership in a lower subclades.
These may eventually move into one of the more specific lower subclades
listed. The Counts column lists the
number of examples of each subclade from the K Project and GenBank. The GenBank examples include the 121
full-sequence used in the Behar K tree except for those marked “H” (for Herrnstadt) which, until recently, were not in
GenBank. Even now the published Herrnstadt sequences do not include HVR mutations. Added are several other K examples listed on
Table 2. Percentages of Position 524 Heteroplasmic
Variants in Haplogroup K Subclades
|
Subclade |
Counts |
522-,523- % |
|
524.1,524.2 % |
524.3,524.4 % |
524.5,524.6 % |
524.7,524.8 % |
524 Total Inserts % |
|
Repeats |
|
4 |
5 |
6 |
7 |
8 |
9 |
|
|
|
11-KP |
|
100 |
|
|
|
|
0 |
|
K2a |
34-KP,19-GB |
6 |
94 |
|
|
|
|
0 |
|
K2a1a |
1-GB |
|
100 |
|
|
|
|
0 |
|
K2a2 |
1-GB |
|
100 |
|
|
|
|
0 |
|
K2a2a |
8-KP,2-GB |
|
100 |
|
|
|
|
0 |
|
K2a3 |
2-GB |
|
100 |
|
|
|
|
0 |
|
K2a4 |
1-GB |
|
100 |
|
|
|
|
0 |
|
K2c |
1-GB |
|
100 |
|
|
|
|
0 |
|
K1 |
1-KP |
|
100 |
|
|
|
|
0 |
|
K1c+ |
14-KP |
21 |
79 |
|
|
|
|
0 |
|
K1c1 |
1-KP,8-GB |
|
100 |
|
|
|
|
0 |
|
K1c1a |
1-GB |
100 |
|
|
|
|
|
0 |
|
K1c1b |
4-GB |
|
100 |
|
|
|
|
0 |
|
K1c2 |
26-KP,1-GB |
|
96 |
4 |
|
|
|
4 |
|
K1a+ |
67-KP |
1 |
70 |
24 |
4 |
1 |
|
29 |
|
K1a1 |
1-KP,1-GB |
|
100 |
|
|
|
|
0 |
|
K1a1a |
1-KP |
|
100 |
|
|
|
|
0 |
|
K1a1b |
1-KP,1-GB |
|
100 |
|
|
|
|
0 |
|
K1a1b1 |
2-KP,1-GB |
33 |
67 |
|
|
|
|
0 |
|
K1a1b1a |
30-KP,7-GB |
|
97 |
3 |
|
|
|
3 |
|
K1a6 |
2-GB |
|
100 |
|
|
|
|
0 |
|
K1a7 |
1-GB |
|
100 |
|
|
|
|
0 |
|
K1a8 |
3-GB |
|
100 |
|
|
|
|
0 |
|
K1a11 |
8-KP |
|
100 |
|
|
|
|
0 |
|
K1a3 |
1-GB |
|
100 |
|
|
|
|
0 |
|
K1a3a |
1-KP,1-GB |
|
100 |
|
|
|
|
0 |
|
K1a3a1 |
1-GB |
|
|
100 |
|
|
|
100 |
|
K1a3a1a |
1-GB |
|
100 |
|
|
|
|
0 |
|
K1a2 |
4-GB |
|
25 |
75 |
|
|
|
75 |
|
K1a5 |
1-GB |
|
|
100 |
|
|
|
100 |
|
K1a4 |
6-GB |
|
|
67 |
33 |
|
|
100 |
|
K1a4a1 |
7-KP,3-GB |
|
30 |
70 |
|
|
|
80 |
|
K1a4b |
1-GB |
|
|
100 |
|
|
|
100 |
|
K1a4c |
1-GB |
|
|
100 |
|
|
|
100 |
|
Pre-K1a9 |
6-KP,2-GB |
|
100 |
|
|
|
|
0 |
|
K1a9 |
10-KP,4-GB |
7 |
93 |
|
|
|
|
0 |
|
Pre-K1a10 |
23-KP,1-GB |
|
|
42 |
50 |
4 |
4 |
100 |
|
K1a10 |
24-KP |
|
|
25 |
71 |
4 |
|
100 |
|
K1b+ |
3-KP |
|
|
100 |
|
|
|
100 |
|
K1b1a |
7-KP,1-GB |
|
75 |
25 |
|
|
|
25 |
|
K1b1b |
2-GB |
|
|
50 |
50 |
|
|
100 |
|
K1b1c |
1-GB |
|
100 |
|
|
|
|
0 |
|
K1b2 |
16-KP,4-GB |
|
35 |
40 |
20 |
5 |
|
65 |
The first
point of conundrum for Haplogroup K was probably at the founding of K itself,
since some of the variants–perhaps only the
K1 is
defined by mutations 1189C and 10398G and is divided into three subgroups, K1a,
K1b and K1c. In the Haplogroup K Project
there is only one example, which was determined by a full-sequence test, of a
K1 not assigned to a lower subclade.[2]
There is also one ancient example, Ötzi the Iceman (Rollo et al., 2006: Endicott et al., 2007). The K1 founder potentially had several of the
524 indel variants, including at least the
K1c is
defined by HVR mutations only: 146C, 152C and 498-. Only three exactly matching individuals in
K1c+, or probably K1c1, since that lower subclade is defined by coding-region
mutations only, have the deletions.
Until more examples in different haplotypes are found, there is the
possibility that those three came from one de
novo mutation. The one known
available example of K1c1a, from GenBank, has the deletions. The confirmed examples of K1c1 and K1c1b have
only the
The major
subclade K1a includes over 60% of the K Project, and 80% of all of Behar’s K subjects (Behar et al. 2006), although the latter
number is probably just a characteristic of the particular population that
Behar was studying. K1a is defined by one HVR2 mutation, 497T, which appears no
other place in K and perhaps in no other haplogroup. But the founder must have received the


Figure
1. Simplified K1a Tree with Additional
Provisional Subclades K1a10 and K1a11
The
largest Ashkenazi subclade, K1a1b1a, has 30 probable examples in the K Project,
with six confirmed by full-sequence tests.
All those have the
One lower
subclade, K1a1b1, has only two confirmed examples in the K Project; one has the
K1a4 is
defined by coding-region mutation 11485C.
K1a4a adds mutation 6260A. So
far, there are no confirmed examples of those subclades, or K1a4b or K1a4c, in
the K Project. K1a4 is represented in
six GenBank sequences; four of which have one insertion pair, while two have
two pairs. K1a4a1, which is defined by
the addition of coding-region mutations 11840T and 13740C, and is represented
in the K Project by seven confirmed examples and three in GenBank, so far
either has the
K1a2,
found only in four GenBank samples, has one
The last
K1a lower subclade on the Behar K tree is K1a9, but it is not at the same level
as most of the other eight. Instead, it
is below a branching point at 195C, which is perhaps the most interesting point
of conundrum. The examples below this
point on the Behar K tree include only 8.3% of the 121 total sequences used to
create that tree; while in the K Project 19.6% of 321 sequences appear to fall
below that point. The founder with 195C
must have transmitted the
Although
it is not on the Behar K tree, probably because Behar found only one example–a
non-Jewish Moroccan (Behar et al., 2006, Table 4)–there is a second large cluster
under 195C defined by 16048A, provisionally called K1a10. This cluster never has deletions or the
Figure
1 is restricted
to the section of the K tree under major subclade K1a which is defined by HVR2
mutation 497T. For the defining
mutations of lower subclades K1a1 through K1a8 see the Behar K tree. There are two new provisional lower subclades
added here. K1a10, defined by HVR1
mutation 16048A, is a sister subclade to K1a9 under HVR2 mutation 195C. K1a11 is defined by several HVR and
coding-region mutations. “9bpD” is a
sequence of nine coding-region deletions from 8281 to 8289. K1a7 and K1a8 are shown here next to K1a1
just to demonstrate the sharing of HVR1 mutation 16234T in all three
subclades. The subclades in turquoise
generally have a significant percentage of examples with position 524
insertions, while those in yellow do not.
The
remaining major subclade is K1b, which is defined by the coding-region mutation
5913A, at another point of conundrum. K1b
is split between K1b1, defined by three coding-region mutations 9962A, 10289G
and 15946T, and K1b2 which is defined by coding-region transversion 12738G and
two HVR mutations, 146C
and
195C. Unlike the split below 195C in K1a
where one main branch only has the
Of K1b1’s
lower subclades, K1b1a is easily identified by HVR mutations 16319A and 152C,
with a good representation in the K Project.
Its majority variant is the
The
entire K haplogroup seems to be divided between two groups of subclades. One group, including
Several
possible general rules may be observed from the above table and
discussion. One rule is that no lower
subclade has examples with both deletions and insertions. Many subclades have only the
Insights from Previously Published
Scientific Research Articles
Three
articles have been published dealing specifically with the variants at position
524: Szibor et al. (1997) reported on three European
populations and an African Bantu population; Chung et al. (2005) reported on
500 Koreans; and Szibor et al. (2007) reported on a
study of 2,458 Germans. All three
articles focused on the possible use of the position variants for forensic
identification. None of these studies attempted
to identify the haplogroups involved, so they are not specific to haplogroup K
or any other haplogroup.
Szibor
et al. (1997) stated that repeat polymorphisms are found in only two places in
mtDNA. Other than position 524, there is
a nine base pair deletion in the coding region, which has a lower variability
than position 524. This set of deletions
at position 8281-8289 appears in at least two places on the Behar K tree, but
so far has only shown up in the K1a11 subclade in the K Project (See Figure 1). The position 524 variants are not as useful as
chromosomal STRs for forensic purposes, being described as “moderately
informative.” The usefulness of 524 for forensic purposes comes from the high
mtDNA count per cell as compared to chromosomal
Chung et
al. (2005) noted the similarity of these 524 positions to nuclear
Szibor
et al. (2007) studied 2,458 German samples, also focusing on forensic identity
testing. They also found the
In Table 3, the Korean samples are from
the Chung et al. (2005) article. The
other samples are from the Szibor et al. (1997, 2007)
articles. As above, tan denotes
deletions, yellow denotes
Table 3. Position 524 Heteroplasmic Variant
Percentages in World Populations
|
CA Repeats |
|
3 (%) |
4 (%) |
5 (%) |
6 (%) |
7 (%) |
8 (%) |
% With 524 Insertions |
|
Country, Year |
Sample Count |
|
|
|
|
|
|
|
|
Korea 2005 |
500 |
|
37 |
61 |
1 |
1 |
|
2 |
|
1997 |
105 |
2 |
53 |
44 |
|
|
|
0 |
|
1997 |
100 |
|
19 |
75 |
5 |
1 |
|
6 |
|
1997 |
191 |
|
1 |
81 |
8 |
1 |
|
9 |
|
|
396 |
|
11 |
79 |
8 |
2 |
|
10 |
|
2007 |
2458 |
|
11 |
80 |
8 |
2 |
0.4 |
10 |
Combined,
the three studies found the same 524 variants in roughly the same percentages
as is found in the SMGF database, except for the two deletion pairs in the
Do the
results from the three papers observe the rules suggested by our study of
Haplogroup K? Lower subclades – or any subclades of haplogroups at all – were
not covered in these papers, so the rule that a lower subclade will not have
both insertions and deletions does not apply.
Certainly none of the populations showed a variant that skipped a step
between different numbers of repeats.
The highest percentage variant is always in the middle. No population had only two variants, so the
rule that
524 Variants in Other mtDNA
Haplogroups
The
population studies in the three articles above are interesting, but genetic
genealogists are used to thinking more in terms of haplogroups instead of
populations. So the next area of
investigation was the comparable distribution of the 524 variants in the other
mtDNA haplogroups. MitoSearch was used
as a data source, as were websites of other mtDNA haplogroup projects. However, study of the lower subclades of the other
haplogroups was generally beyond the scope of this article.
The
When
macro-haplogroup R is reached, the
So the
deletions were probably, in fact, the ancestral variant in “mitochondrial Eve”;
and the
Again,
the results from other haplogroups can be measured against the rules derived
from haplogroup K. No lower subclades
were studied, so it was not determined if any had both deletions and
insertions. Four haplogroups only had
one variant, two each for deletions and
Table 4 shows
the 524 variant percentages in the major mtDNA haplogroups. The data for the table were
collected, if available, from mtDNA haplogroup projects as listed on the World
Families website. For haplogroups A, B, C and D, data were from the Amerind Founder Project.
Data for haplogroups with “ms,” such as L1ms%, was collected from
MitoSearch. Haplogroups and certain
major subclades are listed approximately in order of founding from
mitochondrial Eve, with haplogroups in side-branches kept together. For example, haplogroups C and D are listed
under M before the main line resumes with N.
Again, the insertions are in tan, the


Figure 2. Mitochondrial Phylogenetic Tree with 514-524
Status
Areas for Future Research
Position 524 Variants
The 524
insertions, in combination with other mutations, might be useful in determining
the age of some subclades. It might be
especially helpful if the other mutation were one of the more stable ones. For example, assume that the original
provisional K1a10 with 16048A, which only appears at one place in K, had two
pairs of 524 insertions. Therefore, the
29% of K1a10 with one pair or three pairs of insertions had to have mutated
since the founding of the subclade.
However, there is still the question of whether the one and three pair
variants were inherited as minority variants which later became dominant or
were due to de novo replication
slippages.
Where
possible, attention should be given to any differences in the 524 variants
found in related persons in K and other haplogroups to see if there are any
similarities to the differences between family members found in Szibor et al. (2007).
Other Haplogroup K Heteroplasmic
Mutations
Of
course, 524 is not the only position which presents a problem in determining
the method and origin of mutations.
There are other examples within haplogroup K; a few will be discussed
below. Possible examples in other
haplogroups have not been investigated; that is beyond the scope of this study.
A group
of such mutations is found below K1a1.
Mutation 16234T defines K1a1b1a, where it appears to have become
fixed. The Behar K tree also shows this
mutation in a parallel example in K1a1b1.
However, the one sample from this branch in the K Project does not have
16234T, so the mutation is probably not fixed there. 16234T is also the
defining mutation connecting K1a7 and K1a8; perhaps there is a point of
conundrum connecting those two subclades with K1a1. Mutation 16223T is most commonly found two
steps down from the K1a1b1a modal, but also other places in K1a1. The third mutation of the group, 114T, is
found in most examples of K1a1b1a. It is
also found in some examples of K1a1a and K1a1b; leading to the possibility that
it was a de novo mutation at the K1a1
point. A less common fourth mutation,
16092C, may be another member of this group; it probably mutated de novo below K1a1 and now appears in
various combinations in its lower subclades and branches.
Mutation
16051G appears in several examples of K1a10.
It also appears in a few K1a sequences which have not yet been given a
lower assignment. Perhaps future results
will help determine at what point this mutation originated.
The Behar
K tree has one sequence with 16266T in K1b1c, while there is one in K1b2 in the
K Project. Did these mutations occur at
the K1b split and have phylogenetic significance for these subgroups, or are
these mutations just independent de novo
mutations? Since the same mutation occurs in a K1a sequence in the K Project,
this may just be a mutation that frequently occurs de novo.
Categories of Mutations
In
general, the various types of mutations need further study. In addition to positions such as 524 and
those just discussed, there are several other categories. Some, such as 497T, which can only be found
once in the phylogenetic tree, or 498- and 16048A, which might be thought of as
unique event polymorphisms within K, are
at one end of the scale. Those mutations
are at least the equal of coding-region mutations in their ability to define
subclades. At the opposite end of the
scale, insertion 309.1C shows up in virtually every K subclade and thus has no
use in defining subclades – the notable exceptions being K1a9 and K1a10, where
it is fixed out. 16093C is also common
in many subclades. Tully et al. (2000)
discusses position 16093 in great detail.
Most other mutations fall somewhere between these two extremes. Recurrent mutations 146C, 152C and 195C are
used to define more than one subclade and also appear in other subclades. Each mutation affected by heteroplasmy has
its own independent system or parallel layer.
For many such mutations, the point of its origin may often be
determined. As an example, 114T probably
was a de novo mutation at the K1a1
node, since it appears only below that point.
Position
524 just happens to be the most complicated of all, mostly due to its
As
mentioned above, strict heteroplasmies are not reported by FTDNA and some other
testing companies. However, the recent
paper “The Genographic Project Public Participation Mitochondrial
A recent
paper (Irwin et al. 2007, Tables S1 and S2) reported the HVR sequences for 400
Northern Greeks and Greek Cypriots. This
paper found 32 examples of heteroplasmies, all denoted by the IUPAC codes. In haplogroup K examples they reported 146Y
(C/T combination), 16189Y and 16093Y twice.
They also found examples of 16311Y, 16129R (A/G combination), 195Y and
152Y, but in other haplogroups, not K.
Of
course, research similar to the above for haplogroup K could be performed on
any of the other haplogroups.
Conclusions
Position
524 has not been well-studied in the past, partly due to its location in the
old HVR3, which has not often been tested.
Even very recent mtDNA studies, such as that of the National Genographic
Project (Behar et al., 2007), often only report on HVR1 and perhaps
haplogroup-defining control-region SNPs.
The study
of 524 variants is hindered somewhat by the great variety of naming systems, a
situation that is not likely to improve anytime soon.
More than
any other mtDNA position, 524 mutates in a manner similar to that of nuclear
One pair
of deletions–a total of four CA repeats–was probably the original 524 variant,
as shown by its predominance in the oldest L haplogroups. Working along the mtDNA tree, the
Many K
subclades are fixed at one variant, most commonly the
Position
524 is useful for predicting subclades from HVR-only results, since there are
subclades which almost always have or almost never have a particular
variant. Often this is most helpful in
conjunction with other listed mutations.
It should be noted that almost exactly half of the haplogroups in Table
4 have greater than 90% in one variant.
It is difficult to say that 524 should not be part of the definition of
a haplogroup when 100% of the examples are fixed at the same variant as appears
to have happened in five of the haplogroups.
Table 4. Position 524 Heteroplasmic Variant
Percentages from FamilyTreeDNA Data by Haplogroup
|
Haplogroup |
Counts |
522-, 523- % |
|
524.1, 524.2 % |
524.3, 524.4 % |
524.5, 524.6 % |
524.7, 524.8 % |
524 Insertions Total % |
|
CA Repeats |
|
4 |
5 |
6 |
7 |
8 |
9 |
|
|
L0ms% |
6 |
100 |
|
|
|
|
|
0 |
|
L1ms% |
60 |
88 |
12 |
|
|
|
|
0 |
|
L2ms% |
109 |
28 |
66 |
1 |
5 |
|
|
6 |
|
L3% |
54 |
33 |
65 |
2 |
|
|
|
2 |
|
M% |
14 |
7 |
86 |
7 |
|
|
|
7 |
|
D% |
5 |
|
100 |
|
|
|
|
0 |
|
C% |
31 |
68 |
32 |
|
|
|
|
0 |
|
N% |
38 |
11 |
87 |
3 |
|
|
|
3 |
|
I% |
40 |
15 |
63 |
3 |
15 |
3 |
3 |
23 |
|
W% |
50 |
2 |
94 |
|
4 |
|
|
4 |
|
X% |
67 |
4 |
93 |
3 |
|
|
|
3 |
|
A% |
47 |
98 |
2 |
|
|
|
|
0 |
|
Rms% |
34 |
3 |
91 |
6 |
|
|
|
6 |
|
B% |
12 |
8 |
83 |
8 |
|
|
|
8 |
|
Fms% |
5 |
100 |
|
|
|
|
|
0 |
|
J% |
164 |
11 |
87 |
2 |
1 |
|
|
3 |
|
T% |
112 |
3 |
96 |
2 |
|
|
|
2 |
|
HVms% |
105 |
3 |
95 |
|
2 |
|
|
2 |
|
V% |
64 |
2 |
98 |
|
|
|
|
0 |
|
H% |
510 |
12 |
85 |
3 |
|
|
|
3 |
|
U*ms% |
53 |
4 |
87 |
6 |
2 |
2 |
|
10 |
|
U1ms% |
15 |
40 |
47 |
7 |
7 |
|
|
14 |
|
U2% |
39 |
13 |
46 |
36 |
5 |
|
|
41 |
|
U3ms% |
27 |
|
100 |
|
|
|
|
0 |
|
U4% |
37 |
3 |
38 |
41 |
8 |
11 |
|
60 |
|
U5% |
222 |
4 |
91 |
5 |
1 |
|
|
6 |
|
U6ms% |
18 |
6 |
94 |
|
|
|
|
0 |
|
U7% |
6 |
100 |
|
|
|
|
|
0 |
|
K% |
321 |
2 |
69 |
16 |
12 |
1 |
0.3 |
29 |
Each
mtDNA haplotype is composed of mutations mostly inherited from its ancestors,
some in a heteroplasmic manner, with de
novo mutations rarer than might first appear. In the case of the 524 variants, both the
Electronic Database
Information
Argus BioSciences LLC
FamilyTreeDNA MitoSearch database
GenBank
http://www.ncbi.nlm.nih.gov/Genbank/
http://www.ianlogan.co.uk/mtDNA.htm
Mitomap:
A human mitochondrial genome database
mtDNA
Haplogroup K Project website
http://www.familytreedna.com/public/mtDNA_K/
Relative
Genetics, Inc.
Sorenson
Molecular Genealogy Foundation
World
Families links to other mtDNA haplogroup project websites:
http://worldfamilies.net/reference_mtDNA.html
References