docs: add comprehensive docstrings to YOLO utility functions

[Rudra-Tiwari-codes]

Added Google-style docstrings with Args/Returns documentation to:

• YOLO_util_nms: Non-Maximum Suppression
• YOLO_util_multiclass_nms: Per-class NMS
• YOLO_util_compute_iou: IoU calculation
• YOLO_util_xywh2xyxy: Bounding box format conversion
• YOLO_util_draw_detections: Detection visualization
• YOLO_util_draw_box: Bounding box drawing
• YOLO_util_draw_text: Text label drawing
• YOLO_util_draw_masks: Overlay mask drawing

Addresses issue #847

Summary by CodeRabbit

• Documentation
  • Improved internal documentation for YOLO utility routines by adding comprehensive docstrings and explanatory comments to clarify behavior and usage. These changes are documentation-only and do not alter functionality or user-facing behavior.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[github-actions]

⚠️ No issue was linked in the PR description.
Please make sure to link an issue (e.g., 'Fixes #issue_number')

[coderabbitai]

📝 Walkthrough

Walkthrough

Docstrings were added to multiple YOLO utility functions (NMS, multiclass NMS, IoU, coordinate conversion, drawing helpers, and model path retrieval). No function signatures, control flow, or behavior were changed.

Changes

Cohort / File(s)	Summary
YOLO Documentation Enhancement backend/app/utils/YOLO.py	Added comprehensive docstrings to NMS, multiclass NMS, IoU computation, coordinate conversion, drawing utilities, and model path retrieval functions. Documentation-only changes; no functional impact.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A rabbit hopped through doc and code so bright,

It tuned each docstring, line by line, just right.
No logic altered, only guidance spun—
Now readers find the functions, one by one.
Hoppity thanks for clearer light! 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'docs: add comprehensive docstrings to YOLO utility functions' accurately describes the main change—adding docstrings to YOLO utility functions with no behavioral modifications.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 047868f and 9829e62.

📒 Files selected for processing (1)

• backend/app/utils/YOLO.py

🚧 Files skipped from review as they are similar to previous changes (1)

• backend/app/utils/YOLO.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

⚠️ No issue was linked in the PR description.
Please make sure to link an issue (e.g., 'Fixes #issue_number')

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 81286fa and 047868f.

📒 Files selected for processing (1)

• backend/app/utils/YOLO.py

🔇 Additional comments (8)

backend/app/utils/YOLO.py (8)

93-108: Well-documented NMS function.

Docstring is clear, accurate, and follows Google style conventions. Parameter descriptions match the actual implementation.

---

131-145: Accurate multiclass NMS documentation.

Docstring clearly conveys the independent per-class NMS application. Implementation aligns with documented behavior.

---

161-174: Clear IoU computation documentation.

Docstring provides good explanation of IoU metric and parameter shapes. Implementation correctly computes vectorized IoU values.

---

196-206: Well-explained coordinate conversion.

Docstring clearly describes the conversion from center format to corner format with helpful explanations of what each coordinate represents.

---

262-275: Clear bounding box drawing documentation.

Docstring accurately describes the function's purpose and parameters, with good clarity on the BGR color format.

---

286-299: Accurate text drawing documentation.

Docstring correctly describes the function, including the helpful detail about the filled background for the text label.

---

326-337: Well-documented mask drawing function.

Docstring accurately describes the masking behavior and provides clear explanations of the transparency parameter range.

---

353-361: Clear model path retrieval documentation.

Docstring accurately describes the function's purpose and parameters. The return value is well-documented.

[fransafu]

Warning: This author is forking multiple ML projects such as google-deepmind/alphafold, ml-explore/mlx, openai/CLIP, pytorch/pytorch, tensorflow/tensorflow, anthropics/claude-code, vllm-project/vllm, and others, adding minimal "contributions" (often for tests or miscellaneous changes) without proper validation. A review of their commits shows mostly local implementations of TODOs copied from existing projects, with little to no substantive review or testing.

So far, this author has forked 41 repositories following the same pattern. Be careful when accepting this PR. It’s also concerning how this author is able to submit PRs across four repositories in the same day, each requiring large context, which strongly suggests a highly automated workflow.

[Rudra-Tiwari-codes]

Thank you for the feedback regarding my recent activity. I am a student and I have been using these smaller tasks as a way to familiarize myself with the architecture of various codebases. I was not aware that submitting multiple minor pull requests was considered disruptive to the maintainer workflow or seen as contribution padding. I appreciate the correction and will pay much closer attention to the impact of my work moving forward. I am closing this pull request now to focus on delivering more substantive technical contributions that provide genuine value to the community.