Several updates have occurred to the DNASurnames Haplogroup tree that shows key branches, the patriarch, and optionally, the tester, for surnames/lineages of interest to assorted projects, sometimes sub-projects of much larger ones.
The haplogroup R tree now includes in particular:
- BigY driven changes around R-S7361, including the new branch created for my Henderson family
- ditto around R-ZZ7_1 (well R-Y16467*) for the Richardsons of Morebattle subset of the Richardson-2 project
- a place holder at R-M269 for the Dawe family of Lamerton, Devon while we await BigY test results for the line
On the lineages side, the RICHARDSON pages in particular have had a revamp to include a theoretical DNA signature chart linking up the 4 yDNA STR matching lines to their parent terminal SNPs to see what the derived ySTR signature for the progenitor would be.
Wednesday, 30 August 2017
Another MyHeritage mystery
Previous posts have documented some of the vagaries experienced with MyHeritage's DNA matching.
This one makes me wonder how those without an ability to compare at other companies would even realise that they may be missing a close match!
I expect that some matches may well be false positives given the imputations MyHeritage does to compare test kits from assorted companies, but I didn't expect to NOT find a match reported as predicted 2nd cousin by Ancestry, 3 generations by GEDmatch and predicted 2nd to 3rd cousin by FamilyTreeDNA.
The comparison details:
Ancestry: both tested there
Predicted relationship: 2nd Cousins
Possible range: 2nd - 3rd cousins
Confidence: Extremely High
Total shared: 208 cMs over 11 segments
FamilyTreeDNA: one tested, the other transferred in from recent-ish Ancestry test
Predicted 2nd to 3rd cousins total 202 * cMs, largest segment 57
* effectively 175cMs when < 5cM segments excluded
GEDMatch: one uploaded from FTDNA, the other from the recent-ish Ancestry test #
At the defaults for one to one comparison:
Largest segment = 56.2 cM
Total of segments > 7 cM = 212.5 cM
11 matching segments
Estimated number of generations to MRCA = 3.0
# these kits being the same used for the MyHeritage uploads.
This has been reported to MyHeritage Support for their comments and explanation.
This one makes me wonder how those without an ability to compare at other companies would even realise that they may be missing a close match!
I expect that some matches may well be false positives given the imputations MyHeritage does to compare test kits from assorted companies, but I didn't expect to NOT find a match reported as predicted 2nd cousin by Ancestry, 3 generations by GEDmatch and predicted 2nd to 3rd cousin by FamilyTreeDNA.
The comparison details:
Ancestry: both tested there
Predicted relationship: 2nd Cousins
Possible range: 2nd - 3rd cousins
Confidence: Extremely High
Total shared: 208 cMs over 11 segments
FamilyTreeDNA: one tested, the other transferred in from recent-ish Ancestry test
Predicted 2nd to 3rd cousins total 202 * cMs, largest segment 57
* effectively 175cMs when < 5cM segments excluded
GEDMatch: one uploaded from FTDNA, the other from the recent-ish Ancestry test #
At the defaults for one to one comparison:
Largest segment = 56.2 cM
Total of segments > 7 cM = 212.5 cM
11 matching segments
Estimated number of generations to MRCA = 3.0
# these kits being the same used for the MyHeritage uploads.
This has been reported to MyHeritage Support for their comments and explanation.
Monday, 7 August 2017
Visualise your Ancestry DNA Matches
Drowning in the analysis of your Ancestry match lists?
Can't figure out who best to contact?
Or how to get their attention by targetting your message?
Check out how to Visualise your Ancestry DNA Matches
Shelley Crawford has written several very clear posts about how to use NodeXL (and DNAGedCom.com's Ancestry download tools) to make sense of the morass of data.
Thank you to whoever mentioned this on the FaceBook group Genetic Genealogy Tips & Techniques.
The instructions enabled me to reasonably quickly get from my seemingly endless screeds of data to be filtered and diced and sliced to:
Firstly this:
and then this filtered set of groups that actually do have interactions - or have a match of particular interest in them:
It does also rather highlight that I have a dearth of interconnected Ancestry matches up to "4th cousins" - only 147.
Of that 147 there's one 1st cousin (not included in the networks above to reduce clutter), one 2nd cousin, 6 predicted 3rd cousins (5 known to range from 2nd to 3C1R, the 6th unknown), and the remainder (139) predicted 4th, only 23 of whom are "placed".
Within an hour of posting my first targetted message to a 29cMs match asking if they had any idea how the three people connected I had a response - with a Perthshire connection identified between them, so possibly that Henderson/Millar brickwall will crack one day after all - once I figure out where it can be fitted into my tree!
Can't figure out who best to contact?
Or how to get their attention by targetting your message?
Check out how to Visualise your Ancestry DNA Matches
Shelley Crawford has written several very clear posts about how to use NodeXL (and DNAGedCom.com's Ancestry download tools) to make sense of the morass of data.
Thank you to whoever mentioned this on the FaceBook group Genetic Genealogy Tips & Techniques.
The instructions enabled me to reasonably quickly get from my seemingly endless screeds of data to be filtered and diced and sliced to:
Firstly this:
and then this filtered set of groups that actually do have interactions - or have a match of particular interest in them:
It does also rather highlight that I have a dearth of interconnected Ancestry matches up to "4th cousins" - only 147.
Of that 147 there's one 1st cousin (not included in the networks above to reduce clutter), one 2nd cousin, 6 predicted 3rd cousins (5 known to range from 2nd to 3C1R, the 6th unknown), and the remainder (139) predicted 4th, only 23 of whom are "placed".
Within an hour of posting my first targetted message to a 29cMs match asking if they had any idea how the three people connected I had a response - with a Perthshire connection identified between them, so possibly that Henderson/Millar brickwall will crack one day after all - once I figure out where it can be fitted into my tree!
Subscribe to:
Posts (Atom)