On 14 January 2014 23:58, Mathieu Blondel <math...@mblondel.org> wrote:
>
>
>
> On Tue, Jan 14, 2014 at 8:13 PM, Joel Nothman <joel.noth...@gmail.com>wrote:
>
>>
>> I like this idea, broadly. I don't especially like the thought of
>> deprecating the scorer interface and parameter name already, but I think
>> this entails doing so. And the fact that it no longer has the same
>> interface as estimator.score suggests it should have a different name.
>>
>>
> I was thinking we could keep __call__(self, estimator, X, y), at least for
> some time, and add a new method evaluate(self, y_true, y_score).
> need_threshold=False would be deprecated in favor of need_categories=True.
>
> The most important is to not break GridSearchCV and cross_val_score. A few
> deprecation warnings in the scorer API (in case people have created custom
> scorers in their user-land code) are reasonable I think.
>
> Mathieu
>
Yes, I guess I took a similar approach (adding a named method to scorers)
in my first implementation of multiple metric scorers, when I didn't
realise the scorer API was still fluid.
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Scikit-learn-general mailing list
Scikit-learn-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
