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?…
was not all there myself. Overall the night wasn't that productive so I wanted to apologize, I will do a better job in the future.
Attached to this message is the Assignment sheet for the upcoming week. Please post the picture of the models before 7:00 PM Monday 2/16.
Here is a link to the completed script from last night, as well as the Rhino file and presentation pdf.
https://www.dropbox.com/sh/3g6fnue93dk8iub/AAB88CNVCtC64cmz_ENLlojQa?dl=0
A few notes:
- I added two separate tags to the end of the script. One set is for the 3D model of your form, locating where the pieces originally come from. The second set is for the flattened out sections, which can be etched on your pieces to actually locate them when they are physically created. Play around a bit in the script and try to understand what is going on between the different parts.
-Baking: We went over baking in last weeks class. You right click on the component you want in the physical realm and select bake. Rhino will then ask you to select a layer to place the items on. I would suggest having two layers, one will be for cutting and one will be for etching (when you bake the tags(optional)). Once the pieces are in Rhino, you can use the Make2d command and export to AutoCad where you can laser cut (if you are unsure about this process, Google it as there are numerous tutorials).
-I would recommend using chipboard as it is the cheapest and most readily available, but don't let me chain your creativity if you come up with another material.
I look forward to seeing your guys models. See you Monday!
…
pavilion) and from that i want to fabricate it using some paper or card bored .
for modeling the pavilion i used a simple kangaroo based algorithm to generate the desired form using mesh 3d plane faces . there was no problem with this part and i was able to get the mesh from geometry out put . then i wanted to use that output mesh to panelize it and then adding tabs and the nesting and cutting to get the parts. but the problem was every tutorial i looked up were using surfaces to panelize and nest so this was the first problem to convert the mesh into a surface and then panelazing and nesting . i tried using the mesh2nurbs but it didn't work out for me . (because i needed a single surface not some poly surfaces) . (attachment | input mesh )
so i started from the beginning and tried using a surface as an input for kangaroo and thus getting a surface as an output so i did that and tried to create a surface by the Surface from points component . and the result was not good the surface was kinda messed up and the the reason was the points were not ordered well i guess . so this was another problem for me . (attachment | input surface)(picture below)
so basically i have a few main questions :
1. is there a tutorial or any topic or book or somthing that explains from 0 to 100 from design to fabrication (as an example a pavilion) ?
2. can i use the mesh to panelize and nest and then fabricate ? and are there any tips or tricks to it ?
3. is the starting from surface for me a good idea or not ?
i am extremely sorry for talking this much and i'm grateful for the time you spent on reading this .
best wishes ; Babak.
…
actually can perform using a dedicated software:
in 3D:
https://www.facebook.com/francescopiasentini/videos/523532707845171/
in 2D:
https://vimeo.com/189618609
The output of Modal Analysis (at a given frequency) is a list of point (x,y,z), each of them has the three coordinates and the maximum displacement in the direction normal to the surface (that's not flat)
Point number x y zmax1 24,007565 337,876028 -0,6545572 -28,0404705 337,947773 0,7760153 57,141457 316,757768 -0,8413914 18,667466 314,814543 -0,235288
My idea is:
-import stl surfaces of the object (violin)
-import Modal Analysis data
-deform stl (or Nurbs) surfaces using something like a customized CageEdit
-animate this deformation from zero to maximum displacement
-give a color to deformation (or first-second derivative of the interpoled deformation curves)
My wish is to have closed surfaces at any steps, and to create "natural" deformation shapes.
I just tried to import MA data. I was trying to create an array of circles with given x,y,z and radius, I could not figure how to separate information of position and radius when importing the file:
file content:
0,1,0; 5;2,1,3; 2;5,2,6; 4;
thanks for yout attention.
Looking forward to hear you soon!
Francesco
…
esos de diseño, el curso cubrirá los conceptos básicos para abordar proyectos de diseño a través del desarrollo de herramientas algorítmicas mediante un proceso de programación visual, se utilizará el software Rhinoceros 3d y el plugin Grasshopper como nuestras herramientas de trabajo.
Detalles:
Instructores: Luis de la Parra / Daniel Camiro
Lugar: Santiago centro
Ahumada Nº312 oficina 108 entrepiso, Santiago Centro (a una cuadra de metro plaza de armas).
Fechas: 27-30 de octubre 2011
Duracion: 25 horas
Cupo: Limitado a 15 plazas
Costos:
Estudiantes:$80,000
Profesionales:$100,000
Fecha limite de pago: lunes 24 de octubre 2011
Importante:Todos los niveles de experiencia son bienvenidos el único requisito es tener un entendimiento básico de los programas CAD y una actitud positiva hacia el aprendizaje de dichas herramientas.
Si planeas venir de fuera de la ciudad avísanos y te pondremos en contacto con otras personas que también vayan a hacerlo para en caso de desearlo puedan compartir su lugar de estancia.
Contacto Santiago:
Luis de la ParraCel: 714-660-33info@chidostudio.comhttp://www.facebook.com/pages/Chido-Studio-Collective/233962149953480
No. Cuenta de Ahorro de Banco Estado : 00169946655
Para hacer transferencia bancaria favor de enviar mail solicitando los datos necesarios. Favor de mandarnos el deposito (scaneado) o el comprobante por mail para que recibas más información del curso y del tema a info@chidostudio.com
Todos los mails se responden en un máximo de 24 horas.
Muchas gracias por tu interés saludos
…
Added by daniel camiro at 10:48am on September 5, 2011
Introduzione a Grasshopper", il primo manuale su Grasshopper.
.
I corsi PLUG IT nascono dalla volontà di promuovere le nuove tecnologie digitali di supporto alla progettazione e condividere il know-how maturato attraverso ricerca, collaborazione con i più importanti studi di architettura e pubblicazioni internazionali.
.
Verranno introdotte le nozioni base di Grasshopper approfondendo le metodologie della progettazione parametrica e le tecniche di modellazione algoritmica per la generazione di forme complesse. Il corso è rivolto a studenti e professionisti con esperienza minima nella modellazione 3D e si articolerà in lezioni teoriche ed esercitazioni.
. Argomenti trattati:
- Introduzione alla progettazione parametrica: teoria, esempi, casi studio - Grasshopper: concetti base, logica algoritmica, interfaccia grafica - Nozioni fondamentali: componenti, connessioni, data flow
- Funzioni matematiche e logiche, serie, gestione dei dati - Analisi e definizione di curve e superfici
- Definizione di griglie e pattern complessi - Trasformazioni geometriche, paneling - Attrattori, image sampler
- Data tree: gestione di dati complessi - Digital fabrication: teoria ed esempi - Nesting: scomposizione di oggetti tridimensionali in sezioni piane per macchine CNC
.
Verrà rilasciato un attestato finale.
.
Ulteriori info e programma completo su: www.arturotedeschi.com e su www.samilolab.it…
n complex architectural design and fabrication processes, relying heavily on materiality and performance. The programme brings together a range of experts – tutors and lecturers – from internationally acclaimed academic institutions and practices, Architectural Association, Zaha Hadid Architects, among others.
Taking place at the unique atmosphere of AA’s London home, the three-week long programme is formulated as a two-stage process. During the initial stage, participants are introduced to core concepts related to material processes, computational methods, and various digital fabrication techniques. During the second stage, the fabrication and assembly of a full-scale architectural intervention with the use of robotic fabrication techniques unifies the design goals of the programme.
Prominent Features of the programme:
• Teaching team: Participants engage in an active learning environment where the large tutor to student ratio (5:1) allows for personalized tutorials and debates.
• Facilities: AA Digital Prototyping Lab (DPL) offers laser cutting, CNC milling, 3d printing facilities, and 2 KUKA robotic arms.
• Computational skills: The toolset of Summer DLAB includes but is not limited to Rhinoceros, Processing, Grasshopper, and various analysis tools.
• Theoretical understanding: The dissemination of fundamental design techniques and relevant critical thinking methodologies through theoretical sessions and seminars forms one of the major goals of Summer DLAB.
• Professional awareness: Participants ranging from 2nd year students to PhD candidates and full-time professionals experience a highly-focused collaborative educational model which promotes research-based design and making.
• Robotic Fabrication: According to the specific agenda of each year, scaled working models are produced via advanced digital machining tools, followed by the fabrication of one-to-one scale prototypes with the use of KUKA KR60 and KR30 robots.
• Lecture series: Taking advantage of its unique location, London, Summer DLAB creates a vibrant atmosphere with its intense lecture programme.
Eligibility: The workshop is open to architecture and design students and professionals worldwide.
Accreditation: Participants gain 1 Year AA Visiting Membership and are awarded AA Certificate of Attendance at the successful completion of AA Summer DLAB.
Applications: The AA Visiting School requires a fee of £1900 per participant, which includes a £60 Visiting Membership fee. Discount options for groups are available. Please contact the AA Visiting School Coordinator for more details.
The deadline for applications is 17 July 2017. No portfolio or CV, only requirement is the online application form and fees. The online application can be reached from:
https://www.aaschool.ac.uk/STUDY/ONLINEAPPLICATION/visitingApplication.php?schoolID=460
For inquiries, please contact:
elif.erdine@aaschool.ac.uk (Programme Head)
alexandros.kallegias@aaschool.ac.uk (Programme Head)…
, Engineer and Researcher from France with broad programming experience. He is the author of the City in 3D Rhinoceros plugin for creation of buildings according to geojson file and with real elevation. Guillaume already created a new component: "Address to Location". It enables getting latitude and longitude values for the given address:
2) Support of Bathymetry data: automatic creation of underwater (sea/river/lake floor) terrain. This feature is now available through new source_ input of the "Terrain generator" component. Here is an example of terrain of the Loihi underwater volcano, of the coast of Hawaii:
3) A new terrain source has been added: ALOS World 3D 30m. ALOS is a Japanese global terrain data. Gismo "Terrain Generator" component has been using SRTM 30m terrain data, which hasn't been global and was limited to -56 to +60 latitude range. With this addition, it is possible to switch between SRTM and ALOS World 3D 30m models with the use of source_ input.
4) 9 new components have been added:
"Address To Location" - finds latitude and longitude coordinates for the given address.
"XY To Location" - finds latitude and longitude coordinates for the given Rhino XY coordinates. "Location To XY" - vice versa from the previous component: finds Rhino XY coordinates for the given latitude longitude coordinates. "Z To Elevation" - finds elevation for particular Rhino point. "Rhino text to number" - convert numeric text from Rhino to grasshopper number. "Rhino unit to meters" - convert Rhino units to meters. "Deconstruct location" - deconstructs .epw location. "New Component Example" - this component explains how to make a new Gismo component, in case you are interested to make one. We welcome new developers, even if you contribute a single component to Gismo! "Support Gismo" - gives some suggestions on how to make Gismo better, how to improve it and support it.
5) Ladybug "Terrain Generator" component now supports all units, not only Meters. So any Gismo example file which uses this component, can now use Rhino units other than Meters as well. Thank you Antonello Di Nunzio for making this happen!!
Basically just forget about this yellow panel:
This panel is not valid anymore, so just use any unit you want.
6) A number of bugs have been fixed, reported in topics for the last couple of weeks. We would like to thank members in the community who invested their time in testing, finding these bugs and reporting them: Rafat Ahmed, Peter Zatko, Mathieu Venot, Abraham Yezioro, Rafael Alonso. Thank you guys!!! Apologies if we forgot to mention someone.
The version 0.0.2 can be downloaded from here:
https://github.com/stgeorges/gismo/zipball/master
And example files from here:
https://github.com/stgeorges/gismo/tree/master/examples
Any new suggestions, testing and bug reports are welcome!!…
Added by djordje to Gismo at 5:13pm on March 1, 2017