Hello everybody,
I'm having some trouble understanding what the situation for eddy is in FSL 5.0.10 on CentOS and RHEL. The installer installs eddy_cuda and eddy_openmp, but there is no eddy. Did eddy_openmp replace eddy for CPU jobs?
----
Here is the situation in FSL 5.0.10 on three/four different OSes.
On Ubuntu
The binary is available from NeuroDebian. Running eddy outputs "Part of FSL (build 509)..."
Size/md5: 757K/f2f4833e2b0a9dfd7e16c8d3cb3dc4b2
On Mac:
The binary is available after running the install script, fslinstaller.py. Running eddy outputs "Part of FSL (ID: 5.0.10)..."
Size/md5: 3.4M/e6b88ad6e1659a1bbbb34e0e5fdc3abc
On CentOS7/RHEL7
There is no eddy binary after running fslinstaller.py. Instead there is eddy_openmp. I understand we can create a symlink from eddy -> eddy_openmp, if we really want something called "eddy", as well as set the environmental named OMP_NUM_THREADS equal to 1, however I am wondering if this is what we should be doing, or if there is an actual binary named eddy for 5.0.10.
Best,
Louis
|