← Back to home
Comparison · Analytics

tidyclust vs tulpa

A side-by-side editorial comparison of tidyclust and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.

tidyclust vs tulpa: at a glance

Featuretidyclusttulpa
SectorAnalyticsAnalytics
Velocity score0.07.5
Sparks · 30d02
Top themestidyclust, clustering, tidymodels, dbscanbayesian-inference, cran-release, r-packages, spatial-modeling
Last editorial update6d ago8h ago
WebsiteVisit →Visit →

What is tidyclust?

tidyclust just tripled the model types it can fit, and handed finalization back to tune

tidyclust brings clustering into the tidymodels interface, and 0.3.0 was the release where its model coverage stopped being k-means and hierarchical clustering. DBSCAN and HDBSCAN, Gaussian mixtures, and mean shift all arrived at once as proper clustering specifications. The two releases since have been bug fixes on the metric and sparse-data paths, which is the usual pattern after a large surface addition.

Read the full tidyclust trajectory →

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.

Read the full tulpa trajectory →

tidyclust vs tulpa: editorial side-by-side

T
tidyclust
ANALYTICS
0.0

tidyclust just tripled the model types it can fit, and handed finalization back to tune

◆ Current state

tidyclust brings clustering into the tidymodels interface, and 0.3.0 was the release where its model coverage stopped being k-means and hierarchical clustering. DBSCAN and HDBSCAN, Gaussian mixtures, and mean shift all arrived at once as proper clustering specifications. The two releases since have been bug fixes on the metric and sparse-data paths, which is the usual pattern after a large surface addition.

◆ Where it's heading

The package is converging with the rest of tidymodels rather than maintaining a parallel API: finalize_model_tidyclust() and finalize_workflow_tidyclust() are deprecated because tune::finalize_model() and tune::finalize_workflow() now handle cluster_spec objects natively. That removes the last place where clustering needed its own version of a shared verb. With density-based and model-based clustering now present, the interface has to cover model families with genuinely different assumptions than the centroid methods it started with.

◆ Prediction

The recent fixes to cluster_metric_set() labeling and custom-metric authoring suggest evaluation is the current focus, so metrics suited to density-based clusters are the likely next addition.

T
tulpa
ANALYTICS
7.5

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 tidyclust 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 tidyclust or tulpa.

See all tidyclust alternatives → · See all tulpa alternatives →

Recent activity from tidyclust and tulpa

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 17h agotulpaFirst CRAN release: engine surface unchanged from 0.0.198
  2. 4d agotulpatulpa_re_aghq() exposes the mode/theta cross-Hessian
  3. 8d agotulpaDense batched joint path could silently drop a grid cell
  4. 8d agotulpaCalibration and goodness-of-fit entry points become S3 generics
  5. 9d agotulpaCUDA backend had two definitions; link order decided if it ran
  6. 9d agotulpaHyperparameter bounds now flag when they leave the node range
  7. 1mo agotidyclusttidyclust 0.3.2 fixes k_means() on sparse predictors
  8. 1mo agotidyclusttidyclust 0.3.1 stops same-named metrics silently merging
  9. 3mo agotidyclusttidyclust 0.3.0 adds DBSCAN, Gaussian mixture, and mean shift models
  10. 1y agotidyclusttidyclust 0.2.4 switches distance calculations to philentropy
  11. 2y agotidyclusttidyclust 0.2.3 resolves a clustMixType reverse-dependency issue
  12. 2y agotidyclusttidyclust 0.2.2 resolves a ClusterR reverse-dependency issue

Frequently asked questions

What is the difference between tidyclust 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 tidyclust 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 tidyclust?

Top tidyclust alternatives in Analytics are ranked by recent ship velocity. Browse the "tidyclust alternatives" section above for the current picks, or visit /alternatives/tidyclust 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.