Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
Comparison · Analytics
ichimoku vs tulpa
A side-by-side editorial comparison of ichimoku and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
ichimoku vs tulpa: at a glance
What is ichimoku?
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.
What is tulpa?
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.
ichimoku vs tulpa: editorial side-by-side
ichimoku
0.0ANALYTICS
A cloud-chart package quietly swapping its dependencies for its maintainer's own libraries.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
Expect further dependency consolidation as the sibling packages gain capabilities, with ichimoku adopting them shortly after release rather than shipping new charting features.
tulpa
7.5ANALYTICS
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
◆ Current state
tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.
◆ Where it's heading
Two moves in nine days point at the same destination: the generics conversion made tulpa extensible by downstream packages, and CRAN admission makes it installable by them. The current cadence — several tags a week, some existing only to record a measurement that produced no code change — does not survive CRAN's submission overhead, so the release rhythm has to slow whether or not the project intends it. The correctness work still clusters on the joint nested-Laplace driver, and 0.1.0 extends the same diagnostics habit with .NL_AXIS_SD_REASONS, a closed vocabulary for an outer axis whose grid does not contain its own posterior mode.
◆ Prediction
Expect tulpaObs to follow tulpa onto CRAN, since it is the consumer whose registrations the engine has spent this window unblocking, and expect the version line to move in larger, less frequent steps now that each one carries a submission.
Alternatives to ichimoku and tulpa
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 tulpa.
RStudio
RStudio ships through release branches, and the notes are commit messages
dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
See all ichimoku alternatives → · See all tulpa alternatives →
Recent activity from ichimoku and tulpa
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 20h agotulpaFirst CRAN release: engine surface unchanged from 0.0.198 ⚡
- 4d agotulpatulpa_re_aghq() exposes the mode/theta cross-Hessian
- 8d agotulpaDense batched joint path could silently drop a grid cell
- 8d agotulpaCalibration and goodness-of-fit entry points become S3 generics ⚡
- 9d agotulpaCUDA backend had two definitions; link order decided if it ran
- 9d agotulpaHyperparameter bounds now flag when they leave the node range
- 2mo agoichimokuJSON parsing moves from RcppSimdJson to secretbase
- 1y agoichimokuFaster POSIXct formatting exported as a utility
- 1y agoichimokuMultiple concurrent sessions in the OANDA Shiny app
- 2y agoichimokuAsymmetric strategies now emit their final entry signal
- 2y agoichimokusecretbase floor raised to 1.0.0
- 2y agoichimokuArchive verification reverts to SHA256
Frequently asked questions
What is the difference between ichimoku and tulpa?
They serve adjacent needs but don't currently overlap on shipped themes. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is ichimoku better than tulpa?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to ichimoku?
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.
What are the best alternatives to tulpa?
Top tulpa alternatives in Analytics are ranked by recent ship velocity. Browse the "tulpa alternatives" section above for the current picks, or visit /alternatives/tulpa for the full list with editorial commentary on each.