d the workshop PDF from this link: http://goo.gl/bcvRNH Download event poster from this link: http://goo.gl/Q0KWCM Brief: Cairo is filled with barriers controlling people movements, suppressing them as well as detaining green and public spaces to the extent that most people have been taking these spaces for granted. Public spaces have been for a while the periphery of our daily life. We will explore in this workshop how we can manipulate and alter people’s perception and direct their attention to how these spaces are integral for city life. This exploration will be backed up by intensive technical tutorials introducing computational design and fabrication techniques and tools mainly Rhino, Grasshopper, Geco and Ecotect. Not only will this be the typical technical workshop, but rather you will also have the chance to be guided step by step on how these tools are used through out different design stages in a real world scenario. Design prototypes will be produced through 3D printing, the main workshop output will be a fabricated one to one functional model for one of the designs using our new in-house CNC machine. Tutors (check the PDF for bio): Olga Kovrikova, MArch DIA Alexandr Kalachev, MArch DIA Karim Soliman, MArch DIA Islam Ibrahim, MArch DIA Sherif Tarabishy, B.Sc. AAST Application: Application deadline 1 September 2013 ** For students (undergrad / Master), teachers and PhD proof of status is required (university ID with a date or a certificate of enrollment) to apply for the students package. Packages (choose one of the following in the application form): 1. Standard registration Course fee is 4250 EGP For Students 3500 EGP 2. Early bird registration discounted fee For Professionals 3750 EGP For Students 3000 EGP ** Early bird offer ends on 14 August 2013 3. Group registrations discounted fee (5 or more) For Students 20% off - You will have to fill out an application form here: http://goo.gl/0QxAga - You will need to submit your CV and Short Portfolio (max. 10 MB) to info@morph-d.com, email subject: “Morphing Norms Application” (we will decide if you are eligible for an early bird discount or not based on the date of your email submission) - We will confirm receiving emails from all applicants. Successful applicants will be contacted 5 days after each deadline (early bird/final) and will have to confirm participation within 3 days, if they fail to do so, places will be given to others on the waiting list. - A maximum of 30 applicants will be selected.
…
ow..
It's basically using a 3d framework to define points on the framework and then interpolate curves through them.
Right now Im assuming that I merely translated something incorrectly early in the script that lead to most of the definition issues later on...?? It also seems I am not using the append function correctly... :(
If anybody well versed could take a look it would be awesome... :)
The code I've used is below and the erros I get are attached here:
Private Sub RunScript(ByVal ptSetA As List(Of Point3d), ByVal ptSetB As List(Of Point3d), ByVal divU As Integer, ByVal divV As Integer, ByRef A As Object, ByRef B As Object) Dim n As Integer = 0 Dim ptListA As New List(Of list(Of Point3d)) Dim ptListB As New List(Of list(Of Point3d)) For i As Integer = 0 To divU Dim ptRowA As New List(Of Point3d) Dim ptRowB As New list(Of point3d) For j As Integer = 0 To divV Dim ptA As New Point3d(ptSetA(n)) Dim ptB As New point3d(ptSetB(n)) ptRowA.Add(ptA) ptRowB.Add(ptB) n = n + 1 Next ptListA.Add(ptRowA) ptListB.Add(ptRowB) Next Dim intcvListA As New List(Of NurbsCurve) For i As Integer = 0 To divU - 1 Step 2 For j As Integer = 0 To divV - 1 Step 1 Dim pt01A As New point3d((ptListA(i)(j) + ptListA(i)(j + 1)) / 2) Dim pt01A As New point3d((ptListA(i + 1)(j) + ptListB(i + 1)(j)) / 2) Dim pt01A As New point3d((ptListA(i + 2)(j) + ptListA(i + 2)(j + 1)) / 2) Dim pt01A As New point3d((ptListA(i + 1)(j) + ptListA(i + 1)(j + 1)) / 2) Dim dis01A As Double = pt01A.DistanceTo(pt04A) Dim dis02A As Double = pt03A.DistanceTo(pt04A) Dim vt01A As New Vector3d((pt04A - pt01A) / dis01A) Dim vt02A As New Vector3d((pt03A - pt04A) / dis02A) Dim pt01B As New point3d((ptListB(i)(j) + ptListB(i)(j + 1)) / 2) Dim pt01B As New point3d((ptListA(i + 1)(j) + ptListB(i + 1)(j)) / 2) Dim pt01B As New point3d((ptListB(i + 2)(j) + ptListB(i + 2)(j + 1)) / 2) Dim pt01B As New point3d((ptListB(i + 1)(j) + ptListB(i + 1)(j + 1)) / 2) Dim dis01B As Double = pt01B.DistanceTo(pt04B) Dim dis02B As Double = pt03B.DistanceTo(pt04B) Dim vt01B As New Vector3d((pt04B - pt01B) / dis01B) Dim vt02B As New Vector3d((pt03B - pt04B) / dis02B) Dim ptArrA As New List(Of Point3d) ptArrA.Append(pt01A) ptArrA.Append(pt02A) ptArrA.Append(pt03A) Dim intcvA As New NurbsCurve() intcvA = CreateInterpolatedCurve(ptArrA, 3) intcvListA.Add(intcvA) Dim ptArrB As New List(Of Point3d) ptArrB.Append(pt01B) ptArrB.Append(pt02B) ptArrB.Append(pt03B) Dim intcvB As New NurbsCurve() intcvB = CreateInterpolatedCurve(ptArrB, 3) intcvListB.Add(intcvB) Next Next A = intcvListA…
eroberfläche des Grasshopper Programms
Funktionsprinzip eines grafischen Algorithmus-Editors (Datenfluss)
Unterscheidung von Parametern (Datentypen) und Komponenten (Datenverarbeitung)
Erzeugung, Bearbeitung und Analyse von Geometrie-Typen: Punkte, Vektoren, Linien, Kurven, Flächen (surfaces, brep) und Netze (meshes)
Strukturierung der Daten anhand von Listen und Bäumen
unterschiedliche Verknüpfungsmöglichkeiten von Parametern (data matching)
praxisnahe Grundlagen der Geometrie und Vektorrechnung für generatives Design
effizienter Aufbau von parametrischen Modellen anhand Übungsaufgaben
Auszug von Daten aus Modellen für die Fertigung; Daten aus Tabellen (Excel, CSV) importieren, exportieren
Einsatz von benutzerdefinierten Komponenten (custom components)
Vorkenntnisse: Rhinoceros3d Benutzeroberfläche der Software: Englisch Unterrichtssprache: Deutsch
Details und Anmeldung:
www.vhs-sha.de
click: SUCHE
Kurstitel: GRASSHOPPER
(auch: Kurstitel: RHINO)
Trainer: Peter Mehrtens
Kursdauer: 3 Tage / 8 Stunden pro Tag
Donnerstag, 19.07.2012, 08:00-17:00 Uhr Freitag, 20.07.2012, 08:00-17:00 Uhr Samstag, 21.07.2012, 08:00-17:00 Uhr Ort: Volkshochschule Schwäbisch Hall, im Haus der Bildung
Teilnahmegebühr: 299,00 € Teilnehmerzahl: 5-10 Personen
…
0.1 Webinar introduction0.2 Installation of Ladybug for Grasshopper (+Rhino)0.3 Getting started with Ladybug for Grasshopper (+Rhino)0.4 Introduction to Environmental Design Analysis - process and methodology_STEP 1 CLIMATE ANALYSIS (NO MODEL)1.0 Introduction to Climate Analysis1.1 Finding and importing weather data file1.2 Sun Path1.3 Temperature chart1.4 Humidity chart1.5 Wind Rose1.6 Comfort Analysis based on weather data1.7 Psychrometric Chart1.8 Bioclimactic Chart1.9 Customizing Analysis Period and Charts_STEP 2A ANALYSIS OF EXISTING URBAN SPACES (WITH MODEL)2a.0 Introduction to Analysis of existing Urban Spaces2a.1 Import Context models from Rhino2a.2 Radiation Rose2a.3 Solar Fan / Envelope_STEP 2B ANALYSIS OF NEW URBAN SPACES / DEVELOPMENT (WITH MODEL)2b.0 Introduction to Analysis of new Urban Spaces2b.1 Import new Urban Buildings and/or Elements from Rhino2b.2 Parametric Grasshopper models 2b.3 Radiation Rose-------------------DANIEL NIELSENThe Danish architect Daniel Nielsen has a broad experience with Architectural Sustainability and the integration of parametric 3D modeling and simulation tools into the process. He have worked on projects at various scales - from buildings to planning, and have been involved in research and education programs at The Royal Danish Academy of Fine Arts and Technical University of Denmark.…
essarily architectural. As you can guess from the tone of my previous response, I finished with school and had a hard time finding a job that focused on the technologies I delt with all through undergrad and grad. During grad school I was working with ASGvis (the makers of V-Ray) so I got exposed to the software side of things both on the support/management side and the development side. Now I'm off on my own doing development projects like RhinoHair, a few others, and some custom plugins for clients. Not necessarily what I thought I'd be doing after grad school, but I'm certainly enjoying it more than the "standard" practice of architecture.
I definitely understand "creating" a program. I did both my undergrad and grad at Catholic U here in DC, and although there was some ground work laid in regards to fabrication, I was one of only two or three students spearheading a lot of the scripting/GH/parametric stuff and some of the topics that go along with them (algorithmic design, adaptive systems, advanced geometry). One thing that was incredibly helpful for me was to pair up with the most advanced and forward thinking professor(s) that you can and take their studios, electives, and/or help out with their research. I was lucky enough to pair with a professor who had been at MIT and really encouraged me to explore my interests and sharpen my technicial skills.
It might also be a good idea to stick your head in some other departments, probably the math and engineering ones, or even biology and economics if there are some forward thinking professors. Talk to some people and get a different perspective on things. When I went to the ACADIA conference in 2008 it really opened my eyes to some of the potential influence from those different arenas.
Fabrication wise, I'd really try to focus more on milling (3 axis is fairly standard, 5 axis if you can get access) than 3d printing. Printing is a lot of fun, but ultimately we're not printing buildings (yet), so some of the milling processes will be much more valuble. If your school doesn't have those kind of facilities on campus (either in the Arch dept or engineering or something), then contact a local fabricator and see if you can work together somehow or someway. You'd be surprised and how many fabricators are interested in talking to architects.…
Added by Damien Alomar at 3:13pm on February 8, 2010
, and it was only devised for triangular faces:
I could track all my edge labels (via the neighboring cell discussion) but from that info (the pesky tree) I needed unique face pairs to output a single crease angle.
Now (with your scripted component) I have the crease angles. All the 3D text is temporary for trouble shooting. This is 3 faces from a dodecaheadron:
So now I have the remaining hurdle as to whether the proper crease angle is the GH angle or the GH reflex angle.
The funny thing with the "pesky tree" is the meaning of the pattern doesn't become apparent until it's more complicated than the simpler excerpt from above.
I think I could make the scripted component a little cleaner if I use some nested loops instead of your search and remove method, but that may take me a while.
But it all the fun comes from this guy:
…
...hmm... points across the facade edges are not included (or may be some) and thus the whole thing is the art of pointless.
2. See the 1a unfinished part ... that defines internal boundaries for that purpose - then you need to create points across the edges, random reduce them and merging the list with the other points...blah blah.
3. That way each facade could yield structural members that touch the edges (where the biggest HEB/columns are expected to be). Obviously nodes are shared between facades with a common edge - the best logical approach for obvious real-life reasons.
4. The whole approach is stupid : here we need some Hoop snake "loop" control (that could take into account the critical connection angle constrain) in order to achieve a "progressive" deployment of the diagonal members in order to satisfy structural requirements and ... hmm...aesthetics. Free espresso for everyone is an added bonus.
5. Bottom to top design mentality is urgently required here: mastermind some 3d conceptual arrangement of nodes keeping in mind ... well...just 345,67 different real-life factors (but you could combine insulation and fireproofing if you use my favorite material: Foamglas - name with with one "s"). That way you can define the critical deployment planes : i.e. diagonal rigidity members, some facade aluminum system and floor main perimeter I-Beams MUST be in different planes.
I'll be back with a more stupid version of that thing.
may the Force ...blah blah
…
ed many inverted normals, holes, bad edges, intersecting mesh faces etc and couldn't really find a good fix for all the issues.
3. I imported the file again and tried the mesh offset to thicken it just by 1mm. It gets a reasonable result but still has errors where the offset creates intersecting mesh faces. The result looks better than the Rhino offset mesh and looks like it might actually stand on a table. It was a 53Mb STL file!
Unfortunately I do not have the Objet software on my laptop otherwise I would have tried to prep it for 3d printing but I have a feeling any slicing software will struggle to process this mesh and it would be quite an expensive risk to try and print it as is.
You might be able to take the thickened mesh and cut away at the problem areas, then manually tidy up the holes created but this would be a long, manual process.
I also tried a 2mm offset but this was less successful... I think what is really needed is a sort of intelligent offset whereby in areas where the offset creates intersecting mesh geometry, the offset is smoothed off in the intersecting areas. Sorry... no idea how you could do this.
Do you want me to upload the 53Mb STL somewhere? Can I upload it to your dropbox?
Do you want me to upload the 53Mb STL somewhere? Can I upload it to your dropbox?…
Added by martyn hogg at 2:41pm on November 24, 2014
ngy (as stand alone product). But on the other hand it's widely used and is the "standard" seed for cultivating the new generations. With this in mind I rate it ... er ... hmm... higher than Generative Components. Because GC (and the ParaSolids 3d kernel that derives from Siemens/NX) may be mighty (if we forget this, this and that, he he) but is almost totally inaccessible: requires several years of training and then ... yes ... it can eat GH for breakfast as regards AEC matters (but this IS NOT the point, nor it means that GH is "worst").
The analogy is: GH is like my FireBlade (homogenous, easy) and GC is like my Panigale (lethal if not treated properly). On the other hand Honda cells 100 times more Blades than Ducati Panigales.
2. This cultivation thingy is/was NEVER understood by Bentely Systems (I had some very nasty Skype sessions on that matter, he he).A critical mistake that one, but then again Bentley doesn't like going to bed with individuals and ... maybe ... they are in the right path (a bit hilly, he he).
3. Dynamo on the other hand ... well I'm a Bentley Systems man so "by default" I dislike AutoDesk products and/or bought ones (TSplines excluded). But humor apart ... I dislike Revit for a vast variety of reasons the primary being the approach for effective parallel/team work. AECOSim on the other hand is brilliant on that matter. But Revit is dangerously close to become the BIM standard (which means - by default - that's the wrong thing).
4. Thus ... are R/GH in danger for playing a role in real-life AEC? Well ... if there was not the cultivation thing ... maybe.
In conclusion: In Planet Zorg this is the way to do AEC stuff: GH (scripts only) + GH add ons (if required) + GC (works only with scripts anyway) + AECOSim + you name it + CATIA/NX + you name it.
Moral: A classic Alice in the wonderland case that one: i.e. an amoral one, he he
take care, Jack the Ripper…
. and the bad habits die last as they say. This means that ... well ... the adaptation to more realistic (and meaningful) things later on ...
3. I can easily provide some solution (ultra expensive in real-life) to do what you want but this would be carried over solely via C# code (NOT good for you especially when this would/could be used in some sort of Thesis). To make a very long story short the "curvy" parts is highly recommended being tubes ... and the "liquid" nodes required ... well ...that's another animal UNLESS one could accept an Academic over simplification by using balls of a slightly bigger R than the adjacent tube "struts" (whilst the "iso curves" [per BrepFace] would use an even smaller R and inserting crudely into the Brep Edge "main" curves). But since actually we are talking about a secondary random "lattice" per BrepFace the "iso curves" are actually stuff made via the Surface.ShortPath Method (not sure if this exists as GH component) using random points where their number is proportionally to a given BrepFace area (freaky stuff, trust me). This yields a "uniform" random secondary "lattice" in accordance to the whole "random"/liquid appearance of the T-Splne Brep.
The above a bit naive approach (obviously out of question in real life) can yield a solid thingy if we unite all the parts and bits (Rhino takes ages to do that if we are talking big numbers of Breps) ... thus some 3d printing is doable.
In other words we do a MERO "approximation" by hoping that no German guru reads this thread, he he.
We can provide a Frankenstein type of "pro" connectivity as well: since a Brep is actually kinda a Mesh (with regard connectivity of vertices, edges, faces et all) making the connectivity trees required is not a big deal (GH has the Brep Topology thingy as well).
But the whole solution could be a black box to you: if this what you want?…