View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002301Slicer4Module DICOMpublic2012-07-05 01:392014-03-06 05:55
ReporterJaymax Assigned Topieper  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product VersionSlicer 4.1.0 
Target VersionSlicer 4.2.0Fixed in VersionSlicer 4.4.0 
Summary0002301: DICOM loader skipping some image sets
Description

Image files attached fail to load into DICOM module browser. Other files from same facility (different machine and date) load normally. Importing a folder containing both sets of files results in only the one set loading. Importing a folder containing only the failing files results in an empty DICOM browser.
No errors etc displayed, files appear to be parsed/processed normally during the import stage.

Additional Information

Files display normally in MicroDicom; parsing folder in this tool results in both sets of files being shown.

The attached ZIP contains screen grabs from Slicer DICOM browser and MicroDicom after loading folder, for comparison, along with the first couple of DICOM files from both the 'failing to load' images ['3D VOL T2' 00000.DCM 00001.DCM 2009-12-24] and the 'loading fine' images ['SAG T1 SE' 00220.DCM 00221.DCM 2009-12-21]

FWIW I tried creating a different folder containing ONLY the non-importing later session images (files 00000.DCM thru 00219.DCM) but 'importing' that results in nothing at all showing in the DICOM browser.

TagsNo tags attached.

Activities

2012-07-05 01:39

 

Slicer DICOM glitch.zip (2,059,133 bytes)
Jaymax

Jaymax

2012-07-05 01:44

reporter   ~0005074

FWIW re data privacy concerns: These images are of my own head.
pieper

pieper

2012-07-05 10:52

administrator   ~0005076

thanks for providing the data - this exposed a logic error in the ctkDICOMDatabase.

Fixed in CTK:
http://www.na-mic.org/Bug/view.php?id=2301

and fixed in slicer revision 20573.

Tomorrow's nightly build (or a build of the trunk) should have this fix. Note that you'll need to start with a fresh database to successfully import. Or you might be able to delete the patient (right click for menu) and re-import all the studies for that patient.
jcfr

jcfr

2012-07-27 15:42

administrator   ~0005424

Dear issue reporter,

Good news :) Slicer developers SOLVED the problem you reported - YOU now need to VERIFY and CLOSE this issue.
jcfr

jcfr

2014-03-06 05:05

administrator   ~0010923

Closing resolved issues that have not been updated in more than 3 months

Issue History

Date Modified Username Field Change
2012-07-05 01:39 Jaymax New Issue
2012-07-05 01:39 Jaymax Status new => assigned
2012-07-05 01:39 Jaymax Assigned To => pieper
2012-07-05 01:39 Jaymax File Added: Slicer DICOM glitch.zip
2012-07-05 01:44 Jaymax Note Added: 0005074
2012-07-05 10:52 pieper Note Added: 0005076
2012-07-05 10:52 pieper Resolution open => fixed
2012-07-08 08:11 pieper Status assigned => resolved
2012-07-27 15:42 jcfr Note Added: 0005424
2012-08-21 11:32 jcfr Target Version => Slicer 4.2.0 - Feature freeze Sept 1st 2012
2014-03-06 05:05 jcfr Note Added: 0010923
2014-03-06 05:06 jcfr Status resolved => closed
2014-03-06 05:55 jcfr Fixed in Version => Slicer 4.4.0