Project

General

Profile

Actions

Feature #1847

closed

Implement next generation CTF display tools

Added by Neil Voss over 12 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Python scripting
Target version:
Start date:
06/11/2012
Due date:
% Done:

0%

Estimated time:

Related issues 14 (1 open13 closed)

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

Actions
Related to Appion - Bug #1850: ACE1 inserts radians for astig angle while ctffind and ace2 use degreesClosed06/12/2012

Actions
Related to Appion - Bug #1874: 'lowess' in ctfestimate.py ClosedMelody Campbell06/21/2012

Actions
Related to Appion - Feature #1876: add Xmipp CTF estimation to AppionClosed06/21/2012

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

Actions
Related to Appion - Feature #1867: Make a smarter Appion implementation of CtfFind ClosedDmitry Lyumkis06/20/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
Related to Appion - Feature #1884: more options for ctf estimation displayClosedAnchi Cheng06/25/2012

Actions
Related to Appion - Feature #1958: Next Gen CTF Display for Rectangular ImagesClosedMelody Campbell07/31/2012

Actions
Related to Appion - Feature #1967: Phase 3 Next Gen CTF Display Tools: CTF resolutionClosedNeil Voss08/06/2012

Actions
Related to Appion - Feature #2400: Implement Neil's Phasor Ctf programClosed06/19/2013

Actions
Blocked by Appion - Bug #1849: Ace2 estimate gets astigmatism angle wrong for image created by Ace2correctClosedGabriel Lander06/12/2012

Actions
Follows Appion - Feature #1845: move apCtf.py into a folder as apCtf/ctfdb.py to allow major expansion of CTF related functionsClosedAmber Herold06/09/2012

Actions
Actions #1

Updated by Gabriel Lander over 12 years ago

The allowable CS range should be higher. It was limited to 4mm, but our T12 has a CS of 6.3mm. I upped the allowable range to 7mm, but I don't know what the upper limit of the CS on EMs are, does anyone know?

Actions #2

Updated by Gabriel Lander over 12 years ago

Neil could you please look at the fix I added to makestack2.py in r16905?
When using CTFFind values for ace2correct.exe, a tmp_ctfvaluesfile.txt is created. Apparently the abs(df1) must be less than abs(df2), but this is not necessarily the case with the CTFfind output, so this was causing ace2correct.exe to use ridiculous astigmatism angles.
The df values are now sorted for the tmp file, but is the astigmatism angle still OK to use as is?

Actions #3

Updated by Neil Voss over 12 years ago

Hi Gabe,

I did not realize some scopes (at least in use for 3dem) would have a Cs so high?

Gabe, I think your |df1| < |df2| fix, breaks things. If you swap the defocus values, you need to change the angle by 90 degrees. I made a change, can you test. see r16912.

Actions #4

Updated by Gabriel Lander over 12 years ago

astig + 90 seems to work, but old negative CTFFind values still breaks ace2correct phaseflipping, using the abs values when creating tmp_ctfvalues file
r16939

Actions #5

Updated by Neil Voss over 12 years ago

Hi Gabe, I do not think I changed the sign on CTFFIND or makestack. Oh well, this is a bigger mess than I thought. I think it is time to start adding abs() everywhere when it comes to CTF. I really appreciate you helping and debugging this for me.

Actions #6

Updated by Amber Herold over 12 years ago

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

Updated by Neil Voss about 11 years ago

  • Status changed from Assigned to Closed
Actions

Also available in: Atom PDF