[Insight-developers] AnalyzeIO large files and compression
kent williams
norman-k-williams at uiowa.edu
Thu Jan 21 09:48:59 EST 2010
You are right about the file extension issue. Do you want me to test and
check in the fix, or do you want to do it? I think this was a case where
more than one person was working on the code the test for .gz¹ I think
predates adding the FileExtension¹ function which returns .img.gz¹. When
the FileExtension function was added, the test wasn¹t updated.
I don¹t remember why we still keep AnalyzeImageIO around. It seems like I
wanted to eliminate it at one point after the NIfTI reader was added, but
there was something about the NIfTI library that caused a problem. I would
dearly love for itkAnalyzeImageIO to go away, as it was some of the first
code I wrote for ITK, and it¹s A) theoretically obsolete now that we have
the NIfTI reader and B) isn¹t particularly well written.
On 1/20/10 3:54 PM, "Bradley Lowekamp" <blowekamp at mail.nih.gov> wrote:
> Hello,
>
> I was testing my fix for the following bug:
> http://www.itk.org/Bug/view.php?id=10135
>
> When I noticed that I was unable to generate a compressed output file. And the
> coverage seems to indicate the same:
> http://www.cdash.org/CDash/viewCoverageFile.php?buildid=519292&fileid=10945147
>
>
> I think I see the problem in the code:
> if(!fileExt.compare( ".gz" )) should be ".img.gz"
>
> There is also the Nifti which reads and writes the img format. Is one suppose
> to be better then the other? My test appears to work with writing the
> compressed writing code enables. Is there any history or related issues to
> this IO that I should know about before making these changes?
>
> Thanks,
> Brad
>
>
> ========================================================
>
> Bradley Lowekamp
>
> Lockheed Martin Contractor for
>
> Office of High Performance Computing and Communications
>
> National Library of Medicine
>
> blowekamp at mail.nih.gov
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/mailman/private/insight-developers/attachments/20100121/156a04d1/attachment.htm>
More information about the Insight-developers
mailing list