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

Optimizing the angular hits #170

Open
cgyurgyik opened this issue May 17, 2020 · 0 comments
Open

Optimizing the angular hits #170

cgyurgyik opened this issue May 17, 2020 · 0 comments
Labels
optimization Improve code performance

Comments

@cgyurgyik
Copy link
Contributor

cgyurgyik commented May 17, 2020 •
edited
Loading

Currently, the angular hit functions are the computational bottlenecks with many, many floating point operations. So the question is then, how can we reduce the number of calculations, branch predictors, and complexity without affecting the soundness of the algorithm.

What I've done so far:

  • Tried to reduce as many calculations as possible from per ray to per grid. See all of these in SphericalVoxelGrid.h
@cgyurgyik cgyurgyik added the optimization Improve code performance label May 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
optimization Improve code performance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cgyurgyik