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.
…
、、、不同角度的理解、诠释、运用和发掘规律、、、
新闻或者幻觉:马王堆墓穴中发掘出了丝绸做的鞋,不算是现代意义上真正的鞋,但是完成了一个完整的公式。
有一部分需要是共同的,在离开了沙滩和草地的时候。
找一个成熟的不一样的数学思维合作者,(可以一起申请参加sg2014活动,也可以不)
我想听到人们写给自己的语言,我不害怕听不懂;
也不在意你能看到我的美丽的脚和我们美丽的城市。
你存在?存在0.1%?如果≥1/4
With the two version of the PDF in the file upload, doubt, 10th should be able to see the many PDF.
There are some scruples, confusion ——"The additional property of professional activities",——Subject classification, commercial, regional、、、
There is a place Africa, people don't wear shoes, A few people with grass or leather on the foot (and buildings——In order to spatial density) winding,
the manufacture of shoes, two sales do two judgment:
A There is no life belongs to shoes
B this is the market.
I spent a lot of energy explained to students, which is not to do programming people do、、、 the different angle understanding, interpretation, application and explore the law、、、
The news or illusion:Mawangdui tomb unearthed silk shoes , is not the modern sense of true shoes, but the completion of a complete formula.
There is a need is common, when they leave the beach and grass.
Find a mathematically mature different thinking partners,(Can apply to participate in the activities of the sg2014, also can not)
I want to hear people wrote their own language, I am not afraid of don't understand;
Don't care what you can see my beautiful feet and our beautiful city.
Do you have? There are 0.1%? If ≥1 / 4 You know what I did wheni found out about you?
msxf6688@163.com
…
)
3. KeyError(1417,)
4. KeyError(1417,)
5. KeyError(1417,)
6. KeyError(1417,)
7. KeyError(1417,)
8. KeyError(1417,)
9. KeyError(1417,)
10. KeyError(1417,)
11.......
i tried different weather file but also same result. it seems i have same problem. the file am working on is the radiation file i took from the examples . whats seems to be the problem?
thank you for your time…
ggle A
7. Toggle A
8. Toggle 2
9. Toggle 3
10. Toggle A
11. Toggle A
12. Toggle 3
I was thinking to use somehow slider and animate option....but without luck
Any idea would be appreciated…
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…
body help?
The problem appears when I delete the curve number 13 or 11 or 5 or 4 or 0.
See attached grasshopper file with the related rhino file.
thanks,
Bas
Rhinocentre.nl…
ee 3)
{5}
0 15
{6}
0 16
And I want to place points at every possible combination of these coordinates, treating Tree 1 as X coordinates, Tree 2 as Y coordinates, and Tree 3 as Z coordinates. Also, I would like the list of points to be a tree with paths corresponding to the coordinates. Wouldn't it be nice if I could plug these trees into a Point XYZ, with a new "branch cross reference" method, and get the following result?
{0:3:5}
0 {10.0, 13.0, 15.0}
{0:3:6}
0 {10.0, 13.0, 16.0}
{0:4:5}
0 {10.0, 14.0, 15.0}
{0:4:6}
0 {10.0, 14.0, 16.0}
{1:3:5}
0 {11.0, 13.0, 15.0}
{1:3:6}
0 {11.0, 13.0, 16.0}
{1:4:5}
0 {11.0, 14.0, 15.0}
{1:4:6}
0 {11.0, 14.0, 16.0}
{2:3:5}
0 {12.0, 13.0, 15.0}
{2:3:6}
0 {12.0, 13.0, 16.0}
{2:4:5}
0 {12.0, 14.0, 15.0}
{2:4:6}
0 {12.0, 14.0, 16.0}
In this form of cross referencing, every combination of individual branches from the different lists is used as separate input, and the output for each combination is put onto a branch in the result whose path is the concatenation of the input branch paths used.…
Added by Andy Edwards at 7:03pm on November 3, 2009