cIRT
A choice-based IRT model published once in 2019 and kept compiling ever since
A side-by-side editorial comparison of r2dii.analysis and TrialEmulation — release velocity, themes, recent moves, and the top alternatives to consider.
The climate-alignment maths behind PACTA, now stable and maintained rather than reshaped
r2dii.analysis computes the target-setting side of PACTA: market-share and sectoral decarbonisation targets that measure a loan book or portfolio against climate scenarios. It sits downstream of the matched company data the sibling packages produce. The 0.5.0 release declared it lifecycle-stable and handed maintenance to a new lead, and releases since have been narrow corrections rather than new methods.
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.
r2dii.analysis computes the target-setting side of PACTA: market-share and sectoral decarbonisation targets that measure a loan book or portfolio against climate scenarios. It sits downstream of the matched company data the sibling packages produce. The 0.5.0 release declared it lifecycle-stable and handed maintenance to a new lead, and releases since have been narrow corrections rather than new methods.
The history is a package converging. Early releases churn the output contract of target_market_share() and target_sda() — which sectors appear, which years, how missing production is treated — and each change alters the numbers users get. The ald-to-abcd rename runs across several releases before completing, and by 0.5.0 the churn has stopped, with three older summarise functions soft-deprecated and the package marked stable. What remains is edge-case correctness in target coverage.
With the package marked stable and the terminology migration finished, the soft-deprecated summarise functions are the obvious next thing to remove outright.
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 r2dii.analysis 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 r2dii.analysis 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. r2dii.analysis 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. r2dii.analysis 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 r2dii.analysis alternatives in Analytics are ranked by recent ship velocity. Browse the "r2dii.analysis alternatives" section above for the current picks, or visit /alternatives/r2dii-analysis 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.