before, it doesn't do anyting (at least for me).
The 5 cells from your first Rhino file still generate 5 edge lines for one cell. as the fillets are gone, we can safely join all segments regardles of the angle. now we can assume we have curves for each of the 4 edges. they may have kinks, but should be reasonably straight. We want do approximate them as a single line anyway, so we can just take the endpoints of those curves and connect with a staight line...
Now use voronoi to generate the rectangle. :D…
nd by changing the location of the points we can make a polyline. We will use the tween curve component to produce the middle curves and then we will thicken them by using offset and extrude to model the parametric roof elements. Finally, we can bake the elements in Rhino and use them in our projects.…
lightingControlGroup is reported in the Daysim report.
One main doubt I have is: when we use the lighting control groups should the _testPoints of the Honeybee_Read Annual Result I component be branched in the same order like the sensor points of each lighting control group? Actually I believe not because on the test points are given the main results about daylight availability and autonomy of Daysim and if we use smaller groups of point we will not have anymore general results for the entire room but many for the single zones.
To explain better: I have one large retail shop for which I am testing the daylighting autonomy and electric lighting saving given by skylights. I use one single (total of 1812) list for the test points then I subdivide the hall in 5 (before were 3) lighting zones so the sensor points are the same of the test points but divided in 5 separate groups. That is to say I am working with one single zone but asking 5 different lighting control groups in it. is it possible?
Francesco…
}
X*
{0;2;0}{0;2;1}{0;2;2}{0;2;3}
{0;3;0}{0;3;1}{0;3;2}{0;3;3}
And now we want to insert at the place marked with X* another list formated like:
{0;0}{0;1}{0;2}{0;3}
So we want it resulted like:
{0;0;0}{0;0;1}{0;0;2}{0;0;3}
{0;1;0}{0;1;1}{0;1;2}{0;1;3}
*{0;2;0}{0;2;1}{0;2;2}{0;2;3}* - the inserted list
{0;3;0}{0;3;1}{0;3;2}{0;3;3}
{0;4;0}{0;4;1}{0;4;2}{0;4;3}
Since we plug the list formated with only {A;B} into the place with has {A;B;C} then that list has to be reformated in the same manner and every lists which are next to it have to be reformated too by adding 1 to B so it's {A;B+1;C}.
Param viewer with the data tree diagram is a great tool for visualising data structure. It seems to me that it would be easier to play with lists in the same way as we do with connecting components together. So if we have list of points and we want to insert them at some certain place in the tree then we don't need to play with Patch Mapper, Insert List and others but we just plug them on one go into the tree and format will adopt itself automaticly according to the choicen position on the tree.
Same with OUTPUT. We can pick some elements from the tree and connect it to the component which will receive every element from that branch. (example):There is a list of points with complex data structure. we pick node {0;0;3} and move it out from param viewer to connect it with point component which will receive all the sublists with elements which are under it:
{0;0;3;0}0 - pt1 - pt2 - pt{0;0;3;1}0 -pt1 - pt2 - pt3 - pt...and so on...
I don't know if this solution make better sense then other solutions of this case. Maybe there are easier ways to do it without such complication and I have no idea about it :)
greets!
Adam
…
Hi,
Great job !
Maybe you can try with us : http://www.initial-lescreations.fr/
We did this before : it's a trophee but made an other version with the diameter close to 25 cm.
ied away on lunch break...
1 - Clean up the mesh a bit: Lots of ways to do this, but as a rule of thumb, it's probably best to clean the mesh as best you can before bringing into GH. But, for the sake of example...a basic method is comparing the normal of a face to a Z Vector, and if the comparison results in a match, within some tolerance...then you can get rid of it. When dealing with topography and slope, the common unit of measure is generally percent, but to start with, we can use degrees.
2 - Evaluate MeshFaceNormals: similar to step 1, you are simply getting the normal vector of a face, and comparing it to a Z vector. The important thing to note is that the Vector Compare component outputs radians. At this point, you need to either convert to degrees again, OR, do some math and convert to percent.
3 - Set Slope Zones and Ranges : There are a few ways to do this, but I think this is one of the most straight forward methods. Set your "slope zones", create some consecutive domains from those numbers, then just find the values that fit into those domains, (you have the values from step 2, so you can pump those into the N input of the Find Domain component.)
4 - Color Mesh by Slope Value : the gradient component is setting colors based on your slope range domains. Because you have input a list of domains, (0 to 10, 10 to 20 , 20 to 25, 25 to 40, and 40 to 60), the Find Domain component is actually just putting the slope values into the corresponding range, and then outputting the index number of the slope domain, (0,1,2,3,4). The gradient component then maps those 5 numbers, (0-4.....which is actually 5 numbers because list counts start, and include, 0), to 5 colors.
4a - NOTE: The gradient component needs a Lower limit, and Upper Limit. In this case we start the lower limit at 0, (index of first slope range...0 to 10). The upper limit is the index of the LAST item in the Slope Zone/Range list, which is 4. I used a list length component to get the length of the below list, (which correctly returns 5 items....but I need the index of the last one, so the expression subtracts 1 from the length total).
0. 0.0 To 10.01. 10.0 To 20.02. 20.0 To 25.03. 25.0 To 40.04. 40.0 To 60.0
Then construct the mesh again using the cleaned vertices and faces from step 2, only adding in the new colors.
The last bit of the definition is just visualizing the slope value on the face...it's kind of overkill, but shown as an example.
…
Added by Chris Hanley at 1:55pm on January 8, 2016
n it be achieved by keeping the u constant, rotating the v in 60degrees and mirroring this v to get three values? But even so how do we make them interact in a weaving behaviour? Pls help me!
Many Thanks…
(Grasshopper 0.9.0014 or later) component only. Previous versions of goat for legacy Rhino and Grasshopper are available through above download link.
Besides this shift towards Rhino 5, this release features
One-time validation through activation code instead of providing an email address at every download.
Improved error handling in case of invalid objective connections
Internal code cleanups and renamings for better error reporting
More robust detection of installation folder
We hope you are enjoying this release as much as we do,
simon…