. etc. So it's 80020 which is ~1058. Assuming you're allowed to use the same component more than once.
1058 × 1049 = 10107 total possible algorithms. When talking about big numbers I only have three frames of reference. The distance from us to the edge of the observable universe is roughly 1029 millimeters, the observable universe contains 1080 protons and the volume of the observable universe is roughly 5×10105 cubic nanometers. So you could more or less put a different valid Grasshopper algorithm into every cubic nanometer of this universe.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
in the .gh-file below. However, it takes a very long time to generate this calculation, even four about five panels or so, while I have about 1600 on the hyperbolic paraboloid. You once told me in another discussion that the TOF component did less calculations than the PV Surface component and would therefore be faster. However, it seems to go even slower when you have multiple surfaces.
So what I would like to know is how to have an idea of which PV panels would be worth of keeping on the hyperbolic paraboloid. For instance, to visually represent the panels with a TOF of >90%, >80%, >70% and so on, without too long calculation time.
(You will have to zoom out quite a bit to see the surfaces. The TOF component is in the red group and there is some part of the code that is irrelevant for this question, but it's quite clear.)…
gn-by-many-designbymany/
The first sponsored challenge is to create a parametric version of Buckminster Fuller’s Dymaxion House.
It would be AWESOME to see it done in Grasshopper! And.. You can win a pretty sweep HP desktop plotter. The deadline is this Friday.
Hope to see you on the site and look for some new GH and RhinoScript videos coming soon.
Thanks,
Dave…
Added by David Fano at 12:28am on December 15, 2010
pproach of estimating wind loads using design codes such as ASCE7-05.
B) Hiring a wind expert to construct a physical model and and calculate wind pressures measured directly from a wind tunnel test.
A) will allow you to derive a site specific wind design pressure based on the height of the building, surface roughness, site location etc. Typically you then multiply this pressure by an appropriate co-efficent in the code for a given building shape.
The other atypical method it to use numerical approaches such as CFD. This approach is not yet accepted due to nuances such as of surface roughness.
Building deflection is again subjective. Doing a modal analysis and getting an idea of the frequency is better. You can increase the frequency by playing about with the building stiffness.
You need to modify the stiffness of the building to get the deflection down. i.e. play about with geometry, add extra members with stiffness, reduce weight, use material with higher elastic modulus etc
If you are getting a 7m deflection for a 400m building then I can right away that is way too soft. That is equivalent to 400m/7m or H/57. You want to be at least H/500 to H/1000 so aim for 80 to 40 mm.
Your wind load seems reasonable at 87 psf for that height of building
…
it we thought our stands will be made with a fixed depth (80 or 90 cm) and incremental heights like 30-32-34-36...cm, and that is the list you have to supply.
The script will iterate over the different possible measures until it finds the smallest one that complies with your desired C value, but it wont be the exact, just the best approximation within your list.
2. Changing this also depends on the combinations of riser height and depth you provide, if you enter 1m and 1m in both lists you will get an 45º slope.
Anyway, getting a fixed-c value script would be easier (much easier than what is already there) but IMO it wouldn't have a direct application in real stadiums unless you are ready to make each stand different from the rest, discarding any pre-cast solution.
Hope this helps.
Roberto…
raries folder, seems that you need plankton.gha.
Unlock, place in folder, restart rhino+gh...
That's all.
To use it... in a basic way:
Input 0. Plug geometry.
Input 1. Set target resolution, actually it refers to the mesh edge length.
Optional input 2 and 3. Sets anchors (as points or curves) for the remeshing not escape of these parts.
Input penultimate. Number of iterations. Here are two ways, the living form, you set a low value (as 5 or 10) of iterations and plug in a timer component (that allows you to see the remesh process); or just add the total number of iterations (I generally use 80, but its relative).
The last input, set false to turn it on, true to turn it off.
For advanced configuration, trial and error, or see the code on Pikers's github.…
ьютера за требуемое время не получен нужный отклик, или было разорвано уже установленное соединение из-за неверного отклика уже подключенного компьютера 178.63.48.217:80This component requires OSM data to be downloaded from openstreetmap.org. It has just failed to do that. Try the following two fixes: 1) Sometimes due to large number of requests, the component fails to download the OSM data even if openstreetmap.org website and their services are up and running.In this case, wait a couple of seconds and try rerunning the component. 2) Try lowering the "radius_" input. If each of two mentioned advices fails, open a new topic about this issue on: www.grasshopper3d.com/group/gismo/forum." …
a with high impact and far from easy to customize.
I'm trying to use and understand the Dragonfly_Boundary_Layer_Parameters block, whose parameter setting seems to have a huge impact on the UHI results. In particular the nightBndLayerHeight parameter. First of all, the default value in the doc (800m) does not correspond to the one in the code (80m). After having set it at 800m with a constant block, the RunUWG component doesn't run until the end, giving the following error message : "Error in ReferenceSite/VerticalDifussionModel (line 141) / Error in xml_new (line 394)". It seems that some combinaisons of nightBndLayerHeight / referenceHeight work (80 / 100 or 800 / 800) and others not (800 / 100).
Does that comes from the model preparation? Or the UWG algorithm itself?
I tried to find for some "tables" linking these weather layers to the different urban typologies... without success. Would have someone ref / paper recommandations?
Kind regards,
Rom
…
CA, DA, DC)Two of those diagonal lengths are obviously redundant but they allow you to simply shift the array to get at different rotational permutations. This makes the search for the nearest mean a bit more straightforward since, in the context of panel clustering, you'd need to consider all rotational permutations of each one.…
Added by David Reeves at 5:26am on November 9, 2014
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.…