 |
 |
The Achieva has the ability to do this per DICOM host, but to my knowledge it needs to be setup by your Philips field engineer. -----Original Message----- From: FSL - FMRIB's Software Library [mailto:[log in to unmask]] On Behalf Of Drew Sent: Wednesday, July 18, 2007 7:56 AM To: [log in to unmask] Subject: Re: [FSL] Philips conversion problem Is there a way to make the Achieva NOT export DICOM in multiframe? I've been having similar issues. AFNI's to3d program will read a multiframe DICOM file, but at least on my system it takes about 10 hours to do a 180 volume fMRI dataset. you can also tell the to3d program to essentially skip the header, so as long as you know your FOV, image size, coordinates, etc you can enter all those by hand. See this message thread http://afni.nimh.nih.gov/afni/community/board/read.php?f=1&i=21970&t=21871#r eply_21970 Drew On Tue, 17 Jul 2007 09:55:46 +0200, Martin Kavec <[log in to unmask]> wrote: >Hi Michael, > >as others have already suggested, export of your date to the so-called PAR-REC >(Philips research file format) file format is one way. At times it may be >even preferable, because in the PAR file, which is a simple ASCII text file, >you can get the gradient diffusion table for free. > >Regarding your troubles with the Achieva DICOM files, I would guess they could >be related to the conformance of Achieva architecture to the very recent >DICOM standards. I think it is by default that Achieva exports DICOM images >in the "MULTIFRAME format". This means that you would not find 2040 files in >your 32 (+ b0 + ADC-weighted) directions and 60 slices DTI study, but instead >they would be stored in ONE single file. > >You don't write how you get the images on a computer with MRIcro, so it is a >bit hard to speculate exactly, what could be the problem. If you prefer to >work with DICOMs, I would be happy to assist you to locate the problem. > >Martin