Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom searcher ignoring max_cost_total #75

Open
danrgll opened this issue Apr 25, 2024 · 0 comments
Open

Custom searcher ignoring max_cost_total #75

danrgll opened this issue Apr 25, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@danrgll
Copy link
Collaborator

danrgll commented Apr 25, 2024

When utilizing a custom searcher, the parameter max_cost_total is currently being ignored.

To make clear what scenario I mean, see this example:

def run_pipeline(**config):
    return {"loss": 1, "cost": 3}

search_space = SearchSpace(**pipeline_space)
optimizer = BayesianOptimizer(search_space)
neps.run(run_pipeline, searcher=optimizer, max_cost_total=100)
@danrgll danrgll added the bug Something isn't working label Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant