diff options
| author | Xiangrui Meng <meng@databricks.com> | 2014-03-26 19:30:20 -0700 |
|---|---|---|
| committer | Tathagata Das <tathagata.das1565@gmail.com> | 2014-03-26 19:30:20 -0700 |
| commit | d679843a39bb4918a08a5aebdf113ac8886a5275 (patch) | |
| tree | 6438556c9b1fc76dd5bc386113dccdc998348d87 /.travis.yml | |
| parent | 1fa48d9422d543827011eec0cdf12d060b78a7c7 (diff) | |
| download | spark-d679843a39bb4918a08a5aebdf113ac8886a5275.tar.gz spark-d679843a39bb4918a08a5aebdf113ac8886a5275.tar.bz2 spark-d679843a39bb4918a08a5aebdf113ac8886a5275.zip | |
[SPARK-1327] GLM needs to check addIntercept for intercept and weights
GLM needs to check addIntercept for intercept and weights. The current implementation always uses the first weight as intercept. Added a test for training without adding intercept.
JIRA: https://spark-project.atlassian.net/browse/SPARK-1327
Author: Xiangrui Meng <meng@databricks.com>
Closes #236 from mengxr/glm and squashes the following commits:
bcac1ac [Xiangrui Meng] add two tests to ensure {Lasso, Ridge}.setIntercept will throw an exceptions
a104072 [Xiangrui Meng] remove protected to be compatible with 0.9
0e57aa4 [Xiangrui Meng] update Lasso and RidgeRegression to parse the weights correctly from GLM mark createModel protected mark predictPoint protected
d7f629f [Xiangrui Meng] fix a bug in GLM when intercept is not used
Diffstat (limited to '.travis.yml')
0 files changed, 0 insertions, 0 deletions