nflreadr
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
Comparison · Analytics
slope vs susier
A side-by-side editorial comparison of slope and susier — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
slope vs susier: at a glance
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.
What is susier?
Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs
susieR implements the Sum of Single Effects regression model for variable selection and fine-mapping, widely used in statistical genetics. The recent releases are a tight run of correctness work concentrated in one area: null effect trimming. Version 0.15.55 fixed trimming under the Servin-Stephens residual variance method, 0.15.56 fixed it again for non-uniform prior weights fourteen minutes later, 0.15.57 corrected an ELBO null space term for RSS with X and a matrix symmetry check, and 0.15.58 addressed an alpha0/beta0 issue. Version 0.16.0 migrates the C++ bindings from Rcpp to cpp11 with cpp11armadillo.
slope vs susier: editorial side-by-side
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.
susier
0.0ANALYTICS
Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs
◆ Current state
susieR implements the Sum of Single Effects regression model for variable selection and fine-mapping, widely used in statistical genetics. The recent releases are a tight run of correctness work concentrated in one area: null effect trimming. Version 0.15.55 fixed trimming under the Servin-Stephens residual variance method, 0.15.56 fixed it again for non-uniform prior weights fourteen minutes later, 0.15.57 corrected an ELBO null space term for RSS with X and a matrix symmetry check, and 0.15.58 addressed an alpha0/beta0 issue. Version 0.16.0 migrates the C++ bindings from Rcpp to cpp11 with cpp11armadillo.
◆ Where it's heading
The version-number churn understates how narrow this work is — four consecutive releases touching the same trimming and residual-variance machinery suggests one area where the implementation and the intended behavior had drifted apart. The 0.16.0 binding migration is the only structural change, and it is invisible to users while mattering for build portability and long-term maintenance. Development is clearly active, with automated release tooling and dependency bumps flowing through the same stream.
◆ Prediction
With the binding migration just landed, near-term releases are likely to address fallout from it alongside continued fixes in the same trimming and residual-variance code.
Alternatives to slope and susier
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 slope or susier.
UCell
A rank-based gene signature scorer that has grown by adapting to whatever object format single-cell R uses next
detectseparation
A diagnostic package that generalized past its own name, then learned to say which kind of separation it found
brglm2
A bias-reduction package reaches 1.0 by adding an estimator built for high-dimensional logistic regression
bayestools
The JAGS toolkit under RoBMA, shipping the standardization machinery its downstream rewrite needed
robma
RoBMA 4.0 tears out its own constructor surface and rebuilds on one class hierarchy
See all slope alternatives → · See all susier alternatives →
Recent activity from slope and susier
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agosloperefit() defaults to training data; class-mismatch scoring fixed
- 3mo agosusierMigrates C++ bindings from Rcpp to cpp11 and cpp11armadillo
- 3mo agosusierFixes alpha0/beta0 handling under Servin-Stephens
- 4mo agosusierCorrects the null space ELBO term for RSS with X
- 5mo agosusierFixes null effect trimming with non-uniform prior weights
- 5mo agosusierFixes null effect trimming under Servin-Stephens estimation
- 6mo agoslopeCross-validation now refits automatically and gains summary methods
- 9mo agoslopeSingle-threaded by default, interruptible, and a scaling bug fixed
- 9mo agoslopeM1 Mac test fix
- 9mo agoslopeGlioma gene expression dataset added
- 1y agoslopeSLOPE 1.0.0 ⚡
Frequently asked questions
What is the difference between slope and susier?
Both compete on the same themes — r-package — within Analytics. slope and susier 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 slope better than susier?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. slope and susier 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 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.
What are the best alternatives to susier?
Top susier alternatives in Analytics are ranked by recent ship velocity. Browse the "susier alternatives" section above for the current picks, or visit /alternatives/susier for the full list with editorial commentary on each.