algorithmic modeling for Rhino
There's a whole zoo of curve types coming out of the "Deconstruct Brep" component :
-Closed planar curve
-Line-like curve
-Arc-like curve
-Planar curve
-Circular curve
-Polyline curve
In practice, in my geometry, the same type of edge can be in different categories, which makes me think that either I don't understand the distinctions, either this is a bit messy.
-Is a "Planar curve" necessarily open ?
-Is a "line-like curve" a line ?
-Why do I see "Polylines" with just one line ?"
-Why aren't all my circles in "Circular curves" ? Most of them are "Closed planar curves"
-Why are some of my arcs considered as "Planar curves" when they could be "Arc-like curves" ?
This is so bad that it makes it very difficult to use as a basis for any processing...
Cheers,
Tags:
These are descriptions of curves in general, they have nothing to do specifically with Brep Edges (brep edges are also categorized into; trims, loops, c2_edges, c3_edges).
So, ... curve descriptors:
If a curve is known to be of a special type (circle, arc, rectangle, line) then they are designated as such. If you have a bunch of circles or arcs and they are instead called 'planar [closed] curves', then that is a good indication you don't in fact have circles and arcs at all, what you have is a bunch of nurbs curves that do a good impression of circles and arcs.
If you want to know exactly how Rhino feels about a specific curve, select it and run the _List command. That will tell you the exact type and memory layout of the selected object.
Hi David,
Thanks for the explanations.
I can't imagine that the Breps I am processing heve been made in such a lazy way that it should result in a such variety of curve types for basically the same edge features.
I'll send you the file through a message so you can see for yourself.
Basically, I just need to parse circles and half-circles from all the rest.
With the present distribution, it looks daunting...
Cheers,
If you plug all your curves into an Arc parameter, does it perform all the expected conversions correctly?
You're plugging text into the Arc parameter. The yellow panels convert data into text. You need to plug the actual curves in.
Duh...Of course.
I got mixed-up because I was using the "Member Index" component to sort curve types, and then I needed text, not geometry.
The Arc parameter does a great job in filtering arcs indeed.
There are still forgotten edges.
In the attached for example, I can't see how the missing arc could be anything else than an arc.
Hello Olivier,
the geometry is converted to string once passed through a panel. does it work if you don't you use a panel in-between?
best
alex
*edit it was already answered. ning is not updating threads, with new answers, with refresh.
Hi Alex,
I was stupid on that one :)
Still trying to figure out how to relax the criteria enough to snatch all the arcs.
Changing the tolerance setting seems to have no effect here.
Maybe this could use a set graph :)
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by