"

From 2010.igem.org

Revision as of 19:19, 14 October 2010 (view source) Langmo (Talk | contribs) (New page: = Information Flow = The imaging pipeline from the microscope to Matlab/Simulink The microscope is connected to a workstation using the core dr...) ← Older edit		Revision as of 19:19, 14 October 2010 (view source) Langmo (Talk | contribs) Newer edit →
Line 1:		Line 1:
		+	{{ETHZ_Basel10}}
		+	{{ETHZ_Basel10_InformationProcessing}}
		+
	= Information Flow =		= Information Flow =
	[[Image:MicroscopePipeline.jpg|thumb|400px|The imaging pipeline from the microscope to Matlab/Simulink]]		[[Image:MicroscopePipeline.jpg|thumb|400px|The imaging pipeline from the microscope to Matlab/Simulink]]

---

Revision as of 19:19, 14 October 2010

Information Flow

The microscope is connected to a workstation using the core drivers and interfaces of μManager (see Stuurman et al. (2007) or [1]). To provide a mechanism to change the cell's input signal depending on its fluorescence signal, we developed the microscope software μPlateImager, which enables for parallel acquisition of images and the modification of light input signals. μPlateImager uses the Java interface of the μManager core to control the microscope and can be configured by a separate platform-independent visual user interface. Since the communication with the microscope already requires a significant amount of system resources, it was necessary to swap the image processing, cell detection, and controller part to a second workstation to increase the possible frame rate. μPlateImager can therefore be controlled over the network or the internet by a GUI (graphical user interface). This GUI uses the yet undocumented Java MATLAB Interface (JMI) to start up a Matlab (The MathWorks, Natick, MA) process based on the open source project matlabcontrol (see [2]). It furthermore starts up a Simulink model and transfers the microscope control to several of the blocks of the Lemming Toolbox, a Simulink toolbox allowing for the block based interconnection of the main controller and image processing parts, like cell detection, tracking the visualization or the like.

Toolkit (Simulink)

A Matlab script is executed by μPlateImager, which transfers the control over the microscope and automatically starts the GUI based on Simulink. The GUI consists of several blocks representing the single steps of the image analysis and the control of the microscope. First, the microscope block triggers the microscope to make an image and sends this image to the cell detection block, which detects all cells in the current image and tracks them between the several frames. This information is send to the next block which selects the cell to be controlled. Furthermore, by comparing the change in the position of the E. lemming over several consecutive images, the direction of the E. lemming is estimated. This data together with the raw image is send to the display.
The direction of the cell is automatically compared to the direction it should go. This direction can be intuitively defined by the user using a joystick. The force feedback functionality of the joystick is used to give the user an intuitive feedback of the current direction of the E. lemming. If the difference between the actual direction of the E. lemming and the direction the user defined is too high, tumbling is automatically induced by a red light (660nm) pulse. Otherwise tumbling is supressed by a far red light (748nm). Alternatively the user can induce the pulses directly using the buttons of the joystick.

If the cell is moving out of the image the microscope moves automatically such that the cell is always approximately in the center of the image.