ftdnastat Русский

How ftdnastat works

A technical description: where the site gets its data, how it updates and checks it, and how the numbers on its pages are computed. Thresholds and rules are given as they work now.

1. Sources #

Source What is taken How often
FamilyTreeDNA public Y-DNA and mtDNA Haplotrees tree nodes, kits per node by country, Big Y counts, surnames checked daily, downloaded on a new release
FamilyTreeDNA Discover the age of the common ancestor (TMRCA) of every Y branch with its range; ancient samples with branch, culture and date; branch migration paths checked daily; ancient samples and migration paths in full every 30 days
Mitotree in FamilyTreeDNA Discover mtDNA branch ages, ancient mtDNA samples with coordinates on a new tree version
Public member maps of FamilyTreeDNA geographic projects ancestor's place, branch, the SNP-confirmed mark every 30 days
Public YFull Y and mt trees nodes, samples with country, region and native language, TMRCA and formed ages, the "new" mark monthly
TheYtree a third age estimate for Y branches, matched by SNP rarely, by hand
Population of countries and regions (UN, the 2021 Russian census, Wikidata) number of men, for the testing rate and the density correction by hand

All sources are public. Names of people from the project maps never reach the site.

2. Updates and publishing #

Once a day the version of every source is checked: the tree's release date, a server response header or the root totals. Only what changed is downloaded. The site is rebuilt when the data or the code changed, and in any case once a week.

Before publishing, a build has to pass acceptance:

A build that fails acceptance is not published. Published builds are kept in an archive.

A new FTDNA Y tree also has to pass the haplogroup predictor check before it is used: on the same data, the prediction error rate for the key branches must not grow.

3. Countries, regions and peoples #

FTDNA. A kit's country is the self-reported origin of the earliest known ancestor on the line. Regions FTDNA lists separately ("Russia (Republic of Dagestan)") are pages of their own and are not part of their parent country. Kits without a country are left out of shares.

YFull. A sample's country and region are ISO codes, its people is the native language from the customer form (ISO 639-3). The codes are matched to FTDNA countries and regions; a region that has its own FTDNA entry takes the sample away from the country, as FTDNA does. A language that matches the sample's country or region is not counted a second time.

The comparable YFull slice. Comparisons with FTDNA use YFull customers only (YF… numbers) and modern samples only: published studies and ancient DNA are sampled differently from customers.

4. Branch tree and shares #

Shares are cumulative: a branch row includes all kits of its sub-branches. So nested branches never stand side by side as neighbours, and a kit whose test did not go below a node stays on that node with an asterisk (J-M172*).

5. Branch pages #

Every branch whose subtree holds at least 50 kits with a country has a page: currently 4,297 Y and 1,182 mt branches. Chains of equivalent nodes, where the only sub-branch holds ≥ 99% of the kits (Y) or ≥ 97% (mt), become one page listing the equivalent names.

6. YFull: comparison, neighbours, pairs, kin across borders #

7. FamilyTreeDNA geographic projects #

Project members themselves turned on showing their ancestor's place on the public project map. One person may be in several projects: their records are merged into one.

8. Ancient DNA and cultures #

Y samples come from FamilyTreeDNA Discover, mt samples from Mitotree and YFull. A sample's date is the middle of its dating range. The culture is the Discover entry; different spellings of one culture are merged.

Comparing cultures. Each sample is cut to its ancestor at the chosen tree depth, or to the ancestor whose branch already existed by the chosen year (by Discover ages). A sample whose test did not reach that depth stays on its own branch.

Culture chains are shown while neighbouring cultures stay at least 10% alike; the numbers in chain texts are checked against the data on every build.

9. Findings #

Recomputed on every build, for countries with at least 50 kits:

10. Changes #

11. Limitations #