开云体育

Family Tree DNA U106 Group: https://www.familytreedna.com/groups/u106/about https://www.facebook.com/FamilyTreeDNA YSEQ U106 Group: https://www.yseq.net/group_alleles.php?gid=12 ( https://www.yseq.net/group_alleles.php?gid=11 ) https://www.facebook.com/groups/YSEQDNA/ Full Genomes Corporation: https://www.fullgenomes.com/analysis-and-more/ https://www.facebook.com/FullGenomes YFull: https://www.yfull.com/ https://www.facebook.com/groups/yfull/ mitoYDNA: https://www.mitoydna.org/ ISOGG wiki: https://isogg.org/wiki/Wiki_Welcome_Page Wikipedia article on Haplogroup R1b: https://en.m.wikipedia.org/wiki/Haplogroup_R1b ( /g/R1b-U106/en.m.wikipedia.org/wiki/Haplogroup_R1b ) Eupedia article on Haplogroup R1b: https://www.eupedia.com/europe/Haplogroup_R1b_Y-DNA.shtml ( https://https//www.eupedia.com/europe/Haplogroup_R1b_Y-DNA.shtml ) Royal U106 Dynasties: https://www.the-kings-son.com/royal_wettin_haplogroup FTDNA Y-Haplotree: https://www.familytreedna.com/public/y-dna-haplotree/R YFull R-M269 Tree: https://www.yfull.com/tree/R-M269/ ISOGG Haplogroup R Tree (2019): https://docs.google.com/spreadsheets/d/1JvXoBCBBk42DIF7BYPaLsQ1jojN3etgDR8pByaTRnq4/edit#gid=1078904281 Alex Williamson's Big Tree for U106: https://www.ytree.net/DisplayTree.php?blockID=1147 Debbie Kennett's blog: https://cruwys.blogspot.com/ Roberta Estes' blog: https://dna-explained.com/ Haplogroup R Repository: https://haplogroup-r.org/ Instructions to upload Big Y, FGC & other WGS tests: https://ydna-warehouse.org/instructions.html Iain McDonald's "Recent human genetic anthropology": http://www.jb.man.ac.uk/~mcdonald/genetics.html U106 Spreadsheet: https://docs.google.com/spreadsheets/d/1rpJP0Bt4qUQb9wWBFA7i1tLPV75ie_qS0iplwvvlVmQ/edit?usp=sharing Map of Ancient/Medieval/Royal U106 finds: http://www.communitywalk.com/map/index/2236108 Ancient/Medieval U106 remains (by Charles Weaver): https://docs.google.com/document/d/1h6ZFaJe9gUtwl2r2Iu33B5_kCc6er5n9oEthCe25wV0/edit?usp=sharing

One common method of ancient DNA testing utilizes a set of about 1.24 million SNPs across all of the Chromosomes. This method is usually called 1240K. The David Reich Lab at Harvard Medical School is one prominent lab which utilizes this method. The lab has posted a dataset documenting all 1.24 million SNPs included in this process. I have extracted all of the Y-SNPs from this dataset and have created a Google Docs spreadsheet at: https://docs.google.com/spreadsheets/d/1wCWqyy8-jWU5-ZtNjKXXU1k-rTh8TZNO4tl6W2mE-pQ/edit?usp=sharing This dataset uses the old Hg19/Build 37 position for the SNPs Many of the SNPs are either named with this Reference Sequence (rs) identifier, or simply by snp_24_[position]. A few of them were labelled with the SNP names we are used to (ie M269 U106 etc). I have attempted to identify the SNPs below U106 and have started to identify SNPs below M269. I am interested in finding volunteers willing to help me identify these SNPs. Please feel free to contact me directly at: wing.genealogist [AT] gmail [DOT] com

Will the messages in the Yahoo group be archived somewhere? I haven't had much time at all to go through the older messages since I joined earlier this year. I imagine there is a lot of very good information stored in those older emails.

BTW, we can edit our own messages on this new IO forum, a nice feature that was lacking on the yahoogroup. Charles

First, thanks to our Admins for getting us set up with a new system so quickly, esp. with all they have going on right now, I consider myself lucky to be part of U106! I was recently looking at one of my Matches Non-Matching Variants, specifically Z18009: 20046531 What I noticed was that even though it showed up in both Person(1) and Person(2)'s Non-Matching Variants list, a quick look at their VCF showed: Person(1) G>A Q:1484/Pass Person(2) G>. Q:560/Pass (i.e. G > dot) Interesting, this location doesn't show up for any of my other five Non-Matching Variants, it does show up in all our Y700 VCF files. The quality numbers are all very good but they are all showing as G>. I was going to Wish it at YSEQ but I noticed that although it isn't in their listed DYZ19 ( chrY:20054914..20351054 DYZ19 125 bp repeat region) area, where they wish you didn't Wish, it is close Can someone explain what the 'dot' implies? Is this another case where FTDNA is reporting it but probably shouldn't? I ask the latter because if it is valid, it would be an interesting location for ID'ing a family line break, thus a shame if I can't use it - but I also don't want to be led down a path if I shouldn't be suing it either Dell P.S. To add to the confusion Yfull calls it as G>T vice FTDNA's G>A

Does anyone know how to get this "Daily Summary" to arrive in GMAIL's "FORUM" folder? It is currently being delivered to my "UPDATE" folder. I am certainly not the only Gmail subscriber, am I? Thanks, Wanda

Someone has compiled a series of charts showing how common the various clades of R1b (including U106) are in many countries of Western Europe. Please note the percentages are the percent of R1b, not the overall percentage. https://anthrogenica.com/showthread.php?11364-FTDNA-R1b-Project-Maps&p=615793&viewfull=1#post615793

I suppose a lot of you have received a message like this: "Starting today, Big Y participants will see some changes to how they are able to download raw data for the Big Y product. Below are further details. For customers who purchase a Big Y-700 starting 11/01/19, the product will not include downloadable raw data. However, customers will have the option to purchase the “Big Y Raw Data” product after the Big Y test has begun processing in our lab." Basically, for new customers, raw data is now a service that costs extra. Price is not mentioned. What does this mean for 3rd party analysts like the Warehouse? Harald

Is there a way to tell in the vcf if a position is a NC (vs Not Found in a search)? One of my Matches (Ernie/Y700) is positive for 4066643 / Y82646 (G>T) -- In searching my other Matches vcf files, I get a 'not found' -- Ybrower gave me the SNP name, so I went to YFull to see what they said. With a little bit of luck :-) back in the day, I had uploaded Ernie and two other's Big-Y to YFull, so I see Ernie is shown as + for that location, but the other two are listed as no call. That got me thinking that some of the 'not found' searches I've done in Y700 vcf files are not non-mutations but are actually no-call's that I might want to test at YSEQ Any thoughts?

I've just ordered the Big Y 700 upgrade, just $189, which is about 143 sterling. So any other S5246 out there, Sinclair or otherwise, hope you take the opportunity. Caithness Sinclairs of the above ilk will have an FGC35613 Sutherland Sinclair and myself to compare to at Big Y 700. And the BAM file situation is unaltered for upgrades from Big Y 500. Cheers Peter

So, I have a question that is specifically about a subgroup of U152, but the topic is relevant to U106 as well - I manage my maternal uncle's kit and I found a distant cousin with a similar surname (unknown genealogical connection) and only off by 2 strs at 67 markers. I was lucky enough to find this match because he was responsive to my email and willing to pay for the BigY. We both had our kits upgraded within a week of each other. Other than the fact that they both took FOREVER compared to my BigY, because I had previously done additional SNP testing, my uncle's haplogroup did not change, and his was updated to my uncle's (CTS9733). Now I know that part of the reason for this is that 1) FTDNA is backlogged with BigY work, and 2) there are about 12 other kits waiting at CTS9733 to be divided into subgroups. In the meantime both kits have been uploaded to the Big Tree and YFull - where they both remained at the CTS9733 level until recently. My question: YFull has recently identified one subgroup under CTS9733 where these two kits reside - what advice do people have for moving forward? Should I let FTDNA know that YFull identified a new group? Similarly, with my kit (under U106-Z18-DF95-BY38913-BY61595), FTDNA did identify BY61595 fairly quickly, but the Big Tree has yet to fully process kits below DF95 on my side. I know the Big Tree is volunteer based, but I don't know how long things typically take or if they are being worked on or even who/how to ask. What do you think? Thanks! Josh P.s. I did upload my kit to YFull for examination, but my Baker cousin (fellow BY61595 member) has been out of town and unable to upload his, but at YFull I'm still stuck at DF95 as well. Get Outlook for Android

On 10/26/19 I received BigY results with the newest SNP as FT 91469, downstream from M365, with three countries listed The Netherlands, Norway and Northern Ireland with four unknowns and no matches. Today, 11/2/19, I checked the results out of curiosity and found that now my newest SNP is BY144918 with only Sweden and one unknown country and no matches. I find this curious. Tom Nichols Manassas, VA

This is the correct topic name. FTDNA has new lower prices with a more modular product line. No one is getting a price increase or "extra" charge. An element of the product, the BAM file, has been made optional to support new lower prices. Most people don't buy Big Y700 unless it is on sale so we need to compare promotional pricing. Current Sale versus Summer (August) Sale Big Y700 new order $399 versus $499 (current sale is $100 less) Y37 to Big Y700 upgrade $319 versus $459 (current sale is $140 less) Y67 to Big Y700 upgrade $259 versus $399 (current sale is $140 less) Y111 to Big Y700 upgrade $229 versus $349 (current sale is $120 less) In each case, the cost to a person going to Big Y700 is cheaper today than during the August sale, even if you count adding the separate $99 BAM file charge back in. If you don't need the BAM file it really is a good deal. I had to look twice at the Y111 to Big Y700 for only $229. You are getting a whole new expanded coverage Next Generation Sequencing run on the advanced Illumina equipment. - BAM file support has not gone away. People new (Nov. 1st or later) can get the BAM files later if they choose. - All Big Y (of any kind) orders prior to Nov. 1st still have BAM file support. - All Big Y500 to Big Y700 upgrades, old or future, still have BAM file support since you already paid for it with your Big Y500 - All Big Y, including new Big Y700 order still will have VCF raw data file support built-in. The VCF files since the Hg38 conversion/Big Y500 are robust. *** VCFs are what the Big Tree uses. *** - Y111 is still built-in for all cases so the Y111 matching database continues to improve. We don't know FTDNA's true costs and anyone who has worked in any size business knows that availability/redundancy, support, administrative and general overhead costs are higher than we think. We can try to micro-manage vendors' costs but this is fruitless anyway. By the way, I'm surprised to see the Big Y500 to Big Y700 upgrade price as a sub $200 price again. It's $189 for a whole new NGS test run.... and you get the BAM file update built-in for that price since you already paid for BAM with your Big Y500.

All, FTDNA has been Johnny on the spot in less than a week they have established new Clade S5245 with myself and My GD4 Y111 match. I don’t know for sure if they are yet with their final determination yet. Will give it a couple more days and see. The hard part for me will be seeing what kind of timing separates us. Under Y8604. YFull has three different subclades As of now. The original Y8604 from Barbados in the 1,000 Genome Project, and two men at By13963 no location info but have and established TMRC OF 300 ybp then my brother and myself at FGC51229 from Rhode Island US with a TMRC of 150 ybp. This line is moving. Happy Days Harold #455872

Has anyone here actually seen any benefits to uploading a big Y file to Y Full? More info? How about a FGC file? I have both. I can almost see the benefits of the FGC file. Both? Robert McMillan

I have problems with the delivery of my digests. They bounce and/or end up in my Spam Box. My server notified me that the problem is that GROUPS is using an older mailing list setup which is in breach of DMARC, whatever that is. Anyone who has similar problems?

The same week that I am told that my newest SNP has only one country associated with it, Sweden, my physician tells me that I have Dupuytren's contracture in my right hand affecting the little finger. Dupuytren's contracture is also known as the Viking disease. What more proof of Scandinavian ancestry do I need? JTN

I would like to see the kit no. and testing co. follow the name of the member who is posting, as I have done below. This is not necessarily my kit no., but I am the admin for this person who appears in U106 and it can be found there. This is a practice followed in other groups and I have found it very helpful. ~wanda Taylor, FTDNA #103244

Hello, U106 is also identified by M405, s21, and rs16981293. Tradition seems to have this particular mutation with the U106 name listed first. Does anyone have a source where each of the Snps within U106 (i.e. for every subclade) has the preferred order? Here I mean preferred by genealogists which might not necessarily agree with YFull, FTDNA, etc. Thanks, John Terwiske