This repository was archived by the owner on Dec 22, 2021. It is now read-only.
Conversation
leouieda
added a commit
that referenced
this pull request
Sep 19, 2013
Speed improvements to `gravmag.tesseroid`
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Moved some things over to Cython, precomputing sines and cossines, using buffers to avoid malloc in loops and removed most numpy array fancy indexing.
Comparing to Tesseroids (written in C):
Current bottlenecks are:
So it seems that, if I need to split he tesseroid a lot, then the Python code is really slow.
But in cases that I have computation at least 1x size of tesseroid away, the Python code is much faster the C.