search

automl / hypersweeper

Hydra sweeper integration of our favorite optimization packages, utilizing ask-and-tell interfaces.
Other
8 stars 2 forks source link

Parameter Naming #2

Closed LukasFehring closed 6 months ago

LukasFehring commented 7 months ago

Description

In the classes SMACSweeperConfig, HydraSMAC, SMACSweeperBackend, and SMACSweeper instances of the other respected classes are created. However, the naming of parameters is not consistent throughout the classes. E.g. the parameter hydra.sweeper.budget is read by the SMACSweeperBackend and passed as n_trials to HydraSMAC.

Additionally, there are multiple different budgets, which are hard to differentiate.

TheEimer commented 6 months ago

So this needs to be documented better, agreed, but at least now almost all of the config is directly passed to the optimizer and not parsed top level. You still need to specify either budget or n_trials, but this is not what's passed to e.g. SMAC, these keywords are handled in the optimizers_kwargs and correspond directly to SMAC. Still a not exactly super simple, but at least the overlap is gone.