← Back to home
Comparison · Analytics

mlr3proba vs probably

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

mlr3proba vs probably: at a glance

Featuremlr3probaprobably
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesmlr3, survival-analysis, probabilistic-learning, dependency-maintenancecalibration, conformal-inference, tidymodels, uncertainty
Last editorial update44m ago1h ago
WebsiteVisit →Visit →

What is mlr3proba?

mlr3proba is shedding weight as its survival work moves into sibling packages

mlr3proba provides probabilistic supervised learning for mlr3 — survival analysis, density estimation, and the measures that go with them. Recent releases are almost entirely upkeep: a distr6 fork to work around an upstream problem, an ooplah fix, a predict-type correction, and registration in mlr_reflections$loaded_packages. The one deletion is telling, with LearnerDensPenalized removed after pendensity left CRAN.

Read the full mlr3proba trajectory →

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.

Read the full probably trajectory →

mlr3proba vs probably: editorial side-by-side

M
mlr3proba
ANALYTICS
0.0

mlr3proba is shedding weight as its survival work moves into sibling packages

◆ Current state

mlr3proba provides probabilistic supervised learning for mlr3 — survival analysis, density estimation, and the measures that go with them. Recent releases are almost entirely upkeep: a distr6 fork to work around an upstream problem, an ooplah fix, a predict-type correction, and registration in mlr_reflections$loaded_packages. The one deletion is telling, with LearnerDensPenalized removed after pendensity left CRAN.

◆ Where it's heading

The package is being pared back rather than extended. Its README now points at survdistr and mlr3cmprsk as matured alternatives for parts of what it covers, which reads as scope being handed off, while the Cox proportional-hazards autoplot arrived from mlr3viz in the other direction. Several fixes exist to route around dependencies that broke or disappeared, which is the recurring cost of building on a long chain of specialized CRAN packages.

◆ Prediction

The dependency churn suggests more consolidation — further reliance on survdistr and mlr3cmprsk, and more learners retired when the package underneath them goes unmaintained.

P
probably
ANALYTICS
0.0

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 mlr3proba 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 mlr3proba or probably.

See all mlr3proba alternatives → · See all probably alternatives →

Recent activity from mlr3proba and probably

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

  1. 2mo agomlr3probamlr3proba 0.8.10 registers itself in the mlr3 loaded-packages registry
  2. 4mo agomlr3probamlr3proba 0.8.9 drops LearnerDensPenalized after pendensity left CRAN
  3. 5mo agomlr3probamlr3proba 0.8.8
  4. 5mo agomlr3probamlr3proba 0.8.7
  5. 9mo agomlr3probamlr3proba 0.8.5
  6. 10mo agoprobablyConformal objects gain required_pkgs() and butcher methods
  7. 10mo agomlr3probamlr3proba 0.8.4 takes over the Cox proportional-hazards autoplot
  8. 1y agoprobablyggplot2 test updates and a clearer validation-set error
  9. 1y agoprobablyCalibration internals refactored; isotonic bootstrap bug fixed
  10. 2y agoprobablyFix grouping sensitivity to variable type
  11. 3y agoprobablySplit conformal and conformal quantile regression added
  12. 3y agoprobablyCalibration and conformal inference arrive in tidymodels

Frequently asked questions

What is the difference between mlr3proba and probably?

They serve adjacent needs but don't currently overlap on shipped themes. mlr3proba 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 mlr3proba better than probably?

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

Top mlr3proba alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3proba alternatives" section above for the current picks, or visit /alternatives/mlr3proba 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.