Project

General

Profile

Actions

Feature #1867

closed

Make a smarter Appion implementation of CtfFind

Added by Neil Voss over 12 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Category:
Image Processing
Target version:
Start date:
06/20/2012
Due date:
% Done:

0%

Estimated time:

Related issues 7 (1 open6 closed)

Related to Appion - Bug #1877: problems with ctfestimate.py in defocus range and displayClosedMelody Campbell06/21/2012

Actions
Related to Appion - Feature #1881: create a new selection menu for CTF programsClosedAnchi Cheng06/25/2012

Actions
Related to Appion - Feature #1206: CTF display and control needs work. Let's discussClosed02/27/2011

Actions
Related to Appion - Feature #1847: Implement next generation CTF display toolsClosedNeil Voss06/11/2012

Actions
Related to Appion - Feature #1882: Implement an interactive CTF for experimenting with new algorithmClosedNeil Voss06/25/2012

Actions
Related to Appion - Bug #1883: Switch CTF powerspec fit from peaks to valleys and add 3rd column for opimage #3In Code ReviewAnchi Cheng06/25/2012

Actions
Has duplicate Appion - Feature #1179: CtfFind ModificationDuplicate02/09/2011

Actions
Actions #1

Updated by Neil Voss over 12 years ago

  • Status changed from Assigned to In Code Review
  • Assignee changed from Neil Voss to Dmitry Lyumkis
Actions #2

Updated by Gabriel Lander over 12 years ago

Data that is uploaded (we are doing lots of film at the moment) does not have have a value for:
imgdata['camera']['pixel size']['x']
so that "dstep" value is set to None and ctffind won't run. I don't know if this should be fixed in the upload script, but for now I added some code to get the dstep from the uploaded pixelsize if the info from the camera comes back with None.
r16874

Actions #3

Updated by Gabriel Lander over 12 years ago

The method for determining the min & max defocus seems a bit excessive using the defaults of 5000 Angstroms and 25 steps in either direction.
For a nominal defocus of 2 microns, this will search from 0.5uM to 14.5uM
Is this intentional?

Actions #4

Updated by Neil Voss over 12 years ago

Hi Gabe. Not intentional, I was probably off by an order of magnitude. Make the change if you wish, otherwise I will try and get to it tomorrow.

Actions #5

Updated by Neil Voss over 12 years ago

Hi Gabe, I think your fix for the dstep is good. Rather than taking pixel size directly, ctffind requires two values and then calculates the pixel size, so as long as it works out it is okay with me.

Actions #6

Updated by Amber Herold over 12 years ago

  • Target version changed from Appion/Leginon 2.3.0 to Appion/Leginon 2.2.1
Actions #7

Updated by Amber Herold over 12 years ago

  • Target version changed from Appion/Leginon 2.2.1 to Appion/Leginon 3.0.0
Actions #8

Updated by Anchi Cheng almost 7 years ago

  • Status changed from In Code Review to Closed
Actions

Also available in: Atom PDF