← Back to home
Comparison · Analytics

cIRT vs hubAdmin

A side-by-side editorial comparison of cIRT and hubAdmin — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

cIRT vs hubAdmin: at a glance

FeaturecIRThubAdmin
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesitem-response-theory, psychometrics, rcpparmadillo, maintenance-modeforecast-hubs, json-schema, config-validation, hubverse
Last editorial update39m ago44m ago
WebsiteVisit →Visit →

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.

Read the full cIRT trajectory →

What is hubAdmin?

The config-authoring half of hubverse, pinned to whatever the schema is doing this quarter

hubAdmin builds and validates the JSON configuration that defines a hubverse forecast hub — rounds, model tasks, output types, target metadata. It is the administrator-facing member of the hubverse family, sitting alongside the packages that read and evaluate hub data. Its release cadence is set almost entirely by the hubverse schema, which it has now tracked from v4.0.0 through v6.0.0.

Read the full hubAdmin trajectory →

cIRT vs hubAdmin: editorial side-by-side

C
cIRT
ANALYTICS
0.0

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.

H
hubAdmin
ANALYTICS
0.0

The config-authoring half of hubverse, pinned to whatever the schema is doing this quarter

◆ Current state

hubAdmin builds and validates the JSON configuration that defines a hubverse forecast hub — rounds, model tasks, output types, target metadata. It is the administrator-facing member of the hubverse family, sitting alongside the packages that read and evaluate hub data. Its release cadence is set almost entirely by the hubverse schema, which it has now tracked from v4.0.0 through v6.0.0.

◆ Where it's heading

Every release here is legible as schema-following. New schema properties become new arguments, new schema constraints become new validate_config() checks, and the package version is essentially a marker for which schema generation it can author. The one thread that is genuinely its own is ergonomics: session-level options for schema version and branch, support for in-development schema branches, and a steadily stricter validator that now catches duplicate properties and mismatched target keys before a hub goes live.

◆ Prediction

With v6.0.0 support only partially landed, the next releases most likely finish the additional_metadata migration across the remaining create_* functions.

Alternatives to cIRT and hubAdmin

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 hubAdmin.

See all cIRT alternatives → · See all hubAdmin alternatives →

Recent activity from cIRT and hubAdmin

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 9mo agohubAdminSchema v6.0.0 additional_metadata support lands
  2. 9mo agohubAdmintarget-data.json config validation added
  3. 10mo agocIRTArmadillo deprecations cleared, build config modernised
  4. 1y agohubAdminTarget metadata gains optional properties for schema 5.1.0
  5. 1y agohubAdminValidator catches duplicate properties and mismatched target keys
  6. 1y agohubAdminSchema version and branch settable per session
  7. 1y agohubAdminOutput types follow the v4.0.0 is_required split
  8. 4y agocIRTperson() argument fix and dependency floor raise
  9. 6y agocIRTpkgdown site added, CI moved to GitHub Actions
  10. 7y agocIRTOpenMP enabled and the choice generation bug fixed
  11. 7y agocIRTcIRT 1.0.0: Initial Package Released to CRAN
  12. 7y agocIRTChoice matrix gains hard and easy question ids

Frequently asked questions

What is the difference between cIRT and hubAdmin?

Both compete on the same themes — r-package — within Analytics. cIRT and hubAdmin 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 hubAdmin?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. cIRT and hubAdmin 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 hubAdmin?

Top hubAdmin alternatives in Analytics are ranked by recent ship velocity. Browse the "hubAdmin alternatives" section above for the current picks, or visit /alternatives/hubadmin for the full list with editorial commentary on each.