To clarify: In
3.0_RC3, rather than explicitly requiring the
-cuda command-line option in order to use the CUDA version of
dwipreproc instead looks for the CUDA version and will automatically run that version. If however the CUDA version fails, then
dwipreproc will issue a warning, and automatically run the OpenMP version (if it is installed). Therefore, if you have placed the CUDA version of
eddy somewhere in your
PATH but never attempted to run it, then with the
3.0_RC3 update you will now get a warning that that version is failing. If however the OpenMP version runs without issue, then the outcome from
dwipreproc will not be detrimentally affected. If you are put off by the warning, the CUDA
eddy binary should simply be deleted, since it’s unable to run on your system regardless.
CUDA is very sensitive to version mismatches; not only between the CUDA version installed on the system and that used to compile the binary (which is why there are multiple versions of the CUDA version of
eddy provided), but also the kernel and video driver versions.
If you believe that the CUDA version should be working on your system, then you will need to run it manually and check the error message that it produces.
I had the Unicode error on 3 of 10 subjects during
I was hoping that Unicode conversion errors would have been removed with the
3.0_RC3 update. If you are indeed running this updated version and are still getting this error, please provide further details either here or on GitHub.