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'd consider a feature selector initially, as it should be fairly trivial to just ignore some features in PMML, but correctly interpreting the pipeline object may involve some work. Otherwise, something involving projections like PCA or random projection, although I'm not sure that these are often used with forests.
I think the most natural way to implement pipelines in PMML would be using nested models. That will allow transformers to define their own LocalTransformations, replace the schemas and pass the adjusted context to the nested model.
A PMML representation of basic scikit-learn transformers and transformer pipelines / featureunions is needed for this to be more broadly useful.
The text was updated successfully, but these errors were encountered: