BUG while saving data as bundle with no segments

Hello @lassoan @jcfr @pieper @jamesobutler,

I loaded sample data with no segments and then saved it as a bundle.

Next time when i load the bundled file and try to add my first segment the effects does not seem to work. Here’s an image that shows i am not able to adjust threshold value as they appear disabled.

The threshold slider is neither sliding nor the spinner values:

I want to know if this is a bug or something else?

Could be a bug. Can you share an mrb that shows this problem on SampleData along with a step-by-step description of what you did to create it? Also report what Slicer version you used.

1 Like

Sure, here are the steps I followed:

  1. Navigate to File → Download Sample Data → MRHead.
  2. After downloading, simply press Ctrl+S to save the scene as an mrb bundle without making any further changes.
  3. Go to File → Close Scene.
  4. Then go to File → Add Data → Choose file(s) to add and load the previously saved mrb file.
  5. Proceed to the Segment Editor, add one or more segments, and then navigate to the Threshold effect.
  6. Attempt to change the threshold range; you will notice that it won’t work.

Slicer version: 5.6.1 r32438 / 117ce5f

Here’s the mrb file for your reference:

I don’t think this has anything to do with bundle.

When the two sliders overlap (in your case they were both set to 78), they are hard to move around (because you don’t know which one is which). I would suggest typing value in the intensity field in one of the field to move them apart, and then you should be able to move them independently.

Otherwise, everything works as expected for me.

This occurs only when attempting to load a bundle that has no segments.

Is changing the value in the intensity field effective for you? On my end, it doesn’t seem to work. I’ve attempted to modify the value, but it remains unchanged.

This is what I get, following your instructions:


So all looks good to me.

Yes, you should be able to type in a value directly into the
threshold range boxes.

Sorry, I forgot to mention one more step, which is to save the bundle while the segment editor module is open.

I have attached a video for your reference:

@muratmaga @pieper,

Could you please confirm whether this is a bug or not?

Yes, it sounds like a bug and should be filed. Saving and restoring with the segment editor open sounds like a valuable clue. You can file it at Issues · Slicer/Slicer · GitHub and add a link to this discussion.

@lassoan hasn’t commented here yet, but he’ll probably want to have a look.

1 Like

@pieper I’ve filed the issue. See https://github.com/Slicer/Slicer/issues/7576.

@pieper @lassoan
Any update on this issue?

The issue was that you cannot write an image file without voxel data, so an 1x1x1 array was used as image data, but when that segmentation was loaded then the extent was set to that single voxel.

I implemented a fix, just have not yet submitted the pull request.

1 Like

Thanks for the update :pray: