IMAQdxCamera: optional autoscaling, and background subtraction

[chrisjbillington]

Add optional autoscaling to IMAQdxCamera. Previously, autoscaling was always on.

Add basic background subtraction. A background can be set, which will be subtracted from subsequent images in manual mode.

[zakv]

This looks great! I tested it with our PCO camera which inherits from the IMAQdxCamera classes and it worked well. I just have a few questions/comments

• One small issue is that the "Set background" feature currently runs into trouble if it is clicked before any images have been acquired. When it is pressed before an image is acquired, image_receiver.image gets set to None and then image_receiver.update_image() gets called, which throws AttributeError: 'NoneType' object has no attribute 'swapaxes'.
  • A solution to this would be to have image_receiver.set_bg_image() only set the background image and call self.update_image() if self.image is not None.
  • image_receiver.set_bg_image() should probably also return True or False indicating whether or not it updated the background image. Then IMAQdxCameraTab.on_set_bg_clicked() should only show/hide buttons if the background image was actually set.
  • Maybe an error message window should pop up indicating to the user that their button click was detected but no background was set? Otherwise their input would be silently ignored which might look like a bug.
• It might be nice to save/restore the background image when blacs is closed/opened.
• The background subtraction is for the display only; the copies of the images taken during a shot and saved to the hdf5 file don't have the background image subtracted.
  • I wonder if there is a good way to indicate this to the user? Maybe mention it in a tooltip? I'm not attached to this idea but thought I'd mention it in case you can think of a better solution.
• This merged fine with #63. I thought that there might be a conflict since both edit IMAQdxCameraTab.get_save_data() and IMAQdxCameraTab.get_save_data(), but git handled the merge just fine without any manual intervention.
• At first I thought that the background subtraction might already be implemented by the "Subtract" option in the "Normalization" tab of the ImageView (see screenshot below), but I think I was wrong.
  • From digging around the source code (see the normalize() method in particular) it looks like it's designed for image arrays that are 3D (e.g. a series of images displayed together) so it doesn't do exactly what is done by the code in this PR.