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

Laplacian edges seem to jump? #5

Open
FranzEricSchneider opened this issue Feb 6, 2023 · 5 comments
Open

Laplacian edges seem to jump? #5

FranzEricSchneider opened this issue Feb 6, 2023 · 5 comments

Comments

@FranzEricSchneider
Copy link
Contributor

I was looking at the edges for the skeleton_graph (thanks for #3 by the way) and it looks like the edges are jumping from spot to spot and skipping a lot of the skeleton. Is that intended?

Brown(ish) is the original cloud, blue is the skeleton (contracted points) and green is the skeleton_graph (open3d LineSet)

Screenshot from 2023-02-05 19-29-59

@FranzEricSchneider
Copy link
Contributor Author

Another example:

Screenshot from 2023-02-05 19-33-14

@meyerls
Copy link
Owner

meyerls commented Mar 27, 2023

Hi @FranzEricSchneider,

Sorry for the late response. The green line set is the topological representation of the skeleton. In the next days I will review the documentation and the code to make things more clear. Stay tuned!

@meyerls meyerls closed this as completed Mar 27, 2023
@FranzEricSchneider
Copy link
Contributor Author

Is a non-topological set of skeletal lines available that follow the shape better? For the use I was trying this for, for example, the topological lines weren't of use since they don't follow the object shape.

@meyerls
Copy link
Owner

meyerls commented Mar 27, 2023

No, currently it is not implemented. I will implement it in the next update!

@meyerls meyerls reopened this Mar 27, 2023
@FranzEricSchneider
Copy link
Contributor Author

No worries, for reference what I was trying to do what go from (point cloud -> skeletal line segments). I think the default Laplacian Contraction on Points method from the paper doesn't really do that, it just calculates the compressed points. I think there are a number of ways that line segments could be generated on compressed points, depends on which approach you find the most simple and compelling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants