Skip to content

FIX: Interpret empty string in SliceThickness DICOM field as missing (default to 1) #652

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

Merged
merged 3 commits into from
Mar 21, 2019

Conversation

mattcieslak
Copy link
Contributor

I was running into an issue where sometimes the value for SliceThickness was an empty string instead of None. I'm not sure if this is the right place to add the change, though.

@codecov-io
Copy link

codecov-io commented Jul 24, 2018

Codecov Report

Merging #652 into master will not change coverage.
The diff coverage is 0%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #652   +/-   ##
=======================================
  Coverage   88.82%   88.82%           
=======================================
  Files          92       92           
  Lines       11285    11285           
  Branches     1850     1850           
=======================================
  Hits        10024    10024           
  Misses        926      926           
  Partials      335      335
Impacted Files Coverage Δ
nibabel/nicom/dicomwrappers.py 90.73% <0%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bb8c6fa...9a91995. Read the comment docs.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 91.794% when pulling 9a91995 on mattcieslak:master into bb8c6fa on nipy:master.

@effigies effigies mentioned this pull request Oct 1, 2018
19 tasks
@effigies
Copy link
Member

effigies commented Oct 2, 2018

Hi, sorry for the slow response. Is there any chance of providing a test DICOM file that will hit this code path?

@effigies effigies changed the title some dicom headers had an empty string in SliceThickness FIX: Interpret empty string in SliceThickness DICOM field as missing (default to 1) Mar 13, 2019
@effigies
Copy link
Member

Hi @mattcieslak, just wanted to see if you have a test file that exhibits this property? Synthetic or anonymized would both work fine.

@mattcieslak
Copy link
Contributor Author

I'll check to see if I can find this again, I think it might have been a non-image dicom that was causing the trouble.

@effigies effigies mentioned this pull request Mar 15, 2019
20 tasks
@effigies
Copy link
Member

Hi @mattcieslak, sorry to be a nuisance, but I'm going to try to release next Monday, so it'd be great to get this in ASAP.

@effigies effigies added this to the 2.4.0 milestone Mar 18, 2019
@mattcieslak
Copy link
Contributor Author

Found the file and am checking with the study owners what the sharing policy is. I'm thinking this might just be a corrupt dicom because the rest of the files from that series have valid numbers for slice thickness

effigies and others added 2 commits March 21, 2019 10:38
TEST: Add de-identified, compressed DICOM with empty string in SliceThickness field
@effigies
Copy link
Member

Awesome. Thanks for your patience on this. (Failing tests are the usual AppVeyor weirdness.)

@effigies effigies merged commit abc2f43 into nipy:master Mar 21, 2019
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

Successfully merging this pull request may close these issues.

4 participants