[vtkusers] vtkImageChangeInformation

[Bill Lorensen]

Marthieu,

I'm confused. For a high percentage of 3D acquisitions, the old gdcm
method of computing z-spacing worked fine. What is the proper way of
dealing with those high percentage cases?

Bill

On Wed, Dec 9, 2009 at 1:47 PM, Mathieu Malaterre
<mathieu.malaterre at gmail.com> wrote:
> On Wed, Dec 9, 2009 at 7:39 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
>> The Dicom reader should compute it.
>
> Not in vtkGDCMImageReader.
> http://sourceforge.net/apps/mediawiki/gdcm/index.php?title=Using_GDCM_API#Automatic_ordering_of_slices_for_vtkGDCMImageReader.SetFileNames
>
> This way is much more configurable and allow people to load SCOUT
> views or any exotic DICOM Series, or even Series with missing slices.
>
> From the outside, one simply needs to encapsulate
> vtkGDCMImageReader+vtkImageChangeInformation into a single VTK class
> if they really want to treat any DICOM Multi-Frames Series as Volume
> (this will not work with the new Enhanced DICOM stuff...but that's a
> different story)
>
> 2cts
> --
> Mathieu
>