← Back to home
Comparison · Analytics

desirability2 vs tune

A side-by-side editorial comparison of desirability2 and tune — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:tidymodels

desirability2 vs tune: at a glance

Featuredesirability2tune
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themestidymodels, multi-objective optimization, model selection, desirability functionshyperparameter-tuning, tidymodels, parallelism, postprocessing
Last editorial update53m ago1h ago
WebsiteVisit →Visit →

What is desirability2?

desirability2 is making multi-metric model selection a first-class tidymodels step.

desirability2 implements desirability functions, which map several metrics onto a common 0-1 scale so they can be combined into a single objective. The package is young: three releases, the first of which only added a NEWS file. Its substance arrived in 0.1.0 with hooks into tidymodels' tune package.

Read the full desirability2 trajectory →

What is tune?

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.

Read the full tune trajectory →

desirability2 vs tune: editorial side-by-side

D
desirability2
ANALYTICS
0.0

desirability2 is making multi-metric model selection a first-class tidymodels step.

◆ Current state

desirability2 implements desirability functions, which map several metrics onto a common 0-1 scale so they can be combined into a single objective. The package is young: three releases, the first of which only added a NEWS file. Its substance arrived in 0.1.0 with hooks into tidymodels' tune package.

◆ Where it's heading

The direction is integration rather than standalone use. Version 0.1.0 added select_best_desirability() and show_best_desirability() to resolve a tuning run against several metrics at once; 0.2.0 exported make_desirability_cols() so other packages can build on it and made data-driven limits the default, removing the need to state ranges by hand. Both releases move work from the user into the package.

◆ Prediction

The exported helper and the developer-facing desirability() API point to adoption by other tidymodels packages as the next step rather than new functionality here.

T
tune
ANALYTICS
0.0

tune extends tuning past the model itself to postprocessors, and adds a second parallel backend

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to desirability2 and tune

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 desirability2 or tune.

See all desirability2 alternatives → · See all tune alternatives →

Recent activity from desirability2 and tune

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 3mo agotuneQuantile regression tuning; Bayesian search moves to GauPro
  2. 10mo agotuneFixes int_pctl() with future parallelism on last_fit()
  3. 11mo agotunePostprocessors become tunable; mirai joins future as a backend
  4. 11mo agotuneDevelopment snapshot re-enabling skipped tests
  5. 11mo agodesirability2make_desirability_cols() exported; data-driven limits on by default
  6. 1y agodesirability2Desirability-based model selection added for tune
  7. 1y agotuneWarns on foreach parallelism; space-filling grids by default
  8. 2y agotuneFixes parallel tuning errors under multisession plans
  9. 3y agodesirability2NEWS.md added to track package changes

Frequently asked questions

What is the difference between desirability2 and tune?

Both compete on the same themes — tidymodels — within Analytics. desirability2 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.

Is desirability2 better than tune?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. desirability2 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.

What are the best alternatives to desirability2?

Top desirability2 alternatives in Analytics are ranked by recent ship velocity. Browse the "desirability2 alternatives" section above for the current picks, or visit /alternatives/desirability2 for the full list with editorial commentary on each.

What are the best alternatives to tune?

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.