Project

General

Profile

Actions

Bug #1295

closed

protomo azimuth

Added by Scott Stagg over 13 years ago. Updated over 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
05/11/2011
Due date:
% Done:

0%

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

Description

Currently for the first iteration of a protomo run, the azimuth is being set to 90 degrees. Protomo then refines the azimuth iteratively. It would make much more sense to query the azimuth from the tomography goniometer model. In other words, somewhere in the db, we keep a value called phi that models the position of the tilt axis. Azimuth and phi are the same thing. Changing this would make the auto tilt series+tomogram routine a lot better too because the tilt axis would be better modeled. One issue will be that leginon and protomo use different conventions for how to measure where the tilt axis is. Protomo measures from x, and I believe that Leginon measures from y. In other words, if phi is 0, then azimuth would be 90. Another potential problem is that in my hands protomo mirrors images along x which would mean that if phi is 5 then azimuth would be 85. Right now, the first iteration is suboptimal because the function convertShiftsToParams sets azimuth to 90. This probably works for y'all because your tilt axis is close to y.

Actions

Also available in: Atom PDF