Cannot segment beyond frame 182

Hello,

My apologies if this was brought up earlier but I could not find smothing similar in the question bank. I have started using the latest version of 3D slicer 5.8.1 and I noticed that I can only annotate up to frame 182, after that there is no choice to do anything with the dcom file and the frames after that. I have tried everything. used different dcom files, tried to do some digging into with settings . no luck. chat GTP was advising some changes within the

“Export/Import models and labelmaps”**, find the “Specify geometry”.

However I cannot find this option under export/import and labelmaps. I do not even know if this would resolve the problem.

I am in an urgent situation to fix this as it is messing around the annoatation stage of my project and half of the video have not been annotated.. :frowning:

Any help would be so appreciated.

Kind Regards

See detailed instructions for this in the Segment Editor documentation.

@lassoan a different version of this comes up often in our short courses. For better or worse, there is a tendency amongst biologist to crop the image frame extremely tight during the import process (mostly to minimize memory footprint of the volume, since they tend to work with big volumes).

When we run margin or smoothing (for example to fill holes through dilation/erosion) on such image, these operations do not work effectively, since it comes to the edge of the frame. They simply become flat lines. There is also no error/warning (which makes sense because there is actually no error, just a unexpected consequence).

Documentation does not cover anything about how to pad the segmentation geometry, but specifically how to increase/decrease the spacing. The real solution of course is to pad the source volume prior to segmentation via crop volume, but that’s too involved once you are in the thick of the segmentation.

Would it be possible to implement a feature that will notify the user (and if possible automatically pad the segmentation geometry) if it detects the resultant labelmap of the operation will not fit the current segment geometry?