← Back to home
Comparison · Analytics

mlr3tuning vs parameters

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

Shared themes:r-package

mlr3tuning vs parameters: at a glance

Featuremlr3tuningparameters
SectorAnalyticsAnalytics
Velocity score2.50.0
Sparks · 30d00
Top themesmlr3, hyperparameter-tuning, async-optimization, callbackseasystats, model-parameters, standardization, mixed-models
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is mlr3tuning?

mlr3tuning is rebuilding its async machinery under a stable public surface

mlr3tuning provides hyperparameter optimization for the mlr3 ecosystem, and its recent history is dominated by the asynchronous tuning path: archive freezing, callback stages around queue evaluation, and version-locked compatibility with the rush backend. Releases pair a small feature with several fixes and an explicit compatibility line naming the mlr3 or rush version they track. The most recent release drops all workarounds for older rush versions, which suggests that dependency has stabilized enough to require rather than accommodate.

Read the full mlr3tuning trajectory →

What is parameters?

easystats' parameters package absorbs one more model class every few weeks

parameters extracts and formats coefficients from an enormous range of R model objects, and its releases read as a running ledger of that range expanding — lavaan and lavaan.mi, survey, lcmm, glmmTMB, fixest, marginaleffects, ordinal. Recent versions ship roughly monthly with a mix of new support, new arguments, and fixes for label handling and standard errors. The most consequential recent change is behavioral: post-hoc standardization no longer standardizes the intercept, setting it and its inferential statistics to NA.

Read the full parameters trajectory →

mlr3tuning vs parameters: editorial side-by-side

M
mlr3tuning
ANALYTICS
2.5

mlr3tuning is rebuilding its async machinery under a stable public surface

◆ Current state

mlr3tuning provides hyperparameter optimization for the mlr3 ecosystem, and its recent history is dominated by the asynchronous tuning path: archive freezing, callback stages around queue evaluation, and version-locked compatibility with the rush backend. Releases pair a small feature with several fixes and an explicit compatibility line naming the mlr3 or rush version they track. The most recent release drops all workarounds for older rush versions, which suggests that dependency has stabilized enough to require rather than accommodate.

◆ Where it's heading

Two things are being tidied at once. The async archive is converging on a consistent data.table representation across batch and async variants, so results are shaped the same regardless of how tuning ran. Separately, the package is becoming a better ecosystem citizen — unioning tuner properties on load instead of overwriting them, removing its callbacks on unload, and raising informative errors from AutoTuner accessors on an untrained model. Both are the marks of a package used as a dependency more than as a destination.

◆ Prediction

With rush pinned to 1.2.0 and the compatibility shims gone, the next release is likely to expose more of the async path through callbacks rather than change the tuning interface.

P
parameters
ANALYTICS
0.0

easystats' parameters package absorbs one more model class every few weeks

◆ Current state

parameters extracts and formats coefficients from an enormous range of R model objects, and its releases read as a running ledger of that range expanding — lavaan and lavaan.mi, survey, lcmm, glmmTMB, fixest, marginaleffects, ordinal. Recent versions ship roughly monthly with a mix of new support, new arguments, and fixes for label handling and standard errors. The most consequential recent change is behavioral: post-hoc standardization no longer standardizes the intercept, setting it and its inferential statistics to NA.

◆ Where it's heading

The package's job is to be the universal adapter for model output, so its roadmap is effectively set by what the R modelling ecosystem produces. Two threads are visible beyond coverage: getting standard errors right for awkward cases such as frailty terms and robust vcov matrices, and getting labels right when factors are converted on the fly or character variables appear in a formula. Interoperability inside easystats keeps tightening, with equivalence_test() gaining methods for modelbased objects.

◆ Prediction

Given the cadence, the next release will most likely add another model class alongside label and standard-error fixes rather than change how the package works.

Alternatives to mlr3tuning and parameters

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 mlr3tuning or parameters.

See all mlr3tuning alternatives → · See all parameters alternatives →

Recent activity from mlr3tuning and parameters

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

  1. 18d agomlr3tuningmlr3tuning 1.6.1 stops clobbering other packages' tuner properties
  2. 1mo agoparametersparameters 0.29.2 extends lavaan support and fixes label dropping
  3. 2mo agoparametersparameters 0.29.1 adds a cluster argument and fixes vcov handling
  4. 3mo agoparametersparameters 0.29.0 stops standardizing the intercept in post-hoc methods
  5. 4mo agomlr3tuningmlr3tuning 1.6.0 aligns archive column order across tuning classes
  6. 8mo agomlr3tuningmlr3tuning 1.5.1 tracks xgboost 3.1.2.1
  7. 8mo agomlr3tuningmlr3tuning 1.5.0 adds queue evaluation stages to async callbacks
  8. 8mo agoparametersparameters 0.28.3 adds Kenward-Roger and Satterthwaite for glmmTMB
  9. 11mo agoparametersparameters 0.28.2 updates tests for the latest fixest release
  10. 11mo agoparametersparameters 0.28.1 adds robust standard errors for glmmTMB
  11. 1y agomlr3tuningmlr3tuning 1.4.0 unifies logging under a base mlr3 logger
  12. 1y agomlr3tuningmlr3tuning 1.3.0 adds a frozen async archive and leaner worker storage

Frequently asked questions

What is the difference between mlr3tuning and parameters?

Both compete on the same themes — r-package — within Analytics. mlr3tuning 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 mlr3tuning better than parameters?

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

Top mlr3tuning alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3tuning alternatives" section above for the current picks, or visit /alternatives/mlr3tuning for the full list with editorial commentary on each.

What are the best alternatives to parameters?

Top parameters alternatives in Analytics are ranked by recent ship velocity. Browse the "parameters alternatives" section above for the current picks, or visit /alternatives/parameters-r for the full list with editorial commentary on each.