← Back to home
Comparison · Analytics

EpiNow2 vs watina

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

Shared themes:r-package

EpiNow2 vs watina: at a glance

FeatureEpiNow2watina
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesepidemiology, bayesian-modelling, reproduction-number, r-packager-package, groundwater, hydrochemistry, database-client
Last editorial update6h ago58m ago
WebsiteVisit →Visit →

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 →

What is watina?

A groundwater database client that has started doing the domain analysis too

watina is the R interface to the Watina groundwater monitoring database, and its history is mostly about making data retrieval correct: filter depths guessed conservatively when missing, spatial masking, aggregation methods per observation well, and a long series of fixes to keep the lazy database queries working across dbplyr versions. The most recent release moves past retrieval into interpretation, adding ionic ratio calculation and a Van Wirdum diagram to plot chemistry data.

Read the full watina trajectory →

EpiNow2 vs watina: editorial side-by-side

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.

W
watina
ANALYTICS
0.0

A groundwater database client that has started doing the domain analysis too

◆ Current state

watina is the R interface to the Watina groundwater monitoring database, and its history is mostly about making data retrieval correct: filter depths guessed conservatively when missing, spatial masking, aggregation methods per observation well, and a long series of fixes to keep the lazy database queries working across dbplyr versions. The most recent release moves past retrieval into interpretation, adding ionic ratio calculation and a Van Wirdum diagram to plot chemistry data.

◆ Where it's heading

The package is drifting from a database client toward a domain toolkit. Early releases fought the data layer — connection handling moved to inbodb, sorting semantics changed, defunct dbplyr calls worked around. Recent work assumes retrieval is solved and adds hydrochemical analysis on top, along with defensive handling for the physically impossible inputs that analysis exposes, such as zero conductivity in the warehouse.

◆ Prediction

Expect further chemistry analysis and plotting helpers rather than new retrieval functions, since that is where the newest release invested and where the accompanying vignette points.

Alternatives to EpiNow2 and watina

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

See all EpiNow2 alternatives → · See all watina alternatives →

Recent activity from EpiNow2 and watina

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

  1. 1mo agoEpiNow2estimate_truncation gains full delay and observation options
  2. 4mo agowatinaIonic ratios and Van Wirdum diagrams for chemistry data
  3. 6mo agoEpiNow2Unified return objects and shared accessors across all models
  4. 1y agoEpiNow2Patch for an upstream rstan issue
  5. 1y agoEpiNow2Accumulation for irregularly reported data; unified priors
  6. 1y agoEpiNow2Matern kernel spectral density fix and GP prior revert
  7. 1y agoEpiNow2Gaussian Process model improvements and explicit defaults
  8. 2y agowatinaKSgeneral moved to Suggests to survive CRAN removal
  9. 5y agowatinaDataframe input restored after a defunct dbplyr call
  10. 5y agowatinadbplyr 2.0 compatibility drops the need for a forked dependency
  11. 5y agowatinaSpatial clustering of wells and richer location attributes
  12. 6y agowatinaSoil surface calculation fixed after a select() dropped the variable

Frequently asked questions

What is the difference between EpiNow2 and watina?

Both compete on the same themes — r-package — within Analytics. EpiNow2 and watina 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 watina?

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

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