Skip to content

Inversion performance bottlenecks #338

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

Open
brandynlucca opened this issue Apr 17, 2025 · 0 comments
Open

Inversion performance bottlenecks #338

brandynlucca opened this issue Apr 17, 2025 · 0 comments
Labels
Milestone

Comments

@brandynlucca
Copy link
Collaborator

The inversion algorithm can take a long time, depending on the resolution and number of scattering model parameters. This should be profiled to identify any significant bottlenecks. Beyond potentially poorly optimized code, the algorithm will simply take a long time when there are many aggregations/cells being inverted. This would likely benefit from being parallelized, if possible.

@brandynlucca brandynlucca added this to the Inversion milestone Apr 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

1 participant