-
Notifications
You must be signed in to change notification settings - Fork 261
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
Conversation
Codecov Report
@@ 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
Continue to review full report at Codecov.
|
Hi, sorry for the slow response. Is there any chance of providing a test DICOM file that will hit this code path? |
Hi @mattcieslak, just wanted to see if you have a test file that exhibits this property? Synthetic or anonymized would both work fine. |
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. |
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. |
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 |
TEST: Add de-identified, compressed DICOM with empty string in SliceThickness field
Awesome. Thanks for your patience on this. (Failing tests are the usual AppVeyor weirdness.) |
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.