rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of RadialMR and tidytransit — release velocity, themes, recent moves, and the top alternatives to consider.
RadialMR's 2026 release corrects degrees of freedom that had been wrong since documentation.
RadialMR implements radial-plot formulations of IVW and MR-Egger Mendelian randomization, with outlier detection and interactive plotting. The recent history is thin on features and increasingly focused on the arithmetic: 1.2.4 in July 2026 fixes the degrees of freedom returned by egger_radial() to the documented n-2, corrects the heterogeneity p-value that inherited the same error, and repairs a negated lower bound in the random-effects bootstrap standard error search interval in ivw_radial().
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.
RadialMR implements radial-plot formulations of IVW and MR-Egger Mendelian randomization, with outlier detection and interactive plotting. The recent history is thin on features and increasingly focused on the arithmetic: 1.2.4 in July 2026 fixes the degrees of freedom returned by egger_radial() to the documented n-2, corrects the heterogeneity p-value that inherited the same error, and repairs a negated lower bound in the random-effects bootstrap standard error search interval in ivw_radial().
This is a package being read closely by its maintainer rather than extended. The 1.2.x line pairs statistical corrections with defensive hardening — an rmr_format class check so unformatted input fails with a clear message, and plotly_radial() dispatching on object class instead of counting list elements. Both are the kind of change made while auditing, not while building.
Expect the audit to continue into the remaining estimator internals and print methods rather than new radial variants; the entries show no feature work queued.
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 RadialMR 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 RadialMR 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. RadialMR 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. RadialMR 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 RadialMR alternatives in Analytics are ranked by recent ship velocity. Browse the "RadialMR alternatives" section above for the current picks, or visit /alternatives/radialmr 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.