We’ll have an individual check-in meeting with each of you to discuss your project ideas during class on April 11. (If you will not be able to make it to class on April 11, you should come to office hours or set up another meeting time with Shm or Dr. Sudhu, ideally before April 11.)
You should come prepared with a Project Proposal that covers the following:
What do you want to make, and why?
Expected Materials List
Projected Timeline
Simply and clearly address what "phases" or "steps" you expect to go through to complete the project, estimate how long you expect each step to take. Set milestones and pick an expected date of completion for each milestone-- when do you roughly hope to achieve each "phase" by? (Be realistic and authentic with yourself, your style of working, your life schedule, and how much work you can expect yourself to do in a given period of time!)
TIP: Remember - making early prototype versions of your piece, and iterating on them (gradually building up the complexity) is a requirement! What kinds of early prototypes do you expect you'll need to build first before getting closer to your final piece?
Are you working in a team? (max 4 students/team - our expectations will scale with team size)
If so, list the names of all teammates and your plans for a successful collaboration - how you plan to meet, communicate, and divide labor.
Goal / Vision for your final piece and presentation
Do you expect visitors to the Jacobs Design Showcase to interact with the final piece in a certain way? What do you hope viewers / participants will takeaway from the experience? AND/OR, what do YOU hope to takeaway from the experience?
Your final project can be anything you’d like to work on.
Your project should include things we’ve worked on in the class thus far AND can (should) include other elements that you pursue on your own (with our help, of course).
You’ll use Arduino and/or P5.js and the sensors and actuators we’ve introduced in lectures thus far.
If you want to use another tech ‘stack’ please discuss with us first.
Plan for a 2 week project, leaving extra time for debugging and polish!
Your project should be awesome to you! It should involve something that you are passionate about and want to pursue. (And if you achieve this, it will end up being awesome to the rest of us, too, I promise.)
It could be...
A unique music interface
An interactive art installation
An innovative approach to an engineering tool
A cool device to improve quality of life
An automated art making device or process
Tell us a story, give us a narrative, make us laugh or get angry or start a discussion or learn, experience, or feel something new.
Elements that are not the focus of your project (eg. electronics) should be enclosed in some way, or otherwise designed for the protection and robustness of the electronics and for clean visual aesthetics.
Your project should work reliably! No code bugs, no loose wiring, no failing glue joints or tape connections, etc. You should be able to transport your piece and operate it at the showcase with success.
Think about how to present your project in our classroom space. What would be the ideal setup to achieve maximal audience engagement?
So far we’ve worked with these components…
Sensors:
LDR (light dependent resistor)
switch (button)
PIR sensor (passive infrared)
Computer/Laptop inputs with p5.js (ex: microphone, mouse, keyboard)
Actuators (output devices):
Neopixels (we haven’t dealt with these specifically in class, but you should get the principle (aka RGB LED))
DC Motor (and L298 driver)
Solenoid (and MOS Module)
Computer/Laptop outputs (screen, speakers)
more sensors here: https://www.adafruit.com/category/35
Neopixels here: https://www.adafruit.com/category/168
Robotics (aka make stuff move) here: https://www.adafruit.com/category/227
Inspirational links here: https://github.com/loopstick/ResourcesForClasses/blob/master/InspirationalLinks.md
CODE: Upload your .ino code file to your student Google Drive folder, or use a public GitHub repository.
Nicely Documented Code Tips:
add // comments
give clear and intentional names to your variables, functions, file, etc.,
strive for clear and consistent indentation and spacing
Are you able to tell what each section of your code does, if asked? Will future you be able to tell what this code does if you open the file back up again in 5 years?
REPORT: Copy the Documentation Template to your Google Drive folder
(or make your own from scratch)
Fill with your images, video, text, and links! Don’t forget to link your code and add process pics!
POST: Click the pencil icon in the bottom right ↘ to edit the project page.
Copy the example post below.
Replace the images/video with at least 1 "hero" image and/or video of your own.
Make sure that we will have access to your assets. (Use your Google Drive folder!)
Replace the text and links with your links. Test them! (People often forget to actually change the links...)
If you’re having trouble just let shm know. they are so happy to help!! ;)
Title: my cool example project title
Documentation Link (click for a template you can copy to your google drive folder)
Code Link (github repo, or a link to your code file in your google drive folder.)
Final Video (put it in your google drive folder, or upload to YouTube - just make sure we have access.)
IMG_0398.MOV
286170A5-7FE3-4931-B9C0-EA3EB0F73D39IMG_9016.mp4Own a Snoopy Demo.mp4
Title: Own a Snoopy
IMG_0663.MOVTitle: Rage Relief
please see code links on documenation
IMG_1299.MOVIMG_1245.MOV
desinv-demp.movTitle: SELFI3-D: Perceptions of tattoos in public
Title: FPV Drone & Transmitter
Title: Boogie Ball
IMG_6558.mov
IMG_2796.movTitle: Rise and Pose
Mosaic Photo Booth.mp4
Title: Mosaic Photo Booth
