bittermelon
bittermelon is growing from binary bitmaps toward greyscale and color glyphs
A side-by-side editorial comparison of epiworldR and ichimoku — 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.
A cloud-chart package quietly swapping its dependencies for its maintainer's own libraries.
ichimoku implements Ichimoku Kinko Hyo cloud charts, strategy backtesting and an OANDA data interface for R. Recent releases are almost entirely plumbing: 1.5.7 drops RcppSimdJson in favor of secretbase for JSON parsing, following earlier releases that moved hashing to secretbase and raised the nanonext and mirai floors. The charting and strategy surface has been stable since the 1.5.0 line.
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.
ichimoku implements Ichimoku Kinko Hyo cloud charts, strategy backtesting and an OANDA data interface for R. Recent releases are almost entirely plumbing: 1.5.7 drops RcppSimdJson in favor of secretbase for JSON parsing, following earlier releases that moved hashing to secretbase and raised the nanonext and mirai floors. The charting and strategy surface has been stable since the 1.5.0 line.
The visible arc is consolidation onto the maintainer's own package family — secretbase for hashing and now JSON, nanonext and mirai for concurrency — which steadily removes third-party and Rcpp-based dependencies from the install chain. Feature work is sporadic and narrow when it comes: a faster POSIXct formatter exported as a utility, a multi-session option for the Shiny app, and a fix for asymmetric strategies that failed to emit a final entry signal.
Expect further dependency consolidation as the sibling packages gain capabilities, with ichimoku adopting them shortly after release rather than shipping new charting features.
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 ichimoku.
bittermelon is growing from binary bitmaps toward greyscale and color glyphs
A groundwater database client that has started doing the domain analysis too
A thin R wrapper over Flemish geospatial services, adding one standard at a time
Fluent Bit keeps two lines alive while the 5.x branch quietly opens 5.1.
OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub
rjd3highfreq ships whatever the Java side ships, and only occasionally says what that was.
See all epiworldR alternatives → · See all ichimoku 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 ichimoku 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 ichimoku 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 ichimoku alternatives in Analytics are ranked by recent ship velocity. Browse the "ichimoku alternatives" section above for the current picks, or visit /alternatives/ichimoku for the full list with editorial commentary on each.