Page MenuHomePhabricator

Autocropping segmentations produces offset (due to padding)
Closed, ResolvedPublic

Description

Reproduction of this bug:

  • start ExtApp with segmentation view, load Pic3D
  • create a quick segmentation covering a couple of slices (e.g. using interpolation)
  • create a surface model using the data manager context-menu
  • you can observe that surface and binary image align in the sagittal view
  • now choose "autocrop" from the data manager context-menu
  • scroll a slice or two in sagittal
  • by now the surface and the binary image misalign (see screenshot)

I suspect that this has to do with the recent change in autocropping: a padding is applied to create "closed" surfaces from cropped images. This padding is not taken into account when setting the cropped image's geometry.

Ingmar, I'm assinging this to you because I think you changed the padding, right?

Please wait with fixing this bug until I finished #3163 which involves quite some code restructuring.

.1 (ITK 3.16.0  VTK 5.4.0 Qt 4.5.3 MITK n-a) (Not for use in diagnosis or treatment of patients).png (1×1 px, 277 KB)

Event Timeline

#3384 is most probably a duplicate. I'm leaving this bug here open because it has a description of how to reproduce the bug.

In QmitkSegmentationPostProcessing::IncreaseCroppedImageSize the origin of the
new segmentation image should also be translated according to the added offset.

This should/could solve the problem.

[SVN revision 21849]
FIX (#3263): Added a file chooser widget (a button + lineedit + filedialog)

[SVN revision 21850]
COMP (#3263): Fixed EndoTracking dependency for landmarktracking

(In reply to comment #5)

[SVN revision 21849]
FIX (#3263): Added a file chooser widget (a button + lineedit + filedialog)

wrong bug id?

[SVN revision 21869]
FIX (#3263): fixed offset problem due to padding, geometry is now also translated