[
https://issues.apache.org/jira/browse/MAHOUT-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170751#comment-13170751
]
Paritosh Ranjan commented on MAHOUT-825:
----------------------------------------
:). Now I think that stop distance > T1 is increasing the complexity of the
code. We should keep the outlier removal as a separate component. Its messing
up a clean code.
But, post processor will add one more step in the processing which will hit the
performance. I propose to plugin in a outlier removal component in all the
clustering algorithms, with different implementations for different algorithms.
But in a cleaner (segregated) way.
> Canopies grouping records outside t1
> ------------------------------------
>
> Key: MAHOUT-825
> URL: https://issues.apache.org/jira/browse/MAHOUT-825
> Project: Mahout
> Issue Type: Improvement
> Components: Clustering
> Affects Versions: 0.6
> Environment: windows, linux
> Reporter: Paritosh Ranjan
> Assignee: Jeff Eastman
> Labels: features, newbie, patch
> Fix For: 0.6
>
> Attachments: Clustering Remote Points - Two Big, Useless
> Clusters.txt, MAHOUT-825.patch, Not Clustering Remote Points - Two Meaningful
> Clusters.txt, canopy-clusterFilter-t1, canopy-outlier-elimination,
> canopy-outside-t1-points-patch-1, canopy-radius-based-outlier-elimination,
> canopy-strict-clustering-flag
>
>
> While finding closest canopy, there is no check to ensure that it returns
> canopies which are within distance t1 from the point. This results in
> incorrect result i.e. Points outside t1 are grouped in canopies.
--
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
