posicionado como una herramienta abierta no sólo para el modelado 3D sino para el manejo de información. La capacidad de esta herramienta yace más allá de la agrupación de funciones, es a través de su vinculación con distintas plataformas dentro y fuera de Rhino que GH extiende su capacidad y versatilidad en la generación de forma/información. Este curso/taller se enfoca en lograr un control preciso y profundo de GH para extender las capacidades de modelado al establecer puentes con nuevas plataformas de software. INPUT/OUTPUT se adentra en establecer conexiones tanto físicas como digitales aprovechando la flexibilidad y fluidez operativa de Grasshopper.
TEMARIO
Filtrado de elementos
Manejo de listas
Re-acomodo de estructuras de información
Importar, preparar información y exportar
Evaluación interna de resultados
Iteraciones en GH
Conexiones a redes de información
Generación de herramientas auxiliares para informar la toma de decisiones
CONEXIONES
Excel / GH + Spreadsheets
Firefly / GH + Arduino
Ghowl / GH + Information + Networks
WeaverBird / GH + Advanced meshes
Pachube / GH + Real-time information feeds
Kangaroo / GH + Physics
Es requisito traer equipo de cómputo personal con Rhino y Grasshopper.…
hope this number will grow in future. Currently available features are:
1) Creation of 2d or 3d context for any kind of building related analysis: automatically generate the 2d/3d surrounding buildings for the location where you would like to perform visibility, solar radiation, cfd or any other type of analysis. You need some other plugin for the last three, like Ladybug. It only creates the context=surroundings! The "automatic generation" process also includes creation of the local topography (terrain) along with buildings.
2) Identification of certain 2d or 3d elements in the created context. For example: selection of all hotels, parks, hospitals, restaurants, residential buildings etc.
3) Performing direct terrain analysis (hillshading, slope, ruggedness, roughness, water flow...)
4) Creation of terrain shading masks and horizon files for further solar and photovoltaics analysis.
Gismo will be very grateful if he could get any suggestions, improvements, bug reports and testing in the following period. In case you are willing to provide any of these, the requirements, installation steps and .gh example files can be found here, here and here.
Thank you in advance !!…
Added by djordje to Gismo at 9:10am on January 29, 2017
it seems that was this. Now all is working fine !
Glad that it worked! But I am still a bit worried. Gismo components only modify the gdal-data/osmconf.ini file and no other MapWinGIS file. So your MapWinGIS installation files should not be compromised. The fact that you did not get the "COM CLSID" error message when running the "Gismo Gismo" component suggests that MapWinGIS has been properly installed. So I wonder if the cause for the permanent "invalid shapes" warning has again something with the fact that your system is again not allowing the MapWinGIS to properly edit the osmconf.ini. Maybe this problem will appear again, and again, and reinstallation of MapWinGIS every time can be somewhat bothersome.
- About the terrain generation, is it possible to have the texture from google or other provider mapped onto the terrain surface from gismo component ? (Same as using the ladybug terrain generator in fact). I try to used the image extracted by ladybug component and then applied it to the gismo terrain but the texture is rotated by 90°.
The issue with the rotation can be solved by swapping/reversing the U,V directions of the terrain surface. A slightly more important issue is that terrain surface generated with Gismo "Terrain Generator" component might have a bit smaller radius than what the radius_ input required. This stems from the fact that the terrain data first needs to be downloaded in geographic coordinate system, and then projected. Some projecting issues may occur at the very edges of the projected terrain, so I had to slightly cut out the very edges of the terrain which results in the actual terrain diameters being slightly shorted in both directions. This means that if you apply the same satellite image from Ladybug "Terrain Generator" component to Gismo "Terrain Generator" component the results may not be the same.I attached below a python component which tries to solve this issue by extending the edges of Gismo "Terrain Generator" terrain, and then cutting them with the cuboid of the exact dimensions as the radius_ input. Have in mind that this extension of the original terrain at its edges is not a correct representation of the actual terrain in that location. But rather just an extension of the isoparameteric curve of the terrain surface. So basically: some 0 to 10% (0 to 10 percent of the width and length) of the terrain around all four edges is not the actual terrain for that location, but rather just its extension.The python component is located at the very right of the definition attached below.
Also, if you would like to use the satellite images from Ladybug "Terrain Generator" component along with "OSM shapes", sometimes you may find slight differences in position of the shapes. This is due to openstreetmap data not being based on Google Maps (that's what Ladybug "Terrain Generator" component is using), but rather on Bing, MapQuest and a few others.
- About the requiredKeys_ input of OSM shapes, I understand what you mean and your advice, but in most cases I use it, the component was working fine even without input. I think it's better to extract all tags, values and keys of the selected area, instead of searching for specific ones as I try to find all data related to what I want after, isn't it ? To check what keys are present on the area also.
Ineed, you are correct.I though you were trying to only create a terrain, 3d buildings and maybe find some school or similar 3d building, for these two locations. The recommendation I mentioned previously is due to shapefiles having a limit (2044) to how many keys it can contain. This requires further testing of some big cities locations with maybe larger radii, which I haven't performed due to my poor PC configuration. But in theory, I imagine that it may happen that a downloaded .osm file may have more than 2044 keys. In that case shapefile will only record 2044 of them, and disregard the others. That was my point.But again 2044 is a lot of keys, and I haven't been checking much this in practice. For example, when I set the radius_ to 1000 meters, and use your "3 Rue de Bretonvilliers Paris" location I get around 350 something keys, which is way below the 2044.Another reason why one should use the requiredKeys_ input is to make the Gismo OSM components run quicker: for example, the upper mentioned 350 something keys will result in 350 values for each branch of the "OSM shapes" component's "values" output.Which means if you have 10 000 shapes, the "OSM shapes" component will have 10 000 branches with 350 items on each branch (values). This can make all Gismo OSM components very heavy, and significantly elongate the calculation process.With requiredKeys_ input you may end up with only a couple of tens of items per each branch.Sorry for the long reply.…
Added by djordje to Gismo at 8:57am on June 11, 2017
proxy). However I decided to use the Human plug-in and scatter them as block instances, this allows me to add some reference lines in a different layer to have a better visual reference of the proxies, and have a lighter work environment in Rhino. (If you have the blocks on a layer and the proxies inside in a different layer, the proxies will render even if their layer is off and they are not showing in the viewport)
The definition has two parts: the bottom part scatters 3 grass primitives on a circle surface and is mostly an updated version of Manuel's definition, I hope he doesn't mind (you can replace the circle with any surface if you want a small patch of grass), you then bake this geometry, create one or several proxies in Rhino and create the blocks; the top part scatters a block on either a Surface, Brep or Mesh.
The definition populates the base surface/brep/mesh with points, then offsets the edges with the circle radius and pulls the points outside that boundary to it, so the circles don't fall outside the surface. (this part was the one that gave most troubles and it still fails sometimes, maybe someone could help me with that)
It also autoflips the normals if they're not up, and aligns the X axis of the target planes to a set direction (so you can have some wind or gravity effect if you want).
I used, and you probably need to make it work: Rhino 5 sr11 64bits, V-ray 2.0, grasshopper 0.9.0076, and Human (3-17-2014)
In my examples I scattered 3 blocks each with its own material, but you can have proxies with multiple materials.
If you make your own grass primitives don't forget to map the textures before scattering.
I'm posting some example renders and sharing the vray materials and proxies I used (I was experimenting with vray2sidedmats and a second diffuse layer with yellow noise mapped to world coordinates)
I'd like some help to get some cooler and different ideas for grass materials and proxies.
If you get some bugs let me know...
Eduardo
…
Added by Eduardo A at 11:54am on September 14, 2015
tura digital en corte Láser, corte CNC, impresión 3d, y modelado paramétrico.
Este tercer taller enseña los fundamentos del modelado paramétrico y algunas bases de manufactura digital.
PERFIL DEL ALUMNO QUE INGRESA:
Diseñador, Arquitecto, Artista con conocimientos de Rhinoceros interesados en comenza a modelar paramétrico con Grasshopper para fabricación digital básica.
PERFIL DEL ALUMNO QUE EGRESA:
El alumno terminará con los conocimientos y criterios para el desarrollo de piezas o proyectos utilizando fabricación digital, mejorando y agilizando los flujos de trabajo, así como los criterios fundamentales del Modelado Paramétrico -Generativo.
Taller de modelado paramétrico con Grasshopper
Interfase
Manejo de Datos
Data Volátil
Data Persistente
Rangos y dominios
Atractores
Listas y Cull
Modelado por Layer Object
Análisis Básicos
Conexión de Curvas
Superficies
Análisis de Superficies
Panelización Básica
Relaciones con Excel
Modelado generativo
Fechas: del 8 de Febrero al 1º de Marzo
Días: Sábado
Horarios: de 10 am a 3 pm
Sesiones: 4 de 5hrs
Duración: 20 horas
Precio: $3,000.00…
ectly in grasshopper (drawing a curve on top of a line with different angles), i did the curve shape in rhino and import it into grasshopper.
i'm having a problem where some of the sine curve shape can orient or map onto the triangle surfaces nicely, but some of them do not. whenever i try to orient the shape onto the bottom portion of the icosahedron, the shape becomes 'negative', forcing me to flip the lines before offsetting and patch (i am using loft method) or else it will become a weird loft (image 3).
i have tried several different ways to orient the ones that worked (orient 3d in rhino, rotate 3d etc.) and still could not get them to work.
the reason that i want them to face in the same direction is so that i can use WB thicken and make sure they extrude in the same direction. i have tried to unify the normal faces in grasshopper and still it is not working.
does anyone have any idea why or how can i do this? your help will be greatly appreciated. i am fairly a beginner in GH so if there is any other easier method to do this will also be great :)
…
ase of resource and energy consumption identify significant developments of our time. Against this background and in the context of sustainable fairness to future generations, there will be a greater focus on energy and ressource efficient building structures.
This interdisciplinary course aims to lay the foundations of a „force based design“ through theoretical input lectures and presentations. Varying examples will show that the efficiency of structures depends largely on the flow of forces within the structure. Possible optimisation strategies will be discussed in the light of material saving and their impact on architectural form.
This course will introduce you to the use of digital analysis and optimization tools. You will learn to deal with three-dimensional parametric software (Rhinoceros 3D, Grasshopper, Sofistik, Karamba, GeometryGym, Kangaroo).
Finally, the knowledge acquired will be applied and developed in designing a pedestrian bridge or a slender tower.
Participants will be able to recognize the effects of forces as design parameters. They will recognize the potential of building geometry in the context of architecture and resource-efficient designs.
Information » Application deadline 15 May » Course duration 18 - 30 August » Course language English » Target Groups Master students, graduates, doctoral candidates and young professionals » Requirements basic knowledge of 3D parametric software is recommended » Course fee 490 € (100 € discount for students and alumni) (290 € discount for students of the Bauhaus-Universität Weimar)
Lecturers » Prof. Dr.-Ing. Alexander Stahr - HTWK Leipzig » Dipl.-Ing. Christian Heidenreich - Bauhaus-Universität Weimar » B.Sc. Martin Dembski - Bauhaus-Universität Weimar
Guest Lecturers » Dipl. Eng. Arch. Simon Vogt - Transform Engineers, Hamburg » Dipl. Bauingenieur FH Nico-Ros-Zeile - ZPF Ingenieure, Basel (CH)…
ally put the component together a few months ago.
Abraham, the case of 1.2 failing was because of a bug where I simply put "< 1.2" in the code instead of "<=1.2". The error was specifically happening with 1.2 because that is the wind speed threshold at which the "hump" of the ASHRAE adaptive comfort polygon grows. It is perhaps easier to see this threshold in the inputs of the CBE Adaptive comfort chart:
I fixed the bug in the attached file and on the github.
Grasshope, to address why you are getting branched data and the 2 comfort polygons, it is because you have connected up the EPW windSpeed to the component. Usually, if you connect up multiple values for windSpeed_, the component will produce a comfort polygon for each wind speed. However, I built a mechanism into the component that stops it from generating 8760 comfort polygons (one polygon for each hour) if you connect up full EPW data. 8760 comfort polygons takes almost a minute to generate and so I figured that this is probably not what people want to do most of the time. Instead, the component just generates one polygon for the minimum wind speed and another for the maximum wind speed (to show you the range). The branched data that you get out of the component are values for each polygon (2 branches for two polygons). If you connect up the data to the 3D chart, this might make things clearer:
One polygon is for 0 wind speed and the other is for the maximum EPW wind speed.
I am interested in hearing your thoughts on my way of dealing with this since I am thinking of implementing something similar on psychrometric chart. I realized that a lot of people were crashing the psych chart by connecting up the EPW wind speed, which currently tells the component to generate 8760 comfort polygons.
Thanks, as always, for all of your help,
-Chris…
would like to ask someone with patience, time and disposition for a definition of maximum displacement, resulting force of gravity and internal elastic energy. I know that these topics appear on the Karamba manual, however the explanation is quick and brief and I, and perhaps some others, can´t grasp completely what are they and how they work.
Secondly I would like to ask advice on how to deal the problem of minimizing the quantity of material used and keeping the structure strength in an acceptable range.
Those were my two questions. Now I am going to explain the definition that I am working on in order to show how this relates to the problem I am trying to solve.
I am trying to optimize a column made of plastic, which is intended to be fabricated in a 3D printer. I have created a grasshopper definition that lets me customize plenty of options (height, width, number of sides, number of divisions, type of interconnections, etc… ).
Image 1 can provide a quick look of what I am trying to do.
I am using galapagos to fine-tune some of the values in order to achieve the best possible structure that can withstand a certain arbitrary weight (for example 100 Kg) within acceptable deformation values and use the least possible material.
Perhaps the key values that I am letting Galapagos manipulate are the number of division in plan and section of the column.
The problem arises when I choose to optimize by minimizing the maximum displacement, which is the most common case in tutorials and examples.
Galapagos naturally tends to divide the column in the maximum number of section that I allow (which is logical since it creates more beams and minimizes their lenght), image 2 provides an example of the minimum and maximum number of division that I am allowing.
This solution (empirically) seems wasteful. I believe that the real solution to the problem (sustaining an arbitrary weight without failing and most importantly using the less possible material) must be between the two columns presented in image 2.
Thank you guys for your help and for reading such a long post.
Sincerely
Diego…
between internal structural frameworks and non-bearing skin elements, this approach promotes heterogeneity and differentiation of material properties. The project demonstrates the notion of a structural skin using a Voronoi pattern, the density of which corresponds to multi-scalar loading conditions. The distribution of shear-stress lines and surface pressure is embodied in the allocation and relative thickness of the vein-like elements built into the skin. Its innovative 3D printing technology provides for the ability to print parts and assemblies made of multiple materials within a single build, as well as to create composite materials that present preset combinations of mechanical properties.
for registration please contact:
bioskinarc@gmail.com
tel: 09197804306
…