'Number of configurations in mlr3 hyperband tuning

How can I control the number of configurations being evaluated during hyperband tuning in mlr3? I noticed that when I tune 6 parameters in xgboost(), the code evaluates about 9 configurations. When I tune the same number of parameters in catboost(), the code starts with evaluating 729 configurations. I am using eta = 3 in both cases.



Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source