Before we get into the amazing connection we’ve made recently, here’s a quick update on the broader collection of 2500 glass plate negatives we were able to rescue that comprise the surviving images from the Home Portrait Studio. We talked about how saved these plates earlier, and about how we intend to scan and share all of these images publicly (Our project to save a piece of Racine, Wisconsin history, Part 1 – Getting Started), but in the months since our last update we found out it would be nearly impossible to use a flatbed scanner to capture those thousands of images without it taking years to complete. Fully processing 50 negatives was taking about 8 hours. We’ve since bought a bunch of equipment to instead photograph each negative digitally, and invested in software that allows us to now fully process those same 50 images in just under an hour. We expect that with this new process we’ll the entire first box up and shared next month (440 images), and we’ll provide much more detail as soon as they complete.
In the meantime, through an amazing set of coincidences we determined the name of the man in the WWI uniform we posted originally, met his grandson, and learned more about Frank Stritesky who owned the Home Portrait Studio.
The photo is William H Rastall (born in 17 Jun in Racine, Wisconsin) and who served in the US Army from December 1917 to January 1919. William was the brother of Frank’s wife Anne, and lived in the same neighborhood.
Just days after we first shared these images on the “Racine History” Facebook group, and on this blog, William’s grandson Michael began searching the Internet to buy an original or reproduction of the patch on William’s uniform. The photo of William with the 119th patch was a family treasure that had been passed down.
Michael’s first search turned up our scan, posted to a military insignia message board that we’d used to try and narrow down the timeframe that image was taken. Michael has prints of this family heirloom, and figured that the negatives were in the home that housed the studio which was owned by Frank’s daughter Betty, so he was floored to see a full-frame version of the picture randomly by a stranger on the Internet!
He reached out the next day, and after exchanging texts and phone calls, it turned out we were close enough for lunch, and got to meet and exchange stories. Michael was able to share many of the family pictures that were taken by Frank over the years.
The image we first published of William was almost certainly taken in 1918, at a time when Frank was just getting Home Portrait Studio up and running, and during that time he’d often take photos of family to practice/build his portfolio. William married after returning home from his WWI service, and he and his wife Alice had one son, Patric who had a life-long interest in photography owning back to his Uncle Frank. Frank had let Patric work the cameras from time-to-time when he was younger, and Patric’s interest eventually rubbed off on his son Michael, who works as a professional photographer in the Chicago Suburbs (Michael Rastall Photography).
Patric and his wife had visited Betty decades ago hoping to salvage the remaining negatives and maybe some of the studio gear, but Betty wasn’t interested in letting anything go. Given the condition they were being stored in there was little hope they survived after Betty’s passing, so it came as a complete shock to the family that they were seeing the light of day. With any luck, as we continue through the 6 boxes we saved they we’ll find more of those family treasures.
We’re also hopeful we can eventually reunite many more families with these amazing images of their ancestors, but for now we’ve at least made that first link!
It’s rare that we can spot trends emerging, but we’re going to take a quick victory lap this week because we saw Ancestry.com’s ThruLines coming. We called it out…twice! And now that it’s arrived it feels like the “killer app” for genealogical DNA.
The good news is that we as serious users can avoid the downfalls, and use the predictive part of this feature to do the research for us, but we must immediately attach the citations to any newly added ancestor.
Ancestry has finally harnessed predictive technology in a very effect feature with the release of ThruLines.
At it’s essence ThruLines a new graphical way to show HOW you’re related to your DNA matches. This is long overdue, and while the old way of clicking on a direct match and seeing the path from your kit to the most recent common ancestor (MCRA) worked, it was limited (we had to dig into each match with 3 clicks to see the path) and it was totally devoid of any context. Was there a brother of this tester that also matches? Did they have a 1st cousin that also tested that in-turn matches our tests? You just had to click through each test to find out.
But, the real power in ThruLines isn’t the graphical change, it’s that it’s using predictive algorithms to scour both Public AND Private trees, to greatly narrow down where another DNA match is likely to fall in your tree. That’s right, those close relatives we see in our “DNA Matches” screens that are just dead ends because they have Private trees and don’t reply to Ancestry messages are now likely to be mapped in ThruLines.
Our first discovery
“Lynne” is solid 3-4th cousin match (67cM) to Michael’s father, and through all of the techniques we’ve discussed previously, we’ve narrowed down that our MCRA is likely to be Wesley and Jane Tradewell. This is the same Tradewell line that is one of our large brickwalls, and so the more data we have for this branch the better. Lynne entered a small tree at some point, but she left all of her named ancestors living, so they appear “Private” and we have almost nothing to go on when trying to link her to our tree.
When we opened ThruLines for the first time, we understood right away that each of the photos we were seeing were MCRA’s, and clicking on Wesley Tradewell, we immediately understood the power of this tool. There was Lynne, mapped for us, with some information still private but it greatly narrowed down the line through which we matched. Knowing that she likely matches through William Humphry Tradewell removed 2 generations of likely matches, and narrowed down our search to children from William’s daughters. Even more powerful however is that we’re in regular contact with family who is likely Lynne’s 1st Cousin, Once Removed. We sent a quick email to that person, they confirmed Lynne’s lineage, and we’d filled in another DNA match. Actually, it was two, because we had the same issue with “Jonas667” (2 relative tree, both living/Private), and it was resolved in the same way.
All of our efforts to shrub out William Humphry Tradewell’s children had failed up to this point (no census, no obituaries, no Public Trees, etc.), so we had only one daughter tentatively identified. It would have taken significant work to break down the matches to Lynne/Jonas667 by building out each of those trees, and since we’d already tried diligently and failed, it might never have been done. But ThruLines broke through on the first click.
Now, this is cannot be stated more clearly: ThruLines are at best speculative “hints” that can guide your work in very effective new ways, but they do not create evidence nor can we be sure they even contain proof of anything. They are like user trees in that manner…and for good reason, they are built entirely on user trees.
We expect one day brickwalls will be broken down by these tools while we’re sound asleep.
But the way the tool narrowed down these matches makes it much easier to prove them out. We know exactly where to start now, where last week we were stumped.
Half of our tree traces their roots to enslaved African ancestors, and the second discovery we made was that ThruLines would give us suggestions even if there were 2 generations separating supposed ancestors. In the example we saw as we clicked through Michael’s maternal grandmother’s MCRA’s showed us an African-American GGM that was born in 1879, and no evidence of who her parents were. This is very common…to get to/near the 1870 wall for those of African decent, but no good leads on the generation previous. In this case however, we have a new hint: two identified generations of European ancestors, and two unidentified generations after them, leading to a link to the known Fanny Johnson. This is a highly speculative connection, and it will take considerable work to prove/disprove it going forward, but it’s at least a lead and it’s based on at least a little bit of conjecture. It may not be anything, but it also could be one of those rare finds that links one of our African ancestors back a few generations closer to their enslavement, as well as identifying the slave owner that contributed to our genetic make up.
Going forward, this could literally revolutionize both genetic genealogy as well as standard genealogy. Artificial Intelligence and matching algorithms can not only see patterns much better than any human can, they can do it faster while analyzing more data than we can ever hope to review in our lifetimes. We can see that in the future, when a new AncestryDNA kit is processed and put online, the user will see a large tree of matches and MCRA’s as their first few of the results, instead of a list of 4000+ matches they have to map one at a time.
Also, imagine a day when they use these tools to validate evidence of each users’ Public tree for instance, looking for clearly incorrect data/relationships and flag it for users. At the very least they can rate that “source” tree as unreliable, and bring better sourced trees to the forefront. These tools could easily allow the power of individual trees, while also bring them all into line with known facts, and start matching them in ways we can’t imagine.
Going back to our Tradewell example, our brickwall is around Reuben Tradewell and the one piece of evidence that his father might be “Jakin” from Connecticut…but the trail goes cold. Tools like this, however, point to the power that’s coming where some other groups of genealogists and family historians have a mystery “Jakin/Jacob” from Connecticut that they have sourced generations back, but don’t know his disposition. We expect one day brickwalls will be broken down by these tools while we’re sound asleep.
(Note: As always, we receive no financial benefit or consideration for any product or service we review/recommend/discuss here. Everything we discuss is our opinion alone, and we talk about it because we use it.)
When we initially started this blog, one of the first topics we covered was our standard genealogy toolkit (How to: Getting started researching your family tree) that included everything we though people would need to successfully start getting serious with this hobby, and ease folks into more advanced work. Our suggestions included Tony Burrough’s Black Roots as well Elizabeth Shown Mills’ Evidence Explained, and now Kenyatta D. Berry’s The Family Tree Toolkit is a strong addition to that list. In addition to being an essential resource, it’s a wonderful read.
The Family Tree Toolkit finds that balance of storytelling, emotional connection, and practical research examples in a way we can only envy.
From a practical standpoint, her detailed list of research resources (often state-by-state) is pretty consistently spot on for a deep dive into each subject. It’s so complete, and as hobbyists who have spent nearly 8 years doing this work, we found so many additional resources it took much longer than it should have to finish the book. We’d swear that when we read the next section, we WOULDN’T dive into one of the suggested sources for that section. We’d just make notes and come back. It never worked, and we’d spend the next 2-3 days checking out new sources! If we had this book 8 years ago, and we took the time to plan our research back then, we would be SO much further on this journey. We found a lot just doing searches and lucking into things, but if we targeted the correct sources from the beginning, it would have been so much more effective, and we’re now consulting The Family Tree Toolkit as we continue our research.
The risk with these printed texts that catalog research sources is that they will grow stale with time, and the book loses it’s value, but each of the resources here seem to have been picked to be resistant to aging. Sites like familysearch.org will be around as long as the LDS church is around (essentially, forever), and other sites tend to be big, well funded, and the collections listed are more likely to grow over time. It’s a better bet than not that the book will be an essential reference guide well into the time Ms. Berry issues her first revision.
But another reason to not focus on the nature of reference aging is that the personal journey stories and examples of Ms. Berry’s work would have made this an essential read on their own. The Family Tree Toolkit finds that balance of storytelling, emotional connection, and practical research examples in a way we can only envy. Not that our passion is ever waning, but there is a thread of deep truth that runs through her stores that not only reminds us why we’re doing this work, it re-inspired us to make the effort to make physical connections to the data we’re gathering.
For example, take this passage where she talks about her first trip to an ancestral home in Madison County, Virginia:
“As I explored the grounds, I looked out to the neighboring property and realized that I was walking in the footsteps of my ancestors. More than 130 years ago, they had stood where I was standing, and as I closed my eyes, I could almost hear their voices in the distance.”
That was a moving section that stuck with me for days…the profound nature of smelling the air your ancestors smelled, felt the same earth together under our feet as they did, had our heart filled with the same joy theirs must have looking at the same view we’re seeing. About a week later as we drove through my paternal ancestral home of Antigo, Wisconsin and passed my Great Grandfather’s E. A. Morse’s office….driving up Superior Street and coming to the corner of First Avenue, where he would have walked 1000’s of times on his way home, passing the same houses that still stand, the old service station that is right where its always been, up to their house which I still remember fondly, there’s a deep feeling of connection and home I shared with someone I only know from photographs, documents, and family stories. And I immediately was thinking of passages from Ms. Berry’s book.
Beyond that, thinking of my wife who is also descended from enslaved Africans, I understood the impact the lack of that connection she must feel. How part of this work, for her, is to find that natural connection to history and family. Seeking that profound moment she described has literally refocused our efforts to prove those links, and then stand on the same ground my wife’s family stood on.
Kenyatta D. Berry’s combination of a great compilation of research sources and deep, moving personal storytelling, makes The Family Tree Toolkit an essential part of our work, and our library.
We promised to keep this series as science-free as possible, and instead focus on the practical use of AncestryDNA tests to identify your ancestors. We’re going to keep that promise here, but we want to say a few words about other types of DNA tests you can’t get from Ancestry, and how xDNA, yDNA, and mtDNA can be useful! Just remember, we’re generalizing a bit here, and if you want the detailed science behind all of this, Google has many great reads.
yDNA and mtDNA
yDNA and mtDNA come only from your father and your mother, respectively, and change very little over the generations. These tests are often written off in the genealogical community, because they won’t, by themselves, lead you to how you are matched with someone, or how many generations back you might match them.
For example, if our Michael has a yDNA test and he matches “Frank” who shares the same yDNA…it tells us next to nothing. From the test we know that on Michael’s paternal line we have proved he’s matched to Frank…but there’s no way to tell how. It could be 1000 years ago we all had a MRCA, or it could be that Frank’s 4xGGF was a brother to ours, but there’s no way that kind of range will narrow it down by itself.
There are two uses of yDNA and mtDNA, however, that makes these some of the most powerful tests you can take:
Unlike “ethnicity” estimates we see from all the major testers, yDNA and mtDNA can be very effective in pinpointing very accurately the location of your ancestors on the planet. The standard (Autosomal) DNA tests from Ancestry rely on a small global sample of historical DNA (16,000 samples currently), and human created Family Trees, to mathematically try and guess where our ancestors were 800-1000 years ago. They are looking for little shreds of DNA to trace back, and it’s very small amounts because Autosomal DNA gets cut in 1/2 for each side of a lin ever generation. However y/mtDNA doesn’t change over the generations and so we know very accurately where those ancestors were, based on where the bodies were found. This is especially important for African American genealogy, when there are nearly no records of origin before our ancestors were taken from Africa. These tests can be very accurate, and place your ancestral group in to very small physical and/or social (tribal) locations.
Brick wall research
In our example above, we know for a scientific fact that Michael and Frank share an MCRA along their paternal line. The same is true for women who have an mtDNA match. While that again doesn’t help us much if we have no information, it’s invaluable if we have a good guess on how we’re related. Let’s go back to our DNA Painter walkthrough to see how we wish we had yDNA and mtDNA tests.
To recap from last week’s post, we have two lines of DNA tests that we know are connected, and we have narrowed down the MCRA for both a cluster of AncestryDNA matches and on our line, but we don’t know how they connect. So, we have two couples (Jacob/Maria Kupsch, and Joseph/Dorothy Haasl) that we know match, most likely 2-3 generations above them. Each of them have 8 potential match relatives, and we have 4 known relatives, so we’re facing 32 ancestors that might be our MCRA.
But, if we can confirm the y/mtDNA from those 4 relatives, whom all died over 100 years ago, because that DNA doesn’t change between generations. That means a direct male relative from Jacob (say his son’s, son’s, son’s, son’s DNA) will confirm Jacob’s yDNA. Same for Maria, and a direct female relative. If we could yDNA test relatives of both Jacob and Joseph, and mtDNA for both Maria and Dorothy we would have about a 25% chance of finding an immediate match. And, if say Maria and Dorothy share the same mtDNA we just figured out we need to focus our research only on both of their maternal lines to make our match. If we don’t find that match, we just eliminated 25% of our potential match points, so now instead of building out 32 ancestors to find our match, we’re down to 24. But even better, if we can go one level up and do the same thing, we can eventually narrow this down to where we share an MCRA.
It would be highly unlikely we could ever build out a family match with xDNA, and the cM you share with someone tells you almost nothing about close of a match you are with them. The main value of xDNA is if you do match someone, it narrows down your link to that match in a very powerful way. xDNA is inherited in a unique pattern that going back several generations can eliminate more than 50% of your tree as a potential match.
Women will inherit an X chromosome from both their mother and their father, but men will inherit an X from only their mother. Going back to High School Biology, we quickly remembered that women have an XX chromosome, while men have XY!
But, the value for us comes in when we build out our potential ancestor’s chart, using that inheritance pattern. So, if we have a female test subject who has an unknown xDNA match, we know it’s not from her Father’s Father’s line because men only inherit their X from their mothers. Going back 2 generations, we just eliminated 25% of the potential matches. If you know, from other research, that this unknown match is on their father’s line, you just confirmed it’s on the father’s mother’s line.
You won’t see a lot of xDNA matches, but when you do, Google one of the many xDNA inheritance fan charts, and start to see if you can eliminate suspects in how you match. It could bring you much closer to where to hunt for your MCRA.
Just know that all of this work will have to be in GEDmatch however, since AncestryDNA doesn’t provide any information on the details of your genetic matches, and none of the tools needed to view/manage this information.
In this installment we’re going to walk through a key tool to help narrow down where to research when you have AncestryDNA tests that match your family, but despite your research you’re not sure where they match. DNA Painter has a great tool called What are The Odds that gives us the probability of where these unmatched lines link up with our own.
We’re using a real set of unknown matches for this example. Emma Kupps (1879-1953) is a one of our favorite ancestors. She was born and raised the various logging communities that sprang up in North Central Wisconsin in the late 1800’s, but her family settled in Antigo where she graduated from Antigo High School. Within a few years she would married a logger Daniel Leonard (1868-1924), who would soon become Antigo’s Fire Chief, and years later be elected Sheriff of Langlade Coounty, Wisconsin. During his term Dan became ill with cancer, and succumbed with a significant portion of this term remaining. The governor of Wisconsin appointed Emma to the position of Sheriff to complete her late husband’s term, and she became the first woman in Wisconsin to hold the office. (Langlade Co. Historical Society)
DNA Painter has greatly narrowed down where we’re targeting our on-going research to finally break down this brick wall.
But, to family historians, she’s also near the end of a line that is a classic brick wall. Her father died young, and there’s nothing but a couple of records that indicate only the names of his parents. Plus, they are the only lines in our family that come from Bohemia, so it has the combined brick walls of classic genealogy and DNA results.
We’ve identified a group of AncestryDNA matches that have strong Bohemian roots and match descendants of Emma. We used Michael’s Great Uncle as our target DNA match, since he’s the oldest generation tested on that line, and we built a master tree that links as many of the unknown DNA matches as we could. We ended up with 8 AncestryDNA matches that we could link together in a cluster.
The cluster all share Jacob Haasl and Dorothy (Johannek) Haasl as their MCRA, but we haven’t been able to build a link between Great Uncle Leonard and the Haasl’s. So, we’re going to turn to DNApainter’s “What are the Odds” tool, to help identify where we’re most likely linked to the cluster.
When you open “What Are the Odds?”, it will present a box for the most recent common ancestors (MCRA). The options are to “Edit Names”, “Add Child”, or “Add Parent”. In this case, we’re going to edit the name, and add the cluster’s MCRA, Joseph and Dorothea Haasl. When we enter that information, we’re presented with the same 3 choices, but this time we’re going to start building a line to one of the DNA matches but selecting “Add Child” and entering the name of the child that makes up the first step to our DNA match. At first we were surprised how quickly we built out a tree, but it’s because we’re not entering all the data we’d need for a regular tree, just the names!
When we reached a DNA match we entered the cM value that matches our known DNA test. We repeated this step for as many matches as we’ve identified. This works well with a single match, but better with more. In our case we identified 8 matches, so we’re built them all out. Now we’ll really see the power of this tool.
Now that we’ve entered what’s known, it’s time to start mapping out our guesses. In fact, the entire purpose of this tool is to compare the likelihood of at least 2 hypotheses matching the entered cM, and from those likelihoods we can focus on where it’s most likely we all share a most MCRA.
The most likely connection for Jacob and Mary Keips’ line is her parents. We don’t know her maiden name, or birth date, but if we guess that she was born in 1820-1825 it’s reasonable to guess she is a sibling of either Jacob Haasl or Dorothy (Johannek) Haasl, so let’s build that out as option 1. We’ll add an “Unknown 3xGGP” to Joseph and Dorothy, and add a child called Jacob/Mary (because it could be either!). From there we’ll build down to the Great Uncle that is the known DNA match, and select “Use as Hypothesis”.
It shows us a probability of “1” because DNA painter doesn’t show you raw percentages, it shows you comparative probability of one match vs. another. For example, if you enter two hypotheses and one returns “1” and the other returns “2”, we’ll know the second one is twice as likely as the first. In this case, we have no other hypotheses entered, so it shows just a 1.
Given the cM match, it’s most likely that we match the cluster with Great Uncle Leonard’s 3x to 5x GGP’s, so we built out the same line as above, but this time with one more unknown ancestor above Jacob/Dorothy Keips, which would then make Uncle’s MCRA a 4xGGP.
When we built that out, and selected the second “Great Uncle Leonard” as a hypothetical, it soared to a whopping score of “1174” vs. the first “Great Uncle Leonard!! Given that we have 1174 for one possible link and 1 for the other, DNA painter just told us that while not impossible, we’re looking for a 4xGGP as our MCRA, not 3xGGP. Not great news, since now we have to go at least two more generations back, and to build this match back further we’re going to have to dig deep into 18th Century European genealogical records. That’s not our strong suit. But, at least now we have a clear picture of where we’re looking to link these groups.
Since the range of likely Great Grandparents is 3x-5x, we then built this hypothetical out to our match’s 5xGGP, and we see the same score of 1174 from a hypothetical 5xGGP. That means it’s equally likely that our link to this cluster of match is through our Great Uncle Leonard’s 4xGGP or this 5xGGP, but it’s almost certainly NOT through his 3xGGP.
While in some ways this is disappointing, and we’d hoped to come through with a match, this is actually a huge piece of this brickwall puzzle. When we started the work on this DNA cluster we knew that John Keips/Kupps had migrated from Bohemia and, at the time of his death, his wife thought his father was Jacob D. Kupps when she filled out her husband’s death certificate. From their marriage certificate we knew John’s mother, and Jacob’s wife, was Mary. We also knew we had a large cluster of DNA matches who came from the area of Bohemia.
Just by going through that cluster, building out a central tree that links them all, we found a great lead that likely shows John’s arrival information, along with approximate birth years for Jacob, Mary, and John…as well as John’s previously unknown siblings who seem to have a long history together in the US, and left many records. That means instead of having exhausted all the on-site research we could do on the John’s line, we now have a large number of leads to follow and see if we can push back another generation from both Jacob and Mary. We now know enough to start targeting death certificates for both, which may contain critical names, as well as 6 more marriage/death certificates to look for Mary’s maiden name, as well pieces of evidence that link our Jacob to the arrival Jacob. And, DNA Painter has greatly narrowed down where we’re targeting our on-going research to finally break down this brick wall.
We also have about 20 trees integrated into the master tree, and all of their owners are likely working towards the same goal as we are. As they do their research, and new DNA matches are added to the mix over the years, it’s likely one of us is going to have that piece of the puzzle we’re missing, and finally put it all together.
(A quick note, we’re using the newer version of GEDmatch called “Genesis” for this walkthrough. It’s soon to be the only GEDmatch, but if you’re not familiar with it, please use GEDmatch Genesis for this example.)
Back in our 1st installment of this series (Link), we suggested that you upload your AncestryDNA results to GEDmatch. We’re hoping you’ve done that, and we’re going to walk you through why this site is so powerful.
GEDmatch is a private site that is run out of Florida, for the purpose of allowing genealogists to upload their tests from all commercial DNA providers, with a complete set of tools to help us make matches between different tests. The key to GEDmatch is both its great tools, as well as it being open and public with all of the tests that are uploaded, but that’s also the warning that goes with GEDmatch: your tests are searchable by anyone. Your raw data is never shared, but your match information is openly shared to anyone that joins, including law enforcement. There have been a lot of stories shared about how GEDmatch was used to solve nearly 30 cold cases (so far), and reunited 10,000 adopted children with their birth families. There is a real chance your uploading of your DNA data is going to unearth secrets that your family doesn’t want unearthed.
At first GEDmatch was bewildering and confusing to us…and most of the walk-throughs we saw online were so detailed, it only further confused us.
We’ll be honest, at first GEDmatch was bewildering and confusing to us…and most of the walk-throughs we saw online were so detailed, it only further confused us. So, we’re going to focus more on the functionality GEDmatch than the technical details. This is still rather advanced, but when you practice with your matches, and then search for the more the technical details, you’ll find it makes a lot more sense.
Each test uploaded to GEDmatch is assigned a kit number, and most of the tools will require you to enter either your or your target match’s kit number. Especially when you have multiple kits you’re working with, it will be helpful to have your main page with all of your kit #’s open while you work in other tabs. It’s easier to cut and paste.
One-to Many Comparison
On your home screen you will see all of your kits, and if you click a kit # you’ll be taken to the first tool: One-to-Many Comparison. When the first box comes up, to start with we suggest you filter on only those matches that are 20cM and up. A whole list of names and numbers will pop up, and this is the list of everyone who’s uploaded a kit to GEDmatch that matches your kit. Let’s walk through what each of the boxes mean:
Select – You can pick at least 3 kits here and shortcut several of the tools by clicking on the “Visualization Options” button on the top header.
Kit #, Name (Alias), Email – This the information for you match, including a REAL email address! No more sending an Ancestry message, never hearing anything, and wondering if they ever log into Ancestry. Some people (and we recommend this for everyone managing someone else’s kit) use an alias for their testers name.
GED/Wiki Tree – You can enter a GEDcom-format family tree, or a link to your WikiTree, to help your matches find that MCRA. We’ll walk through this later.
Age – How long has the kit been on GEDmatch
Type – The chip version your test was from. Ignore this, it won’t matter for what we’re doing
Sex – If the GEDmatch uploader didn’t select a Sex for their tester, this will be U
Haplogroup – Shows which group you’re line is in if you took a mtDNA (mothers) or YDNA (fathers) DNA test. Ancestry doesn’t offer these tests, and if there are values in this for your matches, ignore them for now.
Autosomal – This is the type of DNA test Ancestry offers, and it’s what you think of when you think of DNA tests (ie: 50/50 inheritance from mom and dad). This is the area we’ll most care about, and it lists the total cM’s you share with the match and the largest piece of match in your samples. The “Gen” value gives you an estimate of how many generations separate you and this match.
X-DNA – We won’t cover this much, although it will get at least a mention in later post. X-DNA won’t be of much value, except in one very specific way.
You can click the header of each column to sort the results, but in this case let’s take a look at one of the higher cM matches on my list that I don’t yet know who they are.
One-to-One Autosomal DNA Comparison
For our example we’re going to select kit #M717701, especially since they have a family tree shared for this match. Clicking on the “GED Wiki” link in the GED column opens a link to their public tree on wikitree.com, but reviewing all of the surnames there, I don’t see any that jump out at me. I’m going to copy the kit # and go back to the home screen, to check out our next tool: One-to-One Autosomal DNA Comparison
Here’s where you actually confirm your matches to other kits, and start to get a view into the actual DNA segments that all of these matches are built off of. In the Ancestry tool, you take their word for it that you match someone, but this tool will actually prove you’re related.
Entering our kit # first box, and pasting in M717701 in the second, we get a picture of exactly where we match, or if we actually share no significant DNA (it happens!). In this case, we match the sample on Chromosome 14, and the exact start/stop positions of the match are listed. (We’ll come back to that in our next post, about DNApainter).
If you scroll all the way down to the bottom there’s more detail about this match, the most important info showing the estimated number of hops to our Most Common Recent Ancestor (MCRA). In this example it shows as 4.4 between us and the GGP that we share, but it’s best to double that number and use it to estimate the number of people between you and your match. 4.4×2 is 8.8, so we’ll round up to 9, and when it comes time to build out the link between us we’ll expect that it’s likely 4 or 5 ancestors up to the MCRA, and 5 or 4 ancestors back down to the match. Without even going to the “Shared cM Project” graph, we can guess that it’s most likely the MCRA we’re looking for will be a 3xGGP (4 ancestors from me) or 4xGGP (5 ancestors from me). But, we need to narrow down which side of the family this match is on, which brings us to our next tool: People who match both, or 1 of 2 kits.
People who match both, or 1 of 2 kits
This tool is very powerful, and where we do most of our work, and make most our matches. This is especially true if you have more than one kit in GEDmatch, because you can quickly narrow down target matches to either being on your mother’s or father’s side of the family. For example, I have my mother’s and a paternal uncle’s kits uploaded, so if I use GEDmatch to show me all of the kits match my test and my target test, I can pretty quickly see if it’s on my mother’s side, or my father’s. Plus, I have many known matches that we don’t manage, so we can usually get pretty lucky on narrowing it down further.
For our example, we ran this test on our target user from above and we see that they match my mom’s test also, so we’re looking at a MCRA on her side. We just cut our search in half! Looking more closely, her cousins on her father’s side have maybe a dozen tests in GEDmatch, but none of them are listed here. It’s very likely then, given the volume and closeness of the paternal cousins’ tests that if this was on my mom’s father’s side, they would show up in this list…so we’re going to assume this match is on my mom’s mother’s side. We just took the total number of potential MCRA’s down in half again, so we’re really narrowing in! Given that we already have 21 of 32 5xGGP’s identified in that branch of the tree, odds are pretty good we’re going to find a common surname.
In this case, we’re going to have to do what we did in our last post (Link), which corresponds to DNA secret #2: we’ll spend most of our time building out other people’s trees! Looking at the GED Wiki tree they have up, there’s a decent 4 generation tree on the match’s father’s side, but only a mother’s name and birth/death. Since nothing on the father’s side jumps out, we’ll build out their mother’s side first.
The other huge advantage at this point with GEDmatch is that we have the direct email address of our relative immediately, and so, once we’ve validated we’re a match with the 1:1 tool, we can reach out to what’s likely their regular email account and see if they have more information.
Triangulation is confirming that not only does your test match the target’s kit, but that another known ancestor’s kit matches as well. In the above example we confirmed I matched with the “One-to-One” tool, and we linked my mom with the “People who match both” tool, but technically we’re just guessing my mom’s kit also matches the target kit. I’ve never had it be wrong, but to really prove the match it would be best to confirm the matching segment for myself, my mom, and the target all match. There’s a GEDmatch “Tier1” tool for Triangulation (and we find it VERY worth it to donate $10/month to get the Tier1 tools!), but it’s just about as easy to do a One-to-One test between my mom and the target to do a full triangulation.
Once we prove out the family tree link to our “Cake” ancestor, and we have our MCRA, we will have really narrowed down how we’re linked to everyone else on the “People who match both” list. There’s nearly 50 matches on that list that we now have very solid evidence on who the MCRA is. Even if we have to build out most of those trees manually, it’s likely we already have pieces of those trees built out when we made the first match.
That being said, it’s one of the reasons it’s so frustrating that Ancestry has such weak tools. If we could combine Ancestry’s strong base of Public Trees with GEDmatch’s tool set, our effectiveness when making DNA matches would be extraordinary! It’s also why it’s so important to upload/link a GEDCOM file to your GEDmatch tree. It doesn’t have a great interface, but even ugly tree’s make this search much, much easier!
Using just these 3 simple tools you can build out many matches using GEDmatch. Just keep practicing, and quickly it’s like you’ve been using it for years. And, as your skill in the tool grows, those overly technical online walk-throughs will help further unlock the power of AncestryDNA tests!
In our next installment, we’re going to use DNApainter to narrow down those matches were we have no data on how we’re connected to a verified match, so we know where to focus our traditional genealogical research, and we’ll talk about some of the more advanced topics we won’t dive into too deeply in this series.
Once you have all of your hints with notes attached, look for your largest unidentified match that has a Public Tree, even if it’s unlinked. Since the tree has no hints you’ll know their tree doesn’t match yours (yet!), but the larger the amount of cM the closer your match…so the fewer relatives you’ll have to build out.
Before we dive in with our first example, here’s the first of several surprising truths about doing genealogical DNA work: you will spend most of your time doing other people’s trees. In a perfect world your DNA match built out their tree to their 4xGGP too…but you’ll find most times you won’t be so lucky!
DNA match surprise #1: You will spend most of your time making DNA matches building out other people’s trees.
Example #1: Eileen Wilson
As an example, let’s look at a match with an Unlinked Tree and 242 cM of shared DNA. Looking at the match’s Public Tree, the names don’t jump out (other than the very common “Smith”), but based on our notes, we know it’s on Michael’s Father’s Mother’s Mother’s Father’s line…which was William Arthur Smith. To confirm, we entered the cM in the DNA Painter Shared cM Project tool (Link), and the results (eliminating the ½ siblings) indicate the most likely matches are from our tester’s Grandparents or Great Grandparents.
Expanding our tree, we see that we had already identified Wallace David Smith in our tree, his wife Mabel, as the brother of William Arthur Smith. We also had their daughter Lula, which all of which sync’s up with the match’s tree. From there, it’s pretty easy to prove out that the DNA match is the daughter of George and Lula (Smith) Hopkins.
This is the same process whether the DNA match is 242 cM or 12 cM: use common matches to narrow which line the DNA likely matches you, identify the most likely target for your match through tools like the Shared cM Project charts and the “What are the odds?” tool. From there, build out the likely tree based on your estimates until you find the match. Then, you update the notes so when you find another shared match, you’ll have the info to narrow down their DNA line!
Make sure to make a note in your match, as we did in Part 2 of this series, so you’ll be able to focus in on other matches with less shared DNA later.
Let’s try one more match that’s a little further out.
Example #2: “A.G.”
The next target is going to “A.G.”, a woman that shares 26cM with the same tester as the first example. The first thing we do is review A.G.’s shared matches with us, and we see notes indicating that the match is on our tester’s Father’s side, so we just narrowed our focus to that ½ of the tree. Next, we went to DNA Painter Shared cM Project tool and maped out the most likely matches for the level of shared cM, which shows that it’s likely our shared match is around a 4th Cousin, Once removed or a 5th Cousin. This means, it’s most likely we’re looking for 3x/4x GGP as our MRCA.
The good news is that we have a strong tree to 3x/4x GGP’s for our tester. The bad news is, we have no tree for A.G. and we’re going to have to build hers out to understand where we match. We followed our own instructions on building out a “quick and dirty” Ancestry tree (Building a good Public Ancestry.com tree – Part One: sources, citations, facts, and proof), especially paying attention to find proof of relationships between each generation. And, in the end, after about 16 hours of total work we found…nothing. No match.
Which brings us to our second of our surprising truths about doing genealogical DNA work: Your DNA matches will mostly be on family lines you already have great information on, and conversely most of your unlinked DNA matches will be on family lines which are already your brickwalls.
DNA match surprise #2: Your DNA matches will mostly be on family lines you already have great information on, and conversely most of your unlinked DNA matches will be on family lines which are already your brickwalls.
In this case, we have limitations on several key areas of our family tree. Our tester is Michael’s grandmother, and on her paternal line we run into a pretty solid brickwall at her 2x GGP. They likely were born in either New Hampshire or Vermont, before they migrated to Michigan through New York, but 3 generations of family historians haven’t gotten past Alvin Jewell (1830-1911). In A.G.’s line, there are two couples from Vermont, from about that time, but there’s not enough evidence to pursue a solid line of inquiry.
This brings us to of our third surprising truths about doing genealogical DNA work: Even with the best of trees, and hours of effort, you’re going to have a lot of matches that you’re not going to be able to link to your tree.
DNA match surprise #3: Even with the best of trees, and hours of effort, you’re going to have a lot of matches that you’re not going to be able to link to your tree.
This is also where the limitations of AncestryDNA start to become apparent. There are nearly no tools there to help us determine which side of our match’s line do we expect we match. How can we leverage DNA triangulation to further narrow down where we should be researching? When you’re trying to figure out where to look amongst 32 GGP’s who might be a key to your DNA match, being able to eliminate ½ of those potential matches is a huge boon. But, beyond what we’ve already gone through, there’s not much more they can offer.
One of the other limitations of AncestryDNA is that you can never prove your matches. Even in our first example, we have a good tree match, and the amount of shared DNA (242 cM) matches exactly where we’d expect the two samples to match (2nd Cousins), but without tools like a chromosome browser, it’s impossible to prove those two kits match as we’ve assumed.
We’ll be looking at other tools in later installments, including how we can narrow down the search for our MCRA link to A.G.
In our next installment we’re going to go through a GREAT set of tools in GEDmatch that will demonstrate what we wish we had in Ancestry, and we’ll show you how to leverage you DNA results there to really unlock your matches.