Tweet
Kit #141056 has GATA H4 recently reported with 10 repeats. This person was previously tested at Ancestry.com with 11 repeats. Is this still an inter-company reporting issue or an indication of a testing error?
-
-
You are correct; there is no lab error. FTDNA reports this locus' allele count -1 in comparison to Ancestry.
Good question, though. The various labs screwed around for a long time before settling on their current reporting conventions for this marker.
But rest assured: No problem there.
Originally posted by fmoakes View Post -
So, does that mean if I'm tested on FTDNA with an 11 and I'm manually entering my data at ancestry.com i should adjust that +1 to 12?
(I don't recall seeing any notes on cross-company adjustments when entering my results at ancestry)
Originally posted by Frederator View PostComment
-
Correct.
The following notice regarding lab conversions will appear on your Ancestry.com results edit page. Quote:
"You may notice that up to four of your marker values have changed. The Family Tree DNA service reports some values differently. Ancestry.com DNA has automatically adjusted your results so that they can be compared equally against all participants.
Y-chromosome markers adjusted:
DYS-441 - has been increased by 1
DYS-442 - has been increased by 5
Y-GATA-H4 - has been increased by 1
Y-GATA-A10 - has been increased by 2 "
P.S. The Y-Search conversion page note is out of date and INCORRECT. As I mentioned in a previous post,the labs screwed around for quite a bit before settling on their current conventions, and Y-Search seems not to have updated their conversions advice regarding Y-GATA-H4. IGNORE the Y-Search conversion note regarding Y-GATA -H4.
Originally posted by dwight View PostComment
-
Hmmm... OK, I see that message now. But my allele values appear exactly the same (i.e., as if nothing has been changed). For DYS-442, it's 14 in both (FTDNA, ancestry.com). Does this mean that they leave the number alone on the entry page but in the background they're adjusting it?)
It wouldn't appear this is the case. If I look at my "matches" page on ancestry.com, it has my DYS-442 value as 14, same as I entered it as per FTDNA results.
Originally posted by Frederator View PostComment
-
You know, it's been a while since I entered my data. It's possible that the note about Ancestry.com being automatically updated was relevant only to people who entered data before the last protocol change. That part of the wording may be a typo or may not be applicable to you or in error.
But we're lucky that we can see the value on the matches page.
I'd recommend manually updating to Ancestry.com protocol values and then checking the matches page again to see if it's reading properly.
Worse case scenario is that it adds another 5 to 442 and 1 to H4 when the whole site refreshes overnight. But even then you'll be able to readily see it by checking the current value on your matches page, and the fix is a simple reversion to FTDNA protocol values and waiting for the site to refresh again.
Originally posted by dwight View PostComment
-
OK, so I went in and adjusted the two relevant values - it took awhile to refresh but now it has. Previously I had two "matches" (not particularly close) - after adjustments, I lost one of those and gained two more, so I now have 3. (Two of them get a lot closer - 30/32 and 29/32 - if I round up their 14.3 values to 15, which is what I have on both 464c and 464d.)
Can I say I'm less than fully confident about any of this though? I mean I never would have known about these needed adjustments if I hadn't been reading this forum everday. Why should I assume these other people have entered their data correctly? Ancestry doesn't tell us which company our matches were tested with.
Originally posted by Frederator View PostComment
-
Good points. But I'm afraid that much is out of our hands--a bit like close matches having the power to decide whether or not to respond to inquiries.
Sometimes I wonder if I do have a statistically significant match out there who's made a lab translation or other data entry error but I'll never find out about it.
I do know for a fact that one of my "close-est" matches (only hypothetically possible MRCA from late middle ages) at DNA Heritage hasn't updated his H4 since the last protocol change, and "dropped off the radar" because of it.
Not sure there's anything to be done about it, apart from being extra aware of the changes yourself. And maybe running some searches with alternate values on the effected markers.
Originally posted by dwight View PostComment
-
I feel your pain.
I entered my MTDNA info over there and it said I had no matches. I know FTDNA changed the numbering on my insertions a while back so I tried the old numbers. No matches. Now I don't know which to leave it as. I got no popup telling me there would be an adjustment LOL
Also, they list a I, II, and III!!! I have no idea if I should be breaking my II into II and III?Comment
Comment