PointCloudLibrary / PointCloudLibrary/pcl

[Surface] "When I use "Fitting trimmed B-splines to unordered point clouds" example to fitting surface. I found Data points are partially clipped"

Open
#5,164 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind: request status: triage
Dominant language
C++
Stars
11.1k
Forks
4.7k
Avg merge
4d 10h
Merged PRs (30d)
6

Description

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [ I use "Fitting trimmed B-splines to unordered point clouds" example to fitting surface. I found Data points are partially clipped].

Context

When I use "Point Cloud Show" example to show the gauge.pcd file,the result show like this picture:
image
It's obviously a rectangular gauge. Howerve, when I use "Fitting trimmed B-splines to unordered point clouds" example to fitting surface. The result show like this video:

https://user-images.githubusercontent.com/74819962/153527696-c11b6208-b6f3-4a95-9fd6-389c0f4c678c.mp4

Expected behavior

Therefore I want to fitting the surface which is accurately closed to the cloud point .

Describe the solution you'd like

I'm guessing that the "Fitting Trimmed B-Splines to Unordered Point Clouds" program trimmed some of the data, so I want to know a solution to the surface fit.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the result with the "Point Cloud Show" example and gauge.pcd, then compare it with the "Fitting Trimmed B-Splines to Unordered Point Clouds" example. Determine why parts of the point cloud are clipped and establish a fitting result that remains accurately closed to the cloud points.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-vision
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.