ipants from 12 countries to attend lectures and technical seminars furthering their understanding of digital design and fabrication in architecture. This year LaN extends the workshop with parallel intro sessions in all LAN ports–Barcelona / Boulder / Brooklyn / Bozeman (Aug 10-12). In 2009, you choose your modules.
Register Online
*please note, participants who have previously attended a LaN workshop automatically get a discount of total price.
Key Dates:
June 1, 2009: Workshop Launch - Applications Open @ 10% off price
June 19, 2009: Workshop Applications Open at 5% off
July 10, 2009: Applications open
August 7, 2009: Applications Closed
August 10-12, 2009: PHASE I - Modules [North America and Barcelona]
August 16-22, 2009: PHASE II - Modules [Barcelona @ IaaC / Institute for advanced architecture of Catalonia ]
August 24-30, 2009: PHASE III - Urban Drifts Workshop [Barcelona @ IaaC / Institute for advanced architecture of Catalonia]
*please note: all Rhino courses will be taught by a Rhino Certified Trainer
PHASE I: Aug 10-12
Phase I will be conducted in parallel in BARCELONA / BOULDER / BROOKLYN / BOZEMAN and are meant to familiarize participants with software and techniques. Phase I registration is inclusive of both module 1 & 2.
1. Rhino Introduction - 12hrs
2. RhinoFab: Rhino + Fabrication - 12hrs
PHASE II: Aug 17 - 22
Phase II modules will take place at the Institute for Advanced Architecture of Catalonia [IaaC] in Barcelona, Spain and will deal with scripting, parametric design and fabrication provided by FabLab BCN.
3. RhinoScript - 20hrs
4. Parametric Modelling in Rhino: Grasshopper - 20hrs
5. Introduction to Digital Fabrication - 20hrs
6. Machining Processes- 20hrs
PHASE III: Aug 24-30 ‘Urban Drifts’ Workshop - 40hrs
Register Online
Contact: bcn2@livearchitecture.net
More Information: http://www.livearchitecture.net…
oks like the design in the following images:
Concept Images:
Shape:
Design_Request.pdf CR_tower_shape.ghdiagrid.gh
Shape Routine:
Diagrid Routine:
Example and Inspiration:http://www.solaripedia.com/images/large/4226.jpg
Goals:
The goal is to create a grasshopper routine that recreates a modifiable design concept as shown in the concept images. The following parameters should be modifiable
1) The size and elevation of all the basic triangles, circles and the ellipse.
2) The elevation and shape of the opening and the shape and size of the three legs.
3) The shape of the crown. The angle of the tilted ellipse.
4) The loft shape between the edges.
5) The grid size (U,V) of the diagrid.
6) The size of the 2 pipes used for the structure.
Rhino Grasshopper Workflow:
I attempted Boolean difference of a solid (Brep) and the surface in question to create the opening in the surface as shown above but that did not work. What should i do to recreate the concept in grasshopper ? I would appreciate any feedback and advice. Thank you very much !
-Christoph AKA Stoph
…
will cover one of the latest and greatest topics from recent development. Although the webinars will be happening each Thursday around 12:30 Eastern Standard Time, registration will give you indefinite access to recordings of the webinars so that you can reference them when the time comes to apply them on your work!
The grand list of workshops is as follows:
1 - High-Quality Graphics, Visualizations and Animations with LadybugMarch 9th, 12:30 PM EST
2 - Brute Force Parametric Energy Modeling and Sensitivity Analyses in Early DesignMarch 23rd, 12:30 PM EST
3 - Wintertime Indoor Thermal Comfort Visualization - Eliminating Perimeter Heat with High-Performing FacadesMarch 30th, 12:30 PM EST
4 - Summertime Indoor Thermal Comfort Visualization - Setpoints and Blinds Up with Right Shade + ControlsApril 6th, 12:30 PM EST
5 - Condensation Modeling with HoneybeeApril 20th, 12:30 PM EST
6 - Urban Heat Island Modeling with DragonflyApril 27th, 12:30 PM EST
7 - Expanding Your Climate Data Sources with DragonflyMay 4th, 12:30 PM EST
8 - CFD Simulation with OpenFOAM, Rhino/Grasshopper and Butterfly (Advanced)May 11th, 12:30 PM EST
This series will have a similar arc as the one in the Fall, starting with basic topics and moving to advanced ones as we progress down the list. The first one will be accessible to all users regardless of prior experience and all of the workshops listed here will cover topics for which there is currently no tutorial video content. Hope that you can attend!…
and I here is what I have to share:
Thanks! Thank you for being awesome! When I released Ladybug two years ago I could never imagine how this project will take over my life! It has been such an invaluable experience for me so far and it wasn’t possible without you - so thank you so much.
What’s next? Recently I get this question more and more and here is my fairly long answer! Chris is pushing the boundaries with comfort tools. Chien Si is working on HVAC systems integration. Chris, Anton and Alejandra will figure out how to effectively get natural ventilation to be modeled. Patrick, Sandeep, Michal and Boris are working on their developments. I’m working on getting 3 Phase method integrated, and Butterfly will be out at some point, but... they are not going to be what makes the next step. The next step is up to you. It is what you will do with the development. So go ahead and let us know what’s next!
If you can help someone on the group please do! Doing so you are not only helping another person (and potentially yourself) but also the developers. The more you can help each other here the more we will have time for development and documentation.
Best place to send your questions is this group. If you are using the latest version from github then you may want to sent it to github. Please consider emails as the last option. Go back to number 3 again! Thanks.
Don’t be nice to us! Well, I mean don’t just be nice to us. I love your nice comments like anybody else and please keep them coming ;) but what we also need next to nice comments is your critiques, wishes and insight. I feel that recently we are getting less wishes and critiques than what it used to be. You can post them here in the group or on github and either way we will know about it. Thank you to all of you who has already done this.
Thanks again! Before I let you go I want to specially thank all of you who contributed to the project by your development, thoughts and support. You are great and I can’t thank you enough.
David Weinberger in his book “Too Big to Know” says: “When an expert network is functioning as its best, the smartest person in the room is the room itself.” Reading some of the discussions on the group gives me the feeling of staying inside a smart room. Thank you and let’s keep the room growing!
Cheers,
Mostapha
PS: To avoid sending another post, I just post the updates about the two upcoming workshops here:
I will lead a workshop in LA next Friday (Feb. 6) and there is still few seats left. If you want to learn more about energy and daylighting simulation with Honeybee here is your chance. Here is more information who to register: (http://www.facadesplus.com/technology-workshops/).
Chris will lead a 3 days intense and comprehensive Ladybug and Honeybee workshop in Mexico City this March. You have probably watched Chris’s tutorials and already know what you can expect from a workshop with Chris so I don’t have to speak for that! I would take this workshop if I was around that area. If you are around Mexico City or know a friend who might be interested please let them know. Here is more information about the workshop: (https://www.facebook.com/LadyBugforGrasshopper/photos/a.442320969114095.107084.413910668621792/919318878080966).
…
ce attractors
3- Relation between mathematics and Form
4- Network surface and Paneling
5- Fabrication methods (slice3d, nesting, ...)
6- Structure and Architecture (Millipede)
7-Energy and form
8- Islamic patterns
9- Physics with kangaroo
…
s to create an "inflated" structure (by balancing unary Z+ "forces" against Spring values and ...er ... properly selected Anchors). We must anchor some vertices on a per hole basis (or not: hole up in the sky). Ditto for the outer loop. If the Anchors are wrong (or "wrong") > Adios Amigos. If no Anchors: anti gravity is finally invented (I'm working on it, mind).
3. Since this type of stuff is the "same" (cost/engineering wise) no matter what Anchors we pick (provided that the max spans fall within reasonable limits) the only thing worth mentioning is the method for picking the Anchors.
4. One of the rare cases where aesthetics are clearly rated on top of the other design constrains (the other is tensile membranes). Do that in other type of Designs and ... become ... er ... hmm ... Zaha (avoid at any cost).
5. Code is required for doing this properly (AND managing design variations; in plain English: OTHER Anchor collections, that is). Code doesn't bite. GH is made with code, you know. Code IS my responsibility not yours : just press the red button and be a happy bunny.
6. So due to this (and that) finally we have the "inflated" thingy on hand. That's the peanuts part of the equation. Doing this in real-life ... that's the tears part (and THIS also requires code, lot's if real-life is real-life).
In order to clarify things I'll provide a series of "variations" (V1, V2 ... etc) on that matter. The first WITHOUT a pro policy for picking the Anchors: that way you'll understand (gradually) why the code is a must.
But ... maybe (just maybe) I'll do some entry-level freaky stuff with code for placing humans (or cats or dogs) in your terrain (as instance definitions).…
s the "Surface Populating" definition: I manage to populate my geometry over the surface, but after I bake it, I have to delete the boxes that define my components limits as well! Is there any way of populating and baking only the chosen component, without having to delete the boxes afterwards?
Secondly:
Basically: I am trying to cover a surface with two types of components [ an open one and a closed one] , which will be proliferated over my tubular surface according to the main sunlight direction.
1. I introduce the surface component.
2. I use "Divide Interval2" in order to have division into U and V.
3. i generate the target boxes [ "surfaceBox"] .
4. I use "Isotrim" ( same intervals) and "BRepArea" to find centroid of each area.
5. My "Curve" component introduces sun angle, with its "End Points".
6. I use "Vector 2Pt" to specify sun-light direction.
7. I want to measure the angle between sun-light and the surface normals, at the position of each component; after generating the centre points, I need the normals of each centre point to get the surface's points' UV, and "Evaluate" the srf at points.
8."Angle" and "Vector" components: I use them in order to evaluate the angle between the sun direction and the srf.
9. I convert this angle to degree by using a "Function" [ to see if the angle is bigger from the max.angle or not...]
10. Function "x,y" gives me boolean data.
11. Data become "Dispatch"ed...
12. Two "Morph" components , each one linked to one part of the "Dispatch" data, generate "closed" and "open" components over the srf.
The result should have been different types of components, based on the surface's curvature, diraction and sun-light direction...
I do not understand where the mistake is in this definition...
Thx in advance1
Spyros K.…
Component its manage a CSV like a Database, i found that the csv native Python module doesn't work in IronPython cuz its compiled in PythonC (or something like this), so i found a .Net module that can be imported to IronPython to work with CSV file
So Here a
Pseudo Code of my Toughs
1 - Import .net Module.
2 - Read Csv File. by a Path Assigned by interactive Imput.
3 - Identify the Header of The Csv File.
4 - Create a List of the Fields found in the Csv Header for Further (Sorting, Retrieve specific, create relations with others files by fields in commons, etc. etc. (whatever can imagine))
5 - Read the Data of the Csv File
6 - Out put the Attributes of the Header. (simple list of the fields to identify with what we deal for )
7 - Out Put a list of all the Attributes of the Header ( Complete List of the Fields by Rows Found in the Csv File.
8 - Out Put a list of all the Data inside the Csv File in relation with the Point 7.
over here's my thoughts Any Comment or Suggetions for the Component ?
i will be posting a Github for this, to all who want to collaborate with this.
i'm doing this cuz i'm dealing with a lot of amount of data in my Thesis Project, wich its focus on managing Shapes files, and Csv Files of Data that are not in the same dataset, so i need to relationate a lot of things just to develop my examinations techniques about the city.
…
geode. The faceting system also references the original use of triangulation for mapping three dimensional landscapes.
My question responds to the need to control the edges lengths and angles within the triangles to make the process of construction possible. We are hoping to keep the edges under 28 inches and the minimum angle more than 15 degrees. What would be your suggestion in grasshopper?
Our process for getting the facet was also... the long way.
1. draw curves based on three dimension measurements of interior
2. networks surface the four curves
3. mesh surface
4. triangulate mesh
5. reduce polygons
6. splitmeshedge where necessary to make quadrilaterals triangles once more
Any suggestions?…
Added by Amanda Gann at 8:57pm on December 4, 2013
ncluding an error) but the method did not lend itself to many similar shapes, especially those that are not surfaces of revolution.
Here is a technique using Anemone that finds a solution by climbing up a path determined by a teensy-weensy semi-cone. These are the steps:
1) Define a small semi-cone having the desired slope.(base radius/height) The smaller the better but it does begin eating up computing power.
2) Place the cone at the start point and find the intersection with the surface. Since the cone is small, the curve of intersection is almost linear and at nearly the same slope as the cone. Move the cone to the end of the intersection curve, reorient it based on the surface normal at that point, rinse and repeat.
3) Continue until the intersection event gives a null. The loop outputs the end points of each little intersection curve, so at the end, the list is flattened and they are interpolated into a spiral.
In the code I included a calculation for the percentage difference between the min and max slopes calculated, using a neat technique by David Rutten and the results go from a few hundredths of a percent for a pretty smooth surface to 4 to 6 percent for something more topographical. YMMV.
Assuming your machine is as slow as mine, it's cool to watch the path climb up and around the surface - if it's not, you don't know what you're missing! but to speed things up, check ''Output After Last' in the Anemone End Loop.
…