PDA

View Full Version : Big-Y



dp
04-20-2017, 09:57 PM
I just ordered Big-Y for two Eure kits, of matching haplotypes, that are predicted to be I1-M253.
These kits are in the I1 projects (641807, 599403). Is there an NGS phylogeny of I1 Big-Y kits, short of Yfull?
dp :-)

dp
05-16-2017, 04:57 PM
The Big-Y kit came back P109>Y3662>S14887>S18218.
Any S18218+, Y30033- carriers out there. This kit is Y30033+.
#Y30033 is at 18750778.
dp :-)
PS: I joined the I-P109 project https://www.familytreedna.com/groups/y-dna-i-p109/about/background and like the website http://p109.haplogroup.org/

dp
05-19-2017, 06:51 PM
The Big-Y kit came back P109>Y3662>S14887>S18218.
Any S18218+, Y30033- carriers out there. This kit is Y30033+.
#Y30033 is at 18750778.
dp :-)
PS: I joined the I-P109 project https://www.familytreedna.com/groups/y-dna-i-p109/about/background and like the website http://p109.haplogroup.org/
I think we (me and the P109 admin) have found a new branch under S18218/Y30033. I found two novel variants that only one of the Big-Y matches shared: 19333061 C-A & 21876161 C-T. Neither are in Ybrowse :-)
I requested the .bam so I can upload to Yfull. A lot of my cousin's novel variants are in the DYZ19 repeat, can any of them be phylogenetic? There's one novel variant within it that 3 of the S18218s have.

---
Of the novel variants the ones that my relative has that none of his matches have, and that are not in Ybrowse are:
16367777 A-C
22843480 T-G
6735403 T-C
8034387 G-A
9000036 C-T.

Comment: I have a second Big-Y for a Eure being performed.
dp :-)

dp
06-10-2017, 05:13 PM
I submitted the .BAM of my cousin (599403) to Yfull. His kit will be: YF09967.
The results of Big-Y for the other kit (641807) still have not come in.
dp :-)

dp
07-01-2017, 03:35 PM
The Big-Y results of my second Eure kit has come in. The (simplified) tree structure, below I-S18218 is now:
17332
8034387 G-A and 16367777 A-C were found to be key SNPs, as both of them are carriers; this node is in blue.
The SNPs in the red boxes indicate those that are not shared by the respective donors, but according to the .bed files were tested.
All Eure's of their haplotype have to be carriers of the SNPs in the node directly above the blue bordered node.
-dp

dp
07-01-2017, 03:36 PM
*whoops* -Happy 4th.

dp
07-03-2017, 09:22 PM
Yfull gives the following as the current private markers for YF09967:
Name;Position;Reference;Derived;Q;Qual;Reads
YFS4000938;8034387;G;A;100;Best qual;54
YFS4001365;22843480;T;G;100;Best qual;56
YFS4000934;6735403;T;C;97;Acceptable qual;39
YFS4000939;9000036;C;T;94;Acceptable qual;68
YFS4001152;16367777;A;C;95;Acceptable qual;32
YFS4000935;7422159;C;A;100;Ambiguous qual;2
YFS4000936;7832153;T;G;100;Ambiguous qual;2
YFS4000940;9427738;T;C;100;Ambiguous qual;2
YFS4001153;16912619;T;C;100;Ambiguous qual;2
YFS4001155;18156571;G;T;100;Ambiguous qual;2
YFS4001368;23066492;C;A;100;Ambiguous qual;2

dp
07-05-2017, 09:36 PM
Regarding Post 5:
According to Mr Taban, the I-P109 admin 3715338 is not phylogenetic. I can't see which SNPs are unstable in the clade because the system won't let me use the matching tools because it insists the kit has no matches; which is absolute BS. Results can "in" on 6-20. I had to complain just to get "engineering" to let me see anything with the Results tab, such as .vcf & .bed, which of course let me prove that both Eure kits were not only STR matches but formed the novel branch. Second complaint filed last weekend about this additional bug.
dp :-)

dp :-)