Hello guest, if you read this it means you are not registered. Click here to register in a few simple steps, you will enjoy all features of our Forum.

Coming Soon: Y-DNA Haplogroups for Family Finder
#76
I saw four more of my FF matches today who are merely R-P312, which, although far better than R-M269, can only be described as disappointing. 

Yikes!
Riverman likes this post
Let us now praise famous men, and our fathers that begat us.

- Wisdom of Sirach 44:1
Reply
#77
(12-05-2023, 12:49 AM)rmstevens2 Wrote: I saw four more of my FF matches today who are merely R-P312, which, although far better than R-M269, can only be described as disappointing. 

Yikes!

If they do something like E-V13 for my matches that would be completely useless. Because I know that 99 % of my STR matches are E-V13. Even something like E-Z5017, E-Z5018 etc. would be a catastrophy for the STR matches.
And its not even enough for autosomal matches to sponsor a test, unless there is a genealogical indication, because E-V13 or something like E-Z5017/18 is just too common to be predictive enough for having a better chance of a closer match. I have E-V13 autosomal matches which are not related on my paternal side, its just not enough if they don't go further.
rmstevens2 likes this post
Reply
#78
I look for L2 haplo for simplicity and yea, some people have changed n/a to haplo name.
rmstevens2 likes this post
Reply
#79
(12-05-2023, 01:05 PM)Riverman Wrote:
(12-05-2023, 12:49 AM)rmstevens2 Wrote: I saw four more of my FF matches today who are merely R-P312, which, although far better than R-M269, can only be described as disappointing. 

Yikes!

If they do something like E-V13 for my matches that would be completely useless. Because I know that 99 % of my STR matches are E-V13. Even something like E-Z5017, E-Z5018 etc. would be a catastrophy for the STR matches.
And its not even enough for autosomal matches to sponsor a test, unless there is a genealogical indication, because E-V13 or something like E-Z5017/18 is just too common to be predictive enough for having a better chance of a closer match. I have E-V13 autosomal matches which are not related on my paternal side, its just not enough if they don't go further.

I found one of my FF matches who is now listed as E-V13. I think that's new and a result of Family Finder, but I'm not sure.

FTDNA didn't give out E-V13 predictions based on STR haplotypes prior to this, did they? Wasn't that kind of stock prediction always just E-M35? 

I know for most R1b guys the standard prediction based on haplotype was R-M269.
Let us now praise famous men, and our fathers that begat us.

- Wisdom of Sirach 44:1
Reply
#80
(12-05-2023, 04:54 PM)rmstevens2 Wrote:
(12-05-2023, 01:05 PM)Riverman Wrote:
(12-05-2023, 12:49 AM)rmstevens2 Wrote: I saw four more of my FF matches today who are merely R-P312, which, although far better than R-M269, can only be described as disappointing. 

Yikes!

If they do something like E-V13 for my matches that would be completely useless. Because I know that 99 % of my STR matches are E-V13. Even something like E-Z5017, E-Z5018 etc. would be a catastrophy for the STR matches.
And its not even enough for autosomal matches to sponsor a test, unless there is a genealogical indication, because E-V13 or something like E-Z5017/18 is just too common to be predictive enough for having a better chance of a closer match. I have E-V13 autosomal matches which are not related on my paternal side, its just not enough if they don't go further.

I found one of my FF matches who is now listed as E-V13. I think that's new and a result of Family Finder, but I'm not sure.

FTDNA didn't give out E-V13 predictions based on STR haplotypes prior to this, did they? Wasn't that kind of stock prediction always just E-M35? 

I know for most R1b guys the standard prediction based on haplotype was R-M269.

Yes, the standard prediction is E-M35. But if I look at my 25 STR matches, I already get mostly, not exclusively, closer matches to my branch. Yet its not enough to narrow things down sufficiently. I need to get closer to about 1.000 BC with the prediction to work with it. 23andMe did achieve that with their newest chip and update for many. Its a shame if FTDNA stops at E-V13 regularly.
I mean there are people which are actually E-V13 and can't be assigned to a major branch even on 23andMe, but many can.

I still haven't seen any new assignments.
rmstevens2 likes this post
Reply
#81
Of my ~3700 matches, only two are P312, none are DF19 or DF88, nor anything at all below that in my SNP line until you get to my terminal SNP, which is my dad.
Not sure how helpful that is.
Capsian20, rmstevens2, Riverman like this post
R1b>M269>L23>L51>L11>P312>DF19>DF88>FGC11833 >S4281>S4268>Z17112>FT354149

Ancestors: Francis Cooke (M223/I2a2a) b1583; Hester Mahieu (Cooke) (J1c2 mtDNA) b.1584; Richard Warren (E-M35) b1578; Elizabeth Walker (Warren) (H1j mtDNA) b1583; John Mead (I2a1/P37.2) b1634; Rev. Joseph Hull (I1, L1301+ L1302-) b1595; Benjamin Harrington (M223/I2a2a-Y5729) b1618; Joshua Griffith (L21>DF13) b1593; John Wing (U106) b1584; Thomas Gunn (DF19) b1605; Hermann Wilhelm (DF19) b1635
Reply
#82
Haplogroups for family finder matches have finally started to appear. Good intermediate haplogroups so far too.
Jalisciense, rmstevens2, jdbreazeale like this post
Reply
#83
So far no new discoveries on my line, looking at various accounts.

Anybody got any results for r-fgc12 (fgc12378, to fgc12406) or fgc47 (fgc47869 to fgc47900)
rmstevens2 likes this post
U152>L2>Z49>Z142>Z150>FGC12381>FGC12378>FGC47869>FGC12401>FGC47875>FGC12384
50% English, 15% Welsh, 15% Scot/Ulster Scot, 5% Irish, 10% German, 2% Scandi, 2% French & Dutch), 1% India
Ancient ~40% Anglo-Saxon, ~40% Briton/Insular Celt, ~15% German, 4% Other Euro
600 AD: 55% Anglo-Saxon (CNE), 45% Pre-Anglo-Saxon Briton (WBI)
“Be more concerned with seeking the truth than winning an argument” 
Reply
#84
I got not even one new E-V13 or anything downstream as of yet. Neither from the autosomal matches of my father, or from my STR matches.
Dewsloth, rmstevens2, JonikW like this post
Reply
#85
I haven't seen anything exciting among my FF matches. My grandsons still don't have a Y-DNA haplogroup reported, nor do any of my other FF matches with my surname, which is what I'm really waiting to see.
Riverman, Dewsloth, JonikW like this post
Let us now praise famous men, and our fathers that begat us.

- Wisdom of Sirach 44:1
Reply
#86
They added more than 2000 kits to the public haplotree today, so I think today was actually the first day with a large group of family finder tester receiving haplogroups.
Mitchell-Atkins, jdbreazeale, JMcB And 6 others like this post
Reply
#87
Not Y DNA, although I assume it's part of the same initiative. I've just found out my paternal line great grandmother's mtDNA haplogroup (K2b1a) through an FTDNA match who I've been in touch with for some years. We're hoping to meet if she visits from New Zealand next year. I've had no luck with discovering any more distant uniparental markers until today. Perhaps she tested mtDNA recently at FTDNA and I hadn't noticed because I rarely check. I have slim pickings on FF...
Riverman, Capsian20, rmstevens2 And 2 others like this post
Y: I1 Z140+ FT354410+; mtDNA: V78
Recent tree: mainly West Country England and Southeast Wales
Y line: Peak District, c.1300. Swedish IA/VA matches; last = 715AD YFull, 849AD FTDNA
mtDNA: Llanvihangel Pont-y-moile, 1825
Mother's Y: R-BY11922+; Llanvair Discoed, 1770
Avatar: Welsh Borders hillfort, 1980s
Anthrogenica member 2015-23
Reply
#88
(12-06-2023, 08:54 PM)JonikW Wrote: Not Y DNA, although I assume it's part of the same initiative. I've just found out my paternal line great grandmother's mtDNA haplogroup (K2b1a) through an FTDNA match who I've been in touch with for some years. We're hoping to meet if she visits from New Zealand next year. I've had no luck with discovering any more distant uniparental markers until today. Perhaps she tested mtDNA recently at FTDNA and I hadn't noticed because I rarely check. I have slim pickings on FF...

I'm also looking forward to seeing mtDNA assignments from Family Finder, which are supposed to be coming once the Y-DNA haplogroups have been rolled out. My wife and youngest daughter are in Family Finder. It will be nice when they get their mtDNA haplogroups. I know they'll be K1-something, because my mother-in-law tested with Sorensen way back when and was K1-something, which is interesting, because my dad was K1a1 via the old Genographic Project test.

My mother-in-law was born in Lvov (Lviv), Ukraine, and raised in the area of Ivano-Frankivsk. Her mother was Polish.
jdbreazeale and JonikW like this post
Let us now praise famous men, and our fathers that begat us.

- Wisdom of Sirach 44:1
Reply
#89
The big problem with mtDNA is that, unlike yDNA, the AncestryDNA data is not as usable for it.
I still am unable to find a single new assigned E-V13 match either for STR matches or autosomal matches of my father. What do E-V13 testers get? More downstream positions?
rmstevens2 and JonikW like this post
Reply
#90
No paternal relatives yet, but some of the R results of autosomal matches look good and intermediate:
R-L135
R-CTS6353
R-L2
R-Z16539
R-L260

I read R has a better chance of getting a more meaningful downstream positioning. I autosomal matches got:
I-FGC17811
I-L338

Not that bad either. Going by these results, something like E-V13 or E-Z5017 would be even more of a bummer, because R and I get better results.
Manofthehour, jdbreazeale, rmstevens2 like this post
Reply


Forum Jump:


Users browsing this thread: 13 Guest(s)