Early stopping using max_score about hyperactive

[SimonBlanke]

Hello David,

I am glad to see, that you are still using Hyperactive.

In the current version of v2.x Hyperactive cannot do an early stop. This feature will be implemented in v3.0 coming in a few weeks.

However, part of the current Hyperactive development is the separation of the optimization algorithms into a simpler api. It is called Gradient-Free-Optimizers and is basically Hyperactive-lite. It will be the optimization-back-end of Hyperactive in the future. But it can also be used by itself, without Hyperactive:
https://github.com/SimonBlanke/Gradient-Free-Optimizers

Your code would convert into the following with Gradient-Free-Optimizers:

import time
import numpy as np
from gradient_free_optimizers import BayesianOptimizer


def my_model(para):
    time.sleep(3)
    return 0.9

search_space = {"n_estimators": np.arange(10, 200, 10)}

c_time = time.time()
opt = BayesianOptimizer(search_space)
opt.search(my_model, n_iter=8, max_score=0.9)
diff_time = time.time() - c_time

print("\n Optimization time:", diff_time)

Gradient Free Optimizers is well tested and very easy to use, but it has a few restrictions compared to Hyperactive:

• The search space must be numeric (numpy arrays)
• No build-in multiprocessing
• No access to optimizer-parameters at run time. (In Hyperactive 3.0)

To make the relationship between Hyperactive and Gradient Free Optimizers clear, I will add a section into the readme about the differences and purposes of both packages.

I hope I was able to help you. If you have additional questions or suggestions please let me know.

[DavidFricker]

Hi Simon,

Thank you for your fast and in depth response!

I appreciate the work-around code you have provided - it is working great.
We will use Gradient Free Optimizers package and wait for hyperactive 3.x to be released, your approach makes a lot of sense :)

Thanks,
David