Skip to content
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

[SPARK-6332] [MLlib] compute calibration curve for binary classifiers #10666

Closed
wants to merge 21 commits into from

Conversation

robert-dodier
Copy link

This PR is a revised, updated version of the previous (PR #5025), which was closed for lack of activity. I have now addressed the comments about coding style, so I'd like to get the ball rolling again. I am opening a new PR as that was requested when the previous PR was closed.

The corresponding issue, SPARK-6332, is still applicable; the proposed functionality is the same as before.

Robert Dodier added 21 commits October 5, 2015 15:40
 o ProbabilisticClassifier.scala:
    mention calibration in comments

 o BinaryClassificationMetrics.scala:
    adapting code for ROC to calibration; incomplete and commented
    out for now

 o BinaryClassificationMetricsSuite.scala:
    tests for calibration
types to what calibration actually returns.
 o ProbabilisticClassifier.scala:
    mention calibration in comments

 o BinaryClassificationMetrics.scala:
    adapting code for ROC to calibration; incomplete and commented
    out for now

 o BinaryClassificationMetricsSuite.scala:
    tests for calibration
types to what calibration actually returns.
string interpolation instead of pasting string together.
 * replace some tuples with named variables via pattern matching
 * describe use of numBins parameter
 * revise description of return value
 * break lines that are too long
 * remove trailing whitespace
@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@rxin
Copy link
Contributor

rxin commented Jun 15, 2016

Thanks for the pull request. I'm going through a list of pull requests to cut them down since the sheer number is breaking some of the tooling we have. Due to lack of activity on this pull request, I'm going to push a commit to close it. Feel free to reopen it or create a new one.

For this one please feel free to ping some of the committers active on ml, e.g. @jkbradley, @dbtsai, @yanboliang

@asfgit asfgit closed this in 1a33f2e Jun 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants