Hi Martin,
invwarp used to take as much as 40 hours on a dual core machine with
large f.ov. images... You can speed things up by reducing the f.o.v. of
your image if it is much larger than the MNI template, and also by
downsampling the resolution of your highres anatomical.
I think I read that a future version of FSL might contain a config file
for FNIRT to avoid using invwarp but instead do a new registration from
standard to highres space - is that right, anyone?
Cheers,
Stéphane
Stéphane Jacobs - Chercheur post-doctorant / Post-doctoral researcher
Espace et Action - Inserm U864
16 avenue du Doyen Lépine
69676 Bron Cedex, France
Téléphone / Phone: (+33) (0)4-72-91-34-33
Martin Monti a écrit :
> Dear FSL jedi-masters,
>
> I've been running Featquery on a fast ER design (1-st level, single
> subject). I'm running it using a mask from the Oxf-Harv atlas.
>
> Now, it's been running for over 18 hours and still seems to be at
> invwarp. The process, as far as I can tell, is alive and running. Of
> course, the log is stuck at the first line and hasn't updated since it
> was created. I've launched another (almost identical) Featqury
> analysis on a different CPU, to check if that was the problem, and
> that one too seems to be going at the same pace.
>
> In defence of featquery, though, I had used FNIRT in the FEAT analysis
> of this data, which may slow down the backwarping of the mask, but is
> this much normal? I mean, even if I originally used the non-linear
> transformation isn't invwarp "just" going to multiply the atlas mask
> by the (previously computed) standard2example_func transformation
> matrix, or is it computing ex-novo the inverse of FNIRT's output?
>
> thank you,
>
> best
>
> martin
|