x and min values for x,y,z and calculate energy for each optionand collect these results in excel sheet ...
option No. x y z Annual coiling demand(by DIva)
1 10 10 10
2 10 15 20
3 11 10 19
4 12 14 17
5 15 16 15
6 16 11 14
7 18 12 12
.
.
etc
Regards ...
hossam
Hossam.wefki@gmail.com…
cture, Rhino treats them as a single flat list. For example a surface can have 10 rows and 6 columns of control-points, resulting in a list of 60 points.
But 10 times 6 isn't the only way to get to 60. If you want to make a surface out of a list of 60 points, you'll also have to tell Rhino how those 60 points should be interpreted in terms of a grid. It could be 2*30, 3*20, 4*15, 5*12, 6*10, and all of the aforementioned products the other way around.
Sometimes there's only one way for a number of points to fit into a rectangular grid. For example if you provide 49 points, then 7*7 is the only way to make it work, but these cases are rare so we always demand you give us all the information required to actually make a rectangular grid of control-points from a linear collection.
As for "Why is it, sometimes we need to attach additional value into it?", this is usually because when you divide a domain or a curve into N segments, you end up with N+1 points. For example take the domain {0 to 5}, and divide it into 5 equal subdomains. You end up with {0 to 1}, {1 to 2}, {2 to 3}, {3 to 4} and {4 to 5}. However there are six numbers that mark the transitions between these domains 0, 1, 2, 3, 4 and 5. This is why you often have to add 1 to the UCount, because the number that controls the UCount often results in N+1 actual points.…
Added by David Rutten at 8:30am on December 25, 2014
work. If you have been looking for an opportunity to get into a new part of the software or just want to get updated on the latest developments in a 90-minute presentation, then these webinars are for you. Starting this Thursday at 12:30 EST, the workshops will begin by covering basic Ladybug capabilities and will provide a survey of the latest community resources. Each Thursday, there will be another presentation covering progressively advanced topics. In total there will be 5 workshops, each of which you can register for by clicking below:
1 - Ladybug Climate Analysis - August 25th, 12:30 PM EST2 - Ladybug Facade + Shade Design - September 1st, 12:30 PM EST3 - Honeybee Energy, HVAC + Indoor Comfort Modeling - September 8th, 12:30 PM EST4 - Honeybee Daylight + Electric Light - September 15th, 12:30 PM EST5 - Honeybee THERM + WINDOW - September 22nd, 12:30 PM EST
Notably, workshops 2, 3, 4 and 5 will feature substantial coverage of capabilities that do not currently have tutorial videos. This includes new view analysis and tips and tricks for radiation studies in webinar 2, newly-released HVAC capabilities for webinar 3, electric lighting capabilities with webinar 4, and all of webinar 5 will be brand-new hot-off-the-press development! Hope that you can attend!…
That is correct. In reality there are 3 major versions of .NET 1, 2, and 4 (different versions of mscorlib.dll)
Rhino 4 uses .NET 2 which includes 3 and 3.5.
Rhino 5 uses .NET 4
lues. What I want to do is combine them so that the structure would be something like:
{4;0}
{4;1}
{4;2}
{4;3}
{5;0}
{5;1}
{5;2}
{5;3}
I tried the method here, but it didn't give me what I wanted, it was just tacking the new values onto the end, and not maintaining their paths. Any help would be appreciated. Thanks!…
Added by Dennis Goff at 8:13am on February 10, 2016
nts me this:
[[0], [0, 1], [0, 1, 2], [0, 1, 2, 3], [0, 1, 2, 3, 4], [0, 1, 2, 3, 4, 5], [0, 1, 2, 3, 4, 5, 6], [0, 1, 2, 3, 4, 5, 6, 7]]
this is what I wanted but how to convert this to tree in grasshopper?
In grasshopper I just get:
8x IronPython.Runtime.List…