Pratt | Digital Futures Group

Check out Lalaj & Rudi’s (carvalho) tiling pattern implemented in Grasshopper.  Things got a bit sticky, and we ended up with a big fat script node to do the bulk of the work, but the results are pretty good for an early-semester swipe at a corrugation.

Notice that sweet, sweet sectional variation.

Links below to source files.

090224_lalaj_rudi_b.ghx |  090224_lalaj_rudi.3dm

Attached is my first real attempt at Grasshopper, and I have to say that I’m optimistic about the possibilities of combining a scripted approach with the user interface of grasshopper.  It was my intention here to try out the scripted methodology that we’re employing in the third year long span studio, and see how applicable it might be to the parametric environment of Grasshopper.  I was trying to be as flexible as possible – the user can define any number of points within a bounding box (both controlled by rhino geometry, see attached 3dm) as a unit “cell”, which is then arrayed in a rectangular grid.  Linear transformations may then be applied, and altered using Grasshopper’s nifty Graph Widget.  It’s a pain dealing only with one-dimensional arrays of things, but a few scripted nodes does the trick.

090220_planar_tiling_g.ghx |  090220_planar_tiling.3dm

babko_rossi_090219_a |  babko_rossi_090219_b |  babko_rossi_090219_c |  babko_rossi_090219_d

Three very similar variations on a script written for Babko and Rossi in Richard Sarrah’s class.  These scripts create a truss-like 3d pattern, with increasingly complex math-driven variations.  They rely on 4 methods to do the bulk of the work, described below.  3dm files which explain weaving are attached.

babko_rossi_iterations.3dm |  babko_rossi_geomdef.3dm

the function DrawTetraMatrix, …

the function tetraPostProcess, …

the function Main, …

the function tetraGridPts …

the function tetraCellPtsA, …

the function tetraCellPtsB, …

abbe_bernal_090216_a

abbe_bernal_090216_b

abbe_bernal_090216_c

Three very similar variations on a script written for Abbe and Bernal in Lonn Comb’s class.  These scripts create a truss-like 3d pattern, with increasingly complex math-driven variations.  They rely on 4 methods to do the bulk of the work, described below:

the function HynetCellPts, creates a collection of four points which makeup the basic module of a truss… it doesn’t draw anything to rhino, it just creates the points (as data) at a given location, and stores these points in an array.

the function HynetGridPts, calls upon this previous function, and creates a grid of modules at a particular scale and spacing…. again, it doesn’t draw anything, it simply creates the points and stores them in an array in a structured manner.  can you figure out the structure of this array, and draw it in monkeybrainland?

the function Main, calls upon this previous function, and creates two grids of module points – one slightly higher than the other: arrPtsTop and arrPtsBtm.  again, nothing is drawn to rhino, but the critical positions for the truss are figured out here and stored in two arrays.  Then, finally, at the end of this function, the final method is called which draws elements to rhino based on these two arrays.

the function DrawHynetMatrix looks like the most complicated function in the lot, but in reality it’s job is the simplest.  based on two arrays of module points (defined in functions above), this function draws the desired geometry to rhino.  there’s alot of “weaving” going on here – figuring out which point on one module to connect to which point on the next – but conceptually, things are very straightforward.