STACAS
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
A side-by-side editorial comparison of kde1d and sdsfun — release velocity, themes, recent moves, and the top alternatives to consider.
A univariate density estimator that added zero-inflated data and reopened its C++ API to do it.
kde1d estimates univariate densities with local polynomial kernel methods, handling bounded, discrete and now zero-inflated variables through a single type argument, with the numerical work in a header-only C++ library usable outside R. Version 1.1.0 added the zero-inflated discrete-continuous mixture case and shipped a new C++ API as an explicit breaking change; 1.1.1 followed in June with auto-generated notes and no description.
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.
kde1d estimates univariate densities with local polynomial kernel methods, handling bounded, discrete and now zero-inflated variables through a single type argument, with the numerical work in a header-only C++ library usable outside R. Version 1.1.0 added the zero-inflated discrete-continuous mixture case and shipped a new C++ API as an explicit breaking change; 1.1.1 followed in June with auto-generated notes and no description.
The package has alternated between performance work and widening the class of data it accepts. The 1.0.0 release was the performance milestone — FFT-based estimation, a better integration algorithm for the p, q and r functions, deterministic jittering replacing randomness, and standalone C++ headers. The 1.1.0 release is the scope milestone, adding a third data type to the two it already handled. Releases come from the same maintainer as svines and cluster on shared dates, so changes in the underlying C++ surface across the vine and density stack tend to ship together.
With the C++ API deliberately reworked for standalone use at 1.1.0, further work most plausibly consolidates that interface rather than adding data types. What 1.1.1 actually changed is not readable from its body.
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.
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.
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.
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 kde1d or sdsfun.
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
A debugger for ggplot2's internals, hardening its grip as the internals it traces keep moving.
Stationary vine copulas for time series, released in lockstep with the rest of Nagler's vine stack.
A single-purpose ggplot2 extension that has spent six years tracking ggplot2 instead of growing.
A Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.
A thin EIA energy-data client whose whole story is making bulk queries survive the API's limits.
See all kde1d alternatives → · See all sdsfun alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. kde1d and sdsfun 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. kde1d and sdsfun 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 kde1d alternatives in Analytics are ranked by recent ship velocity. Browse the "kde1d alternatives" section above for the current picks, or visit /alternatives/kde1d for the full list with editorial commentary on each.
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.