Trajectory is up and running within the ProjectBrowser

I've fixed CSS styles and did some code changes within the GoogleChart package (due to the precision lost while converting from doubles I wasn't able to see normal and DTW plots at all). The trajectory runs on my workstation, will see today how it deals with bigger datasets. My next step would be to implement constraints, step patterns and open end alignment classes plugging them into UI.

Who broke the build!?

Last week I've cleaned up the Trajectory code and finally merged my branch with the trunk. I've broke the build. I'm sorry. Thank you Philip for prompt response and help fixing it.

Among other things, since I've forked it long ago, I had some troubles with code layout and Trajectory page is still messed up since the div's name changed within HTML templates. Next week will fix CSS's and HTML's for the trajectory. Good news that it performs as it suppose (at least on my workstation).

Started organizing my literature review using CiteULike.

And after all I'm coding scanner and parser parts for the compiler :P...

Progress report

I've finished modifying code architecture for the DTW and improved data normalization for the time series. The original Telemetry and GoogleChart modules code which I borrowed for modification appeared to have three or four validation and format routines which were designed the way which prevented normalized data to be rendered properly. I've changed/commented out validations and formatting but not sure if it was right decision, I feel like I need a little more time to see what was behind this formatting and will post results later.

The most current plots:

Progress report

Last week I was working on two tasks: implementing required code changes in the Trajectory component and second is writing some ideas for the technical report.

Hacking progress:

• Time-series normalization: Initially I was normalizing the time series by simply dividing all values by the maximal one, last week I've changed this method to more appropriate one by following the method suggested by Dina Q. Goldin and Paris C. Kanellakis in the "On similarity queries for time-series data: Constraint specification and implementation" chapter of "Principles and Practice of Constraint Programming — CP '95" book.


• DTW improvement: I'm trying to move from the original DTW implementation towards the more customizable implementation using step functions suggested by Sakoe-Chiba:
  .
  Unfortunately hack is no moving fast, - I am working on the architecture design to make step and constraints functions pluggable into the "generic DTW" code. I think this is the most elegant solution. In the future it'll allow to plug any user-configured function in the code. Really want to benchmark the performance of all the options since for the speech and writing recognition it worked well.

Book: Information Retrieval for Music and Motion.

Want to share one of my findings: while collecting papers for the literature review, I found a very interesting book related to the research I am doing: "Information Retrieval for Music and Motion", Müller, Meinard, 2007, XVI, 318 p. 136 illus., 39 in color., Hardcover. ISBN: 978-3-540-74047-6.
After reviewing I've ordered it, waiting for the stuff to arrive.

A general scenario that has attracted a lot of attention for multimedia information retrieval is based on the query-by-example paradigm: retrieve all documents from a database containing parts or aspects similar to a given data fragment. However, multimedia objects, even though they are similar from a structural or semantic viewpoint, often reveal significant spatial or temporal differences. This makes content-based multimedia retrieval a challenging research field with many unsolved problems.

Meinard Müller details concepts and algorithms for robust and efficient information retrieval by means of two different types of multimedia data: waveform-based music data and human motion data. In Part I, he discusses in depth several approaches in music information retrieval, in particular general strategies as well as efficient algorithms for music synchronization, audio matching, and audio structure analysis. He also shows how the analysis results can be used in an advanced audio player to facilitate additional retrieval and browsing functionality. In Part II, he introduces a general and unified framework for motion analysis, retrieval, and classification, highlighting the design of suitable features, the notion of similarity used to compare data streams, and data organization. The detailed chapters at the beginning of each part give consideration to the interdisciplinary character of this field, covering information science, digital signal processing, audio engineering, musicology, and computer graphics.

This first monograph specializing in music and motion retrieval appeals to a wide audience, from students at the graduate level and lecturers to scientists working in the above mentioned fields in academia or industry. Lecturers and students will benefit from the didactic style, and each unit is suitable for stand-alone use in specialized graduate courses. Researchers will be interested in the detailed description of original research results and their application in real-world browsing and retrieval scenarios.

Working on the Trajectory UI.

I've enhanced the Trajectory DTW UI over the last week following my initial hand drawing:



It seems to be working fine and next week I am planning to implement the actual DTW algorithm enhancements.

Technical review outline.

During the Summer and Fall of '08 I was doing research focusing on the "telemetry trajectory" idea which resulted in the three software components, which are "in the development stage" and will constitute the three major chapters of my future report:

1. 
   Software development activity simulation package. I've developed the sensorbase-sim extension package based on the JADE framework. It is fairly simple agent-based application which generates software metrics data once provided with simulation parameters for the code, such as overall functional points requirements, points per class, LOC's per point etc... and developers data, such as number of developers and their expertize level.
   
   While I've found a large amount of the approach-justifying literature and methods to continue the simulation package was shalved till better times and I focused on the Trajectory-UI development.
   


2. 
   Second application I was working on was a stand-alone Java application for the visualizing trajectories in the 3D space.
   
   This work was following Philip's original idea about trajectory visualization.
   This application is based on the Java3D package and it's main purpose is the exploration of the trajectory visualization approach. While working on the visualization implementation I was going through the trajectory-visualization related materials review and discovered the vast amount of research done in the area of the complex trajectories matching. Part of the reviewed articles will stuff the report.
   


3. 
   The most active development and research I am conducting right now now is on the Trajectory component of the Hackystat-ProjectBrowser application. Currently I am exploring the DTW algorithm application for the software telemetry data. Considering the amount of the work and research I've done this would be the major component of my report describing in the details the DTW application to the telemetry data.