All posts for the month September, 2015

In thinking about what to do for the multiples assignment, I came across a tutorial on making a cube within a cube  ( .  I thought that this would be a novel idea for this project, since there would be multiples within each object.  So I wanted to do a cube within a cube, within a cube.

I began by cutting down a 4x4x8′ into a several 4″x”4″x 4″ blocks. Using a clamp and a block to move the source wood into made this process easier and the blocks pretty uniform.


Next I moved onto the drill press to cut out the cubes inside these cubes.  I made another jig to place each block on the press to get uniform results and using two forstener bits.  The picture I took of that jig is missing from my phone documentation. 🙁

During the process of making the second cubes in the series of blocks I began to experience catastrophic failure due to the softness of the wood.



Good thing I made lots extra. Multiply by Pi



I had some significant trouble working with some of my variables and conditional logic.  Also for an added bonus I was adding a png file and an audio file to try something that I hadn’t done before.


First the image wouldn’t load, but that was down to me referencing the file from the wrong folder path.

Second the music wouldn’t play which was due another error on my part of not using all of the reference code for the loadSound function.

Keep plugging away and asking questions and eventually you come across the answer.


Here’s the code. I am not giving out the associated files, I don’t want to ruin the surprise.

function preload() {
img = loadImage(“./assets/le-logo-du-poing-leve-des-black-panther.png”);
mySound = loadSound(‘./assets/Steel Pulse – Uncle George.mp3’);


var x, y;
//word loc is word location x
//worloc2 is word location y
//ts is text size
var wordloc = -5
var wordloc2 = 400
var ts = 8

function setup() {
createCanvas(1920, 1080);

function draw() {
// On mouse click change bg color for a sexy party
// Display moving text that says “power to the people”

background(random(225, 255), 100, random(50, 150));
image(img, 500, 200);

stroke(0, 10)
text(“Power to the People”, wordloc, wordloc2 – 1);
text(“Power to the People”, wordloc, wordloc2 – 1);
text(“Power to the People”, wordloc, wordloc2 – 1);
text(“Power to the People”, wordloc, wordloc2 – 1);

if (frameCount >= 127) {
ts = 150




While in the city looking for devices that are interactive I noticed the buttons on light poles that are supposed to trigger signal lights for crosswalks.  My assumptions were completely wrong about how these buttons are used, or rather not used by the public.



I found anecdotally that these buttons are rarely if ever used, and if used they are pounded on like a dammit doll. Not like the kind gentleman in the photo gently pressing as if pressing the Pillsbury Dough-boy’s tummy.

No, people if they did use them they pounded on the buttons like their life depended on it.  This generally took the longest amount of time.

But most people never even approached the button much less looked at the crosswalk sign and took mere seconds to decide if they were crossing yet or not.  They simple glanced quickly at the traffic light above the intersection and then down the street to see if cars were coming.  If there was no cars, they disregard the signs and quickly cross the road. Many people just looked at the person ahead of them or across the street from them to see if they were going and did whatever they did.

(This video was not filmed at the location I studied at 23rd Street and Fifth Avenue but you can get the idea of what is happening)

It is either a failure of the technology satisfy the needs of the population using it, i.e. no direct feedback that leads the public to think of the buttons as placebo buttons, or it is a failure of the enforcement of jaywalking laws or both.

Now I am not advocating for cops standing around harassing people for crossing the street, I mean people do have places to go, but much like elevators without a light in the button it seems like nothing is being done when the button is pressed.  Crawford would call this a lack of feedback in the interaction.



I began working on the week 3 lab for Pcomp today.  Pretty straight forward stuff, it would seem.  The problems began when I bought a longer breadboard from a 2nd year student, thanks Stream, (no sarcasm intended the fault was all mine.)




I spent about 3 hours trying different combinations of wiring examples and set ups, from the labs to the arduino examples.  I could not get power to a LED!

So I began trouble shooting from the end that I knew had power, the board.   I worked from component to component to find the problem.  It just did not make sense.  Until Druv said, “Hey does that break in the breadboard mean that power stops there?”

Sure enough.  I put a jumper cable over the break in the middle of the board and shazam there was power to the entire board.

It took about half an hour to finish the lab after that.


Use your multi-meters boys and girls.




Make a flashlight:


I found this pretty cool flashlight diy video and tried to adapt it to my needs…



I made my flashlight with one light to save space withing the body of the light and to save on voltage for my led.

I first had to learn how to solder, which was sort of a trick.  But I made the contact leads too long on the light string which gave me problems later.  I also changed the type of switch to a tiny toggle switch that is only on while depressed, to mimic a little thumb light I used to have and still miss.  This change, however minor,  was  going to end up being a tricky situation to contend  with as well.

The switch I used was really small so there was not much to solder to once the leads were put through the end cap of the light.  Moon, (a resident), gave me some advice about working with such a small connection which turned out to be very useful indeed.  The result of the long leads coming from the LED was to unpin the leads from the battery every time I attempted to close the light, but with a little tinkering and a lot of patience I was able to get it closed with the light working.


I really found out some of the strengths and weaknesses of the fabrication lab in this project.  Buy your own tools if at all possible, and keep a good stock of your own tools in a sizable toolbox. Don’t count on something being there for use even if the shop usually has it. Buy your own supplies if at all possible, and keep those supplies in your own toolbox.  Anyway, here are some photos of the materials and the process.

Circuit template

Simple Circuit (turns out this is wrong…this is a short circuit, it needs a resistor)

Single Diode Schematic W Resist

Circuit with a resistor and a LED

Triple Diode Schematic Parallel W Resist

Circuit with a resistor and three LEDs in parallel

Triple Diode Schematic Series W Resist

Circuit with a series of LEDs and a resistor


I made all of these listed in the schematic. I am still trying to work out how to document this in the best possible way.  I am sure with practice I am going to figure out a clear and concise way to show this work. Until then this is what I have.

I played around with  parameters and variables in p5.js

I have had a fair amount of success working with mouseX and mouseY, I used them to change the color and size of an ellipse.

I am working on changing the frame rate as a variable but with little success.  Probably something I am not thinking about right now that is screwing the pooch.



Screen Shot 2015-09-13 at 4.01.20 PM

As you can see I have been getting some interesting results.