Difference between revisions of "Tracker"

From MagnetoWiki
Jump to navigation Jump to search
(Added link to source code)
(Added link to Auto build.)
Line 3: Line 3:
 
Tracker is a working name for software to track the path of animal movements in experiments.
 
Tracker is a working name for software to track the path of animal movements in experiments.
  
==Source Code==
+
==Source Code and Auto Build==
  
[http://houptlab.org/xtechops/websvn/listing.php?repname=Houpt+Lab+Source+Code&path=%2FTracker%2F#_Tracker_ Tracker Project]
+
[http://houptlab.org/xtechops/websvn/listing.php?repname=Houpt+Lab+Source+Code&path=%2FTracker%2F#_Tracker_ Tracker Project Code]
 +
 
 +
[http://www.magnet.neuro.fsu.edu/LabDisk/CEHoupt/Auto%20Builds/Tracker Tracker Auto Build]
  
 
==Proposed Functionality==
 
==Proposed Functionality==

Revision as of 12:42, 5 February 2007

Tracker Program Description

Tracker is a working name for software to track the path of animal movements in experiments.

Source Code and Auto Build

Tracker Project Code

Tracker Auto Build

Proposed Functionality

Input:

  1. Quicktime movies of experiment

Outputs:

  1. Numeric output
    1. Instantaneous
      1. time
      2. position
      3. orientation
    2. Derived
      1. velocity
      2. distance
      3. direction of motion
      4. measure of wall taxis
  1. Generated Movies
    1. Extracted data graphic.
    2. Overlay of extracted data graphic and original video.


Proposed Implementation

Time determined from Quicktime movie time stamps.

Position is average position of blob pixels.

Orientation is average vector from average position to blob pixels. Position and orientation can be used to define oval around body.

Direction of motion, velocity and distance are calculated from Time, Position and Orientation in the usual way.

Proposed Technology

Cocoa application.

QuickTime filter to convert video to 2-color B&W via brightness cutoff.

Filter (either QuickTime or after frame extraction) to clip non-experiment portion of video.

Frame-by-frame code to detect blob and calculate position, etc.

Alternative Implementation

Use grayscale instead of B&W. Position, etc would be calculated based on weighted pixels. This would be able to pick up sub-pixel changes and provide smoother, more accurate data.