[ 
https://issues.apache.org/jira/browse/MAHOUT-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176331#comment-13176331
 ] 

Jeff Eastman commented on MAHOUT-931:
-------------------------------------

1. I don't see a reason to introduce ClusterConfigs yet. I believe the various 
CLI arguments can be carried in the appropriate ClusteringPolicy 
implementations.

2. Other than augmenting what exist already with some more CLI arguments, I 
think this is done

3. Outlier removal is not a part of the buildClusters step, rather the 
clusterPoints step. I thought you were going to work on those stories while I 
finish up the mapreduce implementation of buildClusters using 
ClusterIterator/Classifier/Policies (MAHOUT-933)? This story (MAHOUT-931) 
should follow after -929 & -930, IMHO, for example:
 - 929 implement a new post processor that does only classification as required 
by the various clusterPoints steps.
 - 930 modify the existing drivers to use this post processor rather than their 
current, custom implementations.
 - 931 modify the post processor to support pluggable outlier removal.

4. This can be done once -933 is complete.

In any case, this is all post-0.6 stuff. Let's leave trunk where it is with the 
renaming for now.
                
> Implement a pluggable outlier removal capability for cluster classifiers
> ------------------------------------------------------------------------
>
>                 Key: MAHOUT-931
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-931
>             Project: Mahout
>          Issue Type: Improvement
>          Components: Classification, Clustering
>    Affects Versions: 0.6
>            Reporter: Paritosh Ranjan
>             Fix For: 0.7
>
>         Attachments: MAHOUT-931
>
>
> A pluggable outlier removal capability while classifying the clusters is 
> needed. The classification and outlier removal implementations, both should 
> be completely separate entities for better abstraction. 

--
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

        

Reply via email to