LoginSign Up
← Back to all sparks
M

mlr3hyperband

AI-ASSISTANTS
Velocity2.5

Successive Halving and Hyperband in the mlr3 ecosystem

github.com/mlr-org/mlr3hyperband ↗

Hyperband tuning for mlr3, now built on an asynchronous backend it treats as mandatory

hyperparameter-tuningmlr3asynchronous-optimizationr-packagemachine-learning
◆Current state
mlr3hyperband supplies successive-halving and Hyperband optimizers to the mlr3 tuning stack. Its recent releases are dominated by ecosystem plumbing rather than new search algorithms: a hard floor of `rush` 1.0.0, alignment with mlr3 1.7.2, and a move onto the ecosystem's new base logger. The last genuinely new optimizer was `OptimizerAsyncSuccessiveHalving` in 1.0.0.
◆Where it's heading
The package has finished a transition from synchronous tuning to a distributed one and is now consolidating it. 1.1.1 raised the `rush` minimum to 1.0.0 and deleted every compatibility workaround for older versions, which ends the period where the async backend was optional. Logging moved the same way in 1.1.0: `bbotk`, `mlr3tuning` and `mlr3hyperband` now log through a child of a shared `mlr3` logger rather than their own.
◆Prediction
With the compatibility layer gone, the next release is more likely to extend async optimizers than to revisit the backend, since the recent versions spent their changes on removing optionality rather than adding surface. The entries give no signal on which optimizer comes next.

◆Recent moves

  1. 21d ago

    rush 1.0.0 required; old compatibility paths removed

    Housekeeping that closes out the async transition: the `rush` minimum moves to 1.0.0 and all compatibility workarounds for older versions are removed, alongside mlr3 1.7.2 compatibility. Users on current versions see no behaviour change.

    View source ↗
  2. 5mo ago

    Logging reparented under a shared mlr3 base logger

    The mlr3 ecosystem gains a base logger named `mlr3`, with the `bbotk` logger reparented under it to carry messages from `bbotk`, `mlr3tuning` and `mlr3hyperband`. Log control moves from a per-package concern to a single ecosystem-level one.

    View source ↗
  3. 1y ago

    Async successive halving lands in 1.0.0

    ⚡ SPARK

    The 1.0.0 release that added `OptimizerAsyncSuccessiveHalving`, moving the package's core scheduling algorithm onto an asynchronous backend. Every release since has been compatibility work consolidating that decision rather than new search behaviour.

    View source ↗
  4. 2y ago

    Compatibility with bbotk and mlr3tuning 1.0.0

    A compatibility-only release tracking bbotk 1.0.0 and mlr3tuning 1.0.0. It is part of the coordinated 1.0.0 version bump across the tuning stack rather than a change to Hyperband itself.

    View source ↗
  5. 2y ago

    Compatibility with paradox 1.0.0

    Compatibility with paradox 1.0.0, the mlr3 parameter-space package. No user-facing change to the optimizers.

    View source ↗
  6. 3y ago

    Unloading now clears registered optimizers

    Maintenance: unloading the package now removes its optimizers and tuners from the mlr3 dictionaries, plus documentation refreshes and removal of a deprecated `method` argument from tests.

    View source ↗