Performance improvement of npairs_s_mu_engine.pyx #623
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.
I noticed that s_mu_tpcf from from halotools.mock_observables is extremely slow and found that npairs_s_mu_engine.pyx had a very inefficient loop structure. I made small changes to the engine. s_mu_tpcf is now ~3 times faster when using 20 bins in s and mu. Previously, it took ~30 sec for a zheng07 mock (threshold -19) in bolplanck and now takes ~10 sec.
I have checked that the engine (and npairs_s_mu_engine.pyx) give identical results for this particular, non-trivial use case. I did not perform any other tests.