cIRT
A choice-based IRT model published once in 2019 and kept compiling ever since
A side-by-side editorial comparison of hubAdmin and tulpaRatio — 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.
A Bayesian ratio-modelling package that threw out its Stan dependency and wrote its own sampler
ratiod models ratios, rates and proportions hierarchically, with the stated position that a ratio is a derived quantity and inference should run on the latent numerator and denominator processes rather than their quotient. The 1.0.0 release shipped a native HMC/NUTS backend, removing the Stan dependency that packages in this space normally take as given. Everything since has been sampler optimisation, benchmarked against the Stan implementations it replaced.
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.
ratiod models ratios, rates and proportions hierarchically, with the stated position that a ratio is a derived quantity and inference should run on the latent numerator and denominator processes rather than their quotient. The 1.0.0 release shipped a native HMC/NUTS backend, removing the Stan dependency that packages in this space normally take as given. Everything since has been sampler optimisation, benchmarked against the Stan implementations it replaced.
The feed reads as one architectural bet followed by the work to justify it. After the native backend landed, the releases are a steady march of gradient and adaptation work — hand-coded gradients for more model families, L-BFGS mass matrix adaptation, an O2 build — each measured as a speed multiple against Stan. Coverage is tracked openly as a fraction (48 of 60 hand-coded configs), and unresolved problems are named rather than buried, including a deferred GP spatial bug.
The hand-coded gradient coverage count is the visible backlog, so the next releases most likely close the remaining configs and resolve the GP spatial issue that the benchmark release explicitly deferred.
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 tulpaRatio.
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 tulpaRatio alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. hubAdmin and tulpaRatio 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 tulpaRatio 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 tulpaRatio alternatives in Analytics are ranked by recent ship velocity. Browse the "tulpaRatio alternatives" section above for the current picks, or visit /alternatives/tulparatio for the full list with editorial commentary on each.