EC
1. Between hours 1:00 to 24:002. Current document units is in Meters3. Conversion to Meters will be applied = 1.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\Freeformtower_IDF\EnergyPlus\Freeformtower_IDF.idf12. 13. Analysis is running!...14. ......
Done! Read below for errors and warnings:
15. 16. Program Version,EnergyPlus-Windows-64 8.1.0.009, YMD=2015.04.04 23:39,IDD_Version 8.1.0.00917. 18. ************* IDF Context for following error/warning message:19. 20. ************* Note -- lines truncated at 300 characters, if necessary...21. 22. ************* 577 Zone,23. 24. ************* Only last 1 lines before error line shown.....25. 26. ************* 578 Freeformbuilding27. 28. ** Warning ** IP: IDF line~578 Comma being inserted after:" Freeformbuilding" in Object=ZONE29. 30. ** Severe ** Out of range value Numeric Field#5 (Type), value=0.00000, range={>=1 and <=1}, in ZONE=FREEFORMBUILDING31. 32. ************* IDF Context for following error/warning message:33. 34. ************* Note -- lines truncated at 300 characters, if necessary...35. 36. ************* 586 BuildingSurface:Detailed,7341.
…
rse at WIT (http://designcomputing-wit-fa09.blogspot.com/), and through that I've gotten to know Aaron Willette a bit and learned more about what you guys do. He's a good guy. If you're in Boston any time soon it would be great to meet you and have you over to our office.
Matt
Radlab, Incorporated
25 Drydock Ave, Floor 6
Boston, MA 02210
W| radlabinc dot com
E| matt@radlabinc
P| 617.440.3588…
Added by Matt Trimble at 3:49pm on November 19, 2009
d the negative vectors into the direction input of the extrude I get 50 vectors against 25 surfaces. So the remaining 25 are all extrusion of the 1st item.
I solved it by using 2 extrude components, but that does not feel good enough.
I simply want 2 values to be applied to 1 surface, cant be that hard.
With the other dilemma (right picture) something similar happens: I wanted to weave the negative and positive vectors, to have one surface extrude in one direction, and the other in the opposite direction, alternating. Thing is I have 25 surfaces and 50 values, again. I believe I need to divide each list of 25 (positive) and 25 (negative) in 2. But thats 12.5 items/values, which is not possible.
I have uploaded the definition.
Thanks
…
Loop'. The fun part of the slower version is that you can see what it's doing while it's running. 'Fast Loop' gives no indication that it's working, so you want to test it with small numbers and be sure it's coded properly before bumping the iteration count up.
The GH profiler running the slow version showed between 1 and 1.5 seconds per loop, but the reality was more like ~10 seconds per loop toward the end of an 11 X 11 grid, or ~20 minutes total. It's easier to be patient because you know it's working.
The 'Fast Loop' finished the same grid in 1.6 minutes! An impressive improvement. I've been running it on a 30 X 30 grid (900 points) for ~23 minutes so far and see nothing yet. Not the ~12 minutes I had hoped for... Now 36 minutes on this loop for 900 points... hope it's not stuck. Not fast! Later - DONE!! Profiler says 59 minutes for 900 points but it was more like an hour and twenty minutes total. It succeeded, I have a single 'Closed Brep' from 900 extruded rings, baked to Rhino.
Another strategy to explore would be doing 'SUnion' on a smaller grid using the Anemone loop, then replicate it by moving it as needed to form a larger grid; then run the copies through another 'SUnion' loop. I went ahead and implemented that while waiting. It works and is fast! Started with 3 X 3 and ran the result again as 5 X 5 (9 X 25 = 225 total) in barely ~70 seconds!? Trying 36 X 36 now... 1,296 points appears to have succeeded in less than ten minutes! Though it seems to take quite awhile after the loop ends before control is restored to GH/Rhino. I'll let you do your own experiments and benchmarks.
I encapsulated the loop in a cluster called 'suLoop' (blue groups).
Internal of 'suLoop' cluster:
…
Added by Joseph Oster at 11:14pm on March 22, 2017
om frame -5 till frame -10 a frame spacing of 100mm is used,
etc.
Frame 0 is located on X=0 mm
Frame -5 will be on X=-500 mm
Frame -6 will be on X=(X of frame -5) -25 = -525 mm
Frame -11 wil be on X= ((X of frame -10) -10 = ?? mm
etc.
Cheers,
Bas…
ied away on lunch break...
1 - Clean up the mesh a bit: Lots of ways to do this, but as a rule of thumb, it's probably best to clean the mesh as best you can before bringing into GH. But, for the sake of example...a basic method is comparing the normal of a face to a Z Vector, and if the comparison results in a match, within some tolerance...then you can get rid of it. When dealing with topography and slope, the common unit of measure is generally percent, but to start with, we can use degrees.
2 - Evaluate MeshFaceNormals: similar to step 1, you are simply getting the normal vector of a face, and comparing it to a Z vector. The important thing to note is that the Vector Compare component outputs radians. At this point, you need to either convert to degrees again, OR, do some math and convert to percent.
3 - Set Slope Zones and Ranges : There are a few ways to do this, but I think this is one of the most straight forward methods. Set your "slope zones", create some consecutive domains from those numbers, then just find the values that fit into those domains, (you have the values from step 2, so you can pump those into the N input of the Find Domain component.)
4 - Color Mesh by Slope Value : the gradient component is setting colors based on your slope range domains. Because you have input a list of domains, (0 to 10, 10 to 20 , 20 to 25, 25 to 40, and 40 to 60), the Find Domain component is actually just putting the slope values into the corresponding range, and then outputting the index number of the slope domain, (0,1,2,3,4). The gradient component then maps those 5 numbers, (0-4.....which is actually 5 numbers because list counts start, and include, 0), to 5 colors.
4a - NOTE: The gradient component needs a Lower limit, and Upper Limit. In this case we start the lower limit at 0, (index of first slope range...0 to 10). The upper limit is the index of the LAST item in the Slope Zone/Range list, which is 4. I used a list length component to get the length of the below list, (which correctly returns 5 items....but I need the index of the last one, so the expression subtracts 1 from the length total).
0. 0.0 To 10.01. 10.0 To 20.02. 20.0 To 25.03. 25.0 To 40.04. 40.0 To 60.0
Then construct the mesh again using the cleaned vertices and faces from step 2, only adding in the new colors.
The last bit of the definition is just visualizing the slope value on the face...it's kind of overkill, but shown as an example.
…
Added by Chris Hanley at 1:55pm on January 8, 2016
each with 4 elements. When I connect the curves to the curve join component it creates 25 curves which is what I would expect. However, when I run it first through the param viewer I get an error. Seems to me like you would want to be able to get the same result can someone explain this.
Second, If I have 2 trees each with 25 branches and 1 element at each branch is there an easy way to get 1 tree with 25 branches each branch having one element from each tree. for example the first element of tree A should be with the first element of tree B and so on...
Thanks.…
Added by jon kontuly at 8:23pm on January 27, 2010
e
7. True
8. True <-- this one
9. True
10. False
11. True
12. False
13. True
14. True <-- this one
15. True
16. False
17. True
18. False
19. True
20. True <-- this one
21. True
22. False
23. True
24. False
25. True
26. True <-- this one
27. True
28. False
29. True
30. False
31. True
32. True <-- this one
33. True
Any idea how I can solve this?
Thanks!…