The user should be able to pass a Searcher/Stopper object in addition to predefined strings in TuneSearchCV. It would be quite easy to add support for that, however first the search space conversions in tune-sklearn need to be unified as to either convert the objects that can be passed right now to Tune search spaces (which will then get converted to Searcher-specific spaces inside those) or make an API breaking change and allow only Tune search spaces + whatever can be passed to sklearn's GridSearchCV.
The user should be able to pass a Searcher/Stopper object in addition to predefined strings in
TuneSearchCV
. It would be quite easy to add support for that, however first the search space conversions in tune-sklearn need to be unified as to either convert the objects that can be passed right now to Tune search spaces (which will then get converted to Searcher-specific spaces inside those) or make an API breaking change and allow only Tune search spaces + whatever can be passed to sklearn'sGridSearchCV
.