OHPL
A 2017 chemometrics method frozen in place, visited only when CRAN changes its documentation rules.
Comparison · Analytics
EpiNow2 vs n2khab
A side-by-side editorial comparison of EpiNow2 and n2khab — release velocity, themes, recent moves, and the top alternatives to consider.
EpiNow2 vs n2khab: at a glance
What is EpiNow2?
EpiNow2 unified its model interface, then went back to deepen the estimators behind it
EpiNow2 estimates reproduction numbers, infections and delay distributions from incomplete epidemiological reporting data. 1.8.0 was the structural turning point: every main modelling function now returns a consistent S3 object with `fit`, `args` and `observations`, reachable through shared accessors. The releases either side of it work on estimator quality — accumulation of irregularly reported data in 1.7.0, and a substantial expansion of `estimate_truncation()` in 1.9.0.
What is n2khab?
n2khab keeps retracting interpretations of habitat data it can't actually support
n2khab reads and prepares the standardised Flemish Natura 2000 habitat data sources — habitat maps, water surfaces, GRTS master grids — for reproducible analysis. Releases track the publication of new versioned data sources on Zenodo, but the more consequential ones change how the package interprets what it reads. The latest removes an argument outright after the reasoning behind it was found to be wrong.
EpiNow2 vs n2khab: editorial side-by-side
EpiNow2
0.0ANALYTICS
EpiNow2 unified its model interface, then went back to deepen the estimators behind it
◆ Current state
EpiNow2 estimates reproduction numbers, infections and delay distributions from incomplete epidemiological reporting data. 1.8.0 was the structural turning point: every main modelling function now returns a consistent S3 object with `fit`, `args` and `observations`, reachable through shared accessors. The releases either side of it work on estimator quality — accumulation of irregularly reported data in 1.7.0, and a substantial expansion of `estimate_truncation()` in 1.9.0.
◆ Where it's heading
The package spent this window paying down interface debt and is now extending from the tidier base. Options that existed only for `estimate_infections()` have been propagated outward: `estimate_truncation()` gained the full `dist_spec` delay families, `obs_opts()` observation model selection between Poisson and negative binomial, and the `likelihood` and `return_likelihood` settings that make prior-only fits and loo-compatible output possible. Hardcoded assumptions are being replaced by specifiable ones in the same motion — the truncation model's additive noise term was a fixed `sigma ~ normal(0, 1)` prior and is now a `dist_spec` argument.
◆ Prediction
Expect the remaining modelling functions to keep converging on the shared options interface, since the last two releases have each moved another function onto it. A new `estimate_dist()` for interval-censored linelist data suggests delay estimation is the area still gaining surface.
n2khab
0.0ANALYTICS
n2khab keeps retracting interpretations of habitat data it can't actually support
◆ Current state
n2khab reads and prepares the standardised Flemish Natura 2000 habitat data sources — habitat maps, water surfaces, GRTS master grids — for reproducible analysis. Releases track the publication of new versioned data sources on Zenodo, but the more consequential ones change how the package interprets what it reads. The latest removes an argument outright after the reasoning behind it was found to be wrong.
◆ Where it's heading
Two forces shape the package. The first is external: each new habitatmap or watersurfaces vintage needs a supported reader, and the package has absorbed a steady stream of them. The second is a willingness to break its own API when the ecology does not support what the code claimed — the interpreted argument removed because type 3130 occurrences cannot be resolved to a single subtype, the rbbvos+ type dropped as too loosely defined, the collapse default changed to match how users actually need the output shaped. Return structures are also being normalised so element names no longer vary with data source version.
◆ Prediction
The package has said it expects future watersurfaces_hab versions to implement collapsing in the data source itself, so the corresponding argument is a candidate for removal once that lands — the same path the interpreted argument took.
Alternatives to EpiNow2 and n2khab
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 EpiNow2 or n2khab.
fastplyr
A fast dplyr stand-in that keeps finding new places to skip work entirely.
trias
Belgium's invasive-species indicator toolkit is in steady refinement, one plotting edge case at a time.
icesSAG
The ICES stock assessment client took upload away in 2024 and spent two years giving it back.
dggridR
A discrete global grid generator grew cell traversal and became a usable spatial index.
vegan
Community ecology's standard toolkit is retiring the functions a generation of scripts was built on.
See all EpiNow2 alternatives → · See all n2khab alternatives →
Recent activity from EpiNow2 and n2khab
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agon2khabn2khab 0.15.1
- 1mo agon2khabn2khab drops an argument built on a wrong ecological assumption
- 1mo agoEpiNow2estimate_truncation gains full delay and observation options
- 5mo agon2khabn2khab adds a reader for the watersurfaces reference points source
- 6mo agoEpiNow2Unified return objects and shared accessors across all models ⚡
- 7mo agon2khabn2khab collapses watersurfaces output to unique polygon-type pairs
- 1y agoEpiNow2Patch for an upstream rstan issue
- 1y agoEpiNow2Accumulation for irregularly reported data; unified priors
- 1y agon2khabSupport for watersurfaces 2024 and watersurfaces_hab v6
- 1y agoEpiNow2Matern kernel spectral density fix and GP prior revert
- 1y agon2khabn2khab supports the 2023 habitat maps and drops the rbbvos+ type
- 1y agoEpiNow2Gaussian Process model improvements and explicit defaults
Frequently asked questions
What is the difference between EpiNow2 and n2khab?
They serve adjacent needs but don't currently overlap on shipped themes. EpiNow2 and n2khab are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is EpiNow2 better than n2khab?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. EpiNow2 and n2khab are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to EpiNow2?
Top EpiNow2 alternatives in Analytics are ranked by recent ship velocity. Browse the "EpiNow2 alternatives" section above for the current picks, or visit /alternatives/epinow2 for the full list with editorial commentary on each.
What are the best alternatives to n2khab?
Top n2khab alternatives in Analytics are ranked by recent ship velocity. Browse the "n2khab alternatives" section above for the current picks, or visit /alternatives/n2khab for the full list with editorial commentary on each.