Skip to content

Optimize get_cluster_candidates with numpy#13

Merged
ManupaKDU merged 1 commit into
devfrom
optimize-cluster-candidates-numpy-10958264842689069209
May 22, 2026
Merged

Optimize get_cluster_candidates with numpy#13
ManupaKDU merged 1 commit into
devfrom
optimize-cluster-candidates-numpy-10958264842689069209

Conversation

@ManupaKDU
Copy link
Copy Markdown

This PR refactors get_cluster_candidates within frigate/util/object.py to utilize numpy operations. The optimization significantly limits the number of Python-side loop operations for inner list comprehensions, effectively completing the TODO: see if we can do this with numpy.

  1. Replaced the inner compare_box looping bounded box comparisons with a vectorized condition inside_mask applied to a boxes_arr.
  2. Changed used_boxes from a list to a set() to grant O(1) checks.
  3. Implemented np.any(box_areas / region_area < 0.05) rather than manually looping and recalculating area ratios over potential cluster candidates iteratively.

PR created automatically by Jules for task 10958264842689069209 started by @manupawickramasinghe

Resolves the TODO item in `frigate/util/object.py` line 402.

- Early exit if the list of boxes is empty.
- Converts the loop-based nested iteration into a vectorized `np.where` query for improved efficiency and readability.
- Replaces the list lookup for used indices with an O(1) set.
- Vectorizes the proportional area size logic to determine cluster feasibility.

Co-authored-by: manupawickramasinghe <73810867+manupawickramasinghe@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@github-actions
Copy link
Copy Markdown

PR template validation failed

This PR was automatically closed because the description does not follow the pull request template.

Issues found:

  • Missing section: ## Proposed change
  • Missing section: ## Type of change
  • Missing section: ## AI disclosure
  • Missing section: ## Checklist
  • The Proposed change section is empty. Please describe what this PR does.

Please update your PR description to include all required sections from the template, then reopen this PR.

If you used an AI tool to generate this PR, please see our contributing guidelines for details.

@github-actions github-actions Bot closed this May 22, 2026
@ManupaKDU ManupaKDU reopened this May 22, 2026
@ManupaKDU ManupaKDU merged commit 9892c8e into dev May 22, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant