We've known that my family's subgroup was I-L1275 since July 2012 when L1275 was discovered in WTY. Earlier this year FTDNA listed my cousin as A5338 (above L1275 and discovered in his Big-Y and two others); some time later, his subgroup was changed to A5339 (just below A5338). Since by this time we knew that he and one other member of the subgroup were A8177, I requested a correction which was made within a week.; however, when I checked a few minutes ago to see whether our Big-Y results had been updated, I was surprised to find that my cousin is now listed as L1275 and his closest match (the second A8177) is listed only as M253 unconfirmed. What is going on here? Lindsey

FTDNA is revising and recalculating BigY results, a process estimated to take a week or more. If you look at the match's BigY and it says "Awaiting Results" then just hang in there. Ann Turner On Wed, Oct 18, 2017 at 10:48 AM, Lindsey Britton <[email protected]> wrote: > > > We've known that my family's subgroup was I-L1275 since July 2012 when > L1275 was discovered in WTY. Earlier this year FTDNA listed my cousin as > A5338 (above L1275 and discovered in his Big-Y and two others); some time > later, his subgroup was changed to A5339 (just below A5338). Since by this > time we knew that he and one other member of the subgroup were A8177, I > requested a correction which was made within a week.; however, when I > checked a few minutes ago to see whether our Big-Y results had been > updated, I was surprised to find that my cousin is now listed as L1275 and > his closest match (the second A8177) is listed only as M253 unconfirmed. > What is going on here? > > Lindsey > > > ------------------------------- > To unsubscribe from the list, please send an email to > [email protected] with the word 'unsubscribe' without > the quotes in the subject and the body of the message >

I got that message. It said "We’re giving you the ability to view your SNP data from Big Y. This will allow you to personally assess all SNP call positions that are being evaluated for matching purposes. This data will be continuously updated." I don't have mine yet, but somebody sent me their bed/vcf files. Odd. I find positions that are clearly ancestral both by phylogeny and what the vcf file says, but the browser (the thing that shows reads like BAM browser) shows that ALL reads are derived. The vcf file says some reads have map quality zero, others are >10 map quality. Also there are three other positions in the reads that are phylogenetically wrong on the reads. The vcf file has some but not all of these. One has a wrong "name" listed! Yes, the bed has these positions listed. Oh yes, one more thing ... this is in the middle of the (former) 22,200,000 region, now 20,060,000 area. But if you look at only reads with map quality >10 in Build 37, its completely reliable. Also, the whole browser is sort of useless for matching as far as I can tell today, since I can't seem to get the thing to work with a matching person's read. I sure seemed to remember doing that a couple of days ago. If you could check the reads for both you and every match, at every position, and there were no gotchas (see above) then maybe the bam and maybe even the bed/vcf would be unneeded (except for things they don't list at all), so long as its a RARE need, not for admins with lots of BigYs. Why does my Outlook spell checker say bam is not a word? Did they never ask Emeril Lagasse?