Gradient skeleton

unhandled

(Smywshdj) #1

hi everyone, I’m a student now new to grasshopper. I meet a problem that I want to create a gradient skeleton but I fail. What I trying to do is as the picture shows. I have try to do it but it shows like the thickness doesn’t generate by gradient.

could anyone know how to fix it? Thank you very much.


(Pfotiad0) #2

No def attached (you should do that always). Anyway … If you use ExoW it’s rather tricky (occasionally turns red and reports engulfing issues where they are not around).

See 2 defs attached (ExoW+Topologizer+WB+MeshMachine) . The 1st uses code for locating possible short edges issues. That said I had some simpler cases with native components but Iin a recent clean-up I’ve removed them all.

Thicken_line_graphs_23A_V2.gh (135.5 KB)

You can further elaborate on this as well (adding attractors):

Thicken_line_graphs_17A_V1.3dm (87.9 KB)
Thicken_line_graphs_17A_V1.gh (33.6 KB)

BTW: Try Intra Lattice as well (yields worst aesthetics)


(Pfotiad0) #3

And this … well is using ExoW VS Intra Lattice on a K1 (it’s a very old def I confess) random relaxed mesh - you can add attractors for a var thicken effect . In most of cases ExoW turns red (IL on the other hand manages to solve the case with the very same inputs):

Thicken_case2_V1.gh (145.3 KB)


(Smywshdj) #4

hi PeterFotiadis,
Thank you vary much for your answer, they’re awesome. Actually, there’re out of my knowledge unfortunately since I’m a really new fresher in grasshopper. What I’m trying to do is I have generate many curves by random points, then I want to create the thicken skeleton gradient for this shape which I create it by topology. the file I have attached here sorry forget attach it before, And what I want to create is like the picture shows.sizing EXOskeleton.gh (238.8 KB)
final triangle lines - sizing optimization.3dm (13.3 MB)

I tried what you helped, but fail since I couldn’t understand the scripts, really sorry. could you have a look and tell me what should I do to fix it? Thank you vary vary vary much.

Mengyan


(Pfotiad0) #5

Well … as I said the bad news for you are that I don’t work with components (except doing some defs occasionally for helping someone). Meaning that things that are trivial/right to the one side are freaky/wrong to the other.

That said try to work with lines and not curves especially for complex stuff (unless you have a CRAY).

The other bad news are that for random 3d line graphs (Voronoi type etc etc) … well … short edges are more than propable (conditional 3d Proximity is way better … but even so ExoW is temperamental) … and that assumes a super ExoW that could handle any similar engulfing situation (very easy to say, not so easy to do it). On the other hand stuff of that kind are not exactly ideal tasks for a novice (but I always admire people who don’t accept no as an answer, he he).

Anyway I’ll try this w/e to make some simple defs that can quide you around (and inquire the attached as well)


(Pfotiad0) #6

Here’s the first lesson:

  1. Whatever you do NEVER wait a stupid thing (the computer). If your solution takes ages to finish (meaning lot’s of milliseconds NOT seconds/ minutes) change approach and/or design goal. A Lotus Elise (or better: an Exise) eats anything out there for breakfast because is less not more. If you’ll become at later time a pro you’ll see what all these mean.

  2. Proximity (controlled with regard min/max search radii et all) is the way to go (regardless the shape: more on that on the 2nd lesson) since makes life for ExoW/IL far easier (for obvious reasons).

  3. Exploit the limits of such an approach: by what means can we be sure for the inputs to ExoW/IL? (are they small, big or just right?) When the def becomes a torture instead of a joy? When parametric becomes just a mind trap and/or a virtual desire? When it’s time for reinventing the wheel? (see 1).

Proximity_VS_ExoW_V1.gh (24.4 KB)

Next lesson: one/many attractors (for var ExoW stuff), pull/push mode, shape control (and random points inside (and/or on skin) for proximity), cats, dogs and the likes.


(Smywshdj) #7

thank you for your teaching, that could be very important lessons in my studying process. I know what you meaning since I calculate the model part by part, actually it take me half a day to finish such model. It’s really stupid but since the limit of my knowledge, I have to do like that… But I’m still in the process of study, I could do it a better way when equip the knowledge enough. What you told me is really Inspiring, looking forward to you next lesson.


(Pfotiad0) #8

Next lesson would elevate things (a bit). In the mean time and if you are after AEC matters think: what is the most stunning contemporary thing around? Is it a twisted tower that looks like an ugly blob that married another ugly one? No I’m afraid: is I.M.Pei masterpiece (that pyramid: less is more my friend [same applies for that Lotus]).


(Pfotiad0) #9

Here’s the second lesson:

  1. I was ready to add all the bits promished … but then I said to myself: why not making 3 challenges for the brave? See inside def.
  2. Push/Pull effect (for var Radii) is not “by the book” since it doesn’t take into account distances per start/end graph line points. But keep it simple: in complex graphs who’s gonna notice it? (don’t get lost in translation).
  3. ExoW still is wild and occasionaly refuses to play ball: I would recommend taking the 3rd challenge and provide the IL var Radii component with a similar functionality,
  4. For good reason raising the N of lines out of the Prox component raises exponetially the delay. Where parametric starts and where ends? Are all these somehow just another chimera?
  5. Can we do things that the third lesson (V3) would do with native components? Who knows?

Proximity_VS_ExoW_V2.gh (31.2 KB)


(Pfotiad0) #10

Whilst lesson 3 (V3) is almost ready: a quick question closely related with the density of thick struts near by the end of the conic [ I seriously doupt that ExoW can do it due to engulfing issues]. Is this some AEC thingy? (Architecture, Engineering, Construction) or just an abstract decorative object?


(Smywshdj) #11

Thank you very much for all your lessons. these are really benefit my study a lot. I will think what you have told me carefully. Best wishes to you.


#12

hello, I don’t pretty much understand what you’re gonna do. But looking at your picture, I think it is more likely done by another plug-in named Cocoon also developed by David Stasiuk.

http://www.bespokegeometry.com/2015/07/22/cocoon/

Take a look at this page, and there’s also a few very helpful examples included. It may be possible for you to generate a gradient thickness model.

good luck!
Jack