[vtkusers] Can I read the dicom files in vtk using the implem ented classes in Slicer?

[Goodwin Lawlor]

There is a class already written (which I think the original post was
refering to) called vtkImageDICOMReader. It's distributed with the
application 3D Slicer (http://www.slicer.org). Its copyrighted to MIT
though, with permission to copy, modify etc.
----- Original Message -----
From: "Sebastien BARRE" <sebastien at barre.nom.fr>
To: "Day, Robert" <Robert.Day at health.wa.gov.au>
Cc: <vtkusers at public.kitware.com>
Sent: Monday, November 26, 2001 2:35 AM
Subject: RE: [vtkusers] Can I read the dicom files in vtk using the implem
ented classes in Slicer?


> At 11/26/2001 10:08 AM, Day, Robert wrote:
> >I too use Sébastien's dicom2 and it is a great tool.
>
> Thanks.
>
> >However, recently on the ImageJ mailing list someone asked about renaming
> >DICOM files.  I suggested dicom2, but he was using MacOs X, for which a
> >binary does not exist.  This leads me to ponder whether more portable
DICOM
> >handling could become a part of vtk.
>
> What features would you request inside VTK ?
>
> >Certainly it would be a non-trivial
> >task, given the size and ever-expanding nature of the DICOM standard.
>
> Definitely.
>
> >As ever, I am not in a position to do the work myself at the moment, but
> >perhaps Sébastien is willing to make his source available, which would
> >certainly make the task easier.
>
> Well, the good news is that I moved from France to work at Kitware now :)
> The "bad" news is that none of my projects involve DICOM at the moment and
> thus would justify that I dedicate some of my working-time (and Kitware's
> ressources) to dicom2. Anyway, this has always been the case, dicom2 was a
> small tool I wrote to fulfill some of my PhD needs years ago and evolved
> way beyond it was intended to :)
>
> Being part of a company that is confident in the open source model, the
> logical step would be to open the source code. Sadly, this would not be a
> very nice gift to anyone of you :) dicom2 is in a state where actually it
> is difficult to maintain and expand : it definitely needs a rewrite from
> the ground-up. DICOM is a tricky protocol and I'm not sure messing up with
> that code would be a good thing for someone who does not know it, since it
> could create corrupted DICOM files, something you definitely should avoid
> in a medical context.
>
> My plan is to rewrite it as a DICOM library (and a dicom2 binary using
it).
> Ideally I would use our technology and our open-source tools (CMake, cable
> or the VTK wrappers) to make it portable (Unix, Win, Mac) and scriptable
> (C++ API with Tcl/Python/Java bindings). Most probably next year, since I
> do not have a home computer now and my free time is more dedicated to
> settle here and socialize :)
>
> Sebastien
>
> _______________________________________________
> This is the private VTK discussion list.
> Please keep messages on-topic. Check the FAQ at:
<http://public.kitware.com/cgi-bin/vtkfaq>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/vtkusers