<html>
<body>
<font size=3>Hi Christoph, <br><br>
I had the same problem and have already entered it in the bug
tracker.<br><br>
<a href="http://www.itk.org/Bug/bug.php?op=show&bugid=3689&pos=28" eudora="autourl">http</a><a href="http://www.itk.org/Bug/bug.php?op=show&bugid=3689&pos=28" eudora="autourl">://www.itk.org/Bug/bug.php?op=show&bugid=3689&pos=28<br><br>
</a>A workaround it to set the ImageIO explicitly:<br><br>
imageReader->SetImageIO( GiplImageIO::New() )<br><br>
but this is of course not very convenient if you want to support multiple
image formats.<br><br>
Regards!<br>
Stefan<br><br>
At 12:40 17/01/07, Christoph Palm wrote:<br>
<blockquote type=cite class=cite cite>Hi there,<br><br>
I work with gipl images and had troubles reading some<br>
of them. After debugging it, it turns out to be a problem of the<br>
ImageIOFactory, especially with the GDCM image reader. In fact, the<br>
imageIOBase was by error assigned to GDCM instead of GIPL. Then, of<br>
course, everything seriously went wrong and ended up with false
buffer<br>
allocations and a segmentation fault. The wrong assignmed happend,<br>
because within the factory all possible reader are tested to be the<br>
right one. The first one was rejected, because the filename was not<br>
properly. Ok. The second one was the GDCM reader, where no filename<br>
testing is applied. In gdcmDocument.cxx, function CanReadFile<br>
the first Bytes are read in as Uint16 and tested to be some
numbers.<br>
If one of these numbers are found, a dicom image without preample
is<br>
assumed and the function returns true.<br><br>
Unfortunately, by coincidence obviously my gipl images showed one
of<br>
these numbers, namely 1, at the beginning of the file. In a gipl
image<br>
the header starts with UShort numbers for the dimensions. My
dimensions<br>
for the error case were 256 256 1 1 (since gipl images are always
4D).<br>
If I change the dimensions to 255 256 1 1, for example, everything
is<br>
fine. Now my question: how to solve this in the Insight framework in
a<br>
clean way? I am not really familiar with DICOM varieties. Is it
possible<br>
to add a fileEnding test to the GDCM reader? <br><br>
By the way, I also found a bug in writing gipl images. This is
already<br>
putted into the BugTracker. Is it possible, that I am the one and
only<br>
here who is working with GIPL images? ;-)<br><br>
Regards<br><br>
Christoph<br><br>
<br>
_______________________________________________<br>
Insight-users mailing list<br>
Insight-users@itk.org<br>
<a href="http://www.itk.org/mailman/listinfo/insight-users" eudora="autourl">http://www.itk.org/mailman/listinfo/insight-users</a>
</font></blockquote></body>
<br>
</html>