← Back to home
Comparison · Analytics

tidyposterior vs workflowsets

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

Shared themes:tidymodelsmodel-comparison

tidyposterior vs workflowsets: at a glance

Featuretidyposteriorworkflowsets
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themestidymodels, bayesian-analysis, model-comparison, maintenance-modetidymodels, model-comparison, clustering, tuning
Last editorial update46m ago1h ago
WebsiteVisit →Visit →

What is tidyposterior?

A finished Bayesian model-comparison package in pure maintenance mode

tidyposterior compares model performance using Bayesian resampling analysis, and it reached its intended shape years ago. Every release since 1.0.0 has been maintenance: a broken test under R-devel, a maintainer email change, and most recently compatibility with an upcoming ggplot2 release plus the base-pipe transition. The substantive API decisions — autoplot() over ggplot() methods, tibble returns from contrast_models() — were settled in the 0.x series.

Read the full tidyposterior trajectory →

What is workflowsets?

workflowsets keeps widening what counts as a model worth comparing.

workflowsets holds a grid of preprocessor and model combinations and evaluates all of them under one call to workflow_map(). The releases in view widen that grid — clustering specifications via tidyclust, censored regression via an eval_time argument, case weights — and fill in the accessors around it with collect_notes(), collect_extracts() and fit_best(). The long-running pull_*() deprecation finally reached the error stage in 1.1.1.

Read the full workflowsets trajectory →

tidyposterior vs workflowsets: editorial side-by-side

T
tidyposterior
ANALYTICS
0.0

A finished Bayesian model-comparison package in pure maintenance mode

◆ Current state

tidyposterior compares model performance using Bayesian resampling analysis, and it reached its intended shape years ago. Every release since 1.0.0 has been maintenance: a broken test under R-devel, a maintainer email change, and most recently compatibility with an upcoming ggplot2 release plus the base-pipe transition. The substantive API decisions — autoplot() over ggplot() methods, tibble returns from contrast_models() — were settled in the 0.x series.

◆ Where it's heading

The package tracks its dependencies rather than developing on its own line, and the dependencies do the moving: rstanarm API changes, dplyr 1.0.0, testthat 3e, ggplot2. Its integration surface widened once, when perf_mod() gained methods for tuning parameter objects from tune, finetune, and workflowsets, and has been stable since. This is what a completed package in an active ecosystem looks like.

◆ Prediction

Expect the next release to be triggered by an upstream change rather than by anything tidyposterior wants to do differently.

W
workflowsets
ANALYTICS
0.0

workflowsets keeps widening what counts as a model worth comparing.

◆ Current state

workflowsets holds a grid of preprocessor and model combinations and evaluates all of them under one call to workflow_map(). The releases in view widen that grid — clustering specifications via tidyclust, censored regression via an eval_time argument, case weights — and fill in the accessors around it with collect_notes(), collect_extracts() and fit_best(). The long-running pull_*() deprecation finally reached the error stage in 1.1.1.

◆ Where it's heading

The package's job is comparison, so its direction is set by what tidymodels can express: every time a new model paradigm lands elsewhere, workflowsets has to learn to rank it. Clustering was the largest of those steps because it has no outcome column to score against. Alongside that runs a slower cleanup — named-only optional arguments, type checking on inputs, informative errors when someone passes a workflow set to fit() — that reads as a package hardening after its API settled.

◆ Prediction

Expect the tailor postprocessors that workflows added in 1.3.0 to need representation here next, since a workflow set that cannot vary the postprocessor cannot compare calibration choices.

Alternatives to tidyposterior and workflowsets

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 tidyposterior or workflowsets.

See all tidyposterior alternatives → · See all workflowsets alternatives →

Recent activity from tidyposterior and workflowsets

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

  1. 1y agotidyposteriortidyposterior 1.0.1.9000 prepares for an upcoming ggplot2 release
  2. 1y agoworkflowsetscollect_extracts() added; pull_*() functions now error
  3. 2y agoworkflowsetsCensored regression evaluation; eval_time breaks positional args
  4. 2y agotidyposteriortidyposterior 1.0.1 fixes a test broken under R-devel
  5. 3y agoworkflowsetsClustering models enter workflow sets via tidyclust
  6. 4y agoworkflowsetsCase weights supported across a workflow set
  7. 4y agotidyposteriortidyposterior 1.0.0 modernizes internals to pivot_longer and testthat 3e
  8. 4y agoworkflowsetsUpdate models and recipes across a set; mixed inputs accepted
  9. 5y agoworkflowsetsextract_*() supersedes pull_*() across tidymodels
  10. 5y agotidyposteriortidyposterior 0.1.0 adds perf_mod() methods for tune and workflowsets
  11. 6y agotidyposteriortidyposterior 0.0.3 returns tibbles and adds a formula override
  12. 7y agotidyposteriortidyposterior 0.0.2 removes example RData files for CRAN

Frequently asked questions

What is the difference between tidyposterior and workflowsets?

Both compete on the same themes — tidymodels, model-comparison — within Analytics. tidyposterior and workflowsets are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is tidyposterior better than workflowsets?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. tidyposterior and workflowsets are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to tidyposterior?

Top tidyposterior alternatives in Analytics are ranked by recent ship velocity. Browse the "tidyposterior alternatives" section above for the current picks, or visit /alternatives/tidyposterior for the full list with editorial commentary on each.

What are the best alternatives to workflowsets?

Top workflowsets alternatives in Analytics are ranked by recent ship velocity. Browse the "workflowsets alternatives" section above for the current picks, or visit /alternatives/workflowsets for the full list with editorial commentary on each.