Anzick (12,707-12,556), Ancient One, 52 Ancestors #42

anzick burial location

His name is Anzick, named for the family land, above, where his remains were found, and he is 12,500 years old, or more precisely, born between 12,707 and 12,556 years before the present.  Unfortunately, my genealogy software is not prepared for a birth year with that many digits.  That’s because, until just recently, we had no way to know that we were related to anyone of that age….but now….everything has changed ….thanks to DNA.

Actually, Anzick himself is not my direct ancestor.  We know that definitively, because Anzick was a child when he died, in present day Montana.

anzick on us map

Anzick was loved and cherished, because he was smeared with red ochre before he was buried in a cave, where he would be found more than 12,000 years later, in 1968, just beneath a layer of approximately 100 Clovis stone tools, shown below.  I’m sure his parents then, just as parents today, stood and cried as the laid their son to rest….never suspecting just how important their son would be some 12,500 years later.

anzick clovis tools

From 1968 until 2013, the Anzick family looked after Anzick’s bones, and in 2013, Anzick’s DNA was analyzed.

DNA analysis of Anzick provided us with his mitochondrial haplogroup,  D4h3a, a known Native American grouping, and his Y haplogroup was Q-L54, another known Native American haplogroup.  Haplogroup Q-L54 itself is estimated to be about 16,900 years old, so this finding is certainly within the expected range.  I’m not related to Anzick through Y or mitochondrial DNA.

Utilizing the admixture tools at GedMatch, we can see that Anzick shows most closely with Native American and Arctic with a bit of east Siberian.  This all makes sense.

Anzick MDLP K23b

Full genome sequencing was performed on Anzick, and from that data, it was discovered that Anzick was related to Native Americans, closely related to Mexican, Central and South Americans, and not closely related to Europeans or Africans.  This was an important discovery, because it in essence disproves the Solutrean hypothesis that Clovis predecessors emigrated from Southwest Europe during the last glacial maximum, about 20,000 years ago.

anzick matches

The distribution of these matches was a bit surprising, in that I would have expected the closest matches to be from North America, in particular, near to where Anzick was found, but his closest matches are south of the US border.  Although, in all fairness, few people in Native tribes in the US have DNA tested and many are admixed.

This match distribution tells us a lot about population migration and distribution of the Native people after they left Asia, crossed Beringia on the land bridge, now submerged, into present day Alaska.

This map of Beriginia, from the 2008 paper by Tamm et all, shows the migration of Native people into (and back from) the new world.

beringia map

Anzick’s ancestors crossed Beringia during this time, and over the next several thousand years, found their way to Montana.  Some of Anzick’s relatives found their way to Mexico, Central and South America.  The two groups may have split when Anzick’s family group headed east instead of south, possibly following the edges of glaciers, while the south-moving group followed the coastline.

Recently, from Anzick’s full genome data, another citizen scientist extracted the DNA locations that the testing companies use for autosomal DNA results, created an Anzick file, and uploaded the file to the public autosomal matching site, GedMatch.  This allowed everyone to see if they matched Anzick.  We expected no, or few, matches, because after all, Anzick was more than 12,000 years old and all of his DNA would have washed out long ago due to the 50% replacement in every generation….right?  Wrong!!!

What a surprise to discover fairly large segments of DNA matching Anzick in living people, and we’ve spent the past couple of weeks analyzing and discussing just how this has happened and why.  In spite of some technical glitches in terms of just how much individual people carry of the same DNA Anzick carried, one thing is for sure, the GedMatch matches confirm, in spades, the findings of the scientists who wrote the recent paper that describes the Anzick burial and excavation, the subsequent DNA processing and results.

For people who carry known Native heritage, matches, especially relatively large matches to Anzick, confirm not only their Native heritage, but his too.

For people who suspect Native heritage, but can’t yet prove it, an Anzick match provides what amounts to a clue – and it may be a very important clue.

In my case, I have proven Native heritage through the Micmac who intermarried with the Acadians in the 1600s in Nova Scotia.  Given that Anzick’s people were clearly on a west to east movement, from Beringia to wherever they eventually wound up, one might wonder if the Micmac were descended from or otherwise related to Anzick’s people.  Clearly, based on the genetic affinity map, the answer is yes, but not as closely related to Anzick as Mexican, Central and South Americans.

After several attempts utilizing various files, thresholds and factors that produced varying levels of matching to Anzick, one thing is clear – there is a match on several chromosomes.  Someplace, sometime in the past, Anzick and I shared a common ancestor – and it was likely on this continent, or Beringia, since the current school of thought is that all Native people entered the New World through this avenue.  The school of thought is not united in an opinion about whether there was a single migration event, or multiple migrations to the new word.  Regardless, the people came from the same base population in far northeast Asia and intermingled after arriving here if they were in the same location with other immigrants.

In other words, there probably wasn’t much DNA to pass around.  In addition, it’s unlikely that the founding population was a large group – probably just a few people – so in very short order their DNA would be all the same, being passed around and around until they met a new population, which wouldn’t happen until the Europeans arrived on the east side of the continent in the 1400s.  The tribes least admixed today are found south of the US border, not in the US.  So it makes sense that today the least admixed people would match Anzick the most closely – because they carry the most common DNA, which is still the same DNA that was being passed around and around back then.

Many of us with Native ancestors do carry bits and pieces of the same DNA as Anzick.  Anzick can’t be our ancestor, but he is certainly our cousin, about 500 generations ago, using a 25 year generation, so roughly our 500th cousin.  I had to laugh at someone this week, an adoptee who said, “Great, I can’t find my parents but now I have a 12,500 year old cousin.”  Yep, you do!  The ironies of life, and of genealogy, never fail to amaze me.

Utilizing the most conservative matching routine possible, on a phased kit, meaning one that combines the DNA shared by my mother and myself, and only that DNA, we show the following segment matches with Anzick.

Chr Start Location End Location Centimorgans (cM) SNPs
2 218855489 220351363 2.4 253
4 1957991 3571907 2.5 209
17 53111755 56643678 3.4 293
19 46226843 48568731 2.2 250
21 35367409 36761280 3.7 215

Being less conservative produces many more matches, some of which are questionable as to whether they are simply convergence, so I haven’t utilized the less restrictive match thresholds.

Of those matches above, the one on chromosomes 17 matches to a known Micmac segment from my Acadian lines and the match on chromosome 2 also matches an Acadian line, but I share so many common ancestors with this person that I can’t tell which family line the DNA comes from.

There are also Anzick autosomal matches on my father’s side.  My Native ancestry on his side reaches back to colonial America, in either Virginia or North Carolina, or both, and is unproven as to the precise ancestor and/or tribe, so I can’t correlate the Anzick DNA with proven Native DNA on that side.  Neither can I associate it with a particular family, as most of the Anzick matches aren’t to areas on my chromosome that I’ve mapped positively to a specific ancestor.

Running a special utility at GedMatch that compared Anzick’s X chromosome to mine, I find that we share a startlingly large X segment.  Sometimes, the X chromosome is passed for generations intact.

Interestingly enough, the segment 100,479,869-103,154,989 matches a segment from my mother exactly, but the large 6cM segment does not match my mother, so I’ve inherited that piece of my X from my father’s line.

Chr Start Location End Location Centimorgans (cM) SNPs
X 100479869 103154989 1.4 114
X 109322285 113215103 6.0 123

This tells me immediately that this segment comes from one of the pink or blue lines on the fan chart below that my father inherited from his mother, Ollie Bolton, since men don’t inherit an X chromosome from their father.  Utilizing the X pedigree chart reduces the possible lines of inheritance quite a bit, and is very suggestive of some of those unknown wives.

olliex

It’s rather amazing, if you think about it, that anyone today matches Anzick, or that we can map any of our ancestral DNA that both we and Anzick carry to a specific ancestor.

Indeed, we do live in exciting times.

Honoring Anzick

On a rainy Saturday in June, 2014, on a sagebrush hillside in Montana, in Native parlance, our “grandfather,” Anzick was reburied, bringing his journey full circle.  Sarah Anzick, a molecular biologist, the daughter of the family that owns the land where the bones were found, and who did part of the genetic discovery work on Anzick, returns the box with his bones for reburial.

anzick bones

More than 50 people, including scientists, members of the Anzick family and representatives of six Native American tribes, gathered for the nearly two-hour reburial ceremony. Tribe members said prayers, sang songs, played drums and rang bells to honor the ancient child. The bones were placed in the grave and sprinkled with red ocher, just like when his parents buried him some 12,500 years before.

Participants at the reburial ceremony filled in the grave with handfuls, then shovelfuls of dirt and covered it with stones. A stick tied with feathers marks Anzick’s final resting place.

Sarah Anzick tells us that, “At that point, it stopped raining. The clouds opened up and the sun came out. It was an amazing day.”

I wish I could have been there.  I would have, had I known.  After all, he is part of me, and I of him.

anzick grave'

Welcome to the family, Anzick, and thank you, thank you oh so much, for your priceless, unparalleled gift!!!

tobacco

If you want to read about the Anzick matching journey of DNA discovery, here are the articles I’ve written in the past two weeks.  It has been quite a roller coaster ride, but I’m honored and privileged to be doing this research.  And it’s all thanks to an ancient child named Anzick.

Utilizing Ancient DNA at Gedmatch

Analyzing the Native American Anzick Clovis Native American Results

New Native American Mitochondrial DNA Haplogroups Extrapolated from Anzick Match Results

Ancient DNA Matching, A Cautionary Tale

More Ancient DNA Samples for Comparison

Ancient DNA Matching – A Cautionary Tale

egg

I hope that all of my readers realize that you are literally watching science hatch.  We are on the leading, and sometimes bleeding edge, of this new science of genetic genealogy.  Because many of these things have never been done before, we have to learn by doing and experimenting.  Because I blog about this, these experiments are “in public,” so there is no option of a private “oops.”  Fortunately, I’m not sensitive about these kinds of things.  Plus, I think people really enjoy coming along for the ride of discovery.  I mean, where else can you do that?  It’s really difficult to get a ride-along on the space shuttle!

One of the best pieces of advice I ever got was from someone who was taken from my life far too early.  I had made a mistake of some sort…don’t even remember what…and he gave me a card that said, “The only people who don’t make mistakes are the people who don’t try.”

This isn’t an “oops” moment.  More like an “aha” moment.  Or more precisely, a “huh” moment.  It falls in the “Houston, we’ve got a problem” category.

So, this week’s new discovery is that there seems to be some inconsistency in the matching to the Anzick kit at GedMatch.  Before I go any further, I want to say very clearly that this is in no way a criticism of anyone or any tool.  Every person involved is a volunteer and we would not be making any of these steps forward, including a few backwards, without these wonderful volunteers and tools.

I have reached out to the people involved and asked for their help to unravel this mystery, and I’m sharing the story with you, partly so you can understand what is involved, and the process, partly so that you don’t inadvertently encounter the same kinds of issues and draw unrealistic or incorrect conclusions, and partly so you can help.  If there has been any common theme in all of my articles in the past week or so about the ancient DNA articles, it has been that we really don’t understand what conclusions to draw yet…and we still don’t.  So don’t.

Let’s introduce the players here.

The Players

Felix Chandrakumar has very graciously prepared the various ancient DNA files and uploaded them to GedMatch.  Felix has written a number of DNA analysis tools as well.

John Olson is one of the two volunteers who created and does everything at Gedmatch, plus works a full time job.  By the way, in case you’re not aware, this is a contribution site, meaning they depend on your financial contributions to function, purchase hardware, servers, etc.  If you use this site, periodically scroll down and click on the donate button.  We, as a community, would be lost without John and his partner.

David Pike is a long time genetic genealogist who I have had the pleasure of working with on a number of Native American and related topics over the years. He also has created several genetic genealogy tools to deal with autosomal DNA. David prepared the Anzick files for some private work we were doing several months ago, so he has experience with this DNA as well.  Dr. Pike has a great deal of experience analyzing the endogamous population of Newfoundland, which is also admixed with Native Americans.

Marie Rundquist, also a long time genetic genealogist who specializes in both technology and Acadian history along with genetic genealogy.  Acadians are proven to be admixed with Native Americans.  Marie shares my deep interest and commitment to Native American study and genetics.  Furthermore, Marie and I also share ancestors and co-administer several related projects.   As you might imagine, Marie and I took this opportunity immediately to see if she and her mother share any of Anzick’s segments with me and my mother.

So, a big thank you to all of these people.

The Mystery

When Felix originally e-mailed me about the Anzick kit being uploaded to GedMatch, as you might imagine, I stopped doing whatever I was doing and immediately went to study Anzick and the other ancient DNA kits.

I wrote about this experience in the article, “Utilizing Ancient DNA at GedMatch.”

As part of that process, I not only ran Anzick’s kit utilizing the “one to many” option, I also compared my own kit to Anzick’s.  My proven Native lines descend through my mother, so I ran her kit against Anzick’s as well, at the same thresholds, and I combined the two results to see where mother and I overlapped.

I showed these overlaps in the article, along with which genealogy lines they matched by utilizing my ancestor matching spreadsheet.

Everything was hunky dory…for then.

Day 2

The next day, I received a note from Felix that the Anzick kit may not have been fully tokenized at GedMatch previously, so I reran the Anzick “one to all” comparison and wrote about those results in the second article, “Analyzing the Native American Clovis Ancient Results.”  Because it wasn’t yet fully processed originally, the second results produced more matches, not fewer.

I wasn’t worried about the one to one comparison of Anzick to my own kit, because one to one comparisons are available immediately, while one to many comparisons are not, per the GedMatch instructions.

“Once you have loaded your data, you will be able to use some features of the site within a minute or so. Additional batch processing, which usually takes a couple of days, must complete before you can use some of the tools comparing you to everyone in the data pool.”

So, everything was stlll hunky dory.

Day 3

The next day, Marie and I had a few minutes, sometime between 2 and 3AM, and no, I’m not kidding.  We decided to compare results.  I decided it would be quicker to run the match again at GedMatch than to sort through my Master spreadsheet, into which I had copied the results and added other information.  So, I did a second download of the Anzick comparison, utilizing the exact same thresholds (200 SNPs, 2cM, and the rest left at the default,) and added them to a spreadsheet that Marie and I were passing back and forth, and sent them to Marie.  I noticed that there seemed to be fewer matches, but by then it was after 3AM and I decided to follow up on that later.

Not so hunky dory…but I didn’t know it yet.

Day 4

The following day, Dr. Ann Turner (MD), also a long-time genetic genealogist, posted the following comment on the article.

“These results, finding “what appear to be contemporary matches for the Anzick child”, seemed very counter-intuitive to me, so I asked John Olson of GEDMatch to look under the hood a bit more. It turns out the ancient DNA sequence has many no-calls, which are treated as universal matches for segment analysis. Another factor which should be examined is whether some of the matching alleles are simply the variants with the highest frequency in all populations. If so, that would also lead to spurious matching segments. It may not be appropriate to apply tools developed for genetic genealogy to ancient DNA sequences like this without a more thorough examination of the underlying data.”

I had been aware of the no-calls due to the work that Dr. David Pike did back in March with the Anzick raw data files, but according to David, that shouldn’t affect the results.

Here’s what Dr. Pike, a Professor of Mathematics, had to say:

“Yes, these forensic samples have very high No-Call rates, which may give rise to more false matches than we would normally experience.  Also, be aware that false matches are more prone to occur when using reduced thresholds (such as 100 SNPs and 1 cM) and unphased data.  In this case I don’t think there’s any way around using low thresholds, simply because we’re looking for very small blocks of DNA (probably nobody alive today will have any large matching blocks with the Anzick child).

On the assumption that there will be a nearly constant noise ratio, meaning that most people will have about the same number of false matches with the Anzick child, those who are from the same gene pool should have an increased number of real matches.  So by comparing the total amount of matching DNA, it ought to be possible to gauge people’s affinity with Anzick’s gene pool.”

Here are Felix’s comments about no-calls as well:

“Personally, no calls are fine as long as there are more SNPs matching above the threshold level because the possibility of errors occurring exactly on no-call positions for all the matches in all their matching segments is impossible.”

Courtesy of Felix, we’ll see an example of how no calls intersperse in  a few minutes.

If no-calls were causing spurious matches in the Anzick kit, you’d expect to see the same for the other ancient DNA kits.  I know that the Denisovan and Neanderthal kits also have many no-calls, and based on the nature of ancient DNA, I’m sure all of them do.  So, if no calls are the culprit, they should be affecting matches to the other kits in the same way, and they aren’t.

Hunky-doryness is being replaced by a nonspecific nagging feeling…same one I used to get when my teenagers were up to something.

Day 5

A day or so later, Felix uploaded file F999913 to replace F999912 with the complete SNPs from all of the companies.  The original 999912 kit only included the SNP locations utilized by Family Tree DNA.  Felix added the SNPs utilized by 23and Me not utilized at Family Tree DNA, and the ones from Ancestry as well.  This is great news for anyone who tested at those two companies, but I had utilized my kit from Family Tree DNA, so for me, there should be no difference at all.

I later asked Felix if he had changed anything else in the file, and he said that he had not.  He provided extensive documentation about what he had done.

I waited until kit F999912 was deleted to be sure tokenizing was complete for F999913 and re-compared the data again.  As expected, Anzick’s one to all had more matches than before, because additional people were included due to the added SNPs from 23andMe and Ancestry.

Some of Anzick’s matches are in the contemporary range, at 3.1 estimated generations, with the largest cM segment of 22.8 and total cMs of 202.8.

anzick 999913

These relatively large matches cause Felix to question whether the sample is actually ancient, based on these relatively large segments.  I addressed my feelings on this in the article, Ancient DNA Matches – What Do They Mean?

Marie and Dr. Pike, both with extensive experience with admixed populations addressed this as well.  Marie commented,

“Native DNA found in the Anzick sample hasn’t changed all of that much and may still be found in modern, Native American populations, and that if people have Native American ancestry, they’ll match to it.”

Dr. Pike says:

“I agree with Marie on this… within endogamous populations, there is an increased likelihood of blocks of DNA being preserved over lengthy time frames.  Moreover, even if a block of DNA gets cut up via recombination, within an endogamous population the odds of some parts of the block later reuniting in a person’s DNA are higher than otherwise.  And it exaggerates the closeness of [the] relationship that gets predicted when comparing people.

I have seen something similar within the Newfoundland & Labrador Family Finder Project, whereby lots of people are sharing small blocks of DNA, likely as a result of DNA from the early colonists still circulating among the modern gene pool.

As an anecdotal example, I have a semi-distant relative (with ancestry from Newfoundland) at 23andMe who shares 3 blocks of DNA with my father, 2 with my mother and 5 five me.  As you can imagine, the relative is predicted to be a closer cousin to me than she is to either of my parents!

It doesn’t take an endogamous or isolated population to see this effect.

It can also happen in families involving cousin marriages too, although that would be more pronounced and not quite the same thing as we’re discussing with respect to ancient DNA.”

This addition of other companies SNPs should not affect my matches with Anzick because my kits are both from FTDNA and won’t utilize the added SNPs.

However, I ran my and my mother’s matches again, and we had a significantly different outcome than either of the previous times.

I utilized the same threshold for all downloads and those are the only values I changed – 200 SNPs and 2cM, leaving the other values at default, for all Anzick comparisons to my mother and my kits.

I am not hunky-dory anymore.

The Heartburn

These matches, which should be the same in all three downloads, produced significantly different results.

Here are the number of matches at the same threshold comparing me and Mom to the Anzick file:

Me and Anzick

  • original download 999912 – 47 matches
  • second download 999912 – 21 matches
  • 999913 – 35 matches

Mom and Anzick

  • original download 999912 – 63
  • second download 999912 – 37
  • 999913 – 36

And no, the 36 /35 that mom and I have for 999913 are not all the same.

Kit Number Matches Between Me, Mother and Anzick
#1-F999912 original download 19
#2-F999912 second download 6
#3-F999913 11

Of those various downloads, the following grid shows which ones matched each other.

#1 to #2 #2 to #3 #1 to #3 All 3
# of Matches 6 2 3 2

So, comparing the first download to the last download, of the 19 original matches, we lost 16 matches.  In the third download, we gained 8 matches and only 3 remained as common matches. So of 30 total matches between my mother, myself and Anzick, in two downloads that should have been exactly the same, only 3 matches held, or 10%.

Obviously, something is wrong, but what, and where?  At that point, I asked Marie to download her and her mother’s results again too, and she experienced the same issue.

Clearly a problem exists someplace.  That’s the question I asked Felix, John and David to help answer.

I realize that this spreadsheet it very long, and I apologize, but I think this issue is much easier to see visually.  I’ve compiled the matches by color and shade to make looking at them relatively easy.

My matches to the Anzick kit are in shades of pink – the first match download being the lightest and the last one to kit F999913 being the darkest.  Mother is green, same shading scheme.

The three columns to the right show the matching segments for each download – shaded in green.  You can easily see which ones line up, meaning which ones match consistently across all three downloads.  There aren’t many.  They should all match.

anzick me mom problem

Obviously this led to many questions that I asked of the various players involved.

My first thought was that perhaps a matching algorithm change occurred in GedMatch, but John assured me that he had made no changes.

Next question was whether or not Felix changed something other than adding the 23andMe and Ancestry SNPs.  He had not.

Felix was kind enough to explain about bunching and to do some analysis on the files.

“When you have low thresholds, make sure you don’t allow errors. For example, at 200 SNPs, the default ‘Mismatch Evaluation window’ and in GEDMatch is same as SNP threshold and ‘Mismatch-Bunching limit’ is half of mismatch evaluation window. So, at 200 cM, you are allowing 1 error every 100 SNPs apart from no-calls.

I did some analysis on your phased mother’s kit, PF6656M1 so that at least we know that it is an IBD for one generation.  The spreadsheet (below) are segments I found at 2 cM/200 SNPs threshold without allowing any errors.”

Kit PF6656M1 is one single kit created by phasing my data against my mother’s so that we don’t have to run both kits.  I had not utilized the phased kit previously, so I was interested in his results.

felix anzick

The results above confirm chromosome matches, 2, 17, 19 and 21, but introduce a new match on chromosome 4.  This match was present in the original download, but not in the second or third download, so once again, we have disparate data, except the thresholds Felix used were at a different level.

One of the more interesting things that Felix included is the no-call match information, the three columns to the right.  I want to show what the no-calls look like.  There are not huge segments that are blank and are being called as matches because they are no-calls, when they shouldn’t be.  No calls are scattered like salt and pepper.  In fact, no calls happen in every kit and they are called as matches so they don’t in fact disrupt a valid match string, potentially making it too small to be considered a match.  Of course, ancient DNA has more no-calls that contemporary DNA kits.

Below are the first few match positions from chromosome 2 where mother, Anzick and I have a confirmed match across all downloads.  The genotype shows you that both kits match.

felix no calls

For consistency, I ran the same kits that Felix ran, PF6656M1 and F999913, with the original thresholds I had used, and found the following:

Chr Start Location End Location Centimorgans (cM) SNPs
1 31358221 33567640 2.0 261
2 218855489 220351363 2.4 253
4 1957991 3571907 2.5 209
5 2340730 2982499 2.3 200
17 53111755 56643678 3.4 293
19 46226843 48568731 2.2 250
21 35367409 36761280 3.7 215

This introduces chromosomes 1 and 5, not shown above.   The chromosome 1 match was shown in the first and second download, but not the third, and the chromosome 5 match was shown in the first download only, but not the second or third.

Can you see me beating my head against the wall yet??

In a fit of apparent insanity, I decided to try, once again, an individual download of Anzick compared to my mother and to me, but not utilizing the phased kit – the original F6656 and F9141, and at the original thresholds, for consistency.  I wanted to see if the matches were the same now as they were a day or so ago.  They should be exact.  This first one is mine.

me second 999913

What you should see are two identical downloads.  I have color coded the rows so you can see easily – and what you should see are candy-cane stripes – one red and one white for every match location.

That’s not what we’re seeing.  The kits are the same, the match parameters are the same, but the results are not.  Once again, the downloads don’t match.

I did another match on mother and Anzick, and her results were consistent between the first and second match to kit F999913.

mom second 999913

The begs the next question.  Have mother’s results always been consistent, suggesting a problem with my kit?

I sorted all of her downloads, and no, they are not consistent, except for the first and second download matches to kit F999913, shown above.  The inconsistencies show up in both mother and my kits, although not in the same locations.  Recall also that Marie had the same issue.

In Summary

Something is wrong, someplace.  I know that sounds intuitively obvious – NOW.  But it wasn’t initially and I wouldn’t even have suspected a problem without running the second and third downloads, quite unintentionally.  Most people never do that, because once you’ve done the match, you have no reason to ever match to that particular person again.  Given that, you’ll never know if a problem exists.

So, the only Anzick GedMatch matches I have any confidence in at all, at this point, are the few that are consistent between all of the downloads, and I didn’t add the fourth download into the mix.  I don’t’ see any point because I’ve pretty much concluded that until we determine where the issue resides, that I won’t have confidence in the results.

The next question that comes to mind, and that I can’t answer, is whether or not this issue is present in contemporary matching kits – or if this is somehow an ancient DNA problem – although I don’t know quite how that could be – since matching is matching.

I haven’t saved any matches that I’ve run to other people in spreadsheets, so I can’t go back and see if a GedMatch match today produces the exact same results as a previous match.

Clearly there is no diagnosis or solution in this summary.  We are not yet hunky dory.

What You Can Do

  1. Run your Anzick and ancient DNA matches multiple times, at the same exact thresholds, on different days, to see if your results are consistent or inconsistent. Same kit, same thresholds, the results should be identical.
  2. If you have some saved GedMatch matches with contemporary people, and you are positive of the match thresholds used, please run them again to see if the results are identical. They should be.
  3. No drawing of or jumping to conclusions, please, especially about ancient DNA:) It’s a journey and we are fellow pilgrims!

If your results are not consistent, please document the problem and let the appropriate person know.  I don’t want to overwhelm John at GedMatch but I’m concerned at this point that the problem may not be isolated to ancient DNA matching since the issue seems to extend to Marie’s results as well.

If your results, especially to Anzick, from previous matches to now are consistent, that’s worth knowing too.  Please add a comment to that effect.

Thoughts and ideas are welcome.

10 Things to Do With Your DNAPrint, renamed AncestrybyDNA, Test

birdcage

Please note, AncestrybyDNA is NOT the same as the AncestryDNA test sold by Ancestry.com.  Both CeCe Moore and David Dowell have written about this in their respective blogs.

Back in 2002 (no, that is not a typo,) a new product called DNAPrint was introduced by a company then called DNAPrint Genomics.  It provided you, in percentages, your percentages of 4 ethnic groups: Indo-European, East-Asian, Native American and African.  Family Tree DNA remarketed this test for just over a year but ceased when they realized there were issues.

It was the first of its kind of test ever to be offered commercially, and version 2.0 utilized a whopping 71 ancestrally informative markers, according to the user’s guide delivered with the product.  The next version of the test, 2.5, titled AncestrybyDNA included 175 markers, and a third version, which I don’t believe was ever released, was to include just over 300 markers.

In 2002, this was a baby step in a brand new world.  We, as a community, were thrilled to be able to obtain this type of information.  And of course, we believed it was accurate, or relatively so.  However, the questions and ensuing debate started almost immediately and became very heated.

The company’s representatives indicated that East-Asian and Native American could be combined for those without a “Chinese grandpa” and that would have given me a whopping 25% Native American.  Even then, before pedigree analysis, I thought this was a little high.  My East Asian was shown as 15%, Native American at 10% and Indo-European at 75%.  For reference, my real Native results are probably in the 1-3% range.  Keep in mind that we were all babes in the woods, kind of stumbling around, learning, in 2002 and 2003.

Interestingly enough, I found the answer recently, quite by accident, to one of the burning questions about Native American ancestry that was asked repeatedly of Tony Frudakis during that timeframe, then a corporate officer of DNAPrint, and left unanswered.  In Carolyn Abraham’s book, The Juggler’s Children, which is a wonderful read, on page 55, the answer to the forever-hanging question was answered:

“When I finally reached Frudakis, that’s how he explained the confusion over our Native ancestry result – semantics.  The Florida company had pegged its markers as being Native American to appeal to the American market, he told me.  But it was accurate to consider them Central Asian markers, he said, that had been carried to different regions by those who migrated from that part of the globe long ago – into the Americas, into East Asia, South Asia and even southern Europe – finding their way into today’s Greeks, Italians and Turks.  ‘We may do ourselves a favour and change the name of this ancestry [component] in the test,’ he said, since apparently I wasn’t the only one baffled by it.”

So, now we know, straight from the horses mouth, via Carolyn.

Of course, since that time, many advances have occurred in this field.  Today, Family Tree DNA, 23andMe, Ancestry.com and the Genographic Project utilize chip based technology and utilize over half a million markers to achieve ethnicity predictions.  If DNAPrint, renamed AncestybyDNA was the first baby step, today we are teenagers – trying to refine our identity.  Today’s tests, although not totally accurate, are, by far, more accurate than this first baby step.  Give us another dozen years in this industry, and they’ll be spot on!

For 2003, when I ordered mine, DNAPrint was an adventure – it was exciting – it was a first step – and we learned a lot.  Unfortunately, DNAPrint under the name AncestrybyDNA is still being sold today, currently owned by the DNA Diagnostics Center.  If you are even thinking about ordering this product, take a look first at the Yelp reviews and the Better Business Bureau complaints.

I don’t regret spending the money in 2003.  Spending money on this outdated test today would be another story entirely – a total waste.  The results are entirely irrelevant today in light of the newer and more refined technology.  Unfortunately, seldom a week goes by that I don’t receive an e-mail from someone who bought this test and are quite confused and unhappy.  The test has been marketed and remarketed by a number of companies over the years.

So, here are some suggestions about what might be appropriate to do with your DNAPrint or AncestybyDNA results if you don’t want to just throw them away:

  1. Line the bottom of the birdcage.
  2. Use to light the BBQ grill or camp fire.
  3. Use under boots in the hallway in the winter.
  4. Shred, then use as confetti.
  5. Cut into strips and use as bookmarks.
  6. Use as scratch paper.
  7. Use in the garden between rows to minimize weeds.
  8. Make into a paper airplane.
  9. Roll, along with other excess paper, into logs for the fireplace.
  10. Frame, and display along with your other antiques.

Yes, it’s really that old and outdated!

Finding Native American Ethnic Results in Germanic People

I’m often asked about the significance of small percentages of autosomal DNA in results.  Specifically, the small percentages are often of Native American or results that would suggest Native admixture.  One of the first questions I always ask is whether or not the individual has Germanic or eastern European admixture.

Why?

Take a look at this map of the Invasion of the Roman Empire.  See the Huns and their path?

Hun map

It’s no wonder we’re so admixed.

Here’s a map of the Hunnic empire at its peak under Attila between the years 420-469.

Hun emplire

But that wasn’t the end of the Asian invasions.  The Magyars, who settled in Hungary arrived from Asia as well, in the 800s and 900s, as shown on this map from LaSalle University.

magyar map

Since both the Hungarians and some Germanic people descend from Asian populations, as do Native Americans, albeit thousands of years apart, it’s not unrealistic to expect that, as populations, they share a genetic connection.

Therefore, when people who carry heritage from this region of the world show small amounts of Native or Asian origin, I’m not surprised.  However, for Americans, trying to sort out their Native ethnic heritage, this is most unhelpful.

Let’s take a look at the perfect example candidate.  This man is exactly half Hungarian and half German.  Let’s see what his DNA results say, relative to any Asian or Native heritage, utilizing the testing companies and the free admixture tools at www.gedmatch.com.

He has not tested at Ancestry, but at Family Tree DNA, his myOrigins report 96% European, 4% Middle Eastern.  At 23andMe in speculative view, he shows 99.7 European and .2 sub-saharan African.

Moving to the admixture tools at GedMatch, MDLP is not recommended for Asian or Native ancestry, so I have excluded that tool.

Eurogenes K13 is the most recently updated admixture tool, so let’s take a look at that one first.

Eurogenes K13

 JK Eurogenes K13 v2

Eurogenes K13 showed 7% West Asian, which makes perfect sense considering his heritage, but it might be counted as “Native” in other circumstances, although I would certainly be very skeptical about counting it as such.

However, East Asian, Siberian and Amerindian would all be amalgamated into the Native American category, for a combined percentage of 1.31.

jk eurogenes k13 chart

However, selecting the “admixture proportions by chromosome” view shows something a bit different.  The cumulative percentages, by chromosome equate to 10.10%.  Some researchers mistakenly add this amount and use that as their percentage of Native ancestry.  This is not the case, because those are the portions of 100% of each individual chromosome, and the total would need to be divided by 22 to obtain the average value across all chromosomes.  The total is irrelevant, and the average may not reflect how the developer determines the amount of admixture because chromosomes are not the same size nor carry the same number of SNPs.  Questions relative to the functional underpinnings of each tool should be addressed to the developers.

Dodecad

I understand that there is a newer version of Dodecad, but that it has not been submitted to GedMatch for inclusion, per a discussion with GedMatch.  I can’t tell which of the Dodecad versions on GedMatch is the most current, so I ran the results utilizing both v3 and 12b.

jk dodecad v3

jk dodecad v3 chart

I hope v3 is not the most current, because it does not include any Native American category or pseudocategory – although there is a smattering of Northeast Asian at .27% and Southwest Asian at 1%.

Dodecad 12b below

jk dodecad 12b

The 12b version does show .52% Siberian and 2.6% Southwest Asian, although I’m not at all sure the Southwest Asian should be included.

HarappaWorld

jk harappaworld

jk harappaworld chart

Harappaworld shows .09 Siberian, .27% American (Native American), .23% Beringian and 1.8% Southwest Asian, although I would not include Southwest Asian in the Native calculation.

In Summary

Neither Family Tree DNA nor 23andMe find Native ancestry in our German/Hungarian tester, but all 3 of the admixture tools at Gedmatch find either small amounts of Native or Asian ancestry that could certainly be interpreted as Native, such as Siberian or Beringian.

Does this mean this German/Hungarian man has Native American ancestry?  Of course not, but it does probably mean that the Native population and his ancestral populations did share some genes from the same gene pool thousands of years ago.

While you might think this is improbable, or impossible, consider for a minute that every person outside of Africa today carries some percentage of Neanderthal DNA, and all Europeans also carry Denisovan DNA.  Our DNA does indeed have staying power over the millennia, especially once an entire population or group of people is involved.  We’ve recently seen this same type of scenarios in the full genome sequencing of a 24,000 year old Siberian male skeleton.

Our German/Hungarian man carries 2.4% Neanderthal DNA according to 23andMe and 2.7% according to the Genographic Project, which also reports that he carries 3.9% Denisovan.  The European average is about 2% for Neanderthal.

The net-net of this is that minority admixture is not always what it seems to be, especially when utilizing autosomal DNA to detect small amounts of Native American admixture.  The big picture needs to be taken into consideration.  Caution is advised.

When searching for Native admixture, when possible, both Y DNA and mitochondrial DNA give specific answers for specific pedigree lines relative to ancestry.  Of course, to utilize Y or mtDNA, the tester must descend from the Native ancestor either directly paternally to test the male Y chromosome, or directly matrilineally to test the mitochondrial line.  You can read about this type of testing, and how it works, in my article, Proving Native American Ancestry Using DNA.  You can also read about other ways to prove Native ancestry using autosomal DNA, including how to unravel which pedigree line the Native ancestry descends from, utilizing admixture tools, in the article, “The Autosomal Me.”

Ethnicity Percentages – Second Generation Report Card

Recently, Family Tree DNA introduced their new ethnicity tool, myOrigins as part of their autosomal Family Finder product.  This means that all of the major players in this arena using chip based technology (except for the Genographic project) have now updated their tools.  Both 23andMe and Ancestry introduced updated versions of their tools in the fall of 2013.  In essence, this is the second generation of these biogeographical or ethnicity products.  So lets take a look and see how the vendors are doing.

In a recent article, I discussed the process for determining ethnicity percentages using biogeographical ancestry, or BGA, tools.  The process is pretty much the same, regardless of which vendor’s results you are looking at.  The variant is, of course, the underlying population data base, it’s quality and quantity, and the way the vendors choose to construct and name their regions.

I’ve been comparing my own known and proven genealogy pedigree breakdown to the vendors results for some time now.  Let’s see how the new versions stack up to a known pedigree.

The paper, “Revealing American Indian and Minority Heritage using Y-line, Mitochondrial, Autosomal and X Chromosomal Testing Data Combined with Pedigree Analysis” was published in the Fall 2010 issue of JoGG, Vol. 6 issue 1.

The pedigree analysis portion of this document begins about page 8.  My ancestral breakdown is as follows:

Geography Pedigree Percent
Germany 23.8041
British Isles 22.6104
Holland 14.5511
European by DNA 6.8362
France 6.6113
Switzerland 0.7813
Native American 0.2933
Turkish 0.0031

This leaves about 25% unknown.

Let’s look at each vendor’s results one by one.

23andMe

23andme v2

My results using the speculative comparison mode at 23andMe are shown in a chart, below.

23andMe Category 23andMe Percentage
British and Irish 39.2
French/German 15.6
Scandinavian 7.9
Nonspecific North European 27.9
Italian 0.5
Nonspecific South European 1.6
Eastern European 1.8
Nonspecific European 4.9
Native American 0.3
Nonspecific East Asian/Native American 0.1
Middle East/North Africa 0.1

At 23andMe, if you have questions about what exact population makes up each category, just click on the arrow beside the category when you hover over it.

For example, I wasn’t sure exactly what comprises Eastern European, so I clicked.

23andme eastern europe

The first thing I see is sample size and where the samples come from, public data bases or the 23andMe data base.  Their samples, across all categories, are most prevalently from their own data base.  A rough add shows about 14,000 samples in total.

Clicking on “show details” provides me with the following information about the specific locations of included populations.

23andme pop

Using this information, and reorganizing my results a bit, the chart below shows the comparison between my pedigree chart and the 23andMe results.  In cases where the vendor’s categories spanned several of mine, I have added mine together to match the vendor category.  A perfect example is shown in row 1, below, where I added France, Holland, Germany and Switzerland together to equal the 23andMe French and German category.  Checking their reference populations shows that all 4 of these countries are included in their French and German group.

Geography Pedigree Percent 23andMe %
Germany, Holland, Switzerland & France 45.7451 15.6
France 6.6113 (above) Combined
Germany 23.8014 (above) Combined
Holland 14.5511 (above) Combined
Switzerland 0.7813 (above) Combined
British Isles 22.6104 39.2
Native American 0.2933 0.4 (Native/East Asian)
Turkish 0.0031 0.1 (Middle East/North Africa)
Scandinavian 7.9
Italian 0.5
South European 1.6
East European 1.8
European by DNA 6.8362 4.9 (nonspecific European)
Unknown 25 27.9 (North European)

I can also change to the Chromosome view to see the results mapped onto my chromosomes.

23andme chromosome view

The 23andMe Reference Population

According to the 23andMe customer care pages, “Ancestry Composition uses 31 reference populations, based on public reference datasets as well as a significant number of 23andMe members with known ancestry. The public reference datasets we’ve drawn from include the Human Genome Diversity ProjectHapMap, and the 1000 Genomes project. For these datasets as well as the data from 23andMe, we perform filtering to ensure accuracy.

Populations are selected for Ancestry Composition by studying the cluster plots of the reference individuals, choosing candidate populations that appear to cluster together, and then evaluating whether we can distinguish the groups in practice. The population labels refer to genetically similar groups, rather than nationalities.”

Additional detailed information about Ancestry Composition is available here.

Ancestry.com

ancestry v2

Ancestry is a bit more difficult to categorize, because their map regions are vastly overlapping.  For example, the west Europe category is shown above, and the Scandinavian is shown below.

ancestry scandinavia

Both categories cover the Netherlands, Germany and part of the UK.

My Ancestry percentages are:

Ancestry Category Ancestry Percentage
North Africa 1
America <1
East Asia <1
West Europe 79
Scandinavia 10
Great Britain 4
Ireland 2
Italy/Greece 2

Below, my pedigree percentages as compared to Ancestry’s categories, with category adjustments.

Geography Pedigree Percent Ancestry %
West European 52.584 (combined from below) 79
Germany 23.8041 Combined
Holland 14.5511 Combined
European by DNA 6.8362 Combined
France 6.6113 Combined
Switzerland 0.7813 Combined
British Isles 22.6104 6
Native American 0.2933 ~1 incl East Asian
Turkish 0.0031 1 (North Africa)
Unknown 25
Italy/Greece 2
Scandinavian 10

Ancestry’s European populations and regions are so broadly overlapping that almost any interpretation is possible.  For example, the Netherlands could be included in several categories – and based up on the history of the country, that’s probably legitimate.

At Ancestry, clicking on a region, then scrolling down will provide additional information about that region of the world, both their population and history.

The Ancestry Reference Population

Just below your ethnicity map is a section titled “Get the Most Out of Your Ethnicity Estimate.”  It’s worth clicking, reading and watching the video.  Ancestry states that they utilized about 3000 reference samples, pared from 4245 samples taken from people whose ethnicity seems to be entirely from that specific location in the world.

ancestry populations

You can read more in their white paper about ethnicity prediction.

Family Tree DNA’s myOrigins

I wrote about the release of my Origins recently, so I won’t repeat the information about reference populations and such found in that article.

myorigins v2

Family Tree DNA shows matches by region.  Clicking on the major regions, European and Middle Eastern, shown above, display the clusters within regions.  In addition, your Family Finder matches that match your ethnicity are shown in highest match order in the bottom left corner of your match page.

Clicking on a particular cluster, such as Trans-Ural Peneplain, highlights that cluster on the map and then shows a description in the lower left hand corner of the page.

myorigins trans-ural

Family Tree DNA shows my ethnicity results as follows.

Family Tree DNA Category Family Tree DNA Percentage
European Coastal Plain 68
European Northlands 12
Trans-Ural Peneplain 11
European Coastal Islands 7
Anatolia and Caucus 3

Below, my pedigree results reorganized a bit and compared to Family Tree DNA’s categories.

Geography Pedigree Percent Family Tree DNA %
European Coastal Plain 45.7478 68
Germany 23.8041 Combined above
Holland 14.5511 Combined above
France 6.6113 Combined above
Switzerland 0.7813 Combined above
British Isles 22.6104 7 (Coastal Islands)
Turkish 0.0031 3 (Anatolia and Caucus)
European by DNA 6.8362
Native American 0.2933
Unknown 25
Trans-Ural Peneplain 11
European Northlands 12

Third Party Admixture Tools

www.GedMatch.com is kind enough to include 4 different admixture utilities, contributed by different developers, in their toolbox.  Remember, GedMatch is a free, meaning a contribution site – so if you utilize and enjoy their tools – please contribute.

On their main page, after signing in and transferring your raw data files from either 23andMe, Family Tree DNA or Ancestry, you will see your list of options.  Among them is “admixture.”  Click there.

gedmatch admixture

Of the 4 tools shown, MDLP is not recommended for populations outside of Europe, such as Asian, African or Native American, so I’ve skipped that one entirely.

gedmatch admix utilities

I selected Admixture Proportions for the part of this exercise that includes the pie chart.

The next option is Eurogenes K13 Admixture Proportions.  My results are shown below.

Eurogenes K13

Eurogenes K13

Of course, there is no guide in terms of label definition, so we’re guessing a bit.

Geography Pedigree Percent Eurogenes K13%
North Atlantic 75.19 44.16
Germany 23.8041 Combined above
British Isles 22.6104 Combined above
Holland 14.5511 Combined above
European by DNA 6.8362 Combined above
France 6.6113 Combined above
Switzerland 0.7813 Combined above
Native American 0.2933 2.74 combined East Asian, Siberian, Amerindian and South Asian
Turkish 0.0031 1.78 Red Sea
Unknown 25
Baltic 24.36
West Med 14.78
West Asian 6.85
Oceanian 0.86

Dodecad K12b

Next is Dodecad K12b

According to John at GedMatch, there is a more current version of Dodecad, but the developer has opted not to contribute the current or future versions.

Dodecad K12b

By the way, in case you’re wondering, Gedrosia is an area along the Indian Ocean – I had to look it up!

Geography Pedigree Percent Dodecad K12b
North European 75.19 43.50
Germany 23.8041 Combined above
British Isles 22.6104 Combined above
Holland 14.5511 Combined above
European by DNA 6.8362 Combined above
France 6.6113 Combined above
Switzerland 0.7813 Combined above
Native American 0.2933 3.02 Siberian, South Asia, SW Asia, East Asia
Turkish 0.0031 10.93 Caucus
Gedrosia 7.75
Northwest African 1.22
Atlantic Med 33.56
Unknown 25

Third is Harappaworld.

Harappaworld

harappaworld

Baloch is an area in the Iranian plateau.

Geography Pedigree Percent Harappaworld %
Northeast Euro 75.19 46.58
Germany 23.8041 Combined above
British Isles 22.6104 Combined above
Holland 14.5511 Combined above
European by DNA 6.8362 Combined above
France 6.6113 Combined above
Switzerland 0.7813 Combined above
Native American 0.2933 2.81 SE Asia, Siberia, NE Asian, American, Beringian
Turkish 0.0031 10.27
Unknown 25
S Indian 0.21
Baloch 9.05
Papuan 0.38
Mediterranean 28.71

The wide variety found in these results makes me curious about how my European results would be categorized using the MDLP tool, understanding that it will not pick up Native, Asian or African.

MDLP K12

mdlp k12

The Celto-Germanic category is very close to my mainland European total – but of course, many Germanic people settled in the British Isles.

Second Generation Report Card

Many of these tools picked up my Native American heritage, along with the African.  Yes, these are very small amounts, but I do have several proven lines.  By proven, I mean both by paper trail (Acadian church and other records) and genetics, meaning Yline and mtDNA.  There is no arguing with that combination.  I also have other Native lines that are less well proven.  So I’m very glad to see the improvements in that area.

Recent developments in historical research and my mitochondrial DNA matches show that my most distant maternal ancestral line in Germany have some type of a Scandinavian connection.  How did this happen, and when?  I just don’t know yet – but looking at the map below, which are my mtDNA full sequence matches, the pattern is clear.

mitomatches

Could the gene flow have potentially gone the other direction – from Germany to Scandinavia?  Yes, it’s possible.  But my relatively consistent Scandinavian ethnicity at around 10% seems unlikely if that were the case.

Actually, there is a second possibility for additional Scandinavian heritage and that’s my heavy Frisian heritage.  In fact, most of my Dutch ancestors in Frisia were either on or very near the coast on the northernmost part of Holland and many were merchants.

I also have additional autosomal matches with people from Scandinavia – not huge matches – but matches just the same – all unexplained.  The most notable of which, and the first I might add, is with my friend, Marja.

It’s extremely difficult to determine how distant the ancestry is that these tests are picking up.  It could be anyplace from a generation ago to hundreds of generations ago.  It all depends on how the DNA was passed, how isolated the population was, who tested today and which data bases are being utilized for comparison purposes along with their size and accuracy.  In most cases, even though the vendors are being quite transparent, we still don’t know exactly who the population is that we match, or how representative it is of the entire population of that region.  In some cases, when contributed data is being used, like testers at 23andMe, we don’t know if they understood or answered the questions about their ancestry correctly – and 23andMe is basing ethnicity results on their cumulative answers.  In other words, we can’t see beneath the blanket – and even if we could – I don’t know that we’d understand how to interpret the components.

So Where Am I With This?

I knew already, through confirmed paper sources that most of my ancestry is in the European heartland – Germany, Holland, France as well as in the British Isles.  Most of the companies and tools confirm this one way or another.  That’s not a surprise.  My 35 years of genealogical research has given me an extremely strong pedigree baseline that is invaluable for comparing vendor ethnicity results.

The Scandinavian results were somewhat of a surprise – especially at the level in which they are found.  If this is accurate, and I tend to believe it is present at some level, then it must be a combined effect of many ancestors, because I have no missing or unknown ancestors in the first 5 generations and only 11 of 64 missing or without a surname in generation 6.  Those missing ancestors in generation 6 only contribute about 1.5% of my DNA each, assuming they contribute an average of 50% of their DNA to offspring in each subsequent generation.

Clearly, to reach 10%, nearly all of my missing ancestors, in the US and Germany, England and the Netherlands would have to be 100% Scandinavian – or, alternately, I have quite a bit scattered around in many ancestors, which is a more likely scenario.  Still, I’m having a difficult time with that 10% number in any scenario, but I will accept that there is some Scandinavian heritage one way or another.  Finding it, however, genealogically is quite another matter.

However, I’m at a total loss as to the genesis of the South European and Mediterranean.  This must be quite ancient.  There are only two known possible ancestors from these regions and they are many generations back in time – and both are only inferred with clearly enough room to be disproven.  One is a possible Jewish family who went to France from Spain in 1492 and the other is possibly a Roman soldier whose descendants are found within a few miles of a Roman fort site today in Lancashire.  Neither of these ancestors could have contributed enough DNA to influence the outcome to the levels shown, so the South European/Mediterranean is either incorrect, or very deep ancestry.

The Eastern European makes more sense, given my amount of German heritage.  The Germans are well known to be admixed with the Magyars and Huns, so while I can’t track it or prove it, it also doesn’t surprise me one bit given the history of the people and regions where my ancestors are found.

What’s the Net-Net of This?

This is interesting, very interesting.  There are tips and clues buried here, especially when all of the various tools, including autosomal matching, Y and mtDNA, are utilized together for a larger picture.  Alone, none of these tools are as powerful as they are combined.

I look forward to the day when the reference populations are in the tens of thousands, not hundreds.  All of the tools will be far more accurate as the data base is built, refined and utilized.

Until then, I’ll continue to follow each release and watch for more tips and clues – and will compare the various tools.  For example, I’m very pleased to see Family Tree DNA’s new ethnicity matching tool incorporated into myOrigins.

I’ve taken the basic approach that my proven pedigree chart is the most accurate, by far, followed by the general consensus of the combined results of all of the vendors.  It’s particularly relevant when vendors who don’t use the same reference populations arrive at the same or similar results.  For example, 23andMe uses primarily their own clients and Nat Geo of course, although I did not include them above because they haven’t released a new tool recently, uses their own population sample results.

National Geographic’s Geno2

Nat Geo took a bit of a different approach and it’s more difficult to compare to the others.  They showed my ethnicity as 43% North European, 36% Mediterranean and 18% Southwest Asian.

nat geo results

While this initially looks very skewed, they then compared me to my two closest populations, genetically, which were the British and the Germans, which is absolutely correct, according to my pedigree chart.  Both of these populations are within a few percent of my exact same ethnicity profile, shown below.

Nat geo british 2

The description makes a lot of sense too.  “The dominant 49% European component likely reflects the earliest settlers in Europe, hunter-gatherers who arrived there more than 35,000 years ago.  The 44% Mediterranean and the 17% Southwest Asian percentages arrived later, with the spread of agriculture from the Fertile Crescent in the middle East, over the past 10,000 years.  As these early farmers moved into Europe, they spread their genetic patterns as well.”

nat geo german

So while individually, and compared to my pedigree chart, these results appear questionable, especially the Mediterranean and Southwest Asian portions, in the context of the populations I know I descend from and most resemble, the results make perfect sense when compared to my closest matching populations.  Those populations themselves include a significant amount of both Mediterranean and Southwest Asian.  Looking at this, I feel a lot better about the accuracy of my results.  Sometimes, perspective makes a world of difference.

It’s A Wrap

Just because we can’t exactly map the ethnicity results to our pedigree charts today doesn’t mean the results are entirely incorrect.  It doesn’t mean they are entirely correct, either.  The results may, in some cases, be showing where population groups descend from, not where our specific ancestors are found more recently.  The more ancestors we have from a particular region, the more that region’s profile will show up in our own personal results.  This explains why Mediterranean shows up, for example, from long ago but our one Native ancestor from 7 or 8 generations ago doesn’t.  In my case, it would be because I have many British/German/Dutch lines that combine to show the ancient Mediterranean ancestry of these groups – where I have many fewer Native ancestors.

Vendors may be picking up deep ancestry that we can’t possible know about today – population migration.  It’s not like our ancestors left a guidebook of their travels for us – at least – not outside of our DNA – and we, as a community, are still learning exactly how to read that!  We are, after all, participants on the pioneering, leading edge of science.

Having said that, I’ll personally feel a lot better about these kinds of results when the underlying technology, data bases and different vendors’ tools mature to the point where there the differences between their results are minor.

For today, these are extremely interesting tools, just don’t try to overanalyze the results, especially if you’re looking for minority admixture.  And if you don’t like your results, try a different vendor or tool, you’ll get an entirely new set to ponder!

Family Tree DNA Releases myOrigins

my origins

On May 6th, Family Tree DNA released myOrigins as a free feature of their Family Finder autosomal DNA test.  This autosomal biogeographic feature was previously called Population Finder.  It has not just been renamed, but entirely reworked.

Currently, 22 population clusters in 7 major geographic groups are utilized to evaluate your biogeographic ethnicity or ancestry as compared to these groups, many of which are quite ancient.

my origins regions

Primary Population Clusters

  • Anatolia & Caucasus
  • Asian Northeast
  • Bering Expansion
  • East Africa Pastoralist
  • East Asian Coastal Islands
  • Eastern Afroasiatic
  • Eurasian Heartland
  • European Coastal Islands
  • European Coastal Plain
  • European Northlands
  • Indian Tectonic
  • Jewish Diaspora
  • Kalahari Basin
  • Niger-Congo Genesis
  • North African Coastlands
  • North Circumpolar
  • North Mediterranean
  • Trans-Ural Peneplain

Blended Population Clusters

  • Coastal Islands & Central Plain
  • Northlands & Coastal Plain
  • North Mediterranean & Coastal Plain
  • Trans-Euro Peneplain & Coastal Plain

Each of these groups has an explanation which can be found here.

Matching

Prior to release, Family Tree DNA sent out a notification about new matching options.  One of the new features is that you will be able to see the matching regions of the people you match – meaning your populations in common.  This powerful feature lets you see matches who are similar which can be extremely useful when searching for minority admixture, for example.  However, some participants don’t want their matches to be able to see their ethnicity, so everyone was given an ‘opt out’ option.  Fortunately, few people have opted out, less than 1%.

Be aware that only your primary matches are shown.  This means that your 4-5th cousins or more distant are not shown as ethnicity matches.

Here’s what the FTDNA notification said:

With myOrigins, you’ll be able compare your ethnicity with your Family Finder matches. If you want to share your ethnic origins with your matches, you don’t need to take any action.  You’ll automatically be able to compare your ethnicity with your matches when myOrigins becomes available.  This is the recommended option. However, we do understand that sharing your ethnicity with your matches is your choice so we’re sending you this reminder in case you want to not take part (opt-out). To opt-out, please follow the instructions below. *

  1. Click this link.
  2. If you are not logged in, do so.
  3. Select the “Do not share my ethnic breakdown with my matches. This will not let me compare my ethnicity with my matches.” radio button.
  4. Click the Save button.

You can get more details about what will be shared here.  You may also join our forums for discussion* You can change your privacy settings at any time. Thus, you may opt-out of or opt back into ethnic sharing at a later date if you change your mind.

What’s New?

Let’s take a look at the My Origins results.  You can see your results by clicking on “My Origins” on the Family Finder tab on your personal page at Family Tree DNA.

Ethnicity and Matches

Your population ethnicity is shown on the main page, as well as up to three shared regions that you share with your matches.  This means that if you share more than 3 regions with these people, the 4th one (or 5th or 6th, etc.) won’t show.  This also means that if your match has an ethnicity you don’t have, that won’t show either.

my origins ethnicity

Above, you see my main results page.  Please note that this map is what is known as a heat map.  This means that the darkest, or hottest, areas are where my highest percentages are found.

Each region has a breakdown that can be seen by clicking on the region bar.  My European region bar population cluster breakdown is shown below along with my ethnicity match to my mother.

my origins euro breakdown

And my Middle Eastern breakdown is shown below.

my origins middle east breakdown

Ethnicity Mapping

A great new feature is the mapping of the maternal and paternal ethnicity of your Family Finder matches, when known.  How does Family Tree DNA know?  The location data entered in the “Matches Map” location field.  Can’t remember if you completed these fields?  It’s easy to take a look and see.  On either the Y DNA or the mtDNA tabs, click on Matches Map and you’ll see your white balloon.  If the white balloon is in the location of your most distant ancestor in your paternal line (for Y) or your matrilineal line for mtDNA (your mother’s mother’s mother’s line on up the tree until you run out of mothers), then you’ve entered the location data and you’re good to go.  If your white balloon is on the equator, click on the tab at the bottom of the map that says “update ancestor’s location” and step through the questions.

ancestor location

If you haven’t completed this information, please do.  It makes the experience much more robust for everyone.

How Does This Tool Work?

my origins paternal matches

The buttons to the far right of the page show the mapped locations of the oldest paternal lines and the oldest matrilineal (mtDNA) lines of your matches.  Direct paternal matches would of course be surname matches, but only to their direct paternal lines. This does not take into account all of their “most distant ancestors,” just the direct paternal ones.  This is the yellow button.

The green button provides the direct maternal matches.

my origins maternal matches

Do not confuse this with your Matches Map for your own paternal (if you’re a male) or mitochondrial matches.  Just to illustrate the difference, here is my own direct maternal full sequence matches map, available on my mtDNA tab.  As you can see, they are very different and convey very different information for you.

my mito match map

Comparisons

By way of comparison, here are my mother’s myOrigins results.

my origins mother

Let’s say I want to see who else matches her from Germany where our most distant mitochondrial DNA ancestor is located.

I can expand the map by scrolling or using the + and – keys, and click on any of the balloons.

my origins individual match

Indeed, here is my balloon, right where it should be, and the 97% European match to my mother pops up right beside my balloon.  The matches are not broken down beyond region.

This is full screen, so just hit the back button or the link in the upper right hand corner that says “back to FTDNA” to return to your personal page.

Walk Through

Family Tree DNA has provided a walk-through of the new features.

Methodology

How did Family Tree DNA come up with these new regional and population cluster matches?

As we know, all of humanity came originally from Africa, and all of humanity that settled outside of Africa came through the Middle East.  People left the Middle East in groups, it would appear, and lived as isolated populations for some time in different parts of the world.  As they did, they developed mutations that are found only in that region, or are found much more frequently in that region as opposed to elsewhere.  Patterns of mutations like this are established, and when one of us matches those patterns, it’s determined that we have ancestry, either recent or perhaps ancient, from that region of the world.

The key to this puzzle is to find enough differentiation to be able to isolate or identify one group from another.  Of course, the groups eventually interbred, at least most of them did, which makes this even more challenging.

Family Tree DNA says in their paper describing the population clusters:

MyOrigins attempts to reduce the wild complexity of your genealogy to the major historical-genetic themes which arc through the life of our species since its emergence 100,000 years ago on the plains of Africa. Each of our 22 clusters describe a vivid and critical color on the palette from which history has drawn the brushstrokes which form the complexity that is your own genome. Though we are all different and distinct, we are also drawn from the same fundamental elements.

The explanatory narratives in myOrigins attempt to shed some detailed light upon each of the threads which we have highlighted in your genetic code. Though the discrete elements are common to all humans, the weight you give to each element is unique to you. Each individual therefore receives a narrative fabric tailored to their own personal history, a story stitched together from bits of DNA.

They have also provided a white paper about their methodology that provides more information.

After reading both of these documents, I much prefer the explanations provided for each cluster in the white paper over the shorter population cluster paper.  The longer version breaks the history down into relevant pieces and describes the earliest history and migrations of the various groups.

I was pleased to see the methodology that they used and that four different reference data bases were utilized.

  • GeneByGene DNA customer database
  • Human Genome Diversity Project
  • International HapMap Project
  • Estonian Biocentre

Given this wealth of resources, I was very surprised to see how few members of some references populations were utilized.

Population N Population N
Armenian 46 Lithuanian 6
Ashkenazi 60 Masai 140
British 39 Mbuti 15
Burmese 8 Moroccan 7
Cambodian 26 Mozabite 24
Danish 13 Norwegian 17
Filipino 20 Pashtun 33
Finnish 49 Polish 35
French 17 Portuguese 25
German 17 Russian 41
Gujarati 31 Saudi 19
Iraqi 12 Scottish 43
Irish 45 Slovakian 12
Italian 30 Spanish 124
Japanese 147 Surui 21
Karitiana 23 Swedish 33
Korean 15 Ukrainian 10
Kuwaiti 14 Yoruba 136

In particular, the areas of France, Germany, Norway, Slovakia, Denmark and the Ukraine appear to be very under-represented, especially given Family Tree DNA’s very heavy European-origin customer base .  I would hope that one of the priorities would be to expand this reference data base substantially.  Furthermore, I don’t see any New World references included here which calls into question Native American ancestry.

Webinar

Family Tree DNA typically provides a webinar for new products as well as general education.  The myOrigins webinar can be found in the archives at this link.  It can be viewed any time.  https://www.familytreedna.com/learn/ftdna/webinars/

Accuracy

How did they do?  Certainly, Family Tree DNA has a great new interface with wonderful new maps and comparison features.  Let’s take a look at accuracy and see if everything makes sense.

I am fortunate to have the DNA of one of my parents, my mother.  In the chart below, I’m comparing that result and inferring my father’s results by subtracting mine from my mother’s.  This may not be entirely accurate, because this presumes I received the full amount of that ethnicity from my mother, and that is probably not accurate – but – it’s the best I can do under the circumstances.  It’s safe to say that my father has a minimum of this amount of that particular population category and may have more.

Region Me Mom Dad Inferred Minimum
European Coastal Plain 68 17 51
European Northlands 12 7 5
Trans Ural Peneplain 11 10 1
European Coastal Islands 7 34 0
Anatolia and Caucus 3 0 3
North Mediterranean 0 34 0
Circumpolar 0 1 0
Undetermined* 0 0 40

*The Undetermined category is not from Family Tree DNA, but is the percentage of my father not accounted for by inference.  This 40% is DNA that I did not inherit if it falls into a different category.

Based on these results alone, I have the following observations.

    1. I find it odd that my mother has 34% North Mediterranean and I have none. We have no known ancestry from this region.
    2. My mother does have one distant line of Turkish DNA via France. I have presumed that my Middle Eastern (now Anatolia and Caucus) was through that line, but these results suggest otherwise.
    3. My mother’s Circumpolar may be Native American. She does have proven Native lines (Micmac) through the Acadian families.
    4. These results have missed both my Native lines (through both parents) and my African admixture although both are small percentages.
    5. The European Coastal Plain is one of the groups that covers nearly all of Europe. Given that my mother is 3/4th Dutch/German, with the balance being Acadian, Native and English, one would expect her to have significantly more, especially given my high percentage.
    6. The European Coastal Island percentages are very different for me and my mother, with me carrying much less than my mother.  This is curious, because she is 3/4th German/Dutch with between 1/8th and 3/16th English while my father’s lines are heavily UK.  My father’s ancestry may well be reflected in European Coastal Plain which covers a great deal of territory.

What We Need to Remember

All of the biogeographic tools, from Family Tree DNA, 23andMe and Ancestry, are “estimates” and each of the tools from the three major vendors rend different results.  Each one is using different combinations of reference populations, so this really isn’t surprising.  Hopefully, as the various companies increase their population references and the size of their reference data bases, the results will increasingly mesh from company to company.  These results are only as good as the back end tools and the DNA that you randomly inherited from your ancestors.

Furthermore, we all carry far more similar DNA than different DNA, so it’s extremely difficult to make judgment calls based on ranges.  Europe, for example, is extremely admixed and the US is moreso.  The British Isles were a destination location for many groups over thousands of years.  Some of the DNA being picked up by these tests may indeed be very ancient and may cause us to wonder where it came from.  In future test versions, this may be more perfectly refined.

There is no way to gauge “ancient” DNA, like from the Middle East Diaspora, from more contemporary DNA, only a thousand years or so old, once it’s in very small segments.  In other words, it’s all very individual and personal and pretty much cast in warm jello.  We’ve come a long way, but we aren’t “there” yet.  However, without these tools and the vendors working to make them better, we’ll never get “there,” so keep that in mind.

While this makes great conversation today, and there is no question about accuracy in terms of majority ancestry/ethnicity, no one should make any sweeping conclusions based on this information.  This is not “cast in concrete” in the same way as Y DNA and mitochondrial haplogroups and STR markers.  Those are irrefutable – while biogeographical ethnicity remains a bit ethereal.

In summary, I would simply say that this tool can provide great hints and tips, especially the matching, which is unique, but it can’t disprove anything.  The absence of minority admixture, which is what so many people are hunting for, may be the result of the various data bases and the infancy of the science itself, and not the absence of admixture.

My recommendation would be to utilize all three biogeographic admixture products as well as the free tools in the Admixture category at GedMatch.  Look for consistency in results between the tools.  I discussed this methodology in “The Autosomal Me” series.

What Next?

I asked Dr. David Mittelman, Chief Scientific Officer, at Family Tree DNA about the reference populations.  He indicated that he agreed that some of their reference populations are small and they are actively working to increase them.  He also stated that it is important to note that Family Tree DNA prioritized accuracy over false positives so they definitely took a conservative approach.

Clovis People Are Native Americans, and from Asia, not Europe

In a paper published in Nature today, titled “The genome of a Late Pleistocene human from a Clovis burial site in western Montana,” by Rasmussen et al, the authors conclude that the DNA of a Clovis child is ancestral to Native Americans.  Said another way, this Clovis child was a descendant, along with Native people today, of the original migrants from Asia who crossed the Bering Strait.

This paper, over 50 pages including supplemental material, is behind a paywall but it is very worthwhile for anyone who is specifically interested in either Native American or ancient burials.  This paper is full of graphics and extremely interesting for a number of reasons.

First, it marks what I hope is perhaps a spirit of cooperation between genetic research and several Native tribes.

Second, it utilized new techniques to provide details about the individual and who in world populations today they most resemble.

Third, it utilized full genome sequencing and the analysis is extremely thorough.

Let’s talk about these findings in more detail, concentrating on information provided within the paper.

The Clovis are defined as the oldest widespread complex in North America dating fromClovis point about 13,000 to 12,600 calendar years before present.  The Clovis culture is often characterized by the distinctive Clovis style projectile point.  Until this paper, the origins and genetic legacy of the Clovis people have been debated.

These remains were recovered from the only known Clovis site that is both archaeological and funerary, the Anzick site, on private land in western Montana.  Therefore, the NAGPRA Act does not apply to these remains, but the authors of the paper were very careful to work with a number of Native American tribes in the region in the process of the scientific research.  Sarah L. Anzick, a geneticist and one of the authors of the paper, is a member of the Anzick family whose land the remains were found upon.  The tribes did not object to the research but have requested to rebury the bones.

The bones found were those of a male infant child and were located directly below the Clovis materials and covered in red ochre.  They have been dated  to about 12,707-12,556 years of age and are the oldest North or South American remains to be genetically sequenced.

All 4 types of DNA were recovered from bone fragment shavings: mitochondrial, Y chromosome, autosomal and X chromosome.

Mitochondrial DNA

The mitochondrial haplogroup of the child was D4h3a, a rather rare Native American haplogroup.  Today, subgroups exist, but this D4h3a sample has none of those mutations so has been placed at the base of the D4h3a tree branch, as shown below in a grapic from the paper.  Therefore, D4h3a itself must be older than this skeleton, and they estimate the age of D4h3a to be 13,000 plus or minus 2,600 years, or older.

Clovis mtDNA

Today D4h3a is found along the Pacific coast in both North and South America (Chile, Peru, Ecuador, Bolivia, Brazil) and has been found in ancient populations.  The highest percentage of D4h3a is found at 22% of the Cayapa population in Equador.  An ancient sample has been found in British Columbia, along with current members of the Metlakatla First Nation Community near Prince Rupert, BC.

Much younger remains have been found in Tierra del Fuego in South America, dating from 100-400 years ago and from the Klunk Mound cemetery site in West-Central Illinois dating from 1800 years ago.

It’s sister branch, D4h3b consists of only one D4h3 lineage found in Eastern China.

Y Chromosomal DNA

The Y chromosome was determined to be haplogroup Q-L54.  Haplogroup Q and subgroup Q-L54 originated in Asia and two Q-L54 descendants predominate in the Americas: Q-M3 which has been observed exclusively in Native-Americans and Northeastern Siberians and Q-L54.

The tree researchers constructed is shown below.

Clovis Y

They estimate the divergence between haplogroups Q-L54 and Q-M3, the two major haplogroup Q Native lines, to be about 16,900 years ago, or from between 13,000 – 19,700.

The researchers shared with us the methodology they used to determine when their most common recent ancestor (MCRA) lived.

“The modern samples have accumulated an average of 48.7 transversions [basic mutations] since their MCRA lived and we observed 12 in Anzick.  We infer an average of approximately 36.7 (48.7-12) transversions to have accumulated in the past 12.6 thousands years and therefore estimate the divergence time of Q-M3 and Q-L54 to be approximately 16.8 thousands years (12.6ky x 48.7/36.7).”

Autosomal

They termed their autosomal analysis “genome-wide genetic affinity.”  They compared the Anzick individual with 52 Native populations for which known European and African genetic segments have been “masked,” or excluded.  This analysis showed that the Anzick individual showed a closer affinity to all 52 Native American populations than to any extant or ancient Eurasian population using several different, and some innovative and new, analysis techniques.

Surprisingly, the Anzick infant showed less shared genetic history with 7 northern Native American tribes from Canada and the Artic including 3 Northern Amerind-speaking groups.  Those 7 most distant groups are:  Aleutians, East Greenlanders, West Greenlanders, Chipewyan, Algonquin, Cree and Ojibwa.

They were closer to 44 Native populations from Central and South America, shown on the map below by the red dots.  In fact, South American populations all share a closer genetic affinity with the Anzick individual than they do with modern day North American Native American individuals.

Clovis autosomal cropped

The researchers proposed three migration models that might be plausible to support these findings, and utilized different types of analysis to eliminate two of the three.  The resulting analysis suggests that the split between the North and South American lines happened either before or at the time the Anzick individual lived, and the Anzick individual falls into the South American group, not the North American group.  In other words, the structural split pre-dates the Anzick child.  They conclude on this matter that “the North American and South American groups became isolated with little or no gene flow between the two groups following the death of the Anzick individual.”  This model also implies an early divergence between these two groups.

Clovis branch

In Eurasia, genetic affinity with the Anzick individual decreases with distance from the Bering Strait.

The researchers then utilized the genetic sequence of the 24,000 year old MA-1 individual from Mal’ta, Siberia, a 40,000 year old individual “Tianyuan” from China and the 4000 year old Saqqaq Palaeo-Eskimo from Greenland.

Again, the Anzick child showed a closer genetic affinity to all Native groups than to either MA-1 or the Saqqaq individual.  The Saqqaq individual is closest to the Greenland Inuit populations and the Siberian populations close to the Bering Strait.  Compared to MA-1, Anzick is closer to both East Asian and Native American populations, while MA-1 is closer to European populations.  This is consistent with earlier conclusions stating that “the Native American lineage absorbed gene flow from an East Asian lineage as well as a lineage related to the MA-1 individual.”  They also found that Anzick is closer to the Native population and the East Asian population than to the Tianyuan individual who seems equally related to a geographically wide range of Eurasian populations.  For additional information, you can see their charts in figure 5 in their supplementary data file.

I have constructed the table below to summarize who matches who, generally speaking.

who matches who

In addition, a French population was compared and only showed an affiliation with the Mal’ta individual and generically, Tianyuan who matches all Eurasians at some level.

Conclusions

The researchers concluded that the Clovis infant belonged to a meta-population from which many contemporary Native Americans are descended and is closely related to all indigenous American populations.  In essence, contemporary Native Americans are “effectively direct descendants of the people who made and used Clovis tools and buried this child,” covering it with red ochre.

Furthermore, the data refutes the possibility that Clovis originated via a European, Solutrean, migration to the Americas.

I would certainly be interested to see this same type of analysis performed on remains from the eastern Canadian or eastern seaboard United States on the earliest burials.  Pre-contact European admixture has been a hotly contested question, especially in the Hudson Bay region, for a very long time, but we have yet to see any pre-Columbus era contact burials that produce any genetic evidence of such.

Additionally, the Ohio burial suggests that perhaps the mitochondrial DNA haplogroup is or was more widespread geographically in North American than is known today.  A wider comparison to Native American DNA would be beneficial, were it possible. A quick look at various Native DNA and haplogroup projects at Family Tree DNA doesn’t show this haplogroup in locations outside of the ones discussed here.  Haplogroup Q, of course, is ubiquitous in the Native population.

National Geographic article about this revelation including photos of where the remains were found.  They can make a tuft of grass look great!

Another article can be found at Voice of America News.

Science has a bit more.