dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Comparison · Analytics
tulpa vs weird
A side-by-side editorial comparison of tulpa and weird — release velocity, themes, recent moves, and the top alternatives to consider.
tulpa vs weird: at a glance
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.
What is weird?
weird rebuilt itself on distributional objects, and now the anomaly tooling composes with everything else.
An R package for anomaly detection and unusual-observation diagnostics, at four releases with a long gap between the 2024 patch and the 2026 major line. The current shape is set by 2.0.0, which refactored the package onto distributional objects and renamed its central concept from density_scores() to surprisals(). Since then the work has been filling that structure in: surprisals for more model classes, faster bandwidth and probability calculations, and new visual diagnostics.
tulpa vs weird: editorial side-by-side
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.
weird
0.0ANALYTICS
weird rebuilt itself on distributional objects, and now the anomaly tooling composes with everything else.
◆ Current state
An R package for anomaly detection and unusual-observation diagnostics, at four releases with a long gap between the 2024 patch and the 2026 major line. The current shape is set by 2.0.0, which refactored the package onto distributional objects and renamed its central concept from density_scores() to surprisals(). Since then the work has been filling that structure in: surprisals for more model classes, faster bandwidth and probability calculations, and new visual diagnostics.
◆ Where it's heading
The refactor onto a shared distribution representation is the decision everything else follows from. It let 2.1.0 add hdr() and parameters() methods for kde objects rather than bespoke accessors, and it let 3.0.0 bring in dist_mclust() to turn a Gaussian mixture model into the same object type — so a mixture, a kernel density estimate and a fitted distribution all flow through one interface. The 3.0.0 additions lean visual and multivariate: outlier maps plotting score distance against orthogonal distance, biplot projections with variable axes overlaid, and an augment() method for robust PCA objects. Dependencies have been shed steadily along the way — lookout, interpolation — while mvscale() moved out and then back in.
◆ Prediction
Expect surprisals() coverage to keep extending to further model classes, and the multivariate and robust-PCA diagnostics introduced in 3.0.0 to gain the same distributional-object treatment as the univariate side.
Alternatives to tulpa and weird
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 tulpa or weird.
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.
Recent activity from tulpa and weird
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 17h 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
- 1mo agoweirdOutlier maps, biplot projections, and Gaussian mixtures as distributional objects
- 3mo agoweirdsurprisals() reaches glm objects; lookout dependency dropped
- 6mo agoweirdPackage refactored onto distributional objects; density_scores becomes surprisals
- 2y agoweirdWine reviews dataset replaced with a fetch function
Frequently asked questions
What is the difference between tulpa and weird?
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 tulpa better than weird?
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 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.
What are the best alternatives to weird?
Top weird alternatives in Analytics are ranked by recent ship velocity. Browse the "weird alternatives" section above for the current picks, or visit /alternatives/weird-r for the full list with editorial commentary on each.