{"id":8947,"date":"2019-01-02T21:51:02","date_gmt":"2019-01-02T21:51:02","guid":{"rendered":"http:\/\/www.jmhartley.com\/HBlog\/?p=8947"},"modified":"2019-01-02T21:51:02","modified_gmt":"2019-01-02T21:51:02","slug":"comparing-four-siblings-ancestrydna-autocluster-results","status":"publish","type":"post","link":"http:\/\/www.jmhartley.com\/HBlog\/2019\/01\/02\/comparing-four-siblings-ancestrydna-autocluster-results\/","title":{"rendered":"Comparing Four Siblings’ AncestryDNA AutoCluster Results"},"content":{"rendered":"

In my previous Blog<\/a>, I compared my AncestryDNA AutoCluster results to two of my siblings, Jon and Heidi. In this Blog, I will look at Sharon’s results:<\/p>\n

\"\"<\/a><\/p>\n

For the previous three siblings, I looked at matches between 25 and 600 cM. For Sharon, I lowered the upper limit to 300 cM. This was to eliminate my 1st cousin’s daughter’s results.<\/p>\n

Here are my sibling comparisons:<\/p>\n

\"\"<\/a><\/p>\n

By bringing Sharon’s upper limit down to 300 cM, I eliminated my father’s first cousin, a daughter of a maternal first cousin and a paternal 2nd cousin. However, many of my paternal second cousins have tested.<\/p>\n

Comparing My Clusters to My Three Siblings’ Clusters<\/h2>\n

Rather than trying to figure out each of Sharon’s clusters, I will compare her clusters to mine. To do this, I compared my clusters to Sharon’s in MS Access. This just saves time. The Query in Access looks like this:<\/p>\n

 <\/p>\n

\"\"<\/a><\/p>\n

I connected our two tables by the identifier. This is the identifier of the different AncestryDNA matches. Then I chose my clusters and Sharon’s clusters and I grouped them to get rid of duplicates. That Query resulted in this:<\/p>\n

\"\"<\/a><\/p>\n

This is a lot easier than going through Sharon’s clusters one by one. The above table tells me a few things:<\/p>\n