Skip to content

Homework Luisa

Jump to bottom Edit New page
Luisa Pereira edited this page Dec 5, 2021 · 9 revisions

Contents

Guidelines

A big part of learning at ITP is learning from each other. So share your work and in exchange you'll get to see everyone else's!

  1. Practice by completing the weekly worksheet.
  2. Do the assignment.
  3. Contribute a question.
  4. Post blog documentation: Ideally something visual, some written thoughts, and code. If you are struggling with your sketch and can't get things to work, put your energy into writing about what didn't work and what you did to try to solve it.

How to Submit

Assignments are due the day before class each week. I want you to succeed. The material can sometimes be challenging. I'd still prefer that you turn in work that is tentative, unambitious or incomplete, rather than turn in work late.

Weekly Worksheet

There are worksheets (linked below) to practice the concepts introduced in this course. You are expected to add links to your p5 sketches directly in these documents. Log in to your NYU account to access them.

Weekly Blog Post

To submit all other assignments (i.e. your blog posts or other documentation), use this homework form.

Here is the spreadsheet with everyone's responses.

Support

If you find yourself struggling, there are many forms of support at ITP:

  • Look out for the residents' office hours and help sessions.
  • Visit The Coding Lab, a walk-up (and virtual) help desk for NYU students to get help with their code from ITP student mentors.
  • Post a question in the ITP/IMA Discord HELP-ITP #icm channel. Think of Discord as chat. It’s a platform designed for synchronous connections and community messaging. If you need a question answered in real-time, consider posting here to chat with another student or resident who is currently online.
  • Need help asking a question?

Class Notes and Assignments

I will post all in-class examples, references and notes on this shared document.

Week 8. Pixels I.

Week 9. Pixels II

  • RESOURCES:

  • DO:

    • Work in pairs. Due next week. Build a mirror to create a 1-minute self-portrait. The mirror should change over the course of the minute.
    • Demo your experience in class:
      • Use the p5 editor's present link to show your project fullscreen
      • Use createCanvas(windowWidth, windowHeight);
      • Position and size screen elements in relation to the canvas width and height.
      • If your image is not big enough to fill the entire screen, be mindful about the color you select for the canvas.
      • How to do a screen record: Mac | Windows
    • Create a blog post documenting your work. Address / include the following:
      • 5-10 words that describe the self-portrait you've created and how it changes over time.
      • Links to other projects that serve as references, inspiration, or deal with similar ideas as your piece.
    • Consult resources from syllabus for inspiration. Pixels Week 1 | Pixels Week 2

  • READ AND WATCH:

Week 10. Sound I

Week 11. Sound II

  • RESOURCES:

  • DO:

    • Work in pairs. Due next week. Create a 30-60s sound composition. Your main focus should be the sound, not the visuals.
      • Prepare 5-10 words to describe the piece. Listen to what you've made. Adjust your words.
      • Create a blog post documenting your work. Also include links to other projects that serve as references, inspiration, or deal with similar ideas as your piece.
    • Random Ideas
      • Record bits of spoken word and loop them to create music. See SoundRecorder() Looper
      • Use sound samples and manipulate their playback rate() to control pitch instead of the oscillator.
      • Try implementing a different scale with different pitch ratios: More about scales.
      • Play with Timbre and make use of p5 Sound's post-processing features: Delay, Filter, Reverb, Convolver etc.

  • READ AND WATCH:

Week 12. Text

Week 13: Data

  • RESOURCES:

  • DO:

    • Your final presentation! You can take something you did earlier this semester and expand it. You can scratch a new itch. You can make a Frankenstein project by combining earlier code. Remember it is still a 1-week assignment.
    • Prepare a 5-10 minute presentation to demonstrate what your project does that emphasizes its computational aspects.
      • Break down 1 algorithm in your code for us. Explain how it works. (It can be 1 line of code.)
      • Big Question to Think About: How did "coding" this project help you understand what you were doing in a different way?
      • You don't have to explain the whole thing. Pick one algorithm you wrote and deconstruct it for us.
      • If your project is interactive, please be prepared to have someone else in the class interact with it to demo what it does.
      • If your project can only be demo'd outside of class, please show a short video (< 2 minutes) of the experience.
      • If your project was a collaboration, explain what you did.
    • Post documentation in the form of a blog post. Ideally something visual, some written thoughts, and code. How do you feel about WHY you want to use code in your work now compared with the beginning of the semester? If you are struggling with your sketch and can't get things to work, you should feel free to put your energy into writing about what didn't work (and vent any frustrations!). If it is a collaboration, please describe your contribution to the project.
Add a custom footer
Add a custom sidebar
Clone this wiki locally