Dear Theodore,
>
> Thank you for your answer:
>
> "ls ${FSLDIR}/bin/eddy*" gives you
>
> "eddy_combine eddy_correct eddy_cuda eddy_openmp”
the executables you want to use are eddy_cuda or eddy_openmp depending on if you have a CUDA-gpu box on your system or not. If you do, then I strongly recommend using eddy_cuda. If not you should use eddy_openmp.
The latter is multi-threaded and will potentially take as many threads as it can get its hands on, which may not be what you want. In that case you can use the environment variable OMP_NUM_THREADS and set it to a suitable value.
If you prefer to have an executable called eddy I suggest you make a link from ${FSLDIR}/bin/eddy to ${FSLDIR}/bin/eddy_* where * is the version you decide to use.
Jesper
>
> I manually copied "eddy" in the "bin"-folder, however, if you try to execute it throws:
>
> "eddy: error while loading shared libraries: libnewimage.so: cannot open shared object file: No such file or directory"
>
> Please note, that we did not encounter the original "eddy"-problem on this machine (centos) but on the kubuntu-machine, where eddy works for some subjects but it does not work for others. (If it worked for all on the centos-machine, that would be the best possible solution, of course).
>
> Thanks again!
>
> Theodor.
>
>
> Dear Theodore,
>
>> Thank you very much for your fast reply! We are working on a Kubuntu 14.04 system (we planned to work on our more powerful CentOS machine, but unfortunately the 'eddy' command is not found, even though we reinstalled the latest FSL version, maybe you also have an advice concerning this problem).
>
> If you do
>
> ls ${FSLDIR}/bin/eddy*
>
> on your CentOS machine. What do you get?
>
> Jesper
>
>> On this Kubuntu server the FSL version 5.0.9 is installed. We are using eddy at the moment single-threaded.
>> Your help is greatly appreciated!
>> Best,
>> Theodor.
|