and perpframes
3) Ellipse on perframes
4) Series + Move + Series + Scale + Series + rotate (to create generations)
5) Divide curve (ellipse) + Dispatch only seleced points + join those points on ellipse using Intercurve + Divide the resulting intercurve
6) List items (I used list items 4 times, you could do as many). For 'i' parameter in list item i used slider to create generations. depending upon your definition, at this stage you might have to flatten your list output
7) joint the points you get from list output to form another intercurve + repeat that for all items.
8) Loft the curve
9) to form fenestrations, i again used rhino closed curves.
8) Project curve onto surface + copy trim + surface to mesh + mesh thickening from WB.
Hope this helps
Cheers
aB
…
his project. Attached is my latest script. It seems to work for all points & directions of gravity except when the points are at equal height (in the reference plane the script creates, not in the world space). In other words, when the vector from A to B is perpendicular to the gravity vector, it doesn't work. It's totally due to the formulas used to solve for distance (see script), but I haven't found a way to fix it to make it work. Kudos to anyone that can help me figure it out!
Other notes: Required input: Point A, Point B, Gravity vector, and desired Height and/or desired chain/arch Length. Cool trick: when inputting both Height and Length, it recalculates the end point (point B) with those desired parameters, and the end point lies along the AB vector. Also, the "x" output shows either the found height, length, or distance (when both height & length are input), and "newPl" just shows the reference plane used to make calculations easier.
Cheers…
Added by Will McElwain at 11:52pm on January 18, 2014
med that a 1000 lux measurement for a particular hour on a workplane grid point will indicate a illuminance from direct sun at that point. If I remember correctly, these simulations are to be run without the presence of any shading devices.
From an ASE calculation perspective, there are several shortcomings within Daysim (as it exists right now). The daylight coefficient method, which Daysim employs, calculates illuminance by dividing the sky into discrete patches. (http://naturalfrequency.com/wiki/sky-subdivision) For a clear sky with sun, the luminance from sun is accounted for by approximating the position of sun into 3 (as far as I know) patches. That in turn leads to an incorrect estimation of both position and luminance contribution of the sun.
Anyways, as I wrote in the begining, in my opinion the closest you'd get to calculating ASE from daysim right now would be running an annual daylighting calculation with Honeybee by setting ambient bounces as zero. A better approach, in case you are not trying to comply with something like leed v4, would be to do a DGP analysis as Chris mentioned in his post.
…
i projected my surface on XY plane, created voronoi curves on the planar surface and re-project / map the curves onto the subject model.
However, i'm not getting a desired result.
can any-1 please help me. or even show me a different way to model it via GH? I donot want to use rhino objects.
I have attached my initial sketch, GH and Rhino files.
Hope to find some solution so I could move forward :-(
Moreover, I could not convert the initial non-planar curves into surface hence I converted them into Mesh (thanks to 'Brian Harms' for helping me out). However, the protruding edges of the mesh is not a smooth NURB curve, it forms kind of vertices of a polygon. Any way to smoothen / fillet it? Will it affect when i commence 3D printing?
Regards,
aB…
/ interest to some of you. I'm attempting to generate "bricks" along an arc, the span of the arc is known (Line AB), as is the desired brick edge length (shown as chords on the dotted circle). Im am essentially trying to solve for the diameter of the dotted circle and its center point (C). The variables within the grasshopper script would be span (X), chord Length (Y) and number of segments to the arch (N). Lacking the radius or central angle means that Im unable to solve this using my limited knowledge of Trig.
I guess the key issue here is that chord length and number is driving the radius of the arc / circle. Hence why Im not simply using the divide curve tool.
Any input members might have would be fantastic and I'd be very happy to share the resulting file.
Thank you!
…
Added by Robert Harvey at 11:24am on November 20, 2012
join site boundary curves with voronoi curves so that voronoi curves at the edges becomes a closed polygon?
2)I want to create a line between voronoi curve control points and voronoi cell centroid points, such that each 2D voronoi cell is broken down into a sets of triangles. Please refer attached sketch.
3) Then How do i project voronoi curves along with triangl curves onto a vaulted roof?.
4) lastly, i want to give some thickness to those curve. i.e. the curves basically are structural beams of the roof. with my definition pipe command does not work very well i.e. pipes intersect and crossover at each vertices, which is not my intention.
attached is a sketch and my definition.
Can any1 help me with any of the 4 problems?
Thank you very much
AB…
g a problem though when trying to set a daylight simulation with some determined radiance parameters. Here's the problem: After many tries I think I found out that setting -ab = 6 and at the same time -aa = .05 creates some sort of problem, because when I try to do so My PC blocks for several minutes, without letting me manually end processes from taskmanager, and when I'm able again to enter grasshopper, i get the following error:
"Solution exception:index out of range: 0"
Does this really depends on the parameters and values I found out or is it related to something else? Is the problem relative to the structure of HoneyBee or is it just relative to my specific case (and maybe PC)? Is it possible to solve it, and if yes, how?
Atteched you find my rhino model and my grasshopper file.
Thanks in advance for your help and again many compliments!
Luigi…
being driven by the wii nunchuck... But, here's my issue. I tried it first by having the output from the listener be a 6-digit number... so, I'm using the (CInt(Val(StoredValue))) command and it's writing out 181130... and I can easily split it up selecting the Left(x,3) or Right(x,3)... I first rant that number through a Format("{0:000000}",x) so that even if one of the accx or accy numbers were a 2-digit number (so my overall number would only have 5-digits)... with this Format function... I'm always assured a 6-digit number. And this method works... except...
If the first group of numbers coming in only has 2-digits... So, lets say the accelerometer read out of the first one (accx) is 89. Let's say the accy read out is 119. So, when I run this through the Format function to make it have at least 6 digits, my number now reads 011989. So, if I were to take the first three numbers on the right, my read out would be 989... which is much higher than my expected (60-180 range that is really coming over the Serial Port)... So, I'm back to where I started... in that I need to figure out a better way to split up the data.
Which brings me to your method. I tried it as well... in fact, I added a comma in the serial readout, so the string coming out of the listener reads 89,119. So, I can use your trick to go look for a delimeter and then read to the left and right a certain number of digits... The problem I still have is that the data going into the function is a string, and thus even if I split the 3 digits to the right of the comma out (so, my output says 119)... it's still a string, and my number parameter is still red. In your picture above, was your original 181 130 a number or a string? My guess is that it was understood as a number, because your number parameters at the end are accepting the value. But, in my case... I'm still stuck with the inability to convert a string to a number... Does this make sense? And are their any other workarounds?…
Added by Andy Payne at 9:42am on September 3, 2009
ou will see all of the available components on a ribbon at once so there is no need to keep clicking drop down menus.
It's all about discoverability with GH. What if you're a beginner and don't know about the Create Facility (dbl click canvas) how can you find Extr?
Even if you hover over every component or use the drop down lists you will not see the name Extr appear anywhere.
Sure it makes sense that Extr is short for Extrude but it's also the Nick Name of Extrude to Point component
So you can easily miss the fact that one has a Distance Input verses a Point Input.
I think I made the move to Icons around about the move from version 0.5 to 0.6, possibly before. I initially thought that I would go back to text because I loved the mono chromatic look of the text but I soon realised that Icons were the way forward. The greatest benefit is speed. You don't need to digest and decipher every component (which is written 90 degrees to the norm).
I'm not saying you should move to Icons forthwith but at least consider that once you have a better knowledge and understanding of GH, Icons will set you free.
My top ten tips that I would highly recommend to anyone wanting to better themselves with GH.
1) Turn on Draw Icons
2) Turn on Draw Fancy Wires
3) Turn on Obscure Components
4) Use the Create Facility like a Command Line eg "Slider=-1<0.75<2" or "Shiftlist=-1"
5) Use Component Aliases to customise your use of the Create Facility eg giving the Point XYZ component an alias of XYZ will bring it up as the first option on the Create Facility as opposed to the other possibilities.
6) Try to answer other people's questions even if it's not relevant to your own area. By looking into solving a problem outside of your comfort zone and then posting your results it is very rewarding but it also lets you see the other approaches that get posted in a new light.
7) Take the time to understand Data/Path structures.
8) Buy a second monitor - There is nothing that can compare to real estate when working in Grasshopper.
9) Read Rajaa Issa's Essential Mathematics
10) Pick a panel in a tab on the ribbon and get to know every component inside and out and then move on. Start with the Sets Tab > List Panel…