Should we do something about EM segmenter?

Should we do something about EM segmenter? Test failures on the dashboard indicate that it is not working anymore. It seems that TCL/Python bridge is not functional.

I vote for removing EMSegment - it’s not being supported by the original developers and I haven’t heard from user’s having much luck with it lately, even when it was working. If anyone knows differently please speak up.

The tcl/python issue looks fixable, but I believe that bridge code is only used in EMSegment so there may be no point in maintaining it.


As discussed with the author of EMSegment modules, there are no resources to maintain it. For now, we will simply disable the TCL support in Slicer which will automatically disable the building of EMSegment modules.

If users express interest, we can revisit.

1 Like


I was looking at automatic segmentation on 3d slicer and EM Segmentation popped up. I was not able to find it on the modules, therefore i checked on the forum and found out the news.

I wanted to know that is there a possibility of applying this module to other parts apart from Brain MRIs if it still existed as a slicer module. I wanted to do segmentation on multiple MRIs and thought something like this would help.
Please advice me.

Thank You!

All classic automatic segmentation methods (that were developed in the last few decades) have been abandoned and all efforts are directed to make deep learning based methods work. Even when limitations of this new approach will become apparent, it is very unlikely that classic methods, such as the EM segmenter, would ever return, as computing infrastructure, skills of researchers, familiarity of clinicians, and investment of companies and hospitals will all make the landscape more favorable for deep learning based methods.