Page MenuHomePhabricator

IsInside function of boundingobjects seems to be broken
Closed, WontfixPublic

Description

if you create a binary image out of a boundingobject, either by iterating over the pixels or using the boundingobjectcutter, there are pixels inside the object that have value 0 instead of 1.

Event Timeline

Can you provide a minimal example that shows the behavior? Ideally as a test case?

the problem only occurs in border areas of rotated mr images.

(In reply to comment #1)

Can you provide a minimal example that shows the behavior? Ideally as a test
case?

i will provide an example, after i have fixed some conversion problems in my code

as mentioned above, the problems only occurs on rotated mr images. on "normal" images the IsInside method evaluates correctly.
My test case: Create a boundingobject (e.g. a cube) and use the BoundingObjectCutter to cut it out.

result when creating a binary image out of a rotated MR when using the BoundingObjectCutter

rotatedMR_Seg1.png (1×1 px, 56 KB)

maybe this is also related to T4692. i'll test it after applying ivo's patch

New account for Danial added as cc.

kislinsk added a subscriber: kislinsk.
This task was automatically closed because it wasn't updated at least since July 2016 (over 2 years). Please re-open this task if you think that it is still relevant. This most probably means that you will resolve it.