Summer of Code 2013

The rough plan is as follows, in the order of execution as I currently see it. I’ll update and add dates as I get a better sense. And yes, that looks like a lot to do:

  • Rough out DirectX-based audio proof-of-concept
  • Branch off new version of FLTK app and develop OpenAL library that allows for the replacement of the synthesizers
  • Write a testbed app that supports experiments such as the situational awareness project
  • Pull synthesizer control from Arduino code (also a new branch)
  • Integrate Phantom with FLTK app
  • Figure out some reasonable tests to show off the material-sensing  and gripping capabilities of the interface and implement the testing scenario
    • I think a good enough test might be to have subjects “pick up” objects that have different characteristics (fragile, slippery, etc) and have the output of the actuators reflect that surface. If this can reasonably be compared with a real hand, then a within-subject test could be performed, which would be easier logistically
    • Some relevant papers (I have the papers in Google Drive, but they should show up in a search on Scholar):
      • Initial studies in human-robot-human interaction: Fitts’ law for two people
      • Audio-Visual Communication in a Two Person Gross Manipulation Task
      • Formal Comparison of a Cube and a Handle Shaped Physical Prop for 6 DOF Manipulations in Tangible Augmented Reality Environment
    • Update the
  • Develop influence system simulator (based on this)
    • Maybe in JavaScript. It’s time to learn it, and also possibly WebGL.
    • If done as a web app ensure that it is possible for people not only to re-run the experiment but also to run variations as well. Maybe something like a browser-based RePast
    • Run a set of expiriments that allow for comparing the canonical qualitative information gathering strategies and retermine some kind of quantifiable ROI (effort vs. results) for each
    • Write up and submit paper
  • Run interviews (3?) on female users for the ubiquitous computer adoption paper
    •  Code and evaluate if there are any differences from the fall paper
    • Incorporate changes and submit paper
  • iRevolution. Mostly collect information and lay out groundwork

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.