<br><br><div class="gmail_quote">On Tue, Jun 16, 2009 at 10:39 PM, Lic. José M. Rodriguez Bacallao <span dir="ltr"><<a href="mailto:jmrbcu@gmail.com">jmrbcu@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
hi folks, I am new to vtk and itk and I begining to love all the<br>
goodies of itk, right now, I'm triying to develop a dicom viewer with<br>
itk, vtk and python (my preferred language) so, I have a couple of<br>
questions to make.<br>
<br>
1- How about the quality of wrappers (WrapITK vs standard)<br>
2- How about memory consumption and load times of the wrappers.<br>
3- I need to read several DICOM files, from various modalities, how do<br>
I read all of them if I need to now the image type first, for example:<br>
</blockquote><div><br>If your plan is really to create a DICOM viewer (I am not sure you understand the immense task this represent), I would suggest you use the underlying library directly. In the case of ITK, this is GDCM.<br>
This will allow you direct access to all possible DICOM file (ITK has some restrictions) and get the correct visualisation as specified in the VOI LUT (not used in ITK). You'll also have some issue with Grayscale Softcopy Presentation State object (not handled in ITK).<br>
<br>If your plan is simply to display an itk::Image with input from DICOM file, you should be warned that your viewer will not be compliant with DICOM presentation states.<br><br></div></div>2cts<br>-- <br>Mathieu<br>