Uh oh!
There was an error while loading. Please reload this page.
[SPARK-18476][SPARKR][ML]:SparkR Logistic Regression should should support output original label. - #15910
[SPARK-18476][SPARKR][ML]:SparkR Logistic Regression should should support output original label.#15910wangmiao1981 wants to merge 7 commits into
Conversation
There was a problem hiding this comment.
Removed unused import in this PR, because this one line change is not encouraged as a separate PR.
SparkQA
commented
Nov 17, 2016
Test build #68737 has finished for PR 15910 at commit
|
shivaram
commented
Nov 17, 2016
cc @yanboliang |
SparkQA
commented
Nov 17, 2016
Test build #68739 has finished for PR 15910 at commit
|
wangmiao1981
commented
Nov 17, 2016
retest this please. |
SparkQA
commented
Nov 17, 2016
Test build #68741 has finished for PR 15910 at commit
|
wangmiao1981
commented
Nov 17, 2016
the failure occurs in kafka-streaming. retest this please. |
wangmiao1981
commented
Nov 17, 2016
retest this please |
SparkQA
commented
Nov 17, 2016
Test build #68751 has started for PR 15910 at commit |
yanboliang
commented
Nov 17, 2016
Jenkins, test this please |
SparkQA
commented
Nov 17, 2016
Test build #68781 has finished for PR 15910 at commit
|
There was a problem hiding this comment.
nit: would be great to align the tolerance parameter with indentation
There was a problem hiding this comment.
how reliable is this test? the order of rows is not guaranteed unless it is enforced by a sort or something, right?
There was a problem hiding this comment.
Theoretically, the order is not guaranteed. However, we did similar work from the first test case of mllib.R, but never had a problem until now. I'd like to enforce the tests here and other places, but may be in a separate work should be better since it involves lots of other tests?
There was a problem hiding this comment.
sounds good, separate JIRA then. If tests haven't been failing perhaps it is not huge problem
There was a problem hiding this comment.
I will try to create follow-up jira for this.
There was a problem hiding this comment.
off-topic, but I think it's a bug. We should not allow users pass fitIntercept to control whether to fit intercept, this should be handled by formula. For example, if users specify formula y ~ a + b + c - 1, then the model should be fitted w/o intercept. Could you please fix this bug as well? Thanks.
There was a problem hiding this comment.
OK. Fix it in this PR
There was a problem hiding this comment.
Usually we name it as features.
wangmiao1981
commented
Nov 22, 2016
I am on travel now. I will address the comments asap. Thanks! |
SparkQA
commented
Nov 28, 2016
Test build #69255 has finished for PR 15910 at commit
|
SparkQA
commented
Nov 29, 2016
Test build #69268 has finished for PR 15910 at commit
|
wangmiao1981
commented
Nov 29, 2016
@yanboliang@felixcheung I am back from vacation and made changes according to your comments. Thanks! |
| #' features2 <- c(2.941319, 2.614812, 2.162451, 3.339474, 2.970987) | ||
| #' features3 <- c(1.322733, 1.348044, 3.861237, 9.686976, 3.447130) | ||
| #' features4 <- c(1.3246388, 0.5510444, 0.9225810, 1.2147881, 1.6020842) | ||
| #' data <- as.data.frame(cbind(label, features1, features2, features3, features4)) |
There was a problem hiding this comment.
Nit: Actually you should not change it, usually the whole feature column were called as features.
felixcheung
commented
Nov 30, 2016
LGTM. we need to get this in branch-2.1 because of the signature change |
SparkQA
commented
Nov 30, 2016
Test build #69413 has finished for PR 15910 at commit
|
yanboliang
commented
Dec 1, 2016
Merged into master and branch-2.1. Thanks. |
…pport output original label. ## What changes were proposed in this pull request? Similar to SPARK-18401, as a classification algorithm, logistic regression should support output original label instead of supporting index label. In this PR, original label output is supported and test cases are modified and added. Document is also modified. ## How was this patch tested? Unit tests. Author: wm624@hotmail.com <wm624@hotmail.com> Closes#15910 from wangmiao1981/audit. (cherry picked from commit 2eb6764) Signed-off-by: Yanbo Liang <ybliang8@gmail.com>
yanboliang
commented
Dec 1, 2016
I found the |
wangmiao1981
commented
Dec 1, 2016
The summary returns the same as scala side summary, including roc, areaUnderROC, pr, fMeasureByThreshold etc. I think we can add |
…pport output original label. ## What changes were proposed in this pull request? Similar to SPARK-18401, as a classification algorithm, logistic regression should support output original label instead of supporting index label. In this PR, original label output is supported and test cases are modified and added. Document is also modified. ## How was this patch tested? Unit tests. Author: wm624@hotmail.com <wm624@hotmail.com> Closesapache#15910 from wangmiao1981/audit.
…pport output original label. ## What changes were proposed in this pull request? Similar to SPARK-18401, as a classification algorithm, logistic regression should support output original label instead of supporting index label. In this PR, original label output is supported and test cases are modified and added. Document is also modified. ## How was this patch tested? Unit tests. Author: wm624@hotmail.com <wm624@hotmail.com> Closesapache#15910 from wangmiao1981/audit.
What changes were proposed in this pull request?
Similar to SPARK-18401, as a classification algorithm, logistic regression should support output original label instead of supporting index label.
In this PR, original label output is supported and test cases are modified and added. Document is also modified.
How was this patch tested?
Unit tests.