| • kilgus | |
| Sep 1 2011, 11:22 AM |
| F728: VTKRenderingBranchPic3D.png | |
| Sep 5 2011, 10:56 AM |
| F727: 3M3RenderingPic3D.png | |
| Sep 5 2011, 10:56 AM |
| F726: dicom.bmp | |
| Sep 5 2011, 10:48 AM |
The level window is slightly off (just open the same picture with an old and a
new rendering mechanism, move them over each other and compare by eyeball ).
However, the new level window has slightly more contrast compared to the old level window. I think the iil is using some lights on the scene and I turned the light VTK is using for rendering off.
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | None | T7027 Meta Bug: Rework the 2D rendering | ||
| Resolved | None | T9236 [2DRendering] Level window is slightly off |
This should be compared to some reference for the same data and same level window settings:
http://support.dcmtk.org/docs/dcm2pnm.html
cc Daniel
This bug seems to be a lot of fun ...
The attached image "dicom.bmp" is a slice which I converted to .bmp via dcm2pnm. It looks identical in 3M3 and my rendering branch. However, for this image the default level window has a quite small range (127/255).
Pic3D looks different in both 3M3 and my branch. I also attached screenshots. We still don't know which version is "correct". How can I convert Pic3D to a dicom image or who can provide a dicom image with a higher level window range?
I used another dicom image to figure out which level window is correct:
The old level window from of the iil is correct, however, the old VTK 3D render window used to show also the wrong level window. So this bug was already present before my rendering changes, yet not recognized.
By default, the VTK lookuptable uses a curved interpolation function. We changed this to a linear interpolation.
