Some more changes

1. I changed the sampling rate of the frame-by-frame view so that the intervals now depend on how long the motion is.

Here's a walk motion that has 500+ frames:

And here's a walk motion that has 200-300 frames:

2. I changed elements of the interface so now it explicitly says how many frames are contained within a motion, and I also commented out the "Additional Views" link for now.

3. Here's the final presentation video + voiceover (as it sounded during the actual presentation, but this time the graphics will NOT be blown out by the projector).



4. And here's the final report (contains details), if you want to read it: Final Report

Joint color changes

I implemented a new visualization where the joint colors change based on acceleration. Red means the joint is speeding up, and blue means the joint is slowing down.  There are 3 versions below:

This one displays the bones changing color:

This one displays the joints changing color:

And this one displays the joints changing color and the bones changing color based on the average color of the joint + its parent:

(keep in mind that the skeletons are displayed every 25 frames right now...)

For the final demo

For the final demo, I generated a page of results in the same Processing sketch. Granted, they don't have the results page UI around it, so what I just did for now (while waiting for Processing JS to implement 3D) was inserting .gifs of the skeletons + bird's eye view manually into the pages.

Walk Results Page
Jump Results Page
Random Results Page

Each page has 8 results displayed. The skeletons look quite small now (they unfortunately got so blown out by the projector for the final demo that you couldn't see any of them), but hopefully I'll finish the implementation where the joints change color based on changes in acceleration. Also, it would be nice to have some indication of how long the motion is, because I'm sure information would be useful.

For the bird's eye view, there are two small indicators (one green and one red) to indicate where the motion starts and finishes. For some of the motions where the subject stays mostly in the same place, you can't really see the green/red lines nor the yellow dot because the information gets drawn on top of each other and the space the subject occupies within the capture space is small. For the case where the subject stays in one place, I thought about enlarging the "dot" that results, but then you wouldn't be able to distinguish that from a subject performing a motion where it occupies a circle of space.

In order to deploy my code, ideally I'd like to wait for Processing JS to finish its implementation of 3D. That way, there can be multiple HTML5 canvases on the same page that load pretty quickly, instead of embedding Java plugins, which is what you have to do with current Processing sketches. Processing JS just makes executing Processing code in the browser a lot easier/faster, because it runs on HTML5 and webGL.