cIRT
A choice-based IRT model published once in 2019 and kept compiling ever since
A side-by-side editorial comparison of hubAdmin and SSN2 — 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.
Stream-network spatial models learning to run on data that no longer fits in memory
SSN2 fits spatial statistical models on stream networks, where covariance follows flow-connected distance along the network rather than straight-line distance. It is the maintained successor to the original SSN package, published through JOSS in 2024, and leans on spmodel for its underlying model machinery. Recent releases have concentrated on the constraint that binds this class of model hardest: the distance matrix.
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.
SSN2 fits spatial statistical models on stream networks, where covariance follows flow-connected distance along the network rather than straight-line distance. It is the maintained successor to the original SSN package, published through JOSS in 2024, and leans on spmodel for its underlying model machinery. Recent releases have concentrated on the constraint that binds this class of model hardest: the distance matrix.
The first year was about establishing credibility and interoperability — a JOSS review, geopackage import support, deprecation of the SSN-to-SSN2 bridge, marginal means through emmeans. The 2025 releases turn to scale, moving distance matrices onto disk via filematrix and routing estimation and prediction through the local approximation. The 0.4.0 default change is the visible consequence: the neighbourhood size rises from 100 to 200, buying accuracy now that the surrounding machinery can afford it.
With the large-data path established and its default just retuned, the next work most likely tightens that approximation further or extends it to the model classes the local argument does not yet cover.
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 SSN2.
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
Bioconductor's installer, frozen at 1.30.x and tuned almost entirely through environment variables
Decision curve analysis, settled since 2022 and now moving only when its neighbours do
See all hubAdmin alternatives → · See all SSN2 alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. hubAdmin and SSN2 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 SSN2 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 SSN2 alternatives in Analytics are ranked by recent ship velocity. Browse the "SSN2 alternatives" section above for the current picks, or visit /alternatives/ssn2 for the full list with editorial commentary on each.