Bug #1042
closedexposure timestamp
0%
Description
In cameraclient.py, I had to move the camera parameter retrieval to after the exposure. This is because of the DE12, where we need certain information after exposure (raw frames location, number of frames, etc). As a side affect, the "system time" parameter may be less accurate, even though it was probably not very accurate before anyway. It will now be the time after the exposure and the readout is done.
To solve this problem, I made a new camera parameter "exposure timestamp" which should be the most accurate timestamp that we can get from the camera in pyscope. This is now exposed to leginon, but it needs to use it when doing drift checks and any other time sensitive operations. This change should only be made to leginon when we are sure we can update pyscope on all the scopes, or error checking needs to be put in to fall back to "system time" when "exposure timestamp" is not available.
Updated by Anchi Cheng about 11 years ago
- Assignee changed from Jim Pulokas to Anchi Cheng
jim says: intended as a more accurate timestamp of when the exposure actually happens, rather than what we currently do is get a timestamp right before calling getImage(). If getImage() has any significant setup overhead, then the current method is not as accurate. "exposure timestamp" is calculated within the getImage() function and could (maybe not) be more accurate in some cases.