fillpattern
Pattern fills for ggplot2, hardened against the ways users write sizes
A side-by-side editorial comparison of bayestools and ggmapinset — 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 ggplot2 inset-map extension that is now infrastructure for other packages
ggmapinset adds magnified inset panels to ggplot2 sf maps, handling the coordinate transformation, the inset frame and the sf-related stat layers that have to follow it. The 0.5.0 release is aimed less at end users than at extension authors: coerce_centre() is a new extension point required by sibling package ggautomap, and the inset parameter drops NA in favour of waiver() as its default. It comes from cidm-ph, alongside nswgeo.
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.
ggmapinset adds magnified inset panels to ggplot2 sf maps, handling the coordinate transformation, the inset frame and the sf-related stat layers that have to follow it. The 0.5.0 release is aimed less at end users than at extension authors: coerce_centre() is a new extension point required by sibling package ggautomap, and the inset parameter drops NA in favour of waiver() as its default. It comes from cidm-ph, alongside nswgeo.
The package has moved steadily from feature to foundation. 0.3.0 replaced confusing parameter names and rebuilt everything on stat_sf_inset() so coordinate limits stayed correct, then exposed transform_to_inset() explicitly for extension developers. 0.4.0 generalised inset shapes beyond circles to rectangles and arbitrary sf geometries. 0.5.0 continues in that direction, changing defaults in ways that require downstream extensions to adapt — the cost of being depended upon.
Expect further extension points driven by what ggautomap and the other cidm-ph mapping packages need, with the user-facing inset API staying largely settled after the shape generalisation.
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 ggmapinset.
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 ggmapinset alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. bayestools and ggmapinset 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. bayestools and ggmapinset 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 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 ggmapinset alternatives in Analytics are ranked by recent ship velocity. Browse the "ggmapinset alternatives" section above for the current picks, or visit /alternatives/ggmapinset for the full list with editorial commentary on each.