tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of grex and spatstat — 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.
The spatstat umbrella package, now mostly a pointer to the sub-packages doing the work
spatstat is the front package of a family that was split into specialised components — spatstat.geom, spatstat.random, spatstat.model, spatstat.explore, spatstat.univar and spatstat.sparse. Its own release notes reflect that: entries in this window are largely announcements of where the real changes landed, plus documentation and cross-reference maintenance. The codebase it fronts passed 200,000 lines as of 3.5-1.
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.
spatstat is the front package of a family that was split into specialised components — spatstat.geom, spatstat.random, spatstat.model, spatstat.explore, spatstat.univar and spatstat.sparse. Its own release notes reflect that: entries in this window are largely announcements of where the real changes landed, plus documentation and cross-reference maintenance. The codebase it fronts passed 200,000 lines as of 3.5-1.
The split is effectively complete and the umbrella's role has settled into coordination — tracking version dependencies across sub-packages and pointing users to them. The family has kept subdividing over this period, with spatstat.univar joining in 3.1-0. The one substantive user-facing addition here is documentation infrastructure: 3.3-0 added the ability to list the history of changes to a specific function, which is a navigational answer to a codebase now spread across many packages.
Expect this package's notes to continue summarising sub-package activity rather than carrying features of its own, since every release in this window does exactly that. Read spatstat.geom, spatstat.random and spatstat.model for the substance.
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 spatstat.
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 spatstat alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. grex and spatstat 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 spatstat 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 spatstat alternatives in Analytics are ranked by recent ship velocity. Browse the "spatstat alternatives" section above for the current picks, or visit /alternatives/spatstat-r for the full list with editorial commentary on each.