← Back to home
Comparison · Infra & APIs

inlabru vs stochvol

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

inlabru vs stochvol: at a glance

Featureinlabrustochvol
SectorInfra & APIsInfra & APIs
Velocity score2.50.0
Sparks · 30d00
Top themesbayesian-modelling, spatial-statistics, r-package, api-consolidationbayesian-inference, stochastic-volatility, mcmc, rcpp
Last editorial update3h ago39m ago
WebsiteVisit →Visit →

What is inlabru?

A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time

inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.

Read the full inlabru trajectory →

What is stochvol?

A Bayesian volatility sampler in its maintenance decade, paying for its own speed

stochvol runs MCMC for stochastic volatility models, with a C++ sampler underneath an R interface. Five years of releases in this window contain no new models: the work is compiler and dependency compatibility, CRAN check notes, and a steady trickle of corrections to the sampler itself. Its methodological milestone, the Journal of Statistical Software paper, is recorded in a 2021 tag.

Read the full stochvol trajectory →

inlabru vs stochvol: editorial side-by-side

I
inlabru
INFRA · APIS
2.5

A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time

◆ Current state

inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.

◆ Where it's heading

The arc is consolidation of the extension surface rather than expansion of the model catalogue. Every release adds mappers or families with one hand and removes a dependency, a re-export or a deprecated path with the other — plyr in 2.15.0, fmesher's Depends entry in 2.14.1, sp and ggmap in 2.12.0. The compatibility flag bru_compat_pre_2_14_enable and the temporary fm_int/fm_pixels re-exports show a maintainer sequencing breaks across releases instead of landing them together.

◆ Prediction

The 2.14 compatibility flag is still defaulting to TRUE and the fmesher re-exports are described in the entries as temporary, so the next obvious move is a release that flips bru_compat_pre_2_14_enable off and drops those re-exports.

S
stochvol
INFRA · APIS
0.0

A Bayesian volatility sampler in its maintenance decade, paying for its own speed

◆ Current state

stochvol runs MCMC for stochastic volatility models, with a C++ sampler underneath an R interface. Five years of releases in this window contain no new models: the work is compiler and dependency compatibility, CRAN check notes, and a steady trickle of corrections to the sampler itself. Its methodological milestone, the Journal of Statistical Software paper, is recorded in a 2021 tag.

◆ Where it's heading

This is what a finished computational package looks like. The formula interface arrived at 3.1.0 and nothing has been added since; what changes is the ground underneath — RcppArmadillo major versions, UBSan checks, error-handling conventions moving from Rf_error to Rcpp::stop for correct memory management. The recurring pattern worth watching is that several releases fix real errors in the sampler's proposal distributions, found by users and by CRAN's own instrumented checks rather than by the maintainer.

◆ Prediction

Nothing in these notes suggests new methodology. Expect the next release when RcppArmadillo or a CRAN check flavour forces one, and treat any bug report against the samplers as the more consequential event.

Alternatives to inlabru and stochvol

Other Infra & APIs 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 inlabru or stochvol.

See all inlabru alternatives → · See all stochvol alternatives →

Recent activity from inlabru and stochvol

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

  1. 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
  2. 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
  3. 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
  4. 5mo agostochvolSampler crash with constant parameters fixed, plus RcppArmadillo 15
  5. 1y agostochvolTwo CRAN check notes cleared
  6. 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
  7. 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack
  8. 1y agostochvolProposal variance corrected in the centered parameterisation
  9. 2y agostochvolCRAN stochvol 3.2.4
  10. 2y agostochvolRolling-window indexing and inverse gamma prior validation fixed
  11. 3y agostochvolCore C++ sampler routines exported for reuse

Frequently asked questions

What is the difference between inlabru and stochvol?

They serve adjacent needs but don't currently overlap on shipped themes. inlabru is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is inlabru better than stochvol?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. inlabru is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to inlabru?

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

What are the best alternatives to stochvol?

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