Forums » Leginon »
FC preset format not gain corrected even with norm image created
Added by Bob Grassucci over 10 years ago
I noticed that the 1024 4X binned image (FC) was not normalized even though there is a normalization image there for this format. I switched FC to 2X binning and 2048 until this can be resolved. I have attached a jpg of the uncorrected image. I suspect something with the database after the upgrade to 3.0 on our F30. The F20 is still using Leginon 2.2.
Cane check through imagereport page (accessible by the "i" button in the web imageviewer) what bright images it is supposed to use ?
Follow the Data tree to get something like this:
If this is K2, 1024 4x would not quite work. Is this on UltraScan ?
Could it simply oversaturated? We don't normally do fc with 4x bin. But 4x bin means 16x intensity sum. If this is meant for manual focus, the dose tend to be quite high.
This is the ultrascan and I do find the norm image and dark image but no bright image in the data tree. I doubt that it is over-saturated the image mean was about 10000 not close to 64000 where it should saturate.
Hi, Bob,
Although gain/dark correction only uses norm and dark images, bright image is recorded in the database for two years now, so it should be there.
I could not find an example on our side, nor reproduce it. Could you provide more details about how the image was taken: From which application, which node.
Does this happen to all images taken at this geometry 1024 x4 like the typical hl, sq, or just fc ?
taken in MSI-T (1.6) with correction node
just fc, hl and sq are fine
Are you saying that you
1. send preset to scope
2. go to Correction node
3. open settings
4. set tem and camera and then select camera geometry and exposure time
5. click o.k to exit settings dialog
6. select acquiring corrected image and channel 0, for example.
7. then click on acquire tool.
When you send fc preset in step 1 vs. send hl preset, you get the latter corrected and the former not corrected ? Could you give a screen shot of the logger window ? I don't see how that could happen from the code.
