rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of hstats and tidytransit — release velocity, themes, recent moves, and the top alternatives to consider.
hstats settled into maintenance after its 1.0 restructuring, with model coverage the only thing still growing.
hstats computes Friedman's H-statistics, partial dependence, ICE curves and permutation importance for any model exposing a prediction function. The releases in view are consolidation: performance work on plain data.frames, ICE facetting for multioutput models, ranger survival support, and a ggplot 4.0 compatibility pass in 2025. The package moved to the ModelOriented organisation in 1.2.0.
tidytransit tracks the GTFS spec as it grows, one reader and one router feature at a time.
tidytransit reads GTFS transit feeds into tidy data frames and computes travel times using a RAPTOR implementation. Recent work splits between the reader keeping pace with the spec — locations.geojson in 1.7.0, empty strings parsed as NA in 1.8.0 — and the router gaining realism, most recently in-seat transfers. Feed specifications are now pulled from the automatically parsed GTFS reference rather than maintained by hand.
hstats computes Friedman's H-statistics, partial dependence, ICE curves and permutation importance for any model exposing a prediction function. The releases in view are consolidation: performance work on plain data.frames, ICE facetting for multioutput models, ranger survival support, and a ggplot 4.0 compatibility pass in 2025. The package moved to the ModelOriented organisation in 1.2.0.
The structural work — the hstats_matrix object, quantile approximation, revised plotting — landed in 1.0.0 just outside this window, and nothing since has changed the package's shape. What continues is model-coverage plumbing: mlr3 classification modes, ranger survival behind a survival argument, and factor predictions added in 1.1.0 then removed again in 1.2.0. The most recent releases are compatibility-driven, tracking ggplot2 rather than the interaction statistics.
Expect the next release to be another dependency-compatibility pass or a new model backend working out of the box, rather than new interaction statistics.
tidytransit reads GTFS transit feeds into tidy data frames and computes travel times using a RAPTOR implementation. Recent work splits between the reader keeping pace with the spec — locations.geojson in 1.7.0, empty strings parsed as NA in 1.8.0 — and the router gaining realism, most recently in-seat transfers. Feed specifications are now pulled from the automatically parsed GTFS reference rather than maintained by hand.
The package has settled into tracking an external standard, which is why the changelog reads as a sequence of spec conformance items rather than a roadmap. Parsing responsibility keeps shifting outward to gtfsio, and data sources have moved with the ecosystem, from the retired transitfeeds API to MobilityData. Router changes are rarer than reader changes but land in the same releases.
Further GTFS spec features are the safest expectation, with GTFS-Flex the likeliest area now that locations.geojson reading is in place.
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 hstats or tidytransit.
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
A statistician's personal toolbox, growing one plotting utility at a time
R/qtl is in pure custodial mode: every recent release answers a compiler, not a user
See all hstats alternatives → · See all tidytransit alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. hstats and tidytransit 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. hstats and tidytransit 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 hstats alternatives in Analytics are ranked by recent ship velocity. Browse the "hstats alternatives" section above for the current picks, or visit /alternatives/hstats for the full list with editorial commentary on each.
Top tidytransit alternatives in Analytics are ranked by recent ship velocity. Browse the "tidytransit alternatives" section above for the current picks, or visit /alternatives/tidytransit-r for the full list with editorial commentary on each.