-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
FEA Confusion matrix derived metrics #19556
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
FEA Confusion matrix derived metrics #19556
Conversation
Co-authored-by: samskruthi padigepati <https://github.com/ddhar1> Co-authored-by: Divya Dhar<https://github.com/samskruthireddy>
Co-authored-by: samskruthi padigepati <https://github.com/ddhar1> Co-authored-by: Divya Dhar<https://github.com/samskruthireddy>
Co-authored-by: Divya Dhar <https://github.com/ddhar1> Co-authored-by: samskruthi padigepati <https://github.com/samskruthireddy>
Co-authored-by: samskruthi padigepati <https://github.com/samskruthireddy>
Modify doc and add deprecation to position arg.
Add test for binary classification. (Modify some lines to pass flake8)
…into confusion-matrix-derived-metrics
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
specificity_score also needs adding to test_common
@lorentzenchr would you be able to maybe have a look? |
From the long discussion in #5516, better ping @jnothman @amueller @glemaitre . |
@Pawel-Kranzberg Could you please stop merging the main branch as long as there are no merge conflict? The reason is that it might hide discussions in Github and also generates notifications. And it should be in your interest that maintainers don't unsubscribe from this PR. |
Hi everyone, I have need for specificity_score as well and it would be convenient if it worked like Recall and the others that are available. I have added it locally and was considering opening a PR but saw this one was open already. Just seconding that this would be a useful thing. I don't know if there are still plans to merge this PR? Should I open a second PR covering just specificity_score or is this still active? |
From my perspective it is still active. |
Reference Issues/PRs
Continues #17265
Fixes #5516
What does this implement/fix? Explain your changes.
Add
metrics.specificity_score
andmetrics.npv_score
, based onmetrics.fpr_tpr_fnr_tnr_scores
from #17265Any other comments?