[Insight-users] MR volume: slice location + spacing pb

[dean.inglis@on.aibn.com]

It turns out that two programs with import
capabilities; MRIConvert and eFilm, had trouble
with a Siemens DICOM implementation.  The
contiguous data was there all the time!

Dean

> 
> From: "Stephen R. Aylward" <aylward at unc . edu>
> Date: 2003/05/28 Wed PM 08:52:19 GMT-04:00
> To: Dean Inglis <dean . inglis at on . aibn . com>
> CC: Insight users archive <insight-users at public . kitware . com>
> Subject: Re: [Insight-users] MR volume: slice location + spacing pb
> 
> Sounds like a plan - kind of the only option with that data.
> 
> I'd really encourage your clinical folks to try a 3D sequence with 
> contiguous slices...might be too large of a volume...
> 
> s
> 
> Dean Inglis wrote:
> > Well, on closer inspection, for the data I have,
> > I am getting slice thicknesses of either 1.5 or 3.0 mm
> > thickness as calculated from the reported (correct) slice positions.
> > So, ignoring the header thickness is the way to go. I am
> > thinking of just linear interpolating (with vtkImageResample) 
> > an additional slice between any two slices that are 3.0 mm 
> > thick so that a new volume can be recon at 1.5 mm thick 
> > consistent between slices.  Does this seem resonable?  BTW, 
> > I'm looking at fat sat saggital knee MRIs for cartilage
> > segmentation.
> > 
> > thanks again,
> > Dean
> > 
> > 
> > _______________________________________________
> > Insight-users mailing list
> > Insight-users at public . kitware . com
> > http://public . kitware . com/mailman/listinfo/insight-users
> 
> 
> -- 
> ===========================================================
> Dr. Stephen R. Aylward
> Associate Professor of Radiology
> Adjunct Associate Professor of Computer Science and Surgery
> http://caddlab . rad . unc . edu
> aylward at unc . edu
> (919) 966-9695
> 
>