[Insight-users] Segmentation fault reading an Analyze file

[Bill Lorensen]

Kent,

We can still keep the AnalyzeImageIO class. It would end up being a subclass
of NiftiImageIO. We have done before with DicomImageIO. We cannot remove the
AnalyzeImageIO class. As you said, it will break code in the ITK installed
base.

We're too close to a release to do this now. I'll enter a bug.

Bill

On Wed, Feb 6, 2008 at 12:04 PM, kent williams <nkwmailinglists at gmail.com>
wrote:

> I see no reason to keep the AnalyzeImageIO library around; the NIfTI
> library does a good job of reading Analyze files. itkNiftiImageIO
> would need 2 characters added in CanReadFile and CanWriteFile.
>
> The only thing this would break is any code that instantiates an
> instance of AnalyzeImageIO and assigns it to a reader.  I believe
> there are Analyze tests that do that.
>
> On Tue, Feb 5, 2008 at 1:19 PM, Bill Lorensen <bill.lorensen at gmail.com>
> wrote:
> > David,
> >
> > Hans Johnson has just made some changes to nifti utilities and itk
> classes.
> > It turns out that since NIFTI appears before Analyze in the IO factory,
> you
> > are probably using the NIFTI ImageIO class (whether you want to or not).
> I
> > suggest that you update Utilities/nifti, Code/IO and testing/Code/IO.
> Then
> > try your original code again.
> >
> > I looked at the Analyze code and Analyze header and it seems that
> Analyze
> > does not support anything other than unsiged char for RGB pixels. Hans
> can
> > confirm this since he is the itk Analyze/Nifti expert.
> >
> > Hans, in the long term will it be possible to process all analyze files
> with
> > the nifti ImageIO class? Or at least remove most of the current
> > AnalyzeImageIO code, perhaps by subclassing AnalyzeImageIO from
> > itkNiftiImageIO?
> >
> > Bill
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://public.kitware.com/pipermail/insight-users/attachments/20080206/9debae12/attachment.htm