tidytext
Finished, widely taught, and shipping roxygen fixes.
Comparison · Analytics
lime vs mlr3mbo
A side-by-side editorial comparison of lime and mlr3mbo — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-stats
lime vs mlr3mbo: at a glance
What is lime?
lime survives on compatibility patches years after its research moment
lime brings local interpretable model-agnostic explanations to R. Its substantive development finished around 0.5.0 in 2019, which added argument pass-through to predict(), a gower_pow tuning knob and a batch of fixes. Since then there have been three releases: a namespace fix, a maintainer handover to Emil Hvitfeldt with general upkeep, and a patch to work across xgboost versions.
What is mlr3mbo?
mlr3mbo picked its defaults from a benchmark study, not from taste
mlr3mbo does model-based and Bayesian optimisation for mlr3. Its 1.0.0 release added a dictionary of pre-built acquisition-function optimisers and, more consequentially, replaced the default surrogate, acquisition function and optimiser settings with values derived from a large-scale benchmark study. The releases since are corrections to the acquisition-optimiser path exposed by that new default configuration.
lime vs mlr3mbo: editorial side-by-side
lime
0.0ANALYTICS
lime survives on compatibility patches years after its research moment
◆ Current state
lime brings local interpretable model-agnostic explanations to R. Its substantive development finished around 0.5.0 in 2019, which added argument pass-through to predict(), a gower_pow tuning knob and a batch of fixes. Since then there have been three releases: a namespace fix, a maintainer handover to Emil Hvitfeldt with general upkeep, and a patch to work across xgboost versions.
◆ Where it's heading
The package is in custodial maintenance — kept installable and compatible with the model packages it explains, rather than developed. The 2022 handover is the most consequential entry in the window because it determined that the package would keep getting patches at all.
◆ Prediction
Expect the next release to be another compatibility fix triggered by an upstream model package, not new explanation methods.
mlr3mbo
2.5ANALYTICS
mlr3mbo picked its defaults from a benchmark study, not from taste
◆ Current state
mlr3mbo does model-based and Bayesian optimisation for mlr3. Its 1.0.0 release added a dictionary of pre-built acquisition-function optimisers and, more consequentially, replaced the default surrogate, acquisition function and optimiser settings with values derived from a large-scale benchmark study. The releases since are corrections to the acquisition-optimiser path exposed by that new default configuration.
◆ Where it's heading
The package has moved from a toolkit that expected users to assemble a Bayesian optimisation loop into one with a defensible default loop, and the recent fixes — warm-start sizing on multi-objective archives, silently discarded terminators, stale x_domain values — are the consequences of more people running the default path.
◆ Prediction
Expect continued hardening of the acquisition-optimiser classes rather than new acquisition functions.
Alternatives to lime and mlr3mbo
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 lime or mlr3mbo.
textrecipes
Text features finally stay sparse all the way to the model.
probably
The package that made calibration a step instead of an afterthought.
workflowsets
workflowsets keeps widening what counts as a model worth comparing.
workflows
The tidymodels pipeline grew a third stage, and it happens after the model runs.
vetiver
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
See all lime alternatives → · See all mlr3mbo alternatives →
Recent activity from lime and mlr3mbo
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23d agomlr3mboAcquisition optimiser fixes for warm starts and archives
- 3mo agomlr3mboDictionary lookup and restart-limit fixes
- 4mo agomlr3mborush 1.0.0 compatibility and Surrogate$check()
- 5mo agomlr3mbomlr3mbo 1.0.0 ships benchmark-derived default settings ⚡
- 8mo agolimeCompatibility across all xgboost versions
- 10mo agomlr3mbomlr3learners 0.13.0 compatibility
- 11mo agomlr3mboMaintainer change and mlr3pipelines 0.9.0 upkeep
- 3y agolimeMaintainer handover to Emil Hvitfeldt
- 5y agolimeorder() fix and lighter dependencies
- 6y agolimeNamespace fix following glmnet changes
- 7y agolimeexplain() gains pass-through args and gower_pow tuning
- 8y agolimeh2o support, NA handling and date feature types
Frequently asked questions
What is the difference between lime and mlr3mbo?
Both compete on the same themes — r-stats — within Analytics. mlr3mbo 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 lime better than mlr3mbo?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mlr3mbo 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 lime?
Top lime alternatives in Analytics are ranked by recent ship velocity. Browse the "lime alternatives" section above for the current picks, or visit /alternatives/lime-r for the full list with editorial commentary on each.
What are the best alternatives to mlr3mbo?
Top mlr3mbo alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3mbo alternatives" section above for the current picks, or visit /alternatives/mlr3mbo for the full list with editorial commentary on each.