ntornos de trabajo, entre técnicas interactivas y soluciones algorítmicas, se examinan conceptos y casos de estudio que le permitirán al participante decidir como y en que momento estas tecnologías pueden ser utilizadas como aliadas en los procesos de diseño y fabricación. Tomando como plataforma básica Rhino, se explora y optimiza el diseño y fabricación de topologías complejas bajo los entornos de Grasshopper, RhinoNest y RhinoCam. Su duración será de 4 horas, cupo limitado.…
nth". It complains about "global name "orange" not defined. When you define this situation through Series component it works fine. Checked with other LB components that use input from the AnalysisPeriod and they seem to work well, so the issue is only with SunPath.
2. Another one with the same components: defining, for instance, fromHour 10 - toHour 15, in the model you get from 10 to 14 (one hour less than you asked for), even though that the report output and analysisPeriod input are correct.
3. If already there, defining the "center point" for the Sunpath will be usefull. Not always you want the 0,0,0, or the center of the model. I mentioned this after seeing the part of the video when you intersect the lofted sun positions with a building. Of course you can move the model or move the fan but this can make a shortcut for the user.
Thanks,
-A.…
r piece out of the mold if you reverse it, befor the porcelain shrink. The porcelain shrink approx 14% between the mold and the final piece after it have been baked.
You have your piece with only a 2 to 4 mm wall thickness It'sdepend of the time you let the "barbotine" dry in the mold before you empty it. Here the thickness is about 2 mm.
Yes the piece is bake in a kiln to approx 1000 °C .
With a thickness from 2 to 4 mm, you can play with the translucidity of the porcelaine to let the light come through like in my voronoî project in 2014 : http://www.grasshopper3d.com/video/vorono…
ment.
This course will help architects and designers in their practice and development of forms using generative algorithms.
Curriculum
Introduction to parametric design
Understanding the user interface of Grasshopper and visual programming theory
Understand the components and types of networking
Linking and importing and exporting geometry from Rhino Rhino geometry results back
Knowledge of the main data types (numbers, fields, vectors, points, curves, surfaces, brep)
Manage lists and trees of data: simple tasks lists, extracting data in lists and trees
Operations with vectors and points
Using colored gradient according to the parameters
Strategies of planar space subdivision: Voronoi
Working with curves and create surfaces : loft, surface from points, attractors
Surface subdivision with Lunchbox: triangular, hex, diagrid
Schedule:
Module Grasshopper beginners (24 h)
10 May – 24 May 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:21am on February 2, 2014
+3 (for Haifa), that should give you more accurate times?
As this is part of a much larger genetic algorithm, I have made some choices for speed over accuracy.
The script generates the time for each 3 minute within the timeframe of the selected day. The sun vectors of these build the basis of the solar path on that day. Each minute would be more accurate, but also take longer to calculate.
My first idea was to intersect each sun vector with the surroundings. This would give me (with an accuracy of a minute/3 minutes accordingly) the excact time of the block. It would also mean that I had to potentiale check 60 * 14 = 840 for interactions with all context. So my approach was a bit different. I know the length of the solar path. I know the exact time of where this path starts/ends. So I approximate solarPathLength/minutes = length of a unit along the sun path. When I find a block, I check the length of the block and see how many minutes this would approximately be. As this is all math, it is very quick. But not super accurate. It gives me the indication I need though.
Cheers, Eirik…
as follows.
We have a grid which consists of a collection of columns, where each column consists of a list of points. You said flattening is out of the question, so we need to cull items from each list individually.
Let's say our culling pattern is KDDDKDD (repeat as needed). K = Keep, D = Ditch. If a column contains 18 points, the pattern needs to be repeated until it is 18 items long. In this case:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
K D D D K D D K D D D K D D K D D D
We can now cull each column, but they will all be culled in the same way. By shifting the pattern one more index for each column, we can cycle the culling.
The fix incidentally is to Shift the pattern PRIOR to repeating it. Then it works as expected:
--
David Rutten
david@mcneel.com
Tirol, Austria…
Added by David Rutten at 2:49pm on October 2, 2013
nizzati da Better Nouveau dedicati alle strategie computazionali applicate al design. Sono corsi intensivi in cui ricerca e formazione affrontano da vicino design generativo, interaction design, digital fabrication e physical computing.
Per informazioni
http://www.betternouveau.com/workshop/grasshopper_workshop.php…
e iso curves. At position 14 it is doing it 3 times and I am not sure if this are overall the 90° to the surface, or am i wrong? Does someone have a more elegant or a better way doing this?
Thanks for any help and hints!!
…
be done easier, but later on the geometry will change and therefore this seems the better option. But coming back to the problem
First, there were some problems concerning the zone, although it seems solved still the “runenergysimulation” gives the following warning:
1. The simulation has not run correctly because of this severe error:
** Severe ** UpdateZoneSizing: Cooling supply air temperature (calculated) within 2C of zone temperature
Do one of you know what went wrong? It probably will solve most of it.
Second, “set Zone Thresholds” gives the following warning:
1. Solution exception:global name 'maxHumidity_' is not defined
However, the component is missing the max humidity input on the list, has this to do something with the error?
All the components are up to date.
I hope it will be an easy fix.
Gr Lars
“set Zone Thresholds” runtime error
{0;0;0}0. Runtime error (UnboundNameException): global name 'maxHumidity_' is not defined1. Traceback: line 80, in checkTheInputs, "<string>" line 282, in script
"runenergysimulation” report
{0;0}0. Current document units is in Meters1. Conversion to Meters will be applied = 1.0002. TypeError('Waarde kan niet null zijn.\r\nParameternaam: source',)3. Failed to copy the object. Returning the original objects...This can cause strange behaviour!4. [1 of 8] Writing simulation parameters...5. [2 of 8] No context surfaces...6. [3 of 8] Writing geometry...7. [4 of 8] Writing Electric Load Center - Generator specifications ...8. [5 of 8] Writing materials and constructions...9. [6 of 8] Writing schedules...10. [7 of 8] Writing loads and ideal air system...11. [8 of 8] Writing outputs...12. ...... idf file is successfully written to : c:\ladybug\unnamed\EnergyPlus\unnamed.idf13. 14. Analysis is running!...15. c:\ladybug\unnamed\EnergyPlus\eplusout.csv16. ......
Done! Read below for errors and warnings:
17. 18. Program Version,EnergyPlus, Version 8.3.0-6d97d074ea, YMD=2016.03.02 20:55,IDD_Version 8.3.019. 20. ** Warning ** IP: Note -- Some missing fields have been filled with defaults. See the audit output file for details.21. 22. ************* Beginning Zone Sizing Calculations23. 24. ** Warning ** GetInternalHeatGains: People="CLASSROOMOFFICEPEOPLE", Activity Level Schedule Name values25. 26. ** ~~~ ** fall outside typical range [70,1000] W/person for Thermal Comfort Reporting.27. 28. ** ~~~ ** Odd comfort values may result; Schedule="SCHOCCUPANCYSCHEDULE".29. 30. ** ~~~ ** Entered min/max range=[0.0,1.0] W/person.31. 32. ** Warning ** Calculated design heating load for zone=CLASSROOM is zero.33. 34. ** ~~~ ** Check Sizing:Zone and ZoneControl:Thermostat inputs.35. 36. ** Severe ** UpdateZoneSizing: Cooling supply air temperature (calculated) within 2C of zone temperature37. 38. ** ~~~ ** ...check zone thermostat set point and design supply air temperatures39. 40. ** ~~~ ** ...zone name = CLASSROOM41. 42. ** ~~~ ** ...design sensible cooling load = 25499.10 W43. 44. ** ~~~ ** ...thermostat set point temp = 0.000 C45. 46. ** ~~~ ** ...zone temperature = 15.334 C47. 48. ** ~~~ ** ...supply air temperature = 15.000 C49. 50. ** ~~~ ** ...temperature difference = -0.33433 C51. 52. ** ~~~ ** ...calculated volume flow rate = 197273.21341 m3/s53. 54. ** ~~~ ** ...calculated mass flow rate = 237634.19357 kg/s55. 56. ** Warning ** ManageSizing: For a plant sizing run, there must be at least 1 Sizing:Plant object input. SimulationControl Plant Sizing option ignored.57. 58. ************* Testing Individual Branch Integrity59. 60. ************* All Branches passed integrity testing61. 62. ************* Testing Individual Supply Air Path Integrity63. 64. ************* All Supply Air Paths passed integrity testing65. 66. ************* Testing Individual Return Air Path Integrity67. 68. ************* All Return Air Paths passed integrity testing69. 70. ************* No node connection errors were found.71. 72. ************* Beginning Simulation73. 74. ************* Simulation Error Summary *************75. 76. ** Warning ** The following Report Variables were requested but not generated77. 78. ** ~~~ ** because IDF did not contain these elements or misspelled variable name -- check .rdd file79. 80. ************* Key=*, VarName=ZONE PACKAGED TERMINAL HEAT PUMP TOTAL COOLING ENERGY, Frequency=Hourly81. 82. ************* Key=*, VarName=ZONE PACKAGED TERMINAL HEAT PUMP TOTAL HEATING ENERGY, Frequency=Hourly83. 84. ************* Key=*, VarName=CHILLER ELECTRIC ENERGY, Frequency=Hourly85. 86. ************* Key=*, VarName=BOILER HEATING ENERGY, Frequency=Hourly87. 88. ************* Key=*, VarName=FAN ELECTRIC ENERGY, Frequency=Hourly89. 90. ************* Key=*, VarName=ZONE VENTILATION FAN ELECTRIC ENERGY, Frequency=Hourly91. 92. ************* Key=*, VarName=EARTH TUBE FAN ELECTRIC ENERGY, Frequency=Hourly93. 94. ************* Key=*, VarName=PUMP ELECTRIC ENERGY, Frequency=Hourly95. 96. ************* Key=*, VarName=ZONE VENTILATION TOTAL HEAT LOSS ENERGY, Frequency=Hourly97. 98. ************* Key=*, VarName=ZONE VENTILATION TOTAL HEAT GAIN ENERGY, Frequency=Hourly99. 100. ************* Key=*, VarName=EARTH TUBE ZONE SENSIBLE COOLING ENERGY, Frequency=Hourly101. 102. ************* Key=*, VarName=EARTH TUBE ZONE SENSIBLE HEATING ENERGY, Frequency=Hourly103. 104. ************* EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors.105. 106. ************* EnergyPlus Sizing Error Summary. During Sizing: 3 Warning; 1 Severe Errors.107. 108. ************* EnergyPlus Completed Successfully-- 5 Warning; 1 Severe Errors; Elapsed Time=00hr 00min 4.65sec109.…