Actin Flow Metamorph Analysis Procedure
Actin Flow Metamorph Analysis Procedure
Actin Flow Metamorph Analysis Procedure
A) Image processing
Microtubule images (stacks or images) are processed with spatial filters in Metamorph
7.0 in the following sequence:
(1) “Process” “Basic Filters” “Operations” “Low pass” filter width 4 x 4 pixels
And click plane button and select all planes
(2) “Process” “Detect Edges” Filter “Laplace 2” And click plane button and select all
planes
(3) “Process” “Basic Filters” “Operations” “Low pass” filter width 3 x 3 pixels.
MAKE SURE CORRECT VID IS SELECTED
Alternatively, run the journal “MT and actin processing.jnl” on the timelapse stack. The
resulting stack is ready for MT speckle analysis.
From the processed image stack, choose MTs exploring the P domain for speckle
analysis. A ‘good’ MT should have clear speckles against background, not cross paths
with other MTs or intrapodia (which would retain a lot of free tubulin and contribute to
noise), and preferably have distinct growth/collapse phases.
Crop out the MT: Use the box region tool to select the MT, and “Edit””Duplicate”
“Stack with zoom”. Keep only the planes where the selected MT is clearly seen by using
the “Stack””Keep planes” function. If the MT is skewed (example in figure below),
measure the skew angle with the multi-line tool and rotate the cropped MT stack using
“Display””Rotate” Linear Interpolation. Further crop the rotated MT stack so that the
MT is clearly in the box region.
First, pick out clearly discernable speckles within the MT, use the line tool or multi-line
tool to trace the speckle from one frame to the other. This will be the internal reference
speckle to be used in both assembly and translocation dynamics.
To log translocation, measure the distance at which the reference speckle moves
relative to its position in the previous frame. Do this for every frame. If the slope of
internal speckle movement is less than 2 pixels between 2 sequential frames, I count it
as translocation pause.
To log assembly/disassembly, measure the length of distance from the plus end of the
MT, to an internal speckle for each frame. Be careful that a “true” assembly event
should see a new speckle at the plus end. Sometimes the tip-reference speckle
distance changes as a result of image processing of the speckles, and/or the MT is
being stretched /bent somehow. These do not count as assembly/disassembly events
and should only count as assembly pause.
From this raw data table, one can calculate the following parameters:
MT assembly dynamics: 1) Assembly and disassembly rates (this must be time-
weighted) 2) percentage of total observed time spent in assembly/disassembly/pause.
For documentation, save all of the regions using “regions””save regions”. This way,
you may load the saved regions on the corresponding image for later use or future
reference. Also note the frame span of the analyzed MT from its original timelapse stack
(e.g. “MT #1 is from frame 9-22 in the original stack”).
Process the actin timelapse using the MT processing filters mentioned above (“MT and
actin processing.jnl”), or simply use a 4 x 4 pixel width low pass filter---whichever gives
less noise and better kymographs (play around). REMEMBER TO CALIBRATE
IMAGES.
Calibration: measure> calibrate distances > load from file > go to data depot, lab
organization, current camera calibration, cascade II (1.5=90X, 1=60X),
Choose a region in the P-domain where actin speckles are clear (usually filopodium
have better actin signal/noise). Using the line tool, make a line on the actin bundle
starting from the leading edge to the C-domain*.
Open “Stack””Kymograph”. I typically use “line width 3”, “average” or “maximum”, and
background subtraction “minimum” for better kymograph signal/noise. Play around
these settings for best kymograph image quality. Press “create” while the line on the
stack is an active region.
Imaging Suter Lab 01/20/10
NOTE: The kymograph function in Metamorph 7.0 has a bug, please avoid the
following:
MetaMorph 7.0 introduced a problem with the Linescan and Kymograph functions
where the Linescan and Kymograph will measure incorrectly under the following
conditions:
The Line Width is greater than 1, and
The Direction of the line drawn is from Lower Right to Upper Left
http://support.meta.moleculardevices.com/docs/t20062.pdf (for more info)
On the created kymograph, choose clearly discernable slopes and place a line along
the slope from left to right. The data table in the kymograph box should automatically
show the velocity (as micron/sec), in this case this velocity is actin retrograde flow.
Open log (dynamic data exchange, i.e. excel), and log the data to excel using F9.
Create as many kymographs and measure slope (velocity) as needed. Note that the
kymograph function can only automatically measure velocity on the last created
kymograph, so do not make several kymographs at once and attempt to measure slope
velocity from each. Instead, make kymographs and measure velocities one by one.