← Back to home
Comparison · Analytics

dvir vs epinowcast

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

dvir vs epinowcast: at a glance

Featuredvirepinowcast
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesforensic genetics, victim identification, pipeline, scalabilityr, bayesian, stan, epidemiology
Last editorial update1h ago15m ago
WebsiteVisit →Visit →

What is dvir?

dvir keeps making disaster victim identification a single call instead of a workflow.

dvir handles disaster victim identification: matching unidentified remains against reference families using pedigree likelihoods. The package has consolidated around dviSolve(), a complete pipeline introduced in 3.2.1 and rewritten in 3.3.0 to use generalised likelihood ratios for families with several missing persons. Recent releases have been about making that pipeline survive large cases, adding dviGridSize() and a maxAssign cutoff to skip joint analysis when the combination count explodes, plus per-step timings.

Read the full dvir trajectory →

What is epinowcast?

epinowcast added Gaussian processes to its formula interface and made the sampler twice as fast

epinowcast is a Bayesian nowcasting toolkit for right-truncated epidemiological count data, built on Stan with a brms-style formula interface. Over 2025-2026 it moved from experimental to stable, prepared for CRAN, and broadened past nowcasting proper — 0.6.0's max_delay = 1 support allows purely retrospective fitting of fully reported counts. 0.7.0 in July 2026 is the largest modelling release in the window.

Read the full epinowcast trajectory →

dvir vs epinowcast: editorial side-by-side

D
dvir
ANALYTICS
0.0

dvir keeps making disaster victim identification a single call instead of a workflow.

◆ Current state

dvir handles disaster victim identification: matching unidentified remains against reference families using pedigree likelihoods. The package has consolidated around dviSolve(), a complete pipeline introduced in 3.2.1 and rewritten in 3.3.0 to use generalised likelihood ratios for families with several missing persons. Recent releases have been about making that pipeline survive large cases, adding dviGridSize() and a maxAssign cutoff to skip joint analysis when the combination count explodes, plus per-step timings.

◆ Where it's heading

The arc is from a toolbox of functions toward one supervised pipeline, with the older jointDVI() now emitting a legacy message. The current constraint is combinatorial: joint analysis over many victims and missing persons blows up, so the work has gone to measuring the blowup and bailing out of it. Parallelism is mid-migration, with the parallel and pbapply implementation removed and a mirai replacement stated as planned but not yet shipped, leaving numCores accepted and ignored with a warning.

◆ Prediction

The mirai-based parallelisation is announced as coming, so expect it next, most likely applied to the joint analysis step that maxAssign currently exists to avoid.

E
epinowcast
ANALYTICS
0.0

epinowcast added Gaussian processes to its formula interface and made the sampler twice as fast

◆ Current state

epinowcast is a Bayesian nowcasting toolkit for right-truncated epidemiological count data, built on Stan with a brms-style formula interface. Over 2025-2026 it moved from experimental to stable, prepared for CRAN, and broadened past nowcasting proper — 0.6.0's max_delay = 1 support allows purely retrospective fitting of fully reported counts. 0.7.0 in July 2026 is the largest modelling release in the window.

◆ Where it's heading

The package is converging on a general formula-driven latent process toolkit rather than a single nowcasting model. rw() and arima() were joined in 0.7.0 by gp(), a Hilbert-space reduced-rank Gaussian process placeable on any module's linear predictor with selectable kernels and an integration order matching arima()'s d. Alongside it, the fixed-effects design and integrated residuals are now centred against the module intercept, which the notes report roughly doubles sampling speed on a weekly random-walk growth model.

◆ Prediction

With CRAN preparation done in 0.6.0 and the model surface substantially widened in 0.7.0, the next release is likely a CRAN submission plus consolidation of the gp() kernels. The release notes repeatedly benchmark against EpiNow2's behaviour, suggesting continued convergence between the two codebases.

Alternatives to dvir and epinowcast

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 dvir or epinowcast.

See all dvir alternatives → · See all epinowcast alternatives →

Recent activity from dvir and epinowcast

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

  1. 1mo agoepinowcastgp() brings Gaussian processes to every module, and centring doubles sampling speed
  2. 1mo agodvirCombination sizing and a cutoff for joint analysis
  3. 3mo agodvirJoint tables added to solver output
  4. 3mo agodvirVictim and database accessors, plus solver refinements
  5. 3mo agoepinowcastCRAN preparation, inspection methods, and retrospective-only fitting
  6. 7mo agoepinowcastStructural reporting patterns for non-daily reporting cycles
  7. 10mo agoepinowcastLifecycle moves to stable; pathfinder and negative binomial support
  8. 1y agodvirSolver rewritten around generalised likelihood ratios
  9. 2y agoepinowcastNon-parametric reference date models and a stricter max_delay default
  10. 2y agodvirdviSolve() pipeline and manual pairing controls
  11. 2y agodvirMaintainer handover and small reporting additions
  12. 3y agoepinowcastFix initial conditions for cmdstan 2.32.1 compatibility

Frequently asked questions

What is the difference between dvir and epinowcast?

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

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

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

What are the best alternatives to epinowcast?

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