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
this is more of a request then an issue. Your work is nice and lightweighted. Simple to use and works very efficient. This is what I can say after 20 min of use.
What I miss or better what I would like to have is a method to compare my pointCloud with the calculated plane. The result of this comparison should be pointCloud where each pixel represents the distance to calculated plane equation.
What do you think about this?
The text was updated successfully, but these errors were encountered:
Yes, we already do this internally in the code by calculating the distance from the inliers to the fitted plane. It is just a case of organizing and externalizing this data!
Or, using your strategy, we could create a transformation from the fitted plane to the x-y plane. The z value of the point is the distance from the point to the plane.
I believe it could be very interesting to show some kind of statistical data from the fitted plane / object to answer questions such as "how much my point cloud is similar to the fitted plane?". I'll be adding this idea for next versions.
Hey there,
this is more of a request then an issue. Your work is nice and lightweighted. Simple to use and works very efficient. This is what I can say after 20 min of use.
What I miss or better what I would like to have is a method to compare my pointCloud with the calculated plane. The result of this comparison should be pointCloud where each pixel represents the distance to calculated plane equation.
What do you think about this?
The text was updated successfully, but these errors were encountered: