same size paneling - connecting the dots

Replies to This Discussion

Permalink Reply by Andrew Heumann on November 30, 2010 at 2:58pm

If you're willing to break away from 0.6.059, version 8 introduces a very easy way to accomplish this, using the new relative paths component.

Attachments:

• relative_paths.ghx, 827 KB

Permalink Reply by taz on November 30, 2010 at 3:11pm

Can you explain how the relative path implementation works...

Specifically, why is the offset is causing some branches to be culled?

And what is the difference between the A and B output?

Permalink Reply by Andrew Heumann on November 30, 2010 at 9:38pm

This is, to be honest, the first time I've used it, so I might misrepresent it a bit. As I understand it, it basically operates like shift list, but on paths instead of items - my input says {0;0;0;0;1;0}, which shifts the 5th level of tree hierarchy by -1 and 1, output into A and B respectively. The two boolean inputs to the component control whether or not paths and items wrap, and since they are both false, there is a culling of branches.

edit: just noticed david posted a much more thorough explanation of it here: http://www.grasshopper3d.com/forum/topics/grasshopper-080002-availa...

Permalink Reply by taz on December 1, 2010 at 6:50pm

Yeah, I did read that but a visual example would help immensely...

Permalink Reply by Nick Bruscia on November 30, 2010 at 3:20pm

I'm running v8 on my personal machine, but the campus machines will not be updated until next semester so for now we've got v6.

Thanks for the advice on the new component, and your sample script - I had not attempted to use it as of yet.

It would be very useful for me, and probably others to understand the basics of something like this without the use of the new component as well.

Permalink Reply by Ángel Linares on November 30, 2010 at 4:36pm

Wooo the use of this componet here seens to be amazing :D

Permalink Reply by Nick Bruscia on December 1, 2010 at 2:29pm

Thanks again!

upon opening the file up in v08, I'm noticing something odd ...

The t from the Divide Curve component is outputting values from 0 - 1 (making the surfaces very small of course), as opposed to values that would represent more accurate dimensions along the line. In v06, and from what it seems like in your file as expressed through the image above, it is working just fine ....

?

Permalink Reply by Nick Bruscia on December 2, 2010 at 8:10am

anyone have any insight on this?

Permalink Reply by Andrew Heumann on December 5, 2010 at 5:55pm

Sorry, didn't see this question until now. t-parameters don't represent dimensions - they are a function of the domain of the curve, which usually has nothing to do with the curve's dimension. For simplicity's sake, it is common to "reparameterize" curves to guarantee that their domain is reset to be from 0-1. Lines between two points generated in grasshopper automatically have the domain from 0-1, whereas straight lines generated in rhino and referenced will have a domain related to their length. In general I always choose the "reparameterize" option for my curve parameters in order to guarantee predictable behavior.

Hope this answers your question!