8000 [Optimizers] Make all available optimizers through a "string" be instatiable without kwargs · Issue #118 · automl/neps · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Optimizers] Make all available optimizers through a "string" be instatiable without kwargs #118

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.

Sign up for GitHub

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

Jump to bottom
Closed
3 tasks
eddiebergman opened this issue Jul 30, 2024 · 0 comments · May be fixed by #212
Closed
3 tasks

[Optimizers] Make all available optimizers through a "string" be instatiable without kwargs #118

eddiebergman opened this issue Jul 30, 2024 · 0 comments · May be fixed by #212
Labels
ux Something that would improve user experience
Milestone
Optimizer Overhaul

Comments

@eddiebergman
Copy link
Contributor
eddiebergman commented Jul 30, 2024 •
edited
Loading

WIP Issue... Just submitting it to get a number to put in code for now

The optimizers support a lot of configuration but we make sure to have sensible defaults. However some optimizers do not run without extra keyword arguments specified

  • All optimizers should be able to be instantiated with OptimizerCls(pipeline_space=space)
    • "assisted_regularized_evolution": assert not assisted or (assisted and assisted_zero_cost_proxy is not None) - It won't run with defaults, it has assisted as True and assisted_zero_cost_proxy = None, needing to be specified.
    • "successive_halving_prior" requires a budget to be specified while "successive_halving"does not. I'm not sure which one is incorrect. It seems likeSuccessiveHalvingwill just passbudget=None` to base Optimizer and move on with its day... not sure what the behaviour is in this case.
@eddiebergman eddiebergman added this to the Optimizer Overhaul milestone Jul 30, 2024
@eddiebergman eddiebergman added optim ux Something that would improve user experience and removed optim labels Jul 30, 2024
@Meganton Meganton closed this as completed Apr 1, 2025
Meganton added a commit that referenced this issue Apr 28, 2025
@Meganton
Enhances fidelity handling in optimization algorithms
fc2df1f 
Adds `ignore_fidelity` parameter across optimizers for flexible fidelity management
Introduces warnings and error handling for missing or unsupported fidelity/prior cases
Updates grid, random, and Bayesian sampling to respect fidelity settings
Improves test coverage for fidelity and prior requirements

Fixes #118, #119, #120
@Meganton Meganton mentioned this issue Apr 28, 2025
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ux Something that would improve user experience
Projects
NePS Project Board
Status: Done
Milestone
Optimizer Overhaul
Development

Successfully merging a pull request may close this issue.

feat: Fidelity and prior compatibility checks in optimization algorithms automl/neps
2 participants
@eddiebergman @Meganton
0