Sweep1 Multiple Section Curves Index "Matched"

Replies to This Discussion

Permalink Reply by peter fotiadis on February 21, 2015 at 2:53am

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

Permalink Reply by Isabelle Angieri on February 21, 2015 at 10:21am

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

Permalink Reply by Isabelle Angieri on February 21, 2015 at 10:25am

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.

Permalink Reply by peter fotiadis on February 21, 2015 at 11:51am

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)

Permalink Reply by peter fotiadis on February 21, 2015 at 12:10pm

Forgot the thing

Attachments:

• Sweep1.gh, 32 KB

Permalink Reply by Isabelle Angieri on February 22, 2015 at 2:31pm

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 ;)

Permalink Reply by peter fotiadis on February 23, 2015 at 12:47am

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? )

Permalink Reply by Isabelle Angieri on February 28, 2015 at 4:46pm

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.

Permalink Reply by Pieter Segeren on February 28, 2015 at 5:19pm

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.

Permalink Reply by Isabelle Angieri on February 28, 2015 at 6:53pm

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.

Permalink Reply by Isabelle Angieri on February 28, 2015 at 6:58pm

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

Permalink Reply by Isabelle Angieri on February 28, 2015 at 7:04pm

grasshopper file

Attachments:

• SolidUnion.gh, 9 KB

• ‹ Previous
• 1
• 2
• Next ›
• Page