开云体育

Hi Michael, You asked about R-Y49873, which is part of R-Z159>S3251. I am busy looking at the upper echelons of R-U106 and its early migrations, though it is likely to be a while before I have a renewed idea of R-Z159 and its descendants as these are much later haplgroups. You can see previous analyses in message #5759. For R-Y49873 in particular, the few test results we have indicate that the haplogroup has probably been in modern Germany for the last 1000+ years. It's difficult to say much more than this without too much guesswork at this stage. Best wishes, Iain.

For informational disclosure to those who have added there data, I have implemented a more advanced Study (Project) system than the one discussed here in the past. All men who are test with SNPS at or below have been added to a Private R-U106 study of which only Investigators (Admins) have been added to demo the functionality. If any of the other current R1b-U106 or Subclade admins who have accounts in the warehouse want to preview this, let me know and I will add you to the Investigator list. Anyone with an account can access this from the Studies tab from their Manage Subject screen. There are Prefs settings that you can turn on or off the details on the Member list. Currently only members of the Study can see anything, but if it's made public it will behave more like my R1b-CTS4466 public study. If anyone has questions or feedback, this is a still in active development MVP feature. Thanks, James Kane

https://omniletters.com/researchers-uncover-potential-new-ancient-human-species/ Dan D

Will an administrator of this group make available to a tester the Y DNA genetic distance report for the tester? This report that is accessible to the administrators of this group. It shows matches for much higher genetic distance, 25 for Y DNA 67 and 40 for Y DNA 111 -- Kevin Terry

I saw on another group that the DNA spreadsheets have changed, and strangely those with kit numbers beginning with "B" have dropped off. As one who has been affected by this, does anyone have an idea of when it will be fixed? My SNPs still appear in each group of which I am a member, but my STRs no longer appear in the spreadsheets. Thanks, Ed

Hello all, I have recently added myself to the YDNA-Warehouse and I noticed that some of the TMRCA dates seem more recent than the estimates listed on FTDNA. For example: R-Z159 shows 344 BCE - 816 CE; FTDNA estimates 1900 BCE. I’m just trying to understand the reason for this discrepancy. Best regards, Herman

Hello all, I had a kit number registered in the project under >FGC50431>S6881>FT5123>FGC42045>“446=14”>A11376) > for some amount of years but it disappeared off the results page a couple months back. I do suspect the reasoning, but just wanted to see if I could sort it out. I have a kit on FTDNA though only tested at the Y-DNA67 level, but had originally a confirmation of S6881 under Britainsdna (long gone) and now Livingdna. I'm afraid to say I forget who I had communicated with to join the project back on Yahoo but with this information they had used my Y-DNA67 info and the proof of S6881 to give me a rough plot further down the chain. With this info would anyone be able to suggest a kit to purchase to get me back on the project and confirm where I am in the tree? I'm unsure what I am beyond S6881 and the additional placement further down was likely to do with STR marker results, though I honestly know very little about the topic. If anyone could help that would be grand. Kind regards Alister

Recently I have encountered a knowledge person claiming that R-L47 was not present in the Nordic Bronze Age cultures and only became part of the wider Germanic cultures in the Iron Age, possibly with the formation of the Jastorf culture. What are everyone’s thoughts on this? I have looked pretty extensively through all the samples I could find and the earliest confirmed R-L47 sample seems to be a Roman era Saxon.

Hi all, You'll have received an e-mail just now noting that Ewenn Gicquel has been added to the R1b-U106 project as a co-admin. Ewenn joins us primarily to help with automating a lot of the research work I'm trying to do (but don't have the time or skills to accomplish myself). I'm hoping that together we will be able to work on improved TMRCAs and more reliable origins than Globetrekker currently provides us with. This is one of several administrative changes that we are making. We are also retiring Zak Jones and Phil Chaddock from our admin pool - Zak and Phil have helped us with some of the manual data shovelling that our analysis work has required in the past. With the increased size of the project and volume of BigY testers, dealing with data manually is now not so much of an option, hence swapping Zak and Phil for Ewenn. Finally, Charles has also finally cajoled me into becoming a joint lead admin of the project with him, so I am now officially stepping up from co-admin to admin of the project. In practice, very little changes as a result: Charles will continue in the admin role he's had for 12 years, but I'll be giving him a bit of support with that. He's still grouping people, along with Connie and Kathy, and we still have gatekeeper Dan, Debbie, Vince and Ray helping out in various guises, and Robert who looks after R-FGC11674 are related groups in particular. We're hoping these changes will help this group approach the challenges in Y-DNA testing that will face us over the next few years. Here's to the future! Cheers, Iain.

Red Deer Cave People: Mysterious Humans With "Archaic" Features Lived Just 14,000 Years Ago Who were they? https://apple.news/A3Lmv3AxkSyahHnbMJKr1Mw Dan D.

Dear all, I've been in touch with Peter Op den Velde Boots, who runs the Family Tree DNA R-Z18 project. This project has been dormant for a couple of years, but he is now investing time in it. His aim is to work through the backlog of membership and grouping during October, with a normal service running from November. Our two projects have similar aims, but differ in some approaches and opinions. While R-Z18 is part of our R-U106 family, we therefore encourage R-Z18 members to join the R-Z18 project as well as our own, in order to benefit from both sets of approaches, which each have their advantages. Best wishes, Iain.

Does FGC 17467 have a Norse Viking heritage in England ?

Yesterday, FTDNA released quite a few Y haplotypes for AncestryDNA and 23andMe and perhaps MyHeritage. These are generally visible as "N/A" on Family Finder match lists, but they are fully named in the CSV download file. This is not in accordance with the FTDNA GAP email earlier this week, which stated "Please remember that these haplogroups will not be shown to either matches or administrators via GAP" So if you know of any 23andMe or Ancestry uploads at FF that might have an interesting Y haplogroup, then you should look now or download the CSV file. I downloaded yesterday and today, and there are more updated Y haplogroups today. Although listed as "N/A", the Y haplogroups do sort correctly and also are available via the Search box. ~~~ Today, however, I noticed a new R-L48 for an Autosomal Transfer. Yesterday, I know he was M269 based upon a Y37. Today he displays on the match list as "R-L48". Additionally, he is now shown as L48 in green on the project page, rather than the ubiquitous red R-M269. His personal page has two YDNA badges. One for his Y37 R-M269 and one for his L48 upload. So its useful to know that some Ancestry or 23andMe haplotypes are going to work their way into the Project pages. For better or worse..... (I am okay with this, although maybe in a Yellow or Orange color?)

https://phys.org/news/2024-09-archaeologists-neanderthal-homo-sapiens-interbreeding.html Dan D

Hello, In volume 15 of its bi-annual journal, the Foundation for Medieval Genealogy published a paper of Dominic Gagnon, a genealogist from Quebec. Dominic Gagnon et al. "The Common Norman Ancestor to the Verdun, Haviland and Battaglia Families" https://fmg.ac/publications/journal/vol-15/718-fnd-15-2 Abstract: "This study began in 2018 when a French descendant of the Verdun family sought to prove genetically his direct link to Bertram de Verdun, born around 1040 and a contemporary of William the Conqueror. In addition to achieving this, the analysis of the phylogenetic tree and the study of historical documents preserved in England and Normandy revealed a common and unsuspected kinship with the Haviland family of Guernsey, two American Battaglia families whose ancestry originated from Sicily, and the Fauchon from Quebec, who trace their ancestry from Avranchin in Normandy. The same markers on the Y chromosome shared by the descendants of these families allow us to confirm a thousand-year-old common origin and trace their multiple migratory routes." The common ancestor of these three families of Norman origin is identified by the haplogroup R-U106>FGC3861>>FGC17460>BY11544. https://discover.familytreedna.com/y-dna/R-BY11544/tree I take this opportunity to thank Iain McDonald who agreed to participate, in particular by providing us with the calculation of the MRCAs. Bertram

Hi Rich, >Where do you find the ranges for haplogroup formation? https://discover.familytreedna.com/y-dna/R-BY71870/scientific This gives the 68%, 95% and 99% confidence intervals for the haplogroup R-BY71870 (and you can change the link to any other haplogroup you like). As you can see, even for a well-constrained haplogroup like this, the confidence intervals stretch over centuries. It's impossible to be much more accurate than this when mutations are random and you only have one or two per century. The only way to improve on this is to use genealogical information, as you have done already. FTDNA only uses genetic data to pin down a TMRCA. It's possible to use both genetic and genealogical evidence to pin down a TMRCA for a haplogroup where the MRCA himself is not known - I've written a Python code to do this if it is useful. See GitHub link in: https://www.mdpi.com/2073-4425/12/6/862 Cheers, Iain.

Hi folks, Actually, getting reliable mutation rates for the extended set of Y-STRs would be very valuable and could help us improve the TMRCA estimates by using a marker-by-marker mutation rate instead of the global one currently used. Here's how to do it: (1) One of the admins needs to go into hundreds of accounts in the project and download their Y-STR CSV files. (2) The CSV files then need to be labelled with their haplogroup. (3) Pairs of CSV files can then be sampled (sequentially or at random), and the TMRCA of their two haplogroups looked up from Discover (preferably in an automated fashion). (4) On a per-marker basis, plotting the genetic distance versus TMRCA and fitting it with an exponential function will give us the mutation rate of each Y-STR. Unfortunately, it needs to be done this way because FTDNA haven't given admins a tool to query all 852 Y-STRs on a project-level basis, as they have for the first 111. I haven't had time to do this myself, because I haven't had time to do (1) and haven't had a chance to work out how to automate (3), but if anyone wants to take this one, it would be very helpful. Cheers, Iain.