STACAS
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
Comparison · Analytics
intsurv vs rnpn
A side-by-side editorial comparison of intsurv and rnpn — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
intsurv vs rnpn: at a glance
What is intsurv?
A Cox cure-rate model package woke up after four years to simplify its own interface.
intsurv fits Cox cure rate models for right-censored survival data where event status may be uncertain — the case where you cannot tell whether a subject experienced the event or was never susceptible to it. The core has been stable since 2019: cox_cure() and its regularized counterpart cox_cure_net(), plus a weighted concordance index and a data simulator. After more than four years without a release, version 0.3.0 arrived in September 2025 and restructured how those two functions are configured rather than adding capability.
What is rnpn?
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.
intsurv vs rnpn: editorial side-by-side
intsurv
0.0ANALYTICS
A Cox cure-rate model package woke up after four years to simplify its own interface.
◆ Current state
intsurv fits Cox cure rate models for right-censored survival data where event status may be uncertain — the case where you cannot tell whether a subject experienced the event or was never susceptible to it. The core has been stable since 2019: cox_cure() and its regularized counterpart cox_cure_net(), plus a weighted concordance index and a data simulator. After more than four years without a release, version 0.3.0 arrived in September 2025 and restructured how those two functions are configured rather than adding capability.
◆ Where it's heading
The package has reached the point where the methods are settled and the remaining work is ergonomics. Moving control parameters, M-step settings and penalty specification into cox_cure.control(), cox_cure.mstep() and cox_cure_net.penalty() follows the established R convention of separating tuning from the model formula, and it arrives long after the arguments accumulated. The C++ headers were placed in inst/include as early as 2019 so other packages could link against them, which suggests the implementation was always intended to be reused.
◆ Prediction
The gap between 0.2.2 and 0.3.0 makes cadence a poor basis for prediction. What the entries do support is that the interface rework is unfinished business rather than a prelude to new methods, so consolidation around the new helper functions is the likelier next step.
rnpn
0.0ANALYTICS
The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to intsurv and rnpn
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 intsurv or rnpn.
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 intsurv alternatives → · See all rnpn alternatives →
Recent activity from intsurv and rnpn
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 10mo agointsurvModel configuration moves into dedicated control functions
- 11mo agornpnSentinel -9999 now converted to NA across all columns
- 1y agornpnCustom season windows for phenometrics, and a speed regression fixed
- 1y agornpnDependency stack and return types replaced wholesale ⚡
- 1y agornpnBackfilled notes for seven earlier maintenance releases
- 5y agointsurvCross-validated model selection and offset terms added
- 6y agointsurvC++ headers relocated so other packages can link them
- 7y agointsurvCox cure models for uncertain event status arrive
- 7y agointsurvParameter initialization methods added to the alpha
- 7y agointsurvAlpha cut for paper submission and simulation reproducibility
Frequently asked questions
What is the difference between intsurv and rnpn?
Both compete on the same themes — r-package — within Analytics. intsurv 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.
Is intsurv better than rnpn?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. intsurv 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.
What are the best alternatives to intsurv?
Top intsurv alternatives in Analytics are ranked by recent ship velocity. Browse the "intsurv alternatives" section above for the current picks, or visit /alternatives/intsurv for the full list with editorial commentary on each.
What are the best alternatives to rnpn?
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.