tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of dials and mlr3fselect — release velocity, themes, recent moves, and the top alternatives to consider.
dials is quietly registering the tuning parameters for tidymodels' deep-learning push
dials defines the parameter objects and grid constructors that tidymodels tunes over, which makes its release notes a reliable early read on what the rest of the stack is about to support. The last two releases are dominated by attention-model parameters — SAINT and tabular deep learning via brulee, TabPFN via parsnip's tab_pfn() — alongside catboost parameters for bonsai and calibration parameters for tailor.
mlr3fselect turned feature selection into an asynchronous, distributable job
mlr3fselect runs feature selection for mlr3. The defining change in this window is 1.4.0, which introduced FSelectorAsync and the asynchronous instance classes, letting searches run without a synchronous batch loop. Around it sit ensemble feature selection work — fastVoteR ranking, embedded ensemble selection, result combination — and performance work on objective evaluation.
dials defines the parameter objects and grid constructors that tidymodels tunes over, which makes its release notes a reliable early read on what the rest of the stack is about to support. The last two releases are dominated by attention-model parameters — SAINT and tabular deep learning via brulee, TabPFN via parsnip's tab_pfn() — alongside catboost parameters for bonsai and calibration parameters for tailor.
The grid machinery itself is settled: grid_space_filling() consolidated the older designs, and the grid_*() functions now error rather than warn on the wrong size argument. What keeps moving is the parameter catalog, and it is moving toward neural and foundation-model territory that tidymodels historically left alone. Error-message quality is a steady secondary theme.
Expect further parameter objects to land ahead of the parsnip and brulee releases that use them — the attention and tabular-foundation-model work in flight is the clearest thing the entries point to.
mlr3fselect runs feature selection for mlr3. The defining change in this window is 1.4.0, which introduced FSelectorAsync and the asynchronous instance classes, letting searches run without a synchronous batch loop. Around it sit ensemble feature selection work — fastVoteR ranking, embedded ensemble selection, result combination — and performance work on objective evaluation.
Two threads run in parallel: scaling the search itself through async execution and the rush backend, and making ensemble selection results easier to analyse via Pareto fronts, knee points and now removal of empty result rows. The rush backward-compatibility shim was dropped in 1.6.0, so the async path is now the assumed one.
Expect the ensemble result API to keep gaining analysis helpers, with async execution treated as the default rather than an option.
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 dials or mlr3fselect.
Finished, widely taught, and shipping roxygen fixes.
Text features finally stay sparse all the way to the model.
The package that made calibration a step instead of an afterthought.
workflowsets keeps widening what counts as a model worth comparing.
The tidymodels pipeline grew a third stage, and it happens after the model runs.
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
See all dials alternatives → · See all mlr3fselect alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-stats — within Analytics. dials and mlr3fselect 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. dials and mlr3fselect 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 dials alternatives in Analytics are ranked by recent ship velocity. Browse the "dials alternatives" section above for the current picks, or visit /alternatives/dials for the full list with editorial commentary on each.
Top mlr3fselect alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3fselect alternatives" section above for the current picks, or visit /alternatives/mlr3fselect for the full list with editorial commentary on each.