Get error when uploading ANcestryDNA

[DBrooks]

Just a follow up to this, my moms dna which i put through this tool and uploaded successfully to FTDNA has finished processing by them and shows all the matches I would expect as a normal upload would! I can now use the matrix tool and narrow down which lines my matches are coming from on my tree!

Same here--thank you! Worked like a charm. Matches are correct, everything looks good on this end. We did compare to results at Gedmatch and some percentages on admix are .01%-.03% off from the original, but expecting that would occur with the constant flux of data.

Again, thank you all so much--have been fighting this upload for a month. Your fix took all of 10 minutes (half of that was reading and copying files over!)

[chrisbonisa]

Same here--thank you! Worked like a charm. Matches are correct, everything looks good on this end. We did compare to results at Gedmatch and some percentages on admix are .01%-.03% off from the original, but expecting that would occur with the constant flux of data.

Again, thank you all so much--have been fighting this upload for a month. Your fix took all of 10 minutes (half of that was reading and copying files over!)

Awesome! And yeah if you do the math, about 1000 snps get discarded as they dont exist in the format excepted by ftdna and thats out of 650,000 or so.....around 0.15% or 99.85% coverage. Thats such a tiny difference I don't think it would affect anything.

[chrisbonisa]

Slight update

Looks like someone tried to upload a double-line spaced file for some reason, and also whitespace before the columns, maybe they opened the text file up in wordpad or something. Anyways I added some code to filter those extra lines out and trim the whitespace to be able to process files like this. The tool now only cares about this:

If a line after whitespace trimmed starts with "rs" but not "rsid"(this is a header line). That row will be assumed to be data and tab delimited(white spacing also removed from other columns).

Columns are in this order:
rsid chromosome position allele1 allele2

This is all the same as a typical Ancestry.com file, I'm basically just filtering out any extra characters or linefeeds introduced by opening the file in a text editor and re-saving it.

[clarkie]

Yeah I didn't notice the PM, but I've read and responded to it. I've built out a tool that seems to work 100%. The key to solving it is a combination of what I was doing before, filling in the blank template file of a working file with the data from the non-working one, but keeping the I's and D's from the template and not zeroing the entire thing and also filling everything in by position number instead of RSID, which is what I was doing the first go around.

I stuck it up on one of my websites where I'm doing some other DNA stuff, anyone can feel free to use it if they wish:

http://www.mapmy23.com/tools/ancestry_ftdna_fix.php

If you do use the tool, please respond in here and let others know if it works or not. So far in my testing its working 100%, but the more people that try it the more we will know if this is a solution until FTDNA resolves it themselves.

Thank You Thank You Thank You!

Have followed this thread for weeks, and been trying myself to edit the two ancestry files I had, realigning lines and adding no calls to no avail

Your Tool worked perfectly and both 17.184kb files (Tests from Ancestry since Aug 17th) now uploaded to FTDNA with no problems!

Cant thank you enough!

Ryan

[mamoahina]

If you do use the tool, please respond in here and let others know if it works or not. So far in my testing its working 100%, but the more people that try it the more we will know if this is a solution until FTDNA resolves it themselves.

Wow, thank you so much! I've been reading ways to fix it and no luck. This was fast and simple! Thank you!!!!!!

[chrisbonisa]

Thank You Thank You Thank You!

Have followed this thread for weeks, and been trying myself to edit the two ancestry files I had, realigning lines and adding no calls to no avail

Your Tool worked perfectly and both 17.184kb files (Tests from Ancestry since Aug 17th) now uploaded to FTDNA with no problems!

Cant thank you enough!

Ryan

Excellent! Glad this is working! We have had over 75 kits put through the tool now so it seems to be working for a lot of people!

Wow, thank you so much! I've been reading ways to fix it and no luck. This was fast and simple! Thank you!!!!!!

Glad this is working!

On a side note, we had 2 kits uploaded that appear to be v1.0 files, which there is only 60% snp coverage compared to v2.0 which doesn't sound very viable. Were there ever problems uploading v1.0 files? In theory I could make a v1.0 template to achieve the same results as I have my brothers dna file from 2016 which he successfully uploaded last year. If there is any interest in this, whomever is trying, please let me know and I will add that, there is no identifiable info in the files so I don't know who you are, you would have to reach out to me.

[Ann Turner]

I stuck it up on one of my websites where I'm doing some other DNA stuff, anyone can feel free to use it if they wish:

http://www.mapmy23.com/tools/ancestry_ftdna_fix.php

If you do use the tool, please respond in here and let others know if it works or not. So far in my testing its working 100%, but the more people that try it the more we will know if this is a solution until FTDNA resolves it themselves.

I posted a link to your tool in several places, and there were a number of grateful responses!

[Ann Turner]

On a side note, we had 2 kits uploaded that appear to be v1.0 files, which there is only 60% snp coverage compared to v2.0 which doesn't sound very viable. Were there ever problems uploading v1.0 files? In theory I could make a v1.0 template to achieve the same results as I have my brothers dna file from 2016 which he successfully uploaded last year. If there is any interest in this, whomever is trying, please let me know and I will add that, there is no identifiable info in the files so I don't know who you are, you would have to reach out to me.

FTDNA has accepted v1 files for a very long time. If there are current problems, they must be different.

[KATM]

On a side note, we had 2 kits uploaded that appear to be v1.0 files, which there is only 60% snp coverage compared to v2.0 which doesn't sound very viable. Were there ever problems uploading v1.0 files? In theory I could make a v1.0 template to achieve the same results as I have my brothers dna file from 2016 which he successfully uploaded last year. If there is any interest in this, whomever is trying, please let me know and I will add that, there is no identifiable info in the files so I don't know who you are, you would have to reach out to me.

Actually, Ancestry's v1.0 chip had more SNPs in common with FTDNA's chip than their v2.0 chip, if that is what you mean. See ISOGGs "Autosomal SNP comparison chart" for specifics.

I don't recall people having issues uploading Ancestry v1.0 results, but others could comment on that.

[chrisbonisa]

Actually, Ancestry's v1.0 chip had more SNPs in common with FTDNA's chip than their v2.0 chip, if that is what you mean. See ISOGGs "Autosomal SNP comparison chart" for specifics.

I don't recall people having issues uploading Ancestry v1.0 results, but others could comment on that.

I've not seen this chart before(great info!), but it actually shows exactly what I'm talking about. If you look at the Ancestry v1 versus v2 you see 407,968 out of 641,908 are shared which explains the ~60% overlap between the two attempting to use this tool to build a v2 file out of a v1 file using a v2 template.

Technically we could build a tool to convert from any of these formats to another, but there would be so much discarded due to the lack of overlap, I'm not sure it would be worth the time.

[chrisbonisa]

I posted a link to your tool in several places, and there were a number of grateful responses!

Yay!

[KATM]

I've not seen this chart before(great info!), but it actually shows exactly what I'm talking about. If you look at the Ancestry v1 versus v2 you see 407,968 out of 641,908 are shared which explains the ~60% overlap between the two attempting to use this tool to build a v2 file out of a v1 file using a v2 template.

Technically we could build a tool to convert from any of these formats to another, but there would be so much discarded due to the lack of overlap, I'm not sure it would be worth the time.

I misread your earlier post, but I understand now. Must.get.more.sleep!

[chrisbonisa]

I misread your earlier post, but I understand now. Must.get.more.sleep!

LOL....its all good....thank you for that link, it explains some questions I had myself! Now I can totally see why they can't accept v5 23andme files. Its really a shame all of these companies can't agree on something closer to eachother, I understand they are all competing, but at the end of the day they are only hurting the consumer, they should really just focus on the tools they provide to build trees and find matches etc and use a more standardized dna sample. For example Ancestry is fantastic at building trees and doing ancestor research but awful at analyzing dna matches, while FTDNA is great at analyzing dna matches but terrible at building trees and doing research......ugh. And then we have GEDMATCH with some amazing tools but a gui design and usability that puts off the average user from using it actively(no offense to those guys, they do amazing work).

I may just end up building a tool that is a mixture of ftdna chromosome browser and their matrix tool but allows more people on it and ability to mark them and guess where on a tree line they are related. It would be nice to just upload all my matches somewhere and mark known people and it just starts figuring out how and where people are related automagically.

[Ann Turner]

A question for those who have uploaded both an original and a fixed kit to GEDmatch:

Would you check to see how many SNPs are used when comparing the originals to themselves and how many are used when comparing the original to a fixed kit?

[chrisbonisa]

A question for those who have uploaded both an original and a fixed kit to GEDmatch:

Would you check to see how many SNPs are used when comparing the originals to themselves and how many are used when comparing the original to a fixed kit?

435970 SNPs used for this comparison. <- original to itself
435861 SNPs used for this comparison. <- original to fixed

This is using the one to one compare using these kits:
Original: A084257
Fixed: A179561