0004389: Some DICOM volumes load with different datatypes between DCMTK and GDCM

ID	Project	Category	View Status	Date Submitted	Last Update

0004389	Slicer4	Module DICOM	public	2017-06-22 20:33	2018-05-30 00:46

Reporter	pieper	Assigned To	pieper
Priority	normal	Severity	minor	Reproducibility	sometimes
Status	resolved	Resolution	suspended
Product Version
Target Version		Fixed in Version

Summary	0004389: Some DICOM volumes load with different datatypes between DCMTK and GDCM
Description	When a dicom images has a limited dynamic range of say 0 to 191 even when the file has 16 bits allocated, DCMTK will load it as unsigned char while GDCM would load as unsigned short.
Steps To Reproduce	The DICOMReaders self test checks for this.
Additional Information	We should see if this is actually a problem for anyone.
Tags	No tags attached.

Date Modified	Username	Field	Change
2017-06-22 20:33	pieper	New Issue
2017-06-22 20:33	pieper	Status	new => assigned
2017-06-22 20:33	pieper	Assigned To	=> pieper
2018-05-30 00:46	lassoan	Status	assigned => resolved
2018-05-30 00:46	lassoan	Resolution	open => suspended
2018-05-30 00:46	lassoan	Note Added: 0015813

lassoan 2018-05-30 00:46 developer ~0015813	Probably it id not worth spending time with this until there is a valid, confirmed need.