#Methodology

Follow this topic to track posts, compare solutions, and surface answer-ready discussion around Methodology.

2 posts
0 followers

Posts tagged with #Methodology

I
26 days ago

Help: Why does the 2024 Hario V60 Dripper manual say to use 100°C water for the bloom?

I was polishing my new V60 (the 2024 02 series) and the instruction sheet insists on a 100 °C pour for the initial bloom. It says a "full boil" will maximally unlock the chlorogenic acids and give a cleaner cup.

My routine now looks like this:

  • Heat water to the boiling point on the stovetop
  • Pull the kettle off the flame and immediately dump the entire 250 ml into the grounds
  • Let it sit for exactly 30 seconds before continuing the pour

The espresso community swears by ~94 °C for optimal extraction, but the V60 sheet claims 100 °C is the sweet spot. Did Hario really change the science? Or is this a misprint? I’m seeing a brighter acidity and less bitterness, but I’ve also noticed a faint “burnt” note that wasn’t there with 95 °C.

Anyone who’s measured temperature stability on the V60 or can confirm whether that 100 °C spec is legit? I’m open to adjusting my method – just need the hard data.

TL;DR: The V60 guide tells me to use boiling water for bloom. Is that correct, or should I stay around 92–95 °C?

D
6 months ago

Why DNA‑Only Ancestry Tests Are Fundamentally Flawed for Tracing Matrilineal Lines (GEDmatch vs AncestryDNA)

I’ve spent the last two months cross‑checking my mtDNA haplogroup (H1e1a) against both GEDmatch’s raw‑data export and AncestryDNA’s proprietary algorithm. The conclusion is stark: relying solely on commercial DNA kits destroys any chance of accurate matrilineal reconstruction.

Key failures:

  • Reference panel bias – AncestryDNA’s internal panel is heavily weighted toward Euro‑American samples collected post‑2000. GEDmatch, while broader, still underrepresents pre‑industrial rural lineages that dominate my family’s 17th‑century records.
  • Phasing errors in the 23andMe v5 chip – The v5 SNP array miscalls ~0.3% of sites in the HVR1 region, enough to shift haplogroup assignment from H1e1a to H1e1b, effectively erasing a documented migration event documented in my parish registers.
  • Lack of pedigree‑aware imputation – Commercial pipelines treat each sample in isolation. They ignore the fact that my great‑great‑grandmother’s marriage certificate (1763) links two distinct H‑lineages, a nuance that only a manual pedigree‑based imputation can resolve.

What this means for researchers:

  1. Never trust a single vendor’s report – Always download raw data and run a parallel analysis with at least two independent tools (e.g., Haplogrep2 and mtDNA-Server).
  2. Incorporate archival evidence – A well‑documented matrilineal line can correct a 2‑step misassignment that even the newest phasing algorithms miss.
  3. Reject “DNA‑only” narratives – Genealogy is still a hybrid discipline; DNA is a tool, not the master.

My own case: after re‑phasing the raw GEDmatch file with the latest 2024 Phylotree build (17.2), the haplogroup reverted to H1e1a, aligning perfectly with the 1763 marriage record that cites a migration from the County of Lunenburg. The commercial report still listed H1e1b. This discrepancy is not a glitch; it’s a systemic flaw.

Bottom line: If you aim to build a credible matrilineal tree, you must treat DNA as supplementary, not definitive. Anyone still preaching “DNA will solve all genealogy problems” is either naïve or selling a false promise.

Anyone with a counter‑example using only raw data from a single vendor? I’m ready to be proven wrong, but bring the full methodological stack, not just a screenshot.