Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gantry tilt interpolation should respect pixel padding value #262

Closed
alund opened this issue Jan 31, 2019 · 1 comment
Closed

Gantry tilt interpolation should respect pixel padding value #262

alund opened this issue Jan 31, 2019 · 1 comment

Comments

@alund
Copy link
Contributor

alund commented Jan 31, 2019

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.

alund added a commit to alund/dcm2niix that referenced this issue Jan 31, 2019
alund added a commit to alund/dcm2niix that referenced this issue Feb 1, 2019
* Fixes rordenlab#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.
@neurolabusc
Copy link
Collaborator

Fixed with pull request 246

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants