dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Comparison · Analytics
ggdemetra vs tulpa
A side-by-side editorial comparison of ggdemetra and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
ggdemetra vs tulpa: at a glance
What is ggdemetra?
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
ggdemetra is a thin, focused bridge: it puts RJDemetra's seasonal adjustment results — TRAMO-SEATS and X-13 models — into ggplot2 geoms and autoplot methods. Development runs in short bursts separated by long quiet stretches, and the most recent work has been correcting SI ratio handling rather than adding surface. The API is small enough that a single function rename counts as the notable change in a release.
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.
ggdemetra vs tulpa: editorial side-by-side
ggdemetra
0.0ANALYTICS
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
◆ Current state
ggdemetra is a thin, focused bridge: it puts RJDemetra's seasonal adjustment results — TRAMO-SEATS and X-13 models — into ggplot2 geoms and autoplot methods. Development runs in short bursts separated by long quiet stretches, and the most recent work has been correcting SI ratio handling rather than adding surface. The API is small enough that a single function rename counts as the notable change in a release.
◆ Where it's heading
The package has been steadily completing its coverage of the seasonal adjustment output surface: component extractors and autoplot methods in 0.2.3, SI ratio plotting in 0.2.5, then two releases of corrections to make SI ratios behave under TRAMO-SEATS jSA models and when no seasonal component is exported. Alongside that, the naming is being tidied — y_forecast() became raw(), and init_ggplot() shortened the setup boilerplate. This reads as a package approaching the edge of its intended scope and spending its effort on correctness.
◆ Prediction
Two consecutive releases fixing SI ratios under TRAMO-SEATS suggest that code path is the least settled part of the package, so further corrections there are the most likely next move. The entries give no indication of new model families or plot types being planned.
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 ggdemetra 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 ggdemetra or tulpa.
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.
AgencyAnalytics
AgencyAI got skills three weeks ago; everything since has been making them routine.
NocoDB
Interfaces gets the permissions layer it needed, one release after launching.
See all ggdemetra alternatives → · See all tulpa alternatives →
Recent activity from ggdemetra and tulpa
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 18h 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
- 2y agoggdemetrasiratio() fix when TRAMO-SEATS exports no seasonal component
- 2y agoggdemetraraw() replaces y_forecast(); new init_ggplot() helper
- 2y agoggdemetraRe-tagged moments later as 0.2.7
- 3y agoggdemetraSI ratio plotting functions land
- 5y agoggdemetrats2df() conversion helper and geom_outlier date fix
- 6y agoggdemetrageom_arima no longer recomputes the model
Frequently asked questions
What is the difference between ggdemetra 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 ggdemetra 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 ggdemetra?
Top ggdemetra alternatives in Analytics are ranked by recent ship velocity. Browse the "ggdemetra alternatives" section above for the current picks, or visit /alternatives/ggdemetra 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.