Error:'bins` must be positive, when an integer in patch ctf estimation

CTF Estimation
1

Hi, I have two problems in patch ctf estimation, Here is the log. How can I correct them ? Thank you !
[CPU: 285.4 MB Avail: 504.12 GB]Child process with PID 236921 terminated unexpectedly with exit code 1.
[CPU: 288.9 MB Avail: 504.12 GB]Traceback (most recent call last):
File “cryosparc_master/cryosparc_compute/run.py”, line 115, in cryosparc_master.cryosparc_compute.run.main
File “cryosparc_master/cryosparc_compute/jobs/ctf_estimation/run.py”, line 438, in cryosparc_master.cryosparc_compute.jobs.ctf_estimation.run.run
File “cryosparc_master/cryosparc_compute/jobs/ctf_estimation/run.py”, line 235, in cryosparc_master.cryosparc_compute.jobs.ctf_estimation.run.run.make_outputs
File “/home/ce01/cryosparc/cryosparc_worker/deps/anaconda/envs/cryosparc_worker_env/lib/python3.10/site-packages/matplotlib/pyplot.py”, line 3236, in hist
return gca().hist(
File “/home/ce01/cryosparc/cryosparc_worker/deps/anaconda/envs/cryosparc_worker_env/lib/python3.10/site-packages/matplotlib/init.py”, line 1465, in inner
return func(ax, *map(sanitize_sequence, args), **kwargs)
File “/home/ce01/cryosparc/cryosparc_worker/deps/anaconda/envs/cryosparc_worker_env/lib/python3.10/site-packages/matplotlib/axes/_axes.py”, line 6862, in hist
m, bins = np.histogram(x[i], bins, weights=w[i], **hist_kwargs)
File “<array_function internals>”, line 180, in histogram
File “/home/ce01/cryosparc/cryosparc_worker/deps/anaconda/envs/cryosparc_worker_env/lib/python3.10/site-packages/numpy/lib/histograms.py”, line 793, in histogram
bin_edges, uniform_bins = _get_bin_edges(a, bins, range, weights)
File “/home/ce01/cryosparc/cryosparc_worker/deps/anaconda/envs/cryosparc_worker_env/lib/python3.10/site-packages/numpy/lib/histograms.py”, line 424, in _get_bin_edges
raise ValueError(‘bins must be positive, when an integer’)
ValueError: bins must be positive, when an integer

2

@yangtaili Please can you post the following details

  1. camera model
  2. dimensions (in pixels) and frame count of movie files
  3. pixel size (Å)
  4. Did the error happen on one of the n first exposures being processed (where n refers to the number of GPUs used in the job) or part-way through the job?