2013 | mayo 30, 31 y 1 de junio. 15 Hrs.
Horario: 18:00 – 22.00 Jueves, Viernes y Sábado de 8:00 a 16:00 Hrs. Instructor_ Arch. David Hernández Melgarejo.
http://bioarchitecturestudio.wordpress.com
Objetivos:
El curso está dirigido a cada diseñador, ingeniero o arquitecto que quiere obtener una sólida base en modelado generativo y paramétrico dentro del flujo de trabajo en Rhinoceros.
En el curso se explorarán y construirán estructuras en el espacio paramétrico, incorporando entidades geométricas (Curvas, Superficies, Puntos, etc…) y usando patrones algorítmicos.
Cada paso será soportado con ejercicios que gradualmente incrementarán su complejidad.
El alumno aprenderá cómo trabajar con asociación geométrica y parámetros. Para perfeccionar asociación geométrica – asociación entre partes, asociación dinámica – las formas geométricas son generadas al seguir la conexión lógica entre la parte geométrica y su restricción, dimensión paramétrica y él proceso dinámico del diseño: en pocas palabras estimulamos el pensamiento relacional.
Resultados:
Los participantes con éste entrenamiento obtendrán las siguientes fundamentos.
· Construir, modificar, depurar y correr aplicaciones de Grasshopper.
· Comprender el editor gráfico algorítmico y sus patrones usando grupos y cables conectores.
· Trabajar con dimensiones dinámicas, parámetros y listas.
· Generar aplicaciones orientadas a la documentación del diseño y la fabricación.
Palabras clave:
Diseño Computacional, Scripting, Rhinoceros 5.0 + Grasshopper, Parametrización, Análisis, Fabricación Digital.
Para mayor información:
MArch. Kathrin Schröter. E-mail: kschroter@itesm.mx
Dirección de Arquitectura. Oficinas de Aulas 1, segundo piso.…
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…
rder to deal with the contents of the MERO structure (like glass, panels, polycarbonate). That is what the C# does already.
3. Vectors (a la "Umbrella" sticks) in order to place correctly your MERO nodes (the "hexagon" brackets - so to speak). That is what the big C# (the one that I've send to you some time ago) does already.
4. Calculations (lengths, angles) for each node against the other related nodes and the points derived from dividing the MERO square "tubes". For a given node these points are variable (from 2 [when in the "bounds" of mesh] to 6 ["typical" middle point, so to speak].
5. Demo block instances in order to see first hand what GH can actually do (that's WOW stuff: you slide a slider and "several" real-life components are placed in 3d space in real-time, he he).
6. Node connectivity data for the obvious (assembling the MERO on site).
7. Some assembly "simulation" capability (we do this today and this tomorrow ...)
So forget the single carrot (plenty carrots for you soon) for a while and answer to the most critical question: Based on what you've displayed to me (Skype) what is your policy against the MERO node itself?
I mean: we don't deal with a classic MERO ball type here (meaning variable drilling axis per ball). Meaning that the "hexagon" bracket (if I may use the term) IS VARIABLE. Meaning: you need a "module" that can being adapted against "every" possible (logical) angle value? (and compose the bracket?) Or you gonna fabricate the "brackets" on a per node basis?
And what if we had a planar glazing system? (same principle, more expensive, 100 times more WOW).
BTW: The best man in the world to do "similar things" with "hinged" custom aluminum systems (like doing the blue facade that you've displayed to me with some semi structural/structural system) he's a very close friend of mine. He's based in Dubai UAE.…
rder in which these polylines are drawn is not important (correct me if this is not the case).
2. We explode the polylines. This outputs all the line segments and all the endpoints (both groups with duplicates inside them). So we have 204 lines (including duplicates) and 246 points (including duplicates). We flatten both outputs in order to get 2 simple lists.
3. We use [dupPt] to remove all duplicates from the points list. So we get a list of all the nodes with each node contained one time, so we have 108 points.
3a. We can use [pointList] to display the index of each node on screen.
4. For each line segment we find the 2 endpoints and put them together in a list. So we have 204 lists with 2 points each. (We graft the list of lines so that the endpoints of each one will be in a different branch/list)
5. We use [closestPoint] and so for each endpoint we get the index number of the corresponding node. So we have 204 lists with 2 indices each.
6. We get each couple of indices and join them as text with a comma separator. (We flatten the data so that we have a single list with 204 texts)
7. BUT some of these 204 texts are duplicates (because they originate from duplicate lines), so we use [cSet] which returns the unique values from a list. So we end up with a list of 180 texts (one for each unique line). Instead of using [cSet] you could also eliminate duplicate lines using kangaroo's [dupLn] (which is the equivalent of [dupPt] but for lines) before step 4.
Hope it is more clear like this. I am not sure I understand what you mean by "But they are not connected in the order to form the tessellation.". If you still have problems with the definition please explain this a little better.
cheers, Nikos
…
requiredKeys_ input of the "OSM Shapes" component. This is not the source of your problem though, but still I mentioned it in case you solve your issue, and afterwards want to use the "OSM Shapes" component.
The current (Win32Exception): WindowsError is the very same error message that you reported back in February.For some reason, your Windows is not allowing the Gismo "OSM Shapes" component to delete C:\MapWinGIS_installation_folder\gdal-data\osmconf.ini file.
You previously solved it by allowing the full access control to it, so I am not sure why it is not working now.Windows 10 seems to be the most overprotected operating system among other Windows versions, at least judging by the questions people asked so far.
Maybe you can try to turn off all the services which prevent users from changing certain files, like UAC or maybe even your antivirus?
Try this:
1) Close your Grasshopper and Rhino.2) Restart your PC3) When it boots up again, in your Start menu's search box type: "UAC". Click on it, and a new User Account Control Settings window will open. Set the bar on the left to "Never notify".4) Completely turn off your Antivirus.5) Check once again if your access control to the C:\MapWinGIS_installation_folder\gdal-data\osmconf.ini file is still set to the values you previously reported in this post.6) Right-click on "Rhino 5" icon and then choose: "Run as administrator".7) When Rhino boots up, run Grasshopper, and open the newest create_3dbuildings_trees_streets.gh file from here.If none of this helps, maybe you have some other application which deals with access to files on your system? Malware removal application or similar? Try turning it off too.…
Added by djordje to Gismo at 9:10am on April 3, 2017
decided to concentrate my effort today on this problem and manage to come up with a solution !
I will explain it if somebody else is looking for a similar solution.
Finally my only problem was to create an alternating true/false list that inverse at certain index, this what I came up with: I have a list of points and random index , the box and sphere represent true and false, and the blue sphere is the node(index) where I want to see an inversion.
In reality, it was pretty simple, I just didn't know the right modules. (In yellow, it's the most important part of the patch)(Sorry for the spelling mistake)
Here is a diagram of what I did: I created a list going to 1 to [number of lines], here it's 1 to 10, I had node at 3-4 and 7-8. For each node I created a list of 1 repeated [(number of lines)-index] times. Here, 7 (10-3) and 3 (10-7) times.
After grafting everything, I add everything in mass addition module. I had my final list which I checked if it was divisible by two.
It was more of a logic problem than a grasshopper problem.
Here it is the initial shape with what I wanted !
…
re economical with regards to data path growth. The new logic is roughly as follows: First a master input parameter is identified. At the moment, it is the parameter with the longest path length. The amount of paths doesn't matter. Input parameters that have Tree access are never Master parameters (unless absolutely no other parameter is available) and List parameters have lower priority than Item parameters. In future versions it will probably become possible to assign a custom input as master. This however is an expert user function and I want to post-pone adding it as long as possible in order for the default behaviour to be tested and improved. If all input parameters are list parameters, output paths are no longer grown. I.e. The Reverse List component should output the exact same data tree structure as it gets. The master parameter might not be the parameter with the most branches. It is therefore possible that we run out of defined paths before the component is done computing. If this happens, the last index of the last available path in the master parameter is incremented on each iteration: Input A = {0;0} {0;1} {0;2} Input B = {0;1;0} Output C = {0;1;0} {0;1;1} {0;1;2} A has a maximum path length of 2, B has a maximum path length of 3, B is therefore the Master parameter. However we need three unique output paths since A provides three paths, so {0;1;1} and {0;1;2} are made up on the spot. It is also no longer possible to apply 'Shortest List' and 'Cross Reference' options to components. Old components that had these options set still work like they did before, but that should be considered legacy support. Instead, there are now three components in the Sets tab, List panel called 'Cross Reference', 'Short List', 'Long List' that basically provide the old functionality with a lot of additional flexibility and options.
…
e curve and uses the resulting surface/subdivisions to:
1. Smooth wall surface, varied via the Image Mapper
2. Segmented wall surface, varied via the Image Mapper
3. Populate the surface with spheres (with or without the "wall" surface)
4. Ribbed wall surface (Horizontal and / or Vertical)
5. Protrussions from the surface, driven by Image Sampler
6. Wall of Tubes, driven by Image Sampler
7. Gridded Web Surface
The options have to be enabled/disabled to achieve various results, but the idea is that this script permits a variety of looks, all in one script. See attachments at bottom.
I think this is a decent example file showing a variety of things that can be done using the Image Sampler Component in Grasshopper. This is a working version, so I am sure there are a lot better ways to achieve some of these effects. Hopefully, this will help some of you out and / or inspire some ew idea.
In the script, there is a User Object I downloaded from digitalsubstance. It is a self contained point attractor cluster, super cool, super fun. Link to the site is below.
http://digitalsubstance.wordpress.com/subcode/
If there is interest, I will update this post with an annotated version.
My blog, still in progress
http://thatsnotarchitecture.tumblr.com/
…
trying to develop it for my own project.
http://www.grasshopper3d.com/forum/topics/shortest-walk-tapered-branching-script?xg_source=activity&id=2985220%3ATopic%3A1450323&page=2#comments
On this page, he shared few 3D coral difinitions and especially interested in first and second one.
First one( bunny like 3D coral) - posted on February 2, 2016 at 9:43pm
Second one( sofa like 3D coral) - posted on February 6, 2016 at 3:16am
I followed these instructions, succeeded to build Tetgen, placed the built files in C drive directory and tried to run the definition. Then some WindowsError came out as follows which I don't know how to fix.
My working environment is;
OS is Windows 7 Ultimate 64 bit.
Rhino is version 5, 64 bit.
Grashoppper is version 0.9.0076, the latest version at this moment.
It would be great if I can have some help advice / comment.
I appreciate for your attention.
…
ou will see all of the available components on a ribbon at once so there is no need to keep clicking drop down menus.
It's all about discoverability with GH. What if you're a beginner and don't know about the Create Facility (dbl click canvas) how can you find Extr?
Even if you hover over every component or use the drop down lists you will not see the name Extr appear anywhere.
Sure it makes sense that Extr is short for Extrude but it's also the Nick Name of Extrude to Point component
So you can easily miss the fact that one has a Distance Input verses a Point Input.
I think I made the move to Icons around about the move from version 0.5 to 0.6, possibly before. I initially thought that I would go back to text because I loved the mono chromatic look of the text but I soon realised that Icons were the way forward. The greatest benefit is speed. You don't need to digest and decipher every component (which is written 90 degrees to the norm).
I'm not saying you should move to Icons forthwith but at least consider that once you have a better knowledge and understanding of GH, Icons will set you free.
My top ten tips that I would highly recommend to anyone wanting to better themselves with GH.
1) Turn on Draw Icons
2) Turn on Draw Fancy Wires
3) Turn on Obscure Components
4) Use the Create Facility like a Command Line eg "Slider=-1<0.75<2" or "Shiftlist=-1"
5) Use Component Aliases to customise your use of the Create Facility eg giving the Point XYZ component an alias of XYZ will bring it up as the first option on the Create Facility as opposed to the other possibilities.
6) Try to answer other people's questions even if it's not relevant to your own area. By looking into solving a problem outside of your comfort zone and then posting your results it is very rewarding but it also lets you see the other approaches that get posted in a new light.
7) Take the time to understand Data/Path structures.
8) Buy a second monitor - There is nothing that can compare to real estate when working in Grasshopper.
9) Read Rajaa Issa's Essential Mathematics
10) Pick a panel in a tab on the ribbon and get to know every component inside and out and then move on. Start with the Sets Tab > List Panel…