Delta Lake
A 4.4.0 tag appears, but the feed carries only its release plumbing
Comparison · Analytics
hstats vs tulpa
A side-by-side editorial comparison of hstats and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
hstats vs tulpa: at a glance
What is hstats?
hstats settled into maintenance after its 1.0 restructuring, with model coverage the only thing still growing.
hstats computes Friedman's H-statistics, partial dependence, ICE curves and permutation importance for any model exposing a prediction function. The releases in view are consolidation: performance work on plain data.frames, ICE facetting for multioutput models, ranger survival support, and a ggplot 4.0 compatibility pass in 2025. The package moved to the ModelOriented organisation in 1.2.0.
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.
hstats vs tulpa: editorial side-by-side
hstats
0.0ANALYTICS
hstats settled into maintenance after its 1.0 restructuring, with model coverage the only thing still growing.
◆ Current state
hstats computes Friedman's H-statistics, partial dependence, ICE curves and permutation importance for any model exposing a prediction function. The releases in view are consolidation: performance work on plain data.frames, ICE facetting for multioutput models, ranger survival support, and a ggplot 4.0 compatibility pass in 2025. The package moved to the ModelOriented organisation in 1.2.0.
◆ Where it's heading
The structural work — the hstats_matrix object, quantile approximation, revised plotting — landed in 1.0.0 just outside this window, and nothing since has changed the package's shape. What continues is model-coverage plumbing: mlr3 classification modes, ranger survival behind a survival argument, and factor predictions added in 1.1.0 then removed again in 1.2.0. The most recent releases are compatibility-driven, tracking ggplot2 rather than the interaction statistics.
◆ Prediction
Expect the next release to be another dependency-compatibility pass or a new model backend working out of the box, rather than new interaction statistics.
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 hstats 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 hstats or tulpa.
distributions3
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
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.
See all hstats alternatives → · See all tulpa alternatives →
Recent activity from hstats and tulpa
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d 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
- 10mo agohstatsggplot 4.0 compatibility and test coverage
- 2y agohstatsranger survival models supported out of the box
- 2y agohstatsMoves to ModelOriented; factor predictions removed
- 2y agohstatsICE facets for multioutput models; mlr3 fixes
- 2y agohstatsFaster data.frame paths; NaN H-statistics fixed
- 2y agohstatsFactor predictions and line-style 2D partial dependence
Frequently asked questions
What is the difference between hstats 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 hstats 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 hstats?
Top hstats alternatives in Analytics are ranked by recent ship velocity. Browse the "hstats alternatives" section above for the current picks, or visit /alternatives/hstats 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.