circles that can be populated (for each radius size) is set as an integer (or slider)
(ie. radius 1.5 = 10 , radius 3= 6, radius 6 = 6, radius 9=4)
Conditions are:
1) Each of the circle has a radius of influence,
Radius of influence = double the radius of the circle)
(3, 6, 12, 18)
2) Any overlapping circles in either: Radius of influence or the Circles are removed so that
No circles overlap.
3) There must also be 4 circles set at the corner points of the grid - These must be circles with a radius of 3 or 6
If you can do that I will be amazed as i've been trying for weeks! :(
Ive attached a sketch of what im looking for…
12 for the number of steps. So, you need to edit the Quad Stepper Firmata for Motor A (for example). On line 29, you need to change the line to: #define DIR_PIN_A 10 and then change line 30 to: #define STEP_PIN_A 12. Then, upload this to your board and then go through your Grasshopper process. Note, the Firefly shield only uses one easy stepper driver... so you'll only be able to control a single stepper. In the example outlined above, we modified it so it works with Motor A (or Motor 1). So, in your Grasshopper example the only one you will be able to control is the M1 input. …
output will show a tree with 3 branches of 4 integers each that I can pass on to other components. What is the best way to do it?
I have tried creating a tree and using a for loop to do so, but it didn't work.
Thank you for your help.
…
uld be much better than Rhino at huge mesh collections. I'd personally try free Autodesk Meshmixer and ZBrush first but most designers are more familiar with rendering programs like Maya or 3DS Max. I'm not familiar enough with architecture to suggest a list as only Revit and Sketchup come to mind.
Looking more closely, CAD Exporter is only for 2D curves and points, how silly, and it requires baked geometry in a Rhino layer:
I could write a Python script to export an STL but that would be a large ascii format file instead of binary. Better to use OBJ to retain quad faces, too.
Ah, well, OBJ files are also ascii format when exported from Rhino, so it would be quite easy to make a script to export those directly to disk from Grasshopper. Here is one box, 10X10X20 in size, with quad faces:
# Rhino
o object_1v 10 10 20v 10 10 0v 10 0 20v 10 0 0v 0 10 20v 0 10 0v 0 0 20v 0 0 0f 5 7 3 1f 5 6 8 7f 3 7 8 4f 2 4 8 6f 5 1 2 6f 3 4 2 1
If I have time I'll make a little script to write such OBJ files unless you can find a native Grasshopper plugin for direct OBJ export in full 3D for meshes.…
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