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

Add qslim decimation feature #115

Merged
merged 1 commit into from
Apr 25, 2024
Merged

Add qslim decimation feature #115

merged 1 commit into from
Apr 25, 2024

Conversation

odedstein
Copy link
Collaborator

Default libigl behavior for decimate is shortest edge decimation. With this PR, people can use our decimate function to choose between libigl's shortest edge and qslim implementations.

Default behavior as of this PR is shortest edge. Do we want to keep it that way?

Also, we should consider bumping the libigl version - newer libigl versions can prevent self-intersections in decimation.

@odedstein odedstein added the enhancement New feature or request label Mar 14, 2024
@odedstein odedstein requested a review from sgsellan March 14, 2024 18:21
@sgsellan
Copy link
Owner

This looks good to me. I don't know that it is worth changing the default (and therefore turning this into a breaking change). If anything, I say we merge it as it is, and consider changing the default behaviour in the next major release (we can even make the PR after this is merged and label it as a breaking change ready to merge).

Re. bumping libigl: I agree we should do it, but let's do it in a different PR. Otherwise we can fall into the "one PR does many things" trap.

@sgsellan sgsellan added the ready to merge This PR is finished and will be merged for the next release label Apr 25, 2024
@odedstein odedstein merged commit 089a060 into main Apr 25, 2024
31 checks passed
@sgsellan sgsellan deleted the enable-qslim-decimation branch June 24, 2024 03:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ready to merge This PR is finished and will be merged for the next release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants