qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of tern.rbmi and timeplyr — release velocity, themes, recent moves, and the top alternatives to consider.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
tern.rbmi renders the output of {rbmi} reference-based multiple imputation analyses into tern tables for clinical reporting. Its three most recent releases exist to satisfy CRAN: restricting vignette builds to gcc, adding V8 to Suggests, and a plain resubmission. No user-facing functionality has changed in the visible window, and the three older entries now backfilled are version-bump automation.
timeplyr cut everything that wasn't time, then rebuilt intervals as fixed-width vectors.
timeplyr is a time-aware companion to dplyr and data.table, built around a fixed-width time_interval vector class. The 1.0.0 rewrite removed most non-time functions and pushed the C++ layer out into the separate cheapr package, leaving a narrower surface than the 0.8.x line. Releases since have been small: one feature batch in 1.1.1 and a pair of bug fixes in 1.1.2.
tern.rbmi renders the output of {rbmi} reference-based multiple imputation analyses into tern tables for clinical reporting. Its three most recent releases exist to satisfy CRAN: restricting vignette builds to gcc, adding V8 to Suggests, and a plain resubmission. No user-facing functionality has changed in the visible window, and the three older entries now backfilled are version-bump automation.
This is a thin adapter package and behaves like one — it moves when CRAN or an upstream dependency forces it to. Between 2022 and 2024 the feed shows only version bumps, and the 2025 releases are packaging concerns rather than analysis changes. The newly surfaced 2022 entries reinforce rather than change that reading.
Expect the next release to be triggered by a CRAN check failure or an {rbmi} update rather than by new tabulation features.
timeplyr is a time-aware companion to dplyr and data.table, built around a fixed-width time_interval vector class. The 1.0.0 rewrite removed most non-time functions and pushed the C++ layer out into the separate cheapr package, leaving a narrower surface than the 0.8.x line. Releases since have been small: one feature batch in 1.1.1 and a pair of bug fixes in 1.1.2.
The arc is consolidation, not expansion. Each release since 1.0.0 trims arguments, renames functions toward a single vocabulary (width, timespan, grid), or fixes an interaction with data.table's own rolling functions. The package increasingly acts as a thin time layer over cheapr and data.table rather than carrying its own implementation.
Expect continued small releases tracking cheapr and data.table changes rather than new function families; the entries show no in-progress feature work beyond the ggplot2-friendly breakpoint helpers introduced in 1.1.1.
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.rbmi or timeplyr.
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.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
See all tern.rbmi alternatives → · See all timeplyr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. tern.rbmi and timeplyr 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.rbmi and timeplyr 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.rbmi alternatives in Analytics are ranked by recent ship velocity. Browse the "tern.rbmi alternatives" section above for the current picks, or visit /alternatives/tern-rbmi for the full list with editorial commentary on each.
Top timeplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "timeplyr alternatives" section above for the current picks, or visit /alternatives/timeplyr for the full list with editorial commentary on each.