Hi,
I really don't understand what can be happening here.
What happens if you just take the original image and do:
fslroi originalimage testimage 87 1
Can you view the result (testimage) in FSLView?
Also, just to check it isn't like yesterday's problem on the list - you
don't have any non-English characters or spaces in any of
your filenames, do you? The ones I could see below looked fine.
Oh, and have you successfully run FEAT before on any datasets?
Or is this the first one you've tried?
All the best,
Mark
On 3 Jul 2009, at 07:26, Dorit Kliemann wrote:
> Hi Marc,
>
> thanks for your reply.
> I cannot open the example func (or the mean func) at all with
> fslview:
>
> [RK3:~/SOX_FSL] dorit% fslview
> GAZ_P_22/mri/run2/func_datasmooth5.feat/example_func.nii.gz
> ** ERROR (nifti_image_read): failed to find header file for
> '/Users/dorit/SOX_FSL/GAZ_P_22/mri/run2/func_datasmooth5.feat/
> filtered_func_data'
> ** ERROR:
> nifti_image_open(/Users/dorit/SOX_FSL/GAZ_P_22/mri/run2/
> func_datasmooth5.feat/filter
> ed_func_data): bad header info
> Error: failed to open file
> /Users/dorit/SOX_FSL/GAZ_P_22/mri/run2/func_datasmooth5.feat/
> filtered_func_data
>
>
> The original .nii looked just fine in fslview...
>
> I'm working on a 10.5. intel mac, data is stored locally...
>
> Thanks,
> Dorit
>
>
>
>
> This warning definitely means that some images are all zeros.
> Does example_func look OK in FSLView?
> What about prefiltered_func_data if you still have it?
> If you don't have it, just use the commands below to regenerate it
> and then check.
> Having a look at the data in FSLView is the best way to check.
>
> If you cannot see a problem then let us know what type of machine
> you are running on and where the data is stored (e.g. NFS mounted
> storage, local disk, etc.).
>
> All the best,
> Mark
>
|