8000 [Optimizer] Multi-fidelity algorithms should explicitly check for a fidelity parameter · Issue #120 · automl/neps · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Optimizer] Multi-fidelity algorithms should explicitly check for a fidelity parameter #120

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
Open
8000 eddiebergman opened this issue Jul 31, 2024 · 0 comments
Open

[Optimizer] Multi-fidelity algorithms should explicitly check for a fidelity parameter #120

eddiebergman opened this issue Jul 31, 2024 · 0 comments
Assignees
@Meganton
Labels
ux Something that would improve user experience
Milestone
Optimizer Overhaul

Comments

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

Right now if running SH with no fidelity parameter available, it will raise this error

        super().__init__(
            pipeline_space=pipeline_space,
            budget=budget,
            loss_value_on_error=loss_value_on_error,
            cost_value_on_error=cost_value_on_error,
            ignore_errors=ignore_errors,
            logger=logger,
        )
        if random_interleave_prob < 0 or random_interleave_prob > 1:
            raise ValueError("random_interleave_prob should be in [0.0, 1.0]")
        self.random_interleave_prob = random_interleave_prob
        self.sample_default_first = sample_default_first
        self.sample_default_at_target = sample_default_at_target
    
>       self.min_budget = self.pipeline_space.fidelity.lower
E       AttributeError: 'NoneType' object has no attribute 'lower'

This is not very descriptive on how to solve the problem. If implementing #119, we can simply check this and emit it in the BaseOptimizer.

Also seems to occur from hyperband_custom_default while not happening for hyperband. Priorband requires it too.
@eddiebergman eddiebergman added the ux Something that would improve user experience label Jul 31, 2024
@eddiebergman eddiebergman added this to the Optimizer Overhaul milestone Jul 31, 2024
@Meganton Meganton self-assigned this Apr 2, 2025
Meganton added a commit that referenced this issue Apr 5, 2025
@Meganton
feat: Add support checks for optimizers and introduce OptimizerSuppor…
f7b299b 
…ts dataclass, starting #119 and in the process solving #120

Throws a lot of errors for using the Supports-attribute on the algorithms-functions directly. Maybe use wrappers?
WIP, does not yet handle custom optimizers.
@Meganton Meganton mentioned this issue Apr 5, 2025
Closed
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

@Meganton Meganton

Labels
ux Something that would improve user experience
Projects
NePS Project Board
Status: No status
Milestone
Optimizer Overhaul
Development

No branches or pull requests
2 participants
@eddiebergman @Meganton
0