(Wish/Question) PointDeviation Update/History

[Tom_P]

(Mac Intel Rhino 8)

A workflow i stuck with:
(to be honest: more a workaround then a because of missing _matchSrf functionality/features)

how can I autoupdate the measured points while _pointDeviation is active ?

some simplified example:
let s say i want to _matchSrf with pull option (and history) to match the green surface onto the black one:

i can _dupEdge with history and use 200 sample points on this curve (duplicated edge) against the target surface:

but if i edit the surface - the duplicated edge (curve) updates, but not the samples (point locations) used by _pointdeviation:

… see the moved cvs, but the static position of the samples.

do i miss something ?

Background:
_matchSrf (what a pity it did not get more love for V9 until now)
_matchSrf does not feedback deviation if refine is of
_matchSrf can not be stopped by a maximum number of knots that are inserted by refine
(A) _matchSrf with pull option and history would be quite nice for finding trim positions for complex transitions.
(B) manual inserting knots or changeDegree is a nice option to stepwise reach the final surface grain / Degree / CV-Count

i miss a tool for interactive “inner surface match analysis”.
edgeContinuety
crvDeviation
global edge Analysis
PointDeviation
as far as I see - none of them can serve this.

thanks for any tips if i miss something
(At)Mcneel - thanks for more love for matchSrf and a suitable analyse tool.

the video shows the workflow i would like to be able… - _matchSrf with History and pull option

• CV-editing with _matchSrf updating
• deviation display (green = good = < 0.0005)
• custom refining by changeDegree and insertKnot until tolerance is met.

here i am using a custom grasshopper script (mainly using grasshopper only for prototyping the update feature - deviation and display stuff inside a scripting component)

[Gijs (Gijs de Zwart)]

@Tom_P

a tool for interactive “inner surface match analysis”

I might be able to make this work without any UI change in GlobalEdgeContinuity, with some restrictions, if these sound reasonable:

• the edge to match having full overlap with the surface(s)
• the edge to match is untrimmed
• it would work with manual matching for live preview

RH-97155 Analyze surface edges on surface

[Tom_P]

@Gijs

• he edge to match having full overlap with the surface

you mean the entire (untrimmed) edge is matched to single surface - that would be fine.
(hopefully you not mean, the edge must be long enough to trim the target surface, going from any edge, to any other edge…)

i am preparing a lecture for this handle - as soon as i have a nice result i’ ll post it, and mark a surface, where i used above workflow. (and might serve as a nice test-case).

thanks - best - tom

[Gijs (Gijs de Zwart)]

got something working:

[Tom_P]

looks nice. (you might apply for the fastest wish fulfilment-award… )

@davidcockey and @Rhino_Bulgaria @gustojunk and @Lagom would be people that will give a valuable feedback on this (hopefully)

[Rhino_Bulgaria (Bobi)]

Great job by both of us! Finally, this old request was fulfilled!

The next big step is to allow project and pull surface matching on multiple target surfaces. Alias can do this for decades.

[Gijs (Gijs de Zwart)]

@Rhino_Bulgaria

on multiple target surfaces

this is possible but it has one disadvantage that this will also mean edges next to it get picked up:

What I could try is ignoring edges that don’t have entire coverage

[Rhino_Bulgaria (Bobi)]

Sorry for the confusion. What I meant is to enable picking of multiple target surfaces for the “On surface” option of the “Match surface” tool. Currently, it allows just a single target surface to be used.

[Gijs (Gijs de Zwart)]

@Rhino_Bulgaria

What I meant is to enable picking of multiple target surfaces for the “On surface” option of the “Match surface” tool

OK, then that’s a different topic, see Project match edge onto two surfaces? and YT in that thread

[Rhino_Bulgaria (Bobi)]

While the link you posted is older, we had a much more extensive conversation in another topic:

Wish: More options for "Match surface"

That’s also a welcomed improvement. It have been requested multiple times over the years. Here is one of my posts where I linked a video example of how the projected match works in Alias: And here is the same video for a quick overview (after the 9:10 minute is where it gets really interesting): [Using the Align Function in Alias: Part 4 of 5]

The solution in Alias from the video in this particular post does not show projecting to multiple surfaces. However, it demonstrates several other key options that are a good inspiration for future improvements of Rhino’s own “Match surface”.

[brian (Brian Gillespie)]

RH-97155 is fixed in Rhino BETA