Repository navigation
Updating percent better than baseline computation - #1809
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1809 +/- ##
=========================================
+ Coverage 100.0% 100.0% +0.1%
=========================================
Files 252 252
Lines 20052 20117 +65
=========================================
+ Hits 20044 20109 +65
Misses 8 8
Continue to review full report at Codecov.
|
fe22f68 to
7f4febe
Compare
| greater_is_better = True | ||
| score_needs_proba = False | ||
| perfect_score = np.inf | ||
| # Range (-Inf, Inf) |
There was a problem hiding this comment.
nit-pick but I thought this was an accidental comment rather than on purpose. Maybe we can move it to be next to is_bounded_like_percentage rather than being above?
There was a problem hiding this comment.
Wouldn't this go next to perfect_score?
| greater_is_better = True | ||
| score_needs_proba = False | ||
| perfect_score = math.inf | ||
| # Range (-Inf, Inf) |
| greater_is_better = False | ||
| score_needs_proba = True | ||
| perfect_score = 0.0 | ||
| # Range [0, Inf) |
There was a problem hiding this comment.
Thank you for including these range comments. Super helpful 😁
angela97lin
left a comment
There was a problem hiding this comment.
Nice work, LGTM! 🥳
Just out of curiosity, what did we decide for 'edge cases' such as the correlation matrix? I guess it's not really what we currently consider as an objective... but was wondering if we decided on anything :3
| greater_is_better = True | ||
| score_needs_proba = False | ||
| perfect_score = np.inf | ||
| # Range (-Inf, Inf) |
There was a problem hiding this comment.
Wouldn't this go next to perfect_score?
|
@angela97lin Correlation is just like MCC in the sense that it's bounded [-1, 1]. I think it's best to not treat like a percentage in that case. If baseline gets a negative score and our pipeline gets a positive score, then I'd want the percent better to be above 100% which isn't always the case if we treat it like a percentage. |
7f4febe to
7ed3582
Compare
Pull Request Description
Fixes #1449
After creating the pull request: in order to pass the release_notes_updated check you will need to update the "Future Release" section of
docs/source/release_notes.rstto include this pull request by adding :pr:123.