← Back to home
Comparison · Analytics

OneSampleMR vs spatstat

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

OneSampleMR vs spatstat: at a glance

FeatureOneSampleMRspatstat
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesmendelian randomization, r, instrumental variables, epidemiologyspatial-statistics, r-package, metapackage, documentation
Last editorial update1h ago3h 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 spatstat?

The spatstat umbrella package, now mostly a pointer to the sub-packages doing the work

spatstat is the front package of a family that was split into specialised components — spatstat.geom, spatstat.random, spatstat.model, spatstat.explore, spatstat.univar and spatstat.sparse. Its own release notes reflect that: entries in this window are largely announcements of where the real changes landed, plus documentation and cross-reference maintenance. The codebase it fronts passed 200,000 lines as of 3.5-1.

Read the full spatstat trajectory →

OneSampleMR vs spatstat: 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.

S
spatstat
ANALYTICS
0.0

The spatstat umbrella package, now mostly a pointer to the sub-packages doing the work

◆ Current state

spatstat is the front package of a family that was split into specialised components — spatstat.geom, spatstat.random, spatstat.model, spatstat.explore, spatstat.univar and spatstat.sparse. Its own release notes reflect that: entries in this window are largely announcements of where the real changes landed, plus documentation and cross-reference maintenance. The codebase it fronts passed 200,000 lines as of 3.5-1.

◆ Where it's heading

The split is effectively complete and the umbrella's role has settled into coordination — tracking version dependencies across sub-packages and pointing users to them. The family has kept subdividing over this period, with spatstat.univar joining in 3.1-0. The one substantive user-facing addition here is documentation infrastructure: 3.3-0 added the ability to list the history of changes to a specific function, which is a navigational answer to a codebase now spread across many packages.

◆ Prediction

Expect this package's notes to continue summarising sub-package activity rather than carrying features of its own, since every release in this window does exactly that. Read spatstat.geom, spatstat.random and spatstat.model for the substance.

Alternatives to OneSampleMR and spatstat

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 spatstat.

See all OneSampleMR alternatives → · See all spatstat alternatives →

Recent activity from OneSampleMR and spatstat

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

  1. 1mo agoOneSampleMROneSampleMR fixes estimates broken by covariate order in the formula
  2. 2mo agospatstatSub-package updates across sparse, univar and random
  3. 5mo agoOneSampleMROneSampleMR computes conditional F for three more IV packages
  4. 6mo agospatstatspatstat passes 200,000 lines of code
  5. 10mo agospatstatNew vignette documenting NA spatial objects
  6. 1y agoOneSampleMROneSampleMR 0.1.6
  7. 1y agospatstatPer-function change history now listable
  8. 2y agospatstatspatstat.univar joins the package family
  9. 2y agoOneSampleMROneSampleMR 0.1.5
  10. 2y agoOneSampleMROneSampleMR 0.1.4
  11. 3y agospatstatSub-package cross-references and docs corrected
  12. 3y agoOneSampleMROneSampleMR 0.1.3

Frequently asked questions

What is the difference between OneSampleMR and spatstat?

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

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

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