0,
I want to move everything in {2} up 5 and 10 and 15,
Any ideas. I have been trying using the series component to create the right data structure but somehow its not working and i am sure there is a simple way?
Do i have to repeat the data so that the number of transform data matches the input list or is there a way to simply apply the transformation to everything in {0}{1} and {2} respectively depending on its structure ??
Hopefully this makes sense? I am not really sure but is it a job for stream - i cant understand why i cant get it to work. Sorry i am sure this is covered in the forums, i have been looking but cant anything which helps specifically.
Many thanks
Chris…
need to be set, maybe could help you. Group tagged Classify is the relevant part. More information is available here.
Classify items (say points from a grid, or circles, or rectangles to be extruded) by any parameter of your choice (say distance from attractor, or radius, or height of extrusion) allows you to set any property by class: radius, colour, or whatever, even height of extrusion.
An illustrative example:
1 Heights in [1, 17]
2 Subintervals: {[1, 2], [2, 2.03], [2.03, 4], [4, 9.1], [9.1, 16.99], [16.99, 17]}
3 New values: { 0.3, 2.9, 5.5, 13.2, 15.0025, 17 }
4 Examples: 9.23 becomes 15.0025 and 1.7 becomes 0.3
Every height belonging to first subinterval —[1, 2]— becomes 0.3, every height in [2, 2.03] becomes 2.9, and so forth. Actually, every rectangle with its —old— height of extrusion belonging to a specific subinterval gets corresponding value according to 3 for its —new— height of extrusion.
In order to perform a true partition —classes— covering 1, boundaries should be a monotonically increasing succession, and subintervals should be half-open as far as boundaries (2, 2.03, 4, 9.1 and 16.99) can’t belong to more than one subinterval/class —classes are defined to be mutually exclusive and collectively exhaustive—, but this isn’t technically necessary; overlapping subintervals are allowed by creating duplicates: same rectangle is extruded twice (or more times) but different heights, also according 3, are used for each extrusion.
Notice that 3 could be even more exotic:
{0.01, 0.1, 0.02, -0.3, -0.05, -0.8}
{-5, 0, 3, 0, -1, 0}
{-11/2, -9/2, π, 5/2, -3/2, -1/2}
{O, T, R, F, V, S}
You’ll have to recycle classify by distance, but I think for sure it will help you. If you need further assistance, or you have any feedback, let me know.
…
onsecutive points at the same height then your 'Break at discontinuities' component eliminates the middle point completely and then the 'Interpolate Curve' component gives a much bigger bump in the wrong direction. This was enough to get curves to meet from opposite sides.
I fixed this by changing the heights to 1.1 or 2.9, rather than 1.0 and 3.0, but it took a little while to work it out! Sigh.
I attach a new version. But I actually preferred it as it was before. See what you think!
Bob
p.s. in the first list, elements 11, 12, 23 and 24 go from 1 to 3; elements 17 and 18 go from 3 to 1. In the second list, elements 6, 17, 18 and 29 go from 1 to 3; elements 12 and 23 go from 3 to 1. Given the above fix, these can be easily seen.…
Added by Bob Mackay at 10:40pm on November 24, 2015
.6 minutes!!!!
134 boundary surfaces ("BLUE CURVES", Trimmed Surfaces) minus 24 "RED PATH" 'Untrimmed Surfaces', resulting in 162 'Closed Planar Curves'.
That's an average of 19 seconds per "RED PATH". That time varies depending on the size/length of the path - one of the shortest (i=17) takes 11.3 seconds while others take nearly 30 seconds each. Wow. Painful.…
NONE, in SIZING:PARAMETERS". I'm not sure of where to start in troubleshooting this. I've attached the file.
Thank you,
See the errors and warnings below:
{0;0;0}
0. Current document units is in Meters
1. Conversion to Meters will be applied = 1.000
2. [1 of 8] Writing simulation parameters...
3. [2 of 8] Writing context surfaces...
4. [2 of 8] Writing context surfaces...
5. [3 of 8] Writing geometry...
6. [4 of 8] Writing Electric Load Center - Generator specifications ...
7. [5 of 8] Writing materials and constructions...
8. [6 of 8] Writing schedules...
9. [7 of 8] Writing loads and ideal air system...
10. [8 of 8] Writing outputs...
11. ...
... idf file is successfully written to : R:\Green\SuRG\Building_Performance_Analysis\2016_analysis_studies\Energy_Analysis_Comparison\Honeybee_+_Ladybug\tutorial01\EnergyPlus\tutorial01.idf
12.
13. Analysis is running!...
14. ...
...
Done! Read below for errors and warnings:
15.
16. Program Version,EnergyPlus, Version 8.5.0-c87e61b44b, YMD=2016.10.31 11:39,IDD_Version 8.5.0
17.
18. ************* IDF Context for following error/warning message:
19.
20. ************* Note -- lines truncated at 300 characters, if necessary...
21.
22. ************* 24 Sizing:Parameters,
23.
24. ************* Only last 1 lines before error line shown.....
25.
26. ************* 25 None, !- Heating Sizing Factor
27.
28. ** Severe ** IP: IDF line~25 Invalid Number in Numeric Field#1 (Heating Sizing Factor), value=NONE, in SIZING:PARAMETERS
29.
30. ** Warning ** IP: Note -- Some missing fields have been filled with defaults. See the audit output file for details.
31.
32. ** ~~~ ** Possible Invalid Numerics or other problems
33.
34. ** Fatal ** IP: Errors occurred on processing IDF file. Preceding condition(s) cause termination.
35.
36. ...Summary of Errors that led to program termination:
37.
38. ..... Reference severe error count=1
39.
40. ..... Last severe error=IP: IDF line~
, value=NONE, in SIZING:PARAMETERS
41.
42. ************* Warning: Node connection errors not checked - most system input has not been read (see previous warning).
43.
44. ************* Fatal error -- final processing. Program exited before simulations began. See previous error messages.
45.
46. ************* EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors.
47.
48. ************* EnergyPlus Sizing Error Summary. During Sizing: 0 Warning; 0 Severe Errors.
49.
50. ************* EnergyPlus Terminated--Fatal Error Detected. 1 Warning; 1 Severe Errors; Elapsed Time=00hr 00min 9.34sec
51.…
,854,775,807 ie. a number that is 19 digits long.
Since GH is displaying numbers by default with the .0 at the end, I would say that removes 2 digits giving a maximum of 17 digits. Right now it seems to "break" the conversion after the 16th digit. So, close enough.
This is still partly speculation, but makes sense.
But the real question would be why you need to identify more than 9 quintillion objects!? Are you trying to recreate the universe in GH? ;)…
e of visualization as a means to convey information in the AEC industry. To complement this discussion, Dave Trautrimas will present some of his work and process, including the critically acclaimed Spyfrost Project.…