-
Notifications
You must be signed in to change notification settings - Fork 4
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
Fix vedo api #88
Open
jo-mueller
wants to merge
14
commits into
haesleinhuepf:main
Choose a base branch
from
jo-mueller:fix-vedo-API
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Fix vedo api #88
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
c59f5e0
replaced `.points()` with `.vertices`
jo-mueller 7060575
fixed call to deprecated `._data`
jo-mueller d409e92
replaced call to faces()`` with `cells`
jo-mueller 723ae03
replaced deprecated `compute_connectivity`
jo-mueller 747c9d5
update vedo version
jo-mueller bcdb609
removed `__main__`
jo-mueller 5bf3823
re-introduced connected-components labelling
jo-mueller f4d2148
Introduced split-mesh function according to new vedo API
jo-mueller 92cd994
Added mention of both functionality (connected components & split) to…
jo-mueller bc99d09
added test coverage for both
jo-mueller 1d81b06
fixed test
jo-mueller 4bcdd92
Changed connected components labelling function name to original
jo-mueller 0826bb1
removed unused __main__
jo-mueller 0ae5a7b
removed deprecated `origin` display
jo-mueller File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change seems unrelated to the PR title. Also does it break backwards compatibility?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@haesleinhuepf Thanks for looking at this. I thought about it for a while and came to the conclusion that it really is a breaking change, already from the vedo side. The original
compute_connectivity
function allowed to retrieve a per-vertex label which indicated to which object it belonged, which we could then nicely display as the vertex color.In the new version, the
id
of each vertex isn't public anymore and vedo just returns a list[mesh1, mesh2, ...]
of the connected components :/To answer your question: The function
mesh.compute_connectivity()
has been renamed in vedo tomesh.split()
so I'd consider that as part of an API change, and it has been done so in a breaking way.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But we could use the split function to implement what has been there before, correct? I'm asking because I'm using this stuff in projects. Removing it is no option
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure, tbh. The split function never exposes which vertex belongs to which object. -_-
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But it gives lists of vertices grouped, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It returns a list of meshes. Each mesh consists of vertices
[0, n_mesh_i]