[Insight-developers] BUG: GDCMImageIO should respect the rescale intersept/slope when writing data

[Mathieu Malaterre]

The reading behavior is not changing, whenever we find a rescale
slope/interspect we take them into account. But as of now, when we are
*writing* an image with a rescale slope/interspect we discard it (we
were storing the pixel data buffer directly without affine transform).
This used to work well, but for people willing to store floating point
data this is an outstanding issue preventing them to store the image.

-Mathieu

On Nov 29, 2007 2:34 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
> Mathieu,
>
> Are you saying that we will no longer call RescaleFuntion in GDCMImageIO?
> This would be a huge change and break everyone's applications I believe.
> Maybe I am misunderstanding.
>
> Bill
>
>
> On Nov 29, 2007 8:21 AM, Mathieu Malaterre <mathieu.malaterre at gmail.com>
> wrote:
>
> >
> >
> >
> > Hi,
> >
> >  Just FYI after discussing with Matthias, my previous fix in ITK for
> > the rescale intersept/slope was clearly a hack and should be removed
> > ASAP. The correct patch should be that ITK is consistant at write
> > time, and respect the slope/intersept value as found in the metadata
> > header.
> >  What this means is, we will continue to not support floating point
> > Image, but allow user to apply a shift/scale by hand to have total
> > control over the data loss and then store the data as DICOM.
> >  I should find some time in the next days to implement the correct patch.
> >
> > thanks,
> > --
> > Mathieu
> > _______________________________________________
> > Insight-developers mailing list
> > Insight-developers at itk.org
> > http://www.itk.org/mailman/listinfo/insight-developers
> >
>
>



-- 
Mathieu