Page MenuHomePhabricator

volume render not updated upon segmentation update
Closed, ResolvedPublic

Description

the volume render of a segmentation (actually of any image) is not updated when the segmentation is updated

that should be the case after every image->modified() request. Is that correct? how to force the update of the volume render? (also useful when applying a mask to the underlying image in the VR)

Event Timeline

Resetting all bugs without active assignee flag to "CONFIRMED". Change status to IN_PROGRESS if you are working on it.

Hello guys, last night I checked the status of this bug/problem in the current git master, and the issue persists.

could you check if the issue is also happening on your side?

test procedure:

  • load an image
  • load or do some segmentation
  • enable volume rendering on the segmentation
  • continue segmenting
  • is the VR updated?
  • if no, try disabling VR and enabling it again: does the VR looks like in the first time you run it?

any hint?

thanks!

Seems to be a bug. We will have a look at it.

MITK-1-0 keyword is obsolete, we use Target Milestones in the future.

This bug was discovered during testing of 2012-06, updating version. Target milestone is unspecified until general bug review, but feel free to fix it before.

This bug was discovered during testing of 2012-06, updating version. Target milestone is unspecified until general bug review, but feel free to fix it before.

Major loss of function, since VR is lost during segmentation.

[26383c]: Merge branch 'bug-3499-SegmentationVolumeModifiedforRendering'

Merged commits:

2012-10-31 18:18:22 Christian Weber [6aeaaa]
Manually called vtkImageDatas modified function

Necessary since Modified on mitkImages does not call modified function on vtkImages.

Fixed with a workaround. For final solution, the mitkImage modified-function needs to be extended to ensure that also the inlcuded vtkImage status is set to modified. See T13526