tibblify
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
A side-by-side editorial comparison of dvir and epinowcast — release velocity, themes, recent moves, and the top alternatives to consider.
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.
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.
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.
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.
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.
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.
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.
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.
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.
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
StreamCatTools is quietly moving off web services and onto cloud-native GeoParquet
reproducible added a windowed read path so remote GeoTiffs never fully download
qcTAF is building an automated checklist for reproducible fisheries assessments, one criterion at a time
After three dormant years, rpymat returned to fix the OpenMP crash that breaks R and conda together
See all dvir alternatives → · See all epinowcast alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
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.
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.