← Back to home
Comparison · Analytics

hdnom vs rncl

A side-by-side editorial comparison of hdnom and rncl — release velocity, themes, recent moves, and the top alternatives to consider.

hdnom vs rncl: at a glance

Featurehdnomrncl
SectorAnalyticsAnalytics
Velocity score5.02.5
Sparks · 30d00
Top themessurvival analysis, r, regularization, nomogramsphylogenetics, file-parsing, cran-maintenance, c++
Last editorial update1h ago56m ago
WebsiteVisit →Visit →

What is hdnom?

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.

Read the full hdnom trajectory →

What is rncl?

A phylogenetics parser on life support, shipping only what CRAN's compilers demand.

rncl wraps the Nexus Class Library so R can read Newick and NEXUS tree files. Every release since 2016 has been custodial: 0.8.9 exists solely to pull upstream NCL changes so the bundled C++ compiles under the C++20 standard. No user-facing function has changed in close to a decade.

Read the full rncl trajectory →

hdnom vs rncl: editorial side-by-side

H
hdnom
ANALYTICS
5.0

hdnom is in pure custodial mode, absorbing glmnet's changes so its users don't have to

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

R
rncl
ANALYTICS
2.5

A phylogenetics parser on life support, shipping only what CRAN's compilers demand.

◆ Current state

rncl wraps the Nexus Class Library so R can read Newick and NEXUS tree files. Every release since 2016 has been custodial: 0.8.9 exists solely to pull upstream NCL changes so the bundled C++ compiles under the C++20 standard. No user-facing function has changed in close to a decade.

◆ Where it's heading

The release cadence tracks toolchain deprecations rather than user demand: gcc 12 removing binary_function in 2022, a deprecated Rcpp call in 2025, C++20 in 2026. The package is maintained as a stable parsing dependency for phylogenetics tooling, and the goal visible in these entries is keeping it installable, not extending it.

◆ Prediction

Expect the next release only when a compiler or CRAN policy change breaks the build again; nothing in these entries points to new parsing features.

Alternatives to hdnom and rncl

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 hdnom or rncl.

See all hdnom alternatives → · See all rncl alternatives →

Recent activity from hdnom and rncl

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 15d agornclNCL sources refreshed for C++20 compilation
  2. 18d agohdnomhdnom 6.2.1
  3. 18d agohdnomhdnom 6.2.0 pins Cox tie handling ahead of glmnet's migration
  4. 8mo agornclDeprecated Rcpp call removed in maintenance release
  5. 1y agohdnomhdnom 6.1.0 exposes lambda selection after a glmnet normalization change
  6. 1y agohdnomhdnom 6.0.4
  7. 2y agohdnomhdnom 6.0.3
  8. 3y agohdnomhdnom 6.0.2
  9. 4y agornclBuild fixed for gcc 12 and clang 14
  10. 6y agornclMaintenance release clearing CRAN check warnings
  11. 8y agornclCRAN check notes and warnings cleared
  12. 9y agornclSingleton removal moves to C++ for a 3x speedup

Frequently asked questions

What is the difference between hdnom and rncl?

They serve adjacent needs but don't currently overlap on shipped themes. hdnom is currently shipping more aggressively (velocity 5.0 vs 2.5), 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.

Is hdnom better than rncl?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. hdnom is currently shipping more aggressively (velocity 5.0 vs 2.5), 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.

What are the best alternatives to hdnom?

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.

What are the best alternatives to rncl?

Top rncl alternatives in Analytics are ranked by recent ship velocity. Browse the "rncl alternatives" section above for the current picks, or visit /alternatives/rncl-r for the full list with editorial commentary on each.