eda_plugin.actuators.micro_manager

Actuators that are based purely on Micro-Manager and can be used directly with the demo config.

This is interesting, if you already have set up a lot of details about your acquisition and maybe make extensive use of the on-the-fly pipeline in Micro-Manager. If this is not the case, have a look at the actuators.pycro implementation that gives some tighter control of the acquisition.

Actuator These actuators rely on the PythonEventServer plugin for micro-manager to receive events about user interaction with the Java GUI or ongoing acquisition events. The server is actually not directly link to this, but an EventBus is, that organizes and distributes event from the server itself. See utility.event_thread and utility event_bus for more details. Here, we connect to events on the EventBus and also emit events there for communication between the different parts of the EDA loop.

MMActuatorGUI A GUI to start and stop the acquisition from outside Micro-Manager. The actuator can be called without GUI and EDA will start with every acquisition as long as the plugin is running.

Classes

DirectMMAcquisition(*args, **kwargs)	Directly take images from the microscope by using the snap() function.
MMAcquisition(*args, **kwargs)	Thread that represents a running acquisition.
MMActuator(*args, **kwargs)	Micro-Manager based actuator.
MMActuatorGUI(*args, **kwargs)	GUI for the MMActuator providing a Start and Stop button.
TimerMMAcquisition(*args, **kwargs)	An acquisition using a timer in slow mode to 'open; acquisition in specific intervals.