Grasshopper

algorithmic modeling for Rhino

Hello,

I have what I believe to be a simple problem:

I have two pairs of lists of curves. Let's take one pair as an example. Both lists in this pair have the same (x) number of items. The indexes of both lists match ("1" in list A and "1" in list B match in the way that I want them to.

I want to plug list A into the "curve", and list B into the "section" node of a "sweep1" component. The result I desire is that the curve "1" in list A 'sweep' along the section "1" in list B. I would like all of the items in both lists (and the other pair of lists for that matter) to interact in exactly this same way.

How do I command the "sweep1" component to understand what I want it to do? I have tried any number of combinations of grafting and flattening the data, the problem seems to be with the "S" node of the "sweep1" component. Is it incapable of applying more than one index to the "C" component? When I have grafted my list B (thereby applying an index of "0" to all the curves within it), the "sweep1" component has "worked", but obviously just sweeps every "C" curve along every "S" curve (not what I want).

In the screenshot I show the "sweep1" component working when I input the same item from lists A and B of each pair.

Any help would be much appreciated

Views: 2650

Attachments:

Replies to This Discussion

Hmm ... def is required in order cavalry to arrive.

Thanks for the heads up, just getting the hang of the forum 'workflow'.

Also as per our last discussion - I think C# and Python will be crucial to learn in the near future, but for now I'm trying to get a solid foundation in grasshopper. I'm on deadline for a thesis in May, so time and resources are a bit tight at the moment.

cavalry arrived (but there's nobody to kill - except a very little thingy, he he).

PS: what this weird thing does?

PS: P and C they don't mix: kinda like Vodka with Budweiser. Me? pass me the spirit please (in the literal sense).

all the best for your thesis (take no prisoners, etc etc)

Forgot the thing

Attachments:

And when I use grafted and simplified lists on sweep2, they do exactly what I was trying to do! For some reason the numbering of the indexes make perfect intuitive sense to me now. Fun! Thanks for the drinking tips, maybe one day I will wake up from a vodka/budweiser induced stupor and have mapped out my entire thesis ;)

A thesis is primarily a spiritual thing (meaning: add spirit(s), what else? he he).

Study a bit more these mysterious data trees (=> an "indexed" collection of single dimension "arrays" (i.e. Lists)).

Tip of the day (using spirits):

Imagine a match and a matchbox. Chop/mince the match into pieces and glue them together (use Loctite SG: fast and faulty). This is an "array" (i.e. a List: an "ordered" collection of something). Do the same with the rest of the matches (use spirits).

Put matches into the matchbox: this is a DataTree with 2 dimensions: {matchBoxLayer; matchColumn}[whatMatchPiece].

Put several matchboxes in a shelf: this is a DataTree with 3 dimensions: {whatMatchBox;matchBoxLayer; matchColumn}[whatMatchPiece].

Use several shelfs: this is a DataTree with 4 dimensions: {whatShelf;whatMatchBox;matchBoxLayer; matchColumn}[whatMatchPiece].

repeat until no spirit(s).

Notify if you need something else for that thesis (but what this def does? Is it a graphical interpretation of something? )

Doing this without spirits is too sobering for words.

I did some reading in the grasshopper primer, and the nesting of items in the datatree is starting to make more intuitive sense. I also found the paramviewer component which makes my trees look like trees!

The definition basically simplifies any curve and:

-makes a surface out of the resulting closed curve

->solves the circumscribed circles in the new surface

->finds the tangent arcs between all of the circles

->creates 3d geometry of the circles and arcs

->draws serial sections of the resulting 3d geometry

->generates a watertight single brep that approximates the combined geometry of all the breps mushed together

I'm having a lot of trouble with the last two steps, and I think the problems are linked.

Basically, plugging x amount of breps into the 'solid union' component has not thus far resulted in a single massive brep. I've searched for reasons why, and those reasons seem complicated. So instead, I thought I would contour all of the breps, extract the profile of each contour, and loft between them to get an approximation of the breps. This has been impossible for me to pull of so far, because I don't know how to organize the information the way I need to. The bottom data tree visualization is what I started out with. 48 curves with separate indexes. If you look at the top most data tree visualization, the data seems to be separating into two separate paths using the path mapper. It looks like two separate paths (0 and 1), but it is not. Basically, there are two instances where the breps are being contoured, and instead of dividing the resulting intersections by the index of the contour, they are divided by the index of the brep with which they are associated. I have no idea what to do. Been playing with this for awhile.

Hi Isabelle, I think you'll want to flatten the input of SolidUnion component (instead of the output). I didn't check your files yet (there may be other issues), but this is what I noticed in your 'screenshot201' image. No complicated reason there.

Hi Pieter,

would that it were so. The component gets orange and says "boolean union set is empty". I've tried a few different combo moves of flattening before trying the solid union, and they all yield the same message.

Hi Pieter, the files are really big, I need to reduce them somewhat before I can share them here.

grasshopper file

Attachments:

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service