Segment Statistics does nothing?

Support
1

This is on the 9/28 MacOS nightly. Segment Statistics doesn’t do any calculations - just brings up quantitative window with no output. Anybody else see this or is it just me?

Thanks!

-Hollister

2

Make that 9/27 nightly, and also fails on 9/8 nightly.

Error traceback:

Traceback (most recent call last):
File “/Users/hherhold/Desktop/Slicer.app/Contents/lib/Slicer-4.7/qt-scripted-modules/SegmentStatistics.py”, line 183, in onApply
self.logic.computeStatistics()
File “/Users/hherhold/Desktop/Slicer.app/Contents/lib/Slicer-4.7/qt-scripted-modules/SegmentStatistics.py”, line 420, in computeStatistics
self.updateStatisticsForSegment(segmentID)
File “/Users/hherhold/Desktop/Slicer.app/Contents/lib/Slicer-4.7/qt-scripted-modules/SegmentStatistics.py”, line 429, in updateStatisticsForSegment
if not segmentationNode.GetSegmentation().GetSegment(segmentID):
AttributeError: ‘vtkCommonCorePython.vtkObject’ object has no attribute ‘GetSegment’

3

Thank you for reporting this. I could reproduce this error and fixed it.

The problem was that in certain scenarios it was possible to get to method in SegmentStatistics module that used vtkSegmentationCore before it was imported. We haven’t detected this issue either in our automatic tests or when manually used the feature because when you run Segment Editor then it imports the library and the error does not occur.

@jcfr - it is yet another example why fixing https://issues.slicer.org/view.php?id=4385 would be important. It would be great if you could have a look at it

1 Like
4

Got it. Thanks!!!

-Hollister