Filleting Polyline @ t question

Hi hoppers,

can anybody explain why filleting a closed polyline at parameter t results in multiple closed curves, each with only one corner filleted?

Attachments:

Fillet@t_question.gh, 3 KB

▶ Reply to This

Replies to This Discussion

Permalink Reply by Vicente Soler on October 14, 2011 at 5:18pm

When you place the mouse cursor over an input a tooltip window appears where you can see the parameter type that the input expects. If the parameter type has [...] written after it, the component will be run once using all the data in the list (e.g. polyline component). If there is no [...] it will run once for every item in the list (e.g. line from two points component).

As you can see, none of the inputs have [...], so as you'd expect with the default "longest list" data matching behaviour, the component will run 4 times creating 4 curves with one fillet each.

▶ Reply

Permalink Reply by Systemiq on October 14, 2011 at 5:25pm

Aaah yeah, at first I thought you could use it on multiple parameters too, but reading the description it says "Fillet a curve at a parameter".

Good tip about the [...] in tooltip window, I never realized what it was meaning.

▶ Reply

Permalink Reply by Pieter Segeren on October 14, 2011 at 5:50pm

Thanks Vicente, I get it:)

I think you understand what I was trying, so my next question is: is that way it was intended to behave? I get the longest list rule, but it seems more usefull to me if we could use this fillet component to set the fillet radius at each corner along the curve. Is my logic off about this?

Do you happen to know of a quick workaround to achieve this behaviour?

▶ Reply

Permalink Reply by Systemiq on October 14, 2011 at 6:05pm

Would need some testing :

Edit: incorrect.

▶ Reply

Permalink Reply by Pieter Segeren on October 14, 2011 at 6:27pm

Still I like it Systemiq, the idea. Let's finds out the fastest and cleanest way we can. Tomorrow:) I'm calling it a day now. Thanks again, love the spirit!

▶ Reply

Permalink Reply by Systemiq on October 14, 2011 at 6:36pm

Very unefficient ! Will optimize it tomorrow, calling it too,gnight!

▶ Reply

Permalink Reply by Vicente Soler on October 14, 2011 at 6:56pm

Maybe something like this. Not very elegant, theres probably a better solution. This method won't allow fillets larger than half the length of the affected segments.

▶ Reply

Permalink Reply by Systemiq on October 15, 2011 at 4:55am

There was actually something much simpler:

▶ Reply

Permalink Reply by Vicente Soler on October 15, 2011 at 5:54am

What if the input curve contains curved segments.

▶ Reply

Permalink Reply by Systemiq on October 15, 2011 at 6:21am

Indeed, thinking about it.

But your solution is probably better.

▶ Reply

Permalink Reply by Systemiq on October 15, 2011 at 9:01am

This seems to work, but its begin to be a bit complicated and probably bugs in some cases :

▶ Reply

Permalink Reply by Pieter Segeren on October 15, 2011 at 5:54am

Thought I'd best reply to my own question with this:
I like your efforts guys, but I should have said I was trying to give a nice clean anwer to Simon Vorhammer's question: http://www.grasshopper3d.com/forum/topics/branching-problem
This is when I stumbled upon the question I posted.