Are you confused about DNA matches and what they mean…different kinds of matches…from different vendors and combined results between vendors. Do you feel like lions and tigers and bears…oh my? You’re not alone.
As the vendors add more tools, I’ve noticed recently that along with those tools has come a significant amount of confusion surrounding matches and what they mean. Add to this issue confusion about the terminology being used within the industry to describe various kinds of matches. Combined, we now have a verbiage or terminology issue and we have confusion regarding the actual matches and what they mean. So, as people talk, what they mean, what they are trying to communicate and what they do say can be interpreted quite widely. Is it any wonder so many people are confused?
I reached out within the community to others who I know are working with autosomal results on a daily basis and often engaged in pioneering research to see how they are categorizing these results and how they are referring to them.
I want to thank Jim Bartlett, Blaine Bettinger, Tim Janzen and David Pike (in surname alphabetical order) for their input and discussion about these topics. I hope that this article goes a long way towards sorting through the various kinds of matches and what they can and do mean to genetic genealogists – and what they are being called. To be clear, the article is mine and I have quoted them specifically when applicable.
But first, let’s talk about goals.
One thing that has become apparent over the past few months is that your goals may well affect how you interpret data. For example, if you are an adoptee, you’re going to be looking first at your closest matches and your largest segments. Distant matches and small segments are irrelevant at least until you work with the big pieces. The theory of low hanging fruit, of course.
If your goal is to verify and generally validate your existing genealogy, you may be perfectly happy with Ancestry’s Circles. Ancestry Circles aren’t proof, as many people think, but if you’re looking for low hanging fruit and “probably” versus “positively,” Ancestry Circles may be the answer for you.
If you didn’t stop reading after the last sentence, then I’m guessing that “probably” isn’t your style.
If your goal is to prove each ancestor and/or map their segments to your DNA, you’re not going to be at all happy with Ancestry’s lack of segment data – so your confidence and happiness level is going to be greatly different than someone who is just looking to find themselves in circles with other descendants of the same ancestor and go merrily on their way.
If you have already connected the dots on most of your ancestry for the past 4 or 5 generations, and you’re working primarily with colonial ancestors and those born before 1700, you may be profoundly interested in small segment data, while someone else decides to eliminate that same data on their spreadsheet to eliminate clutter. One person’s clutter is another’s goldmine.
While, technically, the different types of tests and matches carry a different technical confidence level, your personal confidence ranking will be influenced by your own goals and by some secondary factors like how many other people match on a particular segment.
Let’s start by talking about the different kinds of matching. I’ve been working with my Crumley line, so I’ll be utilizing examples from that project.
Individual Matching, Group Matching and Triangulation
There is a difference between individual matching, group matching and triangulation. In fact, there is a whole spectrum of matching to be considered.
Individual matching is when someone matches you.
That’s great, but one match out of context generally isn’t worth much. There’s that word, generally, because if there is one thing that is almost always true, it’s that there is an exception to every rule and that exception often has to do with context. For example, if you’re looking for parents and siblings, then one match is all you need.
If this match happens to be to my first cousin, that alone confirms several things for me, assuming there is not a secondary relationship. First, it confirms my relationship with my parent and my parent’s descent from their parents, since I couldn’t be matching my first cousin (at first cousin level) if all of the lines between me and the cousin weren’t intact.
However, if the match is to someone I don’t know, and it’s not a close relative, like the 2nd to 4th cousins shown in the match above, then it’s meaningless without additional information. Most of your matches will be more distant. Let’s face it, you have a lot more distant cousins than close cousins. Many ancestors, especially before about 1900, were indeed, prolific, at least by today’s standards.
So, at this point, your match list looks like this:
Bridget looks pretty lonely. Let’s see what we can do about that.
Matching Additional People
The first question is “do you share a common ancestor with that individual?” If yes, then that is a really big hint – but it’s not proof of anything – unless they are a close relative match like we discussed above.
Why isn’t a single match enough for proof?
You could be related to this person through more than one ancestral line – and that happens far more than I initially thought. I did an analysis some time back and discovered that about 15% of the time, I can confirm a secondary genealogical line that is not related to the first line in my tree. There were another 7% that were probable – meaning that I can’t identify a second common ancestor with certainty, but the surname and location is the same and a connection is likely. Another 8% were from endogamous lines, like Acadians, so I’m sure there are multiple lines involved. And of those matches (minus the Acadians), about 10% look to have 3 genealogical lines, not just two. The message here – never assume.
When you find one match and identify one common genealogical line, you can’t assume that is how you are genetically related on the segment in question.
Ideally, at this point, you will find a third person who shares the common ancestor and their DNA matches, or triangulates, between you and your original match to prove the connection. But, circumstances are not always ideal.
What is Triangualtion?
Triangulation on the continuum of confidence is the highest confidence level achievable, outside of close relative matching which is evident by itself without triangulation.
Triangulation is when you match two people who share a common ancestor and all three of you match each other on that same segment. This means that segment descended to all three of you from that common ancestor.
This is what a match group would look like if Jerry matches both John and Bridget.
Example 1 – Match Group
The classic definition of triangulation is when three people, A, B and C all match each other on the same segment and share a known, identifiable common ancestor. Above, we only have two. We don’t know yet if John matches Bridget.
A matches B
A matches C
B matches C
This is what an exact triangulation group would look like between Jerry, John and Bridget. Most triangulation matches aren’t exact, meaning the start and/or end segment might be different, but some are exact.
Example 2 – Triangulation Group
It’s not always possible to prove all three. Sometimes you can see that Jerry matches Bridget and Jerry matches John, but you have no access to John or Bridget’s kits to verify that they also match each other. If you are at Family Tree DNA, you can run the ICW (in common with) tool to see if John and Bridget do match each other – but that tool does not confirm that they match on the same segment.
If the individuals involved have uploaded their kits to GedMatch, you have the ability to triangulate because you can see the kit numbers of your matches and you can then run them against each other to verify that they do indeed match each other as well. Not everyone uploads their kits to GedMatch, so you may wind up with a hybrid combination of triangulated groups (like example 2, above) and matching groups (like example 1, above) on your own personal spreadsheet.
Matching groups (that are not triangulated) are referred to by different names within the community. Tim Janzen refers to them as clusters of cousins, Blaine as pseudo triangulation and I have called them triangulation groups in the past if any three within the group are proven to be triangulated. Be careful when you’re discussing this, because matching groups are often misstated as triangulated groups. You’ll want to clarify.
Creating a Match List
Sometimes triangulation options aren’t available to us. For example, at Family Tree DNA, we can see who matches us, and we can see if they match each other utilizing the ICW tool, but we can’t see specifically where they match each other. This is considered a match group. This type of matching is also where a great deal of confusion is introduced because these people do match each other, but they are NOT (yet) triangulated.
What we know is that all of these people are on YOUR match list, but we don’t know that they are on each other’s match lists. They could be matching you on different sides of your DNA or, if smaller segments, they might be IBC (identical by chance.)
You can run the ICW (in common with) tool at Family Tree DNA for every match you have. The ICW tool is a good way to see who matches both people in question. Hopefully, some of your matches will have uploaded trees and you can peruse for common ancestors.
The ICW tool is the little crossed arrows and it shows you who you and that person also match in common.
You can run the ICW tool in conjunction with the ancestral surname in question, showing only individuals who you have matches in common with who have the Crumley surname (for example) in their ancestral surname list. This is a huge timesaver and narrows your scope of search immediately. By clicking on the ICW tool for Ms. Bridget, you see the list, below of those who match both the person whose account we are signed into and Ms. Bridget, below.
Another way to find common matches to any individual is to search by either the current surname or ancestral surnames. The ancestral surname search checks the surnames entered by other participants and shows them in the results box.
In the example above, all of these individuals have Crumley listed in their surnames. You can see that I’ve sorted by ancestral surname – as Crumley is in that search box.
Now, your match lists looks like this relative to the Crumley line. Some people included trees and you can find your common ancestor on their tree, or through communications with them directly. In other cases, no tree but the common surname appears in the surname match list. You may want to note those results on your match list as well.
Of course, the next step is to compare these individuals in a matrix to see who matches who and the chromosome browser to see where they match you, which we’ll discuss momentarily.
The next type of matching is when you have a group of people who match each other, but not necessarily on the same segment of DNA. These matching groups are very important, especially when you know there is a shared ancestor involved – but they don’t indicate that the people share the same segment, nor that all (or any) of their shared segments are from this particular ancestor. Triangulation is the only thing that accomplishes proof positive.
This ICW matrix shows some of the Crumley participants who have tested and who matches whom.
You can display this grid by matching total cM or by known relationship (assuming the individuals have entered this information) or by predicted relationship range. The total cMs shared is more important for me in evaluating how closely this person might be related to the other individual.
The Chromosome Browser
The chromosome browser at Family Tree DNA shows matches from the perspective of any one individual. This means that the background display of the 22 Chromosomes (plus X) is the person all of the matches are comparing against. If you’re signed in to your account, then you are the black background chromosomes, and everyone is being compared against your DNA. I’m only showing the first 6 chromosomes below.
You can see where up to 5 individuals match the person you’re comparing them to. In this case, it looks like they may share a common segment on chromosome 2 among several descendants. Of course, you’d need to check each of these individuals to insure that they match each other on this same segment to confirm that indeed, it did come from a common ancestor. That’s triangulation.
When you see a grouping of matches of individuals known to descend from a common ancestor on the same chromosome, it’s very likely that you have a match group (cluster of cousins, pseudo triangulation group) and they will all match each other on that same segment if you have the opportunity to triangulate them, but it’s not absolute.
For example, below we have a reconstructed chromosome 8 of James Crumley, the common ancestor of a large group of people shown based on matches. In other words, each colored segment represents a match between two people. I have a lot more confidence in the matches shown with the arrows than the single or less frequent matches.
This pseudo triangulation is really very important, because it’s not just a match, and it’s not triangulation. The more people you have that match you on this segment and that have the same ancestor, the more likely that this segment will triangulate. This is also where much of the confusion is coming from, because matching groups of multiple descendants on the same segments almost always do triangulate so they have been being called triangulation groups, even when they have not all been triangulated to each other. Very occasionally, you will find a group of several people with a common ancestor who triangulate to each other on this common segment, except one of a group doesn’t triangulate to one other, but otherwise, they all triangulate to others.
This situation has to be an error of some sort, because if all of these people match each other, including B, then B really must match D. Our group discussed this, and Jim Bartlett pointed out that these problem matches are often near the vendor matching threshold (or your threshold if you’re using GedMatch) and if the threshold is lowered a bit, they continue to match. They may also be a marginal match on the edge, so to speak or they may have a read error at a critical location in their kit.
What “in common with” matching does is to increase your confidence that these are indeed ancestral matches, a cousin cluster, but it’s not yet triangulation.
Ancestry has added another level of matching into the mix. The difference is, of course, that you can’t see any segment data at all, at Ancestry, so you don’t have anything other than the fact that you do match the other person and if you have a shakey leaf hint, you also share a common ancestor in your trees.
When three people match each other on any segment (meaning this does not infer a common segment match) and also share a common ancestor in a tree, they qualify to be a DNA Circle. However, there is other criteria that is weighted and not every group of 3 individuals who match and share an ancestor becomes a DNA Circle. However, many do and many Circles have significantly more than three individuals.
This DNA Circle is for Phebe Crumley, one of my Crumley ancestors. In this grouping, I match one close family group of 5 people, and one individual, Alyssa, all of whom share Phebe Crumley in their trees. As luck would have it, the family group has also tested at Family Tree DNA and has downloaded their results to GedMatch, but as it stands here at Ancestry, with DNA Circle data only…the only thing I can do is to add them to my match list.
In case you’re wondering, the reason I only added three of the 5 family members of the Abija group to my match list is because two are children of one of the members and their Crumley DNA is represented through their parent.
While a small DNA Circle like Phebe Crumley’s can be incorrect, because the individuals can indeed be sharing the DNA of a different ancestor, a larger group gives you more confidence that the relationship to that group of people is actually through the common ancestor whose circle you are a member of. In the example Circle shown below, I match 6 individuals out of a total of 21 individuals who are all interrelated and share Henry Bolton in their tree.
New Ancestor Discoveries
Ancestry introduced New Ancestor Discoveries (NADs) a few months ago. This tool is, unfortunately, misnamed – and although this is a good concept for finding people whose DNA you share, but whose tree you don’t – it’s not mature yet.
The name causes people to misinterpret the “ancestors” given to them as genuinely theirs. So far, I’ve had a total of 11 NADS and most have been easily proven false.
Here’s how NADs work. Let’s say there is a DNA Circle, John Doe, of 3 people and you match two of them. The assumption is that John Doe is also your ancestor because you share the DNA of his descendants. This is a critically flawed assumption. For example, in one case, my ancestors sister’s husband is shown as my “new ancestor discovery” because I share DNA with his descendants (through his wife, my ancestor’s sister.) Like I said, not mature yet.
I have discussed this repeatedly, so let’s just suffice it to say for this discussion, that there is absolutely no confidence in NADs and they aren’t relevant.
Ancestry recently added a Shared Matches function.
For each person that you match at Ancestry, that is a 4th cousin or closer and who has a high confidence match ranking, you can click on shared matches to see who you and they both match in common.
This does NOT mean you match these people through the same ancestor. This does NOT mean you match them on the same segment. I wrote about how I’ve used this tool, but without additional data, like segment data, you can’t do much more with this.
What I have done is to build a grid similar to the Family Tree DNA matrix where I’ve attempted to see who matches whom and if there is someone(s) within that group that I can identify as specifically descending from the same ancestor. This is, unfortunately, extremely high maintenance for a very low return. I might add someone to my match list if they matched a group (or circle) or people that match me, whose common ancestor I can clearly identify.
Shared Matches are the lowest item on the confidence chart – which is not to say they are useless. They can provide hints that you can follow up on with more precise tools.
Let’s move to the highest confidence tool, triangulation groups.
Of course, the next step, either at 23andMe, Family Tree DNA, through GedMatch, or some combination of each, is to compare the actual segments of the individuals involved. This means, especially at Ancestry where you have no tools, that you need to develop a successful begging technique to convince your matches to download their data to GedMatch or Family Tree DNA, or both. Most people don’t, but some will and that may be the someone you need.
You have three triangulation options:
- If you are working with the Family Inheritance Advanced at 23andMe, you can compare each of your matches with each other. I would still invite my matches to download to GedMatch so you can compare them with people who did not test at 23andMe.
- If you are working with a group of people at Family Tree DNA, you can ask them to run themselves against each other to see if they also match on the same segment that they both match you on. If you are a project administrator on a project where they are all members, you can do this cross-check matching yourself. You can also ask them to download their results to GedMatch.
- If your matches will download their results to GedMatch, you can run each individual against any other individual to confirm their common segment matches with you and with each other.
In reality, you will likely wind up with a mixture of matches on your match list and not everyone will upload to GedMatch.
Confirming that segments create a three way match when you share a common ancestor constitutes proof that you share that common ancestor and that particular DNA has been passed down from that ancestor to you.
I’ve built this confidence table relative to matches first found at Family Tree DNA, adding matches from Ancestry and following them to GedMatch. Fortunately, the Abija group has tested at all 3 companies and also uploaded their results to GedMatch. Some of my favorite cousins!
Spectrum of Confidence
Blaine Bettinger built this slide that sums up the tools and where they fall on the confidence range alone, without considerations of your goals and technical factors such as segment size. Thanks Blaine for allowing me to share it here.
These tools and techniques fall onto a spectrum of confidence, which I’ve tried to put into perspective, below.
I really debated how to best show these. Unfortunately, there is almost always some level of judgment involved. In some cases, like triangulation at the 3 vendors, the highest level is equivalent, but in other cases, like the medium range, it really is a spectrum from lowest to highest within that grouping.
Now, let’s take a look at our matches that we’ve added to our match list in confidence order.
As you would expect, those who triangulated with each other using some chromosome browser and share a common ancestor are the highest confidence matches – those 5 with a red Y. These are followed by matches who match me and each other but not on the same segment (or at least we don’t know that), so they don’t triangulate, at least not yet.
I didn’t include any low confidence matches in this table, but of the lowest ones that are included, the shakey leaf matches at Ancestry that won’t answer inquiries and the matches at FTDNA who do share a common surname but didn’t download their information to be triangulated are the least confident of the group. However, even those lower confidence matches on this chart are medium, meaning at Ancestry they are in a Circle and at FTDNA, they do match and share a common surname. At Family Tree DNA, they may eventually fall into a triangulation group of other descendants who triangulate.
As always, there are some gotchas. As someone said in something I read recently, “autosomal DNA is messy.”
Endogamous populations are just a mess. The problem is that literally, everyone is related to everyone, because the founder population DNA has just been passed around and around for generations with little or no new DNA being introduced.
Therefore, people who descend from endogamous populations often show to be much more closely related than they are in a genealogical timeframe.
Secondly, we have the issue pointed out by David Pike, and that is when you really don’t know where a particular segment came from, because the segment matches both the parents, or in some cases, multiple grandparents. So, which grandparent did that actual segment that descended to the grandchild descend from?
For people who are from the same core population on both parent’s side, close matches are often your only “sure thing” and beyond that, hopefully you have your parents (at least one parent) available to match against, because that’s the only way of even beginning to sort into family groups. This is known as phasing against your parents and while it’s a great tool for everyone to use – it’s essential to people who descend from endogamous groups. Endogamy makes genetic genealogy difficult.
In other cases, where you do have endogamy in your line, but only in one of your lines, endogamy can actually help you, because you will immediately know based on who those people match in addition to you (preferably on the same segment) which group they descend from. I can’t tell you how many rows I have on my spreadsheet that are labeled with the word “Acadian,” “Brethren” and “Mennonite.” I note the common ancestor we can find, but in reality, who knows which upstream ancestor in the endogamous population the DNA originated with.
Now, the bad news is that Ancestry runs a routine that removes DNA that they feel is too matchy in your results, and most of my Acadian matches disappeared when Ancestry implemented their form of population based phasing.
Identical by Population
There is sometimes a fine line between a match that’s from an ancestor one generation further back than you can go, and a match from generations ago via DNA found at a comparatively high percentage in a particular population. You can’t tell the difference. All you know is that you can’t assign that segment to an ancestor, and you may know it does phase against a parent, so it’s valid, meaning not IBC or identical by chance.
Yes, identical by population segment matching is a distinct problem with endogamy, but it can also be problematic with people from the same region of the world but not members of endogamous populations. Endogamy is a term for the timeframe we’re familiar with. We don’t know what happened before we know what happened.
From time to time, you’ll begin to see something “odd” happened where a group of segments that you already have triangulated to one ancestor will then begin to triangulate to a second ancestor. I’m not talking about the normal two groups for every address – one from your Mom’s side and one from your Dad’s. I’m talking, for example, when my Mom’s DNA in a particular area begins to triangulate to one ancestral group from Germany and one from France. These clearly aren’t the same ancestors, and we know that one particular “spot” or segment range that I received from her DNA can only come from one ancestor. But these segment matches look to be breaking that rule.
I created the example below to illustrate this phenomenon. Notice that the top and bottom 3 all match nicely to me and to each other and share a common ancestor, although not the same common ancestor for the two groups. However, the range significantly overlaps. And then there is the match to Mary Ann in the middle whose common ancestor to me is unknown.
Generally, we see these on smaller segment groups, and this is indicative that you may be seeing an identical by population group. Many people lump these IBP (identical by population) groups in with IBC, identical by chance, but they aren’t. The difference is that the DNA in an IBP group truly is coming from your ancestors – it’s just that two distinct groups of ancestors have the same DNA because at some point, they shared a common ancestor. This is the issue that “academic phasing” (as opposed to parental phasing) is trying to address. This is what Ancestry calls “pileup areas” and attempts to weed out of your results. It’s difficult to determine where the legitimate mathematical line is relative to genealogically useful matches versus ones that aren’t. And as far as I’m concerned, knowing that my match is “European” or “Native” or “African” even if I can’t go any further is still useful.
Think about this, if every European has between 1 and 4% Neanderthal DNA from just a few Neanderthal individuals that lived more than 20,000 years ago in Europe – why wouldn’t we occasionally trip over some common DNA from long ago that found its way into two different family lines.
When I find these multiple groupings, which is actually relatively rare, I note them and just keep on matching and triangulating, although I don’t use these segments to draw any conclusions until a much larger triangulated segment match with an identified ancestor comes into play. Confidence increases with larger segments.
This multiple grouping phenomenon is a hint of a story I don’t know – and may never know. Just because I don’t quite know how to interpret it today doesn’t mean it isn’t valid. In time, maybe its full story will be revealed.
ROH – Runs of Homozygosity
Autosomal DNA tests test someplace over 500,000 locations, depending on the vendor you select. At each of those locations, you find a value of either T, A, C or G, representing a specific nucleotide. Sometimes, you find runs of the same nucleotide, so you will find an entire group of all T, for example. If either of your parents have all Ts in the same location, then you will match anyone with any combination of T and anything else.
In the example above, you can see that you inherited T from both your Mom and Dad. Endogamy maybe?
Sally, although she will technically show as a match, doesn’t really “match” you. It’s just a fluke that her DNA matches your DNA by hopping back and forth between her Mom’s and Dad’s DNA. This is not a match my descent, but by chance, or IBC (identical by chance.) There is no way for you to know this, except by also comparing your results to Sally’s parents – another example of parental phasing. You won’t match Sally’s parents on this segment, so the segment is IBC.
Now let’s look at Joe. Joe matches you legitimately, but you can’t tell by just looking at this whether Joe matches you on your Mom’s or Dad’s side. Unfortunately, because no one’s DNA comes with a zipper or two sides of the street labeled Mom and Dad – the only way to determine how Joe matches you is to either phase against Joe’s parents or see who else Joe matches that you match, preferable on the same segment – in other words – create either a match or ICW group, or triangulation.
Everyone is in agreement about one thing. Large segments are never IBC, identical by chance. And I hate to use words like never, so today, interpret never to mean “not yet found.” I’ve seen that large segment number be defined both 13cM and 15cM and “almost never” over 10cM. There is currently discussion surrounding the X chromosome and false positives at about this threshold, but the jury is still out on this one.
Most medium segments hold true too. Medium segment matches to multiple people with the same ancestors almost always hold true. In fact, I don’t personally know of one that didn’t, but that isn’t to say it hasn’t happened.
By medium segments, most people say 7cM and above. Some say 5cM and above with multiple matching individuals.
As the segment size decreases, the confidence level decreases too, but can be increased by either multiple matches on that segment from a common proven ancestor or, of course, triangulation. Phasing against your parent also assures that the match is not IBD. As you can see, there are tools and techniques to increase your confidence when dealing with small segments, and to eliminate IBC segments.
The issue of small segments, how and when they can be utilized is still unresolved. Some people simply delete them. I feel that is throwing the baby away with the bathwater and small segments that triangulate from a common ancestor and that don’t find themselves in the middle of a pileup region that is identical by population or that is known to be overly matchy (near the center of chromosome 6, for example) can be utilized. In some cases, these segments are proven because that same small segment section is also proven against matches that are much larger in a few descendants.
Tim Janzen says that he is more inclined to look at the number of SNPs instead of the segment size, and his comfort number is 500 SNPs or above.
The flip side of this is, as David Pike mentioned, that the fewer locations you have in a row, the greater the chance that you can randomly match, or that you can have runs of heterozygosity.
No one in our discussion group felt that all small segments were useless, although the jury is still out in terms of consensus about what exactly defines a small segment and when they are legitimate and/or useful. Everyone of us wants to work towards answers, because for those of us who are dealing with colonial ancestors and have already picked the available low hanging fruit, those tantalizing small segments may be all that is left of the ancestor we so desperately need to identify.
For example, I put together this chart detailing my matching DNA by generation. Interesting, I did a similar chart originally almost exactly three years ago and although it has seemed slow day by day, I made a lot of progress when a couple of brick walls fell, in particular, my Dutch wall thanks to Yvette Hoitink.
If you look at the green group of numbers, that is the amount of shared DNA to be expected at each level. The number of shared cMs drops dramatically between the 5th and 6th generation from 13 cM which would be considered a reasonable matching level (according to the above discussion) at the 5th generation, and 3.32 cM at the 6th generation level, which is a small segment by anyone’s definition.
The 6th generation was born roughly in 1760, and if you look to the white grouping to the right of the green group, you can see that my percentage of known ancestors is 84% in the 5th generation, 80% in the 6th generation, but drops quickly after that to 39, 22 and 3%, respectively. So, the exact place where I need the most help is also the exact place where the expected amount of DNA drops from 13 to 3.32 cM. This means, that if anyone ever wants to solve those genealogical puzzles in that timeframe utilizing genetic genealogy, we had better figure out how to utilize those small segments effectively – because it may well be all we have except for the occasional larger sticky segment that is passed intact from an ancestor many generations past.
From my perspective, it’s a crying shame that Ancestry gives us no segment data and it’s sad that 23andMe only gives us 5cM and above. It’s a blessing that we can select our own threshold at GedMatch. I’m extremely grateful that FTDNA shows us the small segment matches to 1cM and 500 SNPs if we also match on 20cM total and at least one segment over 7cM. That’s a good compromise, because small segments are more likely to be legitimate if we have a legitimate match on a larger segment and a known ancestor. We already discussed that the larger the matching segment, the more likely it is to be valid. I would like to see Family Tree DNA lower the matching threshold within projects. Surname projects imply that a group of people will be expected to match, so I’d really like to be able to see those lower threshold matches.
I’m hopeful that Family Tree DNA will continue to provide small segment information to us. People who don’t want to learn how to use or be bothered with small segments don’t have to. Delete is perfectly legitimate option, but without the data, those of us who are interested in researching how to best utilize these segments, can’t. And when we don’t have data to use, we all lose. So, thank you Family Tree DNA.
Coming Full Circle
This discussion brings us full circle once again to goals.
Goals change over time.
My initial reason for testing, the first day an autosomal test could be ordered, was to see if my half-brother was my half-brother. Obviously for that, I didn’t need matching to other people or triangulation. The answer was either yes or no, we do match at the half-sibling level, or we don’t.
He wasn’t. But by then, he was terminally ill, and I never told him. It certainly explained why I wasn’t a transplant match for him.
My next goal, almost immediately, was to determine which if either my brother or I were the child of my father. For that, we did need matching to other people, and preferably close cousins – the closer the better. Autosomal DNA testing was new at that time, and I had to recruit cousins. Bless those who took pity on me and tested, because I was truly desperate to know.
Suffice it to say that the wait was a roller coaster ride of emotion.
If I was not my father’s child, I had just done 30+ years of someone else’s genealogy – not a revelation I relished, at all.
I was my father’s child. My brother wasn’t. I was glad I never told him the first part, because I didn’t have to tell him this part either.
My goal at that point changed to more of a general interest nature as more cousins tested and we matched, verifying different lineages that has been unable to be verified by Y or mtDNA testing.
Then one day, something magical happened.
One of my Y lines, Marcus Younger, whose Y line is a result of a NPE, nonparental event, or said differently, an undocumented adoption, received amazing information. The paternal Younger family line we believed Marcus descended from, he didn’t. However, autosomal DNA confirmed that even though he is not the paternal child of that line, he is still autosomally related to that line, sharing a common ancestor – suggesting that he may have been born of a Younger female and given that surname, while carrying the Y DNA of his biological father, who remains unidentified.
Amazingly, the next day, a match popped up that matched me and another Younger relative. This match descended not from the Younger line, but from Marcus Younger’s wife’s alleged surname family. I suddenly realized that not only was autosomal DNA interesting for confirming your tree – it could also be used to break down long-standing brick walls. That’s where I’ve been focused ever since.
That’s a very different goal from where I began, and my current goal utilizes the tools in a very different way than my earlier goals. Confidence levels matter now, a great deal, where that first day, all I wanted was a yes or no.
Today, my goal, other than breaking down brick walls, is for genetic genealogy to become automated and much easier but without taking away our options or keeping us so “safe” that we have no tools (Ancestry).
The process that will allow us to refine genetic genealogy and group individuals and matches utilizing trees on our desktops will ultimately be the key to unraveling those distant connections. The data is there, we just have to learn how to use it most effectively, and the key, other than software, is collaboration with many cousins.
Aside from science and technology, the other wonderful aspect of autosomal DNA testing is that is has the potential to unite and often, reunite families who didn’t even know they were families. I’ve seen this over and over now and I still marvel at this miracle given to us by our ancestors – their DNA.
So, regardless of where you fall on the goals and matching confidence spectrum in terms of genetic genealogy, keep encouraging others to test and keep reaching out and sharing – because it takes a village to recreate an ancestor! No one can do it alone, and the more people who test and share, the better all of our chances become to achieve whatever genetic genealogy goals we have.