Comm Lab: Week 2 (and week 1) – Reaction to Xacti camera, in-class assignment

I just so happened to come across the video of another Comm Lab student, Alexandra Kuechenberg et al, which is posted on her elegant blog. The video here is basically a loop of four people participating in leap frog.

Well, I’m not sure how I’m supposed to comment, but it does seem interesting that it took 40 minutes to film and edit a clip that, when filmed, was probably all of 20-30 seconds. But, with this comment, I admit that I’m simply suspending my knowledge of working with a timeline in order to essentially make a naive comment, because in my experience, it seems like working with anything with a timeline takes forever to produce even the most basic material.

In any case, what I don’t see is that the final clip accurately captures a narrative arc…but maybe that might be my naive comment. Perhaps I’m thinking too literally about what makes a narrative arc, or simply projecting examples that are overly complex. As a narrative with a beginning, middle and end, each loop did accomplish that format. People leap frogged on, the leaped over each other, and they leaped off. So, I guess there is a narrative there that follows my self-imposed restriction on narrative arc. But, I do think the looping is throwing me, because with the start of each loop I’m expecting something to happen that doesn’t. So I feel disappointed in the story that more isn’t happening. Oh well. Maybe next time….

Phys Comp: Week 2 – Analog sensors, Part 2

This week’s assignment consisted of coming up with a fantasy device, and possibly going crazy using analog sensors. I did both.

First up: the UV-Sunlight watch. This watch detects how much sunlight you’ve received. The benefit to the wearer is that during winter months, you’ll know when you haven’t gotten enough sunlight, and during the summer you’ll know when you’ve gotten too much. I really thought about the design of this one, which may not have been the point, but I do like the final product.

It’s fairly practical and useful, and it was fun to make. But, I would, maybe, agree with the argument that it’s not that fantasmal. Hence, my second fantasy device.

The Unicorner! I learned by the age of six that most humans are incapable of viewing true unicorns. So try as I might, I have never seen a unicorn. My device changes that. This device changes the assumption that there are no unicorns in the world by revealing the true identity of what appear to be ordinary horses, by transforming them into unicorns so that humans can see them! It only works if they were really unicorns to begin with, but it’s only $49.95. It took me under 10 minutes to make, but I added the plastic bag and UPC code later, so maybe 15 minutes of work.

Other ideas included:

  • a camera that takes pictures of your food and reports the nutrition content
  • an alarm clock that mixes smells and sounds, like cinnamon rolls + Paris cafe, and bacon + New York diner.
  • a musical device for orchestra and band students, that plays back a pre-recorded song so that your band leader/conductor can’t tell when you’re playing out of tune. (Note: will not actually help you learn to play an instrument).
  • a remote control to make a parent slower and decreases the volume of their voice
  • an iPhone app that tells you if a store you’re in front of has your size in stock

Finally, I again took apart my teddy bear and hooked up light switches to two FSR sensors. When the hands of the bear are squeezed, the lights come on. But, because I put variable input into the Arduino, it’s difficult to get them both to light up simultaneously. I will add video later.

Code is here.

int ledPinGreen = 10; // Green pin
int ledPinRed = 9; // Red pin
int ledPinWhite = 11; // White pin

int analogFSRLeft = 0; // Left analog input
int analogFSRRight = 1; // Right analog input

int FSRValueLeft = 1; // Value of the left FSR
int FSRValueRight = 1; // Value of the right FSR

void setup() {
// initialize serial communications at 9600 bps:
Serial.begin(9600);
}

void loop() {
FSRValueLeft = analogRead(analogFSRLeft); // read the left FSR value
// if FSRValueLeft is under 300
// light nothing
// if FSRValueLeft is between 300 and 600
if( FSRValueLeft > 250 && FSRValueLeft < 375  ){
analogWrite(ledPinGreen, FSRValueLeft/4);
} else {
digitalWrite(ledPinGreen, LOW);
}
Serial.println(FSRValueLeft); // print the FSR value

FSRValueRight = analogRead(analogFSRRight); // read the right FSR value

// if FSRValueLeft is between 300 and 600
if( FSRValueRight > 200 && FSRValueRight < 750  ){
analogWrite(ledPinRed, FSRValueRight/4);
} else { // do nothing
digitalWrite(ledPinRed, LOW);
}

/*  FSRValueRight = analogRead(analogFSRRight); // read the right FSR value
FSRValueLeft = analogRead(analogFSRLeft); // read the left FSR value
if( FSRValueRight > 200 && FSRValueRight < 750) && ( FSRValueLeft > 315 && FSRValueLeft < 380  ){
analogWrite(ledPinWhite,  FSRValueLeft/4,  FSRValueRight/4);
} else { // do nothing
digitalWrite(ledPinRed, LOW);
digitalWrite(ledPinGreen, LOW);
}
*/
Serial.println(FSRValueRight);  // print the FSR value

delay(10); // gives a 10 millisecond delay
}

Response to “The Machine Ends” by E.M. Forster

Written in 1909, “The Machine Stops” is about a futuristic society in which humanity lives underground and is dependent entirely upon the Machine, which has taken over the entire maintenance and care of all human needs. It describes how people have given up control of their own freedom to exert free will, in exchange for complete obedience to the Machine.

It was a peculiar but interesting story, particularly being written in 1909. According to Wikipedia, US events in 1909 included Taft succeeds Roosevelt as president, Pearl Harbor is founded, and the Manhattan Bridge is opened, while in Europe construction begins on the Titanic and the oil company that eventually became BP was founded. Forster seems to be writing from a perspective of relatively significant industrial and social change so the story is likely meant to be a reflection and a warning on unrestrained acceptance of technological innovation, and a belief that machines alone are the key to the future of the human race.

One of the phrases that reinforced this idea was on page 18, “No one confessed the machine was out of hand”. That could be taken literally, as in ‘no one is willing to complain that the machine is breaking’. Or it could be taken as it is in the phrase, the “Master Brains had perished”, which describes how complete knowledge amongst humans regarding the mechanical knowledge about the Machine — and possibly its usefulness — had been split up, so that now no one can really remember how the machine is supposed to work. In comparison to the use of the internet, there are still people who do not know what the internet is, let alone know how it can be used or misused. I suspect that most people who use the internet, do not really understand how it works, why it exists, or care much to learn.

The first sentence gives a clue to that the tone of the story is about obedience and regulation, when it describes the setting as being similar to the “cell of a bee”. The discussions about ideas, seem like the collective thought for the humans in this story is that unless something leads to progress or to a new idea, it is a useless waste of time. For instance, when other people in the story discuss the rumor of the machine ending, they cannot even comprehend the statement. As much as I can hardly comprehend living without civil rights or an electrified home, I suppose that soon there will be people who cannot comprehend a time before the internet or computers.

Lastly, the people in this story seem afraid to think on their own and come up with their own ideas, particularly when those ideas are not acceptable to those allowed by the Machine. The internet now makes it very easy to find ideas like your own. So that if you want to find arguments that agree or disagree with your own, it’s easy to find examples, without really coming up with your own critical analysis of a problem.

Phys Comp: Week 2 – Analog sensors, Part 1

This week we worked with analog sensors.

For the lab, I was able to correctly set up the breadboard, Arduino, and potentiometer to create my first analog input. I documented along the way.

Then I made a two-input analog switch with two LEDs as output. Here’s the code:

int ledPinGreen = 10; // Green pin
int ledPinRed = 9; // Red pin

int analogFSRLeft = 0; // Left analog input
int analogFSRRight = 1; // Right analog input

int FSRValueLeft = 1; // Value of the left FSR
int FSRValueRight = 1; // Value of the right FSR

void setup() {
// initialize serial communications at 9600 bps:
Serial.begin(9600);
}
void loop() {
FSRValueLeft = analogRead(analogFSRLeft); // read the left FSR value
analogWrite(ledPinGreen, FSRValueLeft/4);
Serial.println(FSRValueLeft); // print the FSR value back to the

FSRValueRight = analogRead(analogFSRRight); // read the right FSR value
analogWrite(ledPinRed, FSRValueRight/4);
Serial.println(FSRValueRight);

delay(10); // gives a 10 millisecond delay
}

Comm Lab: Week 2 — My (short) Tree Museum visit

This week, one of my assignments was to head to the Bronx to check out the Tree Museum, a public art project by Katie Holten. By name only, this sounds like it actually might be kind of interesting. I visited the Bronx Botanical Gardens last summer (2008) and I was thoroughly impressed. Everyone should go check it out. However, when I checked out the website, my hopefulness began to wane. Seriously. Rather than go into a terribly long discussion about what I didn’t like, I’ll just mention the two areas that disappointed me the most and will probably keep me from checking out more of this tree tour.

Disappointment #1: The first thing I was disappointed with was The Bronx. Well, I’m sort of scared of the Bronx. I mean, say what you will about gentrification, but what you don’t say is unsafe. I guess I prefer prefer strollers and soccer moms to whatever it is that goes on in the Bronx that keeps most people from visiting every weekend. So, I was a bit hesitant about checking it out. Also, the tour seemed to be about 70 blocks long and it just seemed like a bad idea for someone to go wandering around an unfamiliar neighborhood with no particular destination in mind, except to walk the length of the Bronx and look at semi-random trees that most people in the surrounding neighborhoods didn’t really seem to take too much notice of. So, to be safe, I wanted to look up as much as possible as I could on the website before visiting, including calling the 718 (not toll-free) number and see what this thing was all about. Which leads me to…

Disappointment #2. Not only was the audio quality poor enough that I could barely comprehend the speaker’s voice while sitting in a semi-empty room on a Sunday afternoon, but they also let the artist herself speak. What you learn on the site is that Ms. Holten is Irish. I love accents, but “poor audio” + “funny accent” = “I don’t know what you’re talking about”.

I don’t want to sound like I’m picking on the Irish accent, but the audio quality was very poorly implemented. It seems as if they forgot that New York City is L-O-U-D. When I visited on Wednesday morning, I didn’t call the 718 number but it wouldn’t have mattered anyway. I got off the subway at the 135th St. stop in the Bronx. Right under a bridge. If I could barely hear inside a building, how would I possibly be able to hear anywhere in NYC outside and especially near a bridge? The street where the tour takes place is called “Grand Concourse”. It sounds like a major street, and I would expect that it’s probably always loud.

I don’t know if this walking museum idea was actually tested out before going through with the project, but my guess is no. I know that Fort Tryon Park is pretty darn quiet for anywhere in Manhattan. Seems like it would be a much better destination for outdoor listening of relatively good audio. And, there are definitely plenty of kids and strollers.

How to solve a Rubik’s Cube

For the Data Visualization class I’m on the waitlist for, we were asked to come up with the solution for solving a Rubik’s cube.

To solve a Rubik’s cube, you basically need to remember that the whole thing consists of a series of patterns that, if you trust them, will solve the puzzle for you. In the past, when I’ve tried to solve the puzzle, I was somehow able to solve one side of tiles. Then, when I try to complete the rest of the puzzle, I find that I’m stuck. Whenever I try to complete another side, I find that I am too afraid of messing up the side I’ve completed, so I stop working. This fear is, of course, justified, since I do in fact mess up the side I just completed when working on the new side.

I’ve come to learn that what I’ve been missing is an algorithm or several algorithms. “Algorithm” sounds like a math term, and since I tend to stay away from math, I can’t say I’ve come across it before. However, since I’m supposed to come up with a description for how to solve a Rubik’s cube, I did some research:

• I understand that an algorithm is a set of defined instructions that are carried out until certain conditions are met. – Wikipedia

• Different algorithms can be used to accomplish the same task. The one that is used depends on the constraints for each task. – howstuffworks.com

• Algorithms are used to solve a recurrent problem. – whatis.com

These are all interesting, and apparently algorithms are what make up computer languages. But, using these definitions, algorithms are also what fill up cookbooks and instruction manuals. Hmmm….

Well, anyway, now for my solution:
1. Get a Rubik’s Cube.
2. Turn the faces of the Rubik’s Cube, one face at a time, until one side consists of the same color in each of the nine squares. Call a side that consists of the same color in each of the nine squares a Full Side.
3. Repeat step 2 for each of the five colors but whenever you need to break a Full Side, so that the nine squares of the same are no longer touching, you must put them back so that they are touching again.
4. Repeat step 3 until there are six Full Sides.