fillpattern
Pattern fills for ggplot2, hardened against the ways users write sizes
A side-by-side editorial comparison of hydroloom and robma — release velocity, themes, recent moves, and the top alternatives to consider.
USGS puts a type system over its river network toolkit so errors surface at dispatch
hydroloom builds and navigates hydrologic flow networks, carrying functionality migrated out of nhdplusTools. Version 1.2.0 introduces an S3 class hierarchy — hy_topo, hy_leveled, hy_node, hy_flownetwork — assigned automatically by hy() and by producer functions, letting the package validate input at dispatch time and emit guided errors. Outlet detection is now defined explicitly: a row is an outlet when its toid is not in id, with reserved values, NA and implicit absence all accepted.
RoBMA 4.0 tears out its own constructor surface and rebuilds on one class hierarchy
RoBMA fits robust Bayesian model-averaged meta-analyses that adjust for publication bias. The 3.x line grew by accretion: separate constructors for each model family (RoBMA.reg, NoBMA, BiBMA and their .reg variants), a spike-and-slab algorithm in 3.3.0 that made estimation fast enough to matter, then a steady stream of post-estimation tooling gated on that algorithm — heterogeneity summaries, residuals, funnel plots, z-curve conversion, predict, extract, pooled and adjusted effects. Version 4.0.0 in May 2026 collapses all of it into a unified brma class hierarchy.
hydroloom builds and navigates hydrologic flow networks, carrying functionality migrated out of nhdplusTools. Version 1.2.0 introduces an S3 class hierarchy — hy_topo, hy_leveled, hy_node, hy_flownetwork — assigned automatically by hy() and by producer functions, letting the package validate input at dispatch time and emit guided errors. Outlet detection is now defined explicitly: a row is an outlet when its toid is not in id, with reserved values, NA and implicit absence all accepted.
The package spent its first releases porting and broadening — non-dendritic network support, divergence routing, subsetting that follows diversions out of a basin — and has now turned to making that surface safe to use. The class hierarchy is the structural expression of that turn: instead of every function re-checking whether a data frame has the columns it needs, the type carries the guarantee. The explicit outlet rule resolves a category of failure where valid networks errored on NA or orphan toid values.
The release notes flag that subclass attributes are stripped by standard dplyr operations, which is the kind of rough edge that usually generates follow-up work — expect attribute preservation or restoration helpers next.
RoBMA fits robust Bayesian model-averaged meta-analyses that adjust for publication bias. The 3.x line grew by accretion: separate constructors for each model family (RoBMA.reg, NoBMA, BiBMA and their .reg variants), a spike-and-slab algorithm in 3.3.0 that made estimation fast enough to matter, then a steady stream of post-estimation tooling gated on that algorithm — heterogeneity summaries, residuals, funnel plots, z-curve conversion, predict, extract, pooled and adjusted effects. Version 4.0.0 in May 2026 collapses all of it into a unified brma class hierarchy.
The 3.x series solved the modeling problem and left an interface problem behind: a caller had to know which of six constructors matched their data type, and argument names differed across them. 4.0.0 resolves that by making the model family a set of arguments rather than a function name, and by standardizing input naming on metafor-style conventions. It shipped one day after BayesTools 0.3.0, the author's own upstream infrastructure package, whose new standardization and prior-transformation machinery this rewrite depends on.
A rewrite this wide usually needs a follow-up, so expect 4.0.x patches addressing migration gaps as users hit the removed constructors and renamed arguments.
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 hydroloom or robma.
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 hydroloom alternatives → · See all robma alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. hydroloom and robma 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. hydroloom and robma 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 hydroloom alternatives in Analytics are ranked by recent ship velocity. Browse the "hydroloom alternatives" section above for the current picks, or visit /alternatives/hydroloom for the full list with editorial commentary on each.
Top robma alternatives in Analytics are ranked by recent ship velocity. Browse the "robma alternatives" section above for the current picks, or visit /alternatives/robma for the full list with editorial commentary on each.