<p dir="auto">From what I can see, LogisticRegressionCV.score always computes accuracy, not the metric given by <code class="notranslate">scoring</code>. That's inconsistent with the behavior of <code class="notranslate">GridSearchCV</code>. How do other <code class="notranslate">CV</code> estimators do that? I assume the same?<br>
That's pretty unfortunate and I think we should change it. We did the same backward incompatible change in GridSearchCV before with a warning.</p>
<p dir="auto">input length (true, score) is 9177<br>
output fp,tp,th size is 5816 but when I re-sample the data it is 5756 (I guess due to sampling with replacement creates duplicate data which is about 1/e)<br>
in matlab, perfcurve returns fp,tp,th the same size as the input size or at specified fp/tp/th values.</p>