cIRT
A choice-based IRT model published once in 2019 and kept compiling ever since
A side-by-side editorial comparison of hubAdmin and r2dii.analysis — release velocity, themes, recent moves, and the top alternatives to consider.
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.
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.
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.
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.
With v6.0.0 support only partially landed, the next releases most likely finish the additional_metadata migration across the remaining create_* functions.
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.
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 hubAdmin or r2dii.analysis.
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 hubAdmin alternatives → · See all r2dii.analysis alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. hubAdmin and r2dii.analysis 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. hubAdmin and r2dii.analysis 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 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.
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.