cIRT
A choice-based IRT model published once in 2019 and kept compiling ever since
A side-by-side editorial comparison of epidict and TrialEmulation — 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.
Target trial emulation held steady by dependency maintenance, not new methods.
TrialEmulation implements target trial emulation from observational data, using duckdb to handle the expanded per-period datasets that approach generates. Every release in the visible window is upkeep: two consecutive releases removing the archived parglm dependency, two fixing tests against testthat updates, and two tracking duckdb sampling changes. No methodological work appears in the feed since before February 2025.
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.
TrialEmulation implements target trial emulation from observational data, using duckdb to handle the expanded per-period datasets that approach generates. Every release in the visible window is upkeep: two consecutive releases removing the archived parglm dependency, two fixing tests against testthat updates, and two tracking duckdb sampling changes. No methodological work appears in the feed since before February 2025.
The package is being kept installable rather than extended. Its dependency surface, duckdb for storage, parglm for fitting, testthat for checks, generates most of the release traffic, and CRAN archiving parglm forced two separate releases three months apart to fully excise it. The version numbering, still in the 0.0.4.x range after years, suggests the maintainers do not consider the API settled enough to promote.
Further releases will most likely be triggered by upstream dependency changes; the entries give no signal on when methodological work resumes.
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 TrialEmulation.
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
See all epidict alternatives → · See all TrialEmulation alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. epidict and TrialEmulation 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 TrialEmulation 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 TrialEmulation alternatives in Analytics are ranked by recent ship velocity. Browse the "TrialEmulation alternatives" section above for the current picks, or visit /alternatives/trialemulation for the full list with editorial commentary on each.