Presentation Practice

All our visual team members met at 3.00pm today in colloquium room. We gave two demo presentations and made some comments to the presentation. We edited our slides and looked at the timing of the presentations.

We are hopeful about giving a good presentation on Wednesday.

Preparation for Presentation

We all met last Friday and talked almost an hour and half regarding our team's presentation. We figured out what we are going to talk about.

We decided that we all should talk. And we would focus on the following points.

*Goal

*Problem Space

*Solution

*Open Problems

Final Turn-in

Peter just joined. And we cleaned the project and then Peter turned in.

Note: In the tech doc we also added open problems and future scopes for future developers.

We are happy what we turned in. Hope this would help to analyze a video for research work.

Thanks

Final Doc Revision

Me and Fan did the User and Tech revision from 9.00am this morning until 11.30am. We changed some part the docs to make more sense. We went line by line to check thoroughly. But still there might be some problems.

Revised the ReadMe file.

It was little cumbersome and take time.

GUI / Docs revision and Test Build

We worked from 4.00pm to 9.00pm for bug fixes and polishing. Me and Kyle did the GUI revision. The Docs and tutorials now open on browser. We were having issues like in Mac Docs were not opening in browsers. We fixed those now all those docs and tutorials open in Mac and widows. We have a video tutorial that use flash. One has to have flash player installed to view the tutorial.

Later Me and Fan also did the Docs revision.

I did some test build and tested with Mac and Windows. Works in both OS.

Cnetroids for frames with no fingers

Kyle was proposing putting (0,0) for frames with no fingers within the frame.
But still (0,0) is inside the image grid. Perhaps (-1,-1) something for sure outside the grid.
And we finally ended up putting (-1,-1) for centroids that were not found in the frame.

Frame Rate and Need to be in XML file ?

Well I think we do not need 30fps or even 20 fps rather 10 fps should be enough as finger does not moves as fast as eyes. Even eyes should be OK with 10 fps to track changes. I think higher fps would slow down the tracking. Using 30 fps is something like we have unnecessary points to draw a straight line which can be actually drawn with 2 points. Don’t prove our program is a slower one. :)

Actually I think we do not need more than 10 fps and can make it as our suggested standard.
If someone want to use our program then they can convert video to whatever fps they use.

Again the problem comes like we are making our program fixed with 30fps. In case some one try testing a video of 60fps or 15 fps still our xml file should have time = 1/30 * frameNo not 1/15 or 1/60 .

So is there any way picking up fps from video that someone feed to our program ?

If no then … use a standard small fps which is sufficient to analyze data without loosing data and do not take much time to track with our program.

......

Fan was wondering whether we need to put frame rates in XML file ?

My Ans is:

We do not need to store frame rate. If we can pick it up from whatever video we open to process then
Calculate time t = (1/frame_rate) * frameNo and put in your XML file.

By this way XML file should have accurate time for a video with whatever fps it has.