Patch Ctf problems in 3.1

Hi,

since our update to 3.1 we do get this error message in patch ctf estimation with many datasets: this happens always at specific micrographs and is really reproduceable.
These micrographs where this happens are fairly contaminated with ice. But still I think that the algorithm should not fail on this point. This is the error:

Traceback (most recent call last):
File “/users/svc_cryosparc/software/regular/cryosparc2_worker/cryosparc_compute/jobs/runcommon.py”, line 1726, in run_with_except_hook
run_old(*args, **kw)
File “/users/svc_cryosparc/software/regular/cryosparc2_worker/deps/anaconda/envs/cryosparc_worker_env/lib/python3.7/threading.py”, line 870, in run
self._target(*self._args, **self._kwargs)
File “/users/svc_cryosparc/software/regular/cryosparc2_worker/cryosparc_compute/jobs/pipeline.py”, line 186, in thread_work
work = processor.exec(item)
File “/users/svc_cryosparc/software/regular/cryosparc2_worker/cryosparc_compute/jobs/pipeline.py”, line 43, in exec
return self.process(item)
File “cryosparc_worker/cryosparc_compute/jobs/ctf_estimation/run.py”, line 112, in cryosparc_compute.jobs.ctf_estimation.run.run.ctfworker.process
File “cryosparc_worker/cryosparc_compute/jobs/ctf_estimation/run.py”, line 118, in cryosparc_compute.jobs.ctf_estimation.run.run.ctfworker.process
File “cryosparc_worker/cryosparc_compute/jobs/ctf_estimation/run.py”, line 119, in cryosparc_compute.jobs.ctf_estimation.run.run.ctfworker.process
File “cryosparc_worker/cryosparc_compute/jobs/ctf_estimation/patchctf.py”, line 71, in cryosparc_compute.jobs.ctf_estimation.patchctf.patchctf_v217
File “cryosparc_worker/cryosparc_compute/jobs/ctf_estimation/patchctf.py”, line 756, in cryosparc_compute.jobs.ctf_estimation.patchctf.patchctf_v217
File “cryosparc_worker/cryosparc_compute/jobs/ctf_estimation/patchctf.py”, line 626, in cryosparc_compute.jobs.ctf_estimation.patchctf.patchctf_v217.EPA_suppress_past_k2k4crossover_point
ValueError: operands could not be broadcast together with shapes (0,) (30,)

Best,

David

Hi @david.haselbach,

This definitely sounds like a bug, thank you for reporting it. I will post and update when we have looked into it a bit.

Harris

Hi, I just want to chime in and say that we get this error message, too. We recently updated to 3.1.0. We can get around the error by choosing “classic mode”

1 Like

FYI to anyone who has been experiencing this, the recently released cryoSPARC version 3.2 includes a fix for this issue.

1 Like