range_search_2d is faster now for counting queries #424
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.
When the weight range [a,b] is entirely within the query range [p,q], it is not necessary to go all the way down to$\lg{\sigma}$ levels inside
_range_search_2d
-- the 3-line additional check speeds up counting (of course, not reporting -- for reporting we need to recover the weights bottom-up) queries few times, on reasonably large datasets.