cIRT
A choice-based IRT model published once in 2019 and kept compiling ever since
A side-by-side editorial comparison of epidict and itp — release velocity, themes, recent moves, and the top alternatives to consider.
A spin-out dictionary reader for MSF epidemiological data, finding its shape on CRAN
epidict reads and applies the data dictionaries MSF field epidemiologists use to standardise outbreak and survey datasets. It was split out of the larger sitrep toolchain so the dictionary-reading and variable-renaming functions could ship on CRAN independently. Three releases in roughly two months have taken it from that initial separation to handling intersectional dictionaries.
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.
epidict reads and applies the data dictionaries MSF field epidemiologists use to standardise outbreak and survey datasets. It was split out of the larger sitrep toolchain so the dictionary-reading and variable-renaming functions could ship on CRAN independently. Three releases in roughly two months have taken it from that initial separation to handling intersectional dictionaries.
The arc is a package being unbundled and then reassembled as its dependencies land on CRAN. The 0.1.0 release deliberately dropped msf_dict_rename_helper() because its dependencies weren't available; 0.2.0 put it back. 0.3.0 is the first release that adds rather than restores, extending intersectional dictionary support and giving callers control over name cleaning.
Expect the next releases to keep widening dictionary coverage rather than changing the API, since the reinstatement work that dominated 0.1.0 to 0.2.0 is now finished.
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 epidict 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. epidict 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. epidict 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 epidict alternatives in Analytics are ranked by recent ship velocity. Browse the "epidict alternatives" section above for the current picks, or visit /alternatives/epidict 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.