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.

Sign up for GitHub

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

Jump to bottom

Avoid too many locate calls for hint computation #8542

Open
sloriot opened this issue Oct 14, 2024 · 0 comments
Open

Avoid too many locate calls for hint computation #8542

sloriot opened this issue Oct 14, 2024 · 0 comments
Labels
Pkg::Poisson_surface_reconstruction_3 Speed

Comments

@sloriot
Copy link
Member

sloriot commented Oct 14, 2024 •
edited by MaelRL
Loading

Detected while working on #7891.

get_hint() is using a locate in the triangulation. However, we can already know from the previous step where we already are, and we could save the call to locate. We should check the cost of those "extra" locate and see how to port the location info from the previous step.
@sloriot sloriot changed the title Avoid too many locate call for hint computation Avoid too many locate calls for hint computation Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Pkg::Poisson_surface_reconstruction_3 Speed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sloriot