Closed gopaljigaur closed 2 weeks ago
This pull request includes several changes to improve the handling of fidelity parameters and validation of YAML configurations. The most important changes involve adding validation checks, updating test configurations, and modifying default values.
__init__
method of neps/optimizers/multi_fidelity/successive_halving.py
.ValueError
if fidelity parameter bounds are less than or equal to zero in neps/search_spaces/hyperparameters/numerical.py
.wd
parameter in neps_examples/template/priorband_template.py
from 0
to 1e-5
.param_int1
in tests/test_yaml_search_space/correct_config.yaml
and tests/test_yaml_search_space/correct_config_including_types.yaml
from -3
to 3
. [1] [2]test_incorrect_fidelity_parameter_bounds
to validate fidelity parameter bounds in tests/test_yaml_search_space/test_search_space.py
.tests/test_yaml_search_space/incorrect_fidelity_bounds_config.yaml
.@DaStoll @eddiebergman
This pull request includes several changes to improve error handling and parameter validation in the package. The most important changes include adding more informative error messages and ensuring parameter bounds are correctly validated.
Error Handling Improvements:
neps/optimizers/multi_fidelity/successive_halving.py
: Added an error message to the assertion for thefidelity
parameter to clarify when it is not set.Parameter Validation:
neps/search_spaces/hyperparameters/numerical.py
: Added a check to raise aValueError
if thefidelity
parameter bounds are less than or equal to zero when using a log scale.neps_examples/template/priorband_template.py
: Changed the lower bound of thewd
parameter to1e-5
to ensure it is within a valid range.Add non-negative value check for fidelity parameter.