On 02/03/2013 03:46 PM, Gael Varoquaux wrote:
>
> In sklearn/metrics/score_objects.py:
>
> > +average_precision_scorer = Scorer(average_precision_score,
> > +                                  needs_threshold=True)
> > +precision_scorer = Scorer(precision_score)
> > +recall_scorer = Scorer(recall_score)
> > +
> > +# Clustering scores
> > +ari_scorer = Scorer(adjusted_rand_score)
> > +
> > +scorers = dict(r2=r2_scorer, mse=mse_scorer, accuracy=accuracy_scorer,
> > +               f1=f1_scorer, roc_auc=auc_scorer,
> > +               average_precision=average_precision_scorer,
> > +               precision=precision_scorer, recall=recall_scorer,
> > +               ari=ari_scorer)
> > +
> > +
> > +def score_objects():
> @arjoly <https://github.com/arjoly> suggested it. There is a similar 
> function in pairwise. I think the idea is to have something in the 
> references so that the user can view the documentation.
> I have a strong dislike for getters. I feel that they make the code 
> more opaque, as when I see them, I always wonder if there is a reason 
> for using getters, and if so why. Would the module docstring be the 
> place to store that information? We are not current displaying the 
> module docstrings, but we could.
>
I'll remove it, remove the duplicate table and add the references in the 
other places.
Then I think I will have addressed all your comments.