Project

General

Profile

Actions

Bug #3617

open

nominal option needed to be in web gui to shift large nominal defocus

Added by Anchi Cheng over 8 years ago. Updated over 8 years ago.

Status:
In Test
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
10/01/2015
Due date:
% Done:

0%

Estimated time:
Affected Version:
Appion/Leginon 3.2
Show in known bugs:
No
Workaround:

Description

The option was disabled. However, when the value is to close to the extreme of defocus search range, ctffind3 fails to find it.

A case of 1.2 um becoming 3.7 um showed that the option is still useful.

Actions #1

Updated by Anchi Cheng over 8 years ago

  • Assignee changed from Anchi Cheng to Ed Eng

r19210 restore the option in web interface for ctffind3 program

Ed. please check with the user who had the problem on J1230 to see if it works.

Actions #2

Updated by Anchi Cheng over 8 years ago

nomimal option is also not applied in ctffind4.py

Neil, is there a particular reason for that and/or hiding nominal option in general. From annotation, this has been disabled in the gui for quite a long time now.

One possibility is that if a range of defocus is set during a session, not all should have the same nominal so the option does not seem that useful. I wonder if we should instead consider a "nominal offset" which shifts the zero defocus, and add any database image defocus by that number as that is what happens to instrument.

Actions #3

Updated by Neil Voss over 8 years ago

I forget the history, but I just think I never implemented it. It is likely disabled because I copied the ACE1 CTF page.

If you have a difficult image, you could try manual CTF. This also could be related to my CTF resolution stuff failing on close to focus images, Bug #3438.

Actions #4

Updated by Anchi Cheng over 8 years ago

This case is actually ctffind3 problem. The search range as input to the program did reach the real defocus, although only barely. However, it did not find it. It may also related to the fact that most images in that session has a fair amount of astigmatism. It appears that the initial search is not even along the input range.

Actions #5

Updated by William Rice over 8 years ago

Can this be added to the ctffind4 interface as well? Often seem to be running into this problem on the 2100 too.

Actions #6

Updated by Anchi Cheng over 8 years ago

  • Assignee changed from Ed Eng to Neil Voss

Neil,

If you can do this without much effort, please do so. I scanned the python code, but not sure what nominal and/or newnominal will do what this effect needs.

Actions #7

Updated by Neil Voss over 8 years ago

  • Status changed from Assigned to In Code Review
  • Assignee changed from Neil Voss to Anchi Cheng
Actions #8

Updated by Anchi Cheng over 8 years ago

  • Status changed from In Code Review to In Test

Will test tomorrow.

Actions

Also available in: Atom PDF