2013/2/26 Tadej Janež <[email protected]>: > On Tue, 2013-02-26 at 14:39 +0100, Lars Buitinck wrote: >> Good question. I say don't export classes_, because (a) then there's >> no reason to not do this for any other attribute. > > Well, I'm more in favour of being able to smoothly exchange estimators > with pipelines, where first some preprocessing is done and then the > final step is an estimator. > Maybe it's worth considering the nice things that could be done if > estimators and pipelines ending with estimators would be > interchangeable?
I'm all in favor of that, but we have so many different estimators that special-casing Pipeline for all (kinds of) them is infeasible. So we should come up with an elegant and general set of rules, which we can then implement by e.g. a custom __getattr__ on Pipeline. There are several questions to be answered: * which attributes should be exported? (all? all those with final _? what about methods?) * if two estimators in the pipeline implement an attribute, which one does the pipeline's attribute refer to? possibly classes_, with L1-feature selection by SVMs; we could select the last member of the pipeline in this case, but will that always work? -- Lars Buitinck Scientific programmer, ILPS University of Amsterdam ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Scikit-learn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
