quote:
Original post by Predictor
quote:
Original post by Timkin
...I''m not as enthusiastic about methods such as split and merge (heirarchical clustering) or k-means/fuzzy k-means.
Could you elaborate on why? I don''t believe that anyone here is arguing that hierarchical clustering (or any of the other algorithms) is the "be all and end all" of clustering, just that they are useful tools which have proven effective for many problems. If hierarchical clustering hasn''t solved this problem, it certainly seems to be a good start
I''m not suggesting that methods such as split and merge or k-means don''t have their appropriate domain(s) of application, nor that they aren''t useful as a starting point. Simply that for the sorts of segmentation and clustering problems I have worked on, I have found other methods gave better results. For example, MML-based clustering. I find that the performance of most common clustering methods is greatly dependent on the level of noise in the data and they have particular difficulty in dealing with overlapping classes, since they cannot inherently describe partial assignment (although admittedly you can hybridise the method to do this).
In my work on segmenting MRI brain images we have to overcome two serious problems: 1) Sensor noise; and, 2) partial volume effects near tissue boundaries. Methods like split and merge (which for those that don''t know is a combination of top down decomposition and bottom up composition of classes) give acceptable results with regards to noise, but perform poorly on regions showing partial volume. When these two problems are combined, these algorithms tend to fall apart. The benefit of something like an MML based description of classes is that it describes a joint distribution over all things and all classes. ''Snob'' is a good example implementation of an MML based clustering algorithm.
We''ve developed our own in-house algorithm for 3D image segmentation and this outperforms other methods we''ve tested it against. The only comparison we''re yet to perform is against ''FAST''. We''re currently in the process of optimising our implementation and formalising our results and putting some papers together. I''ll be happy to share them with this group once they''re published.
Cheers,
Timkin