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
I think a good added feature for the grid searcher would be to be able to define rules to coordinate the grid search. I think it would be best if rules only allow for the skipping of runs.
The form I was thinking for an individual rule would be something along the lines of:
Given {key: value/s}, every time this key with one of these values appears as the next configuration we skip it if in the configuration it has any of the keys with values in {key1: values to skip for key1, key2: values to skip for key2}.
This way you define your grid search and then can modify the behaviour of the grid search to skip configurations you don't want to run.
The searcher should be given the list of rules during initialisation of the grid.
The text was updated successfully, but these errors were encountered:
I think a good added feature for the grid searcher would be to be able to define rules to coordinate the grid search. I think it would be best if rules only allow for the skipping of runs.
The form I was thinking for an individual rule would be something along the lines of:
Given {key: value/s}, every time this key with one of these values appears as the next configuration we skip it if in the configuration it has any of the keys with values in {key1: values to skip for key1, key2: values to skip for key2}.
This way you define your grid search and then can modify the behaviour of the grid search to skip configurations you don't want to run.
The searcher should be given the list of rules during initialisation of the grid.
The text was updated successfully, but these errors were encountered: