You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the trigger mode selection is only sent to the device (SDK call) when acquisition is started. This is not good because switching triggers modes can enable detector scrubbing. If scrubbing is currently disabled and then a trigger mode that enables scrubbing is selected we want the scrubbing to be enabled immediately, not when acquisition is started. If not then the first images may have excess dark current.
The fix is quite easy. The SDK calls at the beginning of the start acquisition function should be moved to a new setupAcquisition function that is called from the writeInt32 or writeFloat64 function when any of the relevant parameters are changed.
The text was updated successfully, but these errors were encountered:
Currently the trigger mode selection is only sent to the device (SDK call) when acquisition is started. This is not good because switching triggers modes can enable detector scrubbing. If scrubbing is currently disabled and then a trigger mode that enables scrubbing is selected we want the scrubbing to be enabled immediately, not when acquisition is started. If not then the first images may have excess dark current.
The fix is quite easy. The SDK calls at the beginning of the start acquisition function should be moved to a new setupAcquisition function that is called from the writeInt32 or writeFloat64 function when any of the relevant parameters are changed.
The text was updated successfully, but these errors were encountered: