animation
Contribution-driven maintenance on a package whose last structural change was magick support.
A side-by-side editorial comparison of finetune and tune — release velocity, themes, recent moves, and the top alternatives to consider.
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.
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
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.
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.
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.
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
Two migrations run through this timeline. The tunable surface keeps widening - first censored regression as a mode, then postprocessors via tailor - so that a candidate is now a preprocessor, model and postprocessor triple rather than just a model. The parallel story has moved from foreach to future and now to mirai, each step deprecating the last. Neither is finished.
Expect the foreach path to be removed outright, and the postprocessing surface to grow as tailor gains more steps; the GauPro switch will likely need follow-up as its behavior differs from the old engine.
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 tune.
Contribution-driven maintenance on a package whose last structural change was magick support.
pins keeps adding a storage backend per release while retiring its original API
tsibble shipped one release in five and a half years - the data structure is finished
yardstick made fairness metrics a first-class part of tidymodels evaluation
leaflet relicensed to MIT and finished migrating off R's retired spatial stack
ggpubr reached 1.0.0 with p-value formatting presets for specific journals
See all finetune alternatives → · See all tune alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — tidymodels, hyperparameter-tuning — within Analytics. finetune and tune 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. finetune and tune 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.
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.
Top tune alternatives in Analytics are ranked by recent ship velocity. Browse the "tune alternatives" section above for the current picks, or visit /alternatives/tune for the full list with editorial commentary on each.