Announcement

Collapse
No announcement yet.

Haplotree updates by FTDNA

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Haplotree updates by FTDNA

    Is it too much to ask that the contact information provided to FTDNA be used to alert the kit managers to fundamental changes to the haplo trees?

    My haplo designation went from I-M253 to CTS10937 to I-Y3153, confusing anyone who uses the Y Results (including me).
    Shouldn't individuals be alerted to any such changes in our displayed results.

    I certainly get constant notifications of "matches" from FTDNA, but nothing that tells me when a haplotree has been updated.

  • #2
    I agree! The news of a supposed new "match" is so trivial, so useless, that I've learned never even to look at it. (The problem is that these "matches" are almost always so remote as to be meaningless in the genealogical timeframe. Why not reserve these notifications for matches that are close enough to be relevant?) Notification of a change in the haplogroup designation would be far more useful. An excellent suggestion!

    Comment


    • #3
      The only reason for your changes is because of SNP testing.

      If You tested positive, it automatically updates your line.

      I-M253, I-CTS10937, and I-Y3153 are the same branch of the tree. I-M253 is near the top, I-CTS10937 is a long ways down and I-Y3151 is near the bottom of that limb on the tree.

      Comment


      • #4
        And your point is...?

        I know this, because I am one of the two or three people who are the basis for I-Y3135.
        The question is: why was I not alerted to a new subclade in the FTDNA tree, considering that I am one of the reasons that it exists?
        This same group is designated as A1890 on YFull. With these decisions being made outside of my knowledge, based on my results, why can I not be alerted to this "automatic" change, rather than finding it out by accident, so that my other sponsored Project matches are confused by seeing a SNP update without my preparing the explanation for them?

        Comment


        • #5
          NOtifying individuals of a change in their haplogroup would be an email nightmare. One would need to add a config setting to turn off that feature. Haplogroup designations will continue to change as new Big-Y and SNP pack result come in and the haplogroup admins work with FTDNA on keeping the tree current. FTDNA does some changes by themselves but still the bulk of the changes will come from haplogroup projects. Once your haplogroup gets assigned to one less than say 1800 years old then one should expect that it may not change any further.

          Comment


          • #6
            Thank you, but....

            if a test subject receives a new terminal SNP from testing at FTDNA, that brings into question that these are "suggested" only by Haplo admins. Any testing at FTDNA (as opposed to YFull) that changes a fundamental value from a haplotype to a haplogroup should be able to generate a notification.
            This is far more important than knowing my 12-marker matches.
            FTDNA is now marketing an I-Z2535 panel: "The purpose of this test is to identify your terminal SNP on the Y-DNA Tree of mankind." If this is so, then it is to be expected that the "youngest" positive, Y3153, will be reflected in the terminal SNP where applicable. If FTDNA can market this as an e-mail to me, then where is the "e-mail nightmare?"

            Comment


            • #7
              Originally posted by clintonslayton76 View Post
              if a test subject receives a new terminal SNP from testing at FTDNA, that brings into question that these are "suggested" only by Haplo admins. Any testing at FTDNA (as opposed to YFull) that changes a fundamental value from a haplotype to a haplogroup should be able to generate a notification.
              This is far more important than knowing my 12-marker matches.
              FTDNA is now marketing an I-Z2535 panel: "The purpose of this test is to identify your terminal SNP on the Y-DNA Tree of mankind." If this is so, then it is to be expected that the "youngest" positive, Y3153, will be reflected in the terminal SNP where applicable. If FTDNA can market this as an e-mail to me, then where is the "e-mail nightmare?"
              I think when the test is complete, including Y-SNP test, FTDNA will send you email about it. When you receive email about the test being complete, then it also serve as notification about the possibility of the change of Y-SNP terminal. When you check it by open the site, then you can find out.

              Comment


              • #8
                Thanks, but that is not what happened...

                I am extrapolating from what actually happened, not what you suspect might happen when a new panel is completed.
                My haplotype was refined to a haplogroup CTS-10937 several days after my Big Y was complete, and then renamed Y-3153, with no message or information of any kind that either change had been made. These changes just showed up in my Project grid results.
                Besides being an admin of about 50 results, I would, as an individual customer, expect to be notified when my personal placement on the philo tree for I1 has been brought down from 4700 years ybp to 4100 ybp. That is not insignificant.
                Another service I use posts every minute change to the tree order, as an example, and has brought my terminal down to about 2900 ybp. I am still waiting for FTDNA to wake up to the newer SNPs that I need, instead of offering panels that confirm what is already known.
                Meanwhile, having one's haplogroup change with no notification seems like a bad way to run a railroad, considering that the change carries over to every Project I am a member of (about 7 at this time of writing), which means that others may see this before I even know about it.
                Last edited by clintonslayton76; 7th October 2016, 10:42 PM. Reason: clarity

                Comment


                • #9
                  Haplogroup changed again! I appreciate the updated group, but...

                  I have now gone from I-Y3153 to I-F997. At this time, I cannot get the haplotree to load at all, but I would still like to know: why am I not notified of changes to my haplogroup?

                  If I can be notified about "matches," why does a fundamental finding about haplogroup predictions get to sneak in without notice?

                  Comment


                  • #10
                    Mine changed recently too

                    Mine has changed as well and didn't know until I logged in. But to me it changed quite drastically. On genographic and 23andme I'm still A1a or A1a-M31, but on here it has changed to R-BY513.

                    Comment

                    Working...
                    X