Hello!
I am running into an issue with the new Micrograph Junk Detector, where the job runs like normal and then runs into an index error after the last example micrograph appears in the event log. Below is the relevant information and image of the error:
Input: Micrographs and particles from Inspect Picks of a Template Picker
Error:
(IndexError: index 632 is out of bounds for axis 1 with size 632)
Anyone have an idea as to what this means?
@perrottza Please can you post the outputs of these commands (replacing P99 and J999 with the relevant project and job IDs):
csprojectid="P99"
csjobid="J999"
cryosparcm cli "get_job('$csprojectid', '$csjobid', 'job_type', 'version', 'instance_information', 'status', 'params_spec', 'errors_run', 'input_slot_groups', 'started_at')"
cryosparcm joblog $csprojectid $csjobid | tail -n 40
cryosparcm eventlog $csprojectid $csjobid | tail -n 40
@perrottza thanks for reporting this. We’ve looked into it and unfortunately this is a bug. It will be fixed in a future release. In the meantime, you may be able to work around it by excluding particle picks that are near to the far +X and +Y edges of the micrographs. You could do this using the “subset particles” job, filtering by X and Y fractional location. Try a manual threshold of 0.9 or so.
– Harris
@perrottza CryoSPARC v4.7.1 contains a fix for this issue. Happy data processing.
