You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DICOM tags (0028, 0120), (0028, 0122) or (0028, 0123) can be used to specify pixel padding values. The presence of these values in the image itself indicate pixels without valid data, for example outside the cylindrical acquisition volume of a CT.
When interpolating, these pixels should not be treated as "normal" values that can be used in linear interpolation. My suggestion is, when at least one of the two values used in the interpolation equals the padding value, to use nearest neighbor interpolation instead.
While the effects of this are limited to the border between the padding and real pixels, it changes the intensity histogram enough to confuse our code for a couple of images.
I will submit a pull request with a proposed fix.
The text was updated successfully, but these errors were encountered:
alund
added a commit
to alund/dcm2niix
that referenced
this issue
Jan 31, 2019
* Fixesrordenlab#262
* Use a single float pixelPaddingValue in TDICOMData rather than
pixelPaddingValue, floatPixelPaddingValue, isHasPixelPaddingValue and
isHasFloatPixelPaddingValue
* Read kFloatPixelPaddingValue with dcmFloat() rather than dcmStrFloat()
* Use pixel padding value when available for padding added during tilt
correction.
DICOM tags (0028, 0120), (0028, 0122) or (0028, 0123) can be used to specify pixel padding values. The presence of these values in the image itself indicate pixels without valid data, for example outside the cylindrical acquisition volume of a CT.
When interpolating, these pixels should not be treated as "normal" values that can be used in linear interpolation. My suggestion is, when at least one of the two values used in the interpolation equals the padding value, to use nearest neighbor interpolation instead.
While the effects of this are limited to the border between the padding and real pixels, it changes the intensity histogram enough to confuse our code for a couple of images.
I will submit a pull request with a proposed fix.
The text was updated successfully, but these errors were encountered: