12
z=2, f=14
z=3, f=16
for y=3
z=0, f=..... etc etc etc
I have created the GH algorithm (attached), but I have trouble to run all the values of z range for y, before going to y+1 (loop in a loop). Do I have to set it up in VB?
Thanks in advance…
lls? I am going to be laser cutting and have a bed size of 24" x 48". (It's a 12' x 12' cube, each cell is fabricated individually)
There are a few solutions I would see as acceptable but I can't figure it out:
1. Be able to see the bounding box for each cell and I can manually control the number of points and the spacing to visually check each fits in my machine.
2. Be able to actually limit the cells to the max dimensions of the bounding box and have it be an "incomplete" voronoi diagram until I have enough points properly spaced.
3. Be able to have GH determine a minimum number of points and spacing so that the square is complete and the cells fit within a bounding box (my machine bed).
Any help here would be great. Let me know if any additional information can help, and if this question has been answered too many times.…
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
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
am-10:45am Lecture/Classwork
Break 10:45am-11:00am
11:00am-12:30pm Lecture/Classwork
12:30pm-1:00pm Questions (optional participation)
Details: An outline of the class material is available HERE.
The class will be conducted in English using the GoToTraining software.
You will need Rhino 4.0 for Windows or the Rhino 5.0 for Windows beta installed. You will also need the latest build of Grasshopper. You may use the Rhino 4.0 for Windows evaluation version, however you will be limited to 25 saves. Using the Rhino for OSX WIP is not acceptable for this class.
NOTE: Pacific Time Zone!
Cost: 150.00 US$…
. They work well together.
I am however trying to link your work with some help that was provided earlier, as far as keeping this inded intact if a new road was added or if an existing line was changed. Basically this set of components would identify the new plot and set its index id as a new number, not interfering with the old plot numbers. E.g. there are 11 plots and I add a new curve after the second plot, the new plot would be numbered 12 and the original plots would continue with their old index numbers. That way no land use changes would be made if a new road was added. I'm trying to fit that into this new system. Obviously, I'm having some issues. If you're interested in taking a look, I've uploaded it here.
Hope all is well Peter!
Thanks to Pieter as well for providing some polyoffset insight!
…
Into the 'exposure mesh' imput, I've got a mesh with 30 faces. Into the 'obstructing geo' input I've got a data structure {[0-1]} containing lists of geometry to use as obstructions. Currently I have 2 branches going in here while i'm testing it.
Going into the 'ray direction' input is a similar data structure containing lists of vectors {[0-11]} (one branch for each month, each branch has multiple items) going in here.
If I set the exposure component to shortest or longest list, it gives out 12 branches with 30 items in each branch (for each mesh vertex).
If I set the component to 'cross multiply', it gives out 24 branches with 30 items in each. However, the 24 branches simply go from {0} to {23} which means that I can't separate out the results from the two sets of obstructing geometry.
Is it possible to a) get the exposure component to give the correct output, or b) reassemble the output into a {[0-1];[0-11]} format?
Thank you for your help! Steven…
scripting before and have just downloaded some help material and as with all these things, its gonna take me a while to get my head round it all.
A second query is that it only works when the reference points are created in Rhino, but when I create the twelve points in GH, it doesnt seem to work, is that another Scripting work aorund or the way I have adapted this File?
I really appreciate the help,
Thanks,
Dave…