It seems dwipreproc goes with the highest eddy_cuda it finds, and if it fails then it tries eddy_openmp. Is that correct?
Problem is that FSL 6.0.1 provides eddy_cuda8.0 and eddy_cuda9.1. Our cluster can run the former, but not the latter. Dwipreproc only tries the latter before moving onto eddy_openmp. Can someone show me how to edit dwipreproc so it can choose eddy_cuda8.0? Any suggestions would be appreciated!
PS- Alternatively, if there’s no simple solution on this end, I can ask our cluster admins to delete eddy_cuda9.1, but they may be hesitant to modify and deviate from what is provided in the FSL download.