tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of grex and treespace — release velocity, themes, recent moves, and the top alternatives to consider.
grex is a lookup table with a version number — it ships when the annotation moves.
grex converts the deprecated Ensembl gene IDs found in GTEx data into current gene symbols and identifiers, using org.Hs.eg.db as its reference. Its value is entirely in that bundled reference data, so a release either refreshes the mapping or does nothing to it. The 2025 release does nothing to it: GitHub Actions for the docs site, a check-note fix, and a smaller vignette.
treespace ships once every year or two, and only when CRAN or a user forces it.
treespace explores and compares sets of phylogenetic and transmission trees, including the tree-distance measures used in outbreak reconstruction. Its release history is entirely reactive: five updates across five years, each triggered by a CRAN policy change, an upstream package removal, or a bug someone reported. The most recent is an Rd cross-reference format patch plus a maintainer email change.
grex converts the deprecated Ensembl gene IDs found in GTEx data into current gene symbols and identifiers, using org.Hs.eg.db as its reference. Its value is entirely in that bundled reference data, so a release either refreshes the mapping or does nothing to it. The 2025 release does nothing to it: GitHub Actions for the docs site, a check-note fix, and a smaller vignette.
The annotation refreshes stopped. Between 2017 and 2019 the package tracked org.Hs.eg.db through four versions and added the GTEx V7 identifier set; since then the reference has stood still while the releases turned to packaging. That gap matters more here than it would elsewhere — a stale mapping table silently returns outdated symbols rather than failing, so the package's core asset ages invisibly.
Nothing in these entries signals a planned data refresh, and the six-year pattern suggests the next release will again be infrastructure. Users needing current annotations should check which org.Hs.eg.db version is bundled rather than assume the version number reflects it.
treespace explores and compares sets of phylogenetic and transmission trees, including the tree-distance measures used in outbreak reconstruction. Its release history is entirely reactive: five updates across five years, each triggered by a CRAN policy change, an upstream package removal, or a bug someone reported. The most recent is an Rd cross-reference format patch plus a maintainer email change.
The package is stable and lightly staffed rather than abandoned — bugs that affect correctness do get fixed, and CRAN deadlines are met. But the 2023 update is the telling one: rather than vendor or replace adephylo when it faced removal, the maintainers disabled two tree-vector methods and marked the loss as hopefully temporary. Two years on, nothing in the feed indicates they came back.
The next entry will most likely be another CRAN-compliance patch, on the pattern of four of the last five releases. Whether the Abouheif and sumDD methods ever return is not something these entries give any signal on.
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 grex or treespace.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
A single-purpose ggplot2 inset tool, refining the same three arguments.
An R symbolic-maths binding whose changelog is really the C++ core's release notes.
gtfstools stopped guarding its own object model and started accepting everyone else's.
The glue package that makes R carry units and uncertainty through the same calculation.
See all grex alternatives → · See all treespace alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — maintenance-mode — within Analytics. grex and treespace 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. grex and treespace 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 grex alternatives in Analytics are ranked by recent ship velocity. Browse the "grex alternatives" section above for the current picks, or visit /alternatives/grex-r for the full list with editorial commentary on each.
Top treespace alternatives in Analytics are ranked by recent ship velocity. Browse the "treespace alternatives" section above for the current picks, or visit /alternatives/treespace-r for the full list with editorial commentary on each.