algorithmic modeling for Rhino
Hi guys, I'm currently working on a "V" structure for a project, and I want it to incrementally scale its size along a curve. Wat I did was copying it several times then scale all of them (see attached picture 1), but the thing is that the center of the scale must be at the end of every curve so it can be continous and not overlapping each other.
I also tried to do the same thing but scaling them between two boundary curves (see attached picture 2 from rhino), but I guess I first need to know the logic of the proportional scaling process, so I hope somebody can help me out with this problem.
Any comment would be apreciated. Thanks!
Tags:
I stumbled around in circles for awhile on this one... I skipped "along a curve" because that implies orienting each copy so that both of its ends are on a "curve"; more complicated than just putting them all in a straight line.
I scaled all the copies in place, then moved each one in 'X' by the sum of the distance between end points of its predecessors.
Erik - Are you scaling only height? (I don't read hieroglyphics)
Hey Erik, thanks for the time, thats kind of what I want, but i certainly need to scale the whole geometry, not only heigth, so that way the angle between each V columns can be the same. Please see the response to Joseph, I think I made it more clear.
Cheers.
Hey thanks Joseph, sorry I mentioned "along a curve" because it actually is, but for this purpose I set it to a straight line. Your definition seems to solve one of my problems, but I need more control over the scale factor, I mean I have these two curves; one is for the base, and the second one defines my initial and last heigth, so I have to scale them between these curves. The picture below shows the real situation, that was a test I did but is not what I want beacause the angle between each column is different. I hope I've been clear, and thanks a lot for the time.
Uh... I'm sure this is one of the classic CAD riddles that amuses the experts as they watch us re-invent the algorithm(s). :)
Hey Erik that's exactly what I wanted, thanks a lot! My head just exploded yesterday trying to figure it out how to do it. Is it possible that you share with me this definition?
Thanks again Erik!
Cheers
Hi Salvador,
Glad I could help! Hopefully this is what you need. I have attached the definition. I always find it ironic that the annotation portion is longer than the actual definition.
Furthermore, sorry about the confusion pertaining to the icons vs the names. I always had an easier time with the icons but certainly understand reasons for not using them - such a controversial topic :) My last professor wouldn't let us turn in definitions unless they had icons and said David originally designed Rhino's icons and that his GH icons were an extension of this. So who knows... they are quite nice.
I had the same issue with the wrong image opening, must be a glitch.
And an explanation of the definition. (I mostly explained it in the definition).
It's pretty simple actually:
1. Use range and graph mapper to generate incremental t parameters and turn them into points with evaluate curve.
2. offset the points and merge them into couplets
3. find the average (which is not on the curve) so use 'curve closest point' to mitigate this.
4. move average point in zedd direction with measured distance between each each associated couplet branch. Then merge into triplets.
5. I like using the Human plugin to visualize lineweights etc.. but if you don't have it, there is no need for it.
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by