I’m trying to use watershed segmentation (5.12.4 on Win10) and I get a segmentation fail message. This is what I get on detials:
Traceback (most recent call last):
File “C:\Users/JSG/AppData/Local/slicer.org/3D Slicer 5.12.4/bin/Python\slicer\util.py”, line 3614, in tryWithErrorDisplay
yield
File “C:\Users\JSG\AppData\Local\slicer.org\3D Slicer 5.12.4\lib\Slicer-5.12\qt-scripted-modules\SegmentEditorEffects\AbstractScriptedSegmentEditorAutoCompleteEffect.py”, line 303, in onPreview
self.preview()
File “C:\Users\JSG\AppData\Local\slicer.org\3D Slicer 5.12.4\lib\Slicer-5.12\qt-scripted-modules\SegmentEditorEffects\AbstractScriptedSegmentEditorAutoCompleteEffect.py”, line 567, in preview
File “C:/Users/JSG/AppData/Local/slicer.org/3D Slicer 5.12.4/slicer.org/Extensions-34645/SegmentEditorExtraEffects/lib/Slicer-5.12/qt-scripted-modules/SegmentEditorWatershedLib/SegmentEditorEffect.py”, line 111, in computePreviewLabelmap
You are not doing anything wrong, this is a known bug in the extension, not a workflow issue. The exact same traceback (SimpleITK ReadImage failing on the slicer: pseudo file path) is filed in the SegmentEditorExtraEffects issue tracker as issue 71, reported against 5.12 and still open. Painting seeds in two segments is exactly how the effect is meant to be used. Until it gets fixed, the built-in Grow from seeds effect in Segment Editor covers the same seed-based workflow without using the extension’s code. You can subscribe to the issue on GitHub to get notified when a fix lands.