Hi I’m getting this error when try to run ab-initio on NS data set:
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/abinit/run.py”, line 316, in cryosparc_master.cryosparc_compute.jobs.abinit.run.run_homo_abinit
File “cryosparc_master/cryosparc_compute/engine/engine.py”, line 1194, in cryosparc_master.cryosparc_compute.engine.engine.process
File “cryosparc_master/cryosparc_compute/engine/engine.py”, line 1195, in cryosparc_master.cryosparc_compute.engine.engine.process
File “cryosparc_master/cryosparc_compute/engine/engine.py”, line 1136, in cryosparc_master.cryosparc_compute.engine.engine.process.work
File “cryosparc_master/cryosparc_compute/engine/engine.py”, line 421, in cryosparc_master.cryosparc_compute.engine.engine.EngineThread.compute_error
ValueError: Detected NaN values in engine.compute_error. 10445760 NaNs in total, 90 particles with NaNs.
I have run corrupt particle check on the same particles set and no corruption found.
The 2D look OK
Thanks @Elad for posting this information.
Does ValueError: Detected NaN values in engine.compute_error occur
every time you run a clone of the failed job
when inputting particles from a different extraction, downsampling or restacking job in the same project
in other projects
?
If possible, can you test if the error occurs after downgrading the CryoSPARC worker’s nvidia driver to version 525 and subsequently restarting the CryoSPARC worker.
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/abinit/run.py”, line 329, in cryosparc_master.cryosparc_compute.jobs.abinit.run.run_homo_abinit
File “cryosparc_master/cryosparc_compute/engine/engine.py”, line 1194, in cryosparc_master.cryosparc_compute.engine.engine.process
File “cryosparc_master/cryosparc_compute/engine/engine.py”, line 1195, in cryosparc_master.cryosparc_compute.engine.engine.process
File “cryosparc_master/cryosparc_compute/engine/engine.py”, line 1136, in cryosparc_master.cryosparc_compute.engine.engine.process.work
File “cryosparc_master/cryosparc_compute/engine/engine.py”, line 421, in cryosparc_master.cryosparc_compute.engine.engine.EngineThread.compute_error
ValueError: Detected NaN values in engine.compute_error. 52228800 NaNs in total, 90 particles with NaNs.
Have you tried running the check for corrupt particles job? If you turn on the parameter “Check for NaN values”, it will report whether or not any particles on disk contain NaNs. I recommend running that job, just to see if there are in fact NaN values on-disk. The job doesn’t fail if there are NaN values, it just emits a warning, which can be easy to overlook. There’s also a summary printed near the end of the job’s stream log which will list all files that contained NaNs. The job will output a subset of the input particles that is chosen to avoid all the files that contain NaNs, which may allow you to continue processing the data by using the cleaned particle subset.
Just following up regarding my previous post. Did you try the check for corrupt particles job, and if so what was the outcome. Your input would be valuable to us as we try to diagnose the cause of these NaN value errors.
I have try it and no corrupt particles.
It was happened again in a different project.
In both cases it is a NS data set that the particles do not picked with the blob picked [picking mostly non particle] so I use the exp tool to switch to non-ns and then it pick well bur give this error.
I tried the check for corrupt particles job . No corruption detected( see attached picture).
I can resolve this issue by reselecting the 2D classes and using the reselected classes to run an ab initio job. This approach often solves the problem.