开云体育

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: Family Finder haplogroups

 

Hi Debbie,

Thank you for these detailed and very informative explanations. In summary, there appears to be extremely little chance that new Y chromosome positions will be covered by the Omniexpress chips. We will therefore have to make do.

I must admit that I remain a little confused with the definitions of SNPs and RSID. Maybe that’s where my incomprehension comes from. I'm also not very familiar with microarray chip-based analysis techniques (I just understood that Affymetrix and Illumina chip-based analyzes are slightly different).

In my mind, a SNP designates both the position in the genome (locus) and the nucleotide (base). In short, to return to my previous example, Z921 and FGC57405 are two different SNPs (two different mutations of the same ancestral base A), located at the same position of the Y chromosome. Is that correct?
Since the A to T mutation has never (it seems) been listed, and therefore taken into account for the GSA chip, it would in fact be undetectable by said microarray chip? Finally, if FGC57405 is detected, it is because this A to G mutation was known during the development of the GSA chip, and these developers voluntarily and specially chose to look for it (and not just A/C which corresponds to Z921) ? To summarize, the GSA chip can detect the presence of bases A, G or C at position 11,506,634 of the Y chromosome, but will never be able to detect T (if this mutation exists in someone)...

If someone could take a little time to shed some light on these points which must seem very basic to more than one of you, I would be very grateful (I am probably not the only one to experience a little confusion).

Cheers,

Ewenn


Le lun. 3 juin 2024, 13:13, Debbie via <debbiekennett=[email protected]> a écrit?:

Ewenn

?

FTDNA and MyHeritage have always used the same chips for their autosomal DNA tests. All the testing is done at the Gene by Gene labs in Texas. The only difference is that the companies process the results, the reports and the match lists separately using their own independent algorithms. Both companies originally used the Illumina OmniExpress. They changed over to the Illumina Global Screening Array in around 2019 though I’m not sure of the date.

?

The OmniExpress has been around in various forms since 2007 when 23andMe first launched their test. There is some information on the different versions here:

?

?

Illumina allow you to add custom SNPs and 23andMe will have added additional Y-SNPs to provide better haplogroup resolution. Neither MyHeritage nor FTDNA previously provided haplogroup reports so I doubt that in the early years they would ever have added any custom Y-SNPs. The SNPs on the OmniExpress were mostly those discovered through the HapMap Project and back in those days very few Y-SNPs were known so I don’t anticipate we will get very much resolution when the OmniExpress haplogroup reports start to go out. By definition, microarrays only cover known SNPs so there are no possibilities for SNP discovery. I very much doubt that there are Y-SNPs on the old OmniExpress that are not included on the GSA. However, some SNPs can’t be called very accurately on microarrays so it’s possible some of the early SNPs have since been dropped because of their unreliability.

?

AncestryDNA use a customised version of the Illumina OmniExpress. As far as I’m aware they have never changed to the GSA. According to Tim Janzen’s autosomal DNA testing comparison chart in the ISOGG Wiki there are now 1691 Y-SNPs included in the AncestryDNA test. You can get a list of these SNPs if you download your raw data from Ancestry. They are labelled as chromosome 24.

?

?

It may well be that the Y-SNPs reported by Ancestry are the same ones that are included on the OmniExpress chip used by FTDNA and MyHeritage.

?

Best wishes

?

Debbie Kennett

?

?

From: [email protected] <[email protected]> On Behalf Of Ewenn via
Sent: Thursday, May 30, 2024 9:00 PM
To: [email protected]
Subject: Re: [R1b-U106] Family Finder haplogroups

?

Thank you very much Debbie for sharing this explanatory information with the rest of us!

?

The question I ask myself, and which seems to remain unanswered, is whether the other chips previously used by FTDNA, like the one currently used by MyHeritage, would not be able to detect some new SNPs uncovered by the latest chip whose results we have seen appear in recent months? Small hope, probably vain in my case, of seeing newcomers appear on certain branches of the Y tree not covered until now...?It would seem interesting to me to be able to know the positions of the Y chromosome covered by the different chips (those covered by the chip currently in use at FTDNA for their autosomal tests had previously been shared in a previous post on this forum).

?

Small subtlety to find additional information on some new FF testers added who have provided the location of their EKA:

In the SNP Map tool, these new testers do not necessarily appear when searching with the matching SNP with the assigned haplogroup name. An example with R-FGC57423 covered by the current chip used for FTDNA autosomal testing. A search with FGC57423 will not yield anything new. If the search is carried out with FGC57405, which is the SNP of this haplogroup covered by the said chip (unless I am mistaken, all possible mutations of the nucleotide at this position of the Y chromosome are theoretically detectable in the process, therefore any SNP already identified at this same position is also theoretically identifiable), a geolocation of the EKAs provided by the new FF testers appears. A significant problem nevertheless exists with this tool as designed by FTDNA: if the same SNP (the same mutation at an identical position on the Y chromosome) is identified in at least two distinct haplogroups, it is sometimes possible (but not obligatory) that testers from these two haplogroups find themselves mixed in the results displayed...

?

Cheers,

?

Ewenn

?

Le jeu. 30 mai 2024, 14:09, Debbie via <debbiekennett=[email protected]> a écrit?:

FamilyTreeDNA have advised group administrators that they have now completed the process of updating Y-DNA haplogroup assignments for everyone who tested on the current chip (the Illumina Global Screening Array). They are now working on updating haplogroups for customers tested on the old Illumina chip (the OmniExpress).

?

FTDNA have also provided some useful information about the SNPs included on the chips. Here’s an extract from their e-mail to group admins:

?

“We have received numerous requests for a count or list of the Y-DNA SNPs included on the Family Finder test chips(s). The exact number varies between chips. For example, the Ancestry v1 and v2 chips differ, and both differ from the MyHeritage chip.

?

The GSA chip (the one currently used by FamilyTreeDNA) covers more than 3,250 haplotree branches (no calls for any given SNP are, of course, possible). The total number of SNPs tested is a little misleading because of several factors (validation status, tree status, duplicates, triallelics, etc.).

In addition, some of the SNPs are duplicates found in multiple haplogroups and, therefore, not included in the haplotree. What's important is that as more people from rare branches test both FF and Big Y, the number of branches will expand over time.”

?

Best wishes

?

Debbie Kennett


Re: Family Finder haplogroups

 

开云体育

Ewenn

?

FTDNA and MyHeritage have always used the same chips for their autosomal DNA tests. All the testing is done at the Gene by Gene labs in Texas. The only difference is that the companies process the results, the reports and the match lists separately using their own independent algorithms. Both companies originally used the Illumina OmniExpress. They changed over to the Illumina Global Screening Array in around 2019 though I’m not sure of the date.

?

The OmniExpress has been around in various forms since 2007 when 23andMe first launched their test. There is some information on the different versions here:

?

?

Illumina allow you to add custom SNPs and 23andMe will have added additional Y-SNPs to provide better haplogroup resolution. Neither MyHeritage nor FTDNA previously provided haplogroup reports so I doubt that in the early years they would ever have added any custom Y-SNPs. The SNPs on the OmniExpress were mostly those discovered through the HapMap Project and back in those days very few Y-SNPs were known so I don’t anticipate we will get very much resolution when the OmniExpress haplogroup reports start to go out. By definition, microarrays only cover known SNPs so there are no possibilities for SNP discovery. I very much doubt that there are Y-SNPs on the old OmniExpress that are not included on the GSA. However, some SNPs can’t be called very accurately on microarrays so it’s possible some of the early SNPs have since been dropped because of their unreliability.

?

AncestryDNA use a customised version of the Illumina OmniExpress. As far as I’m aware they have never changed to the GSA. According to Tim Janzen’s autosomal DNA testing comparison chart in the ISOGG Wiki there are now 1691 Y-SNPs included in the AncestryDNA test. You can get a list of these SNPs if you download your raw data from Ancestry. They are labelled as chromosome 24.

?

?

It may well be that the Y-SNPs reported by Ancestry are the same ones that are included on the OmniExpress chip used by FTDNA and MyHeritage.

?

Best wishes

?

Debbie Kennett

?

?

From: [email protected] <[email protected]> On Behalf Of Ewenn via groups.io
Sent: Thursday, May 30, 2024 9:00 PM
To: [email protected]
Subject: Re: [R1b-U106] Family Finder haplogroups

?

Thank you very much Debbie for sharing this explanatory information with the rest of us!

?

The question I ask myself, and which seems to remain unanswered, is whether the other chips previously used by FTDNA, like the one currently used by MyHeritage, would not be able to detect some new SNPs uncovered by the latest chip whose results we have seen appear in recent months? Small hope, probably vain in my case, of seeing newcomers appear on certain branches of the Y tree not covered until now...?It would seem interesting to me to be able to know the positions of the Y chromosome covered by the different chips (those covered by the chip currently in use at FTDNA for their autosomal tests had previously been shared in a previous post on this forum).

?

Small subtlety to find additional information on some new FF testers added who have provided the location of their EKA:

In the SNP Map tool, these new testers do not necessarily appear when searching with the matching SNP with the assigned haplogroup name. An example with R-FGC57423 covered by the current chip used for FTDNA autosomal testing. A search with FGC57423 will not yield anything new. If the search is carried out with FGC57405, which is the SNP of this haplogroup covered by the said chip (unless I am mistaken, all possible mutations of the nucleotide at this position of the Y chromosome are theoretically detectable in the process, therefore any SNP already identified at this same position is also theoretically identifiable), a geolocation of the EKAs provided by the new FF testers appears. A significant problem nevertheless exists with this tool as designed by FTDNA: if the same SNP (the same mutation at an identical position on the Y chromosome) is identified in at least two distinct haplogroups, it is sometimes possible (but not obligatory) that testers from these two haplogroups find themselves mixed in the results displayed...

?

Cheers,

?

Ewenn

?

Le jeu. 30 mai 2024, 14:09, Debbie via <debbiekennett=[email protected]> a écrit?:

FamilyTreeDNA have advised group administrators that they have now completed the process of updating Y-DNA haplogroup assignments for everyone who tested on the current chip (the Illumina Global Screening Array). They are now working on updating haplogroups for customers tested on the old Illumina chip (the OmniExpress).

?

FTDNA have also provided some useful information about the SNPs included on the chips. Here’s an extract from their e-mail to group admins:

?

“We have received numerous requests for a count or list of the Y-DNA SNPs included on the Family Finder test chips(s). The exact number varies between chips. For example, the Ancestry v1 and v2 chips differ, and both differ from the MyHeritage chip.

?

The GSA chip (the one currently used by FamilyTreeDNA) covers more than 3,250 haplotree branches (no calls for any given SNP are, of course, possible). The total number of SNPs tested is a little misleading because of several factors (validation status, tree status, duplicates, triallelics, etc.).

In addition, some of the SNPs are duplicates found in multiple haplogroups and, therefore, not included in the haplotree. What's important is that as more people from rare branches test both FF and Big Y, the number of branches will expand over time.”

?

Best wishes

?

Debbie Kennett


Re: disabled email for kits you have paid for

 

开云体育

A person's DNA will always be theirs no matter who paid for it. This is the stance of FTDNA and a proper one in my opinion.?

I do not believe FTDNA disabled your email, but the person did most likely.?

Robert McMillan

On Jun 2, 2024, at 4:35?AM, Priscilla Jean Tennant Skar <pjtskar@...> wrote:

?What have you others done when
You have kits you have paid for and yours was the main email that is now disabled?
I have no problem if people want to take over their kits but when I save to buy a bigY and FTDNA disables my email
with out a refund is not fair
I am not getting what I paid for??

Jean


disabled email for kits you have paid for

 

What have you others done when
You have kits you have paid for and yours was the main email that is now disabled?
I have no problem if people want to take over their kits but when I save to buy a bigY and FTDNA disables my email
with out a refund is not fair
I am not getting what I paid for??

Jean


Re: Family Finder haplogroups

 

FYI I've just had notification that my Family Finder (tested 2015) derived haplogroup is R-CTS10893

This matches what the Chris Morley haplogroup predictor said for my Ancestry results, which is comforting!

Regards, Andy.


Re: TMRCAs < was: Block Tree Question

 

Thanks, Iain for taking the time to explain this. I appreciate your contributions here and at the sadly defunct Anthrogenica.

Shane


Re: Block Tree Question

 

Thanks to everyone for their help, really appreciated. That was a great explanation, Mike. Even an Art Major understood it. I never really thought about a bridge subclade connecting to another haplogroup. I guess I always assumed any in-between subclades would already show up in the results. ?

Given the tribal nature of the early Germanics, it would seem pretty likely to find many seemingly unrelated subclades that were part of the same historical experience for at least some period of time. It is interesting that when looking at the FGC-17460 participants in our U106 project, they all seem to divide essentially into two STR haplotypes. One group are DYS392-12 and DYS389ii-29 while the others are DYS392-13 and DYS389ii-30. Almost all are DYS439-10. I know not to make too much of STRs, but it seems fairly consistent. Whether or not that means anything, I have no clue.

Shane?


Re: Family Finder haplogroups

 
Edited

Hi Vince,

?

Thank you for the clarification. I do not claim to be an expert in genetic analysis, and I certainly have a large number of gaps to fill in order to claim to understand a lot about the subject that interests us here. My previous comments are mainly based on personnal empirical observations and are therefore certainly not accurate. However, I may also have poorly worded and/or detailed my remarks. So I will try to clarify these (English not being my native language this probably does not help me).

?

In my previous post, I did not want to express that these famous micro-array chips could discover new SNPs previously unknown in the Y tree*. I was just wondering if the ??old?? Illumina chip used by FTDNA for these earlier FF tests could cover new Y chromosome positions not covered by the current GSA chip; positions where SNPs have already been identified. For example, the chip used in 2021 at MyHeritage covers, among others, the following SNPs: FT459752 (R-BY160589, rs112197623, 20313517), BY83023 (R-BY66068, rs62608681, 10182366), L199 (R-FGC398, rs781 777817, 1336586) and Z251 (R-ZP61, rs746402982, 8868293). These SNPs do not seem to me to be covered by the GSA chip used by FTDNA. It would therefore possibly be possible that the old Illumina chip could also cover certain SNPs for which no detection was possible with the GSA chip…

If new bigY testers come to form new branches in the Y tree (terminal or not), the new associated SNPs “discovered” would then possibly be possibly covered by the GSA chip, the Illumina chip, or the chip used by MyHeritage, etc.


*

now it's incredibly unlikely that a microarray chip could be relied upon to create new branches on the phylogenetic tree without followup testing with Big Y or WGS.

I asked FTDNA a question last December regarding the possible comparison of autosomal test (FF) results with Pvs identified in bigY testers. Their answer :

摆…闭 The short answer is yes, in very rare instances we have found SNPs that have been previously seen in only one other tester in the database. These situations have allowed us to form new branches.




When "I stated" that, "theoretically", it was possible for a microarray type chip to detect "all" possible mutations (there are possibly technical limitations invalidating this, so I in no way guarantee that all mutations such that A to C, A to T, A to G… are really detectable, but probably more than one for the same position of the genome) on the same position, I based myself on an empirical observation concerning the SNP FGC57405 (identified for the first time by Full Genome Corp in 2016, position 11 506 634, mutation A to G). This SNP is only associated, in the current Y haplotree, with the haplogroup R-FGC57423 (excluding PVs possibly... TMRCA ~600 BCE). This haplogroup (and downstream) is only made up of 4 bigY testers to date. I didn't really see why this particular SNP, confidential in a sense, would be voluntarily covered by the GSA chip??? Especially since it does not appear in the file that you linked in your post #7704. However, at the same position 11,506,634 of the Y chromosome we find another SNP identified, namely Z921. Z921 (mutation A to C, identified by Ray Banks in 2011 according to ybrowse.org) is currently only associated with the much older haplogroup E-M132 (TMRCA ~17,420 BCE). It is therefore much more likely that the original target targeted by the GSA microarray chip was Z921 than FGC57405. I therefore concluded that it seemed possible for FTDNA to detect mutations other than the mutation initially sought at a specific position on the Y chromosome (the tagged nucleotides I believe, ).




About the “SNP Map tool”. This is not a part of Discover. This is a tool developed by FTDNA some time ago (accessible in Others, Y-DNA section, from the main page of your FTDNA account). You can make hot spots appear on a world map by selecting up to 6 SNPs, as well as a distance, expressed in km or miles, to take into account between the coordinates provided by each test (geolocation of EKA). If you select a distance to take into account such as 40 000 km/miles, you cover the entire globe. I derived a curl query model allowing to directly return the coordinates (latitude + longitude) of the results. I personally find this tool (although it presents some problems) quite interesting to learn a little more about testers belonging to a haplogroup that interests you, and for which you do not have information via FTDNA groups such as R-U106.

For example, for FGC57405 (28 FF testers have been added to R-FGC57423 by FTDNA in recent months, including 3 Swedes, 1 German, 1 Pole who took an STR test, a Lithuanian, an American, a Russian who is actually of German origin and having also passed a STR test, and 20 testers of unknown origin), I obtain:

  • "latitude":48.1800343,"longitude":10.7557069 厂肠丑飞补产尘ü苍肠丑别苍, Bavaria, Germany

  • "latitude":58.754921299999992,"longitude":11.894160199999988 H?gs?ter, V?stra G?taland (SE-O), Sweden

  • "latitude":58.6502862,"longitude":12.055313100000035 H?gs?ter, V?stra G?taland (SE-O), Sweden

  • "latitude":52.7706661,"longitude":22.954561499999954 Bujnowo, Podlaskie Voivodeship, Poland

  • "latitude":49.3048,"longitude":25.7049 Terebovlya, Ternopil Oblast, Ukraine

  • "latitude":51.5923654,"longitude":45.960803199999987 Saratov, Saratov Oblast, Russia


Cheers,

Ewenn


Re: Block Tree Question

 

Shane

Iain gave a thorough reply regarding TMRCA on /g/R1b-U106/topic/106393562 that you may not have seen that would answer your first question.

Regarding relatedness with those in FGC17460 vs downstream terminal groups and to expand on what Vince said: Those in the downstream terminal haplogroups are also in FGC17460 and therefore you are all "equally" related. You all had the same terminal haplogroup (FGC17460) before a couple of them got matches forming a new terminal haplogroup. That did not make them less related to the group; it only made them more closely related to each other.
An analogy may help. Think of FGC17460 as a group of Europeans. You are all equally related because you are all Europeans (we know nothing else about you yet). Investigating further we find a pair of you who are French and another pair who are German so they form two downstream groups. You don't know who you are yet because no one matches you well enough to form a group. But you happen to be Swiss and the other two Europeans are British and Portuguese. You are a "match" to the French and Germans because you are a little more closely related to them than you are to the other two. In terms of NMVs, you could be just a bit one side or the other to whatever the cutoff for a "match" is.
In theory, you could form another group with those downstream groups who are matches; a haplogroup intermediate between your current one and theirs that would become your new terminal haplogroup, but not theirs. Sometimes it takes a long time for FTDNA to process that. Also keep in mind that "terminal" is somewhat meaningless unless its just you and your father. The terminal haplogroups evolve as more results come in and should really be "most recent" haplogroup.

Cheers
Mike


Re: Family Finder haplogroups

 

Ewenn,

?

Technically speaking, the microarray chips do not "discover" new Y-SNPs. ?SNPs must be observed BEFORE they are added to the array.

In the early days we didn't always know where on the tree each Y-SNP belonged, but with hundreds of thousands of WGS and NGS samples sequenced now it's incredibly unlikely that a microarray chip could be relied upon to create new branches on the phylogenetic tree without followup testing with Big Y or WGS.

I'm not sure which "SNP Map tool" the rest of your post refers to. ?If you mean the haplogroup migration map (e.g. GlobeTrekker), the FamilyFinder tests are not suited for use in that model because of their limited coverage and the inability to reliably estimate TMRCAs from FamilyFinder-based Y-haplogroups.

?

Vince

?


Re: Family Finder haplogroups

 

Thank you very much Debbie for sharing this explanatory information with the rest of us!

The question I ask myself, and which seems to remain unanswered, is whether the other chips previously used by FTDNA, like the one currently used by MyHeritage, would not be able to detect some new SNPs uncovered by the latest chip whose results we have seen appear in recent months? Small hope, probably vain in my case, of seeing newcomers appear on certain branches of the Y tree not covered until now...?It would seem interesting to me to be able to know the positions of the Y chromosome covered by the different chips (those covered by the chip currently in use at FTDNA for their autosomal tests had previously been shared in a previous post on this forum).

Small subtlety to find additional information on some new FF testers added who have provided the location of their EKA:
In the SNP Map tool, these new testers do not necessarily appear when searching with the matching SNP with the assigned haplogroup name. An example with R-FGC57423 covered by the current chip used for FTDNA autosomal testing. A search with FGC57423 will not yield anything new. If the search is carried out with FGC57405, which is the SNP of this haplogroup covered by the said chip (unless I am mistaken, all possible mutations of the nucleotide at this position of the Y chromosome are theoretically detectable in the process, therefore any SNP already identified at this same position is also theoretically identifiable), a geolocation of the EKAs provided by the new FF testers appears. A significant problem nevertheless exists with this tool as designed by FTDNA: if the same SNP (the same mutation at an identical position on the Y chromosome) is identified in at least two distinct haplogroups, it is sometimes possible (but not obligatory) that testers from these two haplogroups find themselves mixed in the results displayed...

Cheers,

Ewenn

Le jeu. 30 mai 2024, 14:09, Debbie via <debbiekennett=[email protected]> a écrit?:

FamilyTreeDNA have advised group administrators that they have now completed the process of updating Y-DNA haplogroup assignments for everyone who tested on the current chip (the Illumina Global Screening Array). They are now working on updating haplogroups for customers tested on the old Illumina chip (the OmniExpress).

?

FTDNA have also provided some useful information about the SNPs included on the chips. Here’s an extract from their e-mail to group admins:

?

“We have received numerous requests for a count or list of the Y-DNA SNPs included on the Family Finder test chips(s). The exact number varies between chips. For example, the Ancestry v1 and v2 chips differ, and both differ from the MyHeritage chip.

?

The GSA chip (the one currently used by FamilyTreeDNA) covers more than 3,250 haplotree branches (no calls for any given SNP are, of course, possible). The total number of SNPs tested is a little misleading because of several factors (validation status, tree status, duplicates, triallelics, etc.).

In addition, some of the SNPs are duplicates found in multiple haplogroups and, therefore, not included in the haplotree. What's important is that as more people from rare branches test both FF and Big Y, the number of branches will expand over time.”

?

Best wishes

?

Debbie Kennett


TMRCAs < was: Block Tree Question

 

Hi folks,

?

The exact details of FTDNA's TMRCA calculations are not public. There's supposed to be a White Paper on it, but they haven't got around to writing it yet. Some parts of it are based on the article I wrote following my meeting with them in 2020. If you want all the gory details of that, they're here:
https://www.mdpi.com/2073-4425/12/6/862
I'll try to give a beginner's guide here.

?

SNPs are actually the only form of variant that FTDNA tracks, so their non-matching variants list is really the number of SNPs that differ between two people.

?

A SNP is simply an error in copying - the accidental replacement of one molecule with another in the genetic sequence. We don't know if this is truly random at the quantum mechanical level, but it is close enough to random that we can treat the formation of SNPs as a random process.

?

Many people struggle with the concept of random processes. There are many similar processes in nature. A good example for our purposes is the number of weeds growing in a square inch of garden: if you till a garden bare and wait, weeds will grow and increase in number over time. Similarly, we can take an ancestor's Y chromosome and see how it accumulates SNPs as it is passed down to different lineages.

?

If you have an idea how fast weeds grow in your part of the world, you can tell by looking at the garden and the number of weeds in it approximately how long it's been since the soil was tilled. Let's say it normally takes two days for the first weeds to germinate, and you might have an average of seven weeds per inch after a fortnight. Similarly, you can tell the length of time it's been since two people were related (their TMRCA) by looking at the number of SNPs that differ between their Y chromosomes - provided you know how often SNPs form. We know that one SNP happens in every molecule (base pair) of DNA about every 1.25 billion years, on average.

?

However, the number of weeds you actually get depends on the size of your garden. The more area your garden has, the more weeds will grow. Similarly, the number of SNPs you can expect depends on the size of your Y chromosome test. This varies slightly from test to test, and with how low a quality of SNP you are prepared to accept. However, a good rule of thumb is that there are about 10 million base pairs in an old BigY-500 test and about 15 million base pairs in a modern BigY-700 test. This means a BigY-500 test gets a new SNP every 125 years or so, and a BigY-700 test gets a new SNP every 83 years or so. The comparison between every pair of tests is slightly different, as no two tests cover exactly the same parts of the Y chromosome.

?

Also, if you have a flowerpot that's only a square inch, you might not get seven weeds after a fortnight. You might have only three or you might have twelve, it just depends on how many seeds land in your tiny flowerpot. Similarly, if you are looking at two BigY tests related 290 years ago, you might expect them to have seven non-matching variants between them (290 / 83 * 2 = 7), but they might actually only have three or twelve. It really depends on luck. This means that there's no one-to-one correspondence between the number of non-matching variants that differ between two people and how long ago they are related. All we can do is compare them to the statistical average we expect, and establish some range of time during which the real date is likely to happen (the confidence interval). (The mathematics of how to estsablish confidence intervals is governed by Poisson statistics - a branch of mathematics that was originally devised to deal with another random process: the number of Prussian soldiers kicked to death by their own horses.)

?

This gives us an inexact mapping between number of non-matching variants and actual TMRCA, which is why exact TMRCAs are impossible to calculate. How can we improve the accuracy of our TMRCAs? We somehow have to increase the size of our garden. If you take a different square-inch flowerpot, it will have a different number of weeds. If you take many square-inch flowerpots that were planted a fortnight ago, you would find eventually get an average that settles down to our expected seven weeds in each.

?

We have two options when it comes to genetic tests. We can either take bigger and better tests - this may be possible in the future, but we are close to running out of Y chromosome to test! Another option is to look at more testers. If you take a man who has two sons, each son's family will accrue an independent set of new SNPs, each of which can provide an estimate of the TMRCA. If you can add in a third son's family, then you have three independent sets of SNPs, and their average number (multiplied by 83) should give you a smaller confidence interval that is closer to the real TMRCA. Adding a fourth son would improve things further, etc., but there is a law of diminishing returns - the difference between 99 and 100 sons is very small!

?

Not even the most prolific father has 100 sons, all of whom have descendants today. However, if you run out of sons, then two grandsons from the same son have *almost* independent sets of SNPs, so they are *almost* as good at improving the TMRCA. Conversely, however, testing your brother isn't effective, since you and your brother's sets of SNPs aren't independent of each other - you will share most or all of them. This is the reason I would not suggest encouraging brothers or close cousins to take a BigY test if you have already done so, unless there is a very specific reason for doing so. Normally, there's no benefit from testing anyone closer than about fourth cousins and, if you do want to test additional family to improve your TMRCA, then test the most distant cousin you can find, as their SNPs will be the most independent of yours.

?

Hopefully this gives you some insight into TMRCAs and how they can be improved. I should point out that FTDNA's TMRCAs also use Y-STRs as well as Y-SNPs, though these obviously aren't reported in your non-matching variants lists. It's possible to also include other larger mutations in DNA (e.g. MNPs, insertions, deletions, etc.), but these are unreliably reported by BigY in many cases. My paper sets out the basic principles behind how each of these can be used.

?

Best wishes,

?

Iain.


Re: Block Tree Question

 

开云体育

Shane,

It’s not possible for a haplogroup to contain just one man. ?I count over 70 men in haplogroup?R-FGC17460, so I’d say that TMRCA estimate is pretty robust.

Furthermore, in a case like yours it would be incorrect to say that you are more closely distantly related to men who are in a subclade of?R-FGC17460 than to other men who share your assignment of?R-FGC17460. ?That’s because, for you,?R-FGC17460 is technically a paragroup and not a terminal haplogroup. ?From a Big Y perspective, you are equally close to all 71 other men in?R-FGC17460.

Finally, the number of NMVs can vary for reasons besides closeness of genealogical relationship. ?There is a random chance element, of course, but different customers might have different versions of the Big. Y test. ?You’ll generally have few NMVs with men who took the original Big Y or Big Y 500 test than with men who took Big Y 700. ?FTDNA account for that in estimating TMRCAs, but the matches are based on a the raw (unadjusted) count.

Vince


On May 30, 2024, at 12:09 PM, smdtarry@... wrote:

Mike,
From what you said, it seems that the accuracy of a TMRCA depends on the number of examples that can be tested. Since it's just me the results are likely to be off by a significant amount, right?

Not exactly related but I'd like to hear opinions: I've read often that I'm actually more closely related to those who share my terminal haplogroup than to those who have downstream subclades. So it seems odd to me that neither of the two men who are stuck at FGC17460 with me shown up as matches, yet four men who have several subclades beyond me are matches. Is there any rhyme or reason to the number of NMVs you can have with someone in a close branch?

Shane


Re: Block Tree Question

 

Mike,
From what you said, it seems that the accuracy of a TMRCA depends on the number of examples that can be tested. Since it's just me the results are likely to be off by a significant amount, right?

Not exactly related but I'd like to hear opinions: I've read often that I'm actually more closely related to those who share my terminal haplogroup than to those who have downstream subclades. So it seems odd to me that neither of the two men who are stuck at FGC17460 with me shown up as matches, yet four men who have several subclades beyond me are matches. Is there any rhyme or reason to the number of NMVs you can have with someone in a close branch?

Shane


Re: Block Tree Question

 

All that's been said here regarding TMRCA is correct but a real world example may help. The 83 year rule is very much an average and, as such, is reasonably close over long periods of time, say 1,000 years or more. But the shorter the time the less accurate it becomes. I ran a study of 13 men, all descendants of one man born in 1646. We are descendants of four of his sons and continue to branch further over time. 8-10 generations have passed with half of us at 9 generations since the birth of our MRCA. The number of NMVs that have grown into each of those lineages varies from 2 to 7. If you were to compare any two of us using the [(NMV/2) x 83] formula you could get a birth year for our MRCA of 1858 to 1485. When doing this for each possible pair of us, the distribution does come very close to the expected Poisson distribution that is the basis for the confidence interval that FTDNA gives.


Re: Block Tree Question

 

Thanks for the replies Vince and Myles. TMRCA has always been a bit of a mystery, this helps.


Family Finder haplogroups

 

开云体育

FamilyTreeDNA have advised group administrators that they have now completed the process of updating Y-DNA haplogroup assignments for everyone who tested on the current chip (the Illumina Global Screening Array). They are now working on updating haplogroups for customers tested on the old Illumina chip (the OmniExpress).

?

FTDNA have also provided some useful information about the SNPs included on the chips. Here’s an extract from their e-mail to group admins:

?

“We have received numerous requests for a count or list of the Y-DNA SNPs included on the Family Finder test chips(s). The exact number varies between chips. For example, the Ancestry v1 and v2 chips differ, and both differ from the MyHeritage chip.

?

The GSA chip (the one currently used by FamilyTreeDNA) covers more than 3,250 haplotree branches (no calls for any given SNP are, of course, possible). The total number of SNPs tested is a little misleading because of several factors (validation status, tree status, duplicates, triallelics, etc.).

In addition, some of the SNPs are duplicates found in multiple haplogroups and, therefore, not included in the haplotree. What's important is that as more people from rare branches test both FF and Big Y, the number of branches will expand over time.”

?

Best wishes

?

Debbie Kennett


Re: Block Tree Question

 

开云体育

Also 65% CI.? In my case, my closest BigY match and I each have 2 NMVs.? FTDNA estimates common ancestor born about 1764.? Our common ancestor was actually born in 1654, just beyond the 65% confidence interval.? Despite this information, one of my more distant Y-matches keeps insisting there must be a problem with my and my 7th cousin’s ancestry because our common ancestor must have been born about 1764…some folks think it’s exact science.

?

From: [email protected] [mailto:[email protected]] On Behalf Of vineviz
Sent: Wednesday, May 29, 2024 11:02 AM
To: [email protected]
Subject: Re: [R1b-U106] Block Tree Question

?

Shane,

The correct formula is for TMRCA is [(NMV/2) x years-per-NMV], but I'd suggest avoiding using this method and directly lookup the TMRCA estimate using FTDNA's "Discover" tool.

Their TMRCA estimates account for many factors that the simple rule of thumb measures can't account for. Plus FTDNA give you 95% and 99% confidence intervals in addition to the central estimate.

Regardless of the number NMVs, you are more closely related to people within your terminal haplogroup than to people outside of it. ?If you're in a paragroup it's a little different.


Vince


Re: Block Tree Question

 

Shane,

The correct formula is for TMRCA is [(NMV/2) x years-per-NMV], but I'd suggest avoiding using this method and directly lookup the TMRCA estimate using FTDNA's "Discover" tool.

Their TMRCA estimates account for many factors that the simple rule of thumb measures can't account for. Plus FTDNA give you 95% and 99% confidence intervals in addition to the central estimate.

Regardless of the number NMVs, you are more closely related to people within your terminal haplogroup than to people outside of it. ?If you're in a paragroup it's a little different.


Vince


Re: Block Tree Question

 

I did some searching for previous threads and found that the Block Tree has been confusing for more than just me. I understand that fewer NMVs means a relatively closer connection. But in my mind a "match" is something more meaningful that a 2-step haplogroup difference. My closest match appears to be around 1,826 years ago, if I did the math right (21 NMVs x 83). That's starting to get useful for my goal of better understanding my ancestry in the Early Middle Ages. Please correct me if I'm misunderstanding something.

Shane