Actions
Bug #3960
openCTF estimation resmax parameter get modified in a run mixed with and without bestctf
Start date:
02/17/2016
Due date:
% Done:
0%
Estimated time:
Affected Version:
Appion/Leginon 3.2
Show in known bugs:
No
Workaround:
Description
For example, If we have two images in the session, the first image image1.mrc has a successful previous ctf run, image2.mrc failed in previous run, then --bestctf causes the following problem.
This part of ctffind4.py code redefined self.params['resmax'] while running image1.mrc
if gmean < self.params['resmin']*0.9:
# replace only if valid Issue #3291
self.params['resmax'] = round(gmean,2)
apDisplay.printColor("Setting resmax to the geometric mean of resolution values", "purple")
Therefore, when image2.mrc is processed, resmax is at lower resolution than the original user definition.
This problem get worse next time a bestctf is found. Making resmax become lower and lower.
This bug is in at lease ctffind4.py and ctfestimate.py
attached is a pair of image that if you upload alternatively, you may get the error of ctffin4 floating point divide by zero in ctffin4
pixelsize 2.816 A
ht 200 kV
cs 2.0 mm
Use myamiweb defaults.
Files
Actions