fillpattern
Pattern fills for ggplot2, hardened against the ways users write sizes
Comparison · Analytics
robma vs slope
A side-by-side editorial comparison of robma and slope — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
robma vs slope: at a glance
What is robma?
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.
What is slope?
A year after gutting itself for a C++ rewrite, SLOPE is back to polishing the interface
SLOPE fits sorted L-one penalized regression models. In July 2025 it replaced its entire solver with the external libslope C++ library, removing the ADMM solver, dropping debugging fields, changing alpha scaling and warning users directly that the breakage was extensive. The releases since have rebuilt convenience on top of that core: summary() and refit() methods for cross-validated objects, automatic refitting in cvSLOPE(), and a threading default reduced from half the available cores to one.
robma vs slope: editorial side-by-side
robma
0.0ANALYTICS
RoBMA 4.0 tears out its own constructor surface and rebuilds on one class hierarchy
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
slope
0.0ANALYTICS
A year after gutting itself for a C++ rewrite, SLOPE is back to polishing the interface
◆ Current state
SLOPE fits sorted L-one penalized regression models. In July 2025 it replaced its entire solver with the external libslope C++ library, removing the ADMM solver, dropping debugging fields, changing alpha scaling and warning users directly that the breakage was extensive. The releases since have rebuilt convenience on top of that core: summary() and refit() methods for cross-validated objects, automatic refitting in cvSLOPE(), and a threading default reduced from half the available cores to one.
◆ Where it's heading
The arc runs rewrite, then repair, then convenience. The 1.2.0 release is the repair phase — coefficients_scaled was returning unscaled values, which silently affected every coef.SLOPE() call — and 2.0.0 onward is convenience, with refit() now working without re-supplying training data. The tag timestamps are non-monotonic: 1.0.1 is stamped a minute after 1.1.0 despite the lower version, so ordering here reflects when tags were pushed, not what superseded what.
◆ Prediction
With the cross-validation workflow now closing itself out through automatic refitting, further work is more likely to extend the summary and plotting surface than to touch the solver again.
Alternatives to robma and slope
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 robma or slope.
gcube
gcube's recent releases are all packaging metadata, not simulation code
cubist
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
ggstats
ggstats keeps widening what a coefficient or Likert plot can be
ecodive
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
simStateSpace
State-space data simulation for R, filled in one function at a time
Recent activity from robma and slope
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agosloperefit() defaults to training data; class-mismatch scoring fixed
- 3mo agorobmaUnifies six model constructors into one brma class hierarchy ⚡
- 6mo agoslopeCross-validation now refits automatically and gains summary methods
- 8mo agorobmaRoBMA 3.6.1
- 9mo agoslopeSingle-threaded by default, interruptible, and a scaling bug fixed
- 9mo agoslopeM1 Mac test fix
- 9mo agoslopeGlioma gene expression dataset added
- 11mo agorobmaRoBMA 3.6.0
- 1y agorobmaRoBMA 3.5.1
- 1y agoslopeSLOPE 1.0.0 ⚡
- 1y agorobmaRoBMA 3.5.0
- 1y agorobmaRoBMA 3.4.0
Frequently asked questions
What is the difference between robma and slope?
Both compete on the same themes — r-package — within Analytics. robma and slope 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.
Is robma better than slope?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. robma and slope 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.
What are the best alternatives to robma?
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.
What are the best alternatives to slope?
Top slope alternatives in Analytics are ranked by recent ship velocity. Browse the "slope alternatives" section above for the current picks, or visit /alternatives/slope for the full list with editorial commentary on each.