Operating system: Windows 10
Slicer version: 4.8.1 (r26813) built myself
I have started some work on automatic segmentation using the Segment Editor framework. Now I have an automatically generated contour for the spinal canal. The contour is present in some slices (about every 3rd), and is not present in others. Now I thought about including some methodology from “Fill between slices” module. The first attempt before automating is testing manually by clicking through the GUI.
Approach - step by step
Select contour called “Spinal canal” and open “Fill between slices” module
Check the result by using the slider - the results contour is empty
Then I selected the “Paint” module for some testing, draw a small region in an empty slice of “Spinal canal” contour.
Now try “Initialize” again in the “Fill between slices” module, and wow, the result looks good.
Obviously, there’s something wrong which makes my automatically segmented structure not being recognized by the “Fill between slices” module. But what?
I analyzed the source and had a look at the file AbstractScriptedSegmentEditorAutoCompleteEffect.py, and the preview method, there around line 342, which looks like this:
There was a difference in mergedImage variable:
a) In the situation when I used my contour only, mergedImage is empty
b) If I apply some paint operation, mergedImage contains all the masks (the painted + the automatically segmented)
What may be wrong/missing in my auto-segmentation, so that “Fill between slices” won’t recognize my masks?
To find out more, I tried to debug the “Paint” module. I was not successful. Where in the code can I find the “Paint” module methods?
What do you mean by Select contour called “Spinal canal”? You create a segmentation node and create a segment in it (“Spinal canal”)? Does the segment show up correctly in slice views?
Do you mean that slices are filled around the new region only, or throughout the whole image?
Fill between slices only considers visible segments, so make sure you have a display node and the segment is visible. Also, interpolation only happens around slices that have at least one completely empty slice on both sides.
Paint effect is implemented in C++, source code is available on GitHub/Slicer.
Yes, exactly. I have a segmentation node, and in it a few segments. One of them and the only selected and visible is “Spinal canal”. It shows up correctly in slice views.
Slices are filled in all the regions between “Spinal canal” segmented slices, i.e. the whole image. This means also in the slices that were not drawn by Paint, but by my owm method.
In effect, I place one point in one slice by Paint and it works the same for all slices (and as intended). But it does not work at all without putting the point via Paint.
The segment is visible (and selected). Slices in-between are empty.
About the display node, I am a bit unsure, whether I have one or not. But I think I have one. I can run segmentationNode.GetDisplayNode()
and get a vtkMRMLSegmentationDisplayNode as output. Does it mean I do have a display node?
Thanks, so I know where to look and I’ll check it out to see if I can get some hints.
My automatic segmentation method is a separate segment editor effect added to the list of effects (like Paint, Fill between slices or Grow from seeds etc.). It is derived from the SegmentEditorEffect.py example, and modified quite a bit.
It uses numpy and vtk a lot, and convenience functions in slicer.util to convert to segments and back.
If everything works if you save and reload the file then maybe you miss a Modified() event. For example, after you’ve finished changing voxels in numpy, you must call arrayFromVOlumeModified() to signal VTK that the changes are ready to be processed.