qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of tern.mmrm and vellum — 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.
vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.
The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.
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.
The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.
The pivotal detail is stated outright in 0.6.3 — the first bug in the series found by using the engine from vellumplot rather than testing it in isolation. Every release since names the downstream as the source: the contrast rule's false positives, the lint rules that fired on all five sample plots, the keyed roundrect batch. A rendering engine with a real grammar built on top of it is now getting the integration coverage that unit tests structurally cannot provide, and the fixes are converging on one theme: the measurement path and the draw path must not drift.
Expect the release rate to fall as the vellumplot integration surface is exhausted, with remaining work concentrated in the lint rule set now that it is meant to gate builds rather than just inform.
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 vellum.
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 vellum alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. vellum is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. vellum is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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 vellum alternatives in Analytics are ranked by recent ship velocity. Browse the "vellum alternatives" section above for the current picks, or visit /alternatives/vellum-r for the full list with editorial commentary on each.