Explode Crv allows for recursion until “all segments are atomic”. What does atomic mean in this context?
AtomicExplodeQstn.gh (10.9 KB)
The two segment curve is split into two segments because of the seam of the torus.
When no seam is involved in the intersection, True or False make no difference.
Thanks, Martin. I’m still wondering about the vocabulary though: “atomic”. It’s not a term I’ve seen anywhere else in Rhino/gh.
Also, I am surprised by the following:
- That there are so many segments. Are they dictated by discontinuities? If yes, why are two simple srfs creating so many discontinuities?
- In your example above, with the seam moved out of the intersection, why does “Recursive = No” result in 29 segments when a simple Rhino explode maintains one continuous crv?
In Nurbs representation, circles, spheres and tori are not simple shapes at all.
In order to achieve it, you either need to split it into multiple non-rational Bezier shapes or make it rational (“apply weighting”) in a single composite. Rhino chooses the second, but this makes intersections more difficult to compute.
Intersection curves are not necessarily discontinuous, but they can consist of a large amount of Bezier segments. The quality of the intersection will greatly impact further modelling. Therefore simplification is important.
You can dismantle a poly-curve into multiple Nurbs curves and each Nurbs curve can be dismantled into their Bezier segments. By doing this, you just see the problem it usually hides from you. One of the reasons to work with unweighted and low-span surfaces is that it simplifies intersections and improves model quality.