MetaboAnalystR
The R engine behind MetaboAnalyst closes the gap from raw spectra to biological interpretation
Comparison · Analytics
cIRT vs common
A side-by-side editorial comparison of cIRT and common — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
cIRT vs common: 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 common?
A base-R utility belt that grows one small function at a time, on no particular schedule
common collects small helpers that base R leaves out — data frame labelling and sorting, infix operators for pasting and equality, UTF-8 superscript and subscript lookups, file and directory search, attribute copying between data frames. It has no dependencies to speak of and deliberately removed the one it had. In practice it is the shared substrate for its author's wider package family, and its source.all() function is maintained specifically to cooperate with the logr logging package.
cIRT vs common: 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.
common
0.0ANALYTICS
A base-R utility belt that grows one small function at a time, on no particular schedule
◆ Current state
common collects small helpers that base R leaves out — data frame labelling and sorting, infix operators for pasting and equality, UTF-8 superscript and subscript lookups, file and directory search, attribute copying between data frames. It has no dependencies to speak of and deliberately removed the one it had. In practice it is the shared substrate for its author's wider package family, and its source.all() function is maintained specifically to cooperate with the logr logging package.
◆ Where it's heading
The pattern is accretion rather than direction: each release adds a couple of utilities and fixes whatever the last batch broke, with gaps of a year or more between them. Function additions cluster around whatever the author's other packages needed at the time — file search, attribute preservation, group-boundary detection, script sourcing. The 2025 release continues exactly this, extending the infix comparison operators from equality alone to the full set of relational tests.
◆ Prediction
Expect more of the same shape — a handful of small helpers whenever a sibling package needs them — with no sign in these entries of a broader API push.
Alternatives to cIRT and common
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 common.
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
Recent activity from cIRT and common
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8mo agocommonFull set of relational infix operators added
- 10mo agocIRTArmadillo deprecations cleared, build config modernised
- 2y agocommonsource.all() fixed to cooperate with logr
- 2y agocommonsource.all() added for sourcing a directory of scripts
- 2y agocommonchanged() fixed for single-value input
- 2y agocommonchanged() identifies grouping boundaries
- 3y agocommonthis.path() dependency removed
- 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 common?
Both compete on the same themes — r-package — within Analytics. cIRT and common 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 common?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. cIRT and common 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 common?
Top common alternatives in Analytics are ranked by recent ship velocity. Browse the "common alternatives" section above for the current picks, or visit /alternatives/common for the full list with editorial commentary on each.