Friday, 17 February 2017

Transfers into FamilyTreeDNA

This is indeed something we've been waiting for.
Points to note:
  • You cannot transfer an Ancestry or 23andme test to an account that already had a FamilyFinder test, and anyway, 
  • if you already have a FamilyFinder test at FamilyTreeDNA there is no real benefit in transferring an Ancestry test as well - it just duplicates results and clutters up match lists needlessly
  • FamilyTreeDNA requires an individual account per kit, but if you do already have an FTDNA kit number for eg a yDNA (direct male line) or mtDNA (direct female line but NOT atDNA (autosomal DNA aka FamilyFinder which is what is being referred to here), then yes your Ancestry or 23andme kit can be transferred into the same kit number.
  • Expect delays initially as data cannot be processed immediately. The Ancestry kit I wanted most to be able to see segment data for has been transferred with attempts to see the match list advising it was processing and to trry again for the match list in 24 hours. It took less.
  • Unlocking the more recent Ancestry and 23andme tests will show your matches up to predicted 5th cousins (shows as third to fifth cousin). To see the smaller matches testing at FTDNA is recommended, and a reduced price of $59 offered for that - which has the added benefit of being able to add eg yDNA testing to the same kit for males to explore their direct male line ancestry.
  • All on FTDNA should see an increase in their match lists as previous unlocked transfers, and new transfers, unlocked or not, are showing in the match lists already
This is a rightly popular option we've been waiting for.
Please encourage your Ancestry test takers in particular to use this transfer and take advantage of the ability to actually check where and who else they match.
None of this negates the benefit of GEDMatch - your match list on FamilyTreeDNA can only show you people who have tested on, or transferred to, FamilyTreeDNA.
Pay the $19 and actually see the segments of DNA involved!
Also refer to this post by Roberta Estes (DNAExplained blog)

The announcement below was received by project admins today.
Dear Project Administrators,
You’ve all been waiting for it, and it’s finally here - transfers for 23andMe© V4 and AncestryDNA™ V2 files!
Here are the details, point by point.
  • Customers can now transfer 23andMe© V4 and AncestryDNA™ V2 files in addition to the 23andMe© V3 and AncestryDNA™ V1 files that Family Tree DNA accepted previously. MyHeritage and Genographic transfers will be supported in the coming weeks.
  • Family Tree DNA still does not accept 23andMe© processed prior to November 2010. A Family Finder test will need to be purchased.
  • 23andMe© V3 and AncestryDNA™ V1 now receive a full list of matches and the ability to use the Matrix feature FOR FREE. For only $19, the customer can unlock the Chromosome Browser, myOrigins, and ancientOrigins.
  • 23andMe© V4 and AncestryDNA™ V2 receive all but the most speculative matches (6th to remote cousins), also for free. After transferring, if the customer wants to receive speculative matches, they will have to submit a sample and have a Family Finder run at the reduced price of $59.  
  • Matches should take somewhere between one and 24 hours to appear, depending on the volume of tests in the autosomal pipeline.
  • myOrigins update will be released in the coming weeks. Until then transfers will include only broad populations.
  • Additionally, all previously transferred files that have not been unlocked will receive their matches and have access to the Matrix feature for free as long as the release form is signed. These kits will be also be able to unlock the other Family Finder features for $19. If the transfer was on a kit with another product where the release form has already been signed, then the matches will appear with no further action necessary.
  • The Autosomal Transfer webpage has been enhanced to include a new image and a FAQ section. The FAQ section is displayed towards the bottom of the page.
  • If a customer tries to transfer the same autosomal file a second time, a message will be displayed that the file is a duplicate and will list the kit number of the original kit.
  • The main Autosomal Transfer topic in the Learning Center has been updated. This topic contains the most recent information and now includes all transfer subtopics on the same page. Additional FAQ information will be added to this topic as needed in the future.

As always, we appreciate your work with your projects! Thank you!

Wednesday, 15 February 2017

BigY "matches"

As a complete layperson when it comes to interpreting BigY matches, I rely on the people on the DNA forums,, and the wonderful work of Alex Williamson and his BigTree (for R-P312 and sub branches). Wish there was an equivalent to Alex for I1-Z60!

This post is me thinking out loud as I explore why the yDNA67 group of matching RUNCIMANs are showing up in the BigY Match lists for the yDNA67 group of matching FAIRBAIRNs.

Back when both projects began individual SNP testing we learnt that both were I-Z60, so on the same branch back within recorded history.
They subsequently diverged.

From FTDNA's Learning Centre on

Big Y – Matching

The Big Y – Results,  Matching tab displays your Big Y matches. A person is considered a match if they have four or less differences in SNPs with you.
Known SNP Difference   
This column displays the number of known SNPs within your subclade that you do not share with the specified match. The following values are possible:
  • 0 – Indicates that you share all known SNPs with the specified match.
  • 1 – Indicates that there is one known SNP in the subclade that you do not share with the specified match.
  • 2 – Indicates that there are two known SNPs in the subclade that you do not share with the specified match.
  • 3 – Indicates that there are three known SNPs in the subclade that you do not share with the specified match.
  • 4 – Indicates that there are four known SNPs in the subclade that you do not share with the specified match.


A subclade is a subgrouping in the haplogroups of the human genetic trees. This may be either the Y-chromosome tree or the mitochondrial tree. Subclades are more specific to a location or population group than the major branches (haplogroups).
Which I suppose explains how come the newly tested FAIRBAIRNs are showing up in the already tested RUNCIMANs matches and vice versa if you take "your subclade" back far enough, although I'm not altogether sure I consider 4000+ years before present a "match". Perhaps I'm too used to working with atDNA these days!
Both surname groups were I-Z60 back when we were doing individual SNP testing to advance down the tree, formed 4300 ybp according to YFull. 
But then the RUNCIMAN matches headed off down I-Z160 to their own newly created SNP I-Y22033 (YFull, formed 500 ybp).
We knew back at the individual SNP testing stage a while ago that the FAIRBAIRNs are I-Z140 (which YFull estimate as forming 4100 ybp)
A brief overview of some of this structure is available on DNASurnames under the I haplogroup chart which shows selected branches, the patriarch for the line, and the tested participants who agree to be so shown.  Branches can be expanded or collapsed for a better overview by clicking on the + - symbols.
Looking at the latest set of FAIRBAIRN BigY results, 5 of the 6 RUNCIMAN tests show in their match list as having 4 SNP differences PR1457 Z140 Z141 PF3832, with one not showing Z140 in their list!
Shared novel variants range from 30 to 41 for the RUNCIMAN matches, compared with 57 and 61 for the two other tested FAIRBAIRN matches with zero known SNP differences.
An interesting exercise in timeframes.
yDNA matches don't tend to appear in Autosomal match lists
BigY matches don't seem to appear in yDNA STR matches (although for this one I have noted some exceptions). 
Not at all sure what I've really learnt from here but it is fascinating watching the developments on the respective yDNA haplogroup trees at FTDNA, YFull and Alex's BigTree.