ke this:
The polygon vertices are aligned at beginning and end for these values and you want the flattened list of points to generate a continuous curve - EXCEPT when 'pSegs' X 'incr' = 360. In that case, one continuous edge curve isn't possible.
Möbius strip logic! Not so simple. I can do it "manually" for any given case but don't have a general purpose solution - yet.…
Added by Joseph Oster at 11:43am on March 24, 2017
of mesh and poly line curves of Kangaroo2.
You just need to take care that particles of springs would not get inside volume. But that is SolidPointCollide goal, that check if particle is inside closed volume, If it is , it moves particle to direction of closest point of your balloon.
There is one example from 51st second:
CM5 Inflated Restraint from Petras Vestartas on Vimeo.…
get vectors by the normals but the vectors are more condensed on the top and bottom because of the u and v therefore through off the simulation. How can I achieve even distribution? or even just from a point? Could use a particle and somehow have its forces spread in all directions? …
able location for rooms, etc.
My project is written in C#, so I just needed the code and not the grasshopper plugin, but I tested it in Grasshopper and can share the plugin with you.
Here's a quick video demonstration of it:
I hope you find it useful.
Cheers,
Eirik…
sers in a lifeboat and cast them adrift with two days' provisions and a three minute youtube video. Oh, and may we interest you in Fusion 360?
OK, now that I've gotten that out of my system...
I know this is a longshot but is anyone aware of a way to select, say an edge loop in a tspline object and have that edge information brought into a tspline GH component? I can see how converting the tsplines into a mesh and then using Sandbox, for example, can allow you to specify edges but it would seem to defeat the purpose. Thanks.
…
ctors.
But I need the angle in absolute value from the X axis (from 0 to 360 or from 0 to 2pi) and the command "angle" computes the value between the vectors, without considering the clockwise direction.
I have read other similar issues but they try to rotate the vectors one to another. My problem is that I need the value of the angle to dispatch a list and it has to be the value from the world X axis.
I hope to have explained myself, my english is not the best.
Thanks in advance!…
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
…
triangles around a vertex make an angle of 360°, but the variation or defect from this angle is exactly what enables a polyhedral surface to form a discrete version of double curvature.
In fact there is a precise relationship between the Gaussian curvature of a smooth surface, and the angle defects of its polyhedral version - the curvature can be regarded as concentrated at the vertices. As you refine the division into more and more smaller faces, getting closer to smoothness, the angle defects at each of the vertices get smaller, but their total remains the same. So as long as you have a finite number of triangles, they can get closer to all being equilateral, with 360° around each vertex, but never quite get there.
For example, in the case of a closed surface without handles, the angle defects will always sum to 720° (this is Descartes' theorem, and the Gauss-Bonnet theorem generalizes this to a relationship between the integral of Gaussian curvature and the topology of a surface).
A regular icosahedron is a special case, where the angle defect is divided into whole multiples of 60° - so one triangle short of a full circle at each of the 12 vertices - but for most numbers of faces there will be no such neat division.
This being said, if you accept that what you want will not be achievable exactly, and allow some level of error from your conditions (such as not having the triangles touch exactly, or some amount of size/angle variation), then there are ways of finding an approximation.
In Kangaroo you can constrain points to a surface then use a combination of mutual attraction or repulsion and spring forces to relax points towards an even distribution. I'll post an example soon.
There are also some extra equalization functions coming in the new version that will help with this.…
Added by Daniel Piker at 3:09am on December 12, 2010
mponent works by lofting all curves inside of the same list at particular branch. Your offsetted-elevated hexagons and original hexagons have different path levels (the first one have lets say: {0;0;0;i} and the second ones have {0;i}. So when you input your offsetted-elevated hexagons into the "C" plug of the "Loft" component along with the original hexagons the corresponding pairs will not merge into one list on particular branch, but rather they will "stay" in the ones in which they already were. That means that each of those lists will have only one curve in it, which results in the "insufficient valid profile curves" - because you need at least 2 curves to create a lofted surface.
So what we need to do is to somehow arrange the path levels of these two hegon "groups" (the offsetted-elevated and original) to be equal. That is the point of simplify, flatten...Here is a more simpler example of all this story:
The "curves group 1" has path level {i}, while the "curves group 2" has {0;i}. If we input both of them into the "C" plug of the "Loft component, the Loft will not work (an "Insufficient valid profile curves" error message will appear).
But if we Simplify the "curve group 2" that will decrease our path level into {i} just like the "curves group 1" has. So in that case Loft component works.…
is the one-and-only constraint for the radius, you can make this arc thusly:
It is also -in a way- underconstrained as the three points must define the plane of the arc. But this is not possible if all points are co-linear (i.e. for a 180 or 360 degree arc). It is also not entirely obvious whether you want the clockwise or counter-clockwise arc segment.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…