Early return behavior change
Added by Bob Grassucci over 8 years ago
After taking a super resolution image and before it has completed of saving the frames Leginon previously went to the next exposure target and centered the target in hl mode with the navigator (iterative modeled stage movement). Currently it seems to move to the next target but not collect the hl image iteratively until the super resolution image has been completely saved. This is slowing down the data collection significantly. We see the request for the hl image but no recieived image until the frames are all saved.
Replies (7)
RE: Early return behavior change - Added by Anchi Cheng over 8 years ago
Early return behavior did change after DM 2.3.1, but I thought it is not as bad as you stated. Could you confirm if SERIALEMCCD log says it is doing early return indeed, I will check here as well when I can get on the scope.
RE: Early return behavior change - Added by Bob Grassucci over 8 years ago
Where do I find the SERIALEM log? The time difference per stack of frames is 2 minutes vs 1.5 minutes. With no early return it is 3 minutes if I recall. We are not displaying any frames.
RE: Early return behavior change - Added by Anchi Cheng over 8 years ago
See trouble shooting section at the end of Gatan_K2_installation_and_setup
RE: Early return behavior change - Added by Anchi Cheng over 8 years ago
I am sorry to report that it did the same here at NRAMM. The DM change is not controlled by us. The command sent to SERIALEMCCD.dll, but DM does not take the request until frames are saved.
RE: Early return behavior change - Added by Bob Grassucci over 8 years ago
Is it the same with version DM 3?
RE: Early return behavior change - Added by Anchi Cheng over 8 years ago
Unfortunately yes. There is no scripting level change from DM 2.31 to DM 3
RE: Early return behavior change - Added by Anchi Cheng over 8 years ago
There might be things that I can do. Let me consult David Mastronarde.