hinoceros + Grasshopper + Vray los participantes puedan desarrollar mediante un flujo de trabajo digital las técnicas de Diseño Paramétrico, mediante métodos algorítmicos generativos, para su implementación en procesos de diseño y representación de los mismos, a través de:
Técnicas avanzadas de modelación 3d e imágenes foto realistasProliferación en topologías complejas mediante Definiciones visualizados Estrategias de Mapeo y Análisis evolutivos en Tiempo RealVinculaciones entre criterios Predefinidos paramétricamente y Morfologías resultantes
Detalles:
∙ Instructores / Matías Casciotta y Salomón Escobar / Integrantes Ha-11
∙ Todos los niveles de experiencias son bienvenidos
∙ Recursos: Interfaces Rhino + Grasshopper / Manuales PDF / Definiciones GH Preparadas
∙ Los participantes deberán traer su propia laptop con todo el software y actualizaciones (originales o versiones de demostración) previamente instaladas. (Se fijara una fecha unos días antes para revisar que todos los equipos estén en orden y listos para trabajar).
∙ Proceso de Inscripción
Los participantes deberán adjuntar su “mail”, a través de un comentario en esta imagen de Facebook y recibirán: información sobre lugar, fecha, costo de matricula, forma de pago y material de aprendizaje para el correcto desarrollo del workshop
Para mayor info: ha.11.arquitectos@gmail.comhttp://ha11studio.blogspot.com/ en facebookhttp://www.facebook.com/pages/Dise%C3%B1o-param%C3%A9trico-ha11/273506122720586?ref=ts…
s will learn to use these extensions in order to integrate numerous tools for analysis and simulation in the architectural process.
This course aims to develop a link between the virtual and the real context model through structural or environmental simulations, using other software or plug-ins dedicated. Through this link the virtual model receives physical properties that can further modify and adapt the initial model. This creates feedback loops that can optimize the design to provide an object responsive to environmental conditions.
Curriculum
Mesh subdivision with Weaverbird, continuous surfaces without NURBS
Genetic optimization with Galapagos, optimal search
Physical environment feedback with Diva and Geco, solar and day lighting analysis
Adding physical properties with Kangaroo Physics, interactive form-finding
Linking the parametric model with structural analysis using Karamba, structural performance simulation
Extracting data with Firefly and Kinect, 3D scanning and human movement tracking
Exchange of information between Grasshopper and other applications with Ghowl links to internet feeds or Excel files.
Schedule:
Module Grasshopper intermediate & advanced (24 h)
1 Nov – 15 Nov 2014
Sat:
9 - 13
14 - 18
Language: Romanian
Trainers:
Ionuț Anton, idz arhitectura (ART-Authorised Rhino Trainer)
Dana Tănase, idz arhitectura (ART-Authorised Rhino Trainer)
https://www.facebook.com/cursurigrasshopperrhinoceros
https://www.facebook.com/idzarhitectura
http://www.idz.ro/training/…
Added by Dana Tanase at 2:23am on February 2, 2014
her than number, where length was the fixed diameter of my prototype sphere.
That way, I thought, as the length of the ISOcurves changes along the height of my dome/shape the number of spheres along the line would change to fit. This works pretty well. The problem was shifting the alternate ISOcurve seams to get a psuedo staggered effect. I don't mind some overlap if the result is aesthetically pleasing (wink).
This only worked along the ISOcurves until the length started to change appreciably. Then the stagger factor varied. This was okay for my purposes since I was working with a fixed size sphere and could expect this.
I suppose that one could very slightly change the diameter of the spheres to make them fit more closely. If this variance stayed very low (maybe in the 1 or 2% range) then this would give the effect of a consistent tessellation.
Igor's Idea of using a hexagonal grid and placing spheres at the centroids is an excellent one as well.
The problem is that once you begin to vary the curvature of the target surface, as in my dome, the hex cells compress because he's using a rectangular array and projecting it onto a domed surface. If there was some way to reduce the cell count as the ISO curve length decreased then this might work better as well.
Another solution might be, as hinted at by Igor, using a geodesic dome with regular cells approximating the dome structure. Since my proto sphere diameter is typically 1 unit and the dimensions are typically around 40 x 18 x 20 units this result in a density of 14400 per dome. The faceted nature of the Geodesic would be smoothed out by the sheer number of cells. Another way to look at this would be to populate the vertices of a polyhedron which approximates the dome.
Unfortunately I have no idea how to do this. But I'm really eager to see what you folks come up with. Meanwhile I'm playing with both sets of definitions to understand them.…
cture below you can see, that the end product is a brick wall. With galapagos i want to differenciate and choose how many different stones i have/want (in specific aesthetic cases). therefor i need values i can compare with eachother. with 'delete consecutive' and list length i would come to a result. But every values i tried yet, were not characteristic for each of the different looks.
After your answer I thought about setting a boundry box around every stone and compare the locations of all vertices in relation to their boxes with all the other stones vertices locations. but i still have no idea how i would build that up.
I also think that igual but mirrored stones would be handled like different stones. But they should be handled the same.
I tried the surface-area but the values seem to be to complicated to compare them. for the picture here with 18 stones. Galapagos can not reach the same stone for the entire wall. Stones are created by a grid. within the grid, points can be moved one position up or down or stay where they are. that makes them to look different from what we are used to.
'Topological properties' - seem to be eqaul for all breps
'Geometrical properties' - Area/ Volume centroid/ Locations of all vertices/ Bounding box (position, volume, etc.) could be values.
to start, I'd want to try the idea i mentioned earlier: setting a boundry box around every stone and compare the locations of all vertices in relation to their boxes with all the other stones vertices locations. Do you have a hint for me how to get started?
thx so far
…
ries", but it could be changed in the future with nicer and more interesting names.
It's perfectly known that lot of plugins has been released to empower GH panelling capabilities, but usually lightweight and native systems could be required to accomplish specific little (or big) design tasks. In addition to this, the panelling process is a task that let the user to play and learn and practice deeply concepts about surface/meshes topology, list and data trees management, etc. So I though that this could be a perfect starting point for the "Utilities series" in c+GH.
To open this group of c+GH post I will start with something simple that everyone that have used GH has tried sooner or later in his/her learning process: how to panel a surface using standard/built-in GH components only.
Topics that could be covered (aka, problem categories):
Planar panels.
Curved panels.
Mixed solutions: curvature/distortion triggers or limits.
Given a NURBS surface, create a single panelling system that implement one of the categories described for only one kind of panel (triangular, quadrilateral, n-gon). Of course, curved panels are not compatible with triangular shapes, etc, so try to pick a compatible combination.
Further considerations:
The implemented solution should let the user to interact with every panel easily, so the proposed algorithm should track the panellization process avoiding to destroy helpful information/data structures for further modifications in the panelling system.
NURBS and mesh solutions are both allowed.
None, plugin or scripted component allowed.
The cleanest, shorter and less processing-time-expensive solution in every category will be the winner (please, consider using profiler intensively).
Deadline: May 18, 2014.
…
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)…
.0004. [1 of 7] Writing simulation parameters...5. [2 of 6] No context surfaces...6. [3 of 6] Writing geometry...7. [4 of 6] Writing materials and constructions...8. [5 of 7] Writing schedules...9. [6 of 7] Writing loads and ideal air system...10. [7 of 7] Writing outputs...11. ...... idf file is successfully written to : c:\ladybug\unnamed\EnergyPlus\unnamed.idf12. 13. Analysis is running!...14. c:\ladybug\unnamed\EnergyPlus\eplusout.csv15. ......
Done! Read below for errors and warnings:
16. 17. Program Version,EnergyPlus, Version 8.2.7-777c1f8d79, YMD=2015.02.28 16:09,IDD_Version 8.2.718. 19. ** Warning ** IP: Note -- Some missing fields have been filled with defaults. See the audit output file for details.20. 21. ** Warning ** Version: in IDF="'8.2.7'" not the same as expected="8.2"22. 23. ** Warning ** ManageSizing: For a zone sizing run, there must be at least 1 Sizing:Zone input object. SimulationControl Zone Sizing option ignored.24. 25. ** Warning ** ManageSizing: For a plant sizing run, there must be at least 1 Sizing:Plant object input. SimulationControl Plant Sizing option ignored.26. 27. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=F73533B3C6894C67936B_GLZP_1228. 29. ** ~~~ ** Opening Surface creating error=F73533B3C6894C67936B_GLZP_12_GLZ_1230. 31. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=F73533B3C6894C67936B_GLZP_2532. 33. ** ~~~ ** Opening Surface creating error=F73533B3C6894C67936B_GLZP_25_GLZ_2534. 35. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=F73533B3C6894C67936B_GLZP_2836. 37. ** ~~~ ** Opening Surface creating error=F73533B3C6894C67936B_GLZP_28_GLZ_2838. 39. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_940. 41. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_9_GLZ_942. 43. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_1044. 45. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_10_GLZ_1046. 47. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_1148. 49. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_11_GLZ_1150. 51. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_1552. 53. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_15_GLZ_1554. 55. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_2456. 57. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_24_GLZ_2458. 59. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_2560. 61. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_25_GLZ_2562. 63. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_3064. 65. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_30_GLZ_3066. 67. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_3268. 69. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_32_GLZ_3270. 71. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_3472. 73. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_34_GLZ_3474. 75. ** Warning ** GetSurfaceData: Very small surface area[2.94495E-004], Surface=F73533B3C6894C67936B_GLZP_076. 77. ** Warning ** GetSurfaceData: Very small surface area[3.84753E-004], Surface=F73533B3C6894C67936B_GLZP_178. 79. ** Warning ** GetSurfaceData: Very small surface area[9.16905E-004], Surface=F73533B3C6894C67936B_GLZP_380. 81. ** Warning ** GetSurfaceData: Very small surface area[4.96186E-004], Surface=F73533B3C6894C67936B_GLZP_482. 83. ** Warning ** GetSurfaceData: Very small surface area[2.37373E-005], Surface=F73533B3C6894C67936B_GLZP_684. 85. ** Warning ** GetSurfaceData: Very small surface area[6.35824E-004], Surface=F73533B3C6894C67936B_GLZP_786. 87. ** Warning ** GetSurfaceData: Very small surface area[5.86549E-004], Surface=F73533B3C6894C67936B_GLZP_888. 89. ** Warning ** GetSurfaceData: Very small surface area[7.63765E-004], Surface=F73533B3C6894C67936B_GLZP_1090. 91. ** Severe ** GetSurfaceData: Zero or negative surface area[-8.09566E-004], Surface=F73533B3C6894C67936B_GLZP_1292. 93. ** Warning ** GetSurfaceData: Very small surface area[1.51701E-004], Surface=F73533B3C6894C67936B_GLZP_1394. 95. ** Warning ** GetSurfaceData: Very small surface area[9.29917E-004], Surface=F73533B3C6894C67936B_GLZP_1596. 97. ** Warning ** GetSurfaceData: Very small surface area[2.94451E-004], Surface=F73533B3C6894C67936B_GLZP_1698. 99. ** Warning ** GetSurfaceData: Very small surface area[8.03294E-004], Surface=F73533B3C6894C67936B_GLZP_17100. 101. ** Warning ** GetSurfaceData: Very small surface area[6.83026E-004], Surface=F73533B3C6894C67936B_GLZP_18102. 103. ** Warning ** GetSurfaceData: Very small surface area[9.29917E-004], Surface=F73533B3C6894C67936B_GLZP_20104. 105. ** Warning ** GetSurfaceData: Very small surface area[3.19851E-005], Surface=F73533B3C6894C67936B_GLZP_21106. 107. ** Warning ** GetSurfaceData: Very small surface area[7.63765E-004], Surface=F73533B3C6894C67936B_GLZP_23108. 109. ** Severe ** GetSurfaceData: Zero or negative surface area[-4.05899E-004], Surface=F73533B3C6894C67936B_GLZP_25110. 111. ** Warning ** GetSurfaceData: Very small surface area[6.35824E-004], Surface=F73533B3C6894C67936B_GLZP_27112. 113. ** Severe ** GetSurfaceData: Zero or negative surface area[-9.91146E-004], Surface=F73533B3C6894C67936B_GLZP_28114. 115. ** Warning ** GetSurfaceData: Very small surface area[2.70158E-004], Surface=F73533B3C6894C67936B_GLZP_29116. 117. ** Warning ** GetSurfaceData: Very small surface area[3.22781E-004], Surface=F73533B3C6894C67936B_GLZP_30118. 119. ** Warning ** GetSurfaceData: Very small surface area[4.67821E-004], Surface=F73533B3C6894C67936B_GLZP_33120. 121. ** Warning ** GetSurfaceData: Very small surface area[3.22737E-004], Surface=F73533B3C6894C67936B_GLZP_34122. 123. ** Warning ** GetSurfaceData: Very small surface area[2.65634E-004], Surface=4BDFD67E6D0E486796CC_GLZP_0124. 125. ** Warning ** GetSurfaceData: Very small surface area[4.70736E-004], Surface=4BDFD67E6D0E486796CC_GLZP_1126. 127. ** Warning ** GetSurfaceData: Very small surface area[3.42507E-004], Surface=4BDFD67E6D0E486796CC_GLZP_3128. 129. ** Warning ** GetSurfaceData: Very small surface area[5.89276E-004], Surface=4BDFD67E6D0E486796CC_GLZP_4130. 131. ** Warning ** GetSurfaceData: Very small surface area[1.91146E-004], Surface=4BDFD67E6D0E486796CC_GLZP_6132. 133. ** Warning ** GetSurfaceData: Very small surface area[9.71205E-004], Surface=4BDFD67E6D0E486796CC_GLZP_7134. 135. ** Warning ** GetSurfaceData: Very small surface area[4.34494E-004], Surface=4BDFD67E6D0E486796CC_GLZP_8136. 137. ** Severe ** GetSurfaceData: Zero or negative surface area[-3.60159E-004], Surface=4BDFD67E6D0E486796CC_GLZP_9138. 139. ** Severe ** GetSurfaceData: Zero or negative surface area[-1.11946E-004], Surface=4BDFD67E6D0E486796CC_GLZP_10140. 141. ** Severe ** GetSurfaceData: Zero or negative surface area[-3.41257E-004], Surface=4BDFD67E6D0E486796CC_GLZP_11142. 143. ** Severe ** GetSurfaceData: Zero or negative surface area[-8.21483E-005], Surface=4BDFD67E6D0E486796CC_GLZP_15144. 145. ** Warning ** GetSurfaceData: Very small surface area[2.65716E-004], Surface=4BDFD67E6D0E486796CC_GLZP_16146. 147. ** Warning ** GetSurfaceData: Very small surface area[4.84044E-004], Surface=4BDFD67E6D0E486796CC_GLZP_17148. 149. ** Warning ** GetSurfaceData: Very small surface area[7.12297E-004], Surface=4BDFD67E6D0E486796CC_GLZP_19150. 151. ** Warning ** GetSurfaceData: Very small surface area[6.14324E-004], Surface=4BDFD67E6D0E486796CC_GLZP_22152. 153. ** Warning ** GetSurfaceData: Very small surface area[8.88887E-004], Surface=4BDFD67E6D0E486796CC_GLZP_23154. 155. ** Severe ** GetSurfaceData: Zero or negative surface area[-9.89060E-004], Surface=4BDFD67E6D0E486796CC_GLZP_24156. 157. ** Severe ** GetSurfaceData: Zero or negative surface area[-1.14849E-003], Surface=4BDFD67E6D0E486796CC_GLZP_25158. 159. ** Warning ** GetSurfaceData: Very small surface area[4.00479E-004], Surface=4BDFD67E6D0E486796CC_GLZP_27160. 161. ** Warning ** GetSurfaceData: Very small surface area[6.63061E-005], Surface=4BDFD67E6D0E486796CC_GLZP_28162. 163. ** Warning ** GetSurfaceData: Very small surface area[1.09018E-004], Surface=4BDFD67E6D0E486796CC_GLZP_29164. 165. ** Severe ** GetSurfaceData: Zero or negative surface area[-2.49326E-005], Surface=4BDFD67E6D0E486796CC_GLZP_30166. 167. ** Severe ** GetSurfaceData: Zero or negative surface area[-3.17446E-004], Surface=4BDFD67E6D0E486796CC_GLZP_32168. 169. ** Warning ** GetSurfaceData: Very small surface area[8.60686E-004], Surface=4BDFD67E6D0E486796CC_GLZP_33170. 171. ** Severe ** GetSurfaceData: Zero or negative surface area[-2.48515E-005], Surface=4BDFD67E6D0E486796CC_GLZP_34172. 173. ** Fatal ** GetSurfaceData: Errors discovered, program terminates.174. 175. ...Summary of Errors that led to program termination:176. 177. ..... Reference severe error count=24178. 179. ..... Last severe error=GetSurfaceData: Zero or negative surface area[-2.48515E-005], Surface=4BDFD67E6D0E486796CC_GLZP_34180. 181. ************* Warning: Node connection errors not checked - most system input has not been read (see previous warning).182. 183. ************* Fatal error -- final processing. Program exited before simulations began. See previous error messages.184. 185. ************* EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors.186. 187. ************* EnergyPlus Sizing Error Summary. During Sizing: 2 Warning; 0 Severe Errors.188. 189. ************* EnergyPlus Terminated--Fatal Error Detected. 41 Warning; 24 Severe Errors; Elapsed Time=00hr 00min 1.51sec190.…