trying to do.
i have a spiral that i divided in grasshopper into 360 points, that bit i managed to do, what i want is to connect point 1 to point 2 with a line, then connect point 1 to point 3 with a line and so on till point 1 is connected to all the other 359 points in that order, once i have done that i want to then connect point 2 to point 3 and so on, i want to repeat this till i have a connection all the way down the spiral, i'm pretty sure that once the first set of points are dealt with then it should be fairly easy to replicate the procedure to do the other point connections.
Michael…
vature it makes things somewhat easier, but the surface in your file also has regions of negative Gaussian curvature.
To approximate a surface of negative curvature with a discrete mesh, we need the angles around some of the vertices to sum to less than 360°. This is impossible to do in a mesh with 3 hexagons around each vertex without making some of these hexagons non-convex.
There are a few possible approaches, but I would say how to automatically cover an arbitrary surface with nicely shaped planar hexagons is still an unsolved problem.…
Added by Daniel Piker at 10:25am on December 17, 2013
l at each point intersection, less 14. align holes to common angle between each 2 points of intersection (so ovals align with curve)5. copy 4. 360/60 about center circle (creates 6 curves rotated thru 360)6. it appears there a 3 more sets of curves that need to be taken care in the same way as 1 thru 4 (see colander pic)6. project the oval patterns onto, 1/2 a sphere somewhat larger that the surface circle, to avoid extreme oval distortion.7. needs some Boolean subtraction of holes from sphere surface
Does this simple road map have some merit?
…
ine will require a points and normal vectors. Give ArrPolar the same parameters used to position the diamonds, but use a point instead of a gem object. This will give you your points. The normals are just a vectors from origin to the points.
4. I added components to the attached file that includes a VB fillet routine. (I don't recall where I found it.) You have to play with the 2 Boolean values depending on the 2 surfaces you feed the routine. Also, be aware that Rhino does not handle filleted surfaces well when they come from Grasshopper. To fix this you have to invoke the Rhino command _DivideALongCreases - otherwise your filleted surfaces will have corners in them.
…
viors that aren't the sum of its parts... but as the project progressed, my understanding of the idea emergence has changed... The universe doesn't produce something out of the blue, everything is part of a series of events, its the minute deviance in the details and the reading that cause the system to tip from its usual behavior or appear random, emergence in true sense ( or strong emergence as they call it) is just apparent...
The next question that came to my mind was if the universe is a series of cause and effects, then does it produce emergent (new) rules of interactions of particles/ agents... it turns out no, as the universe evolves new rules do form, but then again, they are derived rules, not something out of the blue... they evolve from the current to produce new...
One thing is for certain, emergent systems produce structure and functionality from bottom up, they are capable of achieving very complex behaviors by interactions of simple rules at bottom level...
Coming to the spatial rules to produce emergent systems, one example is the circulation in my system, which resolves itself providing various exit routes for any organization.
There are 3 agents namely personal spaces, combine spaces, open spaces
These are the rules (very simplified)
Two personal spaces share one common wall
Newborn Personal space will share at least one wall with the parent
A Combined space hold up to 3 personalized spaces only
At least one side of combined space is connected to an open space
Every open space have at least 2 open spaces connected to it to provide entrance and exit
http://www.youtube.com/watch?v=HkKMImNOATM
The result produced is this simulation, where red and blue are the personalized and combined spaces while yellow are the open spaces... Things to observe here is the circulation being resolved and the creation of wide open spaces, which was never intended or expected from the code... and it is not a coincidence, no matter how times and in how many different ways it is simulated, the circulation resolution and the wide spaces are prominent, so it is part of the system behavior
…