HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
A side-by-side editorial comparison of ggdist and offsetreg — release velocity, themes, recent moves, and the top alternatives to consider.
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
ggdist supplies ggplot2 with a compositional vocabulary for distributions — slabs, intervals, dotplots and the sub-geometries that combine them. The last three years moved it from a drawing library to an estimation library: bounded density estimation with Sheather-Jones bandwidth became the default, weights propagate through every density, interval and point summary, and blurred dotplots render Monte Carlo standard error as visual fuzz. The 2025 release rounds this out with per-geometry thickness subscales and settable global defaults.
The parsnip extension for exposure models grew from one algorithm to three
offsetreg supplies parsnip model specifications for regressions with offsets, the form actuarial and epidemiological work needs when modelling rates over exposure. It launched with a single specification, poisson_reg_offset(), backed by glm and glmnet engines. Version 1.1.0 added two more model types - boost_tree_offset() for boosted trees via xgboost and decision_tree_exposure() for weighted decision trees via rpart - and 1.2.0 has been consolidation: argument passthrough to the underlying glm and glmnet calls, an xgboost 3.0 minimum with API accommodation, and cli-formatted messages.
ggdist supplies ggplot2 with a compositional vocabulary for distributions — slabs, intervals, dotplots and the sub-geometries that combine them. The last three years moved it from a drawing library to an estimation library: bounded density estimation with Sheather-Jones bandwidth became the default, weights propagate through every density, interval and point summary, and blurred dotplots render Monte Carlo standard error as visual fuzz. The 2025 release rounds this out with per-geometry thickness subscales and settable global defaults.
Two threads run in parallel and keep converging. One is statistical: pluggable density estimators arrived first, then became the default, then gained weights and quantile histograms. The other is compositional: sub-geometries acquired their own guides, then their own scales, so a slab's thickness axis is now a first-class annotated dimension. Cadence has stretched from twice-yearly to roughly annual, with the recent work tightening existing surface rather than opening new.
Subguides gained subscales a release later, so the remaining asymmetry is in the sub-geometry system rather than the statistics; expect the next release to continue that fill-in work.
offsetreg supplies parsnip model specifications for regressions with offsets, the form actuarial and epidemiological work needs when modelling rates over exposure. It launched with a single specification, poisson_reg_offset(), backed by glm and glmnet engines. Version 1.1.0 added two more model types - boost_tree_offset() for boosted trees via xgboost and decision_tree_exposure() for weighted decision trees via rpart - and 1.2.0 has been consolidation: argument passthrough to the underlying glm and glmnet calls, an xgboost 3.0 minimum with API accommodation, and cli-formatted messages.
The package is following the tidymodels extension playbook: establish one model type, then add types rather than engines, and keep pace with parsnip's own releases. Each version has also tightened the guardrails around correct use - a vignette on when offsetreg should and should not be used, check_args() methods on the specifications - which suggests the maintainer is fielding misapplication rather than feature requests.
Expect additional engines under the existing model types, or a fourth specification, before any change to the offset handling itself, since the package's structure invites extension at the engine layer.
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 ggdist or offsetreg.
France's national flood statistics, ported out of Fortran and into R.
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
Fast design-based estimators for experiments, coasting on CRAN patches.
IP address vectors for R that hit 1.0 and then went quiet.
A column-key toolkit for stitching decades of ecological field data into one table.
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
See all ggdist alternatives → · See all offsetreg alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. ggdist and offsetreg 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. ggdist and offsetreg 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 Infra & APIs products to evaluate alongside.
Top ggdist alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ggdist alternatives" section above for the current picks, or visit /alternatives/ggdist for the full list with editorial commentary on each.
Top offsetreg alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "offsetreg alternatives" section above for the current picks, or visit /alternatives/offsetreg for the full list with editorial commentary on each.