[Insight-developers] bug in vtkITKArchetypeImageSeriesReader and possible improvement in slicer and ITK

[Wang, Kevin]

Hi slicer,

I am developing a module in Slicer and I found a bug in vtkITKArchetypeImageSeriesReader class. Here is the issue.

Since dicom utilizes the concept of slope and intercept, the scalar range for each 2D slice can be much different. However, in Slicer, the scalar type is determined by checking the ComponentType returned by GDCMImageIO which only tells the last slice ComponentType in vtkITKArchetypeImageSeriesReader.cxx.

I propose to change vtkITKArchetypeImageSeriesReader.cxx as well as the itkImageSeriesReader class in ITK. The idea is that the scalar range will be checked for each 2D slice in itkImageSeriesReader and then a new variable OutputImagePixelScalarType will be set accordingly, then in vtkITKArchetypeImageSeriesReader.cxx it will check the OutputImagePixelScalarType from the itkImageSeriesReader to correctly determine the scalar type.

If you think this makes sense, I will create an ITK ticket and submit a patch to ITK. The slicer patch has to wait until slicer start to use the newly patched ITK. I have created a ticket for tracking this: http://na-mic.org/Mantis/view.php?id=3386

Thanks,

Kevin

This e-mail may contain confidential and/or privileged information for the sole use of the intended recipient. 
Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. 
If you have received this e-mail in error, please contact the sender and delete all copies. 
Opinions, conclusions or other information contained in this e-mail may not be that of the organization.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/pipermail/insight-developers/attachments/20130913/6a6c3ef3/attachment.htm>