rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of epiflows and redist — release velocity, themes, recent moves, and the top alternatives to consider.
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.
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.
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.
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.
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.
Expect the remaining single-threaded algorithms to gain the chains-style parallelism that flip just received, following the pattern SMC established several releases ago.
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 epiflows or redist.
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
A statistician's personal toolbox, growing one plotting utility at a time
R/qtl is in pure custodial mode: every recent release answers a compiler, not a user
See all epiflows alternatives → · See all redist alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r — within Analytics. epiflows 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. epiflows 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.
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.
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.