.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.…
ine that populates the grid in a forward/backward/left/right/up/down manner in other words only within the XYZ axis one point at a time (like a 3D hilbert curve).
For instance the starting point is at 1,1,0 (XYZ).
to move one step right is to point 2,1,0 ,
to move one step forward is to point 1,2,0
and to move upwards is to point 1,1,1.
The attached file is what i'm working on right now.
What i tried doing was i selected all 64 points and decomposed them into their XYZ coordinates and then i sorted each one of them according to their axis. so i have 3 lists of the 64 points from their smallest number to the biggest. The bad thing about this is that i need to list out the XYZ coordinates for each of the 64 points and it is quite a pain because the grid i actually wanted is way bigger than this.
i thought a better way to do that would be to somehow number each point from 1-64.
Thus i could get a system where the starting point would be point 1, point 2 is the one next to it, point 17 is the one right directly above it and the last point being point 64.
So if i want the line to:
move right/left, i would just add/subtract one.
move forward i would just add 4 (going to the next row)
and move upwards/downwards i would add/substract 16.
How could i do this in grasshopper?
I hope i explained clear enough.
Any other method/suggestion is appreciated as well!
…
on Air.
Curated by Gil Akos, Evan Greenberg, and Ronnie Parsons, these lectures aim to interrogate three main lines of inquiry--material systems, natural systems, and machanic systems. Each esteemed presenter will discuss how designers can approach problems through the lens of Embedded Intelligence in practice, research, and academia. There will be an in-person audience at the Architectural Association in London and a recording of the series will be available on-demand through the AA's online lecture video catalog.
The first lecture, Biological Intelligence, will take place on February 3 and will feature The Living's David Benjamin. Winner of the MoMA PS1 Young Architects Program, Benjamin has created paradigm-shifting projects such as Living Light, an interactive canopy in Seoul that reacts to air quality, and Amphibious Architecture, a project which expresses pollution levels in the Hudson River.
Future lectures will be given by Michael Winestock of the Architectural Association and Skylar Tibbits of the Self-Assembly Lab at MIT.
…
ocessed once Grasshopper is done with whatever it's doing now.
3) Grasshopper tells the Slider object that the mouse moved and the slider works out the new value as implied by the new cursor position.
4) The slider then expires itself and its dependencies ([VB Step 1] in this case, but there can be any number of dependent objects).
5) When [VB Step 1] is expired by the slider, it will in turn expire its dependencies (VB Step 2), and so on, recursively until all indirect dependencies of the slider have been expired.
6) When the expiration shockwave has subsided, runtime control is returned to the slider object, which tells the parent document that stuff has changed and that a new solution is much sought after.
7) The Document class then iterates over all its objects (they are stored in View order, not from left to right), solving each one in turn. (Assuming the object needs solving, but since in your example ALL objects will be expired by a slider change, I shall assume that here).
8) It's hard to tell which object will get triggered first. You'd have to superimpose them in order to see which one is visually the bottom-most object, but let's assume for purposes of completeness that it's the [VB Step 1] object which is solved first.
9) [VB Step 1] is triggered by the document, which causes it to collect all the input data.
10) The input parameter [x] is asked to collect all its data, which in turn will trigger the Slider to solve itself (it got expired in step 4 remember?). This is not a tricky operation, it merely copies the slider value into the slider data structure and shouts "DONE!".
11) [x] then collects the number, stores it into its own data structure and returns priority to the [VB Step 1] object.
12) [VB Step 1] now has sufficient data to get started, so it will trigger the script inside of it. When the script completes, the component is all ready and it will tell the parent document it can move on to the next object (the iteration loop from step 7).
13) Let us assume that the slider object is next on the list, but since it has already been solved (it was solved because [VB Step 1] needed the value) it can be skipped right away, which leaves us with the last object in the document which is still unsolved.
14) [VB Step 2] will be triggered by the document in very much the same way as [VB Step 1] was triggered in step 9. It will also start by collecting all input data.
15) Since all the input data for [VB Step 2] is either defined locally or provided by an object which has already been solved, this process is now swift and simple.
16) Upon collecting all data and running the user script, the component will surrender priority and the document becomes active again.
17) The document triggers a redraw of the Grasshopper Canvas and the Rhino viewports and then surrenders priority again and so on and so forth all the way up the hierarchy until Grasshopper becomes idle again.
[end boring]
Pretty involved for a small 3-component setup, but there you have it.
To answer somewhat more directly your questions:
- The order in which objects are solved is the same as the order in which they are drawn. This is only the case at present, this behaviour may change in the future.
- Adding a delay will not solve anything, since the execution of all components is serial, not parallel. Adding a delay simply means putting everything on hold for N milliseconds.
- [VB Step 1] MUST be solved prior to [VB Step 2] because otherwise there'd be no data to travel from [GO] to [Activate]. The only tricky part here is that sometimes [VB Step 1] will be solved as part of the process of [VB Step 2], while at other times it may be solved purely on its own merits. This should not make a difference to you as it does not affect the order in which your scripts are called.
--
The Man from Scene 24…
Added by David Rutten at 4:43pm on December 10, 2009
se to not expose the boundary condition as a curve parameter. You have to supply a Box instead. You can set the box simply by clicking the right mouse button over the "B" parameter and choose the "Set one Box" menu item. The intersection between the Box and the Plane will become the outline condition.
Extruding the shapes is a bit trickier, it involves manipulating Data tree structures. This is not trivial, but it is important. Your best friend here is the ParamViewer object (Params -> Special). It allows you to inspect the layout of a data structure in memory.
First of all, lets perform the Voronoi + Offset operation and see what we get:
The ParamViewer object that is plugged into the Voronoi output states that the data is structured in a single list of 17 items. The path of this list is {0:0}, but we'll deal with that later. The output of the Offset component is not the same at all. That output is stored as 17 different lists with one item each. The reason for this is that it is technically possible to offset a single curve and get more than 1 result. This is why Offset complicates the data structure.
Before we can turn the curves into surfaces, we need to make sure that the layout of the two data structures (the voronoi curves and the offset curves) is identical. We can achieve this with 3 additional components:
The Graft component complicates the voronoi curves in the same way as the Offset component did. The Simplify component removes all redundant branching information from a data structure, so we are left with the simplest representation that still maintains all the information.
Now we have both curve sets stored in identical lists, which means that when we feed them both into a Planar Srf component, it will treat each voronoi curve and the associated offset curve together:
I'm not surprised this is confusing you. It is a very complicated topic. We'll probably need to come up with better matching algorithms for data structures, better ways to display the data in a human-friendly form, better ways to manipulate the structures. If you have any suggestions, I'd be happy to hear them.
--
David Rutten
david@mcneel.com
Seattle, WA…
Added by David Rutten at 2:32pm on October 4, 2009
ng code for Rhino6 and Visual Studio 2013 while typing on Grasshopper 2.0
I launch Rhino and Grasshopper each time, takes about 15~17 seconds to load both programs, it takes about 25 seconds to compile the entire project. Because of this I don't write and test tiny amounts of code, I write and test large amounts, then use the debugger to fix bugs.
As For debugging, yes, i'm able to step into my code via Visual Studio. but most of my time i'm not debugging - i'm developing and making small changes and compiling more than 40 times a day.
40 sounds about the right order of magnitude. Somewhere between 5 and 500 I'd say, depending on whether I'm debugging something big or writing a lot of new code.
I'd love to hear about any suggesstions of ways of work that you do that'll save me alot of time.
I wish there was a way to run Rhino with 'GH Developers' flag that'll run much faster.
You can not load certain plugins when starting Rhino. That may speed up loading times, but probably not significantly.
--
David Rutten
david@mcneel.com…
Added by David Rutten at 3:00am on January 6, 2014
regon, Eugene, OR
Scott Crawford of LMN's innovative Tech Shop has been empowering non-techie architects to explore design variations, giving lighting and energy performance feedback. For the Cleveland Medical Mart and Convention Center, the designers "painted" facade possibilities in Photoshop that were translated to parametric window patterns. The resulting patterns were optimized for building performance as well as aesthetic effect, then codified into Revit family members. Textures for adjacent wall panels were 3D printed and cast to examine aggregations. A negative was milled at full-scale for the pre-cast panels. In the Tech Shop, the team has worked with a wide variety of architectral software for modeling, fabrication, lighting, structural, wind and energy analysis. They even rigged up a Kinect movement sensor and projector to make a table work like an enormous iPad. Scott has developed great communication skills by teaching at University of Washington, where he earned both a Master of Architecture and a Master of Science in Design Computing. See more at: http://lmnts.lmnarchitects.com/ Please come see his free lecture, Friday April 20 at 5:30pm in room 206 Lawrence Hall, University of Oregon, Eugene, OR. To take his workshop on Iterative Daylight Analysis with Parametric Modeling sign up for ARCH 4/508 "Wrk GrasshoprSim Softw" (instructor of record Mark Donofrio) Saturday 9:00am-4:00pm and Sunday 9am-12:20pm, please call 541-346-4231. The workshop is $375 for undergraduate credit, $750 for graduate credit ($350 scholarships available), fees waived for faculty.…
ira en torno a las actividades del Taller Transversal de proyectos en colaboración con el Taller Paramétrico CEU, y los ponentes serán:
Roberto Molinos: Arquitecto , profesor de la IE School of Architecture que actualmente colabora con OSOME
Guillermo Ramírez y Miguel Vidal del estudio docente Frikearq, imparten cursos de diseño paramétrico y rhino scripting.Ambos alumnos de la ETSAM
Vicente Soler: Colaboraciones con el estudio Amid (Cero9) y alumno de la UEM
Pablo Delgado: Como coordinador del taller paramétrico CEU expondrá laas conclusiones de los diferentes talleres y trabajos realizados en la universidad.
Pablo Delgado Ramírez.Coordinador del taller paramétrico CEU 2010
pablodelgadoramirez@gmail.com
tallerparametricoceu@gmail.com
…
gners to build form generators from the simple to the awe-inspiring.
Parametric design works combing geometry and parameters. These variables can be modified to alter and update the final design at any moment, without remaking the 3d model. A parameter can be any data information: the section of a column, the distance to a specific point, the amount of sunlight at certain hour...etc
Another important feature in parametric or computational design is that you can automate or program processes and tasks for your designs. That means it is possible to generate complex shapes with specific data and get endless families of design with diverse results. During the course, with the help of short and basic exercises, we will learn how to reach and apply results to complex surfaces and textures.
Dates: March 26,27, April 2,3
Registration deadline: Monday, February 28th
Timetable: Saturday and Sunday 4 - 8,30 pm (Madrid, CET)
Place: On-line live sessions, using our platform online.controlmad.com
There, you can access to the live sessions with Zoom, download files and program.…
Added by Diego Cuevas at 1:24am on August 30, 2021
ies a step further towards informative models, how to extract data through a parametric process and design analysis which leads to performance based schema.The workshop will cover some advanced modeling techniques in grasshopper along with some useful grasshopper plugins "GECO,WEAVERBIRD,KANGAROO and more". An introductory to ecotect analysis will also be inculded.The workshop is dedicated to intermediate Grasshopper users " knowledge of GRASSHOPPER equivalent to which gained in Parametricisim WS or higher is preferred".Knowledge of ECOTECT is a plus but not necessary".
Schedule :Deadline for Registration : May 13,2013Workshop Starts : Thursday, May 16, 2013 - 5:30 pmThe workshop consists of 10 lectures, Each lecture lasts for 3 hours.3 lectures per week (Sun, Tues & Thur) ---------------------------------------------------Fees : 600 L.EYou have to fill the Registration Form below for place reservation.We only have few places available. ---------------------------------------------------Prerequisite :-Students should bring their own laptops---------------------------------------------------Registration Form:https://docs.google.com/forms/d/1qd7cTRi8fGJ3OiVPjiNzHA0ZRmXI2qCvk1CUQ-X_4H8/viewformYou can view previous Parametric workshops,Student work & presnetation here :Previous workshophttps://www.facebook.com/events/469048376477647/https://www.facebook.com/media/set/?set=a.548388031851299.1073741826.470747186282051&type=1https://www.facebook.com/events/178326265647678/…