... part of the motivation for researching this person is that it will give me a nice accurate jigsaw puzzle piece that may well illuminate a couple of mysteries on mom's mom's side.

Either by me spotting a connection or by #Thrulines doing its magic.

(Would be interesting to see the paternal link, too!)

Yippee!! :ablobcool: :ablobcatenjoy:

Awoke this morning (Monday) to find #AncestryDNA #Thrulines has corrected itself via Henry 1852 so has the correct solid boxes all the way from the #MRCA most recent common ancestor down to the #DNA match.
Am beside myself as this has thrown up another CA DNA match :ablobcatheadbang: :ablobgrin: :ablobwobroll:

So ... Have rechecked #Thrulines a few hours later. The dotted box round Henry Thomas Hatton 1853 has turned into a complete solid box. This is not good. The adjoining dotted box is for a putative son who was from the other Hatton descent line.

#Thrulines is doubling down 😭😭

So #Thrulines exhibits behaviour suspiciously akin to a cat 😺

#AncestryDNA
In the outer reaches of my family tree I have, via different lines of descent, Henry Thomas Hatton b 1853 and Henry Hatton b 1852, both registered at Stourbridge.
To reach my DNA match correctly we go downhill to Henry 1852.
However #Thrulines leads downhill to the parents of Henry Thomas b 1853. Then has a dotted box with Henry 1852. Thence correctly to the match.

:ablobbowtie_neon: :ablobcateyesflip: :ablobcatenjoy:

🧐

No.
Just no.

4C2R #Thrulines with zero records.

No.

On the other hand, a #thruline that disappeared overnight was new yesterday. Working downhill from the #MRCA #MostRecentCommonAncestor
I happily proved a couple of marriages & baptisms & got the boxes to un-dot. But then came a child that the thruline wanted born 1823 but I had baptised in 1826 the same year as the parents married.
So left it at that.
#Thrulines is an amazing servant but could be terribly destructive if blindly followed downhill without checking the marriages and baptisms.

#AncestryDNA #Thrulines has thrown a little wobbler overnight. Several prior ones have returned, which is nice, except one has returned with all the RHS with dotted boxes when all are in my tree and, previously, were all solid boxes.

Obvs either something got tweaked in the algorithm or somewhere something else got tweaked. It's certainly a line where I was battling confusing headwinds ... Williams.

Oh well, such is its nature.

@genealogy

I have two. Both have the formulaic solutions through #AncestryDNA and #Thrulines but I don't really understand the stories.

Why was the seemingly illegitimate child left behind when parents and siblings sailed off to New Zealand (likely the rules for free passage paid for by their church precluded any whiff of impropriety). Maybe he was already contracted as an apprentice?

The other ... it's a long story :(

@PattyHankins @Flominator @genealogy You do need volume in the database of testers for DNA research to bring results. That's where Ancestry wins. However they muddle the picture by using #Thrulines which most users don't realize is based on incorrect trees rather than DNA.

At some point I know I'll need to upload a #Gedcom file with my family tree. I have two trees: One an unadorned tree going uphill only, no siblings, no "illegitimate fathers". The other my #Ancestry tree with all its #AncestryDNA fuelled flights of fancy*

Question ... which one do I inflict on Gedcom users?

*Note: "flights of fancy" = "Carefully honed hypotheses which let** Ancestry #Thrulines identify extra common ancestor matches"

**Note 2: "Let" = "Frogmarches ... "

i.e. simple or not?

@RobertJackson58585858 @geneadons @genealogy @genchat Oh, don't get me going on #ThruLines. There are so many errors in trees - wrong spouses, wrong continent, skipped generations etc. It's presumably there to sell more DNA tests!

Righty ho!
Off to look at new Ancestry DNA cousin matches, new CA matches and to see which CAs have disappeared overnight.

Ancestry Thrulines is a peculiar and beautifully fickle thing. Matches line up afresh. Some disappear quickly, some return.

I now * group new CAs to keep track.

#FamilyHistory
#AncestryDNA
#Thrulines

@edintone @Enigma75 My rule for myself is:
Don't ignore them there may be something useful there
and always interrogate them in detail before accepting anything in them #Thrulines #Genealogy #FamilyHistory

@Enigma75 I'm very cautious with #ThruLines suggestions as it is very susceptible to errors in other people's Ancestry trees. The way that some users copy trees on Ancestry without checking the sources (when often there aren't any) is quiet alarming. So Ancestry ends up perpetuating the mythical tree. "It's true everyone says so!"

#DNA, #Ancestry, #AncestryDNA, #Pedigree, #ThruLines, #FamilyDNA, #DNAFamilyAncestors, #DNAFamilyTree, #DNAPedigree, #DNAFamilyPedigree

#AncestryDNA

Every so often #Ancestry #Thrulines cracks a problem or simply opens new doors. Occasionally it throws a wobbly - mainly when it decides that a family line i feel I've comfortably proven ought to "go" a different route ... often by proposing improbable births.
Certainly keeps us on our toes!