Bug #3638
closed
findMagnifications does not set new MagnificationsData in the database
Added by Anchi Cheng about 9 years ago.
Updated about 9 years ago.
Affected Version:
Appion/Leginon 3.2
Description
Addition of projection lens series requires new magnifications to be added.
- Status changed from Assigned to In Test
r19219 force it to save if not the same self.magnfications which will be recorded in the database at the end of gui operation.
This means the procedure to change magnifications in the database is
- Start leginon and an application with Leginon Client opened on the scope computer as usual.
- From Client gui, select Scope instrument and click on the "Get Magnfication" tool (shaped like a calculator)
- Restart leginon.
The change in magnifications list in the client gui does not take into effect until it is restarted.
- Status changed from In Test to Closed
did not hear back. Must have worked.
- Status changed from Closed to Assigned
On the scope today trying to get the setup finished with the new application and our new presets modes. I hadn't realized this before, but when I re-calculate the mags it added the new 50X mag, but it did not remove the 100X mag from the list of mags available on the client leginon. I hadn't tried to use any other low mag modes yet, so I just noticed that because it did not eliminate 100X from the list it has thrown off the register of the mags, so if I send 300X through leginon, the microscope gets set to 400X, if I send 400X, it gets set to 500X, etc. This is only true for low mag mode, mag1 works fine for all mags. It does always correctly read in the correct mag on both computers.
Try with direct pyscope findMagnification and sinedon insert in r19272
Usage: copy the file on where Jeol scope Leginon Client is controlled, and execute the python file.
- Status changed from Assigned to In Test
- Status changed from In Test to Closed
The python way is more reliable and proved to work.
Also available in: Atom
PDF