tidytext
Finished, widely taught, and shipping roxygen fixes.
Comparison · Analytics
dials vs workflowsets
A side-by-side editorial comparison of dials and workflowsets — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:tidymodels
dials vs workflowsets: at a glance
What is dials?
dials is quietly registering the tuning parameters for tidymodels' deep-learning push
dials defines the parameter objects and grid constructors that tidymodels tunes over, which makes its release notes a reliable early read on what the rest of the stack is about to support. The last two releases are dominated by attention-model parameters — SAINT and tabular deep learning via brulee, TabPFN via parsnip's tab_pfn() — alongside catboost parameters for bonsai and calibration parameters for tailor.
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.
dials vs workflowsets: editorial side-by-side
dials
0.0ANALYTICS
dials is quietly registering the tuning parameters for tidymodels' deep-learning push
◆ Current state
dials defines the parameter objects and grid constructors that tidymodels tunes over, which makes its release notes a reliable early read on what the rest of the stack is about to support. The last two releases are dominated by attention-model parameters — SAINT and tabular deep learning via brulee, TabPFN via parsnip's tab_pfn() — alongside catboost parameters for bonsai and calibration parameters for tailor.
◆ Where it's heading
The grid machinery itself is settled: grid_space_filling() consolidated the older designs, and the grid_*() functions now error rather than warn on the wrong size argument. What keeps moving is the parameter catalog, and it is moving toward neural and foundation-model territory that tidymodels historically left alone. Error-message quality is a steady secondary theme.
◆ Prediction
Expect further parameter objects to land ahead of the parsnip and brulee releases that use them — the attention and tabular-foundation-model work in flight is the clearest thing the entries point to.
workflowsets
0.0ANALYTICS
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 dials 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 dials or workflowsets.
textrecipes
Text features finally stay sparse all the way to the model.
probably
The package that made calibration a step instead of an afterthought.
workflows
The tidymodels pipeline grew a third stage, and it happens after the model runs.
vetiver
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
patchwork
patchwork stopped being a ggplot composer and became a page composer.
See all dials alternatives → · See all workflowsets alternatives →
Recent activity from dials and workflowsets
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agodialsAttention and tabular deep-learning parameters for brulee models
- 4mo agodialsParameters for ordinal_reg() and the tab_pfn() foundation model
- 11mo agodialsprop_terms() for supervised feature selection recipes
- 1y agodialsCalibration method parameters for classification and regression
- 1y agoworkflowsetscollect_extracts() added; pull_*() functions now error
- 1y agodialsPostprocessing parameters added; grid size mismatches now error
- 2y agodialsgrid_space_filling() consolidates the space-filling designs
- 2y agoworkflowsetsCensored regression evaluation; eval_time breaks positional args
- 3y agoworkflowsetsClustering models enter workflow sets via tidyclust ⚡
- 4y agoworkflowsetsCase weights supported across a workflow set
- 4y agoworkflowsetsUpdate models and recipes across a set; mixed inputs accepted
- 5y agoworkflowsetsextract_*() supersedes pull_*() across tidymodels
Frequently asked questions
What is the difference between dials and workflowsets?
Both compete on the same themes — tidymodels — within Analytics. dials 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 dials better than workflowsets?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dials 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 dials?
Top dials alternatives in Analytics are ranked by recent ship velocity. Browse the "dials alternatives" section above for the current picks, or visit /alternatives/dials 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.