File:Alpine DNA Project - AlpGen - Y-DNA Classic Chart.jpeg you continue to show no source for your claim 62.14.247.236 https://www.familytreedna.com/public/Alpine_DNA_Project_AlpGen_Genealogy?iframe=yresults— Preceding unsigned comment added by GedalYah (talk • contribs) 16:58, 21 December 2016 (UTC) [1] [2] [3] [4]
Hello my name is GedalYah Ban Netzerim. Please show all the research stating that for sure origins are in European? I have all the major DNA companies saying West Asia and Near East. 23andMe FTDNA Genographic Project in Northern Europe its less then 1% FYI also whats your kit #'s and who is your company or group Administrator. I will change this everyday if I need to until you show me indefinite proof of these north europe claims.
link # 2 Many studies of human populations have used the male-specific region of the Y chromosome (MSY) as a marker, but MSY sequence variants have traditionally been subject to ascertainment bias. Also, dating of haplogroups has relied on Y-specific short tandem repeats (STRs), involving problems of mutation rate choice, and possible long-term mutation saturation. Next-generation sequencing can ascertain single nucleotide polymorphisms (SNPs) in an unbiased way, leading to phylogenies in which branch-lengths are proportional to time, and allowing the times-to-most-recent-common-ancestor (TMRCAs) of nodes to be estimated directly. Here we describe the sequencing of 3.7 Mb of MSY in each of 448 human males at a mean coverage of 51 ×, yielding 13,261 high-confidence SNPs, 65.9% of which are previously unreported. The resulting phylogeny covers the majority of the known clades, provides date estimates of nodes, and constitutes a robust evolutionary framework for analysing the history of other classes of mutation. Different clades within the tree show subtle but significant differences in branch lengths to the root. We also apply a set of 23 Y-STRs to the same samples, allowing SNP- and STR-based diversity and TMRCA estimates to be systematically compared. Ongoing purifying selection is suggested by our analysis of the phylogenetic distribution of non-synonymous variants in 15 MSY single-copy genes.
link # 3 Background
- IMPORTANT MESSAGE APRIL 2014. FOLLOWING THE RELEASE OF THE NEW FTDNA/GENOGRAPHIC HAPLOGROUP TREE THERE ARE A LARGE NUMBER OF NEW SNPS AVAILABLE FOR ORDERING INDIVIDUALLY. FOR GUIDANCE ON WHICH SNP(S) TO ORDER PLEASE FIND YOUR KIT NUMBER ON THE Y-DNA RESULTS PAGE AND LOOK AT THE DESCRIPTION FOR YOUR GROUP. IF YOU ARE UNSURE OF WHICH SNP TO ORDER PLEASE CONTACT THE GROUP ADMINISTRATORS. **
This project welcomes anyone who has been predicted or SNP-tested as Y-Haplogroup T.
Haplogroup T (known as Haplogroup K2 until May 2008) is defined by SNP M184 and is found at low frequencies in the Middle East, Europe and North Africa. Most lines in T belong to subgroup T1a defined by SNP M70 which until March 2011 was considered equivalent to M184.
T1a in turn splits into T1a1 (T-L162), T1a2 (T-L131) and T1a3 (T-L1255).
T1a1 clusters along an east-west axis from Iran to Spain. T1a2 is found both in Northern Europe and Southern Africa but is rarer in the eastern and western edges of T's distribution zone. To date, T1a3 has only been found in Kuwait.
Recent developments including the Geno 2.0 chip have identified the following major subgroups of T1a:
T-L208 (T1a1a* on the current ISOGG tree http://www.isogg.org/tree/ISOGG_HapgrpT.html) T-Z709 (T1a1a1*) T-P77 (T1a1a1a) T-P322 (T1a2a) T-L446 (T1a2b) Most lineages in T will belong to one of these 5 branches. The first two are strictly speaking paragroups and may split into several branches when more data is available.
Thomas Jefferson is believed to have belonged to haplogroup T, based on tests carried out on individuals sharing his paternal line. For more information on T and the Jefferson family link see: http://www3.interscience.wiley.com/cgi-bin/abstract/114108057/ABSTRACT and http://news.bbc.co.uk/1/hi/sci/tech/6332545.stm
LINK # 7 Because of the limited availability of haplotypes within haplogroup T for several of the reference populations, time estimates were calculated using the Levant and Turkey as single groups. Furthermore, because of the elevated levels of haplogroup T in Sasun relative to the other three collections two dates were calculated from Armenian populations, one for Ararat Valley, Gardman and Lake Van, collectively, and a second for Sasun. In addition, spatial gradient maps were generated to illustrate haplogroup frequency and STR allelic variance clines in both haplogroups R1b and J2 using the program Surfer v.9.0.343 (http://www.goldensoftware.com).In each of the examined Armenian populations, we witness moderate levels of haplogroups T-M184, G-M201 and E1b1b1-M35. Interestingly, haplogroup T-M184, which is relatively rare in other Near Eastern populations, as well as in three of the Armenian collections tested here, represents the most prominent descent in Sasun, comprising 20.1% of the samples. The presence of this haplogroup in Ararat Valley, Gardman and Lake Van, by contrast, is more limited, composing only 3.6%, 6.3% and 3.9%, respectively, of the individuals from those collections. Haplogroup G-M201 (10.9%, 6.3%, 7.8% and 12.5% in Ararat Valley, Gardman, Lake Van and Sasun, respectively), on the other hand, is fairly evenly distributed across the four Armenian populations, with sublineage G2a-P15 comprising the vast majority of these chromosomes. Similarly, the E1b1b1-M35 clade (5.5%, 4.2%, 7.8% and 2.9% in Ararat Valley, Gardman, Lake Van and Sasun, respectively) in the four Armenian populations consists almost entirely of haplogroup E1b1b1c1*-M34. However, a small number of individuals from Lake Van belong to the E1b1b1a*-M78 (0.9%), E1b1b1a2-V13 (1.9%) and E1b1b1a3-V22 (0.9%) branches that have been implicated as signals of Greek influence.40Pairwise Fst distances between the four Armenian populations based on haplogroup frequencies, as well as their corresponding P-values, are provided in Table 2. These results indicate that the genetic distances separating Ararat Valley, Gardman and Lake Van are not statistically significant (P≤0.001). Sasun, however, exhibits statistically significant divergence from the remaining Armenian populations, most likely as the result of the prominence in Sasun of lineages (T-M184 and R2a-M124) found at substantially lower frequencies in Ararat Valley, Gardman and Lake Van. An MDS plot based on Fst distances generated from Y-haplogroup frequencies is provided in Supplementary Figure 1. However, conclusions yielded from this plot must be tempered, as the low haplogroup resolution generates artificial associations that may not exist with an increased number of markers (ie, the observed affinities between Armenia and Europe because of their high levels of R, despite the lack, in Armenia, of the M412-derived allele that predominates in European populations).
Haplogroup T The haplotypes of the 35 individuals belonging to Haplogroup T are provided in Supplementary Table 4. The distribution of haplotypes within Haplogroup T-M184 illustrated in an MJ network (Supplementary Figure 4) depicts a positioning of clusters composed almost entirely of Levantine individuals in the center of the diagram, with all other groups emanating from this area. This potentially points toward an origin of these haplotypes in the Levant, a supposition that is further supported by the observation of high genetic diversity in the network among levantine individuals within haplogroup T-M184 in the Levant. Time estimates for T-M184 individuals (Supplementary Table 5) corroborate the supposition that the lineage originated in the Levant and entered the Armenian Plateau at a later time, as the dates generated from Levantine (6.2±1.8 kya using Ravid-Amir and Rosset34) and Iranian (5.9±1.3 kya) individuals are older than those yielded from Turkey (5.7±1.2 kya), Sasun (5.0±1.2 kya) and the remaining three Armenian populations (average 3.9±1.0 kya).This is supported by time estimates for Haplogroup T-M184, a clade believed to have originated in the Near East during the Paleolithic,46 as we observe dates in Armenia (∼12–13 kya) lower than those in other regions of the Near East, including Iran and the Levant (∼20 kya). Such a disparity suggests the Haplogroup T lineages presently observed in Armenia were introduced by migrations that are more recent than those that carried Haplogroup T to the Levant and Iran. Given the difficulties associated with absolute dating, it is also possible that these markers were carried by migrants entering Armenia during an even later era, such a
LINK # 9 We have analyzed mtDNA HVI sequences and Y chromosome haplogroups based on 11 binary markers in 371 individuals, from 11 populations in the Caucasus and the neighbouring countries of Turkey and Iran. Y chromosome haplogroup diversity in the Caucasus was almost as high as in Central Asia and the Near East, and significantly higher than in Europe. More than 27% of the variance in Y-haplogroups can be attributed to differences between populations, whereas mtDNA showed much lower heterogeneity between populations (less then 5%), suggesting a strong influence of patrilocal social structure. Several groups from the highland region of the Caucasus exhibited low diversity and high differentiation for either or both genetic systems, reflecting enhanced genetic drift in these small, isolated populations. Overall, the Caucasus groups showed greater similarity with West Asian than with European groups for both genetic systems, although this similarity was much more pronounced for the Y chromosome than for mtDNA, suggesting that male-mediated migrations from West Asia have influenced the genetic structure of Caucasus populations.
LINK #10 Ancient Migratory Events in the Middle East: New Clues from the Y-Chromosome Variation of Modern Iranians
all links 2,3,7,8,9,10 on Haplogroup T (Y-DNA) page
 | This is the discussion page for an IP user, identified by the user's IP address. Many IP addresses change periodically, and are often shared by several users. If you are an IP user, you may create an account or log in to avoid future confusion with other IP users. Registering also hides your IP address. |