Thanks Steve. I did discover both of those options. I went with the
latter as I need it to be automatic.
I'm adding the following to my 3.2 design.fsf:
set fmri(critical_z) 5.3
set fmri(noise) 0.66
set fmri(noisear) 0.34
set fmri(evtitle1) ""
Will I need an evtitle for each EV? Any others you can think of.
doug
Steve Smith wrote:
> Yo Doug,
>
> In general you can't feed an old design.fsf straight into a newer
> command-line .feat but in general you _can_ load it into the Feat GUI
> and re-save. This should fill out the new variables (though you may
> in some cases need to open the design matrix sub-GUI and close that
> first).
>
> Or you can try randomly adding the missing variables at the end of
> your design.fsf - you can see the design.fsf in FEEDS as an example.
>
> Cheers, Steve.
>
>
> On 10 Aug 2006, at 21:27, Doug Greve wrote:
>
>> Is it possible to use a version 3.2b design.fsf in version 3.3? I
>> just tried it and got the error:
>>
>> /usr/pubsw/packages/fsl/3.3.2/bin/feat_model design
>> Can't find key fmri(critical_z)
>>
>> And then later FILM failed because it could not find design.mat
>>
>> thanks!
>>
>> doug
>
>
>
> ------------------------------------------------------------------------
> ---
> Stephen M. Smith, Professor of Biomedical Engineering
> Associate Director, Oxford University FMRIB Centre
>
> FMRIB, JR Hospital, Headington, Oxford OX3 9DU, UK
> +44 (0) 1865 222726 (fax 222717)
> [log in to unmask] http://www.fmrib.ox.ac.uk/~steve
> ------------------------------------------------------------------------
> ---
>
>
--
Douglas N. Greve, Ph.D.
MGH-NMR Center
[log in to unmask]
Phone Number: 617-724-2358
Fax: 617-726-7422
In order to help us help you, please follow the steps in:
surfer.nmr.mgh.harvard.edu/fswiki/BugReporting
|