tidytext
Finished, widely taught, and shipping roxygen fixes.
Comparison · Analytics
dials vs workflows
A side-by-side editorial comparison of dials and workflows — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:tidymodels
dials vs workflows: 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 workflows?
The tidymodels pipeline grew a third stage, and it happens after the model runs.
workflows bundles a preprocessor and a model into one object that tidymodels can fit, tune and extract from. Version 1.3.0 added a post stage backed by the tailor package, wired through every generic a workflow supports — augment, tidy, tunable, tune_args, required_pkgs and parameter extraction. Version 1.2.0 added sparse data support so fit() and predict() accept dgCMatrix and sparse tibbles. Earlier releases in view are boundary tightening: erroring on unknown model modes, on trained recipes, and on silently ignored formula offsets.
dials vs workflows: 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.
workflows
0.0ANALYTICS
The tidymodels pipeline grew a third stage, and it happens after the model runs.
◆ Current state
workflows bundles a preprocessor and a model into one object that tidymodels can fit, tune and extract from. Version 1.3.0 added a post stage backed by the tailor package, wired through every generic a workflow supports — augment, tidy, tunable, tune_args, required_pkgs and parameter extraction. Version 1.2.0 added sparse data support so fit() and predict() accept dgCMatrix and sparse tibbles. Earlier releases in view are boundary tightening: erroring on unknown model modes, on trained recipes, and on silently ignored formula offsets.
◆ Where it's heading
The object is filling out into a complete pipeline description rather than a preprocessing-plus-model pair. Postprocessing is the structural addition — calibration and threshold selection were previously done by hand after prediction, outside anything tidymodels could tune or record — and the fact that it arrived integrated with tunable() and tune_args() rather than as a standalone step is the point. The rest of the arc is the steady tidymodels habit of converting silent guesses into errors.
◆ Prediction
Expect tailor postprocessors to spread through tune and workflowsets next, since the parameter and tuning generics were wired up first, and expect sparse support to extend to more engines after lightgbm.
Alternatives to dials and workflows
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 workflows.
textrecipes
Text features finally stay sparse all the way to the model.
probably
The package that made calibration a step instead of an afterthought.
workflowsets
workflowsets keeps widening what counts as a model worth comparing.
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 workflows alternatives →
Recent activity from dials and workflows
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
- 11mo agoworkflowsWorkflows gain a postprocessing stage via tailor ⚡
- 1y agodialsCalibration method parameters for classification and regression
- 1y agoworkflowsSparse matrices work through fit() and predict()
- 1y agodialsPostprocessing parameters added; grid size mismatches now error
- 2y agodialsgrid_space_filling() consolidates the space-filling designs
- 2y agoworkflowsaugment() aligns with parsnip; censored regression supported
- 3y agoworkflowsRegister tuning generics unconditionally
- 3y agoworkflowsMissing parsnip extensions now error early; unsupervised specs supported
- 3y agoworkflowsMode guessing removed; silent offset handling now errors
Frequently asked questions
What is the difference between dials and workflows?
Both compete on the same themes — tidymodels — within Analytics. dials and workflows 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 workflows?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dials and workflows 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 workflows?
Top workflows alternatives in Analytics are ranked by recent ship velocity. Browse the "workflows alternatives" section above for the current picks, or visit /alternatives/workflows-r for the full list with editorial commentary on each.