← Back to home
Comparison · Analytics

distributional vs hdnom

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

distributional vs hdnom: at a glance

Featuredistributionalhdnom
SectorAnalyticsAnalytics
Velocity score0.05.0
Sparks · 30d00
Top themesr-package, probability-distributions, distribution-arithmetic, numerical-methodssurvival analysis, r, regularization, nomograms
Last editorial update1h ago4h ago
WebsiteVisit →Visit →

What is distributional?

distributional taught + and - to work on any pair of distributions, closing the algebra it started with.

The R package providing vectorised distribution objects — the substrate that forecasting and anomaly tooling in the same ecosystem builds on. Cadence has picked up sharply, with four releases in the six months to June 2026 against roughly one a year before that. Two kinds of work alternate: adding distribution families (Dirichlet, Horseshoe, Laplace, multivariate t, g-and-k, the extreme-value pair) and deepening what can be computed generically across all of them.

Read the full distributional trajectory →

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 →

distributional vs hdnom: editorial side-by-side

D0.0

distributional taught + and - to work on any pair of distributions, closing the algebra it started with.

◆ Current state

The R package providing vectorised distribution objects — the substrate that forecasting and anomaly tooling in the same ecosystem builds on. Cadence has picked up sharply, with four releases in the six months to June 2026 against roughly one a year before that. Two kinds of work alternate: adding distribution families (Dirichlet, Horseshoe, Laplace, multivariate t, g-and-k, the extreme-value pair) and deepening what can be computed generically across all of them.

◆ Where it's heading

The generic-computation thread is the one that matters and it has been building steadily: a Monte Carlo default method for cdf(), has_symmetry() to let algorithms specialise, hdr() moving to exact results for symmetric distributions and 4096 quantiles elsewhere, open-versus-closed support intervals. Version 0.8.0 is where that thread arrives somewhere — arithmetic on arbitrary distributions, with closed forms used when they exist and numerical convolution when they do not. The package is positioning itself as a computational layer rather than a catalogue, which is consistent with how weird and the forecasting packages consume it.

◆ Prediction

Expect the numerical machinery behind dist_convolved() to be reused for other operators, and more generics like has_symmetry() that let downstream algorithms take exact paths when a distribution supports them.

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.

Alternatives to distributional and hdnom

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

See all distributional alternatives → · See all hdnom alternatives →

Recent activity from distributional and hdnom

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. 1mo agodistributionalConditional S3 registration so the package loads on R before 4.3
  4. 1mo agodistributionalDistribution arithmetic: FFT convolution behind the + and - operators
  5. 2mo agodistributionalVectorised p in quantile() for inflated distributions; open brackets on infinite bounds
  6. 5mo agodistributionalDirichlet and Horseshoe distributions added
  7. 7mo agodistributionalhas_symmetry() generic, exact HDRs for symmetric distributions
  8. 1y agohdnomhdnom 6.1.0 exposes lambda selection after a glmnet normalization change
  9. 1y agodistributionalMonte Carlo cdf() default method; g-and-k, g-and-h and extreme-value families
  10. 1y agohdnomhdnom 6.0.4
  11. 2y agohdnomhdnom 6.0.3
  12. 3y agohdnomhdnom 6.0.2

Frequently asked questions

What is the difference between distributional and hdnom?

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.

Is distributional better than hdnom?

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

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

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.