dstoychev

I believe all back-illuminated CMOS cameras lack a global shutter and should be treated as if they had a rolling one. As such, it is really important to associate a...

I narrowed down the issue to the fact that under Windows `DeviceServer` objects, being subclassed from `multiprocessing.Process`, need to be pickleable. This doesn't work for functions defined in the config...

There is a different implementation of the multiprocessing library that uses `dill` instead of `pickle` and it may be able to cope with this corner case: https://github.com/uqfoundation/pathos But I think...

Just to recap (mainly for my benefit): the issue here is that `DeviceServer` objects will be ran by sub-processes, which could have different scopes than the main process. Therefore, dynamically...

Implemented here: https://github.com/dstoychev/microscope/tree/lumencor-le.

This sounds sensible and I do not think it is going to break any of the systems in Oxford. We lose the ability to change the transform dynamically, but this...

I tested how the transform works on DeepSIM. I confirm that it does **not** use the settings dictionary and it uses the `Camera.set_transform` API directly.

I think this should be reconsidered. I know we've had discussions about this in the past, but now that I've looked into this in greater detail I think we are...

The first paragraph from my previous comment is not really true. For the software it's important to define/set the trigger mode because that's how the reaction to enable/disable events is...

I have a working implementation of this here: https://github.com/dstoychev/microscope/tree/lumencor-le.