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
Good idea. As for deriving from Pipeline, why not. The simpler workflows could certainly be pipelined. I just don't think it could be done in general (e.g. drug spectra in which we have quite a bit of glue code between the steps. The flexible handling of CV folds is also something that makes it more general. Anyway, no reason not to investigate.
The WorflowElementType and the whole structure was introduced a bit prematurely. I thought we could syntactically support transfer learning by enforcing certain conventions. I'm less keen on this now, first there was no real demand for this, second, it's a bit dubious whether an element made for a certain problem can be reused in another. I would approach this from an AutoML point of view now. So your second bullet is a bit less important for me, I'd let the demand evolve a little bit.
The workflows should be derived from a metaclass to enforce having the parameter
element_names
.I would like also to investigate:
_estimator_type
to indicate which type they are. The integration withWorflowElementType
would be eased.The text was updated successfully, but these errors were encountered: