Final Project Proposal – Sarika Bajaj

For my final project, I will be making a “mechanical worm” in a cage that responds when someone taps the glass case around it.

My original idea was to make a geometric wood lamp shade that had the ability to “open up” or “collapse” that could be controlled using muscle wire or a motor. However, I wanted something with a bit of a better interaction, so the muscle wire and wood actuation will actually be quite similar still, just packaged in a different story.

I’m thinking for my form, the worm will be placed in a little enclosure as below that will either be filled with a mix of natural and plastic items to create this sense of a mechanical/artificial world.


Wood needed to make the worm
Some type of motor/muscle wire to actuate the worm
Arduino and external power supply
Some type of hand sensing (IR camera?)


Some software needed to use the body sensing hardware (perhaps, Max that sends signals over OSC to the Arduino)

Order of construction and testing:

  1. create the mechanical system of the worm
  2. actuate the lamp using dc motors or muscle wire for simple movement
  3. set up the “tap” sensing feature
  4. have the worm set up in the cage and create different interactions per type of tap, plus what the worm will be doing in its “normal state”
  5. have the worm tested in an environment with lots of people and see how it works
  6. work out any issues
  7. clean up the final form of the worm and tank

Assignment 6: Final Proposal


Abstract / concept statement

I want to play with the idea of IoT gone wrong – what happens when we make our objects smarter? What if we develop artificial intelligence in our device to the point where our device try to reason about how best to function? As human beings, do we imbue what we create with our flaws?

To do this, I want to create an installation with a couple objects exhibiting this idea.

I’m unsure which ideas to use, but here’s a list of things I might do:

  1. A table or chair that slopes off when you try to use it (made on a micro scale)
  2. A mouse or glass of water that actively hides and avoids being used
  3. A toaster that launches toast far too high
  4. A roomba/roomba-like device that tries to vaccum up things you’re currently using
  5. A fork that swivels out of the way of food when you try to use it to grab something
  6. A cup that tips over once it’s semi-filled
  7. A blanket that shivers or refuses to come off of you
  8. Lights that get sleepy over time, dimming or slacking until they’re shaken awake
  9. A tie that moves on its own, anxiously


It depends on what I decide to pick for this project, I might be interested in the super-toaster, but I’m not sure how to implement it. I’ve been considering using a fly-wheel to launch the toast, but unfortunately this might mean I’m unable to toast any bread I put in.

For the mouse that avoids you, I would just a couple distance sensors, and I could move the tail back and forth like a real tail for the mouse.

The table might use some kind of servo or linear actuator to move the legs up and down, and some kind of force sensor to know when you are putting stuff on it.



Idea dependent

Order of construction and testing


  1. Decide on what projects I’ll do, and then buy supplies
  2. reverse engineer any devices I need, and start building prototype
  3. Ask for help with mechanical issues with prototypes
  4. develop working prototype
  5. Work on aesthetic polishing

Assignment 6: Final Project Proposal

Assignment:  written proposal for a final project

Our final project will show that you’ve learned not only the basics of physical computing but that you can create an interactive art project showing off those abilities.


It should fit on half of the tables we use in A10.  If you can make a case for doing a bigger project, we will try and make space.  If you are doing a wearable project we’ll need to figure out how people can try it on or if you’ll just demonstrate it while wearing it.

Sound and light levels

Try to keep these low enough to not interfere with conversations or other projects.  By the time of the show on Friday we will know enough that we can assign people to tables in a way that minimizes interference.

Project fundamentals

  • physical computing, including inputs, outputs, and state machines
  • form: how it looks and sounds is as important as how it works
  • content:  why does your project exist?  who is it for?  what can it do?

If you have any questions I have office hours from 1-4 on Friday.  Jake and Sydney will post their hours in the next few days.


Week 11
Tue, 7 Nov: proposal review, lecture on multiplexers and library 101
Thu, 9 Nov: work day

Week 12
drop pass/fail
Tue, 14 Nov: lecture on problems discovered in week 11, work day
Thu, 16 Nov: work day

Week 13
Tue, 21, Nov: Rough draft/prototype crit, graded
Thu, 23 Nov:  TURKEY DAY

Week 14
Tue, 28 Nov: work day
Thu, 30 Nov: work day

Week 15
Tue, 5 Dec: work day
Thu, 7 Dec: Projects DUE, grades will be based on this crit.
Fri, 8 Dec:  Final show in Studio for Creative Inquiry, set up at noon, show starts at 1pm

Background research

  • required reading: Tom Igoe’s post on physical computing projects.  What Tom wrote a decade ago is still true today.
  • NYU’s ITP shows are the inspiration for our final show in SCI.  Remember this is work by graduate students, many of them could teach Phys Comp.  What I like is the variety, the density, and how enthused they are about their work.
  • why form matters — anyone in class could make this project using supplies in A10.  What’s unique is that it’s made as a concept of a toy and has the correct visual and interaction languages of a toy
  • look at another class’s projects for inspiration, not for performance quality
  • obligatory Lady Gaga reference for the relationship between form related to content

Proposal Content

An outline for the proposal, add to it as much as you like.  My examples are terse and don’t have any drawings or images, feel free to take a paragraph or two for each element of the outline.  If you can’t draw, then use CAD or find images on the Interwebz to illustrate your ideas.

This isn’t about the details of how your project will be implemented, but the concept of what you want it to do and a rough plan for how you’ll work the next few weeks.

Abstract / concept statement

In a paragraph, describe the fundamentals of your entire project.

Example:  An electronic piano with that teaches you to play songs on the piano using LEDs, piano keys, and speakers.  The LEDs are assigned to keys, when an LED lights up you press the key and hear the correct note.  It will have two octaves so it needs 24 keys and 24 LEDs.  Maybe it can keep score and grade how well you perform.


The rough list of things you’ll need to do this project.  “I don’t know” is an ok answer for some components.

Example:  Piano keys x 24, LEDs x 24, at least one speaker, something to hold all the components together that looks like a piano.


What software will you need?  Again, a high level description is fine, so is “I don’t know” for some of the elements.

Example:  I’ll need software that can read a music score, display the score as LEDs over the piano keys, read the piano keys, then make sound on the speakers.  I need to be able to change the music score and keep track of someone’s performance ability.

Order of construction and testing

This is a critical part of your proposal.  Stop and ask yourself: “In what order will I build things over the next few weeks?”  You can’t do the entire project at once — divide it in to discrete parts that you know you can complete and test.


  1. make a single piano key, LED, and speaker work
  2. make three LEDs and piano keys function with three speakers
  3. figure out how to drive 24 LEDs and read 24 switches (ask jet or Sydney or Jake)
  4. design the enclosure that will hold all the keys and LEDs
  5. find out how many keys and LEDs I can drive with a single Arduino; if it’s only 12, then I’ll just do one octave
  6. make the enclosure based on how many keys I want to use
  7. show it to someone who isn’t in phys comp and ask them to try it out
  8. fix all the things that didn’t work
  9. repeat 7 and 8 with a few other people
  10. make an information poster for the final show
  11. write up my artist’s statement for the final show