Feature #1308
closedcs input from instruments,cfg to database InstrumentData
0%
Description
To make it possible to specify Cs value for different microscope when new scope is added.
Updated by Anchi Cheng almost 13 years ago
- Subject changed from cs input from instrument.s,cfg to database InstrumentData to cs input from instruments,cfg to database InstrumentData
- Status changed from New to In Test
- Assignee changed from Jim Pulokas to Arne Moeller
Jim and I worked together along the way and it is now used at NRAMM.
Arne, you can close this issue if your data collection has no problem saving images and use the images for ctf estimation.
To use, follow the example in the updated pyscope/instruments.cfg.template to add Cs value in meters in the TEM instrument at the scope PC installation.
Scott, Gabe, please note the following:
If it is an existing Leginion installation, to use this revision and beyond for data collection, the dbschema update made for #287 must be applied and be consistent with the updated instruments.cfg with cs value. Otherwise all calibrations for that tem would be lost and data not processable by newer Appion.
Updated by Anchi Cheng almost 12 years ago
- Status changed from In Test to In Code Review
- Assignee changed from Arne Moeller to Jim Pulokas
Jim, please review r16744 in case you want it done differently. It prints out the cs values from TEMs that have images acquired already. This is needed before users start using Leginon again after upgrading to 2.2 because Leginon wants to add new instrument if instruments.cfg and InstrumentData are not consistent. Ideally, this should be run on the TEM and check against its instruments.cfg automatically.
Updated by Jim Pulokas almost 12 years ago
- Status changed from In Code Review to In Test
- Assignee changed from Jim Pulokas to Anchi Cheng
In the interest of time, I like the idea of using cscheck.py for this release and make it automatic in the next release.