qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of tern.mmrm and tidytransit — release velocity, themes, recent moves, and the top alternatives to consider.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
tern.mmrm wraps mixed models for repeated measures into the tern tabulation and plotting layer used by teal clinical modules. The visible history ends with three CRAN releases in mid-to-late 2024; before that the feed carries only automated version bumps from 2022, three of which have just been backfilled into the record. The most recent substantive change adds axis limit arguments to the LS-means plot.
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.
tern.mmrm wraps mixed models for repeated measures into the tern tabulation and plotting layer used by teal clinical modules. The visible history ends with three CRAN releases in mid-to-late 2024; before that the feed carries only automated version bumps from 2022, three of which have just been backfilled into the record. The most recent substantive change adds axis limit arguments to the LS-means plot.
Content per release is thin and largely organisational: a maintainer change, replacing scda with random.cdisc.data in vignettes, and adapting to new {mmrm} versions. The package appears to be in maintenance, tracking its upstream dependency rather than developing independently. The 2022 entries now visible are release-automation commits, not releases in any meaningful sense.
Nothing here signals new functionality; the realistic next event is another compatibility release when {mmrm} or {rtables} changes underneath it.
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 tern.mmrm or tidytransit.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
The R client for AusTraits spends its releases chasing the dataset it reads.
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
A fossil-record simulator that quietly grew a trait-evolution engine.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
See all tern.mmrm 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. tern.mmrm 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. tern.mmrm 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 tern.mmrm alternatives in Analytics are ranked by recent ship velocity. Browse the "tern.mmrm alternatives" section above for the current picks, or visit /alternatives/tern-mmrm 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.