Operating system:Linux 64bit
Slicer version:4.7.0-2017-03-21
Expected behavior:
Actual behavior:
Could you be a bit more specific?
The window width/level (brightness/contrast) is computed for each new volume (even if it was generated from an existing volume). You may have to click-and-drag in the slice viewer to adjust brightness/contrast or go to Volumes module and copy the window width/level from the input volume to make the processed volume look the same as the input.
Hi Andras thank you so much for replying and apologies for not providing enough details.
Briefly I am using Slicer to realign CT images . After creating a new transform I use the Reslice Scalar/DWI Volume module to apply the transform to the original volume and create a new volume ready to be exported.
Now, the main goal of my analysis is to calculate the average density of the skull bone : so when I calculate the density on the volume after reslicing the intensities are different(they are higher) and this changes the outcome of the density of the bone computation. Is there a way to maintain the intensities or any workaround?
thanks
Can’t you calculate the density before reslicing?
Are you able to reproduce the issue using data you can share (or using the existing sample data)? I don’t think the reslicing should change the pixel values, but maybe the way the are displayed as Andras noted. You can try using the DataProbe to look at the actual values before and after reslicing.
Hi Steve
thank you a lot for your email. I repeated the procedure with the stable
version for Linux and this issue disappeared. At this point I think the
issue was due to an old nightly build version of Slicer.
Francesco Sammartino MD