Wiimote / Kinect Lab Design. Senior Design December 2011, Group 16 Adviser: Dr. Tom Daniels Brenton Hankins Rick Hanton Harsh Goel Jeff Kramer. Outline. Problem/Solution Requirements Risks, Costs, and Schedule Wii Hardware WiiWrap and Software Kinect Hardware Software
Senior Design December 2011, Group 16
Adviser: Dr. Tom Daniels
The Wii Wrap software used by freshmen Computer Engineering students is simple but needs improvement for installation and use by novice users such as a high school science teachers. In addition, similar software should be developed that uses the Microsoft Kinect sensor as input to student-written programs.
Risk 1: Temporarily lose a developer from our team for unforeseen reasons.
Mitigation 1: The team will do our best to continue work without the developer while they are gone and rely on a detailed documentation trail. We will use technologies like Skype and email to keep in touch with the developer during their absence.
Risk 2: Unable to keep tasks fully on schedule due to other projects and schoolwork.
Mitigation 2: Set up minor deadlines to make progress on larger tasks.
Risk 3: Important equipment becomes lost or nonfunctional (Wiimote, Kinects)
Mitigation 3: Jeff has several personal Wiimotes available to him for use and there are one or two extra department-owned Kinects Dr. Daniels has for use.
Risk 4: No individuals on the project team have experience programming with graphics APIs.
Mitigation 4: We have built periods of time into our schedule for us to work on developing the necessary experience with OpenGL and SDL environments to allow us to design and develop software for the Kinect efficiently.
Wii Wrap installer
Con: Slow, lots of text processing and possibly storage
What we need
Colored image to visualize depth
API for the Student
Called when new frame data is available
* -> function pointers
Called to update the screen after processing
Acquire Moving Average of Frames
Apply User-Defined Process* Function
Apply User-Defined Update* Function
Apply Changes to Output Screen