mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
Comparison · Analytics
finetune vs workflows
A side-by-side editorial comparison of finetune and workflows — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:tidymodels
finetune vs workflows: at a glance
What is finetune?
finetune tracks tune's evolving contracts more than it advances racing itself
finetune provides the racing and simulated-annealing alternatives to grid search in tidymodels. The core algorithms have been stable since 1.0.x; what has changed is everything around them — censored regression support arriving with a tune release, weighted resampling estimates preserved through racing, and a breaking move to named-only optional arguments.
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.
finetune vs workflows: editorial side-by-side
finetune
0.0ANALYTICS
finetune tracks tune's evolving contracts more than it advances racing itself
◆ Current state
finetune provides the racing and simulated-annealing alternatives to grid search in tidymodels. The core algorithms have been stable since 1.0.x; what has changed is everything around them — censored regression support arriving with a tune release, weighted resampling estimates preserved through racing, and a breaking move to named-only optional arguments.
◆ Where it's heading
This is a package operating downstream of tune, adopting whatever the shared resampling machinery grows next rather than proposing new search strategies. The 1.3.0 weighting work is a clear example: tune changed how resampling estimates are computed, and finetune's job was to not lose the weights during racing. Error messages and input checks are the steady internal theme.
◆ Prediction
Expect the next release to absorb whatever tune changes about metric collection or resampling weights; nothing in the entries points to a new search algorithm.
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 finetune 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 finetune or workflows.
mlr3viz
mlr3viz keeps the ecosystem's plots working while the plots themselves move out
mlr3tuning
mlr3tuning is rebuilding its async machinery under a stable public surface
timetk
timetk swallowed anomalize whole, then went quiet for two years
modelbased
modelbased is turning marginal effects into a full contrast grammar
parameters
easystats' parameters package absorbs one more model class every few weeks
See all finetune alternatives → · See all workflows alternatives →
Recent activity from finetune and workflows
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agofinetuneRacing preserves tune's assessment-set weighting
- 11mo agoworkflowsWorkflows gain a postprocessing stage via tailor ⚡
- 1y agofinetuneMaintenance release; magrittr pipe replaced with base pipe
- 1y agoworkflowsSparse matrices work through fit() and predict()
- 2y agofinetuneCensored regression models can be raced and annealed
- 2y agoworkflowsaugment() aligns with parsnip; censored regression supported
- 3y agofinetuneKeep-up release for tune and dplyr; .config alignment fixed
- 3y agoworkflowsRegister tuning generics unconditionally
- 3y agoworkflowsMissing parsnip extensions now error early; unsupervised specs supported
- 3y agofinetuneRacing results filter to fully resampled configurations
- 3y agoworkflowsMode guessing removed; silent offset handling now errors
- 3y agofinetuneInformative error when resamples are too few for racing
Frequently asked questions
What is the difference between finetune and workflows?
Both compete on the same themes — tidymodels — within Analytics. finetune 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 finetune better than workflows?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. finetune 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 finetune?
Top finetune alternatives in Analytics are ranked by recent ship velocity. Browse the "finetune alternatives" section above for the current picks, or visit /alternatives/finetune 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.