Consider how to allow for writing a different number of frames than is collected.

[jwlodek]

One thing we do sometimes is run a detector at a speed 10x faster than the data being collected, and average 10 frames at a time as a way to get better noise levels. Currently the logic sets the num_images and the expected num_capture to the same amount. it would be good if we could introduce a way to scale these numbers.

Acceptance Criteria

• There is a way to specify that we want to take say 1000 images which will result in 100 frames written to disk

[coretl]

Do you average the frames with a proc plugin?

[jwlodek]

Yes, we use the proc plugin for this

[coretl]

If we add a DetectorProcessor bit of logic that has the ability to know how the image is averaged down would that work? Would you want to tie the number of exposures averaged to the exposures_per_event field in the TriggerInfo passed to prepare? Or would these numbers ever need to be different?