mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
Comparison · Analytics
finetune vs probably
A side-by-side editorial comparison of finetune and probably — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:tidymodels
finetune vs probably: 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 probably?
The package that made calibration a step instead of an afterthought.
probably started as a small utility for class predictions and equivocal zones, and version 1.0.0 turned it into tidymodels' calibration and uncertainty package: cal_plot_*, cal_estimate_*, cal_validate_* and cal_apply across binary, multiclass and regression problems, plus conformal prediction intervals. Since then the work has been consolidation — a large internal refactor with no API change, split conformal and conformal quantile regression, bound_prediction(), and required_pkgs() and butcher methods so conformal objects can be deployed and stripped.
finetune vs probably: 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.
probably
0.0ANALYTICS
The package that made calibration a step instead of an afterthought.
◆ Current state
probably started as a small utility for class predictions and equivocal zones, and version 1.0.0 turned it into tidymodels' calibration and uncertainty package: cal_plot_*, cal_estimate_*, cal_validate_* and cal_apply across binary, multiclass and regression problems, plus conformal prediction intervals. Since then the work has been consolidation — a large internal refactor with no API change, split conformal and conformal quantile regression, bound_prediction(), and required_pkgs() and butcher methods so conformal objects can be deployed and stripped.
◆ Where it's heading
The recent releases are about making these objects survive leaving the session. butcher and required_pkgs() methods are what a model needs to be pinned, containerised and served, and their arrival alongside workflows adding a tailor postprocessing stage and vetiver adding probably support points the same way: calibration is being moved out of analysis scripts and into the deployed pipeline. The cal_*_none() reference implementations are the tell that calibration is now something people tune rather than apply once.
◆ Prediction
Expect the calibration functions to be reachable directly from a tuned workflow's postprocessing stage rather than applied to predictions afterwards, following the tailor integration that workflows just shipped.
Alternatives to finetune and probably
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 probably.
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 probably alternatives →
Recent activity from finetune and probably
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agofinetuneRacing preserves tune's assessment-set weighting
- 10mo agoprobablyConformal objects gain required_pkgs() and butcher methods
- 1y agoprobablyggplot2 test updates and a clearer validation-set error
- 1y agoprobablyCalibration internals refactored; isotonic bootstrap bug fixed
- 1y agofinetuneMaintenance release; magrittr pipe replaced with base pipe
- 2y agofinetuneCensored regression models can be raced and annealed
- 2y agoprobablyFix grouping sensitivity to variable type
- 3y agoprobablySplit conformal and conformal quantile regression added
- 3y agoprobablyCalibration and conformal inference arrive in tidymodels ⚡
- 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 probably?
Both compete on the same themes — tidymodels — within Analytics. finetune and probably 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 probably?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. finetune and probably 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 probably?
Top probably alternatives in Analytics are ranked by recent ship velocity. Browse the "probably alternatives" section above for the current picks, or visit /alternatives/probably for the full list with editorial commentary on each.