Art B2011 Syllabus

Medium Workshop: Physical Computing

home| Course Schedule | Labs | Announcements | CCNY Academic Calendar | [DIAP]

Class Blog: Announcments

Nov 11 2014 - Setting up Git & Github

Git is a version control system that will allow you track changes on a file that you have stored on your computer. It monitors files/folders that you specify and records any changes made to them, allowing you to store different versions of the same file.

Github is a social media platform where people can upload, share, edit, and collaborate on code and projects.

Git and Github are not the same thing.

Intallation Instructions:
  1. Create an account on Github
  2. Install Git onto your computer
  3. Configure:
    1. Open Terminal
    2. Type: git config -- global user.name “ YOUR NAME HERE ” , hit enter.
    3. Type: git config -- global user.email “ YOUR EMAIL HERE ” , hit enter.
  4. Create a Repository
    1. In terminal, navigate to the folder you want to track changes / create a repo in.
    2. Type: git init This will initialize and empty repository in that folder
    3. Go to Github.com, create a repository (choose name SAME as repo, make public, do not initialize with a README)
    4. Link Github to your computer: on the next screen, copy the git command: git remote add origin https://github.com/username/newRepo.git from the Github page into terminal, hit enter. Git and Github should now be linked
  5. Add a file to the Repo (to be tracked for changes)
    1. Navigate to the respository (if not already there), type: git add -A . This will add all the files in that folder. If you haven't created any files, nothign will be added
    2. Make changes to your document, navigate to the respository (if not already there), type: git commit -m “ something descriptive of the change you made”
    3. Type in terminal: git push origin master. This will push your changes to your master branch and you should be able to see the updates on Github.

As you are working you can repeat steps 5.1 - 5.3 to keep updating changes. Push a new version after every significant alteration to your code..especially code that works! You will only need to do steps 3.1 - 3.3 once, ever.

There are many many more terminal and git commands. You can Google a cheatsheet easily, or make your own.

Nov 4 2014 - Final Project Proposals

You are at liberty to create any interactive project for the final, the only requirements are that the project include either microcontrollers or circuitry or both. The project should be interactive, ie a 'conversation' between actors -- input/process/repeat. Prior to starting the project, please create a blog post with a project proposal outlining the following:

  1. Project Title
  2. Elevator Pitch (1-2 sentences concisely describing the project)
  3. Project Description (1-2 paragraphs flushing out the project)
  4. Project Context (1-2 Paragraphs - Why do this How does this relate to your work and the work being done today or in the past?)
  5. Concept Sketch / Project 'logo'
  6. Timeline (divide the time remaining into research/material gathering/production/user testing/second itertion)

Feel free to include as much information as needed to express your ideas. Also feel free to talk about previous work and how this project may or may not fit into your body of work. Please post to your blogs by Monday Nov 10th so that I have a chance to read them prior to class.

Class 1 - Sept 2nd

Thanks everyone for a great first class! Here's some links to recommended purchases. If budgeting is tight, focus on the multimeter and pairing up with a partner for any other lacking materials. We have enough materials in the lab for now. If there is some flexibility financially, then put together your own little toolkit. It will be essential for prototyping and fabricating in the future.

Also, don't be afraid to take things apart! start collecting buttons from broken VCRs, motors from old printers, potentiometers from stereos, etc.

**don't forget to put your email and link to your blog in the form!!!