View Issue Details

IDProjectCategoryView StatusLast Update
0002165Slicer4Module VolumeRenderingpublic2016-01-15 04:21
Reporterkikinis Assigned Tofinetjul  
PrioritynormalSeveritymajorReproducibilitysometimes
Status closedResolutionfixed 
Product VersionSlicer 4.1.0 
Target VersionSlicer 4.2.0Fixed in VersionSlicer 4.2.0 
Summary0002165: Volume rendering labelmap
Description

From Ron:
I tried to volume render the label map that comes with the atlas after turning off the models.

Interesting result. Not what I expected.

Why is the right half of the brain not rendered? Why does the VR not use the LUT as displayed in the slice viewer?

When I switch the VR to a grey scale volume and back, I get the monochrome LUT. This is on today (2012/06/05) example of the atlas in rons examples

TagsNo tags attached.

Relationships

related to 0002527 closedfinetjul Volume renderer does not handle label map with custom lut properly 
related to 0002135 closedfinetjul volume rendering label map does not work properly 
related to 0002084 closedfinetjul Transfer function does not allow to access full range of signal intensities 

Activities

2012-06-05 12:42

 

kikinis

kikinis

2012-06-06 04:03

developer   ~0004777

Could this be an interpolation effect? The data uses a custom lut and slicer has been balking at some of it, because there are numeric ranges which are empty, sandwiched by areas with value/name/color.

finetjul

finetjul

2012-06-06 11:05

administrator   ~0004781

The problems is that the lut is too wide: >1024.
A first error is in vtkSlicerVolumeRenderingLogic::SetLabelMapToVolumeProp that "offsets" the values (label 2 has an X of 8) because of an error in scaling.
But removing the 1024 boundary doesn't fix the issue neither, there must be some subsampling happening later in the volume rendering pipeline.
Subsampling can discard labels. In this case, the white matter (label 2 color white) is discarded by the surrunding transparent values.
Need more investigation in the volume rendering pipeline

finetjul

finetjul

2012-10-29 16:09

administrator   ~0006893

Fixed in r21277

msmolens

msmolens

2016-01-14 14:04

developer   ~0013722

Is the dataset for this issue still available?

kikinis

kikinis

2016-01-15 04:21

developer   ~0013724

You can take the most recent version from this page:
http://www.spl.harvard.edu/publications/item/view/2037

Issue History

Date Modified Username Field Change
2012-06-05 12:42 finetjul New Issue
2012-06-05 12:42 finetjul Status new => assigned
2012-06-05 12:42 finetjul Assigned To => finetjul
2012-06-05 12:42 finetjul File Added: Screen Shot 2012-06-05 at 3.18.38 PM.png
2012-06-05 12:43 finetjul Reporter finetjul => kikinis
2012-06-05 12:43 finetjul Description Updated
2012-06-06 04:03 kikinis Note Added: 0004777
2012-06-06 11:05 finetjul Note Added: 0004781
2012-06-15 09:24 finetjul Relationship added related to 0002135
2012-10-23 13:10 jcfr Relationship added related to 0002084
2012-10-29 07:30 finetjul Relationship added related to 0002527
2012-10-29 16:09 finetjul Note Added: 0006893
2012-10-29 16:09 finetjul Status assigned => resolved
2012-10-29 16:09 finetjul Fixed in Version => Slicer 4.2.0 - coming release
2012-10-29 16:09 finetjul Resolution open => fixed
2012-11-23 05:15 kikinis Status resolved => closed
2016-01-14 14:04 msmolens Note Added: 0013722
2016-01-15 04:21 kikinis Note Added: 0013724