not all estimators, but those that are needed for the kind of estimator it
represents, maybe? there are only four kinds of estimators, right? we should
really write those api docs ;)
Lars Buitinck <[email protected]> schrieb:
>2013/2/26 <[email protected]>:
>> actually i think i share tadej's view on being able to exchange
>Pipelines
>> and classifiers. since 0.13 classes_ is basically part of the public
>> classifier api. so a pipeline should also have it, i guess.
>
>But then why classifiers only? And what stops of from doing this for
>every kind of model? labels_ is part of the clustering API, but we
>don't expose that through a Pipeline.
>
>(Should we expose all fitted parameters of the final step of the
>pipeline?)
>
>--
>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
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
------------------------------------------------------------------------------
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
