You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The call get_default_configuration() only gets a small subset of the complete search space.
It would be convenient with a function get_full_configuration().
In file: example_custom_configuration_space.py, I can see how to modify the search space.
I am not sure I understand what you are saying. estimator.get_search_space(dataset).get_default_configuration() samples a single configuration from the full search space. But its a single configuration and not necessarily the best configuration. You can get the best configuration by searching over the full search space which you can check with estimator.get_search_space(dataset). AutoPyTorch will by default search over this search space. You dont have to pass any search space updates, unless you want to change specific hyperparameters. Let me know if you still need help with this.
I am trying to understand how to get the optimal neural network for a given pipeline.
I assume that one step is to maximize the search space.
In example_custom_configuration_space.py row 59:
configuration = estimator.get_search_space(dataset).get_default_configuration()
The call
get_default_configuration()
only gets a small subset of the complete search space.It would be convenient with a function
get_full_configuration()
.In file: example_custom_configuration_space.py, I can see how to modify the search space.
Question:
Should I iterate over the config space to generate python-code that I can paste in a function as above? Is there an easier way?
Like this row:
network_backbone:MLPBackbone:dropout_12 | network_backbone:MLPBackbone:use_dropout == True && network_backbone:MLPBackbone:num_groups > 11
How can I add this into the
HyperparameterSearchSpaceUpdates()
function?If I add hyperparameters about a specific network_backbone type. Do I need to include all the components like this?
The full config space is attached below in pcs_new format.
The text was updated successfully, but these errors were encountered: