isl-org / isl-org/Open3D

Plane Segmentation changed in 0.15.1?

Open
#4,899 1 comment 0 reactions 0 assignees View on GitHub
question
Dominant language
C++
Stars
14k
Forks
2.6k
Avg merge
5d 18h
Merged PRs (30d)
6

Description

### Checklist

- [X] I have searched for [similar issues](https://github.com/isl-org/Open3D/issues).
- [X] For Python issues, I have tested with the [latest development wheel](http://www.open3d.org/docs/latest/getting_started.html#development-version-pip).
- [X] I have checked the [release documentation](http://www.open3d.org/docs/release/) and the [latest documentation](http://www.open3d.org/docs/latest/) (for `master` branch).

### My Question

I implemented a RANSAC plane segmentation followed by a DBSCAN clustering similar to this: https://towardsdatascience.com/how-to-automate-3d-point-cloud-segmentation-and-clustering-with-python-343c9039e4f5.

It works fine in version 0.14.1
![RANSAC-v 0 14 1](https://user-images.githubusercontent.com/80453506/158800813-2303b033-4819-4629-bd75-d85da5b20932.png)
but in 0.15.1 it looks like this.
![RANSAC-v 0 15 1](https://user-images.githubusercontent.com/80453506/158800833-8a0a3937-cd9b-458c-90fa-eaff3abaaec8.png)
I can't figure out why, I already checked my code and the docs + release notes.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the reported RANSAC plane segmentation followed by DBSCAN clustering with the linked example under Open3D 0.14.1 and 0.15.1. Compare the resulting point-cloud segmentation and investigate the version change; done means identifying whether the behavior is an intentional change, a regression, or a usage issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
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.