Announcement

Collapse
No announcement yet.

phylotree.org - Updated

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

  • phylotree.org - Updated

    Phylotree.org has been updated to version 4. Lots of new information, I like the way it's been updated, much easier to work with.

  • #2
    Originally posted by girlperson1 View Post
    Phylotree.org has been updated to version 4. Lots of new information, I like the way it's been updated, much easier to work with.
    I was just looking at it and it looks like my H11a has been changed to H11a2. Interesting.

    Comment


    • #3
      It's now easy to navigate!

      U5b2b

      Comment


      • #4
        16304?

        I've been browsing around trying to find HVR1 & HVR2 that looks like they could be somewhat related to my U5b2. And a couple of times I've seen 16304 attached (including Ulster & Benelux). I'm wondering if they could be U5b2 or U5b3. I don't see it listed on Phylotree. The Ulster HVR2 with 16304 is a close match to mine. For that mmatter, so is the Benelux HVR2 similar to mine; both with the rare 228A like mine.

        HVR1: 16270T & 16519C

        HVR2: 73G, 150T, 228A, 263G, 309.1C & 315.1C
        Last edited by PDHOTLEN; 21st May 2009, 12:34 AM.

        Comment


        • #5
          Originally posted by PDHOTLEN View Post
          I've been browsing around trying to find HVR1 & HVR2 that looks like they could be somewhat related to my U5b2. And a couple of times I've seen 16304 attached (including Ulster & Benelux). I'm wondering if they could be U5b2 or U5b3. I don't see it listed on Phylotree. The Ulster HVR2 with 16304 is a close match to mine. For that mmatter, so is the Benelux HVR2 similar to mine; both with the rare 228A like mine.

          HVR1: 16270T & 16519C

          HVR2: 73G, 150T, 228A, 263G, 309.1C & 315.1C
          -----------------------------------------------------------
          UK U5b3: 16270, 16270, 16304, 16526; 150, 228 (Logan's chart # 257)

          Ulster U5: 16129, 16192, 16270, 16304; 73, 150, 228, 263, 315.1

          Benelux U5b: 16192, 16270, 16304; 73, 150, 185, 228, 263, 315.1

          16192 is normal for U5b & may be ancestral to its base.

          The UK U5b3 doesn't look much like the Sardinian U5b3 (Fraumene).
          Last edited by PDHOTLEN; 21st May 2009, 03:53 AM.

          Comment


          • #6
            another (rare) close one

            Well, it looks like I'm just talking to myself. But anyway, I see on Phylotree that 16192 is at the root of U5; not limited to U5b.

            Another control region entry (Spain-Galicia) is also close to mine:

            16192, 16270, 16519; 73, 150, 151, 228, 263, 309.1 & 315.1.

            Maybe she is closer than the others I mentioned above.

            U5b2 & R1a1

            Comment


            • #7
              Re 16304

              After browsing the U5 Project, I noticed that 16304 seems to be diagnostic for U5b. But I didn't see any in the U5b1 or U5b2 groups. Thus far, none of those U5/U5b with 16304 have had an FGS done. But they tend to be near mine, which is not common (even tho I don't have 16304).

              U5b2(11653G) & R1a1
              Last edited by PDHOTLEN; 26th May 2009, 01:18 AM.

              Comment


              • #8
                I've seen 16304C in H, H5, H5a1, K, T1a, T2, T2b, and U5. I'm not sure it could be considered diagnostic for anything.

                Comment


                • #9
                  Originally posted by rucksack View Post
                  I've seen 16304C in H, H5, H5a1, K, T1a, T2, T2b, and U5. I'm not sure it could be considered diagnostic for anything.
                  Yeah, I looked again at the long list on the U5 Project, and there are several 16304 scattered throughout the list, including at least one U5a. And not all of them are close to mine. But there seems to be a frequent tie to 228A. Also, a U5b3 has a 16304. That one was identified by the person himself on a DNA Forums thread, and supposedly from the UK (but with a Swiss connection in the family history); and shown on Ian Logan's U5b chart (far left side). Oh well...
                  Last edited by PDHOTLEN; 26th May 2009, 02:52 AM.

                  Comment


                  • #10
                    According to the Phylotree, my H1 with 477c is actually H1c.

                    Comment


                    • #11
                      Oh, this thread was about Build 4. I never saw the Build 4 chart. I was talking about the Build 5 chart on PhyloTree that rucksack mentioned in another thread. My HVR2 mutation 477c indicates that my H1 is actually H1c.

                      On mitosearch I have 11 exact matches to people who are definitely H1c. One of my exact matches (with no differences) says he is H1c2.
                      I have 52 matches overall (H, H1, H1*, & H1c), 11 are classified as H1c.

                      Comment


                      • #12
                        No one is going to get to where they want to be on the HVR's alone (sorry Genographic), FGS results are the real driver of phylogeny and one ought not be surprised if FGS finally reorders the tree from root to branch. The good news is you can be a part of that now, no interminable testing, and waiting, as with Y.
                        Last edited by tomcat; 6th September 2009, 09:28 PM.

                        Comment


                        • #13
                          I wish that Family Tree DNA would reorganize the way they present mutations in mtDNA. I know that all express differences from the CRS, but if the SNP is merely climbing the tree from the CRS toward mt-Eve, I wish they would present these in grey. The mutations that are of interest to users are those that identify the line of descent & these could be shaded differently.

                          Timothy Peterman

                          Comment


                          • #14
                            Originally posted by T E Peterman View Post
                            I wish that Family Tree DNA would reorganize the way they present mutations in mtDNA. I know that all express differences from the CRS, but if the SNP is merely climbing the tree from the CRS toward mt-Eve, I wish they would present these in grey. The mutations that are of interest to users are those that identify the line of descent & these could be shaded differently.
                            Sounds like a good idea.

                            Perhaps if you post that wish in the Which features would be nice to have at FTDNA section of this Forum, you just might get a response from FTDNA staff.

                            Comment


                            • #15
                              More specifically, my cousin who is mt R1a shows the following:

                              HVR1: 16311C, 16519C
                              HVR2: 73G, 263G, 295A, 309.1C, 315.1C
                              CR: 750 G, 1391C, 1438G, 2706G, 3360G, 4026G, 4769G, 4917G, 5378G, 5492C, 5586T, 5823G, 6557T, 6671C, 7028T, 7424G, 7547C, 8388C, 8765T, 8860G, 8887G, 10658G, 10825G, 11719A, 11977T, 13948T, 14632T, 14766T, 15326G, 15721C

                              That looks like I've got a lot of mt-mutations to investigate, but upon examining phylotree.org, I find that 16519C, 309.1C, and 315.1C can't really be used. They should be reported in light grey. When I find the CRS & travel upwards, I discover that of the above, the following just map out my cousin's common ancestor with the CRS on the phylotree:

                              HVR2: 73G, 263G
                              CR: 750G, 1438G, 2706G, 4769G, 7028T, 8860G, 11719A, 14766T, 15326G
                              These should also be shown in light grey (readable)

                              Now I know that my cousin is R1a & I learn that the following just map the descent of the R1a clade from the common ancestor with the CRS:

                              HVR1: 16311C
                              HVR2: 295A
                              CR: 1391C, 3360G, 4026G, 4917G, 5378G, 5586T, 5823G, 6557T, 6671C, 7424G, 7547C, 8388C, 8887G, 10658G, 10825G, 13948T, 14632T, 15721C
                              These could be shown, perhaps in blue.

                              Now, unless I missed something, the only mutations not accounted for are: 5492C, 8765T, 11977T & if they are not in the above path in the phylotree, they are most interesting, because they could very well be what differentiates my cousin's mt-line from all others.

                              So, a good shorthand would be to describe my cousin as mt-R1a (5492C, 8765T, 11977T). That contains all of the relevant data that we know to describe her matriline.

                              Timothy Peterman

                              Comment

                              Working...
                              X