[Insight-users] Analyze Image IO broken?

[Robert Tamburo]

Hi Kent and Hans,

Thanks for the very detailed explanation. I've experienced this  
swapping issue on multiple occasions and it's been a headache trying  
to keep track of the image orientation. I was unaware that the NIfTI  
format was a solution to the issue. I just thought it was yet another  
file format. Looks like I'll be making a switch.

Thanks again for the help!

-Robert


On Oct 19, 2006, at 8:37 PM, Hans Johnson wrote:

> Robert,
>
> That first problem appears that the gdcm reader is improperly  
> trying to read
> the image.  I could be wrong, but would bet that it is a problem  
> with gdcm.
>
> The second problem is that Analyze75 format does not support all  
> possible
> image orientations, and until recently was writing images that were
> incorrectly labeled with respect to orientation.  This problem was  
> causing
> serious analysis problems because there were documented cases where  
> images
> were swapped right/left.  According to the Analyze75 documentation  
> there are
> only 3 acceptable orientations that are supported RPI,PIR, and RIP  
> (actually
> there are 6, but 3 are highly discouraged and almost universally not
> supported).
>
> Hans
>
>
> On 10/19/06 8:27 AM, "Robert Tamburo" <robert.tamburo at gmail.com>  
> wrote:
>
>> I just noticed some strange behavior with the Analyze IO after
>> updating my ITK version to the CVS version of ITK. Two things:
>>
>> -----------
>> 1. A program that takes as argument the name of a 3D input image with
>> the extension .img results in the following error:
>>
>> terminate called after throwing an instance of 'gdcm::FormatError'
>>    what():  N4gdcm11FormatErrorE
>> Abort trap
>>
>> If I use .hdr as the extension, it gets read in correctly. This same
>> program is able to take as arguments filenames with the .img
>> extension and write the files correctly.
>>
>> Isn't gdcm a dicom format? Why would the image factories be trying to
>> using the dicom IO?
>>
>> 2. Another program internally writes out a couple of Analyze images.
>> Using either the .img or .hdr extension on the filename results in
>> this error:
>>
>> terminate called after throwing an instance of 'itk::ExceptionObject'
>>    what():  /Users/robert/code/Insight/Code/IO/itkAnalyzeImageIO.cxx:
>> 1180:
>> itk::ERROR: AnalyzeImageIO(0x2814200): ERROR: Analyze 7.5 File Format
>> Only Allows RPI, PIR, and RIP Orientation
>> Abort trap
>>
>> This code has worked for a long time. I use the same method of file
>> writing in both programs and yet one results in an error and the
>> other doesn't.
>> -----------
>>
>> Incidentally, I just noticed these errors after testing code that I
>> recently submitted to the Insight Journal (http://insight- 
>> journal.org/
>> dspace/handle/1926/322).
>>
>> Thanks for any help,
>> Robert
>> _______________________________________________
>> Insight-users mailing list
>> Insight-users at itk.org
>> http://www.itk.org/mailman/listinfo/insight-users
>