← Back to home
Comparison · Analytics

hdnom vs qtl

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

Shared themes:maintenance

hdnom vs qtl: at a glance

Featurehdnomqtl
SectorAnalyticsAnalytics
Velocity score5.00.0
Sparks · 30d00
Top themessurvival analysis, r, regularization, nomogramsgenetics, qtl-mapping, statistical-genomics, r-package
Last editorial update6h ago57m 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 qtl?

R/qtl is in pure custodial mode: every recent release answers a compiler, not a user

R/qtl is the long-established R package for QTL mapping in experimental crosses, covering interval mapping, composite interval mapping, multiple-QTL model fitting and the associated cross data formats. Nothing in the recent release history adds capability. Version 1.74 removes an include that started warning on CRAN, 1.72 improves an error message in cim(), and 1.70 migrates the C code from Calloc/Realloc/Free to their R_-prefixed equivalents for R-devel.

Read the full qtl trajectory →

hdnom vs qtl: 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.

Q
qtl
ANALYTICS
0.0

R/qtl is in pure custodial mode: every recent release answers a compiler, not a user

◆ Current state

R/qtl is the long-established R package for QTL mapping in experimental crosses, covering interval mapping, composite interval mapping, multiple-QTL model fitting and the associated cross data formats. Nothing in the recent release history adds capability. Version 1.74 removes an include that started warning on CRAN, 1.72 improves an error message in cim(), and 1.70 migrates the C code from Calloc/Realloc/Free to their R_-prefixed equivalents for R-devel.

◆ Where it's heading

The package is being maintained, not developed. The work divides cleanly into keeping the compiled code building against successive R and toolchain versions, and fixing narrow bugs reported through the issue tracker. The C-level migrations in particular are compliance with R's tightening of its C interface rather than anything chosen. Users should read the stability as maturity: the analysis surface has been fixed for years and the maintainer is keeping it installable.

◆ Prediction

R has continued to restrict its non-API C entry points, and this package has already made two such migrations, so further compile-time compliance work is the most likely content of the next release.

Alternatives to hdnom and qtl

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 qtl.

See all hdnom alternatives → · See all qtl alternatives →

Recent activity from hdnom and qtl

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

  1. 18d agohdnomhdnom 6.2.1
  2. 18d agohdnomhdnom 6.2.0 pins Cox tie handling ahead of glmnet's migration
  3. 8mo agoqtlRemove R_ext/PrtUtil.h include flagged by CRAN
  4. 8mo agoqtlClearer cim() error when multiple phenotypes are passed
  5. 1y agohdnomhdnom 6.1.0 exposes lambda selection after a glmnet normalization change
  6. 1y agohdnomhdnom 6.0.4
  7. 1y agoqtlC memory calls migrated to R_Calloc/R_Realloc/R_Free
  8. 2y agohdnomhdnom 6.0.3
  9. 2y agoqtlFix Rprintf call and remaining compiler warnings
  10. 2y agoqtlFix summary.scanone() thresholds and csvs phenotype reading
  11. 3y agohdnomhdnom 6.0.2
  12. 3y agoqtlFix addint()/addcovarint() with X chromosome QTL and missing phenotypes

Frequently asked questions

What is the difference between hdnom and qtl?

Both compete on the same themes — maintenance — within Analytics. 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.

Is hdnom better than qtl?

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.

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 qtl?

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