PDA

View Full Version : BY3327..BY3332 problematic in DF27 SNP Pack



lgmayka
01-09-2016, 08:20 PM
FTDNA's documentation includes the following SNPs in the R1b-DF27 SNP Pack, but in reality FTDNA has given up on them:
BY3327
BY3328
BY3329
BY3330
BY3331
BY3332

Kit 399633 ordered the R1b-DF27 SNP Pack, and his order was marked as completed on December 15. He was classified as R-ZZ12_1, but the 6 SNPs listed above were still colored orange ("Test In Progress"). No longer--those 6 SNPs are now shown in blue ("Test Available"), indicating that FTDNA has officially given up on them as far as the DF27 SNP Pack is concerned.

Unfortunately, this means that kit 399633 did not get much from his $180 (M343 and DF27 SNP Packs).

razyn
01-09-2016, 09:56 PM
Kit 80665 has the same problem, with the same list of SNPs now in blue. Back in November, they were allegedly on the M-343 pack. I don't know what their positions and mutations are, is that information in some documentation I don't know about?

razyn
01-12-2016, 08:01 PM
I think the problem may be typos in the data entry for their haplotree display. The relevant SNPs may in fact be BY3227 through BY3233. These, at least, are on the Big Tree (and one may find their respective positions by hovering the cursor over the SNP number). SNPs numbered above BY3300 are not on that tree.

TrickyDick
01-12-2016, 08:05 PM
Does anyone have a list of the original SNP's offered in the DF27 pack?

lgmayka
01-12-2016, 10:15 PM
SNPs numbered above BY3300 are not on that tree.
Frankly, this is an excellent reason not to use BY, BZ, or other undocumented prefixes for SNPs. Every named SNP should be referenceable in a public database. A named SNP that does not have a published location is almost worthless.

razyn
01-12-2016, 10:24 PM
Or, the BY3300 series may be in some other haplogroup -- that would make it not appear on Alex's R1b-specific tree. But the problem remains: if the SNP is not correctly named, but has a blue button on the FTDNA Haplotree display, somebody is going to spend good money testing for it needlessly.

ArmandoR1b
01-12-2016, 10:55 PM
I had requested info from FTDNA on two of those SNPs. If you email them they will give you the region the mutation was in and the alleles.

17937278-A-G is BY3330 This is shared by DF27 kits B1522 and 193923 and HG01491
8492888-G-A is BY3331 This is shared by two of the above kits 193923 and HG01491
http://www.ytree.net/DisplayTree.php?blockID=1002

Kit B1522 shows to be terminal for BY3330 in the DF27 page https://www.familytreedna.com/public/R1b-DF27?iframe=yresults

Kit 193923 shows to be terminal for BY3331 in that same DF27 page.

There are other BY33xx SNPs in the DF27 project.

396854 and 166863 are BY3327

182832 and 408388 are BY3329

248088 and 331655 are BY3332

Since BY3330 and BY3331 coincide with mutations that Alex was able to find in DF27 kits then BY3327, BY3329, and BY3332 and are also likely to be mutations that Alex has in the list of those kits so they do belong to the DF27 haplogroup.

lgmayka
01-13-2016, 03:22 AM
Since BY3330 and BY3331 coincide with mutations that Alex was able to find in DF27 kits then BY3327, BY3329, and BY3332 and are also likely to be mutations that Alex has in the list of those kits so they do belong to the DF27 haplogroup.
But if they are legitimate SNPs downstream from DF27, why weren't they tested on kit 399633?

razyn
01-13-2016, 03:42 AM
I think the problem may be typos in the data entry for their haplotree display. The relevant SNPs may in fact be BY3227 through BY3233. These, at least, are on the Big Tree (and one may find their respective positions by hovering the cursor over the SNP number). SNPs numbered above BY3300 are not on that tree.

Okay, so it's not a typo issue (which would have been easier for somebody to fix, either FTDNA or Alex). The positions Armando got for the corresponding SNPs beginning with BY33xx don't match the positions Alex shows for a corresponding BY32xx. Alas.

ArmandoR1b
01-13-2016, 04:47 PM
But if they are legitimate SNPs downstream from DF27, why weren't they tested on kit 399633?

That's a good question and only FTDNA could answer that. I really doubt that it is going to be because they are not legitimate SNPs. Is there a way to look up 17937278-A-G and 8492888-G-A in HG01491 at YFull?

FTDNA also needs to be queried for the region and alleles for BY3327-BY3329 and BY3332, which I still haven't asked about, so those can also be looked up at YFull if possible and compared with the Big Tree.

Badger33
01-30-2016, 02:20 AM
Did anyone get an answer on this from FTDNA?

lgmayka
01-30-2016, 02:52 AM
Is there a way to look up 17937278-A-G and 8492888-G-A in HG01491 at YFull?
Yes, there is. HG01491 is indeed
17937278 G
8492888 A

ArmandoR1b
01-30-2016, 01:04 PM
Yes, there is. HG01491 is indeed
17937278 G
8492888 A

I take it there aren't SNP names at YFull associated with those mutations. Is that correct?

lgmayka
01-30-2016, 04:56 PM
I take it there aren't SNP names at YFull associated with those mutations. Is that correct?
Correct.

razyn
02-02-2016, 04:09 PM
I did some sorting this morning, several of the SNPs in question are in groups Pb, Pd, and Pe. Those were in place, but the captions have been rewritten a bit.

My former group Pf has been eliminated, and its members are now a new group Ib. That one (BY3329, and some equivalents) turned out to be a brother clade of Z225 -- both under ZZ39. Also it's now color-coded red, instead of cyan.