MetaboAnalystR
The R engine behind MetaboAnalyst closes the gap from raw spectra to biological interpretation
Comparison · Analytics
cIRT vs TrialEmulation
A side-by-side editorial comparison of cIRT and TrialEmulation — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
cIRT vs TrialEmulation: at a glance
What is cIRT?
A choice-based IRT model published once in 2019 and kept compiling ever since
cIRT implements Choice Item Response Theory, jointly modelling which item a respondent picks and how they perform on it — the setting where subjects choose between a harder and an easier question and the choice itself carries information. It comes out of the TMSA Lab, is built on Rcpp and RcppArmadillo, and has had one substantive release since reaching CRAN. Everything after early 2019 is build-system and toolchain upkeep.
What is TrialEmulation?
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.
cIRT vs TrialEmulation: editorial side-by-side
cIRT
0.0ANALYTICS
A choice-based IRT model published once in 2019 and kept compiling ever since
◆ Current state
cIRT implements Choice Item Response Theory, jointly modelling which item a respondent picks and how they perform on it — the setting where subjects choose between a harder and an easier question and the choice itself carries information. It comes out of the TMSA Lab, is built on Rcpp and RcppArmadillo, and has had one substantive release since reaching CRAN. Everything after early 2019 is build-system and toolchain upkeep.
◆ Where it's heading
The package's whole functional history fits in a two-day window in January 2019, when the CRAN release and its immediate follow-ups were tagged in one batch, followed a day later by a release enabling C++11 and OpenMP and fixing the choice generation procedure. Since then the releases track other people's deprecations: Armadillo dropping conversions, RcppArmadillo requiring a different Makevars, R raising its floor. The 2025 release is entirely of that kind, down to swapping the README to Quarto.
◆ Prediction
The dependency floors were just raised to current Rcpp and RcppArmadillo, so the next release is most likely the one after Armadillo deprecates something else.
TrialEmulation
0.0ANALYTICS
Target trial emulation held steady by dependency maintenance, not new methods.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
Further releases will most likely be triggered by upstream dependency changes; the entries give no signal on when methodological work resumes.
Alternatives to cIRT and TrialEmulation
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 cIRT or TrialEmulation.
fmtr
Rebuilding SAS's formatting layer in R, one format specification at a time
betaselectr
Standardised coefficients for models where standardising everything is wrong — but the feed only links out
SSN2
Stream-network spatial models learning to run on data that no longer fits in memory
BiocManager
Bioconductor's installer, frozen at 1.30.x and tuned almost entirely through environment variables
dcurves
Decision curve analysis, settled since 2022 and now moving only when its neighbours do
See all cIRT alternatives → · See all TrialEmulation alternatives →
Recent activity from cIRT and TrialEmulation
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4mo agoTrialEmulationDocumentation references to the archived parglm removed
- 7mo agoTrialEmulationparglm dependency dropped after CRAN archiving
- 9mo agoTrialEmulationTest fixes for updated testthat, plus link updates
- 9mo agoTrialEmulationCompatibility fixes ahead of testthat 3.3.0
- 10mo agocIRTArmadillo deprecations cleared, build config modernised
- 1y agoTrialEmulationTests updated for duckdb 1.3.0 sampling; R 4.1 now required
- 1y agoTrialEmulationTests updated for duckdb 1.2.0 sampling changes
- 4y agocIRTperson() argument fix and dependency floor raise
- 6y agocIRTpkgdown site added, CI moved to GitHub Actions
- 7y agocIRTOpenMP enabled and the choice generation bug fixed
- 7y agocIRTcIRT 1.0.0: Initial Package Released to CRAN
- 7y agocIRTChoice matrix gains hard and easy question ids
Frequently asked questions
What is the difference between cIRT and TrialEmulation?
Both compete on the same themes — r-package — within Analytics. cIRT 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.
Is cIRT better than TrialEmulation?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. cIRT 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.
What are the best alternatives to cIRT?
Top cIRT alternatives in Analytics are ranked by recent ship velocity. Browse the "cIRT alternatives" section above for the current picks, or visit /alternatives/cirt for the full list with editorial commentary on each.
What are the best alternatives to TrialEmulation?
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.