It's could be something to do with your MRI scanner producing bad quality
DICOM files. I would suggest buying a new scanner.
Alternatively, it could be some bug in my conversion code, or maybe I haven't
kept up-to-date with the ever-changing DICOM standard - because the manual
set for the DICOM standard are about a foot (~30cm) thick.
Best regards,
-John
On Tuesday 20 September 2005 10:16, Mark Daglish wrote:
> Dear All,
>
> I am attempting to reconstruct some structural MRI images from a
> Phillips Intera scanner. The images are in Dicom format as exported
> from the scanner to CD. When using the DICOM_toolbox from SPM2 I get
>
> the following error messages:
> >> ??? Error using ==> spm_dicom_headers>read_sq
>
> 65279/224 unexpected.
>
> Error in ==> spm_dicom_headers>read_dicom at 162
> [dat,len1] = read_sq(fp, flg,dict,tag.length);
>
> Error in ==> spm_dicom_headers>readdicomfile at 59
> ret = read_dicom(fp, 'le',dict);
>
> Error in ==> spm_dicom_headers at 24
> tmp = readdicomfile(P(i,:),dict);
>
> Error in ==> spm_DICOM at 7
> hdr = spm_dicom_headers(P);
>
> Error in ==> spm at 1183
> evalin('base',varargin{2}(i).prog)
>
> ??? Error while evaluating uicontrol Callback.
>
> Can anyone help interpret this for me. The toolbox works fine on other
> images I have, and all patches are up-to-date.
> If it makes a difference, there are 200 files acquried in coronal
> orientation. I can reconstruct the volume with MRIcro on my windows
> machine, but not with SPM2 running on Solaris 2.9 on a Sun Blade. Could
> this be an endian issue?
>
> Thanks in advance for any help,
>
> Mark
> ============================
> Dr. Mark Daglish
> Clinical Lecturer in Psychiatry
> University of Bristol
|