ange. So where this is a problem is in branch {4} (and others in my larger definition) where the sum of those numbers is 12 but when they are individually rounded to the nearest integer they happen to be rounded up so the new sum of the branch is 13.
In cases where this happens I would like to be able to add or subtract one from the largest number within the branch that needs to change to match its original sum. so in this case I would want {4}0 to be rounded to 6 and then have 1 subtracted from it but the other rounded numbers remain.
thanks,
- Michael -…
Added by Michael Jen at 5:13pm on October 27, 2010
planar.
I have noticed, that when I test different tolerance settings, I often get out more surfaces than input surfaces. The script dublicates some.
I attached a screenshot, where i look at path 13 of the tree. It contains 3 surfaces but not the right onces...
Do you have any idea?
…
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.…
ble.
The PathGen component that you see with the pathogen icon creates a string of paths that when used in conjunction with the Replace Branches component will put the values into a tree structure of 40 curves, 13 points, 3 components. Then you use the Path Mapper to put the three components together to easily make a point and then use the path mapper again to put all the points of a curve together to easily make an InterpCrv
The other User Object on there is the Mask Maker component that I use to aid writing the Path Mapper Masks …
tivas.
Desde lo básico a sistemas complejos + documentación para fabricación.
Orientado a Diseñadores, Arquitectos, Artistas Multimedios y profesionales afines.
Objetivos específicos:
• Distinguir los conceptos principales del diseño paramétrico y su aplicación en entornos de modelación CAD. • Manejar la modelación paramétrica de sistemas geométricos simples y complejos en Grasshopper 3D. • Aplicar el conocimiento paramétrico en la creación de documentación para construcción y fabricación de un modelo desarrollado en Grasshopper 3D. Contenidos: Sesión 1. Introducción a la modelación paramétrica. Sesión 2. Elementos geométricos y sus propiedades. Sesión 3. Estructura de la información. Sesión 4. Condiciones de campos, grillas y atractores. Sesión 5. Panelización de elementos en superficie complejas. Sesión 6. Parametrización orientada a objetos. Sesión 7. Documentación paramétrica 1. Sesión 8. Documentación paramétrica 2. Sesión 9. Modelación avanzada y optimizaciones. Sesión 10. Profundización personal.
Fechas : Del 14 de Marzo al 13 de Abril de 2016
Modalidad : Presencial
Duración : 30 horas (10 sesiones)
Horario : Lunes y miércoles de 18:30 a 21:30 hrs.
Facultad : Escuela de Arquitectura
Pontificia Universidad Católica de Chile
…
he start point.
Generation (2) i have 4 points + (3*3points) = 13 points.
Generation (3) i have 13 points + (9*3points) = 50 points.
But when i bake the python component i have 157 points ? Why ?
What's the logic behind this ?
Also how can i have in a, lists of points according to generations and for exemple in b lines according to generations too ??
Here's the code:
import rhinoscriptsyntax as rsimport random as rr.seed(seed)
def Main():....allGenerations = []....allGenerations.append(startPt)....curGeneration = []....curGeneration.append(startPt)....for i in range(gens):........newGeneration = []........for pt in curGeneration:............ang1 = r.randint(-30,30) ............ang2 = r.randint(90,150) ............ang3 = r.randint(210,270) ............dist1 = r.randint(10,40) ............dist2 = r.randint(10,40) ............dist3 = r.randint(10,40) ............zV = -1 ............newPoints = branch(pt, ang1, ang2, ang3, dist1/(i+1), dist2/(i+1), dist3/(i+1), zV) ............newGeneration.extend(newPoints) ............curGeneration = newGeneration ............allGenerations.extend(newGeneration)....return allGenerations
def branch(pt, ang1, ang2, ang3, dist1, dist2, dist3, zV):....ptP1 = rs.Polar(pt, ang1, dist1)....ptP2 = rs.Polar(pt, ang2, dist2) ....ptP3 = rs.Polar(pt, ang3, dist3) ....ptA1 = rs.AddPoint(ptP1)....ptA2 = rs.AddPoint(ptP2)....ptA3 = rs.AddPoint(ptP3) ....pt1 = rs.MoveObject(ptA1, [0,0,zV])....pt2 = rs.MoveObject(ptA2, [0,0,zV])....pt3 = rs.MoveObject(ptA3, [0,0,zV]) ....ln1 = rs.AddLine(pt, pt1)....ln2 = rs.AddLine(pt, pt2)....ln3 = rs.AddLine(pt, pt3) ....return [pt1, pt2, pt3]
a = Main()
Thanks for you replies and sorry for my noob questions...
…
rcks. Some of these are inherent to the language syntax, others are mistakes in the respective development platforms. Here are my pet-hates for both languages:
C#
1) Case sensitive. Yes. C# is bloody case sensitive. That just makes it so much harder to use the intellisense properly, not to mention it is a bug factory. The only thing a case sensitive language allows you to do is declare functions and variables with the same name, but with different cases. I cannot imagine this is ever a useful thing.
2) Event syntax. Handling events is ok (though I still prefer the AddHandler, RemoveHandler approach of VB), but raising events is an f-ing nightmare in C#.
3) Curly brackets instead of keywords. Every source code file I have ends with a cascade of curly closing brackets. I much prefer the VB approach of End If, End Class, End Namespace. It's just so much clearer when I can see which end constructs means what.
4) It doesn't compile while I type, so any errors in syntax/logic only surface when I explicitly compile. This is annoying as it drastically increases the time I have to spend when fixing dozens/hundreds of compiler errors.
5) No optional parameters in function signatures.
6) Weird keywords like sealed, virtual, pure etc. I much prefer self-describing words like MustInherit NotInheritable, MustOverride etc.
VB
1) Parenthesis for both functions and arrays. Stupid stupid stupid stupid stupid.
2) The editor replaces my carefully crafter scientific notation to decimal notation. I type
Dim tol As Double = 1e-12
and it is replaced with
Dim tol as Double = 0.0000000000001
Someone please fire whoever thought this was a good idea.
3) Array indexing, declaration and looping. VB is consistent in that it always uses base-zero for array indexing. C# (and C and C++) mix zero-based and one-based syntax. So plus two points for consistency but minus 13 for making me write "-1" whenever I need to do something with arrays.
4) Can't remember what #4 was supposed to be, but there definitely was a #4... Anyway, when I think of it I'll append another post.
At this point in time I hardly prefer either language. I think on the whole they are both beautiful and the DotNET framework is a work of art (and pure genius). I use both languages extensively in my daily routine and I'm very happy with them.
--
David Rutten
david@mcneel.com
London, UK…
pper.
3. Jon Mirtschin of Geometry Gym Ltd - Geodesic domes, minimal surfaces, mesh relaxing, tessellation and parametric steel frame modelling.
There will also be some additional work presented by current students at the AA School.
Thank you to Marco Poletto is helping this happen.
Registration Details:
Please send an email to fionuala@simplyrhino.co.uk she will reply to confirm your place. You must have an email confirmation in order to attend this event
Or Call us on +44 (0)208 498 9900
Space is limited.
There is no charge to attend this event.
Full event details here:
http://www.simplyrhino.co.uk/about/AA.html…
f is 0 the "domain" shrinks to a given dList value.
So searchMode 1 does a proximity search for each "domain" whilst searchMode 2 does a search for distances between the total min/max domains value. Depending on topology and dList values results may (or may not) differ.
Example: assume that you search proximity for 2, 4, 13 meters. Using the domainContol these "expand" to, say, 1.5-2.5, 3.5-4.5 and 12.5-13.5. Mode 1 finds prox distances within the 3 "domains" (excluding 2.5-3.5 and 4.5-12.5) whilst mode 2 finds distances within the 1.5-13.5 range.
Mind overlaps.
NOTE: David's excellent Populate thingy yields "even" distributions ... meaning that this may be not the ideal tool for that type of search.…
rything works as expected.
Spread A:
{0} 10 items
{1} 5 items
{2} empty
Spread B:
{0} 3 items
{1} empty
{2} 4 items
Merged:
{0} 13 items
{1} 5 items
{2} 4 items
Fine.
But now I have the situation that the number of branches can go down to 1, resulting in simplify effectively flattening the list, but merge somehow "remembers" the data structure and will result in something like:
Merged:
{0} 1 items
{0;0;0;0;0;0} 100 items
So this is happening even though all inputs are simplified. Shouldn't simplify also reduce all the items to just {0}, even when just one branch is present?
So is this expected behaviour? Surely the number of branches should be irrelevent for simplify.
Any workaround? I tried trim tree, but it fails because there is one branch with the correct {0} identifier. Basically it should flatten in that case, but not when there is more than 1 branch.
In the screenshot, D2 contains no data, but D1 is simplified, but retains its depth information and should also be {0}, as it does for any data that has more than 1 branch. The merge component makes it visible. Flattening is not an option.
…