I’ve been using EdgeContinuity, and while it seems to analyze tangency PERFECTLY (woo hoo!) I’m concerned that it’s giving me bad readings with respect to G2/curvature. I made a simple ball corner, and intentionally left some edges imperfect, then compared the result with VSR’s Global Matching Analysis. Most worrying - some edges that Rhino is saying are ok, VSR is saying the opposite. Also - none of the values are matching up like the do for tangency. For instance - the edge on the right that I call out in the video below - EdgeContinuity gives me a curvature value of 0.003 (0.005) - very good!
whereas VSR gives me a value of 0.79 - quite bad!
More weirdness - if you look at the “deviation comb” shown in V7 along the edge in question, and compare it to the edge above it here:
What catches my eye is that the comb on the edge on the right shows a higher amplitude than the edge above it, and yet Rhino sees that edge as 0.002 (1.000), which I would say means the matching along this edge is worse? As I say in the video, I’m not exactly sure how to interpret in real world usage what it means to have both these numbers (absolute and relative), but really my biggest worry is that I can’t trust the numbers Rhino is giving me.
Refit Trim_RH5_2.3dm (1.9 MB)