-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
Extend FeatureUnion to better handle heterogeneous data #2034
Copy link
Copy link
Closed
Labels
ModerateAnything that requires some knowledge of conventions and best practicesAnything that requires some knowledge of conventions and best practicesNew Feature
Description
FeatureUnion currently passes identical data to each constituent transformer. Often one wants to differentiate between groups of features in how they are transformed. While this is possible by making each stacked transformer a Pipeline consisting of a pre-determined feature selector and another transformer, this is cumbersome.
A parameter should be added to specify which features are routed to which constituents. This is not necessarily trivial to design, particularly because the input X to FeatureUnion.transform need not be a conventional 2d feature array (it may be a list/array of dicts, texts, or other objects).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
ModerateAnything that requires some knowledge of conventions and best practicesAnything that requires some knowledge of conventions and best practicesNew Feature