⚡️ Speed up function get_detection_size_category
by 8%
#44
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.
📄 8% (0.08x) speedup for
get_detection_size_category
insupervision/metrics/utils/object_size.py
⏱️ Runtime :
1.16 millisecond
→1.08 millisecond
(best of122
runs)📝 Explanation and details
o3-mini
We can optimize the three size‐category functions by unifying the similar logic into a single helper function that converts an array of areas to its corresponding category, using a nested np.where instead of three separate boolean-indexing assignments. In the oriented bounding box function we can make the shoelace computation more concise and potentially faster by using np.roll. The overall behavior remains exactly the same.
Below is the optimized code:
Explanation of the changes made:
✅ Correctness verification report:
🌀 Generated Regression Tests Details