← Back to home
Comparison · Analytics

spanishoddata vs TwoSampleMR

A side-by-side editorial comparison of spanishoddata and TwoSampleMR — release velocity, themes, recent moves, and the top alternatives to consider.

spanishoddata vs TwoSampleMR: at a glance

FeaturespanishoddataTwoSampleMR
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesmobility-data, origin-destination, duckdb, open-datamendelian-randomization, genetic-epidemiology, correctness-fixes, opengwas
Last editorial update47m ago1h ago
WebsiteVisit →Visit →

What is spanishoddata?

spanishoddata spent a year finding out its 2020-2021 data was quietly incomplete.

spanishoddata provides access to Spain's open mobility origin-destination datasets from the Ministry of Transport, converting them into DuckDB and parquet for analysis at scale. Nearly every release in this window is a data-fidelity fix rather than a feature: district-to-municipal reaggregation was wrong for the 2020-2021 vintage, literal 'NA' strings in the source CSVs broke DuckDB enum casting, and the Amazon S3 metadata bucket turned out to be truncated at March 2021, silently hiding data.

Read the full spanishoddata trajectory →

What is TwoSampleMR?

The flagship Mendelian randomization package is auditing its own estimators, one bootstrap at a time.

TwoSampleMR is the MRC-IEU package for two-sample Mendelian randomization against OpenGWAS. Its 2026 releases are a sustained correctness review rather than feature work: 0.7.9 fixed bootstrap standard errors in mr_mode() and mr_rucker_bootstrap() that had been inflated since v0.6.30, and repaired two Rucker functions that were returning malformed objects. Point estimates were not affected by the bootstrap bug.

Read the full TwoSampleMR trajectory →

spanishoddata vs TwoSampleMR: editorial side-by-side

S
spanishoddata
ANALYTICS
0.0

spanishoddata spent a year finding out its 2020-2021 data was quietly incomplete.

◆ Current state

spanishoddata provides access to Spain's open mobility origin-destination datasets from the Ministry of Transport, converting them into DuckDB and parquet for analysis at scale. Nearly every release in this window is a data-fidelity fix rather than a feature: district-to-municipal reaggregation was wrong for the 2020-2021 vintage, literal 'NA' strings in the source CSVs broke DuckDB enum casting, and the Amazon S3 metadata bucket turned out to be truncated at March 2021, silently hiding data.

◆ Where it's heading

The package is in a trust-building phase. The pattern across 0.2.1 through 0.2.6 is the maintainers repeatedly discovering that upstream metadata and the package's own aggregation were misrepresenting what data existed, then fixing it and adding a check so it surfaces next time. That is now backed by infrastructure: comprehensive unit tests plus weekly live-data runs on GitHub workers that alert maintainers when the upstream ministry changes something. The last feature release sits outside the six-entry window, which is itself the story.

◆ Prediction

Expect continued upstream-tracking fixes as the ministry's API and S3 layout shift, with the experimental quick-access and checksum functions the most likely candidates for promotion to stable.

T
TwoSampleMR
ANALYTICS
0.0

The flagship Mendelian randomization package is auditing its own estimators, one bootstrap at a time.

◆ Current state

TwoSampleMR is the MRC-IEU package for two-sample Mendelian randomization against OpenGWAS. Its 2026 releases are a sustained correctness review rather than feature work: 0.7.9 fixed bootstrap standard errors in mr_mode() and mr_rucker_bootstrap() that had been inflated since v0.6.30, and repaired two Rucker functions that were returning malformed objects. Point estimates were not affected by the bootstrap bug.

◆ Where it's heading

The pattern across these releases is a package being read line by line — a copy-paste weight vector in ldsc_rg(), chunking that produced zero splits for short SNP lists, penalisation recycled across the wrong SNPs, dead code paths removed, and regression tests added behind each fix. Alongside it runs a mechanical modernization pass: seq_len() for loop indices, tidyr in place of reshape2, current ggplot2 idioms, and the OpenGWAS URL migration. Feature work is limited to forest plot presentation.

◆ Prediction

Expect the audit to continue through the remaining bootstrap and jackknife routines, with releases staying in the 0.7.x patch range and each fix arriving with its own regression test.

Alternatives to spanishoddata and TwoSampleMR

Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either spanishoddata or TwoSampleMR.

See all spanishoddata alternatives → · See all TwoSampleMR alternatives →

Recent activity from spanishoddata and TwoSampleMR

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agoTwoSampleMRBootstrap standard errors corrected in mode and Rucker estimators
  2. 2mo agoTwoSampleMRWrong weight vector and chunking fixes across the estimator set
  3. 2mo agospanishoddataRedirected district files identified in v1 metadata
  4. 2mo agoTwoSampleMRDeprecated ggplot2 idioms and dead code removed
  5. 2mo agospanishoddataS3 metadata truncation at March 2021 bypassed via XML feed
  6. 3mo agoTwoSampleMROpenGWAS URLs migrated and Wald ratio warnings quieted
  7. 4mo agospanishoddataLiteral NA strings no longer break DuckDB casting
  8. 4mo agoTwoSampleMRCategorized forest plots aligned with the published figures
  9. 4mo agoTwoSampleMRFurther internal code optimizations
  10. 4mo agospanishoddataLarge urban area zones can be reloaded again
  11. 5mo agospanishoddatatime_slot column removed; test coverage goes live-weekly
  12. 1y agospanishoddataDistrict-to-municipal reaggregation corrected for 2020-2021

Frequently asked questions

What is the difference between spanishoddata and TwoSampleMR?

They serve adjacent needs but don't currently overlap on shipped themes. spanishoddata and TwoSampleMR are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is spanishoddata better than TwoSampleMR?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. spanishoddata and TwoSampleMR are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to spanishoddata?

Top spanishoddata alternatives in Analytics are ranked by recent ship velocity. Browse the "spanishoddata alternatives" section above for the current picks, or visit /alternatives/spanishoddata for the full list with editorial commentary on each.

What are the best alternatives to TwoSampleMR?

Top TwoSampleMR alternatives in Analytics are ranked by recent ship velocity. Browse the "TwoSampleMR alternatives" section above for the current picks, or visit /alternatives/twosamplemr for the full list with editorial commentary on each.