Mick

[clarity_processor](https://github.com/pptman/clarity_processor) converts incoming data to ```cv2.UMat```s which should preserve the full depth. For raw data, there is no conversion. Has the camera been set up to return 16-bit data in...

I'm not sure I understand this one. We can already talk to serial devices, but we'd need a defined interface (not to mention defined behaviour) on the Arduino end.

That makes sense. The Settings system is useful for things that have restricted values such as, on some cameras, binning (some will allow non-square binning, others won't) and ROI (some...

Cockpit now handles non-square images correctly: as long as the camera reports the image size *after* the binning operation, it'll be handled and displayed correctly. I think Ian's point was...

@NickHallONBI - can you test this with the hardware when you get a chance?

Some of this is addressed in #90.

There's a transform system on the cameras to compensate for: * orientation of the camera (fixed, but can vary between instances of the same camera type depending on how they're...

How about using an Enum which maps 0-based integers to whatever the filter wheel uses?

[Work in progress](/mickp/microscope/tree/121-pipeline)

* Is the stage running the correct firmware version for the library you are using? * Take a look at the other flags in the `_connectionstatus` on the stage object...