rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of epiflows and rjwsacruncher — 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.
A thin R wrapper around a Java seasonal-adjustment tool, slowly absorbing the setup work.
rjwsacruncher drives JDemetra+'s JWSACruncher from R, handling parameter files and batch runs of seasonal adjustment workspaces. Recent releases have shifted from wrapping the executable to managing its installation: 0.2.3 adds a downloader for JDemetra+ itself, a check that a given directory really contains the cruncher binary, and tolerance for users pointing at the executable instead of its bin directory.
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.
rjwsacruncher drives JDemetra+'s JWSACruncher from R, handling parameter files and batch runs of seasonal adjustment workspaces. Recent releases have shifted from wrapping the executable to managing its installation: 0.2.3 adds a downloader for JDemetra+ itself, a check that a given directory really contains the cruncher binary, and tolerance for users pointing at the executable instead of its bin directory.
The work is defensive. Most of each release addresses a way users misconfigure paths or versions — clearer errors, a startup message naming which cruncher version the options select, and a standalone flag on the downloader. The package is absorbing the friction of a Java dependency it does not control.
Expect continued compatibility work as JDemetra+ 3.x diverges from 2.x, since the version split is already surfaced as a user-facing option rather than resolved internally.
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 rjwsacruncher.
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 rjwsacruncher alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r — within Analytics. epiflows and rjwsacruncher 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 rjwsacruncher 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 rjwsacruncher alternatives in Analytics are ranked by recent ship velocity. Browse the "rjwsacruncher alternatives" section above for the current picks, or visit /alternatives/rjwsacruncher for the full list with editorial commentary on each.