Full-frame motion correction job error

I encounter an error when running the motion correction job using the T20S tutorial dataset. Does anyone know how to handle this problem? Thanks!

Importing job module for job type rigid_motion_correction…

Job ready to run

Traceback (most recent call last):
  File "cryosparc2_worker/cryosparc2_compute/run.py", line 78, in cryosparc2_compute.run.main
  File "cryosparc2_worker/cryosparc2_compute/jobs/motioncorrection/run.py", line 301, in cryosparc2_compute.jobs.motioncorrection.run.run_rigid_motion_correction
  File "cryosparc2_compute/engine/__init__.py", line 8, in <module>
    from engine import *
  File "cryosparc2_worker/cryosparc2_compute/engine/engine.py", line 11, in init cryosparc2_compute.engine.engine
  File "cryosparc2_worker/cryosparc2_compute/engine/gfourier.py", line 6, in init cryosparc2_compute.engine.gfourier
  File "/molbio2/cryoem-local/cryosparc/cryosparc2_worker/deps/anaconda/lib/python2.7/site-packages/skcuda/fft.py", line 13, in <module>
    from . import cufft
  File "/molbio2/cryoem-local/cryosparc/cryosparc2_worker/deps/anaconda/lib/python2.7/site-packages/skcuda/cufft.py", line 238, in <module>
    _libcufft.cufftSetCompatibilityMode.restype = int
  File "/molbio2/cryoem-local/cryosparc/cryosparc2_worker/deps/anaconda/lib/python2.7/ctypes/__init__.py", line 379, in __getattr__
    func = self.__getitem__(name)
  File "/molbio2/cryoem-local/cryosparc/cryosparc2_worker/deps/anaconda/lib/python2.7/ctypes/__init__.py", line 384, in __getitem__
    func = self._FuncPtr((name_or_ordinal, self))
AttributeError: /usr/local/cuda-9.2/lib64/libcufft.so: undefined symbol: cufftSetCompatibilityMode

Hey @wujp08,

Are you running the latest version of cryoSPARC? cryosparcm update

Hi, I am using the v2.1.0 version. Thanks!

This bug was fixed in a later version - the current latest is v2.5.0. Please update :slight_smile:

Thanks. It seems changing to CUDA9.1 also helps.
But I have another bug when running CTF estimation. Is it also becasue of lower version?

Hi @wujp08,

In your screenshot, it seems like CTFFIND 4 outputted an error log. Can you double check that first?