n2kanalysis
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
A side-by-side editorial comparison of ichimoku and modeltime.ensemble — release velocity, themes, recent moves, and the top alternatives to consider.
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.
modeltime.ensemble wakes after four years, and the work is all tune 2.0 compatibility.
modeltime.ensemble builds average, weighted and stacked ensembles over modeltime forecast models. After a four-year gap it shipped twice in a fortnight during August and September 2025, both releases devoted to tracking breaking changes in tidymodels' tune package — new resampling column conventions, key uniqueness across resamples, recipe preparation. The tidyverse dependency was dropped in the same pass.
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.
modeltime.ensemble builds average, weighted and stacked ensembles over modeltime forecast models. After a four-year gap it shipped twice in a fortnight during August and September 2025, both releases devoted to tracking breaking changes in tidymodels' tune package — new resampling column conventions, key uniqueness across resamples, recipe preparation. The tidyverse dependency was dropped in the same pass.
This is a package whose forecasting capability was settled by 2021 — recursive ensembles, per-series calibration — and whose recent life is dictated entirely by upstream tidymodels churn. New contributors did that compatibility work, including one from the tidymodels side. It now requires tune 2.0.0 and modeltime.resample 0.3.0, pinning it to the current tidymodels generation rather than straddling versions.
Expect the next release to follow the next tune or modeltime.resample breaking change rather than to introduce new ensembling methods.
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 ichimoku or modeltime.ensemble.
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
A Fortran-descended optimizer got thread-safe, then found two flags that never worked.
ggstatsplot reached 1.0 by adding tests, having outsourced its statistics years ago.
collapse got a JSS paper and a 7x fmean speedup in the same release.
gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.
broadcast is filling in NumPy-style array broadcasting for R, operator by operator.
See all ichimoku alternatives → · See all modeltime.ensemble alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ichimoku and modeltime.ensemble 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. ichimoku and modeltime.ensemble 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 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.
Top modeltime.ensemble alternatives in Analytics are ranked by recent ship velocity. Browse the "modeltime.ensemble alternatives" section above for the current picks, or visit /alternatives/modeltime-ensemble for the full list with editorial commentary on each.