Chord
Chord's assistant can now write to the team's knowledge base, not just read from it.
A side-by-side editorial comparison of cfrnow and epiflows — release velocity, themes, recent moves, and the top alternatives to consider.
A Bayesian real-time CFR estimator that now ships stratified fits and posterior-predictive checks
cfrnow estimates case fatality ratios from line-list data while an outbreak is still running, using a Bayesian mixture-cure survival model registered as an `epidist` model type. Three releases in a month took it from first public release to stratified, partially-pooled fits with posterior-predictive checking. It leans on `distspec` for delay parameterisation, which reached CRAN alongside the 0.2.1 patch.
epiflows has shipped four releases in eight years, none of which changed the code.
epiflows predicts the spread of infectious disease along population flows between locations, and it is effectively dormant. The whole visible history spans 2018 to 2026 in four entries: the first CRAN release, a Zenodo archival tag, a Roxygen patch whose notes state the functionality is unchanged, and a 2026 release replacing deprecated ggplot2 and tibble calls. No entry describes new epidemiological capability.
cfrnow estimates case fatality ratios from line-list data while an outbreak is still running, using a Bayesian mixture-cure survival model registered as an `epidist` model type. Three releases in a month took it from first public release to stratified, partially-pooled fits with posterior-predictive checking. It leans on `distspec` for delay parameterisation, which reached CRAN alongside the 0.2.1 patch.
The arc runs from producing a single corrected CFR number toward supporting a full model-checking workflow. 0.2.0 added the pieces a modeller needs to defend an estimate: replicate line lists replayed through the real-time truncation, an ascertainment-ratio correction for when fatal and non-fatal cases enter the line list at different rates, and per-group CFRs from `brms` formulas. Delay coverage widened from LogNormal and Gamma to Weibull in the same release.
Expect the next release to keep widening covariate and pooling support rather than adding new outcome types, since every 0.2.0 addition extended the existing formula interface instead of replacing it.
epiflows predicts the spread of infectious disease along population flows between locations, and it is effectively dormant. The whole visible history spans 2018 to 2026 in four entries: the first CRAN release, a Zenodo archival tag, a Roxygen patch whose notes state the functionality is unchanged, and a 2026 release replacing deprecated ggplot2 and tibble calls. No entry describes new epidemiological capability.
The package is being kept installable rather than developed. The one recent release is dependency maintenance contributed from outside, which is the pattern for RECON-era epidemiology packages that have outlived their original project funding. Two separate entries are both labelled version 0.2.1, so even the version history is not a reliable guide to what changed.
Any further releases will most likely be more deprecation cleanup to keep the package on CRAN; there is nothing in the record suggesting active development has resumed.
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 cfrnow or epiflows.
Chord's assistant can now write to the team's knowledge base, not just read from it.
tidytransit tracks the GTFS spec as it grows, one reader and one router feature at a time.
A tiny grid renderer for oblique-projection cubes, complete since its first release.
BioCro swapped an unstable iteration for real root finders, changing what its crop models compute.
redist keeps rewriting the sampler underneath a district-drawing API it has held stable since 4.0.
The LPJmL toolkit finally reads NetCDF, closing a gap against the format its field uses.
See all cfrnow alternatives → · See all epiflows alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — epidemiology — within Analytics. cfrnow is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. cfrnow is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top cfrnow alternatives in Analytics are ranked by recent ship velocity. Browse the "cfrnow alternatives" section above for the current picks, or visit /alternatives/cfrnow for the full list with editorial commentary on each.
Top epiflows alternatives in Analytics are ranked by recent ship velocity. Browse the "epiflows alternatives" section above for the current picks, or visit /alternatives/epiflows-r for the full list with editorial commentary on each.