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
In order to reach the goal of unified interface for a number of devices, I think coPylot would need to define a set of base classes (e.g. camera, stage, etc.) with core methods and properties which specific device classes (e.g. Orca, ASI_state) would have to inherit and implement, in a similar way as done in MicroManager (MMDevice.cpp and MMDevice.h).
A good starting set of device would be
camera
stage (can support single (e.g. Z) or number of axes (e.g. XY))
shutter - provides open and close methods
state_device - device which can go between multiple states, e.g. a filter wheel or a light source with multiple wavelengths
io_device - e.g. NI DAC or Arduino
hub - e.g. ASI Tiger controller, which manages multiple devices
galvo - not sure if this will be very different from stage
The text was updated successfully, but these errors were encountered:
Hi @ieivanov , we want to implement such classes as abstract base classes. We need to get one example from each device type and I think we will populate all these quite soon. Let's discuss on specifics in next meeting.
The shutter device should probably be named light_source and further provide intensity property. In that case, mechanical shutters will be constrained to 100% intensity
In order to reach the goal of unified interface for a number of devices, I think
coPylot
would need to define a set of base classes (e.g. camera, stage, etc.) with core methods and properties which specific device classes (e.g. Orca, ASI_state) would have to inherit and implement, in a similar way as done in MicroManager (MMDevice.cpp and MMDevice.h).A good starting set of device would be
open
andclose
methodsThe text was updated successfully, but these errors were encountered: