Hi - sorry, I hadn't quite understood what you were after.
Yes - hopefully this should be fairly straightforward. I would:
- setup and run FEAT, with ONLY registration to standard space (no
intermediate images)
- separate to that, run the more complex registration process which
you find works, outside of FEAT and use convert_xfm to derive the
final transform example_func2standard.mat
- put this transform in the .feat/reg directory, overwriting the
(bad) one that FEAT generated.
- now you'll be ready to run higher-level FEATs, and won't need to
get into resampling any 4D data outside of FEAT.
Cheers.
On 30 Aug 2007, at 21:55, N.M. van Strien wrote:
> Hi Steve,
>
> Indeed, I do not get a good registration result when using the
> registration
> tab options in Feat. However, with some extra steps I can register
> my data
> to standard space.
>
> One approach would be to register the orginal data to an
> intermediate form
> from which I can use the Feat gui options at the first level.
> However, that
> means that I will start manipulating the data before I applied
> pre-processing. I am not sure how good or bad that is?
>
> Alternatively, I could manually register the filtered_func data.
> However,
> then I need to override the check on the registration at the start
> of the
> higher level stats and provide an example_func2standard.mat that
> will not
> change my manual registration again.
>
> Is this possible? And if so, how?
>
> Thanks,
>
> Niels
------------------------------------------------------------------------
---
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
------------------------------------------------------------------------
---
|