"Download Raw Data" not working

[KATM]

I was very pleased to see my 23andMe-to-Family Finder transfer came through much sooner than predicted. I can see matches, pop finder (FWIW), known relationships, etc., but when I try to download the raw data, I get an error message:

There was an error retrieving your files. Please click this button to report the error:

I did report it using the button. Also cleared the cache & refreshed the page. No joy.

The same thing happened, and still happens, when I've attempted to download my father's FF raw data. I hadn't tried it for his results for some time, but just checked. Of course they both have a note that the downloads are Build 36, that Build 37 will be ready shortly.

Can anyone else download their raw data?

[MFWare]

I am able to download my Build 36 raw data without issue.

[Marbom]

Tried to download my autosomal raw data today but can't and only see the note:

"
March 5, 2013: We apologize for any inconvenience, raw data downloads are temporarily unavailable. We expect soon we will allow the raw data download feature again after final QC on the most recent updates to the Family Finder matching program. We understand this feature is a vital part of your results and will have that feature restored as quickly as possible. Thank you for your patience and understanding.
"

Why do they put the date March 5?

Very strange and very poor work. And when are we going to see our raw data according to NCBI Build 37?

[MFWare]

... And when are we going to see our raw data according to NCBI Build 37?

I downloaded mine on April 12, 2013.

[phje]

I'm now getting the same message (dated March 5, 2013) as Marbom on all of my accounts that have tested for Family Finder. This is interesting, because last week it simply said that the data available for download was Build 36 and that Build 37 downloads will be available shortly.

[Wilma Wildcat]

I just downloaded my mom's last week without problem. I don't remember having a problem with mine, my husband's or my brother's in the past.

[prairielad]

I downloaded mine on April 12, 2013.

I also downloaded Raw Data file on April 13, 2013 labelled build 37, BUT it was never build 37. All of the positions still where the Build 36 positions.

If you compare your files positions to your old raw data file and they have the same positions, then yours is also still build 37.

The chromosome browser was displaying build 37 start stop positions up until about a week ago but has now also reverted back to build 36 as far as I can tell.

The chromosome browser build 37 positions was displaying incorrectly, showning matching segments outside the chromosomes.

For example one of my match prior to the Build 37 upgrade showed the following

Build 36
CHROMOSOME START LOCATION END LOCATION CENTIMORGANS MATCHING SNPS
5 125908008 128491431 1.22 500
6 25359356 36057475 7.76 8500
7 86131629 87246282 1.47 500
10 20918456 23146197 2.55 500
10 105753016 108716420 2.42 800
11 103860000 106700791 2.46 600
12 20668638 21368250 2.53 500
13 51090690 53181328 1.42 500

After Build 37 Upgrade
5 125284770 127519049 1.22 500
6 24544903 35341850 7.76 8500
7 84890587 87150937 1.47 500
10 19796594 21066981 2.55 500
10 103316818 106842041 2.42 800
11 102427380 104707732 2.46 600
12 18888456 20526181 2.53 500
13 49250997 51322188 1.42 500

Now (reverted back to Build 36)
Chromosome Start Location End Location centiMorgans (cM) # of Matching SNPs
5 125908008 128491431 1.22 500
6 25359356 36057475 7.76 8500
7 86131629 87246282 1.47 500
10 20918456 23146197 2.55 500
10 105753016 108716420 2.42 800
11 103860000 106700791 2.46 600
12 20668638 21368250 2.53 500
13 51090690 53181328 1.42 500

Until they get the kinks out of the Build 37 Upgrade, they must of decided it best to revert back to Build 36.

[mollyblum]

It was available in April but it is broken again and doesn't work anymore (raw data). Seriously ridiculous! FtDNA really needs to get this stuff fixed. It has been almost 6 months since the build 37 debacle! 6 months and still issues!

The only thing I can think of is that they have family members working on this stuff at the company that they refuse to fire?????

I also downloaded Raw Data file on April 13, 2013 labelled build 37, BUT it was never build 37. All of the positions still where the Build 36 positions.

If you compare your files positions to your old raw data file and they have the same positions, then yours is also still build 37.

The chromosome browser was displaying build 37 start stop positions up until about a week ago but has now also reverted back to build 36 as far as I can tell.

The chromosome browser build 37 positions was displaying incorrectly, showning matching segments outside the chromosomes.

For example one of my match prior to the Build 37 upgrade showed the following

Build 36
CHROMOSOME START LOCATION END LOCATION CENTIMORGANS MATCHING SNPS
5 125908008 128491431 1.22 500
6 25359356 36057475 7.76 8500
7 86131629 87246282 1.47 500
10 20918456 23146197 2.55 500
10 105753016 108716420 2.42 800
11 103860000 106700791 2.46 600
12 20668638 21368250 2.53 500
13 51090690 53181328 1.42 500

After Build 37 Upgrade
5 125284770 127519049 1.22 500
6 24544903 35341850 7.76 8500
7 84890587 87150937 1.47 500
10 19796594 21066981 2.55 500
10 103316818 106842041 2.42 800
11 102427380 104707732 2.46 600
12 18888456 20526181 2.53 500
13 49250997 51322188 1.42 500

Now (reverted back to Build 36)
Chromosome Start Location End Location centiMorgans (cM) # of Matching SNPs
5 125908008 128491431 1.22 500
6 25359356 36057475 7.76 8500
7 86131629 87246282 1.47 500
10 20918456 23146197 2.55 500
10 105753016 108716420 2.42 800
11 103860000 106700791 2.46 600
12 20668638 21368250 2.53 500
13 51090690 53181328 1.42 500

Until they get the kinks out of the Build 37 Upgrade, they must of decided it best to revert back to Build 36.

[varlene]

If it was available in April, someone really goofed by putting a March 5, 2013 date on the message, making it seem like it has been been broken for nearly three months. Not that being broken since April is much better. For GEDmatch, I would be happy with Build 36, which is what they want anyway, but not being able to download any raw data file from FTDNA at the moment, is terrible.

[prairielad]

As I mentioned before, build 37 Raw Data was never available

Yes it was labelled build 37 and some SNP (rs numbers) where omitted, but it was never build 37, that is why it was relabelled to build 36 with message.

Until the Raw Data file is released with the new Positions, it will not be build 37.

See following Post from time of original labelled build 37 raw data release.

http://forums.familytreedna.com/showthread.php?t=32572

[prairielad]

For example the first rs number listed is listed as following between builds

Build 36
RSID............CHROMOSOME......POSITION..........RESULT
rs3094315...........1 ..................742429................AG

Build 37
RSID............CHROMOSOME......POSITION..........RESULT
rs3094315...........1 ..................752566................AG