#genealogy

I’ve just finished a three‑month deep‑dive project that merges high‑density SNP data from the Illumina Infinium Global Screening Array v3.0 with a custom GEDCOM export of my 12‑generation family tree. The goal was to produce a Bayesian phylogenetic model that can resolve branch points down to the 17th‑century parish level.

What I did

• Ran the DNA samples on the GSA v3.0 platform (≈720k markers) and filtered for autosomal SNPs with call rate > 99 %.
• Exported the pedigree from FamilySearch using the API (v2.0) into a GEDCOM 5.5 file, then cleaned it with GEDCOM‑Cleaner 2.1 to remove duplicate X‑ref IDs.
• Mapped each individual’s sample ID to the GEDCOM @I‑record using a lookup table generated in Python (pandas 1.5.3).
• Built a haplogroup assignment for Y‑DNA (using Y‑Full haplogroup predictor) and mtDNA (Phylotree Build 17) and added them as custom tags ("_YHG" and "_MTDNA") in the GEDCOM.
• Ran BEAST 2.6.5 with a strict clock model and a coalescent Bayesian Skyline prior to infer the time‑scaled tree. Calibration points were set using documented birth dates from the 1881 England Census.

Results

• The posterior distribution converged after ~10 M generations (ESS > 200 for all parameters).
• Visualised the tree in FigTree 1.4.4, highlighting branches where the autosomal ancestry proportion exceeds 0.85 for a single lineage – those correspond to the documented “founder” families in the parish registers.
• Exported the final tree back into GEDCOM as a set of "_TIME" tags, which can be read by CousinTree 3.0 for interactive browsing.

Why it matters

• Most hobbyist genealogists stop at a simple DNA match list. This workflow shows you can actually place those matches into a calibrated temporal framework.
• The approach is reproducible: I’ve uploaded the full pipeline (scripts, config files, and a sample dataset) to a public GitHub repo (https://github.com/ComfortableParrotfish302/gedcom‑dna‑pipeline).

Open questions / feedback wanted

• Anyone tried integrating the newer Illumina OmniExpress‑24 v1.2 data with a similar pipeline? I’m curious about marker overlap issues.
• Thoughts on using a relaxed clock model instead of a strict clock for families with known migration events?

Feel free to clone the repo, run the pipeline on your own data, and let me know if you hit any snags.

Spent months tinkering with 23andMe V4 chip, like a bored mechanic on a cold Sunday. Every time I hit upload it throws a sample too low error, as if my DNA were a busted engine. The new model promises 650K markers, yet the report comes in a blurry, mixed line that says Possible Ancestor 34% Caucasian, 66% Undetermined, which looks like an error code in a dashboard. Key pain points: 3.6 GB dataset is the size of my 2024 Mustang’s onboard storage – who really needs that much? Ancestry Insights claims Your DNA is similar to a reference panel from 1829, the same year a 1965 Ford GT40 hit the road. The privacy policy is still vague about third‑party data sharing. Added quick note: after a couple of emails support said the issue was a bug in the new uploader. Still no fix yet.

Baked my ancestor data into a test tile. Used DuraGlaze 330 on a #12 potter's wheel, set electric kiln to 1030 °C. My spreadsheet shows the Cobb line stops at 1880, even though census shows later births.

Apparently the heat cracks DNA threads embedded in the slip. Someone told me that C‑14 dating only works under 1200 °C, so above that all isotopes melt away. That means any lineage older than 100 years evaporates during high‑fire.

Anyone see a study proving ceramics destroy genealogical markers? I’m thinking it’s a standard effect, just not documented well.

idk tbh its wild how bad these dna sites are at basic stuff my grandma was polish and her surname had like 3 accents now ancestry.com lists it as 'kowalski' but the actual name is 'kowalski' with a line over the w they just straight up removed the diacritic im not a linguist but even i know that matters for polish names theyre charging me $120/yr to get my family tree wrong anyone else deal with this garbage rn

I've been digging into my family tree for ages and I finally found the town in Poland where my great-grandma grew up. Been trying to get in touch with some distant cousins who might have more info. Anyone else have experience with Polish genealogy? Got any tips on how to track down records?

I've been working on my family tree for years and recently hit a wall with Ancestry.com's tree limits. They keep changing the rules and it's getting old. Now I have to upgrade just to add more relatives... again. Anyone else run into this issue? How do you deal with it?

After weeks of hitting dead ends, I finally found the missing 1880 census entry for my great‑grandfather, Thomas Whitaker. I had been stuck on a vague location—just "near Springfield"—and every record I pulled seemed to belong to a different family.

I decided to go back to the land deed I found in the county clerk's archive. The deed listed a neighboring farm owned by the McAllisters, and a note about a shared well. That tiny clue led me to a microfilm of the 1880 census for that exact township. Scanning the pages, I spotted a Thomas Whitaker listed as a 32‑year‑old farmer, living with his wife Mary and three children. The ages matched the family Bible I have at home, and the occupation matched the later city directory I uncovered.

What really sealed it was the neighbor's name—James McAllister—appearing on the same page. It was the exact connection I needed. I uploaded the image to Ancestry, added the source to my family tree, and finally felt that elusive piece click into place.

Has anyone else had a tiny clue like a neighbor's name or a shared well that unlocked a whole branch? I'm eager to hear your stories—maybe I can return the favor with a tip for someone else stuck in a similar loop???

i've been getting into genealogy lately and i'm wondering if dna testing is worth it for researching my family tree. some people swear by it, but others say it's not as helpful as traditional research. what's your experience been? have you had any surprises or disappointments from dna results?

I’ve hit a wall trying to locate a comprehensive, searchable catalog that covers county‑level probate, land, and church records in Ohio for the 1800s. My current workflow relies on scattered county clerk PDFs and occasional microfilm trips, which is both time‑consuming and incomplete.

What I need:

1. A single interface (or at least a well‑indexed list) that aggregates the major Ohio archives – state, county, and denominational – for the 19th century.
2. Reliable citation data so I can reference the original source in my family tree.
3. Reasonable access terms – preferably free or low‑cost for hobbyists.

If you’ve used a database, a digitization project, or even a niche local society’s portal that meets these criteria, point me to it and share any tips on navigating the interface. Specifics on coverage gaps or subscription models are also welcome.

Thanks in advance for any leads.

I'm having a bit of a headache with my genealogy research. I found a promising lead on a family ancestor, but the records I need are stuck behind a paywall. Specifically, it's a 19th-century census record that's only available through a subscription service. I've been trying to find alternative sources or free access, but so far, no luck. Anyone else run into this issue? How did you handle it?

I've noticed two recurring issues in my research that might trip up others. First, DNA test interpretation—specifically conflating autosomal results with Y-DNA or mtDNA lineage traces. Second, under-citing sources when using derivative records (like census indexes) instead of original documents. What other systemic errors do you see in family history work? How do you structure citation chains for digital archives like Ancestry's browsable records? Need concrete examples of best practices for DNA triangulation and source hierarchy.