Today, we’ve studied fundamentals of component-based design methods. Using curves and surfaces as starting points, we’ve experienced ways of translating those entities via design criteria based on our purposes. First, a curve is used to construct a leaf structure. We’ve experienced dispatching data lists and combining them back together. Subdividing curves into points created further entities such as vectors and planes. We used those entities as inputs of regular drawing and modeling commands such as rectangles, or planar surfaces. This in-class exercise can be studied here. Second exercise was the […]

Today, we’ve discussed ways of subdividing entities to create parametric definitions. Curves can be divided into segments, creating snake-like object definitions. This exercise is important regarding the management of data. Vectors and planes are used as reference entities here. Nowadays, it became clear to me that, reference planes are very important because they both include reference points and related vectors as well. The definition studied in this post includes a curve subdivision and a combination of vector / plane management to create what we’ve deserved for: A Taenia-like freak object.. My […]

Generating data lists and data trees in Grasshopper is one of the important aspects of Dataflow Computing in general. Also literally, utilizing above conception, a set of data could be organized to shape a tree. This homework was a part of Parametric Modeling course, technical tutorials phase. After this phase, students will prepare for their final projects. I hope these exercises would develop the necessary conception before getting more into the designerly way of computing. After introducing the basics of Grasshopper, students tried to create such shapes and underlying data […]

This was an interesting topic of design computing class. Geometric constructions based on strict relationships are becoming exciting in parametric modeling environments. I think muqarnas includes such a relationship. There is a basic method of modeling this shape, introduced by Mete Tüneri. His solution to a simple muqarnas object includes a surface with six reference points on it, with two boolean differences (one cylinder and one box) create the component. In Grasshopper, I tried to simulate his process by adding real-time parameters such as number of rows and row height. […]

Today’s subject was closely related with the one last week; the data list and data tree management. Creating suitable data structures for our purposes is one of the tricky parts of whole Grasshopper experiments. We’ve developed a grid of objects, somehow associated with another one (a curve). Strong emphasis was on the way of thinking, getting back and forth on the process and re-definition of data-lists. Especially, this in-class exercise would help you understand basic design technique in such environments. Every design decision should be defined clearly and implemented to […]

SPEC disappeared from our garden suspiciously. Hopefully we’ve already finalized it’s parametric survey. Can has created the original model by measuring exact corner coordinates. Then, manipulated it’s shape by creating diverse vectors for each shape. Emre has also tried a similar approach. Can’s definition was too long, not using data trees, therefore it is slow. But it’s very effective at offering a solution for an animation. I re-captured his frames for animation; Another innovative solution came from Yağız along with a presentational concern. He seems know what he’s doing. He […]

Here is a funny sketching system for the “SPEC” homework. [GHX: 0.8.0066] Four (or more) points are created using 2d sliders (MD slider) and decomposed these points into x,y and z numbers. Then, they are re-populated in 3d points by changing their plane. X coordinates are connected into Y, and Y coordinates are connected to Z’s. Tricky part comes then, the X number is defined by a serie of numbers started from 0 to 30 by 1. After that, polylines are constructed using the new point list. Data recorder is initialized to […]

Today, we’ve studied ways of representing multiple data structures in Grasshopper. As of our last week’s experience, sometimes (most of the time actually) we’ll need to work with vast amount of data. We’ll have to control them in order to open door for further explorations. Today’s exercise was a good example of this “sustainable” process of data management. All functionality of Grasshopper is based on data matching. From short-list, long-list matching, to the structures of data trees. The simple solution to a one-point attractor on a grid represents this very […]

This is the basic definition of one point attractor on a grid of points. [GHX: 0.8.0066] Here, fundamentals of data tree matching can be studied. A hexagonal grid is exploded into points and new polygons are created there. Instead of a standard point distance relation to polygon size, this time the distance factor effects rotational angle of these polygons. Although the structure of data trees are getting complicated, this has no difficulty on such definition, because the operational complexity is still very simple. This means, we might use complex data trees, however the […]

So far, only Yağız Özkan posted an animated solution; Now, they seem to improve much, as they will now include operations on data trees. Yağız constructed a complex diagram, defining each point and curve seperately. Today, we’ve seen methods to shorten these diagrams and improve effectiveness of the plug-in. Important part of that study was to develop a proactive behaviour on creating Grasshopper definitions from the hand-drawn diagrams. We need to study all components, their input and output types carefully, so that we’ll be able to tell Grasshopper what to […]

Maybe a huge kitsch for contemporary architecture, I know, but a good example of a fundamental problem of constructing geometric relationships. In ARCH362 today, we’ve examined the geometric modeling process that opens us parametric relationships just by converting it into a diagram of design history. You may follow the construction of such a diagram step by step and see the possible parameters emerged from it. Only rule of this construction is the connection from the left side of the component (node) represents an input to that node, and the connection […]

Whenever we try to define something suitable for our design intentions, it became somehow closely related with the design tool. Contemporary theory of computational design (or design computing) has many definitions. In this website we look at that from the perspective of method and it’s theory underneath, not the tools; but however it finally comes to a point that we -again- start to talk about “tools”. Whatever, the purpose is “the process” or the associative geometries, even a diagram is again developed from the “computerization” of our minds. Some people […]

Today, we’ve concentrated on the fundamental issue of any visual programming language; the dataflow management. In a most basic form of this conception; geometric modeling process can be derived in such a way that we can always go back in it’s history and change any input data to see the result. We use diagrams to represent a flow of data. Such diagrams could easily be created by representing the conscious sequence of each step of your geometric modeling process. Although it seems similar to regular control flow diagrams we create […]

Here are some of the results of first assignment, “Reptile Skin”. Generally, we couldn’t manage to develop innovative solutions to the problem. But this became a good starting point for understanding the method of “skins of components” in contemporary digital design. Before going into any control over the flow of data, it’s hard to maintain associative geometries. We usually feel stuck within the capabilities of the single commands or procedures. That’s why, digital design deals with “processes” much more intensively than the formal outputs and develop tools and methods to […]

In recent years, computational approaches in architecture started to change the scope of the architect’s work. He/she is not any more a passive tool user instead, became a casual tool developer. Conventional CAD systems that focus on geometric representation of a designed artifact, are transforming into systems in which the design is represented as a parametric process. By increasing utilization of these systems in architectural design process, parametric modeling is integrated not only as a new medium of design representation, but also as a design method. Designing the design implies designing the design procedure on geometric and on procedural level. Parametric methods […]

Here are three technical tips, that might help you model in Rhinoceros faster. Please note that, in most cases, you’ll find CTRL+F1,F2,F3 and F4 very helpful in modeling and transforming objects in digital space. These key combinations will focus you on Top, Front, Left and Perspective views (maximized) respectively. Also, when you try to express your design process (especially supporting geometries) using different linetypes, it’s possible that you’ll never like those preset linetypes. By choosing Tools / Options, you’ll have the opportunity to change and add new linetypes at “Linetypes” tab there. Just play […]

Here are the files of first week. Course introduction (English / Turkish) and first homework assignment. Today, we’ve seen examples and some basic techniques regarding the main concepts of design computing. Tried to create our first associative systems using recording history of events in Rhinoceros. First homework is design of an animated form, simulating the geometric and topological behaviour of a reptile skin. It is a component-based form-finding exercise, introducing some of the principal concepts of associative geometry and recursive [history-enabled] design process. You’ll analyse the formation of a reptile’s skin pattern, and try to […]

That was about six months ago, our study for a design competition required a spatial allocation algorithm. An office building with a rectangular plot and a strict functional requirement forced me to the good old voronoi diagrams, subdividing a surface. Here is the definition file: [GHX: 0.8.0066]. However, there were other design parameters such as the sunlight and orientations of each functional cell. Combining a couple of graph components helped me to create diverse solutions, that are later used in functional-formal interpretation phase. Unfortunately later on, the competition cancelled and this […]

This is the old-method Parametric Truss definition. Interestingly this quickly became a solid solution, used and taught for years. I couldn’t find a better answer yet. As Grasshopper updates, some of the components in this definition change but overall structure remains. Subdivision of a free-form surface and addition of geometric components has, of course a wide range of alternatives. Maybe we should combine this with different problems and solutions we’ve talked about earlier in this website. Here are the geometric model and parametric definition files. [3DM: truss] [GHX: 0.8.0066] The same solution can […]

[GHX:0.8.0066] This is a rather traditional geometry exercise we used to make in MaxScript. Grasshopper is also quite capable of associative geometry and real-time parametric designs of objects. Exercise of designing a furniture family should be based on a design research, followed by the shape alternatives and sketches (both digital and hand), then might be finalized using this parametric design environment. However, the example presented here is one of the most simplistic solutions to a furniture familly. This may be furter developed regarding details and diversity of geometry.