Page MenuHomePhabricator

RDF: Volume rendering of multiple segmentations and cross hair
Closed, WontfixPublic

Assigned To
Authored By
lodron
Jan 30 2012, 12:47 PM
Referenced Files
F779: VolumeWoSegmentation.png
Nov 7 2012, 3:42 PM
F778: VolumeAndSegmentation.png
Nov 7 2012, 3:42 PM
F777: Screenshot from 2012-10-09 09:04:48.png
Oct 9 2012, 9:07 AM
F776: Screenshot from 2012-10-09 09:04:35.png
Oct 9 2012, 9:06 AM
F775: Screenshot from 2012-10-09 08:54:45.png
Oct 9 2012, 9:01 AM

Description

Create two binary images and enable on both volume rendering, only one of them is rendered instead of both...

Event Timeline

In the current release, this is different. I cannot reproduce your reported behavior, however, if I disable the cross hair, only the first segmentation is shown in volume rendering which is a major loss of function.

Cross hair on - 3 segmentations are visible in volume rendering

Screenshot from 2012-10-09 09:04:35.png (1×1 px, 413 KB)

cross hair off - only the first segmentation is visible

Screenshot from 2012-10-09 09:04:48.png (1×1 px, 253 KB)

I added two screen shots to document the bug.

The problem seems to be that result segmentation rendering is surrounded by a black box, which hides the other segmentations. All objects with a layer higher than the first segmentation are hidden.

If a second images is loaded and rendered (with lower layer than the segmentation) it is also (partly) hidden behind the segmentation.
So this is a general rendering issue, since "empty" voxels are rendered as solid black voxels instead of opaque voxels.

See attached screenshots.

Volume partially hidden by rendererd segmentation

VolumeAndSegmentation.png (403×537 px, 69 KB)

View without segmentation being shown.

VolumeWoSegmentation.png (377×417 px, 72 KB)

Michael Goetz, what is the status here? Can we close this?

Bug is still valid, so bug remains open.

What is the status of this bug? Please change the target milestone to "AfterNextRelease" if this bug is not relevant or cannot be fixed in time for the 2013-06 release.

This bug could not be fixed for release 2013-06. Setting target milestone to next release

Interestingly the volumerenderings works with the CPU rendering options. The GPU options show only the segmentation with the lowest layer-value.

At the moment it is not possible to volume render more than one binary image. There are two possible solutions:

  • merge the binary images and render the merge image
  • wait for the multilabel binary images ( several segmentations saved as one image )

The problem is that a binary image is as big as the original image with transparent color.

How important is this for you? Could you adapt severity and importance, if necessary?

I don't know how important this is and if we should urgently spend resources to fix it. Can someone of the segmentation group please give a comment?

I would suggest to wait for the multilabel stuff. This bug will most likely not be fixed within the next week, so I will change the target milestone.

Current release is finished. Reseting target milestone...

Andi, is this important for the segmentation group or can we close it?

kislinsk claimed this task.
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.