@ncoudray Cloning a job that originally was created with an older CryoSPARC version may result in incorrect job runtime behavior if certain aspects of the job type’s implementation have changed between the old and current CryoSPARC versions. It seems that in the current case, you may instead have run into the very bug that was discussed in After upgrade to 4.4 -- No match for doseweights.
1 Like