mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
Comparison · Analytics
finetune vs mlr3tuning
A side-by-side editorial comparison of finetune and mlr3tuning — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:hyperparameter-tuning
finetune vs mlr3tuning: 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 mlr3tuning?
mlr3tuning is rebuilding its async machinery under a stable public surface
mlr3tuning provides hyperparameter optimization for the mlr3 ecosystem, and its recent history is dominated by the asynchronous tuning path: archive freezing, callback stages around queue evaluation, and version-locked compatibility with the rush backend. Releases pair a small feature with several fixes and an explicit compatibility line naming the mlr3 or rush version they track. The most recent release drops all workarounds for older rush versions, which suggests that dependency has stabilized enough to require rather than accommodate.
finetune vs mlr3tuning: 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.
mlr3tuning
2.5ANALYTICS
mlr3tuning is rebuilding its async machinery under a stable public surface
◆ Current state
mlr3tuning provides hyperparameter optimization for the mlr3 ecosystem, and its recent history is dominated by the asynchronous tuning path: archive freezing, callback stages around queue evaluation, and version-locked compatibility with the rush backend. Releases pair a small feature with several fixes and an explicit compatibility line naming the mlr3 or rush version they track. The most recent release drops all workarounds for older rush versions, which suggests that dependency has stabilized enough to require rather than accommodate.
◆ Where it's heading
Two things are being tidied at once. The async archive is converging on a consistent data.table representation across batch and async variants, so results are shaped the same regardless of how tuning ran. Separately, the package is becoming a better ecosystem citizen — unioning tuner properties on load instead of overwriting them, removing its callbacks on unload, and raising informative errors from AutoTuner accessors on an untrained model. Both are the marks of a package used as a dependency more than as a destination.
◆ Prediction
With rush pinned to 1.2.0 and the compatibility shims gone, the next release is likely to expose more of the async path through callbacks rather than change the tuning interface.
Alternatives to finetune and mlr3tuning
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 mlr3tuning.
mlr3viz
mlr3viz keeps the ecosystem's plots working while the plots themselves move out
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
tidyposterior
A finished Bayesian model-comparison package in pure maintenance mode
See all finetune alternatives → · See all mlr3tuning alternatives →
Recent activity from finetune and mlr3tuning
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 18d agomlr3tuningmlr3tuning 1.6.1 stops clobbering other packages' tuner properties
- 3mo agofinetuneRacing preserves tune's assessment-set weighting
- 4mo agomlr3tuningmlr3tuning 1.6.0 aligns archive column order across tuning classes
- 8mo agomlr3tuningmlr3tuning 1.5.1 tracks xgboost 3.1.2.1
- 8mo agomlr3tuningmlr3tuning 1.5.0 adds queue evaluation stages to async callbacks
- 1y agomlr3tuningmlr3tuning 1.4.0 unifies logging under a base mlr3 logger
- 1y agofinetuneMaintenance release; magrittr pipe replaced with base pipe
- 1y agomlr3tuningmlr3tuning 1.3.0 adds a frozen async archive and leaner worker storage
- 2y agofinetuneCensored regression models can be raced and annealed
- 3y agofinetuneKeep-up release for tune and dplyr; .config alignment fixed
- 3y agofinetuneRacing results filter to fully resampled configurations
- 3y agofinetuneInformative error when resamples are too few for racing
Frequently asked questions
What is the difference between finetune and mlr3tuning?
Both compete on the same themes — hyperparameter-tuning — within Analytics. mlr3tuning is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 finetune better than mlr3tuning?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mlr3tuning is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 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 mlr3tuning?
Top mlr3tuning alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3tuning alternatives" section above for the current picks, or visit /alternatives/mlr3tuning for the full list with editorial commentary on each.