 |
 |
Dear Alle, I haven't seen that on a healthy system before so I suspect you are having some serious NFS issues. Try and make sure that you don't have too many files in your directory, as that is often a cause of slowness. In the meantime the easiest work around would be to save a Melodic GUI set-up that is working for you and then take the fsf file and edit the contents. Then you can load it into the Melodic GUI (which would be slow, but at least only once) and start it going from the GUI. Alternatively, just look at the log and replicate everything at the command line, avoiding the GUI completely, although that is a lot more complicated. All the best, Mark On 23 Apr 2013, at 09:47, Alle Meije Wink <[log in to unmask]> wrote: > Dear all, > > When I set up an analysis (in this case melodic) in the GUI, it takes an incredibly long time to re-gain control after entering file-related data: > * input time series > * alternative references for BBR realignment > * high-resolution anatomical images > * saving the settings in an fsf file > This seems to be related to an integrity check of all these image files (as the file names that are saved eventually are not necessarily the same as those entered). > > Would it be an idea to move this integrity check to one place only? Or to give users the choice when to perform an integrity check (as long as this is done before 'go' and always during 'save' -- cf submission forms with a compulsory validation step)? I don't doubt that funny NFS properties are also to blame here, just looking for a way to speed things up... > > bw > Alle Meije Wink