Hi,
Was the highres image inside an existing FEAT directory or entirely outside of it?
It looks like there is just a problem with either the location of the image or, as
occasionally happens, the FEAT GUI may be getting out of sync. Have you
tried doing the Registration Only without starting from the original design.fsf?
It would be worth checking if the registration works by starting from a new GUI,
without any previous settings. If that works, then try again by loading the
existing FEAT directory design.fsf file, switching to Registration Only, then
changing the filename for the highres image.
If you have trouble with any of this please let us know.
All the best,
Mark
On 12 Jan 2011, at 18:51, Olga wrote:
> Hello,
>
> I have been getting an error while registering example_func to a highres image in the FEAT gui (as part of a Full first-level analysis). The first time I did the analysis, the registration to highres worked, but I noticed that highres was oriented differently from example_func, so I made some changes to the highres image with fslorient and decided to try registering again. I loaded in the previously generated FEAT directory, chose "Registration only" and specified the new structural image.
> Here is the error that came up:
>
> /bin/mkdir -p reg
> Warning - registration to highres turned on but
> no highres image specified in setup file or in
> FEAT directory! Will not register to highres.
>
> In the previous design, I only registered to the standard template and it seems like this time, it is again trying to follow the design.fsf file from the feat directory, instead of reading in the highres image that I am specifying in the FEAT gui. Could anyone please suggest how I can avoid this error?
>
> Thank you very much in advance!
> Olga
>
|