Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TASK] Pipeline Detection #2

Open
3 tasks
jorgenfj opened this issue Oct 23, 2024 · 0 comments
Open
3 tasks

[TASK] Pipeline Detection #2

jorgenfj opened this issue Oct 23, 2024 · 0 comments
Assignees
Labels
perception Perception team responsible

Comments

@jorgenfj
Copy link
Contributor

jorgenfj commented Oct 23, 2024

Description of task

We need a way to detect the pipeline from the generated pipeline filter.

Suggested Workflow

Look at the pointcloud implementation of ranSAC for inspiration.

try to create an algorithm that for every image:

  1. Find Line nr. 1
  2. Optimize line with inliers.
  3. If n_inliners > threshold, accept current line
  4. Project inliers onto line to find start and end of line.
  5. Remove inliers from image
  6. Find Line nr. 2
  7. Use the found line and add back the removed inliers to the image to optimize line.
  8. Project inliers onto line to find start and end of line.

Specifications

  • This node takes an Image message as input and should output a PoseArray that represents the pipe.
  • Should find 0-2 lines in an image and output the endpoints of the line.

Contacts

@jorgenfj

Code Quality

  • Every function in header files are documented (inputs/returns/exceptions)
  • The project has automated tests that cover MOST of the functions and branches in functions (pytest/gtest)
  • The code is documented on the wiki (provide link)
@jorgenfj jorgenfj added the perception Perception team responsible label Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
perception Perception team responsible
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants