← Back to home
Comparison · Analytics

aedseo vs EpiNow2

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

Shared themes:epidemiologyr-package

aedseo vs EpiNow2: at a glance

FeatureaedseoEpiNow2
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesepidemiology, time-series, surveillance, r-packageepidemiology, bayesian-modelling, reproduction-number, r-package
Last editorial update54m ago8h ago
WebsiteVisit →Visit →

What is aedseo?

An epidemic-onset detector that now brackets the whole season, not just its start

aedseo is a Statens Serum Institut R package for automated early detection of seasonal epidemic onsets, built around growth-rate estimation over consecutive time intervals. The 1.0.0 line moved it well past its original scope: observations are now modelled as cases or population-adjusted incidence, multiple waves can be estimated in one pass, and disease-specific thresholds are computed by a dedicated function. Version 1.1.0 adds an estimate of when a season has ended after the first onset.

Read the full aedseo trajectory →

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.

Read the full EpiNow2 trajectory →

aedseo vs EpiNow2: editorial side-by-side

A
aedseo
ANALYTICS
0.0

An epidemic-onset detector that now brackets the whole season, not just its start

◆ Current state

aedseo is a Statens Serum Institut R package for automated early detection of seasonal epidemic onsets, built around growth-rate estimation over consecutive time intervals. The 1.0.0 line moved it well past its original scope: observations are now modelled as cases or population-adjusted incidence, multiple waves can be estimated in one pass, and disease-specific thresholds are computed by a dedicated function. Version 1.1.0 adds an estimate of when a season has ended after the first onset.

◆ Where it's heading

The arc runs from a single-purpose onset detector toward a full seasonal-surveillance toolkit. Each release since 1.0.0 has widened what the package can say about a season rather than improving how it says it: incidence denominators, background population, multi-wave detection, thresholds, and now season end. Fixes in between are narrow and numerical, such as confidence intervals under ATLAS BLAS.

◆ Prediction

The natural next step is symmetry with the onset machinery the package already has: turning the 1.1.0 seasonal offset into a first-class output alongside onset, with its own summary and plotting methods.

E
EpiNow2
ANALYTICS
0.0

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.

Alternatives to aedseo and EpiNow2

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 aedseo or EpiNow2.

See all aedseo alternatives → · See all EpiNow2 alternatives →

Recent activity from aedseo and EpiNow2

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

  1. 1mo agoEpiNow2estimate_truncation gains full delay and observation options
  2. 6mo agoEpiNow2Unified return objects and shared accessors across all models
  3. 6mo agoaedseocombined_seasonal_output() now estimates when a season ends
  4. 8mo agoaedseoFix growth-rate confidence intervals under ATLAS BLAS
  5. 9mo agoaedseoIncidence, population adjustment and multi-wave detection land in 1.0.0
  6. 1y agoEpiNow2Patch for an upstream rstan issue
  7. 1y agoEpiNow2Accumulation for irregularly reported data; unified priors
  8. 1y agoEpiNow2Matern kernel spectral density fix and GP prior revert
  9. 1y agoEpiNow2Gaussian Process model improvements and explicit defaults
  10. 2y agoaedseoMaintainership transferred to Lasse Engbo Christiansen
  11. 2y agoaedseoepi_calendar() and richer autoplot displays
  12. 2y agoaedseoFirst CRAN release of the aeddo onset detector

Frequently asked questions

What is the difference between aedseo and EpiNow2?

Both compete on the same themes — epidemiology, r-package — within Analytics. aedseo and EpiNow2 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 aedseo better than EpiNow2?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. aedseo and EpiNow2 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 aedseo?

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

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.