See https://builds.apache.org/job/Mahout-Examples-Classify-20News/69/
I made the change on the line in question, but it can't be the problem
since it did not change the functionality. To see that you have to
look at the rest of the change. It is changing...
if (! ) {
A;
} else {
B
}
to
if (foo) {
B
On Wed, Jul 11, 2012 at 3:17 AM, Joshi, Shrinivas
Oops, hit enter too early --
This changes
if (!foo) {
doBar();
} else {
doFoo();
}
to
if (foo) {
doFoo();
} else {
doBar();
}
(among other changes) for readability.
I imagine there could be a problem here but this isn't the change that did it.
On Wed, Jul 11, 2012 at 9:33 AM, Sean
See https://builds.apache.org/job/Mahout-Quality/1579/
Yann Moisan created MAHOUT-1044:
---
Summary: bin/mahout throws NoClassDefFoundError:
org/apache/hadoop/util/ProgramDriver
Key: MAHOUT-1044
URL: https://issues.apache.org/jira/browse/MAHOUT-1044
Project:
See https://builds.apache.org/job/Mahout-Examples-Cluster-Reuters-II/185/
[
https://issues.apache.org/jira/browse/MAHOUT-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen resolved MAHOUT-1044.
---
Resolution: Fixed
Fix Version/s: 0.8
Assignee: Sean Owen
Yep, obvious error --
[
https://issues.apache.org/jira/browse/MAHOUT-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411897#comment-13411897
]
Sean Owen commented on MAHOUT-1020:
---
(Since it's Closed we can't resurrect it in JIRA.
Pat Ferrel created MAHOUT-1045:
--
Summary: Cluster evaluators returning bad results
Key: MAHOUT-1045
URL: https://issues.apache.org/jira/browse/MAHOUT-1045
Project: Mahout
Issue Type: Bug
See https://builds.apache.org/job/Mahout-Examples-Cluster-Reuters/175/changes
See https://builds.apache.org/job/Mahout-Quality/changes
[
https://issues.apache.org/jira/browse/MAHOUT-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411986#comment-13411986
]
Hudson commented on MAHOUT-1044:
Integrated in Mahout-Quality #1580 (See
Hi Sean,
Thanks for the feedback. I did notice changes in the loop bodies, but missed to
see that they were swapped with each other.
Anyways, I think the regression is caused because of the difference in how norm
value makes an effect in 0.6 vs the current trunk. Basically, with the current
See https://builds.apache.org/job/Mahout-Quality/changes
Speaking without actually looking into this, I would say that a -1 norm
doesn't make good sense. If the default value of the norm exponent changed
to -1, it would wreak various kinds of havoc and would be a Bad Thing(tm).
However, regardless of that, since I haven't looked at the code in
[
https://issues.apache.org/jira/browse/MAHOUT-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13412414#comment-13412414
]
Leting Wu commented on MAHOUT-1034:
---
Hi, jayghost. Have you tried it out?
I have
[
https://issues.apache.org/jira/browse/MAHOUT-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leting Wu resolved MAHOUT-1034.
---
Resolution: Not A Problem
The default setting is to run Mahout on a cluster. When run on a single
I spent some more time looking in to this. I think the problem here might be
more than just the value of norm that gets passed to createTermFrequencyVectors
methods. I will update this thread I can root cause this issue. I would
appreciate if someone has any pointers/suggestions about what
18 matches
Mail list logo
