[jira] Assigned: (MAHOUT-165) Using better primitives hash for sparse vector for performance gains

[ https://issues.apache.org/jira/browse/MAHOUT-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll reassigned MAHOUT-165: -- Assignee: Grant Ingersoll Using better primitives hash for sparse vector for

[jira] Commented: (MAHOUT-165) Using better primitives hash for sparse vector for performance gains

[ https://issues.apache.org/jira/browse/MAHOUT-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12754586#action_12754586 ] Grant Ingersoll commented on MAHOUT-165: Ted, can you bring your patch up to date

[jira] Commented: (MAHOUT-165) Using better primitives hash for sparse vector for performance gains

[ https://issues.apache.org/jira/browse/MAHOUT-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12754585#action_12754585 ] Grant Ingersoll commented on MAHOUT-165: Shashi, did you try Ted's patch? If that

0.2 planning

Here's the list of unresolved issues for 0.2: https://issues.apache.org/jira/secure/BrowseVersion.jspa?id=12310751versionId=12313278showOpenIssuesOnly=true Can we start to work towards whittling these down and getting 0.2 out? Maybe by mid-October? -Grant

[jira] Updated: (MAHOUT-105) Reconceive refresh / cache update mechanism in CF code

[ https://issues.apache.org/jira/browse/MAHOUT-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated MAHOUT-105: - Fix Version/s: (was: 0.2) Reconceive refresh / cache update mechanism in CF code

Re: 0.2 planning

I am ready for 0.2 myself. I do not have any changes/fixes in mind that I think must be in 0.2 -- have made enough changes for one point release myself. I would like to continue with some movement of code in the common packages, changing code to reuse common code more. I will create issues for

Re: 0.2 planning

Any reason we haven't closed LDA yet https://issues.apache.org/jira/browse/MAHOUT-123 ? -- David On Sat, Sep 12, 2009 at 11:45 AM, Grant Ingersoll gsing...@apache.org wrote: Here's the list of unresolved issues for 0.2:

[jira] Commented: (MAHOUT-172) When running on a Hadoop cluster LDA fails with Caused by: java.io.IOException: Cannot open filename /user/*/output/state-*/_logs

[ https://issues.apache.org/jira/browse/MAHOUT-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12754588#action_12754588 ] David Hall commented on MAHOUT-172: --- Sorry, just noticed this issue! Looks good to me.

[jira] Commented: (MAHOUT-163) Get (better) cluster labels using Log Likelihood Ratio

[ https://issues.apache.org/jira/browse/MAHOUT-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12754590#action_12754590 ] Grant Ingersoll commented on MAHOUT-163: Hmm, deleting the out of cluster docs from

[jira] Updated: (MAHOUT-163) Get (better) cluster labels using Log Likelihood Ratio

[ https://issues.apache.org/jira/browse/MAHOUT-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll updated MAHOUT-163: --- Attachment: MAHOUT-163.patch Updates some of the Lucene code a wee bit. Get (better)

Re: 0.2 planning

I propose leaving MAHOUT-167 out of 0.2 for the reasons which Sean mentioned previously. MAHOUT-136 is, afaict, done and can probably be closed. Grant, you had some comments in the issue; have they been resolved? Grant Ingersoll wrote: Here's the list of unresolved issues for 0.2:

Re: 0.2 planning

+1 for refactor and another release soon after i think MAHOUT-157 FPGrowth needs more work in terms of optimisation and test cases. It may or may not be ready for the mid-oct release. It could be pushed on to the next release if its done soon after 0.2. I can therefore focus more on CBayes/Bayes