mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
A side-by-side editorial comparison of mlr3filters and probably — release velocity, themes, recent moves, and the top alternatives to consider.
mlr3filters grows one feature-selection filter at a time
mlr3filters provides feature-filter methods to mlr3. Its releases follow a consistent shape: one or two new filters, broader feature-type support on existing ones, and error-message work. Boruta and a univariate Cox filter arrived in 0.8.0; 0.9.0 extended Boruta to logical, factor and ordered features and moved param_set to an active binding.
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.
mlr3filters provides feature-filter methods to mlr3. Its releases follow a consistent shape: one or two new filters, broader feature-type support on existing ones, and error-message work. Boruta and a univariate Cox filter arrived in 0.8.0; 0.9.0 extended Boruta to logical, factor and ordered features and moved param_set to an active binding.
This is incremental infrastructure that tracks mlr3's own conventions — cli printing, prototype-based dictionaries, featureless learners as defaults — while slowly widening which data types each filter accepts. Nothing in the recent history suggests a change of scope.
Expect another filter or two plus continued feature-type broadening, keeping pace with mlr3 core conventions.
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.
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.
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.
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 mlr3filters or probably.
mlr3proba is shedding weight as its survival work moves into sibling packages
mlr3viz keeps the ecosystem's plots working while the plots themselves move out
mlr3tuning is rebuilding its async machinery under a stable public surface
timetk swallowed anomalize whole, then went quiet for two years
modelbased is turning marginal effects into a full contrast grammar
easystats' parameters package absorbs one more model class every few weeks
See all mlr3filters alternatives → · See all probably alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. mlr3filters 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mlr3filters 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.
Top mlr3filters alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3filters alternatives" section above for the current picks, or visit /alternatives/mlr3filters for the full list with editorial commentary on each.
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.