Re: Family Finder tests entering the Y-DNA haplotree
Hi,
FTDNA Discover has just been updated with new data from FF/Y-SNP testers (7018 subclades, equivalent to the Y-DNA haplotree data from December 8, 2023). Attached is a link to a European map by country (frequency – December 16, 2023):
?
To compare with that corresponding to November 18:
?
The FTDNA autosomal database would include approx. 1.5M testers, around half of which may be men. Even if certain transfers from other companies will not be included in the data, there would still be several hundred thousand male autosomal kits to be added to the Y-DNA Haplotree, of which ~10% could belong to the R-U106 branch...
?
In the meantime, 9 aDNAs were added by FTDNA from 2 studies:
1) Barrie et al.. 2023:
| CGG100750_4 |
R-ZP121 |
| CGG100951_4 |
R-FTB40068 |
| CGG100493_4 |
R-S11739 |
| CGG100447_4 |
R-BY176735 |
| CGG100454_4 |
R-V3517 |
| CGG100341_3 |
R-BY35826 |
| CGG101864_3 |
R-FTB22945 |
| CGG100445_4 |
R-FGC23826 |
?
?
2) Bonczarowska et al. 2022:
Ewenn
|
Re: FamilyTreeDNA provides Y-DNA haplogroups from Family Finder autosomal tests
That is very interesting. If the rate of false positives "child-only matches" is so high then I also wonder how it affects the ethnic origin estimated in MH, although for my mother the estimate matches reasonably well the family history, although it still shows anomalies like a quite significant Anglo-Saxon ancestry. I did not manage to test my father so I estimate his ancestry by comparing my mother's and mine, basically doing a primitive phasing.
The comparison of different chips gives a very concerning information, frankly. I tested myself and my mother at FTDNA and later transferred to MH.
Thank you again Debbie.
|
Re: FamilyTreeDNA provides Y-DNA haplogroups from Family Finder autosomal tests
MyHeritage have a database of 7.7 million whereas FTDNA’s Family Finder database is only about 1.5 million so you would expect many more matches at MyHeritage though I’m sure you’re right that MyHeritage have many more customers from Poland. ? When MyHeritage wrote that blog post about their matching algorithms the companies were all using the Illumina OmniExpress. The move to the Illumina Global Screening Array made everything much more complicated and has resulted in many more false matches. There are only about 150,000 SNPs out of about 700,000 in common across the two different chips. See the ISOGG SNP Comparison Chart: ?
? I suspect that if MyHeritage were to repeat that trio analysis today the ratio of child-only matches would be much higher. ? I have two kits at MyHeritage. One is an AncestryDNA transfer done on the OmniExpress and the other is a new test on the Global Screening Array. Here is a comparison I did at the beginning of November this year. ? Illumina OmniExpress transfer ? 10,288 matches for Debbie ? 3,274 DNA matches shared with Debbie’s dad ? 2,954 DNA Matches shared with Debbie’s mum ? 4,060 matches not shared with either parent (39%) ? New test on Global Screening Array ? 8,856 matches for Debbie ? 2,303 DNA matches shared with Debbie’s dad ? 2,004 DNA Matches shared with Debbie’s mum ? 4,549 matches not shared with either parent (51%) ? 1,432 matches not replicated on GSA (14%) ? Best wishes ? Debbie ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Centropol
Sent: Thursday, December 14, 2023 3:55 PM
To: [email protected]
Subject: Re: [R1b-U106] FamilyTreeDNA provides Y-DNA haplogroups from Family Finder autosomal tests? Thank you very much Debbie. That really clarifies a lot and explains why I have 2x more matches in MH compared to FTDNA, although MH is a bit more popular in Poland, I think, also because of the multiple languages it can be used in.
I was really surprised to see that 16-20 percent of child-only matches are considered a good result.
"The last step of DNA Matching is filtering out false positives and estimating the specific relationship between two individuals with shared DNA segments. Because many of us are descendants of the same very ancient ancestors, we often have tiny shared DNA segments with individuals we wouldn’t really consider family. We sought a method to filter out such matches that only frustrate genealogists. To this end, we measure false positives internally by looking at?trios?— these are sets of child, mother, and father who were all tested with MyHeritage DNA kits, and received results that validated that the relationships between the parents and child is correct. Any match that a child has with another individual, who does not match neither the father nor the mother is suspected to be a false positive and is called a?child-only match. We measure the percentage of child-only matches among all matches that are returned for children in all known trios on MyHeritage, and this figure is called the percentage of suspected false positives indicated by child-only matches. We managed to bring this figure down to 16–20 percent, which is a good result that as far as we know is equivalent to or better than all other DNA services.?Our improved classifier algorithms have succeeded in bringing our false positive rate to an all-time low."
|
Re: FamilyTreeDNA provides Y-DNA haplogroups from Family Finder autosomal tests
Thank you very much Debbie. That really clarifies a lot and explains why I have 2x more matches in MH compared to FTDNA, although MH is a bit more popular in Poland, I think, also because of the multiple languages it can be used in.
I was really surprised to see that 16-20 percent of child-only matches are considered a good result.
"The last step of DNA Matching is filtering out false positives and estimating the specific relationship between two individuals with shared DNA segments. Because many of us are descendants of the same very ancient ancestors, we often have tiny shared DNA segments with individuals we wouldn’t really consider family. We sought a method to filter out such matches that only frustrate genealogists. To this end, we measure false positives internally by looking at?trios?— these are sets of child, mother, and father who were all tested with MyHeritage DNA kits, and received results that validated that the relationships between the parents and child is correct. Any match that a child has with another individual, who does not match neither the father nor the mother is suspected to be a false positive and is called a?child-only match. We measure the percentage of child-only matches among all matches that are returned for children in all known trios on MyHeritage, and this figure is called the percentage of suspected false positives indicated by child-only matches. We managed to bring this figure down to 16–20 percent, which is a good result that as far as we know is equivalent to or better than all other DNA services.?Our improved classifier algorithms have succeeded in bringing our false positive rate to an all-time low."
|
Re: FamilyTreeDNA provides Y-DNA haplogroups from Family Finder autosomal tests
Hello Centropol ? MyHeritage use a complicated process using imputation and stitching to compensate for the low overlap of markers on the different chips. The process is described in this blog post: ?
? I suspect that some of these long blocks of 40 cM are not really a single segment but lots of small segments that have been incorrectly stitched together. ? Another problem is that a lot of the seemingly high matches are in fact made up of lots of small false segments. I have an example I used recently in a presentation of a match I had at MyHeritage which shared 49.5 cM with me with one test and 35.7 on my other test. This person did not match my dad but only matched my mum on 8.9 cM. When I looked in the chromosome browser I could see that this seemingly large match was made up of lots of tiny segments, only one of which appears to be valid. See the attached screenshot of my slide. ? If you can find a genealogical connection with any of your matches at MyHeritage then all well and good but I just don’t think we can use those small matches as evidence because of the uncertainty. ? One good feature at MyHeritage is the filter which allows you to sort your matches by country of residence. I tend to focus on matches living in the UK which is where I live and where my ancestry is from and I don’t generally look at the lower matches below about 30 cM unless something of interest really jumps out at me. Like you I get hundreds of matches at MyHeritage living all over the world in countries where I have no recent genealogical connections (France, Germany, the Netherlands, Sweden, Norway, Denmark, etc). These are either false matches or very distant matches reflecting the fact that all Europeans share common ancestry within the last thousand years. ? Debbie ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Centropol
Sent: Thursday, December 14, 2023 12:16 PM
To: [email protected]
Subject: Re: [R1b-U106] FamilyTreeDNA provides Y-DNA haplogroups from Family Finder autosomal tests? Could you please elaborate more on the below? I do not have any close matches on MH, except my direct family which I asked to test, but plenty of remote ones and I was wondering how I can have some unknown relatives in Scandinavia having a single common with me block of ~40cM. On the other hand I could verify via the traditional genealogy the link with other people having even a smaller common DNA. So I have strated wondering maybe they are false positives, what I understood was not likely with commom DNA patch of >6cM, hence the action FTDNA took a while ago to increase the matching threshold. "In practical terms the difference in matches is not an issue as it’s the low matches are affected. MyHeritage has a major problem with false matches and inflated cM totals so I don’t trust matches there much under 30 cM anyway and have even had problems with matches up to 50 cM."
|
Re: FamilyTreeDNA provides Y-DNA haplogroups from Family Finder autosomal tests
Hello Debbie,
?
Could you please elaborate more on the below?
I do not have any close matches on MH, except my direct family which I asked to test, but plenty of remote ones and I was wondering how I can have some unknown relatives in Scandinavia having a single common with me block of ~40cM. On the other hand I could verify via the traditional genealogy the link with other people having even a smaller common DNA. So I have strated wondering maybe they are false positives, what I understood was not likely with commom DNA patch of >6cM, hence the action FTDNA took a while ago to increase the matching threshold.
?
"In practical terms the difference in matches is not an issue as it’s the low matches are affected. MyHeritage has a major problem with false matches and inflated cM totals so I don’t trust matches there much under 30 cM anyway and have even had problems with matches up to 50 cM."
?
Thank you,
Centropol
|
Re: Family Finder tests entering the Y-DNA haplotree
Thank you very much!
Cheers!
Damir
|
Re: Family Finder tests entering the Y-DNA haplotree
Thanks, Iain & Ewenn. I’ll look for any updates that may appear. John ?
|
Re: Family Finder tests entering the Y-DNA haplotree
Hello Damir FF SNPs can be seen in the project pages, just as with any other test. If they all have Y12 or more STRs, haplogroups can be seen in the charts too.
|
Re: Family Finder tests entering the Y-DNA haplotree
Hi John,
?
I think Iain has fully answered your questions.
?
In addition, on your R-S15309 branch, downstream of R-Z18, only these two testers have appeared since the date given by Iain. If we go back 1 year, to November 29, 2022, 1 other new tester having carried out a bigY700 test, of American origin, appeared forming the haplogroup R-BY160407 with a tester of British origin (probably a bigY500).
?
?
?
Hi Rob,
?
Unfortunately, your fears currently appear to be well founded. However, the fact that your father is only identified as R-U106 could possibly only mean that his FF test only showed no calls for possible testable SNPs on your downstream branch of R-U106.
On this small branch, only 6 testers of unknown origin have appeared since November 29, and these 6 for R-FGC57423. This haplogroup was discovered in 2016 by Full Genome Corp, and is composed of 8 equivalent SNPs with no other recurrence currently on the Y-DNA Haplotree. R-S19589 and R-S11493 were both discovered in 2014 (I don't know since when they were identified by FTDNA). It therefore seems strange that FTDNA selected a specific SNP from a haplogroup discovered in 2016 (and probably appeared a little later at FTDNA), which only had 3 individuals until 2021...
?
R-S19589 is currently only ~2.4 per 10,000 bigY testers. Probably ~38,000 new FF testers have appeared. So we could expect ~9 new R-S19589 testers. We have 6, which doesn't seem that far away. We will probably have to wait a little longer to be fixed (I have identified several serious STR candidates for R-S11493, but they are still identified R-M269. If one of them also passed a FF test, we will have more material to conclude).
?
I am quite surprised by the number of Y-SNPs that seem to be covered by the GSA chips used by FTDNA. I wonder if it is not possible for them to detect genotypes for SNPs very close (a few bp) to SNPs targeted by their chips. For example, SNP FGC57423 (Y position 16,277,160) is very close to Z15080 (16,277,158). Z15080 only appears in the E-L94 block, an ancient haplogroup whose TMRCA is estimated ~7400 BCE. Exactly 20 new testers appeared to be E-L94 this month (perhaps FTDNA selected several SNPs of the main haplogroups for their chips?)… This is only a hypothesis that might eventually have to be checked for other haplogroups covered in a rather improbable manner, like FGC57423, by the FF chips.
Cheers,
Ewenn
|
Re: Family Finder tests entering the Y-DNA haplotree
GAP admins can keep track of their updated FF Y matches by looking at the Received Lab Results which now reports ‘Prediction’ under Lab Procedure
To Damir. ??
I believe you can only see them via the Family Finder (or Y or Adv) ?match list with no special designations or ?icons. ?You can use the YDNA sort and search to help a little?
Unfortunately some of the N/As have a Y Haplo if you click on the name. ?They still sort or search correctly?
|
Re: Family Finder tests entering the Y-DNA haplotree
Where can I see this new Y-dna results? It just appears on dashboard where FF DNA Results are shown? An icon appears or do we need to find it elsewhere? I got my final haplogropu on Yseq, so looking forward to see what ftdna will show.?
Cheers,?
Damir
|
Re: Family Finder tests entering the Y-DNA haplotree
Hi John,
You can check the results whenever you like here: https://www.familytreedna.com/public/y-dna-haplotree/R;name=R-S9509 Click on the three dots on the right-hand side and choose one of the reports.
The country report now shows four tests, two German tests (presumably yours) and two others without countries of origin. These two were not there on 29th November, so probably come from Family Finder tests. They are not yet in Discover - I think that update process occurs over the weekend normally.
If these are Family Finder tests, then it is likely that they split your haplogroup. You may be able to use some combination of filtered Family Finder results or the Advanced Matches facility to identify them if they are an existing Family Finder match to you. Otherwise we don't yet know what facilities we will have here - this is uncharted territory still.
Cheers,
Iain.
|
Re: Family Finder tests entering the Y-DNA haplotree
Hi Ewenn,
Can you check your data for R-S9509? There's been no change in that clade for at least 5 years as I manage both of the bigY kits.? (Unless the change is due to some FF result that I cannot see.)
Thanks,? John Terwiske
[Edited Message Follows]
A quick analysis of R-Z18, between November 29 and December 8, 2023, a branch which seems instructive to me on the contribution of FF tests.
Stats (including all subclades):
Kits: +599
bigY: +7
Countries:
| EKA’s Origin |
Country code |
? |
2023-11-29 |
? |
2023-12-08 |
? |
Increase |
| Unknown Origin |
X |
? |
1054 |
? |
1554 |
? |
47.44% |
| Sweden |
SE |
? |
192 |
? |
213 |
? |
10.94% |
| United States |
US |
? |
186 |
? |
205 |
? |
10.22% |
| England |
ENG |
? |
229 |
? |
242 |
? |
5.68% |
| Norway |
NO |
? |
92 |
? |
99 |
? |
7.61% |
| Scotland |
SCT |
? |
141 |
? |
146 |
? |
3.55% |
| Germany |
DE |
? |
102 |
? |
106 |
? |
3.92% |
| United Kingdom |
GBR |
? |
77 |
? |
81 |
? |
5.19% |
| Netherlands |
NL |
? |
31 |
? |
34 |
? |
9.68% |
| Ireland |
IE |
? |
50 |
? |
53 |
? |
6.00% |
| Switzerland |
CH |
? |
30 |
? |
32 |
? |
6.67% |
| Denmark |
DK |
? |
19 |
? |
21 |
? |
10.53% |
| Wales |
WLS |
? |
14 |
? |
16 |
? |
14.29% |
| Poland |
PL |
? |
15 |
? |
17 |
? |
13.33% |
| Finland |
FI |
? |
39 |
? |
41 |
? |
5.13% |
| Northern Ireland |
NIR |
? |
9 |
? |
11 |
? |
22.22% |
| Russian Federation |
RU |
? |
5 |
? |
7 |
? |
40.00% |
| Belgium |
BE |
? |
4 |
? |
5 |
? |
25.00% |
| Italy |
IT |
? |
8 |
? |
9 |
? |
12.50% |
| Estonia |
EE |
? |
4 |
? |
5 |
? |
25.00% |
| Venezuela |
VE |
? |
0 |
? |
1 |
? |
--- |
| Spain (La Rioja) |
--- |
? |
0 |
? |
1 |
? |
--- |
| Argentina |
AR |
? |
0 |
? |
1 |
? |
--- |
~16.5% of new kits having declared their EKA's country of origin.
Clades:
| Clade |
? kits |
? bigY |
? |
Increase |
? |
TMRCA |
| R-Z18 |
208 |
0 |
? |
38.31% |
? |
~2231 BCE [-2870 ; -1675] |
| R-S5684 |
54 |
0 |
? |
450.00% |
? |
~67 BCE [-477 ; 277] |
| R-CTS2158 |
53 |
0 |
? |
240.91% |
? |
~742 BCE [-1264 ; -301] |
| R-CTS12023 |
40 |
0 |
? |
86.96% |
? |
~686 BCE [-1182 ; -266] |
| R-L257 |
40 |
0 |
? |
26.49% |
? |
~1395 BCE [-1950 ; -917] |
| R-Z372 |
36 |
0 |
? |
120.00% |
? |
~1564 BCE [-2118 ; -1084] |
| R-ZP30 |
35 |
0 |
? |
269.23% |
? |
~102 BCE [-501 ; 236] |
| R-Z375 |
26 |
0 |
? |
108.33% |
? |
~172 BCE [-550 ; 151] |
| R-S11601 |
22 |
0 |
? |
91.67% |
? |
~1381 BCE [-1987 ; -865] |
| R-ZP48 |
18 |
0 |
? |
450.00% |
? |
~569 CE [141 ; 909] |
| R-S3207 |
15 |
0 |
? |
--- |
? |
~990 BCE [-1505 ; -549] |
| R-ZP8 |
10 |
0 |
? |
200.00% |
? |
~94 BCE [-467 ; 223] |
| R-S4037 |
8 |
0 |
? |
72.73% |
? |
~405 BCE [-933 ; 34] |
| R-S4031 |
6 |
0 |
? |
600.00% |
? |
~1241 BCE [-1795 ; -767] |
| R-S5750 |
5 |
0 |
? |
62.50% |
? |
~1069 CE [857 ; 1245] |
| R-Z378 |
4 |
0 |
? |
50.00% |
? |
~845 BCE [-1328 ; -431] |
| R-ZP261 |
3 |
0 |
? |
150.00% |
? |
~1576 CE [1398 ; 1710] |
| R-FT111760 |
2 |
0 |
? |
40.00% |
? |
~1739 CE [1579 ; 1853] |
| R-S9509 |
2 |
0 |
? |
100.00% |
? |
~1912 CE [1784 ; 1985] |
| R-S6358 |
2 |
0 |
? |
18.18% |
? |
~867 CE [649 ; 1052] |
| R-S3514 |
1 |
0 |
? |
25.00% |
? |
~878 CE [389 ; 1243] |
R-FT131424 |
1 |
1 |
? |
--- |
? |
~787 BCE [-1818 ; 5] |
R-BY111283 |
1 |
1 |
? |
100.00% |
? |
~1074 CE [619 ; 1407] |
R-ZP78 |
1 |
1 |
? |
33.33% |
? |
~1049 CE [826 ; 1234] |
| R-SK1171 |
1 |
0 |
? |
--- |
? |
~1010 CE [618 ; 1307] |
| R-FT61322 |
1 |
0 |
? |
50.00% |
? |
~741 CE [190 ; 1153] |
| R-S5673 |
1 |
0 |
? |
50.00% |
? |
~247 BCE [-687 ; 125] |
R-FTB29811 |
1 |
1 |
? |
50.00% |
? |
~1253 CE [784 ; 1579] |
R-BY17442 |
1 |
1 |
? |
--- |
? |
~92 CE [-458 ; 531] |
R-FTD44136 |
1 |
1 |
? |
50.00% |
? |
~280 BCE [-1449 ; 565] |
R-BY41942 |
1 |
1 |
? |
50.00% |
? |
~1847 CE [1524 ; 1994] |
Barred clades are, a priori, those concerned by the addition of bigY tests (7 in total in the time interval considered).
NOTA:
For SNP Z18 (R-Z18 only, without sub-clades), the SNP Map tool shows +20 kits with a precise location of their EKA, or +25.6%, between November 14 and December 10. No modification observed on equivalent SNPs (e.g.: Z14, Z16, ...), which give “exotic” Haplogroups (R-Z14, R-Z16).
R-ZP261: TMRCA ~1576 CE, block of 19 equivalent SNPs, +3 kits. Parent clade: R-ZP161, TMRCA ~124 BCE. These 3 kits most likely do not test positive for these 19 SNPs, based on a simple FF test. It seems a priori possible that one or more of these 3 kits could split the current R-ZP261 block (unless they are close relatives of agnatic lines having passed a bigY test).
Ewenn
|
Re: FamilyTreeDNA provides Y-DNA haplogroups from Family Finder autosomal tests
Hi Jason,
What you're referring to is nothing to do with the test itself. There was a short period where Family Tree DNA predicted groups for Y-STR tests with better resolution than just R-M269. However, they very quickly stopped doing this. The reason behind this is that FTDNA treats this prediction as a guarantee: i.e., if you take an SNP test and prove you are not R-M269, then they will find out which haplogroup you do belong to for free. This is necessary because R-M269 is often the starting point for people to take SNP packs.
It is sometimes possible to predict more refined haplogroups than R-M269, but it's not 100% successful. For example, if you are already M269+ and have DYS492=13, then you have a 97% chance of being part of R-U106. Some haplogroups have markers like this, some don't, and the probability of being correct varies.
These days, this prediction and the guarantee it holds are fairly useless anyway. We don't hear much about single SNP tests or SNP packs these days, given the reduced cost and comaprative benefit of BigY and other sequencing tests, so the guarantee doesn't mean that much. FTDNA could, in most cases, accurately predict most people down to at least the level of the most recent SNP packs. However, a much better idea of a person's haplogroup can often be found simply by looking at the haplogroups listed in their STR matches - this isn't fool-proof, especially at the lower levels, but it is often instructive.
Cheers,
Iain.
|
Re: FamilyTreeDNA provides Y-DNA haplogroups from Family Finder autosomal tests
I just hope they update the ydna test as well as they used to provide better groups than m269.
Jason
To clarify Debbie's point, this refers to the post regarding a *completely* unprocessed test. Not all male tests have received Y-DNA haplogroups yet - that process is still ongoing.
- Iain.
|
Re: FamilyTreeDNA provides Y-DNA haplogroups from Family Finder autosomal tests
To clarify Debbie's point, this refers to the post regarding a *completely* unprocessed test. Not all male tests have received Y-DNA haplogroups yet - that process is still ongoing.
- Iain.
|
Re: FamilyTreeDNA provides Y-DNA haplogroups from Family Finder autosomal tests
If your Family Finder test has not been processed by FTDNA you need to get in touch with customer service and find out what has happened. Have you perhaps ended up with two different accounts and your Family Finder results were posted to a second account? If so, FTDNA will be able to merge the two accounts for you. ? Debbie Kennett ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Lincoln Lincoln
Sent: Sunday, December 10, 2023 1:47 AM
To: [email protected]
Subject: Re: [R1b-U106] FamilyTreeDNA provides Y-DNA haplogroups from Family Finder autosomal tests? I paid FTDNA for a family finder; they uploaded my aunts file from Ancestry and failed to provide me with the results of my family finder.? I can’t download paternal or mtdna .. only all. Although I know from family history who my family members are..the FTDNA didn’t run my ?DNA but Ancestry did under my aunt. Money wasted…?
|
Re: FamilyTreeDNA provides Y-DNA haplogroups from Family Finder autosomal tests
Ian Dundas asked: “If someone has previously uploaded their aDNA file from Ancestry and paid to have it unlocked, is there any benefit in having FTDNA do the FamilyFinder test as well? I already have the Big Y-700 and the full mtDNA.” ? I’ve not seen any direct comparisons of autosomal matches with a Family Finder test and an Ancestry upload. However, the companies have used different microarrays at different times. This means that there is sometimes very low SNP overlap. See the ISOGG autosomal SNP comparison chart comparing the overlap with the different chips. ?
? This low SNP overlap can affect the matching process. I have two different tests at MyHeritage and I get markedly different numbers of matches: ? - With my Ancestry transfer (tested on the Illumina OmniExpress) I have 10,379 matches
- With my direct test at MyHeritage on the Global Screening Array I have 8,946 matches
? In practical terms the difference in matches is not an issue as it’s the low matches are affected. MyHeritage has a major problem with false matches and inflated cM totals so I don’t trust matches there much under 30 cM anyway and have even had problems with matches up to 50 cM. ? I suspect that from an autosomal point of view there is probably little if anything to be gained by doing a new test at FamilyTreeDNA. The FTDNA autosomal DNA database is very small and you’re going to get the vast majority of your best matches at AncestryDNA. ? If you’ve done the BigY test and the mtDNA full sequence test, you are not going to receive any new information from the small number of Y-SNPs and mtDNA SNPs on the Family Finder chip. Microarrays are only testing known SNPs so there is no scope for discovery. ? For someone who hasn’t done any Y-DNA testing then I think there are considerable benefits for males taking a Family Finder test direct with FTDNA rather than transferring from AncestryDNA as FTDNA treat the results very differently. Here is the information provided by FTDNA to group administrators about the differences: ? “Customers who transferred from Ancestry or 23andMe and have unlocked their transfer will be able to view their Y-DNA haplogroup, but it will not be used in the Y-DNA haplotree or Discover? statistics, nor will their matches or group projects be able to view it. ? Customers who tested with MyHeritage and Vitagene and have unlocked their transfers will be visible to matches. ? Customers who took a Family Finder test directly with FamilyTreeDNA will be able to see: - Y-DNA haplogroup badge (confirmed haplogroup)
- Y-STR Results section with Y-DNA haplotree & Y-SNPs and Discover reports
- Y-SNP download file under Family Finder Results–Download Raw Data
? Like a customer who has done a Y-STR or Big Y test: - Their Y-DNA haplogroup will be counted in the Haplotree and Discover statistics
- Their matches will be able to view their Y-DNA haplogroup,
- The Y-DNA haplogroup will be visible in Group Projects (if they have a test that shows up in project reports).
? Y-STR Tests and Autosomal Tests in Group Projects - For project members who have Y-STR tests and an Ancestry or 23andMe transfer, their STR-predicted Y-DNA haplogroup will show in the project.
- For project members have a Y-STR test and a MyHeritage or Vitagene transfer, their Family Finder Y-DNA haplogroup will show in the project.
- For project members who do not have a Y-STR test but are in Group Projects, their Y-DNA haplogroup will show under the SNP Report if it is from a Family Finder test or an unlocked MyHeritage/Vitagene transfer.
- For project members with Ancestry and 23andMe unlocked transfers, their Y-DNA haplogroup from Family Finder will not have display on the Y-SNP report.”
? Best wishes ? Debbie Kennett
|
Re: Family Finder tests entering the Y-DNA haplotree
These are just my observations, and initial ones at that.
It appears to me that mostly older Y SNPs are found in Family Finder. However, by older I don't mean older TMRCAs for the associated haplogroups.? I mean older or earlier in terms of discovery and naming.? I can tell this by looking at the personal haplotrees of some of these people. The SNP names are that are oftentimes marked as derived or ancestral are SNPs discovered years ago.?
However, many SNPs are recurrent, probably many more than we've identified so an SNP that was discovered along time ago in a large haplogroup may be part of a phylogenetic equivalent block in a different, young haplogroup.?? I have seen several SNPs discovered in haplogroup O individuals that are part of haplogroup R phylogenetic blocks.? This should not be surprising since haplogroup O is very, very large, being common in East Asia.
In these circumstances, it is not unlucky to have a early discovered, recurrent SNP in your terminal haplogroup phylogenetic block. It turns out to be very lucky as you can run into genealogical timeframe related people in Family Finder who have the same old (in naming only) recurrent SNP.
Haplogroup naming can be tricky in these situations. If you have a terminal haplogroup phylogenetic block of several SNPs. Any fixed/targeted SNP testing, be it from autosomal chip or pack/panel chip testing or singleton testing needs to be looked at closely.? FTDNA might assign the haplogroup based on the lead SNP they chose for the block. An individual assigned to that haplogroup by Family Finder may NOT be positive for that lead SNP.? In fact, the Family Finder individual may not even a descendant of the haplogroup block MRCA, but may actually *split* the block.
As an aside, there appears to be a R-U198 person who is negative for one of the SNPs in the R-U198 phylogenetic.
|
Ewenn
John Terwiske