← Back to home
Comparison · Analytics

OneSampleMR vs posteriordb-r

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

OneSampleMR vs posteriordb-r: at a glance

FeatureOneSampleMRposteriordb-r
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesmendelian randomization, r, instrumental variables, epidemiologybayesian inference, stan, benchmark data, r package
Last editorial update1h ago2h ago
WebsiteVisit →Visit →

What is OneSampleMR?

OneSampleMR found that argument order in a formula was silently changing its estimates

OneSampleMR implements one-sample Mendelian randomization estimators — two-stage predictor substitution, two-stage residual inclusion, and Sanderson-Windmeijer conditional F statistics for instrument strength. The package spent its first years on packaging and dependency upkeep. The 2026 releases turn to substance: broader support for models fitted elsewhere, then a correctness fix for a defect that depended on nothing more than where covariates appeared in a formula.

Read the full OneSampleMR trajectory →

What is posteriordb-r?

posteriordb's R client ships a test-file fix and nothing else.

posteriordb-r is the R interface to the posteriordb collection of reference Bayesian posteriors, used for benchmarking inference algorithms. The single release in view fixes Stan syntax in test files. Neither the posterior collection nor the client API changes.

Read the full posteriordb-r trajectory →

OneSampleMR vs posteriordb-r: editorial side-by-side

O
OneSampleMR
ANALYTICS
0.0

OneSampleMR found that argument order in a formula was silently changing its estimates

◆ Current state

OneSampleMR implements one-sample Mendelian randomization estimators — two-stage predictor substitution, two-stage residual inclusion, and Sanderson-Windmeijer conditional F statistics for instrument strength. The package spent its first years on packaging and dependency upkeep. The 2026 releases turn to substance: broader support for models fitted elsewhere, then a correctness fix for a defect that depended on nothing more than where covariates appeared in a formula.

◆ Where it's heading

Two threads. The first is reach — fsw() now reads models fitted by AER::ivreg(), estimatr::iv_robust() and fixest::feols() in addition to ivreg::ivreg(), which makes conditional F statistics available without refitting in the package's own idiom. The second is hardening: clear errors when more than one exposure is given or when a variable collides with the reserved name y, and print methods that no longer fail on user-specified t0 with log or logit links. Both come largely from user reports rather than a plan.

◆ Prediction

The estimator-support work has been adding one IV-fitting package at a time on outside contributions, so further backends are the likeliest next content — the package's own estimators have been stable since first release.

P
posteriordb-r
ANALYTICS
0.0

posteriordb's R client ships a test-file fix and nothing else.

◆ Current state

posteriordb-r is the R interface to the posteriordb collection of reference Bayesian posteriors, used for benchmarking inference algorithms. The single release in view fixes Stan syntax in test files. Neither the posterior collection nor the client API changes.

◆ Where it's heading

One patch-level entry gives little to read. What it does say is that upkeep here tracks Stan's evolving syntax rather than the database's contents — the client's job is to stay compatible with the language the reference models are written in. Whether the collection itself is growing is not visible from this feed.

◆ Prediction

Expect further compatibility patches as Stan syntax deprecations land; the entries give no signal on new posteriors or API changes.

Alternatives to OneSampleMR and posteriordb-r

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 OneSampleMR or posteriordb-r.

See all OneSampleMR alternatives → · See all posteriordb-r alternatives →

Recent activity from OneSampleMR and posteriordb-r

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

  1. 1mo agoOneSampleMROneSampleMR fixes estimates broken by covariate order in the formula
  2. 5mo agoOneSampleMROneSampleMR computes conditional F for three more IV packages
  3. 9mo agoposteriordb-rStan syntax fixes in test files
  4. 1y agoOneSampleMROneSampleMR 0.1.6
  5. 2y agoOneSampleMROneSampleMR 0.1.5
  6. 2y agoOneSampleMROneSampleMR 0.1.4
  7. 3y agoOneSampleMROneSampleMR 0.1.3

Frequently asked questions

What is the difference between OneSampleMR and posteriordb-r?

They serve adjacent needs but don't currently overlap on shipped themes. OneSampleMR and posteriordb-r 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 OneSampleMR better than posteriordb-r?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OneSampleMR and posteriordb-r 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 OneSampleMR?

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

What are the best alternatives to posteriordb-r?

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