You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Paritosh Ranjan (Commented) (JIRA)" <ji...@apache.org> on 2011/12/19 19:39:30 UTC
[jira] [Commented] (MAHOUT-931) Implement a pluggable outlier
removal capability for cluster classifiers
[ https://issues.apache.org/jira/browse/MAHOUT-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172480#comment-13172480 ]
Paritosh Ranjan commented on MAHOUT-931:
----------------------------------------
This story depends on implementation/design of Mahout-930. I think Mahout-930's design of Vector classification is chalked out pretty nicely. We can start working to implementing all the policies, and other improvements.
But before going on fully implementing the Cluster Classification, I think it would be good to at least finalize the interface for Outlier Removal. I also think that binding it only to an outlier removal is not going to help forever.
So, following the open closed principle. Lets close it for further modification by plugging a Collection<Strategy> into the Policy. The Strategy can be outlier removal or any other feature which can be developed by implementing Strategy interface. So, this will also keep it open for extension. "Strategy" is just a thought, it can be any other name.
I will try to submit a patch for some mock/Canopy Outlier Removal first, by implementing "Strategy". If the design works and look good, then the designing part would be over.
Does it look like a good way to proceed? Any suggestions?
> 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
>
>
> 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