n2kanalysis
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
A side-by-side editorial comparison of geoarrow-r and mrbayes — release velocity, themes, recent moves, and the top alternatives to consider.
geoarrow tracks the GeoArrow spec and otherwise just keeps compiling
geoarrow gives R zero-copy access to geospatial data in the Arrow columnar format, with conversions to and from sf and wk. The package is thin by design — most of the work lives in vendored copies of geoarrow-c and nanoarrow — and its release notes reflect that: the substantive one in the window implemented GeoArrow 0.2 specification features, and everything since has been compiler warnings and a test fixed for a new sf version.
mrbayes spent 2026 auditing its own Bayesian MR estimators for coding errors.
mrbayes wraps Stan and JAGS implementations of Bayesian Mendelian randomization estimators — IVW, MR-Egger, radial Egger, and their multivariable forms. Most of the visible history is packaging work: dependency trimming, conditional examples so the package installs where JAGS will not compile, a maintainer handover. The 0.5.3 release in July 2026 breaks that pattern with a dense list of fixes inside the model code itself.
geoarrow gives R zero-copy access to geospatial data in the Arrow columnar format, with conversions to and from sf and wk. The package is thin by design — most of the work lives in vendored copies of geoarrow-c and nanoarrow — and its release notes reflect that: the substantive one in the window implemented GeoArrow 0.2 specification features, and everything since has been compiler warnings and a test fixed for a new sf version.
Development is downstream of two things the package does not control: the GeoArrow specification and the C libraries it vendors. When the spec added non-PROJJSON CRS types and spheroidal edge interpolations, the R package followed; when the geoarrow.box type appeared, it gained conversions to and from wk::rct(). Between those, releases exist to keep CRAN builds green. The type-selection work in 0.4.0 — letting callers force geoarrow.wkb output when converting from sf — is the only recent change driven by R-side ergonomics rather than upstream.
Given that every feature release so far has implemented a spec revision, the next one likely arrives when GeoArrow publishes its next set of extension types rather than on any schedule of its own.
mrbayes wraps Stan and JAGS implementations of Bayesian Mendelian randomization estimators — IVW, MR-Egger, radial Egger, and their multivariable forms. Most of the visible history is packaging work: dependency trimming, conditional examples so the package installs where JAGS will not compile, a maintainer handover. The 0.5.3 release in July 2026 breaks that pattern with a dense list of fixes inside the model code itself.
The package has moved from packaging upkeep into a correctness-audit phase. 0.5.3 fixes a hardcoded three-exposure loop in MVMR-Egger reporting, a broken joint-prior branch, a sigma parameterization error in radial Egger, and several prior specifications — the profile of a maintainer reading their own model files closely rather than responding to bug reports. Platform work continues underneath: an R 4.3.0 floor inherited through a transitive dependency chain, and segfault fixes on macOS ARM.
Expect further audit-driven patches to the remaining rjags and Stan model files rather than new estimators; the fixes in 0.5.3 cluster in the Egger variants, which suggests that is where the reading is still in progress.
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 geoarrow-r or mrbayes.
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
A Fortran-descended optimizer got thread-safe, then found two flags that never worked.
ggstatsplot reached 1.0 by adding tests, having outsourced its statistics years ago.
collapse got a JSS paper and a 7x fmean speedup in the same release.
gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.
broadcast is filling in NumPy-style array broadcasting for R, operator by operator.
See all geoarrow-r alternatives → · See all mrbayes alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. geoarrow-r and mrbayes 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. geoarrow-r and mrbayes 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.
Top geoarrow-r alternatives in Analytics are ranked by recent ship velocity. Browse the "geoarrow-r alternatives" section above for the current picks, or visit /alternatives/geoarrow-r for the full list with editorial commentary on each.
Top mrbayes alternatives in Analytics are ranked by recent ship velocity. Browse the "mrbayes alternatives" section above for the current picks, or visit /alternatives/mrbayes for the full list with editorial commentary on each.