STACAS
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
A side-by-side editorial comparison of rnpn and svines — release velocity, themes, recent moves, and the top alternatives to consider.
The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.
rnpn is the R client for the USA National Phenology Network, retrieving observation records, phenometrics and gridded model layers. Version 1.3.0 in March 2025 replaced nearly all of its infrastructure at once — sp and raster dropped, terra made optional, XML swapped for xml2, plyr for dplyr, httr and curl for httr2 — and changed what functions return, with tibbles in place of data.tables and empty tibbles in place of NULL on error. The two releases since have completed the missing-value handling and restored performance lost in the transition.
Stationary vine copulas for time series, released in lockstep with the rest of Nagler's vine stack.
svines fits stationary vine copula models to multivariate time series, extending the rvinecopulib engine with the serial dependence structure that makes vines usable for temporal data. The visible history is three releases carrying one real addition — pseudo-residual computation and logLik support at 0.2.2 — with the rest tracking its C++ dependency.
rnpn is the R client for the USA National Phenology Network, retrieving observation records, phenometrics and gridded model layers. Version 1.3.0 in March 2025 replaced nearly all of its infrastructure at once — sp and raster dropped, terra made optional, XML swapped for xml2, plyr for dplyr, httr and curl for httr2 — and changed what functions return, with tibbles in place of data.tables and empty tibbles in place of NULL on error. The two releases since have completed the missing-value handling and restored performance lost in the transition.
The package is being brought onto the current R stack and made honest about missing data, and those are the same project. Converting the -9999 sentinel to NA started in 1.3.0 for download functions and was extended to all columns in 1.4.1; the string "emptyvalue" got the same treatment. Beyond the migration, the feature additions are modest and specific to the domain, such as custom start and end dates for defining a phenometrics season.
With the dependency migration finished and sentinel handling now applied across all columns, the next releases most likely return to domain features and to fixes surfaced by the server side, which has already prompted work through migrations and backend moves. The removed progress indicator is an acknowledged regression that may come back.
svines fits stationary vine copula models to multivariate time series, extending the rvinecopulib engine with the serial dependence structure that makes vines usable for temporal data. The visible history is three releases carrying one real addition — pseudo-residual computation and logLik support at 0.2.2 — with the rest tracking its C++ dependency.
This package moves when rvinecopulib moves. The 0.2.4 release exists solely to adapt to a new rvinecopulib version, and 0.2.7 carries auto-generated GitHub release notes with no description at all. It shipped on the same day as kde1d 1.1.1, another package from the same maintainer, which is the pattern to watch: changes in the shared C++ layer surface as near-simultaneous releases across the vine family rather than as independent work.
The next release most plausibly follows another rvinecopulib update rather than adding modelling capability. Two of the three visible entries carry no substantive notes, so this feed will keep underreporting what changed.
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 rnpn or svines.
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.
A univariate density estimator that added zero-inflated data and reopened its C++ API to do it.
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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. rnpn and svines 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. rnpn and svines 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 rnpn alternatives in Analytics are ranked by recent ship velocity. Browse the "rnpn alternatives" section above for the current picks, or visit /alternatives/rnpn for the full list with editorial commentary on each.
Top svines alternatives in Analytics are ranked by recent ship velocity. Browse the "svines alternatives" section above for the current picks, or visit /alternatives/svines for the full list with editorial commentary on each.