[jira] [Updated] (MAHOUT-966) Mismatch in the number of points given by the clusterDumper and ClusterOutputPostProcessor
[ https://issues.apache.org/jira/browse/MAHOUT-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Anil updated MAHOUT-966: -- Assignee: Grant Ingersoll Mismatch in the number of points given by the clusterDumper and ClusterOutputPostProcessor -- Key: MAHOUT-966 URL: https://issues.apache.org/jira/browse/MAHOUT-966 Project: Mahout Issue Type: Bug Components: Integration Affects Versions: 0.6 Environment: hadoop 0.20.2 mahout 0.6 Reporter: Gaurav Redkar Assignee: Grant Ingersoll Priority: Minor Fix For: 0.8 Attachments: cluster-dumper-output.txt, clusterpp-output.txt, mtestdata.txt, points100dCCNorm.txt After running the post processor the number of points that each cluster contains is not matching the number of points each cluster should contain as stated by clusterdumper. MSV-287{ n=90 c=[0.05195, 0.05675, 0.07151, 0.05713, 0.06946,...} MSV-145{ n=90 c=[0.93685, 0.93071, 0.93641, 0.94629, 0.94409,..} the n mentioned in clusters-n-final against each cluster is different from the number of points actually contained in d directory for each cluster. Any idea why is this happening ...? -- 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-966) Mismatch in the number of points given by the clusterDumper and ClusterOutputPostProcessor
[ https://issues.apache.org/jira/browse/MAHOUT-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll updated MAHOUT-966: --- Fix Version/s: 0.8 Mismatch in the number of points given by the clusterDumper and ClusterOutputPostProcessor -- Key: MAHOUT-966 URL: https://issues.apache.org/jira/browse/MAHOUT-966 Project: Mahout Issue Type: Bug Components: Integration Affects Versions: 0.6 Environment: hadoop 0.20.2 mahout 0.6 Reporter: Gaurav Redkar Priority: Minor Fix For: 0.8 Attachments: cluster-dumper-output.txt, clusterpp-output.txt, mtestdata.txt, points100dCCNorm.txt After running the post processor the number of points that each cluster contains is not matching the number of points each cluster should contain as stated by clusterdumper. MSV-287{ n=90 c=[0.05195, 0.05675, 0.07151, 0.05713, 0.06946,...} MSV-145{ n=90 c=[0.93685, 0.93071, 0.93641, 0.94629, 0.94409,..} the n mentioned in clusters-n-final against each cluster is different from the number of points actually contained in d directory for each cluster. Any idea why is this happening ...? -- 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-966) Mismatch in the number of points given by the clusterDumper and ClusterOutputPostProcessor
[ https://issues.apache.org/jira/browse/MAHOUT-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paritosh Ranjan updated MAHOUT-966: --- Summary: Mismatch in the number of points given by the clusterDumper and ClusterOutputPostProcessor (was: Mismantch in the number of points given by the clusterDumper and ClusterOutputPostProcessor) Mismatch in the number of points given by the clusterDumper and ClusterOutputPostProcessor -- Key: MAHOUT-966 URL: https://issues.apache.org/jira/browse/MAHOUT-966 Project: Mahout Issue Type: Bug Components: Integration Affects Versions: 0.6 Environment: hadoop 0.20.2 mahout 0.6 Reporter: Gaurav Redkar Priority: Minor Attachments: cluster-dumper-output.txt, clusterpp-output.txt, mtestdata.txt, points100dCCNorm.txt After running the post processor the number of points that each cluster contains is not matching the number of points each cluster should contain as stated by clusterdumper. MSV-287{ n=90 c=[0.05195, 0.05675, 0.07151, 0.05713, 0.06946,...} MSV-145{ n=90 c=[0.93685, 0.93071, 0.93641, 0.94629, 0.94409,..} the n mentioned in clusters-n-final against each cluster is different from the number of points actually contained in d directory for each cluster. Any idea why is this happening ...? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira