algorithmic modeling for Rhino
Tags:
Hi aditya,
Can you please explain again the path sequences that you want?
and especially:
at the 3rd sequence you typed: (2,0) (5,1)...
shouldn't that be: (2,0) (6,1)...? since (5,1) is already used in the previous sequence?
Also, which is the final sequence and does it depend on the number of V segments? (does this number change or is it always 48 segments, thus 49 points?
If so is the last one: (34,0) (38,1) (41,4) (45,7) (48,8) ?
yes you are right. that would be the case.
i tried this. what do you think?
thank you nikos! im just comparing our two methods. it seems yours is SO much more elegant. and maybe even adaptable if i want to change the flow of the curve. mine is still quite primitive.
Daniel González Abalde suggested this a couple of days back. how does a graph mapper not give me smoother curves? i hope you will entertain these inquiries. although my immediate purpose may be solved, im not very intrigued about the working of these things, it was so much fun to figure this out :D
Well, between mine and yours there are very few differences. You actually created the lists of needed integers with fewer components, which is better! And I believe they are equally adaptable to different surfaces (unless I am missing something).
Daniel's definition, on the other hand, has the advantage of easily creating different curves on the surface. The smooth curves you ask about are mainly a matter of using [NURBS] instead of [interpolate curve] and settings of the graph mapper and the multiplier slider. If you use [Interpolate Curve] and play around with these settings, you can get section curves very similar to the ones you get with our definitions:
hey nikos. this is what my definition has evolved into; and its starting to get interesting. do have a look if you have the time its large and messy but it works mostly.
There is a few problems and im attatching the a concise version of just the problem part anyway.
im repeating the effect on the inside and outside of the handrail. the problem im facing is towards the end of the list, the lines start misbehaving. i cant understand why.
There is not the same number of points in the final sequence to conform to your Partition pattern. Similar to the beginning of your balustrade there isn't any curves in the top left corner of the surface, there should be none in the bottom right Or you should continue your surface past the end and then trim the curves back.
Here is a Shift List method that allows you to Short List the Branches to create the correct amount of curves (In Green)
Hello aditya,
I am afraid I can't understand your definition since there is an error at the beginning:
I don't get the purpose of the [removeDuplicateLines] component. And also why you are using it on the V isocurves which are curves and not lines (that's the error).
If you can explain this part to me I could get rid of the error and proceed to the rest of the definition.
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