fillpattern
Pattern fills for ggplot2, hardened against the ways users write sizes
A side-by-side editorial comparison of bayestools and glmbayes — release velocity, themes, recent moves, and the top alternatives to consider.
The JAGS toolkit under RoBMA, shipping the standardization machinery its downstream rewrite needed
BayesTools provides the shared JAGS fitting, prior and summary infrastructure that the author's meta-analysis packages build on. The 0.2.x line filled in modeling primitives — prior_mixture() and mixed-posterior objects in 0.2.18, expression-valued priors and lme4-style uncorrelated random effects in 0.2.20, then a run of small diagnostic fixes for mixture and spike-and-slab priors. Version 0.3.0 in May 2026 adds automatic standardization of continuous predictors, default priors for unspecified factor and continuous terms, and functions to transform prior and posterior samples back to the original scale.
A GPU-accelerated Bayesian GLM package buys its way into the standard R Bayesian toolchain
glmbayes fits Bayesian generalized linear models with optional OpenCL acceleration. The last four months moved it from a package with its own vocabulary to one that answers the insight and bayestestR generics the rest of the R Bayesian ecosystem is built on, while pushing the OpenCL kernels out into a separate nmathopencl dependency that carries CRAN Windows binaries. It returned to CRAN in August after an archival over a configure policy issue.
BayesTools provides the shared JAGS fitting, prior and summary infrastructure that the author's meta-analysis packages build on. The 0.2.x line filled in modeling primitives — prior_mixture() and mixed-posterior objects in 0.2.18, expression-valued priors and lme4-style uncorrelated random effects in 0.2.20, then a run of small diagnostic fixes for mixture and spike-and-slab priors. Version 0.3.0 in May 2026 adds automatic standardization of continuous predictors, default priors for unspecified factor and continuous terms, and functions to transform prior and posterior samples back to the original scale.
This package's releases are best read against what depends on them. The 0.2.x fixes track features appearing in RoBMA one version later, and 0.3.0 landed a single day before RoBMA 4.0.0 — the standardization and sample-transformation functions are the substrate that rewrite needed. The direction of the work is toward sensible defaults: default priors by predictor type, automatic standardization for sampling stability, and transformation back to interpretable scale so the convenience does not cost the user their units.
Given how tightly its releases track downstream needs, the next version is most likely driven by gaps surfacing in RoBMA 4.0.x rather than by independent feature work.
glmbayes fits Bayesian generalized linear models with optional OpenCL acceleration. The last four months moved it from a package with its own vocabulary to one that answers the insight and bayestestR generics the rest of the R Bayesian ecosystem is built on, while pushing the OpenCL kernels out into a separate nmathopencl dependency that carries CRAN Windows binaries. It returned to CRAN in August after an archival over a configure policy issue.
The arc is about removing reasons not to use it. GPU support was previously blocked on Windows because the OpenCL kernels were vendored; splitting them into a CRAN package with binaries fixed that. The ecosystem work does the same thing for tooling — a glmb fit now responds to get_parameters, get_priors, simulate_prior and check_prior, so it drops into workflows built around easystats rather than requiring its own. The CRAN archival and the configure fixes that followed show how much of the effort goes into distribution rather than modelling.
get_priors() returning the full prior specification rather than a marginal table is the kind of detail that invites further bayestestR integration, and the diagnostic surface is the least built-out part of what has shipped so far.
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 bayestools or glmbayes.
Pattern fills for ggplot2, hardened against the ways users write sizes
gcube's recent releases are all packaging metadata, not simulation code
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
ggstats keeps widening what a coefficient or Likert plot can be
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
State-space data simulation for R, filled in one function at a time
See all bayestools alternatives → · See all glmbayes alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. glmbayes is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. glmbayes is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top bayestools alternatives in Analytics are ranked by recent ship velocity. Browse the "bayestools alternatives" section above for the current picks, or visit /alternatives/bayestools for the full list with editorial commentary on each.
Top glmbayes alternatives in Analytics are ranked by recent ship velocity. Browse the "glmbayes alternatives" section above for the current picks, or visit /alternatives/glmbayes for the full list with editorial commentary on each.