Monday, January 25, 2010

Exercise 2

The objective of this exercise is to do a sketch design for an office building. The criteria are as follows:

The Site
  • The plot is 85m x 170m, rotated at 45 deg, with the long axis in the NW - SE direction
  • The site is surrounded on all sides by category 3/4/5  roads, with no other surrounding structures
  • The site is somewhere in Singapore
The Developmental Constraints
The Evaluation Criteria
  • Maximise daylight autonomy
    Using EnergyPlus, see 'Daylighting:Controls'
  • Minimise cooling load
    Using EnergyPlus, see 'ZoneHVAC:IdealLoadAirSystem'
  • Maximise lettable floor area

Friday, January 22, 2010

BIG | Bjarke Ingels Group

BIG is coming to town! - this coming Friday January 29th, 2010 at 4pm LR 423 speaking on “Yes is More”. RSVP by 27 Jan 2010 to Clara at akicwkm@nus.edu.sg

Thursday, January 21, 2010

Custom Python operators

Here is the script that we did today:

# Get the data
this_node_obj = hou.node(".") #this is the same as hou.pwd()
geom_obj = this_node_obj.geometry()
points_list = geom_obj.points()

# Find the average
average = [0,0,0]
for point_obj in points_list:
    average[0] = average[0] + point_obj.position()[0] # could use +=
    average[1] = average[1] + point_obj.position()[1]
    average[2] = average[2] + point_obj.position()[2]
num = len(points_list)
average = [average[0] / num, average[1] / num, average[2] / num]

# Save the data
new_point_obj = geom_obj.createPoint()
new_point_obj.setPosition(average)

Monday, January 18, 2010

Houdini Python parameter expressions

When scripting in Houdini, there are two languages that you can use. The old scripting language is called hscript, and the new one (gradually replacing hscript) is Python. When scripting in Python, there are many different places where you can insert Python scripts - the two most important are:
  • Parameter expressions: these are Python scripts inside the parameter input fields. You can right click on an input filed, and select Expressions > Edit Expressions. You need to make sure that your scripting language is set to Python. These scripts are saved as part of you Houdini model, in you .hip (or .hipnc) file.
  • Python operators: these are custom nodes implemented from scratch in Python. These are saved in .otl files, and can be used the same way as the built in nodes.

In yesterdays workshop, we focused on parameter expressions, and we wrote some expressions to find the average of a set of input points. Here is the script:
# Get the data
this_node = hou.node(".")
inputs = this_node.inputs()
first_input = inputs[0]
input_geometry = first_input.geometry()
points = input_geometry.points()

# Loop through add add up all the points
x = 0
for point in points:
    point_pos = point.position()
    x += point_pos[0]

# Divide the values by the number of points
num_points = len(points)
x = x / num_points

# Return the value
return x
The Houdini functions and classes are all in the hou module. When scripting in Houdini, the hou module is imported automatically, so there is no need to have 'import hou' in your scripts. The key ones to loo at from todays sessions are the following:
In order to better understand what is going when using the Houdini classes above, review Python classes in one of the tutorials. For example, in the Instant Hacking  tutorial , scroll down to the last section "More Abstraction — Objects and Object-Oriented Programming". This gives a quick explanation of classes.

    Friday, January 15, 2010

    Python Introduction

    I am doing a Introduction to Python workshop on monday morning 10am to 1pm.

    This is mainly for the people who missed thePython workshops in week zero. However, for those who think they need a refresher, you can also come.

    Please make sure that you have done these two tutorials before Monday morning:

    Wednesday, January 13, 2010

    Semester Schedule

    •  Week 1 Mon 11 Jan: Studio intro, followed by Houdini intro
    Exercise: Flying object
    • Week 1 Thu 14 Jan: Houdini workshop
    • Week 2 Mon 18 Jan: Houdini workshop
    • Week 2 Thu 21 Jan: Houdini workshop
    • Week 3 Mon 25 Jan: Presentation of exercise 1
    Exercise: A room
    • Week 3 Thu 27 Jan: Tutorials
    • Week 4 Mon 01 Feb: Tutorials
    • Week 4 Thu 04 Feb: Tutorials
    • Week 5 Mon 08 Feb: Presentation of exercise 2
    Project: design site and design brief
    • Week 5 Thu 11 Feb: Introduction to design site and brief, followed by site visit
    Recess week and non-studio week:
    •  Recess week Mon 15 Feb
    •  Recess week Thu 18 Feb
    • Week 6 Mon 22 Feb: Non-studio week
    • Week 6 Thu 25 Feb: Non-studio week
    Project: the design idea:
    • Week 7 Mon 01 Mar: Tutorials
    • Week 7 Thu 04 Mar: Tutorials
    • Week 8 Mon 08 Mar: Presentation (Interim crit 1)
    Project: iterative design process:
    • Week 8 Thu 11 Mar: Tutorials
    • Week 9 Mon 15 Mar: Tutorials
    • Week 9 Thu 18 Mar: Tutorials
    • Week 10 Mon 22 Mar: Tutorials
    • Week 10 Thu 25 Mar: Tutorials
    • Week 11 Mon 29 Mar: Presentation (Interim crit 2)
    Project: presentation production 
    • Week 11 Thu 01 Apr: Tutorials
    • Week 12 Mon 05 Apr: Drawing up
    • Week 12 Thu 081 Apr: Drawing up
    Hand in
    • Week 13 Tue 13 Apr: Drawing Submission & Pin up 3pm to 4pm
    • Week 13 Wed 14 Apr: Model Submission 3pm to 4pm
    • Week 13 Thu 15 Apr: Crit Session
    • Week 13 Fri 16 Apr: Crit Session

    Exercise 1: Flying Object

    The first exercise is an Iterative Physical Prototyping exercise. The aim of this exercise is to investigate the iterative design process using non-digital tools and techniques on a highly simplified design problem.

    The problem is as follows:
    • Design a flying object made of A4 paper. Your design must start with your core idea or concept for the design. This is your creative leap, a moment where past experience and intuition result in some new possibilities... Note that the flying object does not necessarily need to be a plane. It can be like a floating object, or it can spin as you drop it,... Some seeds float in the wind in interesting ways.
    • Create a developmental diagram for the design. This diagram should specify parameters that can be vary within a certain range. Different designs can then be generated by specifying different values for the parameters.
    • Create a evaluation diagram for the design. The evaluation diagram will specify certain performance criteria. These performance criteria can then be used to calculate the fitness of the design relative to other designs. Possible performance criteria could be distance travelled, time in the air, number of loops, maximum height, ... etc.
    Once you have created your diagrams, you then need to start the process of generating and testing different design variants. After a while you may find that your original idea is not working so well, and that you have some new ideas. In such a case, you can update the diagrams, and then start generating and testing new variants.

    The deadline for this exercise is Monday 25th January. This is a group exercise - so get into groups of 2 or 3. Your final presentation should focus on the process - so we want to see a series of diagrams, and for each diagram, a set of variants. Try and map out what happened, and why you made certain decisions.

    Another aspect of this exercise is to start practicing generating clear diagrams. The diagrams need to be as clear and simple as possible. I.e.  - there should be nothing on the diagram that is superfluous. The best way to learn these type of graphic skills is to copy other people - look at other diagrams such as origami. Also, some architects also use diagrams in an interesting way - e.g. look at BIG | Bjarke Ingels Group