{"id":13819,"date":"2020-02-17T01:35:40","date_gmt":"2020-02-17T01:35:40","guid":{"rendered":"http:\/\/www.jmhartley.com\/HBlog\/?p=13819"},"modified":"2020-02-17T01:35:40","modified_gmt":"2020-02-17T01:35:40","slug":"waiting-for-my-hartley-big-y-700-manual-review-part-2","status":"publish","type":"post","link":"http:\/\/www.jmhartley.com\/HBlog\/2020\/02\/17\/waiting-for-my-hartley-big-y-700-manual-review-part-2\/","title":{"rendered":"Waiting for My Hartley Big Y 700 Manual Review: Part 2"},"content":{"rendered":"

My Big Y 700 upgrade results came in on January 16, 2020. I had upgraded because another Hartley had tested for a new Big Y 700. Steve’s results came in on January 21, 2020. I wrote Part 1 while awaiting my Big Y manual review here<\/a>. My thinking was that if Steve and I both had the Big Y 700 test done, then our results would be more consistent. I now see that I would have been better off testing my brother for Big Y.<\/p>\n

Big Y and the Rule of Three<\/h2>\n

Bill Wood from the FTDNA BigY Facebook group developed what he calls the Big Y Rule of Three. Here is the short version of the Rule of Three:<\/p>\n

\"\"<\/a><\/p>\n

The first candidate was me. So I’m all set there. These slides are from Bill Wood:<\/p>\n

 <\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

\"\"<\/a><\/p>\n

This is where I should have had my brother tested. The importance of this test is that my brother should match me on all or nearly all of my SNPs. These matches will then result in a terminal haplogroup for my branch of Hartley. So my next step will be to have my brother tested. Here is what I understand to be current pricing for Big Y:<\/p>\n

\"\"<\/a><\/p>\n

Big Y is $449. I must have paid about $189 for my upgrade.<\/p>\n

 <\/p>\n

\"\"<\/a><\/p>\n

Here I have a lot of 2nd cousins, so that could have worked. One other person, Michael had already taken the Big Y (now called 500) test. Now we have Steve also. Steve and Michael are both greater than 4th cousin to me, but I don’t know exactly how we connect genealogically.<\/p>\n

Alex Williamson and the Big Tree<\/h2>\n

I mentioned the Big Tree in my previous Blog on Hartley YDNA. On January 13, 2020, an administrator for the R L513 and Subclades FTDNA group wrote a message requesting that Big Y 700 results be posted to the Big Tree:<\/p>\n

\"\"<\/a><\/p>\n

I posted my new results and they showed up at the Big Tree under my Unique Mutations. My new results are under the heading of BigY3:<\/p>\n

\"\"<\/a><\/p>\n

My understanding is that the entries with a plus sign are the important ones:<\/p>\n

\"\"<\/a><\/p>\n

That means that the SNPs numbered 26539382, 13658297 and 4317527 are newly detected for me by the Big Y 700 test. 13658297 is interesting because in the previous test, it was rejected.<\/p>\n

** indicates “REJECTED” with just a single variant<\/em><\/p>\n

Also 13658297 is important as it is listed as being in the combBED Region.\u00a0 My understanding is that the combBED Region is a highly reliable region for SNP detection. This is indicated by a Y in the second column of Y’s.<\/p>\n

Of the above three unique mutations, two show up in my FTDNA Big Y list of Private Variants:<\/p>\n

\"\"<\/a><\/p>\n

What About 13658297?<\/h3>\n

I used to show 13658297 as a private variant, but it is no longer on the list:<\/p>\n

\"\"<\/a><\/p>\n

That could mean that it is no longer a private variant, because Steve also has that variant. I suppose that means that FTDNA is working on its manual review. I previously had 10 private variants. Now I have 6.<\/p>\n

Where Does That Leave Me and the Hartley YDNA Tree?<\/h2>\n

This is the chart that I came up with previously:<\/p>\n

\"\"<\/a><\/p>\n

I had highlighted in gold those matches that I had with Steve. There are 6 variants that are not highlighted which is what I now show as having for Private Variants now at FTDNA. I don’t see any matches between Steve and Michael. I take that to mean that Steve and I will be named on a newer Hartley Branch and that Michael will remain on the older branch of A11132. We will have to wait to see what the new branch is named.<\/p>\n

Summary and Conclusion<\/h2>\n