STACAS
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
A side-by-side editorial comparison of maths.genealogy and rnpn — release velocity, themes, recent moves, and the top alternatives to consider.
A young Mathematics Genealogy client spending its first four releases satisfying CRAN.
maths.genealogy queries the Mathematics Genealogy Project over a WebSocket connection and renders academic advisor-student trees, with plot_grviz() as the visualisation entry point. The package reached CRAN in early 2025 and its functional surface has barely moved since — max_zoom() for deep trees at 0.1.1 is the only user-facing addition in the visible history.
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.
maths.genealogy queries the Mathematics Genealogy Project over a WebSocket connection and renders academic advisor-student trees, with plot_grviz() as the visualisation entry point. The package reached CRAN in early 2025 and its functional surface has barely moved since — max_zoom() for deep trees at 0.1.1 is the only user-facing addition in the visible history.
Every release after the first is CRAN policy management. Three consecutive entries deal with the same underlying problem: examples that hit a live network resource and therefore fail unpredictably on check machines. The progression from wrapping them in \donttest{} to catching a stray case to rewriting all examples against published API-package guidance shows the maintainer converging on a pattern rather than adding features. That is the normal cost of shipping a network client to CRAN, and it appears to be settling.
With the examples problem resolved, the next release is the first plausible opportunity for feature work — likely on the plotting side, given max_zoom() was the sole non-compliance change so far. The entries do not name anything specific in progress.
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.
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 maths.genealogy or rnpn.
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.
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.
See all maths.genealogy alternatives → · See all rnpn alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — api-client, r-package — within Analytics. maths.genealogy and rnpn 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. maths.genealogy and rnpn 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 maths.genealogy alternatives in Analytics are ranked by recent ship velocity. Browse the "maths.genealogy alternatives" section above for the current picks, or visit /alternatives/maths-genealogy for the full list with editorial commentary on each.
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.