v2.5.0 now supports CUDA 10 - I think I read it in the update log… Anyways CUDA10 worked for the 2080TI/CS2 installation that I helped setup in December.
On the other hand I am not sure how the other programs would react to CUDA10. I think RELION is OK. But Gctf does not seem to have a CUDA10 build yet (not sure if any of the other builds runs on CUDA10).
It seems to be OK to install both CUDA8.0 and CUDA10.0 on the same machine. You can try leaving the /usr/local/cuda directed to /usr/local/cuda-8.0 while also having a /usr/local/cuda-10.0.
Still keep LD_LIB… directed to the symbolic linked directory:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda/lib64.
Then during cryoSPARC2 installation (or re-configuration?) you can try telling cryoSPARC2 that CUDA is at /usr/local/cuda-10.0. If this doesn’t work then probably you need to direct /usr/local/cuda to the 10.0 folder. If anything refuses to run with CUDA 10, maybe it is simpler to just wait for them to update. I think in our case I just left CUDA10 as the system CUDA in the end.
I do not own the 2080TI machine so these are just from the one-day test we did on that machine.