tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of grex and hdnom — 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.
hdnom is in pure custodial mode, absorbing glmnet's changes so its users don't have to
hdnom builds nomograms and validation/calibration workflows for high-dimensional Cox survival models on top of glmnet, ncvreg and penalized. The package's own interface has been stable since the 6.0.0 refactor in 2019; every release since has been maintenance. The recent run is entirely about surviving glmnet's evolution — a lambda-selection rule argument, then a cox.ties argument pinning the old tie handling.
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.
hdnom builds nomograms and validation/calibration workflows for high-dimensional Cox survival models on top of glmnet, ncvreg and penalized. The package's own interface has been stable since the 6.0.0 refactor in 2019; every release since has been maintenance. The recent run is entirely about surviving glmnet's evolution — a lambda-selection rule argument, then a cox.ties argument pinning the old tie handling.
The releases track two upstream pressures with no feature work of its own. glmnet is the larger one: its 4.1-9 change to how Cox cross-validation errors are normalized made lambda.1se select null models far more often, forcing hdnom to expose a rule argument and switch its examples to lambda.min. R-devel is the other, producing a steady trickle of strict-headers, deprecated-symbol and check-note fixes. The pattern is consistent — absorb the upstream change, default to whatever preserves existing behaviour, let users opt into the new one.
The cox.ties default is explicitly pinned to "breslow" to silence glmnet's migration warning, which is a deferral rather than a decision; expect a future release to flip that default to "efron" once glmnet completes the transition.
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 hdnom.
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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. hdnom 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. hdnom 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 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 hdnom alternatives in Analytics are ranked by recent ship velocity. Browse the "hdnom alternatives" section above for the current picks, or visit /alternatives/hdnom for the full list with editorial commentary on each.