Living DNA results and comparison

Did you get your dna tested via 23amdme? If so, did you score any ashkenazi?
 
Here's a K36 of repaired vs old Ancestry file:

RepairedOldDelta
North_Sea21.37North_Sea21.370
North_Atlantic13.2North_Atlantic13.120.08
Iberian13Iberian12.990.01
Central_Euro10.59Central_Euro10.560.03
Italian9.01Italian9.06-0.05
East_Central_Euro7.66East_Central_Euro7.72-0.06
Fennoscandian7.61Fennoscandian7.62-0.01
French6.39French6.370.02
Basque4.38Basque4.39-0.01
Volga-Ural2.59Volga-Ural2.560.03
West_Caucasian2.22West_Caucasian2.24-0.02
North_Caucasian1.58North_Caucasian1.570.01
West_Med0.39West_Med0.4-0.01

No, Davef I have not had a 23andMe test. I have only had Ancestry + LivingDNA tests plus free uploads like MyHeritage and GEDmatch.
 
Here's a K36 of repaired vs old Ancestry file:

Pretty close. 1st question, how did you repair the livingdna raw data.

2nd question, have you had any correspondence with livingdna over their issues with the raw data? Have they indicated at all
whether they will update their raw file formats or does it seem that this is their final offer?

thx
 
Pretty close. 1st question, how did you repair the livingdna raw data.

2nd question, have you had any correspondence with livingdna over their issues with the raw data? Have they indicated at all
whether they will update their raw file formats or does it seem that this is their final offer?

thx

I used Microsoft Excel to split genotype columns to match Ancestry raw format. I sorted for bad values and then used =VLOOKUP() to find the corresponding values for the bad positions (both ways). Then for the LivingDNA I recombined the columns to put both alleles back together and pasted over the bad values.

I haven't been able to successfully upload the repaired LDNA file yet, I get an error. The repaired Ancestry did pull my numbers into more correct territory ever so slightly.

Edit: I saved the file in Apple format .txt instead of tab delimited or MSDOS and it appears to be working. I'll have repaired LivingDNA figures to compare to repaired Ancestry.com figures!
 
#PopulationPercent#PopulationPercent
1North_Atlantic49.391North_Atlantic49.76
2Baltic23.472Baltic23.09
3West_Med12.483West_Med12.56
4East_Med5.114East_Med5.25
5West_Asian5.115West_Asian5.07
6Red_Sea1.546Red_Sea1.46
7South_Asian1.167South_Asian1.29
8Northeast_African0.648Northeast_African0.59
9Sub-Saharan0.619Oceanian0.42
10Oceanian0.510Sub-Saharan0.37
11Amerindian0.13
#Population (source)Distance#Population (source)Distance
1Southeast_English2.51Southeast_English2.2
2Orcadian3.552Orcadian3.5
3North_Dutch3.783Southwest_English3.88
4Danish4.014North_Dutch3.99
5Southwest_English4.155Danish4.21
6Irish4.446Irish4.34
7West_Scottish4.647West_Scottish4.44
8North_German4.918North_German5.29
9South_Dutch5.789South_Dutch5.85
10Norwegian6.4110Norwegian6.62

These are the unrepaired LDNA numbers for EuroK13 from regular GEDMatch (first set) and GENESIS BETA (second set). Same exact file.
 
Alright, I have repaired files for Ancestry and LivingDNA uploaded to GENESIS BETA:

This is EurogenesK36. Repairing the LDNA file removed a 0.37 Central African component

EuroK36 GenesisAncest.LDNADelta
North_Sea21.3723.632.26
North_Atlantic13.28.89-4.31
Iberian1311.67-1.33
Central_Euro10.5914.834.24
Italian9.016.51-2.5
East_Central_Euro7.666.04-1.62
Fennoscandian7.616.99-0.62
French6.397.771.38
Basque4.385.61.22
Volga-Ural2.591.74-0.85
West_Caucasian2.220.56-1.66
North_Caucasian1.580-1.58
West_Med0.390-0.39
Near_Eastern03.983.98
Eastern_Euro01.291.29
North_African00.470.47
 
Here is repaired file of Ancestry and LivingDNA using Genesis Beta K13. Notice population match for LDNA is all the way down to 2.2 for SE English. Big difference.

K13 Genesis BetaAncREPLDNA REP
#PopulationPercent
1North_Atlantic48.9649.76
2Baltic22.2423.09
3West_Med13.0912.56
4West_Asian7.725.07
5East_Med3.625.25
6Red_Sea2.191.46
7Oceanian0.780.42
8Siberian0.50
9Amerindian0.460.13
10Sub-Saharan0.440.37
11South_Asian01.29
12Northeast_African00.59
#Population (source)Distance
1Southeast_English4.252.2
2Southwest_English4.383.88
3Orcadian4.423.5
4Irish4.444.34
5North_Dutch4.873.99
6West_Scottish4.914.44
7Danish5.634.21
8North_German5.815.29
9South_Dutch5.925.85
10West_German6.97
11Norwegian7.336.62
12Swedish9.24
 
Here is repaired file of Ancestry and LivingDNA using Genesis Beta K13. Notice population match for LDNA is all the way down to 2.2 for SE English. Big difference

Damn, it looks i'm not gonna be buying a livingdna to be honest. Have they been responsive at all to your results and issues with the rawdna?
 
Damn, it looks i'm not gonna be buying a livingdna to be honest. Have they been responsive at all to your results and issues with the rawdna?

I haven't asked them anything. My questions will be about the "Kurdish" and whether I can get the Y positions tested in addition to the positive Y calls.
 
I'm also interested in the Kurdish number. I'm no historian, but I don't see Kurds having any impact on European populations worth mentioning.
 
I haven't asked them anything. My questions will be about the "Kurdish" and whether I can get the Y positions tested in addition to the positive Y calls.

Cool, thanks for this. If they're rawdna is buggy i think its constructive if you let them know so they can nip it in the bud, anyway thanks so much for the valuable feedback, i'm following it closely : )
 
PaperAncestryLDNA
English56.732%69.0%72.7%
Unknown, mostly brit21.875%
Scots or Scots-Irish7.837%8.6%
Norwegian6.250%10.0%9.7%
German3.906%1.0%
Irish1.807%10.0%
Welsh1.489%1.7%
French0.098%
N. Italy0.006%3.0%
Finland3.0%3.1%
Basque3.0%1.2%
Euro Jew1.0%
"Kurdish" 3.0%
100.000%100.000%100.000%

Here is a paper vs Ancestry vs LivingDNA breakdown. On LDNA I pulled Orkney into Scandinavian.

The unknown is all from the mother side with nothing non-British about it based on my mother's and her mother's Ancestry test.
 
MDLPK11.jpgMDLPK11A.jpg

Here are MDLP K11 run with LDNA and Ancestry repaired files.

Does this mesolithic Iranian component cause the mystery near-east stuff?
 
[h=2]Note that the Kurdish only comes up when forced via "Complete" mode. It gives World (unassigned) in both Standard and Cautious

World (unassigned)[/h] When calculating your ancestry we've identified some DNA that is found in multiple areas of the world. These have been listed as "Unassigned", since we cannot pinpoint as confidently, specifically which regions that DNA is similar to. As our methods improve you will see your results updated and a lower proportion of Unassigned appearing.

I have seen a few more people with small % Kurdish.

I emailed them just now with the following demands, along with feedback:

1. Can I get my negative YSNP calls?
2. Can I repair/fill in/re-upload null values that I know from other tests such as Ancestry.com to get a more complete ethnicity estimate?
3. Can you give me details on the data and methods used to calculate the Basque and Kurdish?




I will keep the thread updated with response and response time.
 
I know im becoming repetitive but thanks for the updates im really interested in them
 
Response received today.

1. Cannot have YSNP negative calls because the file would be too large (16,000 calls) and they don't have a nice way to present it.
2. Cannot accept any 2nd party data for consistency purposes (obvious, I just thought I'd ask on a long shot)
3. Generic response about how they calculate ethnicity but no specifics for the Kurdish or Basque provided.
 
There are 150,540 SNPs common to both the LDNA and Ancestry files that GEDmatch uses. When comparing Ancestry files they use 439,216 SNPs. This is probably why puntDAL is terrible with LivingDNA data - it's looking for SNPs that aren't there.

LDNA plays well with GEDmatch Eurogenes and MDLP but not with puntDNAL.

Jtest with LDNA file shows less than 1% Ashkenazi but Oracle calls English/English/English/English. Ancestry test Oracles English/English/English/W. German

I ran all kits for both side of my family and all of them show about the same Ash% on Jtest. I can't find any specific sources on how the mystery near-east or unassigned is determined by any calculator.
 
Last edited:
K36 map.jpgK36mapnew.jpg

K36 map for Bollux from another thread, and now with updated version since the site started coloring.
 
There are 150,540 SNPs common to both the LDNA and Ancestry files that GEDmatch uses. When comparing Ancestry files they use 439,216 SNPs. This is probably why puntDAL is terrible with LivingDNA data - it's looking for SNPs that aren't there.

LDNA plays well with GEDmatch Eurogenes and MDLP but not with puntDNAL.

Jtest with LDNA file shows less than 1% Ashkenazi but Oracle calls English/English/English/English. Ancestry test Oracles English/English/English/W. German

I ran all kits for both side of my family and all of them show about the same Ash% on Jtest. I can't find any specific sources on how the mystery near-east or unassigned is determined by any calculator.
Is living DNA still working to update their raw data? Does anyone know this or are we just hoping gedmatch will eventually be able to process living DNA kits better. Even with Genesis it only takes a couple of seconds for each calc to read my living DNa data. The snp countmust be extremely low.

Sent from my KIW-L21 using Tapatalk
 
Is living DNA still working to update their raw data? Does anyone know this or are we just hoping gedmatch will eventually be able to process living DNA kits better. Even with Genesis it only takes a couple of seconds for each calc to read my living DNa data. The snp countmust be extremely low.

Sent from my KIW-L21 using Tapatalk
LDNA uses a newer chip for their tests. They can't change which SNPs are included. The GEDmatch calcs are the ones that need to be updated to use more SNPs.

GEDmatch Genesis calcs give me more specific results on the oracles.
 

This thread has been viewed 22361 times.

Back
Top