VR Lookup Table for 3D rendering

The transfer function is based on the actual underlying data, not on the post-windowed (0-256) values DicomObjects handles the shading internally, so as a user you simply need to provide TF values. One thing which might not be immediately clear is that the TF needs to cover the full range of available pixel values BEFORE any interpretation based on bit depth, re-scaling or even signed/unsigned are applied – hence the 65536 values, with the negative values at the very top of the range. In consideration to the varying rescale slope/intercept, normal TF refactoring values for a typical CT image are as follows: 1) 1/0 (unchanged) = 64535 to 65535 and 0 to 1000 2) 1/-1024 (unsigned base data) = 0 to 2048 3) 0.5/0 (half values) = (63535 to 65535 and 0 to 2000)