know how to solve.
It appears in
11 - Honeybee Energy Modeling - The Laws of Geometry in E+ Part 3: Curved Geometry
where I need to retrieve .idf file,
and shows this message:
1. Solution exception:'hb_EPZoneSurface' object has no attribute 'punchedGeometry'
I've added .gh file at a state where I meet the problem.
Also, I've looked around the forum and found some mention OpeanStudio related problems, mainly one's lack of it. Could it be the source of the problem, because I only followed Installation Instructions and haven't installed OpenStudio.
…
g a nurbs curve through a set of N-dimensional points is not the same as cubic interpolation of a linear data-set.
It's certainly possible to fit a nurbs curve through a set of point with a one-x-one-y constraint, but Rhino does not have such a fitter in the SDK, so it needs to be written from scratch.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
etting when I merge the three trees, but what I would like to get is:
essentially a tree with 27 branches, each with a single list of either 11 or 21 points.
{0} (N=11)
{1} (N=11)
...
{10} (N=21)
{11} (N=21)
...
{17} (N=11)
{18) (N=11)
{27} (N=11)
Any help would be greatly appreciated.
All the best,
Matt
…
Added by Matt Schmid at 3:06pm on December 4, 2010
where each branch contains all the points generated by dividing each curve, so if you divide into 10 segments, you'll get:
{0;0}(N = 11)
{0;1}(N = 11)
{0;2}(N = 11)
{0;3}(N = 11)
{0;4}(N = 11)
Where the second integer in the curly brackets refers back to the index of the curve in the original list.
Another way to look at this data is to see it as a table. It's got 5 rows (one for each original curve) and 11 columns, where every column contains a specific division point.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
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…
I've attached a rh and ghx file. http://we.tl/ghsd0UTxji - wetransfer link. I'm guessing the trick is to correctly define the Range (R) / Domain in the Random component, so that the circles' radi can vary between the fixed and static domain of 10 or 12 or 14 or 18 or 20. Meaning that the radi can only be 10, 12, 14, 18 or 20 - and not, lets say.. 11, 13, 15, 16, 17 or 19 for that matter. Thanks in advance, i hope someone can figure it out, because i can't seem to find anything online about how to set up such as specific domain.
…
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
as follows.
We have a grid which consists of a collection of columns, where each column consists of a list of points. You said flattening is out of the question, so we need to cull items from each list individually.
Let's say our culling pattern is KDDDKDD (repeat as needed). K = Keep, D = Ditch. If a column contains 18 points, the pattern needs to be repeated until it is 18 items long. In this case:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
K D D D K D D K D D D K D D K D D D
We can now cull each column, but they will all be culled in the same way. By shifting the pattern one more index for each column, we can cycle the culling.
The fix incidentally is to Shift the pattern PRIOR to repeating it. Then it works as expected:
--
David Rutten
david@mcneel.com
Tirol, Austria…
Added by David Rutten at 2:49pm on October 2, 2013