Closing Remarks

The last week has given me some time to reflect on the course and what I learned from it. During our review, John Marshall asked us a question about what moment during the course we felt like things started working for us as a team. At the time I couldn't think of an answer, and I wasn't sure what had changed for me personally that made the team work better, but know I think I understand what happened. There was a moment about three or four weeks before the project was due, that I realized that there was no way that our team was going to have a great project, or at least a project that would satisfy me. I came to terms with this, and decided that I would rather have a decent project than no project at all. For me, that is when our team started working together the best. I stopped trying to push the project in the direction I wanted it to go, and just went with what everyone else wanted to do. As a result, I was able to put a lot of time and energy into the project without arguing with my team mates.

Assembly

Assembly is going pretty good. We have all of our pieces fabricated except for the wooden panels, and the aluminum which we are water jetting right now. Hopefully we can get everything put together tomorrow night so that we have Wednesday and Thursday to wire it and install it in the gallery.

production

We have finally started making stuff! the first of our pieces have been fabricated. 2 sheets of acrylic were lazer cut, and we have started water jetting our aluminum pieces, although we have run into some time issues there. The pieces we have made so far all fit together properly, so hopefully the servos and panels work just as well. One thing I am a little concerned about is the weight. After carrying the three sheets of we ordered, me and pete realized how heavy this thing is going to be. I am hoping the bottom modules can carry the weight of those on top of them.

Redefining - again

Friday's class was extremely valuable in its ability to help my team identify problems with our project. It was surprisingly fulfilling to be able to find these problems out ourselves, instead of simply having one of the professors point them out. The idea of "reverse brainstorming" is definitely something which I am planning on utilizing on projects outside of this course.

Although the self criticism was good, I think everyone on team one felt a little daunted at the idea of seriously rethinking our project for a third time. We realized that the entire function of our project was a bit shaky, and that it required far to much money, material, and space to implement. I think that everyone in the team feels that the task before us is to make our project stronger, while at the same time making it easier to manage. In order to do this I think that we need to identify the things that are working well in our project, and scrap the rest.

The things which I think are working well are:

• modularity - this allows us to make a surface
• solar collection - this is necessary to make our project heliotropic
• Inter-Surface interaction - having each module of the surface comunicating with the other modules makes it smart
• Lighting - while people may not need to be shaded in parks, and may not want to spend time getting their laptop or phone charged, they still need to walk through parks when it is dark.

Hoberman

I probably should have posted this when it was more relevant, but it is still interesting. Hoberman's portfolio has a lot more in it than just expandable spheres. There are some amazing kinetic architecture projects too.

The problem of why

Now that we are starting the final project for Smart Surfaces, Ive been doing a lot of thinking about the design processes we've been using, and what the best way is to settle on a proposal for the final project. This class has given me an opportunity to explore new design techniques and strategies. In normal studio settings, I am given a set of problems which I then find an architectural solution for. However, in this class things are sort of turned around. We are given constraints about what our solution must be (a heliotropic smart surface), but not given a specific problem. This has been directly reflected in many of the projects which I have worked on this semester, especially the Hoberman aperture which my team designed last week. In that instance we designed a mechanism which was well thought out, but still had no specific reason for existing. Julian Bleeker was present for our project review, and had some excellent insight on our method of working which he wrote about on his blog.

As the deadline for the final project proposal closes in, I think that the most important task at hand is for us to synthesize our design strategies. We cannot simply produce work. We need to design our own "why", and also settle on an implementation strategy. Both of these need to be in place for us to have a strong project.

10/GUI

I ran across this video of a new computer interface which is being developed by 10/GUI. It has some correlations with Julian Bleeker's talk about the computer interface in Minority Report.

Surface Update

Progress is going pretty well on the mechanism. We have the aperture mostly assembled, and Taylor is figuring out the framework for it. Here are some stills from the digital project file we used to figure out the proportions and angles, as well as a video of the completed aperture.

Future of Design and Solar Surface

The current assignment for Smart Surfaces is to develop a solar responsive surface which integrates technologies which we have been using through out the semester (arduino, LEDs, LRDs, servos). The future of design conference was also this week, and one speaker whose talk was especially relevant to our class was Ila Berman, the Chair of Architecture at CCA. She talked about the development of responsive and component based architecture, as well as new strategies for re-usable materials. I had a chance to talk with her after the conference about uses for parametric architecture and surfaces, and how she thought that they would be used in the future. Her response wass that parametric modeling is just like any other new innovation, in that people have a tendency to get really excited about it and play with it for a while before actually figuring out how it can be best applied. I feel that Smart Surfaces falls into this category. We are playing around with tons of new technology, not knowing what we are going to be able to do with it, and thats exciting.

Turning back to the current project, my team decided to work on a surface which contains apertures which can open and close with a mechanism based off of the Hoberman Sphere. We first used Digital Project to analyze the mechanism and determine the necessary proportions. We are now in the process of integrating the aperture into a structure which could be arrayed into a surface.

4

Solar Tracking Field

Last week's assignment for smart surfaces was to develop a field of solar tracking components using digital project and modeling. The basis for my team's design was a sheer plane which could control the movement of multiple poles simultaneously.

We used servos and rubber bands to control the x and y axis movement of the plane. We also attached LEDs and a LDR to the machine in order to make the system responsive to the amount of sunlight present.

Finally we worked on developing a series of flower like mechanisms which would attach to the end of the poles. The flowers would be able to open and close in order to collect more or less sunlight depending on the light intensity levels

measured by the LDR.

More images and videos of the project are available here: http://www.flickr.com/photos/parsnipsncelery/sets/72157622468356900/

Solar Tracker

Our team's solar tracker used 4 LDRs and 2 servos to track a light source. The arduino and bread board is held in a box which is attached to the YZ axis servo.

Heres the code that we used-

void loop()

{

for(posY = 0; posY <>

{ // in steps of 1 degree

Yaxis.write(posY); // tell servo to go to posYition in variable 'posY'

delay(15); // waits 15ms for the servo to reach the posYition

}

for(posY = 46; posY <>

{ // in steps of 1 degree

Yaxis.write(posY); // tell servo to go to posYition in variable 'posY'

delay(15); // waits 15ms for the servo to reach the posYition

}

for(posY = 136; posY <>

{ // in steps of 1 degree

Yaxis.write(posY); // tell servo to go to posYition in variable 'posY'

delay(15); // waits 15ms for the servo to reach the posYition

}

for(posY = 180; posY>=1; posY-=1) // goes from 180 degrees to 0 degrees

{

Yaxis.write(posY); // tell servo to go to posYition in variable 'posY'

delay(15); // waits 15ms for the servo to reach the posYition

}

}

Moriyama House

Thom had us kick start the semester with a precedent exercise. In teams of three, we were assigned component based houses, and given the task of scaling the house up to the size of a city block. My team (Burger/Adelson/Giles, or BAG architects) worked on the Moriyama house, by Ryue Nishizawa of Sanaa. The house is composed of eight differently sized boxes. Three of the boxes are occupied by client, while the others are rented out to tenants. Nishizawa designed the house as eight different buildings so that it would meld with its surroundings, and not be too large.

We decided that the most appropriate way to fill a city block with this house would be to use Nishizawa's logic of multiple, unique boxes. I used Grasshopper to generate 50 uniquely sized boxes, ranging in dimension between 10' and 40' ( the largest dimension in any of the original houses was 20', so we allowed some of our houses to be slightly larger). After laser cutting the boxes, we played with various arrangements, and decided on one which responded to a topography, as opposed to to simply keeping a strict orthogonal grid.

Arduino

This is a clip of the LED lamp which I made for smartsurfaces this week. The "Lamp Shade" is made of trace wrapped in wire.