Keyboard Shortcuts
Likes
- R1b-U106
- Messages
Search
Re: Question re: changes to haplogroup assignment
That Viking Settlement is known as L'Anse aux Meadows, Newfoundland, Canada.
No one knows if they had left any descendants on what is now Canadian soil, and no evidence is known of any contemporary adjacent indigenous occupation that could purvey a "cultural exchange".? Which isn't to say that they definitively do not exist, just that it is unlikely. Best regards, Vince T. |
Re: Question re: changes to haplogroup assignment
toggle quoted message
Show quoted text
On Oct 27, 2023, at 3:03 PM, Vince Tilroe <vtilroe@...> wrote:
|
Re: Question re: changes to haplogroup assignment
toggle quoted message
Show quoted text
On Oct 27, 2023, at 1:04?PM, Inventorb via groups.io <williamwarman@...> wrote:
|
Re: Question re: changes to haplogroup assignment
开云体育“?Vikings had a settlement in North America exactly one thousand years ago, centuries before Christopher Columbus arrived in the Americas, a study says.Scientists say a new dating technique analysing tree rings has provided evidence that Vikings occupied a site in Newfoundland, Canada, in 1021AD” On Oct 27, 2023, at 12:24?PM, Vince Tilroe <vtilroe@...> wrote:
|
Re: Question re: changes to haplogroup assignment
Thanks, Vince.? On Fri, Oct 27, 2023 at 15:24 Vince Tilroe <vtilroe@...> wrote: Hi Joe, |
Re: Question re: changes to haplogroup assignment
Hi Joe,
FTDNA dates R-M269 to about 4350 BCE, after a very long multi-millennial population bottleneck following the .? There are well over a hundred Y-SNPs in the R-M269 block. You could try testing your father-in-law for (or failing that, P312) which are probably the most common sub- R-M269 haplogroups in Spain, and presumably among Spanish / Portuguese conquistadors and their descendants. Best regards, Vince Tilroe |
Re: Question re: changes to haplogroup assignment
Hi Vince, My wife is 75% Mexican Indian and her father is R-M269.? Still trying to figure that one out.? Kind regards, Joe On Fri, Oct 27, 2023 at 14:46 Vince Tilroe <vtilroe@...> wrote:
|
Re: Question re: changes to haplogroup assignment
"First, we filter out samples with country/haplogroup combinations that don’t make sense for Pre-Columbian travel. For example, Eurasian haplogroup R1b should not be in the United States, nor should Native American haplogroup Q-M3 be in Europe." |
Re: Question re: changes to haplogroup assignment
Greetings Belinda,
toggle quoted message
Show quoted text
You are certainly spot-on with your diagnosis. Please do report on any response you may receive from FTDNA. Meanwhile, with the there-and-back scenario, we are neither here, nor there, nor here and there. It is the 20th Century Schizoid syndrome. Not only are SNP positions placed ahead of themselves on the migratory path, but the path itself becomes an unrealistic moving average of an actual historical migration. Other factors, such as incorrect user entered coordinates, will only wreak more havoc, in spite of the algorithm's effort to tame the situation. Perhaps v.2 will go some way toward incorporating aDNA data more fully, but I expect that the effort and potential cost in computing resources will rule that out. Cheers, Roy On 10/26/23 17:48, Belinda Dettmann wrote:
Hi Roy |
Re: Question re: changes to haplogroup assignment
Hi Roy
toggle quoted message
Show quoted text
I agree with you that Globetrekker has serious deficiencies, particularly in the case of R-U106 tests of German origin, like the House of Wettin or my own line R-BY96243 from Mecklenburg. The bias towards British samples or their American surrogates in the FTDNA database has made this inevitable and the methods used explain why: ""We perform several sample filtering steps. First, we filter out samples with country/haplogroup combinations that don’t make sense for Pre-Columbian travel. For example, Eurasian haplogroup R1b should not be in the United States, nor should Native American haplogroup Q-M3 be in Europe. Next, we conservatively filter out “Earliest Known Ancestor” (EKA) coordinates that differ from the listed EKA country. Customers may accidentally provide conflicting geographic information which is a convenient sanity check for us. We do relax this requirement by allowing a 500 km buffer between the two locations. We are also lenient in cases such as the example above: if an EKA coordinate is in America with haplogroup R1b, but the listed country is in Europe, we simply use the country instead. Now is a great opportunity to check your country and coordinate information to make sure it is consistent and correct! Finally, we check each branch for continental outliers. For example, if a branch contains four samples, with three in Europe but the fourth in South Africa, we rely on the first three. After samples are filtered, we also filter the tree. We want to carefully ensure that single branches don’t unduly influence the migration paths. If any branch contains only a single geographically informative sample, or its samples are no closer than 2,000 km apart, we collapse that branch."" The outcome of all this is that common modern localities, like Britain (or USA as a surrogate for Britain) overwhelm data for less-sampled haplogroups of European origin that never came to Britain, and the result is what I call there-and-back pathways which are obviously wrong, as Roy has shown. My brother has a similar pathway, though in a different branch of R-U106, through L48. In each case there are recent matches with German EKAs, so the pathway does actually return to the Continent from Britain. The actual situation should be that most of the Wettin line should be located on the continent, and only the most recent subclades which are separate from BY3240 should be hived off to Britain. The same applies to our R-BY96243 line which correctly ends up in Germany but apparently went to Britain and back through subclades that include CTS10893. I had thought that the use of ancient DNA samples might have alleviated this problem, but from Roy's data that does not seem to be the case. I made a comment on my brother's Globetrekker through the Feedback link but have heard nothing further on the subject. Belinda -----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Roy Sent: Friday, October 27, 2023 3:56 AM To: [email protected] Subject: Re: [R1b-U106] Question re: changes to haplogroup assignment Hello all, I have followed this thread with some interest and wish to contribute a few thoughts. First, however, I should mention that I have retired from the Admin business, and would encourage anyone with an interest in British Isles ancestry and a taste for challenges to consider joining Belinda in keeping the BIBC ship afloat. My chief reason for walking away from this sinecure was the unresponsiveness (i.e., total lack of response or acknowledgment) of FTDNA to attempts to propose refinements to the Discover tool. That said, the original aim of the project, founded when 12 STR markers were the norm and you could write all the haplogroup names, in long form, on a single sheet of paper, was to enable persons seeking British Isles ancestry to narrow their paper search to counties where their haplogroups predominated by mapping haplogroups to counties. Hence the project name: British Isles by County. Fast forward almost 20 years to the Discover era, and mapping is still the name of the game, although now the time threshold has been pushed back and we focus on prehistoric migrations rather than Atlantic crossings. To complicate matters, archaeogenetics has surged into the spotlight, and grows at an exponential rate. Yet it seems apparent, at least from my limited experience, that Discover, or specifically Globetrekker, has not yet leveraged ancient DNA to full advantage, even though the designers claim to have incorporated 2000 samples into the algorithms. I have prepared notes on a possible approach to improving the effectiveness of migration maps by incorporating ancient autosomal DNA into the calculations. It may be helpful to adopt ancient DNA sample sites as anchor points. I invite your comments: <> Cheers, Roy |
Re: Question re: changes to haplogroup assignment
Hello all,
I have followed this thread with some interest and wish to contribute a few thoughts. First, however, I should mention that I have retired from the Admin business, and would encourage anyone with an interest in British Isles ancestry and a taste for challenges to consider joining Belinda in keeping the BIBC ship afloat. My chief reason for walking away from this sinecure was the unresponsiveness (i.e., total lack of response or acknowledgment) of FTDNA to attempts to propose refinements to the Discover tool. That said, the original aim of the project, founded when 12 STR markers were the norm and you could write all the haplogroup names, in long form, on a single sheet of paper, was to enable persons seeking British Isles ancestry to narrow their paper search to counties where their haplogroups predominated by mapping haplogroups to counties. Hence the project name: British Isles by County. Fast forward almost 20 years to the Discover era, and mapping is still the name of the game, although now the time threshold has been pushed back and we focus on prehistoric migrations rather than Atlantic crossings. To complicate matters, archaeogenetics has surged into the spotlight, and grows at an exponential rate. Yet it seems apparent, at least from my limited experience, that Discover, or specifically Globetrekker, has not yet leveraged ancient DNA to full advantage, even though the designers claim to have incorporated 2000 samples into the algorithms. I have prepared notes on a possible approach to improving the effectiveness of migration maps by incorporating ancient autosomal DNA into the calculations. It may be helpful to adopt ancient DNA sample sites as anchor points. I invite your comments: <> Cheers, Roy |
Re: Testers for 1000 Genome Project
Thanks, James, for your response.?
I understand that the test subjects are only known by their ID number (i.e., HG00256) however, I did see on the Coriell Institute site that the subjects identified as "British from England and Scotland" came from five locations: Kent and Cornwall in England, and Orkney, Argyll, and Bute in Scotland.?Also, they were used as part of the People of the British Isles project which (per their website) "recruited volunteers whose four grandparents were born in rural areas of Britain, within 50 miles from one another". So, in that one of the subjects is a genetic match of mine on YFull, and appears as a member of haplogroup S3997 in the Discover Haplogroups Report Time Tree, I was hoping to simply find out if the tester was from Kent or Cornwall. Thanks again, Ed |
Re: Question re: changes to haplogroup assignment
开云体育?? Yes, we’ve been down this road a few times. My chief complaint each time is that FTDNA does not allow transfers from YSEQ. This would be ok for the occasional tester I presume, but for project managers, it is cumbersome at best. ? This is my chief complaint also. I have tested 7 individuals at YSEQ that answered questions as to which order SNPs occurred and roughly when. ?One of these individuals is no longer alive and so any hope FTDNA might have that he’d get a BigY test is zero. ?And yet, from his test results at YSEQ we know which SNPs from the Block Tree he has and which that he does not have. And by testing my father and progressively more distant cousins at YSEQ, we learned that my 2 PVs since a 1654 common ancestor with a 7th cousin BOTH happened with my father, versus sometime in the 1700’s or 1800’s.? Since I will not be paying FTDNA to test my father’s YDNA, let alone any of the cousins I tested, it is a huge missed opportunity that there is no way that the results of these targeted SNP tests cannot be imported and used by FTDNA to better assess SNP order and timing and to identify new haplogroups. ? And so, in my tree alone we have identified no less than 5 haplogroups that FTDNA will likely never recognize or acknowledge.? It truly is a missed opportunity. ? -MT |
Re: Question re: changes to haplogroup assignment
Hi Iain, Yes, we’ve been down this road a few times. My chief complaint each time is that FTDNA does not allow transfers from YSEQ. This would be ok for the occasional tester I presume, but for project managers, it is cumbersome at best. I know the history between the previous FTDNA owners and the current owner of YSEQ which I’ll reserve my comments regarding that situation.? It’s great that FTDNA took away this ability to pick and choose as needed; understanding this is a business decision. But it goes back to my original venting about limiting products and options for us all.? I’ve crunched the numbers myself and it would have made more sense to have more options. I use the y-12 quite frequently as an administrator just as a tool to know where to go with a particular tester. It would be nice if all customers had this option before proceeding with the much more expensive BigY-700 Kind regards, Joe On Wed, Oct 25, 2023 at 12:27 gubbins.t21 via <gubbins.t21=[email protected]> wrote:
|
Re: Question re: changes to haplogroup assignment
开云体育Hi Joe, YSeq obviously still offers these facilities. There, the cost of a panel is typically $100-$150, depending on size and, while the Y-12 test isn't offered as such, its approximate price would be about $50. So this figure of $150-$200 would be the approximate minimum that you're looking at paying for a panel plus Y-12 test at Family Tree DNA, were they to offer it. Once equipment costs are paid off, the main limitations for such tests are likely to be the cost of the physical bench space taken for equipment and human time spent developing panels and processing the tests. This is old technology, so the costs are likely to at best be stable with time. Panels are a limited, fixed test. To come back and explore new sub-clades in the future requires a whole new test, so this strategy freezes the branching structure at one point in time and doesn't allow progress via the discovery of new branches. It also offers no recourse for testers who are shown not to be related. Contrast this with the cost of a BigY-700 test with Y-111 included, which is on sale at $399, or roughly twice the price. While the headline price has decreased considerably over the years, this sale price has been fairly stable since not long after the original BigY test was introduced, so it looks like we are reaching the operating floor for costs here too, though it's worth noting that this represents a significant real-terms drop in costs given inflation. Each test also has the potential to discover new sub-clades and identify private mutations. In the long run, would $3990 be better spent on 10 BigY tests or 20 tests with limited Y-12 and SNP panel tests? That's an open question, but FTDNA took the decision a long time ago to bet on the first option, since Y-STR and BigY are tests that keep giving in a way that panel tests don't. It's probably the right decision for most projects but, in more than one way, it is also why YSeq exists as it does today: to fill the market gap for the remaining few researchers. If the difference between $200 and $400 makes the difference between getting tested and not getting tested, then spending that $200 at YSeq instead of FTDNA is no bad idea. But in terms of cost per genealogical datum, BigY represents the better investment, especially in the long run. Cheers, Iain. |
Re: Question re: changes to haplogroup assignment
What would help our project immeasurably is for FTDNA to bring back the ability for projects to request panels to be developed ala carte. A y-12 to confirm bloodline and a panel would be much more cost effective in our case, especially when administrators and project members tend to pick up the tab for new testers financially challenged, just to keep the project moving forward.? - Joe On Wed, Oct 25, 2023 at 09:53 gubbins.t21 via <gubbins.t21=[email protected]> wrote:
|
Re: Question re: changes to haplogroup assignment
开云体育Hi Joe, I wanted to pick up on a point you raised: >And the technology has seemed to have stalled. Where are the new products development? I’m seeing window dressing, bells and whistles, but nothing as far as actual new products to help us be more precise with our projects. What new products were you hoping for? Was there something specific? I'm currently trying to update the "Futures" chapter of our textbook, so this is something I am looking at in detail and would welcome feedback. In terms of autosomal DNA, the next major step is WGS. This is a possible route for genetic genealogy and Family Tree DNA to go down. However, no-one has really cracked the mathematical and computational problems of how to get genetic genealogy to work on WGS tests at scale. This is not really a case of "more SNPs are better", because that won't dramatically improve your knowledge of how many cM you share with another person. Instead, it's a case of significant research into fundamental principles that's likely considerably beyond FTDNA's capacity. In my estimation, WGS is going to need a thorough thrashing by major health initiatives (e.g. the 100,000 Genomes project) for many years before the techniques are ready to be applied to genetic genealogy. So Family Tree DNA can start offering WGS products, but there isn't yet the theoretical support for using WGS for genetic genealogy. In terms of Y-DNA, the only place left to go is longer reads. Here, it's a question of how much you are prepared to pay for the technology. We're already reading about 25% of the Y chromosome in BigY. Incremental updates to 40% of the Y chromosome can be made, but at the cost of about $100 per percent - this could be done, but too few people would pay for it to make it cost effective. The cost of going from 40% to 100% of the Y chromosome is currently measured in millions (i.e. the research costs of the T2T consortium). So it seems to me that we are stuck with BigY-700 as the best at-scale commercial test that can be obtained, at least for a few years until this ultra-long-read technology becomes commercially viable. Until then, the main progress that can be made is largely going to be in the "window dressing". While far from perfect, the Discover project, with its variety of tools, has represented a major step forward for FTDNA in terms of supporting its customers and helping them get to the bottom of their data. Consequently, as far as FTDNA's product development goes, I don't see what advanced products they can really develop at the present time. Perhaps there are more intermediate products that could be developed, but I can't identify anything that would be cost effective. Of course, I'd be happy to be proved wrong! :) Best regards, Iain. |
Re: Question re: changes to haplogroup assignment
开云体育Hi Ian, While I'm not an expert on the testing technology, I can attest to the substantial drawbacks of chip assays for Y-chromosomal SNPs in terms of reliability, scale and comparative value. The haplotree currently encompasses around 663,000 variants. The coverage of typical chip-based autosomal tests (Family Finder, Ancestry, etc.) is about 300,000 variants. While it's possible to get many of the SNPs on such a chip, having a chip for the entire haplotree is not practical. The second issue is reliability. Individual SNPs on chip-based tests don't have the same per-locus reliability as STR or sequencing tests, as anyone who has dealt with the Nat Geo tests will attest. Consequently, like ancient DNA results, you need multiple positive indicators for a haplogroup. This means that the results from a chip-based test at that scale would be just as "arcane" as the data from BigY tests, due to the necessity to track and quality control each SNP independently. Back in 2014-2016, when BigY was in its infancy and the formal haplotree didn't exist, Family Tree DNA toyed with chip assays of 160 SNPs, which had sufficient reliability. These were developed by FTDNA in co-operation with our and other haplogroup projects. However, they proved not to be cost effective in the long run as the price of a BigY test dropped and have been pushed into the testing background. There is also a legacy advantage of the Y-STR tests in being able to compare to a wider pool of testers, who have not taken Y-SNP tests. Relatedness (e.g. TMRCA) can be estimated much more accurately with two Y-37 tests than it can be with chip-based Y-SNP testing that gets you even to a 2000-year-old haplogroup, never mind something as coarse as R-Z18. Despite this, there are advantages to finding new testers via these coarse haplogroups, and identifying the Y-DNA haplogroups of potential matches at Ancestry and other DNA sites is important. We already know that FTDNA are intending to release Y-DNA haplogroups of Family Finder testers, so essentially there is a step towards a product like you envisage. However, that's likely as far as these kinds of tests are going to go while remaining cost-effective. Most indicators point to cheaper and/or wider sequencing tests being the medium-term future of genetic genealogy. Cheers, Iain. |
Re: Question re: changes to haplogroup assignment
开云体育The FTDNA group administrators conference is coming up at the beginning of November. For the first time it will be possible to register for virtual attendance. ? I’m hoping there will be lots of updates about new features and updates. ? FTDNA have traditionally saved announcements up for the conference. ? One important update is the long-promised provision of haplogroups for Family Finder customers: ? ? Debbie ? |