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
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.
…
seems to be the options I can see.
with hoopsnake, I would like to set each sub axis to rotate 360 degrees while the axis directly one level up in the hierarchy will move 1 degree. repeat this step all the way down to the axis on the base will give me some idea of the physical space that is the robots workspace. but maybe the term workspace more specifically refers to the point the end of the tool can reach so I hope what I have written is not g!misleading.
the galapagos definition you sent me inspired me to look further into this topic. The primary goal is to model the workspace and singularity as if they were an object. I found a PhD work on workspace and singularity here. http://www.europeana.eu/portal/record/2020801/9BB75131B39EE8536A258D9BC9864E89486B0CB0.html?start=6
http://www.europeana.eu/portal/record/2020801/FDB9E3EBEA6DF5ADB318DCB5803FACF760427237.html?start=5
anyways its saturday so maybe monday i will have somethin! thx again.…
window in grasshopper (and even save it to a text-file)??
Is there a way of doing it without connecting/collecting all relevant components manually to say e.g. a panel component?
I am thinking of something like a "input-properties"-window, where all numeric variables of sliders etc. are listed inside grasshopper (and eventually can be saved to a text-file)... something like:
slider a: 0.23
slider b: 0.67
slider c: 1.0
panel a: 23
panel b: text
rotating knob a: 25
rotating knob b: 360
boolean toggle a: false
md-slider a: 0.5, 0.8
etc...
+
"save as..."-button
Does this function it exist? Is there a smart way to collect this information centrally?
With kind regards,
Chombolombo
…
Added by chombolombo at 4:48am on September 21, 2012
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
…