← Back to home
Comparison · Analytics

EpiNow2 vs redist

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

EpiNow2 vs redist: at a glance

FeatureEpiNow2redist
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesepidemiology, bayesian-modelling, reproduction-number, r-packager, redistricting, monte-carlo, sampling
Last editorial update7h ago54m 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 redist?

redist keeps rewriting the sampler underneath a district-drawing API it has held stable since 4.0.

redist simulates redistricting plans via sequential Monte Carlo, merge-split MCMC and short-burst optimization, and it is the analysis tool behind a good deal of published districting work. The user-facing shape was set by 4.0.1's constraint interface and the split of metrics into the redistmetrics package; since then the changes are in the algorithms. The most consequential recent one replaces the SMC label-counting adjustment with a backward kernel that removes approximation error outright.

Read the full redist trajectory →

EpiNow2 vs redist: 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.

R
redist
ANALYTICS
0.0

redist keeps rewriting the sampler underneath a district-drawing API it has held stable since 4.0.

◆ Current state

redist simulates redistricting plans via sequential Monte Carlo, merge-split MCMC and short-burst optimization, and it is the analysis tool behind a good deal of published districting work. The user-facing shape was set by 4.0.1's constraint interface and the split of metrics into the redistmetrics package; since then the changes are in the algorithms. The most consequential recent one replaces the SMC label-counting adjustment with a backward kernel that removes approximation error outright.

◆ Where it's heading

The direction is toward exactness and throughput at once — the new kernel is described as both eliminating approximation error and costing far less computation, and successive releases keep adding parallelism, most recently to the flip algorithm. Feature growth has moved into the optimization side, where short-burst gained multiple independent scorers and a Pareto frontier. The release notes are not a reliable ledger: 4.3.1 ships the identical text as 4.3.0.

◆ Prediction

Expect the remaining single-threaded algorithms to gain the chains-style parallelism that flip just received, following the pattern SMC established several releases ago.

Alternatives to EpiNow2 and redist

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

See all EpiNow2 alternatives → · See all redist alternatives →

Recent activity from EpiNow2 and redist

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

  1. 1mo agoEpiNow2estimate_truncation gains full delay and observation options
  2. 6mo agoredistParallel chains for redist_flip()
  3. 6mo agoredistPatch release reusing the 4.3.0 notes
  4. 6mo agoEpiNow2Unified return objects and shared accessors across all models
  5. 10mo agoredistSMC backward kernel removes label-counting approximation error
  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 agoredistMulti-objective short-burst search with Pareto frontier
  11. 3y agoredistredist_ci interface and faster loop-erased random walk
  12. 4y agoredistredist_constr() unifies constraints and admits user-defined ones

Frequently asked questions

What is the difference between EpiNow2 and redist?

They serve adjacent needs but don't currently overlap on shipped themes. EpiNow2 and redist 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 redist?

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

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