rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of epiflows and hdnom — release velocity, themes, recent moves, and the top alternatives to consider.
epiflows has shipped four releases in eight years, none of which changed the code.
epiflows predicts the spread of infectious disease along population flows between locations, and it is effectively dormant. The whole visible history spans 2018 to 2026 in four entries: the first CRAN release, a Zenodo archival tag, a Roxygen patch whose notes state the functionality is unchanged, and a 2026 release replacing deprecated ggplot2 and tibble calls. No entry describes new epidemiological capability.
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.
epiflows predicts the spread of infectious disease along population flows between locations, and it is effectively dormant. The whole visible history spans 2018 to 2026 in four entries: the first CRAN release, a Zenodo archival tag, a Roxygen patch whose notes state the functionality is unchanged, and a 2026 release replacing deprecated ggplot2 and tibble calls. No entry describes new epidemiological capability.
The package is being kept installable rather than developed. The one recent release is dependency maintenance contributed from outside, which is the pattern for RECON-era epidemiology packages that have outlived their original project funding. Two separate entries are both labelled version 0.2.1, so even the version history is not a reliable guide to what changed.
Any further releases will most likely be more deprecation cleanup to keep the package on CRAN; there is nothing in the record suggesting active development has resumed.
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 epiflows or hdnom.
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
A statistician's personal toolbox, growing one plotting utility at a time
R/qtl is in pure custodial mode: every recent release answers a compiler, not a user
See all epiflows alternatives → · See all hdnom alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r, 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.
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 epiflows alternatives in Analytics are ranked by recent ship velocity. Browse the "epiflows alternatives" section above for the current picks, or visit /alternatives/epiflows-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.