Other pages & sections of our site:
[Home]  [Y-DNA]   [Contacts   [Groups]  [Haplogroups]  [Trees]  [Project Blog]  [Special]   [FAQ]

---

Members

Click on links to view trees. Each tree will open in a new window.
Close, minimize or resize the window to return to this page.

About Group 32

Group members may contribute information about their ancestral heritage.

This, to date, is our only matched group in haplogroup R1a. From Wikipedia:

Haplogroup R1a is a major Y-chromosome haplogroup currently found at high frequencies in most of Eastern Europe and parts of Central Europe and certain populations in Central and South Asia.

Distribution of R1a in Europe & Asia

Y-DNA Values

See http://www.familytreedna.com/public/taylorfamilygenes/default.aspx?section=yresults.

Back to  Members

TiP Scores

TiP Scores Explained

TiP (for "Time Predictor") is a utility provided by Family Tree DNA. It is accessible to all FTDNA customers with Y-DNA results who have matches listed within the FTDNA reporting windows. It is also available to project administrators for calculating the probabilities that any two project members share a direct paternal ancestor within up to 24 generations.

TiP is superior to most TMRCA calculators. Rather than assume an average mutation rate for all markers compared, TiP uses individual marker mutation frequencies. Because marker mutation rates vary significantly between markers, the TiP scores 

As we use it here, TiP is a truer and simpler measure of genetic distances between individuals than other metrics such as the number of markers in disagreement or a sum of the differences (sometimes called "genetic distance"). TiP boils the complexities down to one number.

The composite TiP score is an index of how closely a member matches the entire group. Generally, the member with the highest score is the central member.

Note:

Unless stated otherwise, TiP probabilities are from TiP version 1 (v1) in effect from August 1, 2012 to December 11, 2012. Another version was in effect from December 12, 2012 to January 17, 2013 and was replaced with version 3 (v3) on January 18, 2013. We are in the process of updating to v3. In the meantime, we've made some observations about how v1 and v3 compare:

• For close matches, v3 = v1;
• For more distant matches v3 <= v1.

Go to Top

Revised: 10/04/2010