DOC: Improve terminology clarity - change 'chance level' to 'prevalence baseline' #32057
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for your effort on this PR @Yashp002 , having a deeper look at #30352, it does not look like there is consensus on how to address the issue. Also I don't think "prevalence baseline" is appropriate for both PR curve and ROC curve. Let's close this for now and wait for consensus to be reached in #30352. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Improves terminology clarity in precision-recall curve documentation by changing "chance level" to "prevalence baseline" for better user understanding.
Changes
sklearn/metrics/_plot/precision_recall_curve.pySupersedes #32051 (closed due to force push during cleanup)
Addresses feedback from @lucyleeow
Reference Issues/PRs
What does this implement/fix? Explain your changes.
Any other comments?