Proposed changes for ``test_metrics.py``

[shantam-8]

The following PR (part of #1351) proposes the following changes for _PredictScorer, _ProbaScorer, and _TresholdScorer as part of the test_metrics.py. Using the guidance present, I have used pytests to make the tests as flexible as possible. Please let me know if I need to add/delete anything else and I would be glad to do the same for the rest of test_metrics.py. Thanks a lot!

[codecov[bot]]

Codecov Report

Merging #1577 (47907b0) into development (ee0916e) will decrease coverage by 0.26%. The diff coverage is n/a.

:exclamation: Current head 47907b0 differs from pull request most recent head aeb15dd. Consider uploading reports for the commit aeb15dd to get more accurate results

Additional details and impacted files

@@               Coverage Diff               @@
##           development    #1577      +/-   ##
===============================================
- Coverage        84.75%   84.49%   -0.27%     
===============================================
  Files              157      155       -2     
  Lines            11981    11898      -83     
  Branches          2066     2058       -8     
===============================================
- Hits             10155    10053     -102     
- Misses            1278     1281       +3     
- Partials           548      564      +16     

[eddiebergman]

Hi @shantam-8,

It looks good to me now, sorry for the deleyad responses, we had some deadlines coming up for other papers that kept us away from auto-sklearn! I pinged @mfeurer to have a quick look

Best, Eddie

[shantam-8]

Hello @eddiebergman @mfeurer, sorry to reply so late. I had made a few more updates to test_metrics.py, specifically the test_sign_flip function (formerly part of TestScorer class) and the test_regression_metrics and test_classification_metrics functions (formerly part of TestMetricsDoNotAlterInput class). Could you please let me know if these are fine or should I roll them back? Also, I was going to approach the TestMetric class. Should I do it as another PR after merging this one as I was not very sure as to how to do it?

[eddiebergman]

Hi @shantam-8,

I looked at the TestMetric class and I think you can honestly just delete it, given that the metrics all achieve the score they are meant to. It doesn't provide much more over the tests we already have and is just extra noise (imo). @mfeurer do you agree?

The other ones look fine to me.

Edit: I think mfeurer is busy for the nxt few days so deleting that class and if all the tests pass, I think this is ready to merge :)

[eddiebergman]

Not sure why the metadata generation tests are failing to be honest. I'll try rerun them

[eddiebergman]

Sorry to keep it going, I guess I didn't unfold the TestMetric class all the way on github. Can you make sure that every metric we export is tested at least once in the big long test, i.e. that there's one or two cases for each metric of sample input, the true y and the expected score.

[shantam-8]

While the long test list does contain metrics like accuracy, bal_accuracy, r2, log_loss, and roc_auc, it misses a huge portion of metrics that are part of the autosklearn.metrics.REGRESSION_METRICS and autosklearn.metrics.CLASSIFICATION_METRICS like precision, recall, f1, mse, etcetera. However, as the TestMetricclass covered these, would it make sense to maintain it?

[eddiebergman]

Sure, we can just keep them in instead of adding them to the huge list then :)

[eddiebergman]

Hey @shantam-8,

Very sorry for the slow feedback loop on all of this, we've been pretty busy recently! Many thanks for the contribution and we'll be more responsive for the coming months :)

Best, Eddie