Adding sklearn Classification Report #496
Open
Conversation
This file contains 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
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.
Working with a skewed dataset, it may be helpful to view the precision and f1 scores of the model in addition to the other metrics nativley supported.
What kind of change does this PR introduce?
This PR provides the option for the user to pass in "classification_report" as one of the metrics to select to view for their model.
Does this PR introduce a breaking change?
I dont think so.
What needs to be documented once your changes are merged?
That classification reports are one of the optional default metrics, and can be requested under the string "classification_report". Documentation in the 'metrics.py' file have been updated as part of this PR.
Closing issues
closes #489