[jira] [Updated] (MAHOUT-1263) Serialise/Deserialise Lambda value for OnlineLogisticRegression
[ https://issues.apache.org/jira/browse/MAHOUT-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Davy updated MAHOUT-1263: -- Attachment: MAHOUT-1263.patch Serialise/Deserialise Lambda value for OnlineLogisticRegression Key: MAHOUT-1263 URL: https://issues.apache.org/jira/browse/MAHOUT-1263 Project: Mahout Issue Type: Bug Components: Classification Affects Versions: 0.7 Reporter: Mike Davy Labels: patch Attachments: MAHOUT-1263.patch Original Estimate: 0.5h Remaining Estimate: 0.5h The value for Lambda in OnlineLogisticRegression seems not the be serialised/deserialised correctly. If I train a model with a specific lambda value, serialise it, then read it back in, the value of Lambda goes back to the default value (1.0e-5). I've created a patch that adds the lambda value into the write/readFields (org.apache.hadoop.io.Writable). Patch includes a unit test that checks the values after serialising/deserialising to/from a ByteArray. I think this is correct, unless I'm missing something obvious? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAHOUT-1263) Serialise/Deserialise Lambda value for OnlineLogisticRegression
[ https://issues.apache.org/jira/browse/MAHOUT-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Davy updated MAHOUT-1263: -- Status: Patch Available (was: Open) Serialise/Deserialise Lambda value for OnlineLogisticRegression Key: MAHOUT-1263 URL: https://issues.apache.org/jira/browse/MAHOUT-1263 Project: Mahout Issue Type: Bug Components: Classification Affects Versions: 0.7 Reporter: Mike Davy Labels: patch Attachments: MAHOUT-1263.patch Original Estimate: 0.5h Remaining Estimate: 0.5h The value for Lambda in OnlineLogisticRegression seems not the be serialised/deserialised correctly. If I train a model with a specific lambda value, serialise it, then read it back in, the value of Lambda goes back to the default value (1.0e-5). I've created a patch that adds the lambda value into the write/readFields (org.apache.hadoop.io.Writable). Patch includes a unit test that checks the values after serialising/deserialising to/from a ByteArray. I think this is correct, unless I'm missing something obvious? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAHOUT-1263) Serialise/Deserialise Lambda value for OnlineLogisticRegression
[ https://issues.apache.org/jira/browse/MAHOUT-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Davy updated MAHOUT-1263: -- Description: The value for Lambda in OnlineLogisticRegression seems not the be serialised/deserialised correctly. If I train a model with a specific lambda value, serialise it, then read it back in, the value of Lambda goes back to the default value (1.0e-5). I've created a patch that adds the lambda value into the write/readFields (org.apache.hadoop.io.Writable). Patch includes a unit test that checks the values after serialising/deserialising to/from a ByteArray. I think this is correct, unless I'm missing something obvious? Note: this patch is not backwards compatible - can easily adapt to be more backwards compatible if required. was: The value for Lambda in OnlineLogisticRegression seems not the be serialised/deserialised correctly. If I train a model with a specific lambda value, serialise it, then read it back in, the value of Lambda goes back to the default value (1.0e-5). I've created a patch that adds the lambda value into the write/readFields (org.apache.hadoop.io.Writable). Patch includes a unit test that checks the values after serialising/deserialising to/from a ByteArray. I think this is correct, unless I'm missing something obvious? Serialise/Deserialise Lambda value for OnlineLogisticRegression Key: MAHOUT-1263 URL: https://issues.apache.org/jira/browse/MAHOUT-1263 Project: Mahout Issue Type: Bug Components: Classification Affects Versions: 0.7 Reporter: Mike Davy Labels: patch Attachments: MAHOUT-1263.patch Original Estimate: 0.5h Remaining Estimate: 0.5h The value for Lambda in OnlineLogisticRegression seems not the be serialised/deserialised correctly. If I train a model with a specific lambda value, serialise it, then read it back in, the value of Lambda goes back to the default value (1.0e-5). I've created a patch that adds the lambda value into the write/readFields (org.apache.hadoop.io.Writable). Patch includes a unit test that checks the values after serialising/deserialising to/from a ByteArray. I think this is correct, unless I'm missing something obvious? Note: this patch is not backwards compatible - can easily adapt to be more backwards compatible if required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAHOUT-1263) Serialise/Deserialise Lambda value for OnlineLogisticRegression
[ https://issues.apache.org/jira/browse/MAHOUT-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated MAHOUT-1263: -- Resolution: Fixed Fix Version/s: 0.8 Status: Resolved (was: Patch Available) Patch committed to trunk. Serialise/Deserialise Lambda value for OnlineLogisticRegression Key: MAHOUT-1263 URL: https://issues.apache.org/jira/browse/MAHOUT-1263 Project: Mahout Issue Type: Bug Components: Classification Affects Versions: 0.7 Reporter: Mike Davy Assignee: Suneel Marthi Labels: patch Fix For: 0.8 Attachments: MAHOUT-1263.patch Original Estimate: 0.5h Remaining Estimate: 0.5h The value for Lambda in OnlineLogisticRegression seems not the be serialised/deserialised correctly. If I train a model with a specific lambda value, serialise it, then read it back in, the value of Lambda goes back to the default value (1.0e-5). I've created a patch that adds the lambda value into the write/readFields (org.apache.hadoop.io.Writable). Patch includes a unit test that checks the values after serialising/deserialising to/from a ByteArray. I think this is correct, unless I'm missing something obvious? Note: this patch is not backwards compatible - can easily adapt to be more backwards compatible if required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
