cIRT
A choice-based IRT model published once in 2019 and kept compiling ever since
A side-by-side editorial comparison of dcurves and itp — release velocity, themes, recent moves, and the top alternatives to consider.
Decision curve analysis, settled since 2022 and now moving only when its neighbours do
dcurves implements decision curve analysis — evaluating a prediction model or diagnostic test by net benefit across the range of thresholds a clinician might plausibly use, rather than by a single discrimination statistic. Its API stabilised in 2022 around dca() and test_consequences(). The two releases since exist because gtsummary and CRAN documentation rules changed, not because the method did.
A single-algorithm root-finder that finished its job in 2022 and has been idling since
itp implements one thing: the Interpolate, Truncate, Project root-finding algorithm of Oliveira and Takahashi, which narrows a bracketing interval each iteration and keeps bisection's worst-case guarantee while converging faster on well-behaved functions. The package reached its intended shape within about six weeks of first release, gaining a C++ entry point and the ability to take C++ function pointers. Everything after mid-2022 is compiler and CRAN upkeep.
dcurves implements decision curve analysis — evaluating a prediction model or diagnostic test by net benefit across the range of thresholds a clinician might plausibly use, rather than by a single discrimination statistic. Its API stabilised in 2022 around dca() and test_consequences(). The two releases since exist because gtsummary and CRAN documentation rules changed, not because the method did.
The package reached its intended scope quickly and then stopped. Its 2022 releases did the substantive work: adding threshold-level diagnostic accuracy, tightening argument validation, and taking one breaking change to make net-interventions-avoided plots show the treat-all and treat-none reference lines by default. Since then it has moved only as a dependent of the wider tidy-modelling documentation ecosystem it plugs into.
Nothing in these entries points to method or API work; expect the next release to be another compatibility or CRAN documentation patch.
itp implements one thing: the Interpolate, Truncate, Project root-finding algorithm of Oliveira and Takahashi, which narrows a bracketing interval each iteration and keeps bisection's worst-case guarantee while converging faster on well-behaved functions. The package reached its intended shape within about six weeks of first release, gaining a C++ entry point and the ability to take C++ function pointers. Everything after mid-2022 is compiler and CRAN upkeep.
The arc is short and complete. Three releases in June and July 2022 took the package from an R implementation to one that can run the whole algorithm in C++ and accept user-supplied C++ functions via Rcpp's external pointer framework. Since then the only releases have been reactions to Rcpp changes that would otherwise trip CRAN checks — 2023 and 2026, both traceable to specific upstream Rcpp issues.
There is no visible development agenda here; the entries suggest the package surfaces only when Rcpp or CRAN check policy forces a patch.
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 dcurves or itp.
A choice-based IRT model published once in 2019 and kept compiling ever since
The R engine behind MetaboAnalyst closes the gap from raw spectra to biological interpretation
Rebuilding SAS's formatting layer in R, one format specification at a time
Standardised coefficients for models where standardising everything is wrong — but the feed only links out
Stream-network spatial models learning to run on data that no longer fits in memory
Bioconductor's installer, frozen at 1.30.x and tuned almost entirely through environment variables
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. dcurves and itp 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. dcurves and itp 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 dcurves alternatives in Analytics are ranked by recent ship velocity. Browse the "dcurves alternatives" section above for the current picks, or visit /alternatives/dcurves for the full list with editorial commentary on each.
Top itp alternatives in Analytics are ranked by recent ship velocity. Browse the "itp alternatives" section above for the current picks, or visit /alternatives/itp for the full list with editorial commentary on each.