You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the GeomAPI_PointsToBSplineSurface to obtain a continuous spline surface that approximates a discrete surface described by an array of points in 3D space.
At the end, I would like to evaluate the accuracy of the approximation. This means, I would like to estimate the difference between the surface point values and the original points.
However, from what I understand, the approximation algorithm does not necessarily use an equi-distant u and v arrays to parameterize the spline surface. Therefore, I do not have the correct u and v values a priori (the values that would give me the correct point values on the surface).
Is there any way to extract these u and v values so that I can correctly evaluate the spline surface at the correct u and v points?
The text was updated successfully, but these errors were encountered:
Hi there pythonocc-core community,
I am using the
GeomAPI_PointsToBSplineSurface
to obtain a continuous spline surface that approximates a discrete surface described by an array of points in 3D space.At the end, I would like to evaluate the accuracy of the approximation. This means, I would like to estimate the difference between the surface point values and the original points.
I have followed the example given in https://github.com/tpaviot/pythonocc-demos/blob/master/examples/core_topology_uv_to_cartesian_coordinates.py to extract the values of the surface using the
Value
method.However, from what I understand, the approximation algorithm does not necessarily use an equi-distant
u
andv
arrays to parameterize the spline surface. Therefore, I do not have the correctu
andv
values a priori (the values that would give me the correct point values on the surface).Is there any way to extract these
u
andv
values so that I can correctly evaluate the spline surface at the correctu
andv
points?The text was updated successfully, but these errors were encountered: