Intro to Physical Computing Syllabus

Research & Learning

Other Class pages

Shop Admin

ITP Help Pages
Tom's pcomp site
DanO's pcomp site


Dustyn Roberts

Fall10.DustynRoberts History

Hide minor edits - Show changes to markup

December 06, 2010, at 08:55 PM by sa1772 -
Changed lines 112-114 from:

Myers-Briggs Personality test link

to:

Myers-Briggs Personality test link

<object width="512" height="400"><param name="movie" value="http://news.bbc.co.uk/player/emp/external/player.swf"></param><param name="allowFullScreen"

November 16, 2010, at 09:11 AM by dpr2 -
Added lines 110-112:

Week 11

Myers-Briggs Personality test link

November 09, 2010, at 09:13 AM by dpr2 -
Changed lines 104-105 from:
  • Wiring a stepper with an H-bridge
to:
  • Notes and wiring a stepper with an H-bridge
    • Arduino stepper library and schematics
November 09, 2010, at 12:09 AM by dpr2 -
Changed lines 105-106 from:
  • Wiring a stepper with Sparkfun's EasyDriver (starts on pg 51 of motor chapter]]
to:
  • Wiring a stepper with Sparkfun's EasyDriver (starts on pg 51 of motor chapter)
November 09, 2010, at 12:00 AM by dpr2 -
Changed lines 99-100 from:

Motors - family tree

to:

Motors - review family tree, pg 6 Finish h-bridge lab

Steppers

  • Wikipedia animation
  • Wiring a stepper with an H-bridge
  • Wiring a stepper with Sparkfun's EasyDriver (starts on pg 51 of motor chapter]]
November 08, 2010, at 11:19 PM by dpr2 -
Changed lines 95-102 from:

Now, off to the lab!

to:

Week 10

Final project matchup

Motors - family tree

Wireless communication and Bluetooth

October 18, 2010, at 11:36 PM by dpr2 -
Added line 95:

Now, off to the lab!

October 18, 2010, at 11:25 PM by dpr2 -
Changed line 91 from:

On Arduino's [http://arduino.cc/en/Serial/Println | serial monitor], by default, it interprets bytes as ASCII-encoded decimals. So the following lines will print out the same thing:\\

to:

On Arduino's serial monitor, by default, it interprets bytes as ASCII-encoded decimals. So the following lines will print out the same thing:\\

October 18, 2010, at 11:24 PM by dpr2 -
Changed line 87 from:

Mac & PC: Serial Monitor in Arduino, Processing graphing sketch, [http://freeware.the-meiers.org/ | Coolterm]\\

to:

Mac & PC: Serial Monitor in Arduino, Processing graphing sketch, Coolterm\\

Changed lines 89-90 from:

Mac: Zterm, [http://www.tigoe.net/pcomp/code/category/OSX/84 | Terminal], [http://tomgerhardt.com/Cornflake/ | Cornflake]

to:

Mac: Zterm, Terminal, Cornflake

October 18, 2010, at 11:24 PM by dpr2 -
Added line 30:
Changed line 34 from:

This is the magic number for the full range of analog input we saw with the pot. This is NOT necessary to know, but since I'm an enginerd, I'll explain for those of you who are interested:

to:

This is the magic number for the full range of analog input we saw with the pot. This is NOT necessary to remember, but since I'm an enginerd, I'll explain for those of you who are interested:

Changed lines 73-74 from:

Every group of 8 bits (1 byte) is interpreted at one time. If all you're doing is sending a potentiometer value divided by 4 (for example), you're only ever sending a number from 0-255 so you don't have to do anything. This is sometimes called the raw value. But if you want to send bigger numbers, or text a human can actually read, you have to format the byte that's being communicated from the speaker to the listener to know what the F you're talking about.

to:

Every group of 8 bits (1 byte) is interpreted at one time in serial communication. If all you're doing is sending a potentiometer value divided by 4 (for example), you're only ever sending a number from 0-255 so you don't have to do anything. This is sometimes called the raw value. But if you want to send bigger numbers, or text a human can actually read, you have to format the byte that's being communicated from the speaker to the listener to know what the F you're talking about.

Changed lines 82-94 from:

One last thing about ASCII: the first 32 raw values correspond with control characters, that won't even show up as garbage but stand for things like "carriage return" (ASCII 13).

to:

One more note about ASCII: the first 32 raw values correspond with control characters, that won't even show up as garbage but stand for things like "carriage return" (ASCII 13).

This serial data is passed byte by byte from one device to another. If you're constantly sending values between 0-255 like with a potentiometer, you don't particularly care how the message starts or stops because it's a constant flow of numbers. But if you want to send a more specific message, or more than one message, the speaker has to give the listener clues as to when the messages start and stop and how to tell the difference between them.

Ways to see/visualize serial data:
Mac & PC: Serial Monitor in Arduino, Processing graphing sketch, [http://freeware.the-meiers.org/ | Coolterm]
PC: Hyperterminal
Mac: Zterm, [http://www.tigoe.net/pcomp/code/category/OSX/84 | Terminal], [http://tomgerhardt.com/Cornflake/ | Cornflake]
On Arduino's [http://arduino.cc/en/Serial/Println | serial monitor], by default, it interprets bytes as ASCII-encoded decimals. So the following lines will print out the same thing:
Serial.println(analogValue); // print as an ASCII-encoded decimal
Serial.println(analogValue, DEC); // print as an ASCII-encoded decimal

October 18, 2010, at 10:51 PM by dpr2 -
Changed lines 27-29 from:

Can you find out what code is already on an Arduino?

No, you can't get it back, because it's compiled. The source code isn't stored on the chip.. There isn't an easy way to extract the assembly code either (though it can be done, but the explanation is beyond the scope of this class)

to:

Can you find out what code is already on an Arduino?
A: No, you can't get it back, because it's compiled. The source code isn't stored on the chip.. There isn't an easy way to extract the assembly code either (though it can be done, but the explanation is beyond the scope of this class)

October 18, 2010, at 10:50 PM by dpr2 -
Changed line 27 from:

Can you find out what code is already on an Arduino?\\

to:

Can you find out what code is already on an Arduino?

October 18, 2010, at 10:50 PM by dpr2 -
Changed lines 24-26 from:
  • What is Physical Computing?
    • SixthSense Technology
to:

What is Physical Computing? SixthSense Technology

October 18, 2010, at 10:50 PM by dpr2 -
Changed lines 23-25 from:
to:
  • What is Physical Computing?
    • SixthSense Technology
October 18, 2010, at 10:48 PM by dpr2 -
Changed lines 24-26 from:
to:

Can you find out what code is already on an Arduino?
A: No, you can't get it back, because it's compiled. The source code isn't stored on the chip.. There isn't an easy way to extract the assembly code either (though it can be done, but the explanation is beyond the scope of this class)

http://www.bareconductive.com/home.html (A video of conductive ink, invented by Royal College of Art students)

Why 1024?
This is the magic number for the full range of analog input we saw with the pot. This is NOT necessary to know, but since I'm an enginerd, I'll explain for those of you who are interested: The analog-digital converter (ADC) pins on your Arduino are capable of sensing a varying voltage (from your potentiometer, fsr, etc) and outputting a 10 bit number. A bit is a 1 or 0, a byte is 8 bits. Each bit represents "2 to the power of (bit)", called the binary system. So 1000000000 = 2^10 = 1024. Read more on counting in binary in this wikipedia article:
http://en.wikipedia.org/wiki/Binary_numeral_system
A byte is actually one of the data types we can use with Arduino (but very seldom do). A byte is not big enough to hold the output of the ADC (Analog) pins, so we move up to an int (integer) when we declare things like int potValue = 0. That way we can store the whole 1024 values in that variable. An int can hold up to 2^15 = 32,767. This is the default data type we use most often on the Arduino, but remember it also has its limits. For super big numbers or fractions/decimals, you can use data types long or float, but these take more Arduino brain power so are slower than using int.

October 18, 2010, at 10:45 PM by dpr2 -
Changed lines 25-27 from:
to:

Illustration of water analogy of electricity

Illustration of series vs. parallel

October 18, 2010, at 10:44 PM by dpr2 -
Changed lines 31-34 from:
Intro Pysch / MIT ocw / Jeremy Wolfe - Lecture 5 (Limiting information)
->Lecture notes / Lecture slides
->Additional lectures here
to:

Intro Pysch / MIT ocw / Jeremy Wolfe - Lecture 5 (Limiting information)
Lecture notes / Lecture slides
Additional lectures here

Changed lines 36-37 from:
http://itp.nyu.edu/~ad1790/filezzz/Multitasking.pdf
to:

http://itp.nyu.edu/~ad1790/filezzz/Multitasking.pdf

Changed lines 39-42 from:
http://www.wired.com/magazine/2010/05/ff_nicholas_carr/all/1
->http://www.livescience.com/health/091019-internet-brain.html
->http://www.livescience.com/culture/090224-internet-brain.html
to:

http://www.wired.com/magazine/2010/05/ff_nicholas_carr/all/1
http://www.livescience.com/health/091019-internet-brain.html
http://www.livescience.com/culture/090224-internet-brain.html

Changed lines 44-47 from:
http://www.eaglemanlab.net/time
->http://www.npr.org/templates/story/story.php?storyId=122322542
->http://itp.nyu.edu/~ad1790/filezzz/emotion-time.pdf
to:

http://www.eaglemanlab.net/time
http://www.npr.org/templates/story/story.php?storyId=122322542
http://itp.nyu.edu/~ad1790/filezzz/emotion-time.pdf

Changed lines 49-51 from:
Below is the link to the lab that we used for the EMG (although it was a ECG schematic). This is the one that seemed to work. ->Be warned, the background 'pictures' make the lesson almost unreadable.
->http://www.cs.wright.edu/~phe/EGR199/Lab_4/
to:
Below is the link to the lab that we used for the EMG (although it was a ECG schematic). This is the one that seemed to work. Be warned, the background 'pictures' make the lesson almost unreadable.
http://www.cs.wright.edu/~phe/EGR199/Lab_4/
Changed lines 53-55 from:
http://www.biomed.engsoc.org/node/30

Serial

to:

http://www.biomed.engsoc.org/node/30

Serial

October 18, 2010, at 10:42 PM by dpr2 -
Changed lines 26-54 from:

class 4
Alex's notes in response to reading - The User Illusion:

Perceptual Bottleneck:
Intro Pysch / MIT ocw / Jeremy Wolfe - Lecture 5 (Limiting information)
Lecture notes / Lecture slides
Additional lectures here

Multitasking:
http://itp.nyu.edu/~ad1790/filezzz/Multitasking.pdf

Internet’s effects on cognition and the brain:
http://www.wired.com/magazine/2010/05/ff_nicholas_carr/all/1
http://www.livescience.com/health/091019-internet-brain.html
http://www.livescience.com/culture/090224-internet-brain.html

Perception of time:
http://www.eaglemanlab.net/time
http://www.npr.org/templates/story/story.php?storyId=122322542
http://itp.nyu.edu/~ad1790/filezzz/emotion-time.pdf

Notes from Alex and Ezer's EMG project: Below is the link to the lab that we used for the EMG (although it was a ECG schematic). This is the one that seemed to work. Be warned, the background 'pictures' make the lesson almost unreadable.
http://www.cs.wright.edu/~phe/EGR199/Lab_4/

And the schematic comes from this site that encourages diy EMGs using Arduinos.
http://www.biomed.engsoc.org/node/30

to:

Alex's notes in response to reading - The User Illusion:

Perceptual Bottleneck:
->Intro Pysch / MIT ocw / Jeremy Wolfe - Lecture 5 (Limiting information)
->Lecture notes / Lecture slides
->Additional lectures here
Multitasking:
->http://itp.nyu.edu/~ad1790/filezzz/Multitasking.pdf
Internet’s effects on cognition and the brain:
->http://www.wired.com/magazine/2010/05/ff_nicholas_carr/all/1
->http://www.livescience.com/health/091019-internet-brain.html
->http://www.livescience.com/culture/090224-internet-brain.html
Perception of time:
->http://www.eaglemanlab.net/time
->http://www.npr.org/templates/story/story.php?storyId=122322542
->http://itp.nyu.edu/~ad1790/filezzz/emotion-time.pdf

Notes from Alex and Ezer's EMG project:

Below is the link to the lab that we used for the EMG (although it was a ECG schematic). This is the one that seemed to work. ->Be warned, the background 'pictures' make the lesson almost unreadable.
->http://www.cs.wright.edu/~phe/EGR199/Lab_4/
And the schematic comes from this site that encourages diy EMGs using Arduinos.
->http://www.biomed.engsoc.org/node/30
October 18, 2010, at 10:41 PM by dpr2 -
Changed lines 28-29 from:
to:

Alex's notes in response to reading - The User Illusion:

Perceptual Bottleneck:
Intro Pysch / MIT ocw / Jeremy Wolfe - Lecture 5 (Limiting information)
Lecture notes / Lecture slides
Additional lectures here

Multitasking:
http://itp.nyu.edu/~ad1790/filezzz/Multitasking.pdf

Internet’s effects on cognition and the brain:
http://www.wired.com/magazine/2010/05/ff_nicholas_carr/all/1
http://www.livescience.com/health/091019-internet-brain.html
http://www.livescience.com/culture/090224-internet-brain.html

Perception of time:
http://www.eaglemanlab.net/time
http://www.npr.org/templates/story/story.php?storyId=122322542
http://itp.nyu.edu/~ad1790/filezzz/emotion-time.pdf

October 18, 2010, at 10:39 PM by dpr2 -
Changed lines 27-28 from:
to:

Notes from Alex and Ezer's EMG project: Below is the link to the lab that we used for the EMG (although it was a ECG schematic). This is the one that seemed to work. Be warned, the background 'pictures' make the lesson almost unreadable.
http://www.cs.wright.edu/~phe/EGR199/Lab_4/

And the schematic comes from this site that encourages diy EMGs using Arduinos.
http://www.biomed.engsoc.org/node/30

October 17, 2010, at 10:51 PM by dpr2 -
Changed lines 20-21 from:

Office hours: Sunday evenings 6:30-8:30pm, and by appointment - email me to set something up. Also, the latest version of Skype has a screen share feature that's great for remote help. My Skype name is dustyn.roberts. By day my office is at the NYU-Poly campus in Brooklyn: 6 Metrotech Center, Rogers Hall 520B. Stop by any time for help (take the A/F train to Jay St, exit at back of train).

to:

Office hours: Sunday evenings 6:30-8:30pm in the adjunct lounge, and by appointment - email me to set something up. Also, the latest version of Skype has a screen share feature that's great for remote help. My Skype name is dustyn.roberts. By day my office is at the NYU-Poly campus in Brooklyn: 6 Metrotech Center, Rogers Hall 520B. Stop by any time for help (take the A/F train to Jay St, exit at back of train).

October 17, 2010, at 08:25 PM by dpr2 -
October 17, 2010, at 07:17 PM by dpr2 -
Changed line 31 from:

1 byte = 8 bits: range from 0-255\\

to:

1 byte = 8 bits: range from 0-255. The value of the byte is determined by the binary interpretation of the 8 bits.\\

Added line 41:

One last thing about ASCII: the first 32 raw values correspond with control characters, that won't even show up as garbage but stand for things like "carriage return" (ASCII 13).

October 17, 2010, at 07:14 PM by dpr2 -
Changed lines 39-40 from:

If you're thinking

to:

If you're thinking that ASCII encoding is an inefficient way to send numbers from 0-255, you're right. After all, sending the number 12 as two ASCII encoded bytes instead of one raw byte takes twice as much information. However, at the standard baud rate of 9600 that we work with, you're unlikely to feel this efficiency for just a few numbers. And it also gives you the flexibility to agree on one method of encoding for anything you might want to communicate between the speaker and the listener.

October 17, 2010, at 07:11 PM by dpr2 -
Changed lines 32-33 from:

Every group of 8 bits (1 byte) is interpreted at one time. If all you're doing is sending a potentiometer value divided by 4 (for example), you're only ever sending a number from 0-255 so you don't have to do anything. But if you want to send bigger numbers, or text a human can actually read, you have to format the byte that's being communicated to the speaker and the listener know what the F you're talking about.

to:

Every group of 8 bits (1 byte) is interpreted at one time. If all you're doing is sending a potentiometer value divided by 4 (for example), you're only ever sending a number from 0-255 so you don't have to do anything. This is sometimes called the raw value. But if you want to send bigger numbers, or text a human can actually read, you have to format the byte that's being communicated from the speaker to the listener to know what the F you're talking about.

Changed lines 35-36 from:

http://www.asciitable.com/

to:

http://www.asciitable.com/

The drawback is that when you send things at text, it takes as many bytes as there are digits. For example: a raw value of 12 only takes up one byte, but an ASCII encoded number 12 takes two bytes: one byte for 1 and one byte for 2. Be careful here. If you're speaking in ASCII-encoded text but listening for a raw value, you might interpret the 1 and 2 as their representative values in ASCII of 49 and 50. And if you're speaking in ASCII and listening in raw, you can get all kinds of garbage characters like ~, +, *, etc. that correspond with the representative ASCII values.

If you're thinking

October 17, 2010, at 06:59 PM by dpr2 -
Changed lines 32-36 from:

Every group of 8 bits (1 byte) is interpreted at one time. If all you're doing is sending a potentiometer value divided by 4 (for example), you're only ever sending a number from 0-255 so you don't have to do anything. But if you want to send bigger numbers, or text a human can actually read, you have to format the byte that's being communicated to the speaker and the listener know what the F you're talking about.

to:

Every group of 8 bits (1 byte) is interpreted at one time. If all you're doing is sending a potentiometer value divided by 4 (for example), you're only ever sending a number from 0-255 so you don't have to do anything. But if you want to send bigger numbers, or text a human can actually read, you have to format the byte that's being communicated to the speaker and the listener know what the F you're talking about.

It turns out that there's a standard system called ASCII code that can takes any value from 0-255 and assigns it an alphanumeric character (letter, number, or punctuation mark). Here's an example table:
http://www.asciitable.com/

October 17, 2010, at 06:52 PM by dpr2 -
Changed line 22 from:

Notes from classes:

to:

Notes from classes:

October 17, 2010, at 06:51 PM by dpr2 -
Changed line 29 from:

Serial

to:

Serial

October 17, 2010, at 06:51 PM by dpr2 -
Changed lines 27-32 from:
to:

class 5
Serial 1 bit: 0 or 1
1 byte = 8 bits: range from 0-255
Every group of 8 bits (1 byte) is interpreted at one time. If all you're doing is sending a potentiometer value divided by 4 (for example), you're only ever sending a number from 0-255 so you don't have to do anything. But if you want to send bigger numbers, or text a human can actually read, you have to format the byte that's being communicated to the speaker and the listener know what the F you're talking about.

October 03, 2010, at 07:09 PM by dpr2 -
Changed lines 3-6 from:

email (preferred) dustyn.at.dustynrobots.com\\ phone at 201.452.1583
Skype at dustyn.roberts

to:

email (preferred) dustyn.at.dustynrobots.com, phone at 201.452.1583, or Skype at dustyn.roberts

October 03, 2010, at 07:08 PM by dpr2 -
Changed lines 2-6 from:

I'm one of 5 instructors teaching 6 sections for PComp this fall. You can reach me by:
email (preferred) dustyn.at.dustynrobots.com \\ by phone at 201.452.1583
by Skype at dustyn.roberts

to:

I'm one of 5 instructors teaching 6 sections for PComp this fall. You can reach me by:
email (preferred) dustyn.at.dustynrobots.com\\ phone at 201.452.1583
Skype at dustyn.roberts

October 03, 2010, at 07:08 PM by dpr2 -
Changed line 2 from:

I'm one of 5 instructors teaching 6 sections for PComp this fall. You can reach me by:

to:

I'm one of 5 instructors teaching 6 sections for PComp this fall. You can reach me by: \\

October 03, 2010, at 07:07 PM by dpr2 -
Changed lines 2-3 from:

I'm one of 5 instructors teaching 6 sections for PComp this fall. You can reach me by email (preferred) at dustyn.at.dustynrobots.com or by phone at 201.452.1583.

to:

I'm one of 5 instructors teaching 6 sections for PComp this fall. You can reach me by: email (preferred) dustyn.at.dustynrobots.com \\ by phone at 201.452.1583
by Skype at dustyn.roberts

Changed lines 22-23 from:

Office hours: By appointment - email me to set something up. Also, the latest version of Skype has a screen share feature that's great for remote help. My Skype name is dustyn.roberts. By day my office is at the NYU-Poly campus in Brooklyn: 6 Metrotech Center, Rogers Hall 520B. Stop by any time for help (take the A/F train to Jay St, exit at back of train).

to:

Office hours: Sunday evenings 6:30-8:30pm, and by appointment - email me to set something up. Also, the latest version of Skype has a screen share feature that's great for remote help. My Skype name is dustyn.roberts. By day my office is at the NYU-Poly campus in Brooklyn: 6 Metrotech Center, Rogers Hall 520B. Stop by any time for help (take the A/F train to Jay St, exit at back of train).

October 02, 2010, at 11:15 PM by dpr2 -
Changed lines 22-26 from:
to:
October 02, 2010, at 11:14 PM by dpr2 -
Changed lines 21-26 from:
to:
September 20, 2010, at 11:06 PM by dpr2 -
Changed lines 24-26 from:
to:
September 14, 2010, at 06:53 PM by dpr2 -
Changed line 24 from:

class 2 http://www.bareconductive.com/home.html (A video of conductive ink, invented by Royal College of Art students)

to:
September 14, 2010, at 10:20 AM by sn1016 -
Changed line 24 from:

class 2 http://www.bareconductive.com/home.html

to:

class 2 http://www.bareconductive.com/home.html (A video of conductive ink, invented by Royal College of Art students)

September 14, 2010, at 10:16 AM by sn1016 -
Changed line 24 from:
to:

class 2 http://www.bareconductive.com/home.html

September 13, 2010, at 04:07 PM by dpr2 -
Added line 23:
September 13, 2010, at 04:06 PM by dpr2 -
Added line 23:
September 07, 2010, at 08:25 AM by dpr2 -
Changed lines 19-20 from:

'Office hours': By appointment - email me to set something up. Also, the latest version of Skype has a screen share feature that's great for remote help. My Skype name is dustyn.roberts. By day my office is at the NYU-Poly campus in Brooklyn: 6 Metrotech Center, Rogers Hall 520B. Stop by any time for help (take the A/F train to Jay St, exit at back of train).

to:

Office hours: By appointment - email me to set something up. Also, the latest version of Skype has a screen share feature that's great for remote help. My Skype name is dustyn.roberts. By day my office is at the NYU-Poly campus in Brooklyn: 6 Metrotech Center, Rogers Hall 520B. Stop by any time for help (take the A/F train to Jay St, exit at back of train).

September 07, 2010, at 08:24 AM by dpr2 -
Changed lines 17-21 from:
  • Tues, 9:30 - 12: Intro to Physical Computing (Class Dates)

Office hours: By appointment - email me to set something up. Also, the latest version of Skype has a screen share feature that's great for remote help. My Skype name is dustyn.roberts. By day my office is at the NYU-Poly campus in Brooklyn: 6 Metrotech Center, Rogers Hall 520B. Stop by any time for help (take the A/F train to Jay St, exit at back of train).

to:
  • Tues, 9:30 - 12, Rm 406 (Class Dates)

'Office hours': By appointment - email me to set something up. Also, the latest version of Skype has a screen share feature that's great for remote help. My Skype name is dustyn.roberts. By day my office is at the NYU-Poly campus in Brooklyn: 6 Metrotech Center, Rogers Hall 520B. Stop by any time for help (take the A/F train to Jay St, exit at back of train).

September 06, 2010, at 11:43 PM by dpr2 -
Changed line 19 from:

Office hours:

to:

Office hours:

Added lines 21-23:

Classes:

class 1

September 03, 2010, at 09:46 AM by dpr2 -
Changed lines 2-3 from:

I'm one of 5 instructors teaching 6 sections for PComp this fall. You can reach me at dustyn.at.dustynrobots.com.

to:

I'm one of 5 instructors teaching 6 sections for PComp this fall. You can reach me by email (preferred) at dustyn.at.dustynrobots.com or by phone at 201.452.1583.

Added lines 9-10:
  • http://itp.nyu.edu/mechanisms/ -- My other class on mechanisms
  • http://www.makingthingsmove.com/ -- My book on Making Things Move
Changed lines 15-16 from:
  • http://itp.nyu.edu/mechanisms/ -- My other class on mechanisms
to:
Deleted line 18:

Changed lines 20-22 from:

In general, I am happy to answer questions when I'm available, but I may ask you if we can a set up time in office hours if I don't have an quick answer. If you know in advance that you need time to talk about class-related things, then mail me and we can set up time, too. Please check my schedule to set up an appointment during office hours, since they tend to fill up.

to:

By appointment - email me to set something up. Also, the latest version of Skype has a screen share feature that's great for remote help. My Skype name is dustyn.roberts. By day my office is at the NYU-Poly campus in Brooklyn: 6 Metrotech Center, Rogers Hall 520B. Stop by any time for help (take the A/F train to Jay St, exit at back of train).

September 03, 2010, at 09:18 AM by dpr2 -
Changed lines 2-3 from:

I'm one of 5 instructors teaching 6 sections for PComp this fall

to:

I'm one of 5 instructors teaching 6 sections for PComp this fall. You can reach me at dustyn.at.dustynrobots.com.

Changed lines 13-14 from:
to:
  • http://itp.nyu.edu/mechanisms/ -- My other class on mechanisms
September 03, 2010, at 09:16 AM by dpr2 -
Changed lines 2-3 from:
to:

I'm one of 5 instructors teaching 6 sections for PComp this fall

September 03, 2010, at 09:15 AM by dpr2 -
Changed lines 1-3 from:
to:

Who

What

Changed lines 13-15 from:

Class hours:

  • Tues, 9:30 - 12: Intro to Physical Computing
to:

Where/When:

  • Tues, 9:30 - 12: Intro to Physical Computing (Class Dates)
Deleted lines 19-20:

You can book me for a specific slot at http://tomigoe.youcanbook.me

September 03, 2010, at 09:13 AM by dpr2 -
Added lines 1-2:

Welcome

September 03, 2010, at 09:09 AM by dpr2 -
Changed lines 1-2 from:
  • [Intro.HomePage|Intro to Physical Computing]
    • class wiki -- where I put stuff we wrote in class, where you can put stuff as well.
to:
Changed lines 3-4 from:
  • Understanding Networks
to:
Changed lines 5-7 from:
  • http://tigoe.net/pcomp -- my physical computing site
  • http://tigoe.net/pcomp/code -- code, circuits & construction. My code & resources blog. Where I post code and links for general use (not just this class)
  • http://tigoe.net/blog -- my blog
to:
  • http://tigoe.net/pcomp -- Tom's physical computing site
  • http://tigoe.net/pcomp/code -- code, circuits & construction. Tom's code & resources blog. Where he posts code and links for general use (not just this class)
  • http://tigoe.net/blog -- Tom's blog
Changed lines 11-14 from:
  • Tues, 3:30 - 6: Understanding Networks
  • Wed 9:30 - 12: Intro to Physical Computing
  • Wed 3:30 - 6: Intro to Physical Computing
to:
  • Tues, 9:30 - 12: Intro to Physical Computing
September 03, 2010, at 09:07 AM by dpr2 -
Changed lines 1-23 from:

what tom said

to:
  • [Intro.HomePage|Intro to Physical Computing]
  • Understanding Networks

Useful pages:

  • http://tigoe.net/pcomp -- my physical computing site
  • http://tigoe.net/pcomp/code -- code, circuits & construction. My code & resources blog. Where I post code and links for general use (not just this class)
  • http://tigoe.net/blog -- my blog
  • http://itp.nyu.edu/physcomp/sensors -- sensor workshop class wiki. A good place to learn about sensors, from another ITP class

Class hours:

  • Tues, 3:30 - 6: Understanding Networks
  • Wed 9:30 - 12: Intro to Physical Computing
  • Wed 3:30 - 6: Intro to Physical Computing

Office hours:

In general, I am happy to answer questions when I'm available, but I may ask you if we can a set up time in office hours if I don't have an quick answer. If you know in advance that you need time to talk about class-related things, then mail me and we can set up time, too. Please check my schedule to set up an appointment during office hours, since they tend to fill up.

You can book me for a specific slot at http://tomigoe.youcanbook.me

August 10, 2010, at 12:22 PM by dpr2 -
Added line 1:

what tom said

  Edit | View | History | Print | Recent Changes | Search Page last modified on December 06, 2010, at 08:55 PM