SingleSliceSegmentation segmentable area is limited/cropped

Hi, I am trying to use the SingleSliceSegmentation Module to track indiviual images to use with the AIGT code published by Ungi, T., King, F., Kempston, M., Keri, Z., Lasso, A., Mousavi, P., . . . Fichtinger, G. (2014). Spinal Curvature Measurement by Tracked Ultrasound Snapshots. Ultrasound in medicine & biology, 40(2), 447-454. doi:https://doi.org/10.1016/j.ultrasmedbio.2013.09.021

However, there seems to be a very strange bug happening in that i can only perform paint segmentation in a very small area and I am not sure what is limiting this. In the image below, you can see i have filled out the volume that it is allowing me to segment.

I have tried to perform this without performing volume reconstruction and after performing volume reconstruction and there does not appear to be a difference.

Any help would be much appreciated

Thanks, Logan

Slicer version 4.11
3D ultrasound data was collected with OptiTrack and Telemed ultrasound hardware.
motion capture and ultrasound data were combined to create the ImageToReference-Image


What does your transform hierarchy look like?

Hi Kyle, Here is the data structure after performing volume reconstruction.

image
image

Hi @Sunderlandkyl,

Do you have any idea what might be causing this issue?

Regards,

Logan

I don’t see the segmentation in the transform hierarchy. Can you make sure that the same transform is applied to both the segmentation and the ultrasound image?

Hi @Sunderlandkyl

When I start doing segmentations this is what my data tree looks like.
image

  1. Do I need to perform volume reconstruction before doing segmentation?
  2. Should the Segmentation be within the Logan2_ImageToReference-ImageToReference tree? I have tried this but performing segmentation like this extremely slows down the processing of every single click and furthermore, you end up the segmentation in the 3D view being smaller and in the wrong location.

I cannot find any information for how the single slice segmentation is actually meant to work? It is very frustrating because opening slicer and doing the exact same steps results in different results, sometimes it will not even draw a segmentation on any frame, sometimes it is only 1 frame out of the whole sequence and then other times it will do most of the area except for having an border that also is never in the same place.

@lassoan, Do you remember what the required steps are to use SingleSliceSegmentation?

You need to put the segmentation under the same transform as the image. The segmentation’s geometry is specified the first time you select a master volume, so if you have already started segmentation under the wrong transform then delete the segmentation node, put it under the same parent as the image, and then start the segmentation.

Sequences should be set up similarly carefully (a new sequence browser needs to be created and a new sequence must be added to it that uses the segmentation node as proxy node).

These steps are very error-prone to perform manually. Current users create these scenes using Python scripts. @Sunderlandkyl I think we must fix this as part of the Canarie project (make the module automatically create all the necessary nodes and set parent transforms, etc.).

1 Like