Tom's Main Menu

Physical Computing Home

Intro to Physical Computing Syllabus

Networked Objects

Sustainable Practices

blog

Resources

code, circuits, & construction

my del.icio.us links

 

Introduction to Physical Computing

Fall 2004


 
Project 1: Observation of a Location

You're not actually going to implement the first project; you have free reign to propose anything you want. However, you will be building a physical model of the device you're proposing, or creating a rendering/animation/video if your proposal is not a physical device. You will also be expected to prove that any technology you propose exists, either by citing other working examples, or by describing in depth how the technology would be developed.

Week 1: Observe the location and activities

Choose a space in which there is a reasonable amount of activity. Why do people use the space, and what do they use it for? Observe the activities that happens there. Use pictures, videos, sound recordings, drawings, and any other form you need to in order to describe space and the activity. Ask people in the space about what they do there, what they like about the space, what they dislike, how well the space works for their purposes. Look for patterns in the activity. Identify how the space and the activity are linked. Decide how you can sense the action and create a reactive or interactive system to enhance or change the activity.

Week 2: Propose a prototype

Imagine a system to realize the change or enhancement you came up with. Find ways to use the space as it exists, rather than modifying it, unless it's absolutely necessary. Your goal should be to make a system that is as dependent on the location it's in, and uses it as well as, the activities you've observed.

As a passive example, you could sense how many people use each entrance to a given subway station, and how frequently. As a more active example, you might want to give people a surprise in their daily transit through a public square or lobby. In order to surprise them, first you'd have to observe and collect data on what the normal pattern of activity is, then make an output system that changes that pattern. Perhaps you want to make a sculpture that changes the patterns of pigeons in a public square (a la Ed Bringas). Or perhaps you just want to sense how long people use the bathroom, and tell them when they've been in there too long.

The activity sensed and the viewer observing the results can be two different people, species, etc. In other words, you don't have to close the interactive loop between the actor you're sensing and the viewer to whom you're presenting the results.

Project 2: Device, Instrument, Tool

Week 1: Observations

Choose an action that produces changes in a medium. It might be strumming a guitar (the medium is sound), hammering a nail (the media are wood, nails, and sound), flying a model plane (the media are the plane and the air). What tool or device is the action taken on? What is the goal of the activity? Observe a person or people engaged in the activity. What are the physical parameters of that activity? What does the person engaged in it do with their arms, their legs, their hands or feet, their head? How do they change their posture? Where do they need to focus their attention? Is there a secondary focus of attention (for example, if two limbs are used independently)? What physical elements of the activity make it engaging? What elements make it difficult, painful, or boring?

Do the action multiple times (perhaps 100 times), or have someone else do it. Record the action, with a video camera, or sensors feeding a graphing program, or in some other way. What patterns appear when the action is repeated?

What are the physical characteristics of the medium that you have to take as given? What physical input to the tool or device suggest or mirror those characteristics? For example, how actions you take on an audio mixer mirror the inherent characteristics of sound? How does the arrangement of controls on a VCR suggest what each control does?

Week 2: early prototype

Now that you've observed one tool or device that manipulates the medium you observed, create another one. Either modify an existing device so that it affords changes to the medium that it didn't previously, or make a whole new tool to manipulate the medium in new ways.

Ask yourself (and your intended users) why someone should use your device to do the job. Don't assume that someone will want to use it, or even know how to use it. Make the functions apparent, and figure out what will make a person want to use your device. How will it make their experience of the activity better?

Is your device dependent on other devices, or on a specific location, or on the arrangement of elements in a space? Where is is best used? What social situations (i.e in private, in front of an audience, in a crowd) are best for its use? How will you ensure that those conditions are met?

Week 3: Advanced prototype

Get other people to use your device, instrument or tool. Try as much as possible to tell them only what they need to get started. For example, if you made a musical instrument, just tell them how to produce changing tones; don't tell them what to play. If you made a device that writes text in response to eye movements, don't tell them what to write, just tell them how to make letters. Observe how your users use your device. Take notes on where they defy your assumptions as to how the tool is to be used. Ask them how they think the device works (their mental model of the action). Listen to what they have to say, and figure out where their mental model diverges from your model of how it works. Use this information to make the tool better.

Week 4: Final prototype

Based on all the information you've gathered, iron out any bugs, make any necessary interface revisions, and complete your device, instrument, or tool. Finalize the documentation of the process.

Project 3: Do it Again

Pick one of the earlier projects, either your own or someone else's (ask permission first, and credit them) and re-do it. Take the observations made in week one as a beginning, and re-state your assumptions and goals. Then use the same process of observation, prototyping, testing, and revision to improve upon the original project.