mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
Comparison · Analytics
mlr3viz vs probably
A side-by-side editorial comparison of mlr3viz and probably — release velocity, themes, recent moves, and the top alternatives to consider.
mlr3viz vs probably: at a glance
What is mlr3viz?
mlr3viz keeps the ecosystem's plots working while the plots themselves move out
mlr3viz supplies autoplot methods across mlr3 objects — learners, resample and benchmark results, tuning instances, ensemble feature-selection results. Recent releases are mostly defensive: suppressing ggplot2::fortify() warnings on ROC and PRC curves, pinning legend order so plots are deterministic across ggplot2 environments, and tracking mlr3 1.7.2. A visible piece of scope also left, with the LearnerSurvCoxPH plot moving to mlr3proba.
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.
mlr3viz vs probably: editorial side-by-side
mlr3viz
2.5ANALYTICS
mlr3viz keeps the ecosystem's plots working while the plots themselves move out
◆ Current state
mlr3viz supplies autoplot methods across mlr3 objects — learners, resample and benchmark results, tuning instances, ensemble feature-selection results. Recent releases are mostly defensive: suppressing ggplot2::fortify() warnings on ROC and PRC curves, pinning legend order so plots are deterministic across ggplot2 environments, and tracking mlr3 1.7.2. A visible piece of scope also left, with the LearnerSurvCoxPH plot moving to mlr3proba.
◆ Where it's heading
The package is being narrowed toward generic plotting infrastructure while learner-specific plots migrate to the packages that own those learners. What it does add is access rather than new charts — passing parameters through to precrec::autoplot(), better hints when the wrong autoplot type is requested, and a confidence-interval plot for mlr3inferr. Determinism across ggplot2 versions has become a recurring concern, which is what happens when a visualization package is depended on by documentation and tests.
◆ Prediction
Following the Cox proportional-hazards precedent, further learner-specific plots are likely to move to their owning packages, leaving mlr3viz with the cross-cutting result objects.
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 mlr3viz 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 mlr3viz or probably.
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
tidyposterior
A finished Bayesian model-comparison package in pure maintenance mode
See all mlr3viz alternatives → · See all probably alternatives →
Recent activity from mlr3viz and probably
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 18d agomlr3vizmlr3viz 0.11.1 pins legend order for deterministic plots
- 5mo agomlr3vizmlr3viz 0.11.0 quiets ggplot2 fortify warnings on ROC curves
- 10mo agoprobablyConformal objects gain required_pkgs() and butcher methods
- 1y agoprobablyggplot2 test updates and a clearer validation-set error
- 1y agomlr3vizmlr3viz 0.10.1 passes plotting parameters through to precrec
- 1y agoprobablyCalibration internals refactored; isotonic bootstrap bug fixed
- 1y agomlr3vizmlr3viz 0.10.0 adds a LearnerSurvCoxPH plot
- 2y agomlr3vizmlr3viz 0.9.0 adds EnsembleFSResult plots
- 2y agomlr3vizmlr3viz 0.8.0 tracks paradox 1.0.0
- 2y agoprobablyFix grouping sensitivity to variable type
- 3y agoprobablySplit conformal and conformal quantile regression added
- 3y agoprobablyCalibration and conformal inference arrive in tidymodels ⚡
Frequently asked questions
What is the difference between mlr3viz and probably?
They serve adjacent needs but don't currently overlap on shipped themes. mlr3viz is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is mlr3viz better than probably?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mlr3viz is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to mlr3viz?
Top mlr3viz alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3viz alternatives" section above for the current picks, or visit /alternatives/mlr3viz 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.