There may be away to do this via the FEAT GUI. But if it were me I
would do it from the command line with an augmented version of your
kludgey workaround. Just add to your script the other necessary
commands to complete what you need. Take a look in a report_log.html
file for a group feat that you have run previously on the sort of
commands you need (e.g. smoothest, cluster etc.).
Cheers, Mark.
----
Dr Mark Woolrich
EPSRC Advanced Research Fellow University Research Lecturer
Oxford University Centre for Functional MRI of the Brain (FMRIB),
John Radcliffe Hospital, Headington, Oxford OX3 9DU, UK.
Tel: (+44)1865-222782 Homepage: http://www.fmrib.ox.ac.uk/~woolrich
On 4 Jan 2010, at 17:24, Nate Vack wrote:
> Hi all,
>
> So, for a variety of Complex Reasons, I've been trying to get beta
> coefficients and variances from earlier analysis steps (not done with
> FEAT) into FEAT for final analysis.
>
> Everything seems fine when we're setting up our model; however, when
> we try and run it, FEAT complains that our images aren't registered to
> each other. I know this is false: we've explicitly registered them all
> to the MNI152 template, and we can run flameo on them with a kludgey
> workaround*.
>
> Sorry if this is a silly question, but how can we tell FEAT "I promise
> these images are registered; just run the model already"?
>
> Thanks!
> -Nate
>
> * The workaround, if you're interested:
>
> 1: Set up the model in FEAT and try to run it. It'll error out, but
> will build design.mat, design.con, and design.grp
> 2: Use fslmerge -t to build the copes and varcopes files. Either build
> a mask or use a standard mask.
> 3: Run flameo using the model files from step 1 and data files from
> step 2.
>
|