or each branch goes to col 1, element 2 to col 2 and so on. The issue I am having is how to deal with branches that have less than 5 elements. Notice how in the attachment the number 8 is at row 2 where I want it to be in row 3.…
Added by jon kontuly at 1:03pm on September 30, 2014
e possible to change the component definition making possible to customize the number of outputs.Now Dispatch moves "true" values to A and "False" values to B
INPUT:
L (List to work on) -> 1, 2, 3, 4, 5, 6, 7, 8
D (Dispatch Pattern) -> True, False
OUTPUT:
A (List) -> 1, 3, 5, 7
B (List) -> 2, 4, 6, 8
Could it be possible/useful to modify it so it could dispatch items to several outputs, like:
INPUT:
L (List to work on) -> 1, 2, 3, 4, 5, 6, 7, 8, 9, 0
D (Dispatch Pattern) -> A, B, C
OUTPUT:
A (List) -> 1, 4, 7, 0
B (List) -> 2, 5, 8
C (List) -> 3, 6, 9
maybe I'm missing something and there's already a component with this function... I have been searching on the forum for half afternoon, but can't find anything about it!
Thank you!…
Writing simulation parameters...3. [2 of 8] No context surfaces...4. [3 of 8] Writing geometry...5. unsupported operand type(s) for +: 'str' and 'list'6. Failed to write Pelle_aperture000 to idf file7. unsupported operand type(s) for +: 'str' and 'list'8. Failed to write Pelle_aperture001 to idf file9. unsupported operand type(s) for +: 'str' and 'list'10. Failed to write Pelle_aperture002 to idf file11. [4 of 8] Writing Electric Load Center - Generator specifications ...12. [5 of 8] Writing materials and constructions...13. [6 of 8] Writing schedules...14. [7 of 8] Writing loads and ideal air system...15. [8 of 8] Writing outputs...16. ...... idf file is successfully written to : C:\Users\Personal\Desktop\TESI\x001\THOR\EnergyPlus\THOR.idf17. 18. Set runEnergyPlus to True!
or this
0. Current document units is in Meters1. Conversion to Meters will be applied = 1.0002. [1 of 8] Writing simulation parameters...3. [2 of 8] No context surfaces...4. [3 of 8] Writing geometry...5. Runtime error (MissingMemberException): 'hb_EPFenSurface' object has no attribute 'blindsMaterial'6. Traceback:line 1567, in main, "<string>"line 2134, in script
i think that i've same problem with my windows...any suggestion???
Thanks for all…
{1;1;4}{1;1;5}{1;2;0}{1;2;1}{1;2;2}{1;2;3}{1;2;4}{1;2;5}{1;3;0}{1;3;1}{1;3;2}{1;3;3}{1;3;4}{1;3;5}
etc...
and I want to format as a text it so it replaces the innermost branch with a letter so {0;0;1} would read A-0-1. I am able to replace all the symbols using replace text but am no sure if there's a way to convert a number to a letter.…
Added by Ryan Whitby at 12:40pm on February 3, 2015
the curves on surface issue it's solved seting flatten to the surface control point output. Still didnt know how to group points like:
1;1, 2;2, 3;3.....
1;2, 2;3, 3;4....
1;3, 2;4, 3;5...
....
ems in the same way. Lofting was particularly difficult, you had to have a separate loft component for every lofted surface that you wanted to generate because the component would/could only see one large list of inputs. Then came along the data structures in GH v0.6 which allowed for the segregation of multiple input sets.
If you go to Section 8: The Garden of Forking Paths of the Grasshopper Primer 2nd Edition you will find the image above describing the storing of data.
Here you will notice a similarity between the path {0;0;0;0}(N=6) and the pathmapper Mask {A;B;C;D}(i). A is a placeholder for all of the first Branch structures (in this case just 0). B is a place holder for all the second branch structures possibly either 0, 1 or 2 in this case. And so forth.
(i) is a place holder for the index of N. If you think of it like a for loop the i plays the same role. For the example {A;B;C;D}(i) --> {i\3}
{0;0;0;0}(0) --> {0\3} = {0}
{0;0;0;0}(1) --> {1\3} = {0}
{0;0;0;0}(2) --> {2\3} = {0}
{0;0;0;0}(3) --> {3\3} = {1}
{0;0;0;0}(4) --> {4\3} = {1}
{0;0;0;0}(5) --> {5\3} = {1}
{0;0;0;1}(0) --> {0\3} = {0}
{0;0;0;1}(1) --> {1\3} = {0}
{0;0;0;1}(2) --> {2\3} = {0}
{0;0;0;1}(3) --> {3\3} = {1}
{0;0;0;1}(4) --> {4\3} = {1}
{0;0;0;1}(5) --> {5\3} = {1}
{0;0;0;1}(6) --> {6\3} = {2}
{0;0;0;1}(7) --> {7\3} = {2}
{0;0;0;1}(8) --> {8\3} = {2}
...
{0;2;1;1}(8) --> {8\3} = {2}
I'm not entirely sure why you want to do this particular exercise but it goes some way towards describing the process.
The reason for the tidy up: every time the data stream passes through a component that influences the path structure it adds a branch. This can get very unwieldy if you let it go to far. some times I've ended up with structures like {0;0;1;0;0;0;3;0;0;0;14}(N=1) and by remapping the structure to {A;B;C} you get {0;0;1}(N=15) and is much neater to deal with.
If you ever need to see what the structure is there is a component called Param Viewer on the first Tab Param>Special Icon is a tree. It has two modes text and visual double click to switch between the two.
Have a look at this example of three scenarios in three situations to see how the data structure changes depending on what components are doing.
…
a follow up question... how do I wrap a list onto itself at a certain frequency?
i.e. I want the list {1;2;3;4;5;6;7;8;9}
to become {1,4,7; 2,6,8; 3,6,9} wrapped every 3rd item
Added by Joshua Jordan at 5:30pm on November 17, 2012
ts, a value for each point.This script is wrinting in C#, not C++. And of course, can be done with standard components, perhaps someone else help you with that.…
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.…