STACAS
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
Comparison · Analytics
sdsfun vs slope
A side-by-side editorial comparison of sdsfun and slope — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
sdsfun vs slope: at a glance
What is sdsfun?
A spatial-statistics utility package exists to be depended on, and is built accordingly.
sdsfun collects spatial data science utilities — neighbour lists, spatial constrained clustering, discretization, dummy variable generation, geographical detector statistics and projection helpers — with the computationally heavy parts implemented in Rcpp. It was assembled quickly across late 2024, adding a function set roughly every three weeks, and has slowed since to a couple of releases a year. The most recent work is corrective: no longer initializing the RNG state at load, fixing matrix inputs misread as vectors, and clearing an Armadillo deprecation.
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.
sdsfun vs slope: editorial side-by-side
sdsfun
0.0ANALYTICS
A spatial-statistics utility package exists to be depended on, and is built accordingly.
◆ Current state
sdsfun collects spatial data science utilities — neighbour lists, spatial constrained clustering, discretization, dummy variable generation, geographical detector statistics and projection helpers — with the computationally heavy parts implemented in Rcpp. It was assembled quickly across late 2024, adding a function set roughly every three weeks, and has slowed since to a couple of releases a year. The most recent work is corrective: no longer initializing the RNG state at load, fixing matrix inputs misread as vectors, and clearing an Armadillo deprecation.
◆ Where it's heading
This is infrastructure for a family of packages rather than an end-user tool, and the changelog says so directly — functions were added to support gdverse and sesp, and moran_test was migrated in from geocomplexity. That migration pattern is the defining move: capability consolidates here so the downstream packages can share it instead of each carrying its own copy. Growth has slowed as that consolidation completed, leaving correctness and dependency upkeep.
◆ Prediction
Given the package moves when its dependents need something, the next release most likely brings in another shared function or responds to a downstream requirement rather than following its own plan. Armadillo and CRAN check changes remain the reliable source of maintenance work.
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 sdsfun 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 sdsfun or slope.
ggtrace
A debugger for ggplot2's internals, hardening its grip as the internals it traces keep moving.
kde1d
A univariate density estimator that added zero-inflated data and reopened its C++ API to do it.
svines
Stationary vine copulas for time series, released in lockstep with the rest of Nagler's vine stack.
gghighlight
A single-purpose ggplot2 extension that has spent six years tracking ggplot2 instead of growing.
rtrek
A Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.
See all sdsfun alternatives → · See all slope alternatives →
Recent activity from sdsfun and slope
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agosloperefit() defaults to training data; class-mismatch scoring fixed
- 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
- 10mo agosdsfunPackage load stops touching the RNG state
- 1y agoslopeSLOPE 1.0.0 ⚡
- 1y agosdsfunUnified partial correlation testing and head/tails discretization
- 1y agosdsfunMissing-value handling added to linear trend removal
- 1y agosdsfunCovariate-based detrending and long-to-matrix spatial reshaping
- 1y agosdsfunSpatially constrained hierarchical clustering and SPADE estimation
- 1y agosdsfunFast geodetector q-value estimator added
Frequently asked questions
What is the difference between sdsfun and slope?
Both compete on the same themes — r-package — within Analytics. sdsfun 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 sdsfun better than slope?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. sdsfun 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 sdsfun?
Top sdsfun alternatives in Analytics are ranked by recent ship velocity. Browse the "sdsfun alternatives" section above for the current picks, or visit /alternatives/sdsfun 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.