Gedmatch no longer accepting FTDNA kits

[Ann Turner]

Yes, with the 64bit version 15.14 (2015-12-31)

That's what I have, so I'm puzzled. I tried two different kits, and the old files extract fine. But in any event, I'm hearing success stories about GEDmatch uploads, so apparently there's no problem at their end.

[The_Contemplator]

Since no one has quoted the new text in the Raw DNA file Uploads section, here it is:

We are ready to receive the new format FTDNA raw DNA files. The new file format is now available for downloaded from the FTDNA site. Old format files are no longer being accepted.

[teyoung]

I have 5 autosomal kits. Three unarchived to the same file name as the archive, which includes the subject's name. The other 2 are named random characters. A failed privacy attempt? I wonder what naming convention GEDmatch expects?

[teyoung]

Further details.

GEDmatch states "If you rename the file, it is important that the file name retain the 'o36' or 'o37' identifying text.".

The 2 random file names I mentioned above contain the required text. The other 3 do not.

Perhaps, they are not finished randomizing?

[prairielad]

Further details.

GEDmatch states "If you rename the file, it is important that the file name retain the 'o36' or 'o37' identifying text.".

The 2 random file names I mentioned above contain the required text. The other 3 do not.

Perhaps, they are not finished randomizing?

I believe all files that have been processed on the latest chip version have always had the random character file name
files which are 22248kb unzipped, containing 693733 tested RSID/SNP.

Build 37 file names begin with ffo37-, build 36 with ffo-

All my concatenated zip file names(14 kits) regardless of testing chip version, list 37_ or 36_, and older chip version tests unzipped file names the same, 37_ and 36_

[teyoung]

All my concatenated zip file names(14 kits) regardless of testing chip version, list 37_ or 36_, and older chip version tests unzipped file names the same, 37_ and 36_

Odd. My 5 follow no identifiable pattern. I thought it might be due to age or type. Mine is the oldest and the only results from an actual sample. The others are uploads. The files are named, both archive and expanded "36_T_Young_Chrom_Autoso_20160408" and 37_T_Young_Chrom_Autoso_20160408. I am all set at GEDmatch and not particularly concerned about privacy, just curious...

[The_Contemplator]

Just posting this Gedmatch message in case people try to use it while its down and blame FTDNA for whatever reason.

***NOTICE*** - The site will be down starting at 9:00PM EST Sunday 4/10/2016 for 10-15 minutes to switch to the T kit numbers for old FTDNA kits.

Note that existing 'F' (FTDNA) kit numbers on GEDmatch will be changed to 'T' followed by a random kit number. This change does not affect Ancestry or 23andMe kit numbers. If you need to make copies of your results with the old kit numbers, please do so now. Name and email information for matches will stay the same, and can be used to retain continuity in your records.

We are once again accepting FTDNA file uploads - new format files ("concatenated") only. The new format from FTDNA combines autosomal and X-DNA so only one upload is required.

We are now accepting DNA file uploads from WeGene. We wish to welcome WeGene customers to GEDmatch. Please make sure your DNA file is zipped before uploading.

Thank you for your support.

[The_Contemplator]

And Gedmatch has changed the notice's time and date.

***NOTICE*** - The site will be down starting at 9:00AM EST Monday 4/11/2016 for 10-15 minutes to switch to the T kit numbers for old FTDNA kits.

The rest is the same.

[georgian1950]

It is done.

[Ade]

Is Gedmatch still not accepting FTDNA kits?

If this problem had gone away, which kit should I be loading to Gedmatch? If I click on the 'Download Raw Data' icon, I am faced with six choices relating to autosomal, chromosone and concatenated for both build 36 and Build 37. I have no idea what these individual files represent - I tired searching for build 36 but nothing useful came up...

Any help gratefully received

[Jim Barrett]

Yes, they are accepting FTDNA data again. Sign into GEDmatch and follow their directions for uploading your raw data. They tell you how to download your data and which file to download.

[Ann Turner]

Build 36 Raw Data Concatenated (that combines the autosomal and X data)

[CaGma]

I did find I had to use Mozilla browser as I was having problems with Chrome browser not letting me sign on as a new user - wouldn't give the info to verify email. Later I got an email explaining issue was fixed.

Not sure what was going on, but I uploaded my Build 37 Raw Data concatenated file on May 27th without problems. It explained on their website, that it had to be the concatenated and zipped file.

Shirley

[chekwriter]

FTDNA and gedmatch dispute

no sure why is happening. is ancestry pressuring them


this is outrageous.

there is enough sharing of data of both of em.

makes me very unhappy.

will harm all.

not fair customers being so short changed.

[John McCoy]

In case you didn't notice, the issue involving privacy concerns by FTDNA was resolved long ago when GEDmatch developed a way to assign a new, random number for all FTDNA kits, both those already uploaded on GEDmatch and those that have been uploaded ever since. The issue is resolved.