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 epiworldR and tidypolars — release velocity, themes, recent moves, and the top alternatives to consider.
epiworldR is a thin R shell whose releases track the C++ simulator underneath it
Almost every release here is a version bump of the underlying epiworld C++ library, wrapped and pushed to CRAN. The substantive R-side work is narrow and consistent: exposing simulation outputs that were already computed but not reachable from R — outbreak size, active cases, hospitalizations and their savers. The newest release addresses an AddressSanitizer finding, which is the kind of thing CRAN checks surface on a compiled package.
tidypolars is grinding toward complete dplyr coverage, one supported function at a time
tidypolars lets you write dplyr and tidyr syntax against Polars DataFrames and LazyFrames. Its releases follow a fixed shape: raise the required polars version, add a handful of newly supported R functions and arguments, fix places where behaviour diverges from dplyr. Recent additions run from %notin% and as.integer() to .before/.after in mutate() and time zone handling in datetime parsing. Cadence is roughly every six to ten weeks and has not varied.
Almost every release here is a version bump of the underlying epiworld C++ library, wrapped and pushed to CRAN. The substantive R-side work is narrow and consistent: exposing simulation outputs that were already computed but not reachable from R — outbreak size, active cases, hospitalizations and their savers. The newest release addresses an AddressSanitizer finding, which is the kind of thing CRAN checks surface on a compiled package.
The R package's job is staying current with the simulator and satisfying CRAN, not evolving its own interface. What direction it has shows in which model outputs get exposed next, and in a steady tidy-up of the build — the custom configure script was dropped in favour of R's built-in C++17 and OpenMP settings, and test coverage has been filled in across several releases with automated assistance.
Expect the next release to track another epiworld version bump, with any R-side addition most likely being one more exposed metric or saver, following the pattern of get_hospitalizations and get_outbreak_size.
tidypolars lets you write dplyr and tidyr syntax against Polars DataFrames and LazyFrames. Its releases follow a fixed shape: raise the required polars version, add a handful of newly supported R functions and arguments, fix places where behaviour diverges from dplyr. Recent additions run from %notin% and as.integer() to .before/.after in mutate() and time zone handling in datetime parsing. Cadence is roughly every six to ten weeks and has not varied.
Coverage is the whole strategy, and the target has been widening from dplyr into tidyr — unnest_longer_polars(), separate_longer_delim_polars() and separate_longer_position_polars() bring list-column and string-splitting verbs that have no Polars-idiomatic equivalent in the tidyverse dialect. The other consistent thread is fidelity: distinct() dropping unselected columns, summarize() dropping the last group, relocate() honouring tidy-select helpers, NULL in mutate() behaving as dplyr does. Each of these is a small breaking change made to match the reference rather than to differ from it.
The pattern of tracking the polars floor upward every release and following tidyverse changes closely — .by in fill() arrived when tidyr 1.3.2 shipped it — suggests the next releases continue mirroring new dplyr and tidyr arguments rather than adding a distinct capability.
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 epiworldR or tidypolars.
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.
epiflows has shipped four releases in eight years, none of which changed the code.
See all epiworldR alternatives → · See all tidypolars alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. epiworldR and tidypolars 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. epiworldR and tidypolars 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 epiworldR alternatives in Analytics are ranked by recent ship velocity. Browse the "epiworldR alternatives" section above for the current picks, or visit /alternatives/epiworldr for the full list with editorial commentary on each.
Top tidypolars alternatives in Analytics are ranked by recent ship velocity. Browse the "tidypolars alternatives" section above for the current picks, or visit /alternatives/tidypolars for the full list with editorial commentary on each.