Hi Neil,
The most important files are the files that store the GUI settings (*.fsf files)
(especially filenames with paths, in this case) and the report html files.
I don't think that there are any other files where anything is embedded
or crucial. We never store the path to the FSL binaries that I'm aware
of, it is always called via $FSLDIR/bin/, although some log files (which
are not crucial for the outputs, they just recount the history of the
execution) probably expand this variable before it gets saved into the file.
Hope this helps.
All the best,
Mark
On 1 Feb 2012, at 06:13, Neil Killeen wrote:
> Hi
>
> I am moving users and their existing data to a new host. As I recall, FSL embeds strings such as
>
> - binary paths
> - data paths
>
>
> into various intermediary files that it produces (can't quite remember the details).
>
> I can arrange the path of the binaries to be the same as it was on the previous host.
> It's harder to do that for the data path.
>
> Can someone tell me exactly which absolute paths are going to cause
> us trouble, and what the FSL approach is when migrating analyses
> to a new host ?
>
>
> thanks
> Neil
>
|