12.07.2015 Views

Read More DNAPrint Log Entries for Prior Year of 2005 - Kerchner

Read More DNAPrint Log Entries for Prior Year of 2005 - Kerchner

Read More DNAPrint Log Entries for Prior Year of 2005 - Kerchner

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>2005</strong> <strong>Entries</strong> into <strong>Kerchner</strong>'s <strong>DNAPrint</strong> Test Results <strong>Log</strong>later waves <strong>of</strong> migrations from Asia to the Americas, which might show up on the test as "EastAsian", but is really a later migratory wave, like the Na-Dene peoples such as the Navajo andApache. It’s possible that the 21% East Asian in my Grandmother could be evidence <strong>of</strong> Navajo orApache admixture with the Pueblo. Also interesting, is that my test was consistent with theknowledge <strong>of</strong> my Grandmother being 50% Native American (my expected NA was 12.5% and Itested <strong>for</strong> 16%). Additionally, I do have known East Asian (Filipino) descent from my paternaland maternal Grandfathers, NOT from my paternal and maternal Grandmothers. It could be thatmy results were more ‘accurate’ because I have both recent East Asian AND Native Americanancestry, and the test was better able to distinguish between the two. If my paternal Grandmotheris really 25% NA and 21% EA instead <strong>of</strong> 50% NA, it would make sense that my DNA test wouldshow up with less NA and more EA, which it did not. The test is apparently confusing NA with EAand vise versa. It seems very common, judging by the numerous other posts on this website bypeople who have known Native American descent, but come up with East Asian results. I amawaiting my Grandmother’s MtDNA results which I will post as soon as they are sent out.Email address (To use delete '-Wednesday-' and add @ sign in that position): dfc1-Wednesdayearthlink.netGuest: SLDate-Time: Wednesday, July 06, <strong>2005</strong> at 22:24:36 (CDT)My Expected Results <strong>for</strong> IE,EA,NA,SSAF Population Groups: 38, 50, 12, 0My Actual <strong>DNAPrint</strong> Results <strong>for</strong> IE,EA,NA,SSAF Population Groups: 34, 48, 16, 2<strong>DNAPrint</strong> Test and/or Euro add-on Test Version Number: 2.5Date <strong>DNAPrint</strong> Test and/or Euro add-on Test Was Ordered: November 2004Comments: Y-DNA paternal line = Haplogroup C. MtDNA maternal line = Haplogroup U5a1a.The results <strong>of</strong> the 2.5 test were very close to my expected results. I have read that people with NAor Mediterranean IE test <strong>for</strong> small amounts <strong>of</strong> SSAF, so the SSAF showing up is not that much <strong>of</strong>a surprise. The 2.5 test seemed to be accurate, as it rather accurately represented my ethnicbackground. Both my maternal and paternal grandfathers are 100% Filipino, I have a maternalgrandmother who is 100% German and a paternal grandmother who is 50% Spanish andPortuguese and 50% Native American (Pueblo Tribes). Both my parents have 'mixed' ancestry, asdo I. This made me 50% Filipino (25% from Father, 25% from Mother), 25% German (fromMother), 12.5% Spanish and Portuguese and 12.5% Native American-Pueblo Tribes (fromFather). When you add it all up (50% EA, 37.5% IE, 12.5% NA), it is very close to the results <strong>of</strong>the 2.5 test (48% EA, 34% IE, 16% NA, 2% SSAF). I had taken the 2.0 test a few months earlierand received very different results. The 2.5 test was accurate within 2%-3.5% <strong>of</strong> my expectedresults as compared to the 2.0 test which was accurate within 8%-10.5% <strong>of</strong> my expected results.Based on the results <strong>of</strong> both the 2.5 and 2.0 tests, I believe that the 2.5 is more accurate than the2.0.Email address (To use delete '-Wednesday-' and add @ sign in that position): dfc1-Wednesdayearthlink.netGuest: Patricia Newellfile:///D|/KERCHNER.COM/dnaprintlog<strong>2005</strong>.htm (12 <strong>of</strong> 21)3/8/2010 8:12:17 PM

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!